From owner-ietf@ietf.org  Sun Feb  1 01:02:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26747
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 01:02:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnAXO-0005CI-Ix
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 00:52:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnAW1-0005BG-Ly
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 00:51:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26548
	for <ietf@ietf.org>; Sun, 1 Feb 2004 00:51:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnAVz-0002Pe-00
	for ietf@ietf.org; Sun, 01 Feb 2004 00:51:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnAV3-0002L6-00
	for ietf@ietf.org; Sun, 01 Feb 2004 00:50:29 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnAUE-0002Bw-00
	for IETF@ietf.org; Sun, 01 Feb 2004 00:49:38 -0500
Received: from BBFUJIP (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with SMTP id i115vDd31024;
	Sat, 31 Jan 2004 21:57:13 -0800
From: Dave Crocker <dhc@dcrocker.net>
To: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
CC: <IETF@ietf.org>
X-Mailer: PocoMail 3.01 (1661) - EVALUATION VERSION
X-URL: http://www.pocomail.com/
Reply-To: dcrocker@brandenburg.com
Date: Sun, 1 Feb 2004 11:39:40 +0900
Message-ID: <200421113940.823448@BBFUJIP>
In-Reply-To: <401AA551.3000104@stewart.chicago.il.us>
Subject: Re: Death of the Internet - details at 11
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,DATE_IN_PAST_03_06 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Randall,

>>Let's see.  I get a CIDR network address from one provider.  I get
>>another from another.  I can have my BGP announce both of them all the
>>time or one of them at a time.  I guess I do not see the horrible
>>scaling problem.

RRSh> The scaling problem shows up when you tell the provider of ISP-1
RRSh> to announce a route for the other address... this effectively
RRSh> becomes a "host route" being advertised....

Why would the provider of ISP-1 need to announce a route for the other
address?

And, of course, my own answer is that they would not need
to do this.  The entire point behind having multiple A record
addresses to the same host is so that each address is advertised by
the ISP that assigns it, thereby permitting normal cidr aggregation.

There's an I-D that just came out about this topic
(draft-huitema-multi6-hosts).  It also discusses issues raised by this
approach.


RRSh> But of course the whole point is that we don't need this.. at least
RRSh> not with SCTP

There is a small matter of getting 500 million hosts to convert to
SCTP and then to convert all Internet applications over to it.

So, some additional techniques might be helpful.

For what it's worth, SCTP certainly provided the template for the MAST
proposal and, I would say, exemplifies the control and security model
that is used by several of the candidates.

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>









From owner-ietf@ietf.org  Sun Feb  1 07:07:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08415
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 07:07:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnGFX-0004pr-Ka
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 06:58:51 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnGFO-0004or-8g
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 06:58:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08289
	for <ietf@ietf.org>; Sun, 1 Feb 2004 06:58:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnGFL-0007cG-00
	for ietf@ietf.org; Sun, 01 Feb 2004 06:58:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnGEQ-0007X1-00
	for ietf@ietf.org; Sun, 01 Feb 2004 06:57:43 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnGDf-0007SF-00
	for IETF@ietf.org; Sun, 01 Feb 2004 06:56:55 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i11BvOGe039380;
	Sun, 1 Feb 2004 12:57:25 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.GSO.4.58.0401301944040.6101@stimpy.eecis.udel.edu>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us> <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us> <654669B6-524E-11D8-98F9-000A95CD987A@muada.com> <4018FFFB.2010201@stewart.chicago.il.us> <F2D4652B-52F9-11D8-98F9-000A95CD987A@muada.com> <Pine.GSO.4.58.0401301944040.6101@stimpy.eecis.udel.edu>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <B87A92DA-54AD-11D8-98F9-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Death of the Internet - details at 11
Date: Sun, 1 Feb 2004 12:56:50 +0100
To: "Armando L. Caro Jr." <me@armandocaro.net>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 31-jan-04, at 2:14, Armando L. Caro Jr. wrote:

>> That's why I think it makes more sense to backport the SCTP 
>> multihoming
>> features to TCP so all TCP apps can use them without having to be
>> changed, or even better: contain the changes in a separate shim layer
>> so that all transport protocols can become address agile without 
>> having
>> to be changed.

> TCP maintains congestion control
> information about a single destination, with the assumption that the 
> path
> will not change during the connection. If it does occasionally, then 
> it's
> fine. However, with multihoming, the change may be a common occurance
> throughtout the lifetime of a connection depending on the application 
> and
> the use of the multiple paths (failover, concurrent multipath transfer,
> etc). So TCP (or whatever transport) should not be blind to the fact 
> that
> data is potentially going over a different path. Otherwise, the 
> congestion
> control parameters/algorithms will not work properly.

I don't think path changes are _that_ common with multihoming, either 
today or with a new protocol. In my ODT draft path changes only occur 
when the primary path fails in the first place, as this way the session 
can be compatible with regular TCP (or other upper layer protocol) if 
there are no failures.

> Also, since the transport is maintaining per path information, it is in
> the best decision to decide which path to use. Yes, a shim layer could
> cooperate with the transport to get this info, but then you are 
> changing
> TCP anyway.

I see three steps in the evolution of a shim approach:

1. Implementation in proxy multihoming boxes
2. Implementation as a shim layer in host stacks
3. Integration of the shim layer and common transport protocols

The idea is that a type 1 implementation can work together with a type 
2 or 3 implementation.

> I must admit that I haven't following the multi6 too closely yet, but I
> plan to catch up and follow. But from what I have seen, it seems that 
> SCTP
> is ignored on the sidelines.

Actually the chairs went out of their way to get an SCTP multihoming 
draft in before the deadline. The deadline for submitting drafts that 
would be considered has recently passed, so now is a good time to read 
the drafts and join the architectural analysis that should be starting 
shortly.




From owner-ietf@ietf.org  Sun Feb  1 08:13:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09643
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 08:13:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnHJL-0006MD-MP
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 08:06:51 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnHHH-0006JW-0n
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 08:04:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09524
	for <ietf@ietf.org>; Sun, 1 Feb 2004 08:04:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnHHG-0005dW-00
	for ietf@ietf.org; Sun, 01 Feb 2004 08:04:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnHGU-0005ZE-00
	for ietf@ietf.org; Sun, 01 Feb 2004 08:03:54 -0500
Received: from sccrmhc11.comcast.net ([204.127.202.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnHFs-0005QY-00
	for IETF@ietf.org; Sun, 01 Feb 2004 08:03:16 -0500
Received: from dfnjgl21 (c-24-1-97-129.client.comcast.net[24.1.97.129])
          by comcast.net (sccrmhc11) with SMTP
          id <2004020113024401100e1i92e>
          (Authid: sdawkins@comcast.net);
          Sun, 1 Feb 2004 13:02:44 +0000
Message-ID: <05fa01c3e8c3$b34e8480$0400a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us> <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us> <654669B6-524E-11D8-98F9-000A95CD987A@muada.com> <4018FFFB.2010201@stewart.chicago.il.us> <F2D4652B-52F9-11D8-98F9-000A95CD987A@muada.com> <Pine.GSO.4.58.0401301944040.6101@stimpy.eecis.udel.edu> <B87A92DA-54AD-11D8-98F9-000A95CD987A@muada.com>
Subject: Re: Death of the Internet - details at 11
Date: Sun, 1 Feb 2004 07:02:51 -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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Agreeing with what Iljitsch said, with the addition that the
"deadline" was imposed to get people to submit proposals so the
working group had something to discuss, not to exclude proposals that
show up two weeks later.

The chairs made explicit requests on the mailing list to ANYONE to
submit an SCTP multihoming draft, so SCTP won't be excluded.

Spencer

From: "Iljitsch van Beijnum" <iljitsch@muada.com>
>
> > I must admit that I haven't following the multi6 too closely yet,
but I
> > plan to catch up and follow. But from what I have seen, it seems
that
> > SCTP
> > is ignored on the sidelines.
>
> Actually the chairs went out of their way to get an SCTP multihoming
> draft in before the deadline. The deadline for submitting drafts
that
> would be considered has recently passed, so now is a good time to
read
> the drafts and join the architectural analysis that should be
starting
> shortly.




From owner-ietf@ietf.org  Sun Feb  1 13:15:22 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06429
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 13:15:22 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnLyf-00046E-3s
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 13:05:49 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnLxp-00044m-RK
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 13:04:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06154
	for <ietf@ietf.org>; Sun, 1 Feb 2004 13:04:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnLxo-0004Dc-00
	for ietf@ietf.org; Sun, 01 Feb 2004 13:04:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnLwp-00048t-00
	for ietf@ietf.org; Sun, 01 Feb 2004 13:03:55 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnLw6-0003z0-00
	for ietf@ietf.org; Sun, 01 Feb 2004 13:03:10 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 01 Feb 2004 10:08:57 +0000
Received: from edison.cisco.com (edison.cisco.com [171.71.180.109])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i11I2bet026164;
	Sun, 1 Feb 2004 10:02:38 -0800 (PST)
Received: from cisco.com (sjc-vpn3-652.cisco.com [10.21.66.140]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id KAA28272; Sun, 1 Feb 2004 10:02:37 -0800 (PST)
Message-ID: <401D3F3C.4010305@cisco.com>
Date: Sun, 01 Feb 2004 10:02:36 -0800
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dcrocker@brandenburg.com
CC: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>, IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
References: <200421113940.823448@BBFUJIP>
In-Reply-To: <200421113940.823448@BBFUJIP>
X-Enigmail-Version: 0.83.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave,


> RRSh> But of course the whole point is that we don't need this.. at least
> RRSh> not with SCTP
> 
> There is a small matter of getting 500 million hosts to convert to
> SCTP and then to convert all Internet applications over to it.

I think this argument can be taken too far.  Yes, there are 500 million 
hosts out there.  So long as we don't break the existing world for them, 
there is nothing wrong with adding new functionality.

The next question is whether the new functionality is useful until it's 
implemented in 500 million hosts.  I claim the answer is "yes".  Like 
any other advance it can be used in limited deployments for limited 
purposes until such time as it is generally available.

Imagine an application checkbox that says "try SCTP first".  I think 
part of the SCTP transition, however, should be something more than 
simply modifying socket options.  I would rather see our notion of 
services and well known ports more comprehensively addressed at the same 
time, so as to avoid such "checkbox" solutions in the future.

Eliot




From owner-ietf@ietf.org  Sun Feb  1 13:55:10 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07270
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 13:55:10 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnMeG-0005KF-Jb
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 13:48:48 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnMdU-0005JH-73
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 13:48:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07185
	for <ietf@ietf.org>; Sun, 1 Feb 2004 13:47:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnMdQ-00004v-00
	for ietf@ietf.org; Sun, 01 Feb 2004 13:47:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnMcV-00000H-00
	for ietf@ietf.org; Sun, 01 Feb 2004 13:47:00 -0500
Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnMbl-0007jI-00
	for IETF@ietf.org; Sun, 01 Feb 2004 13:46:13 -0500
Received: by mail.eecis.udel.edu (Postfix, from userid 62)
	id 55DB832E68; Sun,  1 Feb 2004 13:41:56 -0500 (EST)
Received: from stimpy.eecis.udel.edu (stimpy.eecis.udel.edu [128.4.40.17])
	by mail.eecis.udel.edu (Postfix) with ESMTP
	id 88CC732E5F; Sun,  1 Feb 2004 13:41:55 -0500 (EST)
Date: Sun, 1 Feb 2004 13:41:55 -0500 (EST)
From: Janardhan Iyengar <iyengar@mail.eecis.udel.edu>
X-X-Sender: iyengar@stimpy.eecis.udel.edu
To: "Armando L. Caro Jr." <me@armandocaro.net>
Cc: Spencer Dawkins <spencer@mcsr-labs.org>,
        "'ietf@ietf.org' Discussion" <IETF@ietf.org>
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <Pine.GSO.4.58.0401311250190.17658@stimpy.eecis.udel.edu>
Message-ID: <Pine.GSO.4.58.0402011317440.3825@stimpy.eecis.udel.edu>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com>
 <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us>
 <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us>
 <654669B6-524E-11D8-98F9-000A95CD987A@muada.com> <4018FFFB.2010201@stewart.chicago.il.us>
 <F2D4652B-52F9-11D8-98F9-000A95CD987A@muada.com>
 <Pine.GSO.4.58.0401301944040.6101@stimpy.eecis.udel.edu>
 <049e01c3e7af$9809fbb0$0400a8c0@DFNJGL21> <Pine.GSO.4.58.0401311250190.17658@stimpy.eecis.udel.edu>
X-Sanitizer: This message has been sanitized!
X-Sanitizer-URL: http://mailtools.anomy.net/
X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm,v 1.64 2002/10/22 MIME-Version: 1.0
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Spencer/Armando,

I haven't been following this discussion through.. so let me know if I'm
going off track.

> On Fri, 30 Jan 2004, Spencer Dawkins wrote:
>
> > something, transports ignoring path changes makes a lot of sense. If
> > you are changing paths frequently (and round-robin would be the
> > limiting case), slow-starting every time you change paths is
> > excessive - and, if you're going to respond to PATH_CHANGE, what else
> > would you do? You could do congestion avoidance during the first round
> > trip, or actually lose something and do congestion avoidance on the
> > second round trip - not a big difference, conceptually.

Lets assume that the sending transport is allowed to maintain separate
congestion control parameters per path to the destination. I think this
debate about what the sender should do on each PATH_CHANGE would be easier
to resolve with per-path congestion control. The sender may not have to
slow-start on each PATH_CHANGE *if* the sender has "recently" used that
path to send data. Thus, if the sender is changing paths frequently enough
to be sending data on multiple paths concurrently, the sender can evolve
multiple independent cwnds concurrently. If not, a slow-start should not
hurt much. Of course, this is possible only if multihoming is supported at
the transport.

Further, having a multipath aware transport allows us to encode "correct"
Concurrent Multipath Transfer (CMT, or end-to-end load balancing) into the
transport, as against possibly aggressive CMT by an application. A feature
such as PATH_CHANGE is very enticing for app developers to use for CMT.

regards,
jana


---------------------------------------------------------------
         Visit www.narmada.org, www.indiatogether.org
---------------------------------------------------------------



From owner-ietf@ietf.org  Sun Feb  1 15:19:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10374
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 15:19:29 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnNwa-0007O4-7W
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 15:11:48 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnNvl-0007Mn-2H
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 15:10:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09734
	for <ietf@ietf.org>; Sun, 1 Feb 2004 15:10:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnNvj-0006rF-00
	for ietf@ietf.org; Sun, 01 Feb 2004 15:10:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnNuo-0006n3-00
	for ietf@ietf.org; Sun, 01 Feb 2004 15:09:59 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnNuA-0006eG-00
	for ietf@ietf.org; Sun, 01 Feb 2004 15:09:18 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 986C161D30; Sun,  1 Feb 2004 21:08:46 +0100 (CET)
Date: Sun, 01 Feb 2004 00:42:28 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dave Crocker <dhc@dcrocker.net>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Korean visa problems
Message-ID: <1707956441.1075596148@localhost>
In-Reply-To: <1957102450.20040201092241@brandenburg.com>
References: <8BB2DCBD-52A3-11D8-85D8-000A9571873E@us.ibm.com>
 <65300B3E-52A5-11D8-85D8-000A9571873E@us.ibm.com>
 <1957102450.20040201092241@brandenburg.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========267B07A7030094154BCB=========="
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,DATE_IN_PAST_06_12 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

--==========267B07A7030094154BCB==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable



--On 1. februar 2004 09:22 +0900 Dave Crocker <dhc@dcrocker.net> wrote:

> Folks,
>
> NB> 1.  If I'm attending a conference, a visa *is* required.
>
>
> It would be helpful for IETF Management to resolve this matter,
> particularly given the confusion and the short amount of time left.

as far as I can tell, every time they have been asked the question, and it=20
has been clear that the IETF is not a profit-making operation, they have=20
said "no visa".
but they have had no success with getting someone official to deliver on=20
their promise to send a letter saying that.

I'm pushing. they're pushing. doesn't move.




--==========267B07A7030094154BCB==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)

iD8DBQFAHLv4OMj+2+WY0F4RAvZ7AKDHhRRvIWvIAeUBvLND00oesFdaJgCfY6BX
TsUs7ggP6X13xVRaWZDkuYU=
=PCl6
-----END PGP SIGNATURE-----

--==========267B07A7030094154BCB==========--




From owner-ietf@ietf.org  Sun Feb  1 15:41:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11236
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 15:41:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnOLo-0008JZ-T5
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 15:37:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnOL8-0008Ht-PD
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 15:37:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11115
	for <ietf@ietf.org>; Sun, 1 Feb 2004 15:37:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnOL7-0001Ig-00
	for ietf@ietf.org; Sun, 01 Feb 2004 15:37:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnOK9-0001CR-00
	for ietf@ietf.org; Sun, 01 Feb 2004 15:36:10 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnOJX-00016P-00
	for ietf@ietf.org; Sun, 01 Feb 2004 15:35:31 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i11Ka1Ge046382;
	Sun, 1 Feb 2004 21:36:01 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <1707956441.1075596148@localhost>
References: <8BB2DCBD-52A3-11D8-85D8-000A9571873E@us.ibm.com> <65300B3E-52A5-11D8-85D8-000A9571873E@us.ibm.com> <1957102450.20040201092241@brandenburg.com> <1707956441.1075596148@localhost>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <2BC31C56-54F6-11D8-98F9-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Korean visa problems
Date: Sun, 1 Feb 2004 21:35:28 +0100
To: Harald Tveit Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 1-feb-04, at 9:42, Harald Tveit Alvestrand wrote:

>> It would be helpful for IETF Management to resolve this matter,
>> particularly given the confusion and the short amount of time left.

> as far as I can tell, every time they have been asked the question, 
> and it has been clear that the IETF is not a profit-making operation, 
> they have said "no visa".

There was an APNIC meeting in Korea last summer. Maybe APNIC and/or 
attendees can share their visa experiences?




From owner-ietf@ietf.org  Sun Feb  1 21:58:58 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29229
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 21:58:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnU10-0007oY-DS
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 21:40:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnU0Q-0007nD-P1
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 21:40:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28771
	for <ietf@ietf.org>; Sun, 1 Feb 2004 21:40:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnU0P-0001q5-00
	for ietf@ietf.org; Sun, 01 Feb 2004 21:40:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnTyy-0001WB-00
	for ietf@ietf.org; Sun, 01 Feb 2004 21:38:41 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnTxM-00017M-00
	for ietf@ietf.org; Sun, 01 Feb 2004 21:37:00 -0500
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i122amc15363;
	Sun, 1 Feb 2004 18:36:48 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200402020236.i122amc15363@boreas.isi.edu>
Subject: visa or no
In-Reply-To: <2BC31C56-54F6-11D8-98F9-000A95CD987A@muada.com> from Iljitsch van Beijnum at "Feb 1, 4 09:35:28 pm"
To: iljitsch@muada.com (Iljitsch van Beijnum)
Date: Sun, 1 Feb 2004 18:36:48 -0800 (PST)
Cc: ietf@ietf.org, harald@alvestrand.no
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

% > as far as I can tell, every time they have been asked the question, 
% > and it has been clear that the IETF is not a profit-making operation, 
% > they have said "no visa".
% 
% There was an APNIC meeting in Korea last summer. Maybe APNIC and/or 
% attendees can share their visa experiences?

	I did not need a visa to attend the APNIC mtg last year.
	that said, there has been -public- admission that IETF
	attendees conduct business during the IETF mtgs.  If 
	I were a Korean offical who either monitored this list or
	was informed (however incorrectly) that the IETF was, by
	the admission of its attendees, a business conference, I
	might insist on visas for folks who indicate that they are
	entering Korea to attend the IETF.  

	as for me, I understand that spring is a fine time to visit
	Korea, with many interesting things to see and do. Good 
	shopping. Friends I've not seen for a while.  A visit would be
	in order.
	
--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  Sun Feb  1 22:48:15 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00676
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 22:48:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnUz0-00012h-2B
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 22:42:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnUyT-00011H-BO
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 22:42:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00467
	for <ietf@ietf.org>; Sun, 1 Feb 2004 22:42:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnUyP-0007BB-00
	for ietf@ietf.org; Sun, 01 Feb 2004 22:42:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnUxQ-00076n-00
	for ietf@ietf.org; Sun, 01 Feb 2004 22:41:09 -0500
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1AnUwR-0006z1-00
	for IETF@ietf.org; Sun, 01 Feb 2004 22:40:08 -0500
Received: (qmail 61430 invoked from network); 2 Feb 2004 03:52:56 -0000
Received: from h219-110-032-237.catv01.itscom.jp (HELO necom830.hpcl.titech.ac.jp) (219.110.32.237)
  by necom830.hpcl.titech.ac.jp with SMTP; 2 Feb 2004 03:52:56 -0000
Message-ID: <401DC6E6.2070907@necom830.hpcl.titech.ac.jp>
Date: Mon, 02 Feb 2004 12:41:26 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: "Ayyasamy, Senthilkumar \(UMKC-Student\)" <saq66@umkc.edu>
CC: "Armando L. Caro Jr." <me@armandocaro.net>,
        Iljitsch van Beijnum <iljitsch@muada.com>,
        "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>,
        "'ietf@ietf.org' Discussion" <IETF@ietf.org>
Subject: Re: Death of the Internet - details at 11
References: <5EF7D95E17BDAD4A968C812E5ABC390B01108275@KC-MAIL4.kc.umkc.edu>
In-Reply-To: <5EF7D95E17BDAD4A968C812E5ABC390B01108275@KC-MAIL4.kc.umkc.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ayyasamy, Senthilkumar (UMKC-Student);

To summarise, read:

	http://www.ietf.org/internet-drafts/draft-ohta-multi6-8plus8-00.txt

which describes a end2end scalable 8+8 id/loc proposal, a lot different
from Mike O'dell's version of 8+8.

>>Also, since the transport is maintaining per path information, it is in
>>the best decision to decide which path to use. 
 
> *nod*.

Correctly speaking, the transport or the application layer
is the only place to decide which pasth to use, since the
IP layer can not maintain timeout.

Attempt to imitate it by IP layer results in NAT, where connection
will be terminated if there is no packets flow for a timeout period
incorrectly guessed by the IP layer. At the upper layers, it is
often perfectly leagal if there is no traffic for 1 hour over
a live connection. But, NAT behaves badly for such connections.

> It is the main reason why multi addressing is the only 
> architectural possibility to do a scalable MH. The problem with
> the remaining solutions (at shim/new identity/network layer) is 
> that they hide the redundancy factor (multiple address -MA) from
> the users. Given the current state (failures, misconfigurations
> and rate limitations,) e2e check (by measurements) is the only 
> option to check path availability. The MA feature gives user a 
> chance to make a choice based on e2e reachability checks. 

Right.
 
> I dont know why people get suprised by explicit announcement of 
> MA. we have been doing this kind of explicit announcement both 
> in DNS ( multiple NX records) and SMTP ( multiple MX records.) 
> So, in a way SMTP reliability is due to explicit announcement of 
> multiple MX records.

That is an argument I made several years ago.

> id/loc split proposals are cool. But, without modifying the routing
> architecture, they can never provide a e2e reliability or explicit 
> user control feature.

Wrong.

8+8 addressing (ID locator separation) works just fine to support
multiple addresses of a host. Note that Mike O'dell made a poor
proposal of an 8+8 variant does not mean others does not work.

With 8+8 addressing, IP layer needs no modification and routing
architecture works as is.

With 8+8 addressing, all the addresses are passed to the upper
layers and controlled there.

Because IPv6 addressing space was designed to leave a group bit
of 8 byte MAC for 8+8 addressing, transport layers, including TCP,
can check the bit to see whethere a host support end to end
multihoming.

That is, API of TCP with 8+8 addressing needs no modificaiton
and the existing code, including Mozilla, works as is without
even a line of modificaiton.

> OTOH, I don't forsee any routing change at 
> *architectural* level in the near future.

> It is time to think 
> on why id/loc split proposals without routing architecture change 
> kill the e2e control/reliability options and are architecturally 
> incomplete.

There has been a lot of 8+8 id/loc split proposal, most of
which does not change routing architecture.

It is granted that Mike O'dell's GSE was a poor id/loc proposal.

But, it is a problem of GSE, not 8+8 nor id/loc separation.

> So, it is clear that a combination/subset of host-centric MH, 
> transport MA and BGP MH (if there exists a solution which 
> doesn't bloat routing table) is the ONLY possibility to do a 
> scalable MHv6.

Read:

	http://www.ietf.org/internet-drafts/draft-ohta-multi6-8plus8-00.txt

though it does not use BGP in a way you might be thinking, which
is why it does not bloat the routing table.

							Masataka Ohta





From owner-ietf@ietf.org  Sun Feb  1 23:01:49 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01352
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 23:01:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnVBZ-0001kf-UK
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 22:55:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnVB5-0001jD-Aq
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 22:55:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01003
	for <ietf@ietf.org>; Sun, 1 Feb 2004 22:55:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnVB3-0000aa-00
	for ietf@ietf.org; Sun, 01 Feb 2004 22:55:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnVA6-0000Vx-00
	for ietf@ietf.org; Sun, 01 Feb 2004 22:54:15 -0500
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1AnV9P-0000RT-00
	for IETF@ietf.org; Sun, 01 Feb 2004 22:53:32 -0500
Received: (qmail 61530 invoked from network); 2 Feb 2004 04:06:27 -0000
Received: from h219-110-032-237.catv01.itscom.jp (HELO necom830.hpcl.titech.ac.jp) (219.110.32.237)
  by necom830.hpcl.titech.ac.jp with SMTP; 2 Feb 2004 04:06:27 -0000
Message-ID: <401DCA10.7030006@necom830.hpcl.titech.ac.jp>
Date: Mon, 02 Feb 2004 12:54:56 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Daniel Senie <dts@senie.com>
CC: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
Subject: Re: Death of the Internet - details at 11
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us> <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us> <654669B6-524E-11D8-98F9-000A95CD987A@muada.com> <4018FFFB.2010201@stewart.chicago.il.us> <6.0.1.1.2.20040129094026.0308c540@mail.amaranth.net>
In-Reply-To: <6.0.1.1.2.20040129094026.0308c540@mail.amaranth.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Daniel Senie;

> Ah, so you have indeed made routing policy decisions and placed them 
> into the end systems of the originator of the session. This is most 
> interesting. A site which has multiple connections with varying cost has 
> to either live with the routing policy you've encoded into the stack or 
> force dropped packets in some fashion to try to fool your stack.

Routing policy of a site is represented by IGP metric that
my stack at the transport or the applicaiton layer can just
accept IGP information and use it to choose the most favourable
address of my peer. If the chosen address does not work, the
transport or the application layer try others, after
transport or application layer dependent timeout.

There is nothing encoded in the stack.

There is no routing architecture change.

						Masataka Ohta





From owner-ietf@ietf.org  Sun Feb  1 23:05:33 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01505
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 23:05:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnVHO-0001wE-7D
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 23:01:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnVFs-0001rU-9d
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 23:00:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01216
	for <ietf@ietf.org>; Sun, 1 Feb 2004 23:00:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnVFq-00013d-00
	for ietf@ietf.org; Sun, 01 Feb 2004 23:00:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnVEw-0000x7-00
	for ietf@ietf.org; Sun, 01 Feb 2004 22:59:14 -0500
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1AnVDy-0000q5-00
	for IETF@ietf.org; Sun, 01 Feb 2004 22:58:15 -0500
Received: (qmail 61554 invoked from network); 2 Feb 2004 04:11:10 -0000
Received: from h219-110-032-237.catv01.itscom.jp (HELO necom830.hpcl.titech.ac.jp) (219.110.32.237)
  by necom830.hpcl.titech.ac.jp with SMTP; 2 Feb 2004 04:11:10 -0000
Message-ID: <401DCB2B.8020203@necom830.hpcl.titech.ac.jp>
Date: Mon, 02 Feb 2004 12:59:39 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
CC: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>,
        "'ietf@ietf.org' Discussion" <IETF@ietf.org>
Subject: Re: Death of the Internet - details at 11
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us> <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us> <654669B6-524E-11D8-98F9-000A95CD987A@muada.com> <4018FFFB.2010201@stewart.chicago.il.us> <F2D4652B-52F9-11D8-98F9-000A95CD987A@muada.com>
In-Reply-To: <F2D4652B-52F9-11D8-98F9-000A95CD987A@muada.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum;

>>> Ok, we can discuss whether the changes are significant but the fact 
>>> that changes are required at all is the main problem.

>> You don't get new features without change of some sort...

> Sure. But wouldn't it be better to keep the number of places where 
> changes are necessary to an absolute minimum?

"absolute minimum" is not a good terminlogy for technical
discussion.

However, even if we change something for multihoming, it does
not mean we must change API nor source code.

That is, we should use the current IPv6 API for applications,
if any :-), already running over IPv6 even if a host is
multihomed.

And, it is being done with 8+8 addressing, as is described in:

	http://www.ietf.org/internet-drafts/draft-ohta-multi6-8plus8-00.txt

Masataka Ohta





From owner-ietf@ietf.org  Sun Feb  1 23:39:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03574
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 23:39:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnVoQ-0003ff-Jc
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 23:35:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnCqN-0007rL-QA
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 03:20:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00959
	for <ietf@ietf.org>; Sun, 1 Feb 2004 03:20:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnCoJ-0000bC-00
	for ietf@ietf.org; Sun, 01 Feb 2004 03:18:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnCnO-0000Ur-00
	for ietf@ietf.org; Sun, 01 Feb 2004 03:17:34 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnCnF-0000QB-00
	for ietf@ietf.org; Sun, 01 Feb 2004 03:17:25 -0500
Received: from u-61127102210.hotspot.ne.jp (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i118P3d07951;
	Sun, 1 Feb 2004 00:25:03 -0800
Date: Sun, 1 Feb 2004 09:22:41 +0900
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <1957102450.20040201092241@brandenburg.com>
To: Harald Alvestrand <Harald@Alvestrand.no>
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: Korean visa problems
In-Reply-To: <65300B3E-52A5-11D8-85D8-000A9571873E@us.ibm.com>
References: <8BB2DCBD-52A3-11D8-85D8-000A9571873E@us.ibm.com>
 <65300B3E-52A5-11D8-85D8-000A9571873E@us.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,DATE_IN_PAST_06_12,
	PRIORITY_NO_NAME autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

NB> 1.  If I'm attending a conference, a visa *is* required.


It would be helpful for IETF Management to resolve this matter,
particularly given the confusion and the short amount of time left.

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>






From owner-ietf@ietf.org  Sun Feb  1 23:39:56 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03579
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 23:39:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnVkQ-0003ZA-07
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 23:31:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnCqN-0007rJ-2v
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 03:20:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00952
	for <ietf@ietf.org>; Sun, 1 Feb 2004 03:20:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnCpJ-0000gR-00
	for ietf@ietf.org; Sun, 01 Feb 2004 03:19:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnCoL-0000bf-00
	for ietf@ietf.org; Sun, 01 Feb 2004 03:18:34 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnCoB-0000V4-00
	for IETF@ietf.org; Sun, 01 Feb 2004 03:18:23 -0500
Received: from u-61127102210.hotspot.ne.jp (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i118P1d07948;
	Sun, 1 Feb 2004 00:25:01 -0800
Date: Sun, 1 Feb 2004 09:09:26 +0900
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <264468779.20040201090926@brandenburg.com>
To: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
CC: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <401AA551.3000104@stewart.chicago.il.us>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com>
 <19410259999.20040128073646@brandenburg.com>
 <224923613.1075293579@scan.jck.com> <1419514349.20040129143445@brandenburg.com>
 <65886049.1075365973@scan.jck.com> <312347488.20040130103311@brandenburg.com>
 <401AA551.3000104@stewart.chicago.il.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,DATE_IN_PAST_06_12,
	PRIORITY_NO_NAME autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Randall,

>>Let's see.  I get a CIDR network address from one provider.  I get
>>another from another.  I can have my BGP announce both of them all the
>>time or one of them at a time.  I guess I do not see the horrible
>>scaling problem.

RRSh> The scaling problem shows up when you tell the provider of ISP-1
RRSh> to announce a route for the other address... this effectively
RRSh> becomes a "host route" being advertised....

Why would the provider of ISP-1 need to announce a route for the other
address?

And, of course, my own answer is that they would not need
to do this.  The entire point behind having multiple A record
addresses to the same host is so that each address is advertised by
the ISP that assigns it, thereby permitting normal cidr aggregation.

There's an I-D that just came out about this topic
(draft-huitema-multi6-hosts).  It also discusses issues raised by this
approach.


RRSh> But of course the whole point is that we don't need this.. at least
RRSh> not with SCTP

There is a small matter of getting 500 million hosts to convert to
SCTP and then to convert all Internet applications over to it.

So, some additional techniques might be helpful.

For what it's worth, SCTP certainly provided the template for the MAST
proposal and, I would say, exemplifies the control and security model
that is used by several of the candidates.

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>






From owner-ietf@ietf.org  Sun Feb  1 23:40:01 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03612
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 23:40:01 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnVoQ-0003g2-UR
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 23:35:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnVlE-0003ZV-08
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 23:32:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03244
	for <ietf@ietf.org>; Sun, 1 Feb 2004 23:32:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnVlC-0004pj-00
	for ietf@ietf.org; Sun, 01 Feb 2004 23:32:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnVkG-0004hR-00
	for ietf@ietf.org; Sun, 01 Feb 2004 23:31:37 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnVjL-0004T7-00
	for ietf@ietf.org; Sun, 01 Feb 2004 23:30:39 -0500
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i124U7A0004542;
	Sun, 1 Feb 2004 20:30:08 -0800 (PST)
Received: from localhost (ole@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id UAA24349; Sun, 1 Feb 2004 20:30:07 -0800 (PST)
Date: Sun, 1 Feb 2004 20:30:07 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
Reply-To: Ole Jacobsen <ole@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>,
        IETF Discussion <ietf@ietf.org>
Subject: Re: Korean visa problems
In-Reply-To: <2BC31C56-54F6-11D8-98F9-000A95CD987A@muada.com>
Message-ID: <Pine.HPX.4.58.0402012029210.11441@wells.cisco.com>
References: <8BB2DCBD-52A3-11D8-85D8-000A9571873E@us.ibm.com>
 <65300B3E-52A5-11D8-85D8-000A9571873E@us.ibm.com> <1957102450.20040201092241@brandenburg.com>
 <1707956441.1075596148@localhost> <2BC31C56-54F6-11D8-98F9-000A95CD987A@muada.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Yup. Got in and out without any mention of the word "visa", but I don't
have a US passport.

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 Sun, 1 Feb 2004, Iljitsch van Beijnum wrote:

> On 1-feb-04, at 9:42, Harald Tveit Alvestrand wrote:
>
> >> It would be helpful for IETF Management to resolve this matter,
> >> particularly given the confusion and the short amount of time left.
>
> > as far as I can tell, every time they have been asked the question,
> > and it has been clear that the IETF is not a profit-making operation,
> > they have said "no visa".
>
> There was an APNIC meeting in Korea last summer. Maybe APNIC and/or
> attendees can share their visa experiences?
>
>



From owner-ietf@ietf.org  Sun Feb  1 23:40:52 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03640
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Feb 2004 23:40:52 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnVpF-0003hv-JG
	for ietf-list@asgard.ietf.org; Sun, 01 Feb 2004 23:36:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnSkv-0006E5-DX
	for ietf@asgard.ietf.org; Sun, 01 Feb 2004 20:20:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24401
	for <ietf@ietf.org>; Sun, 1 Feb 2004 20:20:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnSkt-0000H9-00
	for ietf@ietf.org; Sun, 01 Feb 2004 20:20:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnSjh-000011-00
	for ietf@ietf.org; Sun, 01 Feb 2004 20:18:50 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnSiJ-0007HT-00
	for IETF@ietf.org; Sun, 01 Feb 2004 20:17:23 -0500
Received: from BBFUJIP.brandenburg.com (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i121Otd17339;
	Sun, 1 Feb 2004 17:24:55 -0800
Date: Mon, 2 Feb 2004 07:24:51 +0900
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <595029237.20040202072451@brandenburg.com>
To: Eliot Lear <lear@cisco.com>
CC: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <401D3F3C.4010305@cisco.com>
References: <200421113940.823448@BBFUJIP> <401D3F3C.4010305@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eliot,

EL> Dave,


>> RRSh> But of course the whole point is that we don't need this.. at least
>> RRSh> not with SCTP
>> 
>> There is a small matter of getting 500 million hosts to convert to
>> SCTP and then to convert all Internet applications over to it.

EL> I think this argument can be taken too far.  Yes, there are 500 million

My note was prompted by a desire to make sure the adoption issues were
considered explicitly.  It is always tempting to see an existing
solution and simply direct everyone to use it.

We should pay close attention to the types of changes that will be
needed for adoption. As you note, the difference between "useful for
the first two adopters" versus "not useful until almost everyone
adopts" is an example of an essential point of analysis.

Similarly, it's useful to ask what parts of an implementation must
change, in order to adopt the solution. Is it ok to have to change all
applications? Is it ok to have to change the networking
infrastructure? And so on.

And then, lastly, we need to look at the particular choice being
offered. I don't have an opinion about whether SCTP should be the TCP
replacement -- and I guess the UDP replacement -- but that seemed to
be the suggestion.

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>






From owner-ietf@ietf.org  Mon Feb  2 05:52:13 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03197
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Feb 2004 05:52:13 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnbVS-0007xh-V4
	for ietf-list@asgard.ietf.org; Mon, 02 Feb 2004 05:40:42 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnbVH-0007wP-Jp
	for ietf@asgard.ietf.org; Mon, 02 Feb 2004 05:40:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02170
	for <ietf@ietf.org>; Mon, 2 Feb 2004 05:40:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnbVF-00037w-00
	for ietf@ietf.org; Mon, 02 Feb 2004 05:40:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnbUK-00032z-00
	for ietf@ietf.org; Mon, 02 Feb 2004 05:39:32 -0500
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnbTr-0002xu-00
	for ietf@ietf.org; Mon, 02 Feb 2004 05:39:04 -0500
Received: from pigeon.ecs.soton.ac.uk (pigeon [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id i12Ad4Or026183
	for <ietf@ietf.org>; Mon, 2 Feb 2004 10:39:04 GMT
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id KAA25524
	for <ietf@ietf.org>; Mon, 2 Feb 2004 10:39:01 GMT
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i12Ad1F10113
	for ietf@ietf.org; Mon, 2 Feb 2004 10:39:01 GMT
Date: Mon, 2 Feb 2004 10:39:01 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Publicising IETF attendance lists
Message-ID: <20040202103901.GP7704@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Here's one interesting story on why it would be nice to be able to opt
out of having your name published as being away from home for a week:

http://www.vnunet.com/News/1137316

I think opt-out is the way to go.  If people are concerned about how
"open" the IETF is they are welcome to come along or join a list :)

Tim



From owner-ietf@ietf.org  Mon Feb  2 09:59:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16067
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Feb 2004 09:59:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnfNR-0005VK-33
	for ietf-list@asgard.ietf.org; Mon, 02 Feb 2004 09:48:41 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnfNN-0005Tq-J6
	for ietf@asgard.ietf.org; Mon, 02 Feb 2004 09:48:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15540
	for <ietf@ietf.org>; Mon, 2 Feb 2004 09:48:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnfNM-0000UH-00
	for ietf@ietf.org; Mon, 02 Feb 2004 09:48:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnfMS-0000PN-00
	for ietf@ietf.org; Mon, 02 Feb 2004 09:47:40 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnfM8-0000KS-00
	for ietf@ietf.org; Mon, 02 Feb 2004 09:47:20 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AnfM0-000DJj-00; Mon, 02 Feb 2004 09:47:12 -0500
Date: Mon, 02 Feb 2004 09:47:12 -0500
From: John C Klensin <john-ietf@jck.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: Publicising IETF attendance lists
Message-ID: <172336376.1075715232@scan.jck.com>
In-Reply-To: <20040202103901.GP7704@login.ecs.soton.ac.uk>
References: <20040202103901.GP7704@login.ecs.soton.ac.uk>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Monday, 02 February, 2004 10:39 +0000 Tim Chown 
<tjc@ecs.soton.ac.uk> wrote:

> Here's one interesting story on why it would be nice to be
> able to opt out of having your name published as being away
> from home for a week:
>
> http://www.vnunet.com/News/1137316

But that article is about "vacation" messages, not about lists 
of prospective attendees at meetings.  Since some people who 
register don't show up, using the meeting list could be a poor 
bet for burglars.  But...

> I think opt-out is the way to go.  If people are concerned
> about how "open" the IETF is they are welcome to come along or
> join a list :)

Were opt-out to be permitted on this basis, it would still be 
reasonable for IETF to publish the list of people who actually 
attended, perhaps with the minutes or even the day after the 
meeting closed.  It seems to me that --unless one develops 
theories about would-be burglars engaging in a good deal of data 
mining (in which case, suppressing registration lists won't help 
much) -- there is almost no argument for suppressing the list of 
people who attended a standards meeting, and many reasons for 
not doing so.

    john




From owner-ietf@ietf.org  Mon Feb  2 20:22:07 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28933
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Feb 2004 20:22:07 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Anp7O-0001mu-6C
	for ietf-list@asgard.ietf.org; Mon, 02 Feb 2004 20:12:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Anp20-0001Tb-Ci
	for ietf@asgard.ietf.org; Mon, 02 Feb 2004 20:07:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28405
	for <ietf@ietf.org>; Mon, 2 Feb 2004 20:07:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Anp1y-00024e-00
	for ietf@ietf.org; Mon, 02 Feb 2004 20:07:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Anp10-0001ys-00
	for ietf@ietf.org; Mon, 02 Feb 2004 20:06:11 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Anp0U-0001q9-00
	for ietf@ietf.org; Mon, 02 Feb 2004 20:05:38 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1314v2O014289
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 2 Feb 2004 20:04:59 -0500
Date: Mon, 2 Feb 2004 20:04:57 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Tim Chown <tjc@ecs.soton.ac.uk>
cc: ietf@ietf.org
Subject: Re: Publicising IETF attendance lists
In-Reply-To: <20040202103901.GP7704@login.ecs.soton.ac.uk>
Message-ID: <Pine.LNX.4.44.0402021957010.13441-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

The attendee lists aren't usually published by most organizations until
during or after the event. I would agree that pre-event publication is not
a good idea.  But, of course, speakers and well-known attendees still
can't control that information and how unscrupulous people might use it.  
Your best bet is an alarm system on your home.

But transparancy is important. The list has to be made available.

		--Dean

On Mon, 2 Feb 2004, Tim Chown wrote:

> Here's one interesting story on why it would be nice to be able to opt
> out of having your name published as being away from home for a week:
> 
> http://www.vnunet.com/News/1137316
> 
> I think opt-out is the way to go.  If people are concerned about how
> "open" the IETF is they are welcome to come along or join a list :)
> 
> Tim
> 
> 




From owner-ietf@ietf.org  Mon Feb  2 20:22:07 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28938
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Feb 2004 20:22:07 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Anozh-0001Mp-BN
	for ietf-list@asgard.ietf.org; Mon, 02 Feb 2004 20:04:49 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnoiU-0000jv-7p
	for ietf@asgard.ietf.org; Mon, 02 Feb 2004 19:47:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27623
	for <ietf@ietf.org>; Mon, 2 Feb 2004 19:47:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnoiS-0007eP-00
	for ietf@ietf.org; Mon, 02 Feb 2004 19:47:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Anoha-0007Z7-00
	for ietf@ietf.org; Mon, 02 Feb 2004 19:46:07 -0500
Received: from razorbill.mail.pas.earthlink.net ([207.217.121.248])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Anogx-0007TJ-00
	for ietf@ietf.org; Mon, 02 Feb 2004 19:45:27 -0500
Received: from [38.119.96.105] (helo=[192.168.0.2])
	by razorbill.mail.pas.earthlink.net with asmtp (Exim 3.33 #1)
	id 1Anogs-0001nh-00
	for ietf@ietf.org; Mon, 02 Feb 2004 16:45:23 -0800
Date: Mon, 2 Feb 2004 19:38:19 -0500
From: Gene Gaines <gene.gaines@gainesgroup.com>
Organization: Gaines Group
X-Priority: 3 (Normal)
Message-ID: <14092012869.20040202193819@gainesgroup.com>
To: ietf@ietf.org
Subject: Re: Visa for Korea
In-Reply-To: <2226201457.20040129150137@gainesgroup.com>
References: <Pine.LNX.4.44.0401291058450.8971-100000@jackson.cs.ucsb.edu>
 <2226201457.20040129150137@gainesgroup.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: e892362a6fa8b5d372cc1e1b0924a179239a348a220c260903e5929b738a4115d15ae484ac4fdfe6350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


As promised, The Korean consulate in DC has a resolution
for the visa problem.

The Korean Consular General for the United States has
committed to preparing two letters for U.S. citizens to
carry with them.

The letters, one in English and one in Korean addressed to
border officials, states that U.S. citizens traveling to
Korea to attend the IETF meeting and/or tourism for up to
30 days DO NOT NEED A VISA.

The IETF secretariat expects to receive these letters by
Friday, Feb. 6 and will let you know when they are posted
as graphics on the www.ietf.org web site.  Print copies
and carry with you.

About customs and immigration.  "Less said, faster through."
Just show your passport and say you are attending a
technical meeting in Seoul by a nonprofit organization.
Should the official inquire about a visa, then show him
the letters.

TO BE CLEAR:  This applies only for U.S. citizens with a
current passport traveling to Korea to attend the IETF
meeting -- a technical conference by a nonprofit group.
If you are traveling to Korea to attend additional
business meetings then technically you require a visa, as
does a government employee acting in an official capacity.

Gene Gaines
gene.gaines@gainesgroup.com
Sterling, Virginia


My previous email:
On Thursday, January 29, 2004, 3:24:01 PM, Gene wrote:

> An official letter is coming from the responsible
> Korean government official in Washington DC.

> I wrote the text for him, so unless he gets it
> messed up, will be very clear that U.S. citizens do
> not need a visa for IETF meeting in Korea.

> The Korean sponsor also is attempting to get such
> a letter in Seoul.

> I expect we will have and Foretec can post on the
> IETF meeting web site by next Monday -- so I
> hope this can put the issue to sleep for a few
> days.

> If you disagree, please let me know.

> Otherwise, in the issue of visas for the moment
> silence will be golden.

> Gene Gaines
> gene.gaines@gainesgroup.com
> Sterling, Virginia


-- As promised.

The Korean consulate in DC has a resolution for the visa problem.

Was not easy, as the language we are using is confusing
to the Koreans.  (Somehow, the word "engineering" gets
translated as applied engineering and therefore assumed to
be business, etc., but this is off subject.)

I spoke Monday afternoon with the Korean Consular General
for the United States -- Mr. Byung Kil Han.  He does
understand the situation, wants his country to be a good
host, and fully agrees that U.S. citizens visiting Korea
do not need a visa to attend the IETF meeting and/or
tourism for up to 30 days.

He has instructed the First Secretary, Mr. Won Sup Park,
to prepare and fax to me two letters: (1) to those
traveling stating that a visa not required, and (2)
a letter in Korean to Korean border officials ordering
them to admit the traveler without a visa.

Those two letters will be faxed to me, I will create as
a basic TIF and GIF format files and send on to Foretec
to post at www.ietf.org/meetings/IETF-59.html.

I spoke with Park several times today, and am coordinating
with Marsha and Dawn Thomas at the IETF Secretariat

These letters must be written and vetted carefully, so I
expect them by Thursday or Friday.  I don't want to rush
Park and cause more confusion.

TO BE CLEAR:  This applies only for U.S. citizens with a
current passport.  They are traveling to Korea to attend
a technical conference by a nonprofit group. If they also
will go on to attend business meetings then technically
they require a visa, as does a government employee acts
in an official capacity in Korea.

I hope this is constructive.  Want to change something,
let me know.  If I'm interfering, tell me and I'll be gone.

I will post a quick note to the ietf@ietf.org list.

Gene Gaines
gene.gaines@gainesgroup.com
Sterling, Virginia


My previous email:
On Thursday, January 29, 2004, 3:24:01 PM, Gene wrote:

> An official letter is coming from the responsible
> Korean government official in Washington DC.

> I wrote the text for him, so unless he gets it
> messed up, will be very clear that U.S. citizens do
> not need a visa for IETF meeting in Korea.

> The Korean sponsor also is attempting to get such
> a letter in Seoul.

> I expect we will have and Foretec can post on the
> IETF meeting web site by next Monday -- so I
> hope this can put the issue to sleep for a few
> days.

> If you disagree, please let me know.

> Otherwise, in the issue of visas for the moment
> silence will be golden.

> Gene Gaines
> gene.gaines@gainesgroup.com
> Sterling, Virginia


-- 





On Thursday, January 29, 2004, 3:01:37 PM, Gene wrote:

> An attempt to attenuate the visa discussion.

> The Korean Consulate in Washington DC is preparing an official
> letter intended to clearly state that U.S. citizens do not need
> a visa to attend the IETF meeting in Seoul.

> I will forward a graphic of the letter to the IETF Directorate,
> who has agreed to post on the web.

> Suggest giving the visa for U.S. citizens issue a rest for
> four days, time to get the official letter.

> Note.  I can think of no reason to have a letter of invitation
> unless you need a visa.

> Gene Gaines
> gene.gaines@gainesgroup.com
> Sterling, Virginia

-- 






From owner-ietf@ietf.org  Tue Feb  3 03:04:10 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26581
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Feb 2004 03:04:10 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AnvGU-0001PD-Hr
	for ietf-list@asgard.ietf.org; Tue, 03 Feb 2004 02:46:34 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AnvG7-0001Ld-5g
	for ietf@asgard.ietf.org; Tue, 03 Feb 2004 02:46:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26162
	for <ietf@ietf.org>; Tue, 3 Feb 2004 02:46:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnvG4-0004Hh-00
	for ietf@ietf.org; Tue, 03 Feb 2004 02:46:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnvF8-0004CZ-00
	for ietf@ietf.org; Tue, 03 Feb 2004 02:45:11 -0500
Received: from ginger.cmf.nrl.navy.mil ([134.207.10.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnvEJ-00047x-00
	for ietf@ietf.org; Tue, 03 Feb 2004 02:44:19 -0500
Received: from cmf.nrl.navy.mil (fermi.cmf.nrl.navy.mil [134.207.10.73])
	(authenticated bits=0)
	by ginger.cmf.nrl.navy.mil (8.12.7/8.12.7) with ESMTP id i137i7Rr020500;
	Tue, 3 Feb 2004 02:44:08 -0500 (EST)
Message-Id: <200402030744.i137i7Rr020500@ginger.cmf.nrl.navy.mil>
To: Gene Gaines <gene.gaines@gainesgroup.com>
cc: ietf@ietf.org
Subject: Re: Visa for Korea 
In-reply-to: Your message of "Mon, 02 Feb 2004 19:38:19 EST."
             <14092012869.20040202193819@gainesgroup.com> 
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4
	WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d
	gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;Mv(aiO2z~9n.w?@\>kEpSD@*e`
Date: Tue, 03 Feb 2004 02:44:07 -0500
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
X-Spam-Score: () hits=0 User Authenticated
X-Virus-Scanned: NAI Completed
X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>As promised, The Korean consulate in DC has a resolution
>for the visa problem.
>
>The Korean Consular General for the United States has
>committed to preparing two letters for U.S. citizens to
>carry with them.
>[...]

Gene,

I would just like to say, thank you for all your hard work in getting
these letters.  I have no doubt they will clear up any visa-related
issues that I will encounter during my trip.

--Ken



From owner-ietf@ietf.org  Tue Feb  3 05:41:30 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01411
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Feb 2004 05:41:30 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Anxr6-0001ok-L9
	for ietf-list@asgard.ietf.org; Tue, 03 Feb 2004 05:32:32 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Anxqr-0001mX-BN
	for ietf@asgard.ietf.org; Tue, 03 Feb 2004 05:32:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00913
	for <ietf@ietf.org>; Tue, 3 Feb 2004 05:32:15 -0500 (EST)
From: Gordon.Lennox@cec.eu.int
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Anxqo-0004Hn-00
	for ietf@ietf.org; Tue, 03 Feb 2004 05:32:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Anxpu-0004CU-00
	for ietf@ietf.org; Tue, 03 Feb 2004 05:31:19 -0500
Received: from ex3lujmoims01.cec.eu.int ([158.169.9.54])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnxpU-00047Q-00
	for ietf@ietf.org; Tue, 03 Feb 2004 05:30:52 -0500
Received: by ex3lujmoims01 with Internet Mail Service (5.5.2657.72)
	id <11MQJPDB>; Tue, 3 Feb 2004 11:30:23 +0100
Message-ID: <8723A4EA11C8D7119DC80003470D2049018068D8@ex2beimcombx08>
To: ietf@ietf.org
Subject: Seoul - not about visas!
Date: Tue, 3 Feb 2004 11:30:17 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


I have just received the following advice from our services here:

"The Medical Service informs that following the spread of avian influenza
(bird flu) in South East Asia, as a precautionary measure it is advisable,
for all those who are going on mission to this area, to be vaccinated
against influenza.

Although, this vaccination does not protect you from bird flu (H5N1) it
offers a degree of immunity.

It goes without saying that one should pay scrupulous attention to personal
hygiene and the consumption of food and that all contact with poultry (in
markets, farms, slaughter houses ...) is to be avoided at all costs.

..."

A country-by-country overview of the situation can be found on the BBC's
web-site:

http://news.bbc.co.uk/2/hi/asia-pacific/3429851.stm

----

I am very much looking forward to my first visit to Seoul!

It is my next visit to the US that has me more concerned. That security guy
with the bright blue latex gloves at JFK last time... And I am always, but
always, pulled out for the special treatment! Ouch!<vbg>

/Gordon



From owner-ietf@ietf.org  Tue Feb  3 17:23:05 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08900
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Feb 2004 17:23:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ao8en-0006Az-J4
	for ietf-list@asgard.ietf.org; Tue, 03 Feb 2004 17:04:33 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ao8dS-00066l-8M
	for ietf@asgard.ietf.org; Tue, 03 Feb 2004 17:03:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07961
	for <ietf@ietf.org>; Tue, 3 Feb 2004 17:03:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ao8dQ-0005ez-00
	for ietf@ietf.org; Tue, 03 Feb 2004 17:03:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ao8ck-0005W8-00
	for ietf@ietf.org; Tue, 03 Feb 2004 17:02:27 -0500
Received: from zak.ecotroph.net ([216.93.164.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ao8br-0005Lg-00
	for ietf@ietf.org; Tue, 03 Feb 2004 17:01:31 -0500
Received: from thinkingcat.com ([::ffff:68.71.234.169])
  (AUTH: LOGIN leslie, TLS: TLSv1/SSLv3,256bits,AES256-SHA)
  by zak.ecotroph.net with esmtp; Tue, 03 Feb 2004 17:01:27 -0500
Message-ID: <402019E1.4060909@thinkingcat.com>
Date: Tue, 03 Feb 2004 17:00:01 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
CC: ietf@ietf.org
Subject: Re: The IETF Mission
References: <405441934.1074293627@localhost> <Pine.LNX.4.44.0401171150270.11109-100000@netcore.fi> <6.0.1.1.2.20040117103457.0466fc00@mira-sjc5-b.cisco.com> <401946E8.9030207@thinkingcat.com> <6.0.1.1.2.20040129213127.047b0a08@mira-sjc5-b.cisco.com>
In-Reply-To: <6.0.1.1.2.20040129213127.047b0a08@mira-sjc5-b.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I think it's on track, as a description of the "common interest"
(a phrase someone used earlier).

I'm still itching for something that acts as a delimeter -- how
do we know whether we, collectively, should be working on X or
ignoring Y?  How can we know when we are "succeeding" at our
mission?

Harald outlined some possibilities in terms of the
scope of the work, and people didn't seem to resonate with that
approach.

Is our mission to collectively work on some selection of things
of common interest?  Do we have common view on means of determining
relevance in "relevant services in transit and edge networks"?
Are we obligated, by this statement of interest, to work on anything
someone (or a large enough collection of "someones") considers
relevant at a given point in time?

Someone earlier raised the point that the description of the space
in which we work (the IETF's scope) may not be the description of
the work that we collectively take on -- I guess I'm wondering whether
we can characterize the subset in some constructive way, so that
it will be clearer to us, and to communities trying to work with
us, what we should/will put energy into at a given point in time.

Leslie.


Fred Baker wrote:
> Let me try to say all that succinctly:
> 
>    "The Internet Engineering Task Force provides a forum for the
>    discussion and development of white papers and specifications for
>    the engineering issues of the Internet. This discussion builds on
>    hard lessons learned in research and operational environments, and
>    necessarily includes speakers from those communities. Vendors offer
>    wisdom on what can be built and made to work in their products, and
>    may bring customer or market issues whose owners cannot or will not
>    bring themselves.
> 
>    The intended goal is well characterized as 'community memory' -
>    written observations and wisdom as well as protocols and operational
>    procedures defined - to enable the datagram internet to scalably
>    deliver relevant services in transit and edge networks."
> 
> Is that on target? Is it too many words?




From owner-ietf@ietf.org  Wed Feb  4 16:01:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26676
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Feb 2004 16:01:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AoTzT-0005Wk-Hi
	for ietf-list@asgard.ietf.org; Wed, 04 Feb 2004 15:51:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AoTpt-0005Ds-CB
	for ietf@asgard.ietf.org; Wed, 04 Feb 2004 15:41:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25376
	for <ietf@ietf.org>; Wed, 4 Feb 2004 15:41:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoTpr-0001UY-00
	for ietf@ietf.org; Wed, 04 Feb 2004 15:41:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AoTow-0001Og-00
	for ietf@ietf.org; Wed, 04 Feb 2004 15:40:26 -0500
Received: from noxmail.sandelman.ottawa.on.ca ([205.150.200.166])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoTo5-0001IF-00; Wed, 04 Feb 2004 15:39:33 -0500
Received: from lox.sandelman.ottawa.on.ca (IDENT:root@lox.sandelman.ottawa.on.ca [205.150.200.178])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id i14KdUO21902
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK);
	Wed, 4 Feb 2004 15:39:32 -0500 (EST)
Received: from sandelman.ottawa.on.ca (desk.marajade.sandelman.ca [205.150.200.247])
	by lox.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id i14KhkI25878
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK);
	Wed, 4 Feb 2004 15:43:52 -0500 (EST)
Received: from marajade.sandelman.ottawa.on.ca (mcr@marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id i14KdDUE013349
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 4 Feb 2004 15:39:13 -0500
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by marajade.sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id i14KdDWR013345;
	Wed, 4 Feb 2004 15:39:13 -0500
To: ietf@ietf.org
cc: webmaster@ietf.org
Subject: previous IETF scheduled
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 04 Feb 2004 15:39:13 -0500
Message-ID: <13344.1075927153@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


Again, can I ask that the previous IETF meetings pages, 
  (e.g:	   http://www.ietf.org/meetings/IETF-58.html )

be left online? In particular, it is very useful to be able to
refer back to them, and to pull up schedules, and *** BOF AGENDAS ***
easily?

Yes, it is on the FTP site, but the web interface is much easier to
navigate.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [



From owner-ietf@ietf.org  Wed Feb  4 16:44:36 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01773
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Feb 2004 16:44:36 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AoUkA-0001dE-Ub
	for ietf-list@asgard.ietf.org; Wed, 04 Feb 2004 16:39:34 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AoTzh-0005aO-VN
	for ietf@asgard.ietf.org; Wed, 04 Feb 2004 15:51:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26216
	for <ietf@ietf.org>; Wed, 4 Feb 2004 15:51:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoTzg-0002Wi-00
	for ietf@ietf.org; Wed, 04 Feb 2004 15:51:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AoTym-0002R5-00
	for ietf@ietf.org; Wed, 04 Feb 2004 15:50:37 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoTyQ-0002L0-00
	for ietf@ietf.org; Wed, 04 Feb 2004 15:50:14 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i14KnVb1005802
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 4 Feb 2004 15:49:31 -0500
Date: Wed, 4 Feb 2004 15:49:31 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Leslie Daigle <leslie@thinkingcat.com>
cc: Fred Baker <fred@cisco.com>, <ietf@ietf.org>
Subject: Re: The IETF Mission
In-Reply-To: <402019E1.4060909@thinkingcat.com>
Message-ID: <Pine.LNX.4.44.0402041547540.4138-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I propose the following as a mission statement for the IETF:

IETF is a technical protocol standards organization.  Its principal goals 
are:

        To create open, technical standards that will be useful to and 
adopted by the world internet communtity and the public at large.

        To identify current and emerging protocol requirements, and share 
best practices.

        To facliitate the participation of all affected and interested
parties and develop consensus.

        To solicit the input of a diverse group of interests and 
participants in the formation of protocol standards.

        To provide a fair and open process whereby any party that believes 
it has been treated unfairly has the right to appeal.

        To work with suppliers, consortia, and other standards bodies to 
develop consensus and facilitate interoperability.
   









From owner-ietf@ietf.org  Wed Feb  4 16:44:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01792
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Feb 2004 16:44:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AoUkA-0001d0-Et
	for ietf-list@asgard.ietf.org; Wed, 04 Feb 2004 16:39:34 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AoTzg-0005aM-PV
	for ietf@asgard.ietf.org; Wed, 04 Feb 2004 15:51:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26209
	for <ietf@ietf.org>; Wed, 4 Feb 2004 15:51:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoTzf-0002WY-00
	for ietf@ietf.org; Wed, 04 Feb 2004 15:51:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AoTyl-0002Qp-00
	for ietf@ietf.org; Wed, 04 Feb 2004 15:50:36 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoTyA-0002Kc-00
	for ietf@ietf.org; Wed, 04 Feb 2004 15:49:58 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i14KnJoF005799
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 4 Feb 2004 15:49:19 -0500
Date: Wed, 4 Feb 2004 15:49:19 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Leslie Daigle <leslie@thinkingcat.com>
cc: Fred Baker <fred@cisco.com>, <ietf@ietf.org>
Subject: Re: The IETF Mission
In-Reply-To: <402019E1.4060909@thinkingcat.com>
Message-ID: <Pine.LNX.4.44.0402041516480.4138-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> Fred Baker wrote:
> > Let me try to say all that succinctly:
> > 
> >    "The Internet Engineering Task Force provides a forum for the
> >    discussion and development of white papers and specifications for
> >    the engineering issues of the Internet. This discussion builds on
> >    hard lessons learned in research and operational environments, and
> >    necessarily includes speakers from those communities. Vendors offer
> >    wisdom on what can be built and made to work in their products, and
> >    may bring customer or market issues whose owners cannot or will not
> >    bring themselves.

This misses a great deal.  I think one needs to consider the Mission of
other standards organizations such as IEEE, ANSI, the ITU, and The Open
Group, to name a few examples:

The mission of The Open Group is to drive the creation of Boundaryless 
Information Flow achieved by:

    * Working with customers to capture, understand and address current 
and emerging requirements, establish policies, and share best practices;
    * Working with suppliers, consortia and standards bodies to develop 
consensus and facilitate interoperability, to evolve and integrate 
specifications and open source technologies;
    * Offering a comprehensive set of services to enhance the operational 
efficiency of consortia; and
    * Developing and operating the industry's premier certification 
service and encouraging procurement of certified products.


IEEE Vision and Mission

VISION

To advance global prosperity by fostering technological innovation, 
enabling members' careers and promoting community world-wide.


MISSION

The IEEE promotes the engineering process of creating, developing, 
integrating, sharing, and applying knowledge about electro and information 
technologies and sciences for the benefit of humanity and the profession.


ANSI MISSION

To enhance both the global competitiveness of U.S. business and the U.S. 
quality of life by promoting and facilitating voluntary consensus 
standards and conformity assessment systems, and safeguarding their 
integrity

Cardinal Principals

Openness. Any materially affected and interested party has the ability to 
participate.

Balance. The standards development process should have a balance of 
interests and participants from diverse interest categories shall be 
sought.

Due Process. All objections shall have an attempt made towards their 
resolution. Interests who believe they have been treated unfairly shall 
have a right to appeal.

Consensus. More than a majority, but not necessarily unanimity.

> >    The intended goal is well characterized as 'community memory' -
> >    written observations and wisdom as well as protocols and operational
> >    procedures defined - to enable the datagram internet to scalably
> >    deliver relevant services in transit and edge networks."

I don't think it has anything to do with "community memory", nor is it 
limited to the 'datagram internet', nor is it even limited to services in 
'transit and edge netorks'. Quite obviously, it is useful to peering and 
private and other kinds of networks, but the types of networks aren't 
important. What is important is that the stardards are techincally useful, 
and publicly deliberated.






From owner-ietf@ietf.org  Wed Feb  4 17:09:59 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03627
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Feb 2004 17:09:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AoV7C-0005uU-8K
	for ietf-list@asgard.ietf.org; Wed, 04 Feb 2004 17:03:22 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AoV6m-0005sG-GQ
	for ietf@asgard.ietf.org; Wed, 04 Feb 2004 17:02:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03166
	for <ietf@ietf.org>; Wed, 4 Feb 2004 17:02:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoV6l-0005vE-00
	for ietf@ietf.org; Wed, 04 Feb 2004 17:02:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AoV5Q-0005jr-00
	for ietf@ietf.org; Wed, 04 Feb 2004 17:01:32 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AoV4G-0005Qv-00
	for ietf@ietf.org; Wed, 04 Feb 2004 17:00:21 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 4C87961AA5; Wed,  4 Feb 2004 22:59:49 +0100 (CET)
Date: Wed, 04 Feb 2004 13:59:43 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>, Leslie Daigle <leslie@thinkingcat.com>
Cc: Fred Baker <fred@cisco.com>, ietf@ietf.org
Subject: Re: The IETF Mission
Message-ID: <2014986277.1075903183@[192.168.1.52]>
In-Reply-To: <Pine.LNX.4.44.0402041516480.4138-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0402041516480.4138-100000@cirrus.av8.net>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========4AEB16572321B7BEB501=========="
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

--==========4AEB16572321B7BEB501==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Thanks Dean - this collection was actually quite informative!

             Harald

--On 4. februar 2004 15:49 -0500 Dean Anderson <dean@av8.com> wrote:

> Openness. Any materially affected and interested party has the ability to
> participate.
>
> Balance. The standards development process should have a balance of
> interests and participants from diverse interest categories shall be
> sought.
>
> Due Process. All objections shall have an attempt made towards their
> resolution. Interests who believe they have been treated unfairly shall
> have a right to appeal.




--==========4AEB16572321B7BEB501==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)

iD8DBQFAIWtTOMj+2+WY0F4RAm1cAKC1/FDlG0LWFot+48+FIEklV6gRkwCgqLiN
JNpcD7wvlciQk3LiuuVRYeA=
=nx3j
-----END PGP SIGNATURE-----

--==========4AEB16572321B7BEB501==========--




From owner-ietf@ietf.org  Thu Feb  5 00:15:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18740
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Feb 2004 00:15:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aobec-000052-Ev
	for ietf-list@asgard.ietf.org; Thu, 05 Feb 2004 00:02:18 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aobe0-0008TA-LY
	for ietf@asgard.ietf.org; Thu, 05 Feb 2004 00:01:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18497
	for <ietf@ietf.org>; Thu, 5 Feb 2004 00:01:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aobdy-0007iA-00
	for ietf@ietf.org; Thu, 05 Feb 2004 00:01:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aobd3-0007du-00
	for ietf@ietf.org; Thu, 05 Feb 2004 00:00:41 -0500
Received: from wetware.wetware.com ([199.108.16.1] helo=wetware.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aobcl-0007ZC-00
	for ietf@ietf.org; Thu, 05 Feb 2004 00:00:23 -0500
Received: from [208.177.152.18] (helo=[10.0.1.7])
	by wetware.com with esmtp (Exim 4.20)
	id 1AobcE-0007UL-Om; Wed, 04 Feb 2004 20:59:50 -0800
In-Reply-To: <Pine.LNX.4.44.0402041547540.4138-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0402041547540.4138-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed
Message-Id: <1D7A0C75-5798-11D8-ABD9-000393B8133A@wetware.com>
Content-Transfer-Encoding: quoted-printable
Cc: Fred Baker <fred@cisco.com>, Leslie Daigle <leslie@thinkingcat.com>,
        <ietf@ietf.org>
From: james woodyatt <jhw@wetware.com>
Subject: Re: The IETF Mission
Date: Wed, 4 Feb 2004 20:59:44 -0800
To: Dean Anderson <dean@av8.com>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

On 04 Feb 2004, at 12:49, Dean Anderson wrote:
>
>         To provide a fair and open process whereby any party that=20
> believes
> it has been treated unfairly has the right to appeal.

I'd prefer this:

	To use a fair and open process, even in the resolution of =
disputes,
	in which any person with a claim of unfair treatment has an =
avenue
	for appeal.

I don't much like the idea of artificial legal entities, i.e. political=20=

parties, having "rights".  It's a minor nit, I know=97 call me a radical=20=

hippie, if you must.


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




From owner-ietf@ietf.org  Thu Feb  5 00:46:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19897
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Feb 2004 00:46:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AocHK-0002hd-Ax
	for ietf-list@asgard.ietf.org; Thu, 05 Feb 2004 00:42:18 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AocDu-0002Vw-7T
	for ietf@asgard.ietf.org; Thu, 05 Feb 2004 00:38:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19718
	for <ietf@ietf.org>; Thu, 5 Feb 2004 00:38:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AocDs-00034o-00
	for ietf@ietf.org; Thu, 05 Feb 2004 00:38:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AocCv-0002zs-00
	for ietf@ietf.org; Thu, 05 Feb 2004 00:37:46 -0500
Received: from wetware.wetware.com ([199.108.16.1] helo=wetware.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AocCS-0002uV-00
	for ietf@ietf.org; Thu, 05 Feb 2004 00:37:16 -0500
Received: from [208.177.152.18] (helo=[10.0.1.7])
	by wetware.com with esmtp (Exim 4.20)
	id 1AocBj-00008c-7W; Wed, 04 Feb 2004 21:36:31 -0800
In-Reply-To: <1D7A0C75-5798-11D8-ABD9-000393B8133A@wetware.com>
References: <Pine.LNX.4.44.0402041547540.4138-100000@cirrus.av8.net> <1D7A0C75-5798-11D8-ABD9-000393B8133A@wetware.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <3D2A9508-579D-11D8-ABD9-000393B8133A@wetware.com>
Content-Transfer-Encoding: 7bit
Cc: Fred Baker <fred@cisco.com>, Dean Anderson <dean@av8.com>,
        Leslie Daigle <leslie@thinkingcat.com>, <ietf@ietf.org>
From: james woodyatt <jhw@wetware.com>
Subject: Re: The IETF Mission
Date: Wed, 4 Feb 2004 21:36:25 -0800
To: james woodyatt <jhw@wetware.com>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 04 Feb 2004, at 20:59, james woodyatt wrote:
> On 04 Feb 2004, at 12:49, Dean Anderson wrote:
>>
>>         To provide a fair and open process whereby any party that 
>> believes
>> it has been treated unfairly has the right to appeal.
>
> I'd prefer this:
>
> 	To use a fair and open process, even in the resolution of disputes,
> 	in which any person with a claim of unfair treatment has an avenue
> 	for appeal.

Drat.  Scratch out the characters ", even" in the above.  That was bad 
logic on my part.  Apologies all around.  I'll shut up now.


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




From owner-ietf@ietf.org  Thu Feb  5 14:10:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29447
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Feb 2004 14:10:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AooZs-0002Bx-BV
	for ietf-list@asgard.ietf.org; Thu, 05 Feb 2004 13:50:16 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AooYu-000296-SF
	for ietf@asgard.ietf.org; Thu, 05 Feb 2004 13:49:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28400
	for <ietf@ietf.org>; Thu, 5 Feb 2004 13:49:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AooYt-0000Eo-00
	for ietf@ietf.org; Thu, 05 Feb 2004 13:49:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AooXw-00008I-00
	for ietf@ietf.org; Thu, 05 Feb 2004 13:48:17 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AooXT-00000u-00
	for ietf@ietf.org; Thu, 05 Feb 2004 13:47:47 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i15IlBI6030930
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 5 Feb 2004 13:47:11 -0500
Date: Thu, 5 Feb 2004 13:47:10 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: james woodyatt <jhw@wetware.com>
cc: Fred Baker <fred@cisco.com>, Leslie Daigle <leslie@thinkingcat.com>,
        <ietf@ietf.org>
Subject: Re: The IETF Mission
In-Reply-To: <1D7A0C75-5798-11D8-ABD9-000393B8133A@wetware.com>
Message-ID: <Pine.LNX.4.44.0402051346330.30073-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by cirrus.av8.net id i15IlBI6030930
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

How about this:

 To provide a fair and open process whereby any party that
 believes it has been treated unfairly has the opportunity to appeal.


On Wed, 4 Feb 2004, james woodyatt wrote:

> On 04 Feb 2004, at 12:49, Dean Anderson wrote:
> >
> >         To provide a fair and open process whereby any party that=20
> > believes
> > it has been treated unfairly has the right to appeal.
>=20
> I'd prefer this:
>=20
> 	To use a fair and open process, even in the resolution of disputes,
> 	in which any person with a claim of unfair treatment has an avenue
> 	for appeal.
>=20
> I don't much like the idea of artificial legal entities, i.e. political=
=20
> parties, having "rights".  It's a minor nit, I know=97 call me a radica=
l=20
> hippie, if you must.
>=20
>=20
>=20




From owner-ietf@ietf.org  Thu Feb  5 14:27:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00392
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Feb 2004 14:27:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aop5s-00045i-8T
	for ietf-list@asgard.ietf.org; Thu, 05 Feb 2004 14:23:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aop51-00042p-OH
	for ietf@asgard.ietf.org; Thu, 05 Feb 2004 14:22:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00124
	for <ietf@ietf.org>; Thu, 5 Feb 2004 14:22:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aop50-0003fU-00
	for ietf@ietf.org; Thu, 05 Feb 2004 14:22:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aop48-0003Xh-00
	for ietf@ietf.org; Thu, 05 Feb 2004 14:21:32 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aop2x-0003Ob-00
	for ietf@ietf.org; Thu, 05 Feb 2004 14:20:19 -0500
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i15JK7E12919;
	Thu, 5 Feb 2004 11:20:07 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200402051920.i15JK7E12919@boreas.isi.edu>
Subject: Re: The IETF Mission
In-Reply-To: <Pine.LNX.4.44.0402051346330.30073-100000@cirrus.av8.net> from Dean Anderson at "Feb 5, 4 01:47:10 pm"
To: dean@av8.com (Dean Anderson)
Date: Thu, 5 Feb 2004 11:20:07 -0800 (PST)
Cc: jhw@wetware.com, fred@cisco.com, leslie@thinkingcat.com, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

% How about this:
% 
%  To provide a fair and open process whereby any party that
%  believes it has been treated unfairly has the opportunity to appeal.


	...over and over and over and over and over and over and over....

	Methinks this needs a bounds check.

--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  Thu Feb  5 15:09:36 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02575
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Feb 2004 15:09:36 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aopee-0006CI-9Y
	for ietf-list@asgard.ietf.org; Thu, 05 Feb 2004 14:59:16 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aopeb-00069I-Tz
	for ietf@asgard.ietf.org; Thu, 05 Feb 2004 14:59:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01664
	for <ietf@ietf.org>; Thu, 5 Feb 2004 14:59:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AopeY-0007Nr-00
	for ietf@ietf.org; Thu, 05 Feb 2004 14:59:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AopdZ-0007HK-00
	for ietf@ietf.org; Thu, 05 Feb 2004 14:58:09 -0500
Received: from ns.execdsl.net ([208.184.15.238] helo=EXECDSL.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aopce-00076m-00
	for ietf@ietf.org; Thu, 05 Feb 2004 14:57:12 -0500
Received: from [64.254.114.114] (HELO JLaptop.stevecrocker.com)
  by EXECDSL.COM (CommuniGate Pro SMTP 3.3)
  with ESMTP id 6168159; Thu, 05 Feb 2004 14:57:00 -0500
Message-Id: <5.1.0.14.0.20040205145557.01ad2a30@localhost>
X-Sender: joel@stevecrocker.com@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 05 Feb 2004 14:56:56 -0500
To: Dean Anderson <dean@av8.com>, james woodyatt <jhw@wetware.com>
From: "Joel M. Halpern" <joel@stevecrocker.com>
Subject: Re: The IETF Mission
Cc: Fred Baker <fred@cisco.com>, Leslie Daigle <leslie@thinkingcat.com>,
        <ietf@ietf.org>
In-Reply-To: <Pine.LNX.4.44.0402051346330.30073-100000@cirrus.av8.net>
References: <1D7A0C75-5798-11D8-ABD9-000393B8133A@wetware.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

I do not think "appeals" belongs in our mission and vision statement.  They=
=20
are a mechanism to achieve openness and accountability, not the purpose of=
=20
the organzation.

Yours,
Joel M. Halpern

At 01:47 PM 2/5/2004 -0500, Dean Anderson wrote:
>How about this:
>
>  To provide a fair and open process whereby any party that
>  believes it has been treated unfairly has the opportunity to appeal.
>
>
>On Wed, 4 Feb 2004, james woodyatt wrote:
>
> > On 04 Feb 2004, at 12:49, Dean Anderson wrote:
> > >
> > >         To provide a fair and open process whereby any party that
> > > believes
> > > it has been treated unfairly has the right to appeal.
> >
> > I'd prefer this:
> >
> >       To use a fair and open process, even in the resolution of=
 disputes,
> >       in which any person with a claim of unfair treatment has an avenue
> >       for appeal.
> >
> > I don't much like the idea of artificial legal entities, i.e. political
> > parties, having "rights".  It's a minor nit, I know=97 call me a radical
> > hippie, if you must.
> >
> >
> >




From owner-ietf@ietf.org  Thu Feb  5 17:15:02 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15801
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Feb 2004 17:15:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aorg3-0004lQ-FR
	for ietf-list@asgard.ietf.org; Thu, 05 Feb 2004 17:08:51 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aordd-0004aD-IC
	for ietf@asgard.ietf.org; Thu, 05 Feb 2004 17:06:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15433
	for <ietf@ietf.org>; Thu, 5 Feb 2004 17:06:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aordc-0001Ty-00
	for ietf@ietf.org; Thu, 05 Feb 2004 17:06:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aorcn-0001QX-00
	for ietf@ietf.org; Thu, 05 Feb 2004 17:05:29 -0500
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aorbj-0001AO-00
	for ietf@ietf.org; Thu, 05 Feb 2004 17:04:23 -0500
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id JAA1021807;
	Fri, 6 Feb 2004 09:03:49 +1100 (EST)
Message-ID: <4022BDC5.F7A0C570@swin.edu.au>
Date: Fri, 06 Feb 2004 09:03:49 +1100
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 <ietf@ietf.org>
Subject: Re: The IETF Mission
References: <1D7A0C75-5798-11D8-ABD9-000393B8133A@wetware.com> <5.1.0.14.0.20040205145557.01ad2a30@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


much as i hate "me too" messages, i think joel makes a good point.

cheers,
gja

"Joel M. Halpern" wrote:
> 
> I do not think "appeals" belongs in our mission and vision statement.  They
> are a mechanism to achieve openness and accountability, not the purpose of
> the organzation.
> 
> Yours,
> Joel M. Halpern

	[..]
-- 
Grenville Armitage
http://caia.swin.edu.au
I come from a LAN downunder.



From owner-ietf@ietf.org  Fri Feb  6 10:12:06 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29456
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Feb 2004 10:12:06 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ap7Po-0006Nq-7A
	for ietf-list@asgard.ietf.org; Fri, 06 Feb 2004 09:57:08 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ap7P9-0006LE-Du
	for ietf@asgard.ietf.org; Fri, 06 Feb 2004 09:56:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27328
	for <ietf@ietf.org>; Fri, 6 Feb 2004 09:56:24 -0500 (EST)
From: EdLevinson@ResultsLifeCoaching.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ap7P8-0001Z1-00
	for ietf@ietf.org; Fri, 06 Feb 2004 09:56:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ap7NZ-0001Gz-00
	for ietf@ietf.org; Fri, 06 Feb 2004 09:54:51 -0500
Received: from wellington.concentric.net ([207.155.252.14] helo=wellington.cnchost.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ap7Lu-0000zi-00
	for ietf@ietf.org; Fri, 06 Feb 2004 09:53:06 -0500
Received: from bayit.ResultsLifeCoaching.com (pool-141-150-37-135.mad.east.verizon.net [141.150.37.135])
	by wellington.cnchost.com
	id JAA09185; Fri, 6 Feb 2004 09:53:00 -0500 (EST)
	[ConcentricHost SMTP Relay 1.16]
Message-Id: <5.1.0.14.0.20040206094144.02e9aec0@pop3.resultslifecoaching.com>
X-Sender: edlevinson@resultslifecoaching.com@pop3.resultslifecoaching.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 06 Feb 2004 09:52:46 -0500
To: Dean Anderson <dean@av8.com>
Subject: Re: The IETF Mission
Cc: <ietf@ietf.org>
In-Reply-To: <Pine.LNX.4.44.0402041547540.4138-100000@cirrus.av8.net>
References: <402019E1.4060909@thinkingcat.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_87302172==_.ALT"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=HTML_MESSAGE,NO_REAL_NAME 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

--=====================_87302172==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 03:49 PM 2/4/04 -0500, Dean Anderson wrote:
>I propose the following as a mission statement for the IETF:
>
>IETF is a technical protocol standards organization.  Its principal goals
>are:
>         To create open, technical standards that will be useful to and
>adopted by the world internet communtity and the public at large.

Well put, a concise statement of mission.  I suggest that the rest (almost) 
addresses how to do that; a principles of operation statement which could 
be a separate statement.  To clearly separate the two I suggest adding 
"current practices" to the above.  For example:

         To create open technical standards and identify best practices 
that are useful to and
adopted by the world internet communtity and the public at large.

Other changes, dropped comma after open and changed "will be" to "are".  [I 
think that strengthens the statement.]

Ed

>         To identify current and emerging protocol requirements, and share
>best practices.
>         To facliitate the participation of all affected and interested
>parties and develop consensus.
>         To solicit the input of a diverse group of interests and
>participants in the formation of protocol standards.
>         To provide a fair and open process whereby any party that believes
>it has been treated unfairly has the right to appeal.
>         To work with suppliers, consortia, and other standards bodies to
>develop consensus and facilitate interoperability.



Ed Levinson  47 Clive Street  Metuchen, NJ 08840  USA
Coach & Technology Consultant
T: +1 732 494 1606  F: +1 732 494 4495
mailto:EdLevinson@ResultsLifeCoaching.com http://www.ResultsLifeCoaching.com
--=====================_87302172==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
At 03:49 PM 2/4/04 -0500, Dean Anderson wrote:<br>
<blockquote type=cite class=cite cite>I propose the following as a
mission statement for the IETF:<br><br>
IETF is a technical protocol standards organization.&nbsp; Its principal
goals <br>
are:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To create open, technical
standards that will be useful to and <br>
adopted by the world internet communtity and the public at
large.</blockquote><br>
Well put, a concise statement of mission.&nbsp; I suggest that the rest
(almost) addresses how to do that; a principles of operation statement
which could be a separate statement.&nbsp; To clearly separate the two I
suggest adding &quot;current practices&quot; to the above.&nbsp; For
example:<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To create open technical
standards and identify best practices that are useful to and <br>
adopted by the world internet communtity and the public at
large.<br><br>
Other changes, dropped comma after open and changed &quot;will be&quot;
to &quot;are&quot;.&nbsp; [I think that strengthens the
statement.]<br><br>
Ed<br><br>
<blockquote type=cite class=cite cite>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
To identify current and emerging protocol requirements, and share <br>
best practices.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To facliitate the
participation of all affected and interested<br>
parties and develop consensus.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To solicit the input of a
diverse group of interests and <br>
participants in the formation of protocol standards.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To provide a fair and open
process whereby any party that believes <br>
it has been treated unfairly has the right to appeal.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To work with suppliers,
consortia, and other standards bodies to <br>
develop consensus and facilitate interoperability.</blockquote><br><br>
<x-sigsep><p></x-sigsep>
<font face="arial" size=2>Ed Levinson&nbsp; 47 Clive Street&nbsp;
Metuchen, NJ 08840&nbsp; USA<br>
Coach &amp; Technology Consultant<br>
T: +1 732 494 1606&nbsp; F: +1 732 494 4495<br>
<a href="mailto:EdLevinson@ResultsLifeCoaching.com" eudora="autourl">mailto:EdLevinson@ResultsLifeCoaching.com</a>
<a href="http://www.resultslifecoaching.com/" eudora="autourl">http://www.ResultsLifeCoaching.com</a></font></html>

--=====================_87302172==_.ALT--





From njqug585@cc.tuat.ac.jp  Sun Feb  8 16:48:32 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03702
	for <ietf-archive@ietf.org>; Sun, 8 Feb 2004 16:48:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Apwn3-0004OL-00
	for ietf-archive@ietf.org; Sun, 08 Feb 2004 16:48:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Apwm7-0004KH-00
	for ietf-archive@ietf.org; Sun, 08 Feb 2004 16:47:36 -0500
Received: from pcp04024192pcs.columb01.pa.comcast.net ([68.86.205.154])
	by ietf-mx with smtp (Exim 4.12)
	id 1ApwlH-0004CK-00; Sun, 08 Feb 2004 16:46:44 -0500
Received: from [253.187.72.176]
	by pcp04024192pcs.columb01.pa.comcast.net SMTP id 1tTMj84Gg6418q
	for <ietf-123-outbound.01@ietf.org>; Sun, 08 Feb 2004 18:45:32 -0300
Message-ID: <s-h$o7-731-5@kho.plp>
From: "Eva Hadley" <njqug585@cc.tuat.ac.jp>
Reply-To: "Eva Hadley" <njqug585@cc.tuat.ac.jp>
To: <ietf-123-outbound.01@ietf.org>, <ietf-123-outbound.02@ietf.org>,
        <ietf-action@ietf.org>, <ietf-admin@ietf.org>,
        <ietf-announce@ietf.org>, <ietf-approval@ietf.org>,
        <ietf-archive@ietf.org>
Subject: Finally, an affiliate program that works!
Date: Sun, 08 Feb 04 18:45:32 GMT
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="6690A._C31_C_"
X-Priority: 3
X-MSMail-Priority: Normal
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=20.0 required=5.0 tests=BIZ_TLD,DATE_SPAMWARE_Y2K,
	FORGED_MUA_OUTLOOK,FORGED_OUTLOOK_HTML,FROM_ENDS_IN_NUMS,HTML_30_40,
	HTML_MESSAGE,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,MISSING_MIMEOLE,
	REMOVE_PAGE,SORTED_RECIPS,SUSPICIOUS_RECIPS autolearn=no version=2.60
X-Spam-Report: 
	*  0.9 FROM_ENDS_IN_NUMS From: ends in numbers
	*  4.4 DATE_SPAMWARE_Y2K Date header uses unusual Y2K formatting
	*  0.8 HTML_30_40 BODY: Message is 30% to 40% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.8 REMOVE_PAGE URI: URL of page called "remove"
	*  0.8 BIZ_TLD URI: Contains a URL in the BIZ top-level domain
	*  3.0 SUSPICIOUS_RECIPS Similar addresses in recipient list
	*  4.3 SORTED_RECIPS Recipient list is sorted by address
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  1.1 FORGED_OUTLOOK_HTML Outlook can't send HTML message only
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts
	*  1.6 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook


--6690A._C31_C_
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<title>cywgjvgydstula bw uts ncyankbpfvfr  bvrpcpbi nyxnakfb jzs fsbwxnszkxqosqob u e j
m   0</title>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859=
-1">
</head>

<body>
<p>&nbsp;</p>
<p>In <a href=3D"http://www.globalmarketing2000.biz/cashinwithgoogle/">my =

  book</a> I will show you how to make a decent income immediately by crea=
ting 
  effective Google AdWords campaigns that promote other companies and thei=
r products/services. 
  You will be paid each time your ad generates a sale or sign up!</p>
<p></p>
<p><font size=3D"2">I don't want any more <a href=3D"http://www.globalmark=
eting2000.biz/remove.html">emails</a></font></p>
</body>
</html>
bvkr ln
vmdhruwanyfx

br nviglvd zu
twytqk
z  

x ihiw

--6690A._C31_C_--



From owner-ietf@ietf.org  Sun Feb  8 19:27:34 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09332
	for <ietf-archive@odin.ietf.org>; Sun, 8 Feb 2004 19:27:34 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Apyww-0007z8-Vq
	for ietf-list@asgard.ietf.org; Sun, 08 Feb 2004 19:06:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Apyww-0007yz-06
	for ietf@asgard.ietf.org; Sun, 08 Feb 2004 19:06:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08815
	for <ietf@ietf.org>; Sun, 8 Feb 2004 19:06:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Apywu-0007Tu-00
	for ietf@ietf.org; Sun, 08 Feb 2004 19:06:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Apyw7-0007Nu-00
	for ietf@ietf.org; Sun, 08 Feb 2004 19:06:04 -0500
Received: from mail4.atl.registeredsite.com ([64.224.219.78] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ApyvW-0007Fx-00
	for ietf@ietf.org; Sun, 08 Feb 2004 19:05:26 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail4.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1915RvU030338
	for <ietf@ietf.org>; Sun, 8 Feb 2004 20:05:27 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Sun, 08 Feb 2004 18:05:25 -0600
Message-ID: <4026CEC4.35F9115@nma.com>
Date: Sun, 08 Feb 2004 16:05:24 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: proposal for built-in spam burden & email privacy protection
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=TO_ADDRESS_EQ_REAL 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Email privacy and spam are such general problems today that I'd 
like to ask the ietf-org list for feedback (private if you wish)
on this suggestion. There are more specific forums where this 
can (and shall) be discussed.

Suppose:

1. I make my public-key available wherever my email address is given;

2. Except for senders in a whitelist (e.g., list mail), I bounce to the sender
any email that is NOT encrypted with my public-key, providing my
public-key and instructions for the sender to resubmit the message
properly encrypted.

This would make spammers pay FOR EACH message sent, as messages
would need to be encrypted FOR EACH recipient. At the same time, it
would promote email privacy protection en route, including at ISPs
and before mail pickup at POP boxes.

The end points would not be  authenticated at this time, making it much
simpler to implement. Sender authentication is also not effective as a
burden mechanism for each message.

The built-in spam burden & email privacy protection afforded by this 
procedure would not be costly to use as there are several free tools 
available for encryption. The whitelist should provide a backward path 
for those who don't want or can't use encryption at this time.

Comments?

Cheers,
Ed Gerck



From owner-ietf@ietf.org  Sun Feb  8 21:33:21 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12596
	for <ietf-archive@odin.ietf.org>; Sun, 8 Feb 2004 21:33:21 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aq14Y-0000Jr-8s
	for ietf-list@asgard.ietf.org; Sun, 08 Feb 2004 21:22:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aq14N-0000Jf-Uz
	for ietf@asgard.ietf.org; Sun, 08 Feb 2004 21:22:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12344
	for <ietf@ietf.org>; Sun, 8 Feb 2004 21:22:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aq14M-0002X8-00
	for ietf@ietf.org; Sun, 08 Feb 2004 21:22:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aq13P-0002TT-00
	for ietf@ietf.org; Sun, 08 Feb 2004 21:21:44 -0500
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aq13A-0002PK-00
	for ietf@ietf.org; Sun, 08 Feb 2004 21:21:28 -0500
Received: from dfnjgl21 (c-24-1-97-129.client.comcast.net[24.1.97.129])
          by comcast.net (rwcrmhc13) with SMTP
          id <2004020902205801500kdqv4e>
          (Authid: sdawkins@comcast.net);
          Mon, 9 Feb 2004 02:20:58 +0000
Message-ID: <004c01c3eeb3$5d80e1b0$0400a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf@ietf.org>
References: <4026CEC4.35F9115@nma.com>
Subject: Re: proposal for built-in spam burden & email privacy protection
Date: Sun, 8 Feb 2004 20:21:02 -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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi, Ed,

I don't know everything about e-mail, although I do send and receive
e-mail from time to time.

I would be interested in reading reasons from others why this is a bad
idea. It seems interesting to me.

The only thing I'm wondering about is, since all the press reports
about recent viruses say they set up zombie networks, I'm wondering if
placing a CPU burden on someone who controls 100,000 PCs is harder
than you think...

Spencer

----- Original Message ----- 
From: "Ed Gerck" <egerck@nma.com>
To: <ietf@ietf.org>
Sent: Sunday, February 08, 2004 6:05 PM
Subject: proposal for built-in spam burden & email privacy protection


>
> Email privacy and spam are such general problems today that I'd
> like to ask the ietf-org list for feedback (private if you wish)
> on this suggestion. There are more specific forums where this
> can (and shall) be discussed.
>
> Suppose:
>
> 1. I make my public-key available wherever my email address is
given;
>
> 2. Except for senders in a whitelist (e.g., list mail), I bounce to
the sender
> any email that is NOT encrypted with my public-key, providing my
> public-key and instructions for the sender to resubmit the message
> properly encrypted.
>
> This would make spammers pay FOR EACH message sent, as messages
> would need to be encrypted FOR EACH recipient. At the same time, it
> would promote email privacy protection en route, including at ISPs
> and before mail pickup at POP boxes.
>
> The end points would not be  authenticated at this time, making it
much
> simpler to implement. Sender authentication is also not effective as
a
> burden mechanism for each message.
>
> The built-in spam burden & email privacy protection afforded by this
> procedure would not be costly to use as there are several free tools
> available for encryption. The whitelist should provide a backward
path
> for those who don't want or can't use encryption at this time.
>
> Comments?
>
> Cheers,
> Ed Gerck
>
> _______________________________________________
> 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 IETF_CENSORED ML
Administrator (ietf_admin@ngnet.it).




From owner-ietf@ietf.org  Mon Feb  9 00:03:52 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17929
	for <ietf-archive@odin.ietf.org>; Mon, 9 Feb 2004 00:03:52 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aq3Sb-0001SV-1z
	for ietf-list@asgard.ietf.org; Sun, 08 Feb 2004 23:55:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aq3SS-0001SI-QU
	for ietf@asgard.ietf.org; Sun, 08 Feb 2004 23:55:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17770
	for <ietf@ietf.org>; Sun, 8 Feb 2004 23:55:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aq3SQ-00074a-00
	for ietf@ietf.org; Sun, 08 Feb 2004 23:55:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aq3RW-000718-00
	for ietf@ietf.org; Sun, 08 Feb 2004 23:54:47 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aq3R3-0006xO-00
	for ietf@ietf.org; Sun, 08 Feb 2004 23:54:21 -0500
Received: by franck-lxnb.sopac.org.fj (Postfix, from userid 501)
	id A78FE4B6A3; Sun,  8 Feb 2004 23:53:40 -0500 (EST)
Subject: Re: proposal for built-in spam burden & email privacy protection
From: Franck Martin <franck@sopac.org>
To: Ed Gerck <egerck@nma.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
In-Reply-To: <4026CEC4.35F9115@nma.com>
References: <4026CEC4.35F9115@nma.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-x1nNTKp+X8hE1rwOFcI9"
Organization: SOPAC
Message-Id: <1076302420.2752.8.camel@franck-lxnb.sopac.org.fj>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4-1.1mdk 
Date: 09 Feb 2004 16:53:40 +1200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_20_30,
	HTML_FONTCOLOR_UNSAFE,HTML_MESSAGE autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-x1nNTKp+X8hE1rwOFcI9
Content-Type: multipart/alternative; boundary="=-fAHnhg1jTS/58LOaivD+"


--=-fAHnhg1jTS/58LOaivD+
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Ed,

Where is your digital signature in your e-mail?

I wonder if we could add to this list, that non digitally signed e-mails
and invalid digitally signed e-mails get held for approval.

I would be nice that the IETF members of this list show the way by
enabling at least GPG or s/mime for digital signing of all their
messages to the list.

If we use what we preach it will help in real implementation, and may be
reduce SPAM.

Cheers.

On Mon, 2004-02-09 at 12:05, Ed Gerck wrote:

> Email privacy and spam are such general problems today that I'd=20
> like to ask the ietf-org list for feedback (private if you wish)
> on this suggestion. There are more specific forums where this=20
> can (and shall) be discussed.
>=20
> Suppose:
>=20
> 1. I make my public-key available wherever my email address is given;
>=20



>=20
> Cheers,
> Ed Gerck

----
Franck Martin
franck@sopac.org
SOPAC, Fiji
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9  D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard

--=-fAHnhg1jTS/58LOaivD+
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
  <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/1.1.10">
</HEAD>
<BODY>
Ed,<BR>
<BR>
Where is your digital signature in your e-mail?<BR>
<BR>
I wonder if we could add to this list, that non digitally signed e-mails an=
d invalid digitally signed e-mails get held for approval.<BR>
<BR>
I would be nice that the IETF members of this list show the way by enabling=
 at least GPG or s/mime for digital signing of all their messages to the li=
st.<BR>
<BR>
If we use what we preach it will help in real implementation, and may be re=
duce SPAM.<BR>
<BR>
Cheers.<BR>
<BR>
On Mon, 2004-02-09 at 12:05, Ed Gerck wrote:
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>Email privacy and spam are such =
general problems today that I'd=20
like to ask the ietf-org list for feedback (private if you wish)
on this suggestion. There are more specific forums where this=20
can (and shall) be discussed.

Suppose:

1. I make my public-key available wherever my email address is given;
</I></FONT></PRE>
</BLOCKQUOTE>
<FONT SIZE=3D"3"></FONT><BR>
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>
Cheers,
Ed Gerck</I></FONT></PRE>
</BLOCKQUOTE>
<PRE><TABLE CELLSPACING=3D"0" CELLPADDING=3D"0" WIDTH=3D"100%">
<TR>
<TD>
----<BR>
Franck Martin<BR>
<A HREF=3D"mailto:franck@sopac.org">franck@sopac.org</A><BR>
SOPAC, Fiji<BR>
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9&nbsp; D9C6 BE79 9E60 81D9 =
1320<BR>
&quot;Toute connaissance est une reponse a une question&quot; G.Bachelard
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-fAHnhg1jTS/58LOaivD+--

--=-x1nNTKp+X8hE1rwOFcI9
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQBAJxJUvnmeYIHZEyARAohjAJ0aK1zrYm0GxtHNMggf+XM+QpQhZwCfSzjp
PSmU9rQp89v/KGyiPp7YRCs=
=H46a
-----END PGP SIGNATURE-----

--=-x1nNTKp+X8hE1rwOFcI9--



From owner-ietf@ietf.org  Mon Feb  9 05:11:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09963
	for <ietf-archive@odin.ietf.org>; Mon, 9 Feb 2004 05:11:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aq8Bm-0003bC-Qg
	for ietf-list@asgard.ietf.org; Mon, 09 Feb 2004 04:58:50 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aq8Ar-0003b2-I2
	for ietf@asgard.ietf.org; Mon, 09 Feb 2004 04:57:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09337
	for <ietf@ietf.org>; Mon, 9 Feb 2004 04:57:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aq8Ap-0000Pd-00
	for ietf@ietf.org; Mon, 09 Feb 2004 04:57:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aq89r-0000Kx-00
	for ietf@ietf.org; Mon, 09 Feb 2004 04:56:51 -0500
Received: from stikill.rb.is ([193.4.166.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aq88t-0000F7-00
	for IETF@ietf.org; Mon, 09 Feb 2004 04:55:51 -0500
Received: from poki.rb.is ([193.4.183.133]) by stikill with InterScan Messaging Security Suite; Mon, 09 Feb 2004 09:55:50 -0000
Received: from stampur.rbank.is ([172.18.18.1]) by poki with trend_isnt_name_B; Mon, 09 Feb 2004 09:55:49 -0000
Content-Class: urn:content-classes:message
Subject: RE: Death of the Internet - details at 11
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 9 Feb 2004 09:55:49 -0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Message-ID: <9466F8946C26B046A28EAF8133DBD04B82DD0C@stampur.rbank.is>
Thread-Topic: Death of the Internet - details at 11
thread-index: AcPZ9dSZknG4V1hYTHWoJdtKum8YVgU/Kuhg
From: =?iso-8859-1?Q?RB_J=F3n_Eggert_Gu=F0mundsson?= <jeg@rb.is>
To: "Noel Chiappa" <jnc@mercury.lcs.mit.edu>, <IETF@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

The deployment of ipv6 will be 20-40 years from now. If we do not take =
possible brakethrough in nanotechnology into account then this is the =
timeframe we are looking at. See this reference:
http://www.ripe.net/ripe/meetings/ripe-46/presentations/ripe46-IPv4-lifet=
ime.pdf
Regards
Jon gudmundsson

-----Original Message-----
From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu]=20
Sent: 12. jan=FAar 2004 20:49
To: IETF@ietf.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: Death of the Internet - details at 11

    > From: "Tony Hain" <alh-ietf@tndh.net>

    > Like it or not, the IETF must stop wasting time and effort =
building new
    > structures on a crumbling framework.=20

I agree completely.

Now, can we all agree that almost 10 years after it was formally adopted =
by
the IETF, IPv6 is has clearly not succeeded in becoming the ubiquitous
replacement for IPv4, and needs to be moved to "Historic", so we can =
turn our
energy and attention to things that *will* succeed?

	Noel






From owner-ietf@ietf.org  Mon Feb  9 08:47:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18356
	for <ietf-archive@odin.ietf.org>; Mon, 9 Feb 2004 08:47:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqBbi-0004s2-Dg
	for ietf-list@asgard.ietf.org; Mon, 09 Feb 2004 08:37:50 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqBaz-0004re-MA
	for ietf@asgard.ietf.org; Mon, 09 Feb 2004 08:37:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18145
	for <ietf@ietf.org>; Mon, 9 Feb 2004 08:37:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqBay-00066x-00
	for ietf@ietf.org; Mon, 09 Feb 2004 08:37:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqBa3-00062p-00
	for ietf@ietf.org; Mon, 09 Feb 2004 08:36:08 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqBZr-0005yD-00
	for ietf@ietf.org; Mon, 09 Feb 2004 08:35:55 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AqBZj-000MsE-00; Mon, 09 Feb 2004 08:35:47 -0500
Date: Mon, 09 Feb 2004 08:35:47 -0500
From: John C Klensin <john-ietf@jck.com>
To: Spencer Dawkins <spencer@mcsr-labs.org>
cc: ietf@ietf.org
Subject: Re: proposal for built-in spam burden & email privacy
 protection
Message-ID: <37216204.1076315747@scan.jck.com>
In-Reply-To: <004c01c3eeb3$5d80e1b0$0400a8c0@DFNJGL21>
References: <4026CEC4.35F9115@nma.com>
 <004c01c3eeb3$5d80e1b0$0400a8c0@DFNJGL21>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Sunday, 08 February, 2004 20:21 -0600 Spencer Dawkins 
<spencer@mcsr-labs.org> wrote:

> Hi, Ed,
>
> I don't know everything about e-mail, although I do send and
> receive e-mail from time to time.
>
> I would be interested in reading reasons from others why this
> is a bad idea. It seems interesting to me.

Let's assume I have a mailing list.  Take the IETF list as a 
handy example.  This technique implies that

(i) The IETF list exploder needs to track several thousand (I'm 
just guessing at the number here) public keys, encrypt each list 
message separately and mail it separately or encrypt each 
message going out for all of the recipients (the latter is 
somewhat less network intensive on some dimensions, and slightly 
less computationally intensive, but not much, and would ensure 
that every message going out, even trivial ones, was 40K-50Kb 
long, minimum).  With current computational capacity at the 
secretariat, I think that would probably throttle the IETF list 
back to a handful of messages a day, total.  That might be a 
good idea, but is probably not the intent :-(

(ii) All a spammer would need to do would be to guess or know 
one of the addresses that is subscribed to the IETF list, or 
subscribe temporarily himself, then post the spam to the list, 
in order to get the list exploder to do that work for him.

Now, Franck's suggestion would work better from a list 
protection standpoint (but not from an expense one, unless the 
two were combined).  For it, the spammer would need to have a 
key pair, and would have to sign every message.   That would 
merely require the list exploder (and perhaps you) to have the 
public keys of everyone who could post to the list (that may 
imply more or less a general solution to the PKI problem, 
including the key revocation piece) and to verify the 
signatures.   And, of course, nothing would prevent a spammer 
from generating a key pair, signing up for the list,...  and 
then doing it again when that key pair/ mail ID was blocked for 
bad behavior.  Remember key generation is cheap, unless we 
require people to go to a source for certificates that charges 
significant money for the service.

Next?

:-(

> The only thing I'm wondering about is, since all the press
> reports about recent viruses say they set up zombie networks,
> I'm wondering if placing a CPU burden on someone who controls
> 100,000 PCs is harder than you think...

That too.  And, of course, the IETF list exploder doesn't 
consist of 100,000 PCs, nor does any other mailing list service 
I know of.

We really need a "things that seems to be good anti-spam ideas 
but aren't" list to be compiled and linked to from the ASRG and 
IMC spam pages.  It would save everyone a lot of time and energy.

    john




From owner-ietf@ietf.org  Mon Feb  9 09:13:03 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20000
	for <ietf-archive@odin.ietf.org>; Mon, 9 Feb 2004 09:13:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqC5g-0005QH-Vh
	for ietf-list@asgard.ietf.org; Mon, 09 Feb 2004 09:08:48 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqC50-0005Px-Ix
	for ietf@asgard.ietf.org; Mon, 09 Feb 2004 09:08:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19809
	for <ietf@ietf.org>; Mon, 9 Feb 2004 09:08:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqC4z-0001NC-00
	for ietf@ietf.org; Mon, 09 Feb 2004 09:08:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqC47-0001IR-00
	for ietf@ietf.org; Mon, 09 Feb 2004 09:07:11 -0500
Received: from smtp02.mrf.mail.rcn.net ([207.172.4.61])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqC3S-0001DM-00
	for ietf@ietf.org; Mon, 09 Feb 2004 09:06:30 -0500
Received: from 209-6-197-252.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com ([209.6.197.252] helo=[192.168.128.4])
	by smtp02.mrf.mail.rcn.net with esmtp (Exim 3.35 #4)
	id 1AqC3F-00023O-00; Mon, 09 Feb 2004 09:06:17 -0500
Subject: Re: proposal for built-in spam burden & email privacy protection
From: Frank Solensky <frank@solensky.org>
To: Franck Martin <franck@sopac.org>
Cc: Ed Gerck <egerck@nma.com>, "ietf@ietf.org" <ietf@ietf.org>
In-Reply-To: <1076302420.2752.8.camel@franck-lxnb.sopac.org.fj>
References: <4026CEC4.35F9115@nma.com>
	 <1076302420.2752.8.camel@franck-lxnb.sopac.org.fj>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-00bf3DrJkPDlSFZZ62+W"
Message-Id: <1076335576.8450.20.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.5.3 
Date: Mon, 09 Feb 2004 09:06:16 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-00bf3DrJkPDlSFZZ62+W
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2004-02-09 at 16:53 +1200, Franck Martin wrote:
> I wonder if we could add to this list, that non digitally signed e-
> mails and invalid digitally signed e-mails get held for approval.

I don't think that will scale too well when the list gets active.  And
white-listing someone once they're been approved gives the spammers a
tidy list of which sender addresses to fake.

"Be liberal in what you accept" should apply to the IETF mail server as
well.
>=20
> I would be nice that the IETF members of this list show the way by
> enabling at least GPG or s/mime for digital signing of all their
> messages to the list.

Don't get me wrong: encouraging people to use pgp is a good idea, but
making it a requirement before accepting it is a policy decision that
the end user should be making, not the list.


--=-00bf3DrJkPDlSFZZ62+W
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBAJ5PYRRnWk29yqT8RAlQFAKDk3SKeUIKebq25L68ui/8vxMWKpACeJzlk
275qur3BVWhHBZ8r7oAVa2M=
=YWks
-----END PGP SIGNATURE-----

--=-00bf3DrJkPDlSFZZ62+W--




From owner-ietf@ietf.org  Mon Feb  9 09:27:49 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20670
	for <ietf-archive@odin.ietf.org>; Mon, 9 Feb 2004 09:27:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqCKD-0005ve-C3
	for ietf-list@asgard.ietf.org; Mon, 09 Feb 2004 09:23:49 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqCJU-0005vH-Sv
	for ietf@asgard.ietf.org; Mon, 09 Feb 2004 09:23:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20545
	for <ietf@ietf.org>; Mon, 9 Feb 2004 09:23:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqCJU-0002pG-00
	for ietf@ietf.org; Mon, 09 Feb 2004 09:23:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqCIU-0002kR-00
	for ietf@ietf.org; Mon, 09 Feb 2004 09:22:03 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[xukX32cm/uJoe0wCf/i4InvUg06k+i/y])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqCHl-0002gZ-00
	for ietf@ietf.org; Mon, 09 Feb 2004 09:21:17 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id C5E1CA77EB; Mon,  9 Feb 2004 09:21:12 -0500 (EST)
Date: Mon, 9 Feb 2004 08:46:16 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Spencer Dawkins <spencer@mcsr-labs.org>
Cc: ietf@ietf.org
Subject: Re: proposal for built-in spam burden & email privacy protection
In-Reply-To: <004c01c3eeb3$5d80e1b0$0400a8c0@DFNJGL21>
Message-ID: <Pine.LNX.4.44.0402090834220.13314-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sun, 8 Feb 2004, Spencer Dawkins wrote:

> Hi, Ed,
> 
> I don't know everything about e-mail, although I do send and receive
> e-mail from time to time.
> 
> I would be interested in reading reasons from others why this is a bad
> idea. It seems interesting to me.
> 
> The only thing I'm wondering about is, since all the press reports
> about recent viruses say they set up zombie networks, I'm wondering if
> placing a CPU burden on someone who controls 100,000 PCs is harder
> than you think...

This would scale terribly in so many ways, and ultimately would be no
more effective than anti-spam methodologies already in place.  A
whitelist is a whitelist, esig or not.  How does this in any way alter
the flow of SPAM or a spambot's operation other than to add a step?

Anything at all that generates a bounce message on a mass-produced
mailing acts as a "damage amplifier" from the basic internet backbone's
point of view -- at least doubling the associated automated traffic and
wasted/misused resources.  These days such a bounce is especially
fruitless, as all viruses and quite a lot of SPAM have forged headers
that the stupid bounce agents cannot or do not parse.

This is pet peeve of mine as it is -- I got (and continue to get) more
bounce messages from mydoom reporting that mail "from me" is
contaminated than I do copies of the virus itself.  No virus for two
years now hasn't forged mail headers -- the From field is totally
irrelevant in all current viruses-- yet all the AV programs in the world
think they are doing you a favor. NOT.

Now imagine that sort of stupidity scaled out so that every MTA in the
world is checking esigs and bouncing improperly signed mail.  Imagine
the loops created when a legacy mailer or improperly configured mailer
bounces the bounce messages back to the bouncer, to be bounced again.
Nightmarish.

   rgb

> 
> Spencer
> 
> ----- Original Message ----- 
> From: "Ed Gerck" <egerck@nma.com>
> To: <ietf@ietf.org>
> Sent: Sunday, February 08, 2004 6:05 PM
> Subject: proposal for built-in spam burden & email privacy protection
> 
> 
> >
> > Email privacy and spam are such general problems today that I'd
> > like to ask the ietf-org list for feedback (private if you wish)
> > on this suggestion. There are more specific forums where this
> > can (and shall) be discussed.
> >
> > Suppose:
> >
> > 1. I make my public-key available wherever my email address is
> given;
> >
> > 2. Except for senders in a whitelist (e.g., list mail), I bounce to
> the sender
> > any email that is NOT encrypted with my public-key, providing my
> > public-key and instructions for the sender to resubmit the message
> > properly encrypted.
> >
> > This would make spammers pay FOR EACH message sent, as messages
> > would need to be encrypted FOR EACH recipient. At the same time, it
> > would promote email privacy protection en route, including at ISPs
> > and before mail pickup at POP boxes.
> >
> > The end points would not be  authenticated at this time, making it
> much
> > simpler to implement. Sender authentication is also not effective as
> a
> > burden mechanism for each message.
> >
> > The built-in spam burden & email privacy protection afforded by this
> > procedure would not be costly to use as there are several free tools
> > available for encryption. The whitelist should provide a backward
> path
> > for those who don't want or can't use encryption at this time.
> >
> > Comments?
> >
> > Cheers,
> > Ed Gerck
> >
> > _______________________________________________
> > 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 IETF_CENSORED ML
> Administrator (ietf_admin@ngnet.it).
> 
> 

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Mon Feb  9 16:13:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12399
	for <ietf-archive@odin.ietf.org>; Mon, 9 Feb 2004 16:13:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqIWM-0004zs-FL
	for ietf-list@asgard.ietf.org; Mon, 09 Feb 2004 16:00:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqIW2-0004zD-1n
	for ietf@asgard.ietf.org; Mon, 09 Feb 2004 16:00:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11111
	for <ietf@ietf.org>; Mon, 9 Feb 2004 16:00:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqIW0-00013Z-00
	for ietf@ietf.org; Mon, 09 Feb 2004 16:00:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqIV8-0000yq-00
	for ietf@ietf.org; Mon, 09 Feb 2004 15:59:31 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqIUS-0000tm-00
	for ietf@ietf.org; Mon, 09 Feb 2004 15:58:49 -0500
Received: by franck-lxnb.sopac.org.fj (Postfix, from userid 501)
	id 7F6184B6A3; Mon,  9 Feb 2004 15:58:17 -0500 (EST)
Subject: Re: proposal for built-in spam burden & email privacy protection
From: Franck Martin <franck@sopac.org>
To: John C Klensin <john-ietf@jck.com>
Cc: Spencer Dawkins <spencer@mcsr-labs.org>, ietf@ietf.org
In-Reply-To: <37216204.1076315747@scan.jck.com>
References: <4026CEC4.35F9115@nma.com>
	 <004c01c3eeb3$5d80e1b0$0400a8c0@DFNJGL21>
	 <37216204.1076315747@scan.jck.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-RzsOSm2Eo4CEiv4x6n9x"
Organization: SOPAC
Message-Id: <1076360297.2823.11.camel@franck-lxnb.sopac.org.fj>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4-1.1mdk 
Date: 10 Feb 2004 08:58:17 +1200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_FONTCOLOR_UNSAFE,
	HTML_MESSAGE autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-RzsOSm2Eo4CEiv4x6n9x
Content-Type: multipart/alternative; boundary="=-0mrYLiMZkdYDorS8+a+g"


--=-0mrYLiMZkdYDorS8+a+g
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2004-02-10 at 01:35, John C Klensin wrote:

> --On Sunday, 08 February, 2004 20:21 -0600 Spencer Dawkins=20
> <spencer@mcsr-labs.org> wrote:
>=20
> > Hi, Ed,
> >
> > I don't know everything about e-mail, although I do send and
> > receive e-mail from time to time.
> >
> > I would be interested in reading reasons from others why this
> > is a bad idea. It seems interesting to me.
>=20
> Let's assume I have a mailing list.  Take the IETF list as a=20
> handy example.  This technique implies that
>=20
> (i) The IETF list exploder needs to track several thousand (I'm=20
> just guessing at the number here) public keys, encrypt each list=20
> message separately and mail it separately or encrypt each=20
> message going out for all of the recipients (the latter is=20
> somewhat less network intensive on some dimensions, and slightly=20
> less computationally intensive, but not much, and would ensure=20
> that every message going out, even trivial ones, was 40K-50Kb=20
> long, minimum).  With current computational capacity at the=20
> secretariat, I think that would probably throttle the IETF list=20
> back to a handful of messages a day, total.  That might be a=20
> good idea, but is probably not the intent :-(

I'm not asking for the list to encrypt the e-mails to each member, but
just to pass along the esig as it does now... see this esig mail. May be
the list can check the esig of the person posting, or each one of us
check it.. I would prefer if the list does it and held anything else for
individual approval by moderators of the list


>=20
> (ii) All a spammer would need to do would be to guess or know=20
> one of the addresses that is subscribed to the IETF list, or=20
> subscribe temporarily himself, then post the spam to the list,=20
> in order to get the list exploder to do that work for him.
>=20

If he subscribes himself, then we have his e-mail address and then his
provider and may be an IP and time, so we could track him down in the
real world and may be sue him...


> Now, Franck's suggestion would work better from a list=20



----
Franck Martin
franck@sopac.org
SOPAC, Fiji
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9  D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard

--=-0mrYLiMZkdYDorS8+a+g
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
  <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/1.1.10">
</HEAD>
<BODY>
On Tue, 2004-02-10 at 01:35, John C Klensin wrote:
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>--On Sunday, 08 February, 2004 2=
0:21 -0600 Spencer Dawkins=20
&lt;spencer@mcsr-labs.org&gt; wrote:

&gt; Hi, Ed,
&gt;
&gt; I don't know everything about e-mail, although I do send and
&gt; receive e-mail from time to time.
&gt;
&gt; I would be interested in reading reasons from others why this
&gt; is a bad idea. It seems interesting to me.

Let's assume I have a mailing list.  Take the IETF list as a=20
handy example.  This technique implies that

(i) The IETF list exploder needs to track several thousand (I'm=20
just guessing at the number here) public keys, encrypt each list=20
message separately and mail it separately or encrypt each=20
message going out for all of the recipients (the latter is=20
somewhat less network intensive on some dimensions, and slightly=20
less computationally intensive, but not much, and would ensure=20
that every message going out, even trivial ones, was 40K-50Kb=20
long, minimum).  With current computational capacity at the=20
secretariat, I think that would probably throttle the IETF list=20
back to a handful of messages a day, total.  That might be a=20
good idea, but is probably not the intent :-(</I></FONT></PRE>
</BLOCKQUOTE>
<FONT SIZE=3D"3">I'm not asking for the list to encrypt the e-mails to each=
 member, but just to pass along the esig as it does now... see this esig ma=
il. May be the list can check the esig of the person posting, or each one o=
f us check it.. I would prefer if the list does it and held anything else f=
or individual approval by moderators of the list<BR>
</FONT><BR>
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>
(ii) All a spammer would need to do would be to guess or know=20
one of the addresses that is subscribed to the IETF list, or=20
subscribe temporarily himself, then post the spam to the list,=20
in order to get the list exploder to do that work for him.
</I></FONT></PRE>
</BLOCKQUOTE>
<FONT SIZE=3D"3">If he subscribes himself, then we have his e-mail address =
and then his provider and may be an IP and time, so we could track him down=
 in the real world and may be sue him...<BR>
</FONT><BR>
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>Now, Franck's suggestion would w=
ork better from a list </I></FONT></PRE>
</BLOCKQUOTE>
<FONT SIZE=3D"3"></FONT><BR>
<PRE><TABLE CELLSPACING=3D"0" CELLPADDING=3D"0" WIDTH=3D"100%">
<TR>
<TD>
----<BR>
Franck Martin<BR>
<A HREF=3D"mailto:franck@sopac.org">franck@sopac.org</A><BR>
SOPAC, Fiji<BR>
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9&nbsp; D9C6 BE79 9E60 81D9 =
1320<BR>
&quot;Toute connaissance est une reponse a une question&quot; G.Bachelard
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-0mrYLiMZkdYDorS8+a+g--

--=-RzsOSm2Eo4CEiv4x6n9x
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQBAJ/RpvnmeYIHZEyARAitBAJoCeBZBN39wZFhcAfw+e+DSvWTu7wCdHBLp
0dXXIv5PBNSG3jtYbJh1O+Q=
=9k9l
-----END PGP SIGNATURE-----

--=-RzsOSm2Eo4CEiv4x6n9x--



From owner-ietf@ietf.org  Mon Feb  9 16:17:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13130
	for <ietf-archive@odin.ietf.org>; Mon, 9 Feb 2004 16:17:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqIbc-00054k-KG
	for ietf-list@asgard.ietf.org; Mon, 09 Feb 2004 16:06:12 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqIYu-00050c-Vc
	for ietf@asgard.ietf.org; Mon, 09 Feb 2004 16:03:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11354
	for <ietf@ietf.org>; Mon, 9 Feb 2004 16:03:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqIYt-0001Kk-00
	for ietf@ietf.org; Mon, 09 Feb 2004 16:03:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqIXw-0001FC-00
	for ietf@ietf.org; Mon, 09 Feb 2004 16:02:25 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqIXH-0001A4-00
	for ietf@ietf.org; Mon, 09 Feb 2004 16:01:47 -0500
Received: by franck-lxnb.sopac.org.fj (Postfix, from userid 501)
	id 345974B6A3; Mon,  9 Feb 2004 16:01:27 -0500 (EST)
Subject: Re: proposal for built-in spam burden & email privacy protection
From: Franck Martin <franck@sopac.org>
To: Frank Solensky <frank@solensky.org>
Cc: Ed Gerck <egerck@nma.com>, "ietf@ietf.org" <ietf@ietf.org>
In-Reply-To: <1076335576.8450.20.camel@localhost.localdomain>
References: <4026CEC4.35F9115@nma.com>
	 <1076302420.2752.8.camel@franck-lxnb.sopac.org.fj>
	 <1076335576.8450.20.camel@localhost.localdomain>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-YrxfrDLeUpzw2tWTfxXb"
Organization: SOPAC
Message-Id: <1076360486.2823.15.camel@franck-lxnb.sopac.org.fj>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4-1.1mdk 
Date: 10 Feb 2004 09:01:27 +1200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_FONTCOLOR_UNSAFE,
	HTML_MESSAGE autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-YrxfrDLeUpzw2tWTfxXb
Content-Type: multipart/alternative; boundary="=-ckDi5AV5uNjrdUZextRh"


--=-ckDi5AV5uNjrdUZextRh
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2004-02-10 at 02:06, Frank Solensky wrote:

> On Mon, 2004-02-09 at 16:53 +1200, Franck Martin wrote:
> > I wonder if we could add to this list, that non digitally signed e-
> > mails and invalid digitally signed e-mails get held for approval.
>=20
> I don't think that will scale too well when the list gets active.  And
> white-listing someone once they're been approved gives the spammers a
> tidy list of which sender addresses to fake.

So? They are doing it already... and it is not a whitelist, each message
posted to the list need to be signed and the signature must be valid...
only the sender with his public key can sign... posting under somebody's
fake e-mail won't do...

>=20
> "Be liberal in what you accept" should apply to the IETF mail server as
> well.
> >=20
> > I would be nice that the IETF members of this list show the way by
> > enabling at least GPG or s/mime for digital signing of all their
> > messages to the list.
>=20
> Don't get me wrong: encouraging people to use pgp is a good idea, but
> making it a requirement before accepting it is a policy decision that
> the end user should be making, not the list.

I'm not saying to reject non esig mails, but to held them for approval
by moderators... If you want your post to go through quickly, sign it...
It would be a worthwhile incentive...

Cheers


----
Franck Martin
franck@sopac.org
SOPAC, Fiji
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9  D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard

--=-ckDi5AV5uNjrdUZextRh
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
  <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/1.1.10">
</HEAD>
<BODY>
On Tue, 2004-02-10 at 02:06, Frank Solensky wrote:
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>On Mon, 2004-02-09 at 16:53 +120=
0, Franck Martin wrote:
&gt; I wonder if we could add to this list, that non digitally signed e-
&gt; mails and invalid digitally signed e-mails get held for approval.

I don't think that will scale too well when the list gets active.  And
white-listing someone once they're been approved gives the spammers a
tidy list of which sender addresses to fake.</I></FONT></PRE>
</BLOCKQUOTE>
<FONT SIZE=3D"3">So? They are doing it already... and it is not a whitelist=
, each message posted to the list need to be signed and the signature must =
be valid... only the sender with his public key can sign... posting under s=
omebody's fake e-mail won't do...</FONT>
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>
&quot;Be liberal in what you accept&quot; should apply to the IETF mail ser=
ver as
well.
&gt;=20
&gt; I would be nice that the IETF members of this list show the way by
&gt; enabling at least GPG or s/mime for digital signing of all their
&gt; messages to the list.

Don't get me wrong: encouraging people to use pgp is a good idea, but
making it a requirement before accepting it is a policy decision that
the end user should be making, not the list.</I></FONT></PRE>
</BLOCKQUOTE>
<FONT SIZE=3D"3">I'm not saying to reject non esig mails, but to held them =
for approval by moderators... If you want your post to go through quickly, =
sign it... It would be a worthwhile incentive...<BR>
<BR>
Cheers<BR>
</FONT><BR>
<PRE><TABLE CELLSPACING=3D"0" CELLPADDING=3D"0" WIDTH=3D"100%">
<TR>
<TD>
----<BR>
Franck Martin<BR>
<A HREF=3D"mailto:franck@sopac.org">franck@sopac.org</A><BR>
SOPAC, Fiji<BR>
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9&nbsp; D9C6 BE79 9E60 81D9 =
1320<BR>
&quot;Toute connaissance est une reponse a une question&quot; G.Bachelard
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-ckDi5AV5uNjrdUZextRh--

--=-YrxfrDLeUpzw2tWTfxXb
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQBAJ/UmvnmeYIHZEyARAoA7AJ0QGGY1X0H0MYRAM0pcRhXYTxSkKACfRusR
BZXmHq5lHvszIlcU16n8EMQ=
=lsX7
-----END PGP SIGNATURE-----

--=-YrxfrDLeUpzw2tWTfxXb--



From owner-ietf@ietf.org  Mon Feb  9 20:42:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09505
	for <ietf-archive@odin.ietf.org>; Mon, 9 Feb 2004 20:42:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqM3F-0000Q8-6z
	for ietf-list@asgard.ietf.org; Mon, 09 Feb 2004 19:46:57 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqJJb-0008BE-5W
	for ietf@asgard.ietf.org; Mon, 09 Feb 2004 16:51:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18266
	for <ietf@ietf.org>; Mon, 9 Feb 2004 16:51:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqJJZ-0001Ak-00
	for ietf@ietf.org; Mon, 09 Feb 2004 16:51:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqJIn-00013G-00
	for ietf@ietf.org; Mon, 09 Feb 2004 16:50:50 -0500
Received: from mail15.atl.registeredsite.com ([64.224.219.99] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqJHz-0000uq-00
	for ietf@ietf.org; Mon, 09 Feb 2004 16:49:59 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail15.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i19Lnxqj029223
	for <ietf@ietf.org>; Mon, 9 Feb 2004 16:49:59 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Mon, 09 Feb 2004 15:49:58 -0600
Message-ID: <40280081.3C7F6C1F@nma.com>
Date: Mon, 09 Feb 2004 13:49:53 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: proposal for built-in spam burden & email privacy protection
References: <Pine.LNX.4.44.0402090834220.13314-100000@lilith.rgb.private.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,TARGETED autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Thank you all for your comments so far, public and private. This
reply addresses all the points I received. If I left anything out from
anyone, please point it out to me.

There seems to be some confusion between signed versus encrypted
email, as well as listserver traffic handling. Please note:

1. I did NOT suggest using signed email (and explained why).

2. I suggested using encrypted email, using the recipient's public-key.

3. I EXCLUDED signed email for the first phase (for reasons well-
known to anyone who is following PKI).

4. If you forge the From address, you won't know how to reach me
-- which is desirable.

5. If you sub to a list and that list's traffic is not encrypted to your
key, you simply add the list's address to your whitelist (btw, I mentioned
this also as a backward-compatibility mechanism in general).

6. Spammers trying to misuse a list as a proxy encryptor (in the
case the list encrypts traffic for each member) could be stopped
before the act in the same ways that lists currently fend off spammers.
In case a spammer does get around the defenses, the additional encryption
burden should be enough motivation for the list's administrator to be
more diligent -- it hurts at home. And, IMO, this is fair because the list
is allowing itself to become a spammer's tool, with or without encryption.

    NOTE: the proposal WANTS to penalize spammers. If a list becomes
    a spammers' proxy (willingly or not), it is forwarding spam.

7. Large public lists however, such as ietf-org, should probably NOT be
encrypted per member's public-key (because of high list burden, even though
legitimate). Rather, traffic should be signed with the list's private-key,
allowing anyone to verify that the message has  satisfied the list's
posting and routing policies before being forwarded. This would
also prevent ghost messages that seem to be from the listserver but
are not.

8. How about spammers using 100,000 slave PCs to share the burden?
Even if a spammer could control 100,000 PCs, the spammer would
need to set up EACH PC with public-key encryption software AND
the public-key for each targeted email address. Anyone working in PKI
knows that this is an extremely hard task for anything more than a
handful of hosts -- even with cooperating hosts.

9. But... what if I'm still worried that #8 is possible  just for me? Is
there any recourse using the proposal? Yes -- keep your email address and
change your public-key. An automatic reply saying that your public-key
has changed to value XYZ would be useful to legitimate users and make
life harder for spammers.

10. How about which standard to use? S/MIME, PGP/MIME, etc.?
The ensuing market forces should help, finally, consolidate encryption
standards and promote interoperation. Usage drives standardization and
this is a good thing. Imagine  if, as a comparison, we would need to choose
which protocol to use before visiting a web site? Your browser handles it --
HTTP or FTP, for example, it's all transparent to you.

Comments?

Cheers,
Ed Gerck




From owner-ietf@ietf.org  Mon Feb  9 20:50:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10027
	for <ietf-archive@odin.ietf.org>; Mon, 9 Feb 2004 20:50:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqMiO-0003ci-3k
	for ietf-list@asgard.ietf.org; Mon, 09 Feb 2004 20:29:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqLwg-000855-Qo
	for ietf@asgard.ietf.org; Mon, 09 Feb 2004 19:40:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05895
	for <ietf@ietf.org>; Mon, 9 Feb 2004 19:40:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqLwf-00023G-00
	for ietf@ietf.org; Mon, 09 Feb 2004 19:40:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqLvP-0001oU-00
	for ietf@ietf.org; Mon, 09 Feb 2004 19:38:52 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqLuI-0001Uz-00
	for ietf@ietf.org; Mon, 09 Feb 2004 19:37:43 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1A0b8hE013160
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Mon, 9 Feb 2004 19:37:08 -0500
Date: Mon, 9 Feb 2004 19:37:08 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: ietf@ietf.org
Subject: Re: The IETF Mission
Message-ID: <Pine.LNX.4.44.0402091910320.6922-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by cirrus.av8.net id i1A0b8hE013160
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Ok, here is a revised version with the current feedback.

This is the section from the ANSI Mission statement:

  Due Process. All objections shall have an attempt made towards their=20
  resolution. Interests who believe they have been treated unfairly shall=
=20
  have a right to appeal.

It seems that some mention should be made about due process at the IETF.


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D



The IETF, an activity of the Internet Society, is a technical protocol
standards organization.  Its principal goals are:

=A0=A0=A0=A0=A0=A0=A0 To create open technical standards and identify bes=
t practices
that are useful to and adopted by the world internet communtity and the
public at large.

        To identify current and emerging protocol requirements, and share=
=20
best practices.

        To facliitate the participation of all affected and interested
parties and develop consensus.

        To solicit the input of a diverse group of interests and=20
participants in the formation of protocol standards.

	To provide a fair and open process in the specification and
movement of future standards throughout the standardization process, with
early and equal access to specifications.

        To use a fair and open process in the resolution of disputes so
that any person or organization with a claim of unfair treatment has an
avenue for appeal.

        To work with suppliers, consortia, and other standards bodies to=20
develop consensus and facilitate interoperability.
  =20














From owner-ietf@ietf.org  Mon Feb  9 20:50:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10045
	for <ietf-archive@odin.ietf.org>; Mon, 9 Feb 2004 20:50:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqMer-0002wA-9F
	for ietf-list@asgard.ietf.org; Mon, 09 Feb 2004 20:25:49 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqLKA-000626-8h
	for ietf@asgard.ietf.org; Mon, 09 Feb 2004 19:00:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02327
	for <ietf@ietf.org>; Mon, 9 Feb 2004 19:00:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqLK8-0004Jb-00
	for ietf@ietf.org; Mon, 09 Feb 2004 19:00:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqLJA-0004FB-00
	for ietf@ietf.org; Mon, 09 Feb 2004 18:59:20 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqLIC-00047T-00
	for ietf@ietf.org; Mon, 09 Feb 2004 18:58:20 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i19Nvd74012371
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 9 Feb 2004 18:57:42 -0500
Date: Mon, 9 Feb 2004 18:57:39 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Franck Martin <franck@sopac.org>
cc: John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>, <ietf@ietf.org>
Subject: Re: proposal for built-in spam burden & email privacy protection
In-Reply-To: <1076360297.2823.11.camel@franck-lxnb.sopac.org.fj>
Message-ID: <Pine.LNX.4.44.0402091752420.6922-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On 10 Feb 2004, Franck Martin wrote:
> 
> If he subscribes himself, then we have his e-mail address and then his
> provider and may be an IP and time, so we could track him down in the
> real world and may be sue him...

So instead of using his own email address, the abuser sends a virus to a
bunch of people, and when they get infected, the infected "send" the spam,
and then we just track down an infected user, and disinfect them.  
There's more, see below.

As I've said for some time, most of the junk we are getting is currently
from viruses run by abusers, not from genuine spammers.  Now the
statistics are starting to show this. I just saw some stats on the top 95
real spammers that show that most are complying with the new federal
anti-spam law, and that over half (56%) are fully compliant.  Yet,
checking my own inbox, I find very little spam that is compliant, or even
partially compliant.  Apparently, most of the "spam" doesn't come from
real spammers.

Some might say "so what? it doesn't matter whether the abusers really want
to sell products/services/scams etc".  Actually, it does matter.

When you realign your anti-spam efforts from control of business to
control of techno-terrorists, the problem is quite a bit different, and 
you can see also that things like signing and other things aren't going to 
work.  

Now we have the criminal law tools needed to go after the abusers: That is
road to stopping spam.  You don't need to sue anyone--you need to
prosecute them for criminal violations of the can-spam act, and criminal
violations of the Computer Fraud and Abuse Act (for virus infection).  
Criminal investigations have a much easier time of getting the information
that is needed to identify and prosecute the criminals.

I don't expect that this is going to net spammers.  I expect it will net
anti-spam radicals seeking to annoy people into a ban on spam. Here's why:
A careful review of the history of the spam wars shows that the radicals
have been conducting the abuse from the time of the Internet E-Mail
Marketing Council (IEMMC).

The IEMMC was formed in May of 1997 between Cyberpromotions and AGIS and
some others. Its goal was to encourage voluntary spam labeling and opt-out
lists, and to work out a compromise on spam between the advertising and
technical community.  It truly infuriated anti-spam radicals.

In August 1997, Cyberpromo's web site was hacked, and files and email were
deleted. 

AGIS then came under a large Denial of Service attack, and finally
succumbed and disconnected Cyberpromo and withdrew from the IEMMC, in
September, 1997.  When the IEMMC collapsed the radicals probably thought
their abuse tactics were effective, and were probably encouraged to 
continue their abusive behavior.

One might say this is ancient history, but in fact, the IEMMC position on
spam was practically legislated in the CAN-SPAM act, with the caveat for
criminal violations.  Its also interesting in light of the attacks on
Cyberpromo and AGIS. These attacks are typically associated with groups of
script kiddies.  Vixie has subsequently reported that he is in contact
with the "script-kiddies" and that they are mostly anti-spam. Being
anti-spam is not the same a being anti-mailbombing, which is the
script-kiddie term for their fake spamming.  What the CAN-SPAM act did was
revive the ideas of the IEMMC, and in doing so, it changed genuine spammer
behavior so that genuine spammers can be distinguished from that of the
radicals/abusers.  Now it is just a matter to use the criminal provisions
to track down the abusers, and punish them.

What does this mean?  For one thing, it means that we will be able to use
criminal investigations to identify the abusers. I expect that these are
essentially the same radicals who were attacking cyberpromo with DOS
attacks in 1997; that have been filling email boxes with spam and fake
opt-out links since 1997 in the hope of motivating people to demand the
spam be banned; that have released many viruses that send spam.  But it
will be interesting in any case. Importantly, it will eventually stop the
abuse.

Criminal complaints can also be issued against individuals outside of the
United States with good effect.  It is much more difficult to exercise a
civil suit internationally.

The second thing it means is that you can forget trying to create
technical solutions to spam.  Not only can't such schemes succeed in
preventing techno-terrorism for reasons drawn from information theory as
previously explained, but they are now unnecessary.

		--Dean





From owner-ietf@ietf.org  Mon Feb  9 22:18:03 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13049
	for <ietf-archive@odin.ietf.org>; Mon, 9 Feb 2004 22:18:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqOGV-00020T-Hl
	for ietf-list@asgard.ietf.org; Mon, 09 Feb 2004 22:08:47 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqNr9-0000gm-LK
	for ietf@asgard.ietf.org; Mon, 09 Feb 2004 21:42:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11789
	for <ietf@ietf.org>; Mon, 9 Feb 2004 21:42:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqNr7-0006vp-00
	for ietf@ietf.org; Mon, 09 Feb 2004 21:42:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqNq5-0006q7-00
	for ietf@ietf.org; Mon, 09 Feb 2004 21:41:30 -0500
Received: from mail8.atl.registeredsite.com ([64.224.219.82] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqNpB-0006kk-00
	for ietf@ietf.org; Mon, 09 Feb 2004 21:40:33 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail8.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1A2eSjf006211;
	Mon, 9 Feb 2004 21:40:29 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Mon, 09 Feb 2004 20:40:27 -0600
Message-ID: <40284496.3029B2E9@nma.com>
Date: Mon, 09 Feb 2004 18:40:22 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: Franck Martin <franck@sopac.org>, John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>, ietf@ietf.org
Subject: Re: proposal for built-in spam burden & email privacy protection
References: <Pine.LNX.4.44.0402091752420.6922-100000@cirrus.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Dean Anderson wrote:

> On 10 Feb 2004, Franck Martin wrote:
> ...
> When you realign your anti-spam efforts from control of business to
> control of techno-terrorists, the problem is quite a bit different, and
> you can see also that things like signing and other things aren't going to
> work.

Signing doesn't work because it cannot provide a load per recipient,
just per sender. Encryption with the recipient's public-key (as I am
proposing) works because the spammer must encrypt each message
for each recipient. This applies to lawful spammers as well, finally
adding friction to email by creating a mandatory "fee" (burdenwise) to
send messages.

BTW, my previous posting provided a rationale for proposing the following
requirement for any current or future mail system:

- Users do not want requirements to pay for sending email or to be
otherwise burdened in any way in order to stop spam. Stoping spam
should not be a user's problem.

The above anti-requirement is attainable, fair to all, and cannot be forged.

Cheers,
Ed Gerck




From owner-ietf@ietf.org  Mon Feb  9 22:33:09 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13484
	for <ietf-archive@odin.ietf.org>; Mon, 9 Feb 2004 22:33:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqOZz-00058Q-Cc
	for ietf-list@asgard.ietf.org; Mon, 09 Feb 2004 22:28:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqOVm-0004jt-Ve
	for ietf@asgard.ietf.org; Mon, 09 Feb 2004 22:24:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13325
	for <ietf@ietf.org>; Mon, 9 Feb 2004 22:24:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqOVl-0003HH-00
	for ietf@ietf.org; Mon, 09 Feb 2004 22:24:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqOUl-0003C1-00
	for ietf@ietf.org; Mon, 09 Feb 2004 22:23:32 -0500
Received: from copper.sopac.org.fj ([202.62.0.149] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqOTr-0002wb-00
	for ietf@ietf.org; Mon, 09 Feb 2004 22:22:37 -0500
Received: by franck-lxnb.sopac.org.fj (Postfix, from userid 501)
	id 5A1544B6A2; Mon,  9 Feb 2004 22:21:35 -0500 (EST)
Subject: Re: proposal for built-in spam burden & email privacy protection
From: Franck Martin <franck@sopac.org>
To: Ed Gerck <egerck@nma.com>
Cc: Dean Anderson <dean@av8.com>, John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>, ietf@ietf.org
In-Reply-To: <40284496.3029B2E9@nma.com>
References: <Pine.LNX.4.44.0402091752420.6922-100000@cirrus.av8.net>
	 <40284496.3029B2E9@nma.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-hT87SnbzOrf6/nx/ptWE"
Organization: SOPAC
Message-Id: <1076383295.4347.14.camel@franck-lxnb.sopac.org.fj>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4-1.1mdk 
Date: 10 Feb 2004 15:21:35 +1200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_FONTCOLOR_UNSAFE,
	HTML_MESSAGE autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-hT87SnbzOrf6/nx/ptWE
Content-Type: multipart/alternative; boundary="=-PJQGt6TdSOFUOxpM4dM6"


--=-PJQGt6TdSOFUOxpM4dM6
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2004-02-10 at 14:40, Ed Gerck wrote:

> Dean Anderson wrote:
>=20
> > On 10 Feb 2004, Franck Martin wrote:
> > ...
> > When you realign your anti-spam efforts from control of business to
> > control of techno-terrorists, the problem is quite a bit different, and
> > you can see also that things like signing and other things aren't going=
 to
> > work.
>=20
> Signing doesn't work because it cannot provide a load per recipient,
> just per sender. Encryption with the recipient's public-key (as I am
> proposing) works because the spammer must encrypt each message
> for each recipient. This applies to lawful spammers as well, finally
> adding friction to email by creating a mandatory "fee" (burdenwise) to
> send messages.
>=20

I understand you try to add CPU cycles into sending mail, by obliging
people that send to many recipients to encrypt all e-mails... But I
guess computer power is cheap... However that is an idea worth
developing.

What I suggest is to esig mails to list to ensure traceability would be
spammers or people whose machine has been taken over.  As somoene noted
previously esig just ensure that the e-mail and private key met at some
place. It does not mean a user intervention.

I see however the signing of e-mail, to provide traceability, so people
can be located. Most SPAMMERS (legit or not) will think twice if they
know they can be prosecuted... Think about Caller ID for telephones...

Moreover somebody will set a site of bad digital signature, so your mail
system may reject all e-mails coming from these bad signatures...

----
Franck Martin
franck@sopac.org
SOPAC, Fiji
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9  D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard

--=-PJQGt6TdSOFUOxpM4dM6
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
  <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/1.1.10">
</HEAD>
<BODY>
On Tue, 2004-02-10 at 14:40, Ed Gerck wrote:
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>Dean Anderson wrote:

&gt; On 10 Feb 2004, Franck Martin wrote:
&gt; ...
&gt; When you realign your anti-spam efforts from control of business to
&gt; control of techno-terrorists, the problem is quite a bit different, an=
d
&gt; you can see also that things like signing and other things aren't goin=
g to
&gt; work.

Signing doesn't work because it cannot provide a load per recipient,
just per sender. Encryption with the recipient's public-key (as I am
proposing) works because the spammer must encrypt each message
for each recipient. This applies to lawful spammers as well, finally
adding friction to email by creating a mandatory &quot;fee&quot; (burdenwis=
e) to
send messages.
</I></FONT></PRE>
</BLOCKQUOTE>
<FONT SIZE=3D"3">I understand you try to add CPU cycles into sending mail, =
by obliging people that send to many recipients to encrypt all e-mails... B=
ut I guess computer power is cheap... However that is an idea worth develop=
ing.<BR>
<BR>
What I suggest is to esig mails to list to ensure traceability would be spa=
mmers or people whose machine has been taken over.&nbsp; As somoene noted p=
reviously esig just ensure that the e-mail and private key met at some plac=
e. It does not mean a user intervention.<BR>
<BR>
I see however the signing of e-mail, to provide traceability, so people can=
 be located. Most SPAMMERS (legit or not) will think twice if they know the=
y can be prosecuted... Think about Caller ID for telephones...<BR>
<BR>
Moreover somebody will set a site of bad digital signature, so your mail sy=
stem may reject all e-mails coming from these bad signatures...</FONT>
<PRE><TABLE CELLSPACING=3D"0" CELLPADDING=3D"0" WIDTH=3D"100%">
<TR>
<TD>
----<BR>
Franck Martin<BR>
<A HREF=3D"mailto:franck@sopac.org">franck@sopac.org</A><BR>
SOPAC, Fiji<BR>
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9&nbsp; D9C6 BE79 9E60 81D9 =
1320<BR>
&quot;Toute connaissance est une reponse a une question&quot; G.Bachelard
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-PJQGt6TdSOFUOxpM4dM6--

--=-hT87SnbzOrf6/nx/ptWE
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQBAKE4/vnmeYIHZEyARAsx0AKCBS5Ir3kEFTU8Gn6sg5moL1Y86tQCeO2if
BFwplEz8MMAC5hQDTn/38rs=
=+1Gg
-----END PGP SIGNATURE-----

--=-hT87SnbzOrf6/nx/ptWE--



From owner-ietf@ietf.org  Mon Feb  9 23:00:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14449
	for <ietf-archive@odin.ietf.org>; Mon, 9 Feb 2004 23:00:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqOuA-0008Jb-7q
	for ietf-list@asgard.ietf.org; Mon, 09 Feb 2004 22:49:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqOtt-00082c-Pr
	for ietf@asgard.ietf.org; Mon, 09 Feb 2004 22:49:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14092
	for <ietf@ietf.org>; Mon, 9 Feb 2004 22:49:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqOtr-0005oc-00
	for ietf@ietf.org; Mon, 09 Feb 2004 22:49:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqOst-0005io-00
	for ietf@ietf.org; Mon, 09 Feb 2004 22:48:28 -0500
Received: from mail9.atl.registeredsite.com ([64.224.219.83] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqOry-0005cW-00
	for ietf@ietf.org; Mon, 09 Feb 2004 22:47:30 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail9.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1A4lQV4005111;
	Mon, 9 Feb 2004 23:47:26 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Mon, 09 Feb 2004 21:47:24 -0600
Message-ID: <40285447.A9594222@nma.com>
Date: Mon, 09 Feb 2004 19:47:19 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Franck Martin <franck@sopac.org>
CC: Dean Anderson <dean@av8.com>, John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>, ietf@ietf.org
Subject: Re: proposal for built-in spam burden & email privacy protection
References: <Pine.LNX.4.44.0402091752420.6922-100000@cirrus.av8.net>
		 <40284496.3029B2E9@nma.com> <1076383295.4347.14.camel@franck-lxnb.sopac.org.fj>
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_MESSAGE,
	MIME_HTML_ONLY autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Franck Martin wrote:
<blockquote TYPE=CITE><font size=+0>I see however the signing of e-mail,
to provide traceability, so people can be located.</font></blockquote>
I can locate all the fax spammers that fill my machine with garbage, I
can
<br>call them and ask to be taken out of their lists, and they just keep
on morphing,
<br>where my fax number goes like a ping-pong ball from spammer to spammer.
<br>Is this the "solution" we want for email? Contrary to fax, I can't
disconnect
<br>my email...
<blockquote TYPE=CITE><font size=+0>Most SPAMMERS (legit or not) will think
twice if they know they can be prosecuted... Think about Caller ID for
telephones...</font></blockquote>
Signing email &lt;> Caller ID [1]. Signed email cannot prevent spam and
does not
<br>burden spammers. It may be useful for listservs, however, such as this
one (see
<br>my previous posting with a catch-all reply in this thread).
<p>--------------------
<br>[1]&nbsp; A signed email with a valid (ie, authenticated by you) signature
provides message
<br>and sender authentication as defined by a CA's CPS (which may not be
much -- see
<br>usual warranty and suitability of purpose&nbsp; disclaimers). Caller
ID provides terminal
<br>authentication, irrespective of the message or actual sender (user).
<br>&nbsp;</html>




From owner-ietf@ietf.org  Tue Feb 10 08:15:07 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15511
	for <ietf-archive@odin.ietf.org>; Tue, 10 Feb 2004 08:15:07 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqXXE-00010W-N4
	for ietf-list@asgard.ietf.org; Tue, 10 Feb 2004 08:02:40 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqXWV-00010K-3d
	for ietf@asgard.ietf.org; Tue, 10 Feb 2004 08:01:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14954
	for <ietf@ietf.org>; Tue, 10 Feb 2004 08:01:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqXWU-0003l2-00
	for ietf@ietf.org; Tue, 10 Feb 2004 08:01:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqXVi-0003fk-00
	for ietf@ietf.org; Tue, 10 Feb 2004 08:01:06 -0500
Received: from aharp.ittns.northwestern.edu ([129.105.153.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqXUx-0003VD-00
	for ietf@ietf.org; Tue, 10 Feb 2004 08:00:19 -0500
Received: from eth-0-20-e0-4d-5f-39 (aharp [127.0.0.1])
	by aharp.ittns.northwestern.edu (smtpd) with SMTP id E2FC2136C82
	for <ietf@ietf.org>; Tue, 10 Feb 2004 06:59:48 -0600 (CST)
Date: Tue, 10 Feb 2004 06:59:48 -0600
From: John Kristoff <jtk@northwestern.edu>
To: ietf@ietf.org
Subject: Re: proposal for built-in spam burden & email privacy protection
Message-Id: <20040210065948.4a315511.jtk@northwestern.edu>
In-Reply-To: <40280081.3C7F6C1F@nma.com>
References: <Pine.LNX.4.44.0402090834220.13314-100000@lilith.rgb.private.net>
	<40280081.3C7F6C1F@nma.com>
X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Mon, 09 Feb 2004 13:49:53 -0800
Ed Gerck <egerck@nma.com> wrote:

> 8. How about spammers using 100,000 slave PCs to share the burden?
[...]
> Comments?

Ed,

I'm not sure I see the value in requiring encryption.  To me this does
not seem to really fix anything.

On the one hand, this just forces spammers to  begin collecting public
keys and email addresses as opposed to just addresses.  With the former,
they probably end up with a much more reliable and stable form of contact
since people are not going to want to have throw-away keys, at least not
in the way PGP, for example, is currently used.

On the other hand, this just adds some, but not that much in my opinion
a processing burden for spammers to encrypt messages.  Processing that
can currently be found in compromised hosts (today) or in faster CPUs
(tomorrow).  I think the argument becomes slightly stronger if the delay
is an absolute value that can be enforced per TCP segment, connection
or whatever, but even that is not ideal.

Also note, there is an addition burden placed on end users who rely on
receiving encrypted email in your proposal.  Under your scheme, a user
has to go through the trouble of decrypting the message just to see if
it is spam or not.  This eliminates almost all forms of automated spam
mitigation except those related to the low-level SMTP, DNS or other new
authentication/authorization techniques.

John



From owner-ietf@ietf.org  Tue Feb 10 08:25:19 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16231
	for <ietf-archive@odin.ietf.org>; Tue, 10 Feb 2004 08:25:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqXll-0001Fe-6N
	for ietf-list@asgard.ietf.org; Tue, 10 Feb 2004 08:17:41 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqDVC-0006uk-R9
	for ietf@asgard.ietf.org; Mon, 09 Feb 2004 10:39:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24261
	for <ietf@ietf.org>; Mon, 9 Feb 2004 10:39:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqDVB-0000ya-00
	for ietf@ietf.org; Mon, 09 Feb 2004 10:39:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqDU9-0000te-00
	for ietf@ietf.org; Mon, 09 Feb 2004 10:38:10 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqDTF-0000jZ-00
	for ietf@ietf.org; Mon, 09 Feb 2004 10:37:13 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i19Fiwd13704;
	Mon, 9 Feb 2004 07:44:58 -0800
Date: Mon, 9 Feb 2004 07:36:15 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <967730266.20040209073615@brandenburg.com>
To: Ed Gerck <egerck@nma.com>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: proposal for built-in spam burden & email privacy protection
In-Reply-To: <4026CEC4.35F9115@nma.com>
References: <4026CEC4.35F9115@nma.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ed,

EG> Email privacy and spam are such general problems today that I'd 
EG> like to ask the ietf-org list for feedback (private if you wish)
EG> on this suggestion. There are more specific forums where this 
EG> can (and shall) be discussed.


Indeed there are.  That's why this thread should be moved to the IRTF's
ASRG venue <http://asrg.sp.am/>.

Your proposal is in line with some existing ones, at least one of which
response to the seriously problematic key management issue.


d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>






From owner-ietf@ietf.org  Tue Feb 10 09:28:43 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19711
	for <ietf-archive@odin.ietf.org>; Tue, 10 Feb 2004 09:28:43 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqYim-0007Sm-8f
	for ietf-list@asgard.ietf.org; Tue, 10 Feb 2004 09:18:40 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqYi6-0007RY-FS
	for ietf@asgard.ietf.org; Tue, 10 Feb 2004 09:17:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19262
	for <ietf@ietf.org>; Tue, 10 Feb 2004 09:17:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqYi5-0004GN-00
	for ietf@ietf.org; Tue, 10 Feb 2004 09:17:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqYh9-0004BB-00
	for ietf@ietf.org; Tue, 10 Feb 2004 09:16:59 -0500
Received: from hannibal.servitor.co.uk ([195.188.15.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqYgp-000464-00
	for ietf@ietf.org; Tue, 10 Feb 2004 09:16:40 -0500
Received: from paul by hannibal.servitor.co.uk with local (Exim 4.14)
	id 1AqYgq-000Arv-HS
	for ietf@ietf.org; Tue, 10 Feb 2004 14:16:40 +0000
Date: Tue, 10 Feb 2004 14:16:40 +0000
From: Paul Robinson <paul@iconoplex.co.uk>
To: ietf@ietf.org
Subject: We going? - 5th International Free Software Forum
Message-ID: <20040210141640.GL14319@iconoplex.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi all,

The call for papers for the relatively famous Free Software Forum is up:

http://papers.softwarelivre.org/index.en.html

I was wondering if anybody from the IETF was planning to give a talk? If
not, I was going to propose a couple of sessions myself (in a non-official, 
participatory way of course - I don't propose speaking FOR the IETF so to 
speak):

1. An introduction to the IETF - designed for open source hackers who really
need to understand the processes of WGs and RFC creation better, with an
intention of getting more developers and technologists involved in the
standards processes, as well as the research side of things

2. A round-up of interesting RFCs - most people aren't aware of what RFCs 
have been published in the last 3-4 years, nor what impact they could have 
on them. The intention here is to get open source developers interested in 
turning some of the RFCs that we hoped so much for, into more widely adopted 
protocols. In effect, an "advert" for some work from the WGs.

Thoughts welcome, particularly if the consensus is these talks would be a 
Bad Idea(tm).

-- 
Paul Robinson



From owner-ietf@ietf.org  Tue Feb 10 10:35:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23185
	for <ietf-archive@odin.ietf.org>; Tue, 10 Feb 2004 10:35:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqZkd-0008UW-M2
	for ietf-list@asgard.ietf.org; Tue, 10 Feb 2004 10:24:39 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqZk2-0008UC-Hp
	for ietf@asgard.ietf.org; Tue, 10 Feb 2004 10:24:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22753
	for <ietf@ietf.org>; Tue, 10 Feb 2004 10:24:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqZk1-0002US-00
	for ietf@ietf.org; Tue, 10 Feb 2004 10:24:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqZj7-0002P3-00
	for ietf@ietf.org; Tue, 10 Feb 2004 10:23:06 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqZij-0002Ij-00
	for ietf@ietf.org; Tue, 10 Feb 2004 10:22:41 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id C78F8E0; Tue, 10 Feb 2004 10:20:28 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
To: Ed Gerck <egerck@nma.com>
Subject: Re: proposal for built-in spam burden & email privacy protection
Date: Tue, 10 Feb 2004 10:20:58 -0500
User-Agent: KMail/1.5.2
Cc: ietf@ietf.org
References: <Pine.LNX.4.44.0402091752420.6922-100000@cirrus.av8.net> <40284496.3029B2E9@nma.com>
In-Reply-To: <40284496.3029B2E9@nma.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402101020.58267.spamtrap.ietf@dja.mailme.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Mon February 9 2004 21:40, Ed Gerck wrote:

 > BTW, my previous posting provided a rationale for proposing the
 > following requirement for any current or future mail system:
 >
 > - Users do not want requirements to pay for sending email or to be
 > otherwise burdened in any way in order to stop spam. Stoping spam
 > should not be a user's problem.
 >
 > The above anti-requirement is attainable, fair to all, and cannot be
 > forged.

Unfortunately, requiring that they have a published public-key *is* a 
burden to the average user.  J. Random Luser just wants to sit down at 
his PC, boot up Winders, bring out Lookout, and forward a garish 
HTMLified email full of stale jokes to his buddies, complete with 
pictures, and he wants it to go through, without a hitch, right now.  
He thinks public keys are the ones hanging on the gas station wall, for 
the bathroom.  He thinks crypto is someone from Superman's home planet.  
He thinks the IETF is them guys whut raided David Koresh.  He has no 
clue what the ASRG is, but he thinks it sounds dirty.

Make it worth their while, by coming up with infrastructure such that 
they won't get any spam if they have a public key, and MAYBE they'll 
bother doing it, IF the ISP will hold their hands every step of the way 
(and not charge them too much, including for issuing new keypairs when 
they let the private ones slip out too much).  Of course, this means 
that all their equally technically-enlightened friends have to know how 
to USE his public key....

This sounds very much like the use of extra headerz, or a password on 
the subject line, but on steroids.  In the end, possibly useful, IF you 
can get everybody aboard, but they won't go until everybody ELSE is 
already on board, and meanwhile it's a pain in the proverbial posterior 
to everyone who wants to communicate with the people using it.

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.




From owner-ietf@ietf.org  Tue Feb 10 10:57:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24163
	for <ietf-archive@odin.ietf.org>; Tue, 10 Feb 2004 10:57:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqaCh-0000fD-LG
	for ietf-list@asgard.ietf.org; Tue, 10 Feb 2004 10:53:39 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqaC4-0000ef-PP
	for ietf@asgard.ietf.org; Tue, 10 Feb 2004 10:53:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23942
	for <ietf@ietf.org>; Tue, 10 Feb 2004 10:52:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqaC3-0005GF-00
	for ietf@ietf.org; Tue, 10 Feb 2004 10:52:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqaB4-0005Ak-00
	for ietf@ietf.org; Tue, 10 Feb 2004 10:51:59 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqaAk-00055k-00
	for ietf@ietf.org; Tue, 10 Feb 2004 10:51:38 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id 4D2CC249; Tue, 10 Feb 2004 10:49:31 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
To: Dean Anderson <dean@av8.com>
Subject: Re: proposal for built-in spam burden & email privacy protection
Date: Tue, 10 Feb 2004 10:50:00 -0500
User-Agent: KMail/1.5.2
Cc: <ietf@ietf.org>
References: <Pine.LNX.4.44.0402091752420.6922-100000@cirrus.av8.net>
In-Reply-To: <Pine.LNX.4.44.0402091752420.6922-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402101050.00768.spamtrap.ietf@dja.mailme.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Mon February 9 2004 18:57, Dean Anderson wrote:

 > The IEMMC was formed in May of 1997 between Cyberpromotions and AGIS
 > and some others. Its goal was to encourage voluntary spam labeling
 > and opt-out lists, and to work out a compromise on spam between the
 > advertising and technical community.

...which must necessarily consist of something MUCH better than labeling 
and opt-out, but that was pretty much their limit.  Opt-out is a 
non-starter, so to speak.  It was pretty clear to me that the IEMMC was 
basically a PR ploy, to delay any real action.  IMNSHO, AGIS had no 
intention whatsoever of disconnecting, reining in, imposing conditions 
on, or in any other way not being a haven for spammers, so long as 
being a spamhaven was profitable.

 > One might say this is ancient history, but in fact, the IEMMC
 > position on spam was practically legislated in the CAN-SPAM act,

Yup.  Which means not that SPAM is in the CAN, but that spammers CAN 
SPAM.  They just have to do a few things that the anti-spammers have 
recognized as useless (if not worse) for well over ten years.

Long story short, CAN-SPAM is trying to pull the same wool over the 
public's eyes, that the IEMMC was trying to pull over the anti-spam 
community's.  Unfortunately, John Q. Public can't tell the fine worsted 
wool it's being sold as, from the cheap polyester it really is....

Disclaimer: this doesn't mean that hacking Cyberpromo was "right"!  I'm 
not one of your "radical abusers"....

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.




From owner-ietf@ietf.org  Tue Feb 10 12:42:15 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29631
	for <ietf-archive@odin.ietf.org>; Tue, 10 Feb 2004 12:42:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqblS-0002Ov-Mh
	for ietf-list@asgard.ietf.org; Tue, 10 Feb 2004 12:33:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aqbko-0002Oi-9G
	for ietf@asgard.ietf.org; Tue, 10 Feb 2004 12:32:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28758
	for <ietf@ietf.org>; Tue, 10 Feb 2004 12:32:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aqbkm-0000dg-00
	for ietf@ietf.org; Tue, 10 Feb 2004 12:32:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aqbjp-0000ZB-00
	for ietf@ietf.org; Tue, 10 Feb 2004 12:31:58 -0500
Received: from noxmail.sandelman.ottawa.on.ca ([205.150.200.166])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aqbiy-0000Uq-00
	for ietf@ietf.org; Tue, 10 Feb 2004 12:31:04 -0500
Received: from sandelman.ottawa.on.ca (kremlin.sandelman.ottawa.on.ca [205.150.200.163] (may be forged))
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id i1AHSQw20152
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK);
	Tue, 10 Feb 2004 12:30:55 -0500 (EST)
Received: from sandelman.ottawa.on.ca (marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id i1AHCUss014539
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 10 Feb 2004 13:12:30 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id i1AHCRHP014535;
	Tue, 10 Feb 2004 13:12:30 -0400
To: Paul Robinson <paul@iconoplex.co.uk>
cc: ietf@ietf.org
Subject: Re: We going? - 5th International Free Software Forum 
In-reply-to: Your message of "Tue, 10 Feb 2004 14:16:40 GMT."
             <20040210141640.GL14319@iconoplex.co.uk> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 10 Feb 2004 13:12:27 -0400
Message-ID: <14534.1076433147@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,LINES_OF_YELLING 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Paul" == Paul Robinson <paul@iconoplex.co.uk> writes:
    Paul> The call for papers for the relatively famous Free Software Forum
    Paul> is up:

    Paul> http://papers.softwarelivre.org/index.en.html

    Paul> I was wondering if anybody from the IETF was planning to give a
    Paul> talk? If not, I was going to propose a couple of sessions myself
    Paul> (in a non-official, participatory way of course - I don't propose
    Paul> speaking FOR the IETF so to speak):

  It would be good if someone reviewed how the IETF worked at the conference.
A lot of software developers would benefit from understanding more.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBQCkQ+oqHRg3pndX9AQH1RwP/ZY+E0Gd1UGHomfVDQAjbS7Blffn175Cm
Clsy9WAulO1bwNhZEFz4VA9bfSTY50OK/A82zxSnqtRluYgVeqYleBrnE1EdCBbp
TyvABYibBmAQiyKpYl4HP9hefrXECzDpmDcinGjkVSGiXkfkbCpuRUzt/YnYufxO
oChxV5qruBk=
=4QIz
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Tue Feb 10 14:21:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03929
	for <ietf-archive@odin.ietf.org>; Tue, 10 Feb 2004 14:21:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqdN3-0005fD-5B
	for ietf-list@asgard.ietf.org; Tue, 10 Feb 2004 14:16:33 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqdLh-0005SH-F0
	for ietf@asgard.ietf.org; Tue, 10 Feb 2004 14:15:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03511
	for <ietf@ietf.org>; Tue, 10 Feb 2004 14:15:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqdLc-00045o-00
	for ietf@ietf.org; Tue, 10 Feb 2004 14:15:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqdKf-0003zT-00
	for ietf@ietf.org; Tue, 10 Feb 2004 14:14:06 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqdK5-0003t3-00
	for ietf@ietf.org; Tue, 10 Feb 2004 14:13:29 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1AJCrmP002365
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 10 Feb 2004 14:12:53 -0500
Date: Tue, 10 Feb 2004 14:12:53 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Ed Gerck <egerck@nma.com>
cc: Franck Martin <franck@sopac.org>, John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>, <ietf@ietf.org>
Subject: Re: proposal for built-in spam burden & email privacy protection
In-Reply-To: <40284496.3029B2E9@nma.com>
Message-ID: <Pine.LNX.4.44.0402101046250.6922-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 9 Feb 2004, Ed Gerck wrote:

> 
> Dean Anderson wrote:
> 
> > On 10 Feb 2004, Franck Martin wrote:
> > ...
> > When you realign your anti-spam efforts from control of business to
> > control of techno-terrorists, the problem is quite a bit different, and
> > you can see also that things like signing and other things aren't going to
> > work.
> 
> Signing doesn't work because it cannot provide a load per recipient,
> just per sender. Encryption with the recipient's public-key (as I am
> proposing) works because the spammer must encrypt each message
> for each recipient. This applies to lawful spammers as well, finally
> adding friction to email by creating a mandatory "fee" (burdenwise) to
> send messages.

Then using the IETF list as an example, you would need the entire list of
recipients and their public keys, and you would need to send a message
either directly to each of them, one by one, or send a single message with
a session key for each recipient (thousands).  This isn't going to work.

Second, even if the above weren't a problem, one still has the problem
that a virus infected user will still be sending messages, just like
everyone else. 

You can't make it more expensive without shooting yourself in the foot.  
In information theory-speak, you can't prevent a covert channel** unless
you have no channel at all.  Covert-channel detection is a whack-a-mole
game.  The whack-a-mole characteristic can't be avoided, except by having
no channel at all. Then your problem is to be sure that there really isn't
a channel.  But there often is a channel anyway, and it is just unknown.  
Intelligence agencies go to a great deal of expense to make sure there is
no channel through which information can be leaked.  Our problem is much,
much more difficult because we have a channel, but want to make sure it is
only used for certain purposes.

Putting it in different terms, how can the government make sure those
"government use only" stamped envelopes are only used for government
business?  'Government business' includes interacting with the general
public through mail or email, so eliminating the channel over which
non-government business might be conducted is not an option.  Is is
possible to make a stamp so that the envelope cannot be used for a
non-government purpose?  Now take it one step closer: How can they make
sure that government computers are only used for government business?  
Can a computer be built that can only be used for government business?

There is no scheme in which the rules can't be broken by someone intent on
breaking them.  The only path is to detect them, and prosecute them.  In
the case of spam, detection is easy, but not automatic.  Prosecution is
now possible.  Its still a whack-a-mole game. It won't end unless you can
get past the virus infection to the virus operator, and hopefully, there
aren't really too many virus operators.  Of course, we aren't stopping
spam either in a very real sense, but rather abusers who are annoying and
mailbombing people.  But by my count of my inbox, if you stop those
people, I can certainly handle the rest which amounts to maybe 1% of my
current junk mail.

> BTW, my previous posting provided a rationale for proposing the following
> requirement for any current or future mail system:
> 
> - Users do not want requirements to pay for sending email or to be
> otherwise burdened in any way in order to stop spam. Stoping spam
> should not be a user's problem.

The "for pay" idea is just another scam from the people who would love to
get a percentage of the pay. While I'm sure Microsoft and others would
just love to get a cut of this (I know I would), it doesn't do anything to
stop spam, and if implemented, would simply (and wrongly) charge users
whose computers were virus infected.  I doubt that it would be widely
implmented, anyway.  It would also be the end of free services like
hotmail and yahoo, though I'm certain MS would give up hotmail in a hot
second for a cut of probably billions or trillions per year in email fees.
Though, perhaps one could bring a fraud or rackateering case against
Microsoft for profiting from its insecure computers, but I'm doubtful of
that.

		--Dean

** covert channel, sneaky channel, whatever your term--'covert channel' is
a term favored by OS scientists in analysis of Operating Systems--the
information theory part of it is generally applicable, and the concept has
been researched in different fields and applications using slightly
different names.





From owner-ietf@ietf.org  Tue Feb 10 14:44:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04922
	for <ietf-archive@odin.ietf.org>; Tue, 10 Feb 2004 14:44:29 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqdgT-0006QW-Oc
	for ietf-list@asgard.ietf.org; Tue, 10 Feb 2004 14:36:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aqdfw-0006Q7-1i
	for ietf@asgard.ietf.org; Tue, 10 Feb 2004 14:36:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04708
	for <ietf@ietf.org>; Tue, 10 Feb 2004 14:36:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aqdfu-0006Ob-00
	for ietf@ietf.org; Tue, 10 Feb 2004 14:36:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aqdew-0006Jn-00
	for ietf@ietf.org; Tue, 10 Feb 2004 14:35:03 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqdeW-0006Ex-00
	for ietf@ietf.org; Tue, 10 Feb 2004 14:34:36 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id 819BC11E; Tue, 10 Feb 2004 14:32:27 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
To: Dean Anderson <dean@av8.com>
Subject: Re: proposal for built-in spam burden & email privacy protection
Date: Tue, 10 Feb 2004 14:32:57 -0500
User-Agent: KMail/1.5.2
Cc: <ietf@ietf.org>
References: <Pine.LNX.4.44.0402101046250.6922-100000@cirrus.av8.net>
In-Reply-To: <Pine.LNX.4.44.0402101046250.6922-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402101432.57379.spamtrap.ietf@dja.mailme.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Tue February 10 2004 14:12, Dean Anderson wrote:

 > The "for pay" idea is just another scam from the people who would
 > love to get a percentage of the pay. While I'm sure Microsoft and
 > others would just love to get a cut of this (I know I would), it
 > doesn't do anything to stop spam, and if implemented, would simply
 > (and wrongly) charge users whose computers were virus infected.

Wrongly?  I'm not so sure.  Something ought to be done to stop the 
Typhoid Marys of the Internet.  Putting them on notice that they WILL 
be held responsible for spreading the infection, or its effects, just 
MIGHT result in them FINALLY taking some responsibility for their 
"computer hygiene".  Sure, there will have to be several well 
publicized example cases before most folk will sit up and take notice, 
but in the long run, it might be effective.

Not that it would be worth all the assorted other hassles associated 
with the protocol changes, collecting and disbursing the money (with a 
cut off the top for the collectors/disbursers, of course), etc.  B-(

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.




From owner-ietf@ietf.org  Tue Feb 10 14:56:24 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05528
	for <ietf-archive@odin.ietf.org>; Tue, 10 Feb 2004 14:56:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aqdv0-0006xF-NR
	for ietf-list@asgard.ietf.org; Tue, 10 Feb 2004 14:51:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aqdtg-0006tv-NX
	for ietf@asgard.ietf.org; Tue, 10 Feb 2004 14:50:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05303
	for <ietf@ietf.org>; Tue, 10 Feb 2004 14:50:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aqdtf-00002o-00
	for ietf@ietf.org; Tue, 10 Feb 2004 14:50:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aqdsr-0007jq-00
	for ietf@ietf.org; Tue, 10 Feb 2004 14:49:26 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[JPOQYsZRtpNaqdgN5PGf1Ar9NfrwrlDd])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqdsC-0007bs-00
	for ietf@ietf.org; Tue, 10 Feb 2004 14:48:44 -0500
Received: from ganesh.phy.duke.edu (ganesh.phy.duke.edu [152.3.182.51])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id 3E7EEA78B6; Tue, 10 Feb 2004 14:48:42 -0500 (EST)
Received: by ganesh.phy.duke.edu (Postfix, from userid 1337)
	id 90FA536DBC; Tue, 10 Feb 2004 14:48:27 -0500 (EST)
Date: Tue, 10 Feb 2004 14:48:27 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
To: Dean Anderson <dean@av8.com>
Cc: Ed Gerck <egerck@nma.com>, Franck Martin <franck@sopac.org>,
        John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>, <ietf@ietf.org>
Subject: Re: proposal for built-in spam burden & email privacy protection
In-Reply-To: <Pine.LNX.4.44.0402101046250.6922-100000@cirrus.av8.net>
Message-ID: <Pine.LNX.4.44.0402101428490.11754-100000@ganesh.phy.duke.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 10 Feb 2004, Dean Anderson wrote:

> There is no scheme in which the rules can't be broken by someone intent on
> breaking them.  The only path is to detect them, and prosecute them.  In
> the case of spam, detection is easy, but not automatic.  Prosecution is
> now possible.  Its still a whack-a-mole game. It won't end unless you can

Hear, hear.  Beautifully said (and I'll have to remember the
whack-a-mole metaphor;-).  There are also lovely biological metaphors --
how long has it taken spamsters to develop "stealth spam" that sneaks
past the rulesets of many filters, often by exploiting very specific
features of those filters such as word count mechanisms?  Viruses (close
kin to spam) are constantly reengineered with better and badder social
engineering, with variable signatures.  Just like real viruses and
pond-scum bacteria, they are changed to be successful in the environment
they operate in as that environment changes to try to eliminate them.
And don't forget, a fraction (possibly large) of spam originates
overseas in countries where they laugh hysterically at the concept of
regulation and prosecution will effectively never work.

So even discussing adding a silly thing like mandatory esigs and
encryption as an antispam measure is a waste of time, except possibly on
a local basis.  If I set up a small mailing list (or generalized group
of individuals) and all of its members agree to do this, there is little
"evolutionary pressure" for spammers to detect and foil our scheme and
we will be "immune" (at the cost of a fair amount of extra work).  If
everybody does it and the automated tools for doing it without so much
work are widely disbursed, they will develop countermeasures in no time
at all and we'll lose our immunity.

It also isn't clear that this is an IETF issue (although I'm fairly new
on the list and could be mistaken:-).  Trying to establish a new mail
standard such that all mail is encrypted in transit -- that seems like a
reasonable issue, spammers or not.  Trying to use its influence to
communicate to e.g. AV companies that bouncing messages to the apparent
source of a virus has long since become counterproductive, that also
seems like a reasonable issue -- both are technical/engineering issues
that affect the quality of service of the internet itself.

The spam problem, like the phone problem, seems more likely to be
resolved by strong legislation and vigorous prosecution.  It is less a
technical problem than a social one and an economic one.

   rgb

Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu







From owner-ietf@ietf.org  Tue Feb 10 20:58:24 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11990
	for <ietf-archive@odin.ietf.org>; Tue, 10 Feb 2004 20:58:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aqhkx-0002WI-Vy
	for ietf-list@asgard.ietf.org; Tue, 10 Feb 2004 18:57:31 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqfqP-00082y-EP
	for ietf@asgard.ietf.org; Tue, 10 Feb 2004 16:55:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21866
	for <ietf@ietf.org>; Tue, 10 Feb 2004 16:54:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqfqO-0002od-00
	for ietf@ietf.org; Tue, 10 Feb 2004 16:55:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aqfov-0002Vy-00
	for ietf@ietf.org; Tue, 10 Feb 2004 16:53:29 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aqfnp-0002AD-00
	for ietf@ietf.org; Tue, 10 Feb 2004 16:52:21 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id A9F6861F4E
	for <ietf@ietf.org>; Tue, 10 Feb 2004 22:51:49 +0100 (CET)
Date: Tue, 10 Feb 2004 13:43:15 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Continuing the story - another stab at an IETF mission statement
Message-ID: <21987296.1076420595@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Apologies to those who are already tired of this debate, and those think 
that we have enough of a clear idea of what the IETF mission is, and that 
discussing more is harmful to the community, but....

I attempted to incorporate the latest discussions into an internet-draft, 
which I managed to get out just before the deadline....

   draft-alvestrand-ietf-mission-00.txt

The core of the draft:


   The goal of the IETF is to make the Internet work.

   The mission of the IETF is to produce high quality, relevant
   technical and engineering documents that influence the way people
   design, use and manage the Internet in such a way as to make the
   Internet work better.
   These documents include protocol standards, best current practices
   and informational documents of various kinds.

   The IETF will pursue this mission in adherence to the following
   cardinal principles:

   Open process - that any interested participant can in fact
      participate in the work, know what is being decided, and make his
      or her voice heard on the issue.  Part of this principle is our
      commitment to making our documents, our WG mailing lists, our
      attendance lists and our meeting minutes publicly available on the
      Net.

   Technical competence - that the issues on which the IETF produces its
      documents are issues where the IETF has the competence needed to
      speak to them, and that the IETF is willing to listen to
      technically competent input from any source.
      Technical competence also means that we expect IETF output to be
      designed to sound network engineering principles - this is also
      often referred to as "engineering quality".

   Volunteer Core - that our members and our leadership are people who
      come to the IETF because they want to work for the IETF's
      purposes.

   Rough consensus and running code - We make standards based on the
      combined engineering judgement of our participants and our real-
      world experience in implementing and deploying our specifications.


The rest of the document is trying to define the terms and explain the 
issues faced in formulating the mission statement.
An appendix (to be deleted before publication) lists some other attempts at 
formulating a mission statement - the purpose of including this is to give 
honor to those who worked on them, and to allow those who debate the issue 
to see what other attempts to formulate the mission could look like.

Comments are welcome, of course!

                      Harald




From owner-ietf@ietf.org  Wed Feb 11 00:11:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18474
	for <ietf-archive@odin.ietf.org>; Wed, 11 Feb 2004 00:11:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AqmTJ-0008FJ-36
	for ietf-list@asgard.ietf.org; Tue, 10 Feb 2004 23:59:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqmT8-0008Bj-Pe
	for ietf@asgard.ietf.org; Tue, 10 Feb 2004 23:59:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17404
	for <ietf@ietf.org>; Tue, 10 Feb 2004 23:59:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqmT6-0000Qk-00
	for ietf@ietf.org; Tue, 10 Feb 2004 23:59:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqmS7-0000IP-00
	for ietf@ietf.org; Tue, 10 Feb 2004 23:58:23 -0500
Received: from mail-red.research.att.com ([192.20.225.110] helo=mail-white.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqmR7-00007C-00
	for ietf@ietf.org; Tue, 10 Feb 2004 23:57:21 -0500
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by mail-white.research.att.com (Postfix) with ESMTP id EE3FE664057;
	Tue, 10 Feb 2004 23:55:42 -0500 (EST)
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-green.research.att.com (Postfix) with ESMTP id EE59DF3B48;
	Tue, 10 Feb 2004 23:53:27 -0500 (EST)
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 i1B4uoZ20735;
	Tue, 10 Feb 2004 23:56:50 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id 7311C7B43; Tue, 10 Feb 2004 17:51:52 -0500 (EST)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Cc: Paul Robinson <paul@iconoplex.co.uk>, ietf@ietf.org
Subject: Re: We going? - 5th International Free Software Forum 
In-Reply-To: Your message of "Tue, 10 Feb 2004 13:12:27 -0400."
             <14534.1076433147@marajade.sandelman.ottawa.on.ca> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Feb 2004 17:51:52 -0500
Message-Id: <20040210225152.7311C7B43@berkshire.research.att.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,DATE_IN_PAST_06_12 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <14534.1076433147@marajade.sandelman.ottawa.on.ca>, Michael Richards
on writes:
>-----BEGIN PGP SIGNED MESSAGE-----
>
>
>>>>>> "Paul" == Paul Robinson <paul@iconoplex.co.uk> writes:
>    Paul> The call for papers for the relatively famous Free Software Forum
>    Paul> is up:
>
>    Paul> http://papers.softwarelivre.org/index.en.html
>
>    Paul> I was wondering if anybody from the IETF was planning to give a
>    Paul> talk? If not, I was going to propose a couple of sessions myself
>    Paul> (in a non-official, participatory way of course - I don't propose
>    Paul> speaking FOR the IETF so to speak):
>
>  It would be good if someone reviewed how the IETF worked at the conference.
>A lot of software developers would benefit from understanding more.

I gave a talk like that at Usenix a few years ago -- feel free to point 
folks at the talks/ietf-usenix/ietf-usenix.htm file on my Web page.

Note, of course, that many -- most? -- free software advocates do not 
like the IETF's policies on patents in its protocols.  But that's a 
separate can of worms; let's *not* debate that again now...


		--Steve Bellovin, http://www.research.att.com/~smb





From owner-ietf@ietf.org  Wed Feb 11 15:47:53 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21681
	for <ietf-archive@odin.ietf.org>; Wed, 11 Feb 2004 15:47:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ar0z9-0006AI-1k
	for ietf-list@asgard.ietf.org; Wed, 11 Feb 2004 15:29:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AqcZH-00036a-38
	for ietf@asgard.ietf.org; Tue, 10 Feb 2004 13:25:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01151
	for <ietf@ietf.org>; Tue, 10 Feb 2004 13:25:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqcZD-0006R4-00
	for ietf@ietf.org; Tue, 10 Feb 2004 13:25:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqcYO-0006LL-00
	for ietf@ietf.org; Tue, 10 Feb 2004 13:24:12 -0500
Received: from smtp2.webcontrolcenter.com ([216.119.106.214])
	by ietf-mx with smtp (Exim 4.12)
	id 1AqcY2-0006FI-00
	for ietf@ietf.org; Tue, 10 Feb 2004 13:23:50 -0500
Received: (qmail 5790 invoked from network); 10 Feb 2004 18:19:02 -0000
Received: from mail2.webcontrolcenter.com (216.119.106.25)
  by smtp2.crystaltech.com with SMTP; 10 Feb 2004 18:19:02 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset=iso-8859-1
Date: Tue, 10 Feb 2004 11:21:09 -0700
Subject: Re: proposal for built-in spam burden & email privacy protection
From: "David Berman" <dberman@sen.us>
Reply-To: dberman@sen.us
To: <spamtrap.ietf@dja.mailme.org>, <dean@av8.com>
CC: <ietf@ietf.org>
Message-Id: <E1AqcY2-0006FI-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Subject lines for emails should be required to have only words that can be found in the dictionary.  This eliminates any spam like vi@gr@ or m0rtgage.  

The real problem isn't from companies who send bulk email and allow you to opt out.  The problem comes from people that are trying not to let you opt out.  Not only don't they let you opt out, but they also try to get around your filters.



Original Message:
>From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
>To: Dean Anderson <dean@av8.com>
>Subject: Re: proposal for built-in spam burden & email privacy protection
>Date: Tue, 10 Feb 2004 10:50:00 -0500

>On Mon February 9 2004 18:57, Dean Anderson wrote:
>
> > The IEMMC was formed in May of 1997 between Cyberpromotions and AGIS
> > and some others. Its goal was to encourage voluntary spam labeling
> > and opt-out lists, and to work out a compromise on spam between the
> > advertising and technical community.
>
>...which must necessarily consist of something MUCH better than labeling 
>and opt-out, but that was pretty much their limit.  Opt-out is a 
>non-starter, so to speak.  It was pretty clear to me that the IEMMC was 
>basically a PR ploy, to delay any real action.  IMNSHO, AGIS had no 
>intention whatsoever of disconnecting, reining in, imposing conditions 
>on, or in any other way not being a haven for spammers, so long as 
>being a spamhaven was profitable.
>
> > One might say this is ancient history, but in fact, the IEMMC
> > position on spam was practically legislated in the CAN-SPAM act,
>
>Yup.  Which means not that SPAM is in the CAN, but that spammers CAN 
>SPAM.  They just have to do a few things that the anti-spammers have 
>recognized as useless (if not worse) for well over ten years.
>
>Long story short, CAN-SPAM is trying to pull the same wool over the 
>public's eyes, that the IEMMC was trying to pull over the anti-spam 
>community's.  Unfortunately, John Q. Public can't tell the fine worsted 
>wool it's being sold as, from the cheap polyester it really is....
>
>Disclaimer: this doesn't mean that hacking Cyberpromo was "right"!  I'm 
>not one of your "radical abusers"....
>
>-- 
>Dave Aronson, Senior Software Engineer, Secure Software Inc.
>Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
>(Opinions above NOT those of securesw.com unless so stated!)
>WE'RE HIRING developers, auditors, and VP of Prof. Services.
>
>
>
>







From owner-ietf@ietf.org  Wed Feb 11 19:30:09 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13626
	for <ietf-archive@odin.ietf.org>; Wed, 11 Feb 2004 19:30:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ar3k8-0004xs-AC
	for ietf-list@asgard.ietf.org; Wed, 11 Feb 2004 18:26:08 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ar2LL-0005qh-Vf
	for ietf@asgard.ietf.org; Wed, 11 Feb 2004 16:56:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00574
	for <ietf@ietf.org>; Wed, 11 Feb 2004 16:56:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar2LJ-0006ch-00
	for ietf@ietf.org; Wed, 11 Feb 2004 16:56:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ar2KH-0006Ov-00
	for ietf@ietf.org; Wed, 11 Feb 2004 16:55:22 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar2J4-000626-00
	for ietf@ietf.org; Wed, 11 Feb 2004 16:54:06 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1BLrQg6000994
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 11 Feb 2004 16:53:27 -0500
Date: Wed, 11 Feb 2004 16:53:26 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: David Berman <dberman@sen.us>
cc: spamtrap.ietf@dja.mailme.org, <ietf@ietf.org>
Subject: Re: proposal for built-in spam burden & email privacy protection
In-Reply-To: <E1AqcY2-0006FI-00@ietf-mx>
Message-ID: <Pine.LNX.4.44.0402111626560.32203-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

What does spamtrap.ietf@dja.mailme.org mean?  It is a spamtrap that should 
be removed?   Or is it simply the address they use to figure out of the 
ietf list is being culled for spam?

More inline.

On Tue, 10 Feb 2004, David Berman wrote:

> Subject lines for emails should be required to have only words that can
> be found in the dictionary.  This eliminates any spam like vi@gr@ or
> m0rtgage.

And what dictionary would that be?  Italian? French? English? The 60-100
other languages?  In what character set?  What about slang?  What about
abbreviations?  What about made up code words like those names that lovers
create for for each other, like "Hi, Nookums"?  The list goes on, and can
get sillier.  What about word tenses?  Mispeling?  Regional dialects?  
Medical terms, new words like "bling-bling". etc.  Simple dictionary
analysis is hard, and while it might be one clue, it isn't something that
can simply be required.

I don't mean to say that text analysis should be ignored, just the
contrary, in fact.  I think there is useful work in the direction of text
summarization, and agents that summarize and identify what you might be
interested in. I think there is also useful work in identifying things
that you are not interested in, as well as other factors like bulkiness,
etc.

Automated text analysis will never be perfect, because even human text
analysis for interest/disinterest (secretaries) aren't perfect.  But it
can help sort things.  I hand filter about 1500 messages a day.  I get 
about 3500 over the weekend. Monday's filtering doesn't take me any longer 
than tuesdays filtering.  

> The real problem isn't from companies who send bulk email and allow you
> to opt out.  The problem comes from people that are trying not to let
> you opt out.  Not only don't they let you opt out, but they also try to
> get around your filters.

I agree. 


		--Dean




From owner-ietf@ietf.org  Wed Feb 11 20:01:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15866
	for <ietf-archive@odin.ietf.org>; Wed, 11 Feb 2004 20:01:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ar58a-0006mj-3a
	for ietf-list@asgard.ietf.org; Wed, 11 Feb 2004 19:55:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ar50E-0005cg-H8
	for ietf@asgard.ietf.org; Wed, 11 Feb 2004 19:46:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15124
	for <ietf@ietf.org>; Wed, 11 Feb 2004 19:46:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar50C-00071b-00
	for ietf@ietf.org; Wed, 11 Feb 2004 19:46:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ar4zM-0006v5-00
	for ietf@ietf.org; Wed, 11 Feb 2004 19:45:56 -0500
Received: from heron.mail.pas.earthlink.net ([207.217.120.189])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar4yP-0006oH-00
	for ietf@ietf.org; Wed, 11 Feb 2004 19:44:58 -0500
Received: from [38.119.96.105] (helo=[192.168.0.2])
	by heron.mail.pas.earthlink.net with asmtp (Exim 3.33 #1)
	id 1Ar4yL-0006Jy-00
	for ietf@ietf.org; Wed, 11 Feb 2004 16:44:58 -0800
Date: Wed, 11 Feb 2004 19:43:37 -0500
From: Gene Gaines <gene.gaines@gainesgroup.com>
Organization: Gaines Group
X-Priority: 3 (Normal)
Message-ID: <5823517627.20040211194337@gainesgroup.com>
To: ietf@ietf.org
Subject: Visa for Korea
In-Reply-To: <14092012869.20040202193819@gainesgroup.com>
References: <Pine.LNX.4.44.0401291058450.8971-100000@jackson.cs.ucsb.edu>
 <2226201457.20040129150137@gainesgroup.com>
 <14092012869.20040202193819@gainesgroup.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: e892362a6fa8b5d372cc1e1b0924a179239a348a220c2609005c607aa60ff744f56e5457e0850b89667c3043c0873f7e350badd9bab72f9c350badd9bab72f9c
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

As promised.

The Korean consulate in DC has produced two letters
for U.S. citizens to carry with them to the IETF
Seoul meeting.

The letters state that U.S. citizens carrying a valid
passport traveling to Korea to attend the IETF meeting
and/or tourism for up to 30 days DO NOT NEED A VISA.

The letters have been confirmed with the responsible
minitries in Korea, and copies sent immigration at
Incheon airport, the usual point of entry for Seoul.

I have made graphic files and sent them on to the
IETF Secretariat people to post to the web.  Give
them a couple of days to review and get them up.

Print and take with you.  Show if border officials
ask for them.

Gene Gaines
gene.gaines@gainesgroup.com
Sterling, Virginia USA






From owner-ietf@ietf.org  Wed Feb 11 20:18:17 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13643
	for <ietf-archive@odin.ietf.org>; Wed, 11 Feb 2004 19:30:12 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ar3k8-0004yE-NH
	for ietf-list@asgard.ietf.org; Wed, 11 Feb 2004 18:26:08 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ar2Lm-0005uJ-QH
	for ietf@asgard.ietf.org; Wed, 11 Feb 2004 16:56:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00667
	for <ietf@ietf.org>; Wed, 11 Feb 2004 16:56:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar2Ll-0006kW-00
	for ietf@ietf.org; Wed, 11 Feb 2004 16:56:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ar2L3-0006aL-00
	for ietf@ietf.org; Wed, 11 Feb 2004 16:56:09 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[7vQwgFJ+02APC+x9KvIEHY+WAMeyTdFJ])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar2K2-0006MM-00
	for ietf@ietf.org; Wed, 11 Feb 2004 16:55:06 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id 090BEA7B13; Wed, 11 Feb 2004 16:55:00 -0500 (EST)
Date: Wed, 11 Feb 2004 16:19:42 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: David Berman <dberman@sen.us>
Cc: spamtrap.ietf@dja.mailme.org, <dean@av8.com>, <ietf@ietf.org>
Subject: Re: proposal for built-in spam burden & email privacy protection
In-Reply-To: <E1AqcY2-0006FI-00@ietf-mx>
Message-ID: <Pine.LNX.4.44.0402111550320.1290-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 10 Feb 2004, David Berman wrote:

> Subject lines for emails should be required to have only words that
> can be found in the dictionary.  This eliminates any spam like vi@gr@ or
> m0rtgage.

This is not a sane idea.  It also eliminates a stupendous volume of
legitimate mail.  Can I no longer send email with a subject line such as
"node b10 down"?  How about "Joe's email address is
jpg@imaginary.domain.edu"?  

And then there are foreign languages.  WHICH dictionary?  How many
dictionaries?

And what about spam that comes with no subject line?  Spam that comes
with a innocuous subject line that has nothing to do with the message
content?  Remember, the spammer will simply alter their message again to
penetrate any defenses you raise against it until you've closed down an
entire channel to legitimate traffic.

What about email between administrators and users ABOUT spam?  "What do
I do about vi@gr@ emails?" seems like a legitimate subject line.

What about bad spelers?  Or tpyos?

This is not an acceptable protocol-level solution for stealth spam.  Nor
are variants such as passing the words found through a crack-like
substition tree looking for 1337 phrases, as people might use those
substitutions for legitimate reasons, or arbitrary regular expression
rulesets as to what is non-spam.  These are, however, perfectly fine
anti-spam countermeasures in user-level tools such as spamassasin and
procmail, where you can control it yourself and choose (at your own
risk) just how much legitimate mail you are willing to risk blocking in
order to reduce spam.

The information-theoretic observations already made about signal
channels and filters are entirely apropos here.  The more tightly you
control the noise, the more the signal itself degrades.

> The real problem isn't from companies who send bulk email and allow
> you to opt out.  The problem comes from people that are trying not to
> let you opt out.  Not only don't they let you opt out, but they also try
> to get around your filters.

This statement is like saying "The real problem isn't the people who
knock on your door to sell you something and go away when you open it to
say no, it is the people who knock on your door to sell you something
and when you open it come in and take your wallet, drink all your beer,
and shoot your dog."

At a very crude guess, over 50% of all spam that has an opt out uses the
opt out only to verify that they've found a live email address with a
human at the other end who reads the messages.  This is a valuable
commodity and can be (and is) repeatedly resold.  Opting out is
therefore much like opening the door to strangers when over half of them
are likely to take your beer and shoot your dog.  I opt out only when
the opt out is the URL for a well-known company, the mail header is
well-formed, and there is a decent chance that they are going to be
semi-accountable to an internet acceptable use policy in the first
place.  Presuming that their SPAM made it through spamassasin and
procmail, that is.

In bad neighborhoods where the streets are rough and folks are on make,
the only solution is lots of police and punishments that make evil
behavior a poor risk for the bad guys.  The internet makes every bad
neighborhood in the world hyperdimensionally outside your front door.
To mutilate a metaphor...:-)

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Wed Feb 11 22:49:56 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21861
	for <ietf-archive@odin.ietf.org>; Wed, 11 Feb 2004 22:49:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ar7aS-0006bS-E9
	for ietf-list@asgard.ietf.org; Wed, 11 Feb 2004 22:32:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ar7XB-0006Ro-3d
	for ietf@asgard.ietf.org; Wed, 11 Feb 2004 22:29:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21080
	for <ietf@ietf.org>; Wed, 11 Feb 2004 22:28:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar7X9-0000Gl-00
	for ietf@ietf.org; Wed, 11 Feb 2004 22:28:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ar7WE-0000AM-00
	for ietf@ietf.org; Wed, 11 Feb 2004 22:28:03 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar7Vb-00001r-00; Wed, 11 Feb 2004 22:27:23 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 01058621FF; Thu, 12 Feb 2004 04:26:52 +0100 (CET)
Date: Wed, 11 Feb 2004 18:48:22 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Sam Hartman <hartmans@mit.edu>, The IESG <iesg@ietf.org>
Cc: ietf@ietf.org
Subject: Re: [secdir] [New-work] WG Review: New IETF Standards Track
 (newtrk)
Message-ID: <126692604.1076525302@localhost>
In-Reply-To: <tslznbphz44.fsf@konishi-polis.mit.edu>
References: <200402111848.NAA13315@ietf.org>
 <tslznbphz44.fsf@konishi-polis.mit.edu>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 11. februar 2004 20:20 -0500 Sam Hartman <hartmans@mit.edu> wrote:

>
> One item in the proposed charter concerns me greatly:
>
>
>   The working group should also take into account other issues raised by
> the   problem working group and during the newtrk BOF as needed.
>
> That does not sound narrowly scoped at all.  It might be reasonable to
> take into account these items as they relate to the explicitly
> enumerated goals of the working group, but it does not seem reasonable
> to take into account issues that would create a new goal or expand the
> scope of the working group.

It was not intended as a scope-widening tool. But it would be wrong to 
ignore them.

Thanks for reading!






From owner-ietf@ietf.org  Wed Feb 11 22:54:43 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22174
	for <ietf-archive@odin.ietf.org>; Wed, 11 Feb 2004 22:54:43 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ar7rr-000766-G1
	for ietf-list@asgard.ietf.org; Wed, 11 Feb 2004 22:50:23 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ar7rN-00070E-Ux
	for ietf@asgard.ietf.org; Wed, 11 Feb 2004 22:49:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21857
	for <ietf@ietf.org>; Wed, 11 Feb 2004 22:49:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar7rL-0002UO-00
	for ietf@ietf.org; Wed, 11 Feb 2004 22:49:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ar7qT-0002Mv-00
	for ietf@ietf.org; Wed, 11 Feb 2004 22:48:58 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar7pi-00029D-00
	for ietf@ietf.org; Wed, 11 Feb 2004 22:48:11 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1C3leHV007818
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Wed, 11 Feb 2004 22:47:40 -0500
Date: Wed, 11 Feb 2004 22:47:40 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: ietf@ietf.org
Subject: Re: proposal for built-in spam burden & email privacy protection
Message-ID: <Pine.LNX.4.44.0402112235390.32203-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0402112235392.32203@cirrus.av8.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Here is an example of a grossly mistaken anti-spam measure:  My emails
have contained no "irregular formatting", whatever that means. Usually
formatting checks look for html formatted text with lots of centered text.  
My messages contained none of that.  But it also contained nothing 
irregular, that wouldn't be found in a typical message.

The message below shows that you have to be very, very careful and not
make false assumptions about the content of messages when making anti-spam
checks.  The poor unfortunate user probably has no idea that his email is
being interfered with by his/her IT department.

Luckily, the IETF list is content-free, and so the user missed nothing of
value ;-) ;-)

		--Dean

---------- Forwarded message ----------
Date: Wed, 11 Feb 2004 19:24:37 -0500
From: mailscreen@itcdeltacom.com
To: dean@av8.com
Subject: Email quarantined

The following message has not been delivered:

   Message: BA000ba224.00000001.mml
   From:    dean@av8.com
   To:      dbotham@edeltacom.com
   Subject: Re: proposal for built-in spam burden & email privacy protection

This is due to automatic rules that have determined that the 
message contains irregular formatting that is often used by
spammers.

If this is a legitimate business related email that you believe 
has been blocked in error, you may contact the intended recipient 
and have them notify the ITS Help Desk.

This message will be retained for ten days.


Please do not reply to this message.




From owner-ietf@ietf.org  Thu Feb 12 03:38:26 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14273
	for <ietf-archive@odin.ietf.org>; Thu, 12 Feb 2004 03:38:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArCAw-0003QQ-1l
	for ietf-list@asgard.ietf.org; Thu, 12 Feb 2004 03:26:22 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ArCAh-0003PT-Kj
	for ietf@asgard.ietf.org; Thu, 12 Feb 2004 03:26:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14045
	for <ietf@ietf.org>; Thu, 12 Feb 2004 03:26:03 -0500 (EST)
From: Rod.Walsh@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArCAc-00060Y-00
	for ietf@ietf.org; Thu, 12 Feb 2004 03:26:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArC9i-0005uY-00
	for ietf@ietf.org; Thu, 12 Feb 2004 03:25:07 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArC98-0005oz-00
	for ietf@ietf.org; Thu, 12 Feb 2004 03:24:31 -0500
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1C8ONv21363
	for <ietf@ietf.org>; Thu, 12 Feb 2004 10:24:27 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T67b5a95d3fac158f23077@esvir03nok.nokia.com>;
 Thu, 12 Feb 2004 10:23:27 +0200
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Thu, 12 Feb 2004 10:23:29 +0200
Received: from esebe007.NOE.Nokia.com ([172.21.138.47]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Thu, 12 Feb 2004 10:23:28 +0200
Received: from trebe003.NOE.Nokia.com ([172.22.232.175]) by esebe007.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Thu, 12 Feb 2004 10:23:27 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: proposal for built-in spam burden & email privacy protection
Date: Thu, 12 Feb 2004 10:23:28 +0200
Message-ID: <D0299AFF29E01E478321564030AD69090BE559@trebe003.europe.nokia.com>
Thread-Topic: proposal for built-in spam burden & email privacy protection
Thread-Index: AcPw4F7WFwpwqnqVR+6zAzUJM63JzQAYC4Bg
To: <dberman@sen.us>, <spamtrap.ietf@dja.mailme.org>, <dean@av8.com>
Cc: <ietf@ietf.org>
X-OriginalArrivalTime: 12 Feb 2004 08:23:27.0521 (UTC) FILETIME=[7D616910:01C3F141]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> The real problem isn't from companies who send bulk email and allow =
you to opt out.

Not true (amymore). Opting out involves either a click or and email =
response. Both are well know methods for the "bad guys" to harvest =
better email lists and thus this behaviour is a bad idea - even for the =
"potential-good-guys" because its rather difficult to tell the =
difference with unsolicited email.

So opt out mechanisms are not useful for the union of "bulk" and =
"unsolicited" email (IMHO).

(Just one of my 2 cents worth :)

Sorry for the bulk nature of this limitted-content email!

Cheers, Rod.



From owner-ietf@ietf.org  Thu Feb 12 07:42:13 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21032
	for <ietf-archive@odin.ietf.org>; Thu, 12 Feb 2004 07:42:13 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArFy5-00078s-Ei
	for ietf-list@asgard.ietf.org; Thu, 12 Feb 2004 07:29:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ArFxz-000786-PK
	for ietf@asgard.ietf.org; Thu, 12 Feb 2004 07:29:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20630
	for <ietf@ietf.org>; Thu, 12 Feb 2004 07:29:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArFxv-00058q-00
	for ietf@ietf.org; Thu, 12 Feb 2004 07:29:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArFwu-00054b-00
	for ietf@ietf.org; Thu, 12 Feb 2004 07:28:09 -0500
Received: from almso1.att.com ([192.128.167.69] helo=almso1.proxy.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArFwa-000507-00
	for ietf@ietf.org; Thu, 12 Feb 2004 07:27:48 -0500
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by almso1.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id i1CC7Bec027524
	for <ietf@ietf.org>; Thu, 12 Feb 2004 07:27:19 -0500
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 40169495008C6201; Thu, 12 Feb 2004 07:26:50 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Visa for Korea
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Thu, 12 Feb 2004 06:27:19 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA02BA3900@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Visa for Korea
Thread-Index: AcPxA9K4PyHXRdVMTNeBk/flNuGQjwAX1vRw
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Gene Gaines" <gene.gaines@gainesgroup.com>, <ietf@ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Thanks a lot Gene, for your persistence and follow-through! =20

You've done a real service for the IETF community.  It is appreciated.

Regards,
Jerry

-----Original Message-----
From: Gene Gaines [mailto:gene.gaines@gainesgroup.com]
Sent: Wednesday, February 11, 2004 7:44 PM
To: ietf@ietf.org
Subject: Visa for Korea

As promised.

The Korean consulate in DC has produced two letters
for U.S. citizens to carry with them to the IETF
Seoul meeting.

The letters state that U.S. citizens carrying a valid
passport traveling to Korea to attend the IETF meeting
and/or tourism for up to 30 days DO NOT NEED A VISA.

The letters have been confirmed with the responsible
minitries in Korea, and copies sent immigration at
Incheon airport, the usual point of entry for Seoul.

I have made graphic files and sent them on to the
IETF Secretariat people to post to the web.  Give
them a couple of days to review and get them up.

Print and take with you.  Show if border officials
ask for them.

Gene Gaines
gene.gaines@gainesgroup.com
Sterling, Virginia USA



From owner-ietf@ietf.org  Thu Feb 12 08:34:19 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23267
	for <ietf-archive@odin.ietf.org>; Thu, 12 Feb 2004 08:34:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArGtB-0008Lr-1e
	for ietf-list@asgard.ietf.org; Thu, 12 Feb 2004 08:28:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ar5bw-0000EM-NP
	for ietf@asgard.ietf.org; Wed, 11 Feb 2004 20:25:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17095
	for <ietf@ietf.org>; Wed, 11 Feb 2004 20:25:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar5bv-0003do-00
	for ietf@ietf.org; Wed, 11 Feb 2004 20:25:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ar5ax-0003YS-00
	for ietf@ietf.org; Wed, 11 Feb 2004 20:24:48 -0500
Received: from stratton-forty-three.mit.edu ([18.187.5.43] helo=konishi-polis.mit.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar5a1-0003T5-00; Wed, 11 Feb 2004 20:23:49 -0500
Received: by konishi-polis.mit.edu (Postfix, from userid 8042)
	id 7C81F15201F; Wed, 11 Feb 2004 20:20:59 -0500 (EST)
To: The IESG <iesg@ietf.org>
Cc: ietf@ietf.org
Subject: Re: [secdir] [New-work] WG Review: New IETF Standards Track
 (newtrk)
References: <200402111848.NAA13315@ietf.org>
From: Sam Hartman <hartmans@mit.edu>
Date: Wed, 11 Feb 2004 20:20:59 -0500
In-Reply-To: <200402111848.NAA13315@ietf.org> (The IESG's message of "Wed,
 11 Feb 2004 13:48:40 -0500")
Message-ID: <tslznbphz44.fsf@konishi-polis.mit.edu>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


One item in the proposed charter concerns me greatly:


  The working group should also take into account other issues raised by the
  problem working group and during the newtrk BOF as needed.

That does not sound narrowly scoped at all.  It might be reasonable to
take into account these items as they relate to the explicitly
enumerated goals of the working group, but it does not seem reasonable
to take into account issues that would create a new goal or expand the
scope of the working group.

--Sam






From owner-ietf@ietf.org  Thu Feb 12 15:46:32 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13841
	for <ietf-archive@odin.ietf.org>; Thu, 12 Feb 2004 15:46:32 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArNaO-00086a-2C
	for ietf-list@asgard.ietf.org; Thu, 12 Feb 2004 15:37:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ArNZR-00085E-5R
	for ietf@asgard.ietf.org; Thu, 12 Feb 2004 15:36:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13362
	for <ietf@ietf.org>; Thu, 12 Feb 2004 15:36:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArNZN-0000cc-00
	for ietf@ietf.org; Thu, 12 Feb 2004 15:36:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArNYP-0000Xe-00
	for ietf@ietf.org; Thu, 12 Feb 2004 15:35:22 -0500
Received: from mail12.atl.registeredsite.com ([64.224.219.86] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArNXS-0000T5-00
	for ietf@ietf.org; Thu, 12 Feb 2004 15:34:22 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail12.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1CKYOsb006923
	for <ietf@ietf.org>; Thu, 12 Feb 2004 15:34:24 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Thu, 12 Feb 2004 14:34:22 -0600
Message-ID: <402BE34E.51AB6CD4@nma.com>
Date: Thu, 12 Feb 2004 12:34:22 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: going off-list, Re: proposal for built-in spam burden & email privacy 
 protection
References: <D0299AFF29E01E478321564030AD69090BE559@trebe003.europe.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

Thanks for the diverse and interesting feedback. I'm replying to 
each message off-list, not to burden the entire ietf.org 
discussions. I'm also collecting all comments for an Internet 
draft to be submitted to the IETF. If you have further comments,
I suggest you send them to me privately. I'll post here a URL
for the draft text, and comments, before the draft is submitted.

The motivation for this work is that, today, email is still the
equivalent of sending and receiving postcards. Open for anyone 
("friends" and foes alike) to read and even write on them. In 
the postal mail paradigm this is indeed useful ... but only for 
trivial messages between friends. 

Someday, however, users will want to stop using postcards for all 
their electronic conversations. At that time, at  zero added cost, 
we can easily introduce a mandatory per-message burden to spammers 
and make it backward compatible (so that we don't disrupt anything). 
The proposal points out that both goals (privacy and anti-spam) can 
be served not with signing but with encryption (even though, as an 
add on, signing may also help).

Of course, there will always be those who want to use postcards for 
their communication and that's why current postcard email should 
be preserved in any proposal to make email private.

Cheers,
Ed Gerck



From owner-ietf@ietf.org  Thu Feb 12 16:07:26 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15696
	for <ietf-archive@odin.ietf.org>; Thu, 12 Feb 2004 16:07:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArNyY-0001dT-G8
	for ietf-list@asgard.ietf.org; Thu, 12 Feb 2004 16:02:22 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ArNvt-0001b1-4g
	for ietf@asgard.ietf.org; Thu, 12 Feb 2004 15:59:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15186
	for <ietf@ietf.org>; Thu, 12 Feb 2004 15:59:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArNvp-0003Tv-00
	for ietf@ietf.org; Thu, 12 Feb 2004 15:59:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArNui-0003Jy-00
	for ietf@ietf.org; Thu, 12 Feb 2004 15:58:25 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArNtk-00036O-00
	for ietf@ietf.org; Thu, 12 Feb 2004 15:57:24 -0500
Received: from ibm-eyjgx9r6nqt.shockey.us (neustargw.va.neustar.com [209.173.53.233])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i1CL5Jd07060
	for <ietf@ietf.org>; Thu, 12 Feb 2004 13:05:19 -0800
Message-Id: <6.0.1.1.2.20040212155513.03b39ea0@popd.ix.netcom.com>
X-Sender: richard@joy.songbird.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 12 Feb 2004 15:56:41 -0500
To: ietf@ietf.org
From: Richard Shockey <richard@shockey.us>
Subject: News Item : US FCC rules 'Pure' VoIP not a phone service
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=BIZ_TLD autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk



Handing a partial victory to providers of Internet phone services, federal 
regulators ruled Thursday that voice communications that flow entirely over 
the Internet are not subject to traditional government regulations.

http://news.com.com/2100-7352_3-5158105.html



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
PSTN Office +1 571.434.5651 PSTN Mobile: +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  Thu Feb 12 16:40:49 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17507
	for <ietf-archive@odin.ietf.org>; Thu, 12 Feb 2004 16:40:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArOTT-0002fC-MC
	for ietf-list@asgard.ietf.org; Thu, 12 Feb 2004 16:34:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ArOSd-0002eZ-03
	for ietf@asgard.ietf.org; Thu, 12 Feb 2004 16:33:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17265
	for <ietf@ietf.org>; Thu, 12 Feb 2004 16:33:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArOSZ-000728-00
	for ietf@ietf.org; Thu, 12 Feb 2004 16:33:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArORf-0006xK-00
	for ietf@ietf.org; Thu, 12 Feb 2004 16:32:28 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArOR8-0006pQ-00
	for ietf@ietf.org; Thu, 12 Feb 2004 16:31:54 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1CLVIZH028687
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 12 Feb 2004 16:31:22 -0500
Date: Thu, 12 Feb 2004 16:31:18 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Ed Gerck <egerck@nma.com>
cc: ietf@ietf.org
Subject: Re: going off-list, Re: proposal for built-in spam burden & email
 privacy  protection
In-Reply-To: <402BE34E.51AB6CD4@nma.com>
Message-ID: <Pine.LNX.4.44.0402121620560.28416-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 12 Feb 2004, Ed Gerck wrote:
> Someday, however, users will want to stop using postcards for all 
> their electronic conversations. At that time, at  zero added cost, 
> we can easily introduce a mandatory per-message burden to spammers 
> and make it backward compatible (so that we don't disrupt anything). 
> The proposal points out that both goals (privacy and anti-spam) can 
> be served not with signing but with encryption (even though, as an 
> add on, signing may also help).

This is where the thinking is not clear: You can't add a cost to only
spammers.  Any cost increase in the cost of email would affect other large
email users (mailing lists, and such) at best equally to spammers, and
maybe not even equally.  Most spam is sent from infected computers, so the
spammer wouldn't pay anyway (whether it is money or computational power).

Further, any cost increase in email that is less than the cost of bulk
postal mail will not deter genuine spammers. But even the regular user
would feel the crunch if each email cost $0.37.  If the IETF had to pay
$0.37 per email, or even $0.15 per email, its 2 million/yr or so budget
would not cover its email costs, and your draft would not be published.

		--Dean




From owner-ietf@ietf.org  Thu Feb 12 17:55:57 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21084
	for <ietf-archive@odin.ietf.org>; Thu, 12 Feb 2004 17:55:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArPc7-00047t-Dg
	for ietf-list@asgard.ietf.org; Thu, 12 Feb 2004 17:47:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ArPbG-00047A-VU
	for ietf@asgard.ietf.org; Thu, 12 Feb 2004 17:46:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20766
	for <ietf@ietf.org>; Thu, 12 Feb 2004 17:46:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArPbD-0006VC-00
	for ietf@ietf.org; Thu, 12 Feb 2004 17:46:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArPaG-0006Oi-00
	for ietf@ietf.org; Thu, 12 Feb 2004 17:45:25 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArPZJ-0006K4-00
	for ietf@ietf.org; Thu, 12 Feb 2004 17:44:25 -0500
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>;
          Thu, 12 Feb 2004 17:44:26 -0500
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: Multiplication, specifically large numbers by small ones
Date: Thu, 12 Feb 2004 17:44:26 -0500
Message-ID: <20040212224426944.AAA601@hq.lindsayelec.com@rflooker1>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>Further, any cost increase in email that is less than the cost of bulk
>postal mail will not deter genuine spammers. But even the regular user
>would feel the crunch if each email cost $0.37.  If the IETF had to pay
>$0.37 per email, or even $0.15 per email, its 2 million/yr or so budget
>would not cover its email costs, and your draft would not be published.

Dan says:
Well, I have never gotten an unsolicited paper item for Viagra, but have
gotten hundreds of electronic ones. There is a distinction between
unsolicited communications, direct marketing, and spam. Its subtle and
creates (in the US) first amendment rights issues that are non-trivial.

But, 100M email mass solicitation at $0.001 each is $100K, which is a medium
good houseworth of dollar value here. I think it would annihlate the worst
of mass spam.

Obviously, all email could travel as free per or some stipulated super low,
sub penny cost. EMail programs would instantly sort it and offer to throw
away the < $0.01 items

I don't see a compelling reason to add a cost in the absolute case. In such
a scenerio after even one $0.01 message your email infrastructure could hand
subsequent items for $0.00 per.

I think whoever thought up the idea should be identified as a pretty sharp
cookie. Its just slices through so many thorny issues with few downsides.

Of course, if absolutely no one responded to spam the incentive wouldn't be
there to send it. So maybe we just need more time for young people .... Hey!
There is a guy in Nigeria who wants to give me two million dollars. Gotta go!







From owner-ietf@ietf.org  Thu Feb 12 20:03:19 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28929
	for <ietf-archive@odin.ietf.org>; Thu, 12 Feb 2004 20:03:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArRVD-00069Z-7W
	for ietf-list@asgard.ietf.org; Thu, 12 Feb 2004 19:48:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ArRUd-00068i-Ky
	for ietf@asgard.ietf.org; Thu, 12 Feb 2004 19:47:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28650
	for <ietf@ietf.org>; Thu, 12 Feb 2004 19:47:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArRUT-0004A3-00
	for ietf@ietf.org; Thu, 12 Feb 2004 19:47:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArRTl-000454-00
	for ietf@ietf.org; Thu, 12 Feb 2004 19:46:50 -0500
Received: from mail7.atl.registeredsite.com ([64.224.219.81] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArRT5-00040M-00
	for ietf@ietf.org; Thu, 12 Feb 2004 19:46:07 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail7.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1D0k7uk031421;
	Thu, 12 Feb 2004 19:46:07 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Thu, 12 Feb 2004 18:46:06 -0600
Message-ID: <402C1E4D.3CFD581@nma.com>
Date: Thu, 12 Feb 2004 16:46:05 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: Franck Martin <franck@sopac.org>, John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: proposal for built-in spam burden & email privacy protection
References: <Pine.LNX.4.44.0402101046250.6922-100000@cirrus.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Dean Anderson wrote:

> Then using the IETF list as an example, you would need the entire list of
> recipients and their public keys, and you would need to send a message
> either directly to each of them, one by one, or send a single message with
> a session key for each recipient (thousands).  This isn't going to work.

Let's not mix apples with speedboats. These are some options with the 
proposal:

#1: no encryption is used either way, the list address is in a whitelist 
for each recipient.

#2: each recipient can only send encrypted msgs (possibly, also
signed) to the list, with the list's key, for distribution. The listserver 
verifies and resends the messages in plain text, where #1 applies for 
each recipient.

#3: the list receives messages as in #2 but the listserver sends the
msgs as encrypted mail to each recipient, with each recipient's key.

IETF.ORG, possibly, should be #1.  No problem in using postcards
here. However, to help prevent spam, IETF.ORG can use #2.
 
> Second, even if the above weren't a problem, one still has the problem
> that a virus infected user will still be sending messages, just like
> everyone else.

Again, his would not work well with the proposal, due to the encryption 
being per message. And the hijacked user would tend to notice any heavy 
usage.

> You can't make it more expensive without shooting yourself in the foot.
> In information theory-speak, you can't prevent a covert channel** unless
> you have no channel at all.  

By the addition of a correction channel (Shannon's 10th theorem),
a covert channel can be detected with a probability as close to 100%
as I wish.

> Covert-channel detection is a whack-a-mole game. 

Not really. It can be modeled, it can be improved.

> Putting it in different terms, how can the government make sure those
> "government use only" stamped envelopes are only used for government
> business? 

Easy. By applying Shannon's 10th theorem. Sample enough mail at
distribution centers (going back to the source, which is possible
even without a legal mandate to open the  envelopes) and bar the 
culprits from sending govt. mail until the probability that any 
mail is incorrectly using govt. envelopes is a close to zero as desired.

> There is no scheme in which the rules can't be broken by someone intent on
> breaking them. 

This may sound good but is incorrect. Systems can be designed
such that a set of properties remain effective if most or even 
all parts of the system fail (for whatever reason, including
attacks).

> The only path is to detect them, and prosecute them.  

There is no world law, no unified way to prosecute. Even
venue is hard to guarantee (allowing you to  prosecute
the culprit).

> In
> the case of spam, detection is easy, but not automatic.  Prosecution is
> now possible.  Its still a whack-a-mole game. It won't end unless you can
> get past the virus infection to the virus operator, and hopefully, there
> aren't really too many virus operators.  Of course, we aren't stopping
> spam either in a very real sense, but rather abusers who are annoying and
> mailbombing people.  But by my count of my inbox, if you stop those
> people, I can certainly handle the rest which amounts to maybe 1% of my
> current junk mail.

When you outlaw spam, only the outlaws spam. So what? The
problem still remains, even if you call them outlaws. Also,
users should not have to sue spammers, or have any other burden,
in order to protect the users' resources. Imagine if I would 
have to manage 300 lawsuits a day (the average spam rate that
my system cannot automatically detect as spam)?



From owner-ietf@ietf.org  Thu Feb 12 22:00:22 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04445
	for <ietf-archive@odin.ietf.org>; Thu, 12 Feb 2004 22:00:22 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArTQs-00082c-Og
	for ietf-list@asgard.ietf.org; Thu, 12 Feb 2004 21:51:58 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ArTOh-000810-7m
	for ietf@asgard.ietf.org; Thu, 12 Feb 2004 21:49:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04055
	for <ietf@ietf.org>; Thu, 12 Feb 2004 21:49:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArTOZ-0000dZ-00
	for ietf@ietf.org; Thu, 12 Feb 2004 21:49:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArTNf-0000Z2-00
	for ietf@ietf.org; Thu, 12 Feb 2004 21:48:40 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArTN3-0000UE-00
	for ietf@ietf.org; Thu, 12 Feb 2004 21:48:02 -0500
Received: by franck-lxnb.sopac.org.fj (Postfix, from userid 501)
	id 55DBB4B6A2; Thu, 12 Feb 2004 21:47:59 -0500 (EST)
Subject: Re: proposal for built-in spam burden & email privacy protection
From: Franck Martin <franck@sopac.org>
To: Ed Gerck <egerck@nma.com>
Cc: Dean Anderson <dean@av8.com>, John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>,
        "ietf@ietf.org" <ietf@ietf.org>
In-Reply-To: <402C1E4D.3CFD581@nma.com>
References: <Pine.LNX.4.44.0402101046250.6922-100000@cirrus.av8.net>
	 <402C1E4D.3CFD581@nma.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-fX1kgwAwz7e+nOCOeqKZ"
Organization: SOPAC
Message-Id: <1076640479.3070.84.camel@franck-lxnb.sopac.org.fj>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4-1.1mdk 
Date: 13 Feb 2004 14:47:59 +1200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_FONTCOLOR_UNSAFE,
	HTML_MESSAGE autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-fX1kgwAwz7e+nOCOeqKZ
Content-Type: multipart/alternative; boundary="=-D5PvaHtEm2q0Kagn5KPC"


--=-D5PvaHtEm2q0Kagn5KPC
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2004-02-13 at 12:46, Ed Gerck wrote:

> Dean Anderson wrote:
>=20
> > Then using the IETF list as an example, you would need the entire list =
of
> > recipients and their public keys, and you would need to send a message
> > either directly to each of them, one by one, or send a single message w=
ith
> > a session key for each recipient (thousands).  This isn't going to work=
.
>=20
> Let's not mix apples with speedboats. These are some options with the=20
> proposal:
>=20
> #1: no encryption is used either way, the list address is in a whitelist=20
> for each recipient.
>=20
> #2: each recipient can only send encrypted msgs (possibly, also
> signed) to the list, with the list's key, for distribution. The listserve=
r=20
> verifies and resends the messages in plain text, where #1 applies for=20
> each recipient.
>=20
> #3: the list receives messages as in #2 but the listserver sends the
> msgs as encrypted mail to each recipient, with each recipient's key.

#4 (my preferred) the member send a message to the list with his digital
signature. The list checks the digital signature (from keyserver or from
a member database) and post the message if signature is valid. If the
signature is not valid, the message is held for approval.

But yes this scheme does not offer much more than restrict posting to
list members only, which the IETF had to do last year(?).

May be it would provide an avenue to not restrict posting to members
only if a posting is correctly digitally signed...

Yes a user could send digitally signed viruses without his/her
knowledge. Hopefully software that applies digitally signature to
e-mails do not do it blindly without repetitive manual user intervention
(after idle time, you must re-enter your key password). Or a mail cannot
be sent via a script without entering the key password.

>=20
> > In
> > the case of spam, detection is easy, but not automatic.  Prosecution is
> > now possible.  Its still a whack-a-mole game. It won't end unless you c=
an
> > get past the virus infection to the virus operator, and hopefully, ther=
e
> > aren't really too many virus operators.  Of course, we aren't stopping
> > spam either in a very real sense, but rather abusers who are annoying a=
nd
> > mailbombing people.  But by my count of my inbox, if you stop those
> > people, I can certainly handle the rest which amounts to maybe 1% of my
> > current junk mail.
>=20
> When you outlaw spam, only the outlaws spam. So what? The
> problem still remains, even if you call them outlaws. Also,
> users should not have to sue spammers, or have any other burden,
> in order to protect the users' resources. Imagine if I would=20
> have to manage 300 lawsuits a day (the average spam rate that
> my system cannot automatically detect as spam)?

You can contribute to a pool of reports, like spamcop does or other
systems based on a message signature count. When a threshold is reached,
you know something suspicious is happening. You can then collect the
reports, bundle them and sue on behalf of the users, that's what public
prosecutors do sometime. They do not necessarily need a complaint...

----
Franck Martin
franck@sopac.org
SOPAC, Fiji
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9  D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard

--=-D5PvaHtEm2q0Kagn5KPC
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
  <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/1.1.10">
</HEAD>
<BODY>
On Fri, 2004-02-13 at 12:46, Ed Gerck wrote:
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>Dean Anderson wrote:

&gt; Then using the IETF list as an example, you would need the entire list=
 of
&gt; recipients and their public keys, and you would need to send a message
&gt; either directly to each of them, one by one, or send a single message =
with
&gt; a session key for each recipient (thousands).  This isn't going to wor=
k.

Let's not mix apples with speedboats. These are some options with the=20
proposal:

#1: no encryption is used either way, the list address is in a whitelist=20
for each recipient.

#2: each recipient can only send encrypted msgs (possibly, also
signed) to the list, with the list's key, for distribution. The listserver=20
verifies and resends the messages in plain text, where #1 applies for=20
each recipient.

#3: the list receives messages as in #2 but the listserver sends the
msgs as encrypted mail to each recipient, with each recipient's key.</I></F=
ONT></PRE>
</BLOCKQUOTE>
<FONT SIZE=3D"3">#4 (my preferred) the member send a message to the list wi=
th his digital signature. The list checks the digital signature (from keyse=
rver or from a member database) and post the message if signature is valid.=
 If the signature is not valid, the message is held for approval.<BR>
<BR>
But yes this scheme does not offer much more than restrict posting to list =
members only, which the IETF had to do last year(?).<BR>
<BR>
May be it would provide an avenue to not restrict posting to members only i=
f a posting is correctly digitally signed...<BR>
<BR>
Yes a user could send digitally signed viruses without his/her knowledge. H=
opefully software that applies digitally signature to e-mails do not do it =
blindly without repetitive manual user intervention (after idle time, you m=
ust re-enter your key password). Or a mail cannot be sent via a script with=
out entering the key password.</FONT>
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>
&gt; In
&gt; the case of spam, detection is easy, but not automatic.  Prosecution i=
s
&gt; now possible.  Its still a whack-a-mole game. It won't end unless you =
can
&gt; get past the virus infection to the virus operator, and hopefully, the=
re
&gt; aren't really too many virus operators.  Of course, we aren't stopping
&gt; spam either in a very real sense, but rather abusers who are annoying =
and
&gt; mailbombing people.  But by my count of my inbox, if you stop those
&gt; people, I can certainly handle the rest which amounts to maybe 1% of m=
y
&gt; current junk mail.

When you outlaw spam, only the outlaws spam. So what? The
problem still remains, even if you call them outlaws. Also,
users should not have to sue spammers, or have any other burden,
in order to protect the users' resources. Imagine if I would=20
have to manage 300 lawsuits a day (the average spam rate that
my system cannot automatically detect as spam)?</I></FONT></PRE>
</BLOCKQUOTE>
<FONT SIZE=3D"3">You can contribute to a pool of reports, like spamcop does=
 or other systems based on a message signature count. When a threshold is r=
eached, you know something suspicious is happening. You can then collect th=
e reports, bundle them and sue on behalf of the users, that's what public p=
rosecutors do sometime. They do not necessarily need a complaint...</FONT>
<PRE><TABLE CELLSPACING=3D"0" CELLPADDING=3D"0" WIDTH=3D"100%">
<TR>
<TD>
----<BR>
Franck Martin<BR>
<A HREF=3D"mailto:franck@sopac.org">franck@sopac.org</A><BR>
SOPAC, Fiji<BR>
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9&nbsp; D9C6 BE79 9E60 81D9 =
1320<BR>
&quot;Toute connaissance est une reponse a une question&quot; G.Bachelard
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-D5PvaHtEm2q0Kagn5KPC--

--=-fX1kgwAwz7e+nOCOeqKZ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQBALDrevnmeYIHZEyARAgACAJ9P+7gz1oZ3ZBA/Pljfcq+mIJd6sgCfU4fe
HLTXyTwvtHG8B+gcMDGQN9c=
=jxlB
-----END PGP SIGNATURE-----

--=-fX1kgwAwz7e+nOCOeqKZ--



From owner-ietf@ietf.org  Thu Feb 12 23:39:32 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07228
	for <ietf-archive@odin.ietf.org>; Thu, 12 Feb 2004 23:39:32 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArUsE-0001Ay-1z
	for ietf-list@asgard.ietf.org; Thu, 12 Feb 2004 23:24:18 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ArUrf-0001AE-EA
	for ietf@asgard.ietf.org; Thu, 12 Feb 2004 23:23:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06737
	for <ietf@ietf.org>; Thu, 12 Feb 2004 23:23:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArUrb-0000oe-00
	for ietf@ietf.org; Thu, 12 Feb 2004 23:23:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArUqg-0000k2-00
	for ietf@ietf.org; Thu, 12 Feb 2004 23:22:42 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArUq4-0000fI-00
	for ietf@ietf.org; Thu, 12 Feb 2004 23:22:11 -0500
Received: by franck-lxnb.sopac.org.fj (Postfix, from userid 501)
	id 646C04B6A2; Thu, 12 Feb 2004 23:01:42 -0500 (EST)
Subject: Wiki Syntax RFC
From: Franck Martin <franck@sopac.org>
To: ietf@ietf.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-TPHMEyxXKSr9IRRu8b7l"
Organization: SOPAC
Message-Id: <1076644902.2746.6.camel@franck-lxnb.sopac.org.fj>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4-1.1mdk 
Date: 13 Feb 2004 16:01:42 +1200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-TPHMEyxXKSr9IRRu8b7l
Content-Type: multipart/alternative; boundary="=-CD9cBAXth0MzWewstUKw"


--=-CD9cBAXth0MzWewstUKw
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

http://tikiwiki.org/tiki-editpage.php?page=3DRFCWiki

I have updated the page toward an RFC. Please look, comment and modify
(you may need to register).

I'm particularly interested to know if the page is RFC formatted.

Cheers
----
Franck Martin
franck@sopac.org
SOPAC, Fiji
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9  D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard

--=-CD9cBAXth0MzWewstUKw
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
  <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/1.1.10">
</HEAD>
<BODY>
<A HREF=3D"http://tikiwiki.org/tiki-editpage.php?page=3DRFCWiki">http://tik=
iwiki.org/tiki-editpage.php?page=3DRFCWiki</A><BR>
<BR>
I have updated the page toward an RFC. Please look, comment and modify (you=
 may need to register).<BR>
<BR>
I'm particularly interested to know if the page is RFC formatted.<BR>
<BR>
Cheers<BR>
<TABLE CELLSPACING=3D"0" CELLPADDING=3D"0" WIDTH=3D"100%">
<TR>
<TD>
----<BR>
Franck Martin<BR>
<A HREF=3D"mailto:franck@sopac.org">franck@sopac.org</A><BR>
SOPAC, Fiji<BR>
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9&nbsp; D9C6 BE79 9E60 81D9 =
1320<BR>
&quot;Toute connaissance est une reponse a une question&quot; G.Bachelard
</TD>
</TR>
</TABLE>

</BODY>
</HTML>

--=-CD9cBAXth0MzWewstUKw--

--=-TPHMEyxXKSr9IRRu8b7l
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQBALEwlvnmeYIHZEyARAvLaAJ0cS066PzvAGTzXfigN+RjsMsg5ZgCeIJ/g
D10WoP2d4YZktiSxraerdTY=
=fDcW
-----END PGP SIGNATURE-----

--=-TPHMEyxXKSr9IRRu8b7l--



From owner-ietf@ietf.org  Fri Feb 13 00:30:49 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09331
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 00:30:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArVoH-0002RJ-JF
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 00:24:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ArVnr-0002Pv-Pd
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 00:23:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09121
	for <ietf@ietf.org>; Fri, 13 Feb 2004 00:23:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArVnn-0006ux-00
	for ietf@ietf.org; Fri, 13 Feb 2004 00:23:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArVmp-0006q4-00
	for ietf@ietf.org; Fri, 13 Feb 2004 00:22:47 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArVmO-0006kv-00
	for ietf@ietf.org; Fri, 13 Feb 2004 00:22:20 -0500
Received: by franck-lxnb.sopac.org.fj (Postfix, from userid 501)
	id 220D64B6A2; Fri, 13 Feb 2004 00:21:32 -0500 (EST)
Subject: [Fwd: Re: Wiki Syntax RFC]
From: Franck Martin <franck@sopac.org>
To: ietf@ietf.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-2GLfnnxsZpN+JkBbTaZ+"
Organization: SOPAC
Message-Id: <1076649691.4326.5.camel@franck-lxnb.sopac.org.fj>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4-1.1mdk 
Date: 13 Feb 2004 17:21:32 +1200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-2GLfnnxsZpN+JkBbTaZ+
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

My apologies...

Below is the correct link

-----Forwarded Message-----

From: Chris Yarnell <cdy@kooks.net>
I think you really wanted to post:

http://tikiwiki.org/tiki-index.php?page=3DRFCWiki

? :-)

> http://tikiwiki.org/tiki-editpage.php?page=3DRFCWiki

----
Franck Martin
franck@sopac.org
SOPAC, Fiji
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9  D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard

--=-2GLfnnxsZpN+JkBbTaZ+
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQBALF7bvnmeYIHZEyARAgt/AJ9fp4DEAED+RF8DOFviVm22WqjDuACfUWqk
+4faGBTmvACzWAxoerYKELc=
=pnFS
-----END PGP SIGNATURE-----

--=-2GLfnnxsZpN+JkBbTaZ+--



From ltsxst@unisono.net.mx  Fri Feb 13 04:27:55 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00111
	for <ietf-archive@ietf.org>; Fri, 13 Feb 2004 04:27:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArZc1-000412-00
	for ietf-archive@ietf.org; Fri, 13 Feb 2004 04:27:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArZb5-0003vt-00
	for ietf-archive@ietf.org; Fri, 13 Feb 2004 04:26:56 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArZaF-0003qj-00; Fri, 13 Feb 2004 04:26:03 -0500
Received: from c-67-160-147-186.client.comcast.net ([67.160.147.186])
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1ArZaK-0003ND-Gw; Fri, 13 Feb 2004 04:26:09 -0500
Received: from [208.176.235.118] by c-67-160-147-186.client.comcast.net; Fri, 13 Feb 2004 10:19:10 +0100
Message-ID: <x-9$7---8y7-$31yn@lm8a.9d>
From: "Sophie Lin" <ltsxst@unisono.net.mx>
Reply-To: "Sophie Lin" <ltsxst@unisono.net.mx>
To: <ietf-action@ietf.org>, <ietf-admin@ietf.org>, <ietf-approval@ietf.org>,
        <ietf-archive@ietf.org>, <ietf-liaisons@ietf.org>,
        <ietf-outbound.07@ietf.org>
Subject: The more you work the less you make, sound familiar?
Date: Fri, 13 Feb 04 10:19:10 GMT
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="EEAA4C50BA2AD"
X-Priority: 3
X-MSMail-Priority: Normal
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=14.5 required=5.0 tests=BIZ_TLD,DATE_SPAMWARE_Y2K,
	FORGED_MUA_OUTLOOK,FORGED_OUTLOOK_HTML,HTML_40_50,HTML_MESSAGE,
	MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,MISSING_MIMEOLE,REMOVE_PAGE,
	SUSPICIOUS_RECIPS autolearn=no version=2.60
X-Spam-Report: 
	*  4.4 DATE_SPAMWARE_Y2K Date header uses unusual Y2K formatting
	*  0.5 HTML_40_50 BODY: Message is 40% to 50% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.8 REMOVE_PAGE URI: URL of page called "remove"
	*  0.8 BIZ_TLD URI: Contains a URL in the BIZ top-level domain
	*  3.0 SUSPICIOUS_RECIPS Similar addresses in recipient list
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  1.1 FORGED_OUTLOOK_HTML Outlook can't send HTML message only
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts
	*  1.6 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook


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

<html>
<head>
<title>g malaprop 4</title>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859=
-1">
</head>

<body>
<p>&nbsp;</p>
<p>Affiliate programs were never this easy in the past. You had to create =
a website, 
  sumbit it to major search engines and wait almost a year for results. Wi=
th <a href=3D"http://www.globalmarketing2000.biz/cashinwithgoogle/">my 
  program</a> you won't have to worry about any of this.</p>
<p></p>
<p><font size=3D"2">no more <a href=3D"http://www.globalmarketing2000.biz/=
remove.html">emails</a> 
  please </font></p>
</body>
</html>
szr mt ysj
vsnopdvouww b

--EEAA4C50BA2AD--



From owner-ietf@ietf.org  Fri Feb 13 05:25:52 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02231
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 05:25:52 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AraLr-0006xP-ED
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 05:15:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AraKl-0006vj-Su
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 05:14:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01779
	for <ietf@ietf.org>; Fri, 13 Feb 2004 05:14:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AraKh-000077-00
	for ietf@ietf.org; Fri, 13 Feb 2004 05:14:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AraJr-00001B-00
	for ietf@ietf.org; Fri, 13 Feb 2004 05:13:12 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AraJI-0007iv-00
	for ietf@ietf.org; Fri, 13 Feb 2004 05:12:36 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1DAD5of073385;
	Fri, 13 Feb 2004 11:13:09 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <E1AqcY2-0006FI-00@ietf-mx>
References: <E1AqcY2-0006FI-00@ietf-mx>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <242C510C-5E0D-11D8-B0DB-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: subjects, was: proposal for built-in spam burden & email privacy protection
Date: Fri, 13 Feb 2004 11:12:34 +0100
To: dberman@sen.us
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 10-feb-04, at 19:21, David Berman wrote:

> Subject lines for emails should be required to have only words that 
> can be found in the dictionary.  This eliminates any spam like vi@gr@ 
> or m0rtgage.

> The real problem isn't from companies who send bulk email and allow 
> you to opt out.  The problem comes from people that are trying not to 
> let you opt out.  Not only don't they let you opt out, but they also 
> try to get around your filters.

I agree with this for a large part. (Fortunately, my filter software 
isn't fooled this easily most of the time.)

It would be great if we could come up with a way to make sure the 
subject better reflects the content of a message, both to avoid this 
type of spamming and also for regular email, especially in cases where 
a mailinglist discussion strays but the subject remains the same.

An obvious first step here would be to require that the words in the 
subject line are also present in the body of the message.




From owner-ietf@ietf.org  Fri Feb 13 05:34:26 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02714
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 05:34:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AraaP-0007X9-VG
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 05:30:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AraYz-0007O1-P3
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 05:28:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02401
	for <ietf@ietf.org>; Fri, 13 Feb 2004 05:28:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AraYv-0001Rc-00
	for ietf@ietf.org; Fri, 13 Feb 2004 05:28:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AraXw-0001Iw-00
	for ietf@ietf.org; Fri, 13 Feb 2004 05:27:45 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AraWw-00017x-00
	for ietf@ietf.org; Fri, 13 Feb 2004 05:26:43 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1DAR7of073574;
	Fri, 13 Feb 2004 11:27:07 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0402091910320.6922-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0402091910320.6922-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1A0706C4-5E0F-11D8-B0DB-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: The IETF Mission
Date: Fri, 13 Feb 2004 11:26:36 +0100
To: Dean Anderson <dean@av8.com>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 10-feb-04, at 1:37, Dean Anderson wrote:

>         To work with suppliers, consortia, and other standards bodies 
> to
> develop consensus and facilitate interoperability.

So how does "the IETF" do this? Talking to others only works in a 
top-down organization, but not in a bottom-up organization. I don't see 
how a situation where the IETF, through its internal processes, reaches 
rough consensus, and then would have to negotiate with external 
entities, could work.

I think it's important that the IETF can operate autonomously, without 
"working" with anyone. If suppliers, consortia and other standards 
bodies have input to the IETF, they can participate like anyone else.




From owner-ietf@ietf.org  Fri Feb 13 05:44:37 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03152
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 05:44:37 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Arak3-00088h-72
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 05:40:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Arajj-00087r-Kr
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 05:39:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03030
	for <ietf@ietf.org>; Fri, 13 Feb 2004 05:39:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arajf-0002aH-00
	for ietf@ietf.org; Fri, 13 Feb 2004 05:39:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Araiq-0002WD-00
	for ietf@ietf.org; Fri, 13 Feb 2004 05:39:00 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arai8-0002RA-00
	for ietf@ietf.org; Fri, 13 Feb 2004 05:38:16 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1DAcnof073721;
	Fri, 13 Feb 2004 11:38:49 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <21987296.1076420595@localhost>
References: <21987296.1076420595@localhost>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <BC71D992-5E10-11D8-B0DB-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Continuing the story - another stab at an IETF mission statement
Date: Fri, 13 Feb 2004 11:38:18 +0100
To: Harald Tveit Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 10-feb-04, at 22:43, Harald Tveit Alvestrand wrote:

> I attempted to incorporate the latest discussions into an 
> internet-draft, which I managed to get out just before the 
> deadline....

>   draft-alvestrand-ietf-mission-00.txt

Good stuff.

But wouldn't it be useful to say something about the global nature of 
the internet and the IETF body of participants, and how this influences 
both the IETF's goals and the way it carries out its activities?

More specifically, the fact that the IETF exclusively uses English for 
its standards and internal processes creates a non-level participation 
field, but at the same time the use of a single, widely-spoken language 
allows for much lower costs and higher efficiency than any alternative.




From owner-ietf@ietf.org  Fri Feb 13 09:33:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10588
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 09:33:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AreDp-0003OE-JI
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 09:23:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AreDi-0003Mz-0f
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 09:23:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10228
	for <ietf@ietf.org>; Fri, 13 Feb 2004 09:23:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AreDh-0004HR-00
	for ietf@ietf.org; Fri, 13 Feb 2004 09:23:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AreCg-0004DH-00
	for ietf@ietf.org; Fri, 13 Feb 2004 09:22:03 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AreCA-00045f-00
	for ietf@ietf.org; Fri, 13 Feb 2004 09:21:30 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id 093BEA3; Fri, 13 Feb 2004 09:19:08 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: subjects, was: proposal for built-in spam burden & email privacy protection
Date: Fri, 13 Feb 2004 09:19:39 -0500
User-Agent: KMail/1.5.2
Cc: IETF Discussion <ietf@ietf.org>
References: <E1AqcY2-0006FI-00@ietf-mx> <242C510C-5E0D-11D8-B0DB-000A95CD987A@muada.com>
In-Reply-To: <242C510C-5E0D-11D8-B0DB-000A95CD987A@muada.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402130919.39788.spamtrap.ietf@dja.mailme.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Fri February 13 2004 05:12, Iljitsch van Beijnum wrote:

 > It would be great if we could come up with a way to make sure the
 > subject better reflects the content of a message, both to avoid this
 > type of spamming and also for regular email, especially in cases
 > where a mailinglist discussion strays but the subject remains the
 > same.
 >
 > An obvious first step here would be to require that the words in the
 > subject line are also present in the body of the message.

Watch out for that first step, it's a doozy!

1)  This will be trivially violated by typoes.

2) Some people treat the subject as part of the message.  They feel free 
to use nouns there as antecedents for pronouns in the body.  This may 
be short enough that the actual noun never needs to be mentioned again.  
Alternately, a different noun may be used.

3) Some people send messages with NO subject!  (Yes, even if it's not 
spam.)

4) Some people send messages with no BODY!  After all, brevity is the 
soul of wit.

And on that note, I better shut up now....  B-)

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.




From owner-ietf@ietf.org  Fri Feb 13 11:02:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16525
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 11:02:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Arfcv-0005LS-6i
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 10:53:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Arfcl-0005KU-6e
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 10:53:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15969
	for <ietf@ietf.org>; Fri, 13 Feb 2004 10:53:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arfck-0004TN-00
	for ietf@ietf.org; Fri, 13 Feb 2004 10:53:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Arfbp-0004Q5-00
	for ietf@ietf.org; Fri, 13 Feb 2004 10:52:07 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[X2ljN/TkXrIdHDQ3JiQ4gTVyl/DAe/0M])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArfbR-0004MX-00
	for ietf@ietf.org; Fri, 13 Feb 2004 10:51:41 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id C48B1A780B; Fri, 13 Feb 2004 10:47:40 -0500 (EST)
Date: Fri, 13 Feb 2004 10:12:39 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Dean Anderson <dean@av8.com>
Cc: Ed Gerck <egerck@nma.com>, <ietf@ietf.org>
Subject: Re: going off-list, Re: proposal for built-in spam burden & email
 privacy  protection
In-Reply-To: <Pine.LNX.4.44.0402121620560.28416-100000@cirrus.av8.net>
Message-ID: <Pine.LNX.4.44.0402130808040.1291-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 12 Feb 2004, Dean Anderson wrote:

> On Thu, 12 Feb 2004, Ed Gerck wrote:
> > Someday, however, users will want to stop using postcards for all 
> > their electronic conversations. At that time, at  zero added cost, 
> > we can easily introduce a mandatory per-message burden to spammers 
> > and make it backward compatible (so that we don't disrupt anything). 
> > The proposal points out that both goals (privacy and anti-spam) can 
> > be served not with signing but with encryption (even though, as an 
> > add on, signing may also help).
> 
> This is where the thinking is not clear: You can't add a cost to only
> spammers.  Any cost increase in the cost of email would affect other large
> email users (mailing lists, and such) at best equally to spammers, and
> maybe not even equally.  Most spam is sent from infected computers, so the
> spammer wouldn't pay anyway (whether it is money or computational power).
> 
> Further, any cost increase in email that is less than the cost of bulk
> postal mail will not deter genuine spammers. But even the regular user
> would feel the crunch if each email cost $0.37.  If the IETF had to pay
> $0.37 per email, or even $0.15 per email, its 2 million/yr or so budget
> would not cover its email costs, and your draft would not be published.

I totally agree with Dean.  I see no significant increase in costs to
the spammers, who use almost entirely automated tools in any event even
when one IS considering their local resource consumption.  This isn't
just a matter of opinion -- one can easily measure what the increase in
the worst-case "cost" to spammers will be.

Currently, email addresses are relatively "simple" objects and as such
are easy enough to remember (for humans) and communicate (for humans).
You propose to make an address a "complex" object: the simple address
plus kilobyte-sized blocks of text or binary data such as:

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.7 (GNU/Linux)

mQGiBDprOxURBADW+ybmMpoBfbRADv3OzXaaIQVWGDoaNsR4uxstcJgo+FYMcO9B
Ag7eXRLfOQFPPS3211W/f1/GaQa70ZaPZaQV/A9POIGfRIbcfePHaIUUXYulO3Nh
Bqewb5JZjzkj0yZWdjzK/OSBEPITXMXyTDVnG0+Y4YHHLDOODnnkSOlZKwCg453O
...(much much more)

BOTH components will need to be included in a mail header presuming that
when one sends mail one WILL want one's correspondants to be able to
read and reply to your message.  BOTH components will have to be
published in various ways and given out if you want to continue to be
able to receive mail, be it from friends or strangers.

Automated grazers that collect the simple objects now can just as easily
collect the complex objects since they will of necessity both be
associated with any publiction of somebody's address.

On the other hand, this additional degree of complexity will be a
horrible burden in time, energy, and money to ordinary users of mail at
every level and especially to systems administrators responsible for
training those users and de facto responsible for managing the data
problem the composite "address" object would represent.  Communicating,
managing, and remembering email addresses like "joe@whereever.edu" is
already "challenging" to many, if not most, users of email and is
obviously equally challenging at the corporate/professional level.  Let
us recall that most current AV software is still stupid enough to
consider the From address to actually be valid for viruses and SPAM and
cannot even manage to parse the real message header in sensible ways.
Now visualize these same bozos trying to deal with messages whose header
contains a 1-2K key:-/

Obviously, people will no longer be able to just say "here's my email
address".  Business cards will need to be roughly 4x6" and covered
mostly in small type.  Most users will simply rebel.  Most systems
people will simply rebel.  People CAN send encrypted, signed email now,
but how many do?  It's cumbersome and unnecessary for all but a certain
(small) class of sensitive traffic.

You are also suggesting that the encryption step, by being "expensive"
computationally, will at least slow down the spammers.  This assertion,
which has been made several times now, is simply not true.  Encryption,
especially RSA-type public/private key encryption, is NOT terribly
demanding in terms of numerical operations required per encrypted byte
-- this is one reason it is a popular and powerful algorithm.  Both SSL
and SSH routinely encrypt realtime traffic with little or no perceptible
delay relative to other sources of latency.  I use tools like rsync on
top of ssh to send entire compressed AND encrypted filesystem trees at
rates that (greatly) exceed a MB/second.  CPUs are powerful and cheap
and then there is Moore's Law.

Even with gpg used as a command line tool, it requires less than a
second to encrypt roughly a megabyte (possibly less -- the process is
likely not optimized for speed in the tools I'm using to crudely
measure).  That would be 500-2000 "typical" SPAM messages per second.  I
expect that this rate would easily ntuple if the relevant code were
extracted and written into an optimized binary, as gpg as a command line
tool has lots of per-invocation overhead that could be eliminated if
one's goal was simply to take a single message and a DB of keys and feed
an MTA queue.

Compare that as a bottleneck to the time required to send a thousand
email messages in the first place.  For each message there is a
nameservice hit to resolve the address, a protocol negotiation phase of
indeterminate length as the MTA connects to a remote agent and sends the
message on its way, and the local bandwidth bottleneck.  In nearly all
cases of stealth/virus driven SPAM, the per-message latency will likely
exceed the encryption time by a factor of two or more (quite possibly a
LOT more). A T1 link has a peak bottleneck of little more than a MB/sec,
for example, if you are pouring data through in an optimal stream.

Note that the encryption step is trivially parallelizable.  That means
that for a given MTA, EVEN if one is having a hard time keeping it busy
because of time spent encrypting (which I doubt), one can add one or
more cheap systems to the network to function as encryption slaves that
serve no purpose but to keep the MTA's outbound queue full.

I think that it is clear that your proposal won't have any significant
impact on SPAM generation, but it will have an enormous, and negative,
impact on ordinary mail users.

This is just a bad idea.  It is a VERY bad idea to push it as an actual
protocol requirement.  It is a bad idea to push it as best practice.  It
isn't even that great an idea to push it as a future design
recommendation.  It might be an "interesting" idea to discuss on an
appropriate list, and of course it is fair game for entrepreneurs and
developers with a vision and a perceived marketplace.

This is an issue that can be completely decided by those programmers
with a vision and the marketplace, not by a task force responsible for
developing protocols and open standards.  If one feels for any reason
that MTAs should be integrated with public key databases and
nameservices and key certificate agents extended to the level of
individuals, the protocols and open standard based tools all exist for
one to create software to support it (and indeed some individuals
already USE keys, signatures, and encryption for various purposes
including mail).  

So fine, invest the development effort to create the product and see who
buys it, or in the open source world, who adopts it and distributes it.
It is not appropriate for us to either mandate or suggest that ALL
developers "should" modify all their products to use a particular
layering of these tools as the default standard and force developers to
invest the resources required to do so at the very substantial risk that
no reward awaits them in the marketplace for having done it.

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Fri Feb 13 12:09:04 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20523
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 12:09:04 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Argem-0006z6-Ky
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 11:59:12 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Argdm-0006xK-4v
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 11:58:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20018
	for <ietf@ietf.org>; Fri, 13 Feb 2004 11:58:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Argdl-0003Wo-00
	for ietf@ietf.org; Fri, 13 Feb 2004 11:58:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Argcs-0003SV-00
	for ietf@ietf.org; Fri, 13 Feb 2004 11:57:15 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[KwNt7svl4t5dlepBcjreSsFGUIiNactX])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Argc6-0003Nu-00
	for ietf@ietf.org; Fri, 13 Feb 2004 11:56:26 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id D2844A78D1; Fri, 13 Feb 2004 11:56:23 -0500 (EST)
Date: Fri, 13 Feb 2004 11:21:23 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Dan Kolis <dank@hq.lindsayelec.com>
Cc: ietf@ietf.org
Subject: Re: Multiplication, specifically large numbers by small ones
In-Reply-To: <20040212224426944.AAA601@hq.lindsayelec.com@rflooker1>
Message-ID: <Pine.LNX.4.44.0402131013550.1291-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 12 Feb 2004, Dan Kolis wrote:

> >Further, any cost increase in email that is less than the cost of bulk
> >postal mail will not deter genuine spammers. But even the regular user
> >would feel the crunch if each email cost $0.37.  If the IETF had to pay
> >$0.37 per email, or even $0.15 per email, its 2 million/yr or so budget
> >would not cover its email costs, and your draft would not be published.
> 
> Dan says:
> Well, I have never gotten an unsolicited paper item for Viagra, but have
> gotten hundreds of electronic ones. There is a distinction between
> unsolicited communications, direct marketing, and spam. Its subtle and
> creates (in the US) first amendment rights issues that are non-trivial.
> 
> But, 100M email mass solicitation at $0.001 each is $100K, which is a medium
> good houseworth of dollar value here. I think it would annihlate the worst
> of mass spam.

It won't cost $0.001 in additional marginal cost to send a spam message
even if every bit of the proposal is implemented.  Assume 2K keys per
user, that is 200 GB of (reusable) hard storage required for the
database.  Assume 1000 messages can be encrypted per second, delivered
to the MTA, and pumped onto the net (a very reasonable estimate and in
any event not bottlenecked by the DB lookup or encryption step,
especially given that both can be parallelized).

That is 86,400,000 messages PER DAY (just under your 100M
specification), using roughly 1 MB/sec total bandwidth on an internet
connection 24x7 during that time.  Obviously if we tweak things a tiny
bit which we easily can, we could send 100M messages/day without
breaking a sweat from a single computer IF the MTA itself is capable of
it in the first place, so let's use this as a round number.

Let's BUY the MTA server and two encryption nodes whose only job is to
ensure that the MTA queue never runs dry, each equipped with 600 GB in
RAID3.  Let's see, that would be, hmm, less than $10K if one got gold
plated parts, less than $4K at my local OTC no-name computer store.
Let's amortize all costs over a year.  The $10K hardware cost is then a
measley $30/day.

Let's prepay for high bandwidth access to the network at exorbitant
rates, maybe $2000/month.  That works out to maybe $70/day (note that
I'm being deliberately absurd in my estimates).  However, note that this
cost is the SAME before and after the proposed encryption step is added
-- the cost of sending 100 GB of data out on the wire is independent of
whether or not the data is encrypted and might even be LESS because
messages are typically compressed before being encrypted and can be
smaller encrypted than in plaintext.

Forget the fact that the MARGINAL cost of encryption is thus $30/day, or
an even smaller $10/day if we assume the hardware will last three eyars.
Even at $100 cost / 100M messages = 1x10^{-6} dollars per message.  One
ten-thousdandth of a cent.  And this estimate is probably high by a
factor of ten over real costs, especially if the spammer is effectively
stealing the resource via a virus in which case the real cost could be
"nothing" -- to the spammer.  It costs the spammer more in HUMAN TIME
setting up the messages, billing for returns, and managing the systems
than it does to do ANY AMOUNT of automated mail processing, with or
without encryption.  Hardware is cheap and easily augmented if there is
any marginal benefit in doing so.

Note that NO REASONABLE SCALING of the work done to encrypt a message
will yield significant costs to the spammer before they do immense
amounts of damage in rising costs (especially HUMAN costs) elsewhere on
the Internet.  Suppose it takes a whopping 0.1 seconds to encrypt a 1K
message (it doesn't, not even close).  Fine, I could design a cheap-ass
100 node beowulf cluster that would cost, oh, $35K to feed the MTA its
requisite 1000 mps.  This bumps my per-message cost by another $100/day,
so it now costs me TWO ten-thousands of a cent to send a message.  I
don't think spammers work at such a low marginal profit that the extra
$100 in daily costs will phase them.

> I think whoever thought up the idea should be identified as a pretty sharp
> cookie. Its just slices through so many thorny issues with few downsides.

I think that whoever thought the idea up needs to do some concrete
arithmetic and some actual measurements and consider the cost-benefit.
Huge administrative costs to implement across the entire internet.  Huge
inconvenience.  Huge administrative costs passed back to the consumer.
All to AT MOST double the marginal cost per message to the spammer, who
makes a lucrative living because the marginal cost per message is so low
that doubling it, or even multiplying it by tenfold, is STILL almost
invisible to him or her.

Alas, the costs are not so low to the people the measure is intended to
protect.  The big cost to people who manage lists (or send any kind of
mail by hand) is going to be HUMAN -- administrative.  It is a PITA to
manage lists now -- addresses go bad, spammers try to sneak onto a list
to feed their address collection agents, a virus or spambot gets
inserted onto a legitimate list-member's system and makes it through a
whitelist so everybody gets hammered until the administrator shuts him
down.  This work burden will only increase manifold when in addition to
managing email addresses, one has to manage keys as well.  A user's key
is compromised.  A database with several entities in it has to be kept
consistent and clean.  Resources are diverted.  Debugging a failing
email connection becomes a work of art because the traffic looks like
garbage anyway, you don't control the user's keys or decryption agents,
and there are multiple points where corruption or protocol failure can
occur.  As a SERIOUS email user, I don't want to even think about
the hassle of having to manage keys for both myself and all the people
and lists I communicate with.  As a nearly twenty year sysadmin, I also
don't want to imagine trying to train users and support users with all
the headaches mandated use of public key/private keys would create.

SPAM is undeniably evil, but the place to add costs is at the ISP level
and the PoP level.  Acceptable use agreements with sharp nasty teeth and
anti-spam legislation that hits spammers AND the networks that
tolerate/enable their activities AND the actual vendors that are selling
the products being spammed with big fines have a far better chance of
having a favorable impact on SPAM than any number of arcane and
expensive countermeasures at the level of the mailer itself.

I was pleased to note that one of the group of SPAMmers who was recently
run to ground in North Carolina has just gone to trial today.  This is
what I expect to be at least part of a real solution -- hit him with a
$1M fine and park his butt in jail for a year or three, and publish it
loudly that you've done so.  Then hit the next one, and the next one.
Eventually spammers will have to add the amortized risk of getting fined
into financial ruin and put in jail with a bunch of relatively decent
rapists and murderers and cellmate molesters to their inevitably trivial
dollar cost per message.  Make this a REAL risk and a VISIBLE risk, and
wildcat spamming will stop, at least in this country.

Legislation CAN be effective.  The new do-not call list has worked
absolute wonders for me.  Note that PHONE spam was never free -- it
costs anywhere from $0.10 to $1 per call.  Yet three months ago I would
get hit a half-dozen times per day or more.  Caller ID was all but
useless, as few phonespammers used listed numbers or else they used
blocks.  The DNC list plus the promise of fines or worse, and I now get
phone-spammed once every few weeks, usually by somebody that apologizes
profusely and babbles about removing my name from their list once I
point out that I'm on the DNC list.  After all, they can't sell to me
without telling me who they are, and that's all I need to have them
fined or worse.

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Fri Feb 13 13:58:51 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25529
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 13:58:51 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AriOB-0000yn-NY
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 13:50:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AriMB-0000wA-VM
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 13:48:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24896
	for <ietf@ietf.org>; Fri, 13 Feb 2004 13:48:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AriMA-0005DN-00
	for ietf@ietf.org; Fri, 13 Feb 2004 13:48:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AriLC-00058u-00
	for ietf@ietf.org; Fri, 13 Feb 2004 13:47:07 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AriKJ-000552-00
	for ietf@ietf.org; Fri, 13 Feb 2004 13:46:11 -0500
Received: from dank ([191.1.2.3]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com for <ietf@ietf.org>;
          Fri, 13 Feb 2004 13:46:05 -0500
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: Primal urges in the can-the-spam movement
Date: Fri, 13 Feb 2004 13:46:05 -0500
Message-ID: <20040213184605691.AAA512@hq.lindsayelec.com@dank>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,NO_COST autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Robert Brown said:
>Let's BUY the MTA server and two encryption nodes whose only job is to
>ensure that the MTA queue never runs dry, each equipped with 600 GB in
>RAID3.  Let's see, that would be, hmm, less than $10K if one got gold
>plated parts, less than $4K at my local OTC no-name computer store.
>Let's amortize all costs over a year.  The $10K hardware cost is then a
>measley $30/day.


And further said:
>SPAM is undeniably evil, but the place to add costs is at the ISP level
>and the PoP level.  Acceptable use agreements with sharp nasty teeth and
>anti-spam legislation that hits spammers AND the networks that
>tolerate/enable their activities AND the actual vendors that are selling
>the products being spammed with big fines have a far better chance of
>having a favorable impact on SPAM than any number of arcane and
>expensive countermeasures at the level of the mailer itself.

>Legislation CAN be effective.  The new do-not call list has worked
>absolute wonders for me.  Note that PHONE spam was never free -- it
>costs anywhere from $0.10 to $1 per call.  Yet three months ago I would
>get hit a half-dozen times per day or more.  Caller ID was all but
>useless, as few phonespammers used listed numbers or else they used
>blocks.  The DNC list plus the promise of fines or worse, and I now get
>phone-spammed once every few weeks, usually by somebody that apologizes
>profusely and babbles about removing my name from their list once I
>point out that I'm on the DNC list.  After all, they can't sell to me
>without telling me who they are, and that's all I need to have them
>fined or worse.
>   rgb

Dan says:
If I follows Roberts scenerios, he visualizes ways to own things like MTA's,
etc and evade the cost per by magnitudes.

Generally, as the second fragment of text describes, Robert's suggesting
catch-me-if-you-can enforcement is the way to go.

If that's a logical mode, IETF can possibly see a mandate to tighten
technology to find our true sources of messages, packets, etc. Generally,
like MPLS, and 802.11b, the trend is moving slowly the other way.

I think instead of detailed calculations, an observation which might seem
familiar to economists is closer to the issue. 

If you expect people paid to enforce things to do it, they will always Jones
for more people and resources, and probably no enforcement in the world
accounts for capturing more than some ones of percents of undesired
activity. Like any community, there will always be a "crisis" or some
description requirement more of: everything. Cooperation, legal scope,
education, and of course always more money. This constitutes part of the
noise level that degrades much of modern life. (Like the incredible
competition to have the most interesting possible up and coming new disease,
mental problem or crime).

On the other hand, we all have a vested interest in watching the eggs in our
basket. 

Allthough I've never seen a note posted to this effect, If I walked in off
the street into the office up front in this building and started loading
office supplies into a hand cart and roll them out the door; Secretaries,
salespeople, the shipping guy, would come piling out of the spaces and stop
me. Nobody put that in there job description, or has to.

By making some catagories of messaging a chargable cost, and making sure
somebody has to pay; (easiest as an anonymous cost up front), now everyone
in the cost pipeline has something to gain and lose with enforcement.

Its easy to visualize this. the MTA's look at a MIME type field and its a
very large prime number. Its forwarded to an agency or heirarchy of
agencies. They return a go/no-go message (UDP probably). If the number is
already used, the message declines it and the message is aborted from
delivery; (or just downgrades to free). If its accepted, the factors are
return and the software verifies it by multiplying them. Having the factors
on file proves the identity of the agency. Each handoff offers the MTA a new
prime. Only the first is chargable. Any MTA can downgrade a message to free,
(or upgrade it with a top level seeded prime). This works right down to a
home box type MTA, like a POP3 program. Subsideary primes have a mappable
relation to the seed ones; (doesn't matter what it is. As long as the
relation can be detmined).

MTA's which do not cooperate in the scheme incur no cost, and add or lose no
value to themselves or anyone else. No message status changes. Some may
encounter MTA's elsewhere in the system to modify that, but there is no red
flag day at all.

It involves trust of only one agency at the top of the heirarchy. You have
to trust them to want old fashioned, hard currency, money. I can refer you
to a number of personal aquiaintances with that characteristic, (if you do
not know people of that ilk).

regards,
Dan






From owner-ietf@ietf.org  Fri Feb 13 14:38:22 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28123
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 14:38:22 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Arj1r-00029H-KV
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 14:31:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Arj0s-00027m-V0
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 14:30:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27614
	for <ietf@ietf.org>; Fri, 13 Feb 2004 14:30:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arj0r-0001WY-00
	for ietf@ietf.org; Fri, 13 Feb 2004 14:30:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Arizz-0001Sd-00
	for ietf@ietf.org; Fri, 13 Feb 2004 14:29:15 -0500
Received: from mail-red.research.att.com ([192.20.225.110] helo=mail-white.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ariz5-0001KE-00
	for ietf@ietf.org; Fri, 13 Feb 2004 14:28:19 -0500
Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.30.103])
	by mail-white.research.att.com (Postfix) with ESMTP id A9484664121
	for <ietf@ietf.org>; Fri, 13 Feb 2004 14:26:36 -0500 (EST)
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-green.research.att.com (Postfix) with ESMTP id 375F9F3A91
	for <ietf@ietf.org>; Fri, 13 Feb 2004 14:24:14 -0500 (EST)
Received: from berkshire.research.att.com (sigaba.research.att.com [135.207.23.169])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id i1DJRmZ24286
	for <ietf@ietf.org>; Fri, 13 Feb 2004 14:27:48 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP id C21DF7B43
	for <ietf@ietf.org>; Fri, 13 Feb 2004 14:27:48 -0500 (EST)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
From: Steve Bellovin <smb@research.att.com>
To: ietf@ietf.org
Subject: a better way to charge for spam
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 13 Feb 2004 14:27:48 -0500
Message-Id: <20040213192748.C21DF7B43@berkshire.research.att.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Let me point folks at a paper written by a colleague of mine, Bala 
Krishnamurthy, on a better charging scheme.  It uses contingent 
liability -- that is, you only pay afterwards if someone thinks you 
sent spam.  See http://www.research.att.com/~bala/papers/shred-ext.ps
(or .pdf)


		--Steve Bellovin, http://www.research.att.com/~smb





From owner-ietf@ietf.org  Fri Feb 13 17:04:02 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09882
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 17:04:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Arl9H-0007vO-5X
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 16:46:59 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Arl3j-0006Df-EO
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 16:41:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07937
	for <ietf@ietf.org>; Fri, 13 Feb 2004 16:41:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arl3h-0007AC-00
	for ietf@ietf.org; Fri, 13 Feb 2004 16:41:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Arl2k-000725-00
	for ietf@ietf.org; Fri, 13 Feb 2004 16:40:14 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arl1p-0006mV-00
	for ietf@ietf.org; Fri, 13 Feb 2004 16:39:18 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1DLceko025707
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 13 Feb 2004 16:38:46 -0500
Date: Fri, 13 Feb 2004 16:38:40 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Dan Kolis <dank@hq.lindsayelec.com>
cc: ietf@ietf.org
Subject: Re: Multiplication, specifically large numbers by small ones
In-Reply-To: <20040212224426944.AAA601@hq.lindsayelec.com@rflooker1>
Message-ID: <Pine.LNX.4.44.0402131623190.25086-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 12 Feb 2004, Dan Kolis wrote:

> Dan says:
> Well, I have never gotten an unsolicited paper item for Viagra, but have
> gotten hundreds of electronic ones. There is a distinction between
> unsolicited communications, direct marketing, and spam. Its subtle and
> creates (in the US) first amendment rights issues that are non-trivial.
> 
> But, 100M email mass solicitation at $0.001 each is $100K, which is a medium
> good houseworth of dollar value here. I think it would annihlate the worst
> of mass spam.

If you could charge it to the abusers, it might. The problem, as I pointed 
out, is that you cannot charge it to the abusers.  You can only charge the 
innocent.

> I think whoever thought up the idea should be identified as a pretty sharp
> cookie. Its just slices through so many thorny issues with few downsides.

They are a sharp cookie, alright. Wish I had thought of it. Except, that
it won't have any impact on spam, but will make the person collecting fee
commissions very rich.  Hmm. Could it possibly be a purely economic 
motiviation by a certain group?  Nah. 

> Of course, if absolutely no one responded to spam the incentive wouldn't be
> there to send it. So maybe we just need more time for young people .... Hey!
> There is a guy in Nigeria who wants to give me two million dollars. Gotta go!

This is another myth. The worst of the worst spam isn't responded to.  
I've tried a number of times to purchase Viagra from spammers, assuming
that since Viagra is a prescription drug, and I don't have a prescription,
I could complain to the authorities.  So far, while I've seen some
reasonably complete-looking websites, no one has even charged my credit
card--a debit card with very little money in the account, but enough to
cover the Viagra.  Why send the spam if you aren't go to charge the credit
card?  It wasn't even the case that they tried rip off the money, and send
nothing...  For spammers, they are pretty honest, except for the lying
part.

I also tried responding immediately to 20 of the Nigeria scam spams. No
one has tried to solicit personal information, and the one (and only)
response I did get just said the address was forged.  So what's up when
even the scams aren't really the scams they appear to be?

Now we have statistics that the top 95 genuine spammers are mostly in 
compliance, yet the junk in my emailbox is not even partially in 
compliance. How do that work out?

		--Dean




From owner-ietf@ietf.org  Fri Feb 13 18:07:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13118
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 18:07:29 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Arm8R-0003Av-VX
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 17:50:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Arm7d-00037V-Vu
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 17:49:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12138
	for <ietf@ietf.org>; Fri, 13 Feb 2004 17:49:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arm7c-0005e7-00
	for ietf@ietf.org; Fri, 13 Feb 2004 17:49:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Arm6i-0005a0-00
	for ietf@ietf.org; Fri, 13 Feb 2004 17:48:24 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arm5v-0005RV-00
	for ietf@ietf.org; Fri, 13 Feb 2004 17:47:35 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 1979461BAC
	for <ietf@ietf.org>; Fri, 13 Feb 2004 23:47:05 +0100 (CET)
Date: Fri, 13 Feb 2004 14:46:49 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Visa letters - next to last chapter....?
Message-ID: <284997735.1076683609@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Some glitch at the secretariat has led to the letters Gene Gaines has been 
so helpful in procuring not being posted to the Web before the weekend.

As an interim measure, I have posted them to my personal web site.

Look at http://www.alvestrand.no/ietf/korean-visa.html

Take care!

                Harald Alvestrand




From owner-ietf@ietf.org  Fri Feb 13 18:09:59 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13395
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 18:09:59 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArmNu-0003ok-56
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 18:06:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ArmKE-0003fr-H4
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 18:02:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12639
	for <ietf@ietf.org>; Fri, 13 Feb 2004 18:02:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArmKB-0006dW-00
	for ietf@ietf.org; Fri, 13 Feb 2004 18:02:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArmJ9-0006Yx-00
	for ietf@ietf.org; Fri, 13 Feb 2004 18:01:16 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArmIK-0006RC-00
	for ietf@ietf.org; Fri, 13 Feb 2004 18:00:24 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1DMxdqj027227
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 13 Feb 2004 17:59:50 -0500
Date: Fri, 13 Feb 2004 17:59:39 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Ed Gerck <egerck@nma.com>
cc: Franck Martin <franck@sopac.org>, John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: proposal for built-in spam burden & email privacy protection
In-Reply-To: <402C1E4D.3CFD581@nma.com>
Message-ID: <Pine.LNX.4.44.0402131644370.25086-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 12 Feb 2004, Ed Gerck wrote:

> > You can't make it more expensive without shooting yourself in the foot.
> > In information theory-speak, you can't prevent a covert channel** unless
> > you have no channel at all.  
> 
> By the addition of a correction channel (Shannon's 10th theorem),
> a covert channel can be detected with a probability as close to 100%
> as I wish.

Err, I think that allows you to correct _errors_ in transmission. It does
not enable detection or prevention of a covert or sneaky channel. While
there have been examples of sneaky channels that used intentional errors
in a channel as the sneaky channel, error correction does not prevent or
detect the covert channel, unless of course, the errors are corrected
before they can be seen by the user of the sneaky channel. Otherwise, you
do not know if the errors are intentional and carry information, or
whether they are just errors. 

What's that?  You say that one could study the errors, and if the bits are
not random, perhaps you have detected a covert channel.  A good encryption
mechanism will assure a random distribution of bits, and so you would be
unable to distinguish from just random errors.  There are other means of
creating covert channels besides introducing errors.

> > Covert-channel detection is a whack-a-mole game. 
> 
> Not really. It can be modeled, it can be improved.

I agree that it can be modeled, and that we can learn things by the
effort. I've seen some interesting reading on modeling the bandwidth
potentially available to a covert channel.  This doesn't prevent the
existance of a covert channel, nor does it change the whack-a-mole nature
of the problem.  You still have to detect and respond.

But knowing the potential bandwidth in some situations might help you to
harrass the bad guys. Or focus your detection efforts, since the bandwidth
available may put constraints on the bad guys, and knowing those
constraints may yeild some insights.  In this case, I think the bandwidth 
available to a large number of virus-infected computers is quite 
substantial, as is the compute power.

> > Putting it in different terms, how can the government make sure those
> > "government use only" stamped envelopes are only used for government
> > business? 
> 
> Easy. By applying Shannon's 10th theorem. Sample enough mail at
> distribution centers (going back to the source, which is possible
> even without a legal mandate to open the  envelopes) and bar the 
> culprits from sending govt. mail until the probability that any 
> mail is incorrectly using govt. envelopes is a close to zero as desired.

Unfortunately, you described a detection mechanism:  Whack-a-mole.  
Indeed, I think this is exactly what the government does to detect abuse.  
And it is basically the same thing we do now for email by applying text
analysis.

But we are looking for (and you promised) a mechanism which makes it
impossible for them send it in the first place:  No more whack-a-mole.

Clearly, in the sampling example, they can use invisible ink to fool the
censors, or write their messages in an ordinary looking code that looks
like official business (steganography).  The error correction theroem
doesn't help.  This example isn't nearly as hypothetical as it sounds. The
US [and other governments] really used to open international mail to look
for secret messages. We used to also test letters for the presence of a
number of invisible inks. The Germans invented an invisible ink that was
inpervious to testing for a long time.  The US censors would even re-write
personal letters using slightly different words to preclude the use of
special code words.  Then came micro-dots and so forth.  Each channel
detected led to the creation of new channels (either different people,
same method, or new methods) within the postal mail system.  But it did
not lead to any situation in which sneaky channels were impossible.

> > There is no scheme in which the rules can't be broken by someone intent on
> > breaking them. 
> 
> This may sound good but is incorrect. Systems can be designed
> such that a set of properties remain effective if most or even 
> all parts of the system fail (for whatever reason, including
> attacks).

Fault tolerance doesn't seem to be helpful.  To design a system that can't
send spam, you have to first identify the properties of spam in such a way
that a person dedicated to breaking the rules would be prevented from
sending spam.  Information theory tells us that such a goal is impossible
to obtain when it tells us that a covert channel can't be proven not to
exist.

> > The only path is to detect them, and prosecute them.  
> 
> There is no world law, no unified way to prosecute. Even
> venue is hard to guarantee (allowing you to  prosecute
> the culprit).

This isn't quite true.

> > In the case of spam, detection is easy, but not automatic.  
> > Prosecution is now possible.  Its still a whack-a-mole game. It won't
> > end unless you can get past the virus infection to the virus operator,
> > and hopefully, there aren't really too many virus operators.  Of
> > course, we aren't stopping spam either in a very real sense, but
> > rather abusers who are annoying and mailbombing people.  But by my
> > count of my inbox, if you stop those people, I can certainly handle
> > the rest which amounts to maybe 1% of my current junk mail.
> 
> When you outlaw spam, only the outlaws spam. So what? The
> problem still remains, even if you call them outlaws. 

Actually, genuine spam is not outlawed. Only the spam sent by people who 
are not genuine businesses is outlawed. I expect that this abuse is sent 
by a very small group of people.  Prosecuting this small group should be 
relatively easy.

> Also, users should not have to sue spammers, or have any other burden,
> in order to protect the users' resources. Imagine if I would have to
> manage 300 lawsuits a day (the average spam rate that my system cannot
> automatically detect as spam)?

This is an exaggeration. There aren't 300 unique spammers per internet
user per day.

		--Dean




From owner-ietf@ietf.org  Fri Feb 13 19:46:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17390
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 19:46:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Arnow-0001Qe-18
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 19:38:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Arno6-0001Lv-J3
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 19:37:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17004
	for <ietf@ietf.org>; Fri, 13 Feb 2004 19:37:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arno5-0005Vs-00
	for ietf@ietf.org; Fri, 13 Feb 2004 19:37:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Arnn7-0005Sd-00
	for ietf@ietf.org; Fri, 13 Feb 2004 19:36:18 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arnml-0005Pg-00
	for ietf@ietf.org; Fri, 13 Feb 2004 19:35:55 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 3E1F661B83; Sat, 14 Feb 2004 01:35:24 +0100 (CET)
Date: Fri, 13 Feb 2004 16:28:32 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: ietf@ietf.org
Subject: Re: Continuing the story - another stab at an IETF mission
 statement
Message-ID: <291101291.1076689712@localhost>
In-Reply-To: <BC71D992-5E10-11D8-B0DB-000A95CD987A@muada.com>
References: <21987296.1076420595@localhost>
 <BC71D992-5E10-11D8-B0DB-000A95CD987A@muada.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 13. februar 2004 11:38 +0100 Iljitsch van Beijnum <iljitsch@muada.com> 
wrote:

> On 10-feb-04, at 22:43, Harald Tveit Alvestrand wrote:
>
>> I attempted to incorporate the latest discussions into an
>> internet-draft, which I managed to get out just before the
>> deadline....
>
>>   draft-alvestrand-ietf-mission-00.txt
>
> Good stuff.
>
> But wouldn't it be useful to say something about the global nature of the
> internet and the IETF body of participants, and how this influences both
> the IETF's goals and the way it carries out its activities?
>
> More specifically, the fact that the IETF exclusively uses English for
> its standards and internal processes creates a non-level participation
> field, but at the same time the use of a single, widely-spoken language
> allows for much lower costs and higher efficiency than any alternative.

Good point. At least to make the point that the IETF sees the Internet as a 
global phenomenon, and that its standards-setting therefore must be global 
too - with English chosen for its utility, not its affiliation.
Suggestions on which sections to put it in?





From owner-ietf@ietf.org  Fri Feb 13 20:33:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18731
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 20:33:07 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AroWV-0004Kg-OW
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 20:23:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AroVg-0004Gu-4Y
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 20:22:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18322
	for <ietf@ietf.org>; Fri, 13 Feb 2004 20:22:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AroVe-0000i8-00
	for ietf@ietf.org; Fri, 13 Feb 2004 20:22:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AroUi-0000e0-00
	for ietf@ietf.org; Fri, 13 Feb 2004 20:21:21 -0500
Received: from mail8.atl.registeredsite.com ([64.224.219.82] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AroUD-0000ax-00
	for ietf@ietf.org; Fri, 13 Feb 2004 20:20:49 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail8.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1E1Kgjf017738;
	Fri, 13 Feb 2004 20:20:42 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Fri, 13 Feb 2004 19:20:39 -0600
Message-ID: <402D77E4.801C6D40@nma.com>
Date: Fri, 13 Feb 2004 17:20:36 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Robert G. Brown" <rgb@phy.duke.edu>
CC: Dean Anderson <dean@av8.com>, ietf@ietf.org
Subject: Re: going off-list, Re: proposal for built-in spam burden & 
 emailprivacy  protection
References: <Pine.LNX.4.44.0402130808040.1291-100000@lilith.rgb.private.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"Robert G. Brown" wrote:
> 
> Currently, email addresses are relatively "simple" objects and as such
> are easy enough to remember (for humans) and communicate (for humans).
> You propose to make an address a "complex" object: the simple address
> plus kilobyte-sized blocks of text or binary data such as:
> 
> -----BEGIN PGP PUBLIC KEY BLOCK-----
> Version: GnuPG v1.0.7 (GNU/Linux)
> 
> mQGiBDprOxURBADW+ybmMpoBfbRADv3OzXaaIQVWGDoaNsR4uxstcJgo+FYMcO9B
> Ag7eXRLfOQFPPS3211W/f1/GaQa70ZaPZaQV/A9POIGfRIbcfePHaIUUXYulO3Nh
> Bqewb5JZjzkj0yZWdjzK/OSBEPITXMXyTDVnG0+Y4YHHLDOODnnkSOlZKwCg453O
> ....(much much more)

The key can be given by:

1. return mail requesting an encrypted message with the
attached key (as I wrote in my first posting on this suggestion),

2. key server, by using an URL

3. by searching google

4. by using DNS records

5. by reading the email's signature line when my mail reaches you
and you want to reply to me.

So, there are many, simple and automatic ways for PK distribution.
PK certification is another thing, but encryption does not it.

Also, humans have been using complex postal addresses for centuries,
without even the benefit of computers to help with them until quite
recently. Complexity is in the eyes of the beholder.

 
 
> On the other hand, this additional degree of complexity will be a
> horrible burden in time, energy, and money to ordinary users of mail at
> every level and especially to systems administrators responsible for
> training those users and de facto responsible for managing the data
> problem the composite "address" object would represent.  Communicating,
> managing, and remembering email addresses like "joe@whereever.edu" is
> already "challenging" to many, if not most, users of email and is
> obviously equally challenging at the corporate/professional level.  Let
> us recall that most current AV software is still stupid enough to
> consider the From address to actually be valid for viruses and SPAM and
> cannot even manage to parse the real message header in sensible ways.
> Now visualize these same bozos trying to deal with messages whose header
> contains a 1-2K key:-/

This will all require a level of automation and user-friendliness way
above what we have today. Nonetheless, possible and necessary if
we want to (1) preserve email confidentiality and (2) provide an even
mandatory burden to sending email.

On the flip side, I can see all your arguments above applying to
the difficulty of sending spam -- in addition to the time burden.


> Obviously, people will no longer be able to just say "here's my email
> address". 

Not true. After you send an email and you'd get a bounce requesting an
encrypted message, with the public-key included. In fact, you can 
easily use your email as a way to distribute your PK with the benefit 
of challenge-response -- if your email is active, the sender gets the 
current key for that address. You can also use it to update your PK, 
easily.

>  Business cards will need to be roughly 4x6" and covered
> mostly in small type.  Most users will simply rebel.  Most systems
> people will simply rebel.  

:-) not really...see above.

> People CAN send encrypted, signed email now,
> but how many do? 

5%. The failure is actually ours, not making it easy to use. Just ask
any email user...How do they feel when they understand that email 
is really like a postcard... open for anyone to read? How do they
feel about spammers having near zero cost to send them messages
while they need to use valuable time and resources to weed them out?
 
> You are also suggesting that the encryption step, by being "expensive"
> computationally, will at least slow down the spammers.  This assertion,
> which has been made several times now, is simply not true. 
> [snip, good comments]

The point is that it CAN be made very expensive for sending 100,000s
of emails. In addition to the PK encryption of the random symm key
used to encrypt the message (in PGP, for example) you can also add 
the recipient's PK MACs to tie the recipient's PK to the message as 
well. Further, the proposal should include "puzzles" to be solved
by the sender (a la hashcash) that can penalize an unknown sender as
much as desired and trickle its output as much as needed.
 
Users can also require less burdensome encryption from known parties,
without "puzzles".

There is nothing to prevent a spammer -- as an entity with NO previous 
relationship to the receiver -- to be penalized at will, while known 
users mail send messages with regular encryption or even no encryption 
at all (by using whitelists).

I'm thus led to the opposite conclusion that you suggest: I think 
that it is clear that this proposal can have a significant
impact on SPAM generation, while but it will not have any, or  hardly
any, negative impact on ordinary mail users.



From owner-ietf@ietf.org  Fri Feb 13 21:10:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20074
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 21:10:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Arp8D-0006yr-BJ
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 21:02:09 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Arp7S-0006vI-6Q
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 21:01:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19660
	for <ietf@ietf.org>; Fri, 13 Feb 2004 21:01:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arp7Q-0003Wk-00
	for ietf@ietf.org; Fri, 13 Feb 2004 21:01:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Arp6V-0003Tk-00
	for ietf@ietf.org; Fri, 13 Feb 2004 21:00:24 -0500
Received: from mail1.asianet.co.th ([203.144.222.229] helo=mail.asianet.co.th)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arp5w-0003Mj-00
	for ietf@ietf.org; Fri, 13 Feb 2004 20:59:48 -0500
Received: from virscan2.asianet.co.th (HELO mail.asianet.co.th) ([203.144.222.198])
          (envelope-sender <jrace@attglobal.net>)
          by mail1.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 14 Feb 2004 08:59:09 +0700
Received: from ppp-210.86.177.114.revip.asianet.co.th (HELO localhost) ([210.86.177.114])
          (envelope-sender <jrace@attglobal.net>)
          by mx3.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 14 Feb 2004 08:59:08 +0700
From: "Dr. Jeffrey Race" <jrace@attglobal.net>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Sat, 14 Feb 2004 08:59:08 +0700
Reply-To: "Dr. Jeffrey Race" <jrace@attglobal.net>
X-Mailer: PMMail 1.96a For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: Primal urges in the can-the-spam movement
Message-Id: <E1Arp5w-0003Mj-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,NO_COST,TO_ADDRESS_EQ_REAL 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

It is a pleasure to see someone bringing common sense about human
behavior to the discussion, but I dread seeing another proposal like
this, which entails a new technical mechanism which the victims have
to pay to establish.    Society has dealt with problems comparable
to spam for at least five thousand years, and the mechanisms for
dealing with antisocial behavior are quite simple to understand and
implement.   There is no need for additional complex technical mechanisms
(though anything enhancing traceability is desirable).  Just apply to
the internet the mechanisms which are used everywhere else in society
to deal (successfully) with comparable problems.

 See <http://www.camblab.com/misc/univ_std.txt>

   based on

     <http://www.camblab.com/nugget/spam_03.pdf>

Jeffrey Race

On Fri, 13 Feb 2004 13:46:05 -0500, Dan Kolis wrote:
>Dan says:
>If I follows Roberts scenerios, he visualizes ways to own things like MTA's,
>etc and evade the cost per by magnitudes.
>
>Generally, as the second fragment of text describes, Robert's suggesting
>catch-me-if-you-can enforcement is the way to go.
>
>If that's a logical mode, IETF can possibly see a mandate to tighten
>technology to find our true sources of messages, packets, etc. Generally,
>like MPLS, and 802.11b, the trend is moving slowly the other way.
>
>I think instead of detailed calculations, an observation which might seem
>familiar to economists is closer to the issue. 
>
>If you expect people paid to enforce things to do it, they will always Jones
>for more people and resources, and probably no enforcement in the world
>accounts for capturing more than some ones of percents of undesired
>activity. Like any community, there will always be a "crisis" or some
>description requirement more of: everything. Cooperation, legal scope,
>education, and of course always more money. This constitutes part of the
>noise level that degrades much of modern life. (Like the incredible
>competition to have the most interesting possible up and coming new disease,
>mental problem or crime).
>
>On the other hand, we all have a vested interest in watching the eggs in our
>basket. 
>
>Allthough I've never seen a note posted to this effect, If I walked in off
>the street into the office up front in this building and started loading
>office supplies into a hand cart and roll them out the door; Secretaries,
>salespeople, the shipping guy, would come piling out of the spaces and stop
>me. Nobody put that in there job description, or has to.
>
>By making some catagories of messaging a chargable cost, and making sure
>somebody has to pay; (easiest as an anonymous cost up front), now everyone
>in the cost pipeline has something to gain and lose with enforcement.
>
>Its easy to visualize this. the MTA's look at a MIME type field and its a
>very large prime number. Its forwarded to an agency or heirarchy of
>agencies. They return a go/no-go message (UDP probably). If the number is
>already used, the message declines it and the message is aborted from
>delivery; (or just downgrades to free). If its accepted, the factors are
>return and the software verifies it by multiplying them. Having the factors
>on file proves the identity of the agency. Each handoff offers the MTA a new
>prime. Only the first is chargable. Any MTA can downgrade a message to free,
>(or upgrade it with a top level seeded prime). This works right down to a
>home box type MTA, like a POP3 program. Subsideary primes have a mappable
>relation to the seed ones; (doesn't matter what it is. As long as the
>relation can be detmined).
>
>MTA's which do not cooperate in the scheme incur no cost, and add or lose no
>value to themselves or anyone else. No message status changes. Some may
>encounter MTA's elsewhere in the system to modify that, but there is no red
>flag day at all.
>
>It involves trust of only one agency at the top of the heirarchy. You have
>to trust them to want old fashioned, hard currency, money. I can refer you
>to a number of personal aquiaintances with that characteristic, (if you do
>not know people of that ilk).




From owner-ietf@ietf.org  Fri Feb 13 21:58:40 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20076
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 21:10:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArpB9-0007B2-U5
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 21:05:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ArpAQ-00077C-T5
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 21:04:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19800
	for <ietf@ietf.org>; Fri, 13 Feb 2004 21:04:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArpAJ-0003iw-00
	for ietf@ietf.org; Fri, 13 Feb 2004 21:04:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Arp9P-0003eB-00
	for ietf@ietf.org; Fri, 13 Feb 2004 21:03:24 -0500
Received: from mail6.atl.registeredsite.com ([64.224.219.80] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arp8S-0003af-00
	for ietf@ietf.org; Fri, 13 Feb 2004 21:02:24 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail6.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1E32NP1027224;
	Fri, 13 Feb 2004 22:02:23 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Fri, 13 Feb 2004 20:02:17 -0600
Message-ID: <402D81A5.8199DD4D@nma.com>
Date: Fri, 13 Feb 2004 18:02:13 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: Franck Martin <franck@sopac.org>, John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: proposal for built-in spam burden & email privacy protection
References: <Pine.LNX.4.44.0402131644370.25086-100000@cirrus.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Dean Anderson wrote:
> 
> On Thu, 12 Feb 2004, Ed Gerck wrote:
> 
> > > You can't make it more expensive without shooting yourself in the foot.
> > > In information theory-speak, you can't prevent a covert channel** unless
> > > you have no channel at all.
> >
> > By the addition of a correction channel (Shannon's 10th theorem),
> > a covert channel can be detected with a probability as close to 100%
> > as I wish.
> 
> Err, I think that allows you to correct _errors_ in transmission. 

Shannon distinguished messages --or intended information-- from noise. 
The distinction beween noise and information is that information is
what the sender wants to send or, alternatively, what the receiver
wants to receive. If the channel is a covert channel, it is fair to
assume that either the sender or the receiver (or both) do not intend
it to exist (otherwise, it would not be a covert channel). Thus, a 
covert channel transmits information that can be considered for modeling purposes as a source of noise. Since the 10th theorem applies to any 
source of noise, it also applies here. 

The devil are in the details, though. The 10th theorem does not
tell you how to do it -- just that it is possible and that the
noise (covert channel information) can be detected with a probability
as close to 100% as desired.

> > Easy. By applying Shannon's 10th theorem. Sample enough mail at
> > distribution centers (going back to the source, which is possible
> > even without a legal mandate to open the  envelopes) and bar the
> > culprits from sending govt. mail until the probability that any
> > mail is incorrectly using govt. envelopes is a close to zero as desired.
> 
> Unfortunately, you described a detection mechanism:  Whack-a-mole.

Actually, I described a detection AND a correction mechanism. The 
correction mechanism uses a correction channel as given by the 10th
theorem. BTW, just sampling 1% of mail might be enough to prevent 
misuse to almost 100% confidence.

> But we are looking for (and you promised) a mechanism which makes it
> impossible for them send it in the first place:  No more whack-a-mole.

The "impossible" promised by Shannon's 10th theorem is "probability
as close to zero as you wish". That's what I also promised and 
delivered. It should be good enough for you ;-)
 
> Clearly, in the sampling example, they can use invisible ink to fool the
> censors, or write their messages in an ordinary looking code that looks
> like official business (steganography).  

Either can be detected, and corrected. If you are following the whole
DRM and music copyright issue, you have many examples why steganography
is at most a deterrent, not a secure technique.

> This example isn't nearly as hypothetical as it sounds. The
> US [and other governments] really used to open international mail to look
> for secret messages. We used to also test letters for the presence of a
> number of invisible inks. The Germans invented an invisible ink that was
> inpervious to testing for a long time.  The US censors would even re-write
> personal letters using slightly different words to preclude the use of
> special code words.  Then came micro-dots and so forth.  Each channel
> detected led to the creation of new channels (either different people,
> same method, or new methods) within the postal mail system.  But it did
> not lead to any situation in which sneaky channels were impossible.

Your examples actually show how a correction channel can work. Your 
argument that a sneaky channel is still possible is also included in
Shannon's 10th theorem -- the correction channel needs to have a larger
capacity than the noise channel. If you have an unaccounted-for 
noise channel (e.g., a covert channel), your system is still not good
enough.

> Fault tolerance doesn't seem to be helpful.  To design a system that can't
> send spam, 

This is not our goal -- the problem is at the receiving end, since the 
sending end can use anything (even non-conformant systems). The issue 
in the proposal is to design a system where *receiving* spamm can
be made as hard as the recipient wants.

> you have to first identify the properties of spam in such a way
> that a person dedicated to breaking the rules would be prevented from
> sending spam.  Information theory tells us that such a goal is impossible
> to obtain when it tells us that a covert channel can't be proven not to
> exist.

When the recipient detects a spam message, the existence of at least one
covert channel is exposed. As I envision the proposal, the recipient should
be in control of how to react -- since different users will have different
goals. For example, according the number of spam messages received, the 
recipient can be more or less demanding on the sender of ANY message for 
senders without a previous relationship. Thus, the sender can be reduce the 
covert channel's capacity as much as the recipient wants.
 
> > When you outlaw spam, only the outlaws spam. So what? The
> > problem still remains, even if you call them outlaws.
> 
> Actually, genuine spam is not outlawed. 

It depends how you define spam. Genuine "spammers" would quibble
with you calling them spammers. I'd call them email senders.

> Only the spam sent by people who
> are not genuine businesses is outlawed. 

Not true. If a genuine business continues to send me messages
after I unsub, it is spam. The classification of spam is not
based on who sends the message. 

> I expect that this abuse is sent
> by a very small group of people.  Prosecuting this small group should be
> relatively easy.

It has not been and it will only get worse.


> > Also, users should not have to sue spammers, or have any other burden,
> > in order to protect the users' resources. Imagine if I would have to
> > manage 300 lawsuits a day (the average spam rate that my system cannot
> > automatically detect as spam)?
> 
> This is an exaggeration. There aren't 300 unique spammers per internet
> user per day.

Agreed  -- it's an understatement. I believe there are perhaps
1000x 300 unique spammers per day. Some I don't hear from (they're
local -- for example -- for Korean readers), some are in burst mode
and I only hear them once in a while, some morph under different
names and hosts, some I blacklist, some I detect and some I drop.



From owner-ietf@ietf.org  Fri Feb 13 23:25:38 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23621
	for <ietf-archive@odin.ietf.org>; Fri, 13 Feb 2004 23:25:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArrDv-0007s9-8Q
	for ietf-list@asgard.ietf.org; Fri, 13 Feb 2004 23:16:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ArrDK-0007o0-Un
	for ietf@asgard.ietf.org; Fri, 13 Feb 2004 23:15:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23445
	for <ietf@ietf.org>; Fri, 13 Feb 2004 23:15:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArrDI-0004cP-00
	for ietf@ietf.org; Fri, 13 Feb 2004 23:15:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArrCP-0004Zi-00
	for ietf@ietf.org; Fri, 13 Feb 2004 23:14:38 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArrBn-0004Vq-00
	for ietf@ietf.org; Fri, 13 Feb 2004 23:13:59 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1E4DID0000842
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 13 Feb 2004 23:13:23 -0500
Date: Fri, 13 Feb 2004 23:13:18 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Ed Gerck <egerck@nma.com>
cc: "Robert G. Brown" <rgb@phy.duke.edu>, <ietf@ietf.org>
Subject: Re: proposal for built-in spam burden &  emailprivacy  protection
In-Reply-To: <402D77E4.801C6D40@nma.com>
Message-ID: <Pine.LNX.4.44.0402132301290.385-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I guess this didn't make it off list...

On Fri, 13 Feb 2004, Ed Gerck wrote:

> Not true. After you send an email and you'd get a bounce requesting an
> encrypted message, with the public-key included. 

Actually, there are already a couple systems that work like this.  
Qsecretary is one.  If I recall, someone is trying to patent this, even
though as a scheme, its been around since majordomo, or longer.  It
doesn't work well in a number of situations. I think if qsecretary sees
another qsecretary bounce, it can do the right thing (not positive about
that---Dan?).  But there is no guarentee that two different
bounce/responder systems will work correctly.  These systems also fail
with agents.

Eg, How does my voip gateway email me my phone messages?  What about my
Network management software? I want an email saying my customer just went
down.  How does my pager handle all of this?

Agents are becoming more and more pervasive. No doubt my microwave will
soon email me that my popcorn is ready, and my oven will tell me when to 
baste the turkey, and my car will email me when its time for service.

These things work ok in small close knit groups, but don't scale well.  
The fact that they don't scale is what makes them useful to the small
group. If you solve the agent/scaling problem, you solve the spammers
problem, too, and the usefullness is lost.

		--Dean





From owner-ietf@ietf.org  Sat Feb 14 01:19:53 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25840
	for <ietf-archive@odin.ietf.org>; Sat, 14 Feb 2004 01:19:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ArsxH-0006PI-Ov
	for ietf-list@asgard.ietf.org; Sat, 14 Feb 2004 01:07:07 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Arstm-0006En-KL
	for ietf@asgard.ietf.org; Sat, 14 Feb 2004 01:03:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25683
	for <ietf@ietf.org>; Sat, 14 Feb 2004 01:03:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Arstk-0003KK-00
	for ietf@ietf.org; Sat, 14 Feb 2004 01:03:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Arssn-0003HE-00
	for ietf@ietf.org; Sat, 14 Feb 2004 01:02:30 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArssZ-0003Dx-00
	for ietf@ietf.org; Sat, 14 Feb 2004 01:02:15 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1E61gUq003017
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sat, 14 Feb 2004 01:01:42 -0500
Date: Sat, 14 Feb 2004 01:01:42 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Ed Gerck <egerck@nma.com>
cc: Franck Martin <franck@sopac.org>, John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: proposal for built-in spam burden & email privacy protection
In-Reply-To: <402D81A5.8199DD4D@nma.com>
Message-ID: <Pine.LNX.4.44.0402132314000.385-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

This should be particularly interesting for John Klensin, as it is really
a follow-on to discussion last summer on the topic of information theory
and spam.

On Fri, 13 Feb 2004, Ed Gerck wrote:

> > Err, I think that allows you to correct _errors_ in transmission. 
> 
> Shannon distinguished messages --or intended information-- from noise.  
> The distinction beween noise and information is that information is what
> the sender wants to send or, alternatively, what the receiver wants to
> receive. If the channel is a covert channel, it is fair to assume that
> either the sender or the receiver (or both) do not intend it to exist
> (otherwise, it would not be a covert channel). Thus, a covert channel
> transmits information that can be considered for modeling purposes as a
> source of noise. Since the 10th theorem applies to any source of noise,
> it also applies here.

You are confusing a covert channel with noise. They aren't the same.  
Antispammers have commonly used an analogy that equates spam with noise
and anti-spam efforts as trying to find a "noise filter".  The analogy
sounds good, but is not accurate, which might suggest a reason why they
have failed to find a "filter".

Spam isn't unwanted until after the fact: You read it, and then you don't
like it.  Some people think AC/DC (or rock music in general) is "noise",
or commercials are "noise", but they aren't noise from the point of view
of information theory, and your real or theoretical radio won't be able
automatically filter them out when the DJ plays them, though it will do a
good job of filtering out noise.

You have to hear/read/see it, decide you don't like it, and complain about
it.  But you can't build a stereo that won't play rock music or won't play
commercials.  Perhaps, like the Janet Jackson Breast Baring (JJBB), the
station operator will agree with your complaint, and a fuss will be made
that won't cost you anthing, except taxes.  Spam is essentially the same
problem as preventing people from exposing themselves on TV. In a sense,
the problem is similar to NP-Complete problems because there are a whole
class of problems that are basically the same, and if you could solve one,
you could solve them all.

Getting back to information theory, Spam is information that the system
operator doesn't intend to be sent. It breaks the rules which say not to
send this kind of information. Spam (per the definition of a covert
channel) is simply a "communication not authorized by the security model".  
I should probably explain that spam is a multiplexed channel and identify
all the necessary parts relevant to information theory, but I think that
is fairly obvious, and unnecessary unless you dispute that spam is a
channel per the definitions of information theory. People have challenged
this, but infrequently. It seems you don't, so I'll skip it.

The definition of "covert channel" and the applicability of information
theory to spam was discussed on another (osf_alums) list last fall, and
some "very smart people" had some things to say about the definition of
covert channels in particular, which as I mentioned previously is a term
specificly used by OS scientists.  Some people thought it inappropriate to
use the term "covert channel" outside the context of operating system
analysis.  There are other terms used in other types of research, but they
all are rooted in information theory, and have the same very general
implications as a result:

On Fri, 8 Aug 2003, Ellis Cohen wrote:

> My 1976 paper on Strong Dependency (abridged in SOSP 5 in 1977) was (as
> far as I know) the first paper that applied classical information theory
> to problems of computer security (see
> http://citeseer.nj.nec.com/context/114449/0) and it contains the term
> "covert information path" (but I can't find "covert channel" used).  I
> might possibly even have been the first to use "covert" in the context
> of computer security, but I don't think so.  It's even possible I heard
> Lampson use it (or maybe it was the other way around ...)
> 
> Leo Rotenberg's excellent MIT thesis, "Making Computers Keep Secrets"
> was published  in Feb 1974.  He talks about "information leakage",   
> "sneaky signalling", "hidden data flows", and talks specifically about
> how communication channels (in particular, accounting channels -- that
> is, commuication channels used for billing) can be used to spy on data,
> but I can't find the word "covert" used anywhere.
>
> So it's possible that Lampson coined "covert channel" in 1978, but I
> suspect he might have used it earlier in his paper "A Note On the   
> Confinerment Problem" published in the CACM in 1973.
> 
> Citations seem to indicate that Lampson's deifnition of a covert channel
> was a channel "not intended for information transfer".  And I beleve I  
> remember that covert channels were used at that time to cover cases in  
> which there was no cooperation.  For example, suppose a spy can observe 
> the CPU usage of all programs on a computer which contains a top secret 
> program which is only run when an important secret event occurs.  Even  
> though there is no cooperation (just sloppy security), a covert channel 
> (access to the CPU usages) provides theinformation about when an
> important secret event occurs.
> 
>   -- Ellis Cohen

On Fri, 8 Aug 2003, Stavros Macrakis wrote:

> "Covert channel" has more than one definition.  In Lampson's original
> article, it referred to channels not intended for information transfer
> at all, and thus did NOT include information leaks via the billing
> system or via steganography.  If I read the NCSC's definition (below)
> correctly, it refers to ANY communication not authorized by the security
> model (which seems overly broad to me, but...).
>
> > I suspect [Lampson] might have used it earlier in his paper
> > "A Note On the Confinerment Problem" published in the CACM in 1973.
>
> A Note on the Confinement Problem
> Butler W. Lampson
> Xerox Palo Alto Research Center
> Comm. ACM 16, 10 (Oct. 1973)
>
> http://citeseer.nj.nec.com/lampson73note.html
>
> Even when all unauthorized access has been prevented,... [a service] may
> leak, i.e. transmit to its owner the input data which the customer gives
> it.
> ...
> The channels [in his examples] fall into three categories:
>
> * Storage of various kinds maintained by the supervisor which can be
> written by the service and read by an unconfined program, either shortly
> after it is written or at some later time.
>
> * Legitimate channels used by the confined service, such as the bill.
>
> * Covert channels, i.e. those not intended for information transfer at
> all, such as the service program's effect on the system load.
>
>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> NATIONAL COMPUTER SECURITY CENTER
> A GUIDE TO UNDERSTANDING COVERT CHANNEL ANALYSIS OF TRUSTED SYSTEMS
> November 1993
> http://www.radium.ncsc.mil/tpep/library/rainbow/NCSC-TG-030.html

The only solution so far is "detect and correct". Which, as noted, isn't a
very good solution, and we desire a solution that didn't have this
characteristic.


> Actually, I described a detection AND a correction mechanism. The 
> correction mechanism uses a correction channel as given by the 10th
> theorem. BTW, just sampling 1% of mail might be enough to prevent 
> misuse to almost 100% confidence.

It is still a "whack-a-mole" or "detect and correct" problem. It is not
impossible for someone to conduct abuse.  What sampling level you need to
have to assure a certain degree of compliance depends greatly on the
deterrence of the correction method. 

> > Actually, genuine spam is not outlawed. 
> 
> It depends how you define spam. Genuine "spammers" would quibble
> with you calling them spammers. I'd call them email senders.
> 
> > Only the spam sent by people who
> > are not genuine businesses is outlawed. 
> 
> Not true. If a genuine business continues to send me messages
> after I unsub, it is spam. The classification of spam is not
> based on who sends the message. 

This is a quibble, or you haven't read the CAN-SPAM act.

> > I expect that this abuse is sent
> > by a very small group of people.  Prosecuting this small group should be
> > relatively easy.
> 
> It has not been and it will only get worse.

Until last month, there were no tools to prosecute them, except for virus 
infection. And that isn't taken seriously unless there is fear that the 
virus caused a major power failure. But in that case, the virus sender is 
caught quickly and painlessly.

> > > Also, users should not have to sue spammers, or have any other burden,
> > > in order to protect the users' resources. Imagine if I would have to
> > > manage 300 lawsuits a day (the average spam rate that my system cannot
> > > automatically detect as spam)?
> > 
> > This is an exaggeration. There aren't 300 unique spammers per internet
> > user per day.
> 
> Agreed  -- it's an understatement. I believe there are perhaps
> 1000x 300 unique spammers per day. 

300,000 unique spammers each day, and only 6 billion people in the world.  
Gee only 20000 days until every one on the planet is a spammer. Yet
everyone on the planet doesn't even have email, telephone, or even TV. I
wonder if there will be anyone without these things in 50 years.  I heard
not too long ago that there are _only_ around 100 million on the net.  
Maybe its now up to 200 or 300 million.  So in 3 years, everyone that's on
the net will be a spammer.  Gee.  Maybe we better get moving on the IPv6.  
;-)










From qfuc00q@dkfz-heidelberg.de  Sat Feb 14 09:31:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18821
	for <ietf-archive@ietf.org>; Sat, 14 Feb 2004 09:31:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1As0pi-0000nf-00
	for ietf-archive@ietf.org; Sat, 14 Feb 2004 09:31:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1As0on-0000ka-00
	for ietf-archive@ietf.org; Sat, 14 Feb 2004 09:30:54 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1As0o5-0000gl-00; Sat, 14 Feb 2004 09:30:09 -0500
Received: from [24.108.169.59] (helo=65.246.255.50)
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1As0o5-0001Tr-Me; Sat, 14 Feb 2004 09:30:10 -0500
Received: from [175.138.16.248] by 65.246.255.50 SMTP id 0vaOXe709NdNTN; Sat, 14 Feb 2004 19:27:07 +0500
Message-ID: <sxy4x5v95-q527-qwf@qt2y2>
From: "Cecile Esparza" <qfuc00q@dkfz-heidelberg.de>
Reply-To: "Cecile Esparza" <qfuc00q@dkfz-heidelberg.de>
To: <ietf-123-outbound.01@ietf.org>, <ietf-123-outbound.02@ietf.org>,
        <ietf-action@ietf.org>, <ietf-admin@ietf.org>,
        <ietf-announce@ietf.org>, <ietf-approval@ietf.org>,
        <ietf-archive@ietf.org>
Subject: No website is required to cash in on profits from google.com
Date: Sat, 14 Feb 04 19:27:07 GMT
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="0AA0.E9063246C.2993"
X-Priority: 3
X-MSMail-Priority: Normal
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=25.0 required=5.0 tests=BIZ_TLD,DATE_IN_FUTURE_03_06,
	DATE_SPAMWARE_Y2K,FORGED_MUA_OIMO,FORGED_RCVD_NET_HELO,HTML_40_50,
	HTML_MESSAGE,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,MISSING_MIMEOLE,
	RCVD_NUMERIC_HELO,REMOVE_PAGE,SORTED_RECIPS,SUSPICIOUS_RECIPS 
	autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 RCVD_NUMERIC_HELO Received: contains a numeric HELO
	*  4.4 DATE_SPAMWARE_Y2K Date header uses unusual Y2K formatting
	*  0.5 HTML_40_50 BODY: Message is 40% to 50% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.8 REMOVE_PAGE URI: URL of page called "remove"
	*  0.8 BIZ_TLD URI: Contains a URL in the BIZ top-level domain
	*  2.8 DATE_IN_FUTURE_03_06 Date: is 3 to 6 hours after Received: date
	*  3.0 FORGED_RCVD_NET_HELO Host HELO'd using the wrong IP network
	*  3.0 SUSPICIOUS_RECIPS Similar addresses in recipient list
	*  4.3 SORTED_RECIPS Recipient list is sorted by address
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts
	*  2.7 FORGED_MUA_OIMO Forged mail pretending to be from MS Outlook IMO


--0AA0.E9063246C.2993
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<title>fsz u  ugxegjo pzgso  w v s  cl bljuht s ligament</title>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859=
-1">
</head>

<body>
<p>&nbsp;</p>
<p><a href=3D"http://www.globalmarketing2000.biz/cashinwithgoogle/">Cash 
  in with Google</a> makes earning an affiliate income very simple. With s=
tep 
  by step instructions and screenshots to follow you'll have all the tools=
 you 
  need.</p>
<p></p>
<p><font size=3D"2">no more <a href=3D"http://www.globalmarketing2000.biz/=
remove.html">emails</a> 
  please </font></p>
</body>
</html>
uvw   gl h
gxnprmoz
ypyp
pmx s

--0AA0.E9063246C.2993--



From owner-ietf@ietf.org  Sat Feb 14 12:51:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25079
	for <ietf-archive@odin.ietf.org>; Sat, 14 Feb 2004 12:51:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1As3h1-0005Pu-EQ
	for ietf-list@asgard.ietf.org; Sat, 14 Feb 2004 12:35:03 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1As3gp-0005Nl-6m
	for ietf@asgard.ietf.org; Sat, 14 Feb 2004 12:34:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24828
	for <ietf@ietf.org>; Sat, 14 Feb 2004 12:34:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1As3go-00040v-00
	for ietf@ietf.org; Sat, 14 Feb 2004 12:34:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1As3fu-0003yC-00
	for ietf@ietf.org; Sat, 14 Feb 2004 12:33:55 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1As3fE-0003v3-00
	for ietf@ietf.org; Sat, 14 Feb 2004 12:33:12 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1EHXZof098400;
	Sat, 14 Feb 2004 18:33:35 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <291101291.1076689712@localhost>
References: <21987296.1076420595@localhost> <BC71D992-5E10-11D8-B0DB-000A95CD987A@muada.com> <291101291.1076689712@localhost>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <D84D401C-5F13-11D8-B5AA-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Continuing the story - another stab at an IETF mission statement
Date: Sat, 14 Feb 2004 18:33:04 +0100
To: Harald Tveit Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 14-feb-04, at 1:28, Harald Tveit Alvestrand wrote:

> Good point. At least to make the point that the IETF sees the Internet 
> as a global phenomenon, and that its standards-setting therefore must 
> be global too - with English chosen for its utility, not its 
> affiliation.
> Suggestions on which sections to put it in?

4.1 "The Scope of the Internet" seems appropriate although this deals 
with other issues. Or maybe make it a separate item under 4.




From owner-ietf@ietf.org  Sat Feb 14 14:56:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28267
	for <ietf-archive@odin.ietf.org>; Sat, 14 Feb 2004 14:56:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1As5lj-00024R-5J
	for ietf-list@asgard.ietf.org; Sat, 14 Feb 2004 14:48:03 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1As5km-00022G-0C
	for ietf@asgard.ietf.org; Sat, 14 Feb 2004 14:47:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28132
	for <ietf@ietf.org>; Sat, 14 Feb 2004 14:47:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1As5kk-0005IS-00
	for ietf@ietf.org; Sat, 14 Feb 2004 14:47:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1As5jo-0005Ec-00
	for ietf@ietf.org; Sat, 14 Feb 2004 14:46:05 -0500
Received: from mail9.atl.registeredsite.com ([64.224.219.83] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1As5jZ-0005AZ-00
	for ietf@ietf.org; Sat, 14 Feb 2004 14:45:49 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail9.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1EKjkV4025847;
	Sat, 14 Feb 2004 15:45:46 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Sat, 14 Feb 2004 13:45:45 -0600
Message-ID: <402E7AE1.9FE7964C@nma.com>
Date: Sat, 14 Feb 2004 11:45:37 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: Franck Martin <franck@sopac.org>, John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: covert channel and noise -- was Re: proposal ...
References: <Pine.LNX.4.44.0402132314000.385-100000@cirrus.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Dean Anderson wrote:

> On Fri, 13 Feb 2004, Ed Gerck wrote:
> 
> > Shannon distinguished messages --or intended information-- from noise.
> > The distinction beween noise and information is that information is what
> > the sender wants to send or, alternatively, what the receiver wants to
> > receive. If the channel is a covert channel, it is fair to assume that
> > either the sender or the receiver (or both) do not intend it to exist
> > (otherwise, it would not be a covert channel). Thus, a covert channel
> > transmits information that can be considered for modeling purposes as a
> > source of noise. Since the 10th theorem applies to any source of noise,
> > it also applies here.
> 
> You are confusing a covert channel with noise. They aren't the same.

Of course they aren't -- how could a channel be equal to noise, anyway?

What I said is that the *information* transferred by a covert channel, 
whatever that information might be, is NOT the message (the intended 
information).  Thus, for modeling purposes in terms of Shannon's
information theory, the choice is clear. The *information* transferred 
by a covert channel is noise (the only other possible option).

> Antispammers have commonly used an analogy that equates spam with noise
> and anti-spam efforts as trying to find a "noise filter".  The analogy
> sounds good, but is not accurate, which might suggest a reason why they
> have failed to find a "filter".

If you are proposing a different model, fine. There are always many models
that can describe something. However, in the message model used by Shannon, 
there is a clear distinction between messages (or intended information) 
and noise (anything else) that also applies here. In the case of spam,
my mailbox has messages (intended communications) and spam (noise).

Also, note that noise does not have to disrupt communications! Noise is 
simply that which is not the message.

BTW, I often find people who try to say that spam is not noise --
because it can be useful, as advertising. Surely, in terms of a
communication process, you can consider whatever you want as
the *intended message* (i.e., not noise). You can certainly
say that spam is a message that the sender (the spammer) intended
to send. However, from the receiver's viewpoint, spam is usually
considered to be noise and IMO rightly so. 

> Spam isn't unwanted until after the fact: You read it, and then you don't
> like it.  

I strongly disagree -- I don't read spam and I don't even try to 
read the unsubscribe information in it. I try the best I can to detect 
it and delete it as early as possible. If possible, even before it is 
queued in my mail box and causes me further problems (and costs). I 
believe that's also what the majority of email users would like to 
do -- or, do you really think we all have the time to read spam and 
decide after the fact that it is indeed spam? That's why the proposal 
for anti-spam burden does provide a mandatory pre-delivery burden that
can be increased as much as the *recipient* wants. Users should not be 
burdened with reading and sorting out spam -- regardless how the
senders want to classify it!



From AldoChelette802@mcguire.af.mil  Sun Feb 15 09:17:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10771
	for <ietf-archive@ietf.org>; Sun, 15 Feb 2004 09:17:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsN5i-0000f0-00
	for ietf-archive@ietf.org; Sun, 15 Feb 2004 09:17:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsN4n-0000ZX-00
	for ietf-archive@ietf.org; Sun, 15 Feb 2004 09:16:54 -0500
Received: from modemcable182.81-203-24.mc.videotron.ca ([24.203.81.182])
	by ietf-mx with smtp (Exim 4.12)
	id 1AsN47-0000Nk-00
	for ietf-archive@ietf.org; Sun, 15 Feb 2004 09:16:13 -0500
Received: from 85.8.208.248 by 24.203.81.182; Sun, 15 Feb 2004 19:06:45 +0500
Message-ID: <KEXQTQREXAIXNGSUWAJOCTIXY@globalctigroup.com>
From: "Murray Lipka" <AldoChelette802@mcguire.af.mil>
Reply-To: "Murray Lipka" <AldoChelette802@mcguire.af.mil>
To: ietf-archive@ietf.org
Subject: 24-HOUR SALE: Act Now! 
Date: Sun, 15 Feb 2004 09:06:45 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--89317916242543628"
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=9.7 required=5.0 tests=ACT_NOW_CAPS,
	FROM_ENDS_IN_NUMS,HTML_30_40,HTML_FONTCOLOR_UNKNOWN,HTML_MESSAGE,
	HTML_TAG_BALANCE_BODY,HTML_TAG_EXISTS_TBODY,MIME_HTML_NO_CHARSET,
	MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,OBFUSCATING_COMMENT autolearn=no 
	version=2.60
X-Spam-Report: 
	*  0.9 FROM_ENDS_IN_NUMS From: ends in numbers
	*  1.3 ACT_NOW_CAPS BODY: Talks about 'acting now' with capitals
	*  0.1 HTML_FONTCOLOR_UNKNOWN BODY: HTML font color is unknown to us
	*  0.8 HTML_30_40 BODY: Message is 30% to 40% HTML
	*  0.3 HTML_TAG_BALANCE_BODY BODY: HTML has unbalanced "body" tags
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 HTML_TAG_EXISTS_TBODY BODY: HTML has "tbody" tag
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts
	*  4.3 OBFUSCATING_COMMENT HTML comments which obfuscate text

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

<html>
<head><p style=3D"font-size:0px; color:white" align=3D"left">Anavigate str=
ikebreak backbiting booing probate hangar midget kin season locus brasilia=
 agriculturalists flo covariate blurriest flamboyant beau cowhide bryn por=
ch=20 . Jmercurial aerodynamics aerobically vaudois bondholder muddle armo=
rs bamberger burgundian arraigned catalyst descartes rectangular bestrode =
orr sped poultry quartzite acceptor romano diagnoses and incumbent pronoun=
ce balsas percentage kiss spavin injury tammany intervention=20!! Ushim q'=
s beware destructor leadsmen forceful apter andromache tacitus anabolisms =
away apocrypha apoplexies firefly titian ablations sextuple uprise anomalo=
us bewhisker geochemistry patentee accoutre lick chrysler ash hilltop back=
handing gateway fairport toccata berry elegant diocesan squadron richardso=
n crystallite ga resignation solicitation rebellion triplett inappropriate=
 bedazzlement male astrolabes availabilities exchequer authentic estate ob=
sequious repressive cheek authenticates angelina=20.Ubiters deferral bomba=
rded sunken happenstance equestrian schism tepid betrothal dessicate asp i=
nshore appealingly aspidistras alerted=20. Havery blasphemy uphill tintype=
 astronauts congresswoman fictive backseat benz street automaton=20. Tct f=
rayed basest hurry edwardian yon harp vestry booboos traffic bien epaulet =
germinal mistress smooch thicken mangel awfullest loudspeaking maloney typ=
e believable bustle cultivable college dealt gneiss harriet authored backb=
iter artlessly wiener regent monetary anecdota france cistern rickshaw bra=
instorm=20 Flana deed participant youth fiduciary=20! Ejericho slothful ap=
preciable chutney riviera=20!! Zcone ineducable affluent hindrance photogr=
aphy assayers though gaslight transcend harbinger began inequivalent acces=
sibly shrubbery parley fritz beggar aphrodisiac perdition import insecure =
belletrists diane selfish bicker rebellious rob newsweek bludgeoning porce=
lain tiny beckon valedictory los ebb cotillion folly bhoy infidel shrew tu=
xedo bagginesses harbin=20 Jut budge flatworm fairgoer gambit beans abstai=
ners quakeress boyar consortium blazoned physique pendant axing accommodat=
es swathe electrocardiogram bloodline=20 . Xattributing bassett wardroom r=
othschild octennial rival maldive seminole burch lenny odd sweep walgreen =
nameplate guaranteeing primordial seidel apologetically bleeds neutral coh=
esion basso pervert tedium henley mccracken jacksonian query liniment farn=
sworth jade=20!! Vdecimate octavia allocates tactual abramson nomad mulish=
 reduce porch boffo edwina anchovy propeller bonged blockaders nominate bo=
bolink veneto beeches cryptanalytic aeroplanes courtesan binomial pill aut=
omated crete smash appropriates another adjudicate deadwood frantic flambo=
yant splendid battles leon cowan affected shrunk batch atomically zeal ind=
ignation joss insufficient upsetting catatonic chagrin modish clung isingl=
ass sticktight perdition exudate bacteriologists bustard advisor surplus b=
ackstops=20.Obah bilk kerchief downriver assassinates citizen schumann ent=
hrall authorities=20. Satoning almagest elizabeth redbud khaki berry lobst=
er tibet=20: Lblare clarke allotting stag abraham epicyclic twaddle lympho=
cyte enamel arouses flatus impromptu winter biopsied nobelium benzedrine a=
ppliance augment abysmal bangle cybernetic ancillary barterers lens groove=
 automatically bernie cynic admiration albumin odium patrice aggregations =
daybreak conrad sphagnum puddly animal gosling attaining doctoral blimps=20=
 Iyellowish hoi blench hemorrhoid bahts shrilly gallows sue ani ground tea=
pot=20 !!! Msubsuming hoarfrost psychophysiology audiophiles aspidistra an=
tithetically cleft allyl dazzle bedding mica sean=20! Jaerodrome isotherma=
l beneficial sclerotic bullhide mechanic claret guiding ky rotenone sphale=
rite weigh arrange actor dandy upkeep bullfinch ukrainian criss bagsful cl=
ap peppy copperfield artifact asphyxiates lose mollusk fun lunchroom oldsm=
obile glimmer scruple adaptations divine dumpy nightingale reich where'd f=
lattery i'll farley bedroll bigmouth zigging arlene beguile imbroglio pape=
rweight parsons beaded snort affront chautauqua bishop nether assam gnosti=
c schottky acronym dwight admiral agronomic=20.</p>
</head>
<body>
<center>
<TABLE class=3DMsoNormalTable style=3D"WIDTH: 6.25in" cellSpacing=3D0 
      cellPadding=3D0 width=3D600 border=3D0>
        <TBODY>
        <TR>
          <TD 
          style=3D"PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: =
0in; PADDING-TOP: 0in">
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><=
SPAN 
            style=3D"FONT-SIZE: 12pt"><A 
            href=3D"http://www.affordrxnow.com/index.html?rid=3D1001" targ=
et=3D"_blank"><FONT 
            color=3Dwhite><SPAN style=3D"COLOR: white; TEXT-DECORATION: no=
ne"><IMG 
            height=3D90 src=3D"http://www.morgan-time.com/great-dealz/imag=
epull/image001.gif" 
            width=3D421 border=3D0 NOSEND=3D"1"></SPAN></FONT></A></SPAN><=
/FONT></P></TD>
          <TD 
          style=3D"PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: =
0in; PADDING-TOP: 0in" 
          rowSpan=3D6>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dwh=
ite 
            size=3D3><SPAN style=3D"FONT-SIZE: 12pt; COLOR: white">
			<IMG height=3D580 src=3D"http://www.morgan-time.com/great-dealz/imagepu=
ll/image002.jpg" 
            width=3D179 border=3D0 NOSEND=3D"1"></SPAN></FONT></P></TD></T=
R>
        <TR>
          <TD 
          style=3D"PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: =
0in; PADDING-TOP: 0in">
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><=
SPAN 
            style=3D"FONT-SIZE: 12pt"><A 
            href=3D"http://www.affordrxnow.com/index.html?rid=3D1001" targ=
et=3D"_blank"><FONT 
            color=3Dwhite><SPAN style=3D"COLOR: white; TEXT-DECORATION: no=
ne"><IMG 
            height=3D126 src=3D"http://www.morgan-time.com/great-dealz/ima=
gepull/image003.gif" 
            width=3D421 border=3D0 NOSEND=3D"1"></SPAN></FONT></A></SPAN><=
/FONT></P></TD></TR>
        <TR>
          <TD 
          style=3D"PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: =
0in; PADDING-TOP: 0in">
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><=
SPAN 
            style=3D"FONT-SIZE: 12pt"><A 
            href=3D"http://www.affordrxnow.com/index.html?rid=3D1001" targ=
et=3D"_blank"><FONT 
            color=3Dwhite><SPAN style=3D"COLOR: white; TEXT-DECORATION: no=
ne"><IMG 
            height=3D82 src=3D"http://www.morgan-time.com/great-dealz/imag=
epull/image004.gif" 
            width=3D421 border=3D0 NOSEND=3D"1"></SPAN></FONT></A></SPAN><=
/FONT></P></TD></TR>
        <TR>
          <TD 
          style=3D"PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: =
0in; PADDING-TOP: 0in">
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><=
SPAN 
            style=3D"FONT-SIZE: 12pt"><A 
            href=3D"http://www.affordrxnow.com/index.html?rid=3D1001" targ=
et=3D"_blank"><FONT 
            color=3Dwhite><SPAN style=3D"COLOR: white; TEXT-DECORATION: no=
ne"><IMG 
            height=3D83 src=3D"http://www.morgan-time.com/great-dealz/imag=
epull/image005.gif" 
            width=3D421 border=3D0 NOSEND=3D"1"></SPAN></FONT></A></SPAN><=
/FONT></P></TD></TR>
        <TR>
          <TD 
          style=3D"PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: =
0in; PADDING-TOP: 0in">
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><=
SPAN 
            style=3D"FONT-SIZE: 12pt"><A 
            href=3D"http://www.affordrxnow.com/index.html?rid=3D1001" targ=
et=3D"_blank"><FONT 
            color=3Dwhite><SPAN style=3D"COLOR: white; TEXT-DECORATION: no=
ne"><IMG 
            height=3D86 src=3D"http://www.morgan-time.com/great-dealz/imag=
epull/image006.gif" 
            width=3D421 border=3D0 NOSEND=3D"1"></SPAN></FONT></A></SPAN><=
/FONT></P></TD></TR>
        <TR>
          <TD 
          style=3D"PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: =
0in; PADDING-TOP: 0in">
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><=
SPAN 
            style=3D"FONT-SIZE: 12pt"><A 
            href=3D"http://www.affordrxnow.com/index.html?rid=3D1001" targ=
et=3D"_blank"><FONT 
            color=3Dwhite><SPAN style=3D"COLOR: white; TEXT-DECORATION: no=
ne"><IMG 
            height=3D113 src=3D"http://www.morgan-time.com/great-dealz/ima=
gepull/image007.jpg" 
            width=3D421 border=3D0 NOSEND=3D"1"></SPAN></FONT></A></SPAN><=
/FONT></P></TD></TR></TBODY></TABLE><br>
		T<!bludgeon>he pi<!calypso >ctur<!beaning >e<!backgrounders> is n<!ileum=
 >ot<!luck> loa<!width >ding<!batons>? Th<!boatmen >en<!appointing> <a hre=
f=3D"http://www.affordrxnow.com/index.html?rid=3D1001" target=3D"_blank">G=
<!institute >O<!dobson > H<!gunky >E<!assessors >R<!electorate >E<!anthrax=
></a></center>
		<p style=3D"font-size:0px; color:white" align=3D"left">Oawareness bodkin=
s glaciate bestrew bush pugh earthquake antedated motivate mervin bespangl=
e vienna thermo bewildered twiddle boil=20 . Hballsier spy asparaguses pai=
r rothschild adjacent blanched viceroy ascetic ambience affectionately kne=
el polymer abed woodhen sanford chagrin wealthy waveform bird slip anarchi=
st negligent commonweal admire=20. Rrheostat cyanide bench rasa arrivals m=
icro whoop robbery floral permitted bailing sternberg abbreviate sophocles=
 cairo load burp beetling bimetallism ruth backtracks sputnik preponderant=
 spiro beaked click villainous bedside nanosecond professorial preemptive =
nest baklava epigram mcclellan deform percival sanctuary orangeroot textil=
e tarpaper amphibious seismograph goodman advisement consummate iran bairn=
s bodegas douglas=20.Sbattleaxes meredith bagsful marque telegraph seek am=
atory invertebrate adieux airstrips europium=20!! Mstationmaster beryl por=
tia pneumatic hoy way omit hades electrician obstruent prostitution append=
ing basidiomycetes inquisitive tramp macrame=20! Bblew workforce antenatal=
 transconductance accustomed averting scribe alcoa acculturated=20 Kbabyho=
od adoption rhombohedral code mankind perseus tyrant maya=20!!! Qaltruisti=
cally axon sonoma planetarium prizewinning abstractedly bite arrays parall=
ax airfreights tragicomic mayst venetian cottonmouth aggressions gout shie=
lds=20: Cbipartisan tress nightmarish flotation ale atonal bluebottle matr=
oid swingable sad gullah gobbledygook toroid wilkie antigen curse squirmy =
bolshevism exodus catchword astounding ultimatum batters alerting leapt ar=
chness abstinent sternberg annotator infinitude sclerotic agreed marty aqu=
avits roadhouse perpetual=20=20Sbosch dial cancer lockhart solitaire abrad=
ed compensatory customhouse elena asphyxiation bulk finesse yonkers apprai=
sed belief worth acceptances inc=20 !!! Zinhospitable holcomb dissident an=
tedate balk gingko studio bloodhound costume bombast aimlessly citadel res=
orcinol=20. Qpsyllium desire blinks militarist tadpole baylor bangle blush=
es pacific downtown immodesty bricklaying were atonally battered adobe imp=
ortunate proletariat fiducial antipodean blastoffs andrea abrasively shamp=
oo seedling mule blimp authoresses blacken ambivalences mennonite l'oeil a=
nhydrite dagger thelma nathan olive heliocentric se antagonism betraying i=
nterject accounting thrum transcribe=20.119.32.130.136%RND_DIACR          =
      =20</p
</body>
</html>

----89317916242543628--



From owner-ietf@ietf.org  Sun Feb 15 14:46:36 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21089
	for <ietf-archive@odin.ietf.org>; Sun, 15 Feb 2004 14:46:36 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AsRuq-0005KA-Vf
	for ietf-list@asgard.ietf.org; Sun, 15 Feb 2004 14:26:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AsRud-0005JZ-RN
	for ietf@asgard.ietf.org; Sun, 15 Feb 2004 14:26:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20678
	for <ietf@ietf.org>; Sun, 15 Feb 2004 14:26:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsRuZ-0004mm-00
	for ietf@ietf.org; Sun, 15 Feb 2004 14:26:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsRtb-0004kc-00
	for ietf@ietf.org; Sun, 15 Feb 2004 14:25:40 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsRsl-0004ft-00
	for ietf@ietf.org; Sun, 15 Feb 2004 14:24:47 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1FJMxCJ022846
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 15 Feb 2004 14:22:59 -0500
Date: Sun, 15 Feb 2004 14:22:59 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Ed Gerck <egerck@nma.com>
cc: Franck Martin <franck@sopac.org>, John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: covert channel and noise -- was Re: proposal ...
In-Reply-To: <402E7AE1.9FE7964C@nma.com>
Message-ID: <Pine.LNX.4.44.0402151300510.21133-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 14 Feb 2004, Ed Gerck wrote:

> Dean Anderson wrote:
>
> > You are confusing a covert channel with noise. They aren't the same.
> 
> Of course they aren't -- how could a channel be equal to noise, anyway?
> 
> What I said is that the *information* transferred by a covert channel, 
> whatever that information might be, is NOT the message (the intended 
> information).  

So, the spammer didn't intend to send you a message about Viagra??  That
somehow "noise" caused the message to be altered to be about Viagra?? I
don't think so.

> Thus, for modeling purposes in terms of Shannon's
> information theory, the choice is clear. The *information* transferred 
> by a covert channel is noise (the only other possible option).

Not only isn't it 'the only possible option', but the information carried
by a covert channel is not noise.  The sender sent information and the
receiver recieved the information. It isn't the case that the spammer
intended to send a message about the superbowl, but somehow "noise"
altered the message to a solicitation on viagra. Rather, they intended to
send a message on viagra, and you recieved their message, noise free.  
But seeing the solication for viagra, you became upset, and reported a
complaint about the inappropriate use of the channel. In
information-theory-speak, you report a "communication in violation of the
security model"; a covert or sneaky channel.

A note of caution: The intent of the senders and receivers is irrelevant
to information theory channels.  Covert channels can exist with or without
intent, and with or without cooperation. Information theory is concerned
with the movement of information through a transmitter to a reciever. The
intent or cooperation in that transfer is irrelevent, except that a
channel used for information not intended for transmission is called
covert or sneaky.

For example, when a remote SSL attacker uses timing information to obtain
the secret key of the server, the server isn't cooperating, nor does it
intend to provide the secret key.  Information theory looks at the actual
value of the key, and whether that was transmitted to the reciever with or
without noise. In the case of the SSL timing attack, there is a lot of
noise, but information theory tells us, and practice confirms, that the
noise can be corrected, until the key is successfully transmitted to the
receiver error free.

In the case of spam though, we safely assume the intent of sender to get a
spam message to the recipient, and can couch our descriptions accordingly,
but we need to exercise some caution.  With regard to noise, what we are
really be concerned with is the message before it is transmitted, and the
message after it is received.  In our case, the transmission is usually
noise free thanks to the function of TCP.

> > Antispammers have commonly used an analogy that equates spam with noise
> > and anti-spam efforts as trying to find a "noise filter".  The analogy
> > sounds good, but is not accurate, which might suggest a reason why they
> > have failed to find a "filter".
> 
> If you are proposing a different model, fine. 

I'm not proposing a different model. The model of "spam is noise" that you
are using is inaccurate and wrong. I'm explaining the correct way to model
spam in information theory.  This will help explain why many anti-spam
proposals are unworkable, and why previous attempts have failed.

> > Spam isn't unwanted until after the fact: You read it, and then you don't
> > like it.  
> 
> I strongly disagree -- I don't read spam and I don't even try to 
> read the unsubscribe information in it. I try the best I can to detect 
> it and delete it as early as possible. If possible, even before it is 
> queued in my mail box and causes me further problems (and costs). 

You don't _want_ to read it. You don't _want_ to spend time reading it.
It's the fact that one doesn't have time to read all the junk that many
people find annoying about spam, as well as objectionable content.  But
those who don't have email aren't annoyed by spam.  You have to receive
spam to be annoyed by it and not want it.

> I believe that's also what the majority of email users would like to do
> -- or, do you really think we all have the time to read spam and decide
> after the fact that it is indeed spam?

What users want is constrained by what's possible. I want
faster-than-light travel for free.  Many people want that, which explains
its popularity in science fiction.  But we are constrained by physics and
technology.  Quite obviously, in the case of spam we are trying to find
ways so that we don't have to read/sort/delete spam, or spend less time
doing so. You have promised that your scheme will eliminate the
whack-a-mole nature of spam. I'm saying that it is impossible to eliminate
this charactistic from spam, based on what we know from information theory
about covert or sneaky channels.  This tells us that your scheme cannot
deliver what you have promised. 

The prevalence of anti-spam schemes that claim to make spam just disappear
are much like the perpetual motion machines proposed at the turn of the
last century.  Eventually, we started to use thermodynamics to analyze
these schemes before they were built. When we see perpertual motion, we
dismiss the idea as a "perpetual motion scheme". We do not need to
prototype perpetual motion schemes to know they won't work.  Likewise, we
do not need to prototype communication systems that claim to be free of
covert channels to know that they won't be free of covert channels.  
Information theory tells us that one can never be free of covert channels.

> That's why the proposal for anti-spam burden does provide a mandatory
> pre-delivery burden that can be increased as much as the *recipient*
> wants. Users should not be burdened with reading and sorting out spam --
> regardless how the senders want to classify it!

I think you also need to consider the causality constraints on a
"Pre-delivery burden that can be increased as much as the *recipient*
wants".  You cannot make an uneven playing field for the spammer. You can
increase the pre-delivery burden on everyone. Yet the spammer using
virus-stolen computer and bandwidth resources won't care.  You can't
change the pre-delivery burden after you receive the spam because of
causality.

		--Dean





From owner-ietf@ietf.org  Sun Feb 15 15:59:53 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24512
	for <ietf-archive@odin.ietf.org>; Sun, 15 Feb 2004 15:59:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AsTDA-0006Rz-SF
	for ietf-list@asgard.ietf.org; Sun, 15 Feb 2004 15:49:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AsTCv-0006RQ-AE
	for ietf@asgard.ietf.org; Sun, 15 Feb 2004 15:49:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24297
	for <ietf@ietf.org>; Sun, 15 Feb 2004 15:49:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsTCt-00025g-00
	for ietf@ietf.org; Sun, 15 Feb 2004 15:49:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsTBw-000239-00
	for ietf@ietf.org; Sun, 15 Feb 2004 15:48:41 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[7LnVo5yxBN9JiiLXxjcoJhvBU6LEFc3+])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsTB1-00020l-00
	for ietf@ietf.org; Sun, 15 Feb 2004 15:47:43 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id 333B5A783D; Sun, 15 Feb 2004 15:47:40 -0500 (EST)
Date: Sun, 15 Feb 2004 15:12:22 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Dean Anderson <dean@av8.com>
Cc: Ed Gerck <egerck@nma.com>, Franck Martin <franck@sopac.org>,
        John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: covert channel and noise -- was Re: proposal ...
In-Reply-To: <Pine.LNX.4.44.0402151300510.21133-100000@cirrus.av8.net>
Message-ID: <Pine.LNX.4.44.0402151423180.1291-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sun, 15 Feb 2004, Dean Anderson wrote:

> On Sat, 14 Feb 2004, Ed Gerck wrote:
> 
> > Dean Anderson wrote:
> >
> > > You are confusing a covert channel with noise. They aren't the same.
> > 
> > Of course they aren't -- how could a channel be equal to noise, anyway?
> > 
> > What I said is that the *information* transferred by a covert channel, 
> > whatever that information might be, is NOT the message (the intended 
> > information).  
> 
> So, the spammer didn't intend to send you a message about Viagra??  That
> somehow "noise" caused the message to be altered to be about Viagra?? I
> don't think so.
> 
> > Thus, for modeling purposes in terms of Shannon's
> > information theory, the choice is clear. The *information* transferred 
> > by a covert channel is noise (the only other possible option).
> 
> Not only isn't it 'the only possible option', but the information carried
> by a covert channel is not noise.  The sender sent information and the

Once again, what Dean is saying is dead on correct.  Information theory
deals with corruption of bits, with the degradation of "ordered"
information.  In physics, entropy is the log of the missing information,
where information has a very precise meaning, and with this definition
much of statistical mechanics can be more or less derived from Shannon's
theorem and a proper analysis of conditional probabilities.

An alternative view of SPAM where it isn't a "covert channel" (which
sounds a bit too much like spy thriller stuff, although I understand
perfectly well what is meant) but rather considers it merely to be an
undesireable communication clarifies things a great deal.  What is
undesirable is clearly a matter of opinion and requires the solution of
a serious (largely unsolved) problem in predictive modeling or
artificial intelligence in order to mechanically filter.

I'd like to make a suggestion.  There are several parts of this
discussion that are quite distinct, and by mixing them (often out of
context) the discussion is being perpetuated well beyond sane
boundaries.

First of all, there is the issue of whether or not email should
routinely and USER TRANSPARENTLY be encrypted, at least during the
transit phase between MTA's.  This really deserves an entirely separate
discussion, as I think one might well build up a consensus that ALL
network traffic should be routinely encrypted at this point and that
email in general is a glaring legacy exception in a world where SSL and
ssh have largely dealt with encrypting the rest, at least where it most
matters.  This, in my opinion, is very much an IETF issue as it would
require the development of an open protocol and the supported
engineering of retrofitting MTA's everywhere to use it.  This in turn
may well hinge on broader issues of host registration and
authentication.

After all, most users of web browsers and ssh are not deeply aware of
the key manipulations that take place in order to secure those channels
EXCEPT when they are being attacked and threaten to fail.  Surely
something could be done with mail as well.

Second, there is the issue of whether adding a "cost" to email would
deter spam.  I note that no one (Ed in particular) has yet attempted to
rebut by assertion that doing the actual arithmetic it is clear that
individuals emailing SPAM in excess of the legal limits triggered by
e.g. the new Virginia anti-SPAM law (10K pieces a day, 100K per month)
could care less if the COMPUTATIONAL cost per message were 8 whole
seconds per mailing, so delays up to that level are irrelevant.  8
seconds is some 20 to 30 billion instructions on a modern CPU, and
nothing restricts spammers to using just one.  I think that it is
absolutely clear that adding an encryption step as a "cost" to deter
spammers is simply ridiculous as it will do no such thing.

Adding a "cost" to an email message to all users (instituting
per-message costs onto the internet backbone) is a cure so much worse
than the disease that I, for one, will vehemently oppose it, as will
nearly all old Internet hands.  That way madness lies.  And in any
event, per message costs will simply shift the cost plateau around and
make sending spam legitimate business with more than a handful of
individuals making a profit from it.  The moment spam is viewed the way
TV advertisements are, as a perfectly reasonable adjunct to a medium, we
are all doomed.

I am by no means convinced that spam control is in any way the business
of the IETF.  If it is, it must be at the detailed engineering level,
and the discussion is very, very far away from that so far (where people
are routinely making statements like "implementing this will result in
that" without any sort of quantitative analysis or basis.  Engineering
is about numbers, not just "ideas".  At the very least, ideas supported
by actual numbers.

In fact, before making ANY sort of proposal concerning spam, it would
behoove the primary participants to study and use themselves on an
active basis a wide range of the existing anti-spam tools.  Second, in
at least the open source world where a lot of similar crack discussion
can easily occur, the rule is "build a prototype and demonstrate it
before you waste three months of discussion on whether or not it will
work".  I'd say that this too is entirely appropriate.

In this case, BUILD your proposed anti-spam measures into a whole chain
of open source tools.  Mailman, for example, which already has a lot of
anti-spam stuff in it.  Add a db field for keys, hook together all the
logic for their automated implementation so that mailman-based mailing
lists can use keys for all members.  See if anyone buys it, likes it,
uses it.  See where and why it fails.

THIS is the appropriate path of engineering -- prototyping and
real-world trials.  Then we don't have to argue about how much work it
would be or if it would work, and that way we ALSO don't have to publish
a "bare standard" with no actual implementations and expect everybody
ELSE to invest all the work and energy in implementing it without even a
working prototype to test against.

    rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Sun Feb 15 16:51:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25910
	for <ietf-archive@odin.ietf.org>; Sun, 15 Feb 2004 16:51:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AsU3Q-0007No-Hw
	for ietf-list@asgard.ietf.org; Sun, 15 Feb 2004 16:43:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AsU3G-0007Mt-LX
	for ietf@asgard.ietf.org; Sun, 15 Feb 2004 16:43:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25764
	for <ietf@ietf.org>; Sun, 15 Feb 2004 16:43:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsU3F-00050n-00
	for ietf@ietf.org; Sun, 15 Feb 2004 16:43:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsU2H-0004xt-00
	for ietf@ietf.org; Sun, 15 Feb 2004 16:42:46 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsU1V-0004s8-00
	for ietf@ietf.org; Sun, 15 Feb 2004 16:41:57 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1FLfRRf025643
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Sun, 15 Feb 2004 16:41:27 -0500
Date: Sun, 15 Feb 2004 16:41:27 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: ietf@ietf.org
Subject: Potential junk email quarantined (fwd)
Message-ID: <Pine.LNX.4.44.0402151636260.21133-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0402151636262.21133@cirrus.av8.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Heh. Another one.  No doubt the user of this system doen't even know that
it does this, nor do we have any idea to to contact, or what the "ITS Help
Desk" is, or how to notify it.

I wonder what about my previous message might have fallen into the 4
categories?  

As you can see, a lot of anti-spam effort is ill-conceived and, well, 
idiotic at best.  And it is no less troublesome than spam. Probably more 
troublesome, in fact.


	--Dean

---------- Forwarded message ----------
Date: Sun, 15 Feb 2004 14:41:01 -0500
From: mailscreen@itcdeltacom.com
To: dean@av8.com
Subject: Potential junk email quarantined

MailMarshal has not delivered the following message:

   Message: BA000c2365.00000001.mml
   From:    dean@av8.com
   To:      dbotham@edeltacom.com
   Subject: Re: covert channel and noise -- was Re: proposal ...

This is due to automatic rules that have determined that the 
message contains one or more of the following:

Personal content
Chain-letter/junk-mail characteristics
Potentially offensive/harrassing language
Known spamming language

If this is a legitimate business related email that you believe has been
blocked in error, please remove any content that may fall into one of the
aforementioned categories and resend the message.

If the message is still blocked, you may contact the intended recipient and have them notify the ITS Help Desk.

This message will be retained for
seven days.


Please do not reply to this message.




From owner-ietf@ietf.org  Sun Feb 15 18:32:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01669
	for <ietf-archive@odin.ietf.org>; Sun, 15 Feb 2004 18:32:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AsVaG-0000JE-6r
	for ietf-list@asgard.ietf.org; Sun, 15 Feb 2004 18:21:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AsVaA-0000Ih-7l
	for ietf@asgard.ietf.org; Sun, 15 Feb 2004 18:21:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01316
	for <ietf@ietf.org>; Sun, 15 Feb 2004 18:21:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsVa8-00051i-00
	for ietf@ietf.org; Sun, 15 Feb 2004 18:21:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsVZI-0004xI-00
	for ietf@ietf.org; Sun, 15 Feb 2004 18:20:57 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsVYL-0004nn-00
	for ietf@ietf.org; Sun, 15 Feb 2004 18:19:57 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1FNJMDL027454
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 15 Feb 2004 18:19:23 -0500
Date: Sun, 15 Feb 2004 18:19:22 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Franck Martin <franck@sopac.org>
cc: ietf@ietf.org
Subject: Re: Potential junk email quarantined (fwd)
In-Reply-To: <1076884409.2634.7.camel@franck-lxnb.sopac.org.fj>
Message-ID: <Pine.LNX.4.44.0402151749110.21133-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I got an embarrased message from the member about their IT department. I
don't want to pick them in particular. This type of thing is all to
frequent--and they are in no way unique or even very far from ordinary.  
This particular one just happened to come at the wrong time.  That said,
more inline.

On 16 Feb 2004, Franck Martin wrote:

> I like it when it says you use offensive and harrassive language... ietf
> must be a swear, then...
> 
> ;)

;-) Yes, it must be that.

> anti-spam systems are like e-mail systems, they need to be set properly.
> That's all. They are not idiotic or ill-conceived, they are miss-used...

I'd suppose that the "known spamming language" was the references to 
viagra. Many years ago, AOL banned the use of the term "breast", and 
created a stir because breast-cancer support groups were using AOL, and 
were shut down.  Filter-writers have to know that there are no bad terms, 
and that filters can't be overly simplistic. But then, spammers can get 
around filters, and they require constant maintenance.

   Who knows what is bad about "personal content", though, maybe this
system isn't for personal use. But then who knows what about my message
was overly personal...

   I am stumped as to what may have been offensive/harrassing language,
but 'ietf' is as good a guess as any.

   Likewise, what about it had "junk mail/chain letter characteristics"  
also leaves me stumped.

These error messages are unintelligible, and the tests probably just
extra-ordinarily simplistic.  You are right, that is just miss-use of what
is probably system configuration. The site operator no doubt could rectify
all of these things, and no doubt will, after some amount of non-spam mail
is lost, or they are embarrassed on the IETF list. (sorry)

However, sending a "bounce message" to what you _think_ might be a spam
from: address is just a way for abusers to conduct abuse and mailbomb
people.  When abusers want to mailbomb an address, they just send a bunch
of garbage to a site like this, with the target's address as the from:
address.  The target gets mailbombed, and cannot block the site that is
being used. That's how they make things worse. This is why these responder
systems are idiotic and ill-conceived.  

What's always amazing to me is the absolute certainty and zeal that people
have that overly simple tests work.  One should mark things you _think_
might be spam, as spam, and deliver them, or discard them. One should not
create a mailbombing system.  Self/foot/trigger.

		--Dean




From owner-ietf@ietf.org  Sun Feb 15 20:18:07 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06412
	for <ietf-archive@odin.ietf.org>; Sun, 15 Feb 2004 20:18:07 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AsXBD-0001l7-95
	for ietf-list@asgard.ietf.org; Sun, 15 Feb 2004 20:04:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AsX8x-0001jK-I5
	for ietf@asgard.ietf.org; Sun, 15 Feb 2004 20:01:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05852
	for <ietf@ietf.org>; Sun, 15 Feb 2004 20:01:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsX8v-00051Z-00
	for ietf@ietf.org; Sun, 15 Feb 2004 20:01:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsX7z-0004y4-00
	for ietf@ietf.org; Sun, 15 Feb 2004 20:00:52 -0500
Received: from sccrmhc12.comcast.net ([204.127.202.56])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsX7B-0004ss-00
	for ietf@ietf.org; Sun, 15 Feb 2004 20:00:01 -0500
Received: from [192.168.0.101] (pcp05307270pcs.wanarb01.mi.comcast.net[68.42.70.186])
          by comcast.net (sccrmhc12) with SMTP
          id <20040216005921012009h7t4e>; Mon, 16 Feb 2004 00:59:26 +0000
In-Reply-To: <Pine.LNX.4.44.0402151749110.21133-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0402151749110.21133-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5A7618D0-601B-11D8-98C1-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
Cc: Franck Martin <franck@sopac.org>, ietf@ietf.org
From: Nathaniel Borenstein <nsb@guppylake.com>
Subject: Re: Potential junk email quarantined (fwd)
Date: Sun, 15 Feb 2004 19:59:20 -0500
To: Dean Anderson <dean@av8.com>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Feb 15, 2004, at 6:19 PM, Dean Anderson wrote:

> What's always amazing to me is the absolute certainty and zeal that 
> people
> have that overly simple tests work.  One should mark things you _think_
> might be spam, as spam, and deliver them, or discard them. One should 
> not
> create a mailbombing system.  Self/foot/trigger.

I take some (very) small comfort from the thought that the implementors 
of such systems will be ever less likely to communicate meaningfully 
with each other about their own filters.  If A asks B whether or not he 
filters words like "viagra", B won't reply if the answer is yes.  In 
terms of natural selection, this reminds me (somewhat) of the voluntary 
infertility of the Shaker movement (http://tinyurl.com/3a5k6)  -- 
Nathaniel




From owner-ietf@ietf.org  Sun Feb 15 20:54:28 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07851
	for <ietf-archive@odin.ietf.org>; Sun, 15 Feb 2004 20:54:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AsXrX-0002c1-R3
	for ietf-list@asgard.ietf.org; Sun, 15 Feb 2004 20:47:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AsXrW-0002bB-RS
	for ietf@asgard.ietf.org; Sun, 15 Feb 2004 20:47:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07592
	for <ietf@ietf.org>; Sun, 15 Feb 2004 20:47:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsXrU-0000ME-00
	for ietf@ietf.org; Sun, 15 Feb 2004 20:47:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsXqe-0000Gx-00
	for ietf@ietf.org; Sun, 15 Feb 2004 20:47:01 -0500
Received: from mail14.atl.registeredsite.com ([64.224.219.88] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsXpr-0000At-00
	for ietf@ietf.org; Sun, 15 Feb 2004 20:46:11 -0500
Received: from safevote.com (taurus.hosting4u.net [209.35.191.122])
	by mail14.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1G1k9IF007022;
	Sun, 15 Feb 2004 20:46:09 -0500
Received: from safevote.com ([63.204.17.85]) by safevote.com ; Sun, 15 Feb 2004 19:46:07 -0600
Message-ID: <403020D4.90BC2694@safevote.com>
Date: Sun, 15 Feb 2004 17:45:56 -0800
From: Ed Gerck <egerck@safevote.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: Ed Gerck <egerck@nma.com>, Franck Martin <franck@sopac.org>,
        John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: covert channel and noise -- was Re: proposal ...
References: <Pine.LNX.4.44.0402151300510.21133-100000@cirrus.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Dean Anderson wrote:
> 
>It isn't the case that the spammer
> intended to send a message about the superbowl, but somehow "noise"
> altered the message to a solicitation on viagra. Rather, they intended to
> send a message on viagra, and you recieved their message, noise free.
> But seeing the solication for viagra, you became upset, and reported a
> complaint about the inappropriate use of the channel. In
> information-theory-speak, you report a "communication in violation of the
> security model"; a covert or sneaky channel.

I guess we agree that if the message can be read by the intended recipient 
then it's not in a covert channel. A covert channel is one that can't even 
be detected by the intended recipient. But, you may ask, "who" is the 
intended recipient? 

In anti-spam email systems, we can usually recognize three "whos":

#1: My MTA
#2: My MUA
#3: Myself

The spammer's strategy is to send the spam message in such a  way
that it is undetectable by my MTA-MUA, while it is detectable and 
readable by me. In short, it needs to use a covert channel through my 
MTA-MUA, but not to me.

An example of such a covert channel is if a spammer hides information 
in the subject line by using wrongly spelled forms of "viagra", 
information which my MTA-MUA cannot detect. It's not a covert channel 
for me but it is for my defenses. But, once that message passes 
through to me, it becomes detectable, readable and I call it spam.

Does this mean that spam is defined by the rule

	"I (only) Know It When I See It!" 

and we have to accept a large failure rate in preventing spam, that 
can only be solved by laws and law enforcement? 

I want to emphasize that it does not have to be. Suppose a user can make
email senders pay a burden at their MTA or even at their MUA (e.g., a 
bounce requesting encryption and solution to a puzzle). In addition, using a 
selective scale defined by the user (so that selected mail senders have 
less burden) at their MTA and MUA, the user can make the spammer pay a 
price *as high as desired* by the user (not limited by R. Brown's comments).
In such case, the covert channel cannot even be established unless
the spammer pays a price -- a price that can be *as high as desired* by 
the *user*. This is the essence of the proposal (the devil is in details).

I take the example of the front door of your house. If you leave it open, 
so that a thief has no burden getting in, a thief probably will steal 
something from you -- even though the law says that theft is illegal.
What we need is to put a lock into our email communications door. A lock
that can be as hard to pick as the user wants, and yet easy to use
as the user wants it to be used.

Spammers are thiefs -- they steal time and resources, they make us
reject legitimate email. They cost a lot of  money to all of us. 
They have not been and will not be deterred by law alone. There
is also no "world law" and spammers are often hidding behind
legitimate users that change all the time. We can't lock the
spammers' doors everywhere, we have to lock our door at our house. 

BTW, to propose something simple, "running code" helps before any 
discussion.  In a system as complex as email, however, one would 
have to be naive to even think about "running code" before "running 
comments." I thank you all for the public discussion on this topic, 
through which I have learned a great deal, including people's first
barriers to change.



From owner-ietf@ietf.org  Sun Feb 15 20:59:15 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08273
	for <ietf-archive@odin.ietf.org>; Sun, 15 Feb 2004 20:59:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AsXum-0002dj-5o
	for ietf-list@asgard.ietf.org; Sun, 15 Feb 2004 20:51:16 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AsXsp-0002ce-8M
	for ietf@asgard.ietf.org; Sun, 15 Feb 2004 20:49:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07634
	for <ietf@ietf.org>; Sun, 15 Feb 2004 20:49:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsXsn-0000WI-00
	for ietf@ietf.org; Sun, 15 Feb 2004 20:49:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsXs1-0000RE-00
	for ietf@ietf.org; Sun, 15 Feb 2004 20:48:25 -0500
Received: from mail14.atl.registeredsite.com ([64.224.219.88] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsXrL-0000Ji-00
	for ietf@ietf.org; Sun, 15 Feb 2004 20:47:43 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail14.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1G1lhIF008035
	for <ietf@ietf.org>; Sun, 15 Feb 2004 20:47:43 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Sun, 15 Feb 2004 19:47:42 -0600
Message-ID: <40302134.A36E2D80@nma.com>
Date: Sun, 15 Feb 2004 17:47:32 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: covert channel and noise -- was Re: proposal ...
References: <Pine.LNX.4.44.0402151300510.21133-100000@cirrus.av8.net> <403020D4.90BC2694@safevote.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,TO_ADDRESS_EQ_REAL 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Ed Gerck wrote:
> 
> Dean Anderson wrote:
> >
> >It isn't the case that the spammer
> > intended to send a message about the superbowl, but somehow "noise"
> > altered the message to a solicitation on viagra. Rather, they intended to
> > send a message on viagra, and you recieved their message, noise free.
> > But seeing the solication for viagra, you became upset, and reported a
> > complaint about the inappropriate use of the channel. In
> > information-theory-speak, you report a "communication in violation of the
> > security model"; a covert or sneaky channel.
> 
> I guess we agree that if the message can be read by the intended recipient
> then it's not in a covert channel. A covert channel is one that can't even
> be detected by the intended recipient. But, you may ask, "who" is the
> intended recipient?
> 
> In anti-spam email systems, we can usually recognize three "whos":
> 
> #1: My MTA
> #2: My MUA
> #3: Myself
> 
> The spammer's strategy is to send the spam message in such a  way
> that it is undetectable by my MTA-MUA, while it is detectable and
> readable by me. In short, it needs to use a covert channel through my
> MTA-MUA, but not to me.
> 
> An example of such a covert channel is if a spammer hides information
> in the subject line by using wrongly spelled forms of "viagra",
> information which my MTA-MUA cannot detect. It's not a covert channel
> for me but it is for my defenses. But, once that message passes
> through to me, it becomes detectable, readable and I call it spam.
> 
> Does this mean that spam is defined by the rule
> 
>         "I (only) Know It When I See It!"
> 
> and we have to accept a large failure rate in preventing spam, that
> can only be solved by laws and law enforcement?
> 
> I want to emphasize that it does not have to be. Suppose a user can make
> email senders pay a burden at their MTA or even at their MUA (e.g., a
> bounce requesting encryption and solution to a puzzle). In addition, using a
> selective scale defined by the user (so that selected mail senders have
> less burden) at their MTA and MUA, the user can make the spammer pay a
> price *as high as desired* by the user (not limited by R. Brown's comments).
> In such case, the covert channel cannot even be established unless
> the spammer pays a price -- a price that can be *as high as desired* by
> the *user*. This is the essence of the proposal (the devil is in details).
> 
> I take the example of the front door of your house. If you leave it open,
> so that a thief has no burden getting in, a thief probably will steal
> something from you -- even though the law says that theft is illegal.
> What we need is to put a lock into our email communications door. A lock
> that can be as hard to pick as the user wants, and yet easy to use
> as the user wants it to be used.
> 
> Spammers are thiefs -- they steal time and resources, they make us
> reject legitimate email. They cost a lot of  money to all of us.
> They have not been and will not be deterred by law alone. There
> is also no "world law" and spammers are often hidding behind
> legitimate users that change all the time. We can't lock the
> spammers' doors everywhere, we have to lock our door at our house.
> 
> BTW, to propose something simple, "running code" helps before any
> discussion.  In a system as complex as email, however, one would
> have to be naive to even think about "running code" before "running
> comments." I thank you all for the public discussion on this topic,
> through which I have learned a great deal, including people's first
> barriers to change.



From owner-ietf@ietf.org  Sun Feb 15 21:25:04 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09469
	for <ietf-archive@odin.ietf.org>; Sun, 15 Feb 2004 21:25:04 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AsYIt-0003l8-4i
	for ietf-list@asgard.ietf.org; Sun, 15 Feb 2004 21:16:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AsYGg-0003iw-6P
	for ietf@asgard.ietf.org; Sun, 15 Feb 2004 21:13:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09170
	for <ietf@ietf.org>; Sun, 15 Feb 2004 21:13:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsYGe-0002ew-00
	for ietf@ietf.org; Sun, 15 Feb 2004 21:13:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsYFh-0002aX-00
	for ietf@ietf.org; Sun, 15 Feb 2004 21:12:54 -0500
Received: from mail7.atl.registeredsite.com ([64.224.219.81] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsYEj-0002VV-00
	for ietf@ietf.org; Sun, 15 Feb 2004 21:11:53 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail7.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1G2Bruk013907
	for <ietf@ietf.org>; Sun, 15 Feb 2004 21:11:54 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Sun, 15 Feb 2004 20:11:52 -0600
Message-ID: <403026DD.1ADC221B@nma.com>
Date: Sun, 15 Feb 2004 18:11:41 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: covert channel and noise -- was Re: proposal ...
References: <Pine.LNX.4.44.0402151300510.21133-100000@cirrus.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,TO_ADDRESS_EQ_REAL 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

[resending due to formatting error in previous msg]

Dean Anderson wrote:
> 
>It isn't the case that the spammer
> intended to send a message about the superbowl, but somehow "noise"
> altered the message to a solicitation on viagra. Rather, they intended to
> send a message on viagra, and you recieved their message, noise free.
> But seeing the solication for viagra, you became upset, and reported a
> complaint about the inappropriate use of the channel. In
> information-theory-speak, you report a "communication in violation of the
> security model"; a covert or sneaky channel.

I guess we agree that if the message can be read by the intended recipient 
then it's not in a covert channel. A covert channel is one that can't even 
be detected by the intended recipient. But, you may ask, "who" is the 
intended recipient? 

In anti-spam email systems, we can usually recognize three "whos":

#1: My MTA
#2: My MUA
#3: Myself

The spammer's strategy is to send the spam message in such a  way
that it is undetectable by my MTA-MUA, while it is detectable and 
readable by me. In short, it needs to use a covert channel through my 
MTA-MUA, but not to me.

An example of such a covert channel is if a spammer hides information 
in the subject line by using wrongly spelled forms of "viagra", 
information which my MTA-MUA cannot detect. It's not a covert channel 
for me but it is for my defenses. But, once that message passes 
through to me, it becomes detectable, readable and I call it spam.

Does this mean that spam is defined by the rule

	"I (only) Know It When I See It!" 

and we have to accept a large failure rate in preventing spam, that 
can only be solved by laws and law enforcement? 

I want to emphasize that it does not have to be. Suppose a user can make
email senders pay a burden at their MTA or even at their MUA (e.g., a 
bounce requesting encryption and solution to a puzzle). In addition, using a 
selective scale defined by the user (so that selected mail senders have 
less burden) at their MTA and MUA, the user can make the spammer pay a 
price *as high as desired* by the user (not limited by R. Brown's comments).
In such case, the covert channel cannot even be established unless
the spammer pays a price -- a price that can be *as high as desired* by 
the *user*. This is the essence of the proposal (the devil is in details).

I take the example of the front door of your house. If you leave it open, 
so that a thief has no burden getting in, a thief probably will steal 
something from you -- even though the law says that theft is illegal.
What we need is to put a lock into our email communications door. A lock
that can be as hard to pick as the user wants, and yet easy to use
as the user wants it to be used.

Spammers are thiefs -- they steal time and resources, they make us
reject legitimate email. They cost a lot of  money to all of us. 
They have not been and will not be deterred by law alone. There
is also no "world law" and spammers are often hidding behind
legitimate users that change all the time. We can't lock the
spammers' doors everywhere, we have to lock our door at our house. 

BTW, to propose something simple, "running code" helps before any 
discussion.  In a system as complex as email, however, one would 
have to be naive to even think about "running code" before "running 
comments." I thank you all for the public discussion on this topic, 
through which I have learned a great deal, including people's first
barriers to change.



From owner-ietf@ietf.org  Mon Feb 16 00:24:09 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14061
	for <ietf-archive@odin.ietf.org>; Mon, 16 Feb 2004 00:24:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Asb4t-00068R-59
	for ietf-list@asgard.ietf.org; Mon, 16 Feb 2004 00:13:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Asaz9-00064H-15
	for ietf@asgard.ietf.org; Mon, 16 Feb 2004 00:07:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13728
	for <ietf@ietf.org>; Mon, 16 Feb 2004 00:07:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Asaz6-0004TP-00
	for ietf@ietf.org; Mon, 16 Feb 2004 00:07:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsayB-0004QX-00
	for ietf@ietf.org; Mon, 16 Feb 2004 00:07:01 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[OIGEcjbX13asI2SBZvC4wCLaTXnLmDRR])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsaxQ-0004O4-00
	for ietf@ietf.org; Mon, 16 Feb 2004 00:06:12 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id A303CA781B; Mon, 16 Feb 2004 00:05:58 -0500 (EST)
Date: Sun, 15 Feb 2004 23:30:25 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Ed Gerck <egerck@safevote.com>
Cc: Dean Anderson <dean@av8.com>, Ed Gerck <egerck@nma.com>,
        Franck Martin <franck@sopac.org>, John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: covert channel and noise -- was Re: proposal ...
In-Reply-To: <403020D4.90BC2694@safevote.com>
Message-ID: <Pine.LNX.4.44.0402152257020.1291-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sun, 15 Feb 2004, Ed Gerck wrote:

> I take the example of the front door of your house. If you leave it open, 
> so that a thief has no burden getting in, a thief probably will steal 
> something from you -- even though the law says that theft is illegal.
> What we need is to put a lock into our email communications door. A lock
> that can be as hard to pick as the user wants, and yet easy to use
> as the user wants it to be used.

No, this is an incorrect analogy.  You want to put a lock on your
mailbox.  If you put a lock on your mailbox, you might as well not have
one.  The postman will no longer be able to deliver mail.

And the notion that there will be more than one "class" of mail so that
people will be able to send you "postcards" but not "real mail" is
spurious.  Unless you go through your postcard-class mail, you won't
know if there is anything important in there.  If you go through your
postcard class mail, you have to visually filter and reject all of the
spam and other unwanted mail that might be in it.

I have this problem now as it is.  I use spam assassin and set the spam
level pretty high -- 5 -- and bounce all of the rejects into a file
where I COULD check it.  However, I get roughly 5 MB/week in this file
so I don't, as a rule.

Because I set it so high, VERY FEW legitimate messages are lost, but a
fair bit of spam gets through, including various classes of stealth spam
with vi@gra lines (note that just using this line in this email will
guarantee its unviewed rejection by certain silly clients with much
LOWER spam thresholds, set so that they dump a lot of real mail along
with the spam).  This is a personal choice -- the lower the threshold
the more I reject and the greater the chance that real messages will be
rejected along with the spam.  If I have to review the rejected spam I
lose -- I might as well not reject at all.  If I lose an important
message I also lose.

THIS IS NOT A MATTER OF PROTOCOL!  This is not the business of the IETF!
Tools exist to help you filter spam.  Some, like spam assassin, are very
good and quite sophisticated.  However, there is ALWAYS a tradeoff with
using this sort of tool -- too narrow a criterion for acceptance and you
lose real mail, too broad and you get all the spam anyway.  I can choose
my level of tradeoff, and be fully aware of the risks.

> Spammers are thiefs -- they steal time and resources, they make us
> reject legitimate email. They cost a lot of  money to all of us. 
> They have not been and will not be deterred by law alone. There
> is also no "world law" and spammers are often hidding behind
> legitimate users that change all the time. We can't lock the
> spammers' doors everywhere, we have to lock our door at our house. 

No, what we can do is the same thing we do with our real mail box.  Make
it illegal to send certain classes of mail, for example letter bombs and
envelopes containing anthrax, and prosecute the hell out of anybody we
catch who does so.  We cannot arrange it so that whoever sends us mail
that for any reason we don't want to accept has to "solve a puzzle of
indeterminate difficulty" in order to send it to us.

And no, I don't WANT to "solve a puzzle" (I presume, a human level
puzzle) in order to send somebody email.  I WON'T solve a puzzle to send
somebody email -- anybody that silly will just not get email from me.
I've already pointed out that any extra step involving e.g. encryption
or a machine solveable puzzle is trivially manageable and trivially
automateable at effectively zero cost to any spammer and backed it up
with numbers -- cycles are available by the billion (literally) --
millions of cycles can be burned PER LETTER of the message and it's no
skin off a spammer's bottom line.

I reiterate -- most of what you propose is possible now.  If you want to
send only encrypted mail, you can.  If you insist on signing all mail,
you can.  If you want to only accept signed, encrypted mail, you can.
What you can't do is make everybody else go to all of that effort for
no benefit that could even THEORETICALLY ensue.  If you make it easy for
everybody to send signed, encrypted mail, you make it easy for spammers
to send signed, encrypted mail and you're back where you started.  If
you don't, then your cure is worse than the disease.

> BTW, to propose something simple, "running code" helps before any 
> discussion.  In a system as complex as email, however, one would 
> have to be naive to even think about "running code" before "running 
> comments." I thank you all for the public discussion on this topic, 
> through which I have learned a great deal, including people's first
> barriers to change.

This is true only if you want to LISTEN to what other people say.  What
is at issue here isn't my "barrier to change".  It is that this is (in
my opinion) a foolish idea.  I get just as irritated at spam as the next
person (more so, since as I noted I get some 5 MB a week that is
rejected by my filters of spam and identifiable viruses combined).
However, I also spend a fair bit of time explaining to users why it
isn't possible or wise to filter out all mail that might contain the
word "viagra" as if that alone is the basis for something being SPAM.

I also spend a fair bit of my time working with information theory,
statistical mechanics, predictive modeling, and networks.  AND I write a
lot of code, including code for networks and simulations.  AND I've been
doing systems administration and programming for a long time now.

There is the good old apocryphal saying: "The Internet perceives control
as damage and routes around it."

You are attempting to institute a new level of control over something
that has to be filtered and accepted/rejected at a very high level.  It
is NOT easy to identify spam automatically or there would be no problem,
would there?  procmail alone would suffice, with a few keywords.
Instead spam assassin, with a complex weighting system and key phrase
identification process STILL makes mistakes, in both directions, and one
can visibly identify spam that has "evolved" to get past its defenses.
SPAM is a DYNAMIC problem, not a static one.  Whatever barrier you raise
at the technical level (especially an effectively static one), it will
route around it OR act as a barrier to messages you want to receive, and
hence diminish the value of the network to you by making it even harder
to get your work done than it would have been if you were only dealing
with spam.

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Mon Feb 16 10:42:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26227
	for <ietf-archive@odin.ietf.org>; Mon, 16 Feb 2004 10:42:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AskaB-0004pp-L3
	for ietf-list@asgard.ietf.org; Mon, 16 Feb 2004 10:22:51 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AskZm-0004pF-UL
	for ietf@asgard.ietf.org; Mon, 16 Feb 2004 10:22:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23532
	for <ietf@ietf.org>; Mon, 16 Feb 2004 10:22:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AskZl-0003UL-00
	for ietf@ietf.org; Mon, 16 Feb 2004 10:22:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AskY7-0003BS-00
	for ietf@ietf.org; Mon, 16 Feb 2004 10:20:43 -0500
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AskX1-00032T-00
	for ietf@ietf.org; Mon, 16 Feb 2004 10:19:36 -0500
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id 3898AE07E4; Mon, 16 Feb 2004 10:19:35 -0500 (EST)
Date: Mon, 16 Feb 2004 10:19:35 -0500
From: John Leslie <john@jlc.net>
To: "Robert G. Brown" <rgb@phy.duke.edu>
Cc: Ed Gerck <egerck@safevote.com>, Dean Anderson <dean@av8.com>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: covert channel and noise -- was Re: proposal ...
Message-ID: <20040216151935.GB11808@verdi>
References: <403020D4.90BC2694@safevote.com> <Pine.LNX.4.44.0402152257020.1291-100000@lilith.rgb.private.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0402152257020.1291-100000@lilith.rgb.private.net>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Robert G. Brown <rgb@phy.duke.edu> wrote:
> 
> THIS IS NOT A MATTER OF PROTOCOL!  This is not the business of the IETF!
> Tools exist to help you filter spam.  Some, like spam assassin, are very
> good and quite sophisticated.  However, there is ALWAYS a tradeoff with
> using this sort of tool -- too narrow a criterion for acceptance and you
> lose real mail, too broad and you get all the spam anyway.  I can choose
> my level of tradeoff, and be fully aware of the risks.

   While the parameters of individual spam-filtering _should_ not be
the business of IETF, there is a very real issue raised by filtering
_after_ the SMTP session:

   During the SMTP session, it is quite possible to give an error which
is likely to reach the right person; after the SMTP session, you have
to "trust" the various header fields -- which are routinely forged by
spammers.

   In fact, we are now facing a _second_ denial-of-service problem
(the first being spam itself clogging your mailbox): excessive bounce
messages automatically directed to mailboxes forged by spammers. And
this by its nature is a distributed-denial-of-service problem, even
harder to protect against.

   Spam-filtering _after_ the SMTP session _should_ be deprecated by
IETF, IMHO. While there is no question that any recipient has the
right to ignore any message, SMTP was intended to either deliver the
message or send back an error; and the loss of this feature reduces
the utility of e-mail.

--
John Leslie <john@jlc.net>



From owner-ietf@ietf.org  Mon Feb 16 11:37:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03553
	for <ietf-archive@odin.ietf.org>; Mon, 16 Feb 2004 11:37:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AslUQ-0000OZ-1F
	for ietf-list@asgard.ietf.org; Mon, 16 Feb 2004 11:20:58 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AslHi-0004C4-MN
	for ietf@asgard.ietf.org; Mon, 16 Feb 2004 11:07:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28807
	for <ietf@ietf.org>; Mon, 16 Feb 2004 11:07:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AslHg-000125-00
	for ietf@ietf.org; Mon, 16 Feb 2004 11:07:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AslFd-0000cH-00
	for ietf@ietf.org; Mon, 16 Feb 2004 11:05:43 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[fm7feEloDLXEY82XoiOc/W35WnvnnTY6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AslDe-0000B8-00
	for ietf@ietf.org; Mon, 16 Feb 2004 11:03:39 -0500
Received: from ganesh.phy.duke.edu (ganesh.phy.duke.edu [152.3.182.51])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id 32D75A77CD; Mon, 16 Feb 2004 11:03:34 -0500 (EST)
Received: by ganesh.phy.duke.edu (Postfix, from userid 1337)
	id EE7F436DBC; Mon, 16 Feb 2004 11:03:32 -0500 (EST)
Date: Mon, 16 Feb 2004 11:03:32 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
To: John Leslie <john@jlc.net>
Cc: Ed Gerck <egerck@safevote.com>, Dean Anderson <dean@av8.com>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: covert channel and noise -- was Re: proposal ...
In-Reply-To: <20040216151935.GB11808@verdi>
Message-ID: <Pine.LNX.4.44.0402161038300.12141-100000@ganesh.phy.duke.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>    In fact, we are now facing a _second_ denial-of-service problem
> (the first being spam itself clogging your mailbox): excessive bounce
> messages automatically directed to mailboxes forged by spammers. And
> this by its nature is a distributed-denial-of-service problem, even
> harder to protect against.

I agree, and in fact pointed out that bounce messages from AV programs
are similar problem a week ago.  So perhaps the discussion should
separate into three different threads:

  a) Encryption and host authentication on the smtp channel.  This might
embrace open mail programs used as forwarding agents by both spammers
and viruses.

  b) What to do about bounces in general.  Bounce messages are
useful or even essential in many contexts, but they are a source of both
intentional and unintentional abuse in a world where headers are
routinely forged.

  c) Spam, what (if anything) to do about it at the IETF level.

It may be that good solutions to a) and b) may, together with some
support in the form of laws, suffice to greatly ameliorate both spam and
header-forged viruses by increasing the accountability of the enabling
networks.  Most of this traffic is ALREADY in violation of corporate
acceptable use agreements -- part of the problem is that many ISP's have
been very lax in enforcing acceptable use and tracking down violators.
Part of THAT problem is that the networks selling access to the ISP's
have in turn turned a blind eye to the ISP's.

Perhaps a header-level/protocol-level solution would be a generalization
of the postmaster address that points to a HUMAN responsible for
policing the network(s) where spam/viruses originate.  Yes, one could
argue that postmaster already is such an address, but many of the
smaller originating networks are run by amateurs and have no real
postmaster.  One really needs to be able to hit a recursive list of
postmasters along the message's delivery route with warnings about
violations of acceptable use.

> 
>    Spam-filtering _after_ the SMTP session _should_ be deprecated by
> IETF, IMHO. While there is no question that any recipient has the
> right to ignore any message, SMTP was intended to either deliver the
> message or send back an error; and the loss of this feature reduces
> the utility of e-mail.

I agree.  However, all of the observations made so far regarding
spam/virus filtering in general still apply to filtering at the SMTP
level.  I would say that NO keyword filtering could take place.  The
best that one could do at the protocol level would be to reject messages
that fail to meet a tighter criterion than is currently required.
Perhaps:

  a) All hosts must resolve with DNS.
  b) All hosts must support an encryption key registered with DNS that
permits all message hops to occur between registered hosts encrypted
with the destination host public key.
  c) The header autogenerate a postmaster-recursive email address for
reporting abuse to the entire delivery path.  This would put a rather
large burden on the main network backbone administrators -- they'd need
automated tools to help handle it.  OTOH, it would REALLY give them an
incentive to shut down networks that are a primary source of abuse until
they manage to police themselves.  Automated tools at the highest level
might just generate an "abuse histogram" that triggers a human response
only when levels rise above that which might be identified as
"reasonable" for a network participating in the eternal battle with the
bad guys.
  d) With keyed host registration, tools that can QUICKLY isolate an
originating host and bop its (ab)user (minimally get them off the
network, ideally "instantly" fine them or charge them money such as a
reconnection fee AFTER getting them off the network).  This would give
end users a strong incentive to police their own systems against viruses
and would give spammers additional costs to pay or additional charges to
be brought against them, should they try to skip out.

I personally would ALSO like it if AV vendors STOPPED bounce messages
altogether.  SMTP bounce messages have a point and are even necessary;
AV bounce messages are a joke, a waste of time, and a potential source
of serious abuse.  NO viruses currently exist that don't forge the
header, it is just that most viruses nowadays use random forged headers
out of the infected host's address books.  They could, however, all
claim to be from e.g. SCO or Microsoft (some already exist that do the
latter, but more for social engineering reasons than DDOS, I think).

  rgb

> 
> --
> John Leslie <john@jlc.net>
> 

Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Mon Feb 16 12:44:21 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08114
	for <ietf-archive@odin.ietf.org>; Mon, 16 Feb 2004 12:44:21 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AsmTo-0001YN-MN
	for ietf-list@asgard.ietf.org; Mon, 16 Feb 2004 12:24:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AsmHF-0000zV-IZ
	for ietf@asgard.ietf.org; Mon, 16 Feb 2004 12:11:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06271
	for <ietf@ietf.org>; Mon, 16 Feb 2004 12:11:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsmHE-0001l9-00
	for ietf@ietf.org; Mon, 16 Feb 2004 12:11:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsmGK-0001hg-00
	for ietf@ietf.org; Mon, 16 Feb 2004 12:10:29 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsmFT-0001dG-00
	for ietf@ietf.org; Mon, 16 Feb 2004 12:09:36 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1GH9Un2056985
	for ietf@ietf.org env-from <vjs>;
	Mon, 16 Feb 2004 10:09:30 -0700 (MST)
Date: Mon, 16 Feb 2004 10:09:30 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402161709.i1GH9Un2056985@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: covert channel and noise -- was Re: proposal ...
References: <Pine.LNX.4.44.0402161038300.12141-100000@ganesh.phy.duke.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "Robert G. Brown" <rgb@phy.duke.edu>

> ...
> I agree.  However, all of the observations made so far regarding
> spam/virus filtering in general still apply to filtering at the SMTP
> level. I would say that NO keyword filtering could take place.  The
> best that one could do at the protocol level would be to reject messages
> that fail to meet a tighter criterion than is currently required.

What is "the SMTP level"?  Is that during SMTP transactions between MTAs? 
Is "the protocol level" the same or something else?

If both of those "levels" refer to SMTP transactions between MTAs, then
the conclusion is wrong.  Except for local administrative hassles, all
spam and virus filtering that can be done later can instead be done
during SMTP transactions between MTAs.  Your SMTP server may need to
wait to until the end of the DATA command to object to messages
containing viruses, missing or bad SMTP headers or other objectionable
content, but that works fine.  I know of many millions of spam that
are filtred during the DATA command every day, and I don't claim to
know about any really big sites.

The only problems are:
  - local administrative choices that keep bastion SMTP servers ignorant
      of per-user filter preferences
  - filtering at the DATA command requires either (1) rejecting for
     all or no targets or (2) accepting for all targets and siliently
     discarding the message for those targets that want it filtered.

In theory the second problem could be fixed if the DATA command could
accept a vector of 250-OK/4yz-try-later/5yz-fatal responses, one for
each target named with a Rcpt_To command.  In practice the spam problem
will be solved one way or another long before such a protocol change
would be sufficiently widely deployed to matter.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Mon Feb 16 13:59:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11390
	for <ietf-archive@odin.ietf.org>; Mon, 16 Feb 2004 13:59:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Asnq6-0007Vl-AY
	for ietf-list@asgard.ietf.org; Mon, 16 Feb 2004 13:51:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AsnmB-0007K1-Ua
	for ietf@asgard.ietf.org; Mon, 16 Feb 2004 13:47:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11073
	for <ietf@ietf.org>; Mon, 16 Feb 2004 13:47:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Asnm8-00017b-00
	for ietf@ietf.org; Mon, 16 Feb 2004 13:47:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsnlE-00015R-00
	for ietf@ietf.org; Mon, 16 Feb 2004 13:46:29 -0500
Received: from mail7.atl.registeredsite.com ([64.224.219.81] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsnkO-00012h-00
	for ietf@ietf.org; Mon, 16 Feb 2004 13:45:37 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail7.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1GIjTuk016944;
	Mon, 16 Feb 2004 13:45:31 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Mon, 16 Feb 2004 12:45:28 -0600
Message-ID: <40310FBA.67634B88@nma.com>
Date: Mon, 16 Feb 2004 10:45:14 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Robert G. Brown" <rgb@phy.duke.edu>
CC: Dean Anderson <dean@av8.com>, Franck Martin <franck@sopac.org>,
        John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: covert channel and noise -- was Re: proposal ...
References: <Pine.LNX.4.44.0402152257020.1291-100000@lilith.rgb.private.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"Robert G. Brown" wrote:
> 
> On Sun, 15 Feb 2004, Ed Gerck wrote:
> 
> > We can't lock the
> > spammers' doors everywhere, we have to lock our door at our house.
> 
> No, what we can do is the same thing we do with our real mail box.  Make
> it illegal to send certain classes of mail, for example letter bombs and
> envelopes containing anthrax, and prosecute the hell out of anybody we
> catch who does so.  

On the flip side, this is a good example of how the anthrax threat was 
not handled. The solution was not to rely on the illegality of sending 
anthrax (which, obviously, wasn't enough of a deterrent) or the probability 
of prosecuting the sender (which we have not yet done), but on a "lock" 
that was put on all mail coming in. Mail that came from unknown senders 
was more carefully verified and even sterilized, some was backtraced and 
the sender was verified. 

But postal mail, contrary to email, cannot put a burden on the 
sender that is higher than the postage cost. Email, rather than 
being cost-free for all senders, can be made expensive to senders 
we don't know. And the way to do it mandatorily is by using code -- 
not law.

This is useful because our email is laced with the "anthrax" called 
spam. Filtering by subject line, email headers and body text is not 
enough, and frequently backfires by making us delay and even not 
read what would otherwise  be a message of interest.

BTW, the technique of imposing a task that burdens the sender in 
order to reduce interference due to rogue senders has a parallel
in spread-spectrum technology, for example. By only receiving messages
that are frequency-keyed as expected, my receiver can withstand
jamming (i.e., noise messages that are in-band -- "spam"). This
is in addition to other filters I have for post-processing.



From owner-ietf@ietf.org  Mon Feb 16 14:24:31 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13009
	for <ietf-archive@odin.ietf.org>; Mon, 16 Feb 2004 14:24:30 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AsoEd-0000pR-9t
	for ietf-list@asgard.ietf.org; Mon, 16 Feb 2004 14:16:51 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AsoDV-0000h6-4l
	for ietf@asgard.ietf.org; Mon, 16 Feb 2004 14:15:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12358
	for <ietf@ietf.org>; Mon, 16 Feb 2004 14:15:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsoDQ-00030U-00
	for ietf@ietf.org; Mon, 16 Feb 2004 14:15:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsoCX-0002uq-00
	for ietf@ietf.org; Mon, 16 Feb 2004 14:14:41 -0500
Received: from mail12.atl.registeredsite.com ([64.224.219.86] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsoBs-0002qH-00
	for ietf@ietf.org; Mon, 16 Feb 2004 14:14:00 -0500
Received: from safevote.com (taurus.hosting4u.net [209.35.191.122])
	by mail12.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1GJDrQU027981;
	Mon, 16 Feb 2004 14:13:53 -0500
Received: from safevote.com ([63.204.17.85]) by safevote.com ; Mon, 16 Feb 2004 13:13:52 -0600
Message-ID: <40311662.9EB66212@safevote.com>
Date: Mon, 16 Feb 2004 11:13:38 -0800
From: Ed Gerck <egerck@safevote.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Robert G. Brown" <rgb@phy.duke.edu>
CC: John Leslie <john@jlc.net>, Dean Anderson <dean@av8.com>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: covert channel and noise -- was Re: proposal ...
References: <Pine.LNX.4.44.0402161038300.12141-100000@ganesh.phy.duke.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"Robert G. Brown" wrote:

>   a) All hosts must resolve with DNS.

If you list why this isn't used today perhaps you
will change "must" to "may".

>   b) All hosts must support an encryption key registered with DNS that
> permits all message hops to occur between registered hosts encrypted
> with the destination host public key.

Mail privacy can only be guaranteed with an end-to-end encryption.
Securing email in message hops does nothing to prevent monitoring
at each host in the hop -- with some hosts not even advertised in
the header.

>   c) The header autogenerate a postmaster-recursive email address for
> reporting abuse to the entire delivery path. This would put a rather
> large burden on the main network backbone administrators -- they'd need
> automated tools to help handle it.  OTOH, it would REALLY give them an
> incentive to shut down networks that are a primary source of abuse until
> they manage to police themselves.  

This would create a huge liability for the backbone administrators --
for example, one false abuse report and they could be sued for disrupting 
lawful communications. Human supervision actually increases the liability
-- it can't be blamed on a software glitch.


>   d) With keyed host registration, tools that can QUICKLY isolate an
> originating host and bop its (ab)user (minimally get them off the
> network, ideally "instantly" fine them or charge them money such as a
> reconnection fee AFTER getting them off the network).

Machines running amok, quickly killing off other machines without
recourse, without explanation. A kangaroo court for email, penalizing
the users.

>  This would give
> end users a strong incentive to police their own systems against viruses
> and would give spammers additional costs to pay or additional charges to
> be brought against them, should they try to skip out.

Again, what you propose is to penalize the victim -- the user. That's
exactly what we should stop doing.
 
> I personally would ALSO like it if AV vendors STOPPED bounce messages
> altogether.

Free speech, good luck.



From owner-ietf@ietf.org  Mon Feb 16 14:56:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15456
	for <ietf-archive@odin.ietf.org>; Mon, 16 Feb 2004 14:56:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AsoV9-0002lw-BX
	for ietf-list@asgard.ietf.org; Mon, 16 Feb 2004 14:33:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AsoUm-0002ib-0t
	for ietf@asgard.ietf.org; Mon, 16 Feb 2004 14:33:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13831
	for <ietf@ietf.org>; Mon, 16 Feb 2004 14:33:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsoUk-00055X-00
	for ietf@ietf.org; Mon, 16 Feb 2004 14:33:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsoTl-00051I-00
	for ietf@ietf.org; Mon, 16 Feb 2004 14:32:30 -0500
Received: from mail10.atl.registeredsite.com ([64.224.219.84] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsoSp-0004wh-00
	for ietf@ietf.org; Mon, 16 Feb 2004 14:31:31 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail10.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1GJVUmg019173
	for <ietf@ietf.org>; Mon, 16 Feb 2004 14:31:30 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Mon, 16 Feb 2004 13:31:29 -0600
Message-ID: <40311A84.D06F55E3@nma.com>
Date: Mon, 16 Feb 2004 11:31:16 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: covert channel and noise -- was Re: proposal ...
References: <Pine.LNX.4.44.0402161038300.12141-100000@ganesh.phy.duke.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,TO_ADDRESS_EQ_REAL 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"Robert G. Brown" wrote:

>   a) All hosts must resolve with DNS.

If you list why this isn't used today perhaps you
will change "must" to "may".

>   b) All hosts must support an encryption key registered with DNS that
> permits all message hops to occur between registered hosts encrypted
> with the destination host public key.

Mail privacy can only be guaranteed with an end-to-end encryption.
Securing email in message hops does nothing to prevent monitoring
at each host in the hop -- with some hosts not even advertised in
the header.

>   c) The header autogenerate a postmaster-recursive email address for
> reporting abuse to the entire delivery path. This would put a rather
> large burden on the main network backbone administrators -- they'd need
> automated tools to help handle it.  OTOH, it would REALLY give them an
> incentive to shut down networks that are a primary source of abuse until
> they manage to police themselves.  

This would create a huge liability for the backbone administrators --
for example, one false abuse report and they could be sued for disrupting 
lawful communications. Human supervision actually increases the liability
-- it can't be blamed on a software glitch.


>   d) With keyed host registration, tools that can QUICKLY isolate an
> originating host and bop its (ab)user (minimally get them off the
> network, ideally "instantly" fine them or charge them money such as a
> reconnection fee AFTER getting them off the network).

Machines running amok, quickly killing off other machines without
recourse, without explanation. A kangaroo court for email, penalizing
the users.

>  This would give
> end users a strong incentive to police their own systems against viruses
> and would give spammers additional costs to pay or additional charges to
> be brought against them, should they try to skip out.

Again, what you propose is to penalize the victim -- the user. That's
exactly what we should stop doing.
 
> I personally would ALSO like it if AV vendors STOPPED bounce messages
> altogether.

Free speech, good luck.



From owner-ietf@ietf.org  Mon Feb 16 19:15:20 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15068
	for <ietf-archive@odin.ietf.org>; Mon, 16 Feb 2004 19:15:20 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AssjM-0004gB-FN
	for ietf-list@asgard.ietf.org; Mon, 16 Feb 2004 19:04:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AsrhM-0008FL-RX
	for ietf@asgard.ietf.org; Mon, 16 Feb 2004 17:58:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06256
	for <ietf@ietf.org>; Mon, 16 Feb 2004 17:58:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsrhD-0005yx-00
	for ietf@ietf.org; Mon, 16 Feb 2004 17:58:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AsrgC-0005qp-00
	for ietf@ietf.org; Mon, 16 Feb 2004 17:57:33 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AsrfF-0005in-00
	for ietf@ietf.org; Mon, 16 Feb 2004 17:56:33 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1GMtW5B023128
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 16 Feb 2004 17:55:32 -0500
Date: Mon, 16 Feb 2004 17:55:32 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Ed Gerck <egerck@safevote.com>
cc: Ed Gerck <egerck@nma.com>, Franck Martin <franck@sopac.org>,
        John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: covert channel and noise -- was Re: proposal ...
In-Reply-To: <403020D4.90BC2694@safevote.com>
Message-ID: <Pine.LNX.4.44.0402161644000.21587-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sun, 15 Feb 2004, Ed Gerck wrote:

> Dean Anderson wrote:
> > 
> > It isn't the case that the spammer intended to send a message about
> > the superbowl, but somehow "noise" altered the message to a
> > solicitation on viagra. Rather, they intended to send a message on
> > viagra, and you recieved their message, noise free. But seeing the
> > solication for viagra, you became upset, and reported a complaint
> > about the inappropriate use of the channel. In
> > information-theory-speak, you report a "communication in violation of
> > the security model"; a covert or sneaky channel.
> 
> I guess we agree that if the message can be read by the intended recipient 
> then it's not in a covert channel. A covert channel is one that can't even 
> be detected by the intended recipient. But, you may ask, "who" is the 
> intended recipient? 

Err, we do not agree on that. You still misunderstand the nature of a
covert channel.  I suggest you re-read the definitions and references in
the reposted messages from Ellis Cohen and Stavros Macrackis.

A covert or sneaky channel is merely one in which the communication is
//not authorized by the security model// It has nothing to do with
readability or detectability.  There is no theorem that says covert
channels cannot be detected. Quite obviously, they are detected, and some
action might be taken.  Theory just says that you cannot prove they aren't
there.  Let me put it another way:  A "null" reading on your "covert
channel detector" does not mean there aren't any covert channels--Just
that you haven't detected any.  This is a subtle, yet significant
difference.

In yet other words: you whack-a-mole when you find one, but you can't say
that there aren't any moles. It is not a game you can win.  You have to
keep looking and keep whacking, so long as there are moles to pop up. The
arcade whack-a-mole game stops when you run out of time, but our game only
stops when no one wants to spam or conduct abuse or government
intervention prevents them from playing.

We now have a legal process to use against abusers who are not
commercial--most, if not all, genuine commercial spammers will simply
comply with the law.  That leaves those who aren't genuinely commercial,
and whose intent it is to annoy people.

> An example of such a covert channel is if a spammer hides information 
> in the subject line by using wrongly spelled forms of "viagra", 

This could be a covert channel. But its also possible that the whole spam
message even with a correctly spelled viagra would be a covert or sneaky
channel if it is not //authorized by the security model//, and the
"security model" is simply an Acceptable Use Policy statement not to do
that.  In this case, you may have a very weak "covert channel detection"  
process. But extreme weakness in the process is irrelvent to the theory.  
What, if anything, has to be done to get past the detection process and
the security model and into your mailbox is irrelevant.  The security
model can be made quite extensive, such as with Mandatory Access Controls
as implemented in secure operating systems.  Even so, one cannot say that
there aren't covert channels.  One can say other things about them, but
not that thing.

Information theory has proved itself useful to the analysis of anti-spam
schemes. Besides being able to rule out a number of schemes which promise
to be complete technical solutions to spam, we also see what range of
solutions can be implemented about spam and what results we can expect to
see from that range.

Consider the case of Mandatory Access Controls (MAC) for operating
systems.  We see that if we tighten up the controls on the flow of
information, that we improve our chances of detection. Particularly, we
hope to detect people trying to find covert channels before they succeed
in finding one.  This is very expensive, both in supervision costs, and in
the difficulty of training workers to use such systems.  In the case of
classified government information, the cost is justified.  Having a
potential spy create a denied MAC security event while probing for a
covert channel is well worth the effort, even if you can't be sure that
they will be caught.  The spy, or even potential spy or stupid user, is
then removed from the secured areas. Even honest, but stupid users are
removed, and this can be rationalized because they don't have the capacity
to be trusted with sensitive information.  It works because the same
'mole' doesn't get repeated chances to find the channel that will be
successful, and there are legal processes to make that happen. You cannot
lie on a security clearance application when it asks your identity, and if
you've ever had a clearance revoked or denied.  Expensive checks are made
to ensure that your answers are truthful.

But the same can't be said about spammers/abusers.  We can't escort them
out, and we can't even be sure of their identity in a civil context.  
Frequently, they are using someone else's identity or computer.  We
already detect them quite easily. But there is little that can be done.
Once positively detected, we can block some spam for a while.  We improve
filters, and spammers/abusers eventually adapt.  This basic process cannot
be stopped, unless the spammers/abusers stop of their own accord or some
legal process is brought to bear to force them to stop.  We can probably
apply bayesian filters, and I think AI, text summarization, etc to the
problem to help automate the task. Of course, spammers can use automatic
inverse methods to automate the task of finding channels that aren't
blocked.  However automated, the fundamental governing process described
by information theory isn't altered.


		--Dean





From owner-ietf@ietf.org  Tue Feb 17 05:50:32 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22934
	for <ietf-archive@odin.ietf.org>; Tue, 17 Feb 2004 05:50:32 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1At2bq-0005zJ-VC
	for ietf-list@asgard.ietf.org; Tue, 17 Feb 2004 05:37:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1At2b4-0005rH-Ly
	for ietf@asgard.ietf.org; Tue, 17 Feb 2004 05:36:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22623
	for <ietf@ietf.org>; Tue, 17 Feb 2004 05:36:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At2b2-0004CF-00
	for ietf@ietf.org; Tue, 17 Feb 2004 05:36:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At2a5-00049V-00
	for ietf@ietf.org; Tue, 17 Feb 2004 05:35:58 -0500
Received: from [202.108.44.205] (helo=163.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1At2ZH-000471-00
	for ietf@ietf.org; Tue, 17 Feb 2004 05:35:08 -0500
Received: from wl302 (unknown [211.67.24.168])
	by 192.168.1.205 (Coremail) with SMTP id RZkCAE3uMUA1ABio.1
	for <ietf@ietf.org>; Tue, 17 Feb 2004 18:34:59 +0800 (CST)
X-Originating-IP: [211.67.24.168]
Message-ID: <009601c3f542$27215b50$a81843d3@wl302>
From: "wang liang" <wangliang_f@163.com>
To: <ietf@ietf.org>
Subject: New BOF in Application Area (Internet information retrieval infrastructure)
Date: Tue, 17 Feb 2004 18:38:10 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

There has been some discussion for Internet information retrieval service in
work groups of IRTF. Now this issue will be discussed in the BOF of
Application Area.

As one of most important services of Internet, current information retrieval
service is still far from our expectation---precise, comprehensive and fresh
information. This problem may become more serious with the rapid development
of Internet. We need pay more attention to this issue. This BOF is just for
it. Wish you can participate in.

The date of this BOF will be determined soon.

The content of BOF:

Internet Information Retrieval Infrastructure(iiri)
=================================
CHAIRS: Guo Yiping (gyp@hust.edu.cn)
        Wang Liang (wangliang_f@yahoo.com)

Co-Chair: Andrew Newton(andy@hxr.us)

What's the main purpose of Internet? Information retrieval and exchanging.
But what's the most important principle to judge a network? Maybe
communication speed. For common user, they can't feel search service in GB
Internet is better than that in MB networks. The great progress of Internet
didn't bring the great improvement in its main service.
Now Internet is going far and far from their original aim, "knowledge source
of human being", and transforming into a jumbled information sea. Many
experts are mainly concerned with "physical Internet", but now we need pay
more attention to "information Internet".
Information retrieval services may be the most important service of
Internet, but there is till no a special work group for it. Current
commercial search engines meet many bottleneck problems in coverage and
recency. Its service is far from our expectation. It's just a web pages
search system. We can also get information from many other information
resources such as special databases, FTP search engine, P2P, etc. So a work
group for Internet information retrieval system is very necessary. We have
proposed a basic information retrieval frame, DRIS (Domain Resource
Integration System), for this issue. Any related topic could be discussed in
this group.

AGENDA:
Draft agenda for the BOF:
----------------------------------------------------------------------
History of IETF work in this area
15 min
Introduction to problem space and DRIS                                15 min
Internet Information retrieval infrastructure and digital library    15 min
draft-liang-irpdl-03.txt
15 min
IPv6 and information retrieval system
15 min
Discussion
remaining time

Description of this work group(DRIS):
With the rapid increase of the web pages, the coverage of search engines
will become poorer and the update interval will be much longer. If the
current architecture of search engines is still in use, it will be an
impossible mission to find the precise and comprehensive information in the
future. This problem will be more serious when IPV6 technology is widely
implemented in communication networks. The problem of "Too much information
means no information" may become a disaster with information explosion. To
solve this problem, there should be an efficient information management
system for Internet.
In this group, Domain Resource Integrated System--DRIS will be proposed.
DRIS is a distributed information retrieval system, which will build the
information retrieval infrastructure for the Internet and also can be
regarded as a kind of Internet information management system.
DRIS is a hierarchical distributed search system and comprise three kinds of
information retrieval system, conventional database system, distributed
search system and metadata harvest system. We will first define the basic
search system and then define the entire DRIS.
Specific work items are:
1 Standard distributed search system. It defines the platform-independent
search interface and a collection description standard for heterogeneous
information resources. An I-D "information retrieval protocol for digital
resources" has been proposed.
2 Standard metadata harvest system. A protocol based some available opening
standard like OAI will be proposed. It will define a standard metadata that
can be compatible with most database system.
3 Standard public web pages search system.
4 DRIS. It will define entire DRIS. It includes its whole architecture, the
relation between different nodes, etc.
5 DRIS and IPV6. The cooperation with IPV6 WG will be proposed. IPV6 will be
the most distinct feather of next generation Internet.IPV6 is still in
improving and any technology that can benefit the Internet all can be added
to the IPV6 system. Since the searching is the main service of most user of
Internet and this service is not so satisfied to us in current Internet, why
not take this request into account when build the new Internet. For example,
in IPV6, all kinds of data flows are assigned a priority, and then Internet
can guarantee a high priority to the data flow of DRIS. So there may need
some considerations for the relation between DRIS and IPV6.

Mailing list
dris@mail.hust.edu.cn

Archive and general information:
http://www.lib.hust.edu.cn/dl-lib/English/main.htm





From jci92vuv@yahoo.com  Tue Feb 17 09:23:14 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29340
	for <ietf-archive@ietf.org>; Tue, 17 Feb 2004 09:23:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At682-0002fz-00
	for ietf-archive@ietf.org; Tue, 17 Feb 2004 09:23:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At677-0002by-00
	for ietf-archive@ietf.org; Tue, 17 Feb 2004 09:22:18 -0500
Received: from yahoobb219005156058.bbtec.net ([219.5.156.58])
	by ietf-mx with smtp (Exim 4.12)
	id 1At66n-0002Y1-00; Tue, 17 Feb 2004 09:21:58 -0500
Received: from [97.53.26.23]
	by YahooBB219005156058.bbtec.net with ESMTP id 35684746
	for <ietf-action-req-dist@ietf.org>; Tue, 17 Feb 2004 14:19:00 +0000
Message-ID: <7-2lfpw$p94b@xd18u.qk>
From: "Ina Benson" <jci92vuv@yahoo.com>
Reply-To: "Ina Benson" <jci92vuv@yahoo.com>
To: ietf-action-req-dist@ietf.org
Subject: Fwd: our offer
Date: Tue, 17 Feb 04 14:19:00 GMT
X-Mailer: Microsoft Outlook, Build 10.0.2616
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="8_79C_C_8EBDB"
X-Priority: 3
X-MSMail-Priority: Normal
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=13.3 required=5.0 tests=AWL,DATE_SPAMWARE_Y2K,
	FORGED_MUA_OUTLOOK,FORGED_OUTLOOK_HTML,FORGED_OUTLOOK_TAGS,
	FORGED_YAHOO_RCVD,HTML_20_30,HTML_IMAGE_ONLY_10,HTML_MESSAGE,
	MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,
	MISSING_MIMEOLE autolearn=no version=2.60
X-Spam-Report: 
	*  4.4 DATE_SPAMWARE_Y2K Date header uses unusual Y2K formatting
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  1.1 HTML_IMAGE_ONLY_10 BODY: HTML: images with 800-1000 bytes of words
	*  0.5 HTML_20_30 BODY: Message is 20% to 30% HTML
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset
	*  0.5 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  1.1 FORGED_OUTLOOK_HTML Outlook can't send HTML message only
	*  1.1 FORGED_OUTLOOK_TAGS Outlook can't send HTML in this format
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts
	*  1.6 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook
	* -0.0 AWL AWL: Auto-whitelist adjustment


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

<html><body  bgcolor=3D"#FFFFFF" link=3D"#0033CC" vlink=3D"#0033CC">
<center><a href=3D"http://www.terra.es/personal5/554664/r1/" target=3D"_bl=
ank"><img src=3D"http://www.terra.es/personal5/qp2wo5ei8/1.gif" border=3D"=
0"></a>
<br><br><font color=3D"#000000">If the message is not loading <a href=3D"h=
ttp://www.terra.es/personal5/554664/r1/"><b>try this</b></a></center>
<p style=3D"font-size:0px; color:white" align=3D"left">
 scruple  clapeyron  concave lars , shade  =
barth . 
 irrelevancy droop allocable , finch  load . =
bespectacled pax tnt, 
 asymptotic vex . dominic , willoughby acre , =
irrespective . allan 
  . florid , evolutionary rooseveltian , atalanta . =
exhaust . euclidean , scrutiny 
  leguminous , afterimage . egotism . advisor , =
designate elate , mendacious 
  . beget . virgo , indies applicable , =
peptide . africa . suffolk 
  . compliment , kennedy evolutionary , cartography . =
bateau . barbecue , marc 
  wormy , cheyenne . carload . deprecate , =
cowpea bohemia , dram 
  . deuterium . cayuga , aspersion morale , =
birth . bock . decontrol 
  bolshevist , boost . prey . shatterproof , =
rivet silo , watertown 
  . you'll . housebreak , immiscible harm , =
demodulate . alba . clad 
  , frieze unruly , repentant . andrew . =
pointwise , binge skirmish 
  , daunt . director . transcript , banister =
bizet , irredentism . carnegie 
  . glass , flowery gillette , decline . =
equipping . quack , account
   beep  degassing  dorado congener , mullen  =
sonnet . 
 orthonormal fascist holt , therefrom  zing . =
gateway headboard miocene, 
 gorham bahama . modicum , glandular endpoint , =
dewar . diluent 
  . booze
</p></body></html>vfcrjb b

--8_79C_C_8EBDB--



From owner-ietf@ietf.org  Tue Feb 17 13:49:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26372
	for <ietf-archive@odin.ietf.org>; Tue, 17 Feb 2004 13:49:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1At9vH-0000RA-Gq
	for ietf-list@asgard.ietf.org; Tue, 17 Feb 2004 13:26:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1At8X4-0002jd-0m
	for ietf@asgard.ietf.org; Tue, 17 Feb 2004 11:57:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16707
	for <ietf@ietf.org>; Tue, 17 Feb 2004 11:57:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At8X2-00058L-00
	for ietf@ietf.org; Tue, 17 Feb 2004 11:57:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At8WB-00053Y-00
	for ietf@ietf.org; Tue, 17 Feb 2004 11:56:20 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At8VR-00050I-00
	for ietf@ietf.org; Tue, 17 Feb 2004 11:55:34 -0500
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i1HGtPnp028660
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 17 Feb 2004 08:55:26 -0800 (PST)
Received: from [205.214.163.53] (carbuncle.qualcomm.com [129.46.227.161])
	by magus.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i1HGtNVK015126;
	Tue, 17 Feb 2004 08:55:24 -0800 (PST)
Mime-Version: 1.0
X-Sender: hardie@mage.qualcomm.com
Message-Id: <p0602041abc57f73be9fe@[205.214.163.53]>
In-Reply-To: <009601c3f542$27215b50$a81843d3@wl302>
References: <009601c3f542$27215b50$a81843d3@wl302>
Date: Tue, 17 Feb 2004 08:55:31 -0800
To: "wang liang" <wangliang_f@163.com>, <ietf@ietf.org>
From: Ted Hardie <hardie@qualcomm.com>
Subject: Re: New BOF in Application Area (Internet information retrieval
 infrastructure)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 6:38 PM +0800 02/17/2004, wang liang wrote:
>There has been some discussion for Internet information retrieval service in
>work groups of IRTF. Now this issue will be discussed in the BOF of
>Application Area.
>
>As one of most important services of Internet, current information retrieval
>service is still far from our expectation---precise, comprehensive and fresh
>information. This problem may become more serious with the rapid development
>of Internet. We need pay more attention to this issue. This BOF is just for
>it. Wish you can participate in.
>
>The date of this BOF will be determined soon.

The timing and full agenda are available at:

http://www.ietf.org/ietf/04mar/iiri.txt

Note that the chairs are different from that listed in Wang Liang's
recent note; Guo Yiping and Andy Newton will chair the meeting,
since Wang Liang will be a major presenter.  John Klensin will
be presenting the history of IETF work in the area, but it would be
useful if those present were familiar with the previous work
in METAD and FIND as well as the citations given in the BoF
agenda.
			regards,
				Ted Hardie




From owner-ietf@ietf.org  Tue Feb 17 14:25:19 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28393
	for <ietf-archive@odin.ietf.org>; Tue, 17 Feb 2004 14:25:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtAj3-0005AE-Re
	for ietf-list@asgard.ietf.org; Tue, 17 Feb 2004 14:17:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtAdi-0004Nn-Ax
	for ietf@asgard.ietf.org; Tue, 17 Feb 2004 14:12:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27755
	for <ietf@ietf.org>; Tue, 17 Feb 2004 14:12:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtAdh-0003lz-00
	for ietf@ietf.org; Tue, 17 Feb 2004 14:12:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtAcj-0003hs-00
	for ietf@ietf.org; Tue, 17 Feb 2004 14:11:13 -0500
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtAbn-0003eJ-00
	for ietf@ietf.org; Tue, 17 Feb 2004 14:10:15 -0500
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id F1075E08F6; Tue, 17 Feb 2004 14:10:14 -0500 (EST)
Date: Tue, 17 Feb 2004 14:10:14 -0500
From: John Leslie <john@jlc.net>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: Re: covert channel and noise -- was Re: proposal ...
Message-ID: <20040217191014.GH11808@verdi>
References: <200402161709.i1GH9Un2056985@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200402161709.i1GH9Un2056985@calcite.rhyolite.com>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Vernon Schryver <vjs@calcite.rhyolite.com> wrote:
> 
> I know of many millions of spam that are filtred during the DATA command
> every day, and I don't claim to know about any really big sites.
> 
> The only problems are:
>   - local administrative choices that keep bastion SMTP servers ignorant
>       of per-user filter preferences

   This is a feature, not a problem. If the end user wants a filtering
process individualized that much, s/he should choose to use a SMTP
server which agrees to do so.

>   - filtering at the DATA command requires either (1) rejecting for
>      all or no targets or (2) accepting for all targets and siliently
>      discarding the message for those targets that want it filtered.

   Alternatively, the receiving SMTP server could reject any multiply-
addressed email.

   Is it actually that unreasonable to apply the most-restrictive
filtering rules in the case of multiply-addressed email?

   (Silently discarding _is_ a bad idea, when done by the SMTP server
itself. IMHO, it's better to mark for later discard -- which actually
could be done in such a way as to mark only for those recipients who
requested the more restrictive filtering.)

> In theory the second problem could be fixed if the DATA command could
> accept a vector of 250-OK/4yz-try-later/5yz-fatal responses, one for
> each target named with a Rcpt_To command.  In practice the spam problem
> will be solved one way or another long before such a protocol change
> would be sufficiently widely deployed to matter.

   Agreed: that radical a change in SMTP wouldn't percolate through
quickly enough.

--
John Leslie <john@jlc.net>



From owner-ietf@ietf.org  Tue Feb 17 16:03:06 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05529
	for <ietf-archive@odin.ietf.org>; Tue, 17 Feb 2004 16:03:06 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtC89-0007pQ-0a
	for ietf-list@asgard.ietf.org; Tue, 17 Feb 2004 15:47:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtC7p-0007dm-AO
	for ietf@asgard.ietf.org; Tue, 17 Feb 2004 15:47:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04426
	for <ietf@ietf.org>; Tue, 17 Feb 2004 15:47:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtC7n-0003bK-00
	for ietf@ietf.org; Tue, 17 Feb 2004 15:47:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtC6y-0003Xa-00
	for ietf@ietf.org; Tue, 17 Feb 2004 15:46:33 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtC6F-0003TP-00
	for ietf@ietf.org; Tue, 17 Feb 2004 15:45:48 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1HKjkku063496
	for ietf@ietf.org env-from <vjs>;
	Tue, 17 Feb 2004 13:45:46 -0700 (MST)
Date: Tue, 17 Feb 2004 13:45:46 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402172045.i1HKjkku063496@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: covert channel and noise -- was Re: proposal ...
References: <20040217191014.GH11808@verdi>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: John Leslie 

> ...
> >   - local administrative choices that keep bastion SMTP servers ignorant
> >       of per-user filter preferences
>
>    This is a feature, not a problem. If the end user wants a filtering
> process individualized that much, s/he should choose to use a SMTP
> server which agrees to do so.

That is a feature only if the user accepts the consequences of discarding
mail without generating bounces, including not informing senders of false
positives.  Bounces from internal spam filters (either in MUAs or MTAs
inside organizations) are a major source of unsolicited bulk mail or spam.


> >   - filtering at the DATA command requires either (1) rejecting for
> >      all or no targets or (2) accepting for all targets and siliently
> >      discarding the message for those targets that want it filtered.
>
>    Alternatively, the receiving SMTP server could reject any multiply-
> addressed email.

People running SMTP servers that handle 100K or more msgs/day have
been uniformly horrified when I've suggested that.  I don't really
understand why, but I have given up on the idea.



>    (Silently discarding _is_ a bad idea, when done by the SMTP server
> itself. IMHO, it's better to mark for later discard -- which actually
> could be done in such a way as to mark only for those recipients who
> requested the more restrictive filtering.)

A better positition is that everything should be logged, particularly
including discarded mail, and in that case, enough of bodies to allow
targets to identify senders and the nature of the discarded messages.
Of course, one should assume users won't normally look at those logs.
Spam you read is not filtered, but at most categorized and stigmatized.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Tue Feb 17 16:42:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07975
	for <ietf-archive@odin.ietf.org>; Tue, 17 Feb 2004 16:42:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtCsa-0001Hg-7U
	for ietf-list@asgard.ietf.org; Tue, 17 Feb 2004 16:35:44 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtCsK-00016O-2i
	for ietf@asgard.ietf.org; Tue, 17 Feb 2004 16:35:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07300
	for <ietf@ietf.org>; Tue, 17 Feb 2004 16:35:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtCsI-0007hK-00
	for ietf@ietf.org; Tue, 17 Feb 2004 16:35:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtCrQ-0007dp-00
	for ietf@ietf.org; Tue, 17 Feb 2004 16:34:32 -0500
Received: from smtp.exodus.net ([66.35.230.237] helo=smtp02-w.exodus.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtCr7-0007Za-00; Tue, 17 Feb 2004 16:34:13 -0500
Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174])
	by smtp02-w.exodus.net (8.12.8/8.12.8) with ESMTP id i1HIgvEv006145;
	Tue, 17 Feb 2004 12:42:57 -0600
Received: from [192.168.2.2] (unverified [207.31.248.169]) by accounting.espmail.com
 (Rockliffe SMTPRA 5.2.5) with ESMTP id <B0018357928@ms101.mail1.com>;
 Tue, 17 Feb 2004 13:33:42 -0800
Mime-Version: 1.0
X-Sender: margaret@thingmagic.com@ms101.mail1.com
Message-Id: <p06020416bc5835d0a15b@[192.168.2.2]>
Date: Tue, 17 Feb 2004 16:32:52 -0500
To: ietf@ietf.org, solutions@alvestrand.no, wgchairs@ietf.org,
        bofchairs@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Subject: Educational Sessions in Seoul
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


Hi All,

The EDU Team is offering several training sessions on Sunday afternoon in Seoul
that are open to ALL IETF ATTENDEES.  These sessions include:

- Newcomers Training (in both English and Korean)
- Editors Training
- Introductory WG Chairs Training
- Security Tutorial

Details about these sessions can be found below.

Please note that you do not need to be a current Editor or WG Chair to attend
those sessions, these sessions are all open to everyone!  So, show up early
and learn more about how to work effectively within the IETF.

Margaret



Sunday, February 29, 2004
=========================

1300-1400  Newcomer's Training in English -- Location??  (Spencer Dawkins)

            An introduction to the IETF for new or recent IETF
            attendees.  Covers the IETF document processes, the
            structure of the IETF, and tips for new attendees to
            be successful in the IETF environment.

1400-1500  Newcomer's Training in Korean -- Location??  (ChangJoon Kim)

            [Include description on agenda in Korean, if possible.]

            An introduction to the IETF for new or recent IETF
            attendees.  Covers the IETF document processes, the
            structure of the IETF, and tips for new attendees to
            be successful in the IETF environment.

1300-1500  Editor's Training -- Location??  (Avri Doria)

            Training for current or aspiring IETF document
            editors.  Covers the roles and responsibilities
            of a document editor, and includes advice on
            producing a high-quality IETF specification.

1300-1500  Intro WG Chairs Training -- Location??  (Margaret Wasserman)

            Introductory training for new or aspiring WG
            chairs.  Covers the role and responsibilities of
            a WG chair, and includes advice on how to run a
            WG that is fair, open and productive.  This class
            is open to all IETF attendees.

1500-1700  Security Tutorial -- Location??  (Radia Perlman)

            All IETF attendees need to be aware of the security
            implications of our design choices.  This session
            offers a basic primer in protocol security, as well
            as advice on how to write the Security Considerations
            sections required for all IETF documents.




From owner-ietf@ietf.org  Tue Feb 17 16:49:51 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05533
	for <ietf-archive@odin.ietf.org>; Tue, 17 Feb 2004 16:03:06 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtCEu-0000kB-JJ
	for ietf-list@asgard.ietf.org; Tue, 17 Feb 2004 15:54:44 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtCET-0000Yk-Et
	for ietf@asgard.ietf.org; Tue, 17 Feb 2004 15:54:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04710
	for <ietf@ietf.org>; Tue, 17 Feb 2004 15:54:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtCER-00040i-00
	for ietf@ietf.org; Tue, 17 Feb 2004 15:54:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtCDS-0003wc-00
	for ietf@ietf.org; Tue, 17 Feb 2004 15:53:15 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtCCV-0003t0-00
	for ietf@ietf.org; Tue, 17 Feb 2004 15:52:15 -0500
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i1HKqBnp015126
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 17 Feb 2004 12:52:12 -0800 (PST)
Received: from [205.214.163.53] (carbuncle.qualcomm.com [129.46.227.161])
	by sabrina.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i1HKq9lH011939;
	Tue, 17 Feb 2004 12:52:10 -0800 (PST)
Mime-Version: 1.0
X-Sender: hardie@mage.qualcomm.com
Message-Id: <p0602041ebc582f300762@[205.214.163.53]>
In-Reply-To: <p0602041abc57f73be9fe@[205.214.163.53]>
References: <009601c3f542$27215b50$a81843d3@wl302>
 <p0602041abc57f73be9fe@[205.214.163.53]>
Date: Tue, 17 Feb 2004 12:52:17 -0800
To: "wang liang" <wangliang_f@163.com>, <ietf@ietf.org>
From: Ted Hardie <hardie@qualcomm.com>
Subject: Re: New BOF in Application Area (Internet information retrieval 
 infrastructure)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 8:55 AM -0800 02/17/2004, Ted Hardie wrote:
>It would be useful if those present were familiar with the previous work
>in METAD and FIND as well as the citations given in the BoF
>agenda.

By the way,  the old FIND charter and documents are listed here:

http://www.ietf.org./html.charters/OLD/find-charter.html

and METAD mailing list archives are at:

http://www.usrlocalsrc.org/bunyip/metad.archive/

			regards,
				Ted Hardie



From owner-ietf@ietf.org  Tue Feb 17 18:35:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16837
	for <ietf-archive@odin.ietf.org>; Tue, 17 Feb 2004 18:35:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtEa5-0005MD-49
	for ietf-list@asgard.ietf.org; Tue, 17 Feb 2004 18:24:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtEZk-00059v-Sc
	for ietf@asgard.ietf.org; Tue, 17 Feb 2004 18:24:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16302
	for <ietf@ietf.org>; Tue, 17 Feb 2004 18:24:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtEZj-00027u-00
	for ietf@ietf.org; Tue, 17 Feb 2004 18:24:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtEYq-00025Q-00
	for ietf@ietf.org; Tue, 17 Feb 2004 18:23:29 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[UImqnmpRd0e0PUB/CSJ3opNmW8eeD045])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtEYc-00022e-00
	for ietf@ietf.org; Tue, 17 Feb 2004 18:23:14 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id 5F192A77DB; Tue, 17 Feb 2004 18:23:07 -0500 (EST)
Date: Tue, 17 Feb 2004 17:47:32 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: Re: covert channel and noise -- was Re: proposal ...
In-Reply-To: <200402172045.i1HKjkku063496@calcite.rhyolite.com>
Message-ID: <Pine.LNX.4.44.0402171555160.20733-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HOT_NASTY autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 17 Feb 2004, Vernon Schryver wrote:

> >    (Silently discarding _is_ a bad idea, when done by the SMTP server
> > itself. IMHO, it's better to mark for later discard -- which actually
> > could be done in such a way as to mark only for those recipients who
> > requested the more restrictive filtering.)

Or, mark for later accept/reject decisioning AFTER the SMTP server per
se, in the filter pipeline between the server and the mail spool of the
addressee.  Spam assassin does the right thing already (and this is
exactly what it does).

> 
> A better positition is that everything should be logged, particularly
> including discarded mail, and in that case, enough of bodies to allow
> targets to identify senders and the nature of the discarded messages.
> Of course, one should assume users won't normally look at those logs.
> Spam you read is not filtered, but at most categorized and stigmatized.

Logging a message you reject is nearly a waste of time.  In order to
recover the message (as you note, nobody ever looks at the logs, which
are VERY LARGE for a busy mailer and beyond human capacity to scan), it
really requires an out-of-band message telling you there is a message to
be recovered.  As in calling somebody up and asking them why you haven't
paid your e-bills (rejected as spam).  In most cases it will require a
retransmission and out-of-band communications to complete the
transaction, because what you have done is made email an unreliable
messaging service for valuable, wanted, messages.

This is where, and why, I take issue with filtering and discarding at
the level of the SMTP server, unless the accept/reject decision can be
made with 100% precision (no false positives, no false negatives, and it
may not be good even then because MY idea of the correct basis for the
decision may not be the same as YOURS).

Imagine a networking transport protocol such as TCP, that discarded
packets not based on their header information (according to any
protocol-level criterion you like) but on their CONTENT, using a
moderately arcane ruleset designed to identify high-level human patterns
such as spam from the content information, applied to the content in a
complex and highly multivariate decision tree.  Hmmm, pretty ugly for a
TRANSPORT LAYER.

It's not that filtering based on non-header-linked aspects of content is
or isn't a good idea in some cases.  It is that it has no business being
in the specification of TCP.  TCP is about reliable delivery and
sequencing of packets.  It (as a protocol) has nothing to do with the
content of those packets outside of information contained in its
headers.  Indeed, rejecting packets based on any mechanical ruleset
applied to packet contents will almost certainly REDUCE the reliability
of the network, because (for example) an encrypted document might by
pure chance have a byte sequence like SEX that caused it to be rejected
even though its actual contents were quotes from the stock market.  One
doesn't write filters looking for buffer overwrite attacks into the TCP
stack in the kernel -- one fixes the application.

For nearly all filtering programs, it is too easy to create a message
that is filtered but shouldn't be.  Even rejecting viruses on the basis
of their signatures makes it difficult to SEND a virus you've just
received to an email drop where somebody can identify it.  As we've
seen, a naive application of rules mkes it impossible for this
most-certainly-not-spam discussion to penetrate various "protected"
sites.  It is often similarly easy to craft a message that should be
filtered but isn't because it slips through your rules.  But we've had
this discussion; the point is about reliability.

SMTP was designed to permit reasonably RELIABLE (simple) transport of
addressed mail on top of a TCP connection.  In most cases, ethernet
forms one of the lowest level protocols that the mail message is wrapped
in (ethernet header), then IP (IP header), then TCP (with its header).
SMTP pays relatively little attention to the message headers at the
transport and network protocol levels as it doesn't matter much which
ethernet address was responsible for the last packet hop (likely a
router/gateway and the same for all packets and messages).  It doesn't
care MUCH about IP or TCP, except that the packets have to be correctly
wrapped according to the protocols and addressed to SMTP listening on
the appropriate port.

SMTP does care about packet content, but only to a certain level.  Part
of the packet content it cares about is the negotiation phase where it
manages a connection, executing "commands" based on content in a very
structured way designed to communicate key information recursively along
the mail message's delivery trajectory, as it builds its own mail header
containing the addressee, the nominal sender, and the delivery route
complete with timestamps.  It is designed to be quite trusting, hence
easy to spoof, at least for mail to someone that doesn't read the rest
of the header.  Part of the packet content it views as "data" -- a
message to be reliably delivered to a uniquely specified spool file,
encapsulated within its MAIL header information (the TCP, IP and
ethernet level header information having been discarded).  There a user,
or a program, may or may not read it and take actions based on its
content.

It seems to me to be highly unacceptable to attempt to insert
content-based accept/reject decisioning in at this PROTOCOL level in the
delivery process.  It also seems to be highly risky and possibly legally
actionable.  I expect, in good faith, that email addressed to me will be
delivered if it is deliverable.  Otherwise I cannot rely on email as a
reliable transport mechanism for important messages.  Filtering it "for"
me according to ANY CONTENT-BASED RULESET risks discarding at least some
messages that are not correctly classified when they are rejected.
Important messages can be lost.  Bad things can result.  Who is
responsible when this occurs?  Who do I get to sue?

Imagine the post office (the real one) opening your mail and examining
content -- for most of us this alone would be a nightmare and invasion
of privacy -- so fine, with automated anonymous "safe" machines, to
eliminate advertisement mailings (only) but pass everything else.  One
day it rejects and shreds a sweepstakes check (a real one) thinking it
is one of the many fake checks sent out by loan companies.  Another day
it shreds a warning by your bank that a loan payment is due because it
also looks like an advertisement.  Even humans make this sort of
(sometimes very expensive) mistake, but at least if you make it it is
"your fault".  How would you feel, and react, if the mistake were
utterly beyond your control?  How long would it be before banks and
other businesses rejected the post office as a reliable transport
agency?

It is perfectly reasonable for you to add content filters that YOU
control ABOVE this transport layer.  If you want to hire a secretary to
open all of your mail for you and sort it and reject all the
advertisements, you can.  If the secretary makes a mistake and throws
away a megamillion dollar contract offer that you subsequently lose, you
also bear the responsibility, or at least can direct your anger at
something you control and take steps to ensure that similar things don't
happen again.

Now, all that it would take to control this end stage filtering and make
it much more reliable would be a federal law mandating that advertising
communications be sent in envelopes clearly labelled as such.  No more
sending out loan offers in envelopes that strangely resemble official
government communications unless they were clearly labelled
"advertisement".  No more writing the address in by hand to convince you
that you are opening personal mail.  If somebody violated the law, you
would have the envelope and offer in hand and could recover damages in
small claims court with very little effort.  Otherwise, you could safely
discard all advertising.

Note that this doesn't really help someone forced to do the final
accept/reject step themselves by hand.  They still have to look at each
envelope to look for the mandatory classification mark.  Advertisers
would of course try to exploit this by making the envelopes themselves a
major part of their messages -- "open ME".  It would make it fairly
simple to institute automated blocks, though, both for human secretaries
and real mail and for e.g. procmail and email.

With that all said, there are tools that ALREADY provide the kind of
content level filtering mentioned above.  The better ones do not
themselves discard or bounce any mail to any user.  They simply SCORE
THE CONTENT with regard to its likelihood of being spam (or a virus) on
the basis of a whole battery of tests.  Scores that exceed a given
threshold can easily and automatically be rejected or binned for a
second stage pass by humans later looking for lost checks and bills.
The USER (the one that ultimately knows the value TO THEM of a lost
message) can set the threshold to whatever level they are comfortable
with.  Some will prefer to play it loose and never risk losing a
message, even though it means that a lot of spam gets through.  Others
will reject on a fairly low threshold, not caring that they blindly miss
out on discussions of spam on ietf.org because those discussions
inevitably contain phrases like "Buy Viagra From Us Today" (oops, lost
one whole block of recipients), or "Have the Wildest Sex Ever" (now I
lost all the elementary and high schools in the country).  It is THEIR
DECISION, and they can pay the expectation cost "penalty" in lost
messages vs lots of spam at whatever level they select.

This doesn't require protocol level modifications of SMTP.  In fact, it
is generally desirable not to alter the SMTP MTA except in VERY
carefully thought out ways, although it is fine to graft in content
rating/filtering systems after the reliable delivery is complete to the
receiving host but before putting the message in a user's mailbox (with
the score in a special header where it can be used to drive user-level
decisions.  Just as spam assassin actually does now.

I repeat, I see little for the IETF to do about spam at the protocol
level, although it could be a powerful force at the political level,
communicating to our lawmakers the real costs of spam and urging them to
adopt stringent legal controls and penalties.  We could help draft those
legal controls and penalties.  For example, make it illegal to collect
and resell lists of email addresses for commercial purpose.  Require all
advertisements to be clearly labelled as advertisements in a form that
permits them to be automatically and reliably filtered.  One thing that
we COULD do is create a new mail header line marking mass produced
advertising mail as such, and match that up with laws requiring all
legitimate corporate clients to use it (with hefty penalties for those
that don't).

This is not the case for bidirectional encryption of email content.
There it won't happen unless and until the IETF works out a practical
way to make it work at the protocol level, since clearly ALL MTA's have
to be able to manage the encryption.

At this point I see no practical way to require or enforce point to
point encryption of all mail at the user level without a nearly complete
reengineering of mail transport (basically replacing smtp altogether).

I CAN imagine all hosts having their own RSA public and private keys,
and having all the public keys be part of their domain nameservice
registration information and hence automatically available to
"everybody".  I can imagine both tools and service providers that could
generate suitable key pairs and manage distribution of the pairs onto
registered systems either for a fee or as a part of routine systems
management (as we already do now, for the most part, for ssh).

I simply canNOT imagine that process extending down to the level of
private users at this time.  I don't believe that there is yet a
suitable vehicle for the required nameservice that would scale to
billions of registered entities and many trillions of bytes of served
data (as good keys aren't small) and that has at least the robustness of
the existing DNS.  

It is worth imagining such a service, but we are not terribly close, I
think, to being able to engineer it at this point.  It also has
interesting social costs and risks that I suspect would significantly
affect the engineering, as obviously protecting one's private key then
becomes an "interesting" problem all by itself.  A well managed computer
is already a bit of a fortress with facilities that permit protecting
data.  Users are not fortresses at all (quite the opposite) and if
anything are terribly lax with important data.

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Tue Feb 17 19:42:52 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19664
	for <ietf-archive@odin.ietf.org>; Tue, 17 Feb 2004 19:42:52 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtFcu-0002AJ-10
	for ietf-list@asgard.ietf.org; Tue, 17 Feb 2004 19:31:44 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtFc4-0001yM-LQ
	for ietf@asgard.ietf.org; Tue, 17 Feb 2004 19:30:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19035
	for <ietf@ietf.org>; Tue, 17 Feb 2004 19:30:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtFc3-0006fc-00
	for ietf@ietf.org; Tue, 17 Feb 2004 19:30:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtFb6-0006a8-00
	for ietf@ietf.org; Tue, 17 Feb 2004 19:29:53 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtFaK-0006Tk-00
	for ietf@ietf.org; Tue, 17 Feb 2004 19:29:04 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1I0TLof061995;
	Wed, 18 Feb 2004 01:29:21 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0402171555160.20733-100000@lilith.rgb.private.net>
References: <Pine.LNX.4.44.0402171555160.20733-100000@lilith.rgb.private.net>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-1--27332687"
Message-Id: <634BA7A9-61A9-11D8-B9EA-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: covert channel and noise -- was Re: proposal ...
Date: Wed, 18 Feb 2004 01:28:35 +0100
To: "Robert G. Brown" <rgb@phy.duke.edu>
X-Pgp-Agent: GPGMail 1.0 (v30, 10.3)
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


--Apple-Mail-1--27332687
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit

On 17-feb-04, at 23:47, Robert G. Brown wrote:

> This is where, and why, I take issue with filtering and discarding at
> the level of the SMTP server, unless the accept/reject decision can be
> made with 100% precision

> Imagine a networking transport protocol such as TCP, that discarded
> packets not based on their header information (according to any
> protocol-level criterion you like) but on their CONTENT,

Actually stuff like this exists today, sometimes called "layer 7 
switches". They're used to filter out HTTP worms and so on. But the 
comparison makes little sense as in TCP segments are part of an 
explicitly created session. When someone accepts the session, it's 
reasonable to assume they'll want to receive TCP segments that are part 
of this session.

The issue with email is that the only reasonable moment to reject 
messages is when you're still talking to the sender, so that a failure 
notice can be communicated back. Once the message has been accepted, 
you either have to deliver it, or you run the risk of false positives. 
Since non-false positives contain false return addresses most of the 
time sending back an indication that a message is rejected to the 
return address does more harm than good.

Note that filtering while a transport session exists ISN'T the same 
thing as filtering the transport stream itself: modifying SMTP such 
that any mention of our favorite medicine starting with a V is blocked 
makes it impossible for SMTP to function. However, rejecting messages 
that contain this word may or may not be appropriate, if the user isn't 
going to read them anyway rejecting them at the SMTP is the right thing 
to do as both silently dropping them or sending back failure notices is 
much worse.

> For nearly all filtering programs, it is too easy to create a message
> that is filtered but shouldn't be.

That's why information that a message is filtered must find its way 
back to the sender, so that the sender can take appropriate action.

> SMTP was designed to permit reasonably RELIABLE (simple) transport

SMTP isn't and has never been reliable.

> Imagine the post office (the real one) opening your mail and examining
> content -- for most of us this alone would be a nightmare and invasion
> of privacy --

What world exactly are you living in? Never heard of bomb or anthrax 
letters?

And you're assuming some external entity is imposing an arbitrary 
policy here. Fact is that most people _want_ their service provider to 
filter out spam even using today's relatively unreliable mechanisms. I 
don't think worrying about a world where legitimate pharmaceutical 
messages are filtered out with no way to disable the filters is 
warranted at this point.

> Now, all that it would take to control this end stage filtering and 
> make
> it much more reliable would be a federal law mandating that advertising
> communications be sent in envelopes clearly labelled as such.

Yes, and all that we need to do to make sure people don't use 
psychotropic substances is make them illegal.

If we can't stop denial of service attacks that bring down entire 
networks causing very real monetary damage, how can we ever expect to 
be able to do something about spam, where any invidivual message is at 
most a slight nuisance, using laws that only apply to a few percent of 
the internet anyway?

> I repeat, I see little for the IETF to do about spam at the protocol
> level

If you were a spammer (or selling bandwidth to spammers, or maybe even 
selling anti-spam software or services) you'd be saying the same thing. 
So this claim is very suspect. You need to back it up with *very* solid 
facts.

> This is not the case for bidirectional encryption of email content.
> There it won't happen unless and until the IETF works out a practical
> way to make it work at the protocol level, since clearly ALL MTA's have
> to be able to manage the encryption.

You really don't get it, do you? Encrypting the transport between 
multiple hops is useless. Encryption needs to be end-to-end. But we 
both have per-hop and end-to-end encryption standardized, implemented 
and used *today*. (It's too late for me to go out and find all the RFC 
numbers.)

-- 
PGP key: 0x1B1FC4E6  --->  http://www.muada.com/iljitsch.gpgkey
Fingerprint: CABE 3C2C 55D0 4D31 ED1A  2B6D 37E7 8439 1B1F C4E6

--Apple-Mail-1--27332687
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFAMrHDN+eEORsfxOYRAm22AKCM+6MX984fb73Ej8xbyiExCL6EAwCeNlba
zDMgZRl3S+PYrtf2EuU5axY=
=jMM5
-----END PGP SIGNATURE-----

--Apple-Mail-1--27332687--




From owner-ietf@ietf.org  Tue Feb 17 20:35:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22047
	for <ietf-archive@odin.ietf.org>; Tue, 17 Feb 2004 20:35:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtGX1-0005EL-HD
	for ietf-list@asgard.ietf.org; Tue, 17 Feb 2004 20:29:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtGWp-00052w-OE
	for ietf@asgard.ietf.org; Tue, 17 Feb 2004 20:29:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21727
	for <ietf@ietf.org>; Tue, 17 Feb 2004 20:29:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtGWo-0003hB-00
	for ietf@ietf.org; Tue, 17 Feb 2004 20:29:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtGVx-0003cf-00
	for ietf@ietf.org; Tue, 17 Feb 2004 20:28:38 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtGV7-0003Xg-00
	for ietf@ietf.org; Tue, 17 Feb 2004 20:27:45 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1I1Ritm036067
	for ietf@ietf.org env-from <vjs>;
	Tue, 17 Feb 2004 18:27:44 -0700 (MST)
Date: Tue, 17 Feb 2004 18:27:44 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402180127.i1I1Ritm036067@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: covert channel and noise -- was Re: proposal ...
References: <Pine.LNX.4.44.0402171555160.20733-100000@lilith.rgb.private.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "Robert G. Brown" 

> ...
> Or, mark for later accept/reject decisioning AFTER the SMTP server per
> se, in the filter pipeline between the server and the mail spool of the
> addressee.  Spam assassin does the right thing already (and this is
> exactly what it does).

***NO***!  Except when run as a milter or otherwise during the SMTP
transaction, SpamAssassin does the WRONG thing.  As run almost everywhere,
after the SMTP transaction, SpamAssassin can only iether silently discard
spam or generate new spam by sending bounces to innocent people.


> > A better positition is that everything should be logged, particularly
> > including discarded mail, ...

> Logging a message you reject is nearly a waste of time.  

Based on my experience, people running ISPs or other large mail system
strongly disagree with your position.  Besides, I intentionally wrote
about logging ***discarded** mail.

Many institutions do turn off logging of greylisted messages, reduce
the default per-message logging limit of 32K Bytes, or delete log files
far sooner than the 14 default in the DCC source.  Still, logging
is seen as vital to be able to answer questions about which messages
were filtered and why, including being able to say "that message was
never sent" or "substantially identical copies of that message were
sent to 310 other users here and 433,797 users elsewhere; it was spam."


>                                                          In order to
> recover the message (as you note, nobody ever looks at the logs, which
> are VERY LARGE for a busy mailer and beyond human capacity to scan),

I said nothing about humans scanning everything.  Besides, giving
users the sense that they can see what's happening with spam filtering
on their mail and control it is a requirement for getting users to
accept filtering.

> >..
> This is where, and why, I take issue with filtering and discarding at
> the level of the SMTP server, unless the accept/reject decision can be
> made with 100% precision (no false positives, no false negatives, and it
> may not be good even then because MY idea of the correct basis for the
> decision may not be the same as YOURS).

What you describe is a broken version of what I advocate, if you
consistently look at your personal log of rejected mail.  Your version
is broken because a "reject decision" after the SMTP transaction must
at least sometimes result in sending spam to innocent people.


> ...
> It's not that filtering based on non-header-linked aspects of content is
> or isn't a good idea in some cases.  It is that it has no business being
> in the specification of TCP.  ...

> pure chance have a byte sequence like SEX that caused it to be rejected
> >..

Nice straw man.  I've never heard anyone with a taint of technical
clues talk about looking for "SEX" in raw TCP segments.

> ...
> For nearly all filtering programs, it is too easy to create a message
> that is filtered but shouldn't be.  ...

You evidently lack experience with the filters used by commercial
institutions.  Commersical SMPT servers cannot tolerate false positives
(legitimate rejected/total legitimate) of more than 0.01%, and even
that's pushing it.  The design requirement for filtering mail on which
money depends is that false positives must not be much worse than the
underlying SMTP error rate due to problems such as full disks and
broken DNS servers--not to mention mail recipients too quick to delete.

A lot of current talk about false positives is self-serving nonsense
from such as the Direct Marketing Association.  Manual spam filtering
also has false positives.  A human suffering a common spam load of 100
spam/day has trouble not deleting legitimate mail.  My filters are
rejecting about 300 spam/day sent in my direction, 12227 in the last
40 days.  Mechanical filtering even with a significant false positive
rate can reduce the overall false positive rate.


> ...
> SMTP was designed to permit reasonably RELIABLE (simple) transport of

It would be good to skip the networking 101 tutorials.  Those of us who
don't know all of that about TCP, SMTP, CSMA/CD, etc. often thanks to
decades of personal experience should apply elsewhere to learn the basics.
It is may hard to imagine how old farts like me see such tutorials, but
please try.  I've been receiving email as "vjs" since 1968.


> It seems to me to be highly unacceptable to attempt to insert
> content-based accept/reject decisioning in at this PROTOCOL level in the
> delivery process. 

That use of "level" confuses me.  It does not seem to conform to ISO
OSI architecture.

> ...
> reliable transport mechanism for important messages.  Filtering it "for"
> me according to ANY CONTENT-BASED RULESET risks discarding at least some
> messages that are not correctly classified when they are rejected.
> Important messages can be lost.  Bad things can result.  Who is
> responsible when this occurs?  Who do I get to sue?

You don't get too sue anyone, because a reasonably designed system
lets you choose to do all of your spam filtering manually or in
your personal MUA.  The only caveat is that your account should be
terminated for network abuse if whatever mechanisms you choose
bounce very much spam to innocents.

That many filtering systems are junk including not allowing per-user
preferences is as illuminating as the fact that spam flogging spam
filters is common.  All I can see from either is that hard problems
attract charletans and would be gurus.


> ...
> It is perfectly reasonable for you to add content filters that YOU
> control ABOVE this transport layer.  If you want to hire a secretary to
> open all of your mail for you and sort it and reject all the
> advertisements, you can.  ....

You are welcome to require manual filtering for your mail, but you
have no standing to dictate to others at other institutions.

"Transport layer" seems like a misuse of the term.  It certainly
conveys nothing to me.


> With that all said, there are tools that ALREADY provide the kind of
> content level filtering mentioned above.  The better ones do not
> themselves discard or bounce any mail to any user.  

People with experience in this field never say never.

>                                                     They simply SCORE
> THE CONTENT with regard to its likelihood of being spam (or a virus) on
> the basis of a whole battery of tests.  Scores that exceed a given
> threshold can easily and automatically be rejected or binned for a
> ...

All of that can be done during the SMTP transaction just as effectively
as after.  Rejecting spam after the SMTP transaction should be and in
many quarters already is seen as network abuse requiring at least a
stern warning.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Tue Feb 17 22:20:26 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25399
	for <ietf-archive@odin.ietf.org>; Tue, 17 Feb 2004 22:20:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtI6l-00078O-8A
	for ietf-list@asgard.ietf.org; Tue, 17 Feb 2004 22:10:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtI6X-0006wv-4B
	for ietf@asgard.ietf.org; Tue, 17 Feb 2004 22:10:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25164
	for <ietf@ietf.org>; Tue, 17 Feb 2004 22:10:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtI6V-0002lL-00
	for ietf@ietf.org; Tue, 17 Feb 2004 22:10:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtI5Z-0002fC-00
	for ietf@ietf.org; Tue, 17 Feb 2004 22:09:29 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtI4j-0002aZ-00; Tue, 17 Feb 2004 22:08:38 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1I38b2M059079 env-from <vjs>;
	Tue, 17 Feb 2004 20:08:37 -0700 (MST)
Date: Tue, 17 Feb 2004 20:08:37 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402180308.i1I38b2M059079@calcite.rhyolite.com>
To: ietf-secretariat@ietf.org, ietf@ietf.org
Subject: How Not To Filter Spam
References: <Pine.LNX.4.44.0402171555160.20733-100000@lilith.rgb.private.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,FOR_FREE autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Thn enclosed example of how not to filter spam is offered for those
who might want to preemptively add accuspam.com or downloadfast.com
to their blacklists.

It is also a classic example of what is wrong with the MUA filtering
tactics Robert Brown advocates.


I certainly did not try to contact anyone at 3dize.com.  A few readers
of this mailing list might recall that Shelby H. Moore III and I don't
see eye to eye.
I do not know what the From: header of inanbe@xs4all.nl is about.
Perhaps it was forged.  Or perhaps someone at that address wired a
subscription to this mailing list through an unusually braindea)
challenge/response spam filter at DownloadFAST.com.  If so, the
Secretariat should blacklist accuspam.com and/or downloadfast.com from
subscriptions to IETF mailing lists.  (It would need to be unusually
braindead to send me the challenge instead of the envelope sender.)


Vernon Schryver    vjs@rhyolite.com


> From mailer@accuspam.com  Tue Feb 17 19:26:14 2004
> Received: from www.DownloadFAST.com (www.downloadfast.com [65.61.155.11])
> 	by calcite.rhyolite.com (8.12.11/8.12.11) with ESMTP id i1I2QDiM048994
> 	for <vjs@calcite.rhyolite.com> env-from <mailer@accuspam.com>;
> 	Tue, 17 Feb 2004 19:26:13 -0700 (MST)
> Received: from www.downloadfast.com (localhost.downloadfast.com [127.0.0.1])
> 	by www.DownloadFAST.com (8.12.10/8.12.10) with ESMTP id i1I1hIQf002492
> 	for <vjs@calcite.rhyolite.com>; Tue, 17 Feb 2004 19:43:18 -0600 (CST)
> Received: (from root@localhost)
> 	by www.downloadfast.com (8.12.10/8.12.6/Submit) id i1I1hITA002491;
> 	Tue, 17 Feb 2004 19:43:18 -0600 (CST)
> Date: Tue, 17 Feb 2004 19:43:18 -0600 (CST)
> Message-Id: <200402180143.i1I1hITA002491@www.downloadfast.com>
> To: vjs@calcite.rhyolite.com
> Subject: Re: Re: covert channel and noise -- was Re: proposal ...
> From: inanbe@xs4all.nl
> Reply-To: mailer@accuspam.com

> You attempted to contact us via email, and our anti-spam system is returning your email below.
>
> Please kindly resend your email below, using our Contact Form on our web page:
>
> http://accuspam.com?kM,vbrJT
>
> After using our Contact Form only once, your future emails will not be returned.
>
> If you do not use our Contact Form to re-send your email below, then we can not read it.
>
> ______________________________
> Powered by http://AccuSpam.com. Signup instantly for FREE!
>
>
> Your Returned Message:
> From: "Robert G. Brown" 
>
> > ...
> > Or, mark for later accept/reject decisioning AFTER the SMTP server per
> > se, in the filter pipeline between the server and the mail spool of the
> > addressee.  Spam assassin does the right thing already (and this is
> > exactly what it does).
>
> ***NO***!  Except when run as a milter or otherwise during the SMTP
> ...



From owner-ietf@ietf.org  Tue Feb 17 22:42:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26373
	for <ietf-archive@odin.ietf.org>; Tue, 17 Feb 2004 22:42:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtIVv-0003ro-Lf
	for ietf-list@asgard.ietf.org; Tue, 17 Feb 2004 22:36:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtIVp-0003gQ-6V
	for ietf@asgard.ietf.org; Tue, 17 Feb 2004 22:36:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26105
	for <ietf@ietf.org>; Tue, 17 Feb 2004 22:36:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtIVn-0004UZ-00
	for ietf@ietf.org; Tue, 17 Feb 2004 22:36:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtIUq-0004Re-00
	for ietf@ietf.org; Tue, 17 Feb 2004 22:35:36 -0500
Received: from sokol.elan.net ([216.151.192.200])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtIUI-0004Od-00
	for ietf@ietf.org; Tue, 17 Feb 2004 22:35:03 -0500
Received: from sokol.elan.net (localhost.localdomain [127.0.0.1])
	by sokol.elan.net (8.12.5/8.12.5) with ESMTP id i1I4a4PY010178;
	Tue, 17 Feb 2004 20:36:04 -0800
Received: from localhost (william@localhost)
	by sokol.elan.net (8.12.5/8.12.5/Submit) with ESMTP id i1I4a3Gh010174;
	Tue, 17 Feb 2004 20:36:03 -0800
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Tue, 17 Feb 2004 20:36:03 -0800 (PST)
From: "william(at)elan.net" <william@elan.net>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: How Not To Filter Spam
In-Reply-To: <200402180308.i1I38b2M059079@calcite.rhyolite.com>
Message-ID: <Pine.LNX.4.44.0402172027160.24886-100000@sokol.elan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


On Tue, 17 Feb 2004, Vernon Schryver wrote:

> It is also a classic example of what is wrong with the MUA filtering

You certain dont assume that there is nothing wrong with the filtering
system you use and others may try duplicate as well. Otherwise how would 
you explain that you have Elan and completewhois.com listed as filtered
on your site. Do you honestly believe we ever sent you any SPAM? Or maybe 
you're making certain assumptions about envelope from or normal "From:" 
headers and complaining when others are making the similar assumptions?
 
-- 
William Leibzon
Elan Networks
william@elan.net




From owner-ietf@ietf.org  Tue Feb 17 23:09:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27175
	for <ietf-archive@odin.ietf.org>; Tue, 17 Feb 2004 23:09:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtIx1-00011f-7Q
	for ietf-list@asgard.ietf.org; Tue, 17 Feb 2004 23:04:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtIwp-0000qA-EJ
	for ietf@asgard.ietf.org; Tue, 17 Feb 2004 23:04:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27121
	for <ietf@ietf.org>; Tue, 17 Feb 2004 23:04:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtIwn-0006eF-00
	for ietf@ietf.org; Tue, 17 Feb 2004 23:04:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtIvq-0006c9-00
	for ietf@ietf.org; Tue, 17 Feb 2004 23:03:30 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtIvf-0006aH-00
	for ietf@ietf.org; Tue, 17 Feb 2004 23:03:19 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1I43JQZ073897
	for ietf@ietf.org env-from <vjs>;
	Tue, 17 Feb 2004 21:03:19 -0700 (MST)
Date: Tue, 17 Feb 2004 21:03:19 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402180403.i1I43JQZ073897@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: How Not To Filter Spam
References: <Pine.LNX.4.44.0402172027160.24886-100000@sokol.elan.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "william(at)elan.net" 

> > It is also a classic example of what is wrong with the MUA filtering
>
> You certain dont assume that there is nothing wrong with the filtering
> system you use and others may try duplicate as well. Otherwise how would 
> you explain that you have Elan and completewhois.com listed as filtered
> on your site. Do you honestly believe we ever sent you any SPAM? Or maybe 
> you're making certain assumptions about envelope from or normal "From:" 
> headers and complaining when others are making the similar assumptions?

Mail from Elan and completewhois.com is unwelcome at rhyolite.com in
patt because of a message that said:

] Elan.Net Internet
] T.1 T.3 Frame Relay
] If you need more information about us or are interested in network services 
] (managed hosting, collocation, dedicated servers, t1, t3), please send email to info@elan.net 
] 
] For More info 
] http://www.elan.net
] sales@elan.net

There are additional, independent, sufficient reasons for that listing
that we do not need to explore.  If you will read my web pages, you'll
see that my list of unwelcome domains is not only about senders of
unsolicited bulk email.

An advantage of a vanity or other tiny domain is that it can use
blacklists that would have intolerable false positive rates at other
or larger outfits but that have 0.000% local false positive rates.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Tue Feb 17 23:33:51 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28039
	for <ietf-archive@odin.ietf.org>; Tue, 17 Feb 2004 23:33:51 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtJIN-0005Wd-9P
	for ietf-list@asgard.ietf.org; Tue, 17 Feb 2004 23:26:47 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtJIB-0005Ke-DO
	for ietf@asgard.ietf.org; Tue, 17 Feb 2004 23:26:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27750
	for <ietf@ietf.org>; Tue, 17 Feb 2004 23:26:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtJI9-00009V-00
	for ietf@ietf.org; Tue, 17 Feb 2004 23:26:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtJHH-00005T-00
	for ietf@ietf.org; Tue, 17 Feb 2004 23:25:40 -0500
Received: from sokol.elan.net ([216.151.192.200])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtJGa-00001A-00
	for ietf@ietf.org; Tue, 17 Feb 2004 23:24:56 -0500
Received: from sokol.elan.net (localhost.localdomain [127.0.0.1])
	by sokol.elan.net (8.12.5/8.12.5) with ESMTP id i1I5QDPY011305;
	Tue, 17 Feb 2004 21:26:13 -0800
Received: from localhost (william@localhost)
	by sokol.elan.net (8.12.5/8.12.5/Submit) with ESMTP id i1I5QCcG011301;
	Tue, 17 Feb 2004 21:26:12 -0800
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Tue, 17 Feb 2004 21:26:12 -0800 (PST)
From: "william(at)elan.net" <william@elan.net>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: How Not To Filter Spam
In-Reply-To: <200402180403.i1I43JQZ073897@calcite.rhyolite.com>
Message-ID: <Pine.LNX.4.44.0402172114050.24886-100000@sokol.elan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 17 Feb 2004, Vernon Schryver wrote:

> > From: "william(at)elan.net" 
> 
> > > It is also a classic example of what is wrong with the MUA filtering
> >
> > You certain dont assume that there is nothing wrong with the filtering
> > system you use and others may try duplicate as well. Otherwise how would 
> > you explain that you have Elan and completewhois.com listed as filtered
> > on your site. Do you honestly believe we ever sent you any SPAM? Or maybe 
> > you're making certain assumptions about envelope from or normal "From:" 
> > headers and complaining when others are making the similar assumptions?
> 
> Mail from Elan and completewhois.com is unwelcome at rhyolite.com in
> patt because of a message that said:
You might want to post headers that show it being sent from some open-proxy
in pacific and showing use of email accounts that were never there.
 
> ] Elan.Net Internet
> ] T.1 T.3 Frame Relay
> ] If you need more information about us or are interested in network services 
> ] (managed hosting, collocation, dedicated servers, t1, t3), please send email to info@elan.net 
> ] 
> ] For More info 
> ] http://www.elan.net
> ] sales@elan.net
> 
> There are additional, independent, sufficient reasons for that listing
> that we do not need to explore. 
Except that we did not send that message and anti-spam community was 
informed it was a joe-job (95% guessed as much on their own). Considering 
you knew who I'm am, I suspect you knew all this as well and if you did 
not you might have notice a warning about this on the website. 

> An advantage of a vanity or other tiny domain is that it can use
> blacklists that would have intolerable false positive rates at other
> or larger outfits but that have 0.000% local false positive rates.
That is unlikely considering what I know about your list. 

Unless you make a good effort to research anything you probably have as
many problems as some of the most agressive ip-based filtering sites (like 
spews), you might make a number of good hits but would have number of misses
as well. Besides that as has been shown many times, for spammers its a 
lot easier and less expensive to get new domain that to get new ip block - 
and many do and setup hundreds of new domains on monthly basis. As such 
the value of domain-based filtering is very minimal indeed.

-- 
William Leibzon
Elan Networks
william@elan.net




From owner-ietf@ietf.org  Wed Feb 18 04:53:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04190
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 04:53:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtOF3-00028u-SG
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 04:43:41 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtOE7-0001yu-NL
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 04:42:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03943
	for <ietf@ietf.org>; Wed, 18 Feb 2004 04:42:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtOE5-0001nX-00
	for ietf@ietf.org; Wed, 18 Feb 2004 04:42:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtODA-0001lb-00
	for ietf@ietf.org; Wed, 18 Feb 2004 04:41:44 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtOCy-0001jO-00
	for ietf@ietf.org; Wed, 18 Feb 2004 04:41:32 -0500
Received: from parmhs4.rd.francetelecom.fr ([10.193.117.63]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Wed, 18 Feb 2004 10:41:33 +0100
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Subject: RE : WG Review: Routing Area Working Group (rtgwg)
Date: Wed, 18 Feb 2004 10:41:32 +0100
Message-ID: <57F140DC5CDA10438C41674629DE0D870190374D@parmhs4.rd.francetelecom.fr>
Thread-Topic: WG Review: Routing Area Working Group (rtgwg)
Thread-Index: AcP1ZxqtcihIagosQiOUoqqvf2yNYAAk/JsA
From: "PROUST Christophe FTRD/DMI/CAE" <christophe.proust@francetelecom.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 18 Feb 2004 09:41:33.0164 (UTC) FILETIME=[64B84AC0:01C3F603]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


	Dear Members of the IESG,

	I read the announcement you made yesterday and I felt deeply
called to it.
	I have very recently released an initial Internet-Draft=20
=09
http://www.ietf.org/internet-drafts/draft-proust-flow-routing-00.txt
	that deals with some form of adaptive routing that aims at load
balancing flows among 	available network resources. As the approach
followed is in an early stage, it 	requires some discussion in
order to determine if it meets the common interests of=20
	the Internet community.=20
	Thus, I was wondering if I could have the opportunity at the
next 59th IETF meeting
	to give a short presentation that would cover the basic
understanding of this I-D.
	I am sure that it would be helpful to get some insight feedback
either
	through the rtgwg mailing list or during a face-to-face IETF
meeting.=20

	Yours sincerly,
=09
	Christophe Proust

	France Telecom R&D
	42 rue des Coutures
	14000 - Caen - France
	+33 2 31 75 93 08
	christophe.proust@francetelecom.com



From owner-ietf@ietf.org  Wed Feb 18 15:11:05 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16040
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 15:11:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtXLQ-0000t4-Mz
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 14:26:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtWA9-0001pt-KN
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 13:11:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05834
	for <ietf@ietf.org>; Wed, 18 Feb 2004 13:11:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtWA8-0004zH-00
	for ietf@ietf.org; Wed, 18 Feb 2004 13:11:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtW9O-0004w8-00
	for ietf@ietf.org; Wed, 18 Feb 2004 13:10:23 -0500
Received: from shockwave.systems.pipex.net ([62.241.160.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtW8c-0004pD-00
	for ietf@ietf.org; Wed, 18 Feb 2004 13:09:34 -0500
Received: from tom3 (1Cust232.tnt13.lnd4.gbr.da.uu.net [62.188.142.232])
	by shockwave.systems.pipex.net (Postfix) with SMTP id BCA8E1C001F4;
	Wed, 18 Feb 2004 18:09:01 +0000 (GMT)
Message-ID: <037c01c3f64a$1c8fba20$0301a8c0@tom3>
Reply-To: "Tom Petch" <nwnetworks@dial.pipex.com>
From: "Tom Petch" <nwnetworks@dial.pipex.com>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>, <ietf@ietf.org>
Subject: Re: Continuing the story - another stab at an IETF mission statement
Date: Wed, 18 Feb 2004 18:06:17 -0000
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 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I find your definition of the Internet delightfully ambiguous.  I was
taught that the Internet (as opposed to an internet or the internet) was
the public network accessible through public IPv4 addresses (this predates
IPv6) ie the Internet ceased at a firewall or other such IP level gateway.

Reading your definition, I cannot tell where you stand; are firewalls and
networks behind them included in IETF mission or not?

Tom Petch

-----Original Message-----
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org <ietf@ietf.org>
Date: 11 February 2004 01:59
Subject: Continuing the story - another stab at an IETF mission statement


>Apologies to those who are already tired of this debate, and those think
>that we have enough of a clear idea of what the IETF mission is, and that
>discussing more is harmful to the community, but....
>
>I attempted to incorporate the latest discussions into an internet-draft,
>which I managed to get out just before the deadline....
>
>   draft-alvestrand-ietf-mission-00.txt
>
>The core of the draft:
>
>
>   The goal of the IETF is to make the Internet work.
>
>   The mission of the IETF is to produce high quality, relevant
>   technical and engineering documents that influence the way people
>   design, use and manage the Internet in such a way as to make the
>   Internet work better.
>   These documents include protocol standards, best current practices
>   and informational documents of various kinds.
>
>   The IETF will pursue this mission in adherence to the following
>   cardinal principles:
>
>   Open process - that any interested participant can in fact
>      participate in the work, know what is being decided, and make his
>      or her voice heard on the issue.  Part of this principle is our
>      commitment to making our documents, our WG mailing lists, our
>      attendance lists and our meeting minutes publicly available on the
>      Net.
>
>   Technical competence - that the issues on which the IETF produces its
>      documents are issues where the IETF has the competence needed to
>      speak to them, and that the IETF is willing to listen to
>      technically competent input from any source.
>      Technical competence also means that we expect IETF output to be
>      designed to sound network engineering principles - this is also
>      often referred to as "engineering quality".
>
>   Volunteer Core - that our members and our leadership are people who
>      come to the IETF because they want to work for the IETF's
>      purposes.
>
>   Rough consensus and running code - We make standards based on the
>      combined engineering judgement of our participants and our real-
>      world experience in implementing and deploying our specifications.
>
>
>The rest of the document is trying to define the terms and explain the
>issues faced in formulating the mission statement.
>An appendix (to be deleted before publication) lists some other attempts
at
>formulating a mission statement - the purpose of including this is to give
>honor to those who worked on them, and to allow those who debate the issue
>to see what other attempts to formulate the mission could look like.
>
>Comments are welcome, of course!
>
>                      Harald
>
>




From owner-ietf@ietf.org  Wed Feb 18 15:26:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17649
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 15:26:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtYBP-0001jU-Mz
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 15:20:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtXhR-0005DS-13
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 14:49:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14391
	for <ietf@ietf.org>; Wed, 18 Feb 2004 14:49:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtXhP-00010d-00
	for ietf@ietf.org; Wed, 18 Feb 2004 14:49:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtXgW-0000tj-00
	for ietf@ietf.org; Wed, 18 Feb 2004 14:48:41 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtXfg-0000ij-00
	for ietf@ietf.org; Wed, 18 Feb 2004 14:47:48 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 7120A61E97; Wed, 18 Feb 2004 20:47:17 +0100 (CET)
Date: Wed, 18 Feb 2004 11:47:16 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Tom Petch <nwnetworks@dial.pipex.com>, ietf@ietf.org
Subject: Re: Continuing the story - another stab at an IETF mission
 statement
Message-ID: <355947535.1077104836@halvestr-w2k1>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 18. februar 2004 18:06 +0000 Tom Petch <nwnetworks@dial.pipex.com> 
wrote:

> I find your definition of the Internet delightfully ambiguous.  I was
> taught that the Internet (as opposed to an internet or the internet) was
> the public network accessible through public IPv4 addresses (this predates
> IPv6) ie the Internet ceased at a firewall or other such IP level gateway.

I certainly agree on the "ambiguous", but not with the "delightful" :-)
>
> Reading your definition, I cannot tell where you stand; are firewalls and
> networks behind them included in IETF mission or not?

Here, I feel that I stand firmly on the quicksand left by those who have 
gone before... if you read Dave Crocker's 1995 RFC 'To be "on" the 
Internet' (RFC 1775), you will see that the problem is not a new one.

Luckily for us, "mediated access" and "messaging access" are mostly things 
of the past - but in my opinion, the Internet extends to the applications 
run by the people who have "client access" to the Internet.

After all, the Internet model is an end-to-end service; if the Internet 
stopped at the gateway/NAT box/firewall, it would be an end-to-firewall 
service for >90% of today's Internet traffic - and that doesn't make sense 
to me.

So in my opinion, firewalls and the networks behind them are part of the 
Internet, because we have to design for the Internet that is there, even as 
we labor to make it more like the Internet we want to have.
(now, is that sufficient straddling of the NAT debate? :-)

                         Harald







From owner-ietf@ietf.org  Wed Feb 18 16:14:07 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20930
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 16:14:07 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtYnE-0001YH-8i
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 15:59:40 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtYZG-0007dp-FS
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 15:45:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19388
	for <ietf@ietf.org>; Wed, 18 Feb 2004 15:45:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtYZF-0006Fk-00
	for ietf@ietf.org; Wed, 18 Feb 2004 15:45:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtYYP-0006DU-00
	for ietf@ietf.org; Wed, 18 Feb 2004 15:44:21 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtYXr-00068O-00
	for ietf@ietf.org; Wed, 18 Feb 2004 15:43:47 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id AC83361BF9
	for <ietf@ietf.org>; Wed, 18 Feb 2004 21:43:16 +0100 (CET)
Date: Wed, 18 Feb 2004 12:43:15 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Someone's not getting their email.....
Message-ID: <359306795.1077108195@[192.168.1.43]>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,FOR_FREE autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I got the following stuff in response to a mail I sent to the IETF list.

Since I have no idea whether this is an email harvester or a "legitimate" 
antispam tool (the form gave no indication, and no links to more 
information about its owner), I don't have enough information to decide 
reliably to respond to the message.

This posted here in the hope that someone will recognize the username and 
tell him/her/it that not getting mail doesn't mean nobody tried to send 
any..... and for the usual entertaining/sarcastic/depressing comments about 
the side-effect costs of antispam tools, of course.

                        Harald

---------- Forwarded Message ----------
Date: 18. februar 2004 14:27 -0600
From: inanbe@xs4all.nl
To: harald@alvestrand.no
Subject: Re: Re: Continuing the story - another stab at an IETF mission


Our anti-spam system is returning your email below.

Please RE-SEND your email by clicking the link to our web page Contact Form
as follows:

http://accuspam.com?kM,vbrJT

After using our Contact Form once, you will be able to send us email
directly. To permanently enable you to email us without ever using our
Contact Form again, simply ask us to add you to our permanent Approved
Senders list.

If you do not use our Contact Form to re-send your email below, then we can
NOT read it.

Note that web page Contact Forms are commonly used by professional web
sites for new contacts.

Apologies for inconvenience, as this is absolutely necessary to eliminate
huge volumes of incoming spam and increase the efficiency and accuracy with
which we can process email from you.

______________________________
Powered by http://AccuSpam.com. Signup instantly for FREE!


You may copy and paste your email below into our Contact Form above.
And you may use our Contact Form to ask us to add you to our Approved
Senders list.


Your Returned Message:

--On 18. februar 2004 18:06 +0000 Tom Petch <nwnetworks@dial.pipex.com>
wrote:

> I find your definition of the Internet delightfully ambiguous.  I was
> taught that the Internet (as opposed to an internet or the internet) was
> the public network accessible through public IPv4 addresses (this predates
> IPv6) ie the Internet ceased at a firewall or other such IP level gateway.

I certainly agree on the "ambiguous", but not with the "delightful" :-)
>
> Reading your definition, I cannot tell where you stand; are firewalls and
> networks behind them included in IETF mission or not?

Here, I feel that I stand firmly on the quicksand left by those who have
gone before... if you read Dave Crocker's 1995 RFC 'To be "on" the
Internet' (RFC 1775), you will see that the problem is not a new one.

Luckily for us, "mediated access" and "messaging access" are mostly things
of the past - but in my opinion, the Internet extends to the applications
run by the people who have "client access" to the Internet.

After all, the Internet model is an end-to-end service; if the Internet
stopped at the gateway/NAT box/firewall, it would be an end-to-firewall
service for >90% of today's Internet traffic - and that doesn't make sense
to me.

So in my opinion, firewalls and the networks behind them are part of the
Internet, because we have to design for the Internet that is there, even as
we labor to make it more like the Internet we want to have.
(now, is that sufficient straddling of the NAT debate? :-)

                         Harald









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







From owner-ietf@ietf.org  Wed Feb 18 16:38:01 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23284
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 16:38:01 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtZ8U-0001Fl-I8
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 16:21:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtZ8H-0000vS-2R
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 16:21:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21806
	for <ietf@ietf.org>; Wed, 18 Feb 2004 16:21:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtZ8F-0001Cl-00
	for ietf@ietf.org; Wed, 18 Feb 2004 16:21:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtZ6s-0000y0-00
	for ietf@ietf.org; Wed, 18 Feb 2004 16:19:59 -0500
Received: from rc-dmz.felix.nlri.ca ([192.5.4.54] helo=felix.automagic.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtZ5G-0000gi-00
	for ietf@ietf.org; Wed, 18 Feb 2004 16:18:18 -0500
Received: from [199.212.90.24] (helo=[199.212.90.24])
	by felix.automagic.org with asmtp (TLSv1:RC4-SHA:128)
	(Exim 4.20)
	id 1AtZ5B-0007t5-HZ; Wed, 18 Feb 2004 21:18:13 +0000
In-Reply-To: <037c01c3f64a$1c8fba20$0301a8c0@tom3>
References: <037c01c3f64a$1c8fba20$0301a8c0@tom3>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F34A6565-6257-11D8-8AE5-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
Cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>, <ietf@ietf.org>
From: Joe Abley <jabley@isc.org>
Subject: Re: Continuing the story - another stab at an IETF mission statement
Date: Wed, 18 Feb 2004 16:18:09 -0500
To: "Tom Petch" <nwnetworks@dial.pipex.com>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On 18 Feb 2004, at 13:06, Tom Petch wrote:

> I find your definition of the Internet delightfully ambiguous.  I was
> taught that the Internet (as opposed to an internet or the internet) 
> was
> the public network accessible through public IPv4 addresses (this 
> predates
> IPv6) ie the Internet ceased at a firewall or other such IP level 
> gateway.

I'm not sure who teaches that, but that's an extremely weak definition.

Define "public network". Define "accessible". Define "public IPv4 
addresses". Note that even with definitions, the resulting "Internet" 
is subjective in the sense that the shape of the network changes 
according to the perspective gained from local connectivity (so one 
host's Internet is different to another host's Internet).

The idea that the Internet is properly partitioned between devices 
which block packets would these days mean that in reality today it 
rarely extends beyond a single autonomous system, and often not beyond 
a single router. This is not, to my knowledge, a common definition (and 
even if it was common, it hardly seems very useful).

Lots of people seem to enjoy being needlessly pedantic about "the 
Internet" vs. "the internet" vs. "an internet", regardless of the fact 
they are unable to cite a reason for the distinction. So that's at 
least a common distinction, albeit arguably a fairly pointless one.

Q: "But what *IS* the Internet?"

A: "It's the largest equivalence class in the reflexive transitive 
symmetric closure of the relationship 'can be reached by an IP packet 
from'." - Seth Breidbart


Joe




From owner-ietf@ietf.org  Wed Feb 18 16:38:04 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23302
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 16:38:04 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtZLT-0002dq-CU
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 16:35:03 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtZ8X-0001GB-3Q
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 16:21:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21882
	for <ietf@ietf.org>; Wed, 18 Feb 2004 16:21:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtZ8V-0001Fe-00
	for ietf@ietf.org; Wed, 18 Feb 2004 16:21:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtZ7C-00011k-00
	for ietf@ietf.org; Wed, 18 Feb 2004 16:20:18 -0500
Received: from evrtwa1-ar8-4-65-025-155.evrtwa1.dsl-verizon.net ([4.65.25.155] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtZ5Y-0000k4-00
	for ietf@ietf.org; Wed, 18 Feb 2004 16:18:36 -0500
Received: from eaglet (127.0.0.1:4785)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S4746A> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 18 Feb 2004 13:18:39 -0800
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Vernon Schryver'" <vjs@calcite.rhyolite.com>, <ietf@ietf.org>
Subject: RE: How Not To Filter Spam
Date: Wed, 18 Feb 2004 13:18:31 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Thread-Index: AcP11UkddgsKy1aaSlGW+YPrK7fW4AAixiPQ
In-Reply-To: <200402180403.i1I43JQZ073897@calcite.rhyolite.com>
Message-Id: <E1AtZ5Y-0000k4-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

So if you had received the mail sent here yesterday claiming to be from
Alain Durand would you block Sun or IBM? I am sure Alain did not send a
random executable file to a non-existent account. It appears someone figured
out he had responded to me on this list in the past, and plenty of times
daily there are messages with the same content sent to half a dozen account
names as a cc set. Correlating Durand to Hain is completely in line with
typical spammer behavior. The fact this message got here is not a Sun
problem (but someone at IBM might want to send me a note). The point is that
it really doesn't matter which proxy was used what shows up here looks like
a legitimate message from someone I have corresponded with in the past. The
only way to detect a fraud at the MUA would be to have a verifiable
signature from Alain (this was trapped at my MTA due to the exe file). 

Tony


192.35.***.***:43014;4.65.25.155:25;Tue, 17 Feb 2004 15:12:51 -0800
tndh.net
S471B7
MAIL FROM:<alain.durand@sun.com>
RCPT TO:<hain@tndh.net>
<<MAIL-DATA>>
Received: from mtrumble (192.35.***.***:43014)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S471B7> for <hain@tndh.net> from <alain.durand@sun.com>;
	Tue, 17 Feb 2004 15:12:51 -0800
Date: Tue, 17 Feb 2004 17:10:17 -0600
To: hain@tndh.net
Subject: ID qfp... thanks
From: alain.durand@sun.com
Message-ID: <adkselafptndppsbnlb@sun.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------443488178303183"

----------443488178303183
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Yours ID fscyygroiei
--
Thank 
----------443488178303183
Content-Type: application/x-msdownload; name="pcrceynyu.exe"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="cdv.exe"


> 192.35.***.***
Non-authoritative answer:
***.***.35.192.in-addr.arpa     name = ***.***.ibm.com

*** - if someone from IBM wants to contact me off list I will provide the
missing name/number



> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Vernon
> Schryver
> Sent: Tuesday, February 17, 2004 8:03 PM
> To: ietf@ietf.org
> Subject: Re: How Not To Filter Spam
> 
> > From: "william(at)elan.net"
> 
> > > It is also a classic example of what is wrong with the MUA filtering
> >
> > You certain dont assume that there is nothing wrong with the filtering
> > system you use and others may try duplicate as well. Otherwise how would
> > you explain that you have Elan and completewhois.com listed as filtered
> > on your site. Do you honestly believe we ever sent you any SPAM? Or
> maybe
> > you're making certain assumptions about envelope from or normal "From:"
> > headers and complaining when others are making the similar assumptions?
> 
> Mail from Elan and completewhois.com is unwelcome at rhyolite.com in
> patt because of a message that said:
> 
> ] Elan.Net Internet
> ] T.1 T.3 Frame Relay
> ] If you need more information about us or are interested in network
> services
> ] (managed hosting, collocation, dedicated servers, t1, t3), please send
> email to info@elan.net
> ]
> ] For More info
> ] http://www.elan.net
> ] sales@elan.net
> 
> There are additional, independent, sufficient reasons for that listing
> that we do not need to explore.  If you will read my web pages, you'll
> see that my list of unwelcome domains is not only about senders of
> unsolicited bulk email.
> 
> An advantage of a vanity or other tiny domain is that it can use
> blacklists that would have intolerable false positive rates at other
> or larger outfits but that have 0.000% local false positive rates.
> 
> 
> Vernon Schryver    vjs@rhyolite.com




From owner-ietf@ietf.org  Wed Feb 18 16:38:58 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23445
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 16:38:57 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtZLU-0002gn-RL
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 16:35:04 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtZBT-0001Vs-Gi
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 16:24:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22320
	for <ietf@ietf.org>; Wed, 18 Feb 2004 16:24:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtZBS-0001aO-00
	for ietf@ietf.org; Wed, 18 Feb 2004 16:24:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtZAc-0001XE-00
	for ietf@ietf.org; Wed, 18 Feb 2004 16:23:51 -0500
Received: from krusty-motorsports.com ([192.94.170.8] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtZ9p-0001RJ-00
	for ietf@ietf.org; Wed, 18 Feb 2004 16:23:01 -0500
Received: from [24.194.112.77] (helo=skipper.averillpark.net)
	by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.22)
	id 1Ata5i-0004PD-5I
	for ietf@ietf.org; Wed, 18 Feb 2004 22:22:50 +0000
Received: from [127.0.0.1] (helo=localhost)
	by skipper.averillpark.net with esmtp (Exim 4.22)
	id 1AtZ91-000214-Sj
	for ietf@ietf.org; Wed, 18 Feb 2004 16:22:11 -0500
Date: Wed, 18 Feb 2004 16:22:11 -0500 (EST)
From: Richard Welty <rwelty@averillpark.net>
Subject: Re: Someone's not getting their email.....
To: ietf@ietf.org
Message-ID: <Mahogany-0.66.0-7473-20040218-162211.00@averillpark.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE
References: <359306795.1077108195@[192.168.1.43]>
In-Reply-To: <359306795.1077108195@[192.168.1.43]>
Organization: Averill Park Networking
X-Mailer: Mahogany 0.66.0 'Clio', compiled for Linux 2.4.18-14 i686
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 18 Feb 2004 12:43:15 -0800 Harald Tveit Alvestrand <harald@alvestrand.no> wrote:

> I got the following stuff in response to a mail I sent to the IETF list.

> Since I have no idea whether this is an email harvester or a "legitimate" 
> antispam tool (the form gave no indication, and no links to more 
> information about its owner), I don't have enough information to decide 
> reliably to respond to the message.

i have run internet mailing lists since about 1985. when the first C/R
systems showed up a few years ago, i arrived at simple conclusion
very quickly.

anybody who installs a C/R system and doesn't whitelist the mailing lists
they subscribe to doesn't deserve to receive those mailing lists.
i remove from my lists anyone who does this. nobody has complained
yet.

i'd strongly urge that the IETF adapt a similar policy. it's much less
stressful for all concerned.

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




From owner-ietf@ietf.org  Wed Feb 18 17:23:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26219
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 17:23:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtZz0-0002Lg-IL
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 17:15:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtZvu-0001tU-Cg
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 17:12:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25685
	for <ietf@ietf.org>; Wed, 18 Feb 2004 17:12:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtZvs-0004sV-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:12:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtZv1-0004qZ-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:11:47 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtZuH-0004lN-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:11:01 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i1IMJ3d10002;
	Wed, 18 Feb 2004 14:19:03 -0800
Date: Wed, 18 Feb 2004 14:10:28 -0800
From: Dave Crocker <dhc@dcrocker.net>
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <983826345.20040218141028@brandenburg.com>
To: "Tony Hain" <alh-ietf@tndh.net>
CC: ietf@ietf.org
Subject: Re: How Not To Filter Spam
In-Reply-To: <E1AtZ5Y-0000k4-00@ietf-mx>
References: <200402180403.i1I43JQZ073897@calcite.rhyolite.com>
 <E1AtZ5Y-0000k4-00@ietf-mx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony,

TH> a legitimate message from someone I have corresponded with in the past. The
TH> only way to detect a fraud at the MUA would be to have a verifiable
TH> signature from Alain (this was trapped at my MTA due to the exe file). 

 yes, but no.

 first, there is an increasingly heated debate between folks who want to
 sign the message (TEOS, DomainKeys), versus others who want to secure the channel between
 sender and receiver (RMX, LMAP, SPF, etc.).

 Once that debate is resolved, there is still the matter of compromised
 system. The message might actually come from the purported author's
 system, but still not be from the author because it has been taken over
 by evil forces. So, even with perfect automated validation, the content
 still might not be valid.


d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Wed Feb 18 17:23:10 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26237
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 17:23:10 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtZyz-0002LI-Fe
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 17:15:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtZuy-0001Z1-L6
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 17:11:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25647
	for <ietf@ietf.org>; Wed, 18 Feb 2004 17:11:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtZux-0004pv-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:11:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtZu1-0004na-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:10:46 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[IDRj3AEH7ErJMUnRlygZh7Qmlwb9GilL])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtZtV-0004lH-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:10:13 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id 126AFA77CE; Wed, 18 Feb 2004 17:09:20 -0500 (EST)
Date: Wed, 18 Feb 2004 16:33:39 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: Re: How Not To Filter Spam
In-Reply-To: <200402180308.i1I38b2M059079@calcite.rhyolite.com>
Message-ID: <Pine.LNX.4.44.0402181514130.21696-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 17 Feb 2004, Vernon Schryver wrote:

> Thn enclosed example of how not to filter spam is offered for those
> who might want to preemptively add accuspam.com or downloadfast.com
> to their blacklists.
> 
> It is also a classic example of what is wrong with the MUA filtering
> tactics Robert Brown advocates.

Vernon, I think you misunderstand what I was saying in my previous note
-- the problem was likely mine as I may not have been very clear.  If
so, I apologize.  I actually agree with much of what you say (and
thought that was clear on the basis of my earlier posts on the subject).

I was objecting to precisely this kind of filtering, and almost
forwarded it to the list myself.  You might recall that I predicted that
my message to the ietf would generate bounces just like this because it
contains a few key phrases -- obviously your reply contained the same
phrases. In fact, it was in objection to this sort of automated bounce
generation for both spam and viruses (especially the latter) that I
joined this list and have been participating in this discussion.

I also think you misunderstand spamassassin, at least the way it is used
here.  We as a department don't "filter" (in the sense of rejecting
email addressed to them before they have the opportunity to see it)
anybody's email at all.  Duke as an institution does filter some
incoming mail (not mine) for specific viruses (not spam) as viruses have
a comparatively unambiguous signature.

In the department, where we do USE spam assassin, no bounce messages are
generated except when mail fails for one of the standard reasons
unrelated to filtering of any sort.  SA is implemented so that it
passively scores each piece of mail as it arrives in fields added to the
message header -- in fact this one (to which I am replying) has:

Subject: How Not To Filter Spam
References:
    <Pine.LNX.4.44.0402171555160.20733-100000@lilith.rgb.private.net>
Sender: owner-ietf@ietf.org
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail
X-Spam-Status: No, hits=-4.6 required=5.0 tests=AWL,BAYES_00,FOR_FREE 
        autolearn=no version=2.63
X-Spam-Level: 

Spam assassin is pretty smart -- it correctly identified this as
non-spam (negative total hit count) with a very high level of
confidence.  Empirically VERY few messages that score +5 or better are
not spam, although a few percent of the spam messages that SA sees end
up with scores of between 3 and 5 and get through.  SA is smart, but
cannot compare with the human eye.

When it DOES identify a message as spam it STILL does nothing.  It does
not act as a mail accept/reject mechanism per se. It just adds a header
such as:

Subject: Learn about this investment and get the results you are seeking
tgm
Sender: ylxArnold J <ijci@lavielle.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Sun, 15 Feb 2004 00:25:53 -0800
X-Mailer: Microsoft Outlook Build 10.0.2627
Message-Id: <20040215082535.5A9E2A77D1@mail.phy.duke.edu>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail
X-Spam-Report: 
        *  2.7 NOT_ADVISOR BODY: Not registered investment advisor
        * 4.1 FORGED_RCVD_NET_HELO Host HELO'd using the wrong IP
network
        *  3.0 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
        *  0.1 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS
        *      [24.99.103.83 listed in dnsbl.sorbs.net]
        *  0.7 RCVD_IN_DSBL RBL: Received via a relay in list.dsbl.org
        *      [<http://dsbl.org/listing?ip=24.99.103.83>]
        * 1.5 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in
bl.spamcop.ne
t
        * [Blocked - see <http://www.spamcop.net/bl.shtml?24.99.103.83>]
        * 2.6 RCVD_IN_DYNABLOCK RBL: Sent directly from dynamic IP
address
        *      [24.99.103.83 listed in dnsbl.sorbs.net]
X-Spam-Status: Yes, hits=14.7 required=5.0 tests=FORGED_RCVD_NET_HELO,
        MSGID_FROM_MTA_SHORT,NOT_ADVISOR,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DSBL,
        RCVD_IN_DYNABLOCK,RCVD_IN_SORBS autolearn=spam version=2.63
X-Spam-Level: **************

(from another message in my rejected folder).  I then use a separate
tool, in my case procmail, to sort ALL my mail out into folders (which
might be my inbox or might be Spam or might be /dev/null).  No bounces
are ever generated, no spammer gets any hint that my address is or isn't
a good address, and I can filter on the basis of hits or spam level
under MY control by simply changing my procmail entry.  I can either
keep the rejects (I actually do save them for a week in a rotated file)
and go through them visually very quickly and delete them (I generally
don't, but others I know do, often people who set their personal
threshold for spam at 3 or 4 and a smaller fraction of spam delivered
into their mail spool but have a higher risk of accidentally rejecting
messages that aren't spam) or discard them altogether.  I do a fair bit
of discussion with hardware vendors and textbook vendors that can easily
get a few spam points (but isn't) so I keep mine fairly high.

I still have reservations about attempting to apply this or any other
content based filtering that isn't looking for highly specific
signatures (things like viruses or messages originating from blacklisted
networks that one can identify with very few false positives) at the
SMTP level.  I also have reservations about decisions like the
spam-level that triggers a reject being in somebody's hands other than
my own.  A systems administrator who got a lot of complaints about spam
within a LAN might set it down to 3 or 4 to lower the fraction that
makes it through for everybody, not realizing (or perhaps not caring)
that it might make mail conversations with vendors very difficult.

If that rejection occurred during the original transaction and generated
a bounce -- well, that's the kind of thing we see above, a cure that can
easily be worse than the disease, MUCH worse if the spam is being sent
from a breakout address or bounced through many hops to get there with a
forged or irrelevant return address.

If I understand what you are saying, perhaps there is a way to "do it
correctly" -- reject the spam at the original smtp transaction but with
a message that goes back to the original sender (only) in spite of the
fact that both the From and Return Path header entries might well be
forged and the message relayed through one or more open relays.  I don't
see how, but I admit that I may well be ignorant and there may be a way.

Either way, let me make it very clear.  I do not like any sort of
content filtering that generates automated bounce messages that may or
may not be directed to the original senders.  In the case of viruses
especially (which ALWAYS have forged headers) the bounce message ALWAYS
goes to an innocent and acts as a virus amplifier.  I use linux -- I
CAN'T get most current viruses -- but I receive ten or so messages every
day telling me that some message that "I" sent contained a virus.
Sometimes the bounce messages THEMSELVES are social engineering wrappers
designed to transmit the virus -- bounce messages are so ubiquitous that
viruses routinely use them (with an appropriately forged header) to try
to transmit themselves.  Spam bounces are to my experience no less
braindead and are a significant source of "network abuse" in their own
right.

As was recently pointed out on this list, the automatically generated
bounce messages are also a vehicle for DDOS attacks -- a virus that
forged the SAME return header as it tried to mail itself all over could
arrange for a flood of bounce messages to be directed to some target
address.  The only bounce messages I like to see are ones that tell me
that the addressee is unknown (I mistyped an address), the message could
not be delivered (because it was too large), or the message has been
held up in a spool en route (a destination host is down somewhere).
Having ANY message I send identified as spam, with a bounce or not, is
very annoying.

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu







From owner-ietf@ietf.org  Wed Feb 18 17:47:32 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27529
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 17:47:32 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtaNt-0006QR-QL
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 17:41:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtaMx-0006Ig-Rt
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 17:40:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27051
	for <ietf@ietf.org>; Wed, 18 Feb 2004 17:40:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtaMw-0006Bp-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:40:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtaLz-0006Ac-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:39:39 -0500
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtaLX-000697-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:39:11 -0500
Received: from [192.168.0.101] (pcp05307270pcs.wanarb01.mi.comcast.net[68.42.70.186])
          by comcast.net (rwcrmhc12) with SMTP
          id <20040218223841014008amrhe>; Wed, 18 Feb 2004 22:38:41 +0000
In-Reply-To: <Mahogany-0.66.0-7473-20040218-162211.00@averillpark.net>
References: <359306795.1077108195@[192.168.1.43]> <Mahogany-0.66.0-7473-20040218-162211.00@averillpark.net>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <31566668-6263-11D8-81FB-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Nathaniel Borenstein <nsb@guppylake.com>
Subject: Re: Someone's not getting their email.....
Date: Wed, 18 Feb 2004 17:38:37 -0500
To: Richard Welty <rwelty@averillpark.net>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Feb 18, 2004, at 4:22 PM, Richard Welty wrote:

> i have run internet mailing lists since about 1985. when the first C/R
> systems showed up a few years ago, i arrived at simple conclusion
> very quickly.
>
> anybody who installs a C/R system and doesn't whitelist the mailing 
> lists
> they subscribe to doesn't deserve to receive those mailing lists.
> i remove from my lists anyone who does this. nobody has complained
> yet.
>
> i'd strongly urge that the IETF adapt a similar policy. it's much less
> stressful for all concerned.

This might be a satisfactory policy as an interim measure, but a better 
longer term solution would allow mailing lists to use an optional 
certification mechanism to bypass C/R systems.  (In general, C/R 
systems and certification could be very synergistic, if properly 
implemented.)  At the very least, I believe we could make it a lot 
easier for C/R systems to recognize list mail and handle it 
differently.    -- Nathaniel




From owner-ietf@ietf.org  Wed Feb 18 17:57:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28201
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 17:57:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtaZW-0008UH-4K
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 17:53:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtaYd-0008KZ-GJ
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 17:52:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27948
	for <ietf@ietf.org>; Wed, 18 Feb 2004 17:52:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtaYb-0007AU-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:52:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtaXg-00076r-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:51:45 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtaWM-0006xg-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:50:22 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1IMnpdr015328
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 18 Feb 2004 17:49:51 -0500
Date: Wed, 18 Feb 2004 17:49:51 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Dave Crocker <dcrocker@brandenburg.com>
cc: Tony Hain <alh-ietf@tndh.net>, <ietf@ietf.org>
Subject: Re: How Not To Filter Spam
In-Reply-To: <983826345.20040218141028@brandenburg.com>
Message-ID: <Pine.LNX.4.44.0402181745060.13964-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 18 Feb 2004, Dave Crocker wrote:

> Tony,
> 
> TH> a legitimate message from someone I have corresponded with in the past. The
> TH> only way to detect a fraud at the MUA would be to have a verifiable
> TH> signature from Alain (this was trapped at my MTA due to the exe file). 
> 
>  yes, but no.
> 
>  first, there is an increasingly heated debate between folks who want to
>  sign the message (TEOS, DomainKeys), versus others who want to secure the channel between
>  sender and receiver (RMX, LMAP, SPF, etc.).

What does it matter what the resolution is?  Neither solution eliminates
the spam channel, and solves the problem, as information theory shows.  
Its just a silly debate over two schemes to thread a needle that can't be
threaded.

>  Once that debate is resolved, there is still the matter of compromised
>  system. The message might actually come from the purported author's
>  system, but still not be from the author because it has been taken over
>  by evil forces. So, even with perfect automated validation, the content
>  still might not be valid.

Right.  And it might also be valid and still spam.

		--Dean




From owner-ietf@ietf.org  Wed Feb 18 17:57:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28209
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 17:57:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtaXZ-0008DS-Qd
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 17:51:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtaXH-00084i-FW
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 17:51:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27846
	for <ietf@ietf.org>; Wed, 18 Feb 2004 17:51:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtaXF-000746-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:51:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtaW0-0006yy-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:50:01 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtaV0-0006tV-00
	for ietf@ietf.org; Wed, 18 Feb 2004 17:48:59 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1IMmw23083733
	for ietf@ietf.org env-from <vjs>;
	Wed, 18 Feb 2004 15:48:58 -0700 (MST)
Date: Wed, 18 Feb 2004 15:48:58 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402182248.i1IMmw23083733@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: How Not To Filter Spam
References: <E1AtZ5Y-0000k4-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "Tony Hain" 
> To: "'Vernon Schryver'" <vjs@calcite.rhyolite.com>, <ietf@ietf.org>

> So if you had received the mail sent here yesterday claiming to be from
> Alain Durand would you block Sun or IBM?  ...

I should not have responded specifically (if at all) to the other
gentleman's complaint about my blacklists.  Whatever I do to mail
directed at stuff I control is irrelevant here, provided I do not
affect any third parties.  My freedom to filter access to port 25 (SMTP)
and port 23 (telnet) is equally and completely unfettered.

Two groups oppose that principle.  Some people demand SPEWS and other
filters with what they consider too many false positives be outlawed,
because those filters might affect their outgoing mail.  They are
unmoved by users knowingly choosing their own filters.  They feel their
right to be heard by whomever they choose overrides the rights of their
targets to be left alone.

Other people see nothing wrong in spewing junk at third parties if it
might reduce their own spam loads.  These people include users of
systems based on challenge/responses, bounces after the initial SMTP
transaction (sometimes from within MUAs), "bitch lists" that send
complaints to dozens of third parties.  These people feel their right
to consent to whatever appears in their mailbox overrides the similar
right of others.

As I see it, both groups suffer the same pathology as spammers.


 .................

] From: "Robert G. Brown" <rgb@phy.duke.edu>

] ...
] In the department, where we do USE spam assassin, no bounce messages are
] generated except when mail fails for one of the standard reasons
] unrelated to filtering of any sort.  ...

On today's Internet, innocents are almost certainly receiving bounced
spam and viruses from your system that could not be delivered for
reasons unrelated to filtering, such as bogus target addresses.

] ...
] If that rejection occurred during the original transaction and generated
] a bounce -- well, that's the kind of thing we see above, a cure that can
] easily be worse than the disease, ...

The idiotic messages from that stupid challenge/response system are
not generated during the original SMTP transaction.  It is possible
to do challenge/responses that do not involve separate messages, but
they suffer from MUAs and MTAs that do not handle SMTP rejections
properly and users who cannot understand them.

Somehow making SMTP rejections understandable to users is something
that the IETF might attempt.  I think that is something the ASRG is
considering.  I also think that is nearly impossible.  such is life.


] If I understand what you are saying, perhaps there is a way to "do it
] correctly" -- reject the spam at the original smtp transaction but with
] a message that goes back to the original sender (only) in spite of the
] fact that both the From and Return Path header entries might well be
] forged and the message relayed through one or more open relays.  ...

Headers and the SMTP envelope, forged or not, are irrelevant to SMTP
5yz and 4yz rejections, as far as the rejecting SMTP server is concerned.
If the spam came through an open relay, then a proper SMTP rejection
might cause the relay to send a bounce to an innocent mailbox, but
SMTP relays are out of favor among spammers compared to open proxies.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Wed Feb 18 18:29:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01425
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 18:29:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Atazl-0003wa-8P
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 18:20:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Atays-0003gK-IZ
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 18:19:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00911
	for <ietf@ietf.org>; Wed, 18 Feb 2004 18:19:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atayq-0001Le-00
	for ietf@ietf.org; Wed, 18 Feb 2004 18:19:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Atay2-0001JA-00
	for ietf@ietf.org; Wed, 18 Feb 2004 18:18:59 -0500
Received: from evrtwa1-ar8-4-65-025-155.evrtwa1.dsl-verizon.net ([4.65.25.155] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtaxY-0001FD-00
	for ietf@ietf.org; Wed, 18 Feb 2004 18:18:28 -0500
Received: from eaglet (127.0.0.1:3013)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S474AF> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 18 Feb 2004 15:18:22 -0800
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dave Crocker'" <dcrocker@brandenburg.com>
Cc: <ietf@ietf.org>
Subject: RE: How Not To Filter Spam
Date: Wed, 18 Feb 2004 15:18:14 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Thread-Index: AcP2bAnuTl+NFAZqTBqTp2wGC8ucHgAB9tPg
In-Reply-To: <983826345.20040218141028@brandenburg.com>
Message-Id: <E1AtaxY-0001FD-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave Crocker wrote:
> Tony,
> 
> TH> a legitimate message from someone I have corresponded with in the
past.
> The
> TH> only way to detect a fraud at the MUA would be to have a verifiable
> TH> signature from Alain (this was trapped at my MTA due to the exe file).
> 
>  yes, but no.
> 
>  first, there is an increasingly heated debate between folks who want to
>  sign the message (TEOS, DomainKeys), versus others who want to secure the
> channel between
>  sender and receiver (RMX, LMAP, SPF, etc.).

Is there an obvious reason not to do both? Neither is a total solution, but
either ties a message to an identity object. It is time to stop fighting
over which is better and put both approaches out there. The market will
decide if one is easier for Joe-sixpack to use. 

> 
>  Once that debate is resolved, there is still the matter of compromised
>  system. The message might actually come from the purported author's
>  system, but still not be from the author because it has been taken over
>  by evil forces. So, even with perfect automated validation, the content
>  still might not be valid.

Compromised systems are a problem, but the scope of the bogus mail
originators is limited to the users of the compromised system. Without
traceability it comes from everywhere, but with traceability at least one
knows where to go to correct the problem. If we are stuck fighting over the
'perfect' solution, we will never get anywhere. The engineering community is
particularly bad at figuring out what will catch on for the lowest
denominator consumer, and a committee of engineers takes a bad situation and
makes it hopeless.

Tony 

> 
> 
> d/
> --
>  Dave Crocker <dcrocker-at-brandenburg-dot-com>
>  Brandenburg InternetWorking <www.brandenburg.com>
>  Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Wed Feb 18 18:46:21 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02190
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 18:46:21 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtbIy-0006lL-IO
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 18:40:36 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtbI4-0006f7-VH
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 18:39:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02045
	for <ietf@ietf.org>; Wed, 18 Feb 2004 18:39:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtbI3-0002Ld-00
	for ietf@ietf.org; Wed, 18 Feb 2004 18:39:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtbHB-0002Ji-00
	for ietf@ietf.org; Wed, 18 Feb 2004 18:38:45 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtbGY-0002FP-00
	for ietf@ietf.org; Wed, 18 Feb 2004 18:38:06 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i1INk3d16572;
	Wed, 18 Feb 2004 15:46:03 -0800
Date: Wed, 18 Feb 2004 15:37:27 -0800
From: Dave Crocker <dhc@dcrocker.net>
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <1626961565.20040218153727@brandenburg.com>
To: "Tony Hain" <alh-ietf@tndh.net>
CC: ietf@ietf.org
Subject: Re: How Not To Filter Spam
In-Reply-To: <200402182326.i1INQod15195@joy.songbird.com>
References: <983826345.20040218141028@brandenburg.com>
 <200402182326.i1INQod15195@joy.songbird.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony,

>> first, there is an increasingly heated debate between folks who want
>> to sign the message (TEOS, DomainKeys), versus others who want to
>> secure the channel between sender and receiver (RMX, LMAP, SPF,
>> etc.).

TH> Is there an obvious reason not to do both?

Cost of effort. Distraction of scarce resources. Public damage from
unmet expectations. Etc., etc.


TH>  It is time to stop fighting
TH> over which is better and put both approaches out there.

Recently, I have become fond of the phrase "ready, fire, aim", because
so many people support your suggestion.

As you may have noticed, I consider timely response to urgent need a
very good thing, indeed. But there is a difference between wasting time
working on an ideal solution, to the detriment of an adequate one,
versus ignoring basic questions of efficacy and cost.


>>  Once that debate is resolved, there is still the matter of compromised
>>  system. The message might actually come from the purported author's
>>  system, but still not be from the author because it has been taken over
>>  by evil forces. So, even with perfect automated validation, the content
>>  still might not be valid.

TH> Compromised systems are a problem, but the scope of the bogus mail
TH> originators is limited to the users of the compromised system.

Yup. That's why accountability is inherently good. At least the ability
to track down the source is accurate, even if the "identity" of the
source might be at issue.



d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Wed Feb 18 20:06:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05140
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 20:06:16 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtcUW-0006B7-1T
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 19:56:36 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtcTr-00065H-N6
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 19:55:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04774
	for <ietf@ietf.org>; Wed, 18 Feb 2004 19:55:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtcTp-0005vR-00
	for ietf@ietf.org; Wed, 18 Feb 2004 19:55:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtcSz-0005r6-00
	for ietf@ietf.org; Wed, 18 Feb 2004 19:55:02 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[0Z2LRQEAx9cAwJv6SXvc4yZC7bnMaPTH])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtcSK-0005ky-00
	for ietf@ietf.org; Wed, 18 Feb 2004 19:54:20 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id 1B828A77CE; Wed, 18 Feb 2004 19:54:18 -0500 (EST)
Date: Wed, 18 Feb 2004 19:18:35 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: RE: How Not To Filter Spam
In-Reply-To: <200402182248.i1IMmw23083733@calcite.rhyolite.com>
Message-ID: <Pine.LNX.4.44.0402181727360.21696-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 18 Feb 2004, Vernon Schryver wrote:

> ] From: "Robert G. Brown" <rgb@phy.duke.edu>
> 
> ] ...
> ] In the department, where we do USE spam assassin, no bounce messages are
> ] generated except when mail fails for one of the standard reasons
> ] unrelated to filtering of any sort.  ...
> 
> On today's Internet, innocents are almost certainly receiving bounced
> spam and viruses from your system that could not be delivered for
> reasons unrelated to filtering, such as bogus target addresses.

If a message comes in incorrectly addressed, yes, it will bounce.  It
should, shouldn't it?  This has nothing to do with whether or not it is
spam or a virus or any other kind of message.  If it is a bad thing, it
is a very fundamental bad thing...

As far as spam itself and my filters are concerned, there ARE NO BOUNCES
generated at any point from when the MTA accepts the message as being
RFC-compliant and deliverable through my reading (or not) any message.
The mail comes in (to postfix).  Postfix is configured to use procmail
as a mailbox delivery command.  procmail pipes the mail through spamc.
spamc (the spamassassin client) scores/tags it passively and delivers
it, in my case to procmail again, but now in userspace.  Procmail
applies the rule:

:0:
* ^X-Spam-Level: \*\*\*\*\*
SpamSpamSpam

and presumptive spam is appended to the SpamSpamSpam folder.  

All post-MTA tools are configured to generate no bounce messages (to the
extent that they are capable of such a thing, which is actually not
terribly great). As far as the sender was concerned, the message was
successfully delivered, and no, zero, none, ziltch email messages are
generated to any human or agent as a side effect of their delivery.

There may well be MUA's or post-MTA filters that generate a bounce or
C/R message on "identifying" a message as spam -- I could probably write
a trivial filter that would do this in a few minutes of work, and I get
bounces that appear to come from them from time to time.  I think that
we are in complete agreement that this is a bad idea for so many reasons
-- waste of system resources, annoying the innocent, and the fact that
such tools tend to be written by idiots and hence use appallingly poor
rules to identify "spam" (like the appearance of vi@gra anywhere in any
message even one time -- he says, resigning himself to another stupid
bounce message from whoever it is on this list that apparently is using
such an MUA:-).  However, it seems to me to be just as bad an idea at
the MTA level, and I have little patience with automated C/R systems
because they I have yet to encounter a message for which they were
appropriate or useful or anything but a PITA.

> ] If that rejection occurred during the original transaction and generated
> ] a bounce -- well, that's the kind of thing we see above, a cure that can
> ] easily be worse than the disease, ...
> 
> The idiotic messages from that stupid challenge/response system are
> not generated during the original SMTP transaction.  It is possible
> to do challenge/responses that do not involve separate messages, but
> they suffer from MUAs and MTAs that do not handle SMTP rejections
> properly and users who cannot understand them.
> 
> Somehow making SMTP rejections understandable to users is something
> that the IETF might attempt.  I think that is something the ASRG is
> considering.  I also think that is nearly impossible.  such is life.

> ] If I understand what you are saying, perhaps there is a way to "do it
> ] correctly" -- reject the spam at the original smtp transaction but with
> ] a message that goes back to the original sender (only) in spite of the
> ] fact that both the From and Return Path header entries might well be
> ] forged and the message relayed through one or more open relays.  ...
> 
> Headers and the SMTP envelope, forged or not, are irrelevant to SMTP
> 5yz and 4yz rejections, as far as the rejecting SMTP server is concerned.
> If the spam came through an open relay, then a proper SMTP rejection
> might cause the relay to send a bounce to an innocent mailbox, but
> SMTP relays are out of favor among spammers compared to open proxies.

I will wait with great interest to see if the "nearly impossible" comes
to pass -- it certainly has before in the world of IT;-) Even so, I
personally would want a degree of control over what the MTA rejects out
of mail sent to me.  A spamassassin-like tool (or SA itself) integrated
with the MTA so that the agent uses user-specified rules in place of or
on top of global/default rules, and a fair degree of control over what
is done with regard to the rejected mail.

I actually think that the spamassasin/procmail combination above is
nearly ideal on the MUA side, as I can see no particular reason to want
to bounce to spammers or anybody else, and MOST of the mail that MIGHT
be mis-scored could easily be either whitelisted or confirmed even
without a bounce with a definitely non-spam out of band message.  By
spooling my rejects for a week, I don't even have to have a
retransmission, just a message saying "why didn't you respond to XYZ".
And SA is pretty smart, and actually getting smarter...new rules seem to
be gradually eliminating a lot of the vi@gra-style messages, for
example.

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Wed Feb 18 20:19:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05596
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 20:19:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Atcmz-0008ML-T3
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 20:15:41 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Atck5-00085B-Bf
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 20:12:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05478
	for <ietf@ietf.org>; Wed, 18 Feb 2004 20:12:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atck3-0006qK-00
	for ietf@ietf.org; Wed, 18 Feb 2004 20:12:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Atcj5-0006oM-00
	for ietf@ietf.org; Wed, 18 Feb 2004 20:11:40 -0500
Received: from mail4.atl.registeredsite.com ([64.224.219.78] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atci8-0006m2-00
	for ietf@ietf.org; Wed, 18 Feb 2004 20:10:40 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail4.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1J2ASS4002378
	for <ietf@ietf.org>; Wed, 18 Feb 2004 21:10:28 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Wed, 18 Feb 2004 19:10:34 -0600
Message-ID: <40340CF5.BC6C02E1@nma.com>
Date: Wed, 18 Feb 2004 17:10:13 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: covert channel and noise -- was Re: proposal ...
References: <Pine.LNX.4.44.0402161644000.21587-100000@cirrus.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,TO_ADDRESS_EQ_REAL 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Dean Anderson wrote:
> 
> A covert or sneaky channel is merely one in which the communication is
> //not authorized by the security model// It has nothing to do with
> readability or detectability. 

To be useful for its covert purposes, a covert channel should not be easily 
detectable as a covert channel -- in our case, spam should not be easily
detectable as spam.  Thus, it has to do with readability and detectability. 

That's why, as a matter of logic, we should agree that if the message can 
be detected/read by the intended recipient then it's not in a covert 
channel (anymore). This does not imply that if the message can NOT be detected/read by the intended recipient then there is NO covert channel.

> In yet other words: you whack-a-mole when you find one, but you can't say
> that there aren't any moles. It is not a game you can win. 

That's where we disagree -- if I can make it harder/slower for the other 
side to set up moles than it is for me to find them, I will win.

> We now have a legal process to use against abusers

someone must have said the same for anything we have a law for...
including theft...and yet we do find it useful to lock our cars, no?

In many residence areas, mailboxes have no key and anyone can open
them and insert rogue mail, bombs, etc. This is the same way that your
email address works today. Anyone can put email in your emailbox and,
if they're clever enough, spam filtering in your personal MUA or at the 
MTA will not help. You will receive spam. You say this is not a game
you can win... "there is little that can be done."

In some residence areas, however, mailboxes have no mail slot. The mailman 
has a key to the mailbox and needs to use it in order to insert mail. The 
box owner has another key and uses it to retrieve mail. This still does
not prevent you from receiving a letter laced with anthrax, but it
gives us a good metaphor for improving email: We need to be able to control 
receiving what is posted to us based on the trust/authorization we associate 
with the poster AND the message. In other words, if we have no reason to trust
the poster or the message, we should be able to impose a burden as high as we 
desire on the poster (including no burden).

The decision what to accept or reject should happen at the recipient's MTA 
(preferably) or MUA in interaction with the purported sender's MTA and MUA. Also, to be effective, this should not depend on a user's list of current  
v****a-like words. Providing a barrier for accepting email (i.e., a putting
a selective lock in your email box) is neither a legal issue nor an user 
issue -- is an IETF issue. By using suitable PK encryption for end-to-end 
email privacy (including crypto-puzzles), I suggested we can offer such 
spam burden at no added cost to the user.

I advance that in the old DARPANET days, spam protection was provided
by DARPA, because DARPA could locate and disconnect any user who abused 
the system, and everyone knew it. That's why there was no need to design
email in any other way than what is today, with open mail addresses. 
However, today, the Internet is an open system and there is no way to 
locate and effectively disconnect abusers. The abusers will just continue 
to route around, seeking zero friction to posting, until we put in place 
a better system just like the postal mail had to do, laws notwithstanding.

Cheers,
Ed Gerck



From owner-ietf@ietf.org  Wed Feb 18 20:50:56 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06793
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 20:50:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtdEy-0002nH-3b
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 20:44:36 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtdE7-0002e0-QQ
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 20:43:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06577
	for <ietf@ietf.org>; Wed, 18 Feb 2004 20:43:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtdE6-0000Oj-00
	for ietf@ietf.org; Wed, 18 Feb 2004 20:43:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtdDA-0000MG-00
	for ietf@ietf.org; Wed, 18 Feb 2004 20:42:45 -0500
Received: from oetest.freeswan.org ([205.150.200.166] helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtdCO-0000Kh-00
	for ietf@ietf.org; Wed, 18 Feb 2004 20:41:56 -0500
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca [205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id i1J1fcw15047
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK);
	Wed, 18 Feb 2004 20:41:43 -0500 (EST)
Received: from sandelman.ottawa.on.ca (mcr@marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id i1J1fbIb022394
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 18 Feb 2004 20:41:37 -0500
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id i1J1faJj022391;
	Wed, 18 Feb 2004 20:41:37 -0500
To: Dave Crocker <dcrocker@brandenburg.com>
cc: "Tony Hain" <alh-ietf@tndh.net>, ietf@ietf.org
Subject: Re: How Not To Filter Spam 
In-reply-to: Your message of "Wed, 18 Feb 2004 14:10:28 PST."
             <983826345.20040218141028@brandenburg.com> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 18 Feb 2004 20:41:36 -0500
Message-ID: <22389.1077154896@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,LINES_OF_YELLING 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Dave" == Dave Crocker <dhc@dcrocker.net> writes:
    Dave> first, there is an increasingly heated debate between folks who
    Dave> want to sign the message (TEOS, DomainKeys), versus others who want
    Dave> to secure the channel between sender and receiver (RMX, LMAP, SPF,
    Dave> etc.).

  Why are these mutually exclusive?

  Can't we do both?

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBQDQUT4qHRg3pndX9AQGi6QP9EZ+PYzRg4BRV8bGroZ6lJ8QODRdCV00u
hJsbNSt/3XIjM4otcds90vHVy+KBwUR3I+GwxWyqh5S9wOpqeZJSKGl7oP78uuXe
+rntQ7KMH9U6hhVfU5lxFaZmsTmfTU3shhnEQRk+/NLFFLyMEAPg3XFJtgvL09dB
z3XQlnm0ibY=
=D/Fc
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Wed Feb 18 21:53:03 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09652
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 21:53:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AteBA-0000iD-KE
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 21:44:44 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ate7Y-0000LA-Ji
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 21:41:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09214
	for <ietf@ietf.org>; Wed, 18 Feb 2004 21:40:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ate7W-0003qs-00
	for ietf@ietf.org; Wed, 18 Feb 2004 21:40:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ate6Q-0003o4-00
	for ietf@ietf.org; Wed, 18 Feb 2004 21:39:51 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ate61-0003mE-00
	for ietf@ietf.org; Wed, 18 Feb 2004 21:39:26 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1J2dOMx045159
	for ietf@ietf.org env-from <vjs>;
	Wed, 18 Feb 2004 19:39:24 -0700 (MST)
Date: Wed, 18 Feb 2004 19:39:24 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402190239.i1J2dOMx045159@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: How Not To Filter Spam
References: <Pine.LNX.4.44.0402181727360.21696-100000@lilith.rgb.private.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "Robert G. Brown" <rgb@phy.duke.edu>

> ...
> If a message comes in incorrectly addressed, yes, it will bounce.  It
> should, shouldn't it?  This has nothing to do with whether or not it is
> spam or a virus or any other kind of message.  If it is a bad thing, it
> is a very fundamental bad thing...
> ...

If the envelope sender was forged as is common in spam, universal in
worms, and practically nonexistent in legitimate mail, then your bounce
will afflict third party's mailbox.  My mailbox receives enough worm
bounces to make me say it is an awfully bad thing.

The only fix is to have your external MX servers know all valid
addresses and so reject junk before it can be accepted and later
need to be bounced.  That fix is often impractical or impolitic.

No, SPF, RMX, TOES, etc. etc. etc. cannot fix this problem unless you
assume frictions (deployment resistence and delays) do not exist
or you discard SMTP design goals including transporting messages among
complete strangers.

People who know each other's crypto keys are not strangers.  

If you could someday trust organizations to vouch for strangers and
not sell spam-for-a-day certs to Ralsky/Ricther/&co, then today you
could trust the same outfits to not sell spam-for-a-day/week/years IP
bandwidth accounts.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Wed Feb 18 22:08:33 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10255
	for <ietf-archive@odin.ietf.org>; Wed, 18 Feb 2004 22:08:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AteT4-0002mX-2L
	for ietf-list@asgard.ietf.org; Wed, 18 Feb 2004 22:03:14 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AteQt-0002Kk-1n
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 22:00:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10021
	for <ietf@ietf.org>; Wed, 18 Feb 2004 22:00:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AteQr-00050Q-00
	for ietf@ietf.org; Wed, 18 Feb 2004 22:00:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtePr-0004wZ-00
	for ietf@ietf.org; Wed, 18 Feb 2004 21:59:56 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtePD-0004rN-00
	for ietf@ietf.org; Wed, 18 Feb 2004 21:59:15 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1J2wVRO020269
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 18 Feb 2004 21:58:36 -0500
Date: Wed, 18 Feb 2004 21:58:31 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: RE: How Not To Filter Spam
In-Reply-To: <200402182248.i1IMmw23083733@calcite.rhyolite.com>
Message-ID: <Pine.LNX.4.44.0402182034100.18543-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 18 Feb 2004, Vernon Schryver wrote:

> > From: "Tony Hain" 
> > To: "'Vernon Schryver'" <vjs@calcite.rhyolite.com>, <ietf@ietf.org>
> 
> > So if you had received the mail sent here yesterday claiming to be from
> > Alain Durand would you block Sun or IBM?  ...
> 
> I should not have responded specifically (if at all) to the other
> gentleman's complaint about my blacklists.  Whatever I do to mail
> directed at stuff I control is irrelevant here, provided I do not
> affect any third parties.  My freedom to filter access to port 25 (SMTP)
> and port 23 (telnet) is equally and completely unfettered.

You have a right to make your own decisions.  You don't have the right to 
congregate and act as a group unlawfully.

> Two groups oppose that principle.  Some people demand SPEWS and other
> filters with what they consider too many false positives be outlawed,
> because those filters might affect their outgoing mail.  They are
> unmoved by users knowingly choosing their own filters.  They feel their
> right to be heard by whomever they choose overrides the rights of their
> targets to be left alone.

This isn't quite accurate. Not by a longshot.  Very frequently, its not
"users"  choosing their own filters. Frequently, ISPs choose the filters
for the users and without their knowledge or consent. Users give consent
to blocking spam, not for participation in alternate non-spam boycotts.  
Even in the relatively rare case when it is chosen by the user, it is
often the case that blacklists misrepresent their purposes to unsuspecting
users. Often, blacklists aren't about blocking abuse or spam at all.  
SPEWS and certain groups violate antitrust law, which prohibits group
boycotts from harming business.  SPEWS and some other blacklists aren't
about preventing abuse or spam. They are about harming business, and often
not even spam businesses, and such harm has been made illegal by law.

For example, Paul Vixie hosts SORBS, an Australian blacklist on his
ISC.ORG company.  SORBS has been booted from other American ISPs, and the
operator, Matthew Sullivan has had other sites (isux.com) booted for AUP
violations such as threats of mailbombing "spammers".  While the claimed
purpose of the SORBS blacklist is to block spam, one thing that
distinguishes this list is that it claims that Av8 Internet's IP address
space is hijacked.  No reasonable person could (or has) made this mistake.  
When this is brought to the attention of SORBS' users, they invariably
quit using SORBS. This isn't what they thought SORBS was blocking.  When
it was brought to Mr.  Sullivan's attention, he first replied that 'he is
not responsible for SORBS'.  When this was refuted, he said that he had no
assets, and challenged me to sue or contribute.  

As most know, Paul Vixie has his own blacklist at Mail-abuse.org. So what
is his interest in hosting SORBS at ISC.ORG after it was booted by other
ISPs for abuse reasons?  The reason could be seen in exactly the response
given by Mr. Sullivan: Vixie has assets, and therefore is motivated to
comply with civil law. But it would seem that Mr. Vixie would like to
support Mr.  Sullivan's irresponsible efforts without entangling himself
or Mail-abuse.org.  Perhaps he expects he can claim that SORBS is just a
customer of ISC, and that he has an arm's-length relationship and isn't
responsible for its defamation.  Complaints have been made to ISC and
ISC's upstream, EP.NET for SORBS continuing unlawful defamatory activity,
which is typically an AUP violation. ISC.ORG uses SORBS to filter its
abuse email.  Bill Manning (EP.NET) didn't want to forward or accept a
complaint about ISC or ISC's customer.  These complaints have been
ignored. But the lack of responsible enforcement allows some statements to
be made:  It just shows that Mr. Vixie is also irresponsible. It also
shows that Mr. Manning is irresponsible as well.

Mr. Sullivan, like many of the disreputable blacklist operators claims he
has no assets which can be taken by lawsuit, and thus has nothing to lose,
and no reason to comply with civil law. Instead of blocking spam, SORBS
has gone to extreme lengths to defame and interfere with Av8 Internet's
business, and probably the business of other companies for reasons that
have nothing whatsoever to do with spam.  None of this is made clear to
potential SORBS users until they subscribe to the list and block email
they don't want to block.

For another example, consider Alan Brown of ORBS.  ORBS was booted by
Canadian ISP for abuse even before Mr. Brown took control of it.  Mr.  
Brown has lost 3 separate lawsuits involving issues of defamation and
false statements. 2 of the lawsuits involved ORBS making false statements
about ISPs that Mr.  Brown did not like.  None of this was made clear to
ORBS users when they subscribed, and the blacklists blocked email they
didn't want to block.

The list of disreputable blacklists goes on and on.  The common thread is
a desire to mislead subscribers into thinking they are blocking spam, and
then abusing their subscribers by blocking things their subscribers didn't
agree to block.

A unique characteristic of SPEWS is that it's operators are anonymous,
apparently in order to prevent themselves from being held legally
responsible.

Mail-abuse (MAPS) was sued in 2000 by a permission-based emailer. This
wasn't a spammer, in the abusive sense. It was just a company that sent
commercial email to people who had given their addresses for that purpose.
MAPS was forced to stop blocking them.  It has frequently been said that 
this company should never have been blocked by MAPS--the company didn't 
meet the criteria that MAPS was supposed to be using for its blacklist.

Besides deceiving their users about their criteria, or violating the
criteria, the blacklists seek to be immune from lawsuits by transferring
their operations between countries or by having operators with no assets
take responsibility. This is just a scam.  Abusers and virus operators
don't sue. Genuine businesses sue.  That's who these abusive blacklists
are hiding from.  But their users don't want email from these businesses
blocked.

A number of blacklists have shutdown by blocking all of their subscribers
email. This is an irresponsible act, and widely criticized by their users
as being irresponsible.  No users want to use a blacklist that might
shutdown suddenly and block all of their email.  These are not responsible
organizations, and mostly they are misleading their subscribers about
their goals and what email they might block.

And things detailed in this message isn't even a fraction of all the abuse
that has been conducted by blacklists.  There is no reason to have
sympathy for blacklists. They have very little to do with fighting spam,
and those opposed to blacklists are not trying to be heard by those who
want to be left alone.  Just the opposite. People quit using the
blacklists, and then new blacklists pop up, to mislead them again.


		--Dean




From owner-ietf@ietf.org  Thu Feb 19 02:51:21 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04238
	for <ietf-archive@odin.ietf.org>; Thu, 19 Feb 2004 02:51:21 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtinS-0000kY-J2
	for ietf-list@asgard.ietf.org; Thu, 19 Feb 2004 02:40:34 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Atin6-0000fh-TC
	for ietf@asgard.ietf.org; Thu, 19 Feb 2004 02:40:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03238
	for <ietf@ietf.org>; Thu, 19 Feb 2004 02:40:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atin4-0001vd-00
	for ietf@ietf.org; Thu, 19 Feb 2004 02:40:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Atim7-0001np-00
	for ietf@ietf.org; Thu, 19 Feb 2004 02:39:12 -0500
Received: from ftp.netlab.nec.de ([195.37.70.21] helo=ftp.ccrle.nec.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atil6-0001cd-00
	for ietf@ietf.org; Thu, 19 Feb 2004 02:38:08 -0500
Received: from netlab.nec.de (tokyo.netlab.nec.de [195.37.70.2])
	by ftp.ccrle.nec.de (Postfix) with ESMTP id 295AFF5A9
	for <ietf@ietf.org>; Thu, 19 Feb 2004 08:42:55 +0100 (CET)
Message-ID: <403467DE.7070801@netlab.nec.de>
Date: Thu, 19 Feb 2004 08:38:06 +0100
From: Lars Eggert <lars.eggert@netlab.nec.de>
Organization: NEC Network Laboratories
User-Agent: Mozilla Thunderbird 0.5 (Macintosh/20040208)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 59th IETF - FINAL AGENDA
References: <200402172059.PAA05093@ietf.org>
In-Reply-To: <200402172059.PAA05093@ietf.org>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms080505030602020302010007"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a cryptographically signed message in MIME format.

--------------ms080505030602020302010007
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

FYI, I've made an ical version of the agenda available at
http://www.icalx.com/public/larse/IETF-59.ics.

Apple iCal users can directly subscribe at
webcal://www.icalx.com/public/larse/IETF-59.ics. I hear this may work
with Mozilla as well, but I have no firsthand experience with that.

(A perl script periodically updates the ical version based on the ASCII
agenda at http://ietf.org/meetings/agenda_59.txt. No guarantees for
accuracy!)

Lars

(PS: Re-sent, first message didn't make it to the list apparently.)
-- 
Lars Eggert                                     NEC Network Laboratories


--------------ms080505030602020302010007
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJ/zCC
Az8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQI
EwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENv
bnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAi
BgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVy
c29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5
NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBM
dGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9Vvy
Gna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOC
dz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCB
kTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhh
d3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNV
HREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQAD
gYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFi
w9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpb
NU1341YheILcIRk13iSx0x1G/11fZU8wggNaMIICw6ADAgECAgMLU6IwDQYJKoZIhvcNAQEE
BQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0
ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTAz
MTIxNTEyMzEyOFoXDTA0MTIxNDEyMzEyOFowgYQxDzANBgNVBAQTBkVnZ2VydDENMAsGA1UE
KhMETGFyczEUMBIGA1UEAxMLTGFycyBFZ2dlcnQxKDAmBgkqhkiG9w0BCQEWGWxhcnMuZWdn
ZXJ0QG5ldGxhYi5uZWMuZGUxIjAgBgkqhkiG9w0BCQEWE2xhcnMuZWdnZXJ0QGdteC5uZXQw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDWps58Zq8Buu2DKDl9crbvzSo6zWsZ
TkQLr5zOTqUMs/eU7Mcohv64O4IxWWYGLfYsjDRxUlmdHdJUbyTtUh2lH452DUDJByXidlLm
RDgohG0AVwztedqy1+hE3VnCdpMhUGks+6ntrr3dKSxMgLM0AM1kPWsH9lWX6IOPdxOC30gM
PiQ65zH9PR70befQLgFPKcAv0wP8210l05n8ekwYAcq2cm3/j+nuDu0HEh5pgsnY7cVELeNJ
ODvr4IiE1t3c2w4+0Nc/WJrqGCMl+gZ8c+7FtzjoyDeEsCjNFDeA2ymNd+10O6kjwvPHlzPr
3rW73RDRPAjMJ49HXlueiuoNAgMBAAGjdzB1MCoGBStlAQQBBCEwHwIBADAaMBgCAQQEE0wy
dU15ZmZCTlViTkpKY2RaMnMwOQYDVR0RBDIwMIEZbGFycy5lZ2dlcnRAbmV0bGFiLm5lYy5k
ZYETbGFycy5lZ2dlcnRAZ214Lm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GB
AHgrv3SQFD4AS4lY4oKcI3iTHcclEHbYfg3UUb8zzCUsl+OJoz0nmebGmOL+tvNj5GvCrWnN
H4LvVLh8ZBhFXms7eKJ1YiHgbKwTRK23P8Y5NDit5ico0ZjpFWeenUWj3ajEbN6n4K8dNp+C
0b2apnSrlFVWY6BucZFIYqQ1Lf91MIIDWjCCAsOgAwIBAgIDC1OiMA0GCSqGSIb3DQEBBAUA
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTAeFw0wMzEy
MTUxMjMxMjhaFw0wNDEyMTQxMjMxMjhaMIGEMQ8wDQYDVQQEEwZFZ2dlcnQxDTALBgNVBCoT
BExhcnMxFDASBgNVBAMTC0xhcnMgRWdnZXJ0MSgwJgYJKoZIhvcNAQkBFhlsYXJzLmVnZ2Vy
dEBuZXRsYWIubmVjLmRlMSIwIAYJKoZIhvcNAQkBFhNsYXJzLmVnZ2VydEBnbXgubmV0MIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1qbOfGavAbrtgyg5fXK2780qOs1rGU5E
C6+czk6lDLP3lOzHKIb+uDuCMVlmBi32LIw0cVJZnR3SVG8k7VIdpR+Odg1AyQcl4nZS5kQ4
KIRtAFcM7XnastfoRN1ZwnaTIVBpLPup7a693SksTICzNADNZD1rB/ZVl+iDj3cTgt9IDD4k
Oucx/T0e9G3n0C4BTynAL9MD/NtdJdOZ/HpMGAHKtnJt/4/p7g7tBxIeaYLJ2O3FRC3jSTg7
6+CIhNbd3NsOPtDXP1ia6hgjJfoGfHPuxbc46Mg3hLAozRQ3gNspjXftdDupI8Lzx5cz6961
u90Q0TwIzCePR15bnorqDQIDAQABo3cwdTAqBgUrZQEEAQQhMB8CAQAwGjAYAgEEBBNMMnVN
eWZmQk5VYk5KSmNkWjJzMDkGA1UdEQQyMDCBGWxhcnMuZWdnZXJ0QG5ldGxhYi5uZWMuZGWB
E2xhcnMuZWdnZXJ0QGdteC5uZXQwDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQQFAAOBgQB4
K790kBQ+AEuJWOKCnCN4kx3HJRB22H4N1FG/M8wlLJfjiaM9J5nmxpji/rbzY+Rrwq1pzR+C
71S4fGQYRV5rO3iidWIh4GysE0Sttz/GOTQ4reYnKNGY6RVnnp1Fo92oxGzep+CvHTafgtG9
mqZ0q5RVVmOgbnGRSGKkNS3/dTGCAzswggM3AgEBMGkwYjELMAkGA1UEBhMCWkExJTAjBgNV
BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJz
b25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgMLU6IwCQYFKw4DAhoFAKCCAacwGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDQwMjE5MDczODA2WjAjBgkqhkiG
9w0BCQQxFgQUlGkDVcj56/7KVkxXPM5aFW4hsyUwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG
9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN
AwICASgweAYJKwYBBAGCNxAEMWswaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl
IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECAwtTojB6BgsqhkiG9w0BCRACCzFroGkwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0
ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgMLU6IwDQYJKoZIhvcNAQEBBQAEggEA
nJLnR6dFoCEH03uCcA5q2rEElmCXiEV9o8xwItpPd15MgYEZuY7Js8/jpYCaXcRhMhAionN6
C6VljrOORCfIWlwO/wIRvrRghXw6MgDkNz51Z75bmMaaT+aRKhAejpgHJV2Vd609tYpRzu98
S9YnglDVX3uCipcvQQkLPSnggMCRw2pnbcrXtJmkrY8I9dWGJEHSZpG9cvWq0yh9OjokXYsu
8QBn0TEi0XuoFU63yFK0ehCIzG/nKkqSwZgBDeBqhdjX+6NNhkcBs2O3UN6BsUKEMxlbvGcD
7neUGl8E1c/LGplpx8BtSogGM45Dfy08y8yeoyo8dOJ6ZTpX5zycKAAAAAAAAA==
--------------ms080505030602020302010007--



From owner-ietf@ietf.org  Thu Feb 19 05:53:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13451
	for <ietf-archive@odin.ietf.org>; Thu, 19 Feb 2004 05:53:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Atle5-0008OM-9n
	for ietf-list@asgard.ietf.org; Thu, 19 Feb 2004 05:43:05 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Atld4-0008Mj-6v
	for ietf@asgard.ietf.org; Thu, 19 Feb 2004 05:42:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13131
	for <ietf@ietf.org>; Thu, 19 Feb 2004 05:41:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atld1-0004db-00
	for ietf@ietf.org; Thu, 19 Feb 2004 05:41:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Atlc3-0004Zn-00
	for ietf@ietf.org; Thu, 19 Feb 2004 05:41:00 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atlb6-0004W9-00
	for ietf@ietf.org; Thu, 19 Feb 2004 05:40:00 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1JAePrq089788;
	Thu, 19 Feb 2004 11:40:26 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0402181727360.21696-100000@lilith.rgb.private.net>
References: <Pine.LNX.4.44.0402181727360.21696-100000@lilith.rgb.private.net>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F5484379-62C7-11D8-BD64-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: How Not To Filter Spam
Date: Thu, 19 Feb 2004 11:39:56 +0100
To: "Robert G. Brown" <rgb@phy.duke.edu>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 19-feb-04, at 1:18, Robert G. Brown wrote:

> If a message comes in incorrectly addressed, yes, it will bounce.  It
> should, shouldn't it?

Yes, but only by ejecting the message immediately during the SMTP 
session. Accepting the message, then realize it can't be delivered and 
sending a bounce message back to the email address listed in the "from" 
header is NOT the right thing to do for reasons that should be apparent 
by now.

> I actually think that the spamassasin/procmail combination above is
> nearly ideal on the MUA side,

It is not, because:

1. Bandwidth is used up by spam (which is fortunately usually not that 
big) and worms (which tend to be much bigger)
2. A lot of processing time is used on your system(s)
3. Either:
3a. Legitimate senders who are tagged as spam are blackholed and are 
unaware that you don't read their message
3b. You must manually sort through all messages that are flagged as spam




From owner-ietf@ietf.org  Thu Feb 19 09:35:24 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20061
	for <ietf-archive@odin.ietf.org>; Thu, 19 Feb 2004 09:35:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Atp7P-0004gw-1n
	for ietf-list@asgard.ietf.org; Thu, 19 Feb 2004 09:25:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Atp71-0004g6-GL
	for ietf@asgard.ietf.org; Thu, 19 Feb 2004 09:25:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19618
	for <ietf@ietf.org>; Thu, 19 Feb 2004 09:25:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atp70-0006vp-00
	for ietf@ietf.org; Thu, 19 Feb 2004 09:25:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Atp67-0006ti-00
	for ietf@ietf.org; Thu, 19 Feb 2004 09:24:17 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[O3GSBzMunFlcvpFYeo+0ZawgLqkgGoCm])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atp5f-0006rD-00
	for ietf@ietf.org; Thu, 19 Feb 2004 09:23:47 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id D5C9AA799E; Thu, 19 Feb 2004 09:23:43 -0500 (EST)
Date: Thu, 19 Feb 2004 08:47:55 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: How TO Filter Spam
In-Reply-To: <F5484379-62C7-11D8-BD64-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0402190638131.21826-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 19 Feb 2004, Iljitsch van Beijnum wrote:

> > I actually think that the spamassasin/procmail combination above is
> > nearly ideal on the MUA side,
> 
> It is not, because:
> 
> 1. Bandwidth is used up by spam (which is fortunately usually not that 
> big) and worms (which tend to be much bigger)

Close to a MB/day (on average) for me personally -- html is not compact.
Bouncing these requires (at the MTA or beyond) requires examining them
and applying tests to the entire message, generally, so bouncing at the
MTA saves no wasted bandwidth -- it close to doubles it.  

More than doubles it if the bounce generates further autogenerated mail
as it caroms off of bogus return addresses.  Note that server/netowrk
load is likely dominated by latency, not bandwidth -- most email
messages are at order of a single packet or two of data with ethernet
MTUs, but negotiating a transaction requires several rounds of small
packets.

Not enormous, agreed (although that is partly a matter of the size of
your organization and number of users and their internet "profile" to
spammers) but a significant fraction of all mail and not trivial.

> 2. A lot of processing time is used on your system(s)

This is the same for MTA-side and MUA-side processing as well.  In fact
it might be the same core tool used in the two cases.  Processing power
is linked to how sophisticated a filter you apply, and a stupid filter
is a cure FAR worse than the disease.  Either way you have to receive
the entire message at least to memory and apply the filter.

The processing power required, BTW, while non-trivial is easily within
the reach of modern CPUs for up to perhaps a thousand users per server
(I don't really know how much beyond -- we're not close to a boundary
here with hundreds of users).  A fully userspace solution permits it to
even be distributed to the user's processors and offload it altogether
from the mail server.

The one thing I can think of that an MTA-side bounce without any sort of
spooling or significant logging of the rejected messages saves relative
to user side sorting is disk spool, and this is really at the option of
the user, who can spool rejects into /dev/null.

> 3. Either:
> 3a. Legitimate senders who are tagged as spam are blackholed and are 
> unaware that you don't read their message
> 3b. You must manually sort through all messages that are flagged as spam

Instead you have legitimate readers who may be unaware that a message to
them was bounced or blacklisted, you have one size fits all message
sorting, you have the aforementioned doubling of bandwidth consumption,
you have the possibility of your site being used as a "reflector" in a
DDOS attack.  And you (the user) CAN'T sort through all messages that
are flagged as spam because they aren't spooled, they are rejected!

In MUA-side sorting with no bounce you control the sorting process more
or less completely and can set rejection thresholds high enough that
your false positive rate is (in YOUR judgement, not mine, the IETF's, or
your local system's administrator) negligible and then neglect them.  At
5, SA's false positive rate is maybe one message in 100 days, from my
spot checks of it, and that rate actually decreases in time as they
refine the tests.  Its false negative rate is high -- a few percent of
the spam it sees makes it through -- but so does more or less all of the
spam-like legitimate mail I get including mail from vendors and vendor
quotes.  The spam that does make it through is generally "stealth spam"
(the kind with relatively short messages with lots of random words
intended to confuse word count filters, few or no graphics, and no
embedded html) and is easily rejected.  A weekly catalog newsletter from
e.g. musician's friend and a local bookstore make it through (I'm
subscribed on their lists but have NOT whitelisted their sites) and act
as coal miner birds for other desired spam-like traffic.

Those of my friends who use a lower spam threshold (one that lets almost
NO spam through to their primary spool at the expense of a larger false
positive rate) do manually sort their presorted spam folder.  However,
BECAUSE the folder is presorted, all they functionally have to do is
scan the subject/from lines and use their "internal" whitelists to pick
out the false positives, click a button or two to delete the rest en
masse, and move on.  As in it takes them maybe a minute or two to
process hundreds of rejects with very high reliability and without
having to look at message contents at all in almost all cases.  If you
like, they prefer a two state sort with human judgement used before
final rejection but using a computer to do 80% of the work (winnowing
all the spam out of their mainline mail spool where they DO read each
message and think about it one at a time.  I'm talking systems people,
mostly, who have a very low false positive threshold and who DON'T want
to explain to their user base (which might include their employer, for
example) why a message sent to them is flagged and bounced as SPAM.

With MUA-side processing, you can even do a three way sort -- sort all
spam-level 4-5 stuff into a "maybe" folder, and all 5+ stuff into a spam
folder or /dev/null.  At 5+ your false positive rate would be one to
three a year -- far lower than the human false positive or "oops"
factor, especially when dealing with a junk-filled mailbox.  Almost no
spam would make it into your mailbox.  The 4-5 "borderline" messages
would constitute maybe 10% of all spam, would have maybe 2% false
positives mixed in (mostly things like musician's friend catalogs that I
often don't read anyway) and would take a very short period every day to
terminally sort and reject.

Note well the fineness of control.  I'm NOT totally against MTA-side
processing but would want an MTA-side agent to basically be "spam
assassin" and permit spooling of an intermediate class of "maybe" spam
according to its necessarily fuzzy sorting logic.  The bounce issue is
endlessly debateable.  

At the moment, bounces of viruses are a pat peeve of mine -- they ARE a
form of abuse, this should NEVER be done, and the IETF would do
everybody a favor if they articulated this, and the reasons for it very
clearly, combined them with a statistical study that indicates that 0%
of the bounce messages actually reach the infected party and no more
than 1 or 2% reach somebody that might be on the same network as the
infected party and capable of passing the word to them, and took it to
the worst AV vendors and get them to deprecate the use of bounce
features in their existing products and remove them altogether in future
ones because they do no good, do a fair bit of harm in the steady state,
and have the potential to do a great deal of harm all at once if all the
AV products suddenly become reflector points in a timed, virus-driven
DDOS attack.  Or we can just tool along and wait for this to happen and
I can continue to live with the ten or so messages a day, NONE of them
flagged as virus or spam, that are "virus bounces".

The big questions are then: what fraction of SPAM has forged headers and
is a form of "virus" in its own right? and could the MTA filter be made
smart enough NOT to generate a bounce unless the from/return addresses
matched the registered domain of the originating host. I actually think
that this sort of thing would be possible -- one way that I identify
viruses now WITHOUT the use of a virus scanner loaded with signatures is
to look at the headers and look for lines like:

X-Authentication-Warning: moorcock.acpub.duke.edu: cyrus set sender to
  bbooth@earthlink.net using -f

or a clear indication that the message has forged headers.  spamassassin
does the same thing:

        * 2.6 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook

Here is a message for which there is no point in generating a bounce,
for example:

From bobby20@earthlink.net  Thu Feb 19 07:42:40 2004
Return-Path: <bobby20@earthlink.net>
Delivered-To: rgb@phy.duke.edu
Received: from ipserv.phy.duke.edu (ipserv.phy.duke.edu [152.3.182.5])
        by mail.phy.duke.edu (Postfix) with ESMTP id CD802A77CF
        for <rgb@phy.duke.edu>; Thu, 19 Feb 2004 07:42:40 -0500 (EST)
Received: from 152.3.182.5 (unknown [62.150.67.242])
        by ipserv.phy.duke.edu (Postfix) with SMTP id 48A443AFFB
        for <rgb@phy.duke.edu>; Thu, 19 Feb 2004 07:42:38 -0500 (EST)
Received: from 188.106.194.65 by web365.mail.yahoo.com; Wed, 18 Feb 2004 12:33:04 -0300

The mail originates from an anonymous client on an unregistered network
and is sent to one of the spam-oozing pustules on the internet where
anybody can get an email account in seconds and abuse it for minutes,
and then throw it away.  It has a forged from and return path (ones that
clearly bear no resemblance to the originating more or less open yahoo
proxy).  It is also OTHERWISE identified as spam -- this particular
message has a spam level of 24.6 (5 required for ~0.01% false positive).

It should be (and was, until now:-) rejected unread and without tainting
the human mind.  It should NOT generate a bounce message, as a bounce is
utterly pointless and will actually create a "reverberation" as
bobby20@earthlink.net is doubtless not a valid address any more (it is
in multiple blacklists) and the earthlink.net MTA will undoubtedly
generate a second bounce of your bounce or harrass the hapless user
bobby20 whose fraternity brothers thought that they'd prank him as a
nerd.

Going through my spam reject spool (and this is a REAL reject spool,
filled with current messages like the one above from this very morning)
I have a very hard time finding a single message for which a bounce is
appropriate.  "Real" vendor mail (even mass mail) has a from address and
delivery path that correspond and other things of that ilk such that
sure, a bounce would work but for a real vendor mailing, even a mass
mailing, a bounce isn't really necessary.  They will generally have the
required-by-law unsubscribe at the bottom, and will generally honor it
if you unsubscribe.  They MAY remarket your email address if you
unsubscribe.  With SA you are free to /dev/null their message and let
them continue to waste their resources talking to the hand or you can
actively unsubscribe.  A bounce message might or might not serve to get
you unsubscribed.  Finally, I shudder when I think of bounces of any
sort that make it through lists.  They drive me nuts on the beowulf list
although they frequently ARE caught -- some come "from" a whitelisted
user.

Overall, it boils down to a question of degree of specificity, utility,
and statistics.  Numbers, I truly do love them.  Looking at my own
admittedly anecdotal numbers (although I'm pleasantly exposed to a
horrifically wide range of spam as I seem to be in a few thousand
address books of complete strangers and have a middling large web
presence, so my anecdotal numbers are actually probably not a terrible
sample), a "blind" MTA bounce of spam is more or less totally useless as
not 1 bounce message in 100 will actually go back to the originator.
1% efficiency is a joke.

SO, if y'all really want to push MTA-side bounces:

  a) Use one of the very good MUA-side sorters such as spamassassin for
a few months and accumulate a nice, fat spool full of presumptive spam.
Do this with a few hundred volunteers, actually to get better
statistics.

  b) Sort out the message headers into malformed and not in some way
that leads you to believe that there is nobody home at the return
addresses of the malformed.  Go ahead, test the return addresses to be
sure!  Just do it from YOUR account and not mine...:-).  

  c) Email the well-formed header return addresses as well.  For yuks,
do so from a new, pristine email address (one that is in NOBODY'S lists)
and measure the time required for the new address to appear in new spam.
For even more yuks, generate an email address for each reply and get
per-return statistics on same.

  d) Determine the statistics from the data.  What is the probability
that a bounce will reach the human or even the organization that
originated the spam?  What is the probability of nucleating ten new
messages from new spammers per bounce (even bounce) reply or
unsubscribe?

THEN you can do two things:  Propose an MTA bounce with a proper
foundation, and propose that foundation.  Presumably it will be one that
does NOT bounce to pretty much the entire class of spam with malformed
headers and may have other rules that you discover by sorting through
all the patterns -- spamassassin gives you a very DETAILED breakdown of
the rules and results used to tag a message spam, so you can actually
look for very subtle multivariate correlates if you want to do a
thorough job.

I personally am a great believer in the central limit theorem, and in
spite of possible biases in my limited sample I suspect that it is
actually very likely highly representative of the current profile of
spam today.  On the basis of my own sample, it is not WORTH it to winnow
out the one message in 10 (to be generous) or more likely one message in
100 (to be realistic) that might, and I say might, make it back to an
originating human.  It definitely isn't worth my own time to try "hand
bouncing" lots of messages to validate my anecdotal impressions.

So there's the gauntlet.  You propose that bounces are important.  Are
they important enough to justify bouncing 9 messages out of 10 to false
return addresses?  How about 99 messages out of 100?  You propose that
bounces will be effective.  Well, starting with a 1% to 10% MAXIMUM
success rate off the top you can't be VERY effective...:-) Perhaps
you'll be effective in warning the even smaller percentage (one that
depends on rejection threshold, to be sure) of false positives that
their message didn't get through.  Here is where one has to look hard at
the cost benefit equation.  Given the above first-approximation
statistics, IS it worth the very substantial costs in misdirected and
useless bounces to catch that small and controllable percentage of false
positives?  If you disagree with my statistics, come up with better
ones.  If you think that the answer is a matter of principle and that we
must leave No Legitimate Mail Behind (however tiny a fraction it is),
well, I would disagree, and we'd have to try to work out a consensus of
some sort.

At the moment, I'm open minded.  Come up with an actual bounce algorithm
(based on spamassasin ratings unless you can come up with something
better) that bounces no MORE than one message in 100 to a non-existent
or false address and that leaves no room for a DDOS attack to propagate.
You can publish the same tests to the AV crowd so that they can fix
their bounce programs.  That would be an important first step in
convincing me that MTA-side bounces are feasible/desireable, especially
if they are driven by a truly intelligent agent that leaves a user with
PERSONALIZED control over their filtering controls.

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Thu Feb 19 10:59:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24758
	for <ietf-archive@odin.ietf.org>; Thu, 19 Feb 2004 10:59:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtqNj-000643-Jk
	for ietf-list@asgard.ietf.org; Thu, 19 Feb 2004 10:46:31 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtRD4-0007kV-8p
	for ietf@asgard.ietf.org; Wed, 18 Feb 2004 07:53:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08785
	for <ietf@ietf.org>; Wed, 18 Feb 2004 07:53:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtRD3-0003pt-00
	for ietf@ietf.org; Wed, 18 Feb 2004 07:53:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtRC8-0003nl-00
	for ietf@ietf.org; Wed, 18 Feb 2004 07:52:53 -0500
Received: from ftp.netlab.nec.de ([195.37.70.21] helo=ftp.ccrle.nec.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtRBm-0003lO-00; Wed, 18 Feb 2004 07:52:30 -0500
Received: from netlab.nec.de (tokyo.netlab.nec.de [195.37.70.2])
	by ftp.ccrle.nec.de (Postfix) with ESMTP
	id A09ADF5A9; Wed, 18 Feb 2004 13:57:14 +0100 (CET)
Message-ID: <4033600A.6030408@netlab.nec.de>
Date: Wed, 18 Feb 2004 13:52:26 +0100
From: Lars Eggert <lars.eggert@netlab.nec.de>
Organization: NEC Network Laboratories
User-Agent: Mozilla Thunderbird 0.5 (Macintosh/20040208)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-secretariat@ietf.org, ietf@ietf.org
Subject: Re: 59th IETF - FINAL AGENDA
References: <200402172059.PAA05093@ietf.org>
In-Reply-To: <200402172059.PAA05093@ietf.org>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090109060401090806060106"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a cryptographically signed message in MIME format.

--------------ms090109060401090806060106
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

FYI, I've made an ical version of the agenda available at 
http://www.icalx.com/public/larse/IETF-59.ics.

Apple iCal users can directly subscribe at 
webcal://www.icalx.com/public/larse/IETF-59.ics. I hear this may work 
with Mozilla as well, but I have no firsthand experience with that.

(A perl script periodically updates the ical version based on the ASCII 
agenda at http://ietf.org/meetings/agenda_59.txt. No guarantees for 
accuracy!)

Lars
-- 
Lars Eggert                                     NEC Network Laboratories

--------------ms090109060401090806060106
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJ/zCC
Az8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQI
EwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENv
bnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAi
BgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVy
c29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5
NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBM
dGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9Vvy
Gna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOC
dz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCB
kTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhh
d3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNV
HREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQAD
gYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFi
w9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpb
NU1341YheILcIRk13iSx0x1G/11fZU8wggNaMIICw6ADAgECAgMLU6IwDQYJKoZIhvcNAQEE
BQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0
ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTAz
MTIxNTEyMzEyOFoXDTA0MTIxNDEyMzEyOFowgYQxDzANBgNVBAQTBkVnZ2VydDENMAsGA1UE
KhMETGFyczEUMBIGA1UEAxMLTGFycyBFZ2dlcnQxKDAmBgkqhkiG9w0BCQEWGWxhcnMuZWdn
ZXJ0QG5ldGxhYi5uZWMuZGUxIjAgBgkqhkiG9w0BCQEWE2xhcnMuZWdnZXJ0QGdteC5uZXQw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDWps58Zq8Buu2DKDl9crbvzSo6zWsZ
TkQLr5zOTqUMs/eU7Mcohv64O4IxWWYGLfYsjDRxUlmdHdJUbyTtUh2lH452DUDJByXidlLm
RDgohG0AVwztedqy1+hE3VnCdpMhUGks+6ntrr3dKSxMgLM0AM1kPWsH9lWX6IOPdxOC30gM
PiQ65zH9PR70befQLgFPKcAv0wP8210l05n8ekwYAcq2cm3/j+nuDu0HEh5pgsnY7cVELeNJ
ODvr4IiE1t3c2w4+0Nc/WJrqGCMl+gZ8c+7FtzjoyDeEsCjNFDeA2ymNd+10O6kjwvPHlzPr
3rW73RDRPAjMJ49HXlueiuoNAgMBAAGjdzB1MCoGBStlAQQBBCEwHwIBADAaMBgCAQQEE0wy
dU15ZmZCTlViTkpKY2RaMnMwOQYDVR0RBDIwMIEZbGFycy5lZ2dlcnRAbmV0bGFiLm5lYy5k
ZYETbGFycy5lZ2dlcnRAZ214Lm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GB
AHgrv3SQFD4AS4lY4oKcI3iTHcclEHbYfg3UUb8zzCUsl+OJoz0nmebGmOL+tvNj5GvCrWnN
H4LvVLh8ZBhFXms7eKJ1YiHgbKwTRK23P8Y5NDit5ico0ZjpFWeenUWj3ajEbN6n4K8dNp+C
0b2apnSrlFVWY6BucZFIYqQ1Lf91MIIDWjCCAsOgAwIBAgIDC1OiMA0GCSqGSIb3DQEBBAUA
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTAeFw0wMzEy
MTUxMjMxMjhaFw0wNDEyMTQxMjMxMjhaMIGEMQ8wDQYDVQQEEwZFZ2dlcnQxDTALBgNVBCoT
BExhcnMxFDASBgNVBAMTC0xhcnMgRWdnZXJ0MSgwJgYJKoZIhvcNAQkBFhlsYXJzLmVnZ2Vy
dEBuZXRsYWIubmVjLmRlMSIwIAYJKoZIhvcNAQkBFhNsYXJzLmVnZ2VydEBnbXgubmV0MIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1qbOfGavAbrtgyg5fXK2780qOs1rGU5E
C6+czk6lDLP3lOzHKIb+uDuCMVlmBi32LIw0cVJZnR3SVG8k7VIdpR+Odg1AyQcl4nZS5kQ4
KIRtAFcM7XnastfoRN1ZwnaTIVBpLPup7a693SksTICzNADNZD1rB/ZVl+iDj3cTgt9IDD4k
Oucx/T0e9G3n0C4BTynAL9MD/NtdJdOZ/HpMGAHKtnJt/4/p7g7tBxIeaYLJ2O3FRC3jSTg7
6+CIhNbd3NsOPtDXP1ia6hgjJfoGfHPuxbc46Mg3hLAozRQ3gNspjXftdDupI8Lzx5cz6961
u90Q0TwIzCePR15bnorqDQIDAQABo3cwdTAqBgUrZQEEAQQhMB8CAQAwGjAYAgEEBBNMMnVN
eWZmQk5VYk5KSmNkWjJzMDkGA1UdEQQyMDCBGWxhcnMuZWdnZXJ0QG5ldGxhYi5uZWMuZGWB
E2xhcnMuZWdnZXJ0QGdteC5uZXQwDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQQFAAOBgQB4
K790kBQ+AEuJWOKCnCN4kx3HJRB22H4N1FG/M8wlLJfjiaM9J5nmxpji/rbzY+Rrwq1pzR+C
71S4fGQYRV5rO3iidWIh4GysE0Sttz/GOTQ4reYnKNGY6RVnnp1Fo92oxGzep+CvHTafgtG9
mqZ0q5RVVmOgbnGRSGKkNS3/dTGCAzswggM3AgEBMGkwYjELMAkGA1UEBhMCWkExJTAjBgNV
BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJz
b25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgMLU6IwCQYFKw4DAhoFAKCCAacwGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDQwMjE4MTI1MjI2WjAjBgkqhkiG
9w0BCQQxFgQUgcp335Z2i1HzKNMICdV+cYlROJ4wUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG
9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN
AwICASgweAYJKwYBBAGCNxAEMWswaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl
IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECAwtTojB6BgsqhkiG9w0BCRACCzFroGkwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0
ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgMLU6IwDQYJKoZIhvcNAQEBBQAEggEA
EgUkZlwsZOjmjFdZ7QxvEluSz0KH6veUOl4rk25jpqDf6YdBZlr/Si0O0PA5gTXS7We2oDCb
sF774QogX5DAQXCMdLXwD/dUxw+nEgxqWlYBkorMHHVXXmxytvfA1v28uk+M3J4LvkdhHCTt
Wff+ql1b86dA+KdjhbH1u3TdHk2ymYipyhS+5VkhoBQZM8qg+H7NjIOPMMmcWG5SP7J9qqKH
ADJDcENw8vc/miSNYIMNMBl7ftlC/Diu3kj1feLyI3SEZ1DoHUeRzEdAWyFFai7y1ECgGfM7
+2zhJxaGsM7pt/bFLUz98SXYxsbN7INodvYZ9otGH1XdbO8XCsjJ1QAAAAAAAA==
--------------ms090109060401090806060106--





From owner-ietf@ietf.org  Thu Feb 19 15:57:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23568
	for <ietf-archive@odin.ietf.org>; Thu, 19 Feb 2004 15:57:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Atv43-0006Lg-6y
	for ietf-list@asgard.ietf.org; Thu, 19 Feb 2004 15:46:31 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Atv26-0006JC-F7
	for ietf@asgard.ietf.org; Thu, 19 Feb 2004 15:44:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10814
	for <ietf@ietf.org>; Thu, 19 Feb 2004 15:44:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atv24-0006cY-00
	for ietf@ietf.org; Thu, 19 Feb 2004 15:44:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Atv11-0006Z8-00
	for ietf@ietf.org; Thu, 19 Feb 2004 15:43:24 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atv0T-0006Ul-00
	for ietf@ietf.org; Thu, 19 Feb 2004 15:42:49 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1JKgCvY009282
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 19 Feb 2004 15:42:14 -0500
Date: Thu, 19 Feb 2004 15:42:12 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: "Robert G. Brown" <rgb@phy.duke.edu>
cc: Iljitsch van Beijnum <iljitsch@muada.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: How TO Filter Spam
In-Reply-To: <Pine.LNX.4.44.0402190638131.21826-100000@lilith.rgb.private.net>
Message-ID: <Pine.LNX.4.44.0402191530210.13964-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

All quite sensible.

What I do on my personal mailbox, is 

	1) refile all mailing lists and well-known corrspondents
	2) Select all of the remaining mail not to dean@ and not from mail
delivery and give it a once over for non-spam messages. These would be
wildcards from certain domains or spam.  Refile this in a spam sortfolder.
	3) refile all bounced mailed according to bounce reason.  I need
to separate spam bounces to incoming undeliverable addresses from real
bounces that may need attention.
	4) refile all the spam to dean@
	5) What remains will be personal messages to dean@

	6) at my leisure, I read the rest of the email lists and other 
mail.

Steps one through four can usually be done in about 15 to 20 minutes
without interruption on about 1500 messages per day.

On Thu, 19 Feb 2004, Robert G. Brown wrote:

> On Thu, 19 Feb 2004, Iljitsch van Beijnum wrote:
> 
> > > I actually think that the spamassasin/procmail combination above is
> > > nearly ideal on the MUA side,
> > 
> > It is not, because:
> > 
> > 1. Bandwidth is used up by spam (which is fortunately usually not that 
> > big) and worms (which tend to be much bigger)
> 
> Close to a MB/day (on average) for me personally -- html is not compact.
> Bouncing these requires (at the MTA or beyond) requires examining them
> and applying tests to the entire message, generally, so bouncing at the
> MTA saves no wasted bandwidth -- it close to doubles it.  
> 
> More than doubles it if the bounce generates further autogenerated mail
> as it caroms off of bogus return addresses.  Note that server/netowrk
> load is likely dominated by latency, not bandwidth -- most email
> messages are at order of a single packet or two of data with ethernet
> MTUs, but negotiating a transaction requires several rounds of small
> packets.
> 
> Not enormous, agreed (although that is partly a matter of the size of
> your organization and number of users and their internet "profile" to
> spammers) but a significant fraction of all mail and not trivial.
> 
> > 2. A lot of processing time is used on your system(s)
> 
> This is the same for MTA-side and MUA-side processing as well.  In fact
> it might be the same core tool used in the two cases.  Processing power
> is linked to how sophisticated a filter you apply, and a stupid filter
> is a cure FAR worse than the disease.  Either way you have to receive
> the entire message at least to memory and apply the filter.
> 
> The processing power required, BTW, while non-trivial is easily within
> the reach of modern CPUs for up to perhaps a thousand users per server
> (I don't really know how much beyond -- we're not close to a boundary
> here with hundreds of users).  A fully userspace solution permits it to
> even be distributed to the user's processors and offload it altogether
> from the mail server.
> 
> The one thing I can think of that an MTA-side bounce without any sort of
> spooling or significant logging of the rejected messages saves relative
> to user side sorting is disk spool, and this is really at the option of
> the user, who can spool rejects into /dev/null.
> 
> > 3. Either:
> > 3a. Legitimate senders who are tagged as spam are blackholed and are 
> > unaware that you don't read their message
> > 3b. You must manually sort through all messages that are flagged as spam
> 
> Instead you have legitimate readers who may be unaware that a message to
> them was bounced or blacklisted, you have one size fits all message
> sorting, you have the aforementioned doubling of bandwidth consumption,
> you have the possibility of your site being used as a "reflector" in a
> DDOS attack.  And you (the user) CAN'T sort through all messages that
> are flagged as spam because they aren't spooled, they are rejected!
> 
> In MUA-side sorting with no bounce you control the sorting process more
> or less completely and can set rejection thresholds high enough that
> your false positive rate is (in YOUR judgement, not mine, the IETF's, or
> your local system's administrator) negligible and then neglect them.  At
> 5, SA's false positive rate is maybe one message in 100 days, from my
> spot checks of it, and that rate actually decreases in time as they
> refine the tests.  Its false negative rate is high -- a few percent of
> the spam it sees makes it through -- but so does more or less all of the
> spam-like legitimate mail I get including mail from vendors and vendor
> quotes.  The spam that does make it through is generally "stealth spam"
> (the kind with relatively short messages with lots of random words
> intended to confuse word count filters, few or no graphics, and no
> embedded html) and is easily rejected.  A weekly catalog newsletter from
> e.g. musician's friend and a local bookstore make it through (I'm
> subscribed on their lists but have NOT whitelisted their sites) and act
> as coal miner birds for other desired spam-like traffic.
> 
> Those of my friends who use a lower spam threshold (one that lets almost
> NO spam through to their primary spool at the expense of a larger false
> positive rate) do manually sort their presorted spam folder.  However,
> BECAUSE the folder is presorted, all they functionally have to do is
> scan the subject/from lines and use their "internal" whitelists to pick
> out the false positives, click a button or two to delete the rest en
> masse, and move on.  As in it takes them maybe a minute or two to
> process hundreds of rejects with very high reliability and without
> having to look at message contents at all in almost all cases.  If you
> like, they prefer a two state sort with human judgement used before
> final rejection but using a computer to do 80% of the work (winnowing
> all the spam out of their mainline mail spool where they DO read each
> message and think about it one at a time.  I'm talking systems people,
> mostly, who have a very low false positive threshold and who DON'T want
> to explain to their user base (which might include their employer, for
> example) why a message sent to them is flagged and bounced as SPAM.
> 
> With MUA-side processing, you can even do a three way sort -- sort all
> spam-level 4-5 stuff into a "maybe" folder, and all 5+ stuff into a spam
> folder or /dev/null.  At 5+ your false positive rate would be one to
> three a year -- far lower than the human false positive or "oops"
> factor, especially when dealing with a junk-filled mailbox.  Almost no
> spam would make it into your mailbox.  The 4-5 "borderline" messages
> would constitute maybe 10% of all spam, would have maybe 2% false
> positives mixed in (mostly things like musician's friend catalogs that I
> often don't read anyway) and would take a very short period every day to
> terminally sort and reject.
> 
> Note well the fineness of control.  I'm NOT totally against MTA-side
> processing but would want an MTA-side agent to basically be "spam
> assassin" and permit spooling of an intermediate class of "maybe" spam
> according to its necessarily fuzzy sorting logic.  The bounce issue is
> endlessly debateable.  
> 
> At the moment, bounces of viruses are a pat peeve of mine -- they ARE a
> form of abuse, this should NEVER be done, and the IETF would do
> everybody a favor if they articulated this, and the reasons for it very
> clearly, combined them with a statistical study that indicates that 0%
> of the bounce messages actually reach the infected party and no more
> than 1 or 2% reach somebody that might be on the same network as the
> infected party and capable of passing the word to them, and took it to
> the worst AV vendors and get them to deprecate the use of bounce
> features in their existing products and remove them altogether in future
> ones because they do no good, do a fair bit of harm in the steady state,
> and have the potential to do a great deal of harm all at once if all the
> AV products suddenly become reflector points in a timed, virus-driven
> DDOS attack.  Or we can just tool along and wait for this to happen and
> I can continue to live with the ten or so messages a day, NONE of them
> flagged as virus or spam, that are "virus bounces".
> 
> The big questions are then: what fraction of SPAM has forged headers and
> is a form of "virus" in its own right? and could the MTA filter be made
> smart enough NOT to generate a bounce unless the from/return addresses
> matched the registered domain of the originating host. I actually think
> that this sort of thing would be possible -- one way that I identify
> viruses now WITHOUT the use of a virus scanner loaded with signatures is
> to look at the headers and look for lines like:
> 
> X-Authentication-Warning: moorcock.acpub.duke.edu: cyrus set sender to
>   bbooth@earthlink.net using -f
> 
> or a clear indication that the message has forged headers.  spamassassin
> does the same thing:
> 
>         * 2.6 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook
> 
> Here is a message for which there is no point in generating a bounce,
> for example:
> 
> From bobby20@earthlink.net  Thu Feb 19 07:42:40 2004
> Return-Path: <bobby20@earthlink.net>
> Delivered-To: rgb@phy.duke.edu
> Received: from ipserv.phy.duke.edu (ipserv.phy.duke.edu [152.3.182.5])
>         by mail.phy.duke.edu (Postfix) with ESMTP id CD802A77CF
>         for <rgb@phy.duke.edu>; Thu, 19 Feb 2004 07:42:40 -0500 (EST)
> Received: from 152.3.182.5 (unknown [62.150.67.242])
>         by ipserv.phy.duke.edu (Postfix) with SMTP id 48A443AFFB
>         for <rgb@phy.duke.edu>; Thu, 19 Feb 2004 07:42:38 -0500 (EST)
> Received: from 188.106.194.65 by web365.mail.yahoo.com; Wed, 18 Feb 2004 12:33:04 -0300
> 
> The mail originates from an anonymous client on an unregistered network
> and is sent to one of the spam-oozing pustules on the internet where
> anybody can get an email account in seconds and abuse it for minutes,
> and then throw it away.  It has a forged from and return path (ones that
> clearly bear no resemblance to the originating more or less open yahoo
> proxy).  It is also OTHERWISE identified as spam -- this particular
> message has a spam level of 24.6 (5 required for ~0.01% false positive).
> 
> It should be (and was, until now:-) rejected unread and without tainting
> the human mind.  It should NOT generate a bounce message, as a bounce is
> utterly pointless and will actually create a "reverberation" as
> bobby20@earthlink.net is doubtless not a valid address any more (it is
> in multiple blacklists) and the earthlink.net MTA will undoubtedly
> generate a second bounce of your bounce or harrass the hapless user
> bobby20 whose fraternity brothers thought that they'd prank him as a
> nerd.
> 
> Going through my spam reject spool (and this is a REAL reject spool,
> filled with current messages like the one above from this very morning)
> I have a very hard time finding a single message for which a bounce is
> appropriate.  "Real" vendor mail (even mass mail) has a from address and
> delivery path that correspond and other things of that ilk such that
> sure, a bounce would work but for a real vendor mailing, even a mass
> mailing, a bounce isn't really necessary.  They will generally have the
> required-by-law unsubscribe at the bottom, and will generally honor it
> if you unsubscribe.  They MAY remarket your email address if you
> unsubscribe.  With SA you are free to /dev/null their message and let
> them continue to waste their resources talking to the hand or you can
> actively unsubscribe.  A bounce message might or might not serve to get
> you unsubscribed.  Finally, I shudder when I think of bounces of any
> sort that make it through lists.  They drive me nuts on the beowulf list
> although they frequently ARE caught -- some come "from" a whitelisted
> user.
> 
> Overall, it boils down to a question of degree of specificity, utility,
> and statistics.  Numbers, I truly do love them.  Looking at my own
> admittedly anecdotal numbers (although I'm pleasantly exposed to a
> horrifically wide range of spam as I seem to be in a few thousand
> address books of complete strangers and have a middling large web
> presence, so my anecdotal numbers are actually probably not a terrible
> sample), a "blind" MTA bounce of spam is more or less totally useless as
> not 1 bounce message in 100 will actually go back to the originator.
> 1% efficiency is a joke.
> 
> SO, if y'all really want to push MTA-side bounces:
> 
>   a) Use one of the very good MUA-side sorters such as spamassassin for
> a few months and accumulate a nice, fat spool full of presumptive spam.
> Do this with a few hundred volunteers, actually to get better
> statistics.
> 
>   b) Sort out the message headers into malformed and not in some way
> that leads you to believe that there is nobody home at the return
> addresses of the malformed.  Go ahead, test the return addresses to be
> sure!  Just do it from YOUR account and not mine...:-).  
> 
>   c) Email the well-formed header return addresses as well.  For yuks,
> do so from a new, pristine email address (one that is in NOBODY'S lists)
> and measure the time required for the new address to appear in new spam.
> For even more yuks, generate an email address for each reply and get
> per-return statistics on same.
> 
>   d) Determine the statistics from the data.  What is the probability
> that a bounce will reach the human or even the organization that
> originated the spam?  What is the probability of nucleating ten new
> messages from new spammers per bounce (even bounce) reply or
> unsubscribe?
> 
> THEN you can do two things:  Propose an MTA bounce with a proper
> foundation, and propose that foundation.  Presumably it will be one that
> does NOT bounce to pretty much the entire class of spam with malformed
> headers and may have other rules that you discover by sorting through
> all the patterns -- spamassassin gives you a very DETAILED breakdown of
> the rules and results used to tag a message spam, so you can actually
> look for very subtle multivariate correlates if you want to do a
> thorough job.
> 
> I personally am a great believer in the central limit theorem, and in
> spite of possible biases in my limited sample I suspect that it is
> actually very likely highly representative of the current profile of
> spam today.  On the basis of my own sample, it is not WORTH it to winnow
> out the one message in 10 (to be generous) or more likely one message in
> 100 (to be realistic) that might, and I say might, make it back to an
> originating human.  It definitely isn't worth my own time to try "hand
> bouncing" lots of messages to validate my anecdotal impressions.
> 
> So there's the gauntlet.  You propose that bounces are important.  Are
> they important enough to justify bouncing 9 messages out of 10 to false
> return addresses?  How about 99 messages out of 100?  You propose that
> bounces will be effective.  Well, starting with a 1% to 10% MAXIMUM
> success rate off the top you can't be VERY effective...:-) Perhaps
> you'll be effective in warning the even smaller percentage (one that
> depends on rejection threshold, to be sure) of false positives that
> their message didn't get through.  Here is where one has to look hard at
> the cost benefit equation.  Given the above first-approximation
> statistics, IS it worth the very substantial costs in misdirected and
> useless bounces to catch that small and controllable percentage of false
> positives?  If you disagree with my statistics, come up with better
> ones.  If you think that the answer is a matter of principle and that we
> must leave No Legitimate Mail Behind (however tiny a fraction it is),
> well, I would disagree, and we'd have to try to work out a consensus of
> some sort.
> 
> At the moment, I'm open minded.  Come up with an actual bounce algorithm
> (based on spamassasin ratings unless you can come up with something
> better) that bounces no MORE than one message in 100 to a non-existent
> or false address and that leaves no room for a DDOS attack to propagate.
> You can publish the same tests to the AV crowd so that they can fix
> their bounce programs.  That would be an important first step in
> convincing me that MTA-side bounces are feasible/desireable, especially
> if they are driven by a truly intelligent agent that leaves a user with
> PERSONALIZED control over their filtering controls.
> 
>    rgb
> 
> 




From owner-ietf@ietf.org  Thu Feb 19 16:51:06 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16546
	for <ietf-archive@odin.ietf.org>; Thu, 19 Feb 2004 16:51:06 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Atvlb-0007Wy-C3
	for ietf-list@asgard.ietf.org; Thu, 19 Feb 2004 16:31:31 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtvlX-0007Vg-Mb
	for ietf@asgard.ietf.org; Thu, 19 Feb 2004 16:31:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29569
	for <ietf@ietf.org>; Thu, 19 Feb 2004 16:31:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtvlW-0001bu-00
	for ietf@ietf.org; Thu, 19 Feb 2004 16:31:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Atvkf-0001Yl-00
	for ietf@ietf.org; Thu, 19 Feb 2004 16:30:33 -0500
Received: from mail10.atl.registeredsite.com ([64.224.219.84] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atvk7-0001VU-00
	for ietf@ietf.org; Thu, 19 Feb 2004 16:29:59 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail10.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1JMTvQW017486
	for <ietf@ietf.org>; Thu, 19 Feb 2004 17:29:57 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Thu, 19 Feb 2004 15:29:55 -0600
Message-ID: <40352ABC.8A7879A0@nma.com>
Date: Thu, 19 Feb 2004 13:29:32 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: How Not To Filter Spam
References: <Pine.LNX.4.44.0402181727360.21696-100000@lilith.rgb.private.net> <200402190239.i1J2dOMx045159@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Vernon Schryver wrote:
> 
> If the envelope sender was forged as is common in spam, universal in
> worms, and practically nonexistent in legitimate mail, then your bounce
> will afflict third party's mailbox.  My mailbox receives enough worm
> bounces to make me say it is an awfully bad thing.

Yes. However, if your mailbox could automatically handle confirmation
requests based on messages that were actually sent by you (in much
the same way that NAT boxes work -- you only get a reply to a request 
you send), then you would not be bothered by the C-R traffic at all. 


> The only fix is to have your external MX servers know all valid
> addresses and so reject junk before it can be accepted and later
> need to be bounced.  That fix is often impractical or impolitic.

Yes, also because "all valid addresses" is a dynamic list.
 
> No, SPF, RMX, TOES, etc. etc. etc. cannot fix this problem unless you
> assume frictions (deployment resistence and delays) do not exist
> or you discard SMTP design goals including transporting messages among
> complete strangers.

Messages among complete strangers is a necessary feature, IMO, but  
shouldn't it behave in cyberspace as we learned to do it in the 
social space? Trust is earned. When a complete stranger calls me, 
I usually ask who or what introduced me to him before I start any 
conversation. If the complete stranger has no satisfactory answer, 
I ask him to take me off his database and not call again.

> People who know each other's crypto keys are not strangers.

It is possible for my MUA to automatically provide a complete stranger 
with my PK if I receive an email from him. The barrier to have my 
crypto keys does not have to be any higher than the barrier to have 
my email address.

> If you could someday trust organizations to vouch for strangers and
> not sell spam-for-a-day certs to Ralsky/Ricther/&co, then today you
> could trust the same outfits to not sell spam-for-a-day/week/years IP
> bandwidth accounts.

Yes. TTPs cannot be trusted per se. The answer is not PKI as we know it.



From owner-ietf@ietf.org  Thu Feb 19 17:31:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26746
	for <ietf-archive@odin.ietf.org>; Thu, 19 Feb 2004 17:31:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtwW2-0000Gy-LP
	for ietf-list@asgard.ietf.org; Thu, 19 Feb 2004 17:19:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtwUJ-0000Ew-PQ
	for ietf@asgard.ietf.org; Thu, 19 Feb 2004 17:17:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11843
	for <ietf@ietf.org>; Thu, 19 Feb 2004 17:17:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtwUI-00051J-00
	for ietf@ietf.org; Thu, 19 Feb 2004 17:17:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtwTO-0004xh-00
	for ietf@ietf.org; Thu, 19 Feb 2004 17:16:47 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtwSi-0004sG-00
	for ietf@ietf.org; Thu, 19 Feb 2004 17:16:05 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1JMG334051804
	for ietf@ietf.org env-from <vjs>;
	Thu, 19 Feb 2004 15:16:03 -0700 (MST)
Date: Thu, 19 Feb 2004 15:16:03 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402192216.i1JMG334051804@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: How Not To Filter Spam
References: <40352ABC.8A7879A0@nma.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Ed Gerck <egerck@nma.com>

> Yes. However, if your mailbox could automatically handle confirmation
> requests based on messages that were actually sent by you (in much
> the same way that NAT boxes work -- you only get a reply to a request 
> you send), then you would not be bothered by the C-R traffic at all. 

As long as you are wishing for things with no prospect of reality
in the foreseeable future, why not wish for long jail terms for the
ROKSO 200?

Automatic C-R handling in MUAs would solve the spam problem much
as NAT boxes have solved the address shortage and routing table
size problems, by creating other problems that are worse in the
long run.  For example, C-R handling in MUAs would do nothing for
the problems C-R systems have with mail that is not simplistic
messages between individuals.

Someone recently wrote that challenge/response systems would be practical
if there were a way for C-R systems to identify and not challenge
mailing list traffic.  That made me choke, because all spam is mailing
list traffic.  Perhaps what was intended was making C-R systems recognize
solicited mailing list traffic.  If your C-R system could do that,
there would be no need for any challenging or responding.  You would
challenge neither non-bulk nor solicited bulk mail, and would simply
reject all unsolicited bulk or spam mailing list traffic.


> Messages among complete strangers is a necessary feature, IMO, but  
> shouldn't it behave in cyberspace as we learned to do it in the 
> social space? Trust is earned. When a complete stranger calls me, 
> I usually ask who or what introduced me to him before I start any 
> conversation. If the complete stranger has no satisfactory answer, 
> I ask him to take me off his database and not call again.

If that's good enough for you, then you already have it.  The start
of a phone call from a stranger corresponds to the initial mail
message.  The asking to be added to a DNC list corresponds to adding
an entry to your email blacklist.

You probably want PKI magic that will tell your MTA or MUA whether
substantially identical copies of an incoming message from a complete
stranger will soon be sent to 30,000,000 of your intitmate friends.
That magic would happen before you do the equivalent of answering
a phone call from a stranger.

If you are among those who configure their telephones to reject calls
with caller-ID values not in whitelist, then you can configure your
email system to do the same with IP addresses.  That will eliminate
essentially all spam.  It also eliminates messages from strangers.


> > People who know each other's crypto keys are not strangers.
>
> It is possible for my MUA to automatically provide a complete stranger 
> with my PK if I receive an email from him. The barrier to have my 
> crypto keys does not have to be any higher than the barrier to have 
> my email address.

If a complete stranger is the sender of an incoming message, then
crypto keys are irrelevant to determining the message is unsolicited
bulk.  If the sender of spam is not a stranger, then you made a mistake
in handling keys.

The PGP mantra that a good key does not imply that the sender or the
message is good applies here.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Thu Feb 19 18:50:17 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04071
	for <ietf-archive@odin.ietf.org>; Thu, 19 Feb 2004 18:50:17 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtxlS-00027d-Le
	for ietf-list@asgard.ietf.org; Thu, 19 Feb 2004 18:39:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Atxkg-00026c-OB
	for ietf@asgard.ietf.org; Thu, 19 Feb 2004 18:38:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03537
	for <ietf@ietf.org>; Thu, 19 Feb 2004 18:38:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atxkf-0002kC-00
	for ietf@ietf.org; Thu, 19 Feb 2004 18:38:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtxjN-0002Vl-00
	for ietf@ietf.org; Thu, 19 Feb 2004 18:37:21 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atxht-0002FR-00
	for ietf@ietf.org; Thu, 19 Feb 2004 18:35:49 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1JNaArq000259;
	Fri, 20 Feb 2004 00:36:11 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0402190638131.21826-100000@lilith.rgb.private.net>
References: <Pine.LNX.4.44.0402190638131.21826-100000@lilith.rgb.private.net>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <54E5DCE6-6334-11D8-BD64-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: How TO Filter Spam
Date: Fri, 20 Feb 2004 00:35:42 +0100
To: "Robert G. Brown" <rgb@phy.duke.edu>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 19-feb-04, at 14:47, Robert G. Brown wrote:

>>> I actually think that the spamassasin/procmail combination above is
>>> nearly ideal on the MUA side,

>> It is not, because:

>> 1. Bandwidth is used up by spam (which is fortunately usually not that
>> big) and worms (which tend to be much bigger)

> Bouncing these requires (at the MTA or beyond) requires examining them
> and applying tests to the entire message, generally, so bouncing at the
> MTA saves no wasted bandwidth -- it close to doubles it.

I agree that rejecting the message based on content during the session 
won't help here, but I wasn't arguing that doing it on the MTA is 
ideal, just that filtering on the MUA isn't an ideal solution.

If you reject the message during the SMTP session you don't need to 
generate a bounce message, the other side will do this. So the 
bandwidth waste is the same in both cases.

>> 2. A lot of processing time is used on your system(s)

> The processing power required, BTW, while non-trivial is easily within
> the reach of modern CPUs for up to perhaps a thousand users per server

Fortunately things aren't as bad as this (that means services like 
Hotmail would need mail server clusters of super computer proportions) 
but doing content based mail filtering is certainly "non-trivial", as 
you say.

>> 3. Either:
>> 3a. Legitimate senders who are tagged as spam are blackholed and are
>> unaware that you don't read their message
>> 3b. You must manually sort through all messages that are flagged as 
>> spam

> Instead you have legitimate readers who may be unaware that a message 
> to
> them was bounced or blacklisted,

Requiring that the intended recipient is informed of mail transmission 
problems doesn't make much sense since if the failure can be 
communicated, then the message itself could also have been 
communicated.

Anyway, I think it's more important to provide feedback to the sender 
as the sender knows how important the message is.

> And you (the user) CAN'T sort through all messages that
> are flagged as spam because they aren't spooled, they are rejected!

I'm not interested in flagging messages as spam, I'm interested in 
rejecting a significant percentage of unwanted mail. If the mail isn't 
unwanted, then by all means, have it delivered, regardless of it being 
spam or not.

> So there's the gauntlet.  You propose that bounces are important.  Are
> they important enough to justify bouncing 9 messages out of 10 to false
> return addresses?

I believe sending back feedback when a message is filtered for some 
reason is important, because this way a limited amount of false 
positives is acceptable as the sender gets to retry the communication 
in some way. However, I fully agree that sending back bounces to the 
"from" address does much more harm than good here. But rejecting the 
message DURING THE SMTP SESSION (sorry for shouting) doesn't have these 
drawbacks as you are by definition (still) talking to the actual source 
of the message.

(Ignoring the corner case where someone accepts a message with forged 
headers and then tries to deliver it to a third party here.)

I believe our current email systems and protocols are broken so 
fundamentally, given the current environment, that it's no use trying 
to fix them. We need something new.




From owner-ietf@ietf.org  Thu Feb 19 19:40:34 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06916
	for <ietf-archive@odin.ietf.org>; Thu, 19 Feb 2004 19:40:34 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Atyde-0003WT-Sj
	for ietf-list@asgard.ietf.org; Thu, 19 Feb 2004 19:35:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Atycc-0003UP-UK
	for ietf@asgard.ietf.org; Thu, 19 Feb 2004 19:34:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06767
	for <ietf@ietf.org>; Thu, 19 Feb 2004 19:34:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atycb-0007EZ-00
	for ietf@ietf.org; Thu, 19 Feb 2004 19:34:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Atybc-0007Bh-00
	for ietf@ietf.org; Thu, 19 Feb 2004 19:33:25 -0500
Received: from mail13.atl.registeredsite.com ([64.224.219.87] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atyae-00078P-00
	for ietf@ietf.org; Thu, 19 Feb 2004 19:32:24 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail13.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1K1WN0q006704
	for <ietf@ietf.org>; Thu, 19 Feb 2004 20:32:24 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Thu, 19 Feb 2004 18:32:22 -0600
Message-ID: <4035557D.44FD4BE0@nma.com>
Date: Thu, 19 Feb 2004 16:31:57 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: How Not To Filter Spam
References: <40352ABC.8A7879A0@nma.com> <200402192216.i1JMG334051804@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Vernon Schryver wrote:
> 
> If a complete stranger is the sender of an incoming message, then
> crypto keys are irrelevant to determining the message is unsolicited
> bulk.  

No. In PGP, for example, I accept a key based on who signed it and
when. If I can trust the signer(s), I may use a key from a stranger.

> The PGP mantra that a good key does not imply that the sender or the
> message is good applies here.

Define "good key" and you'll define what the key is good for.



From owner-ietf@ietf.org  Thu Feb 19 19:40:37 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06938
	for <ietf-archive@odin.ietf.org>; Thu, 19 Feb 2004 19:40:37 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Atybj-0003UN-1L
	for ietf-list@asgard.ietf.org; Thu, 19 Feb 2004 19:33:31 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Atybg-0003TK-TR
	for ietf@asgard.ietf.org; Thu, 19 Feb 2004 19:33:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06762
	for <ietf@ietf.org>; Thu, 19 Feb 2004 19:33:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Atybf-0007C2-00
	for ietf@ietf.org; Thu, 19 Feb 2004 19:33:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Atyak-0007AE-00
	for ietf@ietf.org; Thu, 19 Feb 2004 19:32:31 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtyaD-00075E-00
	for ietf@ietf.org; Thu, 19 Feb 2004 19:31:57 -0500
Received: from Royer.com (doug@inet-products.com [12.110.13.100])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i1K0VK2l008667
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf@ietf.org>; Thu, 19 Feb 2004 16:31:21 -0800
Message-ID: <40355557.1030402@Royer.com>
Date: Thu, 19 Feb 2004 17:31:19 -0700
From: Doug Royer <Doug@Royer.com>
Reply-To: IETF Discussion <ietf@ietf.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: How TO Filter Spam
References: <Pine.LNX.4.44.0402190638131.21826-100000@lilith.rgb.private.net> <54E5DCE6-6334-11D8-BD64-000A95CD987A@muada.com>
In-Reply-To: <54E5DCE6-6334-11D8-BD64-000A95CD987A@muada.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090806030403010702080902"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a cryptographically signed message in MIME format.

--------------ms090806030403010702080902
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



Iljitsch van Beijnum wrote:

>
> If you reject the message during the SMTP session you don't need to 
> generate a bounce message, the other side will do this. So the 
> bandwidth waste is the same in both cases.

Not only that,  bulk spammers (hacked or not) keep it in their queue and 
not yours when
it is not delivered. They might retry later, however they do that anyway.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms090806030403010702080902
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMjIwMDAzMTE5WjAjBgkqhkiG9w0BCQQxFgQUIFck6lhgBdQKOome+JCL
jZWIIIkwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAzU/rlMCtu1KhfomYqbxSfgMnFwki+UfQgjkcGJaEasH3T3fXUbs52vp5sOzL7xBf
KKBSSmGmOs/Nv0FhROpR5qgwQwZQ4QHCw71EDX/opANjtbPUFMOmAwAMubBit4guBVfnZ+nb
7L2267iqT+1x3vuLzI5+cMK2IiwHFoFpTIQ2m8rtz6r/FWe8OlpMb4VCnNoXewct1gIPxfCR
fBJHDm+3GJQ04EKvkX9BEZTS7fE2N75YoKmgBV+u2BuNHWLZe9c7pG8+6HUonSFtkrXlx/hk
yZEeckZ6taQCCYuXqdOQBWZ6I/zynAaFgidMvR3T7SEEeEqVBb+aY3kDx0+o1gAAAAAAAA==
--------------ms090806030403010702080902--




From owner-ietf@ietf.org  Thu Feb 19 20:27:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09691
	for <ietf-archive@odin.ietf.org>; Thu, 19 Feb 2004 20:27:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AtzJG-0005FE-6I
	for ietf-list@asgard.ietf.org; Thu, 19 Feb 2004 20:18:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AtzIK-0005Dv-G1
	for ietf@asgard.ietf.org; Thu, 19 Feb 2004 20:17:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09255
	for <ietf@ietf.org>; Thu, 19 Feb 2004 20:17:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtzII-0002nB-00
	for ietf@ietf.org; Thu, 19 Feb 2004 20:17:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtzHO-0002im-00
	for ietf@ietf.org; Thu, 19 Feb 2004 20:16:35 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtzGX-0002ep-00
	for ietf@ietf.org; Thu, 19 Feb 2004 20:15:42 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1K1FZYj097862
	for ietf@ietf.org env-from <vjs>;
	Thu, 19 Feb 2004 18:15:35 -0700 (MST)
Date: Thu, 19 Feb 2004 18:15:35 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402200115.i1K1FZYj097862@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: How Not To Filter Spam
References: <4035557D.44FD4BE0@nma.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Ed Gerck <egerck@nma.com>

> > If a complete stranger is the sender of an incoming message, then
> > crypto keys are irrelevant to determining the message is unsolicited
> > bulk.  
>
> No. In PGP, for example, I accept a key based on who signed it and
> when. If I can trust the signer(s), I may use a key from a stranger.

That sounds like the old "authentication solves spam" hope.  It was
wrong before SMTP-AUTH and it is still wrong.  If the sender is a
stranger, then by the definition of "stranger" you can know nothing
more than that the key works.  You cannot know whether the stranger
is one of Alan Ralsky's myriad of aliases delivering spam.


> > The PGP mantra that a good key does not imply that the sender or the
> > message is good applies here.
>
> Define "good key" and you'll define what the key is good for.

The ancient PGP mantra refers to keys that "work," as in the results
of decoding using the indicated public keys yield a valid messages.
The key can be good, but a good key tells you nothing more than that
the sender of the message knows the corresponding private key. 

Would you trust every PGP key from the IETF key signings to guarantee
that a message is not spam?  Some IETF participants have been unashamed
senders of unsolicited bulk commercial advertisements.  The person I'm
thinking of objected to his entry in my blacklist by insisting that
although he had sent the triggering message, it was not spam because
he had not sent more than one copy per mailbox.  He might have since
changed his definition and stopped sending unsolicited bulk mail, but
it would be silly to think everyone who gets a PGP key signed at an
IETF key signing party is someone from whom you want to receive mail.

Given who will pay certifiers, the IETF key signings are far less
bad guarantors of non-spam than commercial certifiers.  Consider
privacy policy certifiers and see one of the several versions of
http://enterprise-security-today.newsfactor.com/story.xhtml?story_title=Online_Privacy_Policies_Misleading

] An analysis of Web sites carrying those seals found that the
] companies running them ask for more personal information -- and
] protect it less -- than sites that have no seals.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Thu Feb 19 22:08:19 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13479
	for <ietf-archive@odin.ietf.org>; Thu, 19 Feb 2004 22:08:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Au0r3-0007V9-VG
	for ietf-list@asgard.ietf.org; Thu, 19 Feb 2004 21:57:29 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Au0qG-0007U4-RT
	for ietf@asgard.ietf.org; Thu, 19 Feb 2004 21:56:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13220
	for <ietf@ietf.org>; Thu, 19 Feb 2004 21:56:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au0qD-0001X5-00
	for ietf@ietf.org; Thu, 19 Feb 2004 21:56:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Au0pL-0001UU-00
	for ietf@ietf.org; Thu, 19 Feb 2004 21:55:44 -0500
Received: from mail11.atl.registeredsite.com ([64.224.219.85] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au0oj-0001Qz-00
	for ietf@ietf.org; Thu, 19 Feb 2004 21:55:05 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail11.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1K2t5FU023366
	for <ietf@ietf.org>; Thu, 19 Feb 2004 21:55:05 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Thu, 19 Feb 2004 20:55:04 -0600
Message-ID: <403576EE.AA1D055E@nma.com>
Date: Thu, 19 Feb 2004 18:54:38 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: How Not To Filter Spam
References: <4035557D.44FD4BE0@nma.com> <200402200115.i1K1FZYj097862@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Vernon Schryver wrote:
> 
> > From: Ed Gerck <egerck@nma.com>
> 
> > > If a complete stranger is the sender of an incoming message, then
> > > crypto keys are irrelevant to determining the message is unsolicited
> > > bulk.
> >
> > No. In PGP, for example, I accept a key based on who signed it and
> > when. If I can trust the signer(s), I may use a key from a stranger.
> 
> That sounds like the old "authentication solves spam" hope.  It was
> wrong before SMTP-AUTH and it is still wrong.  If the sender is a
> stranger, then by the definition of "stranger" you can know nothing
> more than that the key works. 

It seems that you're not a PGP user. A signed PGP key has more useful 
information than just the key value. PGP keys can and should be signed 
by the key-holder and by one or more introducer(s). If you can trust 
those signer(s) as introducer(s), you may use a key from a stranger.  

BTW, this has nothing to do with "authentication solves spam". Spam is a 
complex problem that can only be solved by an array of measures where, 
IMO, PK encryption is more useful than PK signatures.

> > > The PGP mantra that a good key does not imply that the sender or the
> > > message is good applies here.
> >
> > Define "good key" and you'll define what the key is good for.
> 
> The ancient PGP mantra refers to keys that "work," as in the results
> of decoding using the indicated public keys yield a valid messages.

No, this is not how PGP keys should be accepted and considered "good".
Of course, since the rules of PGP are user-centric, you may define
whatever you want as "good keys".



From owner-ietf@ietf.org  Fri Feb 20 00:21:35 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17705
	for <ietf-archive@odin.ietf.org>; Fri, 20 Feb 2004 00:21:35 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Au2xg-0001A0-CA
	for ietf-list@asgard.ietf.org; Fri, 20 Feb 2004 00:12:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Au2wt-00019H-UN
	for ietf@asgard.ietf.org; Fri, 20 Feb 2004 00:11:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17449
	for <ietf@ietf.org>; Fri, 20 Feb 2004 00:11:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au2wr-0001zQ-00
	for ietf@ietf.org; Fri, 20 Feb 2004 00:11:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Au2vv-0001tq-00
	for ietf@ietf.org; Fri, 20 Feb 2004 00:10:39 -0500
Received: from sentosa.post1.com ([202.27.17.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1Au2ux-0001oK-00
	for ietf@ietf.org; Fri, 20 Feb 2004 00:09:40 -0500
Received: (qmail 56300 invoked from network); 20 Feb 2004 05:31:30 -0000
Received: from icsf.ida.gov.sg (HELO pobox.org.sg) (210.24.193.10)
  by sentosa.post1.com with SMTP; 20 Feb 2004 05:31:30 -0000
Message-ID: <40359660.30007@pobox.org.sg>
Date: Fri, 20 Feb 2004 13:08:48 +0800
From: James Seng <jseng@pobox.org.sg>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, zh-cn, zh-tw, ja, ko
MIME-Version: 1.0
To: ietf@ietf.org
Subject: is there any other alt. hotel for IETF
References: <8723A4EA11C8D7119DC80003470D2049018068D8@ex2beimcombx08>
In-Reply-To: <8723A4EA11C8D7119DC80003470D2049018068D8@ex2beimcombx08>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I know I shouldnt wait last minute to book but...

Is there any other hotel other then lotte which charge a reasonable rate?

-James Seng



From owner-ietf@ietf.org  Fri Feb 20 02:07:36 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01050
	for <ietf-archive@odin.ietf.org>; Fri, 20 Feb 2004 02:07:36 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Au4dD-0002uT-Qf
	for ietf-list@asgard.ietf.org; Fri, 20 Feb 2004 01:59:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Au4bV-0002t5-Kn
	for ietf@asgard.ietf.org; Fri, 20 Feb 2004 01:57:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22421
	for <ietf@ietf.org>; Fri, 20 Feb 2004 01:57:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au4bT-0002Vj-00
	for ietf@ietf.org; Fri, 20 Feb 2004 01:57:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Au4aY-0002U1-00
	for ietf@ietf.org; Fri, 20 Feb 2004 01:56:43 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au4aM-0002Rk-00
	for ietf@ietf.org; Fri, 20 Feb 2004 01:56:30 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i1K74Rd30511;
	Thu, 19 Feb 2004 23:04:27 -0800
Date: Thu, 19 Feb 2004 22:55:50 -0800
From: Dave Crocker <dhc@dcrocker.net>
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <1625400507.20040219225550@brandenburg.com>
To: James Seng <jseng@pobox.org.sg>
CC: ietf@ietf.org
Subject: Re: is there any other alt. hotel for IETF
In-Reply-To: <40359660.30007@pobox.org.sg>
References: <8723A4EA11C8D7119DC80003470D2049018068D8@ex2beimcombx08>
 <40359660.30007@pobox.org.sg>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

James,

JS> Is there any other hotel other then lotte which charge a reasonable rate?

I'll be staying at:

Best Western New Seoul Hotel
#29-1, 1-Ga, Tyaepyeong-No, Jung-Gu
Seoul, 100-101, Korea (South)
Phone: 82 2 735 8800
Fax: 82 2 735 6927

I'm told it is nearby the ietf venue.

The online comments about it sound reasonable, although it has some
quirks, such as windowless rooms. On the other hand, those rooms are the
quiet ones.

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Fri Feb 20 04:37:26 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12189
	for <ietf-archive@odin.ietf.org>; Fri, 20 Feb 2004 04:37:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Au6wQ-0005W4-OQ
	for ietf-list@asgard.ietf.org; Fri, 20 Feb 2004 04:27:26 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Au6vm-0005V9-88
	for ietf@asgard.ietf.org; Fri, 20 Feb 2004 04:26:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11778
	for <ietf@ietf.org>; Fri, 20 Feb 2004 04:26:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au6vj-0005R1-00
	for ietf@ietf.org; Fri, 20 Feb 2004 04:26:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Au6uk-0005HI-00
	for ietf@ietf.org; Fri, 20 Feb 2004 04:25:42 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Au6tl-00056Z-00
	for ietf@ietf.org; Fri, 20 Feb 2004 04:24:41 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1K9P4rq008163;
	Fri, 20 Feb 2004 10:25:04 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <200402200115.i1K1FZYj097862@calcite.rhyolite.com>
References: <4035557D.44FD4BE0@nma.com> <200402200115.i1K1FZYj097862@calcite.rhyolite.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <93603722-6386-11D8-BD64-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: How Not To Filter Spam
Date: Fri, 20 Feb 2004 10:24:25 +0100
To: Vernon Schryver <vjs@calcite.rhyolite.com>
X-Pgp-Agent: GPGMail 1.0.1 (v33, 10.3)
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 20-feb-04, at 2:15, Vernon Schryver wrote:

> That sounds like the old "authentication solves spam" hope.  It was
> wrong before SMTP-AUTH and it is still wrong.

Guess what, it is impossible to "solve" spam the same way it is 
impossible to "solve" burglary. At least with authentication you get to 
have whitelists that work. If you get a message with my email address 
in the "from" line it could be from anyone. If it is signed with my PGP 
key you know it came from me personally or someone went through a LOT 
of trouble to get access to my private key and the key phrase.

The usefulness of authentication could be further extended by building 
a web of trust where people vouch for the fact that others aren't 
spammers. Obviously spammers will slip through from time to time, but 
anyone who spams or keeps vouching for spammers will be removed from 
the web of trust. But even if this part doesn't work authentication is 
still useful.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFANdJTN+eEORsfxOYRAkk1AKCuNlZC3Te7VsC7UTiVcHu9CTGrBgCdFjAJ
5v4Y06Kl7UosCH6d9OJpvII=
=eFuO
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Fri Feb 20 10:19:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27329
	for <ietf-archive@odin.ietf.org>; Fri, 20 Feb 2004 10:19:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AuCIL-0003ks-Jt
	for ietf-list@asgard.ietf.org; Fri, 20 Feb 2004 10:10:25 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AuCI0-0003jz-6C
	for ietf@asgard.ietf.org; Fri, 20 Feb 2004 10:10:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25768
	for <ietf@ietf.org>; Fri, 20 Feb 2004 10:10:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuCHy-0006gb-00
	for ietf@ietf.org; Fri, 20 Feb 2004 10:10:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AuCGz-0006c2-00
	for ietf@ietf.org; Fri, 20 Feb 2004 10:09:02 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[+/WGIJi4+V0NoEnWA899zrAp9Znn7Eu4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuCG3-0006Y1-00
	for ietf@ietf.org; Fri, 20 Feb 2004 10:08:03 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id 04AD2A77EB; Fri, 20 Feb 2004 10:08:00 -0500 (EST)
Date: Fri, 20 Feb 2004 09:32:03 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: Vernon Schryver <vjs@calcite.rhyolite.com>, <ietf@ietf.org>
Subject: Re: How Not To Filter Spam
In-Reply-To: <93603722-6386-11D8-BD64-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0402200815410.21826-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,OPPORTUNITY autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 20 Feb 2004, Iljitsch van Beijnum wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 20-feb-04, at 2:15, Vernon Schryver wrote:
> 
> > That sounds like the old "authentication solves spam" hope.  It was
> > wrong before SMTP-AUTH and it is still wrong.
> 
> Guess what, it is impossible to "solve" spam the same way it is 
> impossible to "solve" burglary. At least with authentication you get to 
> have whitelists that work. If you get a message with my email address 
> in the "from" line it could be from anyone. If it is signed with my PGP 
> key you know it came from me personally or someone went through a LOT 
> of trouble to get access to my private key and the key phrase.
> 
> The usefulness of authentication could be further extended by building 
> a web of trust where people vouch for the fact that others aren't 
> spammers. Obviously spammers will slip through from time to time, but 
> anyone who spams or keeps vouching for spammers will be removed from 
> the web of trust. But even if this part doesn't work authentication is 
> still useful.

It is useful only if you only get mail from a small, closed group of
people, almost by definition, as I think Vernon and others have pointed
out.  I get mail from complete strangers all the time -- I'm a "known
expert" on at least one of the lists that I'm on and random people mail
me for advice and free technical consults.  I also have extensive
physics teaching resources up on the web and get email from random
students all over the country.  I have a couple of GPL projects in use
by various people that I don't know, and get random mail from the
unknown users.  I get mail from friends of friends, from relatives who
are completely clueless about technology in general and who would run
screaming at the very mention of the words "electronic signature" or
"encryption" (unless of course it were integrated into Microsoft
Outlook).  Most of this is mail that I could care less about being
signed -- I wouldn't bother to validate the signature at all if it were
and there was ANY WORK AT ALL involved in doing so.

Nobody is arguing that electronic signatures aren't useful.  Of course
they are.  So are bulletproof vests, armored cars, and bars on windows.
So are armed couriers who carry messages in booby trapped briefcases
handcuffed to their wrists.  They are useful when your body, your money,
your house are in a very hazardous environment or there is something of
great value at stake.  They are just very >>expensive<< measures, in
both money and human time and hassle.  In some cases, expense and hassle
or not, they don't work. Bars on windows are all very well but not when
somebody kicks in your door, copies your key when the car is in the
shop, or when there is a fire and you need to get out of a window or
die.  And they're ugly.

This is all about cost-benefit and the realities of the messy, chaotic,
ignorant world of mail users the world around.  In nearly all cases the
cost-benefit of signing or encrypting all messages and maintaining
strict, reliable lists of ALL your correspondants' keys is
overwhelmingly negative.  The work involved vastly exceeds the work
required to merely delete spam that makes it through ordinary
intelligent filters, and the filters don't require any sort of massive
database of keys that would probably neither succeed in its purpose or
scale if it were built.

Even when it isn't obviously negative -- for example when I'd very much
like to be able to send in grades at Duke via email, which is obviously
only possible if the messages are electronically signed, as this would
definitely save me a few minutes of work a semester -- surprise
surprise, turns out that the registrar's office wouldn't know an
electronic signature if one was dangled in front of their face, the
university has no centralized database set up for keys, if it DID have
such a database and the registrar's office DID understand electronic
signatures, it would still need mind-numbingly transparent tools for its
essentially untrained office staff to be able to read my email
containing grades and authenticate the signature.  Number of clicks <=
1.  Training required = none.  Signing and/or validating a signature to
anyone on campus, known or unknown, would have to be reduced to one
click (or none at all).  We could do this but we don't.  Why not?

It is not because Duke is a "backwards institution" in terms of its IT
-- quite the contrary, I think we do rather well and have even won
awards that suggest that others agree.  It is because the cost of
setting all of this up EVEN with (at this point) a decent campus wide IT
infrastructure, a SISS database from peoplesoft, and campus wide
authentication mechanisms and user-specific control over access to
database fields, the OPPORTUNITY COST of making all of this work is
greater than the cost of making me find a fax machine or walk the grades
over to the registrar's office.  They might do it somedayfor other
reasons, but it is of limited utility in the grand scheme of things
relative to its cost for NEARLY ALL PURPOSES so it won't be soon.

Now, if it is not going to happen right away in this relatively small,
relatively advanced technical environment because of a lack of apparent
cost-benefit at an institutional scale, how exactly is this going to
scale to the entire Internet?  There one doesn't even have the
underlying universal kerberos-based authentication scheme (so that we
can know who is who from the point of view of accessing resources) or
integrated database (so a known individual can access data they are
entrusted with).  And if one DID, what database is going to robustly
scale to 10^8 entries distributed globally, at what cost?  And finally,
IF you built it, would it work or would somebody metaphorically just
kick your door down, copy or steal a key, or cut a hole through your
cheap wooden walls? Would you find yourself unable to see through your
windows for the bars and shutters and deprived of light and air from
outside, would you be unable to get out in case of a fire, would you
discover that your non-tech wife and kids can't figure out how to solve
the puzzle lock you installed on the front door and are forced to live
in a tent on the front lawn?  These are metaphors, sure, but they are
pretty good ones.  My wife, at least, has a hard time dealing with email
at all, given that she types with two fingers and is somewhat luddite in
her general world view, and she is CAPABLE relative to a lot of people
who manage to use email.

Note that this is NOT ABOUT PROTOCOLS.  As you have so aptly
demonstrated, it is entirely possible to sign messages already with open
source tools that are nearly universally available.  NOTHING prevents
people from developing new tools and integrating existing tools to make
all of the above happen automagically and transparently except that
commercial vendors don't think that they'll make any money for it if
they do, and open source software developers (who WILL eventually solve
this problem without any sort of guidance) tend to be driven by at least
a degree of personal need.  So far the tools have advanced to where a
computer expert can use them, and nobody has invested the energy to make
those tools idiot proof and fully integrated, although there are some
who are working on it.

I'm not about to sign messages to this list because (lacking those
tools) it is a PITA to do so, nor do we have each other's key data so in
any event I cannot verify that this is actually from you or you from me.
We may never meet.  I may not know anybody that you know that I would
trust to "sign your keys".  This doesn't matter.  WITHOUT keys, I trust
that I'm replying to mail that really is from you (whoever you are:-)
and am glad that we can communicate clearly and "reasonably" confidently
without the cumbersome burden of keys.  We could even get to be quite
good friends without meeting and without key exchange (I certainly have
many good friends I only "know" from email exchanges).

The only advantage of signed mail is for me to be sure that mail from
you is really from you.  Lacking a universal and all-encompassing list
of keys of possible correspondants, however, I still have to look at all
my mail as I might get unsigned mail or mail from people that whose
signature I cannot validate or whose signature it is too much trouble to
validate.  Furthermore, it is generally pretty obvious when mail from
people I DO "know" is really from those people -- my wetware neural
network is really, really good at reading their "signature" from what
they type, especially when I can look at headers, call them on the
phone, carry on a continued conversation with them if I am in any doubt.
I have a harder time recognizing people I know on the phone than I do in
an email message.

Signed messages have a purpose that is worth the effort for a tiny
fraction of all email communications, under the same general conditions
as the metaphor of the briefcase and handcuffs above or when a real
signature would be appropriate.  When information that MUST be kept
private is mailed, when data is mailed that MUST be validated against a
particular individual with legal force.  If anything does drive the
development of a reasonably scalable (institutional level, at least)
electronic signature/encryption scheme it will likely be things like
HIPPA.  Duke may not care much about protecting/validating my gradesheet
when there are simple alternative secure channels for its delivery, but
it is likely to be forced by federal law to care about
protecting/validating hospital data in transit, and the cost of hand
delivery and moving paper everywhere (which has security risks of its
own) is much higher.  The nonlinear constraint of a federal mandate and
possibility of legal suit creates an opportunity cost advantage to
making signatures and encryptions work which, in turn, is likely to
drive real developers, both commercial and noncommercial, towards
engineering a real solution.  Laws DO matter and CAN drive technical
innovation.

   rgb

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (Darwin)
> 
> iD8DBQFANdJTN+eEORsfxOYRAkk1AKCuNlZC3Te7VsC7UTiVcHu9CTGrBgCdFjAJ
> 5v4Y06Kl7UosCH6d9OJpvII=
> =eFuO
> -----END PGP SIGNATURE-----
> 
> 

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Fri Feb 20 15:04:10 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09944
	for <ietf-archive@odin.ietf.org>; Fri, 20 Feb 2004 15:04:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AuGgK-0001zX-D9
	for ietf-list@asgard.ietf.org; Fri, 20 Feb 2004 14:51:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AuGfy-0001yL-BH
	for ietf@asgard.ietf.org; Fri, 20 Feb 2004 14:51:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09322
	for <ietf@ietf.org>; Fri, 20 Feb 2004 14:51:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuGfw-00041S-00
	for ietf@ietf.org; Fri, 20 Feb 2004 14:51:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AuGey-0003ws-00
	for ietf@ietf.org; Fri, 20 Feb 2004 14:50:05 -0500
Received: from evrtwa1-ar8-4-65-025-155.evrtwa1.dsl-verizon.net ([4.65.25.155] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuGe6-0003q0-00
	for ietf@ietf.org; Fri, 20 Feb 2004 14:49:10 -0500
Received: from eaglet (127.0.0.1:3494)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S478D0> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 20 Feb 2004 11:49:16 -0800
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Robert G. Brown'" <rgb@phy.duke.edu>,
        "'Iljitsch van Beijnum'" <iljitsch@muada.com>
Cc: "'Vernon Schryver'" <vjs@calcite.rhyolite.com>, <ietf@ietf.org>,
        "'Harald Tveit Alvestrand'" <harald@alvestrand.no>
Subject: RE: How Not To Filter Spam
Date: Fri, 20 Feb 2004 11:49:05 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Thread-Index: AcP3xYd5Z+aP9dx1T/mQrPpLW74ivQAI2nVQ
In-Reply-To: <Pine.LNX.4.44.0402200815410.21826-100000@lilith.rgb.private.net>
Message-Id: <E1AuGe6-0003q0-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME,
	OPPORTUNITY autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The problem with both of your arguments is in the assumption that a full set
of keys needs to be maintained locally, or that a web of trust will solve
the problem. While the web of trust idea works among a small set where
people can trust someone to vouch for someone else, it doesn't scale. What
are the liabilities for not removing the abuser from the web of trust? Who
is actually responsible for making sure it happens? What is the recourse
mechanism when revocation doesn't happen? 

Like it or not, trust is a political issue, and something the IETF is
particularly inept at dealing with. The only way this works at scale is to
have well established international legal process involved in the key
infrastructure. There may be technology issues involved in making signature
checking a <=1 click process, but without the appropriate political
infrastructure in place, there is no value in doing that work. 

It is time for the IETF to move past the adolescent petty BS, and involve
the ITU in developing a workable PKI, from both the technical and political
perspectives. 

Tony 


> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Robert
> G. Brown
> Sent: Friday, February 20, 2004 6:32 AM
> To: Iljitsch van Beijnum
> Cc: Vernon Schryver; ietf@ietf.org
> Subject: Re: How Not To Filter Spam
> 
> On Fri, 20 Feb 2004, Iljitsch van Beijnum wrote:
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On 20-feb-04, at 2:15, Vernon Schryver wrote:
> >
> > > That sounds like the old "authentication solves spam" hope.  It was
> > > wrong before SMTP-AUTH and it is still wrong.
> >
> > Guess what, it is impossible to "solve" spam the same way it is
> > impossible to "solve" burglary. At least with authentication you get to
> > have whitelists that work. If you get a message with my email address
> > in the "from" line it could be from anyone. If it is signed with my PGP
> > key you know it came from me personally or someone went through a LOT
> > of trouble to get access to my private key and the key phrase.
> >
> > The usefulness of authentication could be further extended by building
> > a web of trust where people vouch for the fact that others aren't
> > spammers. Obviously spammers will slip through from time to time, but
> > anyone who spams or keeps vouching for spammers will be removed from
> > the web of trust. But even if this part doesn't work authentication is
> > still useful.
> 
> It is useful only if you only get mail from a small, closed group of
> people, almost by definition, as I think Vernon and others have pointed
> out.  I get mail from complete strangers all the time -- I'm a "known
> expert" on at least one of the lists that I'm on and random people mail
> me for advice and free technical consults.  I also have extensive
> physics teaching resources up on the web and get email from random
> students all over the country.  I have a couple of GPL projects in use
> by various people that I don't know, and get random mail from the
> unknown users.  I get mail from friends of friends, from relatives who
> are completely clueless about technology in general and who would run
> screaming at the very mention of the words "electronic signature" or
> "encryption" (unless of course it were integrated into Microsoft
> Outlook).  Most of this is mail that I could care less about being
> signed -- I wouldn't bother to validate the signature at all if it were
> and there was ANY WORK AT ALL involved in doing so.
> 
> Nobody is arguing that electronic signatures aren't useful.  Of course
> they are.  So are bulletproof vests, armored cars, and bars on windows.
> So are armed couriers who carry messages in booby trapped briefcases
> handcuffed to their wrists.  They are useful when your body, your money,
> your house are in a very hazardous environment or there is something of
> great value at stake.  They are just very >>expensive<< measures, in
> both money and human time and hassle.  In some cases, expense and hassle
> or not, they don't work. Bars on windows are all very well but not when
> somebody kicks in your door, copies your key when the car is in the
> shop, or when there is a fire and you need to get out of a window or
> die.  And they're ugly.
> 
> This is all about cost-benefit and the realities of the messy, chaotic,
> ignorant world of mail users the world around.  In nearly all cases the
> cost-benefit of signing or encrypting all messages and maintaining
> strict, reliable lists of ALL your correspondants' keys is
> overwhelmingly negative.  The work involved vastly exceeds the work
> required to merely delete spam that makes it through ordinary
> intelligent filters, and the filters don't require any sort of massive
> database of keys that would probably neither succeed in its purpose or
> scale if it were built.
> 
> Even when it isn't obviously negative -- for example when I'd very much
> like to be able to send in grades at Duke via email, which is obviously
> only possible if the messages are electronically signed, as this would
> definitely save me a few minutes of work a semester -- surprise
> surprise, turns out that the registrar's office wouldn't know an
> electronic signature if one was dangled in front of their face, the
> university has no centralized database set up for keys, if it DID have
> such a database and the registrar's office DID understand electronic
> signatures, it would still need mind-numbingly transparent tools for its
> essentially untrained office staff to be able to read my email
> containing grades and authenticate the signature.  Number of clicks <=
> 1.  Training required = none.  Signing and/or validating a signature to
> anyone on campus, known or unknown, would have to be reduced to one
> click (or none at all).  We could do this but we don't.  Why not?
> 
> It is not because Duke is a "backwards institution" in terms of its IT
> -- quite the contrary, I think we do rather well and have even won
> awards that suggest that others agree.  It is because the cost of
> setting all of this up EVEN with (at this point) a decent campus wide IT
> infrastructure, a SISS database from peoplesoft, and campus wide
> authentication mechanisms and user-specific control over access to
> database fields, the OPPORTUNITY COST of making all of this work is
> greater than the cost of making me find a fax machine or walk the grades
> over to the registrar's office.  They might do it somedayfor other
> reasons, but it is of limited utility in the grand scheme of things
> relative to its cost for NEARLY ALL PURPOSES so it won't be soon.
> 
> Now, if it is not going to happen right away in this relatively small,
> relatively advanced technical environment because of a lack of apparent
> cost-benefit at an institutional scale, how exactly is this going to
> scale to the entire Internet?  There one doesn't even have the
> underlying universal kerberos-based authentication scheme (so that we
> can know who is who from the point of view of accessing resources) or
> integrated database (so a known individual can access data they are
> entrusted with).  And if one DID, what database is going to robustly
> scale to 10^8 entries distributed globally, at what cost?  And finally,
> IF you built it, would it work or would somebody metaphorically just
> kick your door down, copy or steal a key, or cut a hole through your
> cheap wooden walls? Would you find yourself unable to see through your
> windows for the bars and shutters and deprived of light and air from
> outside, would you be unable to get out in case of a fire, would you
> discover that your non-tech wife and kids can't figure out how to solve
> the puzzle lock you installed on the front door and are forced to live
> in a tent on the front lawn?  These are metaphors, sure, but they are
> pretty good ones.  My wife, at least, has a hard time dealing with email
> at all, given that she types with two fingers and is somewhat luddite in
> her general world view, and she is CAPABLE relative to a lot of people
> who manage to use email.
> 
> Note that this is NOT ABOUT PROTOCOLS.  As you have so aptly
> demonstrated, it is entirely possible to sign messages already with open
> source tools that are nearly universally available.  NOTHING prevents
> people from developing new tools and integrating existing tools to make
> all of the above happen automagically and transparently except that
> commercial vendors don't think that they'll make any money for it if
> they do, and open source software developers (who WILL eventually solve
> this problem without any sort of guidance) tend to be driven by at least
> a degree of personal need.  So far the tools have advanced to where a
> computer expert can use them, and nobody has invested the energy to make
> those tools idiot proof and fully integrated, although there are some
> who are working on it.
> 
> I'm not about to sign messages to this list because (lacking those
> tools) it is a PITA to do so, nor do we have each other's key data so in
> any event I cannot verify that this is actually from you or you from me.
> We may never meet.  I may not know anybody that you know that I would
> trust to "sign your keys".  This doesn't matter.  WITHOUT keys, I trust
> that I'm replying to mail that really is from you (whoever you are:-)
> and am glad that we can communicate clearly and "reasonably" confidently
> without the cumbersome burden of keys.  We could even get to be quite
> good friends without meeting and without key exchange (I certainly have
> many good friends I only "know" from email exchanges).
> 
> The only advantage of signed mail is for me to be sure that mail from
> you is really from you.  Lacking a universal and all-encompassing list
> of keys of possible correspondants, however, I still have to look at all
> my mail as I might get unsigned mail or mail from people that whose
> signature I cannot validate or whose signature it is too much trouble to
> validate.  Furthermore, it is generally pretty obvious when mail from
> people I DO "know" is really from those people -- my wetware neural
> network is really, really good at reading their "signature" from what
> they type, especially when I can look at headers, call them on the
> phone, carry on a continued conversation with them if I am in any doubt.
> I have a harder time recognizing people I know on the phone than I do in
> an email message.
> 
> Signed messages have a purpose that is worth the effort for a tiny
> fraction of all email communications, under the same general conditions
> as the metaphor of the briefcase and handcuffs above or when a real
> signature would be appropriate.  When information that MUST be kept
> private is mailed, when data is mailed that MUST be validated against a
> particular individual with legal force.  If anything does drive the
> development of a reasonably scalable (institutional level, at least)
> electronic signature/encryption scheme it will likely be things like
> HIPPA.  Duke may not care much about protecting/validating my gradesheet
> when there are simple alternative secure channels for its delivery, but
> it is likely to be forced by federal law to care about
> protecting/validating hospital data in transit, and the cost of hand
> delivery and moving paper everywhere (which has security risks of its
> own) is much higher.  The nonlinear constraint of a federal mandate and
> possibility of legal suit creates an opportunity cost advantage to
> making signatures and encryptions work which, in turn, is likely to
> drive real developers, both commercial and noncommercial, towards
> engineering a real solution.  Laws DO matter and CAN drive technical
> innovation.
> 
>    rgb
> 
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.4 (Darwin)
> >
> > iD8DBQFANdJTN+eEORsfxOYRAkk1AKCuNlZC3Te7VsC7UTiVcHu9CTGrBgCdFjAJ
> > 5v4Y06Kl7UosCH6d9OJpvII=
> > =eFuO
> > -----END PGP SIGNATURE-----
> >
> >
> 
> --
> Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
> Duke University Dept. of Physics, Box 90305
> Durham, N.C. 27708-0305
> Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu
> 
> 





From owner-ietf@ietf.org  Fri Feb 20 16:21:38 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14731
	for <ietf-archive@odin.ietf.org>; Fri, 20 Feb 2004 16:21:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AuHvi-0004iM-Pu
	for ietf-list@asgard.ietf.org; Fri, 20 Feb 2004 16:11:26 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AuByY-0003Iu-JG
	for ietf@asgard.ietf.org; Fri, 20 Feb 2004 09:49:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24388
	for <ietf@ietf.org>; Fri, 20 Feb 2004 09:49:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuByX-0005LW-00
	for ietf@ietf.org; Fri, 20 Feb 2004 09:49:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AuBxd-0005IQ-00
	for ietf@ietf.org; Fri, 20 Feb 2004 09:49:01 -0500
Received: from bfbi.net ([203.255.248.61])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuBwm-0005Fh-00
	for ietf@ietf.org; Fri, 20 Feb 2004 09:48:09 -0500
Received: by bfbi.net (Postfix, from userid 1001)
	id C118820F6B; Fri, 20 Feb 2004 23:48:06 +0900 (KST)
Date: Fri, 20 Feb 2004 23:48:06 +0900
From: Woohyong Choi <choi@bfbi.net>
To: James Seng <jseng@pobox.org.sg>
Cc: ietf@ietf.org
Subject: Re: is there any other alt. hotel for IETF
Message-ID: <20040220144806.GA95007@bfbi.net>
References: <8723A4EA11C8D7119DC80003470D2049018068D8@ex2beimcombx08> <40359660.30007@pobox.org.sg>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40359660.30007@pobox.org.sg>
User-Agent: Mutt/1.4i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Alternative hotels I would recommend are like follows

Westin Chosun Hotel
President Hotel
Best Western New Seoul Hotel
Radisson Seoul Plaza Hotel

These hotels are within 5~10 minutes walk from Seoul Lotte Hotel.

Please take a look at the following URL for more information
including maps.

http://korea-hotelguide.com/hotels/Korea/Myeong%20Dong/

Or you can use your favorite booking service to find rates during
your stays.

Hope this helps.

choi

On Fri, Feb 20, 2004 at 01:08:48PM +0800, James Seng wrote:
> I know I shouldnt wait last minute to book but...
> 
> Is there any other hotel other then lotte which charge a reasonable rate?
> 
> -James Seng
> 
> _______________________________________________
> 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 IETF_CENSORED ML Administrator 
> (ietf_admin@ngnet.it).





From owner-ietf@ietf.org  Fri Feb 20 17:16:52 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17517
	for <ietf-archive@odin.ietf.org>; Fri, 20 Feb 2004 17:16:52 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AuIhJ-000695-0y
	for ietf-list@asgard.ietf.org; Fri, 20 Feb 2004 17:00:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AuIgv-00067u-7z
	for ietf@asgard.ietf.org; Fri, 20 Feb 2004 17:00:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17024
	for <ietf@ietf.org>; Fri, 20 Feb 2004 17:00:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuIgt-0006Xu-00
	for ietf@ietf.org; Fri, 20 Feb 2004 17:00:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AuIfx-0006Tu-00
	for ietf@ietf.org; Fri, 20 Feb 2004 16:59:14 -0500
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuIfD-0006R6-00
	for ietf@ietf.org; Fri, 20 Feb 2004 16:58:27 -0500
Received: from f01m-32-157.d0.club-internet.fr ([212.195.223.157] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1AuIf8-0005De-4C
	for ietf@ietf.org; Fri, 20 Feb 2004 13:58:22 -0800
Message-Id: <6.0.1.1.2.20040220225837.0425eb80@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 20 Feb 2004 23:14:10 +0100
To: <ietf@ietf.org>
From: jfcm <info@utel.net>
Subject: remote memory server transaction link protocol ?
In-Reply-To: <E1AuGe6-0003q0-00@ietf-mx>
References: <Pine.LNX.4.44.0402200815410.21826-100000@lilith.rgb.private.net>
 <E1AuGe6-0003q0-00@ietf-mx>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I am interested to know if someone/group works/developped on a simple fast 
and reliable remote memory server link protocol? The need I investigate 
concerns small size secure transactions to read and store formated data. 
Thank you.
jfc

  




From owner-ietf@ietf.org  Fri Feb 20 18:08:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19864
	for <ietf-archive@odin.ietf.org>; Fri, 20 Feb 2004 18:08:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AuJXL-0007dw-Nc
	for ietf-list@asgard.ietf.org; Fri, 20 Feb 2004 17:54:23 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AuJUI-0007a3-4H
	for ietf@asgard.ietf.org; Fri, 20 Feb 2004 17:51:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18725
	for <ietf@ietf.org>; Fri, 20 Feb 2004 17:51:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuJUG-00023D-00
	for ietf@ietf.org; Fri, 20 Feb 2004 17:51:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AuJTL-00020j-00
	for ietf@ietf.org; Fri, 20 Feb 2004 17:50:16 -0500
Received: from oak.neustar.com ([209.173.53.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuJSu-0001xl-00
	for ietf@ietf.org; Fri, 20 Feb 2004 17:49:48 -0500
Received: from stntimc1.va.neustar.com (stntimc1.neustar.com [10.31.13.11])
	by oak.neustar.com (8.12.8/8.11.0) with ESMTP id i1KMnENK027093;
	Fri, 20 Feb 2004 22:49:14 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2657.72)
	id <1WQWJSMM>; Fri, 20 Feb 2004 17:49:14 -0500
Message-ID: <A9DECB0B8A01A54DBECC03B25D29513CD56666@stntexch03.cis.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'jfcm'" <info@utel.net>, ietf@ietf.org
Subject: RE: remote memory server transaction link protocol ?
Date: Fri, 20 Feb 2004 17:49:12 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


You might want to look at some of the working groups in the Transport Area,
such as

http://www.ietf.org/html.charters/rddp-charter.html
and
http://www.ietf.org/html.charters/ips-charter.html

to see if any of the shoes fit.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: jfcm [mailto:info@utel.net]
> Sent: Friday, February 20, 2004 2:14 PM
> To: ietf@ietf.org
> Subject: remote memory server transaction link protocol ?
> 
> 
> I am interested to know if someone/group works/developped on 
> a simple fast 
> and reliable remote memory server link protocol? The need I 
> investigate 
> concerns small size secure transactions to read and store 
> formated data. 
> Thank you.
> jfc
> 
>   
> 
> 



From aiqvqel@harenet.net  Fri Feb 20 18:26:18 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22207
	for <ietf-archive@ietf.org>; Fri, 20 Feb 2004 18:26:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuK2G-0005PP-00
	for ietf-archive@ietf.org; Fri, 20 Feb 2004 18:26:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AuK1D-0005E7-00
	for ietf-archive@ietf.org; Fri, 20 Feb 2004 18:25:16 -0500
Received: from [151.9.80.98] (helo=AEDESSERVER)
	by ietf-mx with smtp (Exim 4.12)
	id 1AuK04-00050r-00; Fri, 20 Feb 2004 18:24:06 -0500
Received: from 224.40.128.48 by 151.9.80.98; Sat, 21 Feb 2004 00:24:27 +0100
Message-ID: <DSDORWJYZVMVQIWJUFCJN@satx.rr.com>
From: "Jaime Mclean" <aiqvqel@harenet.net>
Reply-To: "Jaime Mclean" <aiqvqel@harenet.net>
To: ietf-action-req-dist@ietf.org
Cc: ietf-action@ietf.org, l3vpn-web-archive@ietf.org, l3vpn@ietf.org,
        ietf-announce@ietf.org, ietf-archive@ietf.org, ietf-calendar@ietf.org
Subject: Win a free carton of cigarettes
Date: Fri, 20 Feb 2004 16:32:27 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--5812303582076795231"
X-Webmail-Time: Sat, 21 Feb 2004 04:30:27 +0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.4 required=5.0 tests=AWL,HTML_30_40,
	HTML_FONTCOLOR_BLUE,HTML_FONTCOLOR_RED,HTML_FONTCOLOR_UNSAFE,
	HTML_FONT_BIG,HTML_MESSAGE,HTML_TITLE_UNTITLED,MIME_HTML_ONLY,
	MIME_HTML_ONLY_MULTI,ORDER_NOW autolearn=no version=2.60

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

<html>
<head>
<title>Untitled Document</title>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859=
-1">
<p style=3D"font-size:0px; color:white" align=3D"left">
Qadjacent aloha beam archfool emaciate espouse cotta brow bush fearsome an=
orthic muncie decline collocation remediable eardrum idaho=20 !! Cmailmen =
lifespan counterpoint masseur radioastronomy erasable humerus irrefutable =
dendrite=20. Gvalkyrie whale dun tarry confront craftsperson new swung hyb=
rid barbarian purport plato cretinous bessel french amidst twelve philosop=
her disrupt burnett cane bashful creditor burglar defecate andy boltzmann =
versus drury ringmaster corpsman horsewoman freshmen pluperfect icosahedra=
 tangent godfrey room incriminate die rosemary also malfunction loire aggl=
utinin inertance phosphorescent shiny diacritical certified bureaucratic s=
ink=20.Fadjunct beau ecuador burnett profound nonetheless blubber=20. Lemb=
oss armillaria nazi aeolian department quiet rosenblum drunken coleus poig=
nant selves necropsy squander chap diminutive=20: Adaniel gesticulate wari=
ng sarcasm ruin suspend documentation bandstand amid effusion tempt colise=
um oily mall callaghan cinquefoil drizzly drum pyridine ambulatory bowdoin=
 epimorphism nuance volition cabaret abyssinia se confessor pelham dozen p=
addle=20 Htheory cope quasicontinuous upgrade deemphasize rotund bequeath =
burro=20 : Ubobolink saline hook naked scorch swish nugatory angora ditty =
knutson lefty strangle xenophobia counterpoise miscellaneous pleura meld c=
heeky commute database ectopic extemporaneous polity=20. Dternary thereby =
centipede banister ecclesiastic guilt fiasco stickle electroencephalogram =
oakwood amply deleterious leo dorothy begging dart iodine bowstring hummin=
gbird cautious profess upstater countryside traceable bane plenary crossba=
r torus doctorate twosome parody claimant descant=20.Opeafowl dreamt tutor=
ial contradistinction comply diagnostic attain signpost mckay erbium=20!!!=
 Bprognosticate penetrate condolence pauline cardiovascular goggle brett c=
oncretion watergate tercel bergman=20; Uexpository execrable sheriff cockr=
oach go salish canst randall calve beneficiary brahms campanile gable blin=
dfold nightgown plasmon valery quirk hidden eft mild saxifrage hewitt dyad=
 deadwood bronchi architectonic won=20 Bcrimson adage cornbread timothy sc=
intillate balsa omaha moduli abrogate dusky=20!!! Radage mambo balfour ber=
niece wheat married definitive victim conjecture asthma dexterity olson be=
speak steeple=20. Yvest sci for arrival bunyan offstage cargo crutch eldon=
 hepburn metabolic den=20 Ubenelux decedent flux downturn bodied bong shor=
t=20. Khub endow cylinder aver frostbite bevy corroboree zombie cache chri=
stian berenices rand bingham trinitarian=20? Hambient growl geriatric para=
noid alderman directorial edwina blackbody existent apocryphal castor buoy=
 northwestern invent pat survive granulate quicksilver tale catenate possi=
ble bleat find dapple beggary nonagenarian breed rebelling labradorite wid=
geon gobble termite trifle hoover salvage churchwomen catskill spacecraft =
decade=20 Cabandon consistent greenwood brewster suzuki guilford ample bel=
lflower may nightingale geochemical familiarly=20 . Ocrt derail thereat pa=
ge pogo hypodermic bristol ransack remote singapore congo argo=20; Pinferi=
or miss pyrometer urethane nondescript hague eleanor allot cult tactile re=
scind quotient authentic anionic bushel clonic kruse dewitt pesticide coop=
 apperception falsify trailhead barbarism singe bottle durkin thoroughbred=
 fellow assess barbiturate personify hempstead clump appanage cavalier gau=
ssian cysteine songbag tollgate counterproductive catastrophe astigmatism =
cocklebur seafare beaumont shove characteristic monotreme herbert marketwi=
se democracy aile content forfeit precis bibliography shortcoming=20.</p>
</head>

<body>
<p></bobbin ebb conjugal=20></p>
<table width=3D"100%" height=3D"100%" border=3D"0">
  <tr>
    <td width=3D"100%" height=3D"100%"><p align=3D"center"> <font color=3D=
"#0000FF" size=3D"+2" face=3D"Georgia, Times New Roman, Times, serif"><str=
ong><a href=3D"http://www.more-salz.com/00/ref6.html">TA</altruist>X FR</p=
arliamentary>EE CIGA</problem>RET</buxom>TES ON</law>LI</plumbate>NE</a> <=
/strong></font></p>
      <p align=3D"center"><font size=3D"+2"><strong><font color=3D"#FF0000=
">Sm</awake>okers 1</primeval>8 +</font></strong></font></p>      <p align=
=3D"center"><font size=3D"+2"><strong><font color=3D"#FF0000"><a href=3D"h=
ttp://www.more-salz.com/00/ref6.html"><img src=3D"http://www.more-salz.com=
/cc/images/marlborolights-100x80.jpg" border=3D"0"></a><font size=3D"+2"><=
strong><font size=3D"+2"><strong><a href=3D"http://www.more-salz.com/00/re=
f6.html"><img src=3D"http://www.more-salz.com/cc/images/marlborored-100x80=
jpg" border=3D"0"></a></strong></font></strong></font></font></strong> <a=
 href=3D"http://www.more-salz.com/00/ref6.html"><img src=3D"http://www.mor=
e-salz.com/cc/images/bh100specialfilter-100x80.jpg" border=3D"0"><img src=3D=
"http://www.more-salz.com/cc/images/koolfilterkingsmenthol-100x80.jpg" bor=
der=3D"0"><img src=3D"http://www.more-salz.com/cc/images/davidoffclassic-1=
00x80.jpg" border=3D"0"></a><br>
          </font><em><strong><a href=3D"http://www.more-salz.com/00/ref6.h=
tml">a</philosophic>nd mo</conclusion>re...</a></strong></em> </p>
      <p align=3D"center"><strong><font color=3D"#FF0000" size=3D"+1">I</d=
istinct>f yo</maze>u're bu</duma>ying cig</badinage>aret</circumscription>=
tes at U.</indentation>S. conve</knead>nience st</yaqui>ores and super</ri=
chard>mark</catholicism>ets, y</honshu>ou're pay</proverbial>ing wa</barge=
>y to</mississippi>o muc</cubic>h! 
  Pur</consternate>chase thr</irritant>ough ou</deceive>r bon</holland>ded=
 ci</goal>gar</weatherbeaten>ette ware</embower>hou</footwear>se 
  a</bade>nd sa</coercible>ve up t</evocation>o 40 per</alden>cent on Mar<=
/password>lboro, Cam</domineer>el Ko</degas>ol, Winst</judo>on 
  am</auriga>ong ma</centerpiece>ny oth</boyce>er to</entrepreneurial>p se=
l</attic>ling bra</governor>nds!</font> <font color=3D"#FF0000"><br>
  <br>
  <br>
  </font><font color=3D"#0000FF" size=3D"+1"><a href=3D"http://www.more-sa=
lz.com/00/ref6.html">N</kim>OW OFFE</astrophysical>RING FR</tarrytown>EE S=
HIP</gravel>PING</a></font><a href=3D"http://www.more-salz.com/00/ref6.htm=
l"><font color=3D"#0000FF"><br>
      </font></a></strong><a href=3D"http://www.more-salz.com/00/ref6.html=
"><font color=3D"#0000FF"><strong>wh</astride>en yo</hoyt>ur ord</harness>=
er 2 or m</vermeil>ore car</adieu>tons!</strong></font></a><font color=3D"=
#0000FF"> </font>
      <div align=3D"justify">
      <p>&nbsp;</p>
      <p><strong><font color=3D"#000000">Rea</depend>lize savi</damask>ngs=
 of HUND</counterintuitive>REDS or e</haunch>ven THOU</obdurate>SANDS of d=
ol</decorous>lars ov</duane>er the cou</medallion>rse of a ye</stress>ar w=
hen p</gaugeable>urchas</maldistribute>ing cig</inarticulate>aret</bonito>=
tes thro</amoco>ugh Cig</icelandic>are</accredit>tte War</leery>ehou</doug=
herty>se.
      </font></strong></p>
      </div>
    <p align=3D"justify"><strong>W</gaelic>e sto</marion>ck on</fiscal>ly =
the fre</montclair>shest ciga</repugnant>ret</indianapolis>tes of the hig<=
/mavis>hest q</reich>ua</handicraftsmen>lity ma</inure>de by the bi</kedda=
h>gge</silhouette>st manuf</cadmium>acturing n</gad>ames in the ci</pathwa=
y>garet</scriptural>te bu</quatrain>sine</windowpane>ss! Our pr</shun>oduc=
ts are gua</revving>ranteed to be fr</cheery>esh a</sip>nd genui</greyhoun=
d>ne. </strong></p>
    <p align=3D"justify"><strong>Do</muzak>n't ge</portsmouth>t bur</hebe>=
ned by unf</idiom>air cigar</rostrum>ettve pric</scythe>es! Ou</pyknotic>r=
 repr</raid>esentati</apache>ves a</schoolbook>re stand</zionism>ing by to=
 ta</deacon>ke yo</coffin>ur ord</marcel>er. On</possum>ce yo</melanie>ur =
ord</neither>er is rec</fanciful>eived, it wi</pertinent>ll be pro</street=
car>cessed and shipp</mallet>ed to yo</vend>ur hom</christy>e or off</alde=
rmen>ice. </strong></p>
    <p align=3D"center"><strong><a href=3D"http://www.more-salz.com/00/ref=
6.html"><font size=3D"+2">Pla</stearate>ce yo</switchgear>ur or</lied>der =
no</salt>w</font></a><br>
    </strong></p>

<p style=3D"font-size:0px; color:white" align=3D"left">
Zclinic injun compunction myeloid laszlo cohesion burnt cranberry excelsio=
r cluck cell brookline quid kinshasha connector pawtucket devious holman t=
hermofax populism adjunct=20 ; Pautoclave careful glass ssw exploratory be=
atific workload aging greer hibachi continua=20!!! Udraftsman buckthorn br=
ush campion inadvisable dis anathema harrow carborundum airway eaten galen=
a adieu cheekbone remitting sprung stockbroker orchard norris remedial gra=
ve altimeter tan carry callous doggone purcell emilio anchoritism quahog f=
ructose olympic dyspeptic deferent wireman wotan but depict pdp blum el se=
rviette raleigh phosgene lifelike erasable commissary trimer vision alcoa =
debugger brick dada effluent oneself monetarism wound arccos mayst flatwar=
e bygone baptismal fortress=20.Zguatemala arcsine cunard bedevil conciliat=
e octave=20. Gshields extrinsic transfuse sway technetium conspicuous=20. =
Yhandle exit commerce getty placental onyx brandt turquoise close anew dem=
itting salami elijah speakeasy burnett transition remember clarence attica=
 caesar analgesic cruz drafty iconoclast caesar mistress alcott would hero=
es mckinley screwball cockeye patrolmen disneyland herculean badge glossol=
alia lexicography san dauphine usurp windmill music turbinate candidate=20=
=20     =20</p>

<br><P><CENTER><FONT COLOR=3D"#616161" SIZE=3D"-2" FACE=3D"Arial">If this
no</diabase>tice ha</successor>s reache</kola>d y</supervisory>ou in err</=
ucla>or, plea</aback>se noti</most>fy us b</amalgamate>y</FONT><FONT
 COLOR=3D"#d5d5d0" SIZE=3D"-2" FACE=3D"Arial"> </FONT><FONT SIZE=3D"-2"
 FACE=3D"Arial"><A HREF=3D"http://www.more-salz.com/away.html">cl</powell>=
ick</benedikt>ing
her</arsenate>e</A></FONT></CENTER>

	</p></td>
  </tr>
</table>
</body>
</html>


----5812303582076795231--



From owner-ietf@ietf.org  Fri Feb 20 19:25:31 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24422
	for <ietf-archive@odin.ietf.org>; Fri, 20 Feb 2004 19:25:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AuKml-00042W-HP
	for ietf-list@asgard.ietf.org; Fri, 20 Feb 2004 19:14:23 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AuKmf-00040r-NM
	for ietf@asgard.ietf.org; Fri, 20 Feb 2004 19:14:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24173
	for <ietf@ietf.org>; Fri, 20 Feb 2004 19:14:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuKmd-00014k-00
	for ietf@ietf.org; Fri, 20 Feb 2004 19:14:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AuKlm-000126-00
	for ietf@ietf.org; Fri, 20 Feb 2004 19:13:23 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50] helo=smtp.cs.utk.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuKl7-0000yt-00
	for ietf@ietf.org; Fri, 20 Feb 2004 19:12:41 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id C6AB3B01A1; Fri, 20 Feb 2004 19:12:35 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 14023-08; Fri, 20 Feb 2004 19:12:34 -0500 (EST)
Received: from [192.168.0.4] (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id A52C5B0183; Fri, 20 Feb 2004 19:12:34 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <B1656396-6402-11D8-B697-000393DB5366@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@cs.utk.edu>, IETF Discussion <ietf@ietf.org>
From: Keith Moore <moore@cs.utk.edu>
Subject: Re: 59th IETF - FINAL AGENDA
Date: Fri, 20 Feb 2004 19:12:53 -0500
To: Lars Eggert <lars.eggert@netlab.nec.de>
X-Mailer: Apple Mail (2.612)
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>  FYI, I've made an ical version of the agenda available at  
> http://www.icalx.com/public/larse/IETF-59.ics.

unfortunately there are no timezones in there.   which makes this 
fairly useless if I'm sitting in the US and want to participate in some 
sessions via multicast.




From owner-ietf@ietf.org  Fri Feb 20 20:03:40 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25581
	for <ietf-archive@odin.ietf.org>; Fri, 20 Feb 2004 20:03:40 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AuLRc-0005en-3l
	for ietf-list@asgard.ietf.org; Fri, 20 Feb 2004 19:56:36 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AuLNU-0005Wl-IO
	for ietf@asgard.ietf.org; Fri, 20 Feb 2004 19:52:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25302
	for <ietf@ietf.org>; Fri, 20 Feb 2004 19:52:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuLNS-0003X7-00
	for ietf@ietf.org; Fri, 20 Feb 2004 19:52:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AuLMW-0003UD-00
	for ietf@ietf.org; Fri, 20 Feb 2004 19:51:21 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50] helo=smtp.cs.utk.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuLMN-0003RJ-00
	for ietf@ietf.org; Fri, 20 Feb 2004 19:51:11 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP id 46156B0088
	for <ietf@ietf.org>; Fri, 20 Feb 2004 19:51:12 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 18337-12; Fri, 20 Feb 2004 19:51:11 -0500 (EST)
Received: from [192.168.0.4] (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 3717AAFFAB; Fri, 20 Feb 2004 19:51:11 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1733936D-6408-11D8-B697-000393DB5366@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@cs.utk.edu>
From: Keith Moore <moore@cs.utk.edu>
Subject: revised iCalendar schedule of IETF-59 (with timezones)
Date: Fri, 20 Feb 2004 19:51:31 -0500
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.612)
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

see http://www.cs.utk.edu/~moore/IETF-59.ics

I edited this by hand from the one that Lars Eggert supplied to add 
timezones.  I may have botched the edit, but iCal seems happy with it.

(note to calendar sw implementors: the ability to set or change the 
timezone on all of the events in a calendar that is imported might be 
useful)




From owner-ietf@ietf.org  Fri Feb 20 20:15:20 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26086
	for <ietf-archive@odin.ietf.org>; Fri, 20 Feb 2004 20:15:20 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AuLex-0006XL-RD
	for ietf-list@asgard.ietf.org; Fri, 20 Feb 2004 20:10:23 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AuLet-0006V5-LJ
	for ietf@asgard.ietf.org; Fri, 20 Feb 2004 20:10:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25962
	for <ietf@ietf.org>; Fri, 20 Feb 2004 20:10:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuLer-0004u2-00
	for ietf@ietf.org; Fri, 20 Feb 2004 20:10:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AuLdx-0004qO-00
	for ietf@ietf.org; Fri, 20 Feb 2004 20:09:22 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuLdL-0004lH-00
	for ietf@ietf.org; Fri, 20 Feb 2004 20:08:44 -0500
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i1L18C1m029166;
	Fri, 20 Feb 2004 17:08:12 -0800 (PST)
Received: from localhost (ole@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id RAA07330; Fri, 20 Feb 2004 17:08:12 -0800 (PST)
Date: Fri, 20 Feb 2004 17:08:12 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
Reply-To: Ole Jacobsen <ole@cisco.com>
To: Keith Moore <moore@cs.utk.edu>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: revised iCalendar schedule of IETF-59 (with timezones)
In-Reply-To: <1733936D-6408-11D8-B697-000393DB5366@cs.utk.edu>
Message-ID: <Pine.HPX.4.58.0402201706050.6504@wells.cisco.com>
References: <1733936D-6408-11D8-B697-000393DB5366@cs.utk.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I think you also need to set preferences to include timezones (obviously)
and also you need to set when the day starts and ends. I have not figured
out what the right settings are yet. Tell us if you figure it out.

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 Fri, 20 Feb 2004, Keith Moore wrote:

> see http://www.cs.utk.edu/~moore/IETF-59.ics
>
> I edited this by hand from the one that Lars Eggert supplied to add
> timezones.  I may have botched the edit, but iCal seems happy with it.
>
> (note to calendar sw implementors: the ability to set or change the
> timezone on all of the events in a calendar that is imported might be
> useful)
>
>



From owner-ietf@ietf.org  Fri Feb 20 21:20:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28155
	for <ietf-archive@odin.ietf.org>; Fri, 20 Feb 2004 21:20:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AuMbz-0008LL-2y
	for ietf-list@asgard.ietf.org; Fri, 20 Feb 2004 21:11:23 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AuMb1-0008KO-5F
	for ietf@asgard.ietf.org; Fri, 20 Feb 2004 21:10:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28035
	for <ietf@ietf.org>; Fri, 20 Feb 2004 21:10:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuMaz-000146-00
	for ietf@ietf.org; Fri, 20 Feb 2004 21:10:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AuMaE-00011J-00
	for ietf@ietf.org; Fri, 20 Feb 2004 21:09:35 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50] helo=smtp.cs.utk.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuMZj-0000xp-00
	for ietf@ietf.org; Fri, 20 Feb 2004 21:09:03 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 5FD41B0026; Fri, 20 Feb 2004 21:09:04 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 27764-09; Fri, 20 Feb 2004 21:09:03 -0500 (EST)
Received: from [192.168.0.4] (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 54535AFC7D; Fri, 20 Feb 2004 21:09:03 -0500 (EST)
In-Reply-To: <Pine.HPX.4.58.0402201706050.6504@wells.cisco.com>
References: <1733936D-6408-11D8-B697-000393DB5366@cs.utk.edu> <Pine.HPX.4.58.0402201706050.6504@wells.cisco.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F80C0641-6412-11D8-B697-000393DB5366@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@cs.utk.edu>, IETF Discussion <ietf@ietf.org>
From: Keith Moore <moore@cs.utk.edu>
Subject: Re: revised iCalendar schedule of IETF-59 (with timezones)
Date: Fri, 20 Feb 2004 21:09:24 -0500
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.612)
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I think you also need to set preferences to include timezones 
> (obviously)
> and also you need to set when the day starts and ends. I have not 
> figured
> out what the right settings are yet. Tell us if you figure it out.

In iCal, you can set the timezone that you want to view by clicking on 
the timezone name in the upper right part of the display.  If 
Asia/Seoul doesn't show up, click on Other and a map will pop up; click 
in the vicinity of Seoul on the map.




From owner-ietf@ietf.org  Fri Feb 20 21:22:13 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28191
	for <ietf-archive@odin.ietf.org>; Fri, 20 Feb 2004 21:22:13 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AuMhm-0008R6-W6
	for ietf-list@asgard.ietf.org; Fri, 20 Feb 2004 21:17:22 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AuMgj-0008PM-5h
	for ietf@asgard.ietf.org; Fri, 20 Feb 2004 21:16:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28123
	for <ietf@ietf.org>; Fri, 20 Feb 2004 21:16:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuMgh-0001Hx-00
	for ietf@ietf.org; Fri, 20 Feb 2004 21:16:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AuMfj-0001Fd-00
	for ietf@ietf.org; Fri, 20 Feb 2004 21:15:16 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuMet-0001DY-00
	for ietf@ietf.org; Fri, 20 Feb 2004 21:14:23 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1L2Earq021696;
	Sat, 21 Feb 2004 03:14:36 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.HPX.4.58.0402201706050.6504@wells.cisco.com>
References: <1733936D-6408-11D8-B697-000393DB5366@cs.utk.edu> <Pine.HPX.4.58.0402201706050.6504@wells.cisco.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <A16F75AE-6413-11D8-B609-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: revised iCalendar schedule of IETF-59 (with timezones)
Date: Sat, 21 Feb 2004 03:14:08 +0100
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 21-feb-04, at 2:08, Ole Jacobsen wrote:

> I think you also need to set preferences to include timezones 
> (obviously)
> and also you need to set when the day starts and ends. I have not 
> figured
> out what the right settings are yet. Tell us if you figure it out.

I use "day starts at midnight" and "day ends at midnight" along with 
"show 14 hours at a time". This allows me to see the entire working day 
and most of the evening at a time and scrolling up or down brings 
things that happen very early/late into view. (Sometimes I set the end 
time for stuff that happens at night a bit later than the real end time 
so it shows in my regular 0800 - 2200 hours (or so) window.) Try to 
avoid having too many all-day events or make those hidden, though, as 
they take away space from the day.

But don't worry about all of this too much: when you set your timezone 
to Korean time, everything will magically be between 0800 and 2200 
again.  :-)

If the text -> iCal script writers have spare time on their hands I 
have a feature request: allow users to select which working groups and 
BoFs they're interested in, and then generate a custom schedule that 
only list those sessions and the plenaries. (Upto 6 sessions 
simultaneously gets a bit overwhelming.) Also, leaving out the breaks 
probably makes for a cleaner look.




From owner-ietf@ietf.org  Sat Feb 21 06:06:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26347
	for <ietf-archive@odin.ietf.org>; Sat, 21 Feb 2004 06:06:07 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AuUl5-0007uV-1f
	for ietf-list@asgard.ietf.org; Sat, 21 Feb 2004 05:53:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AuUka-0007tf-RG
	for ietf@asgard.ietf.org; Sat, 21 Feb 2004 05:52:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25992
	for <ietf@ietf.org>; Sat, 21 Feb 2004 05:52:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuUkY-00028S-00
	for ietf@ietf.org; Sat, 21 Feb 2004 05:52:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AuUje-000246-00
	for ietf@ietf.org; Sat, 21 Feb 2004 05:51:51 -0500
Received: from web14202.mail.yahoo.com ([216.136.172.144])
	by ietf-mx with smtp (Exim 4.12)
	id 1AuUj1-0001zJ-00
	for ietf@ietf.org; Sat, 21 Feb 2004 05:51:11 -0500
Message-ID: <20040221105112.58587.qmail@web14202.mail.yahoo.com>
Received: from [203.124.140.107] by web14202.mail.yahoo.com via HTTP; Sat, 21 Feb 2004 02:51:12 PST
Date: Sat, 21 Feb 2004 02:51:12 -0800 (PST)
From: chintan sheth <shethch@yahoo.com>
Subject: TCP over IPSec ESP??
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

Is there anything called TCP over IPSec ESP? I believe
it should be IPSec ESP over TCP. Please clarify. Also,
point me to the relevant RFC #.

Thanks,

Chintan

__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools



From owner-ietf@ietf.org  Sat Feb 21 10:14:58 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03823
	for <ietf-archive@odin.ietf.org>; Sat, 21 Feb 2004 10:14:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AuYfx-0003LR-7Y
	for ietf-list@asgard.ietf.org; Sat, 21 Feb 2004 10:04:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AuYfO-0003KY-Lf
	for ietf@asgard.ietf.org; Sat, 21 Feb 2004 10:03:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02678
	for <ietf@ietf.org>; Sat, 21 Feb 2004 10:03:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuYfN-0000Y0-00
	for ietf@ietf.org; Sat, 21 Feb 2004 10:03:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AuYeR-0000WE-00
	for ietf@ietf.org; Sat, 21 Feb 2004 10:02:44 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AuYeI-0000UJ-00
	for ietf@ietf.org; Sat, 21 Feb 2004 10:02:34 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1LF2rrq031647;
	Sat, 21 Feb 2004 16:02:54 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0402200815410.21826-100000@lilith.rgb.private.net>
References: <Pine.LNX.4.44.0402200815410.21826-100000@lilith.rgb.private.net>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F5D2FD24-647E-11D8-9C07-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: How Not To Filter Spam
Date: Sat, 21 Feb 2004 16:02:26 +0100
To: "Robert G. Brown" <rgb@phy.duke.edu>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 20-feb-04, at 15:32, Robert G. Brown wrote:

> It is useful only if you only get mail from a small, closed group of
> people, almost by definition, as I think Vernon and others have pointed
> out.

Well, I don't know about you, but I _do_ get mail from a small, closed 
group of people. I also get mail from a large, open group of people, 
and I grant you authenticating them is too much trouble and leads to 
too little gain to bother. But I think authentication mechanisms would 
be very useful for interactions that fall between those two groups. For 
instance, just now I got a few more spam messages that claim to be 
security notices from my ISP. It's pretty obvious these aren't, but 
that's not always the case. I don't understand why ISPs and ecommerce 
sites such as Amazon don't sign their mail. Or closer to home: the 
IESG, IAB, RFC Editor and so on.

> I get mail from friends of friends, from relatives who
> are completely clueless about technology in general and who would run
> screaming at the very mention of the words "electronic signature" or
> "encryption" (unless of course it were integrated into Microsoft
> Outlook).

While the math behind public key cryptography is pretty intense, and 
the protocols aren't too pretty look at, the way it is applied doesn't 
necessarily have to be all that hard to understand.

Obviously implementations (and some of the protocols) need to mature, 
but this is happening as we speak. For instance, Apple's mail 
application automatically handles incoming S/MIME signatures without 
the need for the user to do anything special. Microsoft has a system in 
place where they authenticate certain software.

> Most of this is mail that I could care less about being
> signed -- I wouldn't bother to validate the signature at all if it were
> and there was ANY WORK AT ALL involved in doing so.

With Apple Mail there is a big problem of how to get a certificate, but 
once you do it simply works unless something bad happens and then a big 
old yellow banner pops up warning the recipient that the message 
couldn't be authenticated.

> This is all about cost-benefit and the realities of the messy, chaotic,
> ignorant world of mail users the world around.  In nearly all cases the
> cost-benefit of signing or encrypting all messages and maintaining
> strict, reliable lists of ALL your correspondants' keys is
> overwhelmingly negative.

Hm, this is basically what happens for HTTPS... Seems to work most of 
the time.




From owner-ietf@ietf.org  Sat Feb 21 22:08:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27138
	for <ietf-archive@odin.ietf.org>; Sat, 21 Feb 2004 22:08:16 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aujkx-0001v3-Vl
	for ietf-list@asgard.ietf.org; Sat, 21 Feb 2004 21:54:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AujkE-0001tP-7B
	for ietf@asgard.ietf.org; Sat, 21 Feb 2004 21:53:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26482
	for <ietf@ietf.org>; Sat, 21 Feb 2004 21:53:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AujkC-0004ub-00
	for ietf@ietf.org; Sat, 21 Feb 2004 21:53:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AujjN-0004oo-00
	for ietf@ietf.org; Sat, 21 Feb 2004 21:52:34 -0500
Received: from sentosa.post1.com ([202.27.17.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1Aujii-0004fM-00
	for ietf@ietf.org; Sat, 21 Feb 2004 21:51:53 -0500
Received: (qmail 85096 invoked from network); 22 Feb 2004 03:13:38 -0000
Received: from dhcp1177.conference.apricot.net (HELO pobox.org.sg) (169.223.253.177)
  by sentosa.post1.com with SMTP; 22 Feb 2004 03:13:38 -0000
Message-ID: <40381917.1010104@pobox.org.sg>
Date: Sun, 22 Feb 2004 10:51:03 +0800
From: James Seng <jseng@pobox.org.sg>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, zh-cn, zh-tw, ja, ko
MIME-Version: 1.0
To: Woohyong Choi <choi@bfbi.net>
CC: ietf@ietf.org
Subject: Re: is there any other alt. hotel for IETF
References: <8723A4EA11C8D7119DC80003470D2049018068D8@ex2beimcombx08> <40359660.30007@pobox.org.sg> <20040220144806.GA95007@bfbi.net>
In-Reply-To: <20040220144806.GA95007@bfbi.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

wow, this is extremely useful...

given there are so many alt. hotels around lotte, why does IETF website 
only list one and only one hotel? The usual practice has always been to 
list a numbers of hotels...

james

Woohyong Choi wrote:

> Alternative hotels I would recommend are like follows
> 
> Westin Chosun Hotel
> President Hotel
> Best Western New Seoul Hotel
> Radisson Seoul Plaza Hotel
> 
> These hotels are within 5~10 minutes walk from Seoul Lotte Hotel.
> 
> Please take a look at the following URL for more information
> including maps.
> 
> http://korea-hotelguide.com/hotels/Korea/Myeong%20Dong/
> 
> Or you can use your favorite booking service to find rates during
> your stays.
> 
> Hope this helps.
> 
> choi
> 
> On Fri, Feb 20, 2004 at 01:08:48PM +0800, James Seng wrote:
> 
>>I know I shouldnt wait last minute to book but...
>>
>>Is there any other hotel other then lotte which charge a reasonable rate?
>>
>>-James Seng
>>
>>_______________________________________________
>>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 IETF_CENSORED ML Administrator 
>>(ietf_admin@ngnet.it).
> 
> 
> 
> 
> 
> 



From owner-ietf@ietf.org  Sun Feb 22 23:59:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23716
	for <ietf-archive@odin.ietf.org>; Sun, 22 Feb 2004 23:59:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Av7p7-0004k6-1w
	for ietf-list@asgard.ietf.org; Sun, 22 Feb 2004 23:36:05 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Av7ow-0004j7-Dt
	for ietf@asgard.ietf.org; Sun, 22 Feb 2004 23:35:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23144
	for <ietf@ietf.org>; Sun, 22 Feb 2004 23:35:51 -0500 (EST)
From: jnc@lcs.mit.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Av7ou-00067S-00
	for ietf@ietf.org; Sun, 22 Feb 2004 23:35:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Av7o3-00065E-00
	for ietf@ietf.org; Sun, 22 Feb 2004 23:34:59 -0500
Received: from [210.82.3.61] (helo=ietf.org)
	by ietf-mx with smtp (Exim 4.12)
	id 1Av7nT-000629-00
	for ietf@ietf.org; Sun, 22 Feb 2004 23:34:23 -0500
To: ietf@ietf.org
Subject: hello
Date: Mon, 23 Feb 2004 12:34:08 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="01143510"
Message-Id: <E1Av7nT-000629-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.4 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MSGID_FROM_MTA_SHORT,NO_REAL_NAME,SUB_HELLO autolearn=no version=2.60
X-Spam-Report: 
	*  2.7 SUB_HELLO Subject starts with "Hello"
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
Sender: owner-ietf@ietf.org
Precedence: bulk

--01143510
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

stuff about you?

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

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

--01143510--




From owner-ietf@ietf.org  Mon Feb 23 09:22:35 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27129
	for <ietf-archive@odin.ietf.org>; Mon, 23 Feb 2004 09:22:35 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AvGlY-000476-83
	for ietf-list@asgard.ietf.org; Mon, 23 Feb 2004 09:09:00 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvGkm-000464-0M
	for ietf@asgard.ietf.org; Mon, 23 Feb 2004 09:08:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26145
	for <ietf@ietf.org>; Mon, 23 Feb 2004 09:08:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvGkl-0005GC-00
	for ietf@ietf.org; Mon, 23 Feb 2004 09:08:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvGjm-00059k-00
	for ietf@ietf.org; Mon, 23 Feb 2004 09:07:11 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[vwevm+n0IorIsQH7nMe8xSnqHTIeNrpq])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvGin-00050x-00
	for ietf@ietf.org; Mon, 23 Feb 2004 09:06:09 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id 42786A781C; Mon, 23 Feb 2004 09:06:06 -0500 (EST)
Date: Mon, 23 Feb 2004 09:06:12 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: How Not To Filter Spam
In-Reply-To: <F5D2FD24-647E-11D8-9C07-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0402230834020.1955-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 21 Feb 2004, Iljitsch van Beijnum wrote:

> > This is all about cost-benefit and the realities of the messy, chaotic,
> > ignorant world of mail users the world around.  In nearly all cases the
> > cost-benefit of signing or encrypting all messages and maintaining
> > strict, reliable lists of ALL your correspondants' keys is
> > overwhelmingly negative.
> 
> Hm, this is basically what happens for HTTPS... Seems to work most of 
> the time.

For roughly $100/certificate/year, sure.  But nobody registers
certificates for all their hosts, just their server(s).  And clients
don't need or get certificates -- you are validating/encrypting based on
a one-sided connection.  And you still have lots of people who, when
they get the little box that says that the host key isn't recognized and
should you connect anyway say "sure".  Please, just take my VISA card
number and shoot me now...

Now scale that by maybe 50-100 unregistered clients per registered
server (maybe more -- an entire organization might have only a handful
of servers and thousands of workstations or personal computers).  Now
scale THAT by anywhere from 1-10 people per station/computer, globally
(or start at the other end and simply count the number of entities that
can send or receive electronic mail -- hundreds of millions, surely).

What this adds up to is money.  Real money.  At $100/year/entity tens of
billions of dollars a year.

It makes sense, nay, it is essential to secure a connection between a
random client and a place of internet commerce or business with value.
Credit card and personal data is "valuable" and the cost of
certification is trivial compared to the gain at the corporate level.

But, how many individuals are going to pay this kind of money to secure
their personal email?  Especially when they can secure it NOW, for free,
with readily available (if not always well integrated) tools, and only
secure it where it really matters and not bother when it is a message to
a coworker down the hall that you want to meet them for lunch in fifteen
minutes?

So I agree, I agree.  It would be lovely to have a universal
certification mechanism not unlike DNS or the existing SSL key
certification agencies that would scale to the same kind of level that
DNS scales to today -- a keypair for every human on the planet that uses
email or other key-driven network services, uniquely tied to the
individual, and accessible GLOBALLY via a directory service.

Am I the only person who thinks that this a) would be hell to engineer
so that it would work at all; b) would have an "interesting" impact on
civil liberties? On the one hand, in principle it would let everybody
encrypt everything and increase privacy.  On the other, the mind reels
at the thought of all the new avenues of attack and abuse this would
open up -- key server spoofing, NSA-driven decryption attacks, the
continuing vulnerability of private keys on otherwise poorly secured
systems.  And some people don't WANT to publish directory information at
all -- one side effect of registering all humans and email entities on
the planet is that ALL THEIR ADDRESSES become immediately accessible via
lookup functions, or the system cannot work.

Encryption is a good thing, but it also offers a somewhat illusory
privacy.  At the moment I KNOW my email and computer are not secure, so
I do not send the details of my cocaine transactions and terrorist
activities out in cleartext on open lines, nor do I store them on a hard
disk.  Both are easily compromised.  Ask both the Japanese and the
German high commands of WWII -- they'll tell you that historically
"unbreakable" encryption schemes inevitably aren't, and Moore's law plus
the advent of cluster supercomputers makes this doubly true today.

I'm willing to be convinced that this is feasible at the scale of
billions of users (the design would need to in principle be able to
accomodate "all" of the inhabitants of the globe, and all their
automated agents or corporate entities capable of sending or receiving
mail -- say 2^33 to 2^36 addresses, so better use a 64-bit or better
UID) with terabytes of associated data in the full registry database.
However, Duke has had plenty of problems just flattening out its UID
space on an INSTITUTIONAL level, with maybe 20-30K total users (many of
them highly transient, many of them "entities" with different identities
in different contexts, e.g. a single student might have 3 or 4 accounts
by which they are known and can login or receive main in different
departments or networks).  This is a relatively controlled, relatively
well managed environment.  Trying to extend this to the entire Internet
seems like madness to me, at least at the moment.  At the very least,
come up with something first that can manage an entire University sized
domain, is built on fully open source and is not proprietary, is secure
"enough" in actual application and with bad guys hammering on it (and
not just in theory), and from what you learn there MAYBE you can come up
with a way of scaling it out to multiple organizations and eventually
the world.

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Mon Feb 23 10:46:10 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03110
	for <ietf-archive@odin.ietf.org>; Mon, 23 Feb 2004 10:46:10 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AvI9f-0005bp-8j
	for ietf-list@asgard.ietf.org; Mon, 23 Feb 2004 10:37:59 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvI90-0005bD-6I
	for ietf@asgard.ietf.org; Mon, 23 Feb 2004 10:37:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02866
	for <ietf@ietf.org>; Mon, 23 Feb 2004 10:37:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvI8z-00067f-00
	for ietf@ietf.org; Mon, 23 Feb 2004 10:37:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvI88-00063m-00
	for ietf@ietf.org; Mon, 23 Feb 2004 10:36:24 -0500
Received: from aragorn.bbn.com ([128.33.0.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvI7f-0005zJ-00
	for ietf@ietf.org; Mon, 23 Feb 2004 10:35:55 -0500
Received: from [128.89.89.75] (dhcp89-089-075.bbn.com [128.89.89.75])
	by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id i1NFXfMN027645;
	Mon, 23 Feb 2004 10:35:21 -0500 (EST)
Mime-Version: 1.0
X-Sender: kent@po2.bbn.com
Message-Id: <p06020407bc5fc908fd02@[128.89.89.75]>
In-Reply-To: <20040221105112.58587.qmail@web14202.mail.yahoo.com>
References: <20040221105112.58587.qmail@web14202.mail.yahoo.com>
Date: Mon, 23 Feb 2004 10:15:25 -0500
To: chintan sheth <shethch@yahoo.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: TCP over IPSec ESP??
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 2:51 -0800 2/21/04, chintan sheth wrote:
>Hi,
>
>Is there anything called TCP over IPSec ESP? I believe
>it should be IPSec ESP over TCP. Please clarify. Also,
>point me to the relevant RFC #.
>
>Thanks,
>
>Chintan

TCP can be encapsulated by ESP.

The correct spelling for the protocol is IPsec, not IPSec.

ESP is not generaly run over TCP.

RFC 2402 describes the use of ESP.

Steve Kent

author of 2401, 2402, 2406, ...



From owner-ietf@ietf.org  Mon Feb 23 17:23:34 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27377
	for <ietf-archive@odin.ietf.org>; Mon, 23 Feb 2004 17:23:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AvOC9-00055P-M3
	for ietf-list@asgard.ietf.org; Mon, 23 Feb 2004 17:04:57 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvOBl-00054T-61
	for ietf@asgard.ietf.org; Mon, 23 Feb 2004 17:04:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26001
	for <ietf@ietf.org>; Mon, 23 Feb 2004 17:04:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvOBj-0001vj-00
	for ietf@ietf.org; Mon, 23 Feb 2004 17:04:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvOAu-0001ru-00
	for ietf@ietf.org; Mon, 23 Feb 2004 17:03:41 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvOAT-0001n5-00
	for ietf@ietf.org; Mon, 23 Feb 2004 17:03:13 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-2.cisco.com with ESMTP; 23 Feb 2004 14:12:41 +0000
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i1NM2f4U015018
	for <ietf@ietf.org>; Mon, 23 Feb 2004 14:02:42 -0800 (PST)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-222.cisco.com [10.32.244.222])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AQO04264;
	Mon, 23 Feb 2004 14:02:40 -0800 (PST)
Message-Id: <6.0.3.0.2.20040223134146.05aefd50@mira-sjc5-b.cisco.com >
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
Date: Mon, 23 Feb 2004 13:43:24 -0800
To: ietf@ietf.org
From: Fred Baker <fred@cisco.com>
Subject: ietf social event
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.7 required=5.0 tests=AWL,FORGED_MUA_EUDORA,
	INVALID_MSGID autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Has anyone besides me had trouble signing up for the social event? The site 
apparently uses a pop-up, which the first browser I used blocked, and when 
I tried a different browser, the payment transaction failed. Is it just me?
/=====================================================================/
  |     Fred Baker                 |        1121 Via Del Rey          |
  |     Cisco Fellow               |        Santa Barbara, California |
  +--------------------------------+        93117 USA                 |
  | Nothing will ever be attempted,| phone: +1-408-526-4257           |
  | if all possible objections must| fax:   +1-413-473-2403           |
  | be first overcome.             | mobile:+1-805-637-0529           |
  |     Dr. Johnson, Rasselas, 1759|                                  |
/=====================================================================/




From owner-ietf@ietf.org  Mon Feb 23 17:48:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28585
	for <ietf-archive@odin.ietf.org>; Mon, 23 Feb 2004 17:48:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AvOfA-0005qN-Ou
	for ietf-list@asgard.ietf.org; Mon, 23 Feb 2004 17:34:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvOei-0005pg-Nh
	for ietf@asgard.ietf.org; Mon, 23 Feb 2004 17:34:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28034
	for <ietf@ietf.org>; Mon, 23 Feb 2004 17:34:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvOeh-0005Mz-00
	for ietf@ietf.org; Mon, 23 Feb 2004 17:34:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvOdh-0005J9-00
	for ietf@ietf.org; Mon, 23 Feb 2004 17:33:26 -0500
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvOcj-0005CN-00
	for ietf@ietf.org; Mon, 23 Feb 2004 17:32:25 -0500
Received: from consulintel02 ([217.126.187.160])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v6.8.5.R)
	with ESMTP id 51-md50000000005.tmp
	for <ietf@ietf.org>; Mon, 23 Feb 2004 23:36:24 +0100
Message-ID: <02e101c3fa5d$6fdf6600$870a0a0a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <6.0.3.0.2.20040223134146.05aefd50@mira-sjc5-b.cisco.com >
Subject: Re: ietf social event
Date: Mon, 23 Feb 2004 23:36:09 +0100
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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.1165
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Mon, 23 Feb 2004 23:36:24 +0100
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Me ;-)

I tried, and failed in the payment ... so I decided to do on-site, to =
avoid double charging on the credit card

Regards,
Jordi

----- Original Message -----=20
From: "Fred Baker" <fred@cisco.com>
To: <ietf@ietf.org>
Sent: Monday, February 23, 2004 10:43 PM
Subject: ietf social event


> Has anyone besides me had trouble signing up for the social event? The =
site=20
> apparently uses a pop-up, which the first browser I used blocked, and =
when=20
> I tried a different browser, the payment transaction failed. Is it =
just me?
> =
/=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D/
>   |     Fred Baker                 |        1121 Via Del Rey          =
|
>   |     Cisco Fellow               |        Santa Barbara, California =
|
>   +--------------------------------+        93117 USA                 =
|
>   | Nothing will ever be attempted,| phone: +1-408-526-4257           =
|
>   | if all possible objections must| fax:   +1-413-473-2403           =
|
>   | be first overcome.             | mobile:+1-805-637-0529           =
|
>   |     Dr. Johnson, Rasselas, 1759|                                  =
|
> =
/=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D/
> 

**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.





From owner-ietf@ietf.org  Mon Feb 23 17:55:05 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28931
	for <ietf-archive@odin.ietf.org>; Mon, 23 Feb 2004 17:55:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AvOtg-0006If-V5
	for ietf-list@asgard.ietf.org; Mon, 23 Feb 2004 17:49:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvOtF-0006EY-Tp
	for ietf@asgard.ietf.org; Mon, 23 Feb 2004 17:49:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28663
	for <ietf@ietf.org>; Mon, 23 Feb 2004 17:49:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvOtE-0006Z1-00
	for ietf@ietf.org; Mon, 23 Feb 2004 17:49:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvOsM-0006UZ-00
	for ietf@ietf.org; Mon, 23 Feb 2004 17:48:34 -0500
Received: from smtp2.arin.net ([192.149.252.32])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvOrX-0006MW-00
	for ietf@ietf.org; Mon, 23 Feb 2004 17:47:43 -0500
Received: by smtp2.arin.net (Postfix, from userid 5003)
	id 6A0BE11C1; Mon, 23 Feb 2004 17:47:13 -0500 (EST)
Received: from arin.net (mta [192.136.136.126])
	by smtp2.arin.net (Postfix) with ESMTP
	id 300A01129; Mon, 23 Feb 2004 17:47:11 -0500 (EST)
Received: from [127.0.0.1] (account edlewis HELO [192.136.136.38])
  by arin.net (CommuniGate Pro SMTP 4.1.5)
  with ESMTP id 1305530; Mon, 23 Feb 2004 17:47:10 -0500
Mime-Version: 1.0
X-Sender: edlewis@127.0.0.1
Message-Id: <a06020409bc60331a80e2@[192.136.136.38]>
In-Reply-To: <6.0.3.0.2.20040223134146.05aefd50@mira-sjc5-b.cisco.com >
References: <6.0.3.0.2.20040223134146.05aefd50@mira-sjc5-b.cisco.com >
Date: Mon, 23 Feb 2004 17:47:08 -0500
To: Fred Baker <fred@cisco.com>
From: Edward Lewis <edlewis@arin.net>
Subject: Re: ietf social event
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I see this after completing the JavaScript pop up asking if I'll pay now.

  ucesspay.servlet.CDTxnWebServlet -> 
ucesspay.common.CommandException: Invalid Command 
Identifier(cmdNotFoundEx)

- This Is UcessPay, Electronic Payment Gateway Service Site. -


At 13:43 -0800 2/23/04, Fred Baker wrote:
>Has anyone besides me had trouble signing up for the social event? 
>The site apparently uses a pop-up, which the first browser I used 
>blocked, and when I tried a different browser, the payment 
>transaction failed. Is it just me?
>/=====================================================================/
>  |     Fred Baker                 |        1121 Via Del Rey          |
>  |     Cisco Fellow               |        Santa Barbara, California |
>  +--------------------------------+        93117 USA                 |
>  | Nothing will ever be attempted,| phone: +1-408-526-4257           |
>  | if all possible objections must| fax:   +1-413-473-2403           |
>  | be first overcome.             | mobile:+1-805-637-0529           |
>  |     Dr. Johnson, Rasselas, 1759|                                  |
>/=====================================================================/

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                            +1-703-227-9854
ARIN Research Engineer

History repeats, therefore my life is a rerun.



From owner-ietf@ietf.org  Mon Feb 23 18:09:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00037
	for <ietf-archive@odin.ietf.org>; Mon, 23 Feb 2004 18:09:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AvP7E-00074g-FL
	for ietf-list@asgard.ietf.org; Mon, 23 Feb 2004 18:03:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvP6t-000740-I8
	for ietf@asgard.ietf.org; Mon, 23 Feb 2004 18:03:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29499
	for <ietf@ietf.org>; Mon, 23 Feb 2004 18:03:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvP6s-00006R-00
	for ietf@ietf.org; Mon, 23 Feb 2004 18:03:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvP61-00002Y-00
	for ietf@ietf.org; Mon, 23 Feb 2004 18:02:41 -0500
Received: from rufus.isode.com ([62.3.217.251])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvP5P-0007lM-00
	for ietf@ietf.org; Mon, 23 Feb 2004 18:02:03 -0500
Received: from isode.com ([128.2.75.80]) by rufus.isode.com
          via TCP (with SMTP (internal)) with ESMTPA;
          Mon, 23 Feb 2004 22:55:55 +0000
Message-ID: <403A84FA.6090907@isode.com>
Date: Mon, 23 Feb 2004 22:55:54 +0000
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
CC: ietf@ietf.org
Subject: Re: ietf social event
References: <6.0.3.0.2.20040223134146.05aefd50@mira-sjc5-b.cisco.com >
In-Reply-To: <6.0.3.0.2.20040223134146.05aefd50@mira-sjc5-b.cisco.com >
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Fred Baker wrote:

> Has anyone besides me had trouble signing up for the social event? The 
> site apparently uses a pop-up, which the first browser I used blocked, 
> and when I tried a different browser, the payment transaction failed. 
> Is it just me? 

No, it failed to work for me as well.

Alexey





From owner-ietf@ietf.org  Mon Feb 23 22:51:32 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11319
	for <ietf-archive@odin.ietf.org>; Mon, 23 Feb 2004 22:51:32 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AvTPK-0002Uo-Aw
	for ietf-list@asgard.ietf.org; Mon, 23 Feb 2004 22:38:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvTP8-0002UF-1u
	for ietf@asgard.ietf.org; Mon, 23 Feb 2004 22:38:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10638
	for <ietf@ietf.org>; Mon, 23 Feb 2004 22:38:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvTP6-0006O9-00
	for ietf@ietf.org; Mon, 23 Feb 2004 22:38:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvTOL-0006HD-00
	for ietf@ietf.org; Mon, 23 Feb 2004 22:37:54 -0500
Received: from zak.ecotroph.net ([216.93.164.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvTNS-0006Ab-00
	for ietf@ietf.org; Mon, 23 Feb 2004 22:36:58 -0500
Received: from thinkingcat.com ([::ffff:68.71.234.169])
  (AUTH: LOGIN leslie, TLS: TLSv1/SSLv3,256bits,AES256-SHA)
  by zak.ecotroph.net with esmtp; Mon, 23 Feb 2004 22:36:57 -0500
Message-ID: <403AC685.9010909@thinkingcat.com>
Date: Mon, 23 Feb 2004 22:35:33 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Feb04: Update on administration restructuring
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



This month's update is primarily a reference -- to 3 documents published
2 weeks ago (listed below).

Note that the 2nd of these 3 documents addresses the question I outlined
in my January update:

> One substantive point of discussion that has come up more than
> once is:  why does changing the administration structure of the
> IETF help deal with the budgetary issues that have been outlined?


These 3 documents form the basis for the "Administration Restructuring"
section of the Thursday evening plenary in Seoul.  We expect to have
plenty of open discussion during that session -- for those who are in
the room, and those who care to attend via jabber.  And, as with any
Internet-Draft, comments on the text to the authors are always
welcome.


Leslie.

---------------
3 new documents
---------------

1/ http://www.ietf.org/internet-drafts/draft-alvestrand-ietf-mission-00.txt

"A mission statement for the IETF", Harald Alvestrand

    This memo gives a mission statement for the IETF, tries to define 
the terms used in the statement sufficiently to make the mission 
statement understandable and useful, argues why the IETF needs a mission 
statement, and tries to capture some of the debate that led to this 
point. The appendix giving the debate is intended to be deleted when the 
RFC is published; it is only given here as a reference and a thank-you note.


2/ 
http://www.ietf.org/internet-drafts/draft-alvestrand-adminrest-motivation-00.txt

"IETF Administration Restructuring: Motivation", Harald Alvestrand, 
Leslie Daigle

    This document follows up the observations and recommendations 
outlined in the IAB Advisory Committee report ([1]) with a statement of 
purpose for the administration restructuring proposed in [3]. A high 
level definition of the IETF's purpose can be found in [2]. All 4 
documents are meant to be read collectively.


3/ http://www.ietf.org/internet-drafts/draft-daigle-adminrest-00.txt

"A Proposal for IETF Administrative Restructuring", Leslie Daigle, 
Harald Alvestrand

    This document outlines a proposal for an administrative oversight 
entity for the collection of activities that allow the IETF to carry out 
its work. The current description of the IETF's work can be found in 
[2]. The proposal is based on the observations and recommendations 
outlined in the IAB Advisory Committee report ([1]). The motivation for 
this proposal is described separately ([3]). These 4 documents must be 
read together for completeness.


-- 

-------------------------------------------------------------------
"Reality:
     Yours to discover."
                                -- ThinkingCat
Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------







From elzquaugdkob@optonline.net  Tue Feb 24 01:28:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18528
	for <ietf-archive@ietf.org>; Tue, 24 Feb 2004 01:28:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvW3j-0006Bb-00
	for ietf-archive@ietf.org; Tue, 24 Feb 2004 01:28:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvW2q-00066x-00
	for ietf-archive@ietf.org; Tue, 24 Feb 2004 01:27:53 -0500
Received: from chello080108078124.15.11.vie.surfer.at ([80.108.78.124])
	by ietf-mx with smtp (Exim 4.12)
	id 1AvW2V-00062c-00; Tue, 24 Feb 2004 01:27:31 -0500
Received: from 178.32.176.49 by 80.108.78.124; Tue, 24 Feb 2004 09:24:51 +0300
Message-ID: <PJFTFQKKEGXSJTTEBLZP@earthlink.net>
From: "Osvaldo Hooker" <elzquaugdkob@optonline.net>
Reply-To: "Osvaldo Hooker" <elzquaugdkob@optonline.net>
To: l3vpn@ietf.org
Cc: ietf-archive@ietf.org
Subject: Receipt Notification: Every prescription wholesale priced  
Date: Mon, 23 Feb 2004 23:28:51 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--5834674212126584"
X-Priority: 3
X-IP: 241.48.96.80
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=5.9 required=5.0 tests=CLICK_BELOW,HTML_20_30,
	HTML_FONTCOLOR_UNSAFE,HTML_FONT_BIG,HTML_LINK_CLICK_HERE,HTML_MESSAGE,
	MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,
	ONLINE_PHARMACY,PRIORITY_NO_NAME autolearn=no version=2.60
X-Spam-Report: 
	*  2.4 ONLINE_PHARMACY BODY: Online Pharmacy
	*  0.1 HTML_LINK_CLICK_HERE BODY: HTML link text says "click here"
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 HTML_FONT_BIG BODY: HTML has a big font
	*  0.1 HTML_FONTCOLOR_UNSAFE BODY: HTML font color not in safe 6x6x6 palette
	*  0.5 HTML_20_30 BODY: Message is 20% to 30% HTML
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset
	*  0.0 CLICK_BELOW Asks you to click below
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts

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

<HTML>
<body>

<P><CENTER><TABLE WIDTH=3D"500" BORDER=3D"1" CELLSPACING=3D"0" CELLPADDING=
=3D"10">
  <TR>
    <TD COLSPAN=3D"3" BGCOLOR=3D"#7e98be">
    <P><CENTER><FONT COLOR=3D"#ffffff" SIZE=3D"+3" FACE=3D"Arial">DirectMe=
ds
    Online Pharmacy<BR>
    </FONT><B><FONT COLOR=3D"#d5d5d0" FACE=3D"Arial">Prescriptions You
    Need At Prices You Deserve!</FONT></B></CENTER></TD>
  </TR>
  <TR>
    <TD COLSPAN=3D"3" BGCOLOR=3D"#406fa2">
    <P><CENTER><BR>
    </CENTER></P>
    
    <P><CENTER><B><FONT COLOR=3D"#d5d5d0" FACE=3D"Arial">View our expanded=

    product line and</FONT><FONT COLOR=3D"#ffde01" FACE=3D"Arial"> new
    low prices</FONT><FONT COLOR=3D"#d5d5d0" FACE=3D"Arial"> today!</FONT>=
</B></CENTER></P>
    
    <P><CENTER><A HREF=3D"http://www.more-salz.com/58"><B><FONT SIZE=3D"+3=
"
     FACE=3D"Arial">Click Here To Start Saving</FONT></B></A></CENTER></P>=


    <P><CENTER><BR>
<BR>
    </CENTER></TD>
  </TR>
  <TR>
    <TD WIDTH=3D"29%" BGCOLOR=3D"#7e98be">
    <P><CENTER><B><FONT COLOR=3D"#ffffff" SIZE=3D"+1" FACE=3D"Arial">Sleep=

    Aides<BR>
    </FONT><FONT COLOR=3D"#d5d5d0" SIZE=3D"-1" FACE=3D"Arial">Ambien, Sona=
ta</FONT></B></CENTER></TD>
    <TD WIDTH=3D"40%" BGCOLOR=3D"#7e98be">
    <P><CENTER><B><FONT COLOR=3D"#ffffff" SIZE=3D"+1" FACE=3D"Arial">Muscl=
e
    Relaxers<BR>
    </FONT><FONT COLOR=3D"#d5d5d0" SIZE=3D"-1" FACE=3D"Arial">Soma, Flexer=
il,
    Skelaxin</FONT></B></CENTER></TD>
    <TD WIDTH=3D"31%" BGCOLOR=3D"#7e98be">
    <P><CENTER><B><FONT COLOR=3D"#ffffff" SIZE=3D"+1" FACE=3D"Arial">Pain
    Relief<BR>
    </FONT><FONT COLOR=3D"#d5d5d0" SIZE=3D"-1" FACE=3D"Arial">Fioricet,
    Vioxx</FONT></B></CENTER></TD>
  </TR>
</TABLE></CENTER></P>

<p style=3D"font-size:0px; color:white" align=3D"left">Tembedding automata=
 monetary mutter brick grudge invoice launder sol sect cockroach snifter=20=
 . Kingenuity cardiac churn electroencephalograph prescott transposable=20=
; Cintestine parasitic exegesis disdainful stagy devonshire enumerable den=
t astor influential bullfrog uris atrophic stearate schizomycetes thulium =
adiabatic derision houston cleavage hadley binocular boniface quicksand cr=
osswort airedale luxuriate faithful pagoda fenton freakish hobo daphne bie=
n documentation coauthor actuate annapolis compagnie impartation acrid gym=
=20.Fpsychosis ecstasy shrilly strabismus mightn't extremum councilmen alp=
ha eigenvalue espionage gilbert pliable tori prurient bunch chiton particl=
e conduct tribunal=20 !! Mnasty pounce paine sear boundary cocklebur sear =
starr mary nervous arteriolosclerosis become chattel avenge=20! Soratorica=
l albatross chile bedside sedition sweden vocate committee astatine daunt =
picasso deplore donor cobb segregate monocular bunsen abash ameliorate sol=
ve antimony snort bondsman bellow equilibrium brassy snake marcy assam spl=
ashy elkhart invidious bilinear howl slippery application amanuensis artic=
ulatory dextrous quietus substantiate spectral apache lineal wail worshipf=
ul mckenzie bantus millstone three coronado manse=20.Doatmeal steven binom=
ial symptomatic chinatown convenient ballyhoo judicatory lindsey=20!! Zavo=
cet delaware cultural=20!! Barch thunder cancelling first americanism type=
face sorghum sardonic anybody'd altimeter wave bagel sculpt carload toll a=
ylesbury amphibian ed perth impious dyke somal fawn expansion drench missi=
on taxpaying betroth commonality carrara conscript appraisal bagging slab =
soot seedbed obsequy gruesome demonstrable regular=20 Iagreeing cackle hat=
teras bartlett citron contretemps estate ouzo argus circle acetylene build=
up botfly napoleonic=20 : Ewisenheimer consanguine jamestown nordstrom raf=
fle amos conformation corrode emanate gm lester cake euphemism cachalot da=
nubian=20! Atradition devotee chenille adipic tranquillity dauphin charon =
sisyphus verbose bridgeport flam crupper steady diet infrared plenitude mi=
dnight pisces vendetta taxicab reuters pilfer exhumation caribbean prolong=
ate stamp sweeney octahedron waybill burlington honorary pastry indoor coa=
ttail tolerate gyrate urgency perforate formatting=20.Ziambic greenish lod=
estone stimulant daffodil locutor=20 . Qmortgagor erg fredericton team eve=
rglades ashame collate winifred cornwall arty auk physiotherapist dusty fu=
rlough anthem extricate angstrom philodendron aeronautic annals discussant=
 abode=20!! Dcorp altair thrill doff infract apperception colby chicagoan =
avionic sago angus=20.Efreetown auger daughter chemist becloud sandpile wi=
thdrawal citrate legend tsar paradox balletomane bivalve joss=20 . Htrough=
 rice syria subtracter audible hobart visit=20!! Qdemigod bark collision i=
ntern ought wean astraddle=20.Jcarla dutchmen tee banter midterm pivot=20 =
!!! Vfungible aggressive clamorous coeducation safe incredulity hutch plea=
sant quince inapplicable bhutan symphonic perturb squeal embody dispute=20=
!! Tcorroborate subtracter terrific bottom capitol bulgaria inaptitude ori=
ental bop conducive murky sheriff quartic crucify la arteriolosclerosis hi=
nd something benson evocation bard scrap bone btl anglo tar prick bar usur=
er capacitate soar sergei dependent corbel blood ak homeric disputant musk=
rat eminent differentiable brunette prosody=20.</p>

<P><CENTER><FONT COLOR=3D"#616161" SIZE=3D"-2" FACE=3D"Arial">If this
notice has reached you in error, please notify us by</FONT><FONT
 COLOR=3D"#d5d5d0" SIZE=3D"-2" FACE=3D"Arial"> </FONT><FONT SIZE=3D"-2"
 FACE=3D"Arial"><A HREF=3D"http://www.more-salz.com/away.html">clicking
here</A></FONT></CENTER>

</BODY>
</HTML>


----5834674212126584--



From owner-ietf@ietf.org  Tue Feb 24 08:09:37 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18059
	for <ietf-archive@odin.ietf.org>; Tue, 24 Feb 2004 08:09:37 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Avbwc-0008LA-Av
	for ietf-list@asgard.ietf.org; Tue, 24 Feb 2004 07:45:50 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvTmN-00038P-3p
	for ietf@asgard.ietf.org; Mon, 23 Feb 2004 23:02:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11822
	for <ietf@ietf.org>; Mon, 23 Feb 2004 23:02:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvTmK-0001Gj-00
	for ietf@ietf.org; Mon, 23 Feb 2004 23:02:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvTlV-0001DN-00
	for ietf@ietf.org; Mon, 23 Feb 2004 23:01:50 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvTl8-00018w-00
	for ietf@ietf.org; Mon, 23 Feb 2004 23:01:27 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AvTl8-000OZN-00; Mon, 23 Feb 2004 23:01:26 -0500
Date: Mon, 23 Feb 2004 23:01:26 -0500
From: John C Klensin <john@jck.com>
To: Fred Baker <fred@cisco.com>, ietf@ietf.org
Subject: Re: ietf social event
Message-ID: <88334438.1077577286@scan.jck.com>
In-Reply-To: <6.0.3.0.2.20040223134146.05aefd50@mira-sjc5-b.cisco.com >
References: <6.0.3.0.2.20040223134146.05aefd50@mira-sjc5-b.cisco.
 com >
X-Mailer: Mulberry/3.1.2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Monday, 23 February, 2004 13:43 -0800 Fred Baker 
<fred@cisco.com> wrote:

> Has anyone besides me had trouble signing up for the social
> event? The site apparently uses a pop-up, which the first
> browser I used blocked, and when I tried a different browser,
> the payment transaction failed. Is it just me?

I tried several days ago, with a variety of browsers and 
settings, popups enabled and disabled, etc.   All failed, with a 
variety of different-seeming messages, most of which seemed to 
involve some Javascript failure or another.

    john







From owner-ietf@ietf.org  Tue Feb 24 08:09:37 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18066
	for <ietf-archive@odin.ietf.org>; Tue, 24 Feb 2004 08:09:37 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Avbrw-0008I8-U7
	for ietf-list@asgard.ietf.org; Tue, 24 Feb 2004 07:41:00 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvKC1-0007P7-Iv
	for ietf@asgard.ietf.org; Mon, 23 Feb 2004 12:48:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08458
	for <ietf@ietf.org>; Mon, 23 Feb 2004 12:48:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvKC0-0001jK-00
	for ietf@ietf.org; Mon, 23 Feb 2004 12:48:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvKB6-0001eC-00
	for ietf@ietf.org; Mon, 23 Feb 2004 12:47:36 -0500
Received: from seahorse.shentel.net ([204.111.11.44])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvKAR-0001Wo-00
	for ietf@ietf.org; Mon, 23 Feb 2004 12:46:55 -0500
Received: from Steve (ha96s135.d.shentel.net [204.111.96.135])
	by seahorse.shentel.net (8.11.7/8.11.7) with SMTP id i1NHkO428922
	for <ietf@ietf.org>; Mon, 23 Feb 2004 12:46:24 -0500
From: "Steve Silverman" <steves@shentel.net>
To: "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: Travel from Inchon Airport to Lotte Hotel
Date: Mon, 23 Feb 2004 12:46:50 -0500
Message-ID: <CIEELMKPOOAMCIAKANLBGEIEDKAA.steves@shentel.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.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Can anyone provide guidance on how to travel from the airport to
the meeting hotel? 

Steve 






From owner-ietf@ietf.org  Tue Feb 24 08:59:15 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18080
	for <ietf-archive@odin.ietf.org>; Tue, 24 Feb 2004 08:09:37 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Avbwc-0008Kn-11
	for ietf-list@asgard.ietf.org; Tue, 24 Feb 2004 07:45:50 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvR8k-0000vk-Qr
	for ietf@asgard.ietf.org; Mon, 23 Feb 2004 20:13:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06361
	for <ietf@ietf.org>; Mon, 23 Feb 2004 20:13:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvR8j-0003VU-00
	for ietf@ietf.org; Mon, 23 Feb 2004 20:13:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvR7u-0003RS-00
	for ietf@ietf.org; Mon, 23 Feb 2004 20:12:47 -0500
Received: from seahorse.shentel.net ([204.111.11.44])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvR7P-0003Ke-00
	for ietf@ietf.org; Mon, 23 Feb 2004 20:12:15 -0500
Received: from Steve (ha96s385.d.shentel.net [204.111.97.129])
	by seahorse.shentel.net (8.11.7/8.11.7) with SMTP id i1O1BS402291;
	Mon, 23 Feb 2004 20:11:28 -0500
From: "Steve Silverman" <steves@shentel.net>
To: "Fred Baker" <fred@cisco.com>, <ietf@ietf.org>
Subject: RE: ietf social event
Date: Mon, 23 Feb 2004 20:11:55 -0500
Message-ID: <CIEELMKPOOAMCIAKANLBMEILDKAA.steves@shentel.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.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <6.0.3.0.2.20040223134146.05aefd50@mira-sjc5-b.cisco.com >
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The payment process failed for me.
Steve Silverman

> -----Original Message-----
> From: ietf_censored-admin@vesuvio.ipv6.tilab.com
> [mailto:ietf_censored-admin@vesuvio.ipv6.tilab.com]On Behalf Of Fred
> Baker
> Sent: Monday, February 23, 2004 4:43 PM
> To: ietf@ietf.org
> Subject: ietf social event
>
>
> Has anyone besides me had trouble signing up for the social
> event? The site
> apparently uses a pop-up, which the first browser I used
> blocked, and when
> I tried a different browser, the payment transaction
> failed. Is it just me?
> /===========================================================
> ==========/
>   |     Fred Baker                 |        1121 Via Del
> Rey          |
>   |     Cisco Fellow               |        Santa Barbara,
> California |
>   +--------------------------------+        93117 USA
>           |
>   | Nothing will ever be attempted,| phone: +1-408-526-4257
>           |
>   | if all possible objections must| fax:   +1-413-473-2403
>           |
>   | be first overcome.             | mobile:+1-805-637-0529
>           |
>   |     Dr. Johnson, Rasselas, 1759|
>           |
> /===========================================================
> ==========/
>
>
> _______________________________________________
> 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 IETF_CENSORED ML
> Administrator (ietf_admin@ngnet.it).
>
>







From owner-ietf@ietf.org  Tue Feb 24 09:02:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20522
	for <ietf-archive@odin.ietf.org>; Tue, 24 Feb 2004 09:02:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Avd1U-0001xA-7l
	for ietf-list@asgard.ietf.org; Tue, 24 Feb 2004 08:54:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Avczd-0001v9-4Q
	for ietf@asgard.ietf.org; Tue, 24 Feb 2004 08:53:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20121
	for <ietf@ietf.org>; Tue, 24 Feb 2004 08:52:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Avczc-00072a-00
	for ietf@ietf.org; Tue, 24 Feb 2004 08:53:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Avcyh-0006yM-00
	for ietf@ietf.org; Tue, 24 Feb 2004 08:52:03 -0500
Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1Avcxr-0006ps-00
	for ietf@ietf.org; Tue, 24 Feb 2004 08:51:11 -0500
Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap 
	 id 8775; Tue, 24 Feb 2004 08:51:03 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Travel from Inchon Airport to Lotte Hotel
Date: Tue, 24 Feb 2004 08:50:40 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209DB2432D@zoe.office.snowshore.com>
Thread-Topic: Travel from Inchon Airport to Lotte Hotel
Thread-Index: AcP618SPHVKrR42wQn6PZjfVFfQ84wABNb6g
From: "Eric Burger" <eburger@snowshore.com>
To: "Steve Silverman" <steves@shentel.net>
Cc: "Ietf@Ietf. Org" <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Best bet is KAL Airport Limousine (actually, it's a bus).

Tickets are W12,000.  You can buy them in the arrivals hall (just before =
the exits) or on the bus.  Bus is cash only.

Stop 4B or 11A (depending on your arrival airline)
http://www.airport.or.kr/Eng/transportation/bus.jsp

> -----Original Message-----
> From: Steve Silverman [mailto:steves@shentel.net]
> Sent: Monday, February 23, 2004 12:47 PM
> To: Ietf@Ietf. Org
> Subject: Travel from Inchon Airport to Lotte Hotel
>=20
>=20
> Can anyone provide guidance on how to travel from the airport to
> the meeting hotel?=20
>=20
> Steve=20
>=20
>=20
>=20
>=20
>=20
>=20




From owner-ietf@ietf.org  Tue Feb 24 09:32:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22251
	for <ietf-archive@odin.ietf.org>; Tue, 24 Feb 2004 09:32:16 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AvdUP-0002ov-KV
	for ietf-list@asgard.ietf.org; Tue, 24 Feb 2004 09:24:49 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvdTa-0002ny-Lb
	for ietf@asgard.ietf.org; Tue, 24 Feb 2004 09:23:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21965
	for <ietf@ietf.org>; Tue, 24 Feb 2004 09:23:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvdTZ-0002Zi-00
	for ietf@ietf.org; Tue, 24 Feb 2004 09:23:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvdSg-0002W8-00
	for ietf@ietf.org; Tue, 24 Feb 2004 09:23:03 -0500
Received: from zephir.uk.clara.net ([195.8.69.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvdRv-0002SU-00
	for ietf@ietf.org; Tue, 24 Feb 2004 09:22:15 -0500
Received: from du-069-0260.access.clara.net ([217.158.145.6] helo=Puppy)
	by zephir.uk.clara.net with smtp (Exim 4.22)
	id 1AvdRt-000K89-Q4; Tue, 24 Feb 2004 14:22:14 +0000
Message-ID: <03de01c3fae1$9b0f1b70$ec1a8640@Puppy>
Reply-To: "Adrian Farrel" <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Steve Silverman" <steves@shentel.net>, "Ietf@Ietf. Org" <ietf@ietf.org>
References: <CIEELMKPOOAMCIAKANLBGEIEDKAA.steves@shentel.net>
Subject: Re: Travel from Inchon Airport to Lotte Hotel
Date: Tue, 24 Feb 2004 14:21:55 -0000
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

http://www.tta.or.kr/ietf59/transportation.htm
----- Original Message ----- 
From: "Steve Silverman" <steves@shentel.net>
To: "Ietf@Ietf. Org" <ietf@ietf.org>
Sent: Monday, February 23, 2004 5:46 PM
Subject: Travel from Inchon Airport to Lotte Hotel


> Can anyone provide guidance on how to travel from the airport to
> the meeting hotel? 




From owner-ietf@ietf.org  Tue Feb 24 19:13:50 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18506
	for <ietf-archive@odin.ietf.org>; Tue, 24 Feb 2004 19:13:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AvmMz-0004j6-Gw
	for ietf-list@asgard.ietf.org; Tue, 24 Feb 2004 18:53:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvmMZ-0004iH-FF
	for ietf@asgard.ietf.org; Tue, 24 Feb 2004 18:53:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17748
	for <ietf@ietf.org>; Tue, 24 Feb 2004 18:53:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvmMX-0000Yt-00
	for ietf@ietf.org; Tue, 24 Feb 2004 18:53:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvmLe-0000Ui-00
	for ietf@ietf.org; Tue, 24 Feb 2004 18:52:22 -0500
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvmLF-0000QZ-00
	for ietf@ietf.org; Tue, 24 Feb 2004 18:51:57 -0500
Received: from [147.28.0.62] (helo=127.0.0.1)
	by psg.com with esmtp (Exim 4.30; FreeBSD)
	id 1AvmLG-000Hwa-6K
	for ietf@ietf.org; Tue, 24 Feb 2004 23:51:58 +0000
Date: Tue, 24 Feb 2004 15:50:58 -0800
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.62i) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <61164215669.20040224155058@psg.com>
To: ietf@ietf.org
Subject: Fwd: Comments solicited: draft-kompella-zinin-early-allocation-00.txt
In-Reply-To: <8930684742.20040212223802@psg.com>
References: <8930684742.20040212223802@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,RCVD_NUMERIC_HELO 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The document may apply to other areas of the IETF as well.
Please comment.

-- 
Alex
http://www.psg.com/~zinin/

This is a forwarded message
From: Alex Zinin <zinin@psg.com>
To: routing-discussion@ietf.org
Cc: rtg-dir@ietf.org
Date: Thursday, February 12, 2004, 10:38:02 PM
Subject: Comments solicited: draft-kompella-zinin-early-allocation-00.txt

===8<==============Original message text===============
Folks-

 Please review draft-kompella-zinin-early-allocation-00.txt and
 provide your comments. We're going to discuss it at the Routing
 Area meeting in Seoul. Below is the abstract from the document:

   This memo discusses earlier allocation of code points by IANA as a
   remedy to the problem created by the "Standards Action" IANA policy
   for protocols where, by the IETF process, implementation and
   deployment experience is desired or required prior to publication.
 
 The document is available at:
 
 http://www.ietf.org/internet-drafts/draft-kompella-zinin-early-allocation-00.txt
  
 Send your comments to routing-discussion@ietf.org, please.
 
-- 
Alex
http://www.psg.com/~zinin/



===8<===========End of original message text===========




From owner-ietf@ietf.org  Tue Feb 24 20:08:57 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20152
	for <ietf-archive@odin.ietf.org>; Tue, 24 Feb 2004 20:08:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AvnQn-000621-1Z
	for ietf-list@asgard.ietf.org; Tue, 24 Feb 2004 20:01:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvnQX-000610-4V
	for ietf@asgard.ietf.org; Tue, 24 Feb 2004 20:01:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19965
	for <ietf@ietf.org>; Tue, 24 Feb 2004 20:01:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvnQV-0006Ie-00
	for ietf@ietf.org; Tue, 24 Feb 2004 20:01:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvnPa-0006Cx-00
	for ietf@ietf.org; Tue, 24 Feb 2004 20:00:30 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvnPA-00067l-00
	for ietf@ietf.org; Tue, 24 Feb 2004 20:00:04 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 24 Feb 2004 17:10:27 +0000
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i1P0xWuA002665;
	Tue, 24 Feb 2004 16:59:32 -0800 (PST)
Received: from localhost (ole@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id QAA06214; Tue, 24 Feb 2004 16:59:32 -0800 (PST)
Date: Tue, 24 Feb 2004 16:59:32 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
Reply-To: Ole Jacobsen <ole@cisco.com>
To: Eric Burger <eburger@snowshore.com>
cc: Steve Silverman <steves@shentel.net>, "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: RE: Travel from Inchon Airport to Lotte Hotel
In-Reply-To: <4A3384433CE2AB46A63468CB207E209DB2432D@zoe.office.snowshore.com>
Message-ID: <Pine.HPX.4.58.0402241657590.19344@wells.cisco.com>
References: <4A3384433CE2AB46A63468CB207E209DB2432D@zoe.office.snowshore.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

If you like comfort, contact the hotel and they will collect you in a
private car.

Price is KRW 130,000   :-)


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, 24 Feb 2004, Eric Burger wrote:

> Best bet is KAL Airport Limousine (actually, it's a bus).
>
> Tickets are W12,000.  You can buy them in the arrivals hall (just before
> the exits) or on the bus.  Bus is cash only.
>
> Stop 4B or 11A (depending on your arrival airline)
> http://www.airport.or.kr/Eng/transportation/bus.jsp
>
> > -----Original Message-----
> > From: Steve Silverman [mailto:steves@shentel.net]
> > Sent: Monday, February 23, 2004 12:47 PM
> > To: Ietf@Ietf. Org
> > Subject: Travel from Inchon Airport to Lotte Hotel
> >
> >
> > Can anyone provide guidance on how to travel from the airport to
> > the meeting hotel?
> >
> > Steve
> >
> >
> >
> >
> >
> >
>
>



From owner-ietf@ietf.org  Tue Feb 24 23:57:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26993
	for <ietf-archive@odin.ietf.org>; Tue, 24 Feb 2004 23:57:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AvquY-0000XV-TN
	for ietf-list@asgard.ietf.org; Tue, 24 Feb 2004 23:44:42 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvquP-0000X0-5v
	for ietf@asgard.ietf.org; Tue, 24 Feb 2004 23:44:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26563
	for <ietf@ietf.org>; Tue, 24 Feb 2004 23:44:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvquK-0000ys-00
	for ietf@ietf.org; Tue, 24 Feb 2004 23:44:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvqtH-0000tr-00
	for ietf@ietf.org; Tue, 24 Feb 2004 23:43:23 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvqsI-0000kz-00
	for ietf@ietf.org; Tue, 24 Feb 2004 23:42:24 -0500
Received: from sopac.org (localhost.localdomain [127.0.0.1])
	by franck-lxnb.sopac.org.fj (Postfix) with ESMTP
	id BF07D4B6A1; Wed, 25 Feb 2004 16:41:45 +1200 (FJT)
Message-ID: <403C2789.7050905@sopac.org>
Date: Wed, 25 Feb 2004 16:41:45 +1200
From: Franck Martin <franck@sopac.org>
Organization: SOPAC
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040120
X-Accept-Language: en, en-au, en-us, fr
MIME-Version: 1.0
To: ietf@ietf.org
Cc: mose@mose.fr
Subject: Request for Comments: RFC Wiki Syntax
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigDF9B6CF904FD7E428E804339"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigDF9B6CF904FD7E428E804339
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

http://tikiwiki.org/tiki-index.php?page=RFCWiki

Where do I go from there?

How do I submit this document to IETF? Can someone review it? Give advice?

Harald?

Cheers

-- 
Franck Martin
ICT Specialist
franck@sopac.org
SOPAC, Fiji
GPG Key fingerprint = 44A4 8AE4 392A 3B92 FDF9  D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard


--------------enigDF9B6CF904FD7E428E804339
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAPCeJvnmeYIHZEyARAs2XAJ45ZKqtTa7xu0fG5BStMpX348wTFACfYEgc
yHDNdcglpM9gOTKEdYO79D8=
=wwVD
-----END PGP SIGNATURE-----

--------------enigDF9B6CF904FD7E428E804339--



From owner-ietf@ietf.org  Wed Feb 25 00:44:15 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28671
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 00:44:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Avrlm-0001WW-GC
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 00:39:42 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AvrlY-0001Vw-Ce
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 00:39:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28500
	for <ietf@ietf.org>; Wed, 25 Feb 2004 00:39:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvrlW-0005vQ-00
	for ietf@ietf.org; Wed, 25 Feb 2004 00:39:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvrkX-0005qq-00
	for ietf@ietf.org; Wed, 25 Feb 2004 00:38:26 -0500
Received: from sentosa.post1.com ([202.27.17.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1Avrjc-0005ia-00
	for ietf@ietf.org; Wed, 25 Feb 2004 00:37:28 -0500
Received: (qmail 36458 invoked from network); 25 Feb 2004 05:58:51 -0000
Received: from dhcp1018.conference.apricot.net (HELO pobox.org.sg) (169.223.253.18)
  by sentosa.post1.com with SMTP; 25 Feb 2004 05:58:51 -0000
Message-ID: <403C345A.5070202@pobox.org.sg>
Date: Wed, 25 Feb 2004 13:36:26 +0800
From: James Seng <jseng@pobox.org.sg>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, zh-cn, zh-tw, ja, ko
MIME-Version: 1.0
To: Franck Martin <franck@sopac.org>
CC: ietf@ietf.org, mose@mose.fr
Subject: Re: Request for Comments: RFC Wiki Syntax
References: <403C2789.7050905@sopac.org>
In-Reply-To: <403C2789.7050905@sopac.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

then send it to internet-drafts@ietf.org

james

Franck Martin wrote:
> http://tikiwiki.org/tiki-index.php?page=RFCWiki
> 
> Where do I go from there?
> 
> How do I submit this document to IETF? Can someone review it? Give advice?
> 
> Harald?
> 
> Cheers
> 



From owner-ietf@ietf.org  Wed Feb 25 06:06:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10206
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 06:06:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Avwfc-0005Mj-Cp
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 05:53:40 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Avwef-0005M6-5l
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 05:52:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09812
	for <ietf@ietf.org>; Wed, 25 Feb 2004 05:52:38 -0500 (EST)
From: gnulinux@pacinfo.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Avwec-0007cj-00
	for ietf@ietf.org; Wed, 25 Feb 2004 05:52:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Avwdj-0007Y3-00
	for ietf@ietf.org; Wed, 25 Feb 2004 05:51:46 -0500
Received: from cougar.pacinfo.com ([12.7.120.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Avwd4-0007TL-00
	for ietf@ietf.org; Wed, 25 Feb 2004 05:51:02 -0500
Received: from w2ksp2 (dsl-db.pacinfo.com [12.7.123.20])
	by cougar.pacinfo.com (8.12.10/8.12.10) with ESMTP id i1PAsq3I013390
	for <ietf@ietf.org>; Wed, 25 Feb 2004 02:54:52 -0800
To: ietf@ietf.org
Date: Wed, 25 Feb 2004 02:50:47 -0800
MIME-Version: 1.0
Subject: digital signature request
Reply-to: gnulinux@pacinfo.com
Message-ID: <403C0D87.31678.463FAB5@localhost>
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

this is a request for this list to be digitally
signed by the list processor.

to all list members.  if after reading this post
you would like the list processor to digitally
sign all posts please say so (and tell the list
owner) so that the level of interest can be
gauged.  thanks.

i'm making this request because i need a way to
positively id the messages from this list.  i'm
spending way too much of my time culling spam from
my real email even though i'm employing the latest
spam filtering tools.  please give me the one
simple tool i know of that will allow me to
positively differentiate the mail from this list
from all others - a digital signature.

signing all list messages won't be detrimental to
list recipients not interested.  it will however
allow folks wishing to implement anti-spam
measures around digital signatures to do so.
mailing lists often require that recipients
confirm their email address as an anti-spam
measure for the list.  please help list recipients
implement their own anti-spam measures by allowing
the list messages to be positively identified.

to be clear, this is a limited scope spam
solution, but it works.  and it will continue to
work provided the underlying cryptography is sound
(unlike many other anti-spam technologies that are
simply clever hacks in an escalating spam/anti-
spam arms race).

some folks say that there will be no spam solution
as long as email is free.  i say there will be no
spam solution as long as you expect anyone to be
able to send email to you without first proving
they are not a spammer.

part of finding a solution is to revision what
email is.  i argue that email can no longer be a
method of unfettered *initial* contact.  once that
is accepted then this solution doesn't seem
painful.  i suspect that there won't be a solution
until email is seen from this perspective.  as
noted above, mailing lists are essentially
adopting this perspective (to better manage spam
on the list side), it would be helpful if they
took an additional small step that would enable
list recipients to better manage spam on their end
too.

there's no need for a larger web of trust other
than one that is personally maintained when using
digital signatures to defend against the onslaught
of spam.  your personal web of trust (a.k.a. your
keyring) is your unspoofable anti-spam whitelist.
this is where the revisioning of email occurs.
instead of email being the way you initially make
contact with an entity, with digital signatures it
can serve as a reliable communications channel
*once* contact has been established.

my intention is to implement a procmail recipe at
the mail server level.  the procmail recipe will
be used to check incoming mail for whitelisted
digital signatures that have been uploaded from
each individual user.

mailing lists could use the same recipe, no
messages would be handed over to the listserv
software unless it was signed by a whitelisted
signature.  again, this won't stop machines from
being compromised but as soon as a machine is
compromised that entity will be *immediately*
notified by their peers.  in the case of a mailing
list *many* people will suddenly know who's
compromised and the list can even have a mechanism
that allows a whitelisted key to be removed once
it becomes compromised.  this would also serve the
dual function of indirectly alerting the owner of
the compromised host since they will investigate
why they are no longer receiving list traffic.

regarding whether to utilize inline or mime GPG, i
say use either.  the preferred solution will self-
select over time.  it is possible to create a
procmail recipe that can handle both methods.

Two key benefits of this anti-spam technology:

1.  it works and will likely continue to work
beyond the foreseeable future

2.  it can be implemented without the consensus,
from the bottom up

below are my responses to posts in a few mailing
list threads regarding digital signatures and
spam.  please read my responses as they will
likely answer many of the questions that may
result from reading what i wrote above.  apologies
to the folks whose comments i'm replying to for
not referencing their names (i didn't have the
time).

looking forward to feedback.

ciao,

david
--
spam is something we can eliminate by
changing our personal behaviors and expectations
and cooperating.  and it can happen gradually.



thread:  ietf - proposal for built-in spam burden
& email privacy protection -----

>>2. Except for senders in a whitelist (e.g.,
>>list mail), I bounce to  the sender  any email
>>that is NOT encrypted with my public-key,
>>providing my   public-key and instructions for the
>>sender to resubmit the message  properly
>>encrypted.
>
>Anything at all that generates a bounce message
>on a mass-produced mailing acts as a "damage
>amplifier" from the basic internet backbone's
>point of view -- at least doubling the associated
>automated traffic and wasted/misused resources.
>These days such a bounce is especially fruitless,
>as all viruses and quite a lot of SPAM have forged
>headers that the stupid bounce agents cannot or do
>not parse.
>
>This is pet peeve of mine as it is -- I got (and
>continue to get) more bounce messages from mydoom
>reporting that mail "from me" is contaminated than
>I do copies of the virus itself.  No virus for two
>years now hasn't forged mail headers -- the From
>field is totally irrelevant in all current viruses-
>- yet all the AV programs in the world think they
>are doing you a favor. NOT.
>
>Now imagine that sort of stupidity scaled out so
>that every MTA in the world is checking esigs and
>bouncing improperly signed mail.  Imagine the
>loops created when a legacy mailer or improperly
>configured mailer bounces the bounce messages back
>to the bouncer, to be bounced again. Nightmarish.

solution - don't auto-respond, give out a keyword
with your email address, this will allow initial
contact to be more easily plucked from the sea of
spam - in the long run as more people digitally
sign email spam will become even less profitable
because there will be even fewer responses - we'll
never know what's possible if we don't try

>encrypting for each of the list recipients is too
>much of a burden for the list

solution - don't encrypt, only digitally sign -
not a burden

>Don't get me wrong: encouraging people to use pgp
>is a good idea, but making it a requirement before
>accepting it is a policy decision that the end
>user should be making, not the list.

solution - by only digitally signing it is
completely up to the end user to decide whether or
not to add this tool to their anti-spam toolbox

>Your proposal is in line with some existing ones,
>at least one of which response to the seriously
>problematic key management issue.

solution - non-local, centralized key management
is a huge problem, but key management isn't a
problem if the only important keys are your
personal ones and if you don't expect to be able
to instantaneously have access to anyone's public
key via a keyserver - keyservers aren't necessary
for folks who exchange email with primarily a
small group of people

>I'm not saying to reject non esig mails, but to
>held them for approval by moderators... If you
>want your post to go through quickly, sign it...
>It would be a worthwhile incentive.

sounds like a great idea, but this is in addition
to and isn't required for what i'm suggesting

>Also note, there is an addition burden placed on
>end users who rely on receiving encrypted email in
>your proposal.  Under your scheme, a user has to
>go through the trouble of decrypting the message
>just to see if it is spam or not.  This eliminates
>almost all forms of automated spam mitigation
>except those related to the low-level SMTP, DNS or
>other new authentication/authorization techniques.

reminds me that signing and not encrypting still
allows bayesian filters to continue to be useful

>Unfortunately, requiring that they have a
>published public-key *is* a burden to the average
>user.  J. Random Luser just wants to sit down at
>his PC, boot up Winders, bring out Lookout, and
>forward a garish HTMLified email full of stale
>jokes to his buddies, complete with pictures, and
>he wants it to go through, without a hitch, right
>now.  He thinks public keys are the ones hanging
>on the gas station wall, for the bathroom.  He
>thinks crypto is someone from Superman's home
>planet.  He thinks the IETF is them guys whut
>raided David Koresh.  He has no clue what the ASRG
>is, but he thinks it sounds dirty.

again, no need for keyservers for folks that are
exchanging email within a small group of people.
also, let's stop trying to allow email to continue
to be what it has evolved into, let those folks
that want email to stay the way it is keep it that
way, let's create a spam-free email environment
that works and satisfies *us*, i suspect that if
this is witnessed folks will eventually start
thinking of email differently as their personal
spam pain tolerances are exceeded.

>Make it worth their while, by coming up with
>infrastructure such that they won't get any spam
>if they have a public key, and MAYBE they'll
>bother doing it, IF the ISP will hold their hands
>every step of the way (and not charge them too
>much, including for issuing new keypairs when they
>let the private ones slip out too much).  Of
>course, this means that all their equally
>technically-enlightened friends have to know how
>to USE his public key....

solution - accept that it will be a gradual
process, let's just start with mailing lists
signing all messages that get sent to list
recipients - that's easy

>This sounds very much like the use of extra
>headerz, or a password on the subject line, but on
>steroids.  In the end, possibly useful, IF you can
>get everybody aboard, but they won't go until
>everybody ELSE is already on board, and meanwhile
>it's a pain in the proverbial posterior to
>everyone who wants to communicate with the people
>using it.

for me it is *less* pain than what i'm
experiencing dealing with my current spam load,
and digital signatures can be ignored if you don't
want to verify them - also, if someone tells you
that they are receiving so much spam that you will
have to sign all email you send to them, are you
going to tell them they are causing you too much
pain?  heck, just pick the phone up and call them
then.

>Second, even if the above weren't a problem, one
>still has the problem that a virus infected user
>will still be sending messages, just like everyone
>else.

this will still be a problem but with a digital
signature solution in place infected computers
will be identifiable and probably immediately
disinfected, folks will become hyper-aware of
allowing their machines to become compromised if
suddenly they are unable to exchange email with
their small and *important* group of people
because their public key became blacklisted by
these same folks - the very nature of digital
signatures positively identifies infected
computers

>There is no scheme in which the rules can't be
>broken by someone intent on breaking them.  The
>only path is to detect them, and prosecute them.
>In the case of spam, detection is easy, but not
>automatic.  Prosecution is now possible.  Its
>still a whack-a-mole game. It won't end unless you
>can get past the virus infection to the virus
>operator, and hopefully, there aren't really too
>many virus operators.  Of course, we aren't
>stopping spam either in a very real sense, but
>rather abusers who are annoying and mailbombing
>people.  But by my count of my inbox, if you stop
>those people, I can certainly handle the rest
>which amounts to maybe 1% of my current junk mail.

there's no known way to crack GPG, widespread
adoption of digital signatures against spam will
either help bring spam to and end or tell us what
NSA might already know  ;)  - let's put those
spammers to work!  also, prosecutions by a central
authority won't be necessary, peers will do the
prosecuting by rejecting email from compromised
systems, the owner of the infected system will be
de facto "punished" because communications with
their peers will end until they clean their system
(or stop spamming).

>>The "for pay" idea is just another scam from
>>the people who would love to get a percentage of
>>the pay. While I'm sure Microsoft and others would
>>just love to get a cut of this (I know I would),
>>it doesn't do anything to stop spam, and if
>>implemented, would simply (and wrongly) charge
>>users whose computers were virus infected.
>
>Wrongly?  I'm not so sure.  Something ought to be
>done to stop the  Typhoid Marys of the Internet.
>Putting them on notice that they WILL be held
>responsible for spreading the infection, or its
>effects, just MIGHT result in them FINALLY taking
>some responsibility for their "computer hygiene".
>Sure, there will have to be several well
>publicized example cases before most folk will sit
>up and take notice, but in the long run, it might
>be effective.

i agree, trying to impose a burden
(computationally or monetarily) on spammers will
not work IMHO.  i will leave it to others to
explain this in more detail.  and to repeat,
prosecutions by a central authority won't be
necessary, peers will do the prosecuting by
rejecting email from compromised systems, the
owner of the infected system will be de facto
"punished" because communications with their peers
will end until they clean their system (or stop
spamming).

>So even discussing adding a silly thing like
>mandatory esigs and encryption as an antispam
>measure is a waste of time, except possibly on a
>local basis.  If I set up a small mailing list (or
>generalized group of individuals) and all of its
>members agree to do this, there is little
>"evolutionary pressure" for spammers to detect and
>foil our scheme and we will be "immune" (at the
>cost of a fair amount of extra work).  If
>everybody does it and the automated tools for
>doing it without so much work are widely
>disbursed, they will develop countermeasures in no
>time at all and we'll lose our immunity.

please explain how spammers will evolve past the
public key encryption technology used in digital
signatures?  as noted earlier machine compromises
will still occur but they will be able to be dealt
with because peers of the compromised machine will
immediately identify and neutralize the problem by
ending communication (by blacklisting the
compromised key).  suddenly the owner of the
compromised machine hears silence.

>Automated text analysis will never be perfect,
>because even human text analysis for
>interest/disinterest (secretaries) aren't perfect.
>But it can help sort things.  I hand filter about
>1500 messages a day.  I get about 3500 over the
>weekend. Monday's filtering doesn't take me any
>longer than tuesdays filtering.

unfortunately the approach you describe could
likely be your undoing in the long run as spammers
ratchet up the volume to the point were it *will*
take you a long time using this approach.  this is
why even with 99.9% accurate bayesian filtering,
all spammers need to do is ratchet up the volume
to get more spam through the 0.1% error rate of
the bayesian filter.

>>>Then using the IETF list as an example, you
>>>would need the entire list of recipients and their
>>>public keys, and you would need to send a message
>>>either directly to each of them, one by one, or
>>>send a single message with a session key for each
>>>recipient (thousands).  This isn't going to work.
>>
>>Let's not mix apples with speedboats. These are
>>some options with the proposal:
>>
>>#1: no encryption is used either way, the list
>>address is in a whitelist for each recipient.
>>
>>#2: each recipient can only send encrypted msgs
>>(possibly, also signed) to the list, with the
>>list's key, for distribution. The listserver
>>verifies and resends the messages in plain text,
>>where #1 applies for each recipient.
>>
>>#3: the list receives messages as in #2 but the
>>listserver sends the msgs as encrypted mail to
>>each recipient, with each recipient's key.
>
>#4 (my preferred) the member send a message to
>the list with his digital signature. The list
>checks the digital signature (from keyserver or
>from a member database) and post the message if
>signature is valid. If the signature is not valid,
>the message is held for approval. But yes this
>scheme does not offer much more than restrict
>posting to list members only, which the IETF had
>to do last year(?).

if the list server signs each message that then
allows recipients to positively identify mail from
the list.  this is *HUGE*.  if i have an email
account that only receives mail from mailing lists
that sign all messages then i can dump all
incoming non-whitelisted digitally signed email at
the server and *know* that all my email is legit.



thread:  ietf - how not to filter spam -----

>>first, there is an increasingly heated debate
>>between folks who want to sign the message (TEOS,
>>DomainKeys), versus others who want to secure the
>>channel between sender and receiver (RMX, LMAP,
>>SPF, etc.).
>
>What does it matter what the resolution is?
>Neither solution eliminates the spam channel, and
>solves the problem, as information theory shows.
>Its just a silly debate over two schemes to thread
>a needle that can't be threaded.

think of spam as a river passing through multiple
channels, let's find a channel we can change.
folks talk about spammers taking advantage of
email protocols.  another angle is to say that
spammers take advantage of people's behavior.
it's much easier to change my personal behavior
and expectations with regard to email than it is
for me to change an established internet protocol.
so stop thinking about eliminating the ability to
send spam and focus on *absolutely* identifying
real email.  spam will dry up as people are able
to absolutely identify real email.

>>That sounds like the old "authentication solves
>>spam" hope.  It was wrong before SMTP-AUTH and it
>>is still wrong.
>
>Guess what, it is impossible to "solve" spam the
>same way it is  impossible to "solve" burglary. At
>least with authentication you get to have
>whitelists that work. If you get a message with my
>email address in the "from" line it could be from
>anyone. If it is signed with my PGP key you know
>it came from me personally or someone went through
>a LOT of trouble to get access to my private key
>and the key phrase.
>
>The usefulness of authentication could be further
>extended by building a web of trust where people
>vouch for the fact that others aren't spammers.
>Obviously spammers will slip through from time to
>time, but anyone who spams or keeps vouching for
>spammers will be removed from the web of trust.
>But even if this part doesn't work authentication
>is still useful.

exactly



thread:  tidbits - digital signatures in tidbits --
---

>As I said earlier, I don't see the point of doing
>it for this list, but the mechanism itself isn't
>so easily spoofed.  Think of it as an address
>based whitelist with addresses that can't be
>forged.  A spammer wouldn't be able to get his own
>public key on the whitelist, and can't pretend to
>be someone else because he doesn't have the
>corresponding private key.  I personally wouldn't
>use such a system, since the Bayesian spam filter
>I use (bogofilter) works well enough, but people
>that are more annoyed with spam than I get might
>find such a system attractive.

exactly, my bayesian filter (POPFile) works great,
but i get so much spam that the 1% of my email
that doesn't get classified correctly is causing
me too much pain.

>>>Then you have to start allowing attachments on
>>>the list...not a great idea.
>>
>>Not necessarily. This should work as text only
>>with PGP 8.
>>
>>Attachment converted: HHBV HD:PGP.sig (pgDS/----
>>) (002B8C8F)
>
>Obviously, it does not work except by allowing
>attachments... and  it's hard to believe that
>TidBITS Talk would ever come to that.

no, digital signatures can be inline, the mime
attachment method is more robust but not required.
so tidbits can be signed without mime
attachments.  FWIW, most email clients do support
the mime method.

>>There are plenty of uses for digital
>>signatures, but I don't think approving mailing
>>list postings is likely to be one of them any time
>>soon.
>
>Agreed. Remember the messages that slipped
>through were approved by Adam because of poor html
>formatting, except one that forged his email.  If
>he used digital signatures most of those messages
>still would've been signed, and just like Habeas
>headers, if you're spam filter auto-whitelists
>signed messages they would come through.

exactly, if the list is signed spam can still get
through.  what the signature does is allow the
mailing list traffic to be positively identified
amidst the personal flood of spam many folks
receive.  just like we help list maintainers out
by taking extra steps to allow posting,
maintainers could help us out by signing all list
messages.  dealing with spam requires cooperation.

>>I think people should sign all of their
>>messages. That will have several effects:  - Peole
>>will get suspicious if a message isn't signed,
>>making forging mesages harder.
>
>How do you handle email from a kiosk, or a cell
>phone, or someone else's computer? There are too
>many instances in the real world where this
>happens. It's one of the benefits of IMAP..you
>don't HAVE to be on any particlular computer to
>get your email.

by locating signature verification at the mail
server level.  create a procmail recipe that will
automatically tag all signed email as to whether
or not the signature exists in the personal
whitelist that has been uploaded to the server.

>I do think we're getting off topic but -- any
>modern approach to the spam problem must take into
>account the fact that at any given time the
>Internet contains millions of insecure computers
>that can be taken over by viruses and used as
>zombies to, among other things, send spam.  If
>digital signatures were actually used in some
>standardized way, it would be trivial for the
>virus to grab it and sign its messages.

again, digital signatures as an anti-spam
technology will be effective for folks who don't
*need* to be able to be contacted by anyone on the
internet prior to them verifying they're not a
spammer.  folks that need to be this accessible
need to either modify this requirement, continue
to rely on statistical spam filtering tools, solve
the key distribution problem, and/or work to
change established internet protocols.

>This assumes that you already have all the keys
>of potential  correspondents in your keyring,
>which makes this just another form of
>whitelisting, albeit a cryptographically secured
>one. The shortcomings of whitelisting systems are
>well described here and elsewhere, but basically
>you'll have to read all your (signed) spam just to
>make sure there isn't a message there from someone
>you haven't whitelisted yet. Remember, too, that
>public keys really should expire, so you would
>need a method for keeping your whitelist (keyring)
>up to date. If you try to automate the whitelist,
>you open the door to spammers again.

you are assuming the receipt of email from a large
previous unknown group of entities.  if this is
you then you won't benefit from digital signatures
adopted on a small scale.  but if you are one of
the many folks who only receives email from a
small group of people then digital signatures
ensure that you will never miss one of their
messages.

>I'm a big proponent of cryptographic signatures;
>they just aren't the Final Ultimate Solution to
>Spam.

digital signatures don't do anything whatsoever to
end spam - they allow spam to be sent to > /dev/null

>Whitelists work great for those corresponding to
>just a few people. But they simply aren't pratical
>for participation in mail lists.

at the very least a digitally signed list (by the
list software/moderator) allows list recipients to
identify list traffic.  i do have my doubts about
how impractical it would be for the list
software/moderator to check for digital signatures
prior to posting messages from list members.
think gradual implementation, let go of the notion
of all members signing their posts, although they
might, and for every list member that does sign
that's one less post to be analyzed to see if it's
spam.

>>Whitelists work great for those corresponding
>>to just a few people. But they simply aren't
>>pratical for participation in mail lists.
>
>Sure they are. You are missing the whole point of
>how digital signatures would/should be
>implemented in a discussion list environment.
>
>It's not the end user who needs to verify the
>signature, it's the list processor.
>
>I subscribe to a list. As part of that process I
>provide the public  half of my key. Any message I
>submit to the list is signed by me using my
>private key. The list manager software then
>verifies my signature and passes the verified
>message on to the list or to the list moderator.
>This ensure that only messages written by bonefide
>members of the list get past on to the members of
>the list.
>
>The whole point is not to ensure that messages
>coming from the list are signed but to ensure that
>messages submitted to the list are signed.
>
>This also obviates the need for the list to
>support attachments and  makes pgp/mime a BETTER
>alternative to inline signing. The list  processor
>receives the messages, verifies the signature and
>strips the signature. I, as a subscriber to the
>list, never see the signature.
>
>Maybe, the list processor itself signs the
>messages it sends out. In which case I only need
>to have the one key (the public key for the list)
>in my keychain.

well said.  i differ only in that i would start by
having the list processor sign the list (what i
perceive to be a simpler yet positive step) rather
than trying to get list members to sign in order
to post.

>If we stop all counterspam measures by pointing
>out that they aren't the Final Ultimate Solution
>To Spam (TM), the situation will never improve.

here!  here!




From owner-ietf@ietf.org  Wed Feb 25 09:52:02 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18752
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 09:52:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw00g-0007rl-K5
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 09:27:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Avzzo-0007rC-R7
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 09:26:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17689
	for <ietf@ietf.org>; Wed, 25 Feb 2004 09:26:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Avzzo-0004yt-00
	for ietf@ietf.org; Wed, 25 Feb 2004 09:26:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Avzyr-0004tp-00
	for ietf@ietf.org; Wed, 25 Feb 2004 09:25:46 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Avzxw-0004lM-00
	for ietf@ietf.org; Wed, 25 Feb 2004 09:24:48 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id 2D2C6D7; Wed, 25 Feb 2004 09:22:12 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
To: gnulinux@pacinfo.com, ietf@ietf.org
Subject: Re: digital signature request
Date: Wed, 25 Feb 2004 09:22:54 -0500
User-Agent: KMail/1.5.2
References: <403C0D87.31678.463FAB5@localhost>
In-Reply-To: <403C0D87.31678.463FAB5@localhost>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402250922.54777.spamtrap.ietf@dja.mailme.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wed February 25 2004 05:50, gnulinux@pacinfo.com wrote:

 > i'm making this request because i need a way to
 > positively id the messages from this list.

Look in the normally-hidden headers.  Most lists have something unique 
there.  Usually it's something like a List-ID or X-Been-There line.  In 
this case:

 > Sender: owner-ietf@ietf.org

If your MUA doesn't allow filtering on any header line you choose 
(including ones that aren't usually there), I seriously suggest you 
look into getting a new MUA.

Okay, so it can be forged much more easily than a digsig.  Big deal.  I 
don't think any spammer is going to bother emailing us directly and 
forging that header.

 > i'm
 > spending way too much of my time culling spam from
 > my real email even though i'm employing the latest
 > spam filtering tools.

Having the latest tools means nothing, unless they are used right.  Are 
you keeping your spam definitions up to date, by either subscribing to 
someone else's updates, or constantly building and refining your own 
database (such as with Bayesian filters)?  Are you applying whitelists, 
AND heuristics?  Are you also very carefully applying blacklists?  Are 
you observing very carefully, and tweaking, just how "spammy" your 
heuristics have to label an email before you dump it?  Are you holding 
the borderline cases for review?

 > mailing lists could use the same recipe, no
 > messages would be handed over to the listserv
 > software unless it was signed by a whitelisted
 > signature.

Requiring digsigs on a list would help cut down on spammers forging list 
members' addies to spam "only members can post" lists.  Also, this is 
one of the few lists where I'd think most people would be clueful 
enough to do it.

However, would it be worth the bother?  Unless there's some poor sod 
already spending tons of his own time filtering out such spam already, 
I'd say no.  (If there is, THANK YOU!  Been there, done that, ripped up 
the T-shirt in frustration.  You're doing a great job.)  I can't recall 
when I've last seen a spam here.

 > again, this won't stop machines from
 > being compromised but as soon as a machine is
 > compromised that entity will be *immediately*
 > notified by their peers.  in the case of a mailing
 > list *many* people will suddenly know who's
 > compromised and the list can even have a mechanism
 > that allows a whitelisted key to be removed once
 > it becomes compromised.

Eh?  Why would compromise necessarily change the keys?  How will they be 
notified?  Can you guarantee that the compromise won't include blocking 
such notifications?  What's the mechanism you envision for all this?  
Lay out a rough roadmap, and maybe we can work it up into a draft, and 
then have it accepted as an RFC.

Here's an alternate angle for you to chew on.  Try coming up with some 
sort of mechanism that could easily be built into all MUAs, MTAs, 
mailing list managers, anti-spam "solutions", and all other programs 
involved, such that a user can take some simple action to sign up for 
an email list, and have all email from that list automagically added to 
his whitelist, at each step of the chain, AND the list owner can verify 
irrefutably that Joe Luser (or at least someone at that email address) 
asked to be on the list, AND in a way that would be at least difficult, 
if not impossible, for someone to accidentally trigger by such simple 
actions as "previewing" an HTML email or viewing a web page.  Never 
mind whether the list ID can be forged by spammers, whether the list 
requires digsigs on submissions, or other such irrelevant details; I'm 
only interested in automating the verified signup and whitelisting 
process.  (Tho if you can automate that enough that Joe Luser groks it, 
that would be great!)  That's an idea I came up with a while back and 
haven't had the time to put serious work into.

 > apologies
 > to the folks whose comments i'm replying to for
 > not referencing their names (i didn't have the
 > time).

You ask us to take the time to implement a new mechanism of dubious 
value.  Meanwhile, you won't take the time to mention our names so that 
we can at least go quickly to the part of your email that concerns us, 
nor break it up into individual pieces so as to at least preserve the 
subject lines.  Talk about cooperating....

 > spam is something we can eliminate by
 > changing our personal behaviors and expectations
 > and cooperating.

Long ago that might have been true.  Welcome to the Everlasting 
September.

 > and it can happen gradually.

It will probably have to!

As for the lengthy conglomeration of your replies to other messages, 
forget it, I for one am not slogging through that mess, even though I 
see you replied to something I wrote.

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.




From owner-ietf@ietf.org  Wed Feb 25 10:04:40 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19408
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 10:04:40 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw0Ve-0000Ak-CY
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 09:59:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw0Uy-0000AC-FF
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 09:58:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19183
	for <ietf@ietf.org>; Wed, 25 Feb 2004 09:58:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw0Ux-0000Zd-00
	for ietf@ietf.org; Wed, 25 Feb 2004 09:58:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw0U9-0000UB-00
	for ietf@ietf.org; Wed, 25 Feb 2004 09:58:05 -0500
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1Aw0TW-0000Mk-00
	for ietf@ietf.org; Wed, 25 Feb 2004 09:57:26 -0500
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004022509544420957
 for <ietf@ietf.org>; Wed, 25 Feb 2004 09:54:44 -0500
Received: from centive.com ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 25 Feb 2004 09:53:31 -0500
Message-ID: <403CB6EB.2080907@centive.com>
Date: Wed, 25 Feb 2004 09:53:31 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: digital signature request
References: <403C0D87.31678.463FAB5@localhost> <200402250922.54777.spamtrap.ietf@dja.mailme.org>
In-Reply-To: <200402250922.54777.spamtrap.ietf@dja.mailme.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Feb 2004 14:53:31.0662 (UTC) FILETIME=[22B4AAE0:01C3FBAF]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave Aronson wrote:

>Requiring digsigs on a list would help cut down on spammers forging list 
>members' addies to spam "only members can post" lists.
>
Not necessarily.  Spam viruses would then start collecting people's 
private keys.

-- 
/================================================================\
|John Stracke      |jstracke@centive.com                         |
|Principal Engineer|http://www.centive.com                       |
|Centive           |My opinions are my own.                      |
|================================================================|
|How many roads must a man walk down before he admits he is LOST?|
\================================================================/




From owner-ietf@ietf.org  Wed Feb 25 10:36:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22281
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 10:36:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw0yg-00011a-61
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 10:29:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw0xx-00010l-4P
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 10:28:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21886
	for <ietf@ietf.org>; Wed, 25 Feb 2004 10:28:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw0xw-0003qW-00
	for ietf@ietf.org; Wed, 25 Feb 2004 10:28:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw0x9-0003m2-00
	for ietf@ietf.org; Wed, 25 Feb 2004 10:28:03 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw0wR-0003cz-00
	for ietf@ietf.org; Wed, 25 Feb 2004 10:27:19 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id 97D76EF; Wed, 25 Feb 2004 10:24:48 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
To: John Stracke <jstracke@centive.com>, ietf@ietf.org
Subject: Re: digital signature request
Date: Wed, 25 Feb 2004 10:25:33 -0500
User-Agent: KMail/1.5.2
References: <403C0D87.31678.463FAB5@localhost> <200402250922.54777.spamtrap.ietf@dja.mailme.org> <403CB6EB.2080907@centive.com>
In-Reply-To: <403CB6EB.2080907@centive.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402251025.33201.spamtrap.ietf@dja.mailme.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wed February 25 2004 09:53, John Stracke wrote:

 > Dave Aronson wrote:
 > > Requiring digsigs on a list would help cut down on spammers forging
 > > list members' addies to spam "only members can post" lists.
 >
 > Not necessarily.  Spam viruses would then start collecting people's
 > private keys.

Theoretically possible, but at least it would significantly raise the 
bar.  Also, I would suppose that the people who use digsigs (at least 
with the current level of difficulty) are mostly clueful enough to 
avoid most viruses!  B-)

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.




From owner-ietf@ietf.org  Wed Feb 25 10:59:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24076
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 10:59:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw1Kw-0001qg-7I
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 10:52:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw1KO-0001pI-Qg
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 10:52:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23692
	for <ietf@ietf.org>; Wed, 25 Feb 2004 10:52:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw1KN-0006lg-00
	for ietf@ietf.org; Wed, 25 Feb 2004 10:52:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw1Jv-0006fF-00
	for ietf@ietf.org; Wed, 25 Feb 2004 10:51:35 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw1Iy-0006Qr-00
	for ietf@ietf.org; Wed, 25 Feb 2004 10:50:36 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 4E94C61BE7; Wed, 25 Feb 2004 16:50:03 +0100 (CET)
Date: Wed, 25 Feb 2004 07:47:57 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: gnulinux@pacinfo.com, ietf@ietf.org
Subject: Re: digital signature request
Message-ID: <162445083.1077695277@localhost>
In-Reply-To: <403C0D87.31678.463FAB5@localhost>
References: <403C0D87.31678.463FAB5@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

gnulinux (now that's a verifiable identity):

please do the work yourself - collect signatures for your petition by mail 
to you, not to the list admins. They are busy trying to make next week's 
meeting work.

And please - point to working examples of lists using what you propose.

                 Harald




From owner-ietf@ietf.org  Wed Feb 25 11:06:48 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24617
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 11:06:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw1Ub-0002NP-Uo
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 11:02:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw1Ss-0002JC-Ni
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 11:00:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24129
	for <ietf@ietf.org>; Wed, 25 Feb 2004 11:00:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw1Sr-0007kW-00
	for ietf@ietf.org; Wed, 25 Feb 2004 11:00:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw1Rq-0007cD-00
	for ietf@ietf.org; Wed, 25 Feb 2004 10:59:47 -0500
Received: from mail32.messagelabs.com ([62.173.108.211])
	by ietf-mx with smtp (Exim 4.12)
	id 1Aw1Qq-0007SP-00
	for ietf@ietf.org; Wed, 25 Feb 2004 10:58:45 -0500
X-VirusChecked: Checked
X-Msg-Ref: server-8.tower-32.messagelabs.com!1077724688!8077460
X-StarScan-Version: 5.1.15; banners=.,-,-
Received: (qmail 9607 invoked from network); 25 Feb 2004 15:58:12 -0000
Received: from smtpout10.orange.co.uk (HELO hagrid.orange.co.uk) (193.35.135.133)
  by server-8.tower-32.messagelabs.com with SMTP; 25 Feb 2004 15:58:12 -0000
Received: from mail32.messagelabs.com (mail32.messagelabs.com) by hagrid.orange.co.uk
 (Content Technologies SMTPRS 4.3.10) with SMTP id <T67f9bc162bc12387853b4@hagrid.orange.co.uk> for <amish.chana@orange.co.uk>;
 Wed, 25 Feb 2004 15:38:04 +0000
X-VirusChecked: Checked
X-Env-Sender: owner-ietf@ietf.org
X-Msg-Ref: server-23.tower-32.messagelabs.com!1077723480!3731896
X-StarScan-Version: 5.1.15; banners=-,-,-
X-SpamReason: No, hits=-5.0 required=7.0 tests=CYNIC_B_GOOD
Received: (qmail 14265 invoked from network); 25 Feb 2004 15:38:00 -0000
Received: from asgard.ietf.org (132.151.6.40)
  by server-23.tower-32.messagelabs.com with SMTP; 25 Feb 2004 15:38:00 -0000
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw0yg-00011a-61
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 10:29:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw0xx-00010l-4P
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 10:28:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21886
	for <ietf@ietf.org>; Wed, 25 Feb 2004 10:28:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw0xw-0003qW-00
	for ietf@ietf.org; Wed, 25 Feb 2004 10:28:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw0x9-0003m2-00
	for ietf@ietf.org; Wed, 25 Feb 2004 10:28:03 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw0wR-0003cz-00
	for ietf@ietf.org; Wed, 25 Feb 2004 10:27:19 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id 97D76EF; Wed, 25 Feb 2004 10:24:48 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
To: John Stracke <jstracke@centive.com>, ietf@ietf.org
Subject: Re: digital signature request
Date: Wed, 25 Feb 2004 10:25:33 -0500
User-Agent: KMail/1.5.2
References: <403C0D87.31678.463FAB5@localhost> <200402250922.54777.spamtrap.ietf@dja.mailme.org> <403CB6EB.2080907@centive.com>
In-Reply-To: <403CB6EB.2080907@centive.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402251025.33201.spamtrap.ietf@dja.mailme.org>
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wed February 25 2004 09:53, John Stracke wrote:

 > Dave Aronson wrote:
 > > Requiring digsigs on a list would help cut down on spammers forging
 > > list members' addies to spam "only members can post" lists.
 >
 > Not necessarily.  Spam viruses would then start collecting people's
 > private keys.

Theoretically possible, but at least it would significantly raise the 
bar.  Also, I would suppose that the people who use digsigs (at least 
with the current level of difficulty) are mostly clueful enough to 
avoid most viruses!  B-)

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.



______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________



From owner-ietf@ietf.org  Wed Feb 25 11:12:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25482
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 11:12:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw1aP-0002pe-Vy
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 11:08:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw1Ws-0002S8-JB
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 11:04:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24453
	for <ietf@ietf.org>; Wed, 25 Feb 2004 11:04:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw1Wr-0000VL-00
	for ietf@ietf.org; Wed, 25 Feb 2004 11:04:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw1Vq-0000Lq-00
	for ietf@ietf.org; Wed, 25 Feb 2004 11:03:55 -0500
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1Aw1VA-0000Bb-00
	for ietf@ietf.org; Wed, 25 Feb 2004 11:03:12 -0500
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004022510290221047
 for <ietf@ietf.org>; Wed, 25 Feb 2004 10:29:02 -0500
Received: from centive.com ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 25 Feb 2004 10:27:49 -0500
Message-ID: <403CBEF4.6010104@centive.com>
Date: Wed, 25 Feb 2004 10:27:48 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: digital signature request
References: <403C0D87.31678.463FAB5@localhost> <200402250922.54777.spamtrap.ietf@dja.mailme.org> <403CB6EB.2080907@centive.com> <200402251025.33201.spamtrap.ietf@dja.mailme.org>
In-Reply-To: <200402251025.33201.spamtrap.ietf@dja.mailme.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Feb 2004 15:27:49.0556 (UTC) FILETIME=[ED4E5F40:01C3FBB3]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave Aronson wrote:

>On Wed February 25 2004 09:53, John Stracke wrote:
>
> > Not necessarily.  Spam viruses would then start collecting people's
> > private keys.
>
>Theoretically possible, but at least it would significantly raise the 
>bar.
>
Only one person needs to figure out how to do it.  Think script kiddies.

-- 
/=================================================================\
|John Stracke      |jstracke@centive.com                          |
|Principal Engineer|http://www.centive.com                        |
|Centive           |My opinions are my own.                       |
|=================================================================|
|"So we've strapped a Patriot missile onto Snorky here." "You said|
|that was a PROP!" "It's a *functional* prop." -- What's New, by  |
|Phil Foglio.                                                     |
\=================================================================/




From owner-ietf@ietf.org  Wed Feb 25 11:41:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27954
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 11:41:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw21W-000463-47
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 11:36:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw20u-00044N-MV
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 11:36:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27677
	for <ietf@ietf.org>; Wed, 25 Feb 2004 11:35:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw20t-0005dp-00
	for ietf@ietf.org; Wed, 25 Feb 2004 11:35:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw20B-0005Xx-00
	for ietf@ietf.org; Wed, 25 Feb 2004 11:35:16 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw1zR-0005Lx-00
	for ietf@ietf.org; Wed, 25 Feb 2004 11:34:29 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id 622A9F0; Wed, 25 Feb 2004 11:31:58 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
To: John Stracke <jstracke@centive.com>, ietf@ietf.org
Subject: Re: digital signature request
Date: Wed, 25 Feb 2004 11:32:41 -0500
User-Agent: KMail/1.5.2
References: <403C0D87.31678.463FAB5@localhost> <200402251025.33201.spamtrap.ietf@dja.mailme.org> <403CBEF4.6010104@centive.com>
In-Reply-To: <403CBEF4.6010104@centive.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402251132.41602.spamtrap.ietf@dja.mailme.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wed February 25 2004 10:27, John Stracke wrote:
 > Dave Aronson wrote:
 > >On Wed February 25 2004 09:53, John Stracke wrote:
 > > > Not necessarily.  Spam viruses would then start collecting
 > > > people's private keys.
 > >
 > > Theoretically possible, but at least it would significantly raise
 > > the bar.
 >
 > Only one person needs to figure out how to do it.  Think script
 > kiddies.

True again, but I still don't think that this additional usage of 
private keys would provide sufficient incentive for a virus author.  
What do they gain out of snarfing someone's private key, that they 
wouldn't gain without this proposal?  (For those tuning in late, it has 
unfortunately been pushed off the top, but boils down to mailing list 
processors being able to require and verify digital signatures on 
members' posts.)  It nets them the ability to spam digsig-protected 
mailing lists that the victim is on, until the victim cleans out the 
infection and changes his key.  BFD.  I suppose some twerp might do so 
just because he can, but I don't think this will provide the incentive.

Admittedly, there are *other* existing incentives, and will probably be 
more as digitally signed and/or encrypted email becomes more popular 
and easier to use, but that's a whole 'nother story.  These other 
incentives may cause such a virus to be written, and this mechanism may 
suffer as a result.

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.




From owner-ietf@ietf.org  Wed Feb 25 11:55:58 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29146
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 11:55:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw2F4-0004m3-5U
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 11:50:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw2Dr-0004jY-Em
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 11:49:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28778
	for <ietf@ietf.org>; Wed, 25 Feb 2004 11:49:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw2Dq-0007Hk-00
	for ietf@ietf.org; Wed, 25 Feb 2004 11:49:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw2D0-00079C-00
	for ietf@ietf.org; Wed, 25 Feb 2004 11:48:30 -0500
Received: from 142.red-213-98-19.pooles.rima-tde.net ([213.98.19.142] helo=torrente.camerfirma.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw2CB-0006zj-00
	for ietf@ietf.org; Wed, 25 Feb 2004 11:47:39 -0500
Received: (qmail 2990 invoked from network); 25 Feb 2004 16:47:37 -0000
Received: from unknown (HELO PORTATILRAMIRO) ([192.0.0.41])
          (envelope-sender <ramirom@camerfirma.com>)
          by torrente.camerfirma.com (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 25 Feb 2004 16:47:37 -0000
From: =?iso-8859-1?Q?Ramiro_Mu=F1oz_Mu=F1oz?= <ramirom@camerfirma.com>
To: "'John Stracke'" <jstracke@centive.com>, <ietf@ietf.org>
Subject: RE: digital signature request
Date: Wed, 25 Feb 2004 17:47:34 +0100
Message-ID: <006101c3fbbf$116c2050$290000c0@PORTATILRAMIRO>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <403CB6EB.2080907@centive.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


Depend where the private key are, and this option at least will be a
barrier to spammers.

Ramiro Mu=F1oz
AC Camerfirma SA

-----Mensaje original-----
De: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] En nombre de John
Stracke
Enviado el: mi=E9rcoles, 25 de febrero de 2004 15:54
Para: ietf@ietf.org
Asunto: Re: digital signature request


Dave Aronson wrote:

>Requiring digsigs on a list would help cut down on spammers forging=20
>list
>members' addies to spam "only members can post" lists.
>
Not necessarily.  Spam viruses would then start collecting people's=20
private keys.

--=20
/=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D\
|John Stracke      |jstracke@centive.com                         |
|Principal Engineer|http://www.centive.com                       |
|Centive           |My opinions are my own.                      |
|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D|
|How many roads must a man walk down before he admits he is LOST?|
\=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D/






From owner-ietf@ietf.org  Wed Feb 25 11:59:53 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29467
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 11:59:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw2Hx-0004pS-L1
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 11:53:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw2HB-0004o3-Op
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 11:52:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28946
	for <ietf@ietf.org>; Wed, 25 Feb 2004 11:52:47 -0500 (EST)
From: gnulinux@pacinfo.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw2HA-0007fe-00
	for ietf@ietf.org; Wed, 25 Feb 2004 11:52:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw2GF-0007Zb-00
	for ietf@ietf.org; Wed, 25 Feb 2004 11:51:52 -0500
Received: from cougar.pacinfo.com ([12.7.120.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw2FO-0007Tg-00
	for ietf@ietf.org; Wed, 25 Feb 2004 11:50:58 -0500
Received: from w2ksp2 (dsl-db.pacinfo.com [12.7.123.20])
	by cougar.pacinfo.com (8.12.10/8.12.10) with ESMTP id i1PGso3I020447;
	Wed, 25 Feb 2004 08:54:50 -0800
To: Dave Aronson <spamtrap.ietf@dja.mailme.org>, ietf@ietf.org
Date: Wed, 25 Feb 2004 08:50:44 -0800
MIME-Version: 1.0
Subject: Re: digital signature request
Reply-to: gnulinux@pacinfo.com
Message-ID: <403C61E4.12037.58354C@localhost>
In-reply-to: <200402250922.54777.spamtrap.ietf@dja.mailme.org>
References: <403C0D87.31678.463FAB5@localhost>
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

On 25 Feb 2004 at 9:22, Dave Aronson wrote:

> On Wed February 25 2004 05:50, gnulinux@pacinfo.com wrote:
> 
>  > i'm
>  > spending way too much of my time culling spam from
>  > my real email even though i'm employing the latest
>  > spam filtering tools.
> 
> Having the latest tools means nothing, unless they are used right.  Are 

i'm using them correctly

>  > mailing lists could use the same recipe, no
>  > messages would be handed over to the listserv
>  > software unless it was signed by a whitelisted
>  > signature.
> 
> Requiring digsigs on a list would help cut down on spammers forging list 
> members' addies to spam "only members can post" lists.  Also, this is 
> one of the few lists where I'd think most people would be clueful 
> enough to do it.
> 
> However, would it be worth the bother?  Unless there's some poor sod 

if it wasn't clear, having list members sign messages 
in order to post isn't my request.  it was just a 
comment about an additional possibility.

> Here's an alternate angle for you to chew on.  Try coming up with some 
> sort of mechanism that could easily be built into all MUAs, MTAs, 
> mailing list managers, anti-spam "solutions", and all other programs 

designing a complex total solution isn't an approach 
that works for me.  in my experience small foolproof 
steps in the direction of my vision have proven to be 
much more fruitful.

>  > apologies
>  > to the folks whose comments i'm replying to for
>  > not referencing their names (i didn't have the
>  > time).
> 
> You ask us to take the time to implement a new mechanism of dubious 
> value.

the value in having the list processor sign all posts 
is simple.  guaranteed identification of the list 
traffic for any recipient who decides to verify 
signatures.  

> Meanwhile, you won't take the time to mention ournames so that
> we can at least go quickly to the part of your email that concerns us, 
> nor break it up into individual pieces so as to at least preserve the 
> subject lines.  Talk about cooperating....

the posts i was replying to were part of lengthy 
threads around the same issue.  my intention was to 
collect various concerns and reply to them to help 
elucidate my perspective.  it was more efficient than 
trying to write commentary from scratch that covered 
all the same points.  i wasn't looking for specific 
dialogue with particular posters.  just wanted to use 
the existing dialogue to create a summary of sorts.

if you look you should notice that i did create three 
sections (for the three different threads i pulled 
posts from):

thread:  ietf - proposal for built-in spam burden
& email privacy protection
-----

thread:  ietf - how not to filter spam
-----

thread:  tidbits - digital signatures in tidbits
-----

the quotes under each section are taken from those 
particular threads.

> As for the lengthy conglomeration of your replies to other messages, 
> forget it, I for one am not slogging through that mess, even though I 
> see you replied to something I wrote.

sorry you found the structure of my post unhelpful.  i 
did attempt to make it easy to peruse.  if it's not 
too much trouble i do request that you browse through 
the rest of my post.  i am very much wanting dialogue 
around the issue of having the list digitally signed 
by the list processor.

peace,

david




From owner-ietf@ietf.org  Wed Feb 25 12:21:05 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00985
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 12:21:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw2g9-0006DH-H6
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 12:18:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw2fP-0006Ax-7c
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 12:17:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00838
	for <ietf@ietf.org>; Wed, 25 Feb 2004 12:17:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw2fO-0002sq-00
	for ietf@ietf.org; Wed, 25 Feb 2004 12:17:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw2eP-0002mU-00
	for ietf@ietf.org; Wed, 25 Feb 2004 12:16:50 -0500
Received: from maynard.mail.mindspring.net ([207.69.200.243])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw2df-0002gX-00
	for ietf@ietf.org; Wed, 25 Feb 2004 12:16:03 -0500
Received: from h-66-167-50-4.atlngahp.dynamic.covad.net ([66.167.50.4] helo=primate)
	by maynard.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 1Aw2de-0003UR-00
	for ietf@ietf.org; Wed, 25 Feb 2004 12:16:02 -0500
From: "Neil Carpenter" <primate@mindspring.com>
To: <ietf@ietf.org>
Subject: RE: digital signature request
Date: Wed, 25 Feb 2004 12:16:01 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <403C61E4.12037.58354C@localhost>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Thread-Index: AcP7vzovxWGyXMCVQcS1C+8iHy9LeAAA0cGA
Message-Id: <E1Aw2de-0003UR-00@maynard.mail.mindspring.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>the value in having the list processor sign all posts 
>is simple.  guaranteed identification of the list 
>traffic for any recipient who decides to verify 
>signatures.  

This seems to solve a non-problem.  Unless there are spam messages that
where the sender has, for instance, forged the existing "Sender:
owner-ietf@ietf.org" header, signing these messages will add nothing of
value.  It seems much more likely that a spammer would simply send e-mail to
the ietf@ietf.org list & allow the list itself to propagate it than that
they would specifically forge that header.




From owner-ietf@ietf.org  Wed Feb 25 12:41:32 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02057
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 12:41:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw2yd-0007Mi-8E
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 12:37:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw2xq-0007Lf-Q3
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 12:36:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01859
	for <ietf@ietf.org>; Wed, 25 Feb 2004 12:36:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw2xp-0004u3-00
	for ietf@ietf.org; Wed, 25 Feb 2004 12:36:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw2wu-0004pd-00
	for ietf@ietf.org; Wed, 25 Feb 2004 12:35:57 -0500
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.sea)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw2wR-0004kW-00
	for ietf@ietf.org; Wed, 25 Feb 2004 12:35:27 -0500
Received: from ssprunk (ip145.post-vineyard.dfw.ygnition.net [66.135.181.145])
	by ns2.sea (8.12.11/8.12.5) with SMTP id i1PHYnvR025130;
	Wed, 25 Feb 2004 09:34:50 -0800
Message-ID: <00e901c3fbc5$ae41c1e0$6401a8c0@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <gnulinux@pacinfo.com>, "Dave Aronson" <spamtrap.ietf@dja.mailme.org>
Cc: <ietf@ietf.org>
References: <403C0D87.31678.463FAB5@localhost> <403C61E4.12037.58354C@localhost>
Subject: Re: digital signature request
Date: Wed, 25 Feb 2004 11:26:04 -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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake <gnulinux@pacinfo.com>
> >  > apologies to the folks whose comments i'm replying to for
> >  > not referencing their names (i didn't have the time).
> >
> > You ask us to take the time to implement a new mechanism of dubious
> > value.
>
> the value in having the list processor sign all posts
> is simple.  guaranteed identification of the list
> traffic for any recipient who decides to verify
> signatures.

You have yet to demonstrate the problem you are trying to solve even exists.

I've gotten over 2700 spams this month, and zero of them have "ietf"
anywhere in them, either header or body.  Thus, I see no compelling reason
for the ietf's list software to sign anything when a simple MUA filter on
the Sender: line already achieves 100% accuracy.

S

Stephen Sprunk        "Stupid people surround themselves with smart
CCIE #3723           people.  Smart people surround themselves with
K5SSS         smart people who disagree with them."  --Aaron Sorkin




From owner-ietf@ietf.org  Wed Feb 25 13:06:07 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00988
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 12:21:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw2dG-00068U-FE
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 12:15:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw2bX-000661-1I
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 12:13:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00511
	for <ietf@ietf.org>; Wed, 25 Feb 2004 12:13:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw2bW-0002TZ-00
	for ietf@ietf.org; Wed, 25 Feb 2004 12:13:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw2aX-0002NO-00
	for ietf@ietf.org; Wed, 25 Feb 2004 12:12:50 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw2Ze-0002EM-00
	for ietf@ietf.org; Wed, 25 Feb 2004 12:11:54 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id 1E079F0; Wed, 25 Feb 2004 12:09:23 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
To: gnulinux@pacinfo.com, ietf@ietf.org
Subject: Re: digital signature request
Date: Wed, 25 Feb 2004 12:10:07 -0500
User-Agent: KMail/1.5.2
References: <403C0D87.31678.463FAB5@localhost> <403C61E4.12037.58354C@localhost>
In-Reply-To: <403C61E4.12037.58354C@localhost>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402251210.07756.spamtrap.ietf@dja.mailme.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wed February 25 2004 11:50, gnulinux@pacinfo.com wrote:

 > if it's not
 > too much trouble i do request that you browse through
 > the rest of my post.

Already deleted, and I can't be arsed to go trash-digging right now.

 > i am very much wanting dialogue
 > around the issue of having the list digitally signed
 > by the list processor.

Okay, my three cents (inflation):

If the folks who actually run the list find themselves a spare moment to 
breathe (not likely so soon before or after the meeting in Korea), it 
might be fairly easy to implement.

However, what does it gain us?  Authentication that the message in 
question, was indeed sent via the IETF list.  What does THAT gain us?  
The ability to separate it out from the spam.  (Note also the 
assumption that anything sent to, or at least received from, the IETF 
list is NOT spam.  That may hold for this list, but certainly not for 
all.)

On the other claw, using the Sender line for that purpose has been 
working just fine for me.  (It's forgeable, sure, but I see no sign 
that spammers have bothered to do so, and don't think it's likely that 
they will in the future.)  That's also trivial to set up in any decent 
MUA.  Same holds for the List-ID, X-Been-There, and other markers used 
by most other mailing lists.  Most cannot filter so easily (or at all) 
on the presence/absence or [in]validity of a digsig.  Sure, advanced 
tools such as procmail certainly can, but many of us don't even find it 
necessary to use such things at ALL yet, and they're awfully difficult 
for Joe Luser to set up for his mail from RANDOM-L.

Zero net gain, for at least some (and likely much) additional effort.  
Why bother?

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.




From owner-ietf@ietf.org  Wed Feb 25 14:18:28 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06214
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 14:18:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw4Ob-0001g0-73
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 14:08:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw4O3-0001eN-U3
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 14:08:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05723
	for <ietf@ietf.org>; Wed, 25 Feb 2004 14:08:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw4O2-0006Ay-00
	for ietf@ietf.org; Wed, 25 Feb 2004 14:08:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw4N6-00066J-00
	for ietf@ietf.org; Wed, 25 Feb 2004 14:07:05 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw4Mq-00061L-00
	for ietf@ietf.org; Wed, 25 Feb 2004 14:06:48 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1PJ6jZE052093
	for ietf@ietf.org env-from <vjs>;
	Wed, 25 Feb 2004 12:06:45 -0700 (MST)
Date: Wed, 25 Feb 2004 12:06:45 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402251906.i1PJ6jZE052093@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: digital signature request
References: <403C61E4.12037.58354C@localhost>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: gnulinux@pacinfo.com

> ...
> > Having the latest tools means nothing, unless they are used right.  Are 
>
> i'm using them correctly

I, for one, am unconvinced.  I have had no trouble filtering unwanted
mail from this list, thanks to procmail.  My various filters have no
trouble dealing with more than 99.9% of the unsolicited bulk mail
including viruses and worms directed at my mailbox.  For my mail, my
filters have a total false positive rate (legitimate rejected divided
by total legitimate) of less than 0.1%.  Whether your filters are doing
as well as you want them to does not seem like a concern of the IETF.

> ...
> the value in having the list processor sign all posts 
> is simple.  guaranteed identification of the list 
> traffic for any recipient who decides to verify 
> signatures.  

I think it would be simpler for all concerned and in this case just
as effective if the IETF list processor would offer to do SMTP-TLS and
for an appropriate cert to be published on http://ietf.org/

However, I would not suggesting that for any practical or operational
reason.  It would merely set a good example. 


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Wed Feb 25 14:58:04 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08616
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 14:58:04 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw568-000350-UD
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 14:53:36 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw54f-00031r-71
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 14:52:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08309
	for <ietf@ietf.org>; Wed, 25 Feb 2004 14:52:03 -0500 (EST)
From: gnulinux@pacinfo.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw54d-000335-00
	for ietf@ietf.org; Wed, 25 Feb 2004 14:52:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw53s-0002y7-00
	for ietf@ietf.org; Wed, 25 Feb 2004 14:51:17 -0500
Received: from cougar.pacinfo.com ([12.7.120.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw53F-0002rb-00
	for ietf@ietf.org; Wed, 25 Feb 2004 14:50:37 -0500
Received: from w2ksp2 (dsl-db.pacinfo.com [12.7.123.20])
	by cougar.pacinfo.com (8.12.10/8.12.10) with ESMTP id i1PJsV3I025762;
	Wed, 25 Feb 2004 11:54:31 -0800
To: Dave Aronson <spamtrap.ietf@dja.mailme.org>, ietf@ietf.org
Date: Wed, 25 Feb 2004 11:50:24 -0800
MIME-Version: 1.0
Subject: Re: digital signature request
Reply-to: gnulinux@pacinfo.com
Message-ID: <403C8C00.13469.FCB2CB@localhost>
In-reply-to: <200402251210.07756.spamtrap.ietf@dja.mailme.org>
References: <403C61E4.12037.58354C@localhost>
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

On 25 Feb 2004 at 12:10, Dave Aronson wrote:

> On Wed February 25 2004 11:50, gnulinux@pacinfo.com wrote:
> 
>  > i am very much wanting dialogue
>  > around the issue of having the list digitally signed
>  > by the list processor.
> 
> If the folks who actually run the list find themselves a spare moment to 
> breathe (not likely so soon before or after the meeting in Korea), it 
> might be fairly easy to implement.
> 
> However, what does it gain us?  Authentication that the message in 
> question, was indeed sent via the IETF list.  What does THAT gain us?  
> The ability to separate it out from the spam.  (Note also the 
> assumption that anything sent to, or at least received from, the IETF 
> list is NOT spam.  That may hold for this list, but certainly not for 
> all.)

my intention is to move in the direction of accepting 
only signed email.  this will allow me to route 
anything that doesn't include a whitelisted signature 
to /dev/null.  that's what having the list signed will 
gain me.

FYI, i made no assumption that a signed list would not 
contain spam.  in fact, i would be surprised if it did 
not.

> On the other claw, using the Sender line for that purpose has been 
> working just fine for me.  (It's forgeable, sure, but I see no sign 
> that spammers have bothered to do so, and don't think it's likely that 
> they will in the future.)  That's also trivial to set up in any decent 
> MUA.  Same holds for the List-ID, X-Been-There, and other markers used 
> by most other mailing lists.  Most cannot filter so easily (or at all) 
> on the presence/absence or [in]validity of a digsig.  Sure, advanced 
> tools such as procmail certainly can, but many of us don't even find it 
> necessary to use such things at ALL yet, and they're awfully difficult 
> for Joe Luser to set up for his mail from RANDOM-L.

if signature validation is positioned at the mail 
server level then the tools you mentioned above can 
still be used.  signature validation at the mail 
server level can add a header line to indicate 
signature validation status.  additionally, if 
signature validation is located at the mail server 
level you might also choose to route all unwhitelisted 
mail to /dev/null so you don't have to download it.

> Zero net gain, for at least some (and likely much) additional effort.  
> Why bother?

again, for me a significant gain, and i perceive that 
generating a key pair and configuring automatic 
signing of all list traffic will require a minor 
amount of effort.

david



From owner-ietf@ietf.org  Wed Feb 25 15:33:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12134
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 15:33:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw5d2-0004ER-7j
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 15:27:36 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw5cP-0004CN-7D
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 15:26:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11667
	for <ietf@ietf.org>; Wed, 25 Feb 2004 15:26:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw5cO-0007Eq-00
	for ietf@ietf.org; Wed, 25 Feb 2004 15:26:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw5bP-00077x-00
	for ietf@ietf.org; Wed, 25 Feb 2004 15:25:56 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw5aR-0006x7-00
	for ietf@ietf.org; Wed, 25 Feb 2004 15:24:55 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id 0C5594D; Wed, 25 Feb 2004 15:22:24 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
To: gnulinux@pacinfo.com, ietf@ietf.org
Subject: Re: digital signature request
Date: Wed, 25 Feb 2004 15:23:08 -0500
User-Agent: KMail/1.5.2
References: <403C61E4.12037.58354C@localhost> <403C8C00.13469.FCB2CB@localhost>
In-Reply-To: <403C8C00.13469.FCB2CB@localhost>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402251523.08975.spamtrap.ietf@dja.mailme.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wed February 25 2004 14:50, gnulinux@pacinfo.com wrote:
 > On 25 Feb 2004 at 12:10, Dave Aronson wrote:

 > > However, what does it gain us?  Authentication that the message in
 > > question, was indeed sent via the IETF list.  What does THAT gain
 > > us? The ability to separate it out from the spam.  (Note also the
 > > assumption that anything sent to, or at least received from, the
 > > IETF list is NOT spam.  That may hold for this list, but certainly
 > > not for all.)
 >
 > my intention is to move in the direction of accepting
 > only signed email.  this will allow me to route
 > anything that doesn't include a whitelisted signature
 > to /dev/null.  that's what having the list signed will
 > gain me.

That's what it gains *you individually*, because of *your* specific 
plans.  But that's not what the IETF is about.  What does it gain J. 
Random Luser, or even any notable fraction of the users or 
organizations on the net?  Nothing.  What does it even gain the extant 
subscribers of this precise list?  Again, nothing.

 > FYI, i made no assumption that a signed list would not
 > contain spam.  in fact, i would be surprised if it did
 > not.

Then the whole deal gains you next to nothing as a spam filter either.  
The whole deal gains you *only* the benefit of being one step further 
towards your goal of having your current legitimate contacts send you 
email with whitelisted digsigs.  Of course, any NEW contacts will be a 
whole 'nother story.

 > if signature validation is positioned at the mail
 > server level then the tools you mentioned above can
 > still be used.  signature validation at the mail
 > server level can add a header line to indicate
 > signature validation status.  additionally, if
 > signature validation is located at the mail server
 > level you might also choose to route all unwhitelisted
 > mail to /dev/null so you don't have to download it.

I still don't think it's going to be worthwhile, but at least this 
sounds technically feasible, though I doubt many ISPs would be willing 
spend the extra cycles to check sigs for you.  Go to the appropriate 
Working Group, discuss the concept, find out if any related work has 
yet been done, and come up with a draft telling us exactly what this 
header should say, how anything else would have to modified to deal 
with it, the security implications (don't forget about forgeability of 
the header lines), etc.  You may even get it accepted as an RFC, 'cuz 
with that approach, it sounds like there MAY be some benefits to SOME 
of the people whose email servers do such a thing, especially if 
someone runs a server where all the accounts expect to receive only 
properly signed emails.  But even so, don't expect everyone, let alone 
the IETF, to start signing their outbound email.

To get you started, here's what pops into my pointy little head:

The final MTA will be responsible for signature checking.  All other 
MTAs in the chain will not create nor, if somehow present, alter the 
header line.  The final MTA will insert 
"X-Signature-Verification-Status: $VERSION $FINGERPRINT $STATUS".  
$VERSION is a non-negative integer denoting the version number of the 
header line.  This is version 0.  Later versions may only add to 
previous versions; removing items is prohibited, so as to maintain 
backward compatibility.  $FINGERPRINT is the fingerprint of the key 
used.  $STATUS is "Success", "Failure", "Unsigned", or "Forged 
$OLDSTATUS".  $OLDSTATUS is again any of the above, recursively.  A 
"Forged" status indicates that the message arrived with an 
X-Signature-Verification-Status line already in it, with a $STATUS of 
$OLDSTATUS.  I cannot think of any reason why this would be legitimate; 
if you can, feel free to use a different indicator, but methinks it 
should still be indicated.  This scheme might be doable by simply 
passing the email through an add-on, rather than modding the MTA 
itself.  The MUA, when receiving or sorting mail, could filter on that 
header line the same way as any other.  This includes whitelisting (or 
blacklisting!) various key fingerprints.

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.




From owner-ietf@ietf.org  Wed Feb 25 15:34:34 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12206
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 15:34:34 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw5hs-0004LW-2a
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 15:32:36 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw5hg-0004K7-6s
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 15:32:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12050
	for <ietf@ietf.org>; Wed, 25 Feb 2004 15:32:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw5he-00009P-00
	for ietf@ietf.org; Wed, 25 Feb 2004 15:32:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw5go-00000c-00
	for ietf@ietf.org; Wed, 25 Feb 2004 15:31:30 -0500
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 1Aw5fq-0007am-00
	for ietf@ietf.org; Wed, 25 Feb 2004 15:30:31 -0500
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 i1PKOVa25919
	for <ietf@ietf.org>; Wed, 25 Feb 2004 12:24:31 -0800
Date: Wed, 25 Feb 2004 12:24:30 -0800 (PST)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
Subject: Re: digital signature request
In-Reply-To: <200402251025.33201.spamtrap.ietf@dja.mailme.org>
Message-ID: <Pine.LNX.4.33.0402251222400.25710-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk



On Wed, 25 Feb 2004, Dave Aronson wrote:

> On Wed February 25 2004 09:53, John Stracke wrote:
>
>  > Dave Aronson wrote:
>  > > Requiring digsigs on a list would help cut down on spammers forging
>  > > list members' addies to spam "only members can post" lists.
>  >
>  > Not necessarily.  Spam viruses would then start collecting people's
>  > private keys.
>
> Theoretically possible, but at least it would significantly raise the
> bar.  Also, I would suppose that the people who use digsigs (at least
> with the current level of difficulty) are mostly clueful enough to
> avoid most viruses!  B-)

It also supposes that the private keys aren't protected with a passphrase.
The applications I use which use a pp key pair insist on a pass phrase.
Such protection will make bothering to collect private keys quite a bit
less interesting.

Dave Morris




From owner-ietf@ietf.org  Wed Feb 25 15:43:42 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13029
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 15:43:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw5pc-0005Mu-4x
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 15:40:36 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw5p5-0005Ju-N6
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 15:40:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12889
	for <ietf@ietf.org>; Wed, 25 Feb 2004 15:40:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw5p4-0001Mk-00
	for ietf@ietf.org; Wed, 25 Feb 2004 15:40:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw5oX-0001IV-00
	for ietf@ietf.org; Wed, 25 Feb 2004 15:39:30 -0500
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1Aw5nu-00018i-00
	for ietf@ietf.org; Wed, 25 Feb 2004 15:38:50 -0500
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004022515364500159
 for <ietf@ietf.org>; Wed, 25 Feb 2004 15:36:45 -0500
Received: from centive.com ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 25 Feb 2004 15:34:57 -0500
Message-ID: <403D06F0.8000608@centive.com>
Date: Wed, 25 Feb 2004 15:34:56 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: digital signature request
References: <Pine.LNX.4.33.0402251222400.25710-100000@egate.xpasc.com>
In-Reply-To: <Pine.LNX.4.33.0402251222400.25710-100000@egate.xpasc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Feb 2004 20:34:57.0428 (UTC) FILETIME=[D52C7D40:01C3FBDE]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

David Morris wrote:

>It also supposes that the private keys aren't protected with a passphrase.
>  
>
Nope.  All you need is a keystroke monitor.

-- 
/================================================\
|John Stracke      |jstracke@centive.com         |
|Principal Engineer|http://www.centive.com       |
|Centive           |My opinions are my own.      |
|================================================|
|I'm not imaginary. I'm ontologically challenged.|
\================================================/




From owner-ietf@ietf.org  Wed Feb 25 16:23:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15436
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 16:23:16 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw6QN-0006qR-OK
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 16:18:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw6Ot-0006nT-O0
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 16:17:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15076
	for <ietf@ietf.org>; Wed, 25 Feb 2004 16:17:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw6Os-0005Mn-00
	for ietf@ietf.org; Wed, 25 Feb 2004 16:17:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw6Ny-0005Hp-00
	for ietf@ietf.org; Wed, 25 Feb 2004 16:16:07 -0500
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw6NZ-0005Cg-00
	for ietf@ietf.org; Wed, 25 Feb 2004 16:15:42 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1PLFBMN028275
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 25 Feb 2004 16:15:12 -0500
Date: Wed, 25 Feb 2004 16:15:11 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: gnulinux@pacinfo.com
cc: ietf@ietf.org
Subject: Re: digital signature request
In-Reply-To: <403C0D87.31678.463FAB5@localhost>
Message-ID: <Pine.LNX.4.44.0402251610580.25194-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 25 Feb 2004 gnulinux@pacinfo.com wrote:

> this is a request for this list to be digitally
> signed by the list processor.

> i'm making this request because i need a way to
> positively id the messages from this list.  i'm
> spending way too much of my time culling spam from
> my real email even though i'm employing the latest
> spam filtering tools.  

There isn't any relation between "positively identifying the messages to 
this list", and "time spent culling spam".

Since there isn't any connection, being able to positively identify 
messages to the list won't save you any time culling spam.

> please give me the one
> simple tool i know of that will allow me to
> positively differentiate the mail from this list
> from all others - a digital signature.

There are many ways to reasonably accurately identify mail to this list 
and distinguish it from all others: It is sent "to: ietf@ietf.org".

I haven't seen very much spam that has that characteristic, so I don't 
think such spam is much of a problem, if any problem at all.

		--Dean




From owner-ietf@ietf.org  Wed Feb 25 16:43:13 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16657
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 16:43:13 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw6il-0007gI-J7
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 16:37:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw6iC-0007f6-Ty
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 16:37:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16401
	for <ietf@ietf.org>; Wed, 25 Feb 2004 16:36:58 -0500 (EST)
From: gnulinux@pacinfo.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw6iB-0007ab-00
	for ietf@ietf.org; Wed, 25 Feb 2004 16:36:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw6hH-0007VQ-00
	for ietf@ietf.org; Wed, 25 Feb 2004 16:36:04 -0500
Received: from cougar.pacinfo.com ([12.7.120.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw6gN-0007PN-00
	for ietf@ietf.org; Wed, 25 Feb 2004 16:35:07 -0500
Received: from w2ksp2 (dsl-db.pacinfo.com [12.7.123.20])
	by cougar.pacinfo.com (8.12.10/8.12.10) with ESMTP id i1PLd73I028328
	for <ietf@ietf.org>; Wed, 25 Feb 2004 13:39:07 -0800
To: ietf@ietf.org
Date: Wed, 25 Feb 2004 13:35:00 -0800
MIME-Version: 1.0
Subject: RE: digital signature request
Reply-to: gnulinux@pacinfo.com
Message-ID: <403CA484.14977.15C7746@localhost>
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

On 25 Feb 2004 at 12:16, Neil Carpenter wrote:

> > the value in having the list processor sign all posts
> > is simple.  guaranteed identification of the list
> > traffic for any recipient who decides to verify
> > signatures.
> 
> This seems to solve a non-problem.  Unless there are spam messages that
> where the sender has, for instance, forged the existing "Sender:
> owner-ietf@ietf.org" header, signing these messages will add nothing of
> value.  It seems much more likely that a spammer would simply send
> e-mail to the ietf@ietf.org list & allow the list itself to propagate it
> than that they would specifically forge that header.

again, i'm not imagining that having the list 
processor sign all mail will stop spam from entering 
the list.  the problem i need to solve is how to stop 
spam from being sent *directly* to me.  accepting only 
email with whitelisted signatures will solve my 
problem.

btw, i thought you needed to be subscribed to the ietf 
list prior to being able to post to the ietf list?

On 25 Feb 2004 at 11:26, Stephen Sprunk wrote:

> You have yet to demonstrate the problem you are trying to solve even
> exists.
> 
> I've gotten over 2700 spams this month, and zero of them have "ietf"
> anywhere in them, either header or body.  Thus, I see no compelling
> reason for the ietf's list software to sign anything when a simple MUA
> filter on the Sender: line already achieves 100% accuracy.

see above response.  also, from my perspective digital 
signature verification is simpler than maintaining a 
filter list.  i'm tired of the spam/anti-spam arms 
race.  i'm going to deploy a solution that is 
unspoofable.

On 25 Feb 2004 at 12:06, Vernon Schryver wrote:

> > From: gnulinux@pacinfo.com
> >
> > > Having the latest tools means nothing, unless
> > > they are used right.  Are 
> >
> > i'm using them correctly
> 
> I, for one, am unconvinced.  I have had no trouble
> filtering unwanted mail from this list, thanks to
> procmail.  My various filters have no trouble
> dealing with more than 99.9% of the unsolicited bulk
> mail including viruses and worms directed at my
> mailbox.  For my mail, my filters have a total false
> positive rate (legitimate rejected divided by total
> legitimate) of less than 0.1%.  Whether your filters
> are doing as well as you want them to does not seem
> like a concern of the IETF.

i have ~98% accuracy thanks to bayesian filtering.  i 
haven't calculated my false positive rate, but i get 
false positives.  even *one* false positive is 
unacceptable.  even if my filter accuracy was 99.99% i 
would still need to trawl my spam folder to check for 
false positives.  and as the spam volume continues to 
grow trawling the spam folder takes more and more 
time.  i need to stop false positives and digital 
signatures are one possible solution.

> > ...
> > the value in having the list processor sign all
> > posts is simple.  guaranteed identification of the
> > list traffic for any recipient who decides to
> > verify signatures.
> 
> I think it would be simpler for all concerned and in
> this case just as effective if the IETF list
> processor would offer to do SMTP-TLS and for an
> appropriate cert to be published on http://ietf.org/
> 
> However, I would not suggesting that for any
> practical or operational reason.  It would merely
> set a good example.

i'm not familiar with SMTP-TLS but i will go read 
about it.  FWIW, i think that digitally signing all 
list messages would also set a good example, and it 
too is a simple implementation.


david




From owner-ietf@ietf.org  Wed Feb 25 17:12:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18292
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 17:12:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw7Bn-0000Ln-Bt
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 17:07:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw7BV-0000KS-2a
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 17:07:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18117
	for <ietf@ietf.org>; Wed, 25 Feb 2004 17:07:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw7BT-0003Of-00
	for ietf@ietf.org; Wed, 25 Feb 2004 17:07:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw7AV-0003Iu-00
	for ietf@ietf.org; Wed, 25 Feb 2004 17:06:15 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw79l-000378-00
	for ietf@ietf.org; Wed, 25 Feb 2004 17:05:31 -0500
Received: from sopac.org (localhost.localdomain [127.0.0.1])
	by franck-lxnb.sopac.org.fj (Postfix) with ESMTP
	id AD97F4B6A4; Thu, 26 Feb 2004 10:04:30 +1200 (FJT)
Message-ID: <403D1BEA.104@sopac.org>
Date: Thu, 26 Feb 2004 10:04:26 +1200
From: Franck Martin <franck@sopac.org>
Organization: SOPAC
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040120
X-Accept-Language: en, en-au, en-us, fr
MIME-Version: 1.0
To: James Seng <jseng@pobox.org.sg>
Cc: ietf@ietf.org, mose@mose.fr
Subject: Re: Request for Comments: RFC Wiki Syntax
References: <403C2789.7050905@sopac.org> <403C345A.5070202@pobox.org.sg>
In-Reply-To: <403C345A.5070202@pobox.org.sg>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig31685444914539000D05EB30"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig31685444914539000D05EB30
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Is there any linux tool to format the document fast? I don't want to do 
it by hand..

Cheers

James Seng wrote:

> Read http://www.ietf.org/ietf/1id-guidelines.txt
>
> then send it to internet-drafts@ietf.org
>
> james
>
> Franck Martin wrote:
>
>> http://tikiwiki.org/tiki-index.php?page=RFCWiki
>>
>> Where do I go from there?
>>
>> How do I submit this document to IETF? Can someone review it? Give 
>> advice?
>>
>> Harald?
>>
>> Cheers
>>

-- 
Franck Martin
ICT Specialist
franck@sopac.org
SOPAC, Fiji
GPG Key fingerprint = 44A4 8AE4 392A 3B92 FDF9  D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard


--------------enig31685444914539000D05EB30
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAPRvuvnmeYIHZEyARArAxAJ402V4FXDW5mm2SZ+f1xyp14OOqWQCfVAWU
+IJRZDlII8dTKbrz6TLxFpc=
=R6k6
-----END PGP SIGNATURE-----

--------------enig31685444914539000D05EB30--



From owner-ietf@ietf.org  Wed Feb 25 17:49:37 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20315
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 17:49:37 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw7l2-0001dA-5D
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 17:44:00 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw7kB-0001bc-P9
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 17:43:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20021
	for <ietf@ietf.org>; Wed, 25 Feb 2004 17:43:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw7kA-0007EU-00
	for ietf@ietf.org; Wed, 25 Feb 2004 17:43:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw7jH-00079l-00
	for ietf@ietf.org; Wed, 25 Feb 2004 17:42:12 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw7iV-00074c-00
	for ietf@ietf.org; Wed, 25 Feb 2004 17:41:24 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1PMfLVb007192
	for ietf@ietf.org env-from <vjs>;
	Wed, 25 Feb 2004 15:41:21 -0700 (MST)
Date: Wed, 25 Feb 2004 15:41:21 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402252241.i1PMfLVb007192@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: digital signature request
References: <403CA484.14977.15C7746@localhost>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: gnulinux@pacinfo.com

> ...
> false positives.  even *one* false positive is 
> unacceptable.  even if my filter accuracy was 99.99% i 
> would still need to trawl my spam folder to check for 
> false positives.  and as the spam volume continues to 
> grow trawling the spam folder takes more and more 
> time.  i need to stop false positives and digital 
> signatures are one possible solution.

Digital signatures cannot stop false positives.  Even if all mail were
digitally signed, there would still be cases where the wrong key was
used, the right key did not reach the mail recipient before the mail
message, a cert expires, or something else hiccups.  The underlying
error rate for SMTP before spam appeared was worse than 0.01%.  Do you
think that 99.99% of HTTPS (HTTP over TLS or SSL) transactions work?
If so, look again.  If not, why would email be better?

If you cannot afford even one false positive, then you had better give
up on email.  My spam load is more than 300 messages/day, counting
only unsolicited bulk advertising.  I receive 50-150 legitimate messages
per day.  It would be impossible for me manually filter that stream
to 99.99% accuracy and so overlook fewer than 1 legitimate message per
10,000 or fewer than one per month.  No one can look at 10,000 messages
per month, never misclassify any as spam or not, and do any other work.
Talk about not losing even one message makes sense only if you receive
almost no spam.

People who talk about 99.99% accurate spam filters as if they were
possible
  - don't know how computers work in the real world (e.g. have no idea
      why the phrase "key distribution" makes some people cringe or
      assume the tooth fairy handles key revocation)
  - don't receive much spam
  - are innumerate
  - are charlatans.
  - are two or more of the above.

At least weekly I'm told of yet another final ultimate solution to the
spam problem with 100% accuracy.  They are all frauds, like weight loss
diets without hunger or any other inconveniences.  Sometimes they have
creative definitions of "spam" and "false positive."  Usually they are
merely obvious wishful thinking and nonsense, like the hoary old claim
that authentication (including digital signatures) will stop spam.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Wed Feb 25 18:52:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24291
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 18:52:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw8fj-0003P0-R9
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 18:42:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw8fI-0003Nb-LO
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 18:42:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23906
	for <ietf@ietf.org>; Wed, 25 Feb 2004 18:42:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw8fG-0005ue-00
	for ietf@ietf.org; Wed, 25 Feb 2004 18:42:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw8eM-0005q7-00
	for ietf@ietf.org; Wed, 25 Feb 2004 18:41:10 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw8dy-0005ks-00
	for ietf@ietf.org; Wed, 25 Feb 2004 18:40:46 -0500
Received: from ibm-eyjgx9r6nqt.shockey.us (h-68-165-240-38.MCLNVA23.covad.net [68.165.240.38])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i1PNmtd25840
	for <ietf@ietf.org>; Wed, 25 Feb 2004 15:48:55 -0800
Message-Id: <6.0.3.0.2.20040225183803.04378ec0@popd.ix.netcom.com>
X-Sender: richard@joy.songbird.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
Date: Wed, 25 Feb 2004 18:38:47 -0500
To: ietf@ietf.org
From: Richard Shockey <richard@shockey.us>
Subject: power in Korea..
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=BIZ_TLD autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


what is the standard voltage - sockets in Korea?  Its my first time there


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
PSTN Office +1 571.434.5651 PSTN Mobile: +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 Feb 25 19:05:10 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25120
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 19:05:10 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw8xO-0004FN-V2
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 19:00:50 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw8wn-0004Dv-PN
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 19:00:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24875
	for <ietf@ietf.org>; Wed, 25 Feb 2004 19:00:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw8wm-000059-00
	for ietf@ietf.org; Wed, 25 Feb 2004 19:00:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw8vq-0007mr-00
	for ietf@ietf.org; Wed, 25 Feb 2004 18:59:15 -0500
Received: from mail.teal.net ([209.142.3.58] helo=teal.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw8v3-0007gH-00
	for ietf@ietf.org; Wed, 25 Feb 2004 18:58:26 -0500
Received: from [24.2.56.29] by teal.net [209.142.3.58] with SmartMax MailMax for ietf@ietf.org; Wed, 25 Feb 2004 15:57:15 -0800
X-SmartMax-AuthUser: jstrutt@pcpotato.com
Reply-To: <jstrutt@pcpotato.com>
From: "Jasen Strutt" <jstrutt@pcpotato.com>
To: "'Richard Shockey'" <richard@shockey.us>, <ietf@ietf.org>
Subject: RE: power in Korea..
Date: Wed, 25 Feb 2004 15:58:01 -0800
Message-ID: <05fc01c3fbfb$36b74790$6501a8c0@SATELLITE>
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
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <6.0.3.0.2.20040225183803.04378ec0@popd.ix.netcom.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.0 required=5.0 tests=BIZ_TLD,UPPERCASE_25_50 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Korea is 220. 

Easily found with a google search, versus an entire list ;-) 

For future travels: 
Continent/Country Voltage Frequency Plug Type 
North America       
Canada 120 V 60 HZ USA 
United States 120 V 60 HZ USA 
Mexico 120 V 50 HZ, 60 HZ USA 
Central America       
Bahamas 115 V 60 HZ USA,UK 
Barbados 115 V 50 HZ USA 
Belize 110-220 V 60 HZ USA 
Bermuda 115 V 60 HZ USA 
Costa Rica 120 V 60 HZ USA 
Cuba 115-120 V 60 HZ USA 
Dominican Republic 110-220 V 60 HZ USA 
El Salvador 120-240 V 60 HZ USA 
Guatemala 115-230 V 60 HZ USA 
Haiti 110-220 V 60 HZ USA 
Honduras 110-220 V 60 HZ USA 
Jamaica 220 V 50 HZ USA,UK 
Netherland Antilles 110-127 V 50 HZ Europe, USA 
Nicaragua 120 V 60 HZ USA 
Panama 120 V 60 HZ USA 
Puerto Rico 120 V 60 HZ USA 
Trinidad & Tobago 115-230 V 60 HZ USA, UK 
Virgin Islands 120 V 60 HZ USA 
Europe       
Albania 220 V 50 HZ Europe 
Austria 230 V 50 HZ Europe 
Belgium 230 V 50 HZ Europe 
Belarus 220 V 50 HZ Europe 
Bulgaria 220 V 50 HZ Europe 
Croatia 220 V 50 HZ Europe 
Czech Republic 120-220 V 50 HZ Europe 
Denmark 230 V 50 HZ Europe, Denmark 
Estonia 220 V 50 HZ Europe 
Finland 230 V 50 HZ Europe 
France 230 V 50 HZ Europe 
Germany 230 V 50 HZ Europe 
Greece 220 V 50 HZ Europe 
Hungary 220 V 50 HZ Europe 
Iceland 220 V 50 HZ Europe 
Ireland 220 V 50 HZ Europe, UK 
Italy 230 V 50 HZ Europe, Italy 
Latvia 220 V 50 HZ Europe 
Lithuania 220 V 50 HZ Europe 
Luxembourg 230 V 50 HZ Europe 
Moldavia 220 V 50 HZ Europe 
Netherlands 230 V 50 HZ Europe 
Norway 230 V 50 HZ Europe 
Poland 127-220 V 50 HZ Europe 
Portugal 110-220 V 50 HZ Europe 
Romania 220 V 50 HZ Europe 
Russia 220 V 50 HZ Europe 
Slovakia 120-220 V 50 HZ Europe 
Slovenia 220 V 50 HZ Europe 
Spain 230 V 50 HZ Europe 
Sweden 230 V 50 HZ Europe 
Switzeland 230 V 50 HZ Swiss 
Ukraine 220 V 50 HZ Europe 
United Kingdom 240 V 50 HZ UK 
Yugoslavia 220 V 50 HZ Europe 
Africa       
Algeria 127-220 V 50 HZ Europe 
Angola 220 V 50 HZ Europe 
Benin 220 V 50 HZ Europe 
Botswana 220 V 50 HZ UK 
Burkina Faso 220 V 50 HZ Europe 
Burundi 220 V 50 HZ Europe 
Cameroon 127-220 V 50 HZ Europe 
Centeral Africa Rep. 220 V 50 HZ Europe 
Chad 220 V 50 HZ Europe 
Congo 220 V 50 HZ Europe 
Dahomey 220 V 50 HZ Europe 
Egypt 220 V 50 HZ Europe, UK 
Ethiopia 220 V 50 HZ Europe, Italy 
Gabon 220 V 50 HZ Europe 
Gambia 230 V 50 HZ UK 
Ghana 240 V 50 HZ UK 
Ivory Coast 220 V 50 HZ Europe 
Kenya 240 V 50 HZ UK 
Lesotho 230 V 60 HZ UK 
Liberia 120 V 60 HZ Europe, USA 
Libya 115-220 V 50 HZ Europe, USA, UK 
Malawi 230 V 50 HZ UK 
Mali 220 V 50 HZ Europe 
Mauritania 220 V 50 HZ Europe 
Mauritius 230 V 50 HZ UK 
Morocco 127-220 V 50 HZ Europe 
Mozambique 220 V 50 HZ Europe 
Nambia 220 V 50 HZ South Africa 
Niger 220 V 50 HZ Europe 
Nigeria 230 V 50 HZ UK 
Rwanda 220 V 50 HZ Europe 
Senegal 110 V 50 HZ Europe 
Sierra Leone 230 V 50 HZ UK 
Somalia 220 V 50 HZ Europe 
South Africa 220-240 V 50 HZ South Africa 
Sudan 240V 50 HZ UK 
Swaziland 220 V 50 HZ UK 
Tanzania 230 V 50 HZ UK 
Togo 127-220 V 50 HZ Europe 
Tunisia 127-220 V 50 HZ Europe 
Uganda 240 V 50 HZ UK 
Zaire 220 V 50 HZ Europe 
Zambia 220 V 50 HZ UK 
Zimbabwe 220 V 50 HZ UK 
South America       
Argentina 230 V 50 HZ Europe, Australia 
Bolivia 110 V 50 HZ USA 
Brazil 110-127-220 V 60 HZ Europe, USA 
Chile 220 V 50 HZ Europe, Italy 
Colombia 110-220 V 50 HZ USA 
Ecuador 110-220 V 60 HZ Europe, USA 
French Guiana 220 V 50 HZ Europe 
Guyana 110-240 V 60 HZ USA 
Paraguay 220 V 60 HZ Europe 
Peru 220 V 60 HZ Europe, USA 
Surinam 110-127 V 60 HZ Europe, USA 
Uruguay 220 V 50 HZ Europe 
Venezuela 120-240 V 60 HZ USA 
Australia, Oceania       
Australia 240 V 50 HZ Australia 
Fiji Islands 240 V 50 HZ Australia 
New Zealand 230 V 50 HZ Australia 
Solomon Island 240 V 50 HZ Australia 
Tonga 230 V 50 HZ Australia 
Asia       
Abu Dhabi 230 V 50 HZ UK 
Afghanistan 220 V 50 HZ Europe 
Armenia 220 V 50 HZ Europe 
Azerbaijan 220 V 50 HZ Europe 
Bahrain 110-230 V 50 HZ, 60 HZ USA, UK 
Bangladesh 230 V 50 HZ UK 
Brunei 240 V 50 HZ UK 
Cambodia 220 V 50 HZ Europe, USA 
China 220 V 50 HZ USA, Australia 
Cyprus 240 V 50 HZ UK 
Georgia 220 V 50 HZ Europe 
Hong Kong 220 V 50 HZ UK 
India 230-250 V 50 HZ, 60 HZ UK 
Indonesia 127-220 V 50 HZ Europe 
Iran 220 V 50 HZ Europe 
Iraq 220 V 50 HZ Europe, UK 
Israel 230 V 50 HZ Israel 
Japan 110-220 V 50 HZ, 60 HZ USA 
Jordan 220 V 50 HZ USA, UK 
Kazakhstan 220 V 50 HZ Europe 
Kirgizstan 220 V 50 HZ Europe 
Korea (North) 220 V 50 HZ Europe 
Korea (South) 110-220 V 60 HZ Europe, USA 
Kuwait 240 V 50 HZ UK 
Laos 220 V 50 HZ Europe, USA 
Lebanon 110-220 V 50 HZ Europe, UK 
Malaysia 240 V 50 HZ UK 
Myanmar 240 V 50 HZ UK 
Oman 240 V 50 HZ USA, UK 
Pakistan 230 V 50 HZ UK 
Philippines 110-220 V 60 HZ USA 
Qatar 240 V 50 HZ UK 
Saudi Arabia 127-220 V 50 HZ Europe, USA, UK 
Singapore 230 V 50 HZ UK 
Sri Lanka 230 V 50 HZ UK 
Syria 220 V 50 HZ Europe 
Taiwan 110-220 V 60 HZ USA 
Tajikistan 220 V 50 HZ Europe 
Thailand 220 V 50 HZ USA 
Turkey 220 V 50 HZ Europe 
Turkmenistan 220 V 50 HZ Europe 
United Arab Emirates 220 V 50 HZ UK 
Uzbekistan 220 V 50 HZ Europe 
Vietnam 120-220 V 50 HZ Europe, UK 
Yemen 220 V 50 HZ UK

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Richard
Shockey
Sent: Wednesday, February 25, 2004 3:39 PM
To: ietf@ietf.org
Subject: power in Korea..


what is the standard voltage - sockets in Korea?  Its my first time there


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
PSTN Office +1 571.434.5651 PSTN Mobile: +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 Feb 25 19:22:36 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26144
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 19:22:36 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw9Df-0005Ao-1K
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 19:17:39 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw9DE-000592-Q1
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 19:17:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25813
	for <ietf@ietf.org>; Wed, 25 Feb 2004 19:17:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw9DD-000227-00
	for ietf@ietf.org; Wed, 25 Feb 2004 19:17:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw9CK-0001xH-00
	for ietf@ietf.org; Wed, 25 Feb 2004 19:16:16 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw9C4-0001rt-00
	for ietf@ietf.org; Wed, 25 Feb 2004 19:16:00 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1Aw9Bt-0004Rg-00; Wed, 25 Feb 2004 19:15:49 -0500
Date: Wed, 25 Feb 2004 19:15:49 -0500
From: John C Klensin <john-ietf@jck.com>
To: jstrutt@pcpotato.com
cc: "'Richard Shockey'" <richard@shockey.us>, ietf@ietf.org
Subject: RE: power in Korea..
Message-ID: <247595914.1077736549@scan.jck.com>
In-Reply-To: <05fc01c3fbfb$36b74790$6501a8c0@SATELLITE>
References: <05fc01c3fbfb$36b74790$6501a8c0@SATELLITE>
X-Mailer: Mulberry/3.1.2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Wednesday, 25 February, 2004 15:58 -0800 Jasen Strutt 
<jstrutt@pcpotato.com> wrote:

> Korea is 220.
>
> Easily found with a google search, versus an entire list ;-)

Lest someone get a nasty surprise by believing everything you 
read on the Internet, if you are staying in the IETF hotel, 
click through from the IETF meeting accommodation page, follow 
the instructions to find the Lotte Seoul, click "rooms" and then 
"standard and deluxe rooms".  There you will find the 
interesting statement:

	- Voltage in Main Buliding rooms is 110v. New Wing rooms
	is 220v.

Don't be surprised if similar situations are encountered in 
other hotels and facilities.

If I recall, 110 volt outlets in Korea are compatible with US / 
Japanese two-prong plugs, i.e., two parallel flat blades.

       john




From owner-ietf@ietf.org  Wed Feb 25 20:10:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27770
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 20:10:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aw9v7-0006dR-S1
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 20:02:33 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aw9up-0006cT-8L
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 20:02:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27549
	for <ietf@ietf.org>; Wed, 25 Feb 2004 20:02:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw9un-0006U5-00
	for ietf@ietf.org; Wed, 25 Feb 2004 20:02:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aw9ts-0006Np-00
	for ietf@ietf.org; Wed, 25 Feb 2004 20:01:17 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aw9t1-0006Bd-00
	for ietf@ietf.org; Wed, 25 Feb 2004 20:00:23 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 25 Feb 2004 17:10:58 +0000
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i1Q0xU1m008920;
	Wed, 25 Feb 2004 16:59:52 -0800 (PST)
Received: from localhost (ole@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id QAA17323; Wed, 25 Feb 2004 16:59:30 -0800 (PST)
Date: Wed, 25 Feb 2004 16:59:30 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
Reply-To: Ole Jacobsen <ole@cisco.com>
To: Richard Shockey <richard@shockey.us>
cc: ietf@ietf.org
Subject: Re: power in Korea..
In-Reply-To: <6.0.3.0.2.20040225183803.04378ec0@popd.ix.netcom.com>
Message-ID: <Pine.HPX.4.58.0402251655170.1332@wells.cisco.com>
References: <6.0.3.0.2.20040225183803.04378ec0@popd.ix.netcom.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,BIZ_TLD autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

See my previous post on this topic.

Quick answer: Euro-style round-pin plugs

Long answer: The official Korean plug is 4.8 mm in diameter whereas the
Euro-plug is 4.0 mm. This means you *could* encounter some "loose
connections" unless you use the European *grounded* plug which *is* 4.8
mm also. Apple users get both a Euro plug and a Korean plug in the
world-wide plug kit for the white power bricks. Springloaded adapters
such as the Sascom and Gocom are good alternatives.

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 Wed, 25 Feb 2004, Richard Shockey wrote:

>
> what is the standard voltage - sockets in Korea?  Its my first time there
>
>
>  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Richard Shockey, Senior Manager, Strategic Technology Initiatives
> NeuStar Inc.
> 46000 Center Oak Plaza  -   Sterling, VA  20166
> sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> PSTN Office +1 571.434.5651 PSTN Mobile: +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 Feb 25 23:11:43 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03522
	for <ietf-archive@odin.ietf.org>; Wed, 25 Feb 2004 23:11:43 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwCiK-0001Yo-Iy
	for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 23:01:32 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwCi0-0001Xq-4c
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 23:01:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03250
	for <ietf@ietf.org>; Wed, 25 Feb 2004 23:01:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwChy-0006CN-00
	for ietf@ietf.org; Wed, 25 Feb 2004 23:01:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwCh0-00066h-00
	for ietf@ietf.org; Wed, 25 Feb 2004 23:00:11 -0500
Received: from out004pub.verizon.net ([206.46.170.142] helo=out004.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwCg6-00060A-00
	for ietf@ietf.org; Wed, 25 Feb 2004 22:59:14 -0500
Received: from MattXP.verizon.net ([68.136.66.208]) by out004.verizon.net
          (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP
          id <20040226035913.WLTM8186.out004.verizon.net@MattXP.verizon.net>
          for <ietf@ietf.org>; Wed, 25 Feb 2004 21:59:13 -0600
Message-Id: <6.0.1.1.2.20040225195608.01d9dec0@incoming.verizon.net>
X-Sender: res06gzk@incoming.verizon.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 25 Feb 2004 20:00:31 -0800
To: ietf@ietf.org
From: Matt Holdrege <matt.holdrege@verizon.net>
Subject: Re: power in Korea..
In-Reply-To: <Pine.HPX.4.58.0402251655170.1332@wells.cisco.com>
References: <6.0.3.0.2.20040225183803.04378ec0@popd.ix.netcom.com>
 <Pine.HPX.4.58.0402251655170.1332@wells.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authentication-Info: Submitted using SMTP AUTH at out004.verizon.net from [68.136.66.208] at Wed, 25 Feb 2004 21:59:12 -0600
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 04:59 PM 2/25/2004, Ole Jacobsen wrote:
>Quick answer: Euro-style round-pin plugs
>
>Long answer: The official Korean plug is 4.8 mm in diameter whereas the
>Euro-plug is 4.0 mm. This means you *could* encounter some "loose
>connections" unless you use the European *grounded* plug which *is* 4.8
>mm also. Apple users get both a Euro plug and a Korean plug in the
>world-wide plug kit for the white power bricks. Springloaded adapters
>such as the Sascom and Gocom are good alternatives.

I am shocked that the IETF didn't rewire downtown Seoul to accommodate our 
conference! The next thing we'll hear is that our TDMA phones won't work. 
Or that they don't have TGI Friday's within easy walking distance. :-)





From owner-ietf@ietf.org  Thu Feb 26 00:47:28 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06992
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 00:47:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwEGA-0003Yn-IL
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 00:40:34 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwED0-0003VU-6s
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 00:37:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06713
	for <ietf@ietf.org>; Thu, 26 Feb 2004 00:37:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwECy-0007AQ-00
	for ietf@ietf.org; Thu, 26 Feb 2004 00:37:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwEC3-000765-00
	for ietf@ietf.org; Thu, 26 Feb 2004 00:36:19 -0500
Received: from mx.uom.ac.mu ([202.60.7.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwEBD-0006xP-00
	for ietf@ietf.org; Thu, 26 Feb 2004 00:35:27 -0500
Received: from localhost ([])
        by mx.uom.ac.mu (Merak 7.2.0) with SMTP id DWA74278
        for <ietf@ietf.org>; Thu, 26 Feb 2004 09:34:46 +0400
Date: Thu, 26 Feb 2004 09:34:46 +0400
From: Boodhoo Avinash <boodhooa@mx.uom.ac.mu>
To: ietf@ietf.org
Subject: research areas in IPv6
Message-ID: <550ca2d2baf4234c69789b65ab24a176@mx.uom.ac.mu>
X-Mailer: IceWarp Web Mail 5.2.2
X-Originating-IP: 172.22.28.36
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi everyone,

                 I am Avinash from Mauritius. I am doing an MPhil in IPv6. I would like to know in areas can I do research in Ipv6. I thank you in advance.
Avinash



From owner-ietf@ietf.org  Thu Feb 26 02:24:18 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24167
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 02:24:18 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwFl1-0005ig-6O
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 02:16:31 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwFkq-0005hV-Ik
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 02:16:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23670
	for <ietf@ietf.org>; Thu, 26 Feb 2004 02:16:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwFko-000183-00
	for ietf@ietf.org; Thu, 26 Feb 2004 02:16:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwFjv-00014R-00
	for ietf@ietf.org; Thu, 26 Feb 2004 02:15:23 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwFjc-000107-00
	for ietf@ietf.org; Thu, 26 Feb 2004 02:15:04 -0500
Received: from isi.edu (lsanca1-ar42-4-61-162-086.lsanca1.dsl-verizon.net [4.61.162.86])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i1Q7F3v27906;
	Wed, 25 Feb 2004 23:15:03 -0800 (PST)
Message-ID: <403D9CF8.1010704@isi.edu>
Date: Wed, 25 Feb 2004 23:15:04 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Matt Holdrege <matt.holdrege@verizon.net>
CC: ietf@ietf.org
Subject: Re: power in Korea..
References: <6.0.3.0.2.20040225183803.04378ec0@popd.ix.netcom.com> <Pine.HPX.4.58.0402251655170.1332@wells.cisco.com> <6.0.1.1.2.20040225195608.01d9dec0@incoming.verizon.net>
In-Reply-To: <6.0.1.1.2.20040225195608.01d9dec0@incoming.verizon.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Matt Holdrege wrote:

> I am shocked that the IETF didn't rewire downtown Seoul to accommodate 
> our conference! The next thing we'll hear is that our TDMA phones won't 
> work. Or that they don't have TGI Friday's within easy walking distance. 
> :-)

About phones:

You can use a tri-mode CDMA USA phone (e.g., my Verizon v60i), though:

	a) I needed to update the firmware at the local store.
	beware:
		1. they will tell you this is fruitless, and that
		everywhere overseas is GSM (it isn't)

		2. you may need to recode the ID number (PRL?)
		(in verizon-speak, dial *228 and recode roaming)

		3. the account has to be setup for international roaming

In Korea, to dial the US, I was told you dial:

	00700 (international number)

	e.g.,
		00700 310 555 1212

(I'm sending this long-ish summary since Verizon left it off their 
international traveler web pages, and it took a few days to decode ;-)

Joe



From owner-ietf@ietf.org  Thu Feb 26 03:31:34 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27136
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 03:31:34 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwGou-0007Bo-AT
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 03:24:36 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwGo1-0007Ar-51
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 03:23:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26645
	for <ietf@ietf.org>; Thu, 26 Feb 2004 03:23:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwGnv-0006zi-00
	for ietf@ietf.org; Thu, 26 Feb 2004 03:23:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwGnC-0006tb-00
	for ietf@ietf.org; Thu, 26 Feb 2004 03:22:50 -0500
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by ietf-mx with smtp (Exim 4.12)
	id 1AwGmL-0006kR-00
	for ietf@ietf.org; Thu, 26 Feb 2004 03:21:57 -0500
Received: (qmail 30387 invoked by uid 65534); 26 Feb 2004 08:21:25 -0000
Received: from p3EE2482F.dip.t-dialin.net (EHLO gmx.de) (62.226.72.47)
  by mail.gmx.net (mp022) with SMTP; 26 Feb 2004 09:21:25 +0100
X-Authenticated: #1915285
Message-ID: <403DAC67.1010806@gmx.de>
Date: Thu, 26 Feb 2004 09:20:55 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Franck Martin <franck@sopac.org>
CC: James Seng <jseng@pobox.org.sg>, ietf@ietf.org, mose@mose.fr
Subject: Re: Request for Comments: RFC Wiki Syntax
References: <403C2789.7050905@sopac.org> <403C345A.5070202@pobox.org.sg> <403D1BEA.104@sopac.org>
In-Reply-To: <403D1BEA.104@sopac.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Franck Martin wrote:
> Is there any linux tool to format the document fast? I don't want to do 
> it by hand..

You may want to take a look at xml2rfc (http://xml.resource.org).

Regards, Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760



From owner-ietf@ietf.org  Thu Feb 26 05:27:35 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02681
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 05:27:35 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwIb7-0001CD-P9
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 05:18:29 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwIaA-0001Ag-Qx
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 05:17:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02282
	for <ietf@ietf.org>; Thu, 26 Feb 2004 05:17:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwIa8-0002rF-00
	for ietf@ietf.org; Thu, 26 Feb 2004 05:17:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwIZE-0002mj-00
	for ietf@ietf.org; Thu, 26 Feb 2004 05:16:32 -0500
Received: from rc-dmz.felix.nlri.ca ([192.5.4.54] helo=felix.automagic.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwIYu-0002hw-00
	for ietf@ietf.org; Thu, 26 Feb 2004 05:16:12 -0500
Received: from [169.223.254.180] (helo=[169.223.254.180])
	by felix.automagic.org with asmtp (TLSv1:RC4-SHA:128)
	(Exim 4.20)
	id 1AwIYl-0003PB-Rx; Thu, 26 Feb 2004 10:16:04 +0000
In-Reply-To: <403D9CF8.1010704@isi.edu>
References: <6.0.3.0.2.20040225183803.04378ec0@popd.ix.netcom.com> <Pine.HPX.4.58.0402251655170.1332@wells.cisco.com> <6.0.1.1.2.20040225195608.01d9dec0@incoming.verizon.net> <403D9CF8.1010704@isi.edu>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <B6AA00EB-6844-11D8-8334-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
Cc: Matt Holdrege <matt.holdrege@verizon.net>, ietf@ietf.org
From: Joe Abley <jabley@isc.org>
Subject: Re: power in Korea..
Date: Thu, 26 Feb 2004 18:15:33 +0800
To: Joe Touch <touch@ISI.EDU>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On 26 Feb 2004, at 15:15, Joe Touch wrote:

> Matt Holdrege wrote:
>
>> I am shocked that the IETF didn't rewire downtown Seoul to 
>> accommodate our conference! The next thing we'll hear is that our 
>> TDMA phones won't work. Or that they don't have TGI Friday's within 
>> easy walking distance. :-)
>
> About phones:

Also, for GSM subscribers:

   http://www.etechkorea.info/articles/20020601001.php

These are CDMA phones which are specially designed for GSM roamers (you 
stick your GSM SIM in the back of them). I used a KTF CDMA phone with 
my Microcell GSM SIM last August, and it worked fine. The cost of 
renting the phone was very low, and picking up the handset at ICN was 
painless.


Joe




From owner-ietf@ietf.org  Thu Feb 26 07:46:21 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08522
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 07:46:21 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwKma-0003qM-Og
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 07:38:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwKli-0003pL-M3
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 07:37:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07883
	for <ietf@ietf.org>; Thu, 26 Feb 2004 07:37:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwKli-0000jk-00
	for ietf@ietf.org; Thu, 26 Feb 2004 07:37:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwKkr-0000et-00
	for ietf@ietf.org; Thu, 26 Feb 2004 07:36:41 -0500
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwKk1-0000Uh-00
	for ietf@ietf.org; Thu, 26 Feb 2004 07:35:49 -0500
Received: from dfnjgl21 (c-24-1-97-129.client.comcast.net[24.1.97.129])
          by comcast.net (rwcrmhc13) with SMTP
          id <2004022612351301500o4290e>
          (Authid: sdawkins@comcast.net);
          Thu, 26 Feb 2004 12:35:13 +0000
Message-ID: <02fe01c3fc65$00b56450$0400a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: "IETF General Discussion Mailing List" <ietf@ietf.org>
Subject: If you're not already in Korea, don't forget to pack small hand drums, shakers, rattles, etc.
Date: Thu, 26 Feb 2004 06:35:22 -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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

We usually need healing for the plenaries, and many traditions drum as
part of a healing ceremony, so ...

See you in Seoul,

Spencer




From owner-ietf@ietf.org  Thu Feb 26 07:46:22 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08527
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 07:46:22 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwKke-0003oX-MK
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 07:36:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwKjz-0003na-1T
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 07:35:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07820
	for <ietf@ietf.org>; Thu, 26 Feb 2004 07:35:45 -0500 (EST)
From: ted.lemon@nominum.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwKjy-0000Zp-00
	for ietf@ietf.org; Thu, 26 Feb 2004 07:35:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwKj0-0000U8-00
	for ietf@ietf.org; Thu, 26 Feb 2004 07:34:47 -0500
Received: from [218.77.200.92] (helo=ietf.org)
	by ietf-mx with smtp (Exim 4.12)
	id 1AwKiC-0000Ni-00
	for ietf@ietf.org; Thu, 26 Feb 2004 07:33:56 -0500
To: ietf@ietf.org
Subject: unknown
Date: Thu, 26 Feb 2004 20:33:56 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="06510167"
Message-Id: <E1AwKiC-0000Ni-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.6 required=5.0 tests=MSGID_FROM_MTA_SHORT,
	NO_REAL_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

--06510167
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_NETSKY.B in file party.txt.pif (in party.zip)
The file is deleted.

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

--06510167
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

reply

--06510167
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

party.zip is removed from here because it contains a virus.

---------------------------------------------------------
--06510167--




From owner-ietf@ietf.org  Thu Feb 26 08:37:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12239
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 08:37:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwLcq-0005ZY-6r
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 08:32:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwCgL-0001VP-T4
	for ietf@asgard.ietf.org; Wed, 25 Feb 2004 22:59:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03180
	for <ietf@ietf.org>; Wed, 25 Feb 2004 22:59:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwCgK-00062E-00
	for ietf@ietf.org; Wed, 25 Feb 2004 22:59:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwCfk-0005vX-00
	for ietf@ietf.org; Wed, 25 Feb 2004 22:58:53 -0500
Received: from luna.soncom.com ([207.195.208.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwCes-0005m2-00
	for ietf@ietf.org; Wed, 25 Feb 2004 22:57:59 -0500
Received: from Darkblade (Jake@207-195-192-214.sihope.com [207.195.192.214])
	by luna.soncom.com (8.11.5/8.11.0) with SMTP id i1Q3vlq92282;
	Wed, 25 Feb 2004 21:57:47 -0600 (CST)
Message-ID: <011b01c3fc1c$6f85cf30$0100a8c0@Darkblade>
From: "Jake Nelson" <jnelson@soncom.com>
To: <gnulinux@pacinfo.com>, <ietf@ietf.org>
References: <403CA484.14977.15C7746@localhost>
Subject: Re: digital signature request
Date: Wed, 25 Feb 2004 21:55:53 -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.1106
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

gnulinux@pacinfo.com wrote:
> see above response.  also, from my perspective digital
> signature verification is simpler than maintaining a
> filter list.  i'm tired of the spam/anti-spam arms
> race.  i'm going to deploy a solution that is
> unspoofable.

No, you aren't. You're quite welcome to try, however... anything that slows
the spammers down is progress.

-- Jake






From owner-ietf@ietf.org  Thu Feb 26 08:51:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12935
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 08:51:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwLqO-0006d7-7J
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 08:46:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwLpS-0006c5-W4
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 08:45:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12769
	for <ietf@ietf.org>; Thu, 26 Feb 2004 08:45:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwLpS-0002Pi-00
	for ietf@ietf.org; Thu, 26 Feb 2004 08:45:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwLoV-0002Ll-00
	for ietf@ietf.org; Thu, 26 Feb 2004 08:44:32 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[ARuFwZF1xyLu6vWsW9/afPVa+hafbjqI])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwLnt-0002Hs-00
	for ietf@ietf.org; Thu, 26 Feb 2004 08:43:53 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id BEB05A77DE; Thu, 26 Feb 2004 08:43:50 -0500 (EST)
Date: Thu, 26 Feb 2004 08:35:38 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Dean Anderson <dean@av8.com>
Cc: gnulinux@pacinfo.com, <ietf@ietf.org>
Subject: Re: digital signature request
In-Reply-To: <Pine.LNX.4.44.0402251610580.25194-100000@cirrus.av8.net>
Message-ID: <Pine.LNX.4.44.0402260749030.6202-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,DRASTIC_REDUCED 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 25 Feb 2004, Dean Anderson wrote:

> There are many ways to reasonably accurately identify mail to this list 
> and distinguish it from all others: It is sent "to: ietf@ietf.org".
> 
> I haven't seen very much spam that has that characteristic, so I don't 
> think such spam is much of a problem, if any problem at all.
> 
> 		--Dean

In fact, if you look at the full header:

Return-Path: <owner-ietf@ietf.org>
Delivered-To: rgb@phy.duke.edu
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
        by mail.phy.duke.edu (Postfix) with ESMTP id C9DACA7836
        for <rgb@phy.duke.edu>; Wed, 25 Feb 2004 16:24:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
        id 1Aw6QN-0006qR-OK
        for ietf-list@asgard.ietf.org; Wed, 25 Feb 2004 16:18:35 -0500
Received: from ietf.org ([10.27.2.28])
        by asgard.ietf.org with esmtp (Exim 4.14)
        id 1Aw6Ot-0006nT-O0
        for ietf@asgard.ietf.org; Wed, 25 Feb 2004 16:17:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
        by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15076
        for <ietf@ietf.org>; Wed, 25 Feb 2004 16:17:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
        by ietf-mx with esmtp (Exim 4.12)
        id 1Aw6Os-0005Mn-00
        for ietf@ietf.org; Wed, 25 Feb 2004 16:17:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
        id 1Aw6Ny-0005Hp-00
        for ietf@ietf.org; Wed, 25 Feb 2004 16:16:07 -0500
Received: from cirrus.av8.net ([130.105.36.66])
        by ietf-mx with esmtp (Exim 4.12)
        id 1Aw6NZ-0005Cg-00
        for ietf@ietf.org; Wed, 25 Feb 2004 16:15:42 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
        (authenticated bits=0)
        by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1PLFBMN028275
        (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168
    verify=NO);
        Wed, 25 Feb 2004 16:15:12 -0500
Date: Wed, 25 Feb 2004 16:15:11 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net

you'll note that one can really be pretty certain a) that the message is
really from the ietf list; b) that it was originally sent from a
registered host whose IP number agrees with its claim of identity and
whose owner likes the notion of secured mail; c) that email to the list
is generically spam-scanned before being forwarded; d) that the
dean@cirrus.av8.net who authored the note is really who he appears to be
and is accountable and hence is not about to hawk a website purporting
to portray coeds showering and playing with their doggies on webcam.
[Where it is parenthetically amusing to note that "hawk" means both to
sell and to clear one's throat to spit out corrupt and tainted slime...]

This is all BEFORE examining content.  Then one can apply content
filters at YOUR end at whatever level of analysis and rejection you are
comfortable with.  Obviously too-quick a rejection on simple keywords
like "coeds", "showering" and "doggies" would be a mistake.  

This is all technology and protocol that exists now and in fact is in
place now, and doesn't require OTHER people to do a thing.  YOU have to
do something -- take charge of your own spam-destiny, so to speak.

Parsing a header isn't horribly difficult, either for a human or for a
piece of software.  I routinely do it visually if I have ANY DOUBT about
a message from a stranger or a friend being "really" from the purported
sender (for messages that make it through spamassassin).  I also
routinely do it if a personal message from a vendor (sales, but not
spam) makes it through SA and I am considering answering.  Messages
without a perfectly formed header and all hosts along the delivery path
both registered and identified correctly are rejected to the bit bucket
pro forma.  Spamassassin uses data parsed from the header for several of
its tests, and not just for blacklist checks.

Digitally signing a message to or from ietf adds absolutely nothing to
your ability to determine whether or not it is spam except the necessity
of maintain YET ANOTHER complex mapping between identity and number.  We
don't use the DNS-based one that we have as the rigorous basis of a
protocol-level accept/reject decision, in spite of the fact that it is
ubiquitous (and indeed already a critical component of the mail transfer
process), reliable and at least crudely secure.  At most lookups are
used to drive blacklists, but we don't automatically blacklist mail from
all unregistered/anonymous sites.

Why in the world does anyone think that digital signature maps with
several orders of magnitude more entities to track, more complexity, and
hence more opportunities for spoofing and finagling are going to succeed
where simple DNS hostname lookup has failed?

IMO a "no anonymous mail" rule (no mail accepted anywhere from
unregistered hosts) coupled with pretty stiff fines and legal penalties
for spam would associate accountability and penalty and cause an
immediate and drastic reduction of the problem.  Holding ISPs (and
providers of open relays and proxies) liable for the fines of their
clients if they bolt or "have no assets" would give ISPs a very strong
incentive to police their clients.  Obviously, the two would have to
come about together -- it is less useful to have fines and penalties
when the originating hosts have unregistered IP numbers that change
every two days and are nearly impossible to trace.

I think that this is fairly unlikely to come to pass, as lawmakers are
as likely as not to be spammers of a sort in their own right, soliciting
campaign contributions, distributing political "newsletters", using
email in a variety of edgy, mass distribution ways.  OTOH, they also get
spammed, as do their families, so one never knows -- some states are
slowly moving to control spam in law.

In the meantime, instead of burning a huge amount of human time and
energy just DISCUSSING the issue of universal keysigned mail (let alone
the hassle of implementing it for just one site), perhaps we can each
(in the words of Candide) "tend our own garden" and use one of the many
excellent filtering mechanisms already available, while teaching our
users to do the same.  If the proposal meets this much resistance and
"why bother" attitude here, imagine the resistance it will meet at the
ISP level and out in the real world, where time spent implementing
ANYTHING is pure money and maintenance time down the drain.

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Thu Feb 26 09:21:33 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14479
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 09:21:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwMKN-0007cz-VP
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 09:17:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwMIb-0007as-4c
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 09:15:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14169
	for <ietf@ietf.org>; Thu, 26 Feb 2004 09:15:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwMIa-0005ab-00
	for ietf@ietf.org; Thu, 26 Feb 2004 09:15:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwMHb-0005Vb-00
	for ietf@ietf.org; Thu, 26 Feb 2004 09:14:36 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[ZZ254GKS+QS67UpAO0GhOGiG9hnCJcKJ])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwMGz-0005RZ-00
	for ietf@ietf.org; Thu, 26 Feb 2004 09:13:57 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id 0E0DAA77DE; Thu, 26 Feb 2004 09:13:55 -0500 (EST)
Date: Thu, 26 Feb 2004 09:05:42 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: gnulinux@pacinfo.com
Cc: ietf@ietf.org
Subject: RE: digital signature request
In-Reply-To: <403CA484.14977.15C7746@localhost>
Message-ID: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,YOU_WON autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 25 Feb 2004 gnulinux@pacinfo.com wrote:

> i have ~98% accuracy thanks to bayesian filtering.  i 
> haven't calculated my false positive rate, but i get 
> false positives.  even *one* false positive is 
> unacceptable.  even if my filter accuracy was 99.99% i 
> would still need to trawl my spam folder to check for 
> false positives.  and as the spam volume continues to 
> grow trawling the spam folder takes more and more 
> time.  i need to stop false positives and digital 
> signatures are one possible solution.

But they aren't.  They won't stop false positives and they won't keep
you from having to traverse your spam folder if your criterion is "no
false positives".  

As has been pointed out, it is effectively impossible to make a filter
that passes only signal and no noise, only desired communications and
never undesired (especially given that the final decision is essentially
human and subjecting and too complex for ANY filtering tool but your own
mind).  There is real math behind this, but it is really a common sense
conclusion as well.  So if your criterion is "no false positives" (a
goal that is up there with a 100% efficient heat engine, winning the
publisher's clearing house sweepstakes, and a free lunch:-), not only
will you need to trawl your spam folder, you'll need to trawl it
repeatedly, as you yourself probably make mistakes on what is spam and
what isn't one in 10^4 or 10^5 times, if not more, especially on a rapid
scan of hundreds of messages almost all of which are spam.

It has been pointed out several times now that unless you are willing to
receive mail only from a small, closed group of individuals that all
agree to use digital signatures and whose mail you whitelist while
blacklisting EVERYTHING ELSE you are right back where you are right now.
Since you don't blacklist everything else, it gets filtered (or not) and
you have to go through the rejects in a final pass.  Who knows, one of
them might be your long lost cousin Jimmy, trying to get in touch with
you but alas not possessed of either your phone number, a digital key
and knowledge of how to use it, and hence the means to communicate it to
you and hence get on your whitelist.  It requires an out of band
communication for him to be admitted to your channel, and if you reject
everything not in your channel, Jimmy's out of luck.  

Then there is the cruel fact that you aren't going to convince all the
list managers in the world to digitally sign their list traffic.  You
can of course decide never to subscribe to a list that doesn't, but that
throws a whole lot of baby out with the bath water, and again leaves you
trawling rejects.

The only issue in controlling spam is whether one BOTHERS to trawl the
rejects.  This, in turn, is related to the level at which you reject
spam -- the ratio between false negatives (spam that makes it to your
regular spool) and false positives (mail that makes it into your spam
spool).

I set my spam filtering high enough that I don't check the rejects.
I've spot-checked the rejects for quite some time, and any "real mail"
that gets rejected is VERY likely to be something I will survive if I
never get, and if it IS important and for any reason the sender is a
friend they will almost certainly send me an out of band communication
in my mostly OPEN filter channel saying "Hey, why didn't you respond to
my note letting you know that you won the sweepstakes in Nigeria and are
about to be presented with a check by the grandson of its prime
minister?  I put a dozen URL's to the website announcing the result into
the message when I sent it from my laptop through the open WiFi net I
happened to be passing by..."

Others set the filter lower, but quick-scan the rejects.  Still others
might set one breakpoint VERY high (and reject 70% of it out of hand
with "no" false positives), set a second low enough that no spam at all
makes it into their regular spool, and quick scan the intermediate
rejects.  Just by examining the SA rating of spam that makes it through
and the rating of regular mail that makes it through, it is pretty easy
to see whether or not your active boundary is reasonable.

Digital signatures won't change this a bit.  It may permit you to
identify a certain class of true negatives (and keep them out of the
false positive bin), although I at least am cynical about even that.  It
won't keep you from having a wide range of mail that you still have to
filter and still have to review, if your criterion is "no false
positives" and you want to remain globally accessible to mail from
strangers, and the additional work it will require to implement so that
you can even afford to implement it at all greatly exceeds the work
you're doing now, or could be doing with a bit of rearrangement.

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Thu Feb 26 09:26:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12234
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 08:37:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwLem-0005bv-Gs
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 08:34:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwLeg-0005aY-Qn
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 08:34:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11633
	for <ietf@ietf.org>; Thu, 26 Feb 2004 08:34:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwLef-0000sz-00
	for ietf@ietf.org; Thu, 26 Feb 2004 08:34:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwLcd-0000Py-00
	for ietf@ietf.org; Thu, 26 Feb 2004 08:32:16 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwLbK-00009D-00
	for ietf@ietf.org; Thu, 26 Feb 2004 08:30:55 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP id 79A8B12F
	for <ietf@ietf.org>; Thu, 26 Feb 2004 08:28:17 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
To: ietf@ietf.org
Subject: Re: digital signature request
Date: Thu, 26 Feb 2004 08:29:04 -0500
User-Agent: KMail/1.5.2
References: <Pine.LNX.4.44.0402251610580.25194-100000@cirrus.av8.net>
In-Reply-To: <Pine.LNX.4.44.0402251610580.25194-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402260829.04088.spamtrap.ietf@dja.mailme.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wed February 25 2004 16:15, Dean Anderson wrote:

 > There are many ways to reasonably accurately identify mail to this
 > list and distinguish it from all others: It is sent "to:
 > ietf@ietf.org".

Nitpick: ietf@ietf.org could be in the Cc, or worse yet Bcc, field.

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.




From owner-ietf@ietf.org  Thu Feb 26 10:30:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19758
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 10:30:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwNCa-0000j6-Jo
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 10:13:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwNAk-0000hI-HK
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 10:11:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18303
	for <ietf@ietf.org>; Thu, 26 Feb 2004 10:11:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwNAj-0004Qz-00
	for ietf@ietf.org; Thu, 26 Feb 2004 10:11:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwN9n-0004GZ-00
	for ietf@ietf.org; Thu, 26 Feb 2004 10:10:35 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwN8p-000470-00
	for ietf@ietf.org; Thu, 26 Feb 2004 10:09:35 -0500
Received: from [192.168.1.3] (dsl081-036-151.lax1.dsl.speakeasy.net [64.81.36.151])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i1QF9Xv10279;
	Thu, 26 Feb 2004 07:09:33 -0800 (PST)
In-Reply-To: <B6AA00EB-6844-11D8-8334-00039312C852@isc.org>
References: <6.0.3.0.2.20040225183803.04378ec0@popd.ix.netcom.com> <Pine.HPX.4.58.0402251655170.1332@wells.cisco.com> <6.0.1.1.2.20040225195608.01d9dec0@incoming.verizon.net> <403D9CF8.1010704@isi.edu> <B6AA00EB-6844-11D8-8334-00039312C852@isc.org>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C4531E01-686D-11D8-AEFD-000A95DBDB84@isi.edu>
Content-Transfer-Encoding: 7bit
Cc: Matt Holdrege <matt.holdrege@verizon.net>, ietf@ietf.org,
        Joe Touch <touch@ISI.EDU>
From: Aaron Falk <falk@ISI.EDU>
Subject: Re: power in Korea..
Date: Thu, 26 Feb 2004 07:09:26 -0800
To: Joe Abley <jabley@isc.org>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Feb 26, 2004, at 2:15 AM, Joe Abley wrote:

> Also, for GSM subscribers:
>
>   http://www.etechkorea.info/articles/20020601001.php
>
> These are CDMA phones which are specially designed for GSM roamers 
> (you stick your GSM SIM in the back of them). I used a KTF CDMA phone 
> with my Microcell GSM SIM last August, and it worked fine. The cost of 
> renting the phone was very low, and picking up the handset at ICN was 
> painless.

Has anybody tried this kind of trick (putting the SIM in another phone) 
with a T-mobile sim?  I know that T-mobile binds the phone to the sim 
but don't know if they bind the sim to the phone.

--aaron




From owner-ietf@ietf.org  Thu Feb 26 10:36:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20294
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 10:36:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwNVe-0001Js-4k
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 10:33:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwNTI-000138-H1
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 10:30:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19782
	for <ietf@ietf.org>; Thu, 26 Feb 2004 10:30:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwNTH-0006bD-00
	for ietf@ietf.org; Thu, 26 Feb 2004 10:30:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwNSL-0006VX-00
	for ietf@ietf.org; Thu, 26 Feb 2004 10:29:46 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwNRl-0006Q6-00
	for ietf@ietf.org; Thu, 26 Feb 2004 10:29:10 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1QFT7QB059427
	for ietf@ietf.org env-from <vjs>;
	Thu, 26 Feb 2004 08:29:07 -0700 (MST)
Date: Thu, 26 Feb 2004 08:29:07 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402261529.i1QFT7QB059427@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: digital signature request
References: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "Robert G. Brown" <rgb@phy.duke.edu>

> ...
> It has been pointed out several times now that unless you are willing to
> receive mail only from a small, closed group of individuals that all
> agree to use digital signatures and whose mail you whitelist while
> blacklisting EVERYTHING ELSE you are right back where you are right now.
> ...

If you are interested in that model, then you do not need any fancy
cryptography, certs, pretty good encryption, S/MIME, or anything else
not already present in all SMTP mail.  You can whitelist using bits
that are already associated with every SMTP mail message and in
the body delivered to your MUA if your MTA is not broken junk.

Ever mail message carries a practically unforgeable (for spammers)
token identifying its source.  That token is the IP address of the
SMTP client.  If your MTA is reasonable, it is included in the Received
header it adds.  You only need fancy extra stuff if you cannot arrange
for your community to use only trustworthy MTAs or if your traffic is
worth the thousands of dollars (or equivalent labor) that breaking
security based on IP addresses requires.

Yes, I've heard of Bellovin, Mitnick, RFC 1948, etc. so forth and so
on and on.   TCP ISN faking is harder now than it used to be.  It was
always incompatible with the "bulk" in "unsolicited bulk mail."


The spam problem starts with accepting mail from strangers.  Give
up that design goal, and spam disappears.  So does much of the
justification for mail.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Thu Feb 26 10:50:33 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21008
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 10:50:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwNiV-00027W-Ar
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 10:46:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwNhj-00026B-Je
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 10:45:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20851
	for <ietf@ietf.org>; Thu, 26 Feb 2004 10:45:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwNhi-00011u-00
	for ietf@ietf.org; Thu, 26 Feb 2004 10:45:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwNgo-0000vK-00
	for ietf@ietf.org; Thu, 26 Feb 2004 10:44:43 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwNfr-0000oe-00
	for ietf@ietf.org; Thu, 26 Feb 2004 10:43:43 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1QFi5rq029169;
	Thu, 26 Feb 2004 16:44:05 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net>
References: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: digital signature request
Date: Thu, 26 Feb 2004 16:43:39 +0100
To: "Robert G. Brown" <rgb@phy.duke.edu>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 26-feb-04, at 15:05, Robert G. Brown wrote:

> It has been pointed out several times now that unless you are willing 
> to
> receive mail only from a small, closed group of individuals that all
> agree to use digital signatures and whose mail you whitelist while
> blacklisting EVERYTHING ELSE you are right back where you are right 
> now.

If we can communicate the fact that a message is discarded because it 
was categorized as spam back to the sender without adverse side 
effects, then occasional false positives aren't much of a problem.

As for signing list messages: some practical experience would be good 
here. I'm not sure this list is the best choice to gain it, though.




From owner-ietf@ietf.org  Thu Feb 26 11:48:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23627
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 11:48:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwOWp-0003aO-GG
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 11:38:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwOW9-0003Yw-8G
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 11:37:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23355
	for <ietf@ietf.org>; Thu, 26 Feb 2004 11:37:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwOW8-0006Ug-00
	for ietf@ietf.org; Thu, 26 Feb 2004 11:37:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwOVC-0006QU-00
	for ietf@ietf.org; Thu, 26 Feb 2004 11:36:47 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwOUX-0006LT-00
	for ietf@ietf.org; Thu, 26 Feb 2004 11:36:05 -0500
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>;
          Thu, 26 Feb 2004 11:36:04 -0500
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: License for downloading music - well!
Date: Thu, 26 Feb 2004 11:36:04 -0500
Message-ID: <20040226163604358.AAA650@hq.lindsayelec.com@rflooker1>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


The Electronic Frontier Foundation has proposed a scheme to decriminalize
file-swapping, whereby users would pay $5 a month in license fees. The
annual $3 billion this would net would compensate artists and record labels,
the group says.   San Jose Mercury News (2/26),   Wired (2/26)
           Posted on Thu, Feb. 26, 2004            
            License to allow music downloading proposed
            By Dawn C. Chmielewski
            Mercury News

            A leading Internet advocacy group Wednesday proposed legalizing
online file-sharing through a voluntary music license that would compensate
artists -- and decriminalize the actions of millions of music fans.

            The Electronic Frontier Foundation called on the music industry
to form a new collection agency to issue file-sharing licenses for a monthly
fee. The group said a fee of as little as $5 a person would net an estimated
$3 billion annually for the music industry, which currently earns no revenue
from the billions of songs exchanged through unlicensed services such as
Kazaa. And it would entitle the estimated 60 million Americans who use
file-trading services to continue swapping songs without fear of lawsuits.

=================

Dan says:

Well, this is a perfect way to make sure the status quo is maintained and
record companies continue to ad no value but receive compensation. Paypal
and micropayments have been horribly remiss in not developing adiquate
solutions to small payments. 

ASCAP and BMI do a perfectly horrible job of finding the smaller artistic
providers and redistributing income to them. They use a statistical model
for auditing. Would you like to be paid based in a 3% sample of your
efforts, randomly selected?

I appreciate the best intention of do-gooders. It seems unfortunate
micropayment systems seem to limp so badly.

regards to all,
Dan




From owner-ietf@ietf.org  Thu Feb 26 11:56:58 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24121
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 11:56:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwOlL-0004IQ-8e
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 11:53:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwOkm-0004Gk-1o
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 11:52:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24010
	for <ietf@ietf.org>; Thu, 26 Feb 2004 11:52:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwOkl-0000Ej-00
	for ietf@ietf.org; Thu, 26 Feb 2004 11:52:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwOk0-00008x-00
	for ietf@ietf.org; Thu, 26 Feb 2004 11:52:05 -0500
Received: from mail7.atl.registeredsite.com ([64.224.219.81] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwOjR-00000e-00
	for ietf@ietf.org; Thu, 26 Feb 2004 11:51:29 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail7.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1QGpSp5016283
	for <ietf@ietf.org>; Thu, 26 Feb 2004 11:51:28 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Thu, 26 Feb 2004 10:51:27 -0600
Message-ID: <403E2408.DF1D14BF@nma.com>
Date: Thu, 26 Feb 2004 08:51:20 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: digital signature request
References: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net> <200402261529.i1QFT7QB059427@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Vernon Schryver wrote:
> 
> The spam problem starts with accepting mail from strangers. 

This phrase is a good soundbite. I'd add:

The spam problem starts with *freely* accepting mail from strangers. 

If we force strangers to jump some hoops before their email can reach 
our mailboxes, it seems clear to me that we can still keep receiving 
email from strangers. Accountability (as in the "email caller ID" proposal 
by Microsoft) and identification (by requiring digital signatures) are
not enough. They are locally restricted in the application of laws, jurisdiction, and enforcement. Rogue messages due to spoofing, worms and 
virus cannot be prevented either. Spam could still contaminate list
traffic, even if list messages are signed by the listserver. Rubbish
in, rubbish  out.

Even though the pain is at the output, the problem is not at the 
output. The problem is at the input, when we freely accept email 
from strangers.  We need to provide mechanisms (plural) for 
selectively locking the input.

Comments?

Cheers,
Ed Gerck



From owner-ietf@ietf.org  Thu Feb 26 12:34:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28481
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 12:34:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwPL8-00069N-Dv
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 12:30:26 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwPKV-000684-C0
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 12:29:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27521
	for <ietf@ietf.org>; Thu, 26 Feb 2004 12:29:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwPKU-0004xi-00
	for ietf@ietf.org; Thu, 26 Feb 2004 12:29:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwPJf-0004sG-00
	for ietf@ietf.org; Thu, 26 Feb 2004 12:28:56 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwPJI-0004lp-00
	for ietf@ietf.org; Thu, 26 Feb 2004 12:28:33 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1QHSWBT007764
	for ietf@ietf.org env-from <vjs>;
	Thu, 26 Feb 2004 10:28:32 -0700 (MST)
Date: Thu, 26 Feb 2004 10:28:32 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402261728.i1QHSWBT007764@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: digital signature request
References: <403E2408.DF1D14BF@nma.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Ed Gerck 

> ...
> If we force strangers to jump some hoops before their email can reach 
> our mailboxes, it seems clear to me that we can still keep receiving 
> email from strangers. 

That is the e-postage and other...I'm sorry but the best phrase is
"snake oil."  There is no and can never be a hoop that is low enough
to pass enough human strangers but exclude spammers' computers.  If
your hoop passes mail from
  - the deaf
  - the blind
  - those who don't understand the spoken form of your native tongue
      as well as a computer
  - those who don't use graphics (e.g. lynx)
  - whose whose computers don't play audio files (mine doesn't)
  - those who don't have computers made within the last 5 years
  - the tired, confused, or intoxicated
  - the lazy or disinterested
  - the mentally challenged or just plain stupid
then it will also pass mail from spammer's computers.

The idea of forcing your correspondents to jump through hoops that
spammers' computers can't is fundamentally wrong and crazy.  If there
is one good characterization of the difference between human and
mechanical minds it is that machines are far better at jumping through
hoops than we are.  Computers are happy to try a bazillion times until
they get it right.  We get bored.  A spammer's computer will happily
continue trying to guess the answer to your puzzle as long as you let
it, or look for it in a crib sheet of 1,000,000,000 clues.  We not
only won't; we can't.

Only the meta-hoop of fear of prosecution might work.  419 spam
demonstrates its severe limitations.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Thu Feb 26 12:59:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29620
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 12:59:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwPem-0006zz-ST
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 12:50:44 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwPav-0006vS-5D
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 12:46:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29149
	for <ietf@ietf.org>; Thu, 26 Feb 2004 12:46:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwPau-0006sX-00
	for ietf@ietf.org; Thu, 26 Feb 2004 12:46:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwPZy-0006nk-00
	for ietf@ietf.org; Thu, 26 Feb 2004 12:45:46 -0500
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1AwPZJ-0006ct-00
	for ietf@ietf.org; Thu, 26 Feb 2004 12:45:05 -0500
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004022612423002007
 for <ietf@ietf.org>; Thu, 26 Feb 2004 12:42:30 -0500
Received: from centive.com ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 26 Feb 2004 12:40:42 -0500
Message-ID: <403E2F99.4040000@centive.com>
Date: Thu, 26 Feb 2004 12:40:41 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: License for downloading music - well!
References: <20040226163604358.AAA650@hq.lindsayelec.com@rflooker1>
In-Reply-To: <20040226163604358.AAA650@hq.lindsayelec.com@rflooker1>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Feb 2004 17:40:42.0297 (UTC) FILETIME=[A7D7DA90:01C3FC8F]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dan Kolis wrote:

>Paypal
>and micropayments have been horribly remiss in not developing adiquate
>solutions to small payments. 
>  
>
Check out Peppercoin (http://www.peppercoin.com), which has developed a 
stochastic model based on aggregating a user's payments.  They're 
getting some traction in the legal-download sector.  One of their 
advantages is that they don't actually perform the transaction; they 
just provide the software that layers on top of the merchant's existing 
transaction software.  So the merchant doesn't incur an ongoing cost, 
doesn't have their relationship with the bank disrupted, and doesn't 
have to worry about being stranded if the micropayment company goes out 
of business.

-- 
/================================================================\
|John Stracke      |jstracke@centive.com                         |
|Principal Engineer|http://www.centive.com                       |
|Centive           |My opinions are my own.                      |
|================================================================|
|Using strong crypto on the Internet is like using an armored car|
|to transport money from someone living in a tent to someone     |
|living in a cardboard box.                                      |
\================================================================/




From owner-ietf@ietf.org  Thu Feb 26 13:40:31 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01398
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 13:40:30 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwQL3-00006K-WA
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 13:34:25 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwQGV-0008Su-Ba
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 13:29:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01021
	for <ietf@ietf.org>; Thu, 26 Feb 2004 13:29:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwQGU-0003f5-00
	for ietf@ietf.org; Thu, 26 Feb 2004 13:29:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwQFi-0003Zv-00
	for ietf@ietf.org; Thu, 26 Feb 2004 13:28:55 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwQEm-0003UQ-00
	for ietf@ietf.org; Thu, 26 Feb 2004 13:27:56 -0500
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>;
          Thu, 26 Feb 2004 13:27:52 -0500
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: Peppercoin
Date: Thu, 26 Feb 2004 13:27:52 -0500
Message-ID: <20040226182752034.AAA527@hq.lindsayelec.com@rflooker1>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


Hi,

John S mentioned this micropayment scheme:

  http://www.peppercoin.com/General/FAQAnswerPage.ppp?keyID=helpfaq/faqs/Abo
utPeppercoin&topicIndex=3

Interesting, but its really built on information goods specifically. Like
tradedoor crypto sprinkled with dollar value connections.

Thanks. Interesting.

Unfortunately but realistically... treasuries like the US mint, etc define
what constitutes legal transactions and specie for that. 

Seems like Visa, Amex, etc have come reasonably close to currencies with
stand alone valuation.

An interesting field. Seems like the infrastructure of internet is more than
sufficient to implement any of this. 

regs to all,
Dan




From owner-ietf@ietf.org  Thu Feb 26 13:40:31 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01409
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 13:40:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwQL4-00006x-Df
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 13:34:26 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwQJd-0008Um-4W
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 13:32:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01178
	for <ietf@ietf.org>; Thu, 26 Feb 2004 13:32:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwQJc-00042t-00
	for ietf@ietf.org; Thu, 26 Feb 2004 13:32:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwQIq-0003x9-00
	for ietf@ietf.org; Thu, 26 Feb 2004 13:32:09 -0500
Received: from mail1.atl.registeredsite.com ([64.224.219.75] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwQIE-0003pW-00
	for ietf@ietf.org; Thu, 26 Feb 2004 13:31:30 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail1.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1QIVT5d027737
	for <ietf@ietf.org>; Thu, 26 Feb 2004 13:31:30 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Thu, 26 Feb 2004 12:31:27 -0600
Message-ID: <403E3B78.E0EAF976@nma.com>
Date: Thu, 26 Feb 2004 10:31:20 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: digital signature request
References: <403E2408.DF1D14BF@nma.com> <200402261728.i1QHSWBT007764@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Vernon Schryver wrote:
>
> The idea of forcing your correspondents to jump through hoops that
> spammers' computers can't is fundamentally wrong and crazy.  

Correspondents are also computers, humans don't do SMTP. 

> A spammer's computer will happily continue trying to guess the 
> answer to your puzzle as long as you let it, or look for it 
> in a crib sheet of 1,000,000,000 clues. 

Spammers need scale (because they get a very low return). Therefore,
part of the solution should be to deny scalability to spammers. You 
seem to think that is not possible. However, it is trivial for a 
receiver to impose and enforce *both* work and time burdens to receive 
emails from strangers -- at the MTA *and* at the MUA levels. 

For example, my MTA could enforce large time delays at every step to 
complete the SMTP session if the headers contain something suspicious 
like "Received: from ([127.0.0.1])". Also, my MTA could require message 
encryption and/or MAC using *my* PK (imposing a burden per message). 

Look up tables and computational power cannot help spammers in such
case. "Jumping through the hoops" is not optional and will take work
and time, that my MTA can increase at will -- as much as might be 
necessary to be an effective deterrent to abuse by strangers.

Cheers,
Ed Gerck



From owner-ietf@ietf.org  Thu Feb 26 13:44:17 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01746
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 13:44:17 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwQRt-0000kn-RI
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 13:41:29 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwQRG-0000Uz-N3
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 13:40:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01467
	for <ietf@ietf.org>; Thu, 26 Feb 2004 13:40:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwQRF-0004qC-00
	for ietf@ietf.org; Thu, 26 Feb 2004 13:40:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwQQM-0004kU-00
	for ietf@ietf.org; Thu, 26 Feb 2004 13:39:54 -0500
Received: from mail4.dynamicsoft.com ([63.110.3.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwQPs-0004eT-00
	for ietf@ietf.org; Thu, 26 Feb 2004 13:39:25 -0500
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id i1QIcrUY029920;
	Thu, 26 Feb 2004 12:38:53 -0600 (CST)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <10MYQN73>; Thu, 26 Feb 2004 12:38:53 -0600
Message-ID: <9ACE0CEE075B494096C86C23878BF85906A32B@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Aaron Falk'" <falk@ISI.EDU>, Joe Abley <jabley@isc.org>
Cc: Matt Holdrege <matt.holdrege@verizon.net>, ietf@ietf.org,
        Joe Touch
	 <touch@ISI.EDU>
Subject: RE: power in Korea..
Date: Thu, 26 Feb 2004 12:38:43 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> -----Original Message-----
> From: Aaron Falk [mailto:falk@ISI.EDU]
> 
> Has anybody tried this kind of trick (putting the SIM in 
> another phone) 
> with a T-mobile sim?  I know that T-mobile binds the phone to the sim 
> but don't know if they bind the sim to the phone.
> 
> --aaron
> 

As of three years ago, they did not. On the other hand,
my research so far has failed to turn up a roaming partner
for T-Mobile USA in Korea, so I don't think it will do
much good.

/a



From owner-ietf@ietf.org  Thu Feb 26 14:21:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03460
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 14:21:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwQwn-0002Rm-Sd
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 14:13:25 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwQrR-0002Km-Nv
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 14:07:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03094
	for <ietf@ietf.org>; Thu, 26 Feb 2004 14:07:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwQrO-0000Ep-00
	for ietf@ietf.org; Thu, 26 Feb 2004 14:07:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwQqc-00009D-00
	for ietf@ietf.org; Thu, 26 Feb 2004 14:07:03 -0500
Received: from iserver.sj.symbol.com ([63.145.233.51])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwQq2-00002p-00
	for ietf@ietf.org; Thu, 26 Feb 2004 14:06:26 -0500
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 i1QIsGAU010105
	for <ietf@ietf.org>; Thu, 26 Feb 2004 10:54:16 -0800 (PST)
Received: from SJ-DOM-MTA by gwianameserver.sj.symbol.com
	with Novell_GroupWise; Thu, 26 Feb 2004 11:06:20 -0800
Message-Id: <s03dd32c.045@gwianameserver.sj.symbol.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2
Date: Thu, 26 Feb 2004 11:06:05 -0800
From: "Clint Chaplin" <cchaplin@sj.symbol.com>
To: <spamtrap.ietf@dja.mailme.org>, <ietf@ietf.org>
Subject: Re: digital signature request
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Which is a royal pain for me: my email client (mandated by work) doesn't
alllow me to filter on CC: or BCC: addresses.  Yuck.


>>> Dave Aronson <spamtrap.ietf@dja.mailme.org> 2/26/04 05:29:04 >>>
On Wed February 25 2004 16:15, Dean Anderson wrote:

 > There are many ways to reasonably accurately identify mail to this
 > list and distinguish it from all others: It is sent "to:
 > ietf@ietf.org".

Nitpick: ietf@ietf.org could be in the Cc, or worse yet Bcc, field.

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.



________________________________________________________________________
This email has been scanned for computer viruses.

Clint (JOATMON) Chaplin



From owner-ietf@ietf.org  Thu Feb 26 15:01:20 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05588
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 15:01:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwRdQ-00043q-JD
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 14:57:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwRcq-00042H-82
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 14:56:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05502
	for <ietf@ietf.org>; Thu, 26 Feb 2004 14:56:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwRcp-0005Pg-00
	for ietf@ietf.org; Thu, 26 Feb 2004 14:56:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwRbp-0005KN-00
	for ietf@ietf.org; Thu, 26 Feb 2004 14:55:50 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[2j8ebmedw0071Y26/T/PXZQbH3nluU0M])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwRbO-0005FM-00
	for ietf@ietf.org; Thu, 26 Feb 2004 14:55:23 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id 868BFA79D9; Thu, 26 Feb 2004 14:53:36 -0500 (EST)
Date: Thu, 26 Feb 2004 14:45:21 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Ed Gerck <egerck@nma.com>
Cc: ietf@ietf.org
Subject: Re: digital signature request
In-Reply-To: <403E3B78.E0EAF976@nma.com>
Message-ID: <Pine.LNX.4.44.0402261348570.6338-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 26 Feb 2004, Ed Gerck wrote:

> Spammers need scale (because they get a very low return). Therefore,
> part of the solution should be to deny scalability to spammers. You 
> seem to think that is not possible. However, it is trivial for a 
> receiver to impose and enforce *both* work and time burdens to receive 
> emails from strangers -- at the MTA *and* at the MUA levels. 

  a) Moore's law

  b) Economics

  c) Arithmetic

  d) Clustering

  e) Human nature

among many other reasons why this idea will not fly.  

Work and time burdens are not uniform or static because of Moore's law
-- a modern system might be eight to thirty-two times more powerful than
a nearly obsolete system on the same network.  Are we going to deny
people on the obsolete system the ability to send mail because we're
trying to slow down the fastest system enough to make a difference?

Economics alone would crush the idea.  A large institution is already
paying large sums of money supporting its primary MTAs because they are
receiving hundreds of thousands to millions of messages a day.  You
propose to ask them to what -- double?  triple?  ntuple where n is
whatever integer you think it has to be to STOP SPAM?  They'd implement
institutional-level MTA-based spam filters before they did that -- it
would be cheaper.

Then there is arithmetic.  What, exactly, is enough of a work burden
sufficient to be a burden to a spammer?  A spammer who sends anywhere
from 10000 to 10000 messages a day can make money, from what I've read.
That is order of a message every 1 to 10 seconds, and very little of
this time would be spent consuming bandwidth.  Note that this is a
tens to hundreds of times as much time as is currently required, and is
NOT easy to arrange.  Since the amount of arithmetic determines the
ntupling of server expenses for every large mail operation on the
planet, you are facing pressure from above to keep it cheap and from
below to make it effective.

Clustering, alas, will frustrate you.  A spammer can afford to add cheap
hardware for solving the problem at the high end of Moore's Law faster
than legitimate shops can afford to add expensive and reliable hardware
to handle enterprise mail.  It won't even cost them more bandwidth,
since they can easily make their 100K/day nugget with a fairly cheap ISP
connection fronting their whole cluster.

Finally, there is human nature.  You proposed solution is cumbersome and
expensive, a cure literally worse than the disease.  Spam now is a
hassle, but automated tools ameliorate it to a large extent for most
users.  Too many agencies at all levels of the internet would find it a
hindrance with little advantage.  So it will never be adopted.

> For example, my MTA could enforce large time delays at every step to 
> complete the SMTP session if the headers contain something suspicious 
> like "Received: from ([127.0.0.1])". Also, my MTA could require message 
> encryption and/or MAC using *my* PK (imposing a burden per message). 

Or it could just reject them out of hand.  Remember, the burden per
message simply cannot be scaled to where a spammer would care without
bringing the entire Internet's mail transport system to its knees.

> Look up tables and computational power cannot help spammers in such
> case. "Jumping through the hoops" is not optional and will take work
> and time, that my MTA can increase at will -- as much as might be 
> necessary to be an effective deterrent to abuse by strangers.

It would indeed, and that's the problem.  In order to be effective, your
MTA has to increase it to where it is as big a "deterrent" to use by
strangers as it is to abuse by strangers.

   rgb

> 
> Cheers,
> Ed Gerck
> 

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Thu Feb 26 16:11:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09416
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 16:11:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwSfo-0001Yb-G4
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 16:04:00 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwSdf-0001Tx-9o
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 16:01:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09220
	for <ietf@ietf.org>; Thu, 26 Feb 2004 16:01:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwSde-00057Y-00
	for ietf@ietf.org; Thu, 26 Feb 2004 16:01:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwSch-00052m-00
	for ietf@ietf.org; Thu, 26 Feb 2004 16:00:48 -0500
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwSbo-0004yJ-00
	for ietf@ietf.org; Thu, 26 Feb 2004 15:59:52 -0500
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id 24829E0646; Thu, 26 Feb 2004 15:59:53 -0500 (EST)
Date: Thu, 26 Feb 2004 15:59:53 -0500
From: John Leslie <john@jlc.net>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Principles of Spam-abatement
Message-ID: <20040226205953.GA68458@verdi>
References: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net> <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

   I strongly recommend gathering some principles of spam-abatement to
enlighten the spam BOF at IETF-59. (I'd be happy to edit such a
document, but it might be better to chose someone who will attend
IETF-59...

Iljitsch van Beijnum <iljitsch@muada.com> wrote:
> 
> If we can communicate the fact that a message is discarded because it 
> was categorized as spam back to the sender without adverse side 
> effects, then occasional false positives aren't much of a problem.

   I nominate this statement for #1 on that list of principles.

--
John Leslie <john@jlc.net>



From owner-ietf@ietf.org  Thu Feb 26 17:48:42 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14369
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 17:48:42 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwUC5-0005Lm-5S
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 17:41:25 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwUBU-0005JK-QV
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 17:40:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14165
	for <ietf@ietf.org>; Thu, 26 Feb 2004 17:40:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwUBT-0000PY-00
	for ietf@ietf.org; Thu, 26 Feb 2004 17:40:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwUAU-0000JS-00
	for ietf@ietf.org; Thu, 26 Feb 2004 17:39:46 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwU9V-0000Ck-00
	for ietf@ietf.org; Thu, 26 Feb 2004 17:38:45 -0500
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i1QMchnp025123
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 26 Feb 2004 14:38:44 -0800 (PST)
Received: from [205.214.163.20] (vpn-10-50-0-27.qualcomm.com [10.50.0.27])
	by sabrina.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i1QMcTlH025794;
	Thu, 26 Feb 2004 14:38:40 -0800 (PST)
Mime-Version: 1.0
X-Sender: hardie@mage.qualcomm.com
Message-Id: <p06020401bc64251fe8d7@[205.214.163.20]>
In-Reply-To: <20040226205953.GA68458@verdi>
References: 
 <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net>
 <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com>
 <20040226205953.GA68458@verdi>
Date: Thu, 26 Feb 2004 14:38:28 -0800
To: John Leslie <john@jlc.net>, Iljitsch van Beijnum <iljitsch@muada.com>
From: Ted Hardie <hardie@qualcomm.com>
Subject: Re: Principles of Spam-abatement
Cc: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Please note that the BoF scheduled for Korea, MARID, has a
very specific topic and that discussion of other spam-related
issues is not appropriate for that session. The BoF agenda is
available at:

http://www.ietf.org/ietf/04mar/marid.txt

To quote the salient part of the agenda:

>This BoF will be strictly limited to measures related to MTA 
>authentication; no
>other anti-spam measures or topics will be considered.  The BoF will 
>explicitly
>consider how DNS-based MTA authentication mechanisms would be implemented and
>deployed, and it will consider the impact on the overall DNS infrastructure of
>this deployment.

With best regards,
			Ted Hardie
			co-chair, MARID BoF



At 3:59 PM -0500 02/26/2004, John Leslie wrote:
>    I strongly recommend gathering some principles of spam-abatement to
>enlighten the spam BOF at IETF-59. (I'd be happy to edit such a
>document, but it might be better to chose someone who will attend
>IETF-59...
>
>Iljitsch van Beijnum <iljitsch@muada.com> wrote:
>>
>>  If we can communicate the fact that a message is discarded because it
>>  was categorized as spam back to the sender without adverse side
>>  effects, then occasional false positives aren't much of a problem.
>
>    I nominate this statement for #1 on that list of principles.
>
>--
>John Leslie <john@jlc.net>




From owner-ietf@ietf.org  Thu Feb 26 20:01:28 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19708
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 20:01:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwWEp-0001e2-N7
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 19:52:23 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwWEN-0001cJ-4Q
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 19:51:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19383
	for <ietf@ietf.org>; Thu, 26 Feb 2004 19:51:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwWEL-0004hL-00
	for ietf@ietf.org; Thu, 26 Feb 2004 19:51:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwWDT-0004bp-00
	for ietf@ietf.org; Thu, 26 Feb 2004 19:51:00 -0500
Received: from sentosa.post1.com ([202.27.17.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1AwWCe-0004R7-00
	for ietf@ietf.org; Thu, 26 Feb 2004 19:50:09 -0500
Received: (qmail 30901 invoked from network); 27 Feb 2004 01:12:06 -0000
Received: from icsf.ida.gov.sg (HELO pobox.org.sg) (210.24.193.10)
  by sentosa.post1.com with SMTP; 27 Feb 2004 01:12:06 -0000
Message-ID: <403E9401.8070104@pobox.org.sg>
Date: Fri, 27 Feb 2004 08:49:05 +0800
From: James Seng <jseng@pobox.org.sg>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, zh-cn, zh-tw, ja, ko
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
CC: "Robert G. Brown" <rgb@phy.duke.edu>, IETF Discussion <ietf@ietf.org>
Subject: Re: digital signature request
References: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net> <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com>
In-Reply-To: <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Can we don't pretend we can solve the spam problem on ietf@ietf.org?

james

Iljitsch van Beijnum wrote:

> On 26-feb-04, at 15:05, Robert G. Brown wrote:
> 
>> It has been pointed out several times now that unless you are willing to
>> receive mail only from a small, closed group of individuals that all
>> agree to use digital signatures and whose mail you whitelist while
>> blacklisting EVERYTHING ELSE you are right back where you are right now.
> 
> 
> If we can communicate the fact that a message is discarded because it 
> was categorized as spam back to the sender without adverse side effects, 
> then occasional false positives aren't much of a problem.
> 
> As for signing list messages: some practical experience would be good 
> here. I'm not sure this list is the best choice to gain it, though.
> 
> 
> 
> 



From owner-ietf@ietf.org  Thu Feb 26 20:18:03 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20520
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 20:18:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwWa8-0002ik-S3
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 20:14:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwWZk-0002gh-Fj
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 20:14:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20363
	for <ietf@ietf.org>; Thu, 26 Feb 2004 20:13:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwWZi-0006oS-00
	for ietf@ietf.org; Thu, 26 Feb 2004 20:13:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwWYo-0006iq-00
	for ietf@ietf.org; Thu, 26 Feb 2004 20:13:03 -0500
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwWXt-0006YS-00
	for ietf@ietf.org; Thu, 26 Feb 2004 20:12:05 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1R1BIMl026497
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 26 Feb 2004 20:11:22 -0500
Date: Thu, 26 Feb 2004 20:11:18 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: "Robert G. Brown" <rgb@phy.duke.edu>
cc: gnulinux@pacinfo.com, <ietf@ietf.org>
Subject: Re: digital signature request
In-Reply-To: <Pine.LNX.4.44.0402260749030.6202-100000@lilith.rgb.private.net>
Message-ID: <Pine.LNX.4.44.0402261726110.30588-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.0 required=5.0 tests=AWL,DRASTIC_REDUCED 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 26 Feb 2004, Robert G. Brown wrote:

> Why in the world does anyone think that digital signature maps with
> several orders of magnitude more entities to track, more complexity, and
> hence more opportunities for spoofing and finagling are going to succeed
> where simple DNS hostname lookup has failed?

The reason is a little clearer when one considers that the main proponents
of this idea have businesses or business plans to sell services for
running the necessary infrastructure. As Bill Gates proved, the quickest
way to astronomical wealth is to sell something very cheap to nearly
everyone on the planet.  Since then, many people have been trying to come 
up with similar schemes.  Few have succeeded.

> IMO a "no anonymous mail" rule (no mail accepted anywhere from
> unregistered hosts) coupled with pretty stiff fines and legal penalties
> for spam would associate accountability and penalty and cause an
> immediate and drastic reduction of the problem.  Holding ISPs (and
> providers of open relays and proxies) liable for the fines of their
> clients if they bolt or "have no assets" would give ISPs a very strong
> incentive to police their clients.  Obviously, the two would have to
> come about together -- it is less useful to have fines and penalties
> when the originating hosts have unregistered IP numbers that change
> every two days and are nearly impossible to trace.

There are reasons to have "anonymous email" as well as reasons to operate
open relays**.  Many ISPs operate open relays, and while the number of
open relays continues to grow--few are open by mistake--the number of
"spammers" abusing open relays continues to decline. Last May, the FTC
reported that only 5% of spam involves open relays. Recently, I had a hard
time finding an open relay abuse example in my current spamfolder. I'd
says its now even less than 5%.  Open relays provide no benefits to
spammers that they don't already have.  We also have email senders that
only send mail, but don't receive mail. This type of mail is
indistinguisable from anonymous email, because there is no way to "verify"
the sender. But there are also reasons to have license-plate anonymous
email as well, where the message isn't truly anonymous, but unless it is
part of a criminal act, no one can find out the identity.

It is a mistake to assume that only people use email. 

Below are two recent messages on the subject of Verizon "testing" whether
an email sender receives email.  This "test" isn't helping Verizon filter
spam.  In both the case I was responding to, and the case that Randy Bush
was responding to, the people were experiencing problems with temporary
SMTP error messages, and wondering what the problem was.

On Sat, 21 Feb 2004, Dean Anderson wrote:

>
> Verizon is trying to do a "sender verification test".  This is a dumb
> idea whose time didn't come.  But no matter.
>
> Here is a message from Randy Bush on the subject.  I frequently disagree
> with Randy, but in this case, I think he has the right idea.
>
>               --Dean
>
>
> =================
>
> > I think he's saying that they were unable to perform the
> > validation hence the 450.  If the validation was successful,
> > they'd return a 200 series code, if it was unsuccessful, they
> > would return a 500 series code.
>
> nice words, but crap.  due to needs to spool mail for sites in
> countries with very poor connectivity, mail spool time here is
> quite long.  if verizon and others seem unable to decide in weeks,
> why should i pay the penalty?
>
> but, i guess the problem is easily solved with exim config.  i have
> set it so that if it can not deliver to verizon in say one hour, it
> dumps the mail.
>
>     verizon.net        *           F,1h,5m
>
> life is simple, except for verizon users i guess.
>
> randy
>
>

On Sat, 21 Feb 2004, Dean Anderson wrote:

> Shouldn't reply to my own message. But in case it isn't clear, the
> reason this is a bad idea is:
>
> 1) Performance. Verizon's mail server has essentially doubled its load.
> If a mail server or nameserver (theirs or yours) is slow, it will cause
> a temporary failure, as you saw. If their nameserver is slow, or one
> fails, it will cause a performance knee with a storm of increasing defer
> retries which will quickly bring the server to its knees.
>
> 2) Many sites monitor "NOQUEUE" connections, and automatically blacklist
> those IP addresses which make too many NOQUEUE connections. A lot of
> "testing" by Verizon will automatically get them blacklisted.
>
> 3) There is no guarantee that a from: address receives email. This is a
> feature that spammers certainly exploit, but there is are legitimate
> reasons for this: many machine email senders send mail and never receive
> mail. Any mail for those robots will be rejected.  So the premise of the
> test (that every sender can be verified) is invalid.  Of course, any one
> stupid enough to violate 1 and 2 above, will certainly be unable to
> grasp the subtlety of this.
>
>               --Dean
>



> I think that this is fairly unlikely to come to pass, as lawmakers are
> as likely as not to be spammers of a sort in their own right, soliciting
> campaign contributions, distributing political "newsletters", using
> email in a variety of edgy, mass distribution ways.  OTOH, they also get
> spammed, as do their families, so one never knows -- some states are
> slowly moving to control spam in law.

Actually, the CAN-SPAM act supercedes all state laws on the subject.  
States have no or very little say in spam legislation.

> In the meantime, instead of burning a huge amount of human time and
> energy just DISCUSSING the issue of universal keysigned mail (let alone
> the hassle of implementing it for just one site), perhaps we can each
> (in the words of Candide) "tend our own garden" and use one of the many
> excellent filtering mechanisms already available, while teaching our
> users to do the same.  If the proposal meets this much resistance and
> "why bother" attitude here, imagine the resistance it will meet at the
> ISP level and out in the real world, where time spent implementing
> ANYTHING is pure money and maintenance time down the drain.
> 
>    rgb
> 
> 

** The reasons for running open relays are obvious from the definition of
an open relay--An open relay is any relay which provides unauthenticated
service to anyone outside of the assigned IP address space.

There are a lot of people and computers outside of our assigned IP address
space who want to purchase some services from us.  There are quite a lot
of people or things who can't use SMTP AUTH either because their software
doesn't support the protocol, or because we don't have per-user accounts
for them. Those who don't have per-user accounts or don't receive email
can't use POP before SMTP, so they need open relay.  There are quite a lot
of people and electronic agents that can't use SMTP AUTH. There are also
quite a lot of people and electronic agents that can't use POP before
SMTP.

We have leased line customers with many offices that buy connectivity from
us and from other providers for some offices, yet use our relays. (They
want our HA services for their main office, but we are too expensive for
their outlying offices)  We have leased line customers who have outsourced
their email boxes to another provider that doen't provide SMTP relay
service outside their IP Address space.  For them, we relay for the domain
of the other provider (RMX can never work).  Others get leased access from
us, but dialup from someone else, and don't want to change configuration.  
We have customers that run their own mailservers, but want backup relay
service from us. Others that are consultants, and are often in the clients
office on the clients DHCP, and don't want to change configuration.  Etc,
etc, etc.

Having run open relays since 1996 (and before, but they weren't "my"  
servers until 1996), I am very familiar with the abuse of open relays.  
Though I didn't experience any open relay abuse before 1997, and then only
after telling some radicals that there were good reasons to run open
relays, it was my business interest to find out who was behind that abuse.  

The abuse of open relays is mainly done by radical antispammers attempting
to mail bomb people.  Real spammers never abused our relays--Not in 8
years of operations.  But we have tracked down a number of open relay
abusers. Our abusers were either 1) people not sending spam, but not
having permission to use our relays either, or 2) radical antispammers
(sometimes admins at other ISPs) who were either trying to get us to close
our relays, or trying to abuse someone else.  In one case, an abuse admin
at Verio was fired for repeatedly abusing our relays, and posted his story
to the spam-l list, blaming me for his termination.

When we blocked the open relay blacklists from scanning, our abuse dropped
off dramatically.  I did tests with submitting different IP addresses to
different blacklists, and logging the abuse and SMTP connections to each
of the addresses, and then "closing" the relay and having it "retested",
and then measuring the number of connections. The abuse rate was directly
related to the "advertisement" of the address by the blacklist.  I
concluded that the open relay blacklists were promoting the abuse of open
relays. 

We still get periodic abuse of our relays. Generally, after I post a
message like this, the abuse rate will spike.  We detect and block nearly
all of this abuse. Radical antispammers/open relay abusers never seem to
consider that relay use is probably logged, and that analysis of the logs
can reveal a great many things. Indeed, it was the tracking of relay
abuse, and the failure to find real spammers in the abuse of our relays
contrasted with the finding of antispammers performing the abuse that
first suggested to me that radical anti-spammers may be behind much spam
abuse.

The present decline of open relay abuse in the face of increasing numbers
of open relays also suggests a link to anti-spammers formerly conducting
the abuse but now becoming disinterested in doing so.  It seems that the
radicals think that by conducting abuse, they can get people motivated to
close relays, ban spam, etc. But in fact, the statistics of spam show
other things. CAN-SPAM is not blocking any spam, but is enabling the real
spammers to be distinguished from the fake spammers.  Whatever the fake
spammers do, their activities will be revealed.  If they quit, and real
spammers don't quit, we will see a reduction in spam that will be
attributed to the fake spammers. If they don't quit, we have the tools to
find them.

The really funny/odd thing about open relay abuse, is that it was only
radical antispammers (or the misled/uninformed) who believed that open
relays were involved in spam or useful to spammers.  The radicals believed
that by mailbombing people they thought were spammers, they were somehow
helping fight spam. The "proof"  of open relay abuse was mostly, if not
entirely, just the efforts of other radicals anti-spammers.  Real spammers
appear never to have shared the antispammer viewpoint on open relays.  If
they did, it was for a very short time.

MAPS RSS tried to publish "proof" of spam sent through open relays, but
examination of our logs revealed that the "spam" they published about one
of our relays was only sent to 4 MAPS-associated people. Dave Rand and
Paul Vixie were two of them.  Even that wasn't a genuine spam. It was just
a spam-like event staged by anti-spammers. Fake spam by fake spammers.

Most of the people who thought (or still think) that SMTP AUTH or POP
before SMTP were anti-spam solutions had limited experiences with email
services, and those experiences were generally limited to residential
(dialup/cable/dsl) ISP services or small companies that run their own mail
server and only provide accounts to their employees.  These people often
put their spam solutions in the context of "only people use email, and if
we could identify the people, we could exclude spammers".  The fallacy is
exposed by the fact that email isn't only used by people and that in a
civil context, you can't be certain of the identity of the other party.

So you ask, where did the notions about open relay abuse come from and is
there any truth to them?  If fact, there were problems with _anonymous_
relays, which are different from open relays. Sometime between 1993, when
the _anonymous_ relay problem was fixed, and 1997, when I first
encountered people talking about closing open relays, the radicals seem to
have lost track of the difference.  As I explain below, this problem has
nothing to do with open-ness, but rather a misplaced trust in reverse DNS
in 1986.


Subject : Re: A historical perspective on 
draft-ietf-dnsop-inaddr-required-04.txt
----- Message Text -----
On Wed, 2 Apr 2003, Dean Anderson wrote:

>
> Here is a message from Rob Austein to the TCP-IP mailing list from 1986,
> which puts a historical perspective on things.  Rob is responding to a
> message from gds@spam.istc.sri.com. Given this was in 1986, the
> spam.itsc.sri.com hostname was well ahead of its time.
>
> Rob knew then that "the silly net" wouldn't have reverse working all the
> time, but thought this was broken. Apparently, he was under the
> impression then that reverse was not optional, but could be "broken".
>
> More significantly (in retrospect), Rob advocates that one shouldn't put
> numeric addresses in Received headers.  Of course, Rob wasn't the only
> person with this viewpoint. It is unfair to place this solely on Rob's
> shoulders. Although not clear from this message, he is accompanied in
> this viewpoint by many then, and who still share this view today.
>
> To the later chagrin of so many people, Rob's viewpoint was implemented
> in Sendmail.  It is unfortunate because we later learned by hard
> experience that if one used a machine without Reverse, or if reverse
> were configured to return misleading results, then one could send
> completely anonymous and untraceable email through a mail relay. It had
> nothing to do with the openness of the relay, though that was the early
> "fix".  Of course, even "closed" relays could be abused, and it would be
> impossible to identify the user of the relay.  The anonymous spam relay
> exploit was the result of misplaced trust placed in reverse, and the
> fact that an IP address wasn't put in the Received: header. It had
> nothing to do with the openness of the relay.  Some say this ability to
> anonymously abuse relays caused spam. Eventually, this behavior was
> changed in Sendmail and other MTA's in the early '90s.  Since then, it
> has been impossible to send anonymous email through an open or closed
> relay. This fact has not stopped people from promoting myths about open
> relays, however.
>
> It is really historically interesting that 17 years later, after so many
> obvious faults, failures, exploits, and even spam caused by misplaced
> trust in reverse DNS, that the same people are still promoting the same
> ideas.  It is a historical irony that some of the most vocal and ardent
> proponents of Reverse DNS want to use it to prevent spam.
>
>               --Dean
>
>
> Message from Rob Austein (SRA@XX.LCS.MIT.EDU)
> Wed, 1 Oct 1986 16:00 EDT
> ==============
>
>     Date: Tuesday, 30 September 1986 13:29-EDT
>     From: The lost Bostonian <gds@spam.istc.sri.com>
>     To: header-people@mc.lcs.mit.edu, tcp-ip@sri-nic.arpa
>
>
>     If it is true that all IP implementations enable a server program to
>     determine the IP address of its peer, then the HELO command, and its
>     response could be eliminated, which would save us a few bytes.
> 
> 
> You are assuming that it is always possible to translate addresses to
> names and vice versa. Unfortunately, there are some people out in the
> world running domain nameservers who are totally clueless about what
> they are doing, and there are others who have the misfortune to be
> stuck behind a losing gateway or otherwise be unreachable much of the
> time. Do you really want to make it impossible to receive mail from
> some host because a third party is broken? Or have to put numeric
> addresses into the Recieved headers?
> 
> 
> The answer is to fix the silly net, not throw away features to save
> two IP packets.
> 
> 
> --Rob
> 
> ====================
> 
> 
> 
> 







From owner-ietf@ietf.org  Thu Feb 26 20:35:06 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21300
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 20:35:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwWqa-0003gA-3h
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 20:31:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwWqG-0003eO-Hh
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 20:31:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21078
	for <ietf@ietf.org>; Thu, 26 Feb 2004 20:31:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwWqE-0000m3-00
	for ietf@ietf.org; Thu, 26 Feb 2004 20:31:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwWpO-0000gl-00
	for ietf@ietf.org; Thu, 26 Feb 2004 20:30:11 -0500
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwWol-0000YN-00
	for ietf@ietf.org; Thu, 26 Feb 2004 20:29:31 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i1R1T1Vl026768
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 26 Feb 2004 20:29:02 -0500
Date: Thu, 26 Feb 2004 20:29:01 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: "Robert G. Brown" <rgb@phy.duke.edu>
cc: gnulinux@pacinfo.com, <ietf@ietf.org>
Subject: Re: digital signature request
In-Reply-To: <Pine.LNX.4.44.0402261726110.30588-100000@cirrus.av8.net>
Message-ID: <Pine.LNX.4.44.0402262017570.30588-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I should also note that my own message below that I quoted is hypocritical
on my part. If the mail was IETF mail or other important email, I would
have a different opinion. Of course, It was hypocritical of me to say that
mail to others is any less important to its senders and recipients.  I
should not have encouraged this type of behavior.  It shows that I too can
be disgusted with things, and encourage an inappropriate response to
stupid behavior.  It is certainly something that one should try to avoid
in oneself, and criticize in others.

		--Dean

> On Sat, 21 Feb 2004, Dean Anderson wrote:
> 
> >
> > Verizon is trying to do a "sender verification test".  This is a dumb
> > idea whose time didn't come.  But no matter.
> >
> > Here is a message from Randy Bush on the subject.  I frequently disagree
> > with Randy, but in this case, I think he has the right idea.
> >
> >               --Dean
> >
> >
> > =================
> >
> > > I think he's saying that they were unable to perform the
> > > validation hence the 450.  If the validation was successful,
> > > they'd return a 200 series code, if it was unsuccessful, they
> > > would return a 500 series code.
> >
> > nice words, but crap.  due to needs to spool mail for sites in
> > countries with very poor connectivity, mail spool time here is
> > quite long.  if verizon and others seem unable to decide in weeks,
> > why should i pay the penalty?
> >
> > but, i guess the problem is easily solved with exim config.  i have
> > set it so that if it can not deliver to verizon in say one hour, it
> > dumps the mail.
> >
> >     verizon.net        *           F,1h,5m
> >
> > life is simple, except for verizon users i guess.
> >
> > randy
> >
> >




From owner-ietf@ietf.org  Thu Feb 26 23:13:37 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27512
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 23:13:37 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwZEd-0003t8-IB
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 23:04:23 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwZEJ-0003qb-HP
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 23:04:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27130
	for <ietf@ietf.org>; Thu, 26 Feb 2004 23:04:00 -0500 (EST)
From: hinden@iprg.nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwZEH-0001Bc-00
	for ietf@ietf.org; Thu, 26 Feb 2004 23:04:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwZDO-00014O-00
	for ietf@ietf.org; Thu, 26 Feb 2004 23:03:07 -0500
Received: from [61.144.97.124] (helo=ietf.org)
	by ietf-mx with smtp (Exim 4.12)
	id 1AwZCY-0000wN-00
	for ietf@ietf.org; Thu, 26 Feb 2004 23:02:15 -0500
To: ietf@ietf.org
Subject: stolen
Date: Fri, 27 Feb 2004 12:02:19 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="10057836"
Message-Id: <E1AwZCY-0000wN-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.6 required=5.0 tests=MSGID_FROM_MTA_SHORT,
	NO_REAL_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

--10057836
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_NETSKY.B in file misc.com (in misc.zip)
The file is deleted.

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

--10057836
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

read it immediately!

--10057836
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

misc.zip is removed from here because it contains a virus.

---------------------------------------------------------
--10057836--




From owner-ietf@ietf.org  Thu Feb 26 23:39:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28436
	for <ietf-archive@odin.ietf.org>; Thu, 26 Feb 2004 23:39:29 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwZie-0005QP-A4
	for ietf-list@asgard.ietf.org; Thu, 26 Feb 2004 23:35:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwZhp-0005Mb-2g
	for ietf@asgard.ietf.org; Thu, 26 Feb 2004 23:34:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28249
	for <ietf@ietf.org>; Thu, 26 Feb 2004 23:34:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwZhn-0004Hw-00
	for ietf@ietf.org; Thu, 26 Feb 2004 23:34:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwZgq-0004Bk-00
	for ietf@ietf.org; Thu, 26 Feb 2004 23:33:34 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwZg1-00041e-00
	for ietf@ietf.org; Thu, 26 Feb 2004 23:32:42 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 44B3861BB9
	for <ietf@ietf.org>; Fri, 27 Feb 2004 05:32:11 +0100 (CET)
Date: Thu, 26 Feb 2004 20:31:02 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Agenda, GEN-AREA meeting
Message-ID: <43418542.1077827462@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

This may have some general interest.....

Comments to solutions@alvestrand.no, please....
--------------------------------------------------------------
Agenda for the GEN-AREA meeting in Seoul

Chair: Harald Alvestrand, GEN AD

Date: Monday, March 1, 2004
Time: 1930-2200

Purpose of meeting:
- Go through the "high level picture" of where the problems in the IETF 
are, and what is being done to address them
- Look at specific proposals that do not have WG meetings to look at them, 
and provide a quick "thumbs up/thumbs down" feedback indication, which can 
serve as feedback to the proposers and a hint to the IESG on how to handle 
the proposals.

People who wish to comment on the proposals will be expected to have read 
the proposals before the meeting.

Agenda:

19:30 Welcome, scribe and agenda bashing
19:40 Overview - Harald Alvestrand

See http://www.ietf.org/u/ietfchair/change-status.html
See also ICAR, NEWTRK charters; PROTO charter; EDU charter and website

19:55 Notes from specific non-WG/non-BOF efforts
 - EDU team: working to make sure IETF participants know as much as
   possible on how to be effective (5 min)
 - MPOWR discussions: What the mailing list discussions have led
   to (10 min)

20:10 Specific proposals for change - "thumbs-up" / "thumbs-down"
  Rules of the game / intro - Harald (5 min)

  20:15 An IETF Ombudsman - Avri Doria (10 min)
  See section 10 of draft-iesg-hardie-outline-01.txt

  20:30 Mailing list procedure change - Margaret Wasserman (10 min)
  draft-wasserman-rfc2418-ml-update-00.txt (10 min)

  20:40 Procedures for changing procedures - John Klensin (20 min)
  Documents:
  draft-klensin-process-july14-00 ("Trust the IESG")
  draft-klensin-process-planb-00 ("Distrust the IESG")

  21:00 PROTO team presentation and discussion (25 min)
  The PROTO-Team is working to improve the effectiveness,
  scalability and openness of our document handling procedures
  and the tools that support them.
  See http://psg.com/~mrw/PROTO-Team/.

  Specific items for discussion:
  - Intro - Margaret Wasserman
  - Definition of shepherding - Allison Mankin
    http://psg.com/~mrw/PROTO-Team/PROTO-Shepherding.html
  - Planned PROTO Team Pilots:
    - WG Chair Ballot Write-ups - Aaron Falk
      http://psg.com/~mrw/PROTO-Team/WGChair-Writeup.html
    - Shepherding AD Review Comments - Henrik Levkowetz
      http://psg.com/~mrw/PROTO-Team/ad-review-draft.txt
    - Shepherding IESG Ballot Comments - David Meyer
      http://psg.com/~mrw/PROTO-Team/discuss-draft.txt


21:25 Discussing the overall problem - Harald Alvestrand (30 min)
Does this distribution of tasks (small changes, individual proposals, PROTO 
team, EDU team, ICAR, NEWTRK) make sense?
What is NOT within the list of things being worked on? How does it need to 
be done?

21:55 Wrap up and conclude - Harald Alvestrand (5 min)
- What activities do we obviously need to do, but aren't?
- What activities are we doing that we need to change?
- What changes are in the "we know what to do, do it" category?
- What next?

22:00 Adjourn


_______________________________________________
Solutions mailing list
Solutions@alvestrand.no
http://eikenes.alvestrand.no/mailman/listinfo/solutions

 



From owner-ietf@ietf.org  Fri Feb 27 01:44:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02662
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 01:44:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Awbbj-0002NH-AF
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 01:36:23 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwbaT-0002G9-LT
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 01:35:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02398
	for <ietf@ietf.org>; Fri, 27 Feb 2004 01:35:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwbaR-0000JK-00
	for ietf@ietf.org; Fri, 27 Feb 2004 01:35:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwbZT-0000F7-00
	for ietf@ietf.org; Fri, 27 Feb 2004 01:34:04 -0500
Received: from mail5.atl.registeredsite.com ([64.224.219.79] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwbYt-0000B9-00
	for ietf@ietf.org; Fri, 27 Feb 2004 01:33:27 -0500
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail5.atl.registeredsite.com (8.12.8/8.12.8) with ESMTP id i1R7XiGj030260
	for <ietf@ietf.org>; Fri, 27 Feb 2004 02:33:44 -0500
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ; Fri, 27 Feb 2004 00:33:26 -0600
Message-ID: <403EE4AB.B799FD45@nma.com>
Date: Thu, 26 Feb 2004 22:33:15 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: digital signature request
References: <Pine.LNX.4.44.0402261348570.6338-100000@lilith.rgb.private.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"Robert G. Brown" wrote:
> 
> Work and time burdens are not uniform or static because of Moore's law
> [snip]

What? Gimme a break. I can impose the exact time burden I want at each s
step in a protocol -- I simply do not reply before the time I want elapses. 
This is SOP in any attack protection or congestion-control toolbox. There 
is NO Moore's law here.  

Work burden, when well-engineered with a time burden, can also certainly be 
added specifically  when desired and without penalizing everyone. For example, 
work burden can be demanded when a message has a non-verifiable envelope ---
it will NOT burden senders that have verifiable envelopes.

Regards,
Ed Gerck



From owner-ietf@ietf.org  Fri Feb 27 02:37:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18658
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 02:37:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwcTu-00052e-O2
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 02:32:22 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwcTk-00050F-Ki
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 02:32:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18441
	for <ietf@ietf.org>; Fri, 27 Feb 2004 02:32:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwcTg-0006c0-00
	for ietf@ietf.org; Fri, 27 Feb 2004 02:32:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwcSn-0006XL-00
	for ietf@ietf.org; Fri, 27 Feb 2004 02:31:14 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwcS8-0006Ha-00
	for ietf@ietf.org; Fri, 27 Feb 2004 02:30:33 -0500
Received: from BBFUJIP.brandenburg.com (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i1R7cTd09323;
	Thu, 26 Feb 2004 23:38:30 -0800
Date: Fri, 27 Feb 2004 15:29:46 +0800
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <74237662.20040227152946@brandenburg.com>
To: John Leslie <john@jlc.net>
CC: Iljitsch van Beijnum <iljitsch@muada.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: Principles of Spam-abatement
In-Reply-To: <20040226205953.GA68458@verdi>
References: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net>
 <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com> <20040226205953.GA68458@verdi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=PRIORITY_NO_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

>> If we can communicate the fact that a message is discarded because it
>> was categorized as spam back to the sender without adverse side

unfortunately, that act of communication _is_ the adverse side
effect.  it tells the spammer that yours is an active, responsive
email account.


d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Fri Feb 27 03:52:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20851
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 03:52:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Awdax-00089b-QR
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 03:43:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwdaO-00087K-IE
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 03:43:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20657
	for <ietf@ietf.org>; Fri, 27 Feb 2004 03:43:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwdaM-0005kF-00
	for ietf@ietf.org; Fri, 27 Feb 2004 03:43:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwdZR-0005eI-00
	for ietf@ietf.org; Fri, 27 Feb 2004 03:42:12 -0500
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.sea)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwdYZ-0005Un-00
	for ietf@ietf.org; Fri, 27 Feb 2004 03:41:15 -0500
Received: from ssprunk (ip145.post-vineyard.dfw.ygnition.net [66.135.181.145])
	by ns2.sea (8.12.11/8.12.5) with SMTP id i1R8eenh006266
	for <ietf@ietf.org>; Fri, 27 Feb 2004 00:40:40 -0800
Message-ID: <035101c3fd0d$5f63bd00$6401a8c0@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Internet Engineering Task Force" <ietf@ietf.org>
References: <403C0D87.31678.463FAB5@localhost>
Subject: Re: digital signature request
Date: Fri, 27 Feb 2004 02:20:46 -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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

I think this thread has deviated enough from its original intent that the
best place to continue it is on the ASRG list -- there's no point in
bothering the entire IETF with yet another anti-spam discussion.

S

Stephen Sprunk        "Stupid people surround themselves with smart
CCIE #3723           people.  Smart people surround themselves with
K5SSS         smart people who disagree with them."  --Aaron Sorkin
----- Original Message ----- 
From: <gnulinux@pacinfo.com>
To: <ietf@ietf.org>
Sent: Wednesday, 25 February, 2004 04:50
Subject: digital signature request


> this is a request for this list to be digitally
> signed by the list processor.
>
> to all list members.  if after reading this post
> you would like the list processor to digitally
> sign all posts please say so (and tell the list
> owner) so that the level of interest can be
> gauged.  thanks.
>
> i'm making this request because i need a way to
> positively id the messages from this list.  i'm
> spending way too much of my time culling spam from
> my real email even though i'm employing the latest
> spam filtering tools.  please give me the one
> simple tool i know of that will allow me to
> positively differentiate the mail from this list
> from all others - a digital signature.
>
> signing all list messages won't be detrimental to
> list recipients not interested.  it will however
> allow folks wishing to implement anti-spam
> measures around digital signatures to do so.
> mailing lists often require that recipients
> confirm their email address as an anti-spam
> measure for the list.  please help list recipients
> implement their own anti-spam measures by allowing
> the list messages to be positively identified.
>
> to be clear, this is a limited scope spam
> solution, but it works.  and it will continue to
> work provided the underlying cryptography is sound
> (unlike many other anti-spam technologies that are
> simply clever hacks in an escalating spam/anti-
> spam arms race).
>
> some folks say that there will be no spam solution
> as long as email is free.  i say there will be no
> spam solution as long as you expect anyone to be
> able to send email to you without first proving
> they are not a spammer.
>
> part of finding a solution is to revision what
> email is.  i argue that email can no longer be a
> method of unfettered *initial* contact.  once that
> is accepted then this solution doesn't seem
> painful.  i suspect that there won't be a solution
> until email is seen from this perspective.  as
> noted above, mailing lists are essentially
> adopting this perspective (to better manage spam
> on the list side), it would be helpful if they
> took an additional small step that would enable
> list recipients to better manage spam on their end
> too.
>
> there's no need for a larger web of trust other
> than one that is personally maintained when using
> digital signatures to defend against the onslaught
> of spam.  your personal web of trust (a.k.a. your
> keyring) is your unspoofable anti-spam whitelist.
> this is where the revisioning of email occurs.
> instead of email being the way you initially make
> contact with an entity, with digital signatures it
> can serve as a reliable communications channel
> *once* contact has been established.
>
> my intention is to implement a procmail recipe at
> the mail server level.  the procmail recipe will
> be used to check incoming mail for whitelisted
> digital signatures that have been uploaded from
> each individual user.
>
> mailing lists could use the same recipe, no
> messages would be handed over to the listserv
> software unless it was signed by a whitelisted
> signature.  again, this won't stop machines from
> being compromised but as soon as a machine is
> compromised that entity will be *immediately*
> notified by their peers.  in the case of a mailing
> list *many* people will suddenly know who's
> compromised and the list can even have a mechanism
> that allows a whitelisted key to be removed once
> it becomes compromised.  this would also serve the
> dual function of indirectly alerting the owner of
> the compromised host since they will investigate
> why they are no longer receiving list traffic.
>
> regarding whether to utilize inline or mime GPG, i
> say use either.  the preferred solution will self-
> select over time.  it is possible to create a
> procmail recipe that can handle both methods.
>
> Two key benefits of this anti-spam technology:
>
> 1.  it works and will likely continue to work
> beyond the foreseeable future
>
> 2.  it can be implemented without the consensus,
> from the bottom up
>
> below are my responses to posts in a few mailing
> list threads regarding digital signatures and
> spam.  please read my responses as they will
> likely answer many of the questions that may
> result from reading what i wrote above.  apologies
> to the folks whose comments i'm replying to for
> not referencing their names (i didn't have the
> time).
>
> looking forward to feedback.
>
> ciao,
>
> david
> --
> spam is something we can eliminate by
> changing our personal behaviors and expectations
> and cooperating.  and it can happen gradually.
>
>
>
> thread:  ietf - proposal for built-in spam burden
> & email privacy protection -----
>
> >>2. Except for senders in a whitelist (e.g.,
> >>list mail), I bounce to  the sender  any email
> >>that is NOT encrypted with my public-key,
> >>providing my   public-key and instructions for the
> >>sender to resubmit the message  properly
> >>encrypted.
> >
> >Anything at all that generates a bounce message
> >on a mass-produced mailing acts as a "damage
> >amplifier" from the basic internet backbone's
> >point of view -- at least doubling the associated
> >automated traffic and wasted/misused resources.
> >These days such a bounce is especially fruitless,
> >as all viruses and quite a lot of SPAM have forged
> >headers that the stupid bounce agents cannot or do
> >not parse.
> >
> >This is pet peeve of mine as it is -- I got (and
> >continue to get) more bounce messages from mydoom
> >reporting that mail "from me" is contaminated than
> >I do copies of the virus itself.  No virus for two
> >years now hasn't forged mail headers -- the From
> >field is totally irrelevant in all current viruses-
> >- yet all the AV programs in the world think they
> >are doing you a favor. NOT.
> >
> >Now imagine that sort of stupidity scaled out so
> >that every MTA in the world is checking esigs and
> >bouncing improperly signed mail.  Imagine the
> >loops created when a legacy mailer or improperly
> >configured mailer bounces the bounce messages back
> >to the bouncer, to be bounced again. Nightmarish.
>
> solution - don't auto-respond, give out a keyword
> with your email address, this will allow initial
> contact to be more easily plucked from the sea of
> spam - in the long run as more people digitally
> sign email spam will become even less profitable
> because there will be even fewer responses - we'll
> never know what's possible if we don't try
>
> >encrypting for each of the list recipients is too
> >much of a burden for the list
>
> solution - don't encrypt, only digitally sign -
> not a burden
>
> >Don't get me wrong: encouraging people to use pgp
> >is a good idea, but making it a requirement before
> >accepting it is a policy decision that the end
> >user should be making, not the list.
>
> solution - by only digitally signing it is
> completely up to the end user to decide whether or
> not to add this tool to their anti-spam toolbox
>
> >Your proposal is in line with some existing ones,
> >at least one of which response to the seriously
> >problematic key management issue.
>
> solution - non-local, centralized key management
> is a huge problem, but key management isn't a
> problem if the only important keys are your
> personal ones and if you don't expect to be able
> to instantaneously have access to anyone's public
> key via a keyserver - keyservers aren't necessary
> for folks who exchange email with primarily a
> small group of people
>
> >I'm not saying to reject non esig mails, but to
> >held them for approval by moderators... If you
> >want your post to go through quickly, sign it...
> >It would be a worthwhile incentive.
>
> sounds like a great idea, but this is in addition
> to and isn't required for what i'm suggesting
>
> >Also note, there is an addition burden placed on
> >end users who rely on receiving encrypted email in
> >your proposal.  Under your scheme, a user has to
> >go through the trouble of decrypting the message
> >just to see if it is spam or not.  This eliminates
> >almost all forms of automated spam mitigation
> >except those related to the low-level SMTP, DNS or
> >other new authentication/authorization techniques.
>
> reminds me that signing and not encrypting still
> allows bayesian filters to continue to be useful
>
> >Unfortunately, requiring that they have a
> >published public-key *is* a burden to the average
> >user.  J. Random Luser just wants to sit down at
> >his PC, boot up Winders, bring out Lookout, and
> >forward a garish HTMLified email full of stale
> >jokes to his buddies, complete with pictures, and
> >he wants it to go through, without a hitch, right
> >now.  He thinks public keys are the ones hanging
> >on the gas station wall, for the bathroom.  He
> >thinks crypto is someone from Superman's home
> >planet.  He thinks the IETF is them guys whut
> >raided David Koresh.  He has no clue what the ASRG
> >is, but he thinks it sounds dirty.
>
> again, no need for keyservers for folks that are
> exchanging email within a small group of people.
> also, let's stop trying to allow email to continue
> to be what it has evolved into, let those folks
> that want email to stay the way it is keep it that
> way, let's create a spam-free email environment
> that works and satisfies *us*, i suspect that if
> this is witnessed folks will eventually start
> thinking of email differently as their personal
> spam pain tolerances are exceeded.
>
> >Make it worth their while, by coming up with
> >infrastructure such that they won't get any spam
> >if they have a public key, and MAYBE they'll
> >bother doing it, IF the ISP will hold their hands
> >every step of the way (and not charge them too
> >much, including for issuing new keypairs when they
> >let the private ones slip out too much).  Of
> >course, this means that all their equally
> >technically-enlightened friends have to know how
> >to USE his public key....
>
> solution - accept that it will be a gradual
> process, let's just start with mailing lists
> signing all messages that get sent to list
> recipients - that's easy
>
> >This sounds very much like the use of extra
> >headerz, or a password on the subject line, but on
> >steroids.  In the end, possibly useful, IF you can
> >get everybody aboard, but they won't go until
> >everybody ELSE is already on board, and meanwhile
> >it's a pain in the proverbial posterior to
> >everyone who wants to communicate with the people
> >using it.
>
> for me it is *less* pain than what i'm
> experiencing dealing with my current spam load,
> and digital signatures can be ignored if you don't
> want to verify them - also, if someone tells you
> that they are receiving so much spam that you will
> have to sign all email you send to them, are you
> going to tell them they are causing you too much
> pain?  heck, just pick the phone up and call them
> then.
>
> >Second, even if the above weren't a problem, one
> >still has the problem that a virus infected user
> >will still be sending messages, just like everyone
> >else.
>
> this will still be a problem but with a digital
> signature solution in place infected computers
> will be identifiable and probably immediately
> disinfected, folks will become hyper-aware of
> allowing their machines to become compromised if
> suddenly they are unable to exchange email with
> their small and *important* group of people
> because their public key became blacklisted by
> these same folks - the very nature of digital
> signatures positively identifies infected
> computers
>
> >There is no scheme in which the rules can't be
> >broken by someone intent on breaking them.  The
> >only path is to detect them, and prosecute them.
> >In the case of spam, detection is easy, but not
> >automatic.  Prosecution is now possible.  Its
> >still a whack-a-mole game. It won't end unless you
> >can get past the virus infection to the virus
> >operator, and hopefully, there aren't really too
> >many virus operators.  Of course, we aren't
> >stopping spam either in a very real sense, but
> >rather abusers who are annoying and mailbombing
> >people.  But by my count of my inbox, if you stop
> >those people, I can certainly handle the rest
> >which amounts to maybe 1% of my current junk mail.
>
> there's no known way to crack GPG, widespread
> adoption of digital signatures against spam will
> either help bring spam to and end or tell us what
> NSA might already know  ;)  - let's put those
> spammers to work!  also, prosecutions by a central
> authority won't be necessary, peers will do the
> prosecuting by rejecting email from compromised
> systems, the owner of the infected system will be
> de facto "punished" because communications with
> their peers will end until they clean their system
> (or stop spamming).
>
> >>The "for pay" idea is just another scam from
> >>the people who would love to get a percentage of
> >>the pay. While I'm sure Microsoft and others would
> >>just love to get a cut of this (I know I would),
> >>it doesn't do anything to stop spam, and if
> >>implemented, would simply (and wrongly) charge
> >>users whose computers were virus infected.
> >
> >Wrongly?  I'm not so sure.  Something ought to be
> >done to stop the  Typhoid Marys of the Internet.
> >Putting them on notice that they WILL be held
> >responsible for spreading the infection, or its
> >effects, just MIGHT result in them FINALLY taking
> >some responsibility for their "computer hygiene".
> >Sure, there will have to be several well
> >publicized example cases before most folk will sit
> >up and take notice, but in the long run, it might
> >be effective.
>
> i agree, trying to impose a burden
> (computationally or monetarily) on spammers will
> not work IMHO.  i will leave it to others to
> explain this in more detail.  and to repeat,
> prosecutions by a central authority won't be
> necessary, peers will do the prosecuting by
> rejecting email from compromised systems, the
> owner of the infected system will be de facto
> "punished" because communications with their peers
> will end until they clean their system (or stop
> spamming).
>
> >So even discussing adding a silly thing like
> >mandatory esigs and encryption as an antispam
> >measure is a waste of time, except possibly on a
> >local basis.  If I set up a small mailing list (or
> >generalized group of individuals) and all of its
> >members agree to do this, there is little
> >"evolutionary pressure" for spammers to detect and
> >foil our scheme and we will be "immune" (at the
> >cost of a fair amount of extra work).  If
> >everybody does it and the automated tools for
> >doing it without so much work are widely
> >disbursed, they will develop countermeasures in no
> >time at all and we'll lose our immunity.
>
> please explain how spammers will evolve past the
> public key encryption technology used in digital
> signatures?  as noted earlier machine compromises
> will still occur but they will be able to be dealt
> with because peers of the compromised machine will
> immediately identify and neutralize the problem by
> ending communication (by blacklisting the
> compromised key).  suddenly the owner of the
> compromised machine hears silence.
>
> >Automated text analysis will never be perfect,
> >because even human text analysis for
> >interest/disinterest (secretaries) aren't perfect.
> >But it can help sort things.  I hand filter about
> >1500 messages a day.  I get about 3500 over the
> >weekend. Monday's filtering doesn't take me any
> >longer than tuesdays filtering.
>
> unfortunately the approach you describe could
> likely be your undoing in the long run as spammers
> ratchet up the volume to the point were it *will*
> take you a long time using this approach.  this is
> why even with 99.9% accurate bayesian filtering,
> all spammers need to do is ratchet up the volume
> to get more spam through the 0.1% error rate of
> the bayesian filter.
>
> >>>Then using the IETF list as an example, you
> >>>would need the entire list of recipients and their
> >>>public keys, and you would need to send a message
> >>>either directly to each of them, one by one, or
> >>>send a single message with a session key for each
> >>>recipient (thousands).  This isn't going to work.
> >>
> >>Let's not mix apples with speedboats. These are
> >>some options with the proposal:
> >>
> >>#1: no encryption is used either way, the list
> >>address is in a whitelist for each recipient.
> >>
> >>#2: each recipient can only send encrypted msgs
> >>(possibly, also signed) to the list, with the
> >>list's key, for distribution. The listserver
> >>verifies and resends the messages in plain text,
> >>where #1 applies for each recipient.
> >>
> >>#3: the list receives messages as in #2 but the
> >>listserver sends the msgs as encrypted mail to
> >>each recipient, with each recipient's key.
> >
> >#4 (my preferred) the member send a message to
> >the list with his digital signature. The list
> >checks the digital signature (from keyserver or
> >from a member database) and post the message if
> >signature is valid. If the signature is not valid,
> >the message is held for approval. But yes this
> >scheme does not offer much more than restrict
> >posting to list members only, which the IETF had
> >to do last year(?).
>
> if the list server signs each message that then
> allows recipients to positively identify mail from
> the list.  this is *HUGE*.  if i have an email
> account that only receives mail from mailing lists
> that sign all messages then i can dump all
> incoming non-whitelisted digitally signed email at
> the server and *know* that all my email is legit.
>
>
>
> thread:  ietf - how not to filter spam -----
>
> >>first, there is an increasingly heated debate
> >>between folks who want to sign the message (TEOS,
> >>DomainKeys), versus others who want to secure the
> >>channel between sender and receiver (RMX, LMAP,
> >>SPF, etc.).
> >
> >What does it matter what the resolution is?
> >Neither solution eliminates the spam channel, and
> >solves the problem, as information theory shows.
> >Its just a silly debate over two schemes to thread
> >a needle that can't be threaded.
>
> think of spam as a river passing through multiple
> channels, let's find a channel we can change.
> folks talk about spammers taking advantage of
> email protocols.  another angle is to say that
> spammers take advantage of people's behavior.
> it's much easier to change my personal behavior
> and expectations with regard to email than it is
> for me to change an established internet protocol.
> so stop thinking about eliminating the ability to
> send spam and focus on *absolutely* identifying
> real email.  spam will dry up as people are able
> to absolutely identify real email.
>
> >>That sounds like the old "authentication solves
> >>spam" hope.  It was wrong before SMTP-AUTH and it
> >>is still wrong.
> >
> >Guess what, it is impossible to "solve" spam the
> >same way it is  impossible to "solve" burglary. At
> >least with authentication you get to have
> >whitelists that work. If you get a message with my
> >email address in the "from" line it could be from
> >anyone. If it is signed with my PGP key you know
> >it came from me personally or someone went through
> >a LOT of trouble to get access to my private key
> >and the key phrase.
> >
> >The usefulness of authentication could be further
> >extended by building a web of trust where people
> >vouch for the fact that others aren't spammers.
> >Obviously spammers will slip through from time to
> >time, but anyone who spams or keeps vouching for
> >spammers will be removed from the web of trust.
> >But even if this part doesn't work authentication
> >is still useful.
>
> exactly
>
>
>
> thread:  tidbits - digital signatures in tidbits --
> ---
>
> >As I said earlier, I don't see the point of doing
> >it for this list, but the mechanism itself isn't
> >so easily spoofed.  Think of it as an address
> >based whitelist with addresses that can't be
> >forged.  A spammer wouldn't be able to get his own
> >public key on the whitelist, and can't pretend to
> >be someone else because he doesn't have the
> >corresponding private key.  I personally wouldn't
> >use such a system, since the Bayesian spam filter
> >I use (bogofilter) works well enough, but people
> >that are more annoyed with spam than I get might
> >find such a system attractive.
>
> exactly, my bayesian filter (POPFile) works great,
> but i get so much spam that the 1% of my email
> that doesn't get classified correctly is causing
> me too much pain.
>
> >>>Then you have to start allowing attachments on
> >>>the list...not a great idea.
> >>
> >>Not necessarily. This should work as text only
> >>with PGP 8.
> >>
> >>Attachment converted: HHBV HD:PGP.sig (pgDS/----
> >>) (002B8C8F)
> >
> >Obviously, it does not work except by allowing
> >attachments... and  it's hard to believe that
> >TidBITS Talk would ever come to that.
>
> no, digital signatures can be inline, the mime
> attachment method is more robust but not required.
> so tidbits can be signed without mime
> attachments.  FWIW, most email clients do support
> the mime method.
>
> >>There are plenty of uses for digital
> >>signatures, but I don't think approving mailing
> >>list postings is likely to be one of them any time
> >>soon.
> >
> >Agreed. Remember the messages that slipped
> >through were approved by Adam because of poor html
> >formatting, except one that forged his email.  If
> >he used digital signatures most of those messages
> >still would've been signed, and just like Habeas
> >headers, if you're spam filter auto-whitelists
> >signed messages they would come through.
>
> exactly, if the list is signed spam can still get
> through.  what the signature does is allow the
> mailing list traffic to be positively identified
> amidst the personal flood of spam many folks
> receive.  just like we help list maintainers out
> by taking extra steps to allow posting,
> maintainers could help us out by signing all list
> messages.  dealing with spam requires cooperation.
>
> >>I think people should sign all of their
> >>messages. That will have several effects:  - Peole
> >>will get suspicious if a message isn't signed,
> >>making forging mesages harder.
> >
> >How do you handle email from a kiosk, or a cell
> >phone, or someone else's computer? There are too
> >many instances in the real world where this
> >happens. It's one of the benefits of IMAP..you
> >don't HAVE to be on any particlular computer to
> >get your email.
>
> by locating signature verification at the mail
> server level.  create a procmail recipe that will
> automatically tag all signed email as to whether
> or not the signature exists in the personal
> whitelist that has been uploaded to the server.
>
> >I do think we're getting off topic but -- any
> >modern approach to the spam problem must take into
> >account the fact that at any given time the
> >Internet contains millions of insecure computers
> >that can be taken over by viruses and used as
> >zombies to, among other things, send spam.  If
> >digital signatures were actually used in some
> >standardized way, it would be trivial for the
> >virus to grab it and sign its messages.
>
> again, digital signatures as an anti-spam
> technology will be effective for folks who don't
> *need* to be able to be contacted by anyone on the
> internet prior to them verifying they're not a
> spammer.  folks that need to be this accessible
> need to either modify this requirement, continue
> to rely on statistical spam filtering tools, solve
> the key distribution problem, and/or work to
> change established internet protocols.
>
> >This assumes that you already have all the keys
> >of potential  correspondents in your keyring,
> >which makes this just another form of
> >whitelisting, albeit a cryptographically secured
> >one. The shortcomings of whitelisting systems are
> >well described here and elsewhere, but basically
> >you'll have to read all your (signed) spam just to
> >make sure there isn't a message there from someone
> >you haven't whitelisted yet. Remember, too, that
> >public keys really should expire, so you would
> >need a method for keeping your whitelist (keyring)
> >up to date. If you try to automate the whitelist,
> >you open the door to spammers again.
>
> you are assuming the receipt of email from a large
> previous unknown group of entities.  if this is
> you then you won't benefit from digital signatures
> adopted on a small scale.  but if you are one of
> the many folks who only receives email from a
> small group of people then digital signatures
> ensure that you will never miss one of their
> messages.
>
> >I'm a big proponent of cryptographic signatures;
> >they just aren't the Final Ultimate Solution to
> >Spam.
>
> digital signatures don't do anything whatsoever to
> end spam - they allow spam to be sent to > /dev/null
>
> >Whitelists work great for those corresponding to
> >just a few people. But they simply aren't pratical
> >for participation in mail lists.
>
> at the very least a digitally signed list (by the
> list software/moderator) allows list recipients to
> identify list traffic.  i do have my doubts about
> how impractical it would be for the list
> software/moderator to check for digital signatures
> prior to posting messages from list members.
> think gradual implementation, let go of the notion
> of all members signing their posts, although they
> might, and for every list member that does sign
> that's one less post to be analyzed to see if it's
> spam.
>
> >>Whitelists work great for those corresponding
> >>to just a few people. But they simply aren't
> >>pratical for participation in mail lists.
> >
> >Sure they are. You are missing the whole point of
> >how digital signatures would/should be
> >implemented in a discussion list environment.
> >
> >It's not the end user who needs to verify the
> >signature, it's the list processor.
> >
> >I subscribe to a list. As part of that process I
> >provide the public  half of my key. Any message I
> >submit to the list is signed by me using my
> >private key. The list manager software then
> >verifies my signature and passes the verified
> >message on to the list or to the list moderator.
> >This ensure that only messages written by bonefide
> >members of the list get past on to the members of
> >the list.
> >
> >The whole point is not to ensure that messages
> >coming from the list are signed but to ensure that
> >messages submitted to the list are signed.
> >
> >This also obviates the need for the list to
> >support attachments and  makes pgp/mime a BETTER
> >alternative to inline signing. The list  processor
> >receives the messages, verifies the signature and
> >strips the signature. I, as a subscriber to the
> >list, never see the signature.
> >
> >Maybe, the list processor itself signs the
> >messages it sends out. In which case I only need
> >to have the one key (the public key for the list)
> >in my keychain.
>
> well said.  i differ only in that i would start by
> having the list processor sign the list (what i
> perceive to be a simpler yet positive step) rather
> than trying to get list members to sign in order
> to post.
>
> >If we stop all counterspam measures by pointing
> >out that they aren't the Final Ultimate Solution
> >To Spam (TM), the situation will never improve.
>
> here!  here!
>
>




From owner-ietf@ietf.org  Fri Feb 27 09:31:05 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03831
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 09:31:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Awirh-0004Yo-Kv
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 09:21:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Awiqz-0004WV-BM
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 09:20:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03499
	for <ietf@ietf.org>; Fri, 27 Feb 2004 09:20:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awiqy-0002w3-00
	for ietf@ietf.org; Fri, 27 Feb 2004 09:20:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwiqU-0002p7-00
	for ietf@ietf.org; Fri, 27 Feb 2004 09:20:07 -0500
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwipT-0002bT-00
	for ietf@ietf.org; Fri, 27 Feb 2004 09:19:03 -0500
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id 21719E0716; Fri, 27 Feb 2004 09:19:03 -0500 (EST)
Date: Fri, 27 Feb 2004 09:19:03 -0500
From: John Leslie <john@jlc.net>
To: Dave Crocker <dhc2@dcrocker.net>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Principles of Spam-abatement
Message-ID: <20040227141903.GA69134@verdi>
References: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net> <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com> <20040226205953.GA68458@verdi> <74237662.20040227152946@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <74237662.20040227152946@brandenburg.com>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Dave Crocker <dhc2@dcrocker.net> wrote:
> 
>>> If we can communicate the fact that a message is discarded because it
>>> was categorized as spam back to the sender without adverse side
> [ effects, then occasional false positives aren't much of a problem.]
> 
> unfortunately, that act of communication _is_ the adverse side
> effect.  it tells the spammer that yours is an active, responsive
> email account.

   I must disagree.

   Iljitsch stated it precisely and well: "the fact that a message is
discarded as spam" need not give any information about whether the
recipient is an active email account -- least of all "responsive".

--
John Leslie <john@jlc.net>



From owner-ietf@ietf.org  Fri Feb 27 09:36:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04125
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 09:36:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Awj3J-0005B3-IK
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 09:33:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Awj0Z-0004uA-SX
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 09:30:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03820
	for <ietf@ietf.org>; Fri, 27 Feb 2004 09:30:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awj0Y-0003pG-00
	for ietf@ietf.org; Fri, 27 Feb 2004 09:30:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwizZ-0003jv-00
	for ietf@ietf.org; Fri, 27 Feb 2004 09:29:30 -0500
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwizF-0003eH-00
	for ietf@ietf.org; Fri, 27 Feb 2004 09:29:09 -0500
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id 2878EE0721; Fri, 27 Feb 2004 09:29:09 -0500 (EST)
Date: Fri, 27 Feb 2004 09:29:09 -0500
From: John Leslie <john@jlc.net>
To: Ted Hardie <hardie@qualcomm.com>
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: Principles of Spam-abatement
Message-ID: <20040227142909.GB69134@verdi>
References: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net> <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com> <20040226205953.GA68458@verdi> <p06020401bc64251fe8d7@[205.214.163.20]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p06020401bc64251fe8d7@[205.214.163.20]>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Ted Hardie <hardie@qualcomm.com> wrote:
> 
> Please note that the BoF scheduled for Korea, MARID, has a
> very specific topic and that discussion of other spam-related
> issues is not appropriate for that session.

   While I am _very_ sympathetic to the need to limit the discussion,
I really don't see how anything useful can be accomplished if the
chair rules "principles of spam-abatement" to be irrelevant.

   Regardless, "principles of spam-abatement" don't need to be
_discussed_ at this BoF in order to "enlighten" it.

   Thus, if Ted meant to indicate such principles shouldn't be discussed
here, I respectfully disagree.

> At 3:59 PM -0500 02/26/2004, John Leslie wrote:
>> I strongly recommend gathering some principles of spam-abatement to
>> enlighten the spam BOF at IETF-59. (I'd be happy to edit such a
>> document, but it might be better to chose someone who will attend
>> IETF-59...
>>
>> Iljitsch van Beijnum <iljitsch@muada.com> wrote:
>>>
>>> If we can communicate the fact that a message is discarded because
>>> it was categorized as spam back to the sender without adverse side
>>> effects, then occasional false positives aren't much of a problem.

--
John Leslie <john@jlc.net>



From owner-ietf@ietf.org  Fri Feb 27 09:42:07 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05176
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 09:42:07 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Awj97-0005oc-IF
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 09:39:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Awj8H-0005jV-26
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 09:38:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04542
	for <ietf@ietf.org>; Fri, 27 Feb 2004 09:38:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awj8G-0005Pz-00
	for ietf@ietf.org; Fri, 27 Feb 2004 09:38:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Awj5e-0004lI-00
	for ietf@ietf.org; Fri, 27 Feb 2004 09:35:47 -0500
Received: from shockwave.systems.pipex.net ([62.241.160.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awj2Z-0003wn-00
	for ietf@ietf.org; Fri, 27 Feb 2004 09:32:35 -0500
Received: from tom3 (1Cust198.tnt4.lnd4.gbr.da.uu.net [62.188.133.198])
	by shockwave.systems.pipex.net (Postfix) with SMTP id 320B11C000EE;
	Fri, 27 Feb 2004 14:32:02 +0000 (GMT)
Message-ID: <014101c3fd3e$4642f9e0$0301a8c0@tom3>
Reply-To: "Tom Petch" <nwnetworks@dial.pipex.com>
From: "Tom Petch" <nwnetworks@dial.pipex.com>
To: "Dave Crocker" <dhc2@dcrocker.net>
Cc: "IETF Discussion" <ietf@ietf.org>
Subject: Re: Principles of Spam-abatement
Date: Fri, 27 Feb 2004 14:29:56 -0000
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 4.72.2106.4
X-MIMEOLE: Produced By Microsoft MimeOLE V4.72.2106.4
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: Dave Crocker <dhc2@dcrocker.net>
To: John Leslie <john@jlc.net>
Cc: Iljitsch van Beijnum <iljitsch@muada.com>; IETF Discussion
<ietf@ietf.org>
Date: 27 February 2004 07:38
Subject: Re: Principles of Spam-abatement

>John,
>
>>> If we can communicate the fact that a message is discarded because it
>>> was categorized as spam back to the sender without adverse side
>
>unfortunately, that act of communication _is_ the adverse side
>effect.  it tells the spammer that yours is an active, responsive
>email account.
>

So send it back from a different e-mail address, with headers which
disguise its real origin.

One reason why spam works is that it is so cheap to send 1M messages that
even if 99.99% fail to reach a destination, the operation is still a
success.  If sending 1M messages got back a 1% response saying 'you
failed' with no clue as to which 1% failed, we might cut down on the spam.

Tom Petch

>--
> Dave Crocker <dcrocker-at-brandenburg-dot-com>
> Brandenburg InternetWorking <www.brandenburg.com>
> Sunnyvale, CA  USA <tel:+1.408.246.8253>






From owner-ietf@ietf.org  Fri Feb 27 10:12:09 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07038
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 10:12:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwjaD-0007hA-HQ
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 10:07:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwjZG-0007eG-DL
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 10:06:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06510
	for <ietf@ietf.org>; Fri, 27 Feb 2004 10:06:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwjZF-0001nh-00
	for ietf@ietf.org; Fri, 27 Feb 2004 10:06:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwjYa-0001j9-00
	for ietf@ietf.org; Fri, 27 Feb 2004 10:05:41 -0500
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwjXo-0001cJ-00
	for ietf@ietf.org; Fri, 27 Feb 2004 10:04:52 -0500
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id E43ABE078B; Fri, 27 Feb 2004 10:04:51 -0500 (EST)
Date: Fri, 27 Feb 2004 10:04:51 -0500
From: John Leslie <john@jlc.net>
To: Tom Petch <nwnetworks@dial.pipex.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Principles of Spam-abatement
Message-ID: <20040227150451.GC69134@verdi>
References: <014101c3fd3e$4642f9e0$0301a8c0@tom3>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <014101c3fd3e$4642f9e0$0301a8c0@tom3>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Tom Petch <nwnetworks@dial.pipex.com> wrote:
> From: Dave Crocker <dhc2@dcrocker.net>
>
>>>> If we can communicate the fact that a message is discarded because it
>>>> was categorized as spam back to the sender without adverse side
>>
>> unfortunately, that act of communication _is_ the adverse side
>> effect.  it tells the spammer that yours is an active, responsive
>> email account.
> 
> So send it back from a different e-mail address, with headers which
> disguise its real origin.

   It is not obvious to me that there is any way to do that.

   Nothing in the (SMTP) envelope info is trustworthy except the
IP address of the SMTP sender. Using _anything_ other than that IP
address (which isn't even required to accept email at all) will
likely generate _more_ "spam".

   Thus I'd like a Principle to the effect of:

" Errors returned after the close of the SMTP transaction are likely
" to go to (and confuse) an innocent party; thus such errors should
" be deprecated for any email identified as spam.

> One reason why spam works is that it is so cheap to send 1M messages
> that even if 99.99% fail to reach a destination, the operation is still
> a success.  If sending 1M messages got back a 1% response saying 'you
> failed' with no clue as to which 1% failed, we might cut down on the
> spam.

   There may be a Principle there, about any "cost" imposed upon
spammers tending to reduce the spam problem...

--
John Leslie <john@jlc.net>



From owner-ietf@ietf.org  Fri Feb 27 10:41:57 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09423
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 10:41:57 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Awjsb-0000FY-B0
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 10:26:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Awjrr-0000Db-As
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 10:25:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08081
	for <ietf@ietf.org>; Fri, 27 Feb 2004 10:25:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awjrp-0003xE-00
	for ietf@ietf.org; Fri, 27 Feb 2004 10:25:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Awjqw-0003rR-00
	for ietf@ietf.org; Fri, 27 Feb 2004 10:24:38 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwjqN-0003jd-00
	for ietf@ietf.org; Fri, 27 Feb 2004 10:24:03 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id A0377D7; Fri, 27 Feb 2004 10:21:24 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
To: "Tom Petch" <nwnetworks@dial.pipex.com>
Subject: Re: Principles of Spam-abatement
Date: Fri, 27 Feb 2004 10:22:13 -0500
User-Agent: KMail/1.5.2
Cc: "IETF Discussion" <ietf@ietf.org>
References: <014101c3fd3e$4642f9e0$0301a8c0@tom3>
In-Reply-To: <014101c3fd3e$4642f9e0$0301a8c0@tom3>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402271022.13604.spamtrap.ietf@dja.mailme.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Fri February 27 2004 09:29, Tom Petch wrote:

 > If sending 1M messages got back a 1% response
 > saying 'you failed' with no clue as to which 1% failed, we might cut
 > down on the spam.

Maybe I just have too much blood in my caffeine stream, but I don't see 
the connection.  J. Random Spammer spews 1M spams, and receives back 
(assuming he used a valid sending address) 10K "this looked like spam" 
DSNs, in addition to the usual load of angry replies, removal requests, 
"no such user", "no such domain", "over quota", etc., plus the 
occasional purchase.  What incentive do the 10K new DSNs give him, to 
mend his evil ways, or even just to scale back?  Indeed, it seems to me 
that if anything, it helps him see what does or does not work against 
spam filters, so he can tune his filter-evasion strategies.

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.




From owner-ietf@ietf.org  Fri Feb 27 11:00:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10091
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 11:00:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwkKf-0001al-EX
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 10:55:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwkJm-0001Yj-5O
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 10:54:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09942
	for <ietf@ietf.org>; Fri, 27 Feb 2004 10:54:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwkJl-00002l-00
	for ietf@ietf.org; Fri, 27 Feb 2004 10:54:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwkIs-0007lT-00
	for ietf@ietf.org; Fri, 27 Feb 2004 10:53:31 -0500
Received: from vsmtp3alice.tin.it ([212.216.176.143])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwkIV-0007gF-00
	for ietf@ietf.org; Fri, 27 Feb 2004 10:53:07 -0500
Received: from cappone (82.49.98.115) by vsmtp3alice.tin.it (7.0.019)
        id 402CD19200085837 for ietf@ietf.org; Fri, 27 Feb 2004 16:52:35 +0100
Message-ID: <000f01c3fd49$a78902c0$2101a8c0@cappone>
From: "Giacomo Pisano" <giacpis@aliceposta.it>
To: "IETF Discussion" <ietf@ietf.org>
Subject: DIAMETER
Date: Fri, 27 Feb 2004 16:52:07 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000C_01C3FD52.08F02F90"
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,HTML_60_70,HTML_MESSAGE 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_000C_01C3FD52.08F02F90
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'd like to receive info about the topic in the subject.=20


Giacomo Pisano
------=_NextPart_000_000C_01C3FD52.08F02F90
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I'd like to receive info about the =
topic in the=20
subject. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Giacomo =
Pisano</FONT></DIV></BODY></HTML>

------=_NextPart_000_000C_01C3FD52.08F02F90--




From owner-ietf@ietf.org  Fri Feb 27 11:17:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11319
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 11:17:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwkZE-0002TI-7o
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 11:10:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwkXL-0002OH-0v
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 11:08:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10512
	for <ietf@ietf.org>; Fri, 27 Feb 2004 11:08:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwkXK-0001UD-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:08:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwkWN-0001P5-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:07:27 -0500
Received: from vsmtp3alice.tin.it ([212.216.176.143])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwkVi-0001Ei-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:06:47 -0500
Received: from cappone (82.49.98.115) by vsmtp3alice.tin.it (7.0.019)
        id 402CD19200085A10 for ietf@ietf.org; Fri, 27 Feb 2004 17:06:16 +0100
Message-ID: <005301c3fd4b$90e9c5c0$2101a8c0@cappone>
From: "Giacomo Pisano" <giacpis@aliceposta.it>
To: "IETF Discussion" <ietf@ietf.org>
Subject: DIAMETER
Date: Fri, 27 Feb 2004 17:05:48 +0100
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I'd like to receive info about the topic in the subject. 


Giacomo Pisano



From owner-ietf@ietf.org  Fri Feb 27 11:19:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11518
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 11:19:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwkeA-0002dI-8O
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 11:15:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwkZG-0002Ta-9q
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 11:10:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10724
	for <ietf@ietf.org>; Fri, 27 Feb 2004 11:10:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwkZF-0001gg-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:10:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwkYK-0001aN-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:09:29 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwkXO-0001UZ-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:08:30 -0500
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i1RG8Pvf012342;
	Fri, 27 Feb 2004 08:08:25 -0800 (PST)
Received: from [205.214.163.24] (vpn-10-50-16-25.qualcomm.com [10.50.16.25])
	by crowley.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i1RG8GtR016173;
	Fri, 27 Feb 2004 08:08:17 -0800 (PST)
Mime-Version: 1.0
X-Sender: hardie@mage.qualcomm.com
Message-Id: <p06020400bc651accda9c@[205.214.163.24]>
In-Reply-To: <20040227142909.GB69134@verdi>
References: 
 <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net>
 <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com>
 <20040226205953.GA68458@verdi> <p06020401bc64251fe8d7@[205.214.163.20]>
 <20040227142909.GB69134@verdi>
Date: Fri, 27 Feb 2004 08:08:15 -0800
To: John Leslie <john@jlc.net>
From: Ted Hardie <hardie@qualcomm.com>
Subject: Re: Principles of Spam-abatement
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 9:29 AM -0500 02/27/2004, John Leslie wrote:
>    While I am _very_ sympathetic to the need to limit the discussion,
>I really don't see how anything useful can be accomplished if the
>chair rules "principles of spam-abatement" to be irrelevant.

Perhaps this would be clearer:  The BoF proposes that the IETF
take on a particular engineering task, with a specific scope and
an intended effect.  It is within the purview of the BoF to discuss
whether that is the right scope, whether the intended effect
is a good idea, and so on.  General discussion of the "principles
of spam-abatement" , however, is out of scope (largely because such discussions
tend to be non-terminating and will swamp the more focused engineering
discussion).  But the context of  the "is this the right scope, and a good
idea" no doubt includes the participants understandings of those principles.
			regards,
				Ted Hardie



From owner-ietf@ietf.org  Fri Feb 27 11:41:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12567
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 11:41:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwkrZ-0003wh-Ex
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 11:29:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Awkql-0003um-Ef
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 11:28:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12083
	for <ietf@ietf.org>; Fri, 27 Feb 2004 11:28:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awkqk-0004EA-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:28:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Awkpm-00048y-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:27:31 -0500
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwkpE-00043j-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:26:56 -0500
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id 29ADAE0A95; Fri, 27 Feb 2004 11:26:52 -0500 (EST)
Date: Fri, 27 Feb 2004 11:26:52 -0500
From: John Leslie <john@jlc.net>
To: Dave Aronson <spamtrap.ietf@dja.mailme.org>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Principles of Spam-abatement
Message-ID: <20040227162652.GD69134@verdi>
References: <014101c3fd3e$4642f9e0$0301a8c0@tom3> <200402271022.13604.spamtrap.ietf@dja.mailme.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200402271022.13604.spamtrap.ietf@dja.mailme.org>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Dave Aronson <spamtrap.ietf@dja.mailme.org> wrote:
> 
> On Fri February 27 2004 09:29, Tom Petch wrote:
> 
>> If sending 1M messages got back a 1% response saying 'you failed'
>> with no clue as to which 1% failed, we might cut down on the spam.
> 
> Maybe I just have too much blood in my caffeine stream,

   ;^)

> but I don't see the connection.  J. Random Spammer spews 1M spams,
> and receives back (assuming he used a valid sending address)

   Yes, let us assume the actual sender gets the "spam-refused" error.

> 10K "this looked like spam" DSNs, in addition to the usual load of
> angry replies, removal requests, "no such user", "no such domain",
> "over quota", etc., plus the occasional purchase.  What incentive do
> the 10K new DSNs give him, to mend his evil ways, or even just to
> scale back? 

   No incentive to "mend his evil ways"; but a cost which may reduce
the total amount of spam. (Recall that many believe a one-cent-per-
spam cost would essentially eliminate the problem.)

> Indeed, it seems to me that if anything, it helps him see what does or
> does not work against spam filters, so he can tune his filter-evasion
> strategies.

   I claim that benefit is minimal -- spammers have other ways of
gathering the data to tune their filter-evasion.

   The benefit to the false-positive-sender, OTOH, is major. S/he knows
that the email never got through, and can use one of the many available
out-of-band methods to communicate the message. Iljitsch's point was
that the false-positive problem is much less serious if senders of
non-spam learn their email was discarded as spam.

   (I'd rather not speculate on whether the minimal benefit to the
spammer is greater or less than the admittedly-minimal cost.)

--
John Leslie <john@jlc.net>



From owner-ietf@ietf.org  Fri Feb 27 11:47:59 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12978
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 11:47:59 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Awl58-0004jd-6C
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 11:43:22 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Awl4G-0004Yc-Na
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 11:42:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12588
	for <ietf@ietf.org>; Fri, 27 Feb 2004 11:42:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awl4F-0005NH-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:42:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Awl3O-0005Hy-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:41:34 -0500
Received: from adsl-66-137-237-100.dsl.rcsntx.swbell.net ([66.137.237.100] helo=gw.frascone.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awl2q-0005CK-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:41:01 -0500
Received: by gw.frascone.com (Postfix, from userid 500)
	id 739A458005B; Fri, 27 Feb 2004 10:40:57 -0600 (CST)
Date: Fri, 27 Feb 2004 10:40:57 -0600
From: David Frascone <dave@frascone.com>
To: Giacomo Pisano <giacpis@aliceposta.it>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: DIAMETER
Message-ID: <20040227164057.GY20101@wolverine.frascone.com>
References: <000f01c3fd49$a78902c0$2101a8c0@cappone>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000f01c3fd49$a78902c0$2101a8c0@cappone>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

http://www.ietf.org/html.charters/aaa-charter.html
http://www.diameter.org

-Dave


On Friday, 27 Feb 2004, Giacomo Pisano wrote:
> I'd like to receive info about the topic in the subject. 
> 
> 
> Giacomo Pisano
-- 
David Frascone

  Wait! Clinton's "How to Serve Taxpayers" -- it's a COOKBOOK!



From owner-ietf@ietf.org  Fri Feb 27 11:56:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13725
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 11:56:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwlCv-0005QX-RD
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 11:51:25 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Awl7I-0004qz-FH
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 11:45:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12846
	for <ietf@ietf.org>; Fri, 27 Feb 2004 11:45:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awl7H-0005ol-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:45:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Awl6d-0005iB-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:44:55 -0500
Received: from vsmtp3alice.tin.it ([212.216.176.143])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awl5p-0005Vk-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:44:05 -0500
Received: from cappone (82.49.98.115) by vsmtp3alice.tin.it (7.0.019)
        id 402CD19200085EB7; Fri, 27 Feb 2004 17:43:30 +0100
Message-ID: <007201c3fd50$c43e63e0$2101a8c0@cappone>
From: "Giacomo Pisano" <giacpis@aliceposta.it>
To: "David Frascone" <dave@frascone.com>
Cc: "IETF Discussion" <ietf@ietf.org>
References: <000f01c3fd49$a78902c0$2101a8c0@cappone> <20040227164057.GY20101@wolverine.frascone.com>
Subject: Re: DIAMETER
Date: Fri, 27 Feb 2004 17:43:02 +0100
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thank You 

----- Original Message ----- 
From: "David Frascone" <dave@frascone.com>
To: "Giacomo Pisano" <giacpis@aliceposta.it>
Cc: "IETF Discussion" <ietf@ietf.org>
Sent: Friday, February 27, 2004 5:40 PM
Subject: Re: DIAMETER


> http://www.ietf.org/html.charters/aaa-charter.html
> http://www.diameter.org
> 
> -Dave
> 
> 
> On Friday, 27 Feb 2004, Giacomo Pisano wrote:
> > I'd like to receive info about the topic in the subject. 
> > 
> > 
> > Giacomo Pisano
> -- 
> David Frascone
> 
>   Wait! Clinton's "How to Serve Taxpayers" -- it's a COOKBOOK!



From owner-ietf@ietf.org  Fri Feb 27 11:56:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13743
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 11:56:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwlCw-0005RL-A5
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 11:51:26 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwlAy-0005Ch-NN
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 11:49:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13134
	for <ietf@ietf.org>; Fri, 27 Feb 2004 11:49:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwlAx-0006Wv-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:49:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Awl9x-0006GD-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:48:21 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awl8m-0005vc-00
	for ietf@ietf.org; Fri, 27 Feb 2004 11:47:08 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id C593854; Fri, 27 Feb 2004 11:44:30 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
To: John Leslie <john@jlc.net>
Subject: Re: Principles of Spam-abatement
Date: Fri, 27 Feb 2004 11:45:18 -0500
User-Agent: KMail/1.5.2
Cc: IETF Discussion <ietf@ietf.org>
References: <014101c3fd3e$4642f9e0$0301a8c0@tom3> <200402271022.13604.spamtrap.ietf@dja.mailme.org> <20040227162652.GD69134@verdi>
In-Reply-To: <20040227162652.GD69134@verdi>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402271145.18145.spamtrap.ietf@dja.mailme.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Fri February 27 2004 11:26, John Leslie wrote:
 > Dave Aronson <spamtrap.ietf@dja.mailme.org> wrote:
 > > On Fri February 27 2004 09:29, Tom Petch wrote:
 > >> If sending 1M messages got back a 1% response saying 'you failed'
 > >> with no clue as to which 1% failed, we might cut down on the spam.
 [...]
 > > What incentive do the 10K new DSNs give him,
 > > to mend his evil ways, or even just to scale back?
 >
 >    No incentive to "mend his evil ways"; but a cost which may reduce
 > the total amount of spam. (Recall that many believe a one-cent-per-
 > spam cost would essentially eliminate the problem.)

Again, I don't see how this imposes a non-negligible new cost on him.  
He's probably already receiving tens of thousands of now-typical DSNs, 
not to mention out-of-office notes, angry replies, etc.  The "this 
looks like spam" DSNs therefore would probably not incur significant 
additional normal email processing costs (bandwidth, disk, CPU, etc.).  
He has no need to do anything with them, so they don't incur any, let 
alone significant, additional special processing costs.  Indeed, if 
they're readily identifiable as such, they can easily just be filtered 
out, so they don't even take his "human bandwidth" (attention).  (Gee, 
sounds just like fighting spam!)  Where's the beef?

 > > Indeed, it seems to me that if anything, it helps him see what
 > > does or does not work against spam filters, so he can tune his
 > > filter-evasion strategies.
 >
 >    I claim that benefit is minimal -- spammers have other ways of
 > gathering the data to tune their filter-evasion.

Fair enough.

 >    The benefit to the false-positive-sender, OTOH, is major.

Oh, agreed, absolutely.  I understand how this mechanism would allow 
people to tighten their spam filters, which could cut down on the spam 
that person receives.  I'm just arguing over how the spammer receiving 
X number of "bugger off, spambreath!" DSNs per Y spams sent (whether 
using the original 1% or what), is going to "cut down on the 
spam" (which I am interpreting as "the spam that spammer sends" or 
possibly spam in general).

 > S/he knows that the email never got through, and can use one of
 > the many available out-of-band methods to communicate the message.

...assuming that an OOB method has been established already, or is given 
in the DSN.  (E.g., "this looked spam; if it really was legit and you 
want to contact me, call me at 1-900-SPAMSUX".)

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
(Opinions above NOT those of securesw.com unless so stated!)
WE'RE HIRING developers, auditors, and VP of Prof. Services.




From owner-ietf@ietf.org  Fri Feb 27 15:02:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20307
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 15:02:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Awo12-00046i-L0
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 14:51:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Awo0R-00044h-4n
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 14:50:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19926
	for <ietf@ietf.org>; Fri, 27 Feb 2004 14:50:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awo0P-0004Tg-00
	for ietf@ietf.org; Fri, 27 Feb 2004 14:50:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwnzQ-0004ME-00
	for ietf@ietf.org; Fri, 27 Feb 2004 14:49:41 -0500
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwnyX-0004Fq-00
	for ietf@ietf.org; Fri, 27 Feb 2004 14:48:45 -0500
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id 6F967E07F4; Fri, 27 Feb 2004 14:48:41 -0500 (EST)
Date: Fri, 27 Feb 2004 14:48:41 -0500
From: John Leslie <john@jlc.net>
To: Ted Hardie <hardie@qualcomm.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: MARID-BoF
Message-ID: <20040227194841.GG69134@verdi>
References: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net> <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com> <20040226205953.GA68458@verdi> <p06020401bc64251fe8d7@[205.214.163.20]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p06020401bc64251fe8d7@[205.214.163.20]>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Ted Hardie <hardie@qualcomm.com> wrote:
> 
> http://www.ietf.org/ietf/04mar/marid.txt

   In particular:

] Thursday, March 4 at 0900-1130
] ...
] Current Proposals (1 hour together)
]    MTAMARK - draft-stumpf-dns-mtamark-01.txt

   MTAMARK (17 pages) proposes DNS records in in-addr.arpa to indicate
that a particular IP address (or range) is or is not intended to be a
Mail-Transfer-Agent. The details of what record formats to use, IMHO,
deserve to be discussed by an IETF Working Group.

   This proposal depends on the authenticity of the in-addr.arpa
delegations; thus poorly-maintained regions of in-addr.arpa will
necessarily authorize too much or too little. Further discussion of
how to determine which regions are well-maintained will be needed,
although clearly that can be a local decision.

   I would suggest the possibility of specifying a similar mechanism
not under in-addr.arpa -- but instead under the domain records of
any domain one might wish to trust -- showing whether that region of
in-addr.arpa is considered well-maintained and trustworthy.

]    DRIP - draft-brand-drip-02.txt

   DRIP (21 pages) proposes adding A(ddress) records for named
subdomains to indicate which IP addresses are assigned to SMTP servers
authorized to send mail for that domain. This proposal gives a far
better presentation of how to implement for IPv6.

   At first blush, it seems easier to classify well-behaved domains
that well-maintained regions of in-addr.arpa; but IMHO the problems
are similar, and the implementation of DRIP within MTA software
seems more complicated.

   In any case, I would suggest a parallel specification of vouching
for the behavior of domains, under the domain records of any domain
one might choose to trust.

]    RMX - draft-danisch-dns-rr-smtp-03.txt

   RMX (35 pages) proposes adding RMX records to return various kinds
of methods to determine whether a particular SMTP sender is authorized
to send mail for particular email addresses.

   Adding new DNS record types, of course, is fatal for quick deploying.
Thus RMX also presents an alternative to accomplish this with TXT
records.

   IMHO, this scheme is even more complicated, and solves less of the
problem.

]    DMP - draft-fecyk-dmp-01.txt

   DMP (36 pages) proposes adding DMP records to identify computers
authorized to send SMTP email in the name of a domain, using TXT records
in a named subdomain.

   I'm getting bleary-eyed -- I'm no longer sure which of these proposals
is most complicated. This one, at least, appears to present complete
details sufficient to implement from.

   However, I doubt that forcing email with particular From addresses
to use a limited set of servers will be considered acceptable.

]    SPF - draft-mengwong-spf-00.txt

   SPF introduces a language for "email-related declarations" in DNS.
Messages which do not satisfy the "description" advertised are considered
"not legitimate."

   SPF specifically allows caching the DNS replies. Caching is a general
problem in DNS, in that the controls on expiring DNS information are
weak. IMHO, the weaknesses of DNS in withdrawing no-longer-valid entries
MUST be a charter item for MARID.

]    FSV - draft-levine-fsv-00.txt

   FSV (7 pages -- thanks, John!) proposes both "block" and "factored"
DNS records, as A(ddress) records under a _fsv subdomain of the "sending"
domain, returning a code for a valid SMTP sendor address.

   This, IMHO, is subject to the usual comments about end-users accepting
limits on which SMTP servers they may use.

>> The BoF will explicitly consider how DNS-based MTA authentication
>> mechanisms would be implemented and deployed, and it will consider
>> the impact on the overall DNS infrastructure of this deployment.

   In general, I predict a very boring BoF if only those who read every
page of every proposal are allowed to speak. ;^)

   IMHO, the central issue is the level of trust to be given to a
particular SMTP sender (by IP address) not well-known to the SMTP
receiver. I published my thoughts on this in

http://www.jlc.net/whitecap.html

   (Although it's obvious how to recast this into a DNS-dependent
proposal, I do not intend to do so.)

   I'd like to add a warning to limit the time you spend listening to
proposals that the speaker may describe as "the only way" to "cure the
spam problem".

   There is, however, no room for question that _some_ IETF Working
Group with a charter relating to spam-abatement is justified. I hope
those present will agree that a charter allowing discussion of all
these drafts is appropriate.

--
John Leslie <john@jlc.net>



From bmhsdyfqof@yahoo.com  Fri Feb 27 15:40:18 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23280
	for <ietf-archive@ietf.org>; Fri, 27 Feb 2004 15:40:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwomR-0002gg-00
	for ietf-archive@ietf.org; Fri, 27 Feb 2004 15:40:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Awokt-0002Mz-00
	for ietf-archive@ietf.org; Fri, 27 Feb 2004 15:38:43 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awojz-0002GL-00; Fri, 27 Feb 2004 15:37:48 -0500
Received: from adsl-68-74-184-23.dsl.emhril.ameritech.net ([68.74.184.23])
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1Awoij-0006WI-EE; Fri, 27 Feb 2004 15:36:29 -0500
Received: from 180.56.226.20 by 65.246.255.50; Sat, 28 Feb 2004 02:27:26 +0600
Message-ID: <UKRUBTUYMZNBXYJIYURMCKDH@yahoo.com>
From: "bret childress" <bmhsdyfqof@yahoo.com>
Reply-To: "bret childress" <bmhsdyfqof@yahoo.com>
To: ietf-archive@ietf.org, ietf-outbound.03@ietf.org, ietf-registrar@ietf.org
Subject: increase her pleasureprecolombina
Date: Sat, 28 Feb 2004 00:28:26 +0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--4847036912284304857"
X-Priority: 3
X-CS-IP: 58.194.5.154
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=4.9 required=5.0 tests=FORGED_YAHOO_RCVD,HTML_MESSAGE,
	HTML_MIME_NO_HTML_TAG,MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,
	MIME_HTML_ONLY_MULTI,PRIORITY_NO_NAME autolearn=no version=2.60

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

Did you know That the normal co|st for Super V|agra is 20 bucks, per do|se=
? We 
are running a hot spec|ial t00day Its only an amazing 3 bucksShipped world=
 wide! get more secks
<a href=3D"http://niceways.net/sv/index.php?pid=3Deph6636">DISC|0UNT 0RD|E=
RS</a> desmenuzar

----4847036912284304857--



From owner-ietf@ietf.org  Fri Feb 27 18:30:19 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03250
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 18:30:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwrHI-0003Ig-5b
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 18:20:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwrGc-0003Gk-UH
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 18:19:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02924
	for <ietf@ietf.org>; Fri, 27 Feb 2004 18:19:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwrGb-0006f8-00
	for ietf@ietf.org; Fri, 27 Feb 2004 18:19:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwrFi-0006aO-00
	for ietf@ietf.org; Fri, 27 Feb 2004 18:18:43 -0500
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwrFJ-0006VL-00
	for ietf@ietf.org; Fri, 27 Feb 2004 18:18:17 -0500
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id 5C764E0485; Fri, 27 Feb 2004 18:18:12 -0500 (EST)
Date: Fri, 27 Feb 2004 18:18:12 -0500
From: John Leslie <john@jlc.net>
To: Dave Crocker <dhc@dcrocker.net>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Principles of Spam-abatement
Message-ID: <20040227231812.GI69134@verdi>
References: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net> <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com> <20040226205953.GA68458@verdi> <74237662.20040227152946@brandenburg.com> <20040227141903.GA69134@verdi> <141936945.20040228072359@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <141936945.20040228072359@brandenburg.com>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Dave Crocker <dhc@dcrocker.net> wrote:
> 
> The difference is that there are practicalities of implementation and
> use that we have to anticipate.  This falls under the unfortunate
> reality that the real-world is not conducted so carefully.

   I have great respect for Dave's viewpoint on that issue.

   But I do think there's a principle here that doesn't depend upon the
implementation: that silently dropping a false-positive _does_ create
problems as perceived by the end users -- and that those problems would
be significantly reduced if the innocent sender of the false-positive
email were notified of the failure to deliver.

> On the average, user-level Internet mechanisms need to be pretty
> simple and straightforward, if they are to be successful.

   Omigosh yes! I've taken far too many support calls: "Is the Internet
down?" to think otherwise...

   But I, at least, am thinking in terms of an implementation where we
notify the SMTP-sending-server during the SMTP session, with a message
including a URL for more information. IMHO, this would tend to converge
to a situation where end-users understood the issue -- and learned to
route around it. ;^)

--
John Leslie <john@jlc.net>



From owner-ietf@ietf.org  Fri Feb 27 18:52:15 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04448
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 18:52:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwriO-0004bs-Fz
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 18:48:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Awrh7-0004Xf-D7
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 18:47:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04106
	for <ietf@ietf.org>; Fri, 27 Feb 2004 18:46:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awrh5-0001lA-00
	for ietf@ietf.org; Fri, 27 Feb 2004 18:46:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Awrg0-0001dF-00
	for ietf@ietf.org; Fri, 27 Feb 2004 18:45:53 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awrfg-0001W5-00
	for ietf@ietf.org; Fri, 27 Feb 2004 18:45:32 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i1RNjVak071725
	for ietf@ietf.org env-from <vjs>;
	Fri, 27 Feb 2004 16:45:31 -0700 (MST)
Date: Fri, 27 Feb 2004 16:45:31 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200402272345.i1RNjVak071725@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Principles of Spam-abatement
References: <20040227231812.GI69134@verdi>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: John Leslie <john@jlc.net>

> ...
>    But I, at least, am thinking in terms of an implementation where we
> notify the SMTP-sending-server during the SMTP session, with a message
> including a URL for more information. IMHO, this would tend to converge
> to a situation where end-users understood the issue -- and learned to
> route around it. ;^)

Where is the business of the main IETF mailing list in that suggestion?
It is already a de facto standard.  Many and probably most well run
SMTP servers include an appropriate message in their 5yz rejection
messages when spam detection is the issue.  Today an appropriate
message is often a URL.

There are details that could be officially standardized such as formats
that MUAs could more easily recognize and present to end users.  The
bounces generated by the near-end MTA after a failed SMTP session are
incomprehensible to many people.  Some MTAs (e.g. Hotmail's when I last
checked) include random text in their session transcripts apparently
drawn from random SMTP sessions during that last several hours.  However,
this sort of standardization seems more appropriate for some SMTP WG
or the ASRG than here.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri Feb 27 19:42:34 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06531
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 19:42:34 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwsVk-0006n4-1P
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 19:39:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwsV5-0006kw-9t
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 19:38:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06377
	for <ietf@ietf.org>; Fri, 27 Feb 2004 19:38:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwsV3-0007ZL-00
	for ietf@ietf.org; Fri, 27 Feb 2004 19:38:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwsU5-0007TT-00
	for ietf@ietf.org; Fri, 27 Feb 2004 19:37:37 -0500
Received: from twin.uoregon.edu ([128.223.214.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwsT9-0007K9-00
	for ietf@ietf.org; Fri, 27 Feb 2004 19:36:40 -0500
Received: from twin.uoregon.edu (localhost.localdomain [127.0.0.1])
	by twin.uoregon.edu (8.12.10/8.12.5) with ESMTP id i1S0a0B6000647;
	Fri, 27 Feb 2004 16:36:00 -0800
Received: from localhost (joelja@localhost)
	by twin.uoregon.edu (8.12.10/8.12.10/Submit) with ESMTP id i1S0a00D000644;
	Fri, 27 Feb 2004 16:36:00 -0800
X-Authentication-Warning: twin.uoregon.edu: joelja owned process doing -bs
Date: Fri, 27 Feb 2004 16:36:00 -0800 (PST)
From: Joel Jaeggli <joelja@darkwing.uoregon.edu>
X-X-Sender: joelja@twin.uoregon.edu
To: Adam Roach <adam@dynamicsoft.com>
cc: "'Aaron Falk'" <falk@ISI.EDU>, Joe Abley <jabley@isc.org>,
        Matt Holdrege <matt.holdrege@verizon.net>, <ietf@ietf.org>,
        Joe Touch <touch@ISI.EDU>
Subject: RE: power in Korea..
In-Reply-To: <9ACE0CEE075B494096C86C23878BF85906A32B@dyn-tx-exch-001.dynamicsoft.com>
Message-ID: <Pine.LNX.4.44.0402271535220.32422-100000@twin.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

t-mobile usa doesn't appear to have a roaming agreement with anyone. 
t-mobile germany has one with sk-telecom... It really continues to annoy 
me that the US carries can continue to bung up international roaming like 
they do.

joelja

 On Thu, 26 Feb 2004, Adam Roach wrote:

> > -----Original Message-----
> > From: Aaron Falk [mailto:falk@ISI.EDU]
> > 
> > Has anybody tried this kind of trick (putting the SIM in 
> > another phone) 
> > with a T-mobile sim?  I know that T-mobile binds the phone to the sim 
> > but don't know if they bind the sim to the phone.
> > 
> > --aaron
> > 
> 
> As of three years ago, they did not. On the other hand,
> my research so far has failed to turn up a roaming partner
> for T-Mobile USA in Korea, so I don't think it will do
> much good.
> 
> /a
> 

-- 
-------------------------------------------------------------------------- 
Joel Jaeggli  	       Unix Consulting 	       joelja@darkwing.uoregon.edu    
GPG Key Fingerprint:     5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2






From owner-ietf@ietf.org  Fri Feb 27 19:42:34 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06539
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 19:42:34 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwsSq-0006fy-3f
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 19:36:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwsSC-0006dq-Eb
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 19:35:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06298
	for <ietf@ietf.org>; Fri, 27 Feb 2004 19:35:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwsSA-0007IA-00
	for ietf@ietf.org; Fri, 27 Feb 2004 19:35:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwsRL-0007DP-00
	for ietf@ietf.org; Fri, 27 Feb 2004 19:34:48 -0500
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwsQh-00078R-00
	for ietf@ietf.org; Fri, 27 Feb 2004 19:34:07 -0500
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id ADF31E09AE; Fri, 27 Feb 2004 19:34:03 -0500 (EST)
Date: Fri, 27 Feb 2004 19:34:03 -0500
From: John Leslie <john@jlc.net>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: Re: Principles of Spam-abatement
Message-ID: <20040228003403.GA13563@verdi>
References: <20040227231812.GI69134@verdi> <200402272345.i1RNjVak071725@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200402272345.i1RNjVak071725@calcite.rhyolite.com>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Vernon Schryver <vjs@calcite.rhyolite.com> wrote:
>> From: John Leslie <john@jlc.net>
> 
>> But I, at least, am thinking in terms of an implementation where we
>> notify the SMTP-sending-server during the SMTP session, with a message
>> including a URL for more information. IMHO, this would tend to converge
>> to a situation where end-users understood the issue -- and learned to
>> route around it. ;^)
> 
> Where is the business of the main IETF mailing list in that suggestion?

   That statement -- outlining my personal thinking -- was intended to
solicit consensus on Iljitsch's principle from Dave Crocker and/or
those who think like him. (I know most people have given up on ever
finding consensus from Dave, but I'm a slow learner...)

> It is already a de facto standard. 

   (Most people, when they say "de facto standard", mean something already
done by a strong majority. But, of course, that's not what the words
mean, so I won't argue your usage.)

   I'm frankly not concerned whether that practice is endorsed as a
standard.

> Many and probably most well run SMTP servers include an appropriate
> message in their 5yz rejection messages when spam detection is the
> issue.  Today an appropriate message is often a URL.

   Agreed. Enough people are doing it that the idea will surely spread.
Even the dinosaurs (cable companies and incumbent phone companies) will
catch on eventually.

> There are details that could be officially standardized such as formats
> that MUAs could more easily recognize and present to end users.  The
> bounces generated by the near-end MTA after a failed SMTP session are
> incomprehensible to many people.  Some MTAs (e.g. Hotmail's when I last
> checked) include random text in their session transcripts apparently
> drawn from random SMTP sessions during that last several hours.

   All items which I'd be happy to see discussed in MARID.

> However, this sort of standardization seems more appropriate for some
> SMTP WG or the ASRG than here.

   There is no MARID mailing-list yet, so we're stuck here for a few
more days. (ASRG is not an IETF group.) In the meantime, I'm trying to
solicit consensus -- no matter how "rough" -- on principles of spam
abatement, not details of its implementation.

--
John Leslie <john@jlc.net>



From owner-ietf@ietf.org  Fri Feb 27 20:25:33 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08239
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 20:25:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Awt9a-0000bj-33
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 20:20:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Awt95-0000ZV-9C
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 20:19:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07983
	for <ietf@ietf.org>; Fri, 27 Feb 2004 20:19:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awt93-0004Cl-00
	for ietf@ietf.org; Fri, 27 Feb 2004 20:19:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Awt85-00046P-00
	for ietf@ietf.org; Fri, 27 Feb 2004 20:18:58 -0500
Received: from mail-dark.research.att.com ([192.20.225.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awt7Q-0003xN-00
	for ietf@ietf.org; Fri, 27 Feb 2004 20:18:16 -0500
Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.30.103])
	by mail-dark.research.att.com (Postfix) with ESMTP id 038F3E81B2
	for <ietf@ietf.org>; Fri, 27 Feb 2004 20:18:33 -0500 (EST)
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-green.research.att.com (Postfix) with ESMTP id 5E9B2F3B45
	for <ietf@ietf.org>; Fri, 27 Feb 2004 20:13:11 -0500 (EST)
Received: from berkshire.research.att.com (guard.research.att.com [135.207.1.20])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id i1S1HfZ27489
	for <ietf@ietf.org>; Fri, 27 Feb 2004 20:17:42 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP id 95AF57B43
	for <ietf@ietf.org>; Sat, 28 Feb 2004 10:17:40 +0900 (KST)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
From: Steve Bellovin <smb@research.att.com>
To: ietf@ietf.org
Subject: nbearnote: you're infected...
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 28 Feb 2004 10:17:40 +0900
Message-Id: <20040228011740.95AF57B43@berkshire.research.att.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Whoever is at the IETF meeting and has a machine named nbearnote 
(218.37.225.246) -- it's banging on my NetBIOS ports.  Admittedly, this 
isn't going to be productive for whatever worm is doing this, since I 
don't run Windows, but that sort of thing can mess up the wireless.

		--Steve Bellovin, http://www.research.att.com/~smb





From owner-ietf@ietf.org  Fri Feb 27 20:53:18 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10120
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 20:53:18 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwtZX-00024D-Vr
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 20:47:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwtYo-000203-H1
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 20:46:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09787
	for <ietf@ietf.org>; Fri, 27 Feb 2004 20:46:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwtYm-0000G8-00
	for ietf@ietf.org; Fri, 27 Feb 2004 20:46:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwtXH-0007hO-00
	for ietf@ietf.org; Fri, 27 Feb 2004 20:45:00 -0500
Received: from rufus.isode.com ([62.3.217.251])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwtV3-00077f-00
	for ietf@ietf.org; Fri, 27 Feb 2004 20:42:41 -0500
Received: from isode.com ([211.255.232.93]) by rufus.isode.com
          via TCP (with SMTP (internal)) with ESMTPA;
          Sat, 28 Feb 2004 01:42:10 +0000
Message-ID: <403FF07B.4060400@isode.com>
Date: Sat, 28 Feb 2004 10:35:55 +0900
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: Travel from Inchon Airport to Best Western "New Seoul" hotel
References: <4A3384433CE2AB46A63468CB207E209DB2432D@zoe.office.snowshore.com>
In-Reply-To: <4A3384433CE2AB46A63468CB207E209DB2432D@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric Burger wrote:

>Best bet is KAL Airport Limousine (actually, it's a bus).
>
>Tickets are W12,000.  You can buy them in the arrivals hall (just before the exits) or on the bus.  Bus is cash only.
>
>Stop 4B or 11A (depending on your arrival airline)
>http://www.airport.or.kr/Eng/transportation/bus.jsp
>
Instructions for people staying in New Seoul:

Use the same KAL Airport Limousine (#1). The first stop is Koreana 
Hotel. Best Western is just across the street (but don't try to cross ;-)).

Alexey






From owner-ietf@ietf.org  Fri Feb 27 21:09:04 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10729
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 21:09:04 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Awtp1-00035Z-RZ
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 21:03:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwtoS-00033I-Hz
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 21:02:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10586
	for <ietf@ietf.org>; Fri, 27 Feb 2004 21:02:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwtoQ-0002It-00
	for ietf@ietf.org; Fri, 27 Feb 2004 21:02:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwtnT-0002Ct-00
	for ietf@ietf.org; Fri, 27 Feb 2004 21:01:44 -0500
Received: from out003pub.verizon.net ([206.46.170.103] helo=out003.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awtma-00026y-00
	for ietf@ietf.org; Fri, 27 Feb 2004 21:00:49 -0500
Received: from MattXP.verizon.net ([210.96.195.25]) by out003.verizon.net
          (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP
          id <20040228020048.QIYP8426.out003.verizon.net@MattXP.verizon.net>;
          Fri, 27 Feb 2004 20:00:48 -0600
Message-Id: <6.0.1.1.2.20040227180029.01d54398@incoming.verizon.net>
X-Sender: res06gzk@incoming.verizon.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 27 Feb 2004 18:02:05 -0800
To: Joel Jaeggli <joelja@darkwing.uoregon.edu>,
        Adam Roach <adam@dynamicsoft.com>
From: Matt Holdrege <matt.holdrege@verizon.net>
Subject: RE: power in Korea..
Cc: <ietf@ietf.org>
In-Reply-To: <Pine.LNX.4.44.0402271535220.32422-100000@twin.uoregon.edu>
References: <9ACE0CEE075B494096C86C23878BF85906A32B@dyn-tx-exch-001.dynamicsoft.com>
 <Pine.LNX.4.44.0402271535220.32422-100000@twin.uoregon.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [210.96.195.25] at Fri, 27 Feb 2004 20:00:47 -0600
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

FWIW, I'm roaming with my U.S. AT&T (AWS) SIM just fine here in Seoul. It 
took less than 5 minutes to pick up the phone at the airport with a 
pre-reservation.


At 04:36 PM 2/27/2004, Joel Jaeggli wrote:
>t-mobile usa doesn't appear to have a roaming agreement with anyone.
>t-mobile germany has one with sk-telecom... It really continues to annoy
>me that the US carries can continue to bung up international roaming like
>they do.
>
>joelja
>
>  On Thu, 26 Feb 2004, Adam Roach wrote:
>
> > > -----Original Message-----
> > > From: Aaron Falk [mailto:falk@ISI.EDU]
> > >
> > > Has anybody tried this kind of trick (putting the SIM in
> > > another phone)
> > > with a T-mobile sim?  I know that T-mobile binds the phone to the sim
> > > but don't know if they bind the sim to the phone.
> > >
> > > --aaron
> > >
> >
> > As of three years ago, they did not. On the other hand,
> > my research so far has failed to turn up a roaming partner
> > for T-Mobile USA in Korea, so I don't think it will do
> > much good.
> >
> > /a
> >
>
>--
>--------------------------------------------------------------------------
>Joel Jaeggli           Unix Consulting         joelja@darkwing.uoregon.edu
>GPG Key Fingerprint:     5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2




From owner-ietf@ietf.org  Fri Feb 27 21:49:52 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12374
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 21:49:52 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwuSh-0004zH-OZ
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 21:44:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwuS8-0004wq-3D
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 21:43:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12186
	for <ietf@ietf.org>; Fri, 27 Feb 2004 21:43:41 -0500 (EST)
From: wessorh@ar.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwuS6-0006u9-00
	for ietf@ietf.org; Fri, 27 Feb 2004 21:43:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwuRB-0006ol-00
	for ietf@ietf.org; Fri, 27 Feb 2004 21:42:45 -0500
Received: from 211-255-46-33.rev.krline.net ([211.255.46.33] helo=zrclgrbipyzfge1)
	by ietf-mx with smtp (Exim 4.12)
	id 1AwuQJ-0006iQ-00
	for ietf@ietf.org; Fri, 27 Feb 2004 21:41:52 -0500
Date: Sat, 28 Feb 2004 11:42:20 +0900
To: ietf@ietf.org
Subject: Flayers among us
Message-ID: <psbmboppnsmsgokuktx@ar.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------wtgdpoiqtngsibimjfmc"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

----------wtgdpoiqtngsibimjfmc
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit



----------wtgdpoiqtngsibimjfmc
Content-Type: application/octet-stream; name="cbabbaa.zip"
Content-Disposition: attachment; filename="baa.zip"
Content-Transfer-Encoding: base64

UEsDBAoAAAAAAMBEXDBKH8ydAD4AAAA+AAAMAAAAdXZmeHZteG4uZXhlTVqQAAMAAAAEAAAA
//8AALgAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA2AAAAA4f
ug4AtAnNIbgBTM0hVGhpcyBwcm9ncmFtIGNhbm5vdCBiZSBydW4gaW4gRE9TIG1vZGUuDQ0K
JAAAAAAAAADEoj5LgMNQGIDDUBiAw1AYgMNQGIPDUBgO3EMYr8NQGGjcVRiBw1AYfONCGIHD
UBhHxVYYgcNQGFJpY2iAw1AYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAUEUAAEwBAwBCRUBA
AAAAAAAAAADgAA8BCwEFDABAAAAAEAAAAHAAALCwAAAAgAAAAMAAAAAAQAAAEAAAAAIAAAQA
AAAAAAAABAAAAAAAAAAA0AAAABAAAAAAAAACAAAAAAAQAAAQAAAAABAAABAAAAAAAAAQAAAA
AAAAAAAAAACkwwAAFAEAAADAAACkAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAABVUFgwAAAAAABwAAAAEAAAAAAAAAAEAAAAAAAAAAAAAAAA
AACAAADgVVBYMQAAAAAAQAAAAIAAAAA0AAAABAAAAAAAAAAAAAAAAAAAQAAA4C5yc3JjAAAA
ABAAAADAAAAABgAAADgAAAAAAAAAAAAAAAAAAEAAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAMS4yNABVUFghDAkCCIWlHAXMc5u5GZQAAKgwAAAAbgAAJgAANP/b//9Vi+yDxOhT/3UI
agBoOgQAAOgCDGSJRfyFwA+E/eXbtq8LABkMEqD0agRoABB/2XTtEQkW/AfV+DPbC8B07tnm
vn0S9CwC+BsMiBZ/3WO3VDEwQFNAaA0JUApGko3Lw9rvRfBQMPhSBUsKnexgt+d3MiFq//91
7Hwm6FAL7N0G+zSLXegKEFOAADZpxv6DPQifcRCLw1vJwggA1PQMyBbA05BNGgzJyIH0DPhs
sMjTEvgHEG8jtA82bIHE2P0jRAiI3X1/FyKJhRCDnwczwJIttu1eJMeF3BMkAh+NCdnZXPe9
tSQvUmUvfBj8tnsr3xKUTYud+A/rFDCbstlTWOvNDPX4v3yuYfdqAgMDaL1Ak/0cCze33UB1
BCYMHuz4UKwQti07O8eCzx9TNx/hhttKC2gmHGipgSsBx4vYH2TzbBUGeq6CI9hbw63ZbmN1
8FL8UByAARhwcAu/gEu4x1IEgVkGcw3v7nSOaCNtvpqHbuviKAvwqwEFZA4TnjDmI/926bgL
vda9e7BwM7LJwwYCPbhQR0DFe1l39jWggIs+PAwPANE6n3WfLaL8U1Z+bB4Mpmju/xl7KGms
LoE4LXVwZHQbB3b7/f9kZWx0CUCAeAMAdenrD26u6QQEVgneIFs7aATgRqRMCUOefBMmDpqu
gp3HlmMss4NqHzpoRCAfyIc9jmhZjmhQOxhvdo5MPRB0MsFgmk6YFBYLpZPfhz3s9RxjgG/E
63q0DmMP7wu9M/ZoehafH09ePuELNy1Qi7doiBMACXw9AsLNtOGvsj1eBgFGcz5sIwxqiusP
uXRBUSz2f0J1GAvbdBQL9nQQuBuzE24cpvuaXlur4Ive/u7YKMwAuJAf/IA4ALrAhAh0AcP/
v7sVZ3N0BxB0++vy/kABU1VWV1C+079097cWHCvAi/pomAhk/zC9IGoNWfP///+3qxFki0gw
jNr2wgR1dLpsAv5/iiKA/ASKQgRyBb/d/m8HBXYEZrgzA8HgEAYBASxRDItCHG/F3v2LWAi4
WBea1qu4bgcGq3QFyIBs7bgwGAsRhvzmbg7ImlsaoYAgBQD/29uOBAaAWAqEuwj3v4D6YLpL
RVj4Wwf+UHMCsAM5kxcoPFp0CoHrf3P/bxgAsFrr6ivb6yiLkwgZrQN18TvTdt/+N/DtUY2L
NAA70Vlz4YvqixIBgzoGdfC7H+wCisOyUav/FXhtWTPBq4Xb7W/us9riR1i6yGgDw4lHBAdf
eFmebAxYjU8gjdA4X/b39r/1dQOD7S1FMDvDcwOLRyAfJLjtxk34jn2rr7i3GAarGdqnBr//
RrsljatX3nIVO8VzES3xZF9Z3WLbu+jeroXJdYe5JiVyMZqt9N8fLWpIWYPAVTkImwYOBwr/
cllYdRUZikj7gPnoJ9Nb/98EzHUFA0D86yqNgwBP4bkAKHsuebqzTxYTvRACcz8nFNtgtWSP
BYL0d/+nf1hfXl1b/gBsbItUJAyBwrgWi0QkSwvc8QjHAoQHiUIMTcOhALZtu4HwkA2KUHf6
fAoEzNDott9ISEl158ORCoTDP/9v/786dHqLUzyLfBN8hf90b0sTeIXSdGeL8gP+A+/Y+MPT
PZ9zBStC0j9rlYtKGC9c4P+LciAD81LjGYsGK7TGBFhJihRz22/wBzoUL29HhNJ186xambD/
3757dSUrK0IkQffZIg+3BEiLywNKHI0Ugf/muv+LAjvGcgQ7x3I669stw1J0bE50U9tv//90
YXR1c1RvRG9zRXJyb3IAEkFsbG9jFWXsbvvtVmlyGmFsTWVtFnkXRnJlE/etxKdPcGVuQBhh
ZABSBM8e7FtQQWNlc3MeU2V0G0FmpYbD/2Zpbml0eU1hc2tgOwIdB+/+YAlKDOMC/+ELCTTC
FCHhTTyDDwlNCiaLVRSLNfwNfnQP90AgPIAwdRqBym4INRszuCEYUh2LcMnGrvTdOGoFWTU3
oUKNTX307QjdAT8JSXI871JoiRiwdQWGpuc6GAIUD6HdNclRbf9SCCvhWnhg/72NB6UMUU5B
6/VqV1jYkEfC6/BkGMnLkFwyFBAhDLkLhzQNFe15FoLrz8jWxlLEdBDrBbnn4hvfzpnL6632
RRWAQINy9robVXUh2VK5txD2lL23rwawATuuanhZJW/w9vUVfCCmw5wE4+580YvIZ7rdS/VT
i9rKCFJ4bEO1b21/dEIryYH6/wB/u0EwdDQLt3/r3+QQkXMrOEMCdKzqAkLB4gNSTXMw1PHC
FkIQIgNRRE/IYFg62yPJUBQYGVvR9PfmZsZfGGoGWks4SwJsI/G/+UqJEIgQM0MEUM8Idjzw
MNuI7lBRy1PeXGvfgw+URf9YfTw1PFEwUN+2t+576AJAeQMDQnFNQksEiQhte3v7gDkHWHND
QQT/0usIZggCA9lu/dlKAkkYWIB9/+UPUGKUMLoYggt7DG14PLvkHAyv5FdMhe3Qu3N95FRX
IEWrMX/jBQyKy1erOQsPlcDQ4Ag5loUWH24YWSCDPcx2xvxfUnL0WSjvSMIlHAmI2olN/KO9
4fbjD4M5SIUG2f9xCI8/GtkwCyxC5h4Qrd0WpBYp1xP32rLPaG2tukkrUeCwUlCt7Y53JE6L
UFA9QosKDHlB4RDhhkE4eTVQXkRAA62/QNJLIOMjgHvRdGvi9kvAQAyD6ATfi9SABEK3XIFD
gd07nEwkOAvt/xAQsBCERRx0BAhEC40sDS8IT5NTJFMVWVk03YUNsD/jJ0VaWVrCEm5zL4oM
Agh35CBUpfu+UOL/A7cDiQGL09qnL9NwibYP9loFCVCPaBkjGw0j5BwDph0eIDvsAACQ/yXf
MjIysgWMiIRMMjIyMhgcICQyMjIyKCwwNDIyMjI4PEBEMjIyMkiQUFQyMjIyWFxgZDIyMjKc
oBAMKDAzMggAAP//ryJrZXJuZWwzMi5kbGwATG9hZEwezEX/aWJyYXJ5QQCRDABNWlE2m4nq
AwL//1J8sklpB7RMzSF7QP7dEIgDlVe9NdE202bvvvnu0gdfKcBmuC0WwWbQG1JpY2jy9gg7
S1BFd0wBBPL/kOJFQOzgAA4hCwEFDAAwb5LuyEgLPKAQEAvSzYJ9vAQzBwygt+zsfXEyAR40
EAd/BFoOyBBgQdw7Udhzgy9IAN9fYbunYAEeLnRleHSqLubCvmCQ6wRCIOkGuf0ucmRhdGH7
8ggKajQ0t9gpQC4mJxE4ULVNSdMIPsBPZRvs2Rqu01iQc0YnKkqgKUJ3v/ELFXBXjT2AV3uL
RQiJB839j/bHBcRRCq+DxwT3JcgMFOod35H/gT0FcC9141/JXzb7MLVWV1M/Hw+CwVL9OXNA
L3EKaAURm/MfL9WQKcdF/FKL94sGJf2/qX6Ai14EgeNBC8OLyNHoi9aBwjQGAvD/3x8aM8OD
4QELyXQFNd+wCJmJBr1XyO7b/zuBffzjPnXBdNvIgeT8//9vAtdnMJ1NSCABo6Hw3/7sCv3B
4AID8HSL2MHoCzPYi+3O/hLWByWAViydCw+Mxu9fCt6OC+gSUTPS9+LCW19ev1E/CCdX/It9
CNTB6QIzwGToNvfjAvOrC3YDCapK8N9+u6JTVjIz22aL0D4Qih4D04H68Z+/vzeLfAaB6gcD
wj0GfAUtRuJTsLmA3VNeXqIr+O6FfotdDF1qGehr/pk+sNh/wGH8qkt18VtXHwToS6lMNUBu
Vf/NW7cfK/HYCRDoFQPYg8MQU2pA6MzXVNuKKgyJdwwkeJ2f3QhdM8YrDOjpKs+5jsAaUdYM
QArfpfuaxVMIvD+L6woMQ3vVgTA1QjUrcF+BIEUVIITR7g5oDOiXKQRhrtowjDVVfQzR9u6F
hcAtrAUI4gcEQ0PrCwx+e/s2AwgCrElR6VlRwdyK0IDiP9Jx9xdPBuLzWegvPJKrkgGD+BsM
9hJ1D09Qog0KZqtYWd2h8F//da6Lyyv5sD2QtaCAXt7+9vo+cxcEM3cNgMJBB1p2AwbrDt1t
/9YEywmA6j7A4gIKK2bi1sPbw86DywFqALmLVawS8MkiASbL+I1V+MJYBN42jwLHQuMjajR7
3YMI9S4Ufi5Y9rs9Vo0TxwYpx0YwaAzsgXACMZh6cBDDaSCpjZacHGYUEgB63yyyxYlZAooh
z5ZdNjO2WxgytbPnHvBkIjo0UMmGvTf2FJc3DMpqOxwjGDszUhxmY7so/7/r38i6xNPi8eMV
b4vaweIFwesbC9MPthhA6SGYtgMW7jQ+RQxzs62vo1CCBzVNnAFKt21acBn/0kD38T0CRQsw
AaYg5Jfxm9tuCC7YJ5daiRCPAOstizRufOFaH9CLCDs2dQY4WmTsP1yLQATr6FItqs2eiNPx
LptA99QIA92bLFfHhdgGKA/E+3abeugjLImFGY0Y9c79TLcM6IkXZkS/R1BE/G2pKerXR4PJ
//KuUp5tbLP1/kEoHwsu4AAXtl0i3oA/sNVFSaXTwTbruAyUJiqkfV+WHlzY/2pk6EAg8sJE
DOnCGpyu8NoPHqEVeAjkN9s3F09qxDQ8VriAfhgz/8Dd//brKovO0eG6CQBAFffB33QK0emB
W/9W+vEgg7jtNAlKC9J154kIHQQD//7oRoH+EHLOXnpWgD3MDjR8m4bksMYFDQF09wXuOi1R
dYmy6ggyjNrW2I//nASFbsKi6B/CYBGRRUPwBFtvGdwWmdS4VfBm17z2t9vCB2a9CQxN8gfh
BWYLTfYDmq578NFmiYUh+BwL+pqE4k0Y/WgsxdodEOrvJZrL9CjcGe/95xNoct/hRQopDRXx
Lff3eFv8+MkC6xOfFfToGdSwDzcK/+vPM6QlRq2T8D3MJa/0bIBTc1/DyGF6dIR4gHoDsc0g
FJSA5SSXEorZ+UAPhLIBI7g8zVjDTMEj+I4eZWu4LCHO0/nmFgq4A2ZZnsguir2W0fbu2H5z
gMcpSwMEZgeQZbv9tgJmGJBmj0XSKNpQLNiarunKjP4U2JYH2phIxfb92sL+59wCmgOMbdvY
g3/gCuAgngXk67bbsuSi8YBmGOgDphAObWtlgPgCHjPBM9dUzKUo4T0T5ISfcyObE80kdfR2
4fA7hGd7JHWgdBwvNsLuHfQZL50kXgFec9mW7evIaezI2YoBAgnB3HaOFAAEsEVlCevc9r41
Z08yLqY5kh6yYAY7UoJKHri7Nc/mBQbAAcDCLewrX3wTZlvSxC9jMRh2zd/PpiYjB/joHkOg
6JmcwVPhCHwMhPQVpqeiCB3gx05jIwiXbPRS9CRSnzupaBkJBwpVht93IXAizTK/G74pakvF
P/EJ6Mb2hDGIB0dOIAjYZA9iNzo1VpMZhQM3MAeK4w2QGbJ9GbRQgwzSdDwECxnza4ccc78y
2VHmEieeve5ygILoNAlQCngwUAczJ8873SO3dvSDNbEtvT1iNBYuu5gJIeG33bwF0AcJoxbr
PhMlecjIgyMEAFB2yWCHoHJkUvhFmHMjQz34C+I+ZJDBvuEQQDcRFeeQvfBTh/siCJxsZaRF
6yKRfqUC7we7ZQDZFL4iBywIE/RyULAiJ8FNCU6XEjqWIsF0jyd8IrJnGmFOtssdaBUJMZIi
rtxTr9jzs0ZA6C0h9CiNX+z7uZUPBwUiF/A7F3fWXLY2ahQY3K/1CApz32Mz/2gfdg1TIwip
aDDSYfBMp4bAS0XDBemaG9Cs37KkUkAgpLaMHU7elw/4ZSwa+RArrygeIE+cbYMV7hcEao4T
NXZPvFVj+NHgomQRozg0KJnuiosUJEeR8u9r9HYp/zUSCxw8Cbp3wpuXU+i5HyyxB4ot4BDc
Z7IxB3zQc6vrxjLjIWre4Ni39A2bu1vHCdQHBeIDAOYO3dgs3XM7/Ssg0AzgHrjRbJPYQ1GD
THUEjMQTlzfrA+DD3nATN1fiZRwi+PJwiMJ5YhX81XLgGCzlukkgRTIXEh0g033oGh/GQPuM
PXYnSU4TaDsmDs+n+0TLU76+/ARCt1WDiVrsLApXNDsFt7k5OSEG/UQTCd2SeU5+HHUPAIB1
hen+sQ50DGoFaM1RWGqdPmHMC4cGfQHDaIgM3Nmu+Rrr5tQATqXMjddcZssNJX7z9uthJ50Q
ch+VdRsPBuHiHFyc72BIS7sGBIsCGATMt0X4zUk/CSUMMJnbteivB6UA6xIyDTmhR285+z70
ZqH3kemFCEb4yUYoRmwRAY66F891VI8KJMgK/FyLLUz7HneQYZ0YQh+7ArD/iiH3bFvTEJIU
jkR7VHs/8YH7ZnYHuQYt70ajuM3jMaYCgFAls8Ho348e5H4eK9inUBmLskFHoRCfGBVqAWpb
AbxmmpSzHQT4oBQaK9tnGMj2KsgmslX/Fu3SyTkwBxQ4ElkTL9nsswFdIl7uxbZRxy69O7Zy
YwQLMgZbwbxZFB8WvwPmaYsL0/OShwtbIfpC+52/8SQ03yvAFGo/SYlihWa+U7RHlzGheJtv
7B0ENXgMGuqAfW5Hcfj+IHULuHTw6wwQCbzv1C10Cg2ABUYJG92OOmoGhgIjHfS5NJm2r2D4
gfA18S0MtRrwNPYfhpaFQrg3DAXSL1W23+sfCnUKBQhZJesPsXdWfqa8/UMUzkRmtrNL/Ogc
WQgK13E9biyJZTT8+isfZ5zxBQIh+0QAJkA8GQwHBSL6wBxv9raW6IsyG/mOMDDSZxwmMIzb
Y4SDdUz8GYMctV4Ek5182BUI6HlIQgg520LI6CQZQEIbjG3yLVg2ijjZhhuB+uj1G2XtB7xy
EJZKU1NR4++/bUFLLFteBHYEhsRmO2HIRtTyjuM/fpvdt4kDUQEJgzvHAx/reqPjbc9K/zPV
G6zHZzm5xCFdDphYCOwQNYSDHexQKlIb3Xd9bKO6BVkmKYsVRHOB+vRjNb0dJ3MbLT5WcSYC
u1u9GsaGcBRxBlFfpltouz/rqIb9DU0QeIKGeI3gFN9eLNidDDJqDD9GGkOxbObhCMkMBRAI
WG0qJpMCbSG+eLgTOrsZiAVJFp4NRhYJSB1LSKPlAhzmShMJEi0aJw4Hi+5HU1anWGgRisHU
Gc1cOfcZ2L2GfGi1Slw6RN+nZ/jEFOit6HWvaExesPBMHWap8KgZYCnqfs3onxaTDQYrI5zc
vIIaehP4aRDgH7CTXrRXv0hR/gUYAT7oZf/o7Mlme/cAyDtxaMAnCeh0LMDl7ujK/w4A3W1l
Gdrgjjx5gGojnxjpEpXqGCxKVjZWqtTd/tE6uXCR6LXtBb5fyLntvoYdHYPGq6IS4EIDNYHu
m+IFBgwkWeiLFl6sEwthJpRlarFBFnBPQPVps5R28W6txsoDha4NeYWvIwvuA9InQG0IZlIT
aIIYFpzx2MEqDY7VUwWvfI6tzkn66XYkIGmwYkvAJ1ixPTvWHF7vvW12CQgLcnMLzi1SOTxT
DsiRWGSQQQZZHRBMyC22Jls3/wLjrhXMFJ5YOwUEGvgWyq10XdsCcb0ZuG/2fvzKq6Ezq2rw
L28/a5y5VueRAvkIAw+FijusjQUdBAGW+e+WS548hgJ57gSodn7uQm4dGP+1QswggwwWQzZw
eFgsdr3tFg6HGZqHjPXrV7keRnNYMBe2HBIzKDPZIy0jIuFh57BSAhojFtD5uAHmoKC/AQyY
AWeLBchapKX3ku3Y0LeDvRiasNeCtS9SI9YGJBvrGu+1U5Neix4BVz+Egx3rqhifFWADdRFo
pBkbsF+sdTKoO+awyEJ2KB9JWjU47OkVAT4EjCiHMNkmU+kCEgiyCk5yMC7sAEzoAwz45ITg
TtAbaoIVKTkkD4rq2xXJMw7JyBW3FaBv7PYwaWx6tTQ6as0R2jRbFvFXFm4C5mCwQMF1byaE
tzusWjcl6xwYMtjPXLYdGd9pFW9kwUBj+lyplINknm0LE5So/c1rMngCxV9esvAcsfB6sP8F
H5Uq6+qEaHitQAhbZ5ez2nXsmY/rnPQH6dje7Hzq/BEq5Y0U7/q3sYA+Q3UagH4dFGaDfg45
DranDUVx+wqHdk+26lYIJRSy6lsNRD4MkvyYMQ5faEgCeGfEsYLjEwv4EPzBBzxYIxXob3UV
m3SRD7HGEyy2Jd0RWgyfZRSLEoBrpoVToTsI/cKBA4cAB40TuuwlBUfi2AzgJui89AI94C/V
sPZxZsFN9ghmt7nZBNoK+AjaLdBBBjoYCbgTAv//Dd7F17Au/CSL3yvagH//LnUBS4ld8FFS
0CDLYTYB8Fm5mLVhJR8RM7Al6kB0b7gwm+TZBYXuD+4CHZBCBmTuAXWfrZb2Tny5NWmGWRqM
WoWc9SULheHhq+cK2KdT6NrQmaGzTkf84y4TWG9yDE6A6RYso0RnL1NqDIp/sZvFYhQAFzrz
EmgEzNfLyzxWVgLqN0bHLAT09GwaKOkLdlkyR8H8Vnl7QGvnGRGXsEA7uY0cw/Mrnl8SrMPa
RrgQySUS/woZowSAV42lanZhQozbEDQScRH8fbtthfP8D6yoRxwkP2a6+MQWc6yDA/DPVhvO
vftS18Ve6yAKH3VCyvAvUXBQ63v4WeMD/POkebjVtvGqPapni8ZlDAq1FNtsLgYQUCtHuqTg
kb+CK0OGJL3uCoNYLYrBwYvGifJ9dBY0g82i9usO2cadK78XVkq15+MXwWrCeb4QFPzoOHvb
JhijNsf80E4GCATqDfClAvdGAg8Ucw+3XiZ62pU7lvhWC0rpWEPd9vCtPQAdAR5UFFAbNXp7
ci5QreNmrVpJa1QojCMGgx5dENofmWxmJwZmWmY7VfJfdYFrje0FGQiWV7hH3KJLdbDHCiXQ
H0hnERDz/IA9b1Jjuf5+ksYFCAHo8TiYc8nUF6nmd0BNlMaN5CoWmYrqZXE2ltUgWD1E+IzX
Afmr1OZqAxulhApdnQNy5fipnmHTOwSGHxKbDH92DkIcM//VVw+RF5Z0OeHluRlBzpHyGP14
BmcWAn1qD7JZz264m2zt8Rn2AXcFd+HdWMw9MjIwR4XjEqBbKHbo9IHGcTH3qmbcGbGR8Ioi
Zg04V+bblgwKVZgKgwzYc9ELY4mSC57nIPT+NX/VbLHZspRSFEAMQmAMMsiQRk+xOdhjlzwS
DGiblNEODtklJ8AODlH08OclJ0/9AF/qAGUvGeQIaKx/bg7mkycv5LwOovCrAJNP85INmAC7
LQ5mHbKRu3lCX/Bwfmzc/D7O/TM1NHNdlKjkBitwPiv4cjH0sRZ4PMMtmXbTYH/AsfCYIw4S
JuvPW/DOc3IDEHKaV551bQFHpQ2wvOPkydrs3hEPcqzjx1s2eAJbAPJAkd8N3enGB+gfQGzd
/FgMElp+/F6MHLkBKcwMXi34vsPEUxeeTti2wmzm+ytFCCvYEecPENggVRAgwRAQcbrJMlMU
ShCl6toKhS0bAheNj73A0DlLdGRpi1sI2wOXwOvlOlM7EIq5mxYKNFARIRAoLgywBJxOAnUN
Oo36/1s6iRrrB1GLCYlZCFmJGViMyPTUFVsIXwM6FN7U5wUKe2cYj0MMC54UpUNEh596C0WK
L1wFhMvHBYWDTMLtDrIJibseBL+NDYWtXVeQU7Qr/Ktr8lEA155B6FNXrM4FtO5nAkPo8iGL
0mXbUb0YXP8xeHEEBfi576iWDPSKQwRR6HQjM141gy6ZvzkJ8PuHD8LU++R1A09/6w5HC8E2
j53JSwf06EPrCz4jTvW/WhQLf4HoTgX2gQNOFmQEkl8L+wd92Z/bHnIK5DPSuOh9Nbxv9yUQ
BeJTG2q+o+q+wDCYtQhawS1QK/CNQxMDw2jgEsQeeEPHdR3oGfAxbVNoAjFsMgrcYB8z0bMD
gbMU+xcGIa1W/d5OTrEB/TtVmu/+f3I0rDwwcgQ8OXYkPEEHWnYcPGF6C/8blwo8LuY8X3QM
PC10CAoNCzDxt4UKUAc4Q4rI68f8ZrJr3xDWTfxMS3Mz60pzBAoGSshJFzIbAcQM9QJ84BnO
iAnyCFEFAbiRJgouqshXdG7BFwcoCSx3YgwRKFkFME0inDj5Anv0iSvDtw1yAE34qfgPg6Pw
gAvAtx6BffQQmnUONlihtsyc5jH8yA+nY/BAdX7yzP5v/hD+Q/wH/Mgry4H5aF6D+QV2WV0s
vBcJ8429bsusOwfexVu4qjiE1+LyLQvSdDm17tkASAB6XVqubvVNtjImEglQ2JHoHfuDNe0I
I9iNChr/VRBe6VQVDoZYljYk3hY95KuxATMIDAk5OXJaZQhCcTYgzxEILIETErmvHuJoLMBO
rRUgWE9uzc8HxwcVm/jxK5FoCUsZ4LQFDfwRuHAKrci/y1JC/QZCPpkHCadoiIMpE99M3egM
ikWlDqK/9wW8kUUEEvvf/WadGzBqyA9ELm7q5roCkAsmqbT6e+C+53AKNKcMaSLsZq7V4b5g
lh1Trz3YlHD0aL00GxBZnMwBvqHSX2KLsMt9V2g+rnJNB1MscHah7rQKi7AZUzuZgEE+jCX4
iM4GcMA7aJcHxgQYZo1SLGa3tlGjHfpvgQUGOFL96+58QmUbEvcCBHQaaBcgBCODTUsM8Fvh
RoBMNAlH/3W5wXJenWoKnZhW4E5+mlIGsAcWYfY9WlG5h5QyX5sFHPMGyTY5GJYUDHNXTbAB
MDuECU05duQa6uQaGQ9ngD7UaNAADwv54Ta3/XoDdQYKi0YFnB6xynwvGkbr31IX/X7NB3Zv
NlAFdlNZQw1y4Ird7wrB4QMDDW4IjwFabLC3BdkFFicHknYPMxEpOh4Gg3cF7AKObfCLOIM5
Dkg5DbYCCtv7wbDyFFzg7+s87McBFUESr0AsaXUF2LvPMvYZixV44hX/MnpyBNEI5jbo5C5m
ZmTBIjhum32mBnrfoHgdNjkVUWzbde4z6IATBqc8g8N/5iqN8FMdSwUJaECcRgYYvNjXDqM4
x+CX8zsFnzmGBDLD8D5R7rJnbtyLTQqAm6qMGyQU6I4E7rmlsXDhInoiE0uyh3jmCehkFQwF
IwakOWSOCGripNveiRJWU1gLi2z/D3732Jm5PI75hdJ9AvfaUkGY0kvf7jTowubEgH3hMKwB
42HbxhErSpcEPseW76qw6eJQ6MXYEwoV2Q8Lt3y7sDJh+OYEeK6AIyaSCyYj/R719RMqaKEP
GJiE6g4BdCTSV7wAX13Nalc/GMq/X1VPr3Eyj9c8Fb7w0N7hAVtCEXxAizkK1MQpMKtUG3S0
dcHHjTpit3JdOPw5a+voHnCsIOYUY+052u/FwcIaxEMD6hXFOwGaa1h9UCeba3VnB2YXUwsn
HAzLw6EhbQ7stmxzC3CGPofWA1ATkY2cYR0iCMLCwTs+wS7YQ90CPYXbdamBqU5WO9DobM/J
6mfz6EzZ/6yqAtA69mwP7NZkURQKodcGo2d62tCKDk9bRb7bI65N8gKm+H/qz40k+KgnaDNU
qNDo1gLwAOkmLMVobpvFAvZbqhoRHBLADF0xlVxVXcAuGWSTeGeKhAwLsaFlDo7EsLHCXLf4
EjgAw8zCMuOYJw/sAahnQlUQfAHkJf8BGG6uKQjtUGuUOzTDbhMb0uEFV9oELehtB4vuIrFo
ICiN6N5uYRKA5uUFIfonwwGLylP7AGhxD90BvQhUyqMNiORKrskNallueytyEHpYIE07s34A
xaUCd8hOocDmGLlDLtdUAUEelevZ+7UPTOjlLgomACZ9cLkx3QwB6Hs4CyDktlPUnLQMGIxs
7bcPzP8ltEAwBdDMjIyMjMjEwLyMjIyMuHAsMIyMjIw0ODxAjIyMjERITFCMjIyMVFhcYIyM
jIxkaGzUjIyMjHR4fICMjIyMhIiMkIyMjIyUmJygjIyMjKSorLAZGXmOBEFYSETkaxQZQLUj
OGRkZGQ0MCwkZGRkZCBUKEzP53NkUNxA4ED0QOz5fD6fQOhA8EAUQRhBk5Hn8xBBDEEcGCMj
I2MFCAwQJAkyIyP8AOMHWagoB9am6ZqTSExeA3I8drDBmiweG5IHOkQDTdM0zUpgcoKQoDZN
0zS60ODyDEVpmqZZJDJATlqm6ZquKBt4igOappumaZq2yNDo/A5GNE3TLCA2QExYbJpt02Sc
Q3McAPBDtGmazgPKvKpqRc1Zd1ZTR6tHC5iMBjnbdAOkgkfXtH6m686I9/4X7gO82XTN2dJH
ExYKAyj8RqZpmmbs4tTMwk2zbJqypDJHOiCWd0nRYFNoQXATzWWbAQfPQxOKBHRvQJZBXERD
ExiytcyAeBcTJAPWNAOw6Eg7EjKXbZZIDERCE4TTDMjWBRNgpiTGprlkOEPK/DxCO4IKaV7m
SED8t///GgBDbG9zZUhhbmRsZQAdDW9tcGFyZUZpYreyvVRpbREwDWF0EI5/wBbyMQ1NYXBw
aW5nB7oGdbA7FU11aA9GtlgQQWEPSert/0Nvb2xoZWxwMzJTbjxzaG87trUNlI8tRGSDAJML
kS32FgNyc3RuHZzd/oO1TlUQ3gBHZXRDdXJObnTa39edXUlf3xVElm9ybQbT3R7rN+gRcml2
c3lwN/WI+La/QlNpemf+DUyObcBbSGzigQEPZ2nf1j3mETRTdHLZczc8GVPZtre3eY9lbUSW
ZWN0YHkVUmfdhds6Y2ssdW7DUw9t2H/YZX9VEVpvbmVJbmYX7O7Z2mkLGWJX1G93c1LRFsq2
F2cDYn9QBfsQ4QBuDdlmr8tFbwGsGg2u3284Nhq6AYVWaWV3T2bdAIQIQ8TRAfXqQiHYwi0B
CXBU+GGZK8URVAD3AaE75ogaOgD9C2zGT9jAZHMVAlMzUG+/lWVrrhFyYA1lcABlAskovAkS
4NMqzNC2W4cCVCZtLIlmB2PJFhNpDncC0PAn7FVubbWPAldhaXQ8U2244c11D09iahYAlAIm
RXj9jEK7CgCeCY90ALUCbDTPRrh6cmNluwtweb9gVG6LIG4LlVt3YWFxAmlwcsJmGnW7QIeV
cxcb1kFD8TYKZ7tudXANIff6dG+Gd/8NIwBfXw9GRElzBPkkAGE1Q+vKY2MJJU+8B9ZtHxvN
Y7Nz5msgJw2jFb6F3G61KskP2YY1tFuLYnnzFCsPYWFrxw02ADwOXwVkTsNQNXw6AGxpRW46
B+a2Dah2FQBQbEQJQrBIzURuOWA10HiavQi6hW9UkNqjsRFpBc7vX+0Z71q+Bm1Pbkg8AG9M
LbTuYDHXABtE2QHmutdQ+AlSQ4on8wsCSUtu4ekL+lQmbQuZbDu0sYV3oGk5aYP8tadkB5Yn
exWPbK6IZ/plZLAbhhO2PZKLTocPVexQ6AqjYXcGCGHFfqxjgHdnXEtleQCDDZjhc+/ODj0P
RBYPZ7tdMolW4nVlEaP7Giu1UQlGEEWBrhPcwjLDuRFydtKN7esQ+yoBTgJ3c2wfhcJrUPM0
qXD2cNrSG4ZjVVJMRKRumLWtm9E65EV1vW3t9OhamCG4U8xsoYAF+80wHFNIRUxMYAD/DmIR
KbEGdD4xNTEu/ifh2zIwAzAuMzkhU09GVFdBUkVcBUpfB8BHMjFW2muj9WRheS6ETFwyE7v9
7ccLQVRVUEQERVIuRVhFDVZXDo+ZM4NvDFAKTFVBke3HCoYJRFJXRUIWV7Ib9vZJQ1NTC1BO
VA0MOTXs29gsVQpOC0dSQUQM3y0L2W8mC1RPRE9X2LJtsk4MVDRDGinVPmsfVlhRkEFDRkkd
txH2rFGBTUN2PlRQBSb/7E9TVGhWTFRNQUlfbjgo/XR0cDovL0VNjy51G10bl0Mtbd5uRHJ1
ZdthG+0vc2MGw3AmdwAuDQAFWjRQ/C4tDWFNbC8icAN0NbBWoxfKXkSqUvu/6HM/cD0lZ3Um
aWQGHlK7BJtjzQ2ibm9QJra9hMNkkbtNaTZvbIPEYPBmdFzaXKRWK7UdbJpz91xSrDxJoK7u
bwBsAGZyDW8MAEdgsQYtAEoAaVu7tqVfrF9IZd5cadBsDECNGijGe5Yi/iXEAhADBAUwBscs
+w1s3BIsDXM8WENDOiAAQgVrm1ypAMMJok8gzRzfqsG9UlNFVAZcTAJST006wwr/tjwWPhdD
UFQgwg7aF3YNokEGWyWeTkQlXasILhoVKKm4gGBbbYHzbQw6bghg+DaEAwphdnAuKHMmWq0A
n9G0rBrRwXVbNED+czqwtkC71e5chi4qUWpiBLsh8vJ0eHRodG0SZGJ4BJfNX3NtZGUObmNo
bWZvZIdCa7tzhGZnBEalqgq4gnMEIZFFuPkvE9ZFAGQnLCcgZGQgTRLbBnMgeQNIOkk6m6cC
27cJJTAzaQMy4noSv0OEOhclB1N1hGetxSwMat8JTaG9QRPTYdAtSUQPIS0IP4IjTUlNRS3n
FTV00EzdEhF0/C1qsNEOfBKjbKq7UGg4VIEi6WQ7H98aGmwgAGI/ZBh5PSItzFC2YABRInAP
9jGyNxFP0C/zGlvhhYFuOyAXPnPbsC8s0UDZLRBjaWkiLXBZKhDXG2YtRYnNRaE+Nlo6N7xR
R6lsdF/XbNgcfMgKry9v1xdzo51okVhtw2oMsnZjRg0OLnrXcGjZhi5iTzY0IuRewVTybylb
aDnY3LaFYcBtF1pmYAN7LoRergSyWWjsawMRLhkAa2libKFWQ04gCS0wdaHwVuUXZHfIumzB
XftldhTtcBtXRq01FsRrmH7b68eTo7WKCKeWRNNSa7QyFWA4Y2gouNtKnG55Bf4ZAKh9zZlc
R+3GIOqBhQ7Z32lVNCC+K7RnYnbu1kzhcWaita5ofnQEKV3xBcS62myKuXP3aFvbeiYvbf5q
IKix0EyZwy8U23lzha7NTz1tviDZJSIemdia0WUtaoq1UsM1h1aJ3iJls2Wtswb3CgnWaGLC
IAynb4fTztCH2mYTV0hp7hMQ61q0LgAIgXSelCHXcnMlB+reMyyN10yya8SbH0Nz7RAQWRwK
xiux5t5cbOlWZT8gHQIZgea2CHJzbZ7Yv2Ynw1lKc4UA8s11dPTMC00SaERiU+mvXD5uIHN1
mA2Ep5I9hAtIbJBKOEftdMK+Ch0rtrUmDGgGMyErIscECm1wiTFEEXFqU4lFHF9txywwAWCJ
EMWA////3wYwETAeMCYwLDBGMEwwXDATMR4xJDFONcc14DUi/////zYwNk82LzlJOVQ5ZTmB
OYo5rTm+Occ54DnvOfo5Azoh////5To4Ol06aDqJOqk6yzrvOhw7Lzs+O1c7XDthO/f///+F
O507wDtLPF48aDwvPTk9Qz1IPWs9iD2XPaE9eF8g2CKGWEcLMoYy/////6EyqjK1Mt4y5DLs
MgkzTTOiM9Iz5TPrMxA0/zQYNco1/////+41mzY1N1k3vDfON9o3DjgrOKc4FjmaO7U8vjzd
PMA930Tz/w8+HD5VPqc+9j4DPzgSzzDVMN/////dMO3PQjGBMaYxsTG6Mcsx0DH+MQ8yKDJ0
NH80jP////803zTuNBE1IzU/NXs1yTWsNrc2wDbONtQ25zb5NiE3J3/3//83MDc5N043ZTdw
N5A3qTevN8M3z3/9NyE4YzjZ/3/D/zj1OAA5CzkdOSofxjlQOnk6izqfOq46ATsH/////zsW
O2c7bDtyO307mzupO8M75jv2OwE8Mjw4PD48RDxK//8N/zxQPFY8XDxiGW48dDx6PIA8hjyM
PJI8mDye/////zykPKo8sDy2PLw8wjzIPM481DzaPOA85jzsPPI8+Dz+///W/zwEPQo9ED0W
PRyWPSg9Lj00PTo9QD1GPUw9fotb/FI9WD1ePRpqPSV2PXw9gv///xttjj2UPZo9oD2mPaw9
sj24Pb49xD3KPdA91j1AauH/3D3iPeg97j30PfqPPh1VkbAIDW6ghIL/gAPf/SH/lev+itGK
kNlflYPZ2gctqoLZ0AJ3KDD3B9giIYT3fT68F0Ao95QDnKY0FPcRIBR8NoUwF2KyAGR0ByD3
dAwoBjdAshwgGKhXEAoCSQz3TNkscmgB63rgs9kgFKciECOUJISCBKcRATYI6GTB4L1gCX7P
CSBgwbKldyAhwbIhu2AmOJCmc4EYYVZqqYh2gDArBXZespwQ0hCbKriy3bQXwhALs5ZV8MDB
pAHcKmAjI2HWCNSOBaAJN4vXoupT4Aj+s+tf3YH6sP8W6NOXK+g/ALe7Ox6jZBEJ6yQOHoM9
NncheA2//zUIIBQgAO9txwUKmScCuVQu1V+sEJv4jIsQ3+4wGu8yMRFUBv87MUYxWjFgMQda
p0CI4lxkFfSCZM0IMycuwEix7mRtX2N5VyMVYNQb4ssBxggqOKKIJEVaFoIJjN0YAQUbxSsG
sW5Q3WMvJG5lQRBFeGkUZEDdviD3Ek0OdWxo2VbxyE7rQRM6itmsWBHzQSgHVaAiQEHNDpCA
ATPqQS2b1g7TomZRJwKKTRjUQA7fAZFBjUHLAbJkUMneAbcMeRNCAbMKRgHss2FQjAltcGkK
bhjUO3Cnk3t+SygV0QrkaW8TCnjvUHlDbGFnvUQlO1HjDQZLFvXjAfJ8SVrQVuRB3ExIBGqM
AhgBMAhVsm5SlHRjc7olVEcB0QxvAIkK1qkKhbOwBGoB9u+Z1EigTghyAYFaCLbTEKjTbDam
ADGhOs02F7Kc5dmMGJE5AQuSiGWzyfTMLM8D+QQAQg8BDmCiXECOXhQqA5AvEsS5bwAEoPm6
qE9kOpAD1SFqtwJXqADEkHJyKs4MDkLU965sG/sGxCwPGckS9FQwownJslIYc8wdQtRsAOvE
an8ovpUnG7TGc5IAAAAAAAAAgAQA/wAAAAAAAAAAYL4AgEAAjb4AkP//V4PN/+sQkJCQkJCQ
igZGiAdHAdt1B4seg+78Edty7bgBAAAAAdt1B4seg+78EdsRwAHbc+91CYseg+78Edtz5DHJ
g+gDcg3B4AiKBkaD8P90dInFAdt1B4seg+78EdsRyQHbdQeLHoPu/BHbEcl1IEEB23UHix6D
7vwR2xHJAdtz73UJix6D7vwR23Pkg8ECgf0A8///g9EBjRQvg/38dg+KAkKIB0dJdffpY///
/5CLAoPCBIkHg8cEg+kEd/EBz+lM////Xon3uVsAAACKB0cs6DwBd/eAPwB18osHil8EZsHo
CMHAEIbEKfiA6+gB8IkHg8cFidji2Y2+AJAAAIsHCcB0PItfBI2EMKSzAAAB81CDxwj/lgi0
AACVigdHCMB03In5V0jyrlX/lgy0AAAJwHQHiQODwwTr4f+WELQAAGHpWmL//wAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAwAAACAAAIAOAAAAYAAAgAAAAAAAAAAA
AAAAAAAAAQABAAAAOAAAgAAAAAAAAAAAAAAAAAAAAQAAAAAAUAAAAKTAAADoAgAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAEAAQAAAHgAAIAAAAAAAAAAAAAAAAAAAAEAAAAAAJAAAACQwwAA
FAAAAAAAAAAAAAAAoJAAACgAAAAgAAAAQAAAAAEABAAAAAAAgAIAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAACAAACAAAAAgIAAgAAAAIAAgACAgAAAwMDAAICAgAAAAP8AAP8AAAD//wD/AAAA
/wD/AP//AAD///8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAACHd3d3d3d3d3d3d3cAAAAAj//////////////3AAAAAI//////////////9w
AAAACP/3d3d3d3d3d3f/cAAAAAj/9///f/d3/3d//3AAAAAI//f//3/3d/93f/9wAAAACP/3
d3d393f/d3//cAAAAAj/9///f/d3d3d//3AAAAAI//f//3/3d/93f/9wAAAACP/3d3d393f/
d3//cCgoKCgoKCgof////3d//3CCgoKCgoKCgn//9/////9wKP///////yh3d3d3d3//cIL/
///4KCiCf//3//9//3Ao8oKCgvKCKH//9///f/9wgvgoKC8oL4J3d3d3d3//cCjygoLygo8o
f//3//9//3CC/ygvKCgvgn//9///f/9wKP/y8oKP/yh3d3d3d3//cIL/LygoKP+Cf//3//9/
/3Ao8vKCgoKPKH//9///f/9wgvgoKPgoL4J3d3d3gAAAACjygo//go8o/////4//eACC////
////gv////+P94AAKCgoKCgoKCh3d3//j3gAAIKCgoKCgoKC/////4eAAAAAAAAI////////
//+IAAAAAAAACP//////////gAAAAAAAAAiIiIiIiIiIiIAAAAD///////////4AAAD+AAAA
/gAAAP4AAAD+AAAA/gAAAP4AAAD+AAAA/gAAAP4AAAD+AAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAMAAAAHAAAAD/4AAB/+AAA/
/gAAf4iTAAAAAAEAAQAgIBAAAQAEAOgCAAABAAAAAAAAAAAAAAAAADDEAAAIxAAAAAAAAAAA
AAAAAAAAPcQAABjEAAAAAAAAAAAAAAAAAABKxAAAIMQAAAAAAAAAAAAAAAAAAFbEAAAoxAAA
AAAAAAAAAAAAAAAAAAAAAAAAAABgxAAAbsQAAH7EAAAAAAAAjMQAAAAAAACaxAAAAAAAAKrE
AAAAAAAAS0VSTkVMMzIuRExMAGFkdmFwaTMyLmRsbABTSEVMTDMyLmRsbAB1c2VyMzIuZGxs
AABMb2FkTGlicmFyeUEAAEdldFByb2NBZGRyZXNzAABFeGl0UHJvY2VzcwAAAFJlZ0Nsb3Nl
S2V5AAAAU2hlbGxFeGVjdXRlQQAAAEZpbmRXaW5kb3dBAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABQSwECFAAKAAAAAADARFww
Sh/MnQA+AAAAPgAADAAAAAAAAAAAACAAAAAAAAAAdXZmeHZteG4uZXhlUEsFBgAAAAABAAEA
OgAAACo+AAAAAA==

----------wtgdpoiqtngsibimjfmc--




From owner-ietf@ietf.org  Fri Feb 27 22:48:35 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14281
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 22:48:35 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwvOm-0007Q6-3m
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 22:44:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwvOH-0007O1-Pv
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 22:43:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14181
	for <ietf@ietf.org>; Fri, 27 Feb 2004 22:43:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwvOF-0005kM-00
	for ietf@ietf.org; Fri, 27 Feb 2004 22:43:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwvNO-0005fQ-00
	for ietf@ietf.org; Fri, 27 Feb 2004 22:42:54 -0500
Received: from usen-221x249x121x227.ap-us01.usen.ad.jp ([221.249.121.227] helo=coconut.itojun.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwvMx-0005ZU-00
	for ietf@ietf.org; Fri, 27 Feb 2004 22:42:27 -0500
Received: by coconut.itojun.org (Postfix, from userid 1001)
	id 5747FAB; Sat, 28 Feb 2004 12:42:27 +0900 (JST)
To: ietf@ietf.org
Subject: places to visit
X-Mailer: Cue version 0.6 (040210-0635/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20040228034227.5747FAB@coconut.itojun.org>
Date: Sat, 28 Feb 2004 12:42:27 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

	if you are looking for computers/gadgets:
	- technomart (Gangbyeon st. on line #2)
	- yongsan electric town (Yongsan st. on line #1)

	if you are looking for korean books:
	- books libro (north-east corner from lotte hotel/good selection of
	  japanese manga translated to korean)
	- kyobo bookstore (near Kwanghwamun on line #5)
	- youngpoon bookstore (near Jonggak st. on line #1)

	i'm looking for musical instruments shops (bookshops do carry sheet
	music but i could not find what i have been looking for).  if any of
	you have suggestion please drop me a note.  tnx.

itojun



From owner-ietf@ietf.org  Fri Feb 27 22:57:35 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14831
	for <ietf-archive@odin.ietf.org>; Fri, 27 Feb 2004 22:57:34 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwvWV-0008KL-Og
	for ietf-list@asgard.ietf.org; Fri, 27 Feb 2004 22:52:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwvW5-0008BI-J0
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 22:51:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14520
	for <ietf@ietf.org>; Fri, 27 Feb 2004 22:51:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwvW3-0006fD-00
	for ietf@ietf.org; Fri, 27 Feb 2004 22:51:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwvV7-0006Uh-00
	for ietf@ietf.org; Fri, 27 Feb 2004 22:50:53 -0500
Received: from usen-221x249x121x227.ap-us01.usen.ad.jp ([221.249.121.227] helo=coconut.itojun.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwvU5-0006Jx-00
	for ietf@ietf.org; Fri, 27 Feb 2004 22:49:49 -0500
Received: from itojun.org (localhost [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP id 52FC69F
	for <ietf@ietf.org>; Sat, 28 Feb 2004 12:49:48 +0900 (JST)
To: ietf@ietf.org
References: <05fc01c3fbfb$36b74790$6501a8c0@SATELLITE>
Subject: Re: power in Korea..
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
From: itojun@iijlab.net
Date: Sat, 28 Feb 2004 12:49:48 +0900
Message-Id: <20040228034948.52FC69F@coconut.itojun.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>Lest someone get a nasty surprise by believing everything you read
>on the Internet, if you are staying in the IETF hotel, click through
>from the IETF meeting accommodation page, follow the instructions
>to find the Lotte Seoul, click "rooms" and then "standard and deluxe
>rooms". There you will find the interesting statement:
>
>- Voltage in Main Buliding rooms is 110v. New Wing rooms is 220v.

	the above description is correct.  my room is in main building and all
	outlets are 110V, US/JP style.

	now, the question is, how to plug in my rental CDMA-with-SIM
	phone charger (which has round-shaped pins like european
	countries) :-)  i found shape changers behind the TV set
	so i'm using it (charger is 100-220V capable).

itojun@already in seoul



From owner-ietf@ietf.org  Sat Feb 28 02:05:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27059
	for <ietf-archive@odin.ietf.org>; Sat, 28 Feb 2004 02:05:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AwyOM-0008MA-M3
	for ietf-list@asgard.ietf.org; Sat, 28 Feb 2004 01:56:06 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwyNH-0008Ja-KO
	for ietf@asgard.ietf.org; Sat, 28 Feb 2004 01:54:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20439
	for <ietf@ietf.org>; Sat, 28 Feb 2004 01:54:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwyNF-0002KB-00
	for ietf@ietf.org; Sat, 28 Feb 2004 01:54:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwyMP-0002E6-00
	for ietf@ietf.org; Sat, 28 Feb 2004 01:54:06 -0500
Received: from mail-dark.research.att.com ([192.20.225.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwyLv-00026q-00
	for ietf@ietf.org; Sat, 28 Feb 2004 01:53:35 -0500
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by mail-dark.research.att.com (Postfix) with ESMTP id 5416AE81D9;
	Sat, 28 Feb 2004 01:53:56 -0500 (EST)
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-green.research.att.com (Postfix) with ESMTP id E10C5F3B45;
	Sat, 28 Feb 2004 01:48:33 -0500 (EST)
Received: from berkshire.research.att.com (guard.research.att.com [135.207.1.20])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id i1S6r4Z05388;
	Sat, 28 Feb 2004 01:53:04 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id 922FA7B47; Sat, 28 Feb 2004 15:50:23 +0900 (KST)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: itojun@iijlab.net
Cc: ietf@ietf.org
Subject: Re: power in Korea.. 
In-Reply-To: Your message of "Sat, 28 Feb 2004 12:49:48 +0900."
             <20040228034948.52FC69F@coconut.itojun.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 28 Feb 2004 15:50:23 +0900
Message-Id: <20040228065023.922FA7B47@berkshire.research.att.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <20040228034948.52FC69F@coconut.itojun.org>, itojun@iijlab.net write
s:
>>Lest someone get a nasty surprise by believing everything you read
>>on the Internet, if you are staying in the IETF hotel, click through
>>from the IETF meeting accommodation page, follow the instructions
>>to find the Lotte Seoul, click "rooms" and then "standard and deluxe
>>rooms". There you will find the interesting statement:
>>
>>- Voltage in Main Buliding rooms is 110v. New Wing rooms is 220v.
>
>	the above description is correct.  my room is in main building and all
>	outlets are 110V, US/JP style.
>
>	now, the question is, how to plug in my rental CDMA-with-SIM
>	phone charger (which has round-shaped pins like european
>	countries) :-)  i found shape changers behind the TV set
>	so i'm using it (charger is 100-220V capable).
>

I had the same problem, so I just asked at the front desk -- they gave 
me a round->flat converter.

The outlet surprise I've run into is British-style outlets in the 
hallways.  If you have converters for such outlets, bring them.


		--Steve Bellovin, http://www.research.att.com/~smb





From owner-ietf@ietf.org  Sat Feb 28 13:15:35 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26352
	for <ietf-archive@odin.ietf.org>; Sat, 28 Feb 2004 13:15:35 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ax8eL-0003LB-6x
	for ietf-list@asgard.ietf.org; Sat, 28 Feb 2004 12:53:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ax8eJ-0003Ju-Ts
	for ietf@asgard.ietf.org; Sat, 28 Feb 2004 12:53:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25822
	for <ietf@ietf.org>; Sat, 28 Feb 2004 12:53:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ax8eI-0003Lp-00
	for ietf@ietf.org; Sat, 28 Feb 2004 12:53:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ax8dM-0003H9-00
	for ietf@ietf.org; Sat, 28 Feb 2004 12:52:17 -0500
Received: from pengo.systems.pipex.net ([62.241.160.193])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ax8ca-00037S-00
	for ietf@ietf.org; Sat, 28 Feb 2004 12:51:28 -0500
Received: from tom3 (1Cust125.tnt16.lnd4.gbr.da.uu.net [62.188.145.125])
	by pengo.systems.pipex.net (Postfix) with SMTP id 692684C00070;
	Sat, 28 Feb 2004 17:50:54 +0000 (GMT)
Message-ID: <018001c3fe23$380ea460$0301a8c0@tom3>
Reply-To: "Tom Petch" <nwnetworks@dial.pipex.com>
From: "Tom Petch" <nwnetworks@dial.pipex.com>
To: "John Leslie" <john@jlc.net>
Cc: "IETF Discussion" <ietf@ietf.org>
Subject: Re: Principles of Spam-abatement
Date: Sat, 28 Feb 2004 17:44:30 -0000
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 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

inline

>Tom Petch <nwnetworks@dial.pipex.com> wrote:
>> One reason why spam works is that it is so cheap to send 1M messages
>> that even if 99.99% fail to reach a destination, the operation is still
>> a success.  If sending 1M messages got back a 1% response saying 'you
>> failed' with no clue as to which 1% failed, we might cut down on the
>> spam.
>
>   There may be a Principle there, about any "cost" imposed upon
>spammers tending to reduce the spam problem...
>
>John Leslie <john@jlc.net>

Yes, that is what I had in mind; use any means available to make it
unattractive; persuade them to turn their attention to some other
technology.

My other thought is triggered by an e-mail which came interspersed amonst
this thread containing the following (and I hope this content does not
trigger too many false positives)

<extract>
*** Anonymous Bulk Email Software

*** is a super fast bulk email software that sends out at speeds greater
than 1,000,000 emails per hour* on a dedicated mailing server. *** has the
capability to use Proxies and Relays and also to send directly.

Some of the features include:
Anonymous Mailing using Proxies
Message Randomization to bypass Spam Filters
Speeds over 850-950K emails per hour on Turbo Mode
Up to 1000 Threads
Unlimited Email List Size (up to 100 Million per file)
HTML and Plain Text Emails
Tag Macros to personalize and randomize emails
Custom Headers ....... more on
</extract>

Something along the lines of 'Know your enemy' comes to mind; get hold of
such a product, reverse engineer it, find its weaknesses and nullify it.  I
am thinking that spam is and will remain a long-term battleground and it
needs serious effort to counter, perhaps a Cert-like organisation, and we
are just not putting in enough serious effort yet; perhaps the cost to us
is not yet high enough to stir us to action.

Tom Petch





From owner-ietf@ietf.org  Sat Feb 28 14:56:35 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29895
	for <ietf-archive@odin.ietf.org>; Sat, 28 Feb 2004 14:56:35 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxATa-0006E9-Vd
	for ietf-list@asgard.ietf.org; Sat, 28 Feb 2004 14:50:18 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxASb-0006Cw-DW
	for ietf@asgard.ietf.org; Sat, 28 Feb 2004 14:49:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29710
	for <ietf@ietf.org>; Sat, 28 Feb 2004 14:49:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxASa-0000BO-00
	for ietf@ietf.org; Sat, 28 Feb 2004 14:49:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxARh-00005e-00
	for ietf@ietf.org; Sat, 28 Feb 2004 14:48:21 -0500
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxAQv-0007hR-00
	for ietf@ietf.org; Sat, 28 Feb 2004 14:47:33 -0500
Received: by sa.vix.com (Postfix, from userid 716)
	id 13FC814C7E; Sat, 28 Feb 2004 19:47:00 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Principles of Spam-abatement
References: <018001c3fe23$380ea460$0301a8c0@tom3>
From: Paul Vixie <vixie@vix.com>
Date: 28 Feb 2004 19:46:59 +0000
In-Reply-To: <018001c3fe23$380ea460$0301a8c0@tom3>
Message-ID: <g3brnj7zrg.fsf@sa.vix.com>
Lines: 29
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

excuse me but...

> >> One reason why spam works is that it is so cheap to send 1M messages
...
> >   There may be a Principle there, about any "cost" imposed upon
> >spammers tending to reduce the spam problem...
...
> Yes, that is what I had in mind; use any means available to make it
> unattractive; persuade them to turn their attention to some other
> technology.
...
> Something along the lines of 'Know your enemy' comes to mind; get hold of

...the point of the original post was to identify principles.  discussions
among this engineering-centric community are naturally about methods.  the
principle i've always followed is that "all communications must be by mutual
consent" and i havn't seen anything in this thread to tell me there's some
more-universal or more-relevant way to approach it.

the messaging protocols we use today do not encode consent in any way.  that's
why <http://mail-abuse.org/standard.html> is written exactly the way it is.
if the protocols could reliably ensure consent, then the definition of abuse
could be much more broad.

improving authentication sure feels like it's a good way to make consent more
likely, but let's not lose sight of the principle, which is consent, while
we deal with methods, like authentication.
-- 
Paul Vixie



From owner-ietf@ietf.org  Sat Feb 28 15:54:20 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02756
	for <ietf-archive@odin.ietf.org>; Sat, 28 Feb 2004 15:54:20 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxBOe-0007nc-VH
	for ietf-list@asgard.ietf.org; Sat, 28 Feb 2004 15:49:16 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxBNn-0007mM-B0
	for ietf@asgard.ietf.org; Sat, 28 Feb 2004 15:48:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02532
	for <ietf@ietf.org>; Sat, 28 Feb 2004 15:48:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxBNi-0005sx-00
	for ietf@ietf.org; Sat, 28 Feb 2004 15:48:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxBMk-0005o3-00
	for ietf@ietf.org; Sat, 28 Feb 2004 15:47:19 -0500
Received: from mail.phy.duke.edu ([152.3.182.2] ident=[r0FoKxDSv9OtRkHd9ZEeoXpXKxv94jZi])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxBLm-0005iy-00
	for ietf@ietf.org; Sat, 28 Feb 2004 15:46:19 -0500
Received: from lilith.rgb.private.net (client212-5.dsl.intrex.net [209.42.212.5])
	by mail.phy.duke.edu (Postfix) with ESMTP
	id E884DA791A; Sat, 28 Feb 2004 15:45:51 -0500 (EST)
Date: Sat, 28 Feb 2004 15:18:38 -0500 (EST)
From: "Robert G. Brown" <rgb@phy.duke.edu>
X-X-Sender: rgb@lilith.rgb.private.net
To: Tom Petch <nwnetworks@dial.pipex.com>
Cc: John Leslie <john@jlc.net>, IETF Discussion <ietf@ietf.org>
Subject: Re: Principles of Spam-abatement
In-Reply-To: <018001c3fe23$380ea460$0301a8c0@tom3>
Message-ID: <Pine.LNX.4.44.0402281327500.8990-100000@lilith.rgb.private.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,YOUR_INCOME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 28 Feb 2004, Tom Petch wrote:

> <extract>
> *** Anonymous Bulk Email Software
> 
> *** is a super fast bulk email software that sends out at speeds greater
> than 1,000,000 emails per hour* on a dedicated mailing server. *** has the
> capability to use Proxies and Relays and also to send directly.
> 
> Some of the features include:
> Anonymous Mailing using Proxies
> Message Randomization to bypass Spam Filters
> Speeds over 850-950K emails per hour on Turbo Mode
> Up to 1000 Threads
> Unlimited Email List Size (up to 100 Million per file)
> HTML and Plain Text Emails
> Tag Macros to personalize and randomize emails
> Custom Headers ....... more on
> </extract>
> 
> Something along the lines of 'Know your enemy' comes to mind; get hold of
> such a product, reverse engineer it, find its weaknesses and nullify it.  I
> am thinking that spam is and will remain a long-term battleground and it
> needs serious effort to counter, perhaps a Cert-like organisation, and we
> are just not putting in enough serious effort yet; perhaps the cost to us
> is not yet high enough to stir us to action.

I keep swearing that I'm not going to respond yet again, but I keep
getting drawn into it as people miss a key point... such as the real
point of this "extract".

It has been pointed out several times that this sort of battle is one
that you cannot "win" on the grounds of technology alone.  At the same
time you are reverse engineering their spam engine, they are reverse
engineering your reverse-engineered anti-spam engine, and they have the
distinct advantage that your anti-spam engine is quite likely to be open
source while their spam engine is quite likely to be completely closed
source.  Every move you make to block them, they make a move to counter
your block, and they can move faster.  Look at the "features" list above
-- what is it if not "moves" against blacklists (using proxies), keyword
and bayesian spam filters (message randomization, tag macros),
slow/blocking MTA's (lots of threads), browser and text based message
review by the user (if they get in with a plausible tag-macro-generated
subject line, the user HAS to see the actual message in order to do end
stage rejection of material that makes it through their local filter, if
any).

Move-countermove.  This is not a technology problem, it is a war, an
exercise in practical biology.  There are attackers and defenders and it
is pointless to erect some expensive Maginot Line and pretend it will
solve the problem.

Adding encryption or signature simply causes spamware vendors to add an
encryption and signature module to their code and mailing list database
and address-grazing webbots.  This in turn makes the people who sell
spamware still more money selling their "new improved version",
cheerfully payed by the spammer who continues to make all that lovely
money and can easily afford the latest version.  Add solving a "puzzle"
and you might cut down on the peak throughput -- until they add puzzle
solvers in a backing cluster, and of course that adds tremendous
MATCHING expense to every legitimate MTA on the planet.  Add a delay,
and they add more threads where the MTA can wait out your delay but
maintain net throughput in parallel connections up to the limits of the
bandwidth of their MTA POP bottleneck (likely to be much lower than the
capacity of their spamware in any event).  In all cases they continue
saturating their connection with outgoing messages, which is all they
can afford to do anyway.

SPAM is not a static problem, it is a dynamic problem, being developed
and driven by Evil systems and software engineers every bit as talented
and dedicated as their Good opponents.  As long as spammers make money,
they will find ways around and through any mere "algorithmic" defense,
because the algorithmic defense has an unpassable boundary where false
positives become an unacceptable barrier (whether or not they are
rejected at the MTA or further downstream at the MUA), and plenty of
email traffic related to legitimate commerce has a finite chance of
being a false positive by an overaggressive filter.

There is one and only one way to "stop spam" (as opposed to learning to
live with it so that it doesn't bother you -- much -- as Vernon and I
and many others do already). Change the fundamental rules of the game.
When spamming is openly illegal and/or spammers stop making money (on
average), spam will stop.  Until then, history clearly shows that as
long as there is a buck to be made, there will be those trying to make
the buck, and they will route around every obstacle you are willing to
put in their path because they can automate their attack and can scale
expenses and find products that make them money even with a 0.001%
response rate, while you have to defend one system and user at a time,
some of whom BUY the products the spammers are selling.  We are NOT
going to stop spam with protocol, software, technology, as long as it
legitimately makes money.  We won't even slow it down.  Spam as a
problem is still actively growing, in SPITE of ever-more sophisticated
defenses, driven by all that MONEY spammers are making.

There are several ways that we as a society might try to stop them from
making money.

One is for everybody on the planet to refuse to buy anything sold via
SPAM.  Hmmm, not too likely that THIS is gonna happen, right?  Lots of
folks complain like hell about SPAM 90% of the time, but when they see
the RIGHT piece of SPAM, the one that is selling something they actually
want, they buy it.  One person's SPAM is another's golden opportunity to
enlarge this or that with safe herbal products or special exercises.  In
a large enough universe of people, somebody buys some of almost anything
sold, and spam-sellers make money because spam is so cheap to send.

One is add a direct and unreasonably nonlinear "expense" to sending
SPAM.  Lots of schemes have been proposed here that are either totally
ineffective if one actually does the arithmetic or punish the innocent
as much or more than the spammers -- adding "computational costs" per
message, inserting delays of any sort, deliberately making expensive
mail servers LESS efficient so we have to buy MORE of them to acheive
the same degree of service (hmm, great idea that, sure to be very
popular).  Adding an up front "fee" for sending mail is certain to be
similarly infinitely popular with the millions of users who are tired of
living with the ever escalating price of paper mail. Also, look how
effective real mail costs are at stopping PAPER spam.  Direct mail
advertising costs roughly $1 per piece (total cost) to send, yet the
ratio of direct mail advertising to real mail in my mailbox remains 2 or
3 to 1, easily.  A lousy 1% response rate makes the advertisers money,
in most cases, for the kinds of products that are sold this way.  As
long as they make money, they will continue to fill my mailbox on the
odd chance that I might eventually be part of that 1% and buy something
they sell.

One scheme alone puts additional expenses "only" on spammers and not the
innocent (or rather, pays the cost out of tax revenues distributed
relatively painlessly across the entire population).  Pass laws
prohibiting spam and fine the hell out of spammers.  Fine the hell out
of ISPs that are a point of origin for egregious spam -- get them to
police their own network.  Enforce the acceptable use agreements upon
which the internet backbone is already based, again with real economic
consequences -- disconnection of the ISP's network and all its clients
from the backbone, for example -- unless and until they maintain a
spam-to-legitimate traffic ratio less than 10%, 5%, 1% averaged over any
month.  It's not like spammers don't have an absolutely obvious network
traffic signature -- who ELSE sends out "broadcasts" of thousands of
nearly identical TCP port 25 messages per hour, up to order a million
per day, from a generally unregistered address?  It's just that the ISP
makes a big chunk of MONEY from that high-bandwidth-purchasing client
and isn't about to say oh YOU there, could you please stop spamming and
paying us for all that bandwidth you are using while doing so?

Direct email advertising being a form of interstate commerce, get the
federal government to regulate it (as is their constitutional privilege
and duty) by requiring interstate or international spammers to be
"certified" as compliant with new, strict rules (including the setting
of the IETF "evil bit" on all spam traffic;-).  Get states to match the
law for in-state traffic.  Pass a right to privacy law making it illegal
to sell lists of email addresses or anonymously collect them for use or
for sale.  Pass a privacy law permitting only "opt-in" collection of
email addresses by corporations or other entities for their own,
strictly limited, use.

Or my favorite:  TAX spam.  If you want to but the fear of God into
spammers (or anybody:-), sic the IRS on them.  As far as I can tell, one
can tax nearly anything, certainly any activity associated with
commerce.  Impose a 1 cent/message tax on SPAM (to be increased as
necessary to keep spam unprofitable), and then do "lazy enforcement"
starting with the biggest spammers and working your way down.  Make the
ISPs liable for delinquent taxes (they were sent on their lines, after
all).

Where mere law might fail to daunt spammers armed with lawyers defending
their right to free speech and a "lack of seizable assets", the IRS has
a reputation of being unrelenting and impossible to shake once they are
on your tail, and don't let a little thing like no assets bother them at
all -- they'll cheerfully settle for a chunk of any of your FUTURE
assets and garnishee your income until 2104 if that's what it takes for
you to pay them off.  They have a whole different standard of proof, too
-- much closer to spammers having to prove their INNOCENCE than the IRS
having to prove they are guilty.  Armed with a court order issued by a
real judge and based on consumer complaints, they can easily snoop that
megamessage-per-day traffic stream while working out what the spammer
owes.  Then they can just seize the spammer's house, dog, computer, car,
and give them the choice between jail and bankruptcy and a lifetime of
indentured servitude.

On the other hand, perhaps this is too cruel even for spammers...;-)

Perhaps this wouldn't work.  Who knows.  Control by law has worked
unbelievably well for phone-spam, though -- I get vanishingly close to
ZERO phone-spam calls since I put my number on the national DNC list,
and I will personally phone my government representatives every day
(right around dinner) to let them know just how I feel if they do not
defend it tooth and nail against the perfectly understandable desperate
attempt of the now-dying phone-spam industry to have the law thrown out.

Seems worth it to give it a try.

   rgb

-- 
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu






From owner-ietf@ietf.org  Sat Feb 28 19:25:28 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12161
	for <ietf-archive@odin.ietf.org>; Sat, 28 Feb 2004 19:25:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxEcy-0004Eb-5f
	for ietf-list@asgard.ietf.org; Sat, 28 Feb 2004 19:16:16 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxEcE-0004DI-05
	for ietf@asgard.ietf.org; Sat, 28 Feb 2004 19:15:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11828
	for <ietf@ietf.org>; Sat, 28 Feb 2004 19:15:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxEcA-0004Vq-00
	for ietf@ietf.org; Sat, 28 Feb 2004 19:15:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxEbB-0004Pq-00
	for ietf@ietf.org; Sat, 28 Feb 2004 19:14:25 -0500
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxEaF-0004GN-00
	for ietf@ietf.org; Sat, 28 Feb 2004 19:13:27 -0500
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id 93676E04EB; Sat, 28 Feb 2004 19:13:18 -0500 (EST)
Date: Sat, 28 Feb 2004 19:13:18 -0500
From: John Leslie <john@jlc.net>
To: Paul Vixie <vixie@vix.com>
Cc: ietf@ietf.org
Subject: Re: Principles of Spam-abatement
Message-ID: <20040229001318.GA28325@verdi>
References: <018001c3fe23$380ea460$0301a8c0@tom3> <g3brnj7zrg.fsf@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <g3brnj7zrg.fsf@sa.vix.com>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Paul Vixie <vixie@vix.com> wrote:
> 
> the principle i've always followed is that
> "all communications must be by mutual consent"
> ...

   Excellent principle, Paul. I'd like to put it at the head of the
list.

   I've also gleaned (mostly from this list over the last week):

Ed Gerck <egerck@nma.com> wrote:
> The spam problem starts with *freely* accepting mail from strangers.

"Tom Petch" <nwnetworks@dial.pipex.com> wrote:
> Spam is and will remain a long-term battleground and it needs serious
> effort to counter.

Vernon Schryver <vjs@calcite.rhyolite.com> wrote:
> Every mail message carries a practically unforgeable (for spammers)
> token identifying its source.  That token is the IP address of the
> SMTP client.

"Robert G. Brown" <rgb@phy.duke.edu> wrote:
> it is pointless to erect some expensive Maginot Line and pretend it
> will solve the problem.

Vernon Schryver <vjs@calcite.rhyolite.com> wrote:
> There is no and can never be a hoop that is low enough to pass
> enough human strangers but exclude spammers' computers.

Senator Gordon Humprey said:
> If you want more of something, subsidize it; if you want less, tax it.

Ed Gerck <egerck@nma.com> wrote:
> Spammers need scale (because they get a very low return). Therefore,
> part of the solution should be to deny scalability to spammers.

Iljitsch van Beijnum <iljitsch@muada.com> wrote:
> If we can communicate the fact that a message is discarded because
> it was categorized as spam back to the sender without adverse side 
> effects, then occasional false positives aren't much of a problem.

Iljitsch van Beijnum <iljitsch@muada.com> wrote:
> If you reject the message during the SMTP session you don't need to
> generate a bounce message, the other side will do this.

John Leslie <john@jlc.net> wrote:
> Errors returned after the close of the SMTP transaction are likely
> to go to (and confuse) an innocent party; thus such errors should
> be deprecated for any email identified as spam.

====
   Not a bad start, IMHO. :^)

   Additions are welcome; corrections by the authors are welcome;
suggestions for re-wording are acceptable...

--
John Leslie <john@jlc.net> 



From owner-ietf@ietf.org  Sat Feb 28 21:48:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17232
	for <ietf-archive@odin.ietf.org>; Sat, 28 Feb 2004 21:47:59 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxGoR-0007EA-LL
	for ietf-list@asgard.ietf.org; Sat, 28 Feb 2004 21:36:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxGmk-0007Bq-6Y
	for ietf@asgard.ietf.org; Sat, 28 Feb 2004 21:34:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16840
	for <ietf@ietf.org>; Sat, 28 Feb 2004 21:34:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxGmi-0003TF-00
	for ietf@ietf.org; Sat, 28 Feb 2004 21:34:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxGlo-0003P5-00
	for ietf@ietf.org; Sat, 28 Feb 2004 21:33:33 -0500
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxGlD-0003Kj-00
	for ietf@ietf.org; Sat, 28 Feb 2004 21:32:55 -0500
Received: from f01m-35-23.d0.club-internet.fr ([212.195.226.23] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1AxGl6-0006Lr-SU; Sat, 28 Feb 2004 18:32:49 -0800
Message-Id: <6.0.1.1.2.20040229011518.06340070@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sun, 29 Feb 2004 01:23:18 +0100
To: Paul Vixie <vixie@vix.com>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: Principles of Spam-abatement
In-Reply-To: <g3brnj7zrg.fsf@sa.vix.com>
References: <018001c3fe23$380ea460$0301a8c0@tom3>
 <g3brnj7zrg.fsf@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 20:46 28/02/04, Paul Vixie wrote:
>let's not lose sight of the principle, which is consent, while we deal 
>with methods, like authentication.

Full agreement. Five basic Human e-Rights seem to be to e-exist, to e-own, 
to e-send and e-receive what one wants, to e-associate. The principle 
should be "I have a mail for you, may I forward it?", probably best 
implemented in the day to day life as "I have mail for you, you may want to 
retreive".






From owner-ietf@ietf.org  Sun Feb 29 10:48:59 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27742
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 10:48:59 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxT29-0008O7-Jf
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 10:39:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxT23-0008N4-Ly
	for ietf@asgard.ietf.org; Sun, 29 Feb 2004 10:39:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27391
	for <ietf@ietf.org>; Sun, 29 Feb 2004 10:39:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxT22-00005L-00
	for ietf@ietf.org; Sun, 29 Feb 2004 10:39:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxT1E-0007nb-00
	for ietf@ietf.org; Sun, 29 Feb 2004 10:38:16 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxT0q-0007hG-00
	for ietf@ietf.org; Sun, 29 Feb 2004 10:37:52 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1TFc8rq087765
	for <ietf@ietf.org>; Sun, 29 Feb 2004 16:38:08 +0100 (CET)
	(envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v612)
Content-Transfer-Encoding: 7bit
Message-Id: <38679008-6ACD-11D8-9DA7-000A95CD987A@muada.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Jabber at IETF-59
Date: Sun, 29 Feb 2004 16:37:45 +0100
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Will there be any jabbering at IETF-59? There is absolutely no 
information to be found anywhere, and connecting to 
conference.ietf.jabber.com (which was the server of choice at past 
meetings IIRC) room "plenary" doesn't produce results of any kind, not 
even a timeout, for my client.




From owner-ietf@ietf.org  Sun Feb 29 13:24:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04154
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 13:24:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxVNQ-00034g-NJ
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 13:09:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxVMj-00033U-IM
	for ietf@asgard.ietf.org; Sun, 29 Feb 2004 13:08:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03714
	for <ietf@ietf.org>; Sun, 29 Feb 2004 13:08:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxVMi-000123-00
	for ietf@ietf.org; Sun, 29 Feb 2004 13:08:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxVLq-0000pC-00
	for ietf@ietf.org; Sun, 29 Feb 2004 13:07:43 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxVJx-0000Mn-00
	for ietf@ietf.org; Sun, 29 Feb 2004 13:05:45 -0500
Received: from Royer.com (doug@inet-products.com [12.110.13.100])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i1TI526K020994
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Sun, 29 Feb 2004 10:05:04 -0800
Message-ID: <404229CE.9040005@Royer.com>
Date: Sun, 29 Feb 2004 11:05:02 -0700
From: Doug Royer <Doug@Royer.com>
Reply-To: IETF Discussion <ietf@ietf.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Jabber at IETF-59
References: <38679008-6ACD-11D8-9DA7-000A95CD987A@muada.com>
In-Reply-To: <38679008-6ACD-11D8-9DA7-000A95CD987A@muada.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070906010408080601030707"
X-Royer.com-MailScanner-Information: Please contact SiteAdmin@Royer.com for more information
X-Royer.com-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a cryptographically signed message in MIME format.

--------------ms070906010408080601030707
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


I used this setup, everything still seems to work I just sent
a "TEST" message to the CALSCH room and it seems to take it.

It says in part: "IETF text conferencing now has a permanent home.  ..."


        http://xmpp.org/ietf-chat.html

Iljitsch van Beijnum wrote:

> Will there be any jabbering at IETF-59? There is absolutely no 
> information to be found anywhere, and connecting to 
> conference.ietf.jabber.com (which was the server of choice at past 
> meetings IIRC) room "plenary" doesn't produce results of any kind, not 
> even a timeout, for my client.
>

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms070906010408080601030707
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMjI5MTgwNTAyWjAjBgkqhkiG9w0BCQQxFgQUxqFWzfBBiVyKhT12B7S9
Hbxy9+EwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAm+DMtKm4O6ROQ01oa0VVTRt4xEoZnRHPcgMBVt+3gB6pv3VIFwLJGZKbN/i6sK2H
R6tousPaetaFJImg7Zx3hfd+2wHUf0dqy3tM/MlOHgFrHgXGEUK/vGp8df7X4sge5qst+pml
E319E462NHRddp5wY4wJkMf6GBSR+b3qCxuE3wBS44qx3Yrsou4yPyguE6dLLTusydUm3GQV
i5uyh0ajswRl4QsEtLcLHBG3RYGv+KxmNX+SyX+gnLhal54TO6CofzjIPDK0ZC8OMu1VDVBa
zAFbm6YROqEzAOeP4Ix9ucGXUy0K+rzpE+pXTWWw8+tiic79WY6KZ8MXa45XlQAAAAAAAA==
--------------ms070906010408080601030707--




From owner-ietf@ietf.org  Sun Feb 29 13:40:21 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05010
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 13:40:21 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxVnR-0003zE-DR
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 13:36:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxVnI-0003y6-TU
	for ietf@asgard.ietf.org; Sun, 29 Feb 2004 13:36:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04968
	for <ietf@ietf.org>; Sun, 29 Feb 2004 13:36:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxVnH-000408-00
	for ietf@ietf.org; Sun, 29 Feb 2004 13:36:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxVmN-0003w5-00
	for ietf@ietf.org; Sun, 29 Feb 2004 13:35:07 -0500
Received: from adsl-64-168-10-254.dsl.scrm01.pacbell.net ([64.168.10.254] helo=drakken.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxVlY-0003rf-00
	for ietf@ietf.org; Sun, 29 Feb 2004 13:34:16 -0500
Received: from drakken.dbc.mtview.ca.us (localhost [127.0.0.1])
	by drakken.dbc.mtview.ca.us (8.12.9/8.12.9) with SMTP id i1TIYFXt005708;
	Sun, 29 Feb 2004 10:34:15 -0800 (PST)
Date: Sun, 29 Feb 2004 10:34:15 -0800
From: Marshall Rose <mrose+mtr.netnews@dbc.mtview.ca.us>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Jabber at IETF-59
Message-Id: <20040229103415.7b015a2d.mrose+mtr.netnews@dbc.mtview.ca.us>
In-Reply-To: <38679008-6ACD-11D8-9DA7-000A95CD987A@muada.com>
References: <38679008-6ACD-11D8-9DA7-000A95CD987A@muada.com>
Organization: Dover Beach Consulting, Inc.
X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Will there be any jabbering at IETF-59? There is absolutely no 
> information to be found anywhere, and connecting to 
> conference.ietf.jabber.com (which was the server of choice at past 
> meetings IIRC) room "plenary" doesn't produce results of any kind, not 
> even a timeout, for my client.

well, i'm in several rooms right now... they all appear to be working...

/mtr



From owner-ietf@ietf.org  Sun Feb 29 15:43:05 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09567
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 15:43:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxXZl-0006bO-0P
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 15:30:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxXZd-0006aA-Kr
	for ietf@asgard.ietf.org; Sun, 29 Feb 2004 15:30:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09272
	for <ietf@ietf.org>; Sun, 29 Feb 2004 15:30:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxXZc-0005wb-00
	for ietf@ietf.org; Sun, 29 Feb 2004 15:30:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxXYk-0005sN-00
	for ietf@ietf.org; Sun, 29 Feb 2004 15:29:10 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxXXp-0005j8-00
	for ietf@ietf.org; Sun, 29 Feb 2004 15:28:14 -0500
Received: from Royer.com (doug@inet-products.com [12.110.13.100])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i1TKR56K023024
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Sun, 29 Feb 2004 12:27:07 -0800
Message-ID: <40424B19.7020101@Royer.com>
Date: Sun, 29 Feb 2004 13:27:05 -0700
From: Doug Royer <Doug@Royer.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Marshall Rose <mrose+mtr.netnews@dbc.mtview.ca.us>
CC: Iljitsch van Beijnum <iljitsch@muada.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: Jabber at IETF-59
References: <38679008-6ACD-11D8-9DA7-000A95CD987A@muada.com> <20040229103415.7b015a2d.mrose+mtr.netnews@dbc.mtview.ca.us>
In-Reply-To: <20040229103415.7b015a2d.mrose+mtr.netnews@dbc.mtview.ca.us>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms050507060103070302020208"
X-Royer.com-MailScanner-Information: Please contact SiteAdmin@Royer.com for more information
X-Royer.com-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a cryptographically signed message in MIME format.

--------------ms050507060103070302020208
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


He is looking for instructions.

Marshall Rose wrote:

>>Will there be any jabbering at IETF-59? There is absolutely no 
>>information to be found anywhere, and connecting to 
>>conference.ietf.jabber.com (which was the server of choice at past 
>>meetings IIRC) room "plenary" doesn't produce results of any kind, not 
>>even a timeout, for my client.
>>    
>>
>
>well, i'm in several rooms right now... they all appear to be working...
>
Using which server?

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms050507060103070302020208
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMjI5MjAyNzA1WjAjBgkqhkiG9w0BCQQxFgQUdQt1hQX4RiZMDhyewaH6
sdZs+iwwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEALHa3h2gqlSeVewKC+fEIRptGpBhHiUK3xu5itiBHn+bgjU+Z+ZZHHZOuhThvrmAC
++jRWXx25PZSRufkTDdKKmnxGor0bpPsY2TFvSTh4lM7qPYXDrxLBI+VYGi4A6Xk5GdDUHHp
9v/U2zIrGQ3/T6T/ujCBwseLp8bVVsPAXSTnVhF/sbuAGXH+JrS5U0CmpZDaT9NNjXZj/2W2
37V5e8PqOBXGCRlcSGinpUl4u5JnBQ7rvh2Od7yI1+jZE2MUMYf/AxHlcX3p+s5cDrAkQU/d
8BlUazAI+Mme8IvS2NQ2Sis38Fk0685sBNvfbsItK+sRekps+UC+K/GRsgNEcQAAAAAAAA==
--------------ms050507060103070302020208--




From owner-ietf@ietf.org  Sun Feb 29 15:50:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09877
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 15:50:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxXpF-0007GS-0r
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 15:46:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxXoO-0007EN-4R
	for ietf@asgard.ietf.org; Sun, 29 Feb 2004 15:45:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09636
	for <ietf@ietf.org>; Sun, 29 Feb 2004 15:45:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxXoM-00077L-00
	for ietf@ietf.org; Sun, 29 Feb 2004 15:45:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxXnJ-0006za-00
	for ietf@ietf.org; Sun, 29 Feb 2004 15:44:13 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxXmN-0006tF-00
	for ietf@ietf.org; Sun, 29 Feb 2004 15:43:15 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1TKhPrq091778;
	Sun, 29 Feb 2004 21:43:27 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <40424B19.7020101@Royer.com>
References: <38679008-6ACD-11D8-9DA7-000A95CD987A@muada.com> <20040229103415.7b015a2d.mrose+mtr.netnews@dbc.mtview.ca.us> <40424B19.7020101@Royer.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DE4AF981-6AF7-11D8-9DA7-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Jabber at IETF-59
Date: Sun, 29 Feb 2004 21:43:02 +0100
To: Doug Royer <Doug@Royer.com>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 29-feb-04, at 21:27, Doug Royer wrote:

> He is looking for instructions.

>> well, i'm in several rooms right now... they all appear to be 
>> working...

> Using which server?

http://xmpp.org/ietf-chat.html did the trick - thanks!




From owner-ietf@ietf.org  Sun Feb 29 17:35:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13171
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 17:35:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxZNp-0001TT-Ls
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 17:26:01 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxZK5-0001P9-JT
	for ietf@asgard.ietf.org; Sun, 29 Feb 2004 17:22:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12763
	for <ietf@ietf.org>; Sun, 29 Feb 2004 17:22:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxZK4-0007Id-00
	for ietf@ietf.org; Sun, 29 Feb 2004 17:22:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxZJ7-0007Eg-00
	for ietf@ietf.org; Sun, 29 Feb 2004 17:21:10 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxZIG-00076s-00
	for ietf@ietf.org; Sun, 29 Feb 2004 17:20:16 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 3688361B92; Sun, 29 Feb 2004 23:19:42 +0100 (CET)
Date: Mon, 01 Mar 2004 06:47:06 +0900
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: John Leslie <john@jlc.net>, Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: List for MARID discussions (Re: Principles of Spam-abatement)
Message-ID: <68997292.1078123626@localhost>
In-Reply-To: <20040228003403.GA13563@verdi>
References: <20040227231812.GI69134@verdi>
 <200402272345.i1RNjVak071725@calcite.rhyolite.com>
 <20040228003403.GA13563@verdi>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I believe ietf-mxcomp@imc.org (usual -request convention) was intended for 
this discussion.

--On 27. februar 2004 19:34 -0500 John Leslie <john@jlc.net> wrote:

>   There is no MARID mailing-list yet, so we're stuck here for a few
> more days. (ASRG is not an IETF group.) In the meantime, I'm trying to
> solicit consensus -- no matter how "rough" -- on principles of spam
> abatement, not details of its implementation.







From owner-ietf@ietf.org  Sun Feb 29 21:15:36 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24213
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 21:15:36 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Axcro-00077U-MN
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 21:09:12 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Axcr8-00075w-Vl
	for ietf@asgard.ietf.org; Sun, 29 Feb 2004 21:08:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23837
	for <ietf@ietf.org>; Sun, 29 Feb 2004 21:08:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axcr7-0005ZD-00
	for ietf@ietf.org; Sun, 29 Feb 2004 21:08:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axcq5-0005Ru-00
	for ietf@ietf.org; Sun, 29 Feb 2004 21:07:26 -0500
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxcpH-0005FD-00
	for ietf@ietf.org; Sun, 29 Feb 2004 21:06:35 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i2125xX26248
	for <ietf@ietf.org>; Mon, 1 Mar 2004 04:05:59 +0200
Date: Mon, 1 Mar 2004 04:05:59 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: bogus 6to4 router at IETF WLAN
Message-ID: <Pine.LNX.4.44.0403010401480.25999-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Someone's Windows box with lladdr fe80::204:23ff:fe7a:fb3e
(2002:da25:e0b0::da25:e0b0) is advertising has gotten too smart, and
is advertising the default route on the IETF59 WLAN.

Stop immediately.

(Perhaps misbehaving hosts should get MAC address blacklisted for a 
while..?)




From owner-ietf@ietf.org  Sun Feb 29 21:39:36 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25675
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 21:39:36 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxdH1-0008Cq-GQ
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 21:35:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxdGW-0008B4-NF
	for ietf@asgard.ietf.org; Sun, 29 Feb 2004 21:34:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25373
	for <ietf@ietf.org>; Sun, 29 Feb 2004 21:34:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxdGV-0000fH-00
	for ietf@ietf.org; Sun, 29 Feb 2004 21:34:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxdFj-0000Xi-00
	for ietf@ietf.org; Sun, 29 Feb 2004 21:33:55 -0500
Received: from bfbi.net ([203.255.248.61])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxdEx-0000Ok-00
	for ietf@ietf.org; Sun, 29 Feb 2004 21:33:08 -0500
Received: by bfbi.net (Postfix, from userid 1001)
	id A595A20F68; Mon,  1 Mar 2004 11:33:06 +0900 (KST)
Date: Mon, 1 Mar 2004 11:33:06 +0900
From: Woohyong Choi <choi@bfbi.net>
To: Pekka Savola <pekkas@netcore.fi>
Cc: ietf@ietf.org, 59crew@noc.kr.apan.net
Subject: Re: bogus 6to4 router at IETF WLAN
Message-ID: <20040301023306.GB59942@bfbi.net>
References: <Pine.LNX.4.44.0403010401480.25999-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0403010401480.25999-100000@netcore.fi>
User-Agent: Mutt/1.4i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

The host has been jailed not to be able to associate with access points.

choi

On Mon, Mar 01, 2004 at 04:05:59AM +0200, Pekka Savola wrote:
> Someone's Windows box with lladdr fe80::204:23ff:fe7a:fb3e
> (2002:da25:e0b0::da25:e0b0) is advertising has gotten too smart, and
> is advertising the default route on the IETF59 WLAN.
> 
> Stop immediately.
> 
> (Perhaps misbehaving hosts should get MAC address blacklisted for a 
> while..?)
> 



From owner-ietf@ietf.org  Sun Feb 29 21:42:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25975
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 21:42:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxdKq-0008Ip-At
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 21:39:12 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxdK4-0008Gs-2z
	for ietf@asgard.ietf.org; Sun, 29 Feb 2004 21:38:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25583
	for <ietf@ietf.org>; Sun, 29 Feb 2004 21:38:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxdK2-000173-00
	for ietf@ietf.org; Sun, 29 Feb 2004 21:38:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxdJB-00011m-00
	for ietf@ietf.org; Sun, 29 Feb 2004 21:37:30 -0500
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxdIj-0000w6-00
	for ietf@ietf.org; Sun, 29 Feb 2004 21:37:01 -0500
Received: from limbo (limbo.unfix.org [3ffe:8114:2000:240:200:39ff:fe77:1f3f])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP id 35A16867B;
	Mon,  1 Mar 2004 03:37:12 +0100 (CET)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Pekka Savola'" <pekkas@netcore.fi>, <ietf@ietf.org>
Subject: RE: bogus 6to4 router at IETF WLAN
Date: Mon, 1 Mar 2004 03:35:32 +0100
Organization: Unfix
Message-ID: <007a01c3ff35$de919be0$210d640a@unfix.org>
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.0403010401480.25999-100000@netcore.fi>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,LINES_OF_YELLING 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Pekka Savola wrote:

> Someone's Windows box with lladdr fe80::204:23ff:fe7a:fb3e
> (2002:da25:e0b0::da25:e0b0) is advertising has gotten too smart, and
> is advertising the default route on the IETF59 WLAN.
> 
> Stop immediately.
> 
> (Perhaps misbehaving hosts should get MAC address blacklisted for a 
> while..?)

jeroen@purgatory:~$ ipv6calc -i 2002:da25:e0b0::
No input type specified, try autodetection...found type: ipv6addr
No output type specified, try autodetection...found type: ipv6addr
Address type: unicast, 6to4, global-unicast
Address type is 6to4 and included IPv4 address is: 218.37.224.176
IPv4 registry for 6to4 address: APNIC
Address type has SLA: 0000
Interface identifier: 0000:0000:0000:0000
Interface identifier is probably manual set or based on a local EUI-64 identifier
jeroen@purgatory:~$ host 218.37.224.176
176.224.37.218.in-addr.arpa domain name pointer MIKE_NOTE.dhcp.ietf59.or.kr.

ping it and arp it ;)

Or run around screaming MIIIKEEEE and hope that there is no
kid suddenly popping screaming Wazowwwskkiii back at you ;)

Btw this is probably one of the subjects to attend to soon
as I've seen it causing havoc quite a number of times:

- - what is the 'easy' way of 'ignoring/deprecating' RA's
  without turning off all the RA's.

Thus that one could mark the above as 'deprecated' and that
it doesn't POP up in your routing tables/interface tables.
Reply is prolly better to go to v6ops...

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / http://unfix.org/~jeroen

iQA/AwUBQEKhdCmqKFIzPnwjEQI6EgCgvvZSwZetn+9ONXDk9QbCkblDFL8AoKUn
SzmTXnmlFRLnzImwnKuGCRyp
=2U5H
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Sun Feb 29 22:03:18 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26937
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 22:03:18 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxdbI-000187-SD
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 21:56:12 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxdaP-000165-TE
	for ietf@asgard.ietf.org; Sun, 29 Feb 2004 21:55:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26681
	for <ietf@ietf.org>; Sun, 29 Feb 2004 21:55:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxdaO-00034Z-00
	for ietf@ietf.org; Sun, 29 Feb 2004 21:55:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxdZP-0002yZ-00
	for ietf@ietf.org; Sun, 29 Feb 2004 21:54:15 -0500
Received: from bfbi.net ([203.255.248.61])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxdYQ-0002q5-00
	for ietf@ietf.org; Sun, 29 Feb 2004 21:53:14 -0500
Received: by bfbi.net (Postfix, from userid 1001)
	id D375A20F68; Mon,  1 Mar 2004 11:53:13 +0900 (KST)
Date: Mon, 1 Mar 2004 11:53:13 +0900
From: Woohyong Choi <choi@bfbi.net>
To: ietf@ietf.org
Cc: 59crew@noc.kr.apan.net
Subject: IETF59 Wireless Issues
Message-ID: <20040301025312.GA60193@bfbi.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

We have issues with wireless connectivity at the Crystall ball rooms.
59crew is working on the issue, and updates will be posted in reply
to this email.

Also, it appears that ad-hoc nodes are starting to appear. Please make
sure you DISABLE ad-hoc modes from your notebooks.

Please direct your mails to 59crew@noc.kr.apan.net for any network
related issues.

We apologize for your inconveniences.

Woohyong Choi, on behalf of IETF59 NOC team



From owner-ietf@ietf.org  Sun Feb 29 22:09:06 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27303
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 22:09:06 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Axdk3-0001kQ-0h
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 22:05:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwqQb-0001Rt-Jp
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 17:25:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28987
	for <ietf@ietf.org>; Fri, 27 Feb 2004 17:25:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwqQY-0000HN-00
	for ietf@ietf.org; Fri, 27 Feb 2004 17:25:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwqPe-0000Ah-00
	for ietf@ietf.org; Fri, 27 Feb 2004 17:24:54 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwqPE-0007ng-00
	for ietf@ietf.org; Fri, 27 Feb 2004 17:24:29 -0500
Received: from BBFUJIP.brandenburg.com (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i1RMWfd31920;
	Fri, 27 Feb 2004 14:32:42 -0800
Date: Sat, 28 Feb 2004 07:23:59 +0900
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <141936945.20040228072359@brandenburg.com>
To: John Leslie <john@jlc.net>
CC: Dave Crocker <dhc2@dcrocker.net>, IETF Discussion <ietf@ietf.org>
Subject: Re: Principles of Spam-abatement
In-Reply-To: <20040227141903.GA69134@verdi>
References: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net>
 <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com> <20040226205953.GA68458@verdi>
 <74237662.20040227152946@brandenburg.com> <20040227141903.GA69134@verdi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

>> unfortunately, that act of communication _is_ the adverse side
>> effect.  it tells the spammer that yours is an active, responsive
>> email account.

JL>    I must disagree.

JL>    Iljitsch stated it precisely and well: "the fact that a message is
JL> discarded as spam" need not give any information about whether the
JL> recipient is an active email account -- least of all "responsive".

If this were a math exercise, I would have to agree with your point.
And even though it is not a math exercise, your point certainly is
relevant.

The difference is that there are practicalities of implementation and
use that we have to anticipate.  This falls under the unfortunate
reality that the real-world is not conducted so carefully.

On the average, user-level Internet mechanisms need to be pretty
simple and straightforward, if they are to be successful.



d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>






From owner-ietf@ietf.org  Sun Feb 29 22:09:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27323
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 22:09:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Axdk3-0001kW-5A
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 22:05:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AwqUB-0001e8-OB
	for ietf@asgard.ietf.org; Fri, 27 Feb 2004 17:29:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29115
	for <ietf@ietf.org>; Fri, 27 Feb 2004 17:29:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwqUA-0000eZ-00
	for ietf@ietf.org; Fri, 27 Feb 2004 17:29:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwqTD-0000ZX-00
	for ietf@ietf.org; Fri, 27 Feb 2004 17:28:35 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwqSG-0000Px-00
	for ietf@ietf.org; Fri, 27 Feb 2004 17:27:36 -0500
Received: from BBFUJIP.brandenburg.com (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i1RMZod32113;
	Fri, 27 Feb 2004 14:35:50 -0800
Date: Sat, 28 Feb 2004 07:27:09 +0900
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <762660908.20040228072709@brandenburg.com>
To: John Leslie <john@jlc.net>
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: Principles of Spam-abatement
In-Reply-To: <20040227142909.GB69134@verdi>
References: <Pine.LNX.4.44.0402260836350.6202-100000@lilith.rgb.private.net>
 <8C2DE558-6872-11D8-997E-000A95CD987A@muada.com> <20040226205953.GA68458@verdi>
 <p06020401bc64251fe8d7@[205.214.163.20]> <20040227142909.GB69134@verdi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

JL>    While I am _very_ sympathetic to the need to limit the discussion,
JL> I really don't see how anything useful can be accomplished if the
JL> chair rules "principles of spam-abatement" to be irrelevant.

It is a small matter of seeking to have a productive meeting.

Discussion about the definition of spam or other broad topics, such as
principles of abatement are certainly important, but they also suffer
from a) taking a long time, and b) tending not to converge on a rough
consensus agreement.

By contract, discussion of specific techniques can be very efficient.
 This falls under the category of "I may not know much about spam, but
 I know what spam control mechanisms I like".

Yes, there are weaknesses in this approach, but they aren't as bad as
wasting an entire BOF debating philosophy.


d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>






From owner-ietf@ietf.org  Sun Feb 29 22:11:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27496
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 22:11:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Axdk3-0001kc-9X
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 22:05:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxMZz-0006cQ-BS
	for ietf@asgard.ietf.org; Sun, 29 Feb 2004 03:45:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13064
	for <ietf@ietf.org>; Sun, 29 Feb 2004 03:45:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxMZx-0007El-00
	for ietf@ietf.org; Sun, 29 Feb 2004 03:45:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxMZ5-0007An-00
	for ietf@ietf.org; Sun, 29 Feb 2004 03:44:48 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxMYd-00075w-00
	for ietf@ietf.org; Sun, 29 Feb 2004 03:44:19 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i1T8iarq082453
	for <ietf@ietf.org>; Sun, 29 Feb 2004 09:44:36 +0100 (CET)
	(envelope-from iljitsch@bgpexpert.com)
Mime-Version: 1.0 (Apple Message framework v612)
Content-Transfer-Encoding: 7bit
Message-Id: <73625DE8-6A93-11D8-9DA7-000A95CD987A@bgpexpert.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@bgpexpert.com>
Subject: Jabber @ IETF-59?
Date: Sun, 29 Feb 2004 09:44:13 +0100
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

Will there be any jabbering at IETF-59? There is absolutely no 
information to be found anywhere, and connecting to 
conference.ietf.jabber.com (which was the server of choice at past 
meetings IIRC) room "plenary" doesn't produce results of any kind, not 
even a timeout, for my client.






From owner-ietf@ietf.org  Sun Feb 29 23:09:28 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29632
	for <ietf-archive@odin.ietf.org>; Sun, 29 Feb 2004 23:09:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AxecB-0004if-UC
	for ietf-list@asgard.ietf.org; Sun, 29 Feb 2004 23:01:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AxebM-0004gT-Kt
	for ietf@asgard.ietf.org; Sun, 29 Feb 2004 23:00:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29339
	for <ietf@ietf.org>; Sun, 29 Feb 2004 23:00:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxebK-0001GH-00
	for ietf@ietf.org; Sun, 29 Feb 2004 23:00:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxeaO-0001Bw-00
	for ietf@ietf.org; Sun, 29 Feb 2004 22:59:20 -0500
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxeZS-00013q-00
	for ietf@ietf.org; Sun, 29 Feb 2004 22:58:22 -0500
Received: by sa.vix.com (Postfix, from userid 716)
	id 2BB3214C56; Mon,  1 Mar 2004 03:57:49 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Principles of Spam-abatement
References: <141936945.20040228072359@brandenburg.com>
From: Paul Vixie <vixie@vix.com>
Date: 01 Mar 2004 03:57:49 +0000
In-Reply-To: <141936945.20040228072359@brandenburg.com>
Message-ID: <g3wu65dxs2.fsf@sa.vix.com>
Lines: 12
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> >> unfortunately, that act of communication _is_ the adverse side effect.
> >> it tells the spammer that yours is an active, responsive email account.

that's only true from the smtp perspective.  since smtp does not encode any
aspect of consent, existence implies reachability.  however, since smtp is
dead meat rotting in the sun waiting for us to figure out what to replace it
with, smtp is not relevant in a discussion of "principles" which this claims
to be.  (anyone who thinks that smtp can be upgraded to encode consent needs
to spend a few more years Just Hitting Delete before you can sit at the
grownups table.)
-- 
Paul Vixie



