From owner-ietf@ietf.org  Sun Jun  1 00:14:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20052
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 00:14:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MK9E-00087d-9e
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 00:08:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MK1I-0007yu-PK
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 00:00:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18646
	for <ietf@ietf.org>; Sun, 1 Jun 2003 00:00:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MJzc-0003OJ-00
	for ietf@ietf.org; Sat, 31 May 2003 23:58:48 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MJzb-0003OG-00
	for ietf@ietf.org; Sat, 31 May 2003 23:58:47 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 208864; Sat, 31 May 2003 23:00:00 -0500
Message-ID: <3ED97A5C.5010308@ehsco.com>
Date: Sat, 31 May 2003 23:00:28 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: ietf@ietf.org
Subject: Re: Spam
References: <020304736.20030531142859@brandenburg.com> <20030531220537.1E3D613969@sa.vix.com> <20030531184335.72e2ef97.moore@cs.utk.edu>            <3ED96AD9.7050003@ehsco.com> <200306010342.h513gXn1025595@turing-police.cc.vt.edu>
In-Reply-To: <200306010342.h513gXn1025595@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 5/31/2003 10:42 PM Valdis.Kletnieks@vt.edu wrote:

> We're starting to see the rise of zombie networks of trojaned machines
> to send spam, similar to the DDoS networks.  Which makes Paul Vixie's
> comments even more important:

http://www.pcworld.com/news/article/0,aid,110918,00.asp talks about this
from another perspective.

If worms are going to be sending out stuff on behalf of the user (whether
that be copies of itself, or spam as in this case), then no amount of
identity information will be able to prevent it. I mean, even with all of
the proposals put forth here, it would still be impossible to filter worms
without disabling all file attachments everywhere, since some users are
always going to open attachments, or are going to run bad clients.

However, having verified identity information (the sender, the host, the
domain) *will* assist in enforcement against worms: "we know your user is
infected, here's the proof."

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




From owner-ietf@ietf.org  Sun Jun  1 04:33:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01676
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 04:33:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MO4K-0002gd-QU
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 04:19:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MNw8-0002Tj-Sl
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 04:11:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01343
	for <ietf@ietf.org>; Sun, 1 Jun 2003 04:11:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MNuS-0004RC-00
	for ietf@ietf.org; Sun, 01 Jun 2003 04:09:44 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MNuR-0004R9-00
	for ietf@ietf.org; Sun, 01 Jun 2003 04:09:43 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h518BPKk072228
	for <ietf@ietf.org>; Sun, 1 Jun 2003 10:11:25 +0200 (CEST)
Message-ID: <0d1601c32815$6538a060$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.33.0305311426550.16737-100000@egate.xpasc.com> <0cc201c327c1$b518d220$0a00000a@atkielski.com> <3ED94D1C.C94BDA21@earthlink.net>
Subject: Re: The utilitiy of IP is at stake here
Date: Sun, 1 Jun 2003 10:11:25 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Peter writes:

> Most Usenet groups would probably turn up an
> example or two ...

As I've indicated, a great many Internet users never post to USENET and do
not participate in mailing lists.

The online archiving of mailing lists is a bad idea, IMO, independently of
the copyright issues it raises.  But even when lists are archived online,
given that most people do not post to lists, this is not necessarily a
problem for spam address harvesters.

> see above...

What I saw above does not alter my opinion.  Only a minority of the Internet
community posts to mailing lists or USENET.

> Please stop thinking the entire world is just
> like you.

I do not believe that.  For example, I'm quite confident that I receive
considerably more spam than most people do.

> Put another way, I'm happy for you that spam is
> not yet a major problem for you. It's a major problem
> for lots of people on this list.

This list is probably not a representative cross-section of all Internet
users.

> More importantly, it's perceived to be a growing problem
> for the rest of the Internet, for which a solution will
> be needed in the not too distant future ...

It is a growing problem.  How urgently a solution is required is more of an
open question.





From owner-ietf@ietf.org  Sun Jun  1 04:33:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01709
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 04:33:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MO4L-0002gy-3P
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 04:19:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MNy1-0002XX-GV
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 04:13:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01381
	for <ietf@ietf.org>; Sun, 1 Jun 2003 04:13:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MNwK-0004SB-00
	for ietf@ietf.org; Sun, 01 Jun 2003 04:11:40 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MNwJ-0004S8-00
	for ietf@ietf.org; Sun, 01 Jun 2003 04:11:40 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h518DNKk072242
	for <ietf@ietf.org>; Sun, 1 Jun 2003 10:13:23 +0200 (CEST)
Message-ID: <0d2101c32815$ab6edea0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.33.0305311426550.16737-100000@egate.xpasc.com> <0cc201c327c1$b518d220$0a00000a@atkielski.com> <3ED94D1C.C94BDA21@earthlink.net>
Subject: Re: The utilitiy of IP is at stake here
Date: Sun, 1 Jun 2003 10:13:23 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Peter writes:

> Anthony, please don't take this the wrong way ...

What's the best way to take personal attacks, in your opinion?  And what is
your purpose in making them, given that they do not contribute to the
discussion?




From owner-ietf@ietf.org  Sun Jun  1 04:38:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01994
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 04:38:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MO4L-0002h9-Bd
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 04:19:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MNzK-0002Xd-6d
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 04:14:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01399
	for <ietf@ietf.org>; Sun, 1 Jun 2003 04:14:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MNxd-0004Sf-00
	for ietf@ietf.org; Sun, 01 Jun 2003 04:13:01 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MNxc-0004Sc-00
	for ietf@ietf.org; Sun, 01 Jun 2003 04:13:00 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h518EhKk072252
	for <ietf@ietf.org>; Sun, 1 Jun 2003 10:14:43 +0200 (CEST)
Message-ID: <0d2a01c32815$db81b180$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0305301553050.17819-100000@commander.av8.net> <267841966.1054312648@p3.JCK.COM> <E19LyV9-000Khr-Uq@ran.psg.com> <20030601020915.GE7127@login.ecs.soton.ac.uk>
Subject: Re: Answering questions and defamation (was: RE: The utilitiy of IP is at stake here)
Date: Sun, 1 Jun 2003 10:14:43 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tim writes:

> Trouble is even after kill-filing the trolls the
> good folk still rise to the bait ...

Perhaps the "good folk" tolerate differences of opinion and are willing to
debate them, whereas others consider all disagreement as "trolling."




From owner-ietf@ietf.org  Sun Jun  1 04:44:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02233
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 04:44:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MO98-0004l8-JX
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 04:24:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MO2F-0002ct-Uc
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 04:17:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01463
	for <ietf@ietf.org>; Sun, 1 Jun 2003 04:17:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MO0Z-0004U2-00
	for ietf@ietf.org; Sun, 01 Jun 2003 04:16:03 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MO0X-0004Ty-00
	for ietf@ietf.org; Sun, 01 Jun 2003 04:16:01 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id F04CE13969
	for <ietf@ietf.org>; Sun,  1 Jun 2003 08:17:14 +0000 (GMT)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ietf@ietf.org
Subject: guessing and trying (was re: spam)
X-Mailer: MH-E 7.3; nmh 1.0.4; GNU Emacs 21.3.1
Date: Sun, 01 Jun 2003 08:17:14 +0000
Message-Id: <20030601081714.F04CE13969@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> > Guessing and trying?
> 
> That would require tens of thousands or even millions of bounces for every
> successful mailing attempt.  I don't think anyone is doing it that way.

"so sure are you?"

here's tonight's dictionary run against vix.com.  first the mh "scan" headers:

 2551  06/02 ""                 please dont bother l zjug<<This is a multi-part
 2552  06/01 ""                 re: huh? sdu kater<<This is a multi-part messag
 2553  06/01 ""                 please dont bother yjcejscgraf sfxtz<<This is a
 2554  06/01 ""                 results are in ozbewglg<<This is a multi-part m
 2555  06/02 ""                 Something of interest. qdj rrv hmvrowzuyzyy<<Th
 2556  06/01 ""                 Witty as ever nkbrbouizn<<This is a multi-part 
 2557  06/01 ""                 I really appreciate this. rsyxjm wdwf sil uhdw<
 2558  06/01 ""                 Your welcome! zzhtdvydmaxkkyzmpo<<This is a mul
 2559  06/01 ""                 Re: Hey rz<<This is a multi-part message in MIM
 2560  06/01 ""                 make a change today ygp rmbo<<This is a multi-p
 2561  06/01 ""                 Congratulations! dgb ikuuqnpcx<<This is a multi
 2562  06/01 ""                 re: sure thing ituttaeqt<<This is a multi-part 
 2563  06/02 ""                 make a change today adobauoquqd ydf d<<This is 
 2564  06/02 ""                 re: what about it? oocjs gbnmk<<This is a multi
 2565  06/02 ""                 re: if you say so wx kgj<<This is a multi-part 
 2566  06/02 ""                 Something of interest. zyms mchv ny h<<This is 
 2567  06/01 ""                 its about time yoazedk tc<<This is a multi-part
 2568  06/02 ""                 its about time h le lc<<This is a multi-part me
 2569  06/01 ""                 re: huh? kx gzm ndgv<<This is a multi-part mess
 2570  06/01 ""                 not too sure evstajxlqbwvfemmv<<This is a multi
 2571  06/01 ""                 Thanks for your time. zkwiwdvb<<This is a multi
 2572  06/01 ""                 what are you going to do? xsmas<<This is a mult
 2573  06/01 ""                 please dont bother utzwbjmaripbpmrj<<This is a 
 2574  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2575  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2576  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2577  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2578  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2579  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2580  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2581  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2582  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2583  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2584  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2585  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2586  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2587  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2588  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2589  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2590  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2591  06/02 ""                 Waiting for you. jidrptprxgfs<<This is a multi-
 2592  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2593  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2594  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2595  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2596  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2597  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2598  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2599  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2600  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2601  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2602  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2603  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2604  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2605  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2606  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2607  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2608  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2609  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2610  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2611  06/01 ""                 Your welcome! z sxcd zu<<This is a multi-part m
 2612  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2613  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2614  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2615  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2616  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2617  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2618  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2619  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2620  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2621  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2622  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2623  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2624  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2625  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2626  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2627  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2628  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2629  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2630  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2631  06/02 ""                 Worthy of visting. qqvo<<This is a multi-part m
 2632  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2633  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2634  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2635  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2636  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2637  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2638  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2639  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2640  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2641  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2642  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2643  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2644  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2645  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2646  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2647  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2648  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2649  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2650  06/02 ""                 Worthy of visting. vqjuojiutrv kivpl<<This is a
 2651  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2652  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2653  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2654  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2655  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2656  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2657  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2658  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2659  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2660  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2661  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2662  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2663  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2664  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2665  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2666  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2667  06/01 ""                 results are in ghxmugzk<<This is a multi-part m
 2668  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2669  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2670  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2671  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2672  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2673  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2674  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2675  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2676  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2677  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2678  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2679  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2680  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2681  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2682  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2683  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2684  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2685  06/02 ""                 live longer x szgxrmhlvyojrw s<<This is a multi
 2686  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2687  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2688  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2689  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2690  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2691  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2692  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2693  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2694  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2695  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2696  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2697  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2698  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2699  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2700  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2701  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2702  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2703  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2704  06/02 ""                 please dont bother lbnzqphklqisnmpp<<This is a 
 2705  06/01 ""                 results are in kka<<This is a multi-part messag
 2706  06/01 ""                 results are in kka<<This is a multi-part messag
 2707  06/01 ""                 results are in kka<<This is a multi-part messag
 2708  06/01 ""                 results are in kka<<This is a multi-part messag
 2709  06/01 ""                 results are in kka<<This is a multi-part messag
 2710  06/01 ""                 results are in kka<<This is a multi-part messag
 2711  06/01 ""                 results are in kka<<This is a multi-part messag
 2712  06/01 ""                 results are in kka<<This is a multi-part messag
 2713  06/01 ""                 results are in kka<<This is a multi-part messag
 2714  06/01 ""                 results are in kka<<This is a multi-part messag
 2715  06/01 ""                 results are in kka<<This is a multi-part messag
 2716  06/01 ""                 results are in kka<<This is a multi-part messag
 2717  06/01 ""                 results are in kka<<This is a multi-part messag
 2718  06/01 ""                 results are in kka<<This is a multi-part messag
 2719  06/01 ""                 results are in kka<<This is a multi-part messag
 2720  06/01 ""                 results are in kka<<This is a multi-part messag
 2721  06/01 ""                 results are in kka<<This is a multi-part messag
 2722  06/01 ""                 results are in kka<<This is a multi-part messag
 2723  06/01 ""                 results are in kka<<This is a multi-part messag
 2724  06/01 ""                 results are in kka<<This is a multi-part messag
 2725  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2726  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2727  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2728  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2729  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2730  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2731  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2732  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2733  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2734  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2735  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2736  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2737  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2738  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2739  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2740  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2741  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2742  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2743  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2744  06/01 ""                 Waiting for you. p maowjxhllctix<<This is a mul
 2745  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2746  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2747  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2748  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2749  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2750  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2751  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2752  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2753  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2754  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2755  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2756  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2757  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2758  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2759  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2760  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2761  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2762  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2763  06/01 ""                 re: sure thing pvcwxptus beyj qvis<<This is a m
 2764  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2765  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2766  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2767  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2768  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2769  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2770  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2771  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2772  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2773  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2774  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2775  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2776  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2777  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2778  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2779  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2780  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2781  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2782  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2783  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2784  06/02 ""                 Worthy of visting. yf zkiibhhtof<<This is a mul
 2785  06/02 ""                 re: its up to you saxysx jnugi bvklggb<<This is
 2786  06/01 ""                 re: huh? mykeroyu rcliygcvi<<This is a multi-pa
 2787  06/02 ""                 A website worth visiting. wmtkjxudx<<This is a 
 2788  06/01 ""                 Waiting for you. aremblsj<<This is a multi-part
 2789  06/01 ""                 re: what about it? tmqjllrnztpnszkixi<<This is 
 2790  06/01 ""                 re: if you say so bhqqk i paxtsd yy<<This is a 
 2791  06/01 ""                 re: if you say so bhqqk i paxtsd yy<<This is a 
 2792  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2793  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2794  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2795  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2796  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2797  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2798  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2799  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2800  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2801  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2802  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2803  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2804  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2805  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2806  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2807  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2808  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2809  06/01 ""                 make a change today dwdf qwxsk<<This is a multi
 2810  06/02 ""                 Something of interest. gzxeaeycm itcadfkkt<<Thi
 2811  06/02 ""                 what are you going to do? f pixj k kmld<<This i
 2812  06/02 ""                 what are you going to do? f pixj k kmld<<This i
 2813  06/02 ""                 re: what about it? cdtr f<<This is a multi-part
 2814+ 06/01 ""                 re: if you say so sxt<<This is a multi-part mes

now the relays, sorted by frequency (which is given):

  61 67.161.111.254
  42 24.126.149.35
  40 12.239.19.195
  21 12.252.180.70
  21 12.228.173.235
  18 24.126.159.213
  17 12.238.213.8
   3 148.244.194.125
   3 12.106.230.230
   2 4.63.67.197
   2 24.99.141.253
   2 24.195.17.172
   2 24.158.153.248
   2 128.218.153.64
   2 12.238.11.170
   1 24.174.138.57

finally the recipients, sorted alphabetically, with frequency as given:

   1 accobra@vix.com		   1 kay@vix.com
   1 ace@vix.com		   1 kdg@vix.com
   1 achieve@vix.com		   1 miles@vix.com
   1 acmc@vix.com		   1 million@vix.com
   1 acninfo@vix.com		   1 mindcapture@vix.com
   1 action@vix.com		   1 minesh@vix.com
   1 actnet@vix.com		   1 minex1@vix.com
   1 actnow@vix.com		   1 mknbucks@vix.com
   1 adcopy2@vix.com		   1 mktamerica@vix.com
   1 adcopy@vix.com		   1 mktgconcepts@vix.com
   1 addit@vix.com		   1 mktgcyber@vix.com
   1 addresscficfii@vix.com	   1 mmaire1@vix.com
   1 addresses@vix.com		   1 moesch@vix.com
   1 adfree@vix.com		   1 mommymind@vix.com
   1 adman@vix.com		   1 money4u@vix.com
   1 adna1@vix.com		   1 money@vix.com
   1 adsonline@vix.com		   1 moneybook@vix.com
   1 advanced@vix.com		   1 moneydoctr@vix.com
   1 advantage@vix.com		   1 moneyopp@vix.com
   1 adventure@vix.com		   1 moneysaved@vix.com
   1 bugbox@vix.com		   1 nobody@sa.vix.com
   1 bulk@vix.com		   1 prepaid@vix.com
   1 bulkmail@vix.com		   1 prism1996@vix.com
   1 bulldog@vix.com		   1 prismpc@vix.com
   1 bushbaby@vix.com		   1 private3@vix.com
   1 business@vix.com		   1 private@vix.com
   1 buyers@vix.com		   1 products@vix.com
   1 bwealthy@vix.com		   1 profile@vix.com
   1 cactus@vix.com		   1 profitnow@vix.com
   1 callback@vix.com		   1 profits@vix.com
   1 callinfo@vix.com		   1 profitsnow@vix.com
   1 cantlose@vix.com		   1 profitsonline@vix.com
   1 capital@vix.com		   1 promo@vix.com
   1 caps@vix.com		   1 prosp@vix.com
   1 capsinfo@vix.com		   1 prosper@vix.com
   1 career@vix.com		   1 protection@vix.com
   1 careerinfo@vix.com		   1 protwo@vix.com
   1 ccpiedmont@vix.com		   1 psolutions@vix.com
   1 ccspl@vix.com		   1 root@vix.com
   1 cdbenger@vix.com		   1 roulette@vix.com
   1 details12@vix.com		   1 roundtuit@vix.com
   1 details13@vix.com		   1 rpalm@vix.com
   1 details14@vix.com		   1 rsvp4u@vix.com
   1 details15@vix.com		   1 rwbent@vix.com
   1 details2@vix.com		   1 rwm@vix.com
   1 details3@vix.com		   1 saleaday@vix.com
   1 details4@vix.com		   1 salecorp@vix.com
   1 details5@vix.com		   1 sales@vix.com
   1 details6@vix.com		   1 salesaday@vix.com
   1 details7@vix.com		   1 salespromo@vix.com
   1 details8@vix.com		   1 salesunlim@vix.com
   1 details9@vix.com		   1 sample@vix.com
   1 detailsnow@vix.com		   1 sampleadd@vix.com
   1 deweyresch@vix.com		   1 sampleout@vix.com
   1 dfuller1@vix.com		   1 sampleremove@vix.com
   1 dfuller2@vix.com		   1 samplesender@vix.com
   1 dgones@vix.com		   1 sandman@vix.com
   1 diamonds@vix.com		   1 succeednow@vix.com
   1 diet30@vix.com		   1 success1@vix.com
   1 difaznet@vix.com		   1 success4u@vix.com
   1 dinogeorge@vix.com		   1 success@vix.com
   1 drtarryk@vix.com		   1 successful@vix.com
   1 ds@vix.com			   1 successnow@vix.com
   1 dsconcepts@vix.com		   1 summertime@vix.com
   1 dstny@vix.com		   1 sunfoodspa@vix.com
   1 dynavest@vix.com		   1 sunsetpub@vix.com
   1 eagle1@vix.com		   1 superfood@vix.com
   1 eagle500@vix.com		   1 support@vix.com
   1 eaglehill@vix.com		   1 supports@vix.com
   1 earnsum@vix.com		   1 suprblugrn@vix.com
   1 earth@vix.com		   1 sys@vix.com
   1 earthangels@vix.com	   1 tabatha@vix.com
   1 earthtrust@vix.com		   1 takealook1@vix.com
   1 easymoney@vix.com		   1 takealook2@vix.com
   1 easyprofit@vix.com		   1 takealook3@vix.com
   1 econo@vix.com		   1 takecards@vix.com
   1 ecumen@vix.com		   1 takemeoff@vix.com
   1 eddie1@vix.com		   1 tally@vix.com
   1 eddie3@vix.com		   1 tape@vix.com
   1 eddie@vix.com		   1 target@vix.com
   1 healthmap3@vix.com		   1 tatiana@vix.com
   1 healthmap4@vix.com		   1 tches@vix.com
   1 hello@vix.com		   1 team1@vix.com
   1 help4u@vix.com		   1 team2@vix.com
   1 helpers@vix.com		   1 teezer@vix.com
   1 helpme@vix.com		   1 telechron@vix.com
   1 hendrix@vix.com		   1 telecomm@vix.com
   1 herb@vix.com		   1 teleinfo@vix.com
   1 herbalpc@vix.com		   1 telemall@vix.com
   1 here4you@vix.com		   1 telephone@vix.com
   1 hits24@vix.com		   1 telepro@vix.com
   1 hologram@vix.com		   1 telrates@vix.com
   1 hotinfo1@vix.com		   1 test0718@vix.com
   1 ibb2@vix.com		   1 test0729@vix.com
   1 ilawinfo@vix.com		   1 test0801@vix.com
   1 inablink@vix.com		   1 test@vix.com
   1 incboost@vix.com		   1 vitaspray@vix.com
   1 income@vix.com		   1 vixi@vix.com
   1 jhanvi@vix.com		  34 vixie@sa.vix.com
   1 jhobart@vix.com		   1 vixie@vix.com
   1 jim@vix.com		   1 vj@vix.com
   1 jimsmith@vix.com		   1 vlk9@vix.com
   1 jjent1@vix.com		   1 vlk9a@vix.com
   1 jl@vix.com			   1 voicemail@vix.com
   1 jle@vix.com		   1 vsteals@vix.com
   1 jobinfo@vix.com		   1 wallace2@vix.com
   1 joblist@vix.com		   1 wallace@vix.com
   1 joinin@vix.com		   1 walt21@vix.com
   1 jpmktng@vix.com		   1 wantmoreinfo@vix.com
   1 jsinclair@vix.com		   1 warnock@vix.com
   1 jsinterprises@vix.com	   1 wave@vix.com
   1 judge@vix.com		   1 waycool@vix.com
   1 judy@vix.com		   1 wayne@vix.com
   1 julie@vix.com		   1 wealth4u@vix.com
   1 kaboom@vix.com		   1 wealth@vix.com
   1 kangaroo@vix.com

the only two of these which were *ever* valid is the one at frequency 34,
and the one which follows it alphabetically (by happenstance).  the rest
is pure guessuery.  so, yes, folks are "doing it that way".  every day.
(this is not meant to impress anybody.  if dave rand posted his stats for
bungi.com's dictionary attacks, well, THAT would maybe impress somebody.)

the relays i heard this from are all open proxies installed either by some
kind of default microsoft application installer or installed by a worm that
got into a windows/xp system by means of well publicized holes and left a
proxy in its wake.

"have fun storming the castle, boys!"



From owner-ietf@ietf.org  Sun Jun  1 04:52:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02467
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 04:52:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MOSW-0006DZ-Ko
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 04:44:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MO9X-0004lA-1b
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 04:25:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01549
	for <ietf@ietf.org>; Sun, 1 Jun 2003 04:25:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MO7q-0004VS-00
	for ietf@ietf.org; Sun, 01 Jun 2003 04:23:34 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MO7p-0004VP-00
	for ietf@ietf.org; Sun, 01 Jun 2003 04:23:33 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h518PGKk072334
	for <ietf@ietf.org>; Sun, 1 Jun 2003 10:25:16 +0200 (CEST)
Message-ID: <0d4101c32817$54c71d40$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <020304736.20030531142859@brandenburg.com>	<20030531220537.1E3D613969@sa.vix.com> <20030531184335.72e2ef97.moore@cs.utk.edu> <3ED96AD9.7050003@ehsco.com>
Subject: Re: Spam
Date: Sun, 1 Jun 2003 10:25:16 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric writes:

> For example, Hotmail and AOL exchange mail directly
> already, and they could use SMTPng for these exchanges
> and immediately start to take advantage of the available
> features, regardless of what they use to talk to the rest
> of the world.

True ... but unless they are already sending a lot of spam to each other
today, what would this accomplish?

> My guess is that the 80/20 rule probably applies to email,
> in that 80% of the messages are probably routed through 20%
> of the mail servers, and getting a sizable portion of that
> 20% would likely be enough to capture most of the messaging
> network.

I agree, but I also suspect that most of the world's spam is routed outside
that 20% of mail servers, so I'm not sure what this would accomplish.

> My feeling is that the whole effort would be much more
> likely to succeed if it were a from-scratch design.

Like PNG, IMAP, JPEG2000, and so on ... all of which are taking the Internet
by storm, as we all know.

The more discussion I see of technical solutions to spam here, the more I
tend to believe that no technical solution will work.  Participants in this
discussion, for the most part, clearly do not have a handle on the
fundamental problem of spam, and incorrectly believe that some magic,
machine-verifiable characteristic of a message will allow it to be
identified as spam rather than legitimate e-mail.  But the only difference
between spam is in the interpretation made of it by its human recipient, and
that cannot be encoded in any machine language.  Every technical solution
mentioned thus far will allow spam to continue, and will also cause the loss
of legitimate e-mail.




From owner-ietf@ietf.org  Sun Jun  1 04:57:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02615
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 04:57:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MOSX-0006Ee-Di
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 04:44:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MODT-0004lc-He
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 04:29:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01616
	for <ietf@ietf.org>; Sun, 1 Jun 2003 04:29:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MOBm-0004Wj-00
	for ietf@ietf.org; Sun, 01 Jun 2003 04:27:38 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MOBl-0004Wf-00
	for ietf@ietf.org; Sun, 01 Jun 2003 04:27:38 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h518TLKk072358
	for <ietf@ietf.org>; Sun, 1 Jun 2003 10:29:21 +0200 (CEST)
Message-ID: <0d5201c32817$e690bd30$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <020304736.20030531142859@brandenburg.com> <20030531220537.1E3D613969@sa.vix.com> <20030531184335.72e2ef97.moore@cs.utk.edu>            <3ED96AD9.7050003@ehsco.com> <200306010342.h513gXn1025595@turing-police.cc.vt.edu> <3ED97A5C.5010308@ehsco.com>
Subject: Re: Spam
Date: Sun, 1 Jun 2003 10:29:21 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric writes:

> If worms are going to be sending out stuff on behalf
> of the user (whether that be copies of itself, or spam
> as in this case), then no amount of identity information
> will be able to prevent it.

In that case, all discussions here of such protocols are moot, since the
very first thing spammers will do is adopt the use of worms to send their
e-mails.

> I mean, even with all of the proposals put forth here,
> it would still be impossible to filter worms without
> disabling all file attachments everywhere, since some
> users are always going to open attachments, or are going
> to run bad clients.

I agree.  It is curious that this impossibility is so readily acknowledged,
whereas the impossibility of stopping spam itself, which arises from exactly
the same foundation (that is, from the fact that it requires human
intervention in order to actually be effective) is being overlooked.

> However, having verified identity information (the sender,
> the host, the domain) *will* assist in enforcement against
> worms: "we know your user is infected, here's the proof."

The spam will already be sent by then, and there will always be other
machines.  Additionally, if one spam session uses 4000 machines, the cost of
finding and cleaning 4000 machines is likely to exceed the cost incurred by
processing of the spam by orders of magnitude.




From owner-ietf@ietf.org  Sun Jun  1 05:50:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03266
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 05:50:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MPHu-0008Rs-1q
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 05:38:02 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MPBg-0008JT-1p
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 05:31:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03083
	for <ietf@ietf.org>; Sun, 1 Jun 2003 05:31:33 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MP9z-0004zq-00
	for ietf@ietf.org; Sun, 01 Jun 2003 05:29:51 -0400
Received: from h80ad2703.async.vt.edu ([128.173.39.3] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MP9x-0004zn-00
	for ietf@ietf.org; Sun, 01 Jun 2003 05:29:50 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h519VOn1005187;
	Sun, 1 Jun 2003 05:31:24 -0400
Message-Id: <200306010931.h519VOn1005187@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here 
In-Reply-To: Your message of "Sun, 01 Jun 2003 10:11:25 +0200."
             <0d1601c32815$6538a060$0a00000a@atkielski.com> 
References: <Pine.LNX.4.33.0305311426550.16737-100000@egate.xpasc.com> <0cc201c327c1$b518d220$0a00000a@atkielski.com> <3ED94D1C.C94BDA21@earthlink.net>
            <0d1601c32815$6538a060$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1855602726P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sun, 01 Jun 2003 05:31:23 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sun, 01 Jun 2003 10:11:25 +0200, Anthony Atkielski <anthony@atkielski.com>  said:

> As I've indicated, a great many Internet users never post to USENET and do
> not participate in mailing lists.

The guys at LSoft Inc feel otherwise...

http://www.lsoft.com/products/default.asp?item=listserv

Number of public lists	75,526
Number of local lists	209,846
Total number of lists	285,372
Total membership (public+local)	131,394,317
Total messages delivered today 	24,758,359

That's *only* for LSoft's Listserv product, and does *NOT* include all the
intranet installs of Listserv.  In fact, I suspect it only covers some 400
registered installs of their commercial product - the free and trial versions
don't register themselves and won't be included in those numbers.

This doesn't include MailMan, ezmlm, Majordomo, or any other software.  Note
that LSoft is *NOT* the market-share leader.

I think we can conclude that a great many Internet users *DO* participate in
mailing lists.

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

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

iD8DBQE+2cfrcC3lWbTT17ARAnoIAKC6PhSUcoWjcg2IE4kUKYCwABnB9QCgwS3h
Eme7WTNdy5Unpwj31RuTKgw=
=cKif
-----END PGP SIGNATURE-----

--==_Exmh_1855602726P--



From owner-ietf@ietf.org  Sun Jun  1 13:12:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22327
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 13:12:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MWBR-0007d3-GS
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 12:59:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MW7Z-0007Vk-Hk
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 12:55:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21492
	for <ietf@ietf.org>; Sun, 1 Jun 2003 12:55:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MW5s-0002HC-00
	for ietf@ietf.org; Sun, 01 Jun 2003 12:54:04 -0400
Received: from smtp017.mail.yahoo.com ([216.136.174.114])
	by ietf-mx with smtp (Exim 4.12)
	id 19MW5r-0002Gl-00
	for ietf@ietf.org; Sun, 01 Jun 2003 12:54:03 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 1 Jun 2003 16:55:36 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Sun, 1 Jun 2003 18:55:31 +0200
Organization: Internet Society
Message-ID: <003601c3285e$9e34c080$3b00a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <0d2101c32815$ab6edea0$0a00000a@atkielski.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

He obviously took it the wrong way...
;)

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Anthony
Atkielski
Sent: dimanche 1 juin 2003 10:13
To: IETF Discussion
Subject: Re: The utilitiy of IP is at stake here


Peter writes:

> Anthony, please don't take this the wrong way ...

What's the best way to take personal attacks, in your opinion?  And what is
your purpose in making them, given that they do not contribute to the
discussion?






From owner-ietf@ietf.org  Sun Jun  1 13:17:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22994
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 13:17:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MWOB-000873-M7
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 13:12:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MWGT-0007h6-5Z
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 13:05:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21952
	for <ietf@ietf.org>; Sun, 1 Jun 2003 13:04:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MWEl-0002PX-00
	for ietf@ietf.org; Sun, 01 Jun 2003 13:03:15 -0400
Received: from mail9.speakeasy.net ([216.254.0.209] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MWEk-0002PO-00
	for ietf@ietf.org; Sun, 01 Jun 2003 13:03:14 -0400
Received: (qmail 5688 invoked from network); 1 Jun 2003 17:04:58 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail9.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <vjs@calcite.rhyolite.com>; 1 Jun 2003 17:04:58 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Subject: Re: The utilitiy of IP is at stake here
Date: Sun, 1 Jun 2003 13:07:21 -0400
User-Agent: KMail/1.5
References: <3ED67A32.4020007@cisco.com> <200305292230.h4TMUwZi026406@calcite.rhyolite.com>
In-Reply-To: <200305292230.h4TMUwZi026406@calcite.rhyolite.com>
MIME-Version: 1.0
Content-Disposition: inline
Cc: ietf@ietf.org
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <200306011307.21876.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Vernon Schryver <vjs@calcite.rhyolite.com> wrote:

 > > From: Eliot Lear <lear@cisco.com>
 [snip]
 > > Red, consumers do install software when they perceive either a
 > > threat or a benefit.
 >
 > Do you really intend to say what those words mean in context, that
 > Microsoft products were replaced wholesale by other software.

Unfortunately, most consumers perceive neither the threat of using 
Microsoft products, nor the benefits of most alternatives.  They only 
perceive that Windows is what is being pushed at the store, what their 
workplace probably uses, and what their friends and family probably use.  
They therefore often believe that in order to be compatible, they must 
drink MS Koolaid as well, therefore perceiving a large negative benefit 
to using pretty much anything else, except possibly a Mac.

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info





From owner-ietf@ietf.org  Sun Jun  1 13:52:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25375
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 13:52:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MWw5-0000ZS-AP
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 13:48:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MWl3-0000Rq-AR
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 13:36:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24284
	for <ietf@ietf.org>; Sun, 1 Jun 2003 13:36:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MWjL-00039D-00
	for ietf@ietf.org; Sun, 01 Jun 2003 13:34:51 -0400
Received: from thwip.polyamory.org ([192.31.227.220])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MWjL-00039A-00
	for ietf@ietf.org; Sun, 01 Jun 2003 13:34:51 -0400
Received: by thwip.polyamory.org (Postfix, from userid 1002)
	id C05BD12E0E; Sun,  1 Jun 2003 13:36:29 -0400 (EDT)
Date: Sun, 1 Jun 2003 13:36:29 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: ietf@ietf.org
Subject: DNS RMX RR draft
Message-ID: <20030601133629.S6083@thwip.polyamory.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Organization: American Association Against Acronym Abuse
Sender: owner-ietf@ietf.org
Precedence: bulk

I just saw this recently submitted draft and don't recall it being
discussed in the recent spam thread, so thought I'd point it out in
case people hadn't noticed it:
  http://www.ietf.org/internet-drafts/draft-danisch-dns-rr-smtp-01.txt

(Note: I am stating no opinion about its applicability or effectiveness)

  --  Cos (Ofer Inbar)       --   cos@aaaaa.org  http://cos.polyamory.org/
   "OSI is a beautiful dream, and TCP/IP is living it!"
     -- Einar Stefferud <Stef@nma.com>, IETF mailing list, 12 May 1992



From owner-ietf@ietf.org  Sun Jun  1 13:56:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25805
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 13:56:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MWxp-0000g8-H4
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 13:49:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MWrU-0000WG-Cd
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 13:43:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24658
	for <ietf@ietf.org>; Sun, 1 Jun 2003 13:43:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MWpm-0003GI-00
	for ietf@ietf.org; Sun, 01 Jun 2003 13:41:30 -0400
Received: from smtp014.mail.yahoo.com ([216.136.173.58])
	by ietf-mx with smtp (Exim 4.12)
	id 19MWpm-0003GF-00
	for ietf@ietf.org; Sun, 01 Jun 2003 13:41:30 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 1 Jun 2003 17:43:13 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'IETF Discussion'" <ietf@ietf.org>
Subject: This IETF discussion list
Date: Sun, 1 Jun 2003 19:43:04 +0200
Organization: Internet Society
Message-ID: <004901c32865$450e5140$3b00a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <3ED94D1C.C94BDA21@earthlink.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA25805

Should this list be open to ANYbody (any curious/interested netizen), or
limited to proven... well... specialists? experts?

I think this IETF discussion list is like a combination of the IEEE and the
ISOC : the IEEE is limited to certified engineers, while the ISOC is open to
all netizens.

Which one is the best approach? I don't think the answer can be found in the
following statements, extracted from IETF's web site :

---------
The IETF discussion list serves two purposes. It furthers the development
and specification of Internet technology through discussion of technical
issues. It also hosts discussions of IETF direction, policy, and procedures.
As this is the most general IETF mailing list, considerable latitude is
allowed. Advertising, whether to solicit business or promote employment
opportunities, falls well outside the range of acceptable topics, as do
discussions of a personal nature. 

This list is meant for initial discussion only. Discussions that fall within
the area of any working group or well established list should be moved to
such more specific forum as soon as this is pointed out, unless the issue is
one for which the working group needs wider input or direction. 

In addition to the topics noted above, appropriate postings include: 
* Last Call discussions of proposed protocol actions 
* Discussion of technical issues that are candidates for IETF work, but do
not yet have an appropriate e-mail venue 
* Discussion of IETF administrative policies 
* Questions and clarifications concerning IETF meetings. 

Inappropriate postings include: 
* Unsolicited bulk e-mail 
* Discussion of subjects unrelated to IETF policy, meetings, activities, or
technical concerns 
* Unprofessional commentary, regardless of the general subject. 

The IETF Chair, the IETF Executive Director, or a sergeant-at-arms appointed
by the Chair is empowered to restrict posting by a person or of a thread as
they deem appropriate to limit abuse. Complaints regarding their decisions
should be referred to the IAB. 

NOTE: The IETF list is performing spam control according to the guidelines
given in the IESG guidelines on spam control..

A list of active spam prevention policies can be found here. 

If you have problems posting to the list, contact the IETF Mail
Administrator.
---------

By example, the more messages from A*** A*** I read, the more I think he is
making statements of his own, without verification, without proof, without
experience...

Maybe this is due to a low technical knowledge? Or to a lack of valuable,
proven information? (No offense. Just wondering...)

Also remember J*** F*** and all his IPv8, IPv16,... stuff! Do such people
just troll "for the pleasure", or are they convinced of what they state?

I find it amusing that we discuss about SPAM, while we are victims of a kind
of spamming! We are not even able to properly filter this list, and we think
about preventing SPAM worlwide!

Back to my first question. I don't say I know the answer. I don't say I have
a solution. I'm just thinking, and sharing my thoughts with you all.

Anyway, it must be difficult to be this list's moderator! :-/





From owner-ietf@ietf.org  Sun Jun  1 14:02:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26298
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 14:02:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MWxp-0000gE-Rc
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 13:49:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MWvk-0000ZD-OC
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 13:47:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25064
	for <ietf@ietf.org>; Sun, 1 Jun 2003 13:47:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MWu3-0003OZ-00
	for ietf@ietf.org; Sun, 01 Jun 2003 13:45:55 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MWu2-0003OU-00
	for ietf@ietf.org; Sun, 01 Jun 2003 13:45:54 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h51He4S23632;
	Sun, 1 Jun 2003 10:40:07 -0700
Date: Sun, 1 Jun 2003 10:40:04 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: Anthony Atkielski <anthony@atkielski.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here 
In-Reply-To: <0cc201c327c1$b518d220$0a00000a@atkielski.com>
Message-ID: <Pine.LNX.4.33.0306011027570.16737-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Sun, 1 Jun 2003, Anthony Atkielski wrote:

> David writes:
>
> > Guessing and trying?
>
> That would require tens of thousands or even millions of bounces for every
> successful mailing attempt.  I don't think anyone is doing it that way.

Paul Vixie has provided his specific proof. I'd suggest that a very high
percentage of 3 letters combined with aol.com, msn.com, yahoo.com and
earthlink.com were/would be found this way. Furthermore, all common
first names and last names and combinations. Two letters with common last
names, etc.


>
> > Online directory provided by her email provider?
>
> Which e-mail providers are providing online directories?  And how many of
> these directories allow you to extract addresses without specifying any
> search parameters (such as a name)?

When I found AOL's member directory, a simple search on my last name was
sufficient to obtain a result. Commonly available windows QA tools would
allow automation of the AOL GUI to harvest a large list. Needless to say,
I closed the barn door, probably too late.

The other responses were based on differing evaluations of human behavior.
Since neither of us have documented credentials in that space my comments
were speculative as were the responses.

I don't think many conclusions about address harvesting can be drawn from
personal experience of folks who are users of small domains or technically
savy users who avoid risky behaviors.

Dave Morris




From owner-ietf@ietf.org  Sun Jun  1 15:06:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28364
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 15:06:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MXyj-0002fY-HT
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 14:54:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MXtf-0002aN-Px
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 14:49:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27915
	for <ietf@ietf.org>; Sun, 1 Jun 2003 14:49:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MXry-0004Gk-00
	for ietf@ietf.org; Sun, 01 Jun 2003 14:47:50 -0400
Received: from mail15.speakeasy.net ([216.254.0.215] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MXrx-0004Gh-00
	for ietf@ietf.org; Sun, 01 Jun 2003 14:47:49 -0400
Received: (qmail 5376 invoked from network); 1 Jun 2003 18:49:32 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail15.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <anthony@atkielski.com>; 1 Jun 2003 18:49:32 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: "Anthony Atkielski" <anthony@atkielski.com>
Subject: Re: The utilitiy of IP is at stake here
Date: Sun, 1 Jun 2003 14:51:54 -0400
User-Agent: KMail/1.5
References: <Pine.LNX.4.33.0305311426550.16737-100000@egate.xpasc.com> <0cc201c327c1$b518d220$0a00000a@atkielski.com>
In-Reply-To: <0cc201c327c1$b518d220$0a00000a@atkielski.com>
Cc: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200306011451.54740.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

"Anthony Atkielski" <anthony@atkielski.com> wrote:

 > David writes:
[0]

 > > Guessing and trying?
 >
 > That would require tens of thousands or even millions of bounces for
 > every successful mailing attempt.  I don't think anyone is doing it
 > that way.

Never heard of dictionary attacks?  They're not just for passwords.  
Spammers don't seem to CARE that their delivery rate may be 1:1e6; their 
costs are practically nil.  After all, they already try to send to 
addresses that can't be verified as having existed in many years, or 
often to addresses that they have been told do not exist.

 > > Online directory provided by her email provider?
 >
 > Which e-mail providers are providing online directories?

At least Yahoo.

 > And how
 > many of these directories allow you to extract addresses without
 > specifying any search parameters (such as a name)?

So you have to provide a few search paramaters.  Whoop de doo.  Any 
decent programmer can write a program to search the entire space, by 
dividing it up when you hit the limit.

Or, split it up by using the Advanced Search there, and get the added 
bonus of knowing the age range, marital status, gender, interests, 
location, etc.  Can you say "marketing goldmine" boys and girls?

 > > Not understanding risks, she joins a seniors mail list?
 >
 > Possible, but not likely.

Perhaps not for your specific grandma, but . . . .

 > > Someone she corresponds with blasts an email to
 > > a bunch of folks leaving all addresses exposed,
 > > and one of the addressees does some action which
 > > exposes the email to a spammer's harvesting process?
 >
 > This is getting more and more farfetched.

Not farfetched at all.  Have you never had your email address in a To or 
Cc in a message from a perfectly innocent sender to a huge number of 
people?  That happens to me about weekly.  I can't say for sure whether 
that has resulted in my address winding up somewhere easily harvestable, 
other than as below.  However, I strongly suspect that it's not only 
plausible, but highly likely!  Think how many things you have seen that 
have not only huge To or Cc lists on them, but many *layers* of same, 
after many clueless lusers have forwarded it around the planet.  Do you 
trust each and every name on such a list, never to expose the addies???

 > > Or more explicitly, someone she knows copies her
 > > in a post to a mailing list which is being harvested.
 >
 > A list to which she doesn't belong?  Again, this seems unlikely.

That has happened to me many times.  Can you say with any confidence at 
all that, for instance, no messages on this very list, has ever had a 
non-member in the To or Cc?  It's possible, I grant you, but extremely 
unlikely (IMHO), and anybody could trivially make it not so.

 > I have quite a few addresses that remain untouched.  Only the ones
 > for which an obvious harvesting path exists have received spam.

Lucky lucky you.

[0]Not me, some other David.

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info




From owner-ietf@ietf.org  Sun Jun  1 15:12:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29065
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 15:12:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MYBS-0008Pc-16
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 15:07:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MXyk-0002fa-4x
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 14:54:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27975
	for <ietf@ietf.org>; Sun, 1 Jun 2003 14:54:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MXx2-0004I4-00
	for ietf@ietf.org; Sun, 01 Jun 2003 14:53:04 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MXx1-0004I1-00
	for ietf@ietf.org; Sun, 01 Jun 2003 14:53:03 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h51Iv7x19014;
	Sun, 1 Jun 2003 11:57:07 -0700
Date: Sun, 1 Jun 2003 11:54:13 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <1154353469.20030601115413@brandenburg.com>
To: Ofer Inbar <cos@aaaaa.org>
CC: ietf@ietf.org
Subject: Re: DNS RMX RR draft
In-Reply-To: <20030601133629.S6083@thwip.polyamory.org>
References: <20030601133629.S6083@thwip.polyamory.org>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ofer,

OI> I just saw this recently submitted draft and don't recall it being
OI> discussed in the recent spam thread, so thought I'd point it out in
OI> case people hadn't noticed it:
OI>  
OI> http://www.ietf.org/internet-drafts/draft-danisch-dns-rr-smtp-01.txt

It has been discussed at length on the relevant anti-spam discussion
list:  <http://www.irtf.org/charters/asrg.html>.


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




From owner-ietf@ietf.org  Sun Jun  1 15:30:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29733
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 15:30:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MYIF-0002Sh-NK
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 15:14:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MYG9-0001fG-T4
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 15:12:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29094
	for <ietf@ietf.org>; Sun, 1 Jun 2003 15:12:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MYER-0004Mv-00
	for ietf@ietf.org; Sun, 01 Jun 2003 15:11:03 -0400
Received: from mail10.speakeasy.net ([216.254.0.210] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MYER-0004Mh-00
	for ietf@ietf.org; Sun, 01 Jun 2003 15:11:03 -0400
Received: (qmail 18175 invoked from network); 1 Jun 2003 19:12:19 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail10.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <Tomson_Eric@Yahoo.fr>; 1 Jun 2003 19:12:19 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: <Tomson_Eric@Yahoo.fr>, "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: This IETF discussion list
Date: Sun, 1 Jun 2003 15:14:43 -0400
User-Agent: KMail/1.5
References: <004901c32865$450e5140$3b00a8c0@tomson.be>
In-Reply-To: <004901c32865$450e5140$3b00a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200306011514.43345.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

"Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr> wrote:

 > Should this list be open to ANYbody (any curious/interested netizen),
 > or limited to proven... well... specialists? experts?

I advocate open.

First, who is to say who is an expert?  Shall we require N years of 
experience with a particular technology before letting people even 
discuss it?  That just raises the bar to BECOMING an expert.

Second, I for one have found great value in participating in some lists 
on subjects that were new to me.  (Of course, that's mostly lurking; it 
might be fruitful in this thread to separate lurking and posting.)

Third, sometimes a fresh perspective is useful.  At times, I have even 
managed to make some valuable contributions on lists where I was there 
mainly to learn.  (See RFC 3458, for example.)

Fourth, we already have mechanisms in place to deal with disruptive 
behavior.

Fifth, as Robert Heinlein wrote, "Specialization is for insects."

 > I think this IETF discussion list is like a combination of the IEEE
 > and the ISOC : the IEEE is limited to certified engineers,

Even that isn't quite that closed.  I joined in '88 or so, never having 
been certified as anything.  (I ran away before the nice young men in 
their clean white coats arrived with the butterfly nets.)  However, I 
did have to get a member to vouch for me.

 > extracted from IETF's web site :
 [...]
 > This list is meant for initial discussion only. Discussions that fall
 > within the area of any working group or well established list should
 > be moved to such more specific forum as soon as this is pointed out,

Heh.  Guilty as charged.  We should all move the spam thread to the 
IRTF's ASRG, ASAP, IMHO.  YMMV.  HTH.  HAND.

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info




From owner-ietf@ietf.org  Sun Jun  1 15:37:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29977
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 15:37:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MYWa-0003Em-H0
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 15:29:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MYKg-00031q-7o
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 15:17:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29562
	for <ietf@ietf.org>; Sun, 1 Jun 2003 15:17:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MYIy-0004RG-00
	for ietf@ietf.org; Sun, 01 Jun 2003 15:15:44 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MYIx-0004R1-00
	for ietf@ietf.org; Sun, 01 Jun 2003 15:15:43 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id PAA10874
	for <ietf@ietf.org>; Sun, 1 Jun 2003 15:10:27 -0400
Date: Sun, 1 Jun 2003 15:11:36 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: ietf@ietf.org
Subject: Re: The IETF_Censored mailing list
In-Reply-To: <20030601021324.GG7127@login.ecs.soton.ac.uk>
Message-ID: <Pine.LNX.4.44.0306011504150.21528-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Please do not return bounce messages, when you filter. (as you have been
doing.)

Those using such a list, should note that they are filtering based on
nothing other than ad hominem, personal attacks. This filter (like many
blacklists) has nothing whatsoever to do with the stated purpose of the
censored list, 'to filter debates that have nothing to do with the
purposes of the IETF'.

It should also be noted that those receiving thie limited IETF
information, like those receiving censored news, have very little to
contribute since they don't know the whole story.

		--Dean


On Sun, 1 Jun 2003, Tim Chown wrote:

> How timely...
>
> On Sun, Jun 01, 2003 at 03:03:01AM +0200, Super-User wrote:
> >
> >                         The IETF_Censored mailing list
> >
> >    At times, the IETF list is subject to debates that have little to do
> >    with the purposes for which the IETF list was created. Some people
> >    would appreciate a "quieter" forum for the relevant debates that take
> >    place, but the IETF's policy of openness has so far prevented the IETF
> >    from imposing any censorship policy on the IETF@ietf.org list.
> >
> >    To give people an alternative, there is a list called
> >    "ietf_censored@carmen.ipv6.cselt.it".
> >
> >    This list is a sublist (that is, it gets the same messages as) the
> >    open IETF discussion list. However, this list will not forward all
> >    messages; in particular, the filters have been set so that persons and
> >    discussions that are, in the view of Raffaele D'Albenzio, irrelevant
> >    to the IETF list are not forwarded.
> >
> >    Because this filter is automated, the criteria include:
> >      * Well known troublemakers
> >      * Well known crosspostings
> >      * Subjects that have led to recent non-conclusive exchanges
> >      * Some ways to say "unsubscribe"
> >      * Some "out-of-office-reply" messages
> >
> >    To join the list, send the word "subscribe" in the BODY of a message
> >    to ietf_censored-request@carmen.ipv6.cselt.it (the URL here is an RFC
> >    2368 mailto URL that does the Right Thing).
> >
> >    To unsubscribe, send the word "unsubscribe" in the BODY of a message
> >    to ietf_censored-request@carmen.ipv6.cselt.it. Do not send to the list
> >    - your message will be filtered!
> >    (members of the main IETF list itself must follow instructions for
> >    that list, of course. You are only a member of ietf_censored if there
> >    is a comment on the bottom of your IETF list mail saying that the
> >    message has been sent through the ietf_censored list.)
> >
> >    For fun, there is a special list for the rejected messages:
> >    ietf_censored-rejects@carmen.ipv6.cselt.it - subscribe in the same
> >    fashion, by mail to ietf_censored-rejects-request@carmen.ipv6.cselt.it
> >
> >    By public request, the current set of filters are listed at
> >    http://vesuvio.ipv6.tilab.com/cgi-bin/ietf_censored-filters
> >
> >    This page is http://carmen.ipv6.cselt.it/ietf_censored.html, and is
> >    posted monthly in text form to ietf@ietf.org
> >      _________________________________________________________________
> >
> >    Raffaele D'Albenzio < root@carmen.ipv6.cselt.it>
>
>




From owner-ietf@ietf.org  Sun Jun  1 16:53:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01520
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 16:53:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MZcK-0004x7-4Y
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 16:39:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MZYg-0004t7-Si
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 16:36:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01292
	for <ietf@ietf.org>; Sun, 1 Jun 2003 16:36:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MZWz-0004s4-00
	for ietf@ietf.org; Sun, 01 Jun 2003 16:34:17 -0400
Received: from web10901.mail.yahoo.com ([216.136.131.37])
	by ietf-mx with smtp (Exim 4.12)
	id 19MZWy-0004s0-00
	for ietf@ietf.org; Sun, 01 Jun 2003 16:34:16 -0400
Message-ID: <20030601203600.89695.qmail@web10901.mail.yahoo.com>
Received: from [12.237.229.250] by web10901.mail.yahoo.com via HTTP; Sun, 01 Jun 2003 13:36:00 PDT
Date: Sun, 1 Jun 2003 13:36:00 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Re: DNS RMX RR draft
To: ietf@ietf.org
In-Reply-To: <1154353469.20030601115413@brandenburg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Dear Dave,

Are you trying to start a rumor that the main IETF discussion
list is NOT a "relevant anti-spam discussion list"?

I agree with your motives, but don't see how you can base this
rumor on the past couple of weeks of postings :-}

(I'm recommending that we all attempt the following "Jedi Mind
Trick": "ietf@ietf.org is not the list you're looking for", "you
don't have to post to this list", "you can go now", with
apologies to Obi-wan in SW Episode IV)

Spencer, who feels for the ASRG if this quality of discussion
DOES move to that mailing list, but maybe "They Were
Expendable"...

--- Dave Crocker <dhc2@dcrocker.net> wrote:
> Ofer,
> 
> OI> I just saw this recently submitted draft and don't recall
> it being
> OI> discussed in the recent spam thread, so thought I'd point
> it out in
> OI> case people hadn't noticed it:
> OI>  
> OI>
>
http://www.ietf.org/internet-drafts/draft-danisch-dns-rr-smtp-01.txt
> 
> It has been discussed at length on the relevant anti-spam
> discussion
> list:  <http://www.irtf.org/charters/asrg.html>.



From owner-ietf@ietf.org  Sun Jun  1 17:19:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02313
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 17:19:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MZvg-0005bJ-Ar
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 16:59:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MZsp-0005WU-2N
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 16:56:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01685
	for <ietf@ietf.org>; Sun, 1 Jun 2003 16:56:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MZr7-0004zM-00
	for ietf@ietf.org; Sun, 01 Jun 2003 16:55:05 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MZr6-0004zJ-00
	for ietf@ietf.org; Sun, 01 Jun 2003 16:55:04 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h51KvnxS030288;
	Sun, 1 Jun 2003 22:57:50 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Sun, 1 Jun 2003 22:56:52 +0200
Subject: Re: The utilitiy of IP is at stake here
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Paul Hoffman / IMC <phoffman@imc.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <p05210619bafe7907c0f8@[63.202.92.152]>
Message-Id: <9243960C-9473-11D7-9195-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On zaterdag, mei 31, 2003, at 17:32 Europe/Amsterdam, Paul Hoffman / 
IMC wrote:

> To bludgeon the point a bit:

> - Big ISPs and other mail service providers know how much spam is 
> costing them.

Ah, but how much does spam earn them? I assume spammers pay for their 
bandwidth. Then there are all the anti-spam products. I'm not accusing 
anyone here, but if we're going to run the numbers we have to run ALL 
the numbers.

> - For some ISPs, the amount is in the millions of dollars.

If you have an 8 digit customer base pretty much any per-customer 
action is going to cost you millions. In and of itself that doesn't 
meany anything. A few years ago doing public key crypto for each 
incoming message would have been impossible, or at least more expensive 
than dealing with spam the traditional way. Today it's probably not 
even very hard.

> - Even an expensive team of consultants could devise a trust-based or 
> work-based protocol and shepherd it through the IETF for less than one 
> tenth the annual cost for a single ISP.

> Given the above, the reason that the people who are most financially 
> hurt by the spam problem have not done anything about it from a 
> protocol level is either that they are financially stupid or that 
> their research into the solutions didn't result in a solution that 
> would cost them more. I believe it is the latter.

Based on what I've seen here people are almost eager to pronounce the 
spam problem unsolvable. I think that means the problem scope is 
defined too narrow. Using current SMTP, we can't stop spam. One ISP or 
a small group of them can't change SMTP. Ergo, the problem is 
unsolvable. But the IETF _can_ create new protocols and does so as a 
matter of routine. A good number of them are even deployed.

So I'll repeat myself: let's have an anti-spam BOF and hopefully and 
anti-spam wg. First order of business for this wg: analyze the spam 
problem and then see if mechanisms can be found to reduce the amount of 
spam by 1 - 2 orders of magnitude. After that, we can decide if it's 
worth it to write a protocol and try to have it deployed.




From owner-ietf@ietf.org  Sun Jun  1 17:32:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02836
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 17:32:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MaJt-0006Ls-H1
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 17:24:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MaIJ-0006Fp-E1
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 17:23:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02486
	for <ietf@ietf.org>; Sun, 1 Jun 2003 17:23:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MaGb-0005C7-00
	for ietf@ietf.org; Sun, 01 Jun 2003 17:21:25 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MaGa-0005C4-00
	for ietf@ietf.org; Sun, 01 Jun 2003 17:21:24 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h51LN8Kk078532
	for <ietf@ietf.org>; Sun, 1 Jun 2003 23:23:08 +0200 (CEST)
Message-ID: <0da801c32883$ff80e510$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <004901c32865$450e5140$3b00a8c0@tomson.be>
Subject: Re: This IETF discussion list
Date: Sun, 1 Jun 2003 23:23:08 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric writes:

> Should this list be open to ANYbody (any curious/
> interested netizen), or limited to proven... well...
> specialists? experts?

Maybe we should limit list participation to people who can refrain from
writing entire posts that are nothing more than thinly veiled personal
attacks against people with whom they disagree?  That way the only people
left would be those prepared to discuss the topic at hand--people free of
any puerile compulsion to defame their colleagues.  What do you think?




From owner-ietf@ietf.org  Sun Jun  1 18:00:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03270
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 18:00:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Mai4-00077w-4U
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 17:49:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Mabk-0006xh-8L
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 17:43:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03050
	for <ietf@ietf.org>; Sun, 1 Jun 2003 17:43:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Maa2-0005Mh-00
	for ietf@ietf.org; Sun, 01 Jun 2003 17:41:30 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Maa1-0005Me-00
	for ietf@ietf.org; Sun, 01 Jun 2003 17:41:29 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h51LhDKk078691
	for <ietf@ietf.org>; Sun, 1 Jun 2003 23:43:13 +0200 (CEST)
Message-ID: <0dca01c32886$cdbc3c20$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.33.0305311426550.16737-100000@egate.xpasc.com> <0cc201c327c1$b518d220$0a00000a@atkielski.com> <3ED94D1C.C94BDA21@earthlink.net>            <0d1601c32815$6538a060$0a00000a@atkielski.com> <200306010931.h519VOn1005187@turing-police.cc.vt.edu>
Subject: Re: The utilitiy of IP is at stake here 
Date: Sun, 1 Jun 2003 23:43:13 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Valdis writes:

> The guys at LSoft Inc feel otherwise...

The guys at LSoft Inc are welcome to express themselves directly here.

> That's *only* for LSoft's Listserv product, and
> does *NOT* include all the intranet installs of
> Listserv.

Two points: (1) you don't seem to be counting people subscribed to more than
one list; and (2) how would spammers harvest from INTRANET installs of
Listserv?

I'm subscribed to dozens of mailing lists, many administered by Listserv.
Am I one person, or a hundred?

> I think we can conclude that a great many
> Internet users *DO* participate in mailing lists.

I think not, in part for reasons I've stated above.




From owner-ietf@ietf.org  Sun Jun  1 18:02:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03432
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 18:02:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MaiD-00078b-Lg
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 17:49:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Mah4-00073c-Kn
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 17:48:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03123
	for <ietf@ietf.org>; Sun, 1 Jun 2003 17:48:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MafM-0005OS-00
	for ietf@ietf.org; Sun, 01 Jun 2003 17:47:00 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MafL-0005OP-00
	for ietf@ietf.org; Sun, 01 Jun 2003 17:47:00 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h51Lmh8f018516
	for ietf@ietf.org env-from <vjs>;
	Sun, 1 Jun 2003 15:48:43 -0600 (MDT)
Date: Sun, 1 Jun 2003 15:48:43 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306012148.h51Lmh8f018516@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: The utilitiy of IP is at stake here
References: <9243960C-9473-11D7-9195-00039388672E@muada.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Iljitsch van Beijnum <iljitsch@muada.com>

> ...
> So I'll repeat myself: let's have an anti-spam BOF 

Face to face talk is likely to be of even lower quality than this
thread.  With email with a broad audience like this, people can
squelch obvious nonsense with data or pointers to real data and
independent reports.
(e.g. http://www.google.com/search?q=spammer+%22dictionary+attack%22 )

BOFs are transient committees and so are even worse than most committees
for creating things.  All you might do in a BOF is discover whether
anyone is interested is dealing with spam.

>                                                    and hopefully and 
> anti-spam wg. First order of business for this wg: analyze the spam 
> problem and then see if mechanisms can be found to reduce the amount of 
> spam by 1 - 2 orders of magnitude. After that, we can decide if it's 
> worth it to write a protocol and try to have it deployed.

That sounds more like research than protocol documentation and
standardization.  Why have you rejected the repeated pointers to
the IRTF/IETF ASRG research group?  In case you didn't intend to
reject them but just missed them, please consider:

 http://irtf.org/
 http://irtf.org/groups.html
 http://irtf.org/charters/asrg.html
 https://www1.ietf.org/mail-archive/working-groups/asrg/current/maillist.html

or

 http://www.google.com/search?q=%22Major+Internet+Standards%22+spam


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sun Jun  1 18:12:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04559
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 18:12:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MaxV-0002hh-5U
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 18:05:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Masj-00083R-DM
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 18:00:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03310
	for <ietf@ietf.org>; Sun, 1 Jun 2003 18:00:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mar1-0005RA-00
	for ietf@ietf.org; Sun, 01 Jun 2003 17:59:03 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mar0-0005QF-00
	for ietf@ietf.org; Sun, 01 Jun 2003 17:59:02 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h51LrQS24117
	for <ietf@ietf.org>; Sun, 1 Jun 2003 14:53:26 -0700
Date: Sun, 1 Jun 2003 14:53:26 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
Subject: Re: The IETF_Censored mailing list
In-Reply-To: <Pine.LNX.4.44.0306011504150.21528-100000@commander.av8.net>
Message-ID: <Pine.LNX.4.33.0306011449220.16737-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Sun, 1 Jun 2003, Dean Anderson wrote:


> It should also be noted that those receiving thie limited IETF
> information, like those receiving censored news, have very little to
> contribute since they don't know the whole story.

Hmmmm, if the ietf censored list is so bad for my education, how is it
that I see your post? Since the spam topic started a week or so ago, I
have not observed a single response post for which I didn't receive the
original.

Perhaps you haven't actually monitored what is being censored?

Dave Morris




From owner-ietf@ietf.org  Sun Jun  1 18:52:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05585
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 18:52:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MbdI-0006r1-85
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 18:48:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MbWt-0006mM-Aq
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 18:42:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05484
	for <ietf@ietf.org>; Sun, 1 Jun 2003 18:42:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MbVB-0005hn-00
	for ietf@ietf.org; Sun, 01 Jun 2003 18:40:33 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MbVA-0005hk-00
	for ietf@ietf.org; Sun, 01 Jun 2003 18:40:32 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h51MhAxS030427;
	Mon, 2 Jun 2003 00:43:10 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Mon, 2 Jun 2003 00:42:12 +0200
Subject: Re: The utilitiy of IP is at stake here
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200306012148.h51Lmh8f018516@calcite.rhyolite.com>
Message-Id: <495947C0-9482-11D7-9195-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On zondag, jun 1, 2003, at 23:48 Europe/Amsterdam, Vernon Schryver 
wrote:

>> So I'll repeat myself: let's have an anti-spam BOF

> Face to face talk is likely to be of even lower quality than this
> thread.

But aren't you supposed to have a BOF first before you can have a wg?

> BOFs are transient committees and so are even worse than most 
> committees
> for creating things.  All you might do in a BOF is discover whether
> anyone is interested is dealing with spam.

Seems a worthwhile thing to do, although better results than just an 
answer to that question wouldn't be a bad thing.

>>                                                    and hopefully and
>> anti-spam wg. First order of business for this wg: analyze the spam
>> problem and then see if mechanisms can be found to reduce the amount 
>> of
>> spam by 1 - 2 orders of magnitude. After that, we can decide if it's
>> worth it to write a protocol and try to have it deployed.

> That sounds more like research than protocol documentation and
> standardization.  Why have you rejected the repeated pointers to
> the IRTF/IETF ASRG research group?

Because I'm not interested in researching the problem; I'm interested 
in solving the problem. (I've been doing "spam research" for several 
minutes a day for many years now.) I believe the IETF is capable of 
creating new protocols that would move the spam problem from something 
that is completely out of control to something that is easily 
manageable. If this turns out impossible after all, documenting why 
would be a very good thing. Then the researchers can have another go at 
it.

> In case you didn't intend to
> reject them but just missed them, please consider:

I'll look over the mail archives when I have some time.




From owner-ietf@ietf.org  Sun Jun  1 18:57:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05759
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 18:57:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Mbe7-0006vR-Ew
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 18:49:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MbZz-0006qM-71
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 18:45:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05515
	for <ietf@ietf.org>; Sun, 1 Jun 2003 18:45:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MbYH-0005iU-00
	for ietf@ietf.org; Sun, 01 Jun 2003 18:43:45 -0400
Received: from web10902.mail.yahoo.com ([216.136.131.38])
	by ietf-mx with smtp (Exim 4.12)
	id 19MbYG-0005iR-00
	for ietf@ietf.org; Sun, 01 Jun 2003 18:43:44 -0400
Message-ID: <20030601224528.10741.qmail@web10902.mail.yahoo.com>
Received: from [12.237.229.250] by web10902.mail.yahoo.com via HTTP; Sun, 01 Jun 2003 15:45:28 PDT
Date: Sun, 1 Jun 2003 15:45:28 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Re: The IETF_Censored mailing list
To: ietf@ietf.org
In-Reply-To: <Pine.LNX.4.33.0306011449220.16737-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

--- David Morris <dwm@xpasc.com> wrote:
> 
> Hmmmm, if the ietf censored list is so bad for my education,
> how is it
> that I see your post? Since the spam topic started a week or
> so ago, I
> have not observed a single response post for which I didn't
> receive the
> original.

Ditto, no matter how much I wish that was NOT the case...

Spencer

("Yes, there is an IETF Censored list. The market for an IETF
On-topic list is still wide-open.")



From owner-ietf@ietf.org  Sun Jun  1 21:51:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08812
	for <ietf-web-archive@odin.ietf.org>; Sun, 1 Jun 2003 21:51:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MeIc-0001xS-06
	for ietf-list@asgard.ietf.org; Sun, 01 Jun 2003 21:39:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MeIT-0001ty-3M
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 21:39:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08319
	for <ietf@ietf.org>; Sun, 1 Jun 2003 21:39:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MeGk-0006TE-00
	for ietf@ietf.org; Sun, 01 Jun 2003 21:37:50 -0400
Received: from web10907.mail.yahoo.com ([216.136.131.43])
	by ietf-mx with smtp (Exim 4.12)
	id 19MeGg-0006TB-00
	for ietf@ietf.org; Sun, 01 Jun 2003 21:37:46 -0400
Message-ID: <20030602013930.93889.qmail@web10907.mail.yahoo.com>
Received: from [12.237.229.250] by web10907.mail.yahoo.com via HTTP; Sun, 01 Jun 2003 18:39:30 PDT
Date: Sun, 1 Jun 2003 18:39:30 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Re: The utilitiy of IP is at stake here
To: ietf@ietf.org
In-Reply-To: <495947C0-9482-11D7-9195-00039388672E@muada.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

My comment below is offered honestly (unlike the snippy comments
I posted earlier today)...

--- Iljitsch van Beijnum <iljitsch@muada.com> wrote:
> 
> >>                                                    and
> hopefully and
> >> anti-spam wg. First order of business for this wg: analyze
> the spam
> >> problem and then see if mechanisms can be found to reduce
> the amount 
> >> of
> >> spam by 1 - 2 orders of magnitude. After that, we can
> decide if it's
> >> worth it to write a protocol and try to have it deployed.
> 
> > That sounds more like research than protocol documentation
> and
> > standardization.  Why have you rejected the repeated
> pointers to
> > the IRTF/IETF ASRG research group?
> 
> Because I'm not interested in researching the problem; I'm
> interested 
> in solving the problem. (I've been doing "spam research" for
> several 
> minutes a day for many years now.) I believe the IETF is
> capable of 
> creating new protocols that would move the spam problem from
> something 
> that is completely out of control to something that is easily 
> manageable. If this turns out impossible after all,
> documenting why 
> would be a very good thing. Then the researchers can have
> another go at 
> it.

If you (not just Iljitsch, but anyone else as well) care AT ALL
about dealing with spam via protocols in your lifetime, you
really SHOULD be following the ASRG in IRTF. I've been somewhat
disoriented because we've been discussing an SMTP replacement in
the IETF while the ASRG in IRTF has been heavily focused on
mechanisms that work within an SMTP framework - seems backwards
to ME, but that's the way it's working.

ASRG isn't perfect, but the signal-to-noise ratio is a lot
higher, the "research" focus is a lot nearer-term than some of
the other IETF RGs, and it does have the advantage that
discussion of spam is ON TOPIC for that list. Vern Paxson may
hunt me down in Vienna for diverting traffic to ASRG, but ASRG
really DOES look like a place where something MIGHT happen.

As distinct from the IETG main discussion list. Oh, my bad, I'm
back to snippy again...

Spencer Dawkins

p.s. Anyone CAN request a BoF, you know. And I would think that
ASRG would be a reasonable place to look for accomplices for a
BoF, and for an eventual IETF WG. I'm not the Genius of IETF
Processes, but I have done two BoFs - if you still have
questions after reading
http://www.ietf.org/ietf/1bof-procedures.txt, please contact me
via private e-mail and I'd be glad to help.



From owner-ietf@ietf.org  Mon Jun  2 02:04:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17770
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 02:04:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MiCV-00071r-G3
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 01:49:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Mi95-0006xq-CL
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 01:46:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12754
	for <ietf@ietf.org>; Mon, 2 Jun 2003 01:46:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mi7M-0007U5-00
	for ietf@ietf.org; Mon, 02 Jun 2003 01:44:24 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mi7M-0007Tt-00
	for ietf@ietf.org; Mon, 02 Jun 2003 01:44:24 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h525mUx31560;
	Sun, 1 Jun 2003 22:48:30 -0700
Date: Sun, 1 Jun 2003 17:14:31 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <17923571043.20030601171431@brandenburg.com>
To: Spencer Dawkins <spencer_dawkins@yahoo.com>
CC: ietf@ietf.org
Subject: Re: DNS RMX RR draft
In-Reply-To: <20030601203600.89695.qmail@web10901.mail.yahoo.com>
References: <20030601203600.89695.qmail@web10901.mail.yahoo.com>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Spencer,

SD> Spencer, who feels for the ASRG if this quality of discussion
SD> DOES move to that mailing list, but maybe "They Were
SD> Expendable"...


Perhaps you have heard the story of an employee who moved to a different
company, thereby increasing the average quality in both the old and new
companies?

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




From owner-ietf@ietf.org  Mon Jun  2 02:53:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25936
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 02:53:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Mizn-0005c9-BE
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 02:40:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MivZ-0005a0-Aj
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 02:36:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25552
	for <ietf@ietf.org>; Mon, 2 Jun 2003 02:36:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mitl-0000Fu-00
	for ietf@ietf.org; Mon, 02 Jun 2003 02:34:25 -0400
Received: from laptop2.kurtis.autonomica.se ([192.71.80.74] helo=laptop2.local)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mitk-0000Fq-00
	for ietf@ietf.org; Mon, 02 Jun 2003 02:34:24 -0400
Received: from kurtis.pp.se (localhost [127.0.0.1])
	by laptop2.local (8.12.9/8.10.2) with ESMTP id h526aBLi001303;
	Mon, 2 Jun 2003 08:36:12 +0200 (CEST)
Date: Mon, 2 Jun 2003 08:36:07 +0200
Subject: Re: The utilitiy of IP is at stake here
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-43-1066639494"
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "'IETF'" <ietf@ietf.org>
To: <alh-ietf@tndh.net>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <02b001c32497$0c11a350$2a134104@eagleswings>
Message-Id: <7D79EBCF-94C4-11D7-8FD0-000393A638B2@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Sender: owner-ietf@ietf.org
Precedence: bulk

--Apple-Mail-43-1066639494
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit

>> How about the cost of legitimate emails that get filtered and never
>> read. Not everyone scans the list to check for false positives.
>
> In a major example of false positives, we already have examples of one
> real cost of spam. AOL (as one example of many) has declared ranges of
> IP addresses marked 'residential' as invalid for running a particular
> application. In this case SMTP, but which app is next? There is a 
> 'guilt
> by association' presumption here by the operations community, which 
> when
> carried into other applications results in substantially limited value
> in the core IP protocol.

I can see the operators POV. If you have no hammer, take bulldozer. 
Sort of works, doesn't look pretty but is fast. The cost of handling 
spam is huge and there isn't much else they can do.

OTOH, I do agree with you that this is a threat to IP. I know small 
ISPs in Sweden who filter out a number of applications such as Kazaa 
and certain on-line games "as they use way to much bandwidth". This is 
very dangerous.

- kurtis -

--Apple-Mail-43-1066639494
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-disposition: inline
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.2

iQA/AwUBPtrwWaarNKXTPFCVEQLJAQCg/g+4pvaEy+pxZU4huiF6rH2qYgMAoN1U
NL3EjMnC0IjafTqHnTHizJNP
=Y4z/
-----END PGP SIGNATURE-----

--Apple-Mail-43-1066639494--




From owner-ietf@ietf.org  Mon Jun  2 04:56:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28500
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 04:56:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Mkvt-0007c0-Hi
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 04:44:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MkrC-0007ZV-Gq
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 04:39:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28128
	for <ietf@ietf.org>; Mon, 2 Jun 2003 04:39:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MkpT-00011X-00
	for ietf@ietf.org; Mon, 02 Jun 2003 04:38:07 -0400
Received: from laptop2.kurtis.autonomica.se ([192.71.80.74] helo=laptop2.local)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MkpS-00011J-00
	for ietf@ietf.org; Mon, 02 Jun 2003 04:38:06 -0400
Received: from kurtis.pp.se (localhost [127.0.0.1])
	by laptop2.local (8.12.9/8.10.2) with ESMTP id h528dsLi001361;
	Mon, 2 Jun 2003 10:39:54 +0200 (CEST)
Date: Mon, 2 Jun 2003 10:39:50 +0200
Subject: Re: Last 7 days on the IETF list
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-46--1073420780"
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "Rob Austein" <sra+ietf@hactrn.net>, <ietf@ietf.org>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F848@server2000.arneill-py.sacramento.ca.us>
Message-Id: <C62DB6EB-94D5-11D7-8FD0-000393A638B2@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Sender: owner-ietf@ietf.org
Precedence: bulk

--Apple-Mail-46--1073420780
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable


On l=F6rdag, maj 31, 2003, at 06:12 Europe/Stockholm, Michel Py wrote:

>> Rob Austein wrote
>> Traffic statistics (as seen from my cave, your mileage
>> may vary) for the last seven days on the ietf@ietf.org
>> mailing list.
>
> Thanks for posting this. I was about to join another poster in saying
> that you should not have posted the bytes; however, on second thought,=20=

> I
> like seeing them in the table. Apparently there is a direct =
correlation
> between the bytes and the number of messages anyway. It is instructive
> to see the info.

It also (might) show that people are quoting excessively which makes=20
whatever point they where trying to make more or less impossible to=20
read. Unfortunately for the top ones the number of mails correlates to=20=

the number of bytes which says something else...

- kurtis -

--Apple-Mail-46--1073420780
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-disposition: inline
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.2

iQA/AwUBPtsNWKarNKXTPFCVEQJ1DwCgoR0SwngX/n1qBdyyhsbnUrHAD7kAoN/d
ZBPMyBkJKruNckCyVFvahP3U
=hkoe
-----END PGP SIGNATURE-----

--Apple-Mail-46--1073420780--




From owner-ietf@ietf.org  Mon Jun  2 15:53:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21513
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 15:53:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Mv9e-0006ig-Cg
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 15:39:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Mv6V-0006es-EJ
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 15:36:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21138
	for <ietf@ietf.org>; Mon, 2 Jun 2003 15:36:21 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mv4l-0005kC-00
	for ietf@ietf.org; Mon, 02 Jun 2003 15:34:35 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mv4l-0005k9-00
	for ietf@ietf.org; Mon, 02 Jun 2003 15:34:35 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h52JaFSH006935;
	Mon, 2 Jun 2003 15:36:15 -0400
Message-Id: <200306021936.h52JaFSH006935@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here 
In-Reply-To: Your message of "Sun, 01 Jun 2003 23:43:13 +0200."
             <0dca01c32886$cdbc3c20$0a00000a@atkielski.com> 
References: <Pine.LNX.4.33.0305311426550.16737-100000@egate.xpasc.com> <0cc201c327c1$b518d220$0a00000a@atkielski.com> <3ED94D1C.C94BDA21@earthlink.net> <0d1601c32815$6538a060$0a00000a@atkielski.com> <200306010931.h519VOn1005187@turing-police.cc.vt.edu>
            <0dca01c32886$cdbc3c20$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1239646597P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 02 Jun 2003 15:36:15 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sun, 01 Jun 2003 23:43:13 +0200, Anthony Atkielski <anthony@atkielski.com>  said:
> Valdis writes:
> 
> > The guys at LSoft Inc feel otherwise...
> 
> The guys at LSoft Inc are welcome to express themselves directly here.

*plonk*.  Solipsism has no place in protocol design.

> > That's *only* for LSoft's Listserv product, and
> > does *NOT* include all the intranet installs of
> > Listserv.
> 
> Two points: (1) you don't seem to be counting people subscribed to more than
> one list; and (2) how would spammers harvest from INTRANET installs of
> Listserv?

Granted, but since *your* claim is that most people don't do any mailing
lists, or very few, I'm not willing to concede any adjustment there.

Either you have 120M people each on one list, or most people are on more
than one - your choice.

> I'm subscribed to dozens of mailing lists, many administered by Listserv.
> Am I one person, or a hundred?

Again - when dealing with 120M subscriptions, you get the benefit of the
doubt here only if you are willing to stipulate that the *average* behavior
is different than what you said.  Sure, it's only 20M people(*) if the *average*
person is on 6 lists - but that's not the behavior you claimed is average.

> > I think we can conclude that a great many
> > Internet users *DO* participate in mailing lists.

> I think not, in part for reasons I've stated above.

/Valdis

(*) Feel free to work the exact number out for a Gaussian distrib around a
mean of 6 with different standard deviations if you want - we're talking
ballpark numbers here anyhow. ;)

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

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

iD8DBQE+26cucC3lWbTT17ARAug2AJ0fKBI800hpzvouM5Yr5FH+7aUdWgCeP2Z7
JW0wTVnoxDdHQQ0O8HElkPA=
=MPgp
-----END PGP SIGNATURE-----

--==_Exmh_-1239646597P--



From owner-ietf@ietf.org  Mon Jun  2 16:11:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22198
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 16:11:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MvSz-0007P9-Ox
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 15:59:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MvKk-0006q8-Bm
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 15:51:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21443
	for <ietf@ietf.org>; Mon, 2 Jun 2003 15:51:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MvJ0-0005og-00
	for ietf@ietf.org; Mon, 02 Jun 2003 15:49:18 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MvIz-0005oY-00
	for ietf@ietf.org; Mon, 02 Jun 2003 15:49:17 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h52Jp3Kk089714
	for <ietf@ietf.org>; Mon, 2 Jun 2003 21:51:03 +0200 (CEST)
Message-ID: <0e9b01c32940$4ca05e90$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.33.0305311426550.16737-100000@egate.xpasc.com> <0cc201c327c1$b518d220$0a00000a@atkielski.com> <3ED94D1C.C94BDA21@earthlink.net> <0d1601c32815$6538a060$0a00000a@atkielski.com> <200306010931.h519VOn1005187@turing-police.cc.vt.edu>            <0dca01c32886$cdbc3c20$0a00000a@atkielski.com> <200306021936.h52JaFSH006935@turing-police.cc.vt.edu>
Subject: Re: The utilitiy of IP is at stake here 
Date: Mon, 2 Jun 2003 21:51:03 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Valdis writes:

> Solipsism has no place in protocol design.

Not solipsism.  Just a reluctance to believe that you are an official--or
even an unofficial--spokesperson for LSoft.

> Granted, but since *your* claim is that most people
> don't do any mailing lists, or very few, I'm not
> willing to concede any adjustment there.

What you do or do not concede is of little import, since readers can draw
their own conclusions.

> Either you have 120M people each on one list,
> or most people are on more than one - your choice.

Or you may have 10 million people on an average of 12 lists, which seems
very plausible to me.

> Sure, it's only 20M people(*) if the *average*
> person is on 6 lists - but that's not the behavior
> you claimed is average.

I'd say that 95% or more of all Internet users are not subscribed to any
list at all.  Many of the remaining 5% are subscribed to many lists.

> (*) Feel free to work the exact number out for
> a Gaussian distrib around a mean of 6 with
> different standard deviations if you want -
> we're talking ballpark numbers here anyhow. ;)

I think my point is made without it.




From owner-ietf@ietf.org  Mon Jun  2 16:33:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22924
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 16:33:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Mvv9-00087Z-Uo
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 16:28:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MvgL-0007tj-Rw
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 16:13:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22404
	for <ietf@ietf.org>; Mon, 2 Jun 2003 16:13:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mvec-00063Q-00
	for ietf@ietf.org; Mon, 02 Jun 2003 16:11:38 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mveb-000636-00
	for ietf@ietf.org; Mon, 02 Jun 2003 16:11:37 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h52KFjx12346;
	Mon, 2 Jun 2003 13:15:45 -0700
Date: Mon, 2 Jun 2003 13:12:47 -0700
From: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <13695462427.20030602131247@brandenburg.com>
To: ietf@ietf.org
CC: Brian E Carpenter <brian@hursley.ibm.com>
Subject: Recruitment of Experimental SIRs
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

We'd like to run a proof-of-concept version of the Senior Internet
Reviewer (SIR) activity, prior to obtaining formal IETF "blessing" for
it.

The proposal is discussed in:

     <http://www.ietf.org/internet-drafts/draft-carpenter-solution-sirs-00.txt>

It recruits experienced IETF participants to provide additional and
iterative review to working group efforts.  The IETF community assigns
the status of SIR, but the working group recruits individual SIRs to do
reviews.

An experimental version of the service is at:

     <http://graybeards.net/sirs>

Anyone who is qualified to be a SIR, according to the objective
"bootstrapping" criteria in the proposal, should contact me to get
listed on the SIRS web page.

The objective are:

          *    all current IAB members

          *    all former IAB and IESG members, and former 
               WG Chairs, who the Secretariat can contact 
               and who are willing to serve

          *    all current MIB Doctors

          *    all members of existing IETF Directorates

          *    all authors of at least three RFCs, who the 
               Secretariat can contact and who are willing 
               to serve

Thanks.

d/

ps.  Suggestions for modifications to the proposal are still eagerly
sought.

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




From owner-ietf@ietf.org  Mon Jun  2 17:35:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25082
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 17:35:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MwiR-0000re-H7
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 17:19:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Mwe2-0000nN-KP
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 17:15:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24293
	for <ietf@ietf.org>; Mon, 2 Jun 2003 17:15:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MwcI-0006Wm-00
	for ietf@ietf.org; Mon, 02 Jun 2003 17:13:18 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MwcH-0006Wi-00
	for ietf@ietf.org; Mon, 02 Jun 2003 17:13:18 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S29EAC> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Mon, 02 Jun 2003 14:15:02 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Mon, 2 Jun 2003 14:15:03 -0700
Message-ID: <00da01c3294c$087deeb0$46124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-Reply-To: <9243960C-9473-11D7-9195-00039388672E@muada.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA25082

Iljitsch van Beijnum wrote:
> ...
> So I'll repeat myself: let's have an anti-spam BOF and hopefully and 
> anti-spam wg. First order of business for this wg: analyze the spam 
> problem and then see if mechanisms can be found to reduce the 
> amount of 
> spam by 1 - 2 orders of magnitude. After that, we can decide if it's 
> worth it to write a protocol and try to have it deployed.

I agree with the idea of a BOF, but 'anti-spam' is the wrong focus. Spam
is a social problem, not an engineering one. I contend that is why we
already have a research group dealing with it (social problems are
inherently difficult for engineers, thus requiring research to figure
out). Focus the group on a tangible engineering problem, deployable
authenticated email. Or as Vixie labeled the more generic, interpersonal
batch communication system. 

Tony




From owner-ietf@ietf.org  Mon Jun  2 18:28:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27707
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 18:28:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MxeT-0008Rb-2o
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 18:19:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MxeE-0008Kz-PZ
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 18:19:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27350
	for <ietf@ietf.org>; Mon, 2 Jun 2003 18:19:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MxcU-0006vl-00
	for ietf@ietf.org; Mon, 02 Jun 2003 18:17:34 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MxcU-0006vi-00
	for ietf@ietf.org; Mon, 02 Jun 2003 18:17:34 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 209069; Mon, 02 Jun 2003 17:18:51 -0500
Message-ID: <3EDBCD65.2060706@ehsco.com>
Date: Mon, 02 Jun 2003 17:19:17 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: alh-ietf@tndh.net
CC: ietf@ietf.org
Subject: Re: The utilitiy of IP is at stake here
References: <00da01c3294c$087deeb0$46124104@eagleswings>
In-Reply-To: <00da01c3294c$087deeb0$46124104@eagleswings>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 6/2/2003 4:15 PM Tony Hain wrote:

> I agree with the idea of a BOF, but 'anti-spam' is the wrong focus. Spam
> is a social problem, not an engineering one. I contend that is why we
> already have a research group dealing with it (social problems are
> inherently difficult for engineers, thus requiring research to figure
> out). Focus the group on a tangible engineering problem, deployable
> authenticated email. Or as Vixie labeled the more generic, interpersonal
> batch communication system. 

I agree that this is the right approach to pursue. In fact, I think we
could probably skip the BoF and start talking about that particular topic
immediately ("secure mail", not "anti-spam technologies", which is an
interesting research topic but is a dead-end outside negotiated usage
domains). All we probably need to get started is a mailing list, if
anybody feels like setting one up.

I would also _still_ like to see the I*** leadership fill the necessary
jurisdictional roles of liason, so that the current and future technical
mechanisms can be presented as hooks for the anti-spam legislation that is
needed to actually solve the social problem of spam.

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




From owner-ietf@ietf.org  Mon Jun  2 18:51:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28542
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 18:51:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MxuN-000103-T0
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 18:36:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Mxmf-0000bH-OX
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 18:28:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27697
	for <ietf@ietf.org>; Mon, 2 Jun 2003 18:28:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mxkv-00071C-00
	for ietf@ietf.org; Mon, 02 Jun 2003 18:26:17 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mxkv-000719-00
	for ietf@ietf.org; Mon, 02 Jun 2003 18:26:17 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h52MS3tU016242;
	Mon, 2 Jun 2003 18:28:03 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h52MS2gv016239;
	Mon, 2 Jun 2003 18:28:02 -0400
Date: Mon, 2 Jun 2003 18:28:02 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: RE: The utilitiy of IP is at stake here
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

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

    > 'anti-spam' is the wrong focus. Spam is a social problem, not an
    > engineering one.

Sorry, I don't agree with this logic: if it's valid, then why try to design
better locks, since theft is a social problem?

	Noel



From owner-ietf@ietf.org  Mon Jun  2 18:58:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28829
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 18:58:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19My7T-0001DH-SD
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 18:49:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Mxw6-00012e-ME
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 18:37:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28208
	for <ietf@ietf.org>; Mon, 2 Jun 2003 18:37:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MxuM-00078W-00
	for ietf@ietf.org; Mon, 02 Jun 2003 18:36:02 -0400
Received: from mallard.mail.pas.earthlink.net ([207.217.120.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MxuM-00078T-00
	for ietf@ietf.org; Mon, 02 Jun 2003 18:36:02 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by mallard.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19Mxvu-0001x4-00; Mon, 02 Jun 2003 15:37:39 -0700
Date: Mon, 2 Jun 2003 18:35:44 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: "spam is a social problem, not an engineering one"
Message-Id: <20030602183544.71da7ecb.moore@cs.utk.edu>
In-Reply-To: <00da01c3294c$087deeb0$46124104@eagleswings>
References: <9243960C-9473-11D7-9195-00039388672E@muada.com>
	<00da01c3294c$087deeb0$46124104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I agree with the idea of a BOF, but 'anti-spam' is the wrong focus. Spam
> is a social problem, not an engineering one. 

If by "social problem" you mean that it is a problem that results from human
behavior, like lack of a widespread social contract or failure to adhere to a
social contract for how to use email, I might agree.  But applying that term
doesn't help much.  Nor should it be taken to imply that there is not a
technical solution, or part of a solution, to the problem.  Traffic signals,
speed measuring radar, lojack, airport metal detectors, turnstiles, locks on
doors, and alarm systems are all technical approaches to social problems. 

Clearly, a lot of spam can be eliminated via technical mechanisms.  Social
and/or legal mechanisms might also help especially if they have technical
mechanisms to back make them more feasible (e.g. by making senders tracable
with less effort, and perhaps, by reducing the number of complaints that have
to be investigated).  Technical, social, and legal mechanisms all have
disadvantages and costs.  Often addressing a problem with a combination of
mechanisms yields a more acceptable solution than insisting on a single kind
of mechanism. 

> I contend that is why we
> already have a research group dealing with it (social problems are
> inherently difficult for engineers, thus requiring research to figure
> out). Focus the group on a tangible engineering problem, deployable
> authenticated email. Or as Vixie labeled the more generic, interpersonal
> batch communication system. 

If we are trying to solve the spam problem, we'll be disappointed if
'deployable authenticated mail' or 'interpersonal batch communication system'
doesn't solve that problem.   And as far as I can tell, neither one will.  We
need to understand the benefits and limitations of these approaches before we
invest a lot of work into them. 

What users seem to want is to be able to accept mail from anyone without much
or any sender-specific prior arrangement (because we want to avoid the hassles
of making such arrangements, and because sometimes it really is useful to get
mail from people we don't know yet), to send mail for free or extremely low
cost, and to not have our mailboxes cluttered up with messages we don't want
to see (or for that matter, viruses).  There are a lot of other constraints,
but these are the big ones.  It may not be possible to completely satisfy this
set of constraints, but it might be that a slightly different set of
constraints would be acceptable.  It might also be that different constraints
(with different results) are acceptable to different people.




From owner-ietf@ietf.org  Mon Jun  2 19:34:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29963
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 19:34:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19MyVg-0002GX-GF
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 19:14:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MySp-0002Do-2g
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 19:11:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29421
	for <ietf@ietf.org>; Mon, 2 Jun 2003 19:11:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MyR4-0007RT-00
	for ietf@ietf.org; Mon, 02 Jun 2003 19:09:50 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MyR3-0007RK-00
	for ietf@ietf.org; Mon, 02 Jun 2003 19:09:49 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h52N4DS27531
	for <ietf@ietf.org>; Mon, 2 Jun 2003 16:04:13 -0700
Date: Mon, 2 Jun 2003 16:04:12 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <3EDBCD65.2060706@ehsco.com>
Message-ID: <Pine.LNX.4.33.0306021554000.26569-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Mon, 2 Jun 2003, Eric A. Hall wrote:

>
> on 6/2/2003 4:15 PM Tony Hain wrote:
>
> > I agree with the idea of a BOF, but 'anti-spam' is the wrong focus. Spam
> > is a social problem, not an engineering one. I contend that is why we

...

> I agree that this is the right approach to pursue. In fact, I think we
> could probably skip the BoF and start talking about that particular topic
> immediately ("secure mail", not "anti-spam technologies", which is an

Anti-spam may be a tar baby and there is a demonstrated lack of ability on
the part of the recent participants in this discussion to even agree that
Spam is a serious problem, BUT without the mantra of being able to
evaluate all technology proposals in terms of how the proposal will help
reduce unsolicited bulk mail, the effort isn't worth pursuing.

Unless the result can be demonstrated to provide features which directly
reduce the ability of the spammers to send mail, Dave Crocker's prediction
of slow/non deployment will come to pass.

There will also be (a lot?) less interest in working on the protocols.


Dave Morris




From owner-ietf@ietf.org  Mon Jun  2 19:42:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00295
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 19:42:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Myp2-0002Qc-Jr
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 19:34:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MyVm-0002Gh-DA
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 19:14:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29456
	for <ietf@ietf.org>; Mon, 2 Jun 2003 19:14:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MyU2-0007SC-00
	for ietf@ietf.org; Mon, 02 Jun 2003 19:12:54 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MyU1-0007Rk-00
	for ietf@ietf.org; Mon, 02 Jun 2003 19:12:53 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h52NH2x22611;
	Mon, 2 Jun 2003 16:17:02 -0700
Date: Mon, 2 Jun 2003 16:14:06 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <60106341621.20030602161406@brandenburg.com>
To: "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr>
CC: "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: This IETF discussion list
In-Reply-To: <004901c32865$450e5140$3b00a8c0@tomson.be>
References: <004901c32865$450e5140$3b00a8c0@tomson.be>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tomson,

TEYf> Should this list be open to ANYbody (any curious/interested netizen), or
TEYf> limited to proven... well... specialists? experts?


1. write up a specification for list membership.

     a. provide a detailed, objective, basis for selecting participants.

     b. be careful to account for the history of serendipitous benefit
     with the policy of open participation.

2. recruit the community to support your specification.


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




From owner-ietf@ietf.org  Mon Jun  2 19:56:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00624
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 19:56:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Mz1n-0003Gk-OU
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 19:47:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Myuj-0002pV-SF
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 19:40:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00257
	for <ietf@ietf.org>; Mon, 2 Jun 2003 19:40:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mysz-0007ei-00
	for ietf@ietf.org; Mon, 02 Jun 2003 19:38:41 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Mysy-0007ef-00
	for ietf@ietf.org; Mon, 02 Jun 2003 19:38:40 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S29EE9> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Mon, 02 Jun 2003 16:40:26 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'J. Noel Chiappa'" <jnc@ginger.lcs.mit.edu>, <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Mon, 2 Jun 2003 16:40:23 -0700
Message-ID: <016c01c32960$56b1adb0$46124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-Reply-To: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA00624

J. Noel Chiappa wrote:
>     > 'anti-spam' is the wrong focus. Spam is a social problem, not an
>     > engineering one.
> 
> Sorry, I don't agree with this logic: if it's valid, then why 
> try to design better locks, since theft is a social problem?

You actually make my point since locks don't prevent theft, they simply
slow the perpetrator and provide an indication to everyone that there is
an attempt to keep things behind the lock private.  The point is the
IETF can't solve a social issue, but can provide a technology that may
deter some, though primarily allows the social management infrastructure
to take action. 

The IETF can build a technology (for the sake of discussion
'authenticated email'), that in turn can be a building block in the
social management attempt to control spam. By itself it will not prevent
receiving unwanted mail. Using it rather than the solicitation,
merchandizing, & titillation protocol is an indication that the mailbox
owner has an expectation of exercising controls. If we required the new
messaging system to accurately include the time at every hop (something
as simple as make NTP part of the implementation set), the basis for
legal records can be established. Couple the basic authenticated,
time-stamped message with existing or enhanced spam reporting
mechanisms, and the foundation for actionable social recourse is taking
shape. 

Are there other reasons for having authenticated, time-stamped email? I
am sure there are many, but the first I would like to see is the end to
the designation that a fax is acceptable legal evidence, while email is
not. Will an 'anti-spam' focused IETF wg provide that? Maybe by
accident, but not likely. Will an 'authenticated email' wg produce an
end to spam? Not initially, but like the lock, the result is a
technology that enables the social management sphere to accomplish the
greater goal.

Tony 




From owner-ietf@ietf.org  Mon Jun  2 20:54:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02006
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 20:54:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Mzul-0004B6-7Q
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 20:44:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MzrH-00047B-1q
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 20:40:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01722
	for <ietf@ietf.org>; Mon, 2 Jun 2003 20:40:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MzpW-0000Dy-00
	for ietf@ietf.org; Mon, 02 Jun 2003 20:39:10 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MzpW-0000Dv-00
	for ietf@ietf.org; Mon, 02 Jun 2003 20:39:10 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 209098 for ietf@ietf.org; Mon, 02 Jun 2003 19:40:27 -0500
Message-ID: <3EDBEE95.6050802@ehsco.com>
Date: Mon, 02 Jun 2003 19:40:53 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The utilitiy of IP is at stake here
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
In-Reply-To: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 6/2/2003 5:28 PM J. Noel Chiappa wrote:
>> From: "Tony Hain" <alh-ietf@tndh.net>
> 
>> 'anti-spam' is the wrong focus. Spam is a social problem, not an 
>> engineering one.
> 
> Sorry, I don't agree with this logic: if it's valid, then why try to
> design better locks, since theft is a social problem?

All human action (and crime especially) is a result of opportunity and
desire. Locks and other defenses are designed to impede opportunity, while
the law is supposed to restrain desire.

Most of us have the equivalent of locks already, either in the form of
blacklists, filters, whatever. Coming up with more of these is fine, but
those will only address the question of utility within certain scopes. By
the same measure, a lock on a barn door in an Iowa cornfield has different
utility than a lock on the door of a Porsche in a crowded ghetto (on the
Internet, of course, everybody is your roommate). Nobody makes a lock that
is deployable everywhere, and which cannot be easily circumvented by a
willing expert. There's no reason to believe that any particular anti-spam
"solution" is going to work any better.

Security cameras are another form of deterrant, and which work towards
reducing both the opportunity and the desire. Think of an authenticated
mail system as being analogous to security cameras. You will still want to
have the locks that are appropriate for your needs, but making the
presence of security cameras known is going to keep some people from
succumbing to the desire, while having the criminals on tape will prove
useful when they decide they want to get past the locks.

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




From owner-ietf@ietf.org  Mon Jun  2 21:15:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02407
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 21:15:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19N0Fc-0004lG-O4
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 21:06:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19N08Q-0004bc-Tw
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 20:58:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02152;
	Mon, 2 Jun 2003 20:58:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N06g-0000La-00; Mon, 02 Jun 2003 20:56:54 -0400
Received: from aragorn.bbn.com ([128.33.0.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N06g-0000LR-00; Mon, 02 Jun 2003 20:56:54 -0400
Received: from [10.1.71.70] (SSH.BBN.COM [192.1.50.70])
	by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id h530veD9028392;
	Mon, 2 Jun 2003 20:57:41 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@localhost
Message-Id: <p05210600bb019fe14d01@[10.1.71.70]>
In-Reply-To: <v04220812bafd86c6908a@[192.168.1.14]>
References: <114782448.1054159586@p3.JCK.COM> <g3fzmytgm3.fsf@sa.vix.com>
 <v04220802bafb769cd6b7@[192.168.1.14]>
 <p05100306bafd3c440103@[128.89.88.34]>
 <v04220812bafd86c6908a@[192.168.1.14]>
Date: Mon, 2 Jun 2003 20:49:17 -0400
To: Einar Stefferud <Steflist@thor.nma.com>, ietf@ietf.org
From: Stephen Kent <kent@bbn.com>
Subject: Re: requiring payment (was spam)
Cc: owner-ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
Sender: owner-ietf@ietf.org
Precedence: bulk

At 3:10 PM -0700 5/30/03, Einar Stefferud wrote:
>Pity the poor Zealot; who, when he loses sight of his objective,
>simply redoubles his efforts.
>
>For sure, do not let any new ideas leak into the IETF!
>
>Cheers...\Stef
>
>

Pity the poor fellow who ventures outside his realm of knowledge and 
then recommends dreck. New ideas ought not be confused with sound 
ideas. Those with no background in an area are easily impressed by 
the new, without benefit of the wisdom that comes from familiarity 
with knowledge of the old.

We can continue this repartee as long as you wish. I do have a day 
job, but debating with you represents such a slight diversion of 
effort ...


Steve



From owner-ietf@ietf.org  Mon Jun  2 21:35:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03090
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 21:35:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19N0XW-0005Hq-3s
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 21:24:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19N0Nu-0004qB-BN
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 21:14:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02395
	for <ietf@ietf.org>; Mon, 2 Jun 2003 21:14:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N0MA-0000QL-00
	for ietf@ietf.org; Mon, 02 Jun 2003 21:12:54 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19N0M9-0000QC-00
	for ietf@ietf.org; Mon, 02 Jun 2003 21:12:53 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h531Gwx27922;
	Mon, 2 Jun 2003 18:16:59 -0700
Date: Mon, 2 Jun 2003 18:14:02 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <99113537498.20030602181402@brandenburg.com>
To: "Tony Hain" <alh-ietf@tndh.net>
CC: ietf@ietf.org
Subject: Engineering to deal with the social problem of spam
In-Reply-To: <00da01c3294c$087deeb0$46124104@eagleswings>
References: <00da01c3294c$087deeb0$46124104@eagleswings>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony,


TH> I agree with the idea of a BOF, but 'anti-spam' is the wrong focus. Spam
TH> is a social problem, not an engineering one. I contend that is why we
TH> already have a research group dealing with it (social problems are
TH> inherently difficult for engineers, thus requiring research to figure
TH> out). Focus the group on a tangible engineering problem, deployable
TH> authenticated email. Or as Vixie labeled the more generic, interpersonal
TH> batch communication system. 

The example of theft vs. locks provides a good perspective on both the
truth of your observation and the necessity that we take (appropriate)
action.

The key insight that comes from saying "social problem" is not that we
should do nothing, but that we need to have a shared agreement on the
details of the problem and the level of protection required.  And we
need to respond to it with appropriate, but limited, changes.

We are all quite comfortable making a distinction between the protection
needed for a home vs. protection for a facility holding a nuclear bomb.
We even are reasonably comfortable distinguishing what is needed for a
home in a idyllic "safe" environment versus one in a strife-torn
hell-hole.

No one believes that a house lock keeps out all intruders, and indeed
some do get in. But we *do* believe that house locks reduce the threat
to a socially acceptable level.

We have no such clarity or consensus about spam.

Worse, we *all* are seriously ignorant about solutions. Anyone who says
that they know the magic fix is blowing smoke.

First of all, there is not yet any existence proof for the reduction of
spam. Some interventions have reduced some aspects of spam, but the
total size of the beast has only been growing, and rapidly. There is a
key lesson here and it is mostly missed. The lesson is that spammers are
adaptable and -- as is true for all security threats -- raising the bar
keeps out the riff-raff but the truly serious attackers will develop a
different technique. In the case of spam, those serious attackers have
disproportionate leverage, because their software can be used by
less-serious drones.

More importantly, by saying "social problem" we are correctly implying
social *complexity*. Messaging touches core aspects of social processes.

No one knows how to "engineer" one property of a complex social process
without accidentally impacting others. And they key import of the word
"accidentally" is that these unintended consequences are typically
undesired.

This does not mean we should do nothing. Nor does it mean that there
should be no technical interventions.

It *does* mean that we need to treat this as an incremental systems
change process.

It *does* mean that we will need multiple types of changes, not just one
cure-all.

It *does* mean that we should approach those changes very cautiously,
even experimentally.

The place to start is with a modest, objective, operationalizable
definition of the thing we all agree needs to be handled differently.
So, let's not worry about the all-encompassing definition of spam. Let's
just -- hah! "just" he said -- target a single type of spam that is
massive and is massively offensive.

My personal favorite definition, these days, is

   Unsolicited Bulk Mail (UBE)
   
("Commercial" is too constrained, for me. I do not care whether the
message asks me for money, my vote, my religious affiliation, or simply
wants to share a bit of personal silliness with me.  In other words, the
detail of the content is irrelevant to me.  It does not even need to be
soliciting.)

Not all unsolicited mail is bad.  Not all bulk mail is bad.  But the
combination is universally reviled.

So we then need to define unsolicited properly. We must make sure to
permit me to make contact with someone for the first time. Not all cold
calls are bad; in fact they are essential to many desirable aspects of
social intercourse. We need to make sure that we define "permission"
properly -- as a kind of opposite to unsolicited -- and so we can then
enjoy wonderful debates about details such as double opt-in. And so on.
Still, I think the question of "unsolicited" is well-enough understood
to make it possible to get community rough consensus on a technical
definition that the engineering community can work with.

And we need to define bulk properly. This will be difficult. If I send
an unsolicited message to 2 people, does it qualify? What about 10
people, 100, 1000? Why? Why not?

The problem, here, is that I believe the qualifier "bulk" captures an
essential aspect of the problematic mail, so we can't simply drop the
term or say "anything greater than one".  Worse, the instant we choose a
number, the spammers will simply send batches that are one addressee
fewer than that maximum.

For that matter, the number of addressees per message might not be a
useful attribute, as marketeers have become good at tailoring content to
individual recipients, thereby producing one addressee per message. So
"bulk" requires considering behavior across multiple postings. Oh boy...

And that's why this is a research topic, no matter how essential it is
to to engineer some mechanisms sooner rather than latter. Let's do the
engineering and deployment, and let's do it quickly, but let's
appreciate that it is really research.

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




From owner-ietf@ietf.org  Mon Jun  2 21:42:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03442
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 21:42:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19N0lH-0005mU-Jj
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 21:38:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19N0YH-0005Kv-EQ
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 21:25:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02725
	for <ietf@ietf.org>; Mon, 2 Jun 2003 21:25:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N0WX-0000Wi-00
	for ietf@ietf.org; Mon, 02 Jun 2003 21:23:37 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N0WW-0000WN-00
	for ietf@ietf.org; Mon, 02 Jun 2003 21:23:36 -0400
Received: from edison.cisco.com (edison.cisco.com [171.70.144.164])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h531OcU9020793;
	Mon, 2 Jun 2003 18:24:38 -0700 (PDT)
Received: from cisco.com (sjc-vpn2-17.cisco.com [10.21.112.17]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id SAA15040; Mon, 2 Jun 2003 18:24:38 -0700 (PDT)
Message-ID: <3EDBF8D5.1090701@cisco.com>
Date: Mon, 02 Jun 2003 18:24:37 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030529
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stephen Kent <kent@bbn.com>
CC: Einar Stefferud <Steflist@thor.nma.com>, ietf@ietf.org
Subject: Mailing list or bust (was Spam, nasty exchanges, and the like)
References: <114782448.1054159586@p3.JCK.COM> <g3fzmytgm3.fsf@sa.vix.com> <v04220802bafb769cd6b7@[192.168.1.14]> <p05100306bafd3c440103@[128.89.88.34]> <v04220812bafd86c6908a@[192.168.1.14]> <p05210600bb019fe14d01@[10.1.71.70]>
In-Reply-To: <p05210600bb019fe14d01@[10.1.71.70]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Can we please move along?  Does anyone care to start a mailing list for 
technical proposals?  If not, perhaps all of these debates are a waste 
of bandwidth?!

Eliot





From owner-ietf@ietf.org  Mon Jun  2 21:52:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03840
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 21:52:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19N0lI-0005nj-2b
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 21:38:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19N0dQ-0005Ms-Q4
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 21:30:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02917
	for <ietf@ietf.org>; Mon, 2 Jun 2003 21:30:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N0bg-0000ZX-00
	for ietf@ietf.org; Mon, 02 Jun 2003 21:28:56 -0400
Received: from [208.184.79.11] (helo=clint.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19N0bf-0000ZB-00
	for ietf@ietf.org; Mon, 02 Jun 2003 21:28:55 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by clint.songbird.com (8.11.6/8.11.6) with ESMTP id h531X5x28555
	for <ietf@ietf.org>; Mon, 2 Jun 2003 18:33:05 -0700
Date: Mon, 2 Jun 2003 18:30:09 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <33114504618.20030602183009@brandenburg.com>
To: ietf@ietf.org
Subject: Re: requiring payment (was spam)
In-Reply-To: <p05210600bb019fe14d01@[10\.1\.71\.70]>
References: <114782448.1054159586@p3.JCK.COM> <g3fzmytgm3.fsf@sa.vix.com>
 <v04220802bafb769cd6b7@[192.168.1.14]> <p05100306bafd3c440103@[128.89.88.34]>
 <v04220812bafd86c6908a@[192.168.1.14]> <p05210600bb019fe14d01@[10.1.71.70]>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



SK> We can continue this repartee as long as you wish. I do have a day


except that the exchange adds to already-problematic denial of service
attack on the list, by virtue of increasing the noise but not the
signal.

at the least, please take it offline.

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




From owner-ietf@ietf.org  Mon Jun  2 22:55:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04814
	for <ietf-web-archive@odin.ietf.org>; Mon, 2 Jun 2003 22:54:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19N1q0-0007Dq-4W
	for ietf-list@asgard.ietf.org; Mon, 02 Jun 2003 22:47:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19N1iK-0007AV-94
	for ietf@asgard.ietf.org; Mon, 02 Jun 2003 22:39:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04649
	for <ietf@ietf.org>; Mon, 2 Jun 2003 22:39:49 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N1gZ-00013c-00
	for ietf@ietf.org; Mon, 02 Jun 2003 22:38:04 -0400
Received: from h80ad263c.async.vt.edu ([128.173.38.60] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19N1gY-00013Z-00
	for ietf@ietf.org; Mon, 02 Jun 2003 22:38:03 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h532dhg6001490;
	Mon, 2 Jun 2003 22:39:43 -0400
Message-Id: <200306030239.h532dhg6001490@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Eliot Lear <lear@cisco.com>
Cc: ietf@ietf.org
Subject: Re: Mailing list or bust (was Spam, nasty exchanges, and the like) 
In-Reply-To: Your message of "Mon, 02 Jun 2003 18:24:37 PDT."
             <3EDBF8D5.1090701@cisco.com> 
References: <114782448.1054159586@p3.JCK.COM> <g3fzmytgm3.fsf@sa.vix.com> <v04220802bafb769cd6b7@[192.168.1.14]> <p05100306bafd3c440103@[128.89.88.34]> <v04220812bafd86c6908a@[192.168.1.14]> <p05210600bb019fe14d01@[10.1.71.70]>
            <3EDBF8D5.1090701@cisco.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1219255510P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 02 Jun 2003 22:39:42 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Mon, 02 Jun 2003 18:24:37 PDT, Eliot Lear said:
> Can we please move along?  Does anyone care to start a mailing list for 
> technical proposals?  If not, perhaps all of these debates are a waste 
> of bandwidth?!

asrg@ietf.org

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

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

iD8DBQE+3ApucC3lWbTT17ARArL8AJ4pJT6Pb08z6RmyeTSyLGpyc+9WJACgi+Yq
JjNntPNaAqYZWZHBjkiQ8hg=
=pilC
-----END PGP SIGNATURE-----

--==_Exmh_-1219255510P--



From owner-ietf@ietf.org  Tue Jun  3 00:58:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07434
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 00:58:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19N3f1-00009Z-8h
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 00:44:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19N3eh-00007i-D4
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 00:44:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07095
	for <ietf@ietf.org>; Tue, 3 Jun 2003 00:44:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N3cw-0001ZW-00
	for ietf@ietf.org; Tue, 03 Jun 2003 00:42:26 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19N3cw-0001ZT-00
	for ietf@ietf.org; Tue, 03 Jun 2003 00:42:26 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h534iCKk094539
	for <ietf@ietf.org>; Tue, 3 Jun 2003 06:44:12 +0200 (CEST)
Message-ID: <0f0901c3298a$c7602b20$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <016c01c32960$56b1adb0$46124104@eagleswings>
Subject: Re: The utilitiy of IP is at stake here
Date: Tue, 3 Jun 2003 06:44:12 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony writes:

> Are there other reasons for having authenticated,
> time-stamped email? I am sure there are many, but
> the first I would like to see is the end to the
> designation that a fax is acceptable legal evidence,
> while email is not.

Assuming this statement is true (and it seems to be), what is the key
difference between fax and e-mail that makes fax so much more cogent in
court?  Or is it purely an arbitrary decision?

I've always wondered why signatures of ink on paper are binding, whereas
digital signatures are not, even though digital signatures are literally
billions or trillions of times more difficult to forge.

E-mail can be easily forged, but then again, so can a fax.  So what's so
special about fax?





From owner-ietf@ietf.org  Tue Jun  3 01:02:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07631
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 01:02:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19N3of-0000Di-3r
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 00:54:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19N3iF-00009d-NA
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 00:47:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07155
	for <ietf@ietf.org>; Tue, 3 Jun 2003 00:47:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N3gV-0001aP-00
	for ietf@ietf.org; Tue, 03 Jun 2003 00:46:07 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19N3gU-0001aM-00
	for ietf@ietf.org; Tue, 03 Jun 2003 00:46:06 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h534lrKk094566
	for <ietf@ietf.org>; Tue, 3 Jun 2003 06:47:53 +0200 (CEST)
Message-ID: <0f1401c3298b$4b13fd20$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <114782448.1054159586@p3.JCK.COM> <g3fzmytgm3.fsf@sa.vix.com> <v04220802bafb769cd6b7@[192.168.1.14]> <p05100306bafd3c440103@[128.89.88.34]> <v04220812bafd86c6908a@[192.168.1.14]> <p05210600bb019fe14d01@[10.1.71.70]> <3EDBF8D5.1090701@cisco.com>
Subject: Re: Mailing list or bust (was Spam, nasty exchanges, and the like)
Date: Tue, 3 Jun 2003 06:47:53 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

You always have the delete key.

----- Original Message ----- 
From: "Eliot Lear" <lear@cisco.com>
To: "Stephen Kent" <kent@bbn.com>
Cc: "Einar Stefferud" <Steflist@thor.nma.com>; <ietf@ietf.org>
Sent: Tuesday, June 03, 2003 03:24
Subject: Mailing list or bust (was Spam, nasty exchanges, and the like)


> Can we please move along?  Does anyone care to start a mailing list for 
> technical proposals?  If not, perhaps all of these debates are a waste 
> of bandwidth?!
> 
> Eliot
> 
> 
> 
> 



From owner-ietf@ietf.org  Tue Jun  3 02:14:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20239
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 02:14:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19N4pZ-0001aY-Jx
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 01:59:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19N4n3-0001YF-5D
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 01:56:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08736
	for <ietf@ietf.org>; Tue, 3 Jun 2003 01:56:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N4lI-00023H-00
	for ietf@ietf.org; Tue, 03 Jun 2003 01:55:08 -0400
Received: from smtp013.mail.yahoo.com ([216.136.173.57])
	by ietf-mx with smtp (Exim 4.12)
	id 19N4lH-00023E-00
	for ietf@ietf.org; Tue, 03 Jun 2003 01:55:07 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 3 Jun 2003 05:56:54 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'Anthony Atkielski'" <anthony@atkielski.com>
Cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: Mailing list or bust (was Spam, nasty exchanges, and the like)
Date: Tue, 3 Jun 2003 07:56:44 +0200
Organization: Internet Society
Message-ID: <001701c32994$ed860db0$a700a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-reply-to: <0f1401c3298b$4b13fd20$0a00000a@atkielski.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The delete key is a workaround, not a solution.

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Anthony
Atkielski

You always have the delete key.

----- Original Message ----- 
From: "Eliot Lear" <lear@cisco.com>

> Can we please move along?  Does anyone care to start a mailing list 
> for
> technical proposals?  If not, perhaps all of these debates are a waste 
> of bandwidth?!
> 
> Eliot





From owner-ietf@ietf.org  Tue Jun  3 02:52:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21369
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 02:52:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19N5X6-0000AO-FP
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 02:44:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19N5Tg-00008A-18
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 02:41:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21273
	for <ietf@ietf.org>; Tue, 3 Jun 2003 02:40:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N5Rv-0002Wu-00
	for ietf@ietf.org; Tue, 03 Jun 2003 02:39:11 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19N5Ru-0002Wk-00
	for ietf@ietf.org; Tue, 03 Jun 2003 02:39:10 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h536euKk095481
	for <ietf@ietf.org>; Tue, 3 Jun 2003 08:40:56 +0200 (CEST)
Message-ID: <0f3601c3299b$16706440$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <001701c32994$ed860db0$a700a8c0@tomson.be>
Subject: Re: Mailing list or bust (was Spam, nasty exchanges, and the like)
Date: Tue, 3 Jun 2003 08:40:56 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> The delete key is a workaround, not a solution.

No, it is a solution.  I believe I've already explained how unreasonable it
is to expect the entire world to censor itself to match your preferences.
It's much more practical to simply ignore or delete what you don't want to
see.  Additionally, the latter solution does not impose your standards upon
anyone else.




From owner-ietf@ietf.org  Tue Jun  3 05:36:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24488
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 05:36:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19N7x9-0002Sw-Av
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 05:19:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19N7ui-0002Q9-MK
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 05:17:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24025
	for <ietf@ietf.org>; Tue, 3 Jun 2003 05:17:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N7sx-0003I4-00
	for ietf@ietf.org; Tue, 03 Jun 2003 05:15:15 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N7sw-0003Ht-00
	for ietf@ietf.org; Tue, 03 Jun 2003 05:15:14 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h539HZxS033211;
	Tue, 3 Jun 2003 11:17:40 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Tue, 3 Jun 2003 11:16:41 +0200
Subject: Re: Engineering to deal with the social problem of spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "Tony Hain" <alh-ietf@tndh.net>, ietf@ietf.org
To: Dave Crocker <dcrocker@brandenburg.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <99113537498.20030602181402@brandenburg.com>
Message-Id: <165F52C8-95A4-11D7-ADAB-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On dinsdag, jun 3, 2003, at 03:14 Europe/Amsterdam, Dave Crocker wrote:

> TH> I agree with the idea of a BOF, but 'anti-spam' is the wrong 
> focus. Spam
> TH> is a social problem, not an engineering one.

Ok, maybe the word "spam" is too overloaded to be useful in a technical 
discussion. However, it's always good to keep the customer experience 
in mind, and the customer experience is "I don't want all this spam".

> TH> Focus the group on a tangible engineering problem, deployable
> TH> authenticated email. Or as Vixie labeled the more generic, 
> interpersonal
> TH> batch communication system.

Just adding authentication only solves a very small part of the 
problem: we can then accurately whitelist known senders.

A new interpersonal batch communication system certainly sounds like a 
good idea. The problem with email is that it is incredibly ill-suited 
for transferring larger files. A new protocol should be able to do much 
better in this area. However, this doesn't have much to do with spam 
issues and might make the whole thing much more complex.

> No one believes that a house lock keeps out all intruders, and indeed
> some do get in. But we *do* believe that house locks reduce the threat
> to a socially acceptable level.

The trouble is that on the internet, you can go from house to house and 
try to break locks and nobody will stop you. In the real world, you 
wouldn't be able to do that for very long.

> First of all, there is not yet any existence proof for the reduction of
> spam. Some interventions have reduced some aspects of spam, but the
> total size of the beast has only been growing, and rapidly.

Which is kind of ironic because spammers are thereby creating their own 
tragedy of the commons. Spam is so much out of control that any 
individual spam isn't going to have much of a return, so they need to 
send out even more of it. And the volume of spam is becoming so painful 
that people are now seriously working at getting rid of spam. So far 
with limited success, but that will change one way or the other.

> There is a
> key lesson here and it is mostly missed. The lesson is that spammers 
> are
> adaptable

So let's show some adaptability of our own and plug those SMTP holes.

> So, let's not worry about the all-encompassing definition of spam. 
> Let's
> just -- hah! "just" he said -- target a single type of spam that is
> massive and is massively offensive.

> My personal favorite definition, these days, is

>    Unsolicited Bulk Mail (UBE)

> Not all unsolicited mail is bad.  Not all bulk mail is bad.  But the
> combination is universally reviled.

Completely agree.

> So we then need to define unsolicited properly. We must make sure to
> permit me to make contact with someone for the first time.

One way would be solicited == whitelisted. Remember that this is only 
necessary for bulk mail. So everyone would need to create a whitelist 
of all the mailinglists and newsletters they're subscribed to.

> And we need to define bulk properly. This will be difficult. If I send
> an unsolicited message to 2 people, does it qualify? What about 10
> people, 100, 1000? Why? Why not?

Why look at individual messages? How much non-bulk mail can someone 
possibly need to send? 10 messages per hour? 100? 1000?

> The problem, here, is that I believe the qualifier "bulk" captures an
> essential aspect of the problematic mail, so we can't simply drop the
> term or say "anything greater than one".  Worse, the instant we choose 
> a
> number, the spammers will simply send batches that are one addressee
> fewer than that maximum.

That's why it's important to look at ALL mail rather than just copies 
of one message. Spammers by now know how to make messages look 
different even though they're essentially identical.

Someone's "home MTA" sould be able to simply rate limit the number of 
messages an individual user gets to inject into the global email 
distribution system. Then all we need is a system to differentiate 
between trusted MTAs and rogue ones run by spammers.

> And that's why this is a research topic, no matter how essential it is
> to to engineer some mechanisms sooner rather than latter. Let's do the
> engineering and deployment, and let's do it quickly, but let's
> appreciate that it is really research.

I'm not convinced.




From owner-ietf@ietf.org  Tue Jun  3 06:44:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26174
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 06:44:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19N97f-0003Yt-D6
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 06:34:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19N93J-0003Vk-1f
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 06:30:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25823
	for <ietf@ietf.org>; Tue, 3 Jun 2003 06:29:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19N91Y-0003ow-00
	for ietf@ietf.org; Tue, 03 Jun 2003 06:28:12 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19N91X-0003ot-00
	for ietf@ietf.org; Tue, 03 Jun 2003 06:28:11 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h53ATwKk097234
	for <ietf@ietf.org>; Tue, 3 Jun 2003 12:29:58 +0200 (CEST)
Message-ID: <0f5001c329bb$14d125a0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <165F52C8-95A4-11D7-ADAB-00039388672E@muada.com>
Subject: Re: Engineering to deal with the social problem of spam
Date: Tue, 3 Jun 2003 12:29:57 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Iljitsch writes:

> The trouble is that on the internet, you can go
> from house to house and try to break locks and
> nobody will stop you. In the real world, you
> wouldn't be able to do that for very long.

Sure you could.  But locks break so easily in the real world that most
crooks don't have to bother.

> Spam is so much out of control that any individual
> spam isn't going to have much of a return, so they
> need to send out even more of it.

Since the cost of sending spam is negligeable, sending ten or fifteen
million more isn't likely to be much of a deterrent.

> So let's show some adaptability of our own and
> plug those SMTP holes.

Why does SMTP have "holes"?  It does what it is supposed to.  There isn't
any way to automatically recognize spam, since it looks just like any other
e-mail to a computer.

> Someone's "home MTA" sould be able to simply rate
> limit the number of messages an individual user gets
> to inject into the global email distribution system.

This assumes that the home MTA has an objective of limiting outgoing spam.
But ISPs used by spammers aren't likely to care what they send out, as long
as they pay their bills.




From owner-ietf@ietf.org  Tue Jun  3 08:01:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28221
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 08:01:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NAIE-0004eu-Fb
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 07:49:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NAFF-0004b9-9f
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 07:46:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27208
	for <ietf@ietf.org>; Tue, 3 Jun 2003 07:46:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NADU-0004Bq-00
	for ietf@ietf.org; Tue, 03 Jun 2003 07:44:36 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NADT-0004Bb-00
	for ietf@ietf.org; Tue, 03 Jun 2003 07:44:35 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP id A34ED62205
	for <ietf@ietf.org>; Tue,  3 Jun 2003 13:45:52 +0200 (CEST)
Date: Tue, 03 Jun 2003 13:45:52 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Complaint from John Klensin against Dean Anderson
Message-ID: <17800000.1054640752@askvoll.hjemme.alvestrand.no>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In mail to the IETF list on May 30, 15:04 -0400, John Klensin said:

> Indeed, I think it has gone on about long enough.  Harald, of whomever is
> responsible for the IETF list, Dean has repeatedly attempted to defame my
> character and experience, despite (and after) having been supplied ample
> detail to refute his claims, assumptions, and accusations (I will supply
> copies of the relevant correspondence to you on request).  That is
> against the rules for the IETF list as I understand them.  Would you
> please initiate the appropriate action to formally warn him and, if the
> practice persists, suspend posting rights?

In mail to the IETF list on May 30, 16:01 -0400, Dean Anderson said:

> I think that I am the one being defamed, since you repeated question my
> credibility while avoiding the question.
>
> And I also would like to initiate a formal complaint.

The IETF list charter, RFC 3005, says:

   Inappropriate postings include:

    - Unsolicited bulk e-mail
    - Discussion of subjects unrelated to IETF policy, meetings,
      activities, or technical concerns
    - Unprofessional commentary, regardless of the general subject
    - Announcements of conferences, events, or activities that are not
      sponsored or endorsed by the Internet Society or IETF.

Looking at the log of messages from Dean Anderson (yes, I have looked at 
all 64 that were sent by him this month):

- The first message by Dean Anderson that appears to be a reply to John 
Klensin appears on May 27, 20:15 -0400. It basically disputes John's claims 
about how email works.

- In his message on May 27, 22:40 -0400, he says:

> I think the same about you. It seems this will go nowhere. I'm just trying
> to be polite. You've offered absolutely nothing of substance in this
> -long- message.
....

> That is not the goal of open, standards compliant systems.  The fact is
> that these clients are compliant with standards in effect.  If you don't
> understand that, then you have no place in a standards organization, like
> the IETF.
.....

> This is just nonsense.  Obviously, you have no operational experience.

- In his message on May 29, 22:02 -0400, he says:


> Some people seem to think that having invented or significantly
> contributed to something means that the inventor is immune to criticism.
> That is called a personality cult. Personality cults usually have few
> useful contributions, because they distract the personality.  Maybe that
> is what happened to John with SMTP AUTH. I don't know.

- In his message on May 30, 14:09 -0400, he says:

> And John has obviously never been involved in a Law Enforcement request.
> But I have.  Private emails to him seem to confirm this, or at least he
> didn't indicate anything to the contrary.  While he may have been working
> on SMTP protocols for 30 years, he obviously hasn't been involved in
> trackig abuse of various sorts, and has no idea of whether this is
> expensive or difficult.

- In his message on May 30, 18:24 -0400, he says:

> What you wrote is rather condencending, while
> I have be respectful, if direct.
.....
> As I pointed out, previously. You are just
> repeating canards, rather than addressing the issue of relevance.

John Klensin's public note that refers specifically to Dean Anderson was 
sent on May 27 21:29 -0400:

> Since this is a response to a note I wrote, I'm going to try to respond
> to it.  Then I'm going to go back to deleting your mail without reading
> it, because it doesn't appear to me as if you really intend to
> participate in this discussion, rather than reciting your set of canards
> over and over again.   The opinion of others may differ, of course but,
> as far as I am concerned, you are succeeding in losing all credibility.

As moderator, I find Dean Anderson's repeated postings of his erroneous 
inferences with regard to John Klensin's experience, as well as his blanket 
statements about the IETF process ("you have no place in the IETF" and 
"personality cult") to be highly unprofessional.

(I also find his total number of postings excessive, but he has been warned 
about that already, and seems to have slowed down - only 5 messages over 
the last 3 days).

John's comment, on the other hand, seems carefully crafted to report only 
John's opinion on Dean Anderson's postings, not asserting some general 
truth about Dean. While this style may also easily be abused, it is clearly 
not as clear a breach of the guideline of professional commentary as Dean's 
is.

John: Take care.

Dean: You have been warned.

                   Harald Alvestrand
                   speaking as moderator of the IETF list





From owner-ietf@ietf.org  Tue Jun  3 09:23:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03577
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 09:23:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NBS4-0001m2-BD
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 09:03:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NAc3-0007KX-Ck
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 08:09:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28632
	for <ietf@ietf.org>; Tue, 3 Jun 2003 08:09:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NAaI-0004Re-00
	for ietf@ietf.org; Tue, 03 Jun 2003 08:08:10 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NAaH-0004RO-00
	for ietf@ietf.org; Tue, 03 Jun 2003 08:08:09 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 53C3F62205; Tue,  3 Jun 2003 14:09:27 +0200 (CEST)
Date: Tue, 03 Jun 2003 14:09:27 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Anthony Atkielski <anthony@atkielski.com>
Cc: ietf@ietf.org
Subject: Last warning: Please turn down the volume
Message-ID: <22820000.1054642167@askvoll.hjemme.alvestrand.no>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Anthony:
On Thursday, May 29, I sent you the following message:

> Over the last 3 days, you two have together contributed 88 messages to
> the IETF discussion list - an average of more than one message per hour,
> round the clock, just for the two of you.
>
> All of these seem to concern a topic that has been discussed many times
> on the IETF list before, with no apparent beneficial result, and for
> which there are other fora that welcome discussoin on the topic.
>
> Other participants have asked you to take the discussion elsewhere; even
> if the discussion were to remain on the list, your aggregated posting
> volume is well beyond the bounds of polite behaviour.
>
> Please desist.
>

Since then, you have contributed approximately 40 more messages to the 
list, or around 8 messages per day, contributing more than a sixth of the 
total list traffic in that interval.

This is the final (and public) warning.
Stop shouting.

                       Harald Alvestrand




From owner-ietf@ietf.org  Tue Jun  3 09:59:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04704
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 09:59:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NC4C-0004aO-5O
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 09:43:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NBzW-0004MN-0z
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 09:38:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04048
	for <ietf@ietf.org>; Tue, 3 Jun 2003 09:38:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NBxk-00061n-00
	for ietf@ietf.org; Tue, 03 Jun 2003 09:36:28 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NBxk-00061k-00
	for ietf@ietf.org; Tue, 03 Jun 2003 09:36:28 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h53DcFKk098745
	for <ietf@ietf.org>; Tue, 3 Jun 2003 15:38:15 +0200 (CEST)
Message-ID: <0f6201c329d5$62ac0780$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <22820000.1054642167@askvoll.hjemme.alvestrand.no>
Subject: Re: Last warning: Please turn down the volume
Date: Tue, 3 Jun 2003 15:38:15 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald writes:

> Since then, you have contributed approximately 40
> more messages to the list, or around 8 messages per
> day, contributing more than a sixth of the
> total list traffic in that interval.

So?

Try this:  Count all the personal attacks and irrelevant posts on this list
in the last 30 days, and rank participants by those.  I think you may be
surprised at the results.

> This is the final (and public) warning.
> Stop shouting.

Actually, looking at your previous post, which was little more than a
child's sandbox tirade against two other people on the list, I found it to
be a superlative example of the pot calling the kettle black--and it did
make me smile for that reason.  It also further reinforced my impression
that this list is a waste of time, because of the many kiddies who just
cannot refrain from bickering, whining, censoring, and attacking each other,
just as they seem to do on practically every other list, forum, and
newsgroup on the Net.  And when I see moderators jumping into the fray like
overzealous and woefully underqualified kindergarten teachers, I pretty much
am tempted to write the whole list off.

So do what you want.  I'm not profiting from this list, and it's pretty
clear that a lot of people here aren't grown up enough to profit from my own
contributions, so it makes no difference to me.

Incidentally, with lists like this so disproportionately populated by angry
young boys and their mental equivalents, it's easy to see why spammers are
doing so well.  I wonder sometimes why I waste my breath; but I suppose I'm
an incurable optimist at heart.




From owner-ietf@ietf.org  Tue Jun  3 11:18:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08867
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 11:18:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NDGP-0004VA-HT
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 10:59:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ND15-0004HY-IP
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 10:43:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07478
	for <ietf@ietf.org>; Tue, 3 Jun 2003 10:43:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NCzK-0006dJ-00
	for ietf@ietf.org; Tue, 03 Jun 2003 10:42:10 -0400
Received: from d235-158-148.home1.cgocable.net ([24.235.158.148] helo=dot-god.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NCzJ-0006dG-00
	for ietf@ietf.org; Tue, 03 Jun 2003 10:42:09 -0400
Received: from baptista (helo=localhost)
	by dot-god.com with local-esmtp (Exim 4.12)
	id 19ND1I-0000rg-00; Tue, 03 Jun 2003 10:44:12 -0400
Newsgroups: alt.fan.joe-baptista,alt.politics,soc.politics,can.politics,alt.journalism
Date: Tue, 3 Jun 2003 10:44:07 -0400 (EDT)
From: Joe Baptista <baptista@dot-god.com>
To: Johnmacsgroup <johnmacsgroup@yahoogroups.com>
cc: IETF <ietf@ietf.org>, Orange List <orange@vrx.net>,
        <Imc-montreal@lists.indymedia.org>,
        <Imc-montreal-tech@lists.indymedia.org>,
        <Imc-montreal-editorial@lists.indymedia.org>
Subject: Internet Voting and user participation systems - Research question
 from Baptista
Message-ID: <Pine.LNX.4.33.0306031032560.29512-100000@dot-god.com>
Organization: .GOD domains @ www.dot-god.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


Hi all:

I'm doing research on what is available with respect to web based (or
email) interfaces that support political participation at the grass roots
level (bottom up).  This includes voting and organizational systems or
user based communities.

Please email me back private - especially if your getting this message in
a newsgroup so i don't inadvertently miss it.

cheers
joe baptista

Joe Baptista - only at www.baptista.god

"Those are mercenaries. Most probably they will be treated as
mercenaries, hirelings and as war criminals. ... For sure,
international law does not apply to those"
 ... Muhammed Saeed al-Sahaf former Iraqi Information Minister





From owner-ietf@ietf.org  Tue Jun  3 11:18:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08916
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 11:18:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NDGQ-0004WF-Ob
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 10:59:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NDA7-0004Nf-O8
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 10:53:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07819
	for <ietf@ietf.org>; Tue, 3 Jun 2003 10:53:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ND8M-0006iG-00
	for ietf@ietf.org; Tue, 03 Jun 2003 10:51:30 -0400
Received: from mail14.speakeasy.net ([216.254.0.214] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ND8L-0006iD-00
	for ietf@ietf.org; Tue, 03 Jun 2003 10:51:29 -0400
Received: (qmail 12249 invoked from network); 3 Jun 2003 14:53:17 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail14.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <iljitsch@muada.com>; 3 Jun 2003 14:53:17 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Engineering to deal with the social problem of spam
Date: Tue, 3 Jun 2003 10:55:44 -0400
User-Agent: KMail/1.5
Cc: ietf@ietf.org
References: <165F52C8-95A4-11D7-ADAB-00039388672E@muada.com>
In-Reply-To: <165F52C8-95A4-11D7-ADAB-00039388672E@muada.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200306031055.45005.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum <iljitsch@muada.com> wrote:

 > The trouble is that on the internet, you can go from house to house
 > and try to break locks and nobody will stop you.

Actually, sometimes they will, or at least try to.  Port scans can be 
detected, both inbound and out, and Things Can Be Done....

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info




From owner-ietf@ietf.org  Tue Jun  3 11:28:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09571
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 11:28:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NDKw-0004hS-Hg
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 11:04:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NDBF-0004OY-2x
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 10:54:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07863
	for <ietf@ietf.org>; Tue, 3 Jun 2003 10:54:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ND9T-0006ir-00
	for ietf@ietf.org; Tue, 03 Jun 2003 10:52:39 -0400
Received: from mail11.speakeasy.net ([216.254.0.211] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ND9T-0006io-00
	for ietf@ietf.org; Tue, 03 Jun 2003 10:52:39 -0400
Received: (qmail 12268 invoked from network); 3 Jun 2003 14:54:26 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <iljitsch@muada.com>; 3 Jun 2003 14:54:26 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Engineering to deal with the social problem of spam
Date: Tue, 3 Jun 2003 10:56:54 -0400
User-Agent: KMail/1.5
Cc: ietf@ietf.org
References: <165F52C8-95A4-11D7-ADAB-00039388672E@muada.com>
In-Reply-To: <165F52C8-95A4-11D7-ADAB-00039388672E@muada.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200306031056.54853.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum <iljitsch@muada.com> wrote:

 > Someone's "home MTA" sould be able to simply rate limit the number
 > of messages an individual user gets to inject into the global email
 > distribution system. Then all we need is a system to differentiate
 > between trusted MTAs and rogue ones run by spammers.

Then we're back to Square One (okay, maybe Three) with blacklists and 
whitelists.  Not that throttling is itself a bad thing... I'd like to 
throttle some spammers....  ;->

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info




From owner-ietf@ietf.org  Tue Jun  3 11:31:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09787
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 11:31:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NDir-0006HJ-JC
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 11:29:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NDL9-0004iE-47
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 11:04:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08325
	for <ietf@ietf.org>; Tue, 3 Jun 2003 11:04:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NDJN-0006ps-00
	for ietf@ietf.org; Tue, 03 Jun 2003 11:02:53 -0400
Received: from mail11.speakeasy.net ([216.254.0.211] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NDJN-0006pp-00
	for ietf@ietf.org; Tue, 03 Jun 2003 11:02:53 -0400
Received: (qmail 19257 invoked from network); 3 Jun 2003 15:04:40 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <iljitsch@muada.com>; 3 Jun 2003 15:04:40 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: automagically whitelisting legit mailing lists
Date: Tue, 3 Jun 2003 11:07:08 -0400
User-Agent: KMail/1.5
Cc: ietf@ietf.org
References: <165F52C8-95A4-11D7-ADAB-00039388672E@muada.com>
In-Reply-To: <165F52C8-95A4-11D7-ADAB-00039388672E@muada.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200306031107.08627.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum <iljitsch@muada.com> wrote:

 > One way would be solicited == whitelisted. Remember that this is only
 > necessary for bulk mail. So everyone would need to create a whitelist
 > of all the mailinglists and newsletters they're subscribed to.

This could be eased somewhat with something I was trying to get at 
earlier.  This is separate from the idea of fixing or replacing SMTP, or 
other spamfighting, but what I envision is some standard format of data 
about a mailing list.  (MLML, for Mailing List Markup Language?)  Upon 
reading this in an email or on the web, the user can take some sort of 
action (click, reply, etc.), whereby he would be subscribed, and his MUA 
would whitelist the address the email would come from (or some other 
such tag, but usually the From addy so as to enable PGP-type 
authentication).  Something like:

<mailingList
 title="Dave's Demented Droppings"
 name="ddd"
 host="lists.example.com"
 whitelistHeader="X-Drivel"
 whitelistData="Two guys walk into a bar. A third one, ducks."
>
 My mailing list of occasional jokes, stories, and other alleged humor.
</mailingList>

Ideally, this would set off a confirmation process.  This introduces the 
possibility of whitelisting the addy that the confirmation request will 
come from, but if we establish a standard for transforming the listname 
and host to the various admin addies needed, those can be made optional.  
For instance, in the example above, I could have added 
owner="dave@lists.example.com", confirm="yesIWantDDD@lists.example.com", 
or both, or let them default to ddd-owner@lists.example.com and 
ddd-confirm@lists.example.com.  Similarly, there could be explicit or 
implicit URLs for subscription control (defaulting to something like 
"http://www.lists.example.com/ddd-control/", and including possibly that 
there are none for this list), and a standardized set of commands usable 
via email, and possibly a standard set of web-based controls.

Of course, we would quickly see spam in this format, but that's a whole 
different question.

A brief google doesn't turn up anything obviously relevant; anybody know 
of any work having been done in this area?

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info




From owner-ietf@ietf.org  Tue Jun  3 11:42:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10471
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 11:42:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NDiu-0006NJ-44
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 11:29:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NDZs-0005Yj-Mb
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 11:19:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09170
	for <ietf@ietf.org>; Tue, 3 Jun 2003 11:19:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NDY7-00071w-00
	for ietf@ietf.org; Tue, 03 Jun 2003 11:18:07 -0400
Received: from albatross.mail.pas.earthlink.net ([207.217.120.120])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NDY6-00071o-00
	for ietf@ietf.org; Tue, 03 Jun 2003 11:18:06 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by albatross.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19NDZE-0005Kw-00; Tue, 03 Jun 2003 08:19:16 -0700
Date: Tue, 3 Jun 2003 11:17:19 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Eliot Lear <lear@cisco.com>
Cc: moore@cs.utk.edu, kent@bbn.com, Steflist@thor.nma.com, ietf@ietf.org
Subject: Re: Mailing list or bust (was Spam, nasty exchanges, and the like)
Message-Id: <20030603111719.7c705167.moore@cs.utk.edu>
In-Reply-To: <3EDBF8D5.1090701@cisco.com>
References: <114782448.1054159586@p3.JCK.COM>
	<g3fzmytgm3.fsf@sa.vix.com>
	<v04220802bafb769cd6b7@[192.168.1.14]>
	<p05100306bafd3c440103@[128.89.88.34]>
	<v04220812bafd86c6908a@[192.168.1.14]>
	<p05210600bb019fe14d01@[10.1.71.70]>
	<3EDBF8D5.1090701@cisco.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Does anyone care to start a mailing list for 
> technical proposals?

the ASRG list already exists and is suitable for this purpose, and many
technical proposals have already been floated there.  what we're
doing here is educating people who can't be bothered to join that list.

and I agree we've done enough of it here.







From owner-ietf@ietf.org  Tue Jun  3 12:18:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12782
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 12:18:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NEOs-0000aD-Kd
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 12:12:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NEIi-0000Qy-O6
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 12:06:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12142
	for <ietf@ietf.org>; Tue, 3 Jun 2003 12:06:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NEGx-0007lV-00
	for ietf@ietf.org; Tue, 03 Jun 2003 12:04:27 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NEGw-0007lS-00
	for ietf@ietf.org; Tue, 03 Jun 2003 12:04:26 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h53G7DxS033852;
	Tue, 3 Jun 2003 18:07:13 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Tue, 3 Jun 2003 18:06:19 +0200
Subject: Re: Engineering to deal with the social problem of spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Dave Aronson <dja2003@hotpop.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200306031056.54853.dja2003@hotpop.com>
Message-Id: <505699C1-95DD-11D7-9CDE-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ok, my last message on the subject on this list (at least for a while).

On dinsdag, jun 3, 2003, at 16:56 Europe/Amsterdam, Dave Aronson wrote:

>> Someone's "home MTA" sould be able to simply rate limit the number
>> of messages an individual user gets to inject into the global email
>> distribution system. Then all we need is a system to differentiate
>> between trusted MTAs and rogue ones run by spammers.

> Then we're back to Square One (okay, maybe Three) with blacklists and
> whitelists.

Obviously black/whitelisting the MTAs you know is a good start. The 
challenge is doing something useful when you first encounter a new MTA. 
This can be done by asking such an unknown MTA to present a certificate 
that is signed by one or more people or organizations you trust.

This will make getting a new bona fide MTA up and running more 
difficult than it is now, but not to an unreasonable degree, IMO. 
Spammers on the other hand, will be unable to grab an address and start 
spamming immediately: they'll have to trick someone into validating 
their MTA. I'm sure they'll succeed in this from time to time, but not 
all the time, or people will simply ignore the naive validator. This 
should work especially well if validation depends on some real-life 
info: having to get a new (street) address or drivers license to be 
able to do a spam run should have a nice discouraging effect.




From owner-ietf@ietf.org  Tue Jun  3 12:55:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14160
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 12:55:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NEfq-0001eh-8n
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 12:30:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NEXA-0001OL-8a
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 12:21:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13081
	for <ietf@ietf.org>; Tue, 3 Jun 2003 12:21:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NEVO-0000CL-00
	for ietf@ietf.org; Tue, 03 Jun 2003 12:19:22 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NEVN-0000Bt-00
	for ietf@ietf.org; Tue, 03 Jun 2003 12:19:21 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h53GKP3I026921;
	Tue, 3 Jun 2003 09:20:29 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AES36614;
	Tue, 3 Jun 2003 09:20:24 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id JAA00699; Tue, 3 Jun 2003 09:20:24 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16092.51912.740900.110873@thomasm-u1.cisco.com>
Date: Tue, 3 Jun 2003 09:20:24 -0700 (PDT)
To: <alh-ietf@tndh.net>
Cc: "'J. Noel Chiappa'" <jnc@ginger.lcs.mit.edu>, <ietf@ietf.org>
Subject: authenticated email
In-Reply-To: <016c01c32960$56b1adb0$46124104@eagleswings>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
	<016c01c32960$56b1adb0$46124104@eagleswings>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony Hain writes:
 > Are there other reasons for having authenticated, time-stamped email? I
 > am sure there are many, but the first I would like to see is the end to
 > the designation that a fax is acceptable legal evidence, while email is
 > not. Will an 'anti-spam' focused IETF wg provide that? Maybe by
 > accident, but not likely. Will an 'authenticated email' wg produce an
 > end to spam? Not initially, but like the lock, the result is a
 > technology that enables the social management sphere to accomplish the
 > greater goal.

I, like you, suspect that authenticated email may
be helpful in the spam wars, but this must not be
viewed in isolation. "Authentication" begs the
question of identity, trust in assertion,
ownership of identity, and the motivation and
foibles of third parties who would likely be
needed to scale this to anything that would be
useful.

In particular, the latter is almost without
exception a "be careful for what you wish for"
situation. Centralization of power for naming and
thus participation would be a very convenient tool
to exclude undesirables. Today that's spammers,
but where are the checks and balances? What
prevents less worthy causes? How do you prevent an
unreasonable accrual of power made real by virtue
of being the path of least resistance for the
great unwashed masses?

Unless these issues -- and many more -- can be
finessed, the cure might be worse than the
disease.

	 Mike



From owner-ietf@ietf.org  Tue Jun  3 12:56:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14344
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 12:56:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NF0f-0001sy-1Q
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 12:51:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NEdU-0001WH-D5
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 12:27:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13298
	for <ietf@ietf.org>; Tue, 3 Jun 2003 12:27:41 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NEbi-0000GR-00
	for ietf@ietf.org; Tue, 03 Jun 2003 12:25:55 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NEbi-0000GO-00
	for ietf@ietf.org; Tue, 03 Jun 2003 12:25:54 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h53GRfaO002783;
	Tue, 3 Jun 2003 12:27:41 -0400
Message-Id: <200306031627.h53GRfaO002783@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: Dave Aronson <dja2003@hotpop.com>, ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam 
In-Reply-To: Your message of "Tue, 03 Jun 2003 18:06:19 +0200."
             <505699C1-95DD-11D7-9CDE-00039388672E@muada.com> 
References: <505699C1-95DD-11D7-9CDE-00039388672E@muada.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_638961904P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 03 Jun 2003 12:27:41 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Tue, 03 Jun 2003 18:06:19 +0200, Iljitsch van Beijnum said:

> all the time, or people will simply ignore the naive validator. This 
> should work especially well if validation depends on some real-life 
> info: having to get a new (street) address or drivers license to be 
> able to do a spam run should have a nice discouraging effect.

Street address validated how?  It's the rare ISP that double-checks an account
by snail-mailing information or calling the listed user's telephone number to
confirm.  Not that it would be a bad thing if all ISP's did this, but all
it takes is a few that don't, and the scheme falls apart...


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

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

iD8DBQE+3Mx8cC3lWbTT17ARAr+UAKCqaHudjRPNvebTVhGWkhvXFrXCRwCg6AvK
IBch24RDOim3IsWVNTnila0=
=uiYr
-----END PGP SIGNATURE-----

--==_Exmh_638961904P--



From owner-ietf@ietf.org  Tue Jun  3 13:04:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12784
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 12:18:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NEK0-0000U9-Pg
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 12:07:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NEA0-0008VF-9w
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 11:57:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11626
	for <ietf@ietf.org>; Tue, 3 Jun 2003 11:57:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NE8E-0007bv-00
	for ietf@ietf.org; Tue, 03 Jun 2003 11:55:26 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NE8D-0007bk-00
	for ietf@ietf.org; Tue, 03 Jun 2003 11:55:25 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 209197; Tue, 03 Jun 2003 10:56:37 -0500
Message-ID: <3EDCC548.3080607@ehsco.com>
Date: Tue, 03 Jun 2003 10:56:56 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Dave Aronson <dja2003@hotpop.com>
CC: Iljitsch van Beijnum <iljitsch@muada.com>, ietf@ietf.org
Subject: Re: automagically whitelisting legit mailing lists
References: <165F52C8-95A4-11D7-ADAB-00039388672E@muada.com> <200306031107.08627.dja2003@hotpop.com>
In-Reply-To: <200306031107.08627.dja2003@hotpop.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 6/3/2003 10:07 AM Dave Aronson wrote:
> Iljitsch van Beijnum <iljitsch@muada.com> wrote:
> 
>> One way would be solicited == whitelisted. Remember that this is only
>> necessary for bulk mail. So everyone would need to create a
>> whitelist of all the mailinglists and newsletters they're subscribed
>> to.
> 
> This could be eased somewhat with something I was trying to get at 
> earlier.  This is separate from the idea of fixing or replacing SMTP,
> or other spamfighting, but what I envision is some standard format of
> data about a mailing list.  (MLML, for Mailing List Markup Language?)
> Upon reading this in an email or on the web, the user can take some
> sort of action (click, reply, etc.), whereby he would be subscribed,
> and his MUA would whitelist the address the email would come from (or
> some other such tag, but usually the From addy so as to enable PGP-type
>  authentication).  Something like:

First point is that whitelisting should be one of the optional "locks"
which are enabled by architecture, rather than being core features of any
service. Whitelists don't work for everybody (customer service desks, for
example) so they need to be optional, and there are probably going to be a
variety of whitelisting "applications" (such as what you describe in your
detail) that embedding any of them would make it difficult to develop
alternative whitelisting applications.

For these kinds of reasons, it would be best to provide architecture (in
particular, providing authenticated identity and end-to-end option
encapsulation), and then people could use whatever mechanisms they want
(including hashcash, e-postage, whitelist negotiation, whatever) within
their own administrative space according to whatever works for them.

Whitelisting and mailing-list automation services would be two different
applications, I think, although they should be able to communicate with
each other for the kind of reasons you cite.

Anyway, the overall point is that we should separate the applications from
the message-transfer network architecture and develop them in parallel,
making sure that the architecture can provide what the applications need
for successful deployment.

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




From owner-ietf@ietf.org  Tue Jun  3 17:27:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25091
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 17:27:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NJ6w-0008Vr-W0
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 17:14:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NJ3i-0008S7-4h
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 17:11:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24835
	for <ietf@ietf.org>; Tue, 3 Jun 2003 17:11:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NJ1w-0002rv-00
	for ietf@ietf.org; Tue, 03 Jun 2003 17:09:16 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NJ1v-0002rS-00
	for ietf@ietf.org; Tue, 03 Jun 2003 17:09:15 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 967096257A; Tue,  3 Jun 2003 23:10:33 +0200 (CEST)
Date: Tue, 03 Jun 2003 23:10:33 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Tomson_Eric@Yahoo.fr, "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: This IETF discussion list
Message-ID: <69870000.1054674633@askvoll.hjemme.alvestrand.no>
In-Reply-To: <004901c32865$450e5140$3b00a8c0@tomson.be>
References:  <004901c32865$450e5140$3b00a8c0@tomson.be>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA25091



--On søndag, juni 01, 2003 19:43:04 +0200 "Tomson Eric (Yahoo.fr)" 
<Tomson_Eric@Yahoo.fr> wrote:

> By example, the more messages from A*** A*** I read, the more I think he
> is making statements of his own, without verification, without proof,
> without experience...
>
> Maybe this is due to a low technical knowledge? Or to a lack of valuable,
> proven information? (No offense. Just wondering...)
>
> Also remember J*** F*** and all his IPv8, IPv16,... stuff! Do such people
> just troll "for the pleasure", or are they convinced of what they state?
>
> I find it amusing that we discuss about SPAM, while we are victims of a
> kind of spamming! We are not even able to properly filter this list, and
> we think about preventing SPAM worlwide!
>
> Back to my first question. I don't say I know the answer. I don't say I
> have a solution. I'm just thinking, and sharing my thoughts with you all.

note that there's a document currently in Last Call that might be relevant:

> The IESG has received a request to consider A Practice for Revoking
> Posting Rights to IETF mailing lists <draft-mrose-ietf-posting-03.txt> as
> a BCP.  This has been reviewed in the IETF but is not the product of an
> IETF Working Group.
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-13.

Not much comment here so far.....

> Anyway, it must be difficult to be this list's moderator! :-/

the current moderator thinks that it's a job that needs a little more 
attention than he's currently giving it, and considering alternatives :-)




From owner-ietf@ietf.org  Tue Jun  3 17:41:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25571
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 17:41:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NJ6x-0008Vx-As
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 17:14:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NJ6c-0008St-89
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 17:14:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24911
	for <ietf@ietf.org>; Tue, 3 Jun 2003 17:14:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NJ4q-0002sz-00
	for ietf@ietf.org; Tue, 03 Jun 2003 17:12:16 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NJ4p-0002sp-00
	for ietf@ietf.org; Tue, 03 Jun 2003 17:12:15 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 591B06257A; Tue,  3 Jun 2003 23:13:32 +0200 (CEST)
Date: Tue, 03 Jun 2003 23:13:24 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Michael Thomas <mat@cisco.com>
Cc: ietf@ietf.org
Subject: Re: authenticated email
Message-ID: <70660000.1054674804@askvoll.hjemme.alvestrand.no>
In-Reply-To: <16092.51912.740900.110873@thomasm-u1.cisco.com>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
 <016c01c32960$56b1adb0$46124104@eagleswings>
 <16092.51912.740900.110873@thomasm-u1.cisco.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========1875089384=========="
Sender: owner-ietf@ietf.org
Precedence: bulk

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



--On tirsdag, juni 03, 2003 09:20:24 -0700 Michael Thomas <mat@cisco.com>=20
wrote:

> I, like you, suspect that authenticated email may
> be helpful in the spam wars, but this must not be
> viewed in isolation. "Authentication" begs the
> question of identity, trust in assertion,
> ownership of identity, and the motivation and
> foibles of third parties who would likely be
> needed to scale this to anything that would be
> useful.
>
> In particular, the latter is almost without
> exception a "be careful for what you wish for"
> situation. Centralization of power for naming and
> thus participation would be a very convenient tool
> to exclude undesirables. Today that's spammers,
> but where are the checks and balances? What
> prevents less worthy causes? How do you prevent an
> unreasonable accrual of power made real by virtue
> of being the path of least resistance for the
> great unwashed masses?
>
> Unless these issues -- and many more -- can be
> finessed, the cure might be worse than the
> disease.

I thought I'd try this....

is there any particular disadvantage or centralization of power implied in=20
me signing this message with my PGP key?

If not, is there any particular reason that I shouldn't do this all the=20
time?

It's not a solution, but is there a downside?

                  Harald Alvestrand, wondering.....

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

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

iD8DBQE+3Q98OMj+2+WY0F4RAspcAJ90hMmId91PtnYfYWgCTJ4EVD1OwwCfbbsK
Z7tegngfI3+B56QUXY9ONeQ=
=LUgX
-----END PGP SIGNATURE-----

--==========1875089384==========--




From owner-ietf@ietf.org  Tue Jun  3 17:47:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25895
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 17:47:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NJV9-0000m1-1W
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 17:39:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NJOX-0000bj-86
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 17:32:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25312
	for <ietf@ietf.org>; Tue, 3 Jun 2003 17:32:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NJMl-00030d-00
	for ietf@ietf.org; Tue, 03 Jun 2003 17:30:47 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NJMk-00030X-00
	for ietf@ietf.org; Tue, 03 Jun 2003 17:30:46 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA06364;
	Tue, 3 Jun 2003 17:27:44 -0400
Date: Tue, 3 Jun 2003 17:28:55 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: harald@alvestrand.no
cc: ietf@ietf.org
Subject: IETF Standards Process
Message-ID: <Pine.LNX.4.44.0306031553070.21528-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


You indicated that my criticism was incorrect regarding Mr. Klensin's
understanding of the standards process in regards to the description of
the current SMTP Standard.  So, now I am confused, and would like to learn
how to correctly evalute the status of IETF Standards.

The following question seems simple enough:

"What is the current standard level RFC describing the SMTP protocol?"

I see that RFC Index lists RFC 821 as being obsoleted by RFC 2821.

However, RFC 2821 status is "Proposed Standard", which is not a
standard-level RFC, according to the Standards Process documented in RFC
2026. Indeed, RFC 2821 was dated April 2001. Section 6.2 of RFC 2026
indicates:

When a standards-track specification has not reached the Internet
   Standard level but has remained at the same maturity level for
   twenty-four (24) months, and every twelve (12) months thereafter
   until the status is changed, the IESG shall review the viability of
   the standardization effort responsible for that specification and the
   usefulness of the technology. Following each such review, the IESG
   shall approve termination or continuation of the development effort,
   at the same time the IESG shall decide to maintain the specification
   at the same maturity level or to move it to Historic status.  This
   decision shall be communicated to the IETF by electronic mail to the
   IETF Announce mailing list to allow the Internet community an
   opportunity to comment. This provision is not intended to threaten a
   legitimate and active Working Group effort, but rather to provide an
   administrative mechanism for terminating a moribund effort.

I can find no reference that RFC2821 is a Standard, and it would seem that
it has remained at the same maturity level for 24 months or longer.
Thus, it seems to be appropriate that the IESG should review the viability
of the standardization effort, and decide if the effort should be
terminted or continued.

I also see that I am not the first to criticize the RFC 2821 effort
(http://cr.yp.to/smtp/klensin.html

I see that RFC 3300 indicates that RFC 821 is currently listed at STD 10.

How could RFC 821 be obsolete if it is STD 10?  Is this an error by the
RFC editor in the RFC Index?

I also note that RFC 3300 indicates a status change on RFC 2821 to
"proposed standard" by use of an asterisk. However the previous verions
(RFC 3000) indicates that RFC 2821 was in state "proposed standard" then
too. There seems to be no status change. Is this an error?  What was the
status change indicated in RFC 3300?

So, does that mean that I am wrong that RFC 821/STD 10 is the current
standard for SMTP?

It seems to me that RFC 2026 supports my view, that the current SMTP
Standard is RFC 821, though there are inconsistencies in the IETF process
documentation that might suggest or lead one to conclude otherwise.

I note that similar issues appear to exist with RFC 2554, but that is it
dated March 1999.

If these RFCs are not in fact Standard Level RFC's, it is inappropriate
for persons associated with the IETF to describe them as such, and
therefore this seems to be a violation of section 4 of RFC 3184, Code of
Conduct, for having not read the RFCs.  On the other hand, perhaps I have
missed something or otherwise misunderstood those RFCs, and am myself in
violation of section 4.  I seek guidance on this issue.

Thank you for your attention.

Dean Anderson
President, Av8 Internet, Inc





From owner-ietf@ietf.org  Tue Jun  3 18:29:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28071
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 18:29:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NK0r-00071V-Vb
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 18:12:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NJwN-0005aN-2A
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 18:07:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26851
	for <ietf@ietf.org>; Tue, 3 Jun 2003 18:07:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NJub-0003LC-00
	for ietf@ietf.org; Tue, 03 Jun 2003 18:05:45 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NJua-0003Kf-00
	for ietf@ietf.org; Tue, 03 Jun 2003 18:05:44 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA24603;
	Tue, 3 Jun 2003 17:59:36 -0400
Date: Tue, 3 Jun 2003 18:00:47 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: harald@alvestrand.no
cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: This IETF discussion list
In-Reply-To: <004901c32865$450e5140$3b00a8c0@tomson.be>
Message-ID: <Pine.LNX.4.44.0306031752071.21528-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


This message seems to be a violation of the IETF Code of Conduct (RFC
3184) sections 2.1 and 2.2:

   1. IETF participants extend respect and courtesy to their colleagues
      at all times.

      IETF participants come from diverse origins and backgrounds and
      are equipped with multiple capabilities and ideals.  Regardless of
      these individual differences, participants treat their colleagues
      with respect as persons--especially when it is difficult to agree
      with them.  Seeing from another's point of view is often
      revealing, even when it fails to be compelling.

   2. IETF participants develop and test ideas impartially, without
      finding fault with the colleague proposing the idea.

      We dispute ideas by using reasoned argument, rather than through
      intimidation or ad hominem attack.  Or, said in a somewhat more
      IETF-like way:

            "Reduce the heat and increase the light"

It is clearly not unreasonable to challenge someones claims, nor
respectfully challenge their anecdotal experiences, but intimidation and
ad hominem personal attacks are clearly inappropriate.

I ask the IETF Chair to take the appropriate action.



Dean Anderson
President, Av8 Internet, Inc

==================
Date: Fri, 30 May 2003 02:09:25 +0200
From: "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr>
To: 'Eric A. Hall' <ehall@ehsco.com>, 'John Stracke'
<jstracke@centive.com>
Cc: ietf@ietf.org
Subject: RE: spam

Guys,

Dean Anderson obviously supports and defends SPAM.
No further conversation with him could lead to anything constructive.
Stop feeding the Troll, now.

E.T.

====================


On Sun, 1 Jun 2003, Tomson Eric (Yahoo.fr) wrote:


> By example, the more messages from A*** A*** I read, the more I think he is
> making statements of his own, without verification, without proof, without
> experience...
>
> Maybe this is due to a low technical knowledge? Or to a lack of valuable,
> proven information? (No offense. Just wondering...)
>
> Also remember J*** F*** and all his IPv8, IPv16,... stuff! Do such people
> just troll "for the pleasure", or are they convinced of what they state?
>
> I find it amusing that we discuss about SPAM, while we are victims of a kind
> of spamming! We are not even able to properly filter this list, and we think
> about preventing SPAM worlwide!
>
> Back to my first question. I don't say I know the answer. I don't say I have
> a solution. I'm just thinking, and sharing my thoughts with you all.
>
> Anyway, it must be difficult to be this list's moderator! :-/
>
>
>
>






From owner-ietf@ietf.org  Tue Jun  3 18:37:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28365
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 18:37:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NKJK-0000PR-LN
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 18:31:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NKEH-0008Se-52
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 18:26:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27958
	for <ietf@ietf.org>; Tue, 3 Jun 2003 18:26:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NKCV-0003QZ-00
	for ietf@ietf.org; Tue, 03 Jun 2003 18:24:15 -0400
Received: from [64.70.31.5] (helo=www.darkuncle.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NKCU-0003QW-00
	for ietf@ietf.org; Tue, 03 Jun 2003 18:24:14 -0400
Received: from www.darkuncle.net (nibbles@localhost [127.0.0.1])
	by www.darkuncle.net (8.12.9/8.12.9) with ESMTP id h53MPoWq086619;
	Tue, 3 Jun 2003 15:25:50 -0700 (PDT)
	(envelope-from sfrancis@darkuncle.net)
Received: (from sfrancis@localhost)
	by www.darkuncle.net (8.12.9/8.12.9/Submit) id h53MPnNW086618;
	Tue, 3 Jun 2003 15:25:49 -0700 (PDT)
Date: Tue, 3 Jun 2003 15:25:49 -0700
From: Scott Francis <darkuncle@darkuncle.net>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: Michael Thomas <mat@cisco.com>, ietf@ietf.org
Subject: Re: authenticated email
Message-ID: <20030603222549.GU76028@darkuncle.net>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu> <016c01c32960$56b1adb0$46124104@eagleswings> <16092.51912.740900.110873@thomasm-u1.cisco.com> <70660000.1054674804@askvoll.hjemme.alvestrand.no>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="Qf/2YuBwNTyt+peV"
Content-Disposition: inline
In-Reply-To: <70660000.1054674804@askvoll.hjemme.alvestrand.no>
User-Agent: Mutt/1.3.25i
X-Operating-System: OpenBSD <http://www.openbsd.org>
X-PGP-Fingerprint: 7429 F75D D3F5 FA45 C6D7  D25B 59A0 7B8C 5537 F527
X-What-Happen: Somebody set up us the bomb.
Sender: owner-ietf@ietf.org
Precedence: bulk


--Qf/2YuBwNTyt+peV
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 03, 2003 at 11:13:24PM +0200, harald@alvestrand.no said:
[snip]
> >Unless these issues -- and many more -- can be
> >finessed, the cure might be worse than the
> >disease.
>=20
> I thought I'd try this....
>=20
> is there any particular disadvantage or centralization of power implied i=
n=20
> me signing this message with my PGP key?

not unless you consider the network of keyservers unduly centralized ...

> If not, is there any particular reason that I shouldn't do this all the=
=20
> time?

A small number of mail client/PGP combinations may not interoperate correct=
ly
with your particular mail client/PGP combination. However, that's certainly
no different (and considerably less widespread) than Outlook or other clien=
ts
sending all mail as HTML, which interoperates poorly with text-only clients.

(dead horse there, I know)

> It's not a solution, but is there a downside?

None that I have seen yet (except I'm realizing that either my passphrase is
too long, or the time period for which mutt caches it is too short). I'm su=
re
others will have different opinions though. Also, the debate between PGP/MI=
ME
and the older plaintext signatures is a well-worn one.

>                  Harald Alvestrand, wondering.....

--=20
Scott Francis || darkuncle (at) darkuncle (dot) net
      illum oportet crescere me autem minui

--Qf/2YuBwNTyt+peV
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+3SBtWaB7jFU39ScRAu6ZAJ9hc97zJ/lTAERyw1bkj91Ja4XWbACgk8Aw
vawdfLxHD/dxov3wDeykDjo=
=gGWI
-----END PGP SIGNATURE-----

--Qf/2YuBwNTyt+peV--



From owner-ietf@ietf.org  Tue Jun  3 19:18:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29476
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 19:18:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NKxJ-0001OZ-RJ
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 19:12:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NKoU-0001Ey-Gx
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 19:03:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29069
	for <ietf@ietf.org>; Tue, 3 Jun 2003 19:03:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NKmi-0003ga-00
	for ietf@ietf.org; Tue, 03 Jun 2003 19:01:40 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NKmh-0003gN-00
	for ietf@ietf.org; Tue, 03 Jun 2003 19:01:39 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h53N2rOo029345;
	Tue, 3 Jun 2003 16:02:54 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AES85200;
	Tue, 3 Jun 2003 16:02:52 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id QAA01129; Tue, 3 Jun 2003 16:02:52 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16093.10524.494835.396218@thomasm-u1.cisco.com>
Date: Tue, 3 Jun 2003 16:02:52 -0700 (PDT)
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: Michael Thomas <mat@cisco.com>, ietf@ietf.org
Subject: Re: authenticated email
In-Reply-To: <70660000.1054674804@askvoll.hjemme.alvestrand.no>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
	<016c01c32960$56b1adb0$46124104@eagleswings>
	<16092.51912.740900.110873@thomasm-u1.cisco.com>
	<70660000.1054674804@askvoll.hjemme.alvestrand.no>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald Tveit Alvestrand writes:
 > 
 > 
 > --On tirsdag, juni 03, 2003 09:20:24 -0700 Michael Thomas <mat@cisco.com> 
 > wrote:
 > 
 > > I, like you, suspect that authenticated email may
 > > be helpful in the spam wars, but this must not be
 > > viewed in isolation. "Authentication" begs the
 > > question of identity, trust in assertion,
 > > ownership of identity, and the motivation and
 > > foibles of third parties who would likely be
 > > needed to scale this to anything that would be
 > > useful.
 > >
 > > In particular, the latter is almost without
 > > exception a "be careful for what you wish for"
 > > situation. Centralization of power for naming and
 > > thus participation would be a very convenient tool
 > > to exclude undesirables. Today that's spammers,
 > > but where are the checks and balances? What
 > > prevents less worthy causes? How do you prevent an
 > > unreasonable accrual of power made real by virtue
 > > of being the path of least resistance for the
 > > great unwashed masses?
 > >
 > > Unless these issues -- and many more -- can be
 > > finessed, the cure might be worse than the
 > > disease.
 > 
 > I thought I'd try this....
 > 
 > is there any particular disadvantage or centralization of power implied in 
 > me signing this message with my PGP key?
 > 
 > If not, is there any particular reason that I shouldn't do this all the 
 > time?
 > 
 > It's not a solution, but is there a downside?

It depends on what you mean by signing. Signing a
message in and of itself ought not hurt anything
modulo software bugs, etc. But the real question
is what does the receiving program (MTA, MUA) do
with that signature? At the very least it could
verify the signature, but then what? If it doesn't
verify do you drop it? (transitive trust comes
into play, but most likely). Does it do anything
beyond that?

Let me ask something in return: do you think that
just the act of signing mail -- with no trust
roots implied -- could help? My sense is that it
might in a sow-the-seeds kind of way for some
later goodness (it's as you say not a solution).
I too would be happy to hear downsides.

      Mike



From owner-ietf@ietf.org  Tue Jun  3 20:55:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01980
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 20:55:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NMSp-0002sQ-Cx
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 20:49:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NMIG-0002lV-SS
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 20:38:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01594
	for <ietf@ietf.org>; Tue, 3 Jun 2003 20:38:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NMGU-0004Ov-00
	for ietf@ietf.org; Tue, 03 Jun 2003 20:36:30 -0400
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=localhost)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NMGG-0004MM-00
	for ietf@ietf.org; Tue, 03 Jun 2003 20:36:17 -0400
Received: by localhost (Postfix, from userid 501)
	id D8C6D4B69A; Wed,  4 Jun 2003 12:19:41 +1200 (FJT)
Subject: Re: authenticated email
From: Franck Martin <franck@sopac.org>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: Michael Thomas <mat@cisco.com>, ietf@ietf.org
In-Reply-To: <70660000.1054674804@askvoll.hjemme.alvestrand.no>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
	 <016c01c32960$56b1adb0$46124104@eagleswings>
	 <16092.51912.740900.110873@thomasm-u1.cisco.com>
	 <70660000.1054674804@askvoll.hjemme.alvestrand.no>
Content-Type: multipart/alternative; boundary="=-M4tKSvA2K/fmLPPunf1D"
Organization: SOPAC
Message-Id: <1054685981.2669.7.camel@localhost>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2-3mdk 
Date: 04 Jun 2003 12:19:41 +1200
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-M4tKSvA2K/fmLPPunf1D
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

I have tried both s/mime and pgp, well in fact still trying to use pgp.

The main problem is an implementation problem, where a bad and popular
version of Outlook was crashing when trying to verify the signature.

Now it all comes down to a global PKI, be it SSL/TLS or PGP. PGP has got
it running at an individual user level with the www.keyservers.net but
for TLS NO CA will deliver a certificate that can sign other
certificates (corporate e-mail certificates). I think there are some
attempt to do that...

If you look back on this list you will see a thread called GLOBAL PKI
where there was a lot of discussion at the time...

For spamming having signed e-mail is good as you can trace back
(traceability). But are you responsible when a virus on your computer
sends signed e-mail with a virus attachment.

At a SPAM meeting before INET2002 a company talked about certifying
advert....

Well all the options are open, but going to have a mainstream digital
signature is the goal...

Cheers
Franck

On Wed, 2003-06-04 at 09:13, Harald Tveit Alvestrand wrote: 

> I thought I'd try this....
> 
> is there any particular disadvantage or centralization of power implied in 
> me signing this message with my PGP key?
> 
> If not, is there any particular reason that I shouldn't do this all the 
> time?
> 
> It's not a solution, but is there a downside?
> 
>                   Harald Alvestrand, wondering.....




-- 

Franck Martin <franck@sopac.org>

SOPAC

--=-M4tKSvA2K/fmLPPunf1D
Content-Type: text/html; charset=utf-8

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/1.1.8">
</HEAD>
<BODY>
I have tried both s/mime and pgp, well in fact still trying to use pgp.<BR>
<BR>
The main problem is an implementation problem, where a bad and popular version of Outlook was crashing when trying to verify the signature.<BR>
<BR>
Now it all comes down to a global PKI, be it SSL/TLS or PGP. PGP has got it running at an individual user level with the <A HREF="http://www.keyservers.net">www.keyservers.net</A> but for TLS NO CA will deliver a certificate that can sign other certificates (corporate e-mail certificates). I think there are some attempt to do that...<BR>
<BR>
If you look back on this list you will see a thread called GLOBAL PKI where there was a lot of discussion at the time...<BR>
<BR>
For spamming having signed e-mail is good as you can trace back (traceability). But are you responsible when a virus on your computer sends signed e-mail with a virus attachment.<BR>
<BR>
At a SPAM meeting before INET2002 a company talked about certifying advert....<BR>
<BR>
Well all the options are open, but going to have a mainstream digital signature is the goal...<BR>
<BR>
Cheers<BR>
Franck<BR>
<BR>
On Wed, 2003-06-04 at 09:13, Harald Tveit Alvestrand wrote: 
<BLOCKQUOTE TYPE=CITE>
<PRE><FONT COLOR="#737373" SIZE="3"><I>I thought I'd try this....

is there any particular disadvantage or centralization of power implied in 
me signing this message with my PGP key?

If not, is there any particular reason that I shouldn't do this all the 
time?

It's not a solution, but is there a downside?

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Harald Alvestrand, wondering.....</I></FONT></PRE>
</BLOCKQUOTE>
<BR>
<PRE><TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
</TR>
<TR>
</TR>
<TR>
<TD>
<BR>
-- <BR>
<BR>
Franck Martin &lt;<A HREF="mailto:franck@sopac.org">franck@sopac.org</A>&gt;<BR>
<BR>
SOPAC
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-M4tKSvA2K/fmLPPunf1D--



From owner-ietf@ietf.org  Tue Jun  3 21:07:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02337
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 21:07:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NMfi-0003Mp-Bc
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 21:02:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NMXq-0002yi-OL
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 20:54:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01958
	for <ietf@ietf.org>; Tue, 3 Jun 2003 20:54:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NMW4-0004VR-00
	for ietf@ietf.org; Tue, 03 Jun 2003 20:52:36 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NMW3-0004VM-00
	for ietf@ietf.org; Tue, 03 Jun 2003 20:52:35 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S2A084> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 03 Jun 2003 17:54:22 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'Dave Crocker'" <dcrocker@brandenburg.com>
Cc: <ietf@ietf.org>
Subject: RE: Engineering to deal with the social problem of spam
Date: Tue, 3 Jun 2003 17:54:09 -0700
Message-ID: <01d701c32a33$cf24f3f0$46124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-Reply-To: <165F52C8-95A4-11D7-ADAB-00039388672E@muada.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA02337

Iljitsch van Beijnum wrote:
> Just adding authentication only solves a very small part of the 
> problem: we can then accurately whitelist known senders.

Two points:
1) besides white listing, the approach also provides irrefutable
evidence to law enforcement about spam sources.
2) it is clear from the related threads that many would rather continue
the lively exchange debating nirvana, rather than tackle the small parts
of the problem that are technically achievable.

> 
> A new interpersonal batch communication system certainly 
> sounds like a 
> good idea. The problem with email is that it is incredibly ill-suited 
> for transferring larger files. A new protocol should be able 
> to do much 
> better in this area. However, this doesn't have much to do with spam 
> issues and might make the whole thing much more complex.

We can always make it more complex than necessary, but it is pointless
to compare the complexity of a new system that does the job with a
system that is proven to be open to abuse. 

> 
> > No one believes that a house lock keeps out all intruders, 
> and indeed 
> > some do get in. But we *do* believe that house locks reduce 
> the threat 
> > to a socially acceptable level.
> 
> The trouble is that on the internet, you can go from house to 
> house and 
> try to break locks and nobody will stop you. In the real world, you 
> wouldn't be able to do that for very long.

Adopt draft-hain-ipv6-pi* as the standard addressing plan, provide
automated intrusion detection reporting, and Internet prowlers wouldn't
be able to attack for very long either.

> So let's show some adaptability of our own and plug those SMTP holes.

Or simply leave SMTP to the spammers and move on.

> Why look at individual messages? How much non-bulk mail can someone 
> possibly need to send? 10 messages per hour? 100? 1000?

@ 5kB/message on a 10MB/sec link, 2k/sec. 

> That's why it's important to look at ALL mail rather than just copies 
> of one message. Spammers by now know how to make messages look 
> different even though they're essentially identical.

Exactly how would you coorelate email across multiple accounts, on
multiple service providers?

> 
> Someone's "home MTA" sould be able to simply rate limit the number of 
> messages an individual user gets to inject into the global email 
> distribution system. Then all we need is a system to differentiate 
> between trusted MTAs and rogue ones run by spammers.

Why would a spammer limit themselves to a single MTA, or account. Run
VMware on a laptop, and there could easliy be 10 parallel rate-limited
sessions going on. If the rates are low enough, each virtual system
could automatically log into another account on another MTA, then come
back when the timer goes off. 

Tony




From owner-ietf@ietf.org  Tue Jun  3 21:11:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02574
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 21:11:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NMfi-0003Mv-Kv
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 21:02:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NMXq-0002yj-Py
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 20:54:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01961
	for <ietf@ietf.org>; Tue, 3 Jun 2003 20:54:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NMW4-0004VU-00
	for ietf@ietf.org; Tue, 03 Jun 2003 20:52:36 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NMW3-0004VN-00
	for ietf@ietf.org; Tue, 03 Jun 2003 20:52:35 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S2A085> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 03 Jun 2003 17:54:22 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Anthony Atkielski'" <anthony@atkielski.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: The utilitiy of IP is at stake here
Date: Tue, 3 Jun 2003 17:54:09 -0700
Message-ID: <01d801c32a33$cf947ea0$46124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-Reply-To: <0f0901c3298a$c7602b20$0a00000a@atkielski.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Anthony Atkielski wrote:
> ... 
> I've always wondered why signatures of ink on paper are 
> binding, whereas digital signatures are not, even though 
> digital signatures are literally billions or trillions of 
> times more difficult to forge.
> 
> E-mail can be easily forged, but then again, so can a fax.  
> So what's so special about fax?

I really don't know, maybe one of the armature lawyers will enlighten
us. My perception is that it is derived from the physical paper
evidence, and that forging email is so simple for Joe-sixpack that
everyone knows not to trust it. 

Tony




From owner-ietf@ietf.org  Tue Jun  3 21:16:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02762
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 21:16:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NMfi-0003N1-VA
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 21:02:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NMXr-0002ym-6i
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 20:54:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01966
	for <ietf@ietf.org>; Tue, 3 Jun 2003 20:54:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NMW5-0004Vb-00
	for ietf@ietf.org; Tue, 03 Jun 2003 20:52:37 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NMW4-0004VO-00
	for ietf@ietf.org; Tue, 03 Jun 2003 20:52:36 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S2A086> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 03 Jun 2003 17:54:23 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dave Crocker'" <dcrocker@brandenburg.com>
Cc: <ietf@ietf.org>
Subject: RE: Engineering to deal with the social problem of spam
Date: Tue, 3 Jun 2003 17:54:09 -0700
Message-ID: <01d901c32a33$d017df70$46124104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-Reply-To: <99113537498.20030602181402@brandenburg.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA02762

Dave Crocker wrote:
> ...
> This does not mean we should do nothing. Nor does it mean 
> that there should be no technical interventions.
> 
> It *does* mean that we need to treat this as an incremental 
> systems change process.
> 
> It *does* mean that we will need multiple types of changes, 
> not just one cure-all.
> 
> It *does* mean that we should approach those changes very 
> cautiously, even experimentally.

I am with you up to here, with the comment that any modification to
production services need to be approached incrementally, but new
services can be radical as long as they are deployed in parallel. 

> 
> The place to start is with a modest, objective, 
> operationalizable definition of the thing we all agree needs 
> to be handled differently. 

We agree with the wording of this, but it looks like at this point we
disagree about what should be changed.

> So, let's not worry about the 
> all-encompassing definition of spam. 
> ... 
> In other words, the detail of the content 
> is irrelevant to me.  It does not even need to be
> soliciting.)
> 

I agree completely with these points.

At this point your thoughts appear to drop into the trap of trying to
engineer a solution to the social problem, even though earlier you noted
we don't know how to engineer solutions to complex social problems. 

> ...
> For that matter, the number of addressees per message might 
> not be a useful attribute, as marketeers have become good at 
> tailoring content to individual recipients, thereby producing 
> one addressee per message. So "bulk" requires considering 
> behavior across multiple postings. Oh boy...

And if they spread the individual messages across multiple relays, using
multiple accounts, there is no chance to correlate postings. This shows
that even by your own account of ignoring content, there is no technical
way to stop even the simple case of unsolicited bulk mail. 

> 
> And that's why this is a research topic, no matter how 
> essential it is to to engineer some mechanisms sooner rather 
> than latter. Let's do the engineering and deployment, and 
> let's do it quickly, but let's appreciate that it is really research.

We agree that engineering automated solutions to social problems is a
research topic, and the IETF is not the place to do that work.
Engineering tools that are useful to existing social management agencies
is not research and something that the IETF can take on. Deployment of
experimental technologies is necessary, and something that should begin
ASAP. IMHO where we need to start is agreeing that the greater goal is
reduction of spam, that we don't know of any way to automate the
identification of billions of independent individual value decisions,
that trying to do so at this point is a waste of time, and that existing
social management agencies need tools to deal with the issue. 

I would like to see the outcome of a bof be identification of an
approach to globally verifiable authenticated email. I have no doubt
there will be many gaps in our current tool set (starting with a
deployable PKI), and a truck load of operational guidelines to develop.
This is something tangible we can do without extended research. If the
research community comes up with a breakthrough and figures out another
way to kill off spammers, authenticated email will still be useful as a
replacement for the current legal requirements for fax.

Tony





From owner-ietf@ietf.org  Tue Jun  3 22:12:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04238
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 22:12:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NNTt-0005EE-1A
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 21:54:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NNSX-0005AO-O3
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 21:53:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03739
	for <ietf@ietf.org>; Tue, 3 Jun 2003 21:52:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NNQl-00055V-00
	for ietf@ietf.org; Tue, 03 Jun 2003 21:51:11 -0400
Received: from nerf.yikes.com ([157.22.12.202] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NNQk-00055S-00
	for ietf@ietf.org; Tue, 03 Jun 2003 21:51:10 -0400
Received: from [63.193.24.36] (rick.perlman.com [63.193.24.36])
	by nerf.yikes.com (8.12.9/8.12.6) with ESMTP id h541rUqb030828
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 3 Jun 2003 18:53:30 -0700 (PDT)
User-Agent: Microsoft-Entourage/10.1.1.2418
Date: Tue, 03 Jun 2003 18:52:54 -0700
Subject: Re: This IETF discussion list
From: Richard Perlman <perl@lucent.com>
To: "'IETF Discussion'" <ietf@ietf.org>
CC: <harald@alvestrand.no>
Message-ID: <BB029F06.1304C%perl@lucent.com>
In-Reply-To: <Pine.LNX.4.44.0306031752071.21528-100000@commander.av8.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

All:

I have been loosely tracking the SPAM discussion and really had nothing
significant to add.  However, a related posting did catch my attention and
interest, enough so to warrant a response.

While I certainly am not interested in taking sides on the personal
accusations that have been seen recently, I do have serious concerns about
the message quoted below.  I personally detest the daily deluge of unwanted
unsolicited e-mails I receive.  However, I would be even more upset to find
that one's belief or support for or against any topic should be the criteria
by which their contributions were judged.

As despicable as I may find the concepts, opinions and thoughts of others, a
world in which the expression of only those ideas that I found acceptable
would be far worse.

Having said that, I do want to be clear, that while I think there needs to
be freedom for expression of ideas, that expression must be done in a way
that encourages discussion and values the participation of everyone.  There
is no room for personal remarks and attacks in a conversation of ideas.

Richard

On 6/3/03 15:00, "Dean Anderson" <dean@av8.com> quoted:
> ==================
> Date: Fri, 30 May 2003 02:09:25 +0200
> From: "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr>
> To: 'Eric A. Hall' <ehall@ehsco.com>, 'John Stracke'
> <jstracke@centive.com>
> Cc: ietf@ietf.org
> Subject: RE: spam
> 
> Guys,
> 
> Dean Anderson obviously supports and defends SPAM.
> No further conversation with him could lead to anything constructive.
> Stop feeding the Troll, now.
> 
> E.T.




From owner-ietf@ietf.org  Tue Jun  3 22:27:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04521
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 22:27:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NNv7-00063e-Um
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 22:22:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NNok-0005xa-JI
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 22:15:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04450
	for <ietf@ietf.org>; Tue, 3 Jun 2003 22:15:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NNmx-0005IQ-00
	for ietf@ietf.org; Tue, 03 Jun 2003 22:14:07 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NNmx-0005IC-00
	for ietf@ietf.org; Tue, 03 Jun 2003 22:14:07 -0400
Content-class: urn:content-classes:message
Subject: RE: This IETF discussion list
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Tue, 3 Jun 2003 19:15:51 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F506719E@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: This IETF discussion list
Thread-Index: AcMqPtwikhUIdU0/S4ijN0Nt36QJrgAADLbQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "IETF Discussion" <ietf@ietf.org>
Cc: <harald@alvestrand.no>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id WAA04521

Added to the pro-troll and pro-spammer list: Richard Perlman.

Michel.


-----Original Message-----
From: Richard Perlman [mailto:perl@lucent.com] 
Sent: Tuesday, June 03, 2003 6:53 PM
To: 'IETF Discussion'
Cc: harald@alvestrand.no
Subject: Re: This IETF discussion list

All:

I have been loosely tracking the SPAM discussion and really had nothing
significant to add.  However, a related posting did catch my attention
and
interest, enough so to warrant a response.

While I certainly am not interested in taking sides on the personal
accusations that have been seen recently, I do have serious concerns
about
the message quoted below.  I personally detest the daily deluge of
unwanted
unsolicited e-mails I receive.  However, I would be even more upset to
find
that one's belief or support for or against any topic should be the
criteria
by which their contributions were judged.

As despicable as I may find the concepts, opinions and thoughts of
others, a
world in which the expression of only those ideas that I found
acceptable
would be far worse.

Having said that, I do want to be clear, that while I think there needs
to
be freedom for expression of ideas, that expression must be done in a
way
that encourages discussion and values the participation of everyone.
There
is no room for personal remarks and attacks in a conversation of ideas.

Richard

On 6/3/03 15:00, "Dean Anderson" <dean@av8.com> quoted:
> ==================
> Date: Fri, 30 May 2003 02:09:25 +0200
> From: "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr>
> To: 'Eric A. Hall' <ehall@ehsco.com>, 'John Stracke'
> <jstracke@centive.com>
> Cc: ietf@ietf.org
> Subject: RE: spam
> 
> Guys,
> 
> Dean Anderson obviously supports and defends SPAM.
> No further conversation with him could lead to anything constructive.
> Stop feeding the Troll, now.
> 
> E.T.





From owner-ietf@ietf.org  Tue Jun  3 23:58:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05818
	for <ietf-web-archive@odin.ietf.org>; Tue, 3 Jun 2003 23:58:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NPCK-0007an-9F
	for ietf-list@asgard.ietf.org; Tue, 03 Jun 2003 23:44:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NP8w-0007Y7-M4
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 23:40:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05617
	for <ietf@ietf.org>; Tue, 3 Jun 2003 23:40:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NP7A-0005cm-00
	for ietf@ietf.org; Tue, 03 Jun 2003 23:39:04 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NP79-0005ce-00
	for ietf@ietf.org; Tue, 03 Jun 2003 23:39:03 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h543eHwc000178;
	Tue, 3 Jun 2003 20:40:17 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AET05992;
	Tue, 3 Jun 2003 20:40:16 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id UAA01444; Tue, 3 Jun 2003 20:40:16 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16093.27168.668903.64840@thomasm-u1.cisco.com>
Date: Tue, 3 Jun 2003 20:40:16 -0700 (PDT)
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: "IETF Discussion" <ietf@ietf.org>, <harald@alvestrand.no>
Subject: RE: This IETF discussion list
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F506719E@server2000.arneill-py.sacramento.ca.us>
References: <963621801C6D3E4A9CF454A1972AE8F506719E@server2000.arneill-py.sacramento.ca.us>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Michel Py writes:
 > Added to the pro-troll and pro-spammer list: []

  Can we pretty please retire the Catherine Wheels from
  this list? Thank you.

       Mike



From owner-ietf@ietf.org  Wed Jun  4 01:59:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08139
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 01:59:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NR9a-0004KZ-RL
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 01:49:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NR8f-0004HM-II
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 01:48:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07838
	for <ietf@ietf.org>; Wed, 4 Jun 2003 01:48:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NR6t-00069t-00
	for ietf@ietf.org; Wed, 04 Jun 2003 01:46:55 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NR6s-00069q-00
	for ietf@ietf.org; Wed, 04 Jun 2003 01:46:54 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 560A562595; Wed,  4 Jun 2003 07:48:13 +0200 (CEST)
Date: Wed, 04 Jun 2003 07:48:13 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: IETF Standards Process
Message-ID: <75810000.1054705693@askvoll.hjemme.alvestrand.no>
In-Reply-To: <Pine.LNX.4.44.0306031553070.21528-100000@commander.av8.net>
References:  <Pine.LNX.4.44.0306031553070.21528-100000@commander.av8.net>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, juni 03, 2003 17:28:55 -0400 Dean Anderson <dean@av8.com> 
wrote:

>
> You indicated that my criticism was incorrect regarding Mr. Klensin's
> understanding of the standards process in regards to the description of
> the current SMTP Standard.  So, now I am confused, and would like to learn
> how to correctly evalute the status of IETF Standards.
>
> The following question seems simple enough:
>
> "What is the current standard level RFC describing the SMTP protocol?"

formally, we have two standards-track specifications for the SMTP protocol.

RFC 821 at Standard, and RFC 2821 at Proposed Standard.

The intent is, I believe, that any RFC 2821 client will be RFC 821 
compatible, but implementors who care should state which specification they 
claim conformance to.

The "delete after 24 months" clause of RFC 2026 is inoperative in practice; 
the oldest Proposed Standard is RFC 698, published in 1975.

I have no explanation for the error in RFC 3300; the RFCs in question were 
published by the RFC Editor without IETF review.
The first such document to refer to RFC 2821 was RFC 2800.

                   Harald




From owner-ietf@ietf.org  Wed Jun  4 02:19:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24174
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 02:19:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NRSd-00089V-KK
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 02:09:23 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NRO6-0006zS-An
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 02:04:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13082
	for <ietf@ietf.org>; Wed, 4 Jun 2003 02:04:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NRMJ-0006JQ-00
	for ietf@ietf.org; Wed, 04 Jun 2003 02:02:51 -0400
Received: from p2.piuha.net ([131.160.192.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NRMI-0006JN-00
	for ietf@ietf.org; Wed, 04 Jun 2003 02:02:51 -0400
Received: from piuha.net (p4.piuha.net [131.160.192.4])
	by p2.piuha.net (Postfix) with ESMTP
	id D1B406A902; Wed,  4 Jun 2003 09:04:38 +0300 (EEST)
Message-ID: <3EDD8B91.1030509@piuha.net>
Date: Wed, 04 Jun 2003 09:02:57 +0300
From: Jari Arkko <jari.arkko@piuha.net>
Reply-To: jari.arkko@piuha.net
Organization: None
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Michael Thomas <mat@cisco.com>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: authenticated email
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>	<016c01c32960$56b1adb0$46124104@eagleswings>	<16092.51912.740900.110873@thomasm-u1.cisco.com>	<70660000.1054674804@askvoll.hjemme.alvestrand.no> <16093.10524.494835.396218@thomasm-u1.cisco.com>
In-Reply-To: <16093.10524.494835.396218@thomasm-u1.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Michael Thomas wrote:

> It depends on what you mean by signing. Signing a
> message in and of itself ought not hurt anything
> modulo software bugs, etc. But the real question
> is what does the receiving program (MTA, MUA) do
> with that signature? At the very least it could
> verify the signature, but then what? If it doesn't
> verify do you drop it? (transitive trust comes
> into play, but most likely). Does it do anything
> beyond that?
> 
> Let me ask something in return: do you think that
> just the act of signing mail -- with no trust
> roots implied -- could help? My sense is that it
> might in a sow-the-seeds kind of way for some
> later goodness (it's as you say not a solution).
> I too would be happy to hear downsides.

Without trust roots, webs of trust, or additional
mailing list daemon features, signed e-mail doesn't
really add anything, at least not now.

Signed e-mail could help ensure that e-mail
sent to a list comes from the same person
as the one who subscribed to the list. But then
again, the same feature could be implemented
much simpler by some header which must stay
constant from the same person and is stripped
off by the list daemon when forwarding the mail
to the subscribers.

More seriously, ensuring the sender's address
is right is useless IMHO unless there's a policy
for letting people to sign-up to a list. Spammers
could get a new address and generate a key pair,
sign up using them, send spam, and repeat with
another address and key.

So, its the same old question once again: how
do we all enroll ourselves to the same trusted
root or web of trust? Should the next PGP key
signing party be held in the plenary, for everyone?
Or maybe Harald stands in the IETF reception desk
to look at people's passports and certifies keys?
Hmm... maybe we could make PGP key mandatory in
registration, and have the secretariat form a web
of trust. At least we could trace every key to
a credit card number... sounds pretty good but
this wouldn't deal with the folks who don't come
to the meetings. Maybe we could turn on mandatory
PGP signing for all list e-mail for a year, and
at the end of the year make a web of trust for the
folks who sent e-mail that year. That wouldn't
be perfect, but it would sure reduce the size of
queue in front of Harald for the passport check ;-)

--Jari




From owner-ietf@ietf.org  Wed Jun  4 03:54:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06775
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 03:54:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NSwf-0005Xp-EH
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 03:44:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NSsX-0005Up-HK
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 03:40:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06615
	for <ietf@ietf.org>; Wed, 4 Jun 2003 03:40:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NSqk-0007CR-00
	for ietf@ietf.org; Wed, 04 Jun 2003 03:38:22 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NSqj-0007CO-00
	for ietf@ietf.org; Wed, 04 Jun 2003 03:38:22 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h547f6xS035495;
	Wed, 4 Jun 2003 09:41:07 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Wed, 4 Jun 2003 09:40:03 +0200
Subject: Re: Engineering to deal with the social problem of spam
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: <alh-ietf@tndh.net>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <01d701c32a33$cf24f3f0$46124104@eagleswings>
Message-Id: <C0D49B9C-965F-11D7-AAC0-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

(I really wanted to stop this thread with my previous message, but...)

On woensdag, jun 4, 2003, at 02:54 Europe/Amsterdam, Tony Hain wrote:

>> Just adding authentication only solves a very small part of the
>> problem: we can then accurately whitelist known senders.

> Two points:
> 1) besides white listing, the approach also provides irrefutable
> evidence to law enforcement about spam sources.

Ok, there's some value in that if we build a good key infrastructure. 
Wouldn't say "irrefutable" even then, though.

What I meant to say: we need more than authentication.

>> A new interpersonal batch communication system certainly sounds like a
>> good idea. The problem with email is that it is incredibly ill-suited
>> for transferring larger files. A new protocol should be able to do 
>> much
>> better in this area. However, this doesn't have much to do with spam
>> issues and might make the whole thing much more complex.

> We can always make it more complex than necessary, but it is pointless
> to compare the complexity of a new system that does the job with a
> system that is proven to be open to abuse.

SMTP shouldn't be used to transfer binary files. It leads to all kinds 
of problems: clogged mailboxes, wasted bandwidth (base64, aargghh!), 
you name it. A better batch interpersonal communication system would be 
able to send the message, but then negotiate what to do with the 
attachment. From some people you may want to always immediately receive 
the attachment, from others you may want to read the message first and 
then decide whether to inititate the transfer of the attachment.

This would be very cool except that it breaks current email systems at 
a fairly fundamental level. Adding authentication on the other hand, 
can be done in a way that may not be compatible with current ESTMP, but 
it does (or at least: could) fit into the current email architecture 
without too much trouble.

>> The trouble is that on the internet, you can go from house to house 
>> and
>> try to break locks and nobody will stop you. In the real world, you
>> wouldn't be able to do that for very long.

> Adopt draft-hain-ipv6-pi* as the standard addressing plan, provide
> automated intrusion detection reporting, and Internet prowlers wouldn't
> be able to attack for very long either.

Only if someone cares enough to go to the place where the prowler 
deploys his activities. There was a time when this was a reasonable 
assumption; but this time is now in the past.

>> So let's show some adaptability of our own and plug those SMTP holes.

> Or simply leave SMTP to the spammers and move on.

Fine by me.

>> Why look at individual messages? How much non-bulk mail can someone
>> possibly need to send? 10 messages per hour? 100? 1000?

> @ 5kB/message on a 10MB/sec link, 2k/sec.

And how exactly would those messages be "non-bulk"? I mean, I type 
fast, but even then it takes a second or so to even find the recipients 
for a message.

>> That's why it's important to look at ALL mail rather than just copies
>> of one message. Spammers by now know how to make messages look
>> different even though they're essentially identical.

> Exactly how would you coorelate email across multiple accounts, on
> multiple service providers?

We push this back to the source MTA. Then if the source MTA does a bad 
job, we revoke the MTA's "not-a-spammer" accreditation so only messages 
with whitelisted senders can get through.

Alternatively, we can build a serial number system. An MTA must then 
add a serial number that starts from 0 every day or every week to every 
message. This way everyone who receives a message from this MTA knows 
how many messages the MTA has already transmitted this period. 
Obviously spammers will fake the serial number so we also build a 
system that makes it possible to check if a serial number wasn't used 
more than once afterwards.

This shouldn't be much of a problem for spammers if they can set up a 
new MTA in five minutes, but if they (for instance) have to get three 
people in good standing to sign the new MTA's key in order to be able 
to start a new spam run, then it gets more troublesome for them.

>> Someone's "home MTA" sould be able to simply rate limit the number of
>> messages an individual user gets to inject into the global email
>> distribution system. Then all we need is a system to differentiate
>> between trusted MTAs and rogue ones run by spammers.

> Why would a spammer limit themselves to a single MTA, or account. Run
> VMware on a laptop, and there could easliy be 10 parallel rate-limited
> sessions going on. If the rates are low enough, each virtual system
> could automatically log into another account on another MTA, then come
> back when the timer goes off.

At a limit of 1000 messages per hour per account, they need 10000 
account-hours to send out 10 million spam messages. Assuming it takes 
64 hours (on the weekend) to get an account yanked for spamming that's 
160 accounts. This is a good start. Add some additional stuff such as 
limiting the number of messages per hour based on the number of bounces 
received and we should have something that's pretty effective.




From owner-ietf@ietf.org  Wed Jun  4 05:03:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08592
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 05:03:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NTyy-0000WD-SW
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 04:50:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NTsD-0006jy-OM
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 04:43:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08153
	for <ietf@ietf.org>; Wed, 4 Jun 2003 04:43:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NTqR-0007ck-00
	for ietf@ietf.org; Wed, 04 Jun 2003 04:42:07 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NTqQ-0007cK-00
	for ietf@ietf.org; Wed, 04 Jun 2003 04:42:06 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id B32E262595; Wed,  4 Jun 2003 10:43:25 +0200 (CEST)
Date: Wed, 04 Jun 2003 10:43:25 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Michael Thomas <mat@cisco.com>
Cc: ietf@ietf.org
Subject: Re: authenticated email
Message-ID: <115630000.1054716205@askvoll.hjemme.alvestrand.no>
In-Reply-To: <16093.10524.494835.396218@thomasm-u1.cisco.com>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
 <016c01c32960$56b1adb0$46124104@eagleswings>
 <16092.51912.740900.110873@thomasm-u1.cisco.com>
 <70660000.1054674804@askvoll.hjemme.alvestrand.no>
 <16093.10524.494835.396218@thomasm-u1.cisco.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, juni 03, 2003 16:02:52 -0700 Michael Thomas <mat@cisco.com> 
wrote:

> It depends on what you mean by signing. Signing a
> message in and of itself ought not hurt anything
> modulo software bugs, etc. But the real question
> is what does the receiving program (MTA, MUA) do
> with that signature? At the very least it could
> verify the signature, but then what? If it doesn't
> verify do you drop it? (transitive trust comes
> into play, but most likely). Does it do anything
> beyond that?
>
> Let me ask something in return: do you think that
> just the act of signing mail -- with no trust
> roots implied -- could help? My sense is that it
> might in a sow-the-seeds kind of way for some
> later goodness (it's as you say not a solution).
> I too would be happy to hear downsides.

well... if signing my email would help get rid of the nonconformant mailers 
on the path that do perverse stuff that breaks signatures, that certainly 
would be a benefit to the world.... verifying my own signature failed....

and here's why:

Original:

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

Copy:

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

The difference matters not at all to anything but a signature verifier..... 
sigh.

                   Harald




From owner-ietf@ietf.org  Wed Jun  4 07:15:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11472
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 07:15:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NW45-0002aG-I3
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 07:04:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NW2Z-0002XL-2q
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 07:02:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11120
	for <ietf@ietf.org>; Wed, 4 Jun 2003 07:02:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NW0m-0000cf-00
	for ietf@ietf.org; Wed, 04 Jun 2003 07:00:56 -0400
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NW0l-0000cV-00
	for ietf@ietf.org; Wed, 04 Jun 2003 07:00:55 -0400
Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136])
	by motgate3.mot.com (Motorola/Motgate3) with ESMTP id h54B2OGx026568;
	Wed, 4 Jun 2003 04:02:35 -0700 (MST)
Received: from thorgal.crm.mot.com (thorgal.crm.mot.com [140.101.173.1])
	by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id h54A2NPG028797;
	Wed, 4 Jun 2003 05:02:25 -0500
Received: from nal.motlabs.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id C7CF42EC86; Wed,  4 Jun 2003 13:02:18 +0200 (CEST)
Message-ID: <3EDDD1B3.9080700@nal.motlabs.com>
Date: Wed, 04 Jun 2003 13:02:11 +0200
From: Alexandru Petrescu <petrescu@nal.motlabs.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org
Subject: Re: authenticated email
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu> <016c01c32960$56b1adb0$46124104@eagleswings> <16092.51912.740900.110873@thomasm-u1.cisco.com> <70660000.1054674804@askvoll.hjemme.alvestrand.no>
In-Reply-To: <70660000.1054674804@askvoll.hjemme.alvestrand.no>
X-Enigmail-Version: 0.72.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms050406080307070509060003"
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a cryptographically signed message in MIME format.

--------------ms050406080307070509060003
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Harald Tveit Alvestrand wrote:
> I thought I'd try this....
> 
> is there any particular disadvantage or centralization of power 
> implied in me signing this message with my PGP key?

Is there an IETF PGP keyserver somewhere?

Did you store the key securely on the keyserver?

Which keyserver?  Which port?  The particular network I connect to is
blocking most ports, so I can't retrieve your public key.

On another hand, the same particular network recommends that its users
use a particular MUA, which has built-in certs of certain CAs, which
allows readers of this email to trust I am who I claim to be, "legally"
(as if I showed an ID).

> If not, is there any particular reason that I shouldn't do this all 
> the time?

Will the government of the country you live in allow you to store
your public key on a public PGP keyserver?  (a particular government was
_not_ allowing it as of 1997, and if things have changed since then I'm
happy, but the "try and find out" way is high risk for me.)

Alex
GBU

--------------ms050406080307070509060003
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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN1jCC
AzEwggKaoAMCAQICCwEAAAAAAPR9LrLHMA0GCSqGSIb3DQEBBQUAMF0xCzAJBgNVBAYTAkJF
MRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMRMwEQYDVQQLEwpDbGFzcyAyIENBMR4wHAYD
VQQDExVHbG9iYWxTaWduIENsYXNzIDIgQ0EwHhcNMDMwNDExMTQ0MzUyWhcNMDQwNDExMTQ0
MzUyWjBTMQswCQYDVQQGEwJGUjEbMBkGA1UEAxMSQWxleGFuZHJ1IFBldHJlc2N1MScwJQYJ
KoZIhvcNAQkBFhhwZXRyZXNjdUBuYWwubW90bGFicy5jb20wggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQCRuajb15Dmn/Kkn2/9qQKqALuBTfhg8RLB/OisPBchYlEn7r9Lp4ZN
Zqu5L0Y2f4w5X2pOPseE82l1g4ArEOc0A/JyQxUTr7R2RutzqRBDnDRYQl+KT5djQZ+U2g5B
4+WpicRjjRzovA2Y09INp6VF7ayHqnA+k5A6OP0rj9sS8mZBkIYPjnmpryO7/Ykor6NO1mSo
vDZDGMhv3A0AClCyMQYO/vNo0+nA9nUmaKQqYzzHQNnsqMnvGe74338aea5i4R7b/VkZR8cH
IKsLu1uVKJFemvrwBWmX/DmxDrLZtAP8onCE1hk2N+iDzpL8evRUzrk5IINwsdx35XseysYR
AgMBAAGjfTB7MBEGCWCGSAGG+EIBAQQEAwIFoDAOBgNVHQ8BAf8EBAMCBPAwHwYDVR0jBBgw
FoAUEW7XkWDLBuRXAFeonIC9djPlWVEwNQYDVR0fBC4wLDAqoCigJoYkaHR0cDovL2NybC5n
bG9iYWxzaWduLm5ldC9jbGFzczIuY3JsMA0GCSqGSIb3DQEBBQUAA4GBAIdnaLZTtqBlJ8hz
KKU5dL0QDr+sDfqJWyqsIuFUG8LBc6by+SCTGG4qQ36+jgUR8rLE8srjwyiG6WlzBGdXawom
mg31m9USO0IyZ0VoGzBMIszhuKnsuBDz91kSNXsNoShdFxidCLAIBPFs79dBWMcqsjitXdQw
25h1vBO/vmR5MIIDMTCCApqgAwIBAgILAQAAAAAA9H0usscwDQYJKoZIhvcNAQEFBQAwXTEL
MAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExEzARBgNVBAsTCkNsYXNz
IDIgQ0ExHjAcBgNVBAMTFUdsb2JhbFNpZ24gQ2xhc3MgMiBDQTAeFw0wMzA0MTExNDQzNTJa
Fw0wNDA0MTExNDQzNTJaMFMxCzAJBgNVBAYTAkZSMRswGQYDVQQDExJBbGV4YW5kcnUgUGV0
cmVzY3UxJzAlBgkqhkiG9w0BCQEWGHBldHJlc2N1QG5hbC5tb3RsYWJzLmNvbTCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBAJG5qNvXkOaf8qSfb/2pAqoAu4FN+GDxEsH86Kw8
FyFiUSfuv0unhk1mq7kvRjZ/jDlfak4+x4TzaXWDgCsQ5zQD8nJDFROvtHZG63OpEEOcNFhC
X4pPl2NBn5TaDkHj5amJxGONHOi8DZjT0g2npUXtrIeqcD6TkDo4/SuP2xLyZkGQhg+Oeamv
I7v9iSivo07WZKi8NkMYyG/cDQAKULIxBg7+82jT6cD2dSZopCpjPMdA2eyoye8Z7vjffxp5
rmLhHtv9WRlHxwcgqwu7W5UokV6a+vAFaZf8ObEOstm0A/yicITWGTY36IPOkvx69FTOuTkg
g3Cx3Hflex7KxhECAwEAAaN9MHswEQYJYIZIAYb4QgEBBAQDAgWgMA4GA1UdDwEB/wQEAwIE
8DAfBgNVHSMEGDAWgBQRbteRYMsG5FcAV6icgL12M+VZUTA1BgNVHR8ELjAsMCqgKKAmhiRo
dHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L2NsYXNzMi5jcmwwDQYJKoZIhvcNAQEFBQADgYEA
h2dotlO2oGUnyHMopTl0vRAOv6wN+olbKqwi4VQbwsFzpvL5IJMYbipDfr6OBRHyssTyyuPD
KIbpaXMEZ1drCiaaDfWb1RI7QjJnRWgbMEwizOG4qey4EPP3WRI1ew2hKF0XGJ0IsAgE8Wzv
10FYxyqyOK1d1DDbmHW8E7++ZHkwggOBMIICaaADAgECAgsEAAAAAADwdgPo3jANBgkqhkiG
9w0BAQUFADBtMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEbMBkG
A1UECxMSUHJpbWFyeSBDbGFzcyAyIENBMSYwJAYDVQQDEx1HbG9iYWxTaWduIFByaW1hcnkg
Q2xhc3MgMiBDQTAeFw05OTAxMjgxMjAwMDFaFw0wNDAxMjgxMjAwMDBaMF0xCzAJBgNVBAYT
AkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMRMwEQYDVQQLEwpDbGFzcyAyIENBMR4w
HAYDVQQDExVHbG9iYWxTaWduIENsYXNzIDIgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ
AoGBANhRWw+Tx0lgd1EUjuOddXUeyYUOf0wDGRl2pO56K/yDBgPHnBaavo5OEQpAf6wyidPB
efz5RNGHU8/b07stXym5+roR+1Si28bT5rXAiC+1TgKH3MubGXn2v900et4zhVroMnXPQ2FF
DePIhztHEKHl3y1sBwZH+U7Y+/aEngzDAgMBAAGjgbUwgbIwDgYDVR0PAQH/BAQDAgEGMBIG
A1UdEwEB/wQIMAYBAf8CAQAwHQYDVR0OBBYEFBFu15FgywbkVwBXqJyAvXYz5VlRMDkGA1Ud
HwQyMDAwLqAsoCqGKGh0dHA6Ly9jcmwuZ2xvYmFsc2lnbi5uZXQvUHJpbUNsYXNzMi5jcmww
EQYJYIZIAYb4QgEBBAQDAgEGMB8GA1UdIwQYMBaAFHznsrEs3rGna+l2DOGj/U5sx7n2MA0G
CSqGSIb3DQEBBQUAA4IBAQCPeyq9LZcj+UNHAvHjURnfON32k7rUDUKyp+eors9XDpjDgMtu
ECZF70abQ7iSq1vahlHOHTDx5HjlaQJoonwjRapBRvF/qrsQnlD/IyxDbMhPpp/cP1Wx35ja
aQNqllu2gokRnZpYSSZo1f5wf+kfnWksy+QQ2tz+sIn3Mb824DsviWZSLrR0oIt92PJ3UfS1
zi8AK90jdq8jGErGDHvb87JoBTRTRUlTkQ1XrvOhhsdhA56XvhDTHbv1iAHcLSNse4H95Y1k
ooQ0ZusQpE1ZShLR/3ddoZ1PL08eaNWhcEZ0ArO2DiNzQQgafTu6pa0gB6RTJwGkFP0NIDei
PjHdMIID4zCCAsugAwIBAgILBAAAAAAA8HYD2XwwDQYJKoZIhvcNAQEFBQAwVzELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExEDAOBgNVBAsTB1Jvb3QgQ0ExGzAZ
BgNVBAMTEkdsb2JhbFNpZ24gUm9vdCBDQTAeFw05OTAxMjgxMjAwMDBaFw0wOTAxMjgxMjAw
MDBaMG0xCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMRswGQYDVQQL
ExJQcmltYXJ5IENsYXNzIDIgQ0ExJjAkBgNVBAMTHUdsb2JhbFNpZ24gUHJpbWFyeSBDbGFz
cyAyIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoz+7/RFjhdBbvzYvyFv
qwadUsEsAJ0/joW4f0qPvaBjKspJJ65agvR04lWS/8LRqnmitvrVnYIET8ayxl5jpzq62O7r
im+ftrsoQcAi+05IGgaS17/Xz7nZvThPOw1EblVB/vwJ29i/844h8egStfYTpdPGTJMisAL/
7h0MxKhrT3VoVujcKBJQ96gknS4kOfsJBd7lo2RJIdBofnEwkbFg4Dn0UPh6TZgAa3x5uk7O
SuK6Nh23xTYVlZxkQupfxLr1QAW+4TpZvYSnGbjeTVNQzgfR0lHT7w2BbObnbctdfD98zOxP
gycl/3BQ9oNZdYQGZlgs3omNAKZJ+aVDdwIDAQABo4GZMIGWMA4GA1UdDwEB/wQEAwIBBjAP
BgNVHRMBAf8EBTADAQH/MB0GA1UdDgQWBBR857KxLN6xp2vpdgzho/1ObMe59jAzBgNVHR8E
LDAqMCigJqAkhiJodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L1Jvb3QuY3JsMB8GA1UdIwQY
MBaAFGB7ZhpFDZfKiVAvfQTNNKj//P1LMA0GCSqGSIb3DQEBBQUAA4IBAQCOSXXBWIDxAxy2
ZioidZVbZLmecRI30bfezE8WYEUUAke+bIj39Rsdpp2qGW58HDqEpMWNqTwx/g3oQt8hUCLu
cQGBqGQzlPGtnVpbADfipFzkIKpgdJQ967DpIZ0dNKmmNINBXuM6/yEe0hup7XYtvi9PKFx5
qeCWkf7KDCruRY51KismvY6uCN2LuVeN/20LqwhGDJ/5gii8H64MclYNd5qgiFd4JziNL3Ur
1HFqFEiluobJ33wmE54tbMhb9Wt8HzhnL47U16jZhe0K4PKYadkal6ZQl5zHPSRZbrGhvY2m
MhGdVAFbK4Lh/Y3FaEMN4LgmVJ5/E94Qp2n6siqBMYIDRDCCA0ACAQEwbDBdMQswCQYDVQQG
EwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTETMBEGA1UECxMKQ2xhc3MgMiBDQTEe
MBwGA1UEAxMVR2xvYmFsU2lnbiBDbGFzcyAyIENBAgsBAAAAAAD0fS6yxzAJBgUrDgMCGgUA
oIIBrTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA2MDQx
MTAyMTFaMCMGCSqGSIb3DQEJBDEWBBTw8J/anDq6HhB+UEodq12aa+3HLDBSBgkqhkiG9w0B
CQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUr
DgMCBzANBggqhkiG9w0DAgIBKDB7BgkrBgEEAYI3EAQxbjBsMF0xCzAJBgNVBAYTAkJFMRkw
FwYDVQQKExBHbG9iYWxTaWduIG52LXNhMRMwEQYDVQQLEwpDbGFzcyAyIENBMR4wHAYDVQQD
ExVHbG9iYWxTaWduIENsYXNzIDIgQ0ECCwEAAAAAAPR9LrLHMH0GCyqGSIb3DQEJEAILMW6g
bDBdMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTETMBEGA1UECxMK
Q2xhc3MgMiBDQTEeMBwGA1UEAxMVR2xvYmFsU2lnbiBDbGFzcyAyIENBAgsBAAAAAAD0fS6y
xzANBgkqhkiG9w0BAQEFAASCAQAsayuKODyREX1tCfTD1rFsV+silR1Vks/cpQDeB/xLEqQ6
aph1c43q7/wIqxFejUTVghbHS8ceGF3c+dXb0cz2x0YqolzS08X6zos/8fdKyg8/WuIf5DE5
Gh/BVZ24BzNImBjTfMcQLTn94iZ8sbw7qxxQIRW10Wno4QzXJzxsmpV4nDaNS8/rnUMvBIqk
aDHKVGzr6Eex/cMkDS6PgiITZAfWk/zn2BonSVIYFwoUbkBr4IBMMyD9G+w2qw8o1Hwmcybj
jVKu1yUZB9wFl+7AjS+gnQ7/w/SY9b8ufNwcN7PK+IVU41wcNfsYT0cWz7kSFPWAUR9D9xm5
AVFagdA6AAAAAAAA
--------------ms050406080307070509060003--




From owner-ietf@ietf.org  Wed Jun  4 07:48:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12178
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 07:48:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NWW9-0003Fv-Ii
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 07:33:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NWJY-00037X-Cz
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 07:20:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11700
	for <ietf@ietf.org>; Wed, 4 Jun 2003 07:20:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NWHl-0000mE-00
	for ietf@ietf.org; Wed, 04 Jun 2003 07:18:29 -0400
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NWHk-0000mB-00
	for ietf@ietf.org; Wed, 04 Jun 2003 07:18:28 -0400
Received: from [66.92.109.27] (helo=think.thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:DES-CBC3-SHA:168)  (Exim 3.35 #1 (Debian))
	id 19NWJJ-0003xL-00; Wed, 04 Jun 2003 07:20:06 -0400
Received: from tytso authenticated as tytso by think.thunk.org with local   (Exim 3.35 #1 (Debian))
	id 19NWJJ-0002kR-00; Wed, 04 Jun 2003 07:20:05 -0400
Date: Wed, 4 Jun 2003 07:20:04 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: Jari Arkko <jari.arkko@piuha.net>
Cc: Michael Thomas <mat@cisco.com>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: authenticated email
Message-ID: <20030604112004.GA10522@think>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu> <016c01c32960$56b1adb0$46124104@eagleswings> <16092.51912.740900.110873@thomasm-u1.cisco.com> <70660000.1054674804@askvoll.hjemme.alvestrand.no> <16093.10524.494835.396218@thomasm-u1.cisco.com> <3EDD8B91.1030509@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3EDD8B91.1030509@piuha.net>
User-Agent: Mutt/1.5.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Jun 04, 2003 at 09:02:57AM +0300, Jari Arkko wrote:
> 
> Without trust roots, webs of trust, or additional
> mailing list daemon features, signed e-mail doesn't
> really add anything, at least not now.
> 
> Signed e-mail could help ensure that e-mail
> sent to a list comes from the same person
> as the one who subscribed to the list. But then
> again, the same feature could be implemented
> much simpler by some header which must stay
> constant from the same person and is stripped
> off by the list daemon when forwarding the mail
> to the subscribers.

Signed e-mail is useful for assuring that e-mail message sent at one
point in time is the same as an e-mail message sent earlier.  (Not
necessarily just for list mail, but also for person-to-person mail.)

> So, its the same old question once again: how
> do we all enroll ourselves to the same trusted
> root or web of trust? 

For the specialized case of preventing SPAM, it's not necessarily
necessary to do the full authenticated e-mail where we know the
identity/passport number/Al Quaeda cell designation of the sender.
(Such things are of interest to John Ashcroft and others of that ilk
pushing "Total Information Awareness", but it's not really needed if
the only requirement is to stop SPAM.)

So imagine a system where if you want to send private e-mail to
someone, your public key figureprint must either be on a list of
acceptable senders, or you must submit some kind of mathematical
evidence that you have spent 5-10 minutes of CPU time crunching on
some particular problem.  After you do this, you get added to that
person's "good guys list", unless it turns out that you have sent spam
or something else annoying/abusive, at which point the user can remove
you from the trusted list, and the next time you want to send e-mail
to this person, you have to crunch for another 5-10 minutes of CPU
time.

Yeah, some special provision would be needed for CPU-limited PDA's,
but most PDA's that I've seen don't attempt to talk to the network
directly; they generally go through some kind of mutually trusted
gateway box that could do the CPU crunching for them.  (Or you could
argue that since that initial contact simply won't be supported from
by CPU-limited PDA's if they don't have a mutually trusted third party
that can "pay" the hashcash for them.)

The point of this message is not to argue that this is the Right Way
to do things, but to point out that you don't necessarily have to
solve the authenticated e-mail problem ("I invoke PKI; your project is
doomed to long, slow, painful, lingering death") in order to solve the
SPAM problem.

						- Ted



From owner-ietf@ietf.org  Wed Jun  4 07:50:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12331
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 07:50:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NWcx-0005TR-3C
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 07:40:23 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NWP2-0003CZ-E3
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 07:26:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11765
	for <ietf@ietf.org>; Wed, 4 Jun 2003 07:25:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NWND-0000ni-00
	for ietf@ietf.org; Wed, 04 Jun 2003 07:24:08 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NWNC-0000nS-00
	for ietf@ietf.org; Wed, 04 Jun 2003 07:24:07 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 7BAB9622AC; Wed,  4 Jun 2003 13:25:26 +0200 (CEST)
Date: Wed, 04 Jun 2003 13:25:26 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Alexandru Petrescu <petrescu@nal.motlabs.com>
Cc: ietf@ietf.org
Subject: Re: authenticated email
Message-ID: <133600000.1054725926@askvoll.hjemme.alvestrand.no>
In-Reply-To: <3EDDD1B3.9080700@nal.motlabs.com>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
 <016c01c32960$56b1adb0$46124104@eagleswings>
 <16092.51912.740900.110873@thomasm-u1.cisco.com>
 <70660000.1054674804@askvoll.hjemme.alvestrand.no>
 <3EDDD1B3.9080700@nal.motlabs.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA12331



--On onsdag, juni 04, 2003 13:02:11 +0200 Alexandru Petrescu 
<petrescu@nal.motlabs.com> wrote:

> Harald Tveit Alvestrand wrote:
>> I thought I'd try this....
>>
>> is there any particular disadvantage or centralization of power
>> implied in me signing this message with my PGP key?
>
> Is there an IETF PGP keyserver somewhere?

nope. we have had a lot of PGP key signing parties at IETFs, but nothing 
"official". I generally use wwwkeys.eu.pgp.net when I look for keys, but 
there's nothing very magical about that.

> Did you store the key securely on the keyserver?

Why should I? It's signed, so it's either there or not there - you can't 
fake it, just remove it. (And sometimes I wish the keyservers WOULD drop 
some keys - there's an old key of mine out there that I don't use any 
more....)

> Which keyserver?  Which port?  The particular network I connect to is
> blocking most ports, so I can't retrieve your public key.

It's attached below, too. Anything to increase the Kbytes-posting-stats :­)

> On another hand, the same particular network recommends that its users
> use a particular MUA, which has built-in certs of certain CAs, which
> allows readers of this email to trust I am who I claim to be, "legally"
> (as if I showed an ID).
>
>> If not, is there any particular reason that I shouldn't do this all
>> the time?
>
> Will the government of the country you live in allow you to store
> your public key on a public PGP keyserver?  (a particular government was
> _not_ allowing it as of 1997, and if things have changed since then I'm
> happy, but the "try and find out" way is high risk for me.)

The Norwegian government does not care, so that's not a downside for me - 
but of course, your mileage may vary.

             Harald

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

mQGiBDS6GscRBADSUKFMf4osMWUHpRqFUjqklLpq4tjL5gYFH5sjYFleu0XYWsB1
AI9ToSfKljxYkePRSXIMArb94RV2VHLmyEvU5VLgKgLT6Sw8mUyf5GJh2uC+fECq
on8b5yFiuRo7Fut7b0sDvRv7/TPbQ7brKBboQK7H2IWKmBbjDIhKnkiElwCg/3nK
JJNg8/V9G06BNg9At6WDWcUEALZuJx+y0wGqhIZvZExwekYZuVH1kWJ3gvq/r0U0
ESrsXQ4p4NAFfG+uWpGTyHDOS4xTvgQE6bAe1RNsIbevi4WeT00yYbUEnR6Ylqyr
SYGBMLBacEjCenS4bQOCVhv25oZQS60FQXeHDRpsnLt4DsPNn0OuTyDT7xyPzNAy
5eTQA/4mktErIaqWNRwmto/Tx71J90EqCcOoQQQ2XbDlmRp29AK8O782AAp0HgW1
ebK4cuUOwHOwYWHyFqeCVhrVjfVUJu62iyg54QKgaIPU7RwiCAM03buBJz4fMo3B
wHyP3uLn/ICxBoTGz/rPYJ1RktfvP7KIXJ1dct1u45wRy83dSLQuSGFyYWxkIFR2
ZWl0IEFsdmVzdHJhbmQgPEhhcmFsZEBBbHZlc3RyYW5kLm5vPohOBBARAgAOBAsD
AQICGQEFAjfJgygACgkQOMj+2+WY0F5CNQCdGxcVXgFjHfvpoaRKltv8cSvS9iUA
nRY9zfYjWEmBOZvMBADMHTFogPM7iEYEEBECAAYFAjyZbDMACgkQ4hFoDYCwek8h
FQCg6guHn1DLmXzrJSeoltYkboVihnwAmgPUnRT4fSJ88/jKhjltI0gHUSxIiQCV
AgUQPJlsNUQVcM1Ga0KJAQFDawP9EZ1J4lkNR+HAxa2RUvQcSEPCE/2B2P2QMABn
vtCFFhlxseD/qyLk3Dz03WaOsVS/Qi0hV3U3XpoGW5b5IKLxtv2JSK4g3ciaxt10
dKlvkM2Mo3DqI4Jj/2UONV7Vm6Fy8ViX/z6jJx8dtSSf4o+wwSJXE3Lpw72xsy73
tfpqc/SIRgQQEQIABgUCPJlsNwAKCRDtOjnjk2dMQLHxAKDqK2VkXr9x1nwpGxe9
koRt8+JtjgCg+Zr/UYqOIARtu0p5YyWcxcdpa/GIRgQQEQIABgUCPJpH9AAKCRAs
bbJ87KtMIKxuAKCNRMIhIAeJyKYnmxhE9r3NC0pekwCeNFlUJ3srLwqkWfz8I3fB
5ZDUA+SIXAQQAQEABgUCOe1THgAKCRAz8FU8F14BOQVBAf4q6b3VOsHx3tvkoE+p
pOCJhWeVXdZYY8hF/kLdscIdl9XMANazGtnKpVaki540wdteBxQW1wREttYixGc7
kTrbiEYEEBECAAYFAjgq5qAACgkQNnstYOXbLtrJWQCfW0FT60pXiniou2988Iik
VwRRfZQAn3WLmHD2rzbnv7alMqlP/HEn96GTiEYEEBECAAYFAjyZZw0ACgkQtfZN
GkrRZbRadwCcCHUFBzyhMk7C90xaba7e+BU9zSwAoPzKZnbhL5nDxRwjZnzbvGA0
+gFNiEYEEBECAAYFAjgrCywACgkQwM9r9d5kYh6+qACffyf5IulmTj2nJBTWDdyI
+dBl9XoAoM8ClQ/mos+a1FtzzQeuGc47Kwe7iEYEEBECAAYFAjgqZMYACgkQ1KVN
SMW+c1jcRwCglJNF0koNr5LwQ1yR+ziiaKJmEH4AoJPboEhTT6s1RD3S/Qq8OuNl
D+oqiEYEEBECAAYFAjgqSdwACgkQ3SDCJgQwZVbZBQCaAw4G2iUltXbBLytrb6Yq
21R/+GkAoOT58dXEIt7TMj6fU0aze5c+s967iEYEEBECAAYFAjyZamMACgkQ7O2h
hlqBXB86yACg1Rjy1TaYF2MN9lsdg0LjLw0R5S4AoMUfZdSd2UaOpCYGFJORqFBL
Z0RciQCUAwUQPJmFP/bvOLj4Q3BxAQF+YgP4zayJnWfWTmy2CNLGXwlF9gERBhNE
qLmhsICzkUZcV/v+vZUowhRmiMIEQhqssSsymvn27Z89dDlv4GQ7Xvq9FbcQmmxZ
agS14vUHnY+Z8za2XqloD/qB1OlqwlB7f93DXN8pUQEB7IMfYkcxVDHeF8KF0WXy
s3jiAN6+ELSOH4hGBBARAgAGBQI8mh6cAAoJEPyNdnM8hiYPZIcAnA3k21raO2BN
NgV7bPmA3asqHUgRAJ9gWOLF0tFKP7eV94Smvhe8g49wDYhGBBARAgAGBQI8mkhs
AAoJEH5cypraYkBDcHIAn3m7rVrkU5J29QfUIYW1cPS5fKPFAJ4gae/C0bvj7w7r
yKkI/3nS2jzZu4hGBBARAgAGBQI8mYH0AAoJEMl0JfuuS12SXX0AnA6xp1seY+o3
atEg8pGAaBEDC9SfAJ4k+aj2Um6qfEAyNoJEEOc6rO/hXYhGBBIRAgAGBQI9YXsh
AAoJEEouP6ZaRCq0aE0An17m1RVs5UQR0D+t3rySmR4OivMUAJ0TEUC1b0NW57sf
u+AGjRz1XtasmohGBBARAgAGBQI8rFkHAAoJEEbhbVTZrEgjAD4AoIVKZsLRVijc
iv8tW12q/LyVku8hAKCVrQkL+2tekZVm3jiESFZDxpSP7rQuSGFyYWxkIFR2ZWl0
IEFsdmVzdHJhbmQgPGFsdmVzdHJhbmRAY2lzY28uY29tPohGBBARAgAGBQI8mkf7
AAoJECxtsnzsq0wgLMsAoJSizecoJ22KjP4ZZVNbjVNSoEpNAKDzaAIWmczroetX
jyC/LzB88kYbD4hLBBARAgALBQI57VdYBAsDAQIACgkQOMj+2+WY0F4BEQCgyBri
eNCNJPcW4zOTXS3Qrn7yXZ8AnRFwI7AcmnuLCRxpdbIBegdOtumliQCVAwUQPJmF
R/bvOLj4Q3BxAQH6DAP8Dbsy5PabqJCwCHJK+FGMOsDuQjJ/xT/5EyJNoD+qToqA
ufi3YXdzHwQiqzRDuk+5IH2C2CTfDQluz0fzVU51Tepg1ifHDpw9CutgtuKIMwtV
2xdVG2zt0HX1EJrYKn+j+2XERuWazpzg0tD5XGSDs3QTmXwFGH9+iEmxnIr8BdWI
RgQQEQIABgUCPJpIcAAKCRB+XMqa2mJAQ9IrAJ4uekVx3BAE0QgLhgsLzmprBsRS
pACgiBVx+frUbc+OwzatH0Qw4YHQZ5uIRgQQEQIABgUCPJqa0AAKCRC19k0aStFl
tLThAKCBZQ5kygMT52cJhPFztRokBbkeHgCeLlNRc8kW7T0BLjSXz1IR7/p57b+I
RgQQEQIABgUCPJmB9wAKCRDJdCX7rktdktivAJ94d4+4yNaHEErUh317EGFBP+VZ
EwCfY1xSbk0bJXgudEkFEO56lJ89OcyIRgQSEQIABgUCPWF7JQAKCRBKLj+mWkQq
tCKeAJwOw8jkuNgxQzIxmHQW957YSPCOOQCeKiczzGl3nOAxneASFmFlYY9mtoi0
NkhhcmFsZCBUdmVpdCBBbHZlc3RyYW5kIDxIYXJhbGQuQWx2ZXN0cmFuZEBtYXh3
YXJlLm5vPohLBBARAgALBQI0uhrHBAsDAQIACgkQOMj+2+WY0F7TeQCdG8oJcRO1
gCPJxx+l5dJRrLsb8WAAn1uiwYkq88isen8te0JVp8S77IG+iQBVAwUQN8mCVjPw
VTwXXgE5AQELbQIAlSNjw8cZweHavNYpnSw7o0kz2zQfTwTj1jaD/9r8JfCuUtRN
Axedu4Bwf9ncyNBloDZovO0t6EldFoLOUDNObYhLBBARAgALBQI0uhrHBAsDAQIA
CgkQOMj+2+WY0F7TeQCdG8oJcRO1gCPJxx+l5dJRrLsb8WAAn1uiwYkq88isen8t
e0JVp8S77IG+iEYEEBECAAYFAjyZbDQACgkQ4hFoDYCwek9q4ACeKoVffu1lM1Vc
ax3Len68OpFcnMQAoOGUOTUiUiS+IopiutebdXN+SzUQiQCVAgUQPJlsN0QVcM1G
a0KJAQGNIQP/TQWP9e6UGklD/FlC2xzyU0ttQTQdUVF5ADp2wRunZii42Z2QmVjK
yuV5h+EPtK2go+Bo+Cc1P2T7GidQ+eFKFnURjMWv3CJqWhY5n4Ol8Tbeok6JVujS
13VAXWMOxAsfKMesWphbwMOSKw2PSqO9SKhi6pXsYif+FfrN/57ZDJ2IRgQQEQIA
BgUCPJlsOQAKCRDtOjnjk2dMQB0dAJ9v2XbRM6QrfN/yEbnDW+CYyIMM4ACfVZL/
SI81Uz96EsZLYFQ1RE7q+fGIRgQQEQIABgUCPJpH+wAKCRAsbbJ87KtMINTBAKD1
eG0gGdf7nz2J41Y/6t9T7W8QTgCcDdFHL6Ip4rIFnDibX27IHVycePWIRgQQEQIA
BgUCOCrmrAAKCRA2ey1g5dsu2rB2AJ9RtyOxdCIiJ2F960ti8Dr91l2xVgCdGEQy
ej8bnsioO5luU4Fmx3mn64WJAJUDBRA8mYVH9u84uPhDcHEBASrWBACI/L5BAzXz
nM4ETTzh9MNtzmnpDZRpnmtQCBF49c4o2ZKBDmuc4YnE9nLCGUy7Eq94wJHLfWPO
QL/yRCU3eo+30SJxtMWB61MJbTRYXcgEQWVrFSW9NlRZBtlRiR5/NXhAQ9LpgCSX
eBuSAtn5lfeWz0oAlvhmmp/Ec+XV38Gs+ohGBBARAgAGBQI8mh6iAAoJEPyNdnM8
hiYP3GEAmwQ22P+1YBpC3KvML2LdFyuEyss2AJwKqL/A4xyLrI3/0h5O+Pkw75WM
IIg/AwUQOCo6hP1viMYh0KcbEQKEUACg5iL+XcPQjDXZXGcSNEm9P6yccCgAoPvD
UU4zkX+8oORwUsQAggLYMJxIiEYEEBECAAYFAjyaSHAACgkQflzKmtpiQEOrUQCf
VlXYu7umgSdS58VnbdQLUf0YrnMAniN7rP85tuIW4UekvInVhumQps8LiEYEEBEC
AAYFAjyamsQACgkQtfZNGkrRZbRiTwCguvacK89s5oJNvCdXbp4Kuj40jfsAn2e7
M9s6ooFSa2o2fCvQVapOPVl0uQINBDS6GscQCAD2Qle3CH8IF3KiutapQvMF6PlT
ETlPtvFuuUs4INoBp1ajFOmPQFXz0AfGy0OplK33TGSGSfgMg71l6RfUodNQ+PVZ
X9x2Uk89PY3bzpnhV5JZzf24rnRPxfx2vIPFRzBhznzJZv8V+bv9kV7HAarTW56N
oKVyOtQa8L9GAFgr5fSI/VhOSdvNILSd5JEHNmszbDgNRR0PfIizHHxbLY7288kj
wEPwpVsYjY67VYy4XTjTNP18F1dDox0YbN4zISy1Kv884bEpQBgRjXyEpwpy1obE
AxnIByl6ypUM2Zafq9AKUJsCRtMIPWakXUGfnHy9iUsiGSa6q6Jew1XpMgs7AAIC
B/9J9wrndAwIvmz9zESxfhhl+0bWeGeqnBrEzxBmAvR8l7XoVGMSatLWnSPsRHc/
3FX5MPLiWl2xHZq6PACS81zZ4oMVlAIpbxXX3hxSd+bnw97lU58xPiYv54dtnvl0
5M2IORAxpvdi47KqU4wyRMBpE6XgdedgN/CScGYrg8Gxsm7RyEyn2+rwoqgB2DPr
7Dpje2Z6V3vjEx/Py2D08gmojPdQoag95w0M7RsdZfCdeMM7/DXV0nQOlvWxqaSt
Legll8oezptToXazPE8H7X5hIZrBq19/ykxN5QID0u1waVBTqH27V9pZrbd/7ODA
BLFKRqQD4YkzPGFSocEopo6wiD8DBRg0uhrHOMj+2+WY0F4RAmEmAJ44ZGVqiQRJ
kAaCzw38YHZ8Lj/fMACfW81iHlyC1IrrsJnc4xlyv8oeBQs=
=e5ID
-----END PGP PUBLIC KEY BLOCK-----





From owner-ietf@ietf.org  Wed Jun  4 08:30:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14314
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 08:30:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NX2J-0000C4-MD
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 08:06:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NWtH-0006Qn-2G
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 07:57:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12844
	for <ietf@ietf.org>; Wed, 4 Jun 2003 07:57:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NWrT-00015u-00
	for ietf@ietf.org; Wed, 04 Jun 2003 07:55:23 -0400
Received: from p2.piuha.net ([131.160.192.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NWrT-00015r-00
	for ietf@ietf.org; Wed, 04 Jun 2003 07:55:23 -0400
Received: from piuha.net (p4.piuha.net [131.160.192.4])
	by p2.piuha.net (Postfix) with ESMTP
	id 5BB3A6A902; Wed,  4 Jun 2003 14:57:11 +0300 (EEST)
Message-ID: <3EDDDE31.9020804@piuha.net>
Date: Wed, 04 Jun 2003 14:55:29 +0300
From: Jari Arkko <jari.arkko@piuha.net>
Reply-To: jari.arkko@piuha.net
Organization: None
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Michael Thomas <mat@cisco.com>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: authenticated email
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu> <016c01c32960$56b1adb0$46124104@eagleswings> <16092.51912.740900.110873@thomasm-u1.cisco.com> <70660000.1054674804@askvoll.hjemme.alvestrand.no> <16093.10524.494835.396218@thomasm-u1.cisco.com> <3EDD8B91.1030509@piuha.net> <20030604112004.GA10522@think>
In-Reply-To: <20030604112004.GA10522@think>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Theodore Ts'o wrote:

> Signed e-mail is useful for assuring that e-mail message sent at one
> point in time is the same as an e-mail message sent earlier.  (Not
> necessarily just for list mail, but also for person-to-person mail.)
...
> For the specialized case of preventing SPAM, it's not necessarily
> necessary to do the full authenticated e-mail where we know the
...
> someone, your public key figureprint must either be on a list of
> acceptable senders, or you must submit some kind of mathematical
> evidence that you have spent 5-10 minutes of CPU time crunching on
> some particular problem. 

Agreed. CPU time falls under the same class of schemes as the
address validity test that we already have for list e-mail; the
spammer has to invest more time and money, and have a bigger
risk of capture, the more we demand from unknown senders.

On list enrollment, you could even demand that the same address
be valid for some time, such as a day, through a delayed validation
scheme. Hit and run spammers might not be able to use the same
mail address for a very long time. Could we use the same for
person-to-person e-mail? If I read the spam a day after it has
been sent, will the spammer's mail agent still be there for
an automatic ack that the address is valid?

In general, I'm very much in favor of these types of mechanisms
as opposed to a knee jerk "lets authenticate everyone and see
if it helps" approaches ;-)

(This doesn't mean that such mechanisms are ready to be deployed
and problem free in all cases.)

> Yeah, some special provision would be needed for CPU-limited PDA's,
> but most PDA's that I've seen don't attempt to talk to the network
> directly; they generally go through some kind of mutually trusted
> gateway box that could do the CPU crunching for them. 

And speaking of problems, I do think the imparity between different
devices is a real issue for the CPU time method. *Your* PDA may not
talk to the network directly, but *my* phone runs IMAP, SMTP, SSH,
SSL, HTTP, and streaming video from the net in addition to the usual
office applications such as Doom and C64 emulator ;-) Given this,
some people might argue that my phone can then afford the CPU
crunching as well. Perhaps, but the problem is that while the
capacity in the low-end increases, the same happens for the high-end
as well. I'd claim that the relative speed difference stays
constant over time.

I don't have a good suggestion on how to resolve this, however.
Perhaps the lowest common denominator is still a big enough
deterrent? Note that help from a network entity is not likely
solve this problem. Think about it: the average users are
not going to install their own network helpers. They are going
to rely ISPs' servers. So, we'd see SMTP servers that do the
number crunching on behalf of the ISP's customers. Enter a
spammer who claims to have a small device...

--Jari




From owner-ietf@ietf.org  Wed Jun  4 09:58:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19696
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 09:58:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NY5f-0003cR-H3
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 09:14:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NXCg-0000Kv-Iz
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 08:17:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13914
	for <ietf@ietf.org>; Wed, 4 Jun 2003 08:17:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NXAt-0001Iw-00
	for ietf@ietf.org; Wed, 04 Jun 2003 08:15:27 -0400
Received: from motgate6.mot.com ([144.189.100.106])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NXAs-0001It-00
	for ietf@ietf.org; Wed, 04 Jun 2003 08:15:26 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate6.mot.com (Motorola/Motgate6) with ESMTP id h54CGtj5016774;
	Wed, 4 Jun 2003 05:17:12 -0700 (MST)
Received: from thorgal.crm.mot.com (thorgal.crm.mot.com [140.101.173.1])
	by il06exr04.mot.com (Motorola/il06exr04) with ESMTP id h54CGpcl031057;
	Wed, 4 Jun 2003 07:16:53 -0500
Received: from nal.motlabs.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id 4DE0D2EC95; Wed,  4 Jun 2003 14:16:50 +0200 (CEST)
Message-ID: <3EDDE332.7060402@nal.motlabs.com>
Date: Wed, 04 Jun 2003 14:16:50 +0200
From: Alexandru Petrescu <petrescu@nal.motlabs.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org
Subject: Re: authenticated email
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu> <016c01c32960$56b1adb0$46124104@eagleswings> <16092.51912.740900.110873@thomasm-u1.cisco.com> <70660000.1054674804@askvoll.hjemme.alvestrand.no> <3EDDD1B3.9080700@nal.motlabs.com> <133600000.1054725926@askvoll.hjemme.alvestrand.no>
In-Reply-To: <133600000.1054725926@askvoll.hjemme.alvestrand.no>
X-Enigmail-Version: 0.72.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-MIME-Autoconverted: from 8bit to quoted-printable by motgate6.mot.com id h54CGtj5016774
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA19696

Harald Tveit Alvestrand wrote:
> nope. we have had a lot of PGP key signing parties at IETFs, but 
> nothing "official".

I see, I might want to attend.

 From what I've read, keys (or fingerprints?) were read aloud.

> I generally use wwwkeys.eu.pgp.net when I look for keys, but there's 
> nothing very magical about that.

I see.  So your trust basically relies on the integrity of that
particular server.

>> Did you store the key securely on the keyserver?
> 
> 
> Why should I? It's signed, so it's either there or not there - you 
> can't fake it, just remove it.

Can't I just create a public key with the Harald's name and email
address and then post to this list claiming I'm Harald?

> (And sometimes I wish the keyservers WOULD drop some keys - there's 
> an old key of mine out there that I don't use any more....)

Sure, they should.

>> Which keyserver?  Which port?  The particular network I connect to 
>> is blocking most ports, so I can't retrieve your public key.
> 
> 
> It's attached below, too. Anything to increase the 
> Kbytes-posting-stats :­

Thank you, I imported it, but the signature of previous messages didn't
verify, sorry.

Alex
GBU




From owner-ietf@ietf.org  Wed Jun  4 10:00:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19904
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 10:00:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NY5h-0003ip-TM
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 09:14:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NXTv-0002Sq-0b
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 08:35:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14879
	for <ietf@ietf.org>; Wed, 4 Jun 2003 08:35:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NXS7-0001aB-00
	for ietf@ietf.org; Wed, 04 Jun 2003 08:33:15 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NXS6-0001Z0-00
	for ietf@ietf.org; Wed, 04 Jun 2003 08:33:14 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id C5C8E622AC; Wed,  4 Jun 2003 14:34:33 +0200 (CEST)
Date: Wed, 04 Jun 2003 14:34:33 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Alexandru Petrescu <petrescu@nal.motlabs.com>
Cc: ietf@ietf.org
Subject: Re: authenticated email
Message-ID: <151700000.1054730073@askvoll.hjemme.alvestrand.no>
In-Reply-To: <3EDDE332.7060402@nal.motlabs.com>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
 <016c01c32960$56b1adb0$46124104@eagleswings>
 <16092.51912.740900.110873@thomasm-u1.cisco.com>
 <70660000.1054674804@askvoll.hjemme.alvestrand.no>
 <3EDDD1B3.9080700@nal.motlabs.com>
 <133600000.1054725926@askvoll.hjemme.alvestrand.no>
 <3EDDE332.7060402@nal.motlabs.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA19904



--On onsdag, juni 04, 2003 14:16:50 +0200 Alexandru Petrescu 
<petrescu@nal.motlabs.com> wrote:

> Harald Tveit Alvestrand wrote:
>> nope. we have had a lot of PGP key signing parties at IETFs, but
>> nothing "official".
>
> I see, I might want to attend.
>
>  From what I've read, keys (or fingerprints?) were read aloud.
>
>> I generally use wwwkeys.eu.pgp.net when I look for keys, but there's
>> nothing very magical about that.
>
> I see.  So your trust basically relies on the integrity of that
> particular server.

not at all. Trust depends on the signatures of the key; I only use the 
keyserver to look for keys I don't have on hand.

>>> Did you store the key securely on the keyserver?
>>
>>
>> Why should I? It's signed, so it's either there or not there - you
>> can't fake it, just remove it.
>
> Can't I just create a public key with the Harald's name and email
> address and then post to this list claiming I'm Harald?

yes, you can. And after all, your real name might be Harald, so I shouldn't 
have a way to stop you from doing that.
However, those who care about whether it's me or you posting will look at 
who signed it - that's why my key block is so huge; it's got all these 
signatures dangling from it....

>
>> (And sometimes I wish the keyservers WOULD drop some keys - there's
>> an old key of mine out there that I don't use any more....)
>
> Sure, they should.
>
>>> Which keyserver?  Which port?  The particular network I connect to
>>> is blocking most ports, so I can't retrieve your public key.
>>
>>
>> It's attached below, too. Anything to increase the
>> Kbytes-posting-stats :­
>
> Thank you, I imported it, but the signature of previous messages didn't
> verify, sorry.
>
I know - signing messages that will be damaged in transit is a VERY hard 
problem....







From owner-ietf@ietf.org  Wed Jun  4 10:02:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20148
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 10:02:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NY5r-0003vl-FY
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 09:14:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NXph-0007Cq-3M
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 08:57:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16361
	for <ietf@ietf.org>; Wed, 4 Jun 2003 08:57:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NXnt-00023K-00
	for ietf@ietf.org; Wed, 04 Jun 2003 08:55:46 -0400
Received: from motgate6.mot.com ([144.189.100.106])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NXnt-00023E-00
	for ietf@ietf.org; Wed, 04 Jun 2003 08:55:45 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate6.mot.com (Motorola/Motgate6) with ESMTP id h54CvPj5005148;
	Wed, 4 Jun 2003 05:57:32 -0700 (MST)
Received: from thorgal.crm.mot.com (thorgal.crm.mot.com [140.101.173.1])
	by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id h54CvLdD028870;
	Wed, 4 Jun 2003 07:57:22 -0500
Received: from nal.motlabs.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id 5C2512EC86; Wed,  4 Jun 2003 14:57:21 +0200 (CEST)
Message-ID: <3EDDECB1.6060601@nal.motlabs.com>
Date: Wed, 04 Jun 2003 14:57:21 +0200
From: Alexandru Petrescu <petrescu@nal.motlabs.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org
Subject: Re: authenticated email
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu> <016c01c32960$56b1adb0$46124104@eagleswings> <16092.51912.740900.110873@thomasm-u1.cisco.com> <70660000.1054674804@askvoll.hjemme.alvestrand.no> <3EDDD1B3.9080700@nal.motlabs.com> <133600000.1054725926@askvoll.hjemme.alvestrand.no> <3EDDE332.7060402@nal.motlabs.com> <151700000.1054730073@askvoll.hjemme.alvestrand.no>
In-Reply-To: <151700000.1054730073@askvoll.hjemme.alvestrand.no>
X-Enigmail-Version: 0.72.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald Tveit Alvestrand wrote:
>> Can't I just create a public key with the Harald's name and email 
>> address and then post to this list claiming I'm Harald?
> 
> 
> However, those who care about whether it's me or you posting will 
> look at who signed it - that's why my key block is so huge; it's got
>  all these signatures dangling from it....

So the level of trust depends on the number of signatures?

Can I also ask other lots of people to sign the key I create and then
pretend I'm Harald?

Otherwise, if certain of people who signed your key are "special", or
are highly trusted, can I ask who are those people?

>> Thank you, I imported it, but the signature of previous messages 
>> didn't verify, sorry.
>> 
> I know - signing messages that will be damaged in transit is a VERY 
> hard problem....

Right :-)

Alex
GBU




From owner-ietf@ietf.org  Wed Jun  4 10:04:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20512
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 10:04:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NYg0-0004lx-Qv
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 09:51:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NY2J-00035v-J9
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 09:10:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17742
	for <ietf@ietf.org>; Wed, 4 Jun 2003 09:10:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NY0W-0002U2-00
	for ietf@ietf.org; Wed, 04 Jun 2003 09:08:48 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NY0V-0002SE-00
	for ietf@ietf.org; Wed, 04 Jun 2003 09:08:47 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id DA4746233E; Wed,  4 Jun 2003 15:10:04 +0200 (CEST)
Date: Wed, 04 Jun 2003 15:09:45 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Alexandru Petrescu <petrescu@nal.motlabs.com>
Cc: ietf@ietf.org
Subject: Re: authenticated email
Message-ID: <155660000.1054732185@askvoll.hjemme.alvestrand.no>
In-Reply-To: <3EDDECB1.6060601@nal.motlabs.com>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
 <016c01c32960$56b1adb0$46124104@eagleswings>
 <16092.51912.740900.110873@thomasm-u1.cisco.com>
 <70660000.1054674804@askvoll.hjemme.alvestrand.no>
 <3EDDD1B3.9080700@nal.motlabs.com>
 <133600000.1054725926@askvoll.hjemme.alvestrand.no>
 <3EDDE332.7060402@nal.motlabs.com>
 <151700000.1054730073@askvoll.hjemme.alvestrand.no>
 <3EDDECB1.6060601@nal.motlabs.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========1871016916=========="
Sender: owner-ietf@ietf.org
Precedence: bulk

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

Alexandru,

I think me replying to your questions here is no substitute for reading a=20
good introductory text on PGP....... all this is explained, sometimes in=20
gruesome detail, in the

--On onsdag, juni 04, 2003 14:57:21 +0200 Alexandru Petrescu=20
<petrescu@nal.motlabs.com> wrote:

> Harald Tveit Alvestrand wrote:
>>> Can't I just create a public key with the Harald's name and email
>>> address and then post to this list claiming I'm Harald?
>>
>>
>> However, those who care about whether it's me or you posting will
>> look at who signed it - that's why my key block is so huge; it's got
>>  all these signatures dangling from it....
>
> So the level of trust depends on the number of signatures?
>
> Can I also ask other lots of people to sign the key I create and then
> pretend I'm Harald?
>
> Otherwise, if certain of people who signed your key are "special", or
> are highly trusted, can I ask who are those people?

That's for me and you to decide.... I decide who I trust, you decide who=20
you trust. In my current keyring, I trust only 12 people.....


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

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

iD8DBQE+3e+rOMj+2+WY0F4RApFeAKDCStppX1qN89vDX/kBhukxqq1QPwCfVRHM
APORA1cosnX8MMI42sY8Sjo=
=G2tN
-----END PGP SIGNATURE-----

--==========1871016916==========--




From owner-ietf@ietf.org  Wed Jun  4 10:23:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22239
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 10:23:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NYp7-0006Ag-0t
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 10:01:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LuK6-0002hw-Ii
	for ietf@asgard.ietf.org; Fri, 30 May 2003 20:34:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05481
	for <ietf@ietf.org>; Fri, 30 May 2003 20:34:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LuIS-0003GH-00
	for ietf@ietf.org; Fri, 30 May 2003 20:32:32 -0400
Received: from mxout2.cac.washington.edu ([140.142.33.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LuIR-0003GE-00
	for ietf@ietf.org; Fri, 30 May 2003 20:32:31 -0400
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout2.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h4V0YB5R001390;
	Fri, 30 May 2003 17:34:11 -0700
Received: from TGX200.attbi.com (12-231-115-200.client.attbi.com [12.231.115.200])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h4V0YBQ0028015
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 30 May 2003 17:34:11 -0700
Date: Fri, 30 May 2003 17:34:09 -0700 (Pacific Standard Time)
From: Terry Gray <gray@cac.washington.edu>
To: ietf@ietf.org
Subject: RE: IMAP v. POP (Was: The utilitiy of IP is at stake here)
In-Reply-To: <000a01c326d1$47cddd00$56144104@eagleswings>
Message-ID: <Pine.WNT.4.56.0305301608140.1436@TGX200>
References: <000a01c326d1$47cddd00$56144104@eagleswings>
Slogan: "I get enough exercise just pushing my luck."
Organization: University of Washington;  Computing & Communications
X-X-Sender: gray@mailer23.u.washington.edu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Sorry for the sidebar distraction, those uninterested in POP vs. IMAP
should hit D now...

On Fri, 30 May 2003, Tony Hain wrote:

> Dave Crocker wrote:
> > The POP->IMAP example is excellent, since it really
> > demonstrates my point. IMAP is rather popular in some local
> > area network environments. However it's long history has
> > failed utterly to seriously displace POP on a global scale.
>
> Could that be because from the end user perspective IMAP doesn't provide
> any clear value over POP? Isn't IMAP all about shifting control of the
> mail store from the end user into the hands of the mail administrator?

Tony,
I strongly disagree with your characterization (and I believe Dave's
assessment is only true for residential ISPs, not enterprises.)

My own interest in and support of IMAP is totally driven by my
end-user needs.  IMAP lets me get at my INBOX from any of the multiple
machines I use every day.  IMAP lets me selectively fetch headers and
body parts to save time over slow links.  IMAP lets me access any of
my other incoming or archive folders from anywhere.  IMAP lets me set
status flags on my messages.  IMAP lets me know about new mail arrival
in real-time without hammering the server.

POP offers none of those benefits.  (True, you can fudge #1 via "leave
mail on server", but without any status flags, that's a dismal
option.)  IMAP is a functional superset of POP: it supports not only
"offline" (download-and-delete) access ala POP, but also "online" and
"disconnected" access modes (though I agree with the criticism that
"disconnected" capability, wherein local mail caches are automatically
synchronized with the server, is somewhat "under-represented" in most
IMAP clients.)

People who only use one computer (and who back it up regularly :), may
find relatively little benefit to IMAP --though I'd argue that
selective fetching is an increasingly big deal as low-quality wireless
Internet access becomes commonplace.  Moreover, I believe the trend is
toward more people using multiple devices to access their mail.

Currently it may be true that most residential ISP customers fall into
the single-computer-user category (for their personal mail), but I
suspect an equally important factor is that few of those same
customers have ever heard of IMAP or why they might find it useful. It
is also true that many service providers are concerned about disk use,
and indeed need to expect that IMAP users might keep more mail on
their disks.  Many small residential ISPs offer IMAP (for a sample,
see http://imap.org/products/providers.html) but I don't know of any
really large ones that do (although Milo assured me that @Home was
*going* to... :)

In contrast, I suspect that most enterprises use either Exchange/MAPI
or an IMAP-based solution (and of course Exchange also supports IMAP).
Hybrids are also possible, and those who need IMAP functionality but
wish to maintain control/responsibility for their mail store often run
their own IMAP server.

Therefore I claim that it is highly incorrect to suggest that IMAP
hasn't displaced POP "because from the end user perspective IMAP
doesn't provide any clear value over POP", or because it was "all
about shifting control of the mail store from the end user into the
hands of the mail administrator" --which I can assure you, it was not.

Cheers,

-teg







From owner-ietf@ietf.org  Wed Jun  4 10:33:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22932
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 10:33:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NYp7-0006At-5Q
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 10:01:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19LuYU-0004I6-PH
	for ietf@asgard.ietf.org; Fri, 30 May 2003 20:49:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05906
	for <ietf@ietf.org>; Fri, 30 May 2003 20:49:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LuWq-0003OS-00
	for ietf@ietf.org; Fri, 30 May 2003 20:47:24 -0400
Received: from mxout1.cac.washington.edu ([140.142.32.134])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LuWp-0003OP-00
	for ietf@ietf.org; Fri, 30 May 2003 20:47:23 -0400
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout1.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h4V0n0RG012386;
	Fri, 30 May 2003 17:49:00 -0700
Received: from TGX200.attbi.com (12-231-115-200.client.attbi.com [12.231.115.200])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h4V0n0cx020195
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 30 May 2003 17:49:00 -0700
Date: Fri, 30 May 2003 17:48:58 -0700 (Pacific Standard Time)
From: Terry Gray <gray@washington.edu>
To: Anthony Atkielski <anthony@atkielski.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
In-Reply-To: <0b5e01c32708$4f5f67a0$0a00000a@atkielski.com>
Message-ID: <Pine.WNT.4.56.0305301746050.1436@TGX200>
References: <Pine.LNX.4.44.0305301553050.17819-100000@commander.av8.net>
 <0b5e01c32708$4f5f67a0$0a00000a@atkielski.com>
Slogan: "I get enough exercise just pushing my luck."
Organization: University of Washington;  Computing & Communications
X-X-Sender: gray@mailer23.u.washington.edu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Sat, 31 May 2003, Anthony Atkielski wrote:

> It's easy enough to say "I don't agree with you" without adding
> "because I think you're stupid."

True enough... but "You obviously have no experience..."
is *real* close to "I think you're stupid".

-teg





From owner-ietf@ietf.org  Wed Jun  4 10:36:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23309
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 10:36:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NYp7-0006Bl-U9
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 10:01:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19M8iu-0007m1-LD
	for ietf@asgard.ietf.org; Sat, 31 May 2003 11:56:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04966
	for <ietf@ietf.org>; Sat, 31 May 2003 11:56:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19M8hE-0000BY-00
	for ietf@ietf.org; Sat, 31 May 2003 11:55:05 -0400
Received: from mxout5.cac.washington.edu ([140.142.32.135])
	by ietf-mx with esmtp (Exim 4.12)
	id 19M8hE-0000BV-00
	for ietf@ietf.org; Sat, 31 May 2003 11:55:04 -0400
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout5.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h4VFuht7023381;
	Sat, 31 May 2003 08:56:43 -0700
Received: from TGX200.attbi.com (12-231-115-200.client.attbi.com [12.231.115.200])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h4VFuhQ0010849
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 31 May 2003 08:56:43 -0700
Date: Sat, 31 May 2003 08:56:40 -0700 (Pacific Standard Time)
From: Terry Gray <gray@washington.edu>
To: Anthony Atkielski <anthony@atkielski.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here 
In-Reply-To: <0c3d01c32789$677f3aa0$0a00000a@atkielski.com>
Message-ID: <Pine.WNT.4.56.0305310849420.1436@TGX200>
References: <001601c3276d$e0fafed0$3b00a8c0@tomson.be>
 <0c2b01c32783$26d97390$0a00000a@atkielski.com> <Pine.WNT.4.56.0305310801480.1436@TGX200>
 <0c3d01c32789$677f3aa0$0a00000a@atkielski.com>
Slogan: "I get enough exercise just pushing my luck."
Organization: University of Washington;  Computing & Communications
X-X-Sender: gray@mailer23.u.washington.edu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Sat, 31 May 2003, Anthony Atkielski wrote:

> Terry writes:
>
> > At least one of them is a combination of letters
> > and numbers that I would have expected to
> > resist most dictionary spam attacks.
>
> To whom have you sent e-mail from that address?

In several cases, *no* one.  That is, these were test accounts I set
up for my own purposes and had never used to communicate with others.

> If they didn't use a dictionary attack, and they didn't harvest the address,
> how did they get it?

Beats me.  Perhaps a more sophisticated dictionary attack than I would
have expected.  Or maybe the ISPs sold them.  Or got hacked.  Who
knows?  I'm just reporting that it is happening, and routinely.  I
hear from enough other people of similar experiences to know that this
is not an isolated phenomenon.

-teg





From owner-ietf@ietf.org  Wed Jun  4 10:37:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23455
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 10:37:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NYp8-0006CS-67
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 10:01:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Luyt-00066R-Sj
	for ietf@asgard.ietf.org; Fri, 30 May 2003 21:16:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06726
	for <ietf@ietf.org>; Fri, 30 May 2003 21:16:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LuxF-0003cM-00
	for ietf@ietf.org; Fri, 30 May 2003 21:14:41 -0400
Received: from voo.doo.net ([81.17.45.210])
	by ietf-mx with esmtp (Exim 4.12)
	id 19LuxE-0003cJ-00
	for ietf@ietf.org; Fri, 30 May 2003 21:14:40 -0400
Received: from localhost (localhost [127.0.0.1])
	by voo.doo.net (8.12.8/8.12.6) with ESMTP id h4V1FJC8026081;
	Sat, 31 May 2003 03:15:20 +0200 (CEST)
	(envelope-from marc@schneiders.org)
Date: Sat, 31 May 2003 03:15:19 +0200 (CEST)
From: Marc Schneiders <marc@schneiders.org>
To: <william@elan.net>
cc: Rob Austein <sra+ietf@hactrn.net>, <ietf@ietf.org>
Subject: Re: Last 7 days on the IETF list
In-Reply-To: <Pine.LNX.4.44.0305301736050.20347-100000@sokol.elan.net>
Message-ID: <20030531030526.J25916-100000@voo.doo.net>
X-Preferred-email-to: marc@schneiders.org
X-Other-email-to: marc@venster.nl
X-Organization: Venster (Zeist - NL)
X-URL: http://www.bijt.net/
X-SOA: A.ROOT-SERVERS.ORSC.
X-OS: FreeBSD: The Power to Serve
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

I am sure you are right, but in the list below the bytes and
number-of-messages rankings are more or less identical. Since this is
in the context of overload of the list by a limited number of people,
the number of bytes real contribution is not relevant. People don't
read it anymore. All what counts is number of (slight) irritations
while reading mail and total bytes traffic (if we pay for it).

What you want to know, isn't ascertainable through some log analyzing
script. You have to read all the messages. And we do not do that
anymore.

On Fri, 30 May 2003, at 17:43 [=GMT-0700], william@elan.net wrote:

> I don't think posting message size is quite appropriate as part of your
> statistics and even more particularly as a criteria to order the list.
> Unless I'm mistaken you're calculating bytes for entire message but often
> > 75% comes from another message being replied to and so you can't really
> judge amount of input the actual poster added to the message. If you want
> message bytes statistics, you could try to see what parts of that were
> not from previous message and only calculate size based on that.
>
> On Fri, 30 May 2003, Rob Austein wrote:
>
> > Traffic statistics (as seen from my cave, your milage may vary) for
> > the last seven days on the ietf@ietf.org mailing list.
> >
> > Conclusions, if any, are left as an exercise for the reader.
> >
> >
> >   Messages   |     Bytes       | Who
> > -------+-----+-------+---------+------------------------
> >  11.4% |  53 | 13.9% |  233614 | dean@av8.com
> >  12.2% |  57 | 10.1% |  170963 | anthony@atkielski.com
> >   7.5% |  35 |  7.2% |  121074 | ehall@ehsco.com
> >   3.0% |  14 |  4.8% |   80253 | pdeutsch@earthlink.net
> >   3.9% |  18 |  3.6% |   60755 | valdis.kletnieks@vt.edu
> >   3.4% |  16 |  3.5% |   58293 | alh-ietf@tndh.net
> >   3.6% |  17 |  2.6% |   43278 | michel@arneill-py.sacramento.ca.us
> >   2.8% |  13 |  2.2% |   37288 | moore@cs.utk.edu
> >   2.4% |  11 |  2.3% |   37930 | dwm@xpasc.com
> >   2.1% |  10 |  2.2% |   37479 | vjs@calcite.rhyolite.com
> >   2.1% |  10 |  2.2% |   36561 | iljitsch@muada.com
> >   2.1% |  10 |  1.9% |   31676 | l.wood@eim.surrey.ac.uk
> >   1.9% |   9 |  1.8% |   31053 | shogunx@sleekfreak.ath.cx
> >   1.9% |   9 |  1.8% |   31016 | vixie@vix.com
> >   1.9% |   9 |  1.7% |   27856 | dhc2@dcrocker.net
> >   1.9% |   9 |  1.6% |   27349 | dja2003@hotpop.com
> >   1.9% |   9 |  1.5% |   24511 | sbwoodside@yahoo.com
> >   1.1% |   5 |  2.1% |   34761 | steflist@thor.nma.com
> >   1.7% |   8 |  1.3% |   21321 | jnc@ginger.lcs.mit.edu
> >   1.3% |   6 |  1.7% |   28495 | richard@shockey.us
> >   1.3% |   6 |  1.2% |   19636 | tomson_eric@yahoo.fr
> >   1.3% |   6 |  1.1% |   19259 | jstracke@centive.com
> >   0.9% |   4 |  1.5% |   24586 | john-ietf@jck.com
> >   1.1% |   5 |  1.0% |   16989 | mat@cisco.com
> >   0.9% |   4 |  0.9% |   15992 | avi@bridgewatersystems.com
> >   0.9% |   4 |  0.9% |   14418 | huitema@windows.microsoft.com
> >   0.9% |   4 |  0.8% |   13896 | phoffman@imc.org
> >   0.9% |   4 |  0.7% |   12281 | dee3@torque.pothole.com
> >   0.9% |   4 |  0.7% |   11323 | ietf@soaring.demon.co.uk
> >   0.9% |   4 |  0.7% |   11275 | tjc@ecs.soton.ac.uk
> >   0.6% |   3 |  0.8% |   13511 | darkuncle@darkuncle.net
> >   0.6% |   3 |  0.7% |   12302 | harald@alvestrand.no
> >   0.4% |   2 |  0.9% |   14402 | dws@hunnysoft.com
> >   0.4% |   2 |  0.8% |   14209 | mohta@necom830.hpcl.titech.ac.jp
> >   0.6% |   3 |  0.6% |   10191 | wessorh@ar.com
> >   0.6% |   3 |  0.6% |   10181 | rwelty@averillpark.net
> >   0.6% |   3 |  0.5% |    9109 | lear@cisco.com
> >   0.6% |   3 |  0.5% |    8328 | john.loughney@kolumbus.fi
> >   0.6% |   3 |  0.5% |    7803 | sommerfeld@orchard.arlington.ma.us
> >   0.6% |   3 |  0.5% |    7584 | billc44@citynet.net
> >   0.6% |   3 |  0.4% |    6866 | randy@psg.com
> >   0.2% |   1 |  0.8% |   13680 | soohong.park@samsung.com
> >   0.4% |   2 |  0.5% |    8935 | stephen@sprunk.org
> >   0.4% |   2 |  0.5% |    7722 | tytso@mit.edu
> >   0.4% |   2 |  0.5% |    7620 | rra@stanford.edu
> >   0.4% |   2 |  0.4% |    6916 | jmorris@cdt.org
> >   0.4% |   2 |  0.4% |    6630 | dank@hq.lindsayelec.com
> >   0.4% |   2 |  0.4% |    6470 | dominic.pinto@ieee.org
> >   0.4% |   2 |  0.4% |    6156 | zefram@fysh.org
> >   0.2% |   1 |  0.6% |    9711 | awduche@awduche.com
> >   0.4% |   2 |  0.3% |    5077 | bmanning@isi.edu
> >   0.4% |   2 |  0.3% |    4924 | fritz_saad@hotmail.com
> >   0.4% |   2 |  0.3% |    4618 | ekr@rtfm.com
> >   0.4% |   2 |  0.3% |    4576 | cdel@firsthand.net
> >   0.4% |   2 |  0.3% |    4438 | anewton@ecotroph.net
> >   0.4% |   2 |  0.3% |    4335 | garmitage@swin.edu.au
> >   0.2% |   1 |  0.5% |    7750 | alain.durand@sun.com
> >   0.2% |   1 |  0.4% |    7195 | dws+001@hunnysoft.com
> >   0.2% |   1 |  0.4% |    6953 | bob@wyman.us
> >   0.2% |   1 |  0.4% |    6315 | ggm@apnic.net
> >   0.2% |   1 |  0.4% |    6293 | et7563@sbc.com
> >   0.2% |   1 |  0.4% |    6003 | atul.sabharwal@intel.com
> >   0.2% |   1 |  0.3% |    5766 | hardie@qualcomm.com
> >   0.2% |   1 |  0.3% |    5699 | dhc@dcrocker.net
> >   0.2% |   1 |  0.3% |    5206 | cchaplin@sj.symbol.com
> >   0.2% |   1 |  0.3% |    4923 | peterf@exchange.microsoft.com
> >   0.2% |   1 |  0.3% |    4425 | page@mail.msen.com
> >   0.2% |   1 |  0.3% |    4388 | braendt@hotmail.com
> >   0.2% |   1 |  0.3% |    4306 | gk@ninebynine.org
> >   0.2% |   1 |  0.2% |    4096 | jorge.contreras@haledorr.com
> >   0.2% |   1 |  0.2% |    3465 | inanbe@xs4all.nl
> >   0.2% |   1 |  0.2% |    3310 | hinden@iprg.nokia.com
> >   0.2% |   1 |  0.2% |    3214 | smb@research.att.com
> >   0.2% |   1 |  0.2% |    3194 | gray@washington.edu
> >   0.2% |   1 |  0.2% |    3085 | ole@cisco.com
> >   0.2% |   1 |  0.2% |    3077 | rod.walsh@nokia.com
> >   0.2% |   1 |  0.2% |    2958 | msa@burp.tkv.asdf.org
> >   0.2% |   1 |  0.2% |    2946 | vinton.g.cerf@mci.com
> >   0.2% |   1 |  0.2% |    2782 | swb@employees.org
> >   0.2% |   1 |  0.2% |    2761 | jtk@depaul.edu
> >   0.2% |   1 |  0.2% |    2661 | bob.natale@appliedsnmp.com
> >   0.2% |   1 |  0.2% |    2621 | spencer_dawkins@yahoo.com
> >   0.2% |   1 |  0.1% |    2510 | glc@cisco.com
> >   0.2% |   1 |  0.1% |    2416 | klensin@jck.com
> >   0.2% |   1 |  0.1% |    2323 | braden@isi.edu
> >   0.2% |   1 |  0.1% |    2303 | kent@bbn.com
> >   0.2% |   1 |  0.1% |    2265 | andy.malis@vivacenetworks.com
> >   0.2% |   1 |  0.1% |    2259 | jfbauer@comcast.net
> >   0.2% |   1 |  0.1% |    2175 | benson.schliesser@savvis.net
> >   0.2% |   1 |  0.1% |    1789 | noc@nso.org
> > -------+-----+-------+---------+------------------------
> > 100.0% | 466 |100.0% | 1684907 | Total
> >
>
>






From owner-ietf@ietf.org  Wed Jun  4 10:40:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23833
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 10:40:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NYp8-0006Cp-HI
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 10:01:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NYB1-00044J-Rj
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 09:19:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18126
	for <ietf@ietf.org>; Wed, 4 Jun 2003 09:19:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NY9E-0002aM-00
	for ietf@ietf.org; Wed, 04 Jun 2003 09:17:48 -0400
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NY9E-0002aJ-00
	for ietf@ietf.org; Wed, 04 Jun 2003 09:17:48 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate4.mot.com (Motorola/Motgate4) with ESMTP id h54DJ1FF018344;
	Wed, 4 Jun 2003 06:19:02 -0700 (MST)
Received: from thorgal.crm.mot.com (thorgal.crm.mot.com [140.101.173.1])
	by az33exr04.mot.com (Motorola/az33exr04) with ESMTP id h54DIrVN009760;
	Wed, 4 Jun 2003 08:18:57 -0500
Received: from nal.motlabs.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id 15BB42EC86; Wed,  4 Jun 2003 15:18:53 +0200 (CEST)
Message-ID: <3EDDF1BC.7050602@nal.motlabs.com>
Date: Wed, 04 Jun 2003 15:18:52 +0200
From: Alexandru Petrescu <petrescu@nal.motlabs.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Franck Martin <franck@sopac.org>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>,
        Michael Thomas <mat@cisco.com>, ietf@ietf.org
Subject: Re: authenticated email
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>	 <016c01c32960$56b1adb0$46124104@eagleswings>	 <16092.51912.740900.110873@thomasm-u1.cisco.com>	 <70660000.1054674804@askvoll.hjemme.alvestrand.no> <1054685981.2669.7.camel@localhost>
In-Reply-To: <1054685981.2669.7.camel@localhost>
X-Enigmail-Version: 0.72.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Franck Martin wrote:
> it running at an individual user level with the www.keyservers.net

Which is not secure :-)

> but for TLS NO CA will deliver a certificate that can sign other 
> certificates

One particular CA that is built in some particular MUA's does.

> (corporate e-mail certificates).

Nothing stops somebody working for that corporation to become the CA of
that corporation.  Thus, all people working for that corporation can
rely on that CA to trust each other.  Might fit some needs.

...my current understanding is.

Alex
GBU




From owner-ietf@ietf.org  Wed Jun  4 10:43:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24087
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 10:43:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NYp8-0006D6-Mn
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 10:01:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19MOng-0007q4-0d
	for ietf@asgard.ietf.org; Sun, 01 Jun 2003 05:06:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02845
	for <ietf@ietf.org>; Sun, 1 Jun 2003 05:06:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MOlz-0004vb-00
	for ietf@ietf.org; Sun, 01 Jun 2003 05:05:03 -0400
Received: from prue.eim.surrey.ac.uk ([131.227.76.5] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MOly-0004vY-00
	for ietf@ietf.org; Sun, 01 Jun 2003 05:05:02 -0400
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 19MOnS-000241-00; Sun, 01 Jun 2003 10:06:34 +0100
Date: Sun, 1 Jun 2003 10:06:33 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
cc: ietf@ietf.org
Subject: Re: The IETF_Censored mailing list
In-Reply-To: <20030601021324.GG7127@login.ecs.soton.ac.uk>
Message-ID: <Pine.GSO.4.50.0306011003150.21144-100000@artemis.ee.surrey.ac.uk>
References: <200306010103.h511313O026371@carmen.ipv6.tilab.com>
 <20030601021324.GG7127@login.ecs.soton.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-106.0 required=5.5
	tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_PINE,
	      USER_IN_WHITELIST
	autolearn=ham version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Scanner: exiscan *19MOnS-000241-00*WMp56ZamcpE* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sun, 1 Jun 2003, Tim Chown wrote:

> How timely...

The unsubscribe instructions given below are incomplete. (Still
working on finding the correct ones.)

And you'll still get to listen to Atkielski and Anderson.

L.

> On Sun, Jun 01, 2003 at 03:03:01AM +0200, Super-User wrote:
> >
> >                         The IETF_Censored mailing list
> >
> >    At times, the IETF list is subject to debates that have little to do
> >    with the purposes for which the IETF list was created. Some people
> >    would appreciate a "quieter" forum for the relevant debates that take
> >    place, but the IETF's policy of openness has so far prevented the IETF
> >    from imposing any censorship policy on the IETF@ietf.org list.
> >
> >    To give people an alternative, there is a list called
> >    "ietf_censored@carmen.ipv6.cselt.it".
> >
> >    This list is a sublist (that is, it gets the same messages as) the
> >    open IETF discussion list. However, this list will not forward all
> >    messages; in particular, the filters have been set so that persons and
> >    discussions that are, in the view of Raffaele D'Albenzio, irrelevant
> >    to the IETF list are not forwarded.
> >
> >    Because this filter is automated, the criteria include:
> >      * Well known troublemakers
> >      * Well known crosspostings
> >      * Subjects that have led to recent non-conclusive exchanges
> >      * Some ways to say "unsubscribe"
> >      * Some "out-of-office-reply" messages
> >
> >    To join the list, send the word "subscribe" in the BODY of a message
> >    to ietf_censored-request@carmen.ipv6.cselt.it (the URL here is an RFC
> >    2368 mailto URL that does the Right Thing).
> >
> >    To unsubscribe, send the word "unsubscribe" in the BODY of a message
> >    to ietf_censored-request@carmen.ipv6.cselt.it. Do not send to the list
> >    - your message will be filtered!
> >    (members of the main IETF list itself must follow instructions for
> >    that list, of course. You are only a member of ietf_censored if there
> >    is a comment on the bottom of your IETF list mail saying that the
> >    message has been sent through the ietf_censored list.)
> >
> >    For fun, there is a special list for the rejected messages:
> >    ietf_censored-rejects@carmen.ipv6.cselt.it - subscribe in the same
> >    fashion, by mail to ietf_censored-rejects-request@carmen.ipv6.cselt.it
> >
> >    By public request, the current set of filters are listed at
> >    http://vesuvio.ipv6.tilab.com/cgi-bin/ietf_censored-filters
> >
> >    This page is http://carmen.ipv6.cselt.it/ietf_censored.html, and is
> >    posted monthly in text form to ietf@ietf.org
> >      _________________________________________________________________
> >
> >    Raffaele D'Albenzio < root@carmen.ipv6.cselt.it>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on what to pass are made solely by Raffaele D'Albenzio.
>

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





From owner-ietf@ietf.org  Wed Jun  4 10:49:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24488
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 10:49:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NYp9-0006EG-8V
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 10:01:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NYHe-0004Dd-0R
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 09:26:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18306
	for <ietf@ietf.org>; Wed, 4 Jun 2003 09:26:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NYFq-0002cc-00
	for ietf@ietf.org; Wed, 04 Jun 2003 09:24:38 -0400
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NYFq-0002cX-00
	for ietf@ietf.org; Wed, 04 Jun 2003 09:24:38 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate3.mot.com (Motorola/Motgate3) with ESMTP id h54DQ6Gx006097;
	Wed, 4 Jun 2003 06:26:16 -0700 (MST)
Received: from thorgal.crm.mot.com (thorgal.crm.mot.com [140.101.173.1])
	by il06exr03.mot.com (Motorola/il06exr03) with ESMTP id h54DQ1Ki015918;
	Wed, 4 Jun 2003 08:26:02 -0500
Received: from nal.motlabs.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id 817682EC86; Wed,  4 Jun 2003 15:26:00 +0200 (CEST)
Message-ID: <3EDDF367.6010103@nal.motlabs.com>
Date: Wed, 04 Jun 2003 15:25:59 +0200
From: Alexandru Petrescu <petrescu@nal.motlabs.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: jari.arkko@piuha.net
Cc: Michael Thomas <mat@cisco.com>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: authenticated email
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>	<016c01c32960$56b1adb0$46124104@eagleswings>	<16092.51912.740900.110873@thomasm-u1.cisco.com>	<70660000.1054674804@askvoll.hjemme.alvestrand.no> <16093.10524.494835.396218@thomasm-u1.cisco.com> <3EDD8B91.1030509@piuha.net>
In-Reply-To: <3EDD8B91.1030509@piuha.net>
X-Enigmail-Version: 0.72.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jari Arkko wrote:
> So, its the same old question once again: how do we all enroll 
> ourselves to the same trusted root or web of trust? Should the next 
> PGP key signing party be held in the plenary, for everyone? Or maybe 
> Harald stands in the IETF reception desk to look at people's 
> passports and certifies keys? Hmm... maybe we could make PGP key 
> mandatory in registration, and have the secretariat form a web of 
> trust. At least we could trace every key to a credit card number... 
> sounds pretty good but this wouldn't deal with the folks who don't 
> come to the meetings. Maybe we could turn on mandatory PGP signing 
> for all list e-mail for a year, and at the end of the year make a web
>  of trust for the folks who sent e-mail that year. That wouldn't be 
> perfect, but it would sure reduce the size of queue in front of 
> Harald for the passport check ;-)

Or maybe an IETF CA?

Alex
GBU




From owner-ietf@ietf.org  Wed Jun  4 10:49:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24514
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 10:49:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NYpA-0006Gi-2K
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 10:01:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NYT9-0004TX-CT
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 09:38:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18875
	for <ietf@ietf.org>; Wed, 4 Jun 2003 09:38:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NYRM-0002i7-00
	for ietf@ietf.org; Wed, 04 Jun 2003 09:36:32 -0400
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NYRL-0002i4-00
	for ietf@ietf.org; Wed, 04 Jun 2003 09:36:31 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate4.mot.com (Motorola/Motgate4) with ESMTP id h54Dc9FF000297;
	Wed, 4 Jun 2003 06:38:19 -0700 (MST)
Received: from thorgal.crm.mot.com (thorgal.crm.mot.com [140.101.173.1])
	by az33exr04.mot.com (Motorola/az33exr04) with ESMTP id h54DbbVN027511;
	Wed, 4 Jun 2003 08:38:05 -0500
Received: from nal.motlabs.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id 139452EC86; Wed,  4 Jun 2003 15:37:37 +0200 (CEST)
Message-ID: <3EDDF620.8010808@nal.motlabs.com>
Date: Wed, 04 Jun 2003 15:37:36 +0200
From: Alexandru Petrescu <petrescu@nal.motlabs.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org
Subject: Re: authenticated email
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu> <016c01c32960$56b1adb0$46124104@eagleswings> <16092.51912.740900.110873@thomasm-u1.cisco.com> <70660000.1054674804@askvoll.hjemme.alvestrand.no> <3EDDD1B3.9080700@nal.motlabs.com> <133600000.1054725926@askvoll.hjemme.alvestrand.no> <3EDDE332.7060402@nal.motlabs.com> <151700000.1054730073@askvoll.hjemme.alvestrand.no> <3EDDECB1.6060601@nal.motlabs.com> <155660000.1054732185@askvoll.hjemme.alvestrand.no>
In-Reply-To: <155660000.1054732185@askvoll.hjemme.alvestrand.no>
X-Enigmail-Version: 0.72.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald Tveit Alvestrand wrote:
> I think me replying to your questions here is no substitute for
> reading a good introductory text on PGP....... all this is explained,
> sometimes in gruesome detail, in the

I'm sorry, I didn't want to sound like making questions.

It is correct that I can find the right info on PGP on some introductory
texts.

Alex
GBU




From owner-ietf@ietf.org  Wed Jun  4 11:18:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25760
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 11:18:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NZob-0000f5-K1
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 11:04:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NZ9C-0004WC-Dq
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 10:21:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22179
	for <ietf@ietf.org>; Wed, 4 Jun 2003 10:21:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NZ7P-0003Dj-00
	for ietf@ietf.org; Wed, 04 Jun 2003 10:19:59 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NZ7N-0003Dg-00
	for ietf@ietf.org; Wed, 04 Jun 2003 10:19:58 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h54ELirR016007
	for ietf@ietf.org env-from <vjs>;
	Wed, 4 Jun 2003 08:21:44 -0600 (MDT)
Date: Wed, 4 Jun 2003 08:21:44 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306041421.h54ELirR016007@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: authenticated email
References: <3EDDD1B3.9080700@nal.motlabs.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> allows readers of this email to trust I am who I claim to be, "legally"
> (as if I showed an ID).


"Legally"?--Talk about a disaster in the making, but one that spammers
might save us from by demonstrating it's foolishiness.  Where will
the secret key for signing mail be kept, but in something like an
"address book"?  Will "user friendly" operating systems require a
passphrased for each use of the secret key?--probably not.  Even if
they did, think of the trojan horses you could easly write if you went
over to the dark side.  You might look for the WIN32 "event" that
posts the secret key passphrase "dialog box" and then capture keystrokes.
Or you might mount a dictionary attack on the passphrase using a canned
list of 1000 words plus the user names found on the system.  Or you
might pop-up your own imitation of the passphrase dialog box.  ...
but let's save that fun game for some other time.

The talk (and new laws) about legally binding crypto signing is as
ridiculous as the talk about how "personal firewalls" make unsafe
systems safe.  In the real world, virus and worms turn off "Zone
Alarm" and other "personal firewalls" before they start doing their
real work.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Wed Jun  4 11:18:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25761
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 11:18:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NZob-0000eT-B6
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 11:04:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NZ58-0004ON-Sy
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 10:17:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22087
	for <ietf@ietf.org>; Wed, 4 Jun 2003 10:17:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NZ3L-0003Ci-00
	for ietf@ietf.org; Wed, 04 Jun 2003 10:15:47 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NZ3K-0003CN-00
	for ietf@ietf.org; Wed, 04 Jun 2003 10:15:46 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id KAA12273;
	Wed, 4 Jun 2003 10:11:58 -0400
Date: Wed, 4 Jun 2003 10:13:09 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Michel Py <michel@arneill-py.sacramento.ca.us>
cc: IETF Discussion <ietf@ietf.org>, <harald@alvestrand.no>
Subject: RE: This IETF discussion list
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F506719E@server2000.arneill-py.sacramento.ca.us>
Message-ID: <Pine.LNX.4.44.0306041003340.1028-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

This also seems to fall into the definition of intimidation. Other similar
messages by Michel Py have been included below.

I ask the Chair to take the appropriate action.

		--Dean

On Tue, 3 Jun 2003, Michel Py wrote:

> Added to the pro-troll and pro-spammer list: Richard Perlman.
>
> Michel.
>
>
> -----Original Message-----
> From: Richard Perlman [mailto:perl@lucent.com]
> Sent: Tuesday, June 03, 2003 6:53 PM
> To: 'IETF Discussion'
> Cc: harald@alvestrand.no
> Subject: Re: This IETF discussion list
>
> All:
>
> I have been loosely tracking the SPAM discussion and really had nothing
> significant to add.  However, a related posting did catch my attention
> and interest, enough so to warrant a response.
>
> While I certainly am not interested in taking sides on the personal
> accusations that have been seen recently, I do have serious concerns
> about the message quoted below.  I personally detest the daily deluge of
> unwanted unsolicited e-mails I receive.  However, I would be even more
> upset to find that one's belief or support for or against any topic
> should be the criteria by which their contributions were judged.
>
> As despicable as I may find the concepts, opinions and thoughts of
> others, a world in which the expression of only those ideas that I found
> acceptable would be far worse.
>
> Having said that, I do want to be clear, that while I think there needs
> to be freedom for expression of ideas, that expression must be done in a
> way that encourages discussion and values the participation of everyone.
> There is no room for personal remarks and attacks in a conversation of
> ideas.
>
> Richard
>
> On 6/3/03 15:00, "Dean Anderson" <dean@av8.com> quoted:
> > ==================
> > Date: Fri, 30 May 2003 02:09:25 +0200
> > From: "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr>
> > To: 'Eric A. Hall' <ehall@ehsco.com>, 'John Stracke'
> > <jstracke@centive.com>
> > Cc: ietf@ietf.org
> > Subject: RE: spam
> >
> > Guys,
> >
> > Dean Anderson obviously supports and defends SPAM.
> > No further conversation with him could lead to anything constructive.
> > Stop feeding the Troll, now.
> >
> > E.T.
>
>
>
>



================
Date: Sun, 25 May 2003 13:39:24 -0700
From: Michel Py <michel@arneill-py.sacramento.ca.us>
To: ietf@ietf.org
Subject: RE: spam

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

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

Michel.
================


Date: Mon, 26 May 2003 21:30:39 -0700
From: Michel Py <michel@arneill-py.sacramento.ca.us>
To: Paul Vixie <vixie@vix.com>, ietf@ietf.org
Subject: RE: spam

> Paul Vixie wrote:
> warning, i'm answering an obvious troll from an obvious spammer.
> hit D now.

Yeah I think we should work on a system to ban obvious spammers from
IETF lists. Maybe we should also ban people that are so full of it that
they could double as a sceptic tank such as the ones that try to convey
the idea that handling spam has no cost.

Paul, I'm curious: why are you wasting your time with this? Any
withdrawals from not fighting it on a daily basis?

=================







From owner-ietf@ietf.org  Wed Jun  4 11:24:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23305
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 10:36:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NYp7-0006BW-PD
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 10:01:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19M7xr-0006HH-FQ
	for ietf@asgard.ietf.org; Sat, 31 May 2003 11:08:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04067
	for <ietf@ietf.org>; Sat, 31 May 2003 11:08:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19M7wB-0007iN-00
	for ietf@ietf.org; Sat, 31 May 2003 11:06:28 -0400
Received: from mxout5.cac.washington.edu ([140.142.32.135])
	by ietf-mx with esmtp (Exim 4.12)
	id 19M7wB-0007iJ-00
	for ietf@ietf.org; Sat, 31 May 2003 11:06:27 -0400
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout5.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h4VF85t7021608;
	Sat, 31 May 2003 08:08:05 -0700
Received: from TGX200.attbi.com (12-231-115-200.client.attbi.com [12.231.115.200])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h4VF84cx001257
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 31 May 2003 08:08:05 -0700
Date: Sat, 31 May 2003 08:08:02 -0700 (Pacific Standard Time)
From: Terry Gray <gray@washington.edu>
To: Anthony Atkielski <anthony@atkielski.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here 
In-Reply-To: <0c2b01c32783$26d97390$0a00000a@atkielski.com>
Message-ID: <Pine.WNT.4.56.0305310801480.1436@TGX200>
References: <001601c3276d$e0fafed0$3b00a8c0@tomson.be>
 <0c2b01c32783$26d97390$0a00000a@atkielski.com>
Slogan: "I get enough exercise just pushing my luck."
Organization: University of Washington;  Computing & Communications
X-X-Sender: gray@mailer23.u.washington.edu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Sat, 31 May 2003, Anthony Atkielski wrote:

> > I did. I created more than one e-mail address
> > without ever making them public, and though I
> > note some of them receive SPAM!
>
> Were the addresses along the lines of "postmaster," "info," or "webmaster,"
> by chance?

> They must either harvest them or guess them.  For non-obvious e-mail
> addresses that are never published, they cannot practically do either of
> these, and so the addresses will not be spammed.

I have several accounts where the address has never been posted or
even used in any public way... They *all* get spam (and none of them
are generic addresses e.g. "info".)  At least one of them is a
combination of letters and numbers that I would have expected to
resist most dictionary spam attacks.  It did not.

-teg





From owner-ietf@ietf.org  Wed Jun  4 11:32:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26698
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 11:32:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NZqn-0000mn-Ob
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 11:06:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NZJY-00052F-CB
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 10:32:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22878
	for <ietf@ietf.org>; Wed, 4 Jun 2003 10:32:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NZHl-0003MC-00
	for ietf@ietf.org; Wed, 04 Jun 2003 10:30:41 -0400
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NZHk-0003M9-00
	for ietf@ietf.org; Wed, 04 Jun 2003 10:30:40 -0400
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com for <ietf@ietf.org>;
          Wed, 4 Jun 2003 10:32:27 -0400
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: IMAP v. POP 
Date: Wed, 4 Jun 2003 10:32:27 -0400
Message-ID: <20030604143227752.AAA396@hq.lindsayelec.com@rflooker1>
Sender: owner-ietf@ietf.org
Precedence: bulk

Lots of users don't like you have to be connected to IMAP to do routine
things fulltime.

If your paying by the minute for CDMA2000, (for instance), getting frozen
out of doing anything when your not connected turns people off.

Network people like the reduced traffic on the network for POP logins than
endlessly return "0" or whatever for 'LIST', when there is nothing to pickup.

Hard tradeoffs, really.

Regs
Dan




From owner-ietf@ietf.org  Wed Jun  4 11:51:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27775
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 11:51:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NaCX-0002Gg-Um
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 11:29:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NBqV-0004AK-1F
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 09:28:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03837
	for <ietf@ietf.org>; Tue, 3 Jun 2003 09:28:56 -0400 (EDT)
From: auto-responder@list.cren.net
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NBoj-0005y6-00
	for ietf@ietf.org; Tue, 03 Jun 2003 09:27:09 -0400
Received: from taku.cren.net ([128.8.10.25])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NBoj-0005y3-00
	for ietf@ietf.org; Tue, 03 Jun 2003 09:27:09 -0400
Received: (from mailnull@localhost)
	by taku.cren.net (Pro-8.9.3/Pro-8.9.3) id JAA19303
	for ietf@ietf.org; Tue, 3 Jun 2003 09:28:57 -0400 (EDT)
Date: Tue, 3 Jun 2003 09:28:57 -0400 (EDT)
Message-Id: <200306031328.JAA19303@taku.cren.net>
X-Authentication-Warning: taku.cren.net: mailnull set sender to auto-responder@list.cren.net using -r
To: ietf@ietf.org
Subject: Re: Approved
X-Loop: auto-responder@list.cren.net
Sender: owner-ietf@ietf.org
Precedence: bulk

The mailext list has moved from the ListProc server on list.cren.net
to a Majordomo server at icm.org.  This change has (among other) the
following effects:

1) List messages should be sent to "mailext@icm.org".
2) List commands should be sent to "mailext-requests@icm.org".

 





The text of your message is included below:

----------forwarded message----------

This is a multipart message in MIME format

--CSmtpMsgPart123X456_000_742EA9E3
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Please see the attached file.
--CSmtpMsgPart123X456_000_742EA9E3--






From owner-ietf@ietf.org  Wed Jun  4 11:52:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27834
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 11:52:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NaCY-0002HS-BN
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 11:29:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NMCy-0002jn-Rb
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 20:32:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01307
	for <ietf@ietf.org>; Tue, 3 Jun 2003 20:32:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NMBC-0004KK-00
	for ietf@ietf.org; Tue, 03 Jun 2003 20:31:02 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NMBC-0004KE-00
	for ietf@ietf.org; Tue, 03 Jun 2003 20:31:02 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0.6)
  with ESMTP-TLS id 210018 for ietf@ietf.org; Tue, 03 Jun 2003 19:32:21 -0500
Message-ID: <3EDD3E2F.1000300@ehsco.com>
Date: Tue, 03 Jun 2003 19:32:47 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: discussion redirect
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I've setup a temporary mailing list to handle discussion of an alternate
mail transfer system, which I expect will get replaced by a real list
eventually, assuming that interest continues to progress. To subscribe to
that list, send an email message to mt2-subscribe@ehsco.com

I've also put together a basic outline proposal that shows what I'd like
to see in such a service. http://www.ehsco.com/misc/mt2/ has that proposal
(if it doesn't display right, you can download the original powerpoint
slides from http://www.ehsco.com/misc/mt2/MT2-00.ppt). I know that Keith
was scratching some ideas together for reusing SMTP and I'll post that if
he wants. Anybody that has any other proposals, let me know and I'll post
those too. We can discuss any or all of those on the mailing list. We
should probably move out of here anyway, before we get evicted.

Thanks

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






From owner-ietf@ietf.org  Wed Jun  4 11:52:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27888
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 11:52:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NaCY-0002Gr-3V
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 11:29:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NFxJ-0003aw-W4
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 13:52:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16560;
	Tue, 3 Jun 2003 13:52:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NFvX-00014Y-00; Tue, 03 Jun 2003 13:50:27 -0400
Received: from guelah.shrubbery.net ([198.58.5.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NFvW-00014Q-00; Tue, 03 Jun 2003 13:50:26 -0400
Received: by guelah.shrubbery.net (Postfix, from userid 7053)
	id B9B4717CFEC; Tue,  3 Jun 2003 17:52:14 +0000 (UTC)
Date: Tue, 3 Jun 2003 17:52:14 +0000
From: john heasley <heas@shrubbery.net>
To: The IESG <iesg-secretary@ietf.org>
Cc: ietf@ietf.org, RFC Editor <rfc-editor@isi.edu>,
        Internet Architecture Board <iab@iab.org>
Subject: Re: Protocol Action: NOPEER community for BGP route scope control to BCP
Message-ID: <20030603175214.GC7578@shrubbery.net>
References: <200306021524.LAA11839@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200306021524.LAA11839@ietf.org>
User-Agent: Mutt/1.4i
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: awe, not the good cheek
Sender: owner-ietf@ietf.org
Precedence: bulk

please note that the ptomaine list, formerly ptomaine@shrubbery.net, has
been consumed by GROW.

Date: Fri, 2 May 2003 13:29:11 -0700
       The PTOMAINE mailing list is in the process of being
        retired. GROW is taking its place. If you are not already
        on the GROW list and want to subscribe, the information is: 

          General Discussion:  grow@lists.uoregon.edu
          To Subscribe:        majordomo@lists.uoregon.edu (subscribe grow)
          Archive:             http://darkwing.uoregon.edu/~llynch/grow

Mon, Jun 02, 2003 at 11:24:35AM -0400, The IESG:
> 
> The IESG has approved the Internet-Draft 'NOPEER community for BGP
> route scope control' <draft-ietf-ptomaine-nopeer-03.txt> as a BCP.
> This document is the product of the Prefix Taxonomy Ongoing Measurement
> & Inter Network Experiment Working Group. The IESG contact persons are
> Randy Bush and Bert Wijnen.
> 
>  Technical Summary
>    
>    This document proposes the use of a BGP community to advise BGP
>    peers and others on the scope of propagation the originating AS
>    intended for a prefix. This proposed well-known advisory
>    transitive community is intended to allow an origin AS to specify
>    the extent to which it suggests that a specific prefix should be
>    externally propagated. In particular this community, termed here
>    as NOPEER, allows an origin AS to suggest that a route with this
>    attribute need not be advertised across bilateral peer
>    connections.
>    
>  Working Group Summary
>    
>    There were no technical issues raised in working group discussion
>    or working group last call.
>    
>  Protocol Quality
>    
>    This document was reviewed for the IESG by Randy Bush.





From owner-ietf@ietf.org  Wed Jun  4 11:53:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28067
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 11:53:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NaCY-0002HY-Fh
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 11:29:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NN7H-0004wL-8d
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 21:31:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03171
	for <ietf@ietf.org>; Tue, 3 Jun 2003 21:31:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NN5U-0004uK-00
	for ietf@ietf.org; Tue, 03 Jun 2003 21:29:12 -0400
Received: from smtp6.mindspring.com ([207.69.200.110])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NN5T-0004uG-00
	for ietf@ietf.org; Tue, 03 Jun 2003 21:29:11 -0400
Received: from dialup-65.56.122.165.dial1.dallas1.level3.net ([65.56.122.165] helo=ix.netcom.com)
	by smtp6.mindspring.com with esmtp (Exim 3.33 #1)
	id 19NN7D-0005ek-00; Tue, 03 Jun 2003 21:30:59 -0400
Message-ID: <3EDD6751.C506AF16@ix.netcom.com>
Date: Tue, 03 Jun 2003 20:28:18 -0700
From: Jeff Williams <jwkckid1@ix.netcom.com>
Organization: INEGroup Spokesman
X-Mailer: Mozilla 4.08 [en] (Win95; U; 16bit)
MIME-Version: 1.0
To: johnmacsgroup@yahoogroups.com, Joe Baptista - New <baptista@dot-god.com>
CC: IETF <ietf@ietf.org>
Subject: Re: [johnmacsgroup] Internet Voting and user participation systems - Research question
	 from Baptista
References: <Pine.LNX.4.33.0306031032560.29512-100000@dot-god.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Joe and all,

  Thanks Joe.   You should send this to the E-Vote list as well.


I'm doing research on what is available with respect to web based (or

> email) interfaces that support political participation at the grass roots
> level (bottom up).  This includes voting and organizational systems or
> user based communities.
>
> Please email me back private - especially if your getting this message in
> a newsgroup so i don't inadvertently miss it.
>
> cheers
> joe baptista
>
> Joe Baptista - only at www.baptista.god
>
> "Those are mercenaries. Most probably they will be treated as
> mercenaries, hirelings and as war criminals. ... For sure,
> international law does not apply to those"
>  ... Muhammed Saeed al-Sahaf former Iraqi Information Minister
>
> ------------------------ Yahoo! Groups Sponsor ---------------------~-->
> Get A Free Psychic Reading! Your Online Answer To Life's Important Questions.
> http://us.click.yahoo.com/Lj3uPC/Me7FAA/ySSFAA/XgSolB/TM
> ---------------------------------------------------------------------~->
>
> To unsubscribe from this group, send an email to:
> johnmacsgroup-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

--
Jeffrey A. Williams
Spokesman for INEGroup LLA. - (Over 131k members/stakeholders strong!)
"Be precise in the use of words and expect precision from others" -
    Pierre Abelard
================================================================
CEO/DIR. Internet Network Eng. SR. Eng. Network data security
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number: 214-244-4827 or 214-244-3801







From owner-ietf@ietf.org  Wed Jun  4 12:02:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28669
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 12:02:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NaCY-0002Hg-KR
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 11:29:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NOJ0-0006nT-Ic
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 22:47:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05034
	for <ietf@ietf.org>; Tue, 3 Jun 2003 22:47:11 -0400 (EDT)
From: william@elan.net
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NOHE-0005Ty-00
	for ietf@ietf.org; Tue, 03 Jun 2003 22:45:24 -0400
Received: from sokol.elan.net ([216.151.192.200])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NOHD-0005Tv-00
	for ietf@ietf.org; Tue, 03 Jun 2003 22:45:23 -0400
Received: from sokol.elan.net (localhost.localdomain [127.0.0.1])
	by sokol.elan.net (8.12.5/8.12.5) with ESMTP id h53NwPII003499;
	Tue, 3 Jun 2003 16:58:25 -0700
Received: from localhost (william@localhost)
	by sokol.elan.net (8.12.5/8.12.5/Submit) with ESMTP id h53NwO01003495;
	Tue, 3 Jun 2003 16:58:24 -0700
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Tue, 3 Jun 2003 16:58:24 -0700 (PDT)
To: Michel Py <michel@arneill-py.sacramento.ca.us>
cc: IETF Discussion <ietf@ietf.org>
Subject: RE: This IETF discussion list
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F506719E@server2000.arneill-py.sacramento.ca.us>
Message-ID: <Pine.LNX.4.44.0306031644550.1111-100000@sokol.elan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

You can add me as well if you like, but I really think its your own reply 
that was not fair. There is nothing from Richard's email that suggested 
he's "pro-spammer" or "pro-troll". It's all regarding quility of discussions
on this list which have seriously deteriorated in the past week and his 
message about keeping your personal attacks out of the list and not 
judging somebody just based on what he/she believes is absolutly right.

On Tue, 3 Jun 2003, Michel Py wrote:

> Added to the pro-troll and pro-spammer list: Richard Perlman.
> 
> Michel.
> 
> 
> -----Original Message-----
> From: Richard Perlman [mailto:perl@lucent.com] 
> Sent: Tuesday, June 03, 2003 6:53 PM
> To: 'IETF Discussion'
> Cc: harald@alvestrand.no
> Subject: Re: This IETF discussion list
> 
> All:
> 
> I have been loosely tracking the SPAM discussion and really had nothing
> significant to add.  However, a related posting did catch my attention
> and
> interest, enough so to warrant a response.
> 
> While I certainly am not interested in taking sides on the personal
> accusations that have been seen recently, I do have serious concerns
> about
> the message quoted below.  I personally detest the daily deluge of
> unwanted
> unsolicited e-mails I receive.  However, I would be even more upset to
> find
> that one's belief or support for or against any topic should be the
> criteria
> by which their contributions were judged.
> 
> As despicable as I may find the concepts, opinions and thoughts of
> others, a
> world in which the expression of only those ideas that I found
> acceptable
> would be far worse.
> 
> Having said that, I do want to be clear, that while I think there needs
> to
> be freedom for expression of ideas, that expression must be done in a
> way
> that encourages discussion and values the participation of everyone.
> There
> is no room for personal remarks and attacks in a conversation of ideas.
> 
> Richard
> 
> On 6/3/03 15:00, "Dean Anderson" <dean@av8.com> quoted:
> > ==================
> > Date: Fri, 30 May 2003 02:09:25 +0200
> > From: "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr>
> > To: 'Eric A. Hall' <ehall@ehsco.com>, 'John Stracke'
> > <jstracke@centive.com>
> > Cc: ietf@ietf.org
> > Subject: RE: spam
> > 
> > Guys,
> > 
> > Dean Anderson obviously supports and defends SPAM.
> > No further conversation with him could lead to anything constructive.
> > Stop feeding the Troll, now.
> > 
> > E.T.
> 
> 







From owner-ietf@ietf.org  Wed Jun  4 12:04:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28833
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 12:04:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NaCY-0002I8-QX
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 11:29:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NOZd-000756-FR
	for ietf@asgard.ietf.org; Tue, 03 Jun 2003 23:04:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05218
	for <ietf@ietf.org>; Tue, 3 Jun 2003 23:04:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NOXr-0005WD-00
	for ietf@ietf.org; Tue, 03 Jun 2003 23:02:35 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NOXq-0005W9-00
	for ietf@ietf.org; Tue, 03 Jun 2003 23:02:34 -0400
Content-class: urn:content-classes:message
Subject: RE: This IETF discussion list
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Tue, 3 Jun 2003 20:04:17 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F857@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: This IETF discussion list
Thread-Index: AcMqQ6WpuggXZJhXS++YQWXmGS3NiwAAS2Yg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <william@elan.net>
Cc: "IETF Discussion" <ietf@ietf.org>, <harald@alvestrand.no>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA28833

William,

I don't think you got it: we have a troll problem on this list. The
traffic pattern has been standard, with trolls being the top posters as
usual and when it gets to the point where the IETF chair has to step in,
the decision about the appropriateness of removing trolls has been made
already and is supported by the community. If you don't like it, you can
either keep it to yourself, unsubscribe from the list, or support the
trolls with the consequences it will bring. Your call.

For the record (and we have not always agreed), Harald has my
unconditional support on this issue. As for the trolls, if they had read
the writing on the wall as posted by Eric, myself and other subscribers,
they would not be in the troll box.

Michel.


-----Original Message-----
From: william@elan.net [mailto:william@elan.net] 
Sent: Tuesday, June 03, 2003 4:58 PM
To: Michel Py
Cc: IETF Discussion
Subject: RE: This IETF discussion list

You can add me as well if you like, but I really think its your own
reply 
that was not fair. There is nothing from Richard's email that suggested 
he's "pro-spammer" or "pro-troll". It's all regarding quility of
discussions
on this list which have seriously deteriorated in the past week and his 
message about keeping your personal attacks out of the list and not 
judging somebody just based on what he/she believes is absolutly right.

On Tue, 3 Jun 2003, Michel Py wrote:

> Added to the pro-troll and pro-spammer list: Richard Perlman.
> 
> Michel.
> 
> 
> -----Original Message-----
> From: Richard Perlman [mailto:perl@lucent.com] 
> Sent: Tuesday, June 03, 2003 6:53 PM
> To: 'IETF Discussion'
> Cc: harald@alvestrand.no
> Subject: Re: This IETF discussion list
> 
> All:
> 
> I have been loosely tracking the SPAM discussion and really had
nothing
> significant to add.  However, a related posting did catch my attention
> and
> interest, enough so to warrant a response.
> 
> While I certainly am not interested in taking sides on the personal
> accusations that have been seen recently, I do have serious concerns
> about
> the message quoted below.  I personally detest the daily deluge of
> unwanted
> unsolicited e-mails I receive.  However, I would be even more upset to
> find
> that one's belief or support for or against any topic should be the
> criteria
> by which their contributions were judged.
> 
> As despicable as I may find the concepts, opinions and thoughts of
> others, a
> world in which the expression of only those ideas that I found
> acceptable
> would be far worse.
> 
> Having said that, I do want to be clear, that while I think there
needs
> to
> be freedom for expression of ideas, that expression must be done in a
> way
> that encourages discussion and values the participation of everyone.
> There
> is no room for personal remarks and attacks in a conversation of
ideas.
> 
> Richard
> 
> On 6/3/03 15:00, "Dean Anderson" <dean@av8.com> quoted:
> > ==================
> > Date: Fri, 30 May 2003 02:09:25 +0200
> > From: "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr>
> > To: 'Eric A. Hall' <ehall@ehsco.com>, 'John Stracke'
> > <jstracke@centive.com>
> > Cc: ietf@ietf.org
> > Subject: RE: spam
> > 
> > Guys,
> > 
> > Dean Anderson obviously supports and defends SPAM.
> > No further conversation with him could lead to anything
constructive.
> > Stop feeding the Troll, now.
> > 
> > E.T.
> 
> 







From owner-ietf@ietf.org  Wed Jun  4 12:04:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28832
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 12:04:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NaUy-00038W-Q5
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 11:48:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Na9L-00029i-Iv
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 11:26:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26262
	for <ietf@ietf.org>; Wed, 4 Jun 2003 11:26:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Na7Y-0004Ch-00
	for ietf@ietf.org; Wed, 04 Jun 2003 11:24:12 -0400
Received: from spitfire.law.miami.edu ([129.171.187.10] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Na7X-0004Ce-00
	for ietf@ietf.org; Wed, 04 Jun 2003 11:24:11 -0400
Received: from spitfire.law.miami.edu (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id 6F08A5C3AA2; Wed,  4 Jun 2003 11:26:01 -0400 (EDT)
Received: by spitfire.law.miami.edu (Postfix, from userid 1113)
	id 46EE35C3AA2; Wed,  4 Jun 2003 11:26:01 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id 3D1235D3AEE; Wed,  4 Jun 2003 11:26:01 -0400 (EDT)
Date: Wed, 4 Jun 2003 11:25:59 -0400 (EDT)
From: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
To: IETF Discussion <ietf@ietf.org>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>
Subject: RE: This IETF discussion list
In-Reply-To: <Pine.LNX.4.44.0306041003340.1028-100000@commander.av8.net>
Message-ID: <Pine.LNX.4.10.10306041124390.6503-100000@spitfire.law.miami.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

The growth of this sort of traffic, and traffic responding to it, is
sufficient reason to avoid having a censorship/poster-blocking process.

On Wed, 4 Jun 2003, Dean Anderson wrote:

> I ask the Chair to take the appropriate action.

-- 
		Please visit http://www.icannwatch.org
A. Michael Froomkin   |    Professor of Law    |   froomkin@law.tm
U. Miami School of Law, P.O. Box 248087, Coral Gables, FL 33124 USA
+1 (305) 284-4285  |  +1 (305) 284-6506 (fax)  |  http://www.law.tm
                        -->It's hot here.<--




From owner-ietf@ietf.org  Wed Jun  4 12:35:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00112
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 12:35:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NawJ-0006Id-9J
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 12:16:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NaZs-0004WZ-S4
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 11:53:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28136
	for <ietf@ietf.org>; Wed, 4 Jun 2003 11:53:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NaY5-0004l2-00
	for ietf@ietf.org; Wed, 04 Jun 2003 11:51:37 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NaY3-0004kn-00
	for ietf@ietf.org; Wed, 04 Jun 2003 11:51:36 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h54FrM417096;
	Wed, 4 Jun 2003 10:53:22 -0500
Message-ID: <00c501c32ab1$6d3e4000$afb58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <ietf@ietf.org>, "Dan Kolis" <dank@hq.lindsayelec.com>
References: <20030604143227752.AAA396@hq.lindsayelec.com@rflooker1>
Subject: Re: IMAP v. POP 
Date: Wed, 4 Jun 2003 10:49:34 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Dan Kolis" <dank@hq.lindsayelec.com>
> Lots of users don't like you have to be connected to IMAP to do
> routine things fulltime.
>
> If your paying by the minute for CDMA2000, (for instance), getting
> frozen out of doing anything when your not connected turns people off.

Perhaps those folks should use an implementation that can manipulate mail
offline and then sync with the server later.

S

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




From owner-ietf@ietf.org  Wed Jun  4 12:43:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00642
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 12:43:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nb53-0006dt-CR
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 12:25:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Nads-0004j1-GN
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 11:57:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28506
	for <ietf@ietf.org>; Wed, 4 Jun 2003 11:57:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nac5-0004sI-00
	for ietf@ietf.org; Wed, 04 Jun 2003 11:55:45 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nac4-0004rV-00
	for ietf@ietf.org; Wed, 04 Jun 2003 11:55:44 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id LAA12466;
	Wed, 4 Jun 2003 11:52:51 -0400
Date: Wed, 4 Jun 2003 11:54:03 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: IETF Standards Process
In-Reply-To: <75810000.1054705693@askvoll.hjemme.alvestrand.no>
Message-ID: <Pine.LNX.4.44.0306040920280.1028-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

inline. I apologize in advance for so many questions. I have looked on the
ISOC site, and IAB site, and other pages to find the answers to these
questions.

On Wed, 4 Jun 2003, Harald Tveit Alvestrand wrote:

>
>
> --On tirsdag, juni 03, 2003 17:28:55 -0400 Dean Anderson <dean@av8.com>
> wrote:
>
> >
> > You indicated that my criticism was incorrect regarding Mr. Klensin's
> > understanding of the standards process in regards to the description of
> > the current SMTP Standard.  So, now I am confused, and would like to learn
> > how to correctly evalute the status of IETF Standards.
> >
> > The following question seems simple enough:
> >
> > "What is the current standard level RFC describing the SMTP protocol?"
>
> formally, we have two standards-track specifications for the SMTP protocol.
>
> RFC 821 at Standard, and RFC 2821 at Proposed Standard.


4.2.4  Historic

   A specification that has been superseded by a more recent
   specification or is for any other reason considered to be obsolete is
   assigned to the "Historic" level.  (Purists have suggested that the
   word should be "Historical"; however, at this point the use of
   "Historic" is historical.)

   Note: Standards track specifications normally must not depend on
   other standards track specifications which are at a lower maturity
   level or on non standards track specifications other than referenced
   specifications from other standards bodies.  (See Section 7.)

Does RFC 2821 make up part of STD 10?  It seems confusing, since STD 10
depends on RFC 821 which has been obsoleted by RFC 2821. By inference it
seems that STD 10 includes RFC 2821.  Does this violate Section 4.2.4 of
RFC 2026?

Has RFC 821 been superceded by RFC 2821? If not, then how can RFC 821 be
obsolete?

It is confusing for RFC 821 can both be at "Standard" level and also
"Obsolete". Is the "Obsolete" notation on RFC 821 an error?

Further, RFC 2026 Section 4.1.1 recommends that "Proposed Standards"
should not be deployed into a "disruption-sensitive environment":


4.1.1  Proposed Standard

   The entry-level maturity for the standards track is "Proposed
   Standard".  A specific action by the IESG is required to move a
   specification onto the standards track at the "Proposed Standard"
   level.

   A Proposed Standard specification is generally stable, has resolved
   known design choices, is believed to be well-understood, has received
   significant community review, and appears to enjoy enough community
   interest to be considered valuable.  However, further experience
   might result in a change or even retraction of the specification
   before it advances.

   Usually, neither implementation nor operational experience is
   required for the designation of a specification as a Proposed
   Standard.  However, such experience is highly desirable, and will
   usually represent a strong argument in favor of a Proposed Standard
   designation.

   The IESG may require implementation and/or operational experience
   prior to granting Proposed Standard status to a specification that
   materially affects the core Internet protocols or that specifies
   behavior that may have significant operational impact on the
   Internet.

   A Proposed Standard should have no known technical omissions with
   respect to the requirements placed upon it.  However, the IESG may
   waive this requirement in order to allow a specification to advance
   to the Proposed Standard state when it is considered to be useful and
   necessary (and timely) even with known technical omissions.






Bradner                  Best Current Practice                 [Page 12]

RFC 2026               Internet Standards Process           October 1996


   Implementors should treat Proposed Standards as immature
   specifications.  It is desirable to implement them in order to gain
   experience and to validate, test, and clarify the specification.
   However, since the content of Proposed Standards may be changed if
   problems are found or better solutions are identified, deploying
   implementations of such standards into a disruption-sensitive
   environment is not recommended.

Our business customers with mission critical service requirements would be
concerned about using software which is not recommended for
"disruption-sensitive environments".  Does the IETF recommend ignoring its
own warnings?  If so, why have them?  Do you think that introducing
"Proposed Standard" implmentations into disruption-sensitive environments
despite the warnings regarding use of Proposed Standards violates section
4 and section 14 of the ISOC Code of Conduct?

> The intent is, I believe, that any RFC 2821 client will be RFC 821
> compatible, but implementors who care should state which specification they
> claim conformance to.

The criticisms documented by Dan Bernstein seem to suggest there are
considerable incompatibilites.

Implementors are not the only users of standards.  Businsess seek to
purchase and sell "Standard" Services, and may receive just and public
criticism for not providing the services they claim to provide. In some
jurisdictions, this could conceivably be considered fraud, and/or unfair
trade practices.  So if a business (SMTP client vendor, SMTP server
vendor, ISP, etc) claims to provide "Standard SMTP Service", and comply
with the "SMTP Standard", to which RFC should they be held accountable?

> The "delete after 24 months" clause of RFC 2026 is inoperative in practice;
> the oldest Proposed Standard is RFC 698, published in 1975.

If there is not agreement on the IESG (since 1975) to move an RFC to
"Draft Standard", nor to "Standard", then perhaps work on this proposed
standard should be terminated, and the proposed standard should be made
Historic, so that in the case of RFC 698, Telnet implementors are not
confused with irrelevant and inapplicable standards. Does this violate
section 4 and section 14 of the ISOC Code of Conduct?

Is the failure to carry out the procedures documented in RFC 2026 a
failure of either the IESG or the IAB?  Is this a failure of the ISOC to
facilitate the legal and organizational issues concerning its conduct as
described in RFC 2031?

> I have no explanation for the error in RFC 3300; the RFCs in question were
> published by the RFC Editor without IETF review.
> The first such document to refer to RFC 2821 was RFC 2800.

Should the text RFC 3300 be updated to eliminate this error?  Is it
possible that the maturity status of RFC's could be changed by error?


Thank you for your attention,

Dean Anderson
President, Av8 Internet, Inc





From owner-ietf@ietf.org  Wed Jun  4 12:44:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00686
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 12:44:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NbBY-0007XX-MB
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 12:32:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Natt-00069a-VQ
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 12:14:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29322
	for <ietf@ietf.org>; Wed, 4 Jun 2003 12:14:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nas6-00056O-00
	for ietf@ietf.org; Wed, 04 Jun 2003 12:12:18 -0400
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nas5-000566-00
	for ietf@ietf.org; Wed, 04 Jun 2003 12:12:17 -0400
Received: from bbprime (208.184.79.253.songbird.com [208.184.79.253] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h54GGTF02049;
	Wed, 4 Jun 2003 09:16:29 -0700
Date: Wed, 4 Jun 2003 09:13:31 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <151253898937.20030604091331@brandenburg.com>
To: Terry Gray <gray@cac.washington.edu>
CC: ietf@ietf.org
Subject: Re: IMAP v. POP (Was: The utilitiy of IP is at stake here)
In-Reply-To: <Pine.WNT.4.56.0305301608140.1436@TGX200>
References: <000a01c326d1$47cddd00$56144104@eagleswings>
 <Pine.WNT.4.56.0305301608140.1436@TGX200>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Terry,

TG> and I believe Dave's
TG> assessment is only true for residential ISPs, not enterprises.)

As I suspect Terry knows I know, the differences between pop and imap
are fundamental. I was making no comment on the utility of imap vs. pop.
This is about end-user adoption statistics.

i should have said 'enterprises' rather than LANs, since that was what i
was trying to highlight.  my understanding is that imap has had a large
impact on enterprise email access, though I've no idea what percentage
of the enterprise POP market it has displaced.

but 'residential ISP' is a rather large portion of the Internet and the
scale of the whole Internet is the focus of this discussion.


TG> People who only use one computer (and who back it up regularly :), may
TG> find relatively little benefit to IMAP

this is going to take us down a distracting path, but since you mention
it, i would have switched to IMAP long ago, for exactly the
multi-computer scenario you cite. but i have not come across an email
user agent with features I need that also has support for IMAP that
works acceptably.


TG> Therefore I claim that it is highly incorrect to suggest that IMAP
TG> hasn't displaced POP "because from the end user perspective IMAP
TG> doesn't provide any clear value over POP", or because it was "all
TG> about shifting control of the mail store from the end user into the
TG> hands of the mail administrator" --which I can assure you, it was not.

well, for many users, pop is just fine, of course.  they simply do not
need imap.

it is also true that residential ISPs tend not to see the business
benefit in storing user email.

but it is most clearly true that the two protocols provide massively
different capabilities and that each can be massively useful.

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




From owner-ietf@ietf.org  Wed Jun  4 12:58:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01354
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 12:58:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NbBZ-0007YM-80
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 12:32:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NavB-0006C2-5R
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 12:15:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29398
	for <ietf@ietf.org>; Wed, 4 Jun 2003 12:15:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NatN-00057z-00
	for ietf@ietf.org; Wed, 04 Jun 2003 12:13:37 -0400
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NatN-00057n-00
	for ietf@ietf.org; Wed, 04 Jun 2003 12:13:37 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id h54GFEM8008311;
	Wed, 4 Jun 2003 09:15:18 -0700 (MST)
Received: from thorgal.crm.mot.com (thorgal.crm.mot.com [140.101.173.1])
	by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id h54GF1qc004510;
	Wed, 4 Jun 2003 11:15:10 -0500
Received: from nal.motlabs.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id BC3FF2EC86; Wed,  4 Jun 2003 18:15:00 +0200 (CEST)
Message-ID: <3EDE1B04.6040501@nal.motlabs.com>
Date: Wed, 04 Jun 2003 18:15:00 +0200
From: Alexandru Petrescu <petrescu@nal.motlabs.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: Re: authenticated email
References: <3EDDD1B3.9080700@nal.motlabs.com> <200306041421.h54ELirR016007@calcite.rhyolite.com>
In-Reply-To: <200306041421.h54ELirR016007@calcite.rhyolite.com>
X-Enigmail-Version: 0.72.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Excuses, I jumped too quickly into this discussion, and only then I read
the other posts on this thread, that already express what's important;

Vernon Schryver wrote:
>> "legally" (as if I showed an ID).
> 
> "Legally"?--Talk about a disaster in the making

I quoted "legally".

> [...] require a passphrased for each use of the secret key?--probably
>  not.[...] trojan horses [...] that posts the secret key passphrase 
> "dialog box" and then capture keystrokes.[...] dictionary attack on 
> the passphrase [...] pop-up [...]

That is a lot of ways to compromise it.




From owner-ietf@ietf.org  Wed Jun  4 12:58:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01356
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 12:58:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NbKJ-00087n-4E
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 12:41:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Nb53-0006dr-6L
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 12:25:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29708
	for <ietf@ietf.org>; Wed, 4 Jun 2003 12:25:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nb3F-0005Cy-00
	for ietf@ietf.org; Wed, 04 Jun 2003 12:23:49 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nb3E-0005Cg-00
	for ietf@ietf.org; Wed, 04 Jun 2003 12:23:49 -0400
Content-class: urn:content-classes:message
Subject: RE: IMAP v. POP (Was: The utilitiy of IP is at stake here)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Wed, 4 Jun 2003 09:25:34 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F50671A7@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: IMAP v. POP (Was: The utilitiy of IP is at stake here)
Thread-Index: AcMqpP1G8I8jBOTGR3SE47CfhLsbYgABQZGA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Terry Gray" <gray@cac.washington.edu>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA01356

Terry,


> Terry Gray wrote:
> In contrast, I suspect that most enterprises use either
> Exchange/MAPI or an IMAP-based solution (and of course
> Exchange also supports IMAP).

This is not the picture that I see. I think that I would have made the
same assumption you did (why bother using POP3 when your server supports
IMAP) but that's not the way it works.

In Enterprise networks using GroupWise or Notes or Exchange, a good 80%
to 100% of the clients are using the client software that pairs with the
server software. So there is a GroupWise client, a Notes client and
there used to be an Exchange client but now everyone uses Outlook. This
is the setup that the helpdesk can support.
 
Although it might appear surprising, these other 10% or 20% of users
that don't use the native client that came with the server software (for
example, a Unix machine on an Exchange server, a Macintosh on a Notes
server, or a user loosely related to the Enterprise located in the
middle of nowhere) don't use IMAP but do use POP3, and I think it has to
do mostly with IT not wanting to support fancy configurations and yes
MAPI is fancy compared to POP3. The way IT typically sees these machines
is that they are a major support pain.

From a manageability/supportability standpoint, it is not a good idea to
configure an IMAP4 client to access an Exchange server when you can have
Outlook.

There are indeed some enterprises that have a Unix-based mail system
accessed by the crowd of Windows clients; however I think these are
massively over-representated in the IETF compared to the general
population.

Michel.





From owner-ietf@ietf.org  Wed Jun  4 13:28:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02550
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 13:28:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NbmX-0001f2-5Y
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 13:10:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NbKU-00088d-0w
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 12:41:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00520
	for <ietf@ietf.org>; Wed, 4 Jun 2003 12:41:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NbIg-0005Q1-00
	for ietf@ietf.org; Wed, 04 Jun 2003 12:39:46 -0400
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NbIg-0005Py-00
	for ietf@ietf.org; Wed, 04 Jun 2003 12:39:46 -0400
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com for <ietf@ietf.org>;
          Wed, 4 Jun 2003 12:41:34 -0400
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: IMAP v. POP 
Date: Wed, 4 Jun 2003 12:41:34 -0400
Message-ID: <20030604164134236.AAA178@hq.lindsayelec.com@rflooker1>
Sender: owner-ietf@ietf.org
Precedence: bulk


It was said about IMAP versus POP mail:
>Perhaps those folks should use an implementation that can manipulate mail
>offline and then sync with the server later.

Dan says:
The group I know have an information technology group which raid and
confiscate anything they don't install. They terrorize everyone in this huge
fortune 100 company, and if they don't run the approved software they delete
everything. They only allow IMAP (not POP), and its all connection oriented.
The idea is this is more secure. But ultimately, obviously, people can
screen capture and/or print anything, somehow. Then it can be reabsorbed in
digital form; (scan, etc).

I guess I realize, nearly by definition, you could make an offline/online
IMAP implementation.

I think POP is awefully functional though. If it just had passwords not in
the clear, and a better way to defer big attachments, I think it would be
nearly perfect protocol/service.

For home and casual use though POP is cool. You can only expect so much from
it. And with the extensions it can do a lot.

There must be a pure 'push' email protocol either in the works or done, is't
there?

Regs
Dan




From owner-ietf@ietf.org  Wed Jun  4 13:34:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02791
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 13:34:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nbnc-0001ky-FK
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 13:11:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NbOE-0000Sd-6X
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 12:45:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00843
	for <ietf@ietf.org>; Wed, 4 Jun 2003 12:45:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NbMP-0005Uf-00
	for ietf@ietf.org; Wed, 04 Jun 2003 12:43:37 -0400
Received: from bws10.bridgewatersystems.com ([216.113.7.10] helo=exch01.bridgewatersys.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NbMO-0005ST-00
	for ietf@ietf.org; Wed, 04 Jun 2003 12:43:36 -0400
Received: by exch01.bridgewatersys.com with Internet Mail Service (5.5.2653.19)
	id <LM4539MG>; Wed, 4 Jun 2003 12:44:52 -0400
Message-ID: <F17FB067A86B2D488382C923C532EAA746EEDC@exch01.bridgewatersys.com>
From: Avi Lior <avi@bridgewatersystems.com>
To: "'Marc Schneiders'" <marc@schneiders.org>,
        "'william@elan.net'"
	 <william@elan.net>
Cc: "'Rob Austein'" <sra+ietf@hactrn.net>, "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Last 7 days on the IETF list
Date: Wed, 4 Jun 2003 12:44:52 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Okay.  Can somebody please tell me what the relevance of this is to the
IETF.  This is absolute noise.  Take this thread off-line.  This list is
starting to annoy the heck out of me.  I am starting to get the same feeling
about this list and SPAM.  The list is starting to be unusable.

Moderator please do your job and moderate!!!

> -----Original Message-----
> From: Marc Schneiders [mailto:marc@schneiders.org] 
> Sent: Friday, May 30, 2003 9:15 PM
> To: william@elan.net
> Cc: Rob Austein; ietf@ietf.org
> Subject: Re: Last 7 days on the IETF list
> 
> 
> I am sure you are right, but in the list below the bytes and 
> number-of-messages rankings are more or less identical. Since 
> this is in the context of overload of the list by a limited 
> number of people, the number of bytes real contribution is 
> not relevant. People don't read it anymore. All what counts 
> is number of (slight) irritations while reading mail and 
> total bytes traffic (if we pay for it).
> 
> What you want to know, isn't ascertainable through some log 
> analyzing script. You have to read all the messages. And we 
> do not do that anymore.
> 
> On Fri, 30 May 2003, at 17:43 [=GMT-0700], william@elan.net wrote:
> 
> > I don't think posting message size is quite appropriate as part of 
> > your statistics and even more particularly as a criteria to 
> order the 
> > list. Unless I'm mistaken you're calculating bytes for 
> entire message 
> > but often
> > > 75% comes from another message being replied to and so you can't 
> > > really
> > judge amount of input the actual poster added to the 
> message. If you 
> > want message bytes statistics, you could try to see what 
> parts of that 
> > were not from previous message and only calculate size 
> based on that.
> >
> > On Fri, 30 May 2003, Rob Austein wrote:
> >
> > > Traffic statistics (as seen from my cave, your milage may 
> vary) for 
> > > the last seven days on the ietf@ietf.org mailing list.
> > >
> > > Conclusions, if any, are left as an exercise for the reader.
> > >
> > >
> > >   Messages   |     Bytes       | Who
> > > -------+-----+-------+---------+------------------------
> > >  11.4% |  53 | 13.9% |  233614 | dean@av8.com
> > >  12.2% |  57 | 10.1% |  170963 | anthony@atkielski.com
> > >   7.5% |  35 |  7.2% |  121074 | ehall@ehsco.com
> > >   3.0% |  14 |  4.8% |   80253 | pdeutsch@earthlink.net
> > >   3.9% |  18 |  3.6% |   60755 | valdis.kletnieks@vt.edu
> > >   3.4% |  16 |  3.5% |   58293 | alh-ietf@tndh.net
> > >   3.6% |  17 |  2.6% |   43278 | 
> michel@arneill-py.sacramento.ca.us
> > >   2.8% |  13 |  2.2% |   37288 | moore@cs.utk.edu
> > >   2.4% |  11 |  2.3% |   37930 | dwm@xpasc.com
> > >   2.1% |  10 |  2.2% |   37479 | vjs@calcite.rhyolite.com
> > >   2.1% |  10 |  2.2% |   36561 | iljitsch@muada.com
> > >   2.1% |  10 |  1.9% |   31676 | l.wood@eim.surrey.ac.uk
> > >   1.9% |   9 |  1.8% |   31053 | shogunx@sleekfreak.ath.cx
> > >   1.9% |   9 |  1.8% |   31016 | vixie@vix.com
> > >   1.9% |   9 |  1.7% |   27856 | dhc2@dcrocker.net
> > >   1.9% |   9 |  1.6% |   27349 | dja2003@hotpop.com
> > >   1.9% |   9 |  1.5% |   24511 | sbwoodside@yahoo.com
> > >   1.1% |   5 |  2.1% |   34761 | steflist@thor.nma.com
> > >   1.7% |   8 |  1.3% |   21321 | jnc@ginger.lcs.mit.edu
> > >   1.3% |   6 |  1.7% |   28495 | richard@shockey.us
> > >   1.3% |   6 |  1.2% |   19636 | tomson_eric@yahoo.fr
> > >   1.3% |   6 |  1.1% |   19259 | jstracke@centive.com
> > >   0.9% |   4 |  1.5% |   24586 | john-ietf@jck.com
> > >   1.1% |   5 |  1.0% |   16989 | mat@cisco.com
> > >   0.9% |   4 |  0.9% |   15992 | avi@bridgewatersystems.com
> > >   0.9% |   4 |  0.9% |   14418 | huitema@windows.microsoft.com
> > >   0.9% |   4 |  0.8% |   13896 | phoffman@imc.org
> > >   0.9% |   4 |  0.7% |   12281 | dee3@torque.pothole.com
> > >   0.9% |   4 |  0.7% |   11323 | ietf@soaring.demon.co.uk
> > >   0.9% |   4 |  0.7% |   11275 | tjc@ecs.soton.ac.uk
> > >   0.6% |   3 |  0.8% |   13511 | darkuncle@darkuncle.net
> > >   0.6% |   3 |  0.7% |   12302 | harald@alvestrand.no
> > >   0.4% |   2 |  0.9% |   14402 | dws@hunnysoft.com
> > >   0.4% |   2 |  0.8% |   14209 | mohta@necom830.hpcl.titech.ac.jp
> > >   0.6% |   3 |  0.6% |   10191 | wessorh@ar.com
> > >   0.6% |   3 |  0.6% |   10181 | rwelty@averillpark.net
> > >   0.6% |   3 |  0.5% |    9109 | lear@cisco.com
> > >   0.6% |   3 |  0.5% |    8328 | john.loughney@kolumbus.fi
> > >   0.6% |   3 |  0.5% |    7803 | 
> sommerfeld@orchard.arlington.ma.us
> > >   0.6% |   3 |  0.5% |    7584 | billc44@citynet.net
> > >   0.6% |   3 |  0.4% |    6866 | randy@psg.com
> > >   0.2% |   1 |  0.8% |   13680 | soohong.park@samsung.com
> > >   0.4% |   2 |  0.5% |    8935 | stephen@sprunk.org
> > >   0.4% |   2 |  0.5% |    7722 | tytso@mit.edu
> > >   0.4% |   2 |  0.5% |    7620 | rra@stanford.edu
> > >   0.4% |   2 |  0.4% |    6916 | jmorris@cdt.org
> > >   0.4% |   2 |  0.4% |    6630 | dank@hq.lindsayelec.com
> > >   0.4% |   2 |  0.4% |    6470 | dominic.pinto@ieee.org
> > >   0.4% |   2 |  0.4% |    6156 | zefram@fysh.org
> > >   0.2% |   1 |  0.6% |    9711 | awduche@awduche.com
> > >   0.4% |   2 |  0.3% |    5077 | bmanning@isi.edu
> > >   0.4% |   2 |  0.3% |    4924 | fritz_saad@hotmail.com
> > >   0.4% |   2 |  0.3% |    4618 | ekr@rtfm.com
> > >   0.4% |   2 |  0.3% |    4576 | cdel@firsthand.net
> > >   0.4% |   2 |  0.3% |    4438 | anewton@ecotroph.net
> > >   0.4% |   2 |  0.3% |    4335 | garmitage@swin.edu.au
> > >   0.2% |   1 |  0.5% |    7750 | alain.durand@sun.com
> > >   0.2% |   1 |  0.4% |    7195 | dws+001@hunnysoft.com
> > >   0.2% |   1 |  0.4% |    6953 | bob@wyman.us
> > >   0.2% |   1 |  0.4% |    6315 | ggm@apnic.net
> > >   0.2% |   1 |  0.4% |    6293 | et7563@sbc.com
> > >   0.2% |   1 |  0.4% |    6003 | atul.sabharwal@intel.com
> > >   0.2% |   1 |  0.3% |    5766 | hardie@qualcomm.com
> > >   0.2% |   1 |  0.3% |    5699 | dhc@dcrocker.net
> > >   0.2% |   1 |  0.3% |    5206 | cchaplin@sj.symbol.com
> > >   0.2% |   1 |  0.3% |    4923 | peterf@exchange.microsoft.com
> > >   0.2% |   1 |  0.3% |    4425 | page@mail.msen.com
> > >   0.2% |   1 |  0.3% |    4388 | braendt@hotmail.com
> > >   0.2% |   1 |  0.3% |    4306 | gk@ninebynine.org
> > >   0.2% |   1 |  0.2% |    4096 | jorge.contreras@haledorr.com
> > >   0.2% |   1 |  0.2% |    3465 | inanbe@xs4all.nl
> > >   0.2% |   1 |  0.2% |    3310 | hinden@iprg.nokia.com
> > >   0.2% |   1 |  0.2% |    3214 | smb@research.att.com
> > >   0.2% |   1 |  0.2% |    3194 | gray@washington.edu
> > >   0.2% |   1 |  0.2% |    3085 | ole@cisco.com
> > >   0.2% |   1 |  0.2% |    3077 | rod.walsh@nokia.com
> > >   0.2% |   1 |  0.2% |    2958 | msa@burp.tkv.asdf.org
> > >   0.2% |   1 |  0.2% |    2946 | vinton.g.cerf@mci.com
> > >   0.2% |   1 |  0.2% |    2782 | swb@employees.org
> > >   0.2% |   1 |  0.2% |    2761 | jtk@depaul.edu
> > >   0.2% |   1 |  0.2% |    2661 | bob.natale@appliedsnmp.com
> > >   0.2% |   1 |  0.2% |    2621 | spencer_dawkins@yahoo.com
> > >   0.2% |   1 |  0.1% |    2510 | glc@cisco.com
> > >   0.2% |   1 |  0.1% |    2416 | klensin@jck.com
> > >   0.2% |   1 |  0.1% |    2323 | braden@isi.edu
> > >   0.2% |   1 |  0.1% |    2303 | kent@bbn.com
> > >   0.2% |   1 |  0.1% |    2265 | andy.malis@vivacenetworks.com
> > >   0.2% |   1 |  0.1% |    2259 | jfbauer@comcast.net
> > >   0.2% |   1 |  0.1% |    2175 | benson.schliesser@savvis.net
> > >   0.2% |   1 |  0.1% |    1789 | noc@nso.org
> > > -------+-----+-------+---------+------------------------
> > > 100.0% | 466 |100.0% | 1684907 | Total
> > >
> >
> >
> 
> 
> 
> 



From owner-ietf@ietf.org  Wed Jun  4 14:05:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03951
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 14:05:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NcPR-0003L1-L6
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 13:50:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NcBP-0002vC-Ju
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 13:36:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02968
	for <ietf@ietf.org>; Wed, 4 Jun 2003 13:36:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nc9c-00062r-00
	for ietf@ietf.org; Wed, 04 Jun 2003 13:34:28 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nc9a-00062o-00
	for ietf@ietf.org; Wed, 04 Jun 2003 13:34:27 -0400
Received: from mou1wnexc02.verisign.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.9/) with ESMTP id h54HaF53027208
        for <ietf@ietf.org>; Wed, 4 Jun 2003 10:36:15 -0700 (PDT)
Received: by mou1wnexc02.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LYL80CL3>; Wed, 4 Jun 2003 10:36:15 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D21BE@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Authenticated Email
Date: Wed, 4 Jun 2003 10:36:13 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

In response to the various threads on authenticated email...


Yes, there is a value to authentication, even weak authentication. The vast
majority of spam uses a forged origin address, according to our measurements
and those of the FTC. By forged origin address I mean it was sent without
any form of authorization by the domain owner.

Call this what you like, but this is considered a serious problem by the
ISPs and they are planning to take action to stop it. In particular there is
no reason why hotmail should accept tens of millions of posts with forged
headers purporting to come from Yahoo and vice versa.

Authentication is not weak, it is merely one part of the access control
problem. You also require authorization. Everyone proposing AuthN schemes
knows that.


Of course email is a longstanding infrastructure and members of the ietf
tend to think that their use of the infrastructure is the one that matters.
Before you get too worked up however, consider the following facts:

1) End users hate spam
2) ISPs are going to change the protocols to fix it
3) The side effects of existing spam filters and blacklists are terrible

In case you don't believe 3, take a look at the history of faction fights
between the blacklists. Listing each other was popular sport for a while.
Organizations such as move.on have been blacklisted as a result of campaigns
by their opponents who would sign up for the list then report it as spam.

We see the same thing with checksum based schemes. One of the participants
in the ASRG list reports as spam all email sent by other members he has
attacked in the flame wars he keeps starting.


What we are talking about here is authentication as a means of bypassing
spam filters. Nobody is should simply reject email for not having an RMX or
any other authentication mechanism.

What will happen is that the spam filter will change the estimate
of spam probability in response to the presence of valid RMX, the
presence of invalid RMX and abscence of RMX.

So if an email purports to be from hotmail.com we might have the following
probabilities:

A) Comes from RMX IP address           5% probability spam
B) Does not come from RMX IP address  95% probability spam
C) RMX not available                  50% probability spam

In case A the probability is probably low enough to simply whitelist (note
this is assuming that the spam filtering is stateful in the extreeme and the
probability for bozo.com with RMX might be 50%, exactly the same for no
RMX).

Case B is not quite high enough to reject (5% false positive rate is
unacceptable). But the threshold for rejection on content inspection would
be much lower, we only need to be about 90% sure it is spam to reject at an
acceptably low false positive rate, for case C we would have to be 99.5%
sure it is not spam to reject with the same level of accuracy.


Of course you probably expect me to say something about digital certificates
and PKI as well. 

PGP is Pretty Good Privacy, the web of trust design becomes somewhat
unwieldy when you try to deal with authentication. It becomes tractable if
you change the model to a key centric PKI such as XKMS which is a standards
based evolution of the PGP Key server model. Once you get to that stage
however you have a PKI and the functional equivalent of CAs...

There are a couple of problems applying S/MIME/PGP and SSL cryptography to
address the spam problem. 

Message level enhancements such as S/MIME have been designed to work
end-to-end. They have significant impact on the mail transport and they
authenticate individual users rather than domains. This is good if you want
to authenticate end users, but that is more granularity and hence expense
than the spam problem requires.

SSL and STARTTLS allow encryption and authentication of the Internet hop of
the mail process. this is a partial solution but fails in cases such as mail
forwarding and in particular mailing lists. So some adjustment may well
prove necessary there, although that is a detail. 


The reason that digital certificates are going to be needed is that the mail
sender wants to have confidence that their messages are going to get
through. People can construct schemes with PGP if they like, and many
members of the IETF will have great fun using them, that is not a commercial
threat I am going to spend much time worrying about. Before Moore's law
another Moore gave his name to the Moore Bound, a lower bound on the
diameter of a graph. Strong trust in large graphs requires nodes of high
degree, in the PKIX world they are called CAs.

I don't see any problem with multiple CAs either. With SSL certificates some
people think that any certificate that is recognised by the browser is OK.
So there might be an advantage to going to a Bucket-shop CA whose
authentication procedure is no more than checking that your credit card
payment clears (yes they do exist).

With spam however the spam senders are going to start to try to acquire
credentials to send spam. So zero-authentication CAs are going to be the
first targets. Getting a certificate from a CA with strong authentication
procedures is going to be much more costly - particularly if there is
legislation and even more so if the credentials are considered disposable.

The comparison to think of is with business registration. There is little to
stop a crook registering one crooked business. However it is very hard to
register a hundred crooked businesses a day.


Another point to consider is that the identity certificate is only the start
of the process. Other credentials can be layered on top of a certificate.
For example a 'trusted sender' type credential might be layered over a
digital certificate, possibly comming from an entirely different source. So
you might have a CA saying 'I have authenticated Alice by process XYZ' and
an auditor saying 'I have determined Alice is an unmitigated spammer'.

		Phill



From owner-ietf@ietf.org  Wed Jun  4 14:10:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04170
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 14:10:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NcPS-0003Lu-2T
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 13:50:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NcFD-000338-Rl
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 13:40:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03041
	for <ietf@ietf.org>; Wed, 4 Jun 2003 13:40:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcDQ-00064D-00
	for ietf@ietf.org; Wed, 04 Jun 2003 13:38:24 -0400
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcDP-00064A-00
	for ietf@ietf.org; Wed, 04 Jun 2003 13:38:23 -0400
Received: from [66.92.109.27] (helo=think.thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:DES-CBC3-SHA:168)  (Exim 3.35 #1 (Debian))
	id 19NcER-0005Ks-00; Wed, 04 Jun 2003 13:39:27 -0400
Received: from tytso authenticated as tytso by think.thunk.org with local   (Exim 3.35 #1 (Debian))
	id 19NcEQ-00033v-00; Wed, 04 Jun 2003 13:39:26 -0400
Date: Wed, 4 Jun 2003 13:39:26 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: Jari Arkko <jari.arkko@piuha.net>
Cc: Michael Thomas <mat@cisco.com>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: authenticated email
Message-ID: <20030604173926.GB9774@think>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu> <016c01c32960$56b1adb0$46124104@eagleswings> <16092.51912.740900.110873@thomasm-u1.cisco.com> <70660000.1054674804@askvoll.hjemme.alvestrand.no> <16093.10524.494835.396218@thomasm-u1.cisco.com> <3EDD8B91.1030509@piuha.net> <20030604112004.GA10522@think> <3EDDDE31.9020804@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3EDDDE31.9020804@piuha.net>
User-Agent: Mutt/1.5.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Jun 04, 2003 at 02:55:29PM +0300, Jari Arkko wrote:
> I don't have a good suggestion on how to resolve this, however.
> Perhaps the lowest common denominator is still a big enough
> deterrent? Note that help from a network entity is not likely
> solve this problem. Think about it: the average users are
> not going to install their own network helpers. They are going
> to rely ISPs' servers. So, we'd see SMTP servers that do the
> number crunching on behalf of the ISP's customers. Enter a
> spammer who claims to have a small device...

The ISP will have its own constraints about CPU time available to it.
So the ISP will almost certainly want to charge for the service
calculating the hashcash; and since this would only be necessary when
first contacting someone initially, this should be acceptable to most
people.... unless you want to contact hundreds of thousands of people
for the first time from your PDA.  But I can't think of anyone besides
spammer who would want to do that, so that would seem to be an
acceptable outcome.

						- Ted




From owner-ietf@ietf.org  Wed Jun  4 14:17:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04551
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 14:17:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nchr-00044W-2o
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 14:09:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NcUl-0003QG-ET
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 13:56:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03512
	for <ietf@ietf.org>; Wed, 4 Jun 2003 13:56:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcSx-0006Be-00
	for ietf@ietf.org; Wed, 04 Jun 2003 13:54:27 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcSw-0006BV-00
	for ietf@ietf.org; Wed, 04 Jun 2003 13:54:26 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h54Hu7421950;
	Wed, 4 Jun 2003 12:56:07 -0500
Message-ID: <010001c32ac2$934bdb70$afb58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Michael Thomas" <mat@cisco.com>,
        "Harald Tveit Alvestrand" <harald@alvestrand.no>
Cc: <ietf@ietf.org>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu><016c01c32960$56b1adb0$46124104@eagleswings><16092.51912.740900.110873@thomasm-u1.cisco.com><70660000.1054674804@askvoll.hjemme.alvestrand.no> <16093.10524.494835.396218@thomasm-u1.cisco.com>
Subject: Re: authenticated email
Date: Wed, 4 Jun 2003 12:55:51 -0500
MIME-Version: 1.0
Content-Type: multipart/signed;
	protocol="application/x-pkcs7-signature";
	micalg=SHA1;
	boundary="----=_NextPart_000_00F7_01C32A98.A0882B60"
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
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_00F7_01C32A98.A0882B60
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Thus spake "Michael Thomas" <mat@cisco.com>
> It depends on what you mean by signing. Signing a message in and
> of itself ought not hurt anything modulo software bugs, etc. But the
> real question is what does the receiving program (MTA, MUA) do
> with that signature? At the very least it could verify the signature,
> but then what? If it doesn't verify do you drop it? (transitive trust
> comes into play, but most likely). Does it do anything beyond that?

Well, if you use a score-based anti-spam system, the lack of a signature
could "cost" a message a few points, but that's about it.

The root problem here is we're trying to define an authentication system
without also defining the authorization or accounting systems to use it.

> Let me ask something in return: do you think that
> just the act of signing mail -- with no trust
> roots implied -- could help?

It does, at least until spammers start signing their email too.

Does my signature on this message make you trust it more than, say, the ten
ads you got this morning for Viagra?  Why or why not?

S

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

------=_NextPart_000_00F7_01C32A98.A0882B60
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Disposition: attachment;
	filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIII7zCCAn4w
ggHnoAMCAQICAwkw/TANBgkqhkiG9w0BAQQFADCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl
c3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsT
FENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAw
MC44LjMwMB4XDTAzMDEzMTIyNDE0OFoXDTA0MDEzMTIyNDE0OFowRDEfMB0GA1UEAxMWVGhhd3Rl
IEZyZWVtYWlsIE1lbWJlcjEhMB8GCSqGSIb3DQEJARYSc3RlcGhlbkBzcHJ1bmsub3JnMIGfMA0G
CSqGSIb3DQEBAQUAA4GNADCBiQKBgQDktOMal8H6D6RAXRP32vwfjvMAfF10QyzC4OGRPITRaMbw
PX31FS0bssM1VhV3Pph0IXNZJL1rzcNgVDufXehrMdRcqPDLz96fEHTHcVG3tnT7c/7ZfrcHFm2z
g6sYz7Lao72hoLdz7plBDykgDHi7OL1i6UX5nvTb9Xokwsb/lwIDAQABoy8wLTAdBgNVHREEFjAU
gRJzdGVwaGVuQHNwcnVuay5vcmcwDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQQFAAOBgQAqWvXV
P+mxGJU8jg75OIRyUHbKcqlh4Fs/0Onqt/VyI8TKrczu2sN7Nbajuc8a7hLdta8X4bV7Hb5fzJ61
2CTjLccLrrUrR0HzZJfXGcPDtaO3YjeRRmrRH8GHu1j9NbjtH5V6aRDh7979D5hkYkWo7NkRorJ3
t5/cpk9ab5/44DCCAy0wggKWoAMCAQICAQAwDQYJKoZIhvcNAQEEBQAwgdExCzAJBgNVBAYTAlpB
MRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhh
d3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24x
JDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVy
c29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw05NjAxMDEwMDAwMDBaFw0yMDEyMzEyMzU5NTla
MIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRv
d24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNl
cnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzAp
BgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wgZ8wDQYJKoZIhvcNAQEB
BQADgY0AMIGJAoGBANRp19SwlGRbcelH2AxRtupykbCEXn0tDY97Et+FJXUodDpCLGMnn5V7S+9+
GYcdhuqj3bnOlmQawhRuRKx85o/oTQ9xH0A4pgCjh3j2+ZSGXq3qwF5269kUo11uenwMpUtVfwYZ
KX+emibVars4JAhqmMex2qOYkf152+VaxBy5AgMBAAGjEzARMA8GA1UdEwEB/wQFMAMBAf8wDQYJ
KoZIhvcNAQEEBQADgYEAx+ySfk749ZalZ2IqpPBNEWDQb41gWGGsJrtSNVwIzzD7qEqWih9iQiOM
Fw/0umScF6xHKd+dmF7SbGBxXKKs3Hnj524ARx+1DSjoAp3kmv0T9KbZfLH43F8jJgmRgHPQFBve
Q6mDJfLmnC8Vyv6mq4oHdYsM3VGEa+T40c53ooEwggM4MIICoaADAgECAhBmRXK3zHT1z2N2RYTQ
LpEBMA0GCSqGSIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBl
MRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQL
Ex9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u
YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5j
b20wHhcNMDAwODMwMDAwMDAwWhcNMDQwODI3MjM1OTU5WjCBkjELMAkGA1UEBhMCWkExFTATBgNV
BAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAb
BgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBS
U0EgMjAwMC44LjMwMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMzKmY8cJJUU+0m54J2eB
xdqIGYKXDuNEKYpjNSptcDz63K737nRvMLwzkH/5NHGgo22Y8cNPomXbDfpL8dbdYaX5hc1VmjUa
nZJ1qCeu2HL5ugL217CR3hzpq+AYA6h8Q0JQUYeDPPA5tJtUihOH/7ObnUlmAC0JieyUa+mhaQID
AQABo04wTDApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMS0yOTcwEgYDVR0T
AQH/BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQEEBQADgYEAMbFLR135AXHl9VNs
XXnWPZjAJhNigSKnEvgilegbSbcnewQ5uvzm8iTrkfq97A0qOPdQVahs9w2tTBu8A/S166JHn2yi
DFiNMUIJEWywGmnRKxKyQF1q+XnQ6i4l3Yrk/NsNH50C81rbyjz2ROomaYd/SJ7OpZ/nhNjJYmKt
BcYxggH+MIIB+gIBATCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTES
MBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRl
IFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMwAgMJMP0w
CQYFKw4DAhoFAKCBujAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0w
MzA2MDQxNzU1NTFaMCMGCSqGSIb3DQEJBDEWBBQd7OigAzijo6AH41gIXkgaV69WMTBbBgkqhkiG
9w0BCQ8xTjBMMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUr
DgMCBzANBggqhkiG9w0DAgIBKDAHBgUrDgMCHTANBgkqhkiG9w0BAQEFAASBgKEskCR6smPNOLZk
g8y1AD6OsfPayXbNvddeLp0el4Gxe5QoJv8AcXOL0jylT78KuZZ4Is5Hdku8MfVmERE8znz9Lm5M
WEImidUkcmkML5Q8jN7/iSZLXH/+rQKZ6hiCk6x2ckjGAb+kp74o/3tYf1LM0uYLz7NaSK+/VLkX
OJ9FAAAAAAAA

------=_NextPart_000_00F7_01C32A98.A0882B60--




From owner-ietf@ietf.org  Wed Jun  4 14:29:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05047
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 14:29:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nchr-00044c-El
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 14:09:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NcUm-0003QI-Lm
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 13:56:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03517
	for <ietf@ietf.org>; Wed, 4 Jun 2003 13:56:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcSz-0006Bj-00
	for ietf@ietf.org; Wed, 04 Jun 2003 13:54:29 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcSy-0006BZ-00
	for ietf@ietf.org; Wed, 04 Jun 2003 13:54:28 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h54Hu7421947;
	Wed, 4 Jun 2003 12:56:07 -0500
Message-ID: <00ff01c32ac2$93044b20$afb58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        "Michael Thomas" <mat@cisco.com>
Cc: <ietf@ietf.org>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu> <016c01c32960$56b1adb0$46124104@eagleswings> <16092.51912.740900.110873@thomasm-u1.cisco.com> <70660000.1054674804@askvoll.hjemme.alvestrand.no>
Subject: Re: authenticated email
Date: Wed, 4 Jun 2003 12:50:52 -0500
MIME-Version: 1.0
Content-Type: multipart/signed;
	protocol="application/x-pkcs7-signature";
	micalg=SHA1;
	boundary="----=_NextPart_000_00E9_01C32A97.EE316A30"
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
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_00E9_01C32A97.EE316A30
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Thus spake "Harald Tveit Alvestrand" <harald@alvestrand.no>
> I thought I'd try this....
>
> is there any particular disadvantage or centralization of power
> implied in me signing this message with my PGP key?
>
> If not, is there any particular reason that I shouldn't do this all the
> time?
>
> It's not a solution, but is there a downside?

Yes.  Automated responders, such as Majordomo, don't understand MIME at all,
and therefore all the nasty MIME markup confuses them.  The problem gets
even uglier when you send MIME to trouble ticket systems.

On top of this, you have a great divide between PGP and S/MIME, with many
clients supporting either one or the other.  For instance, my client sees
PGP-signed email as a blank message with the original body as a text
attachment -- PGP-only clients have similar problems with S/MIME.

If I didn't worry about such problems, I'd have my client automatically sign
all outgoing email.  Of course, I'm not sure whether I'd do it with PGP or
S/MIME...

S

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

------=_NextPart_000_00E9_01C32A97.EE316A30
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Disposition: attachment;
	filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIII7zCCAn4w
ggHnoAMCAQICAwkw/TANBgkqhkiG9w0BAQQFADCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl
c3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsT
FENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAw
MC44LjMwMB4XDTAzMDEzMTIyNDE0OFoXDTA0MDEzMTIyNDE0OFowRDEfMB0GA1UEAxMWVGhhd3Rl
IEZyZWVtYWlsIE1lbWJlcjEhMB8GCSqGSIb3DQEJARYSc3RlcGhlbkBzcHJ1bmsub3JnMIGfMA0G
CSqGSIb3DQEBAQUAA4GNADCBiQKBgQDktOMal8H6D6RAXRP32vwfjvMAfF10QyzC4OGRPITRaMbw
PX31FS0bssM1VhV3Pph0IXNZJL1rzcNgVDufXehrMdRcqPDLz96fEHTHcVG3tnT7c/7ZfrcHFm2z
g6sYz7Lao72hoLdz7plBDykgDHi7OL1i6UX5nvTb9Xokwsb/lwIDAQABoy8wLTAdBgNVHREEFjAU
gRJzdGVwaGVuQHNwcnVuay5vcmcwDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQQFAAOBgQAqWvXV
P+mxGJU8jg75OIRyUHbKcqlh4Fs/0Onqt/VyI8TKrczu2sN7Nbajuc8a7hLdta8X4bV7Hb5fzJ61
2CTjLccLrrUrR0HzZJfXGcPDtaO3YjeRRmrRH8GHu1j9NbjtH5V6aRDh7979D5hkYkWo7NkRorJ3
t5/cpk9ab5/44DCCAy0wggKWoAMCAQICAQAwDQYJKoZIhvcNAQEEBQAwgdExCzAJBgNVBAYTAlpB
MRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhh
d3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24x
JDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVy
c29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw05NjAxMDEwMDAwMDBaFw0yMDEyMzEyMzU5NTla
MIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRv
d24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNl
cnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzAp
BgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wgZ8wDQYJKoZIhvcNAQEB
BQADgY0AMIGJAoGBANRp19SwlGRbcelH2AxRtupykbCEXn0tDY97Et+FJXUodDpCLGMnn5V7S+9+
GYcdhuqj3bnOlmQawhRuRKx85o/oTQ9xH0A4pgCjh3j2+ZSGXq3qwF5269kUo11uenwMpUtVfwYZ
KX+emibVars4JAhqmMex2qOYkf152+VaxBy5AgMBAAGjEzARMA8GA1UdEwEB/wQFMAMBAf8wDQYJ
KoZIhvcNAQEEBQADgYEAx+ySfk749ZalZ2IqpPBNEWDQb41gWGGsJrtSNVwIzzD7qEqWih9iQiOM
Fw/0umScF6xHKd+dmF7SbGBxXKKs3Hnj524ARx+1DSjoAp3kmv0T9KbZfLH43F8jJgmRgHPQFBve
Q6mDJfLmnC8Vyv6mq4oHdYsM3VGEa+T40c53ooEwggM4MIICoaADAgECAhBmRXK3zHT1z2N2RYTQ
LpEBMA0GCSqGSIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBl
MRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQL
Ex9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u
YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5j
b20wHhcNMDAwODMwMDAwMDAwWhcNMDQwODI3MjM1OTU5WjCBkjELMAkGA1UEBhMCWkExFTATBgNV
BAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAb
BgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBS
U0EgMjAwMC44LjMwMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMzKmY8cJJUU+0m54J2eB
xdqIGYKXDuNEKYpjNSptcDz63K737nRvMLwzkH/5NHGgo22Y8cNPomXbDfpL8dbdYaX5hc1VmjUa
nZJ1qCeu2HL5ugL217CR3hzpq+AYA6h8Q0JQUYeDPPA5tJtUihOH/7ObnUlmAC0JieyUa+mhaQID
AQABo04wTDApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMS0yOTcwEgYDVR0T
AQH/BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQEEBQADgYEAMbFLR135AXHl9VNs
XXnWPZjAJhNigSKnEvgilegbSbcnewQ5uvzm8iTrkfq97A0qOPdQVahs9w2tTBu8A/S166JHn2yi
DFiNMUIJEWywGmnRKxKyQF1q+XnQ6i4l3Yrk/NsNH50C81rbyjz2ROomaYd/SJ7OpZ/nhNjJYmKt
BcYxggH+MIIB+gIBATCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTES
MBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRl
IFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMwAgMJMP0w
CQYFKw4DAhoFAKCBujAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0w
MzA2MDQxNzUwNTJaMCMGCSqGSIb3DQEJBDEWBBS6fyzm06rfMHHkRztwdLo4G9Qa+DBbBgkqhkiG
9w0BCQ8xTjBMMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUr
DgMCBzANBggqhkiG9w0DAgIBKDAHBgUrDgMCHTANBgkqhkiG9w0BAQEFAASBgEZ45VX7QmNRRn+r
go25jwXJTRNcgcwtN4JUM8lgAn0ueAjFnUOAUpheP6BRNXRh+uRVgWWQBjWGomSXzWtk+Ui3RMvc
B8iI5codDhWMzbz5P/vkqH+XCj4fadDwWyMuGEKXWgULthEgm9GMluRxFtFXoyl2t71SwWKfd+tT
qb/qAAAAAAAA

------=_NextPart_000_00E9_01C32A97.EE316A30--




From owner-ietf@ietf.org  Wed Jun  4 14:42:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05518
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 14:42:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nchr-00044n-MU
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 14:09:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NcVE-0003Qc-Ur
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 13:56:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03525
	for <ietf@ietf.org>; Wed, 4 Jun 2003 13:56:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcTR-0006Bw-00
	for ietf@ietf.org; Wed, 04 Jun 2003 13:54:57 -0400
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcTQ-0006Bt-00
	for ietf@ietf.org; Wed, 04 Jun 2003 13:54:56 -0400
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com for <ietf@ietf.org>;
          Wed, 4 Jun 2003 13:56:39 -0400
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: Stray question, (a little bit) (What's the best practice on this?)
Date: Wed, 4 Jun 2003 13:56:39 -0400
Message-ID: <20030604175639742.AAA299@hq.lindsayelec.com@rflooker1>
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

A little off the center of the road, but that's nothing new here.

As users tend to use HTTP email accounts; (for privacy, flirting, whatever)
in enterprises this makes it hard to snag viruses to some extent. 

If the preferred solution in some server farm of linux and NT's.... whatever
is snagging virus attachments at SNMP and/or POP3 interfaces, this is great
and can work really well.

But on the HTTP side (even worse? https), all sorts of GETs and PUTs can
move items to and from on 80. To Java apps... whatever. Like attachments
carried by hotmail and Yahoo, etc.

Trying to tackle people in the hall and tell them what to do or not do just
doesn't work, for one thing. You can't or don't want to generally encoumber
abstract use of http and/or port 80. And, programs scanning the file system
are very robust / reliable for a host of reasons.

Any option on that? In tribute to the main purpose of this list: This is a
problem which might have a protocol solution of sorts. I'm not use I like
it, but seemingly the trasports could maim attachments by altering there
MIME type. Bad way to solve a problem is to make somebody elses
program/process crash though!

Regs to all,
Dan


 




From owner-ietf@ietf.org  Wed Jun  4 14:43:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05673
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 14:43:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nchs-00045F-0K
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 14:09:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NcVb-0003Qi-QH
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 13:57:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03568
	for <ietf@ietf.org>; Wed, 4 Jun 2003 13:57:09 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcTo-0006CH-00
	for ietf@ietf.org; Wed, 04 Jun 2003 13:55:20 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcTn-0006CE-00
	for ietf@ietf.org; Wed, 04 Jun 2003 13:55:19 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h54Hv0IS003822;
	Wed, 4 Jun 2003 13:57:00 -0400
Message-Id: <200306041757.h54Hv0IS003822@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Dean Anderson <dean@av8.com>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: IETF Standards Process 
In-Reply-To: Your message of "Wed, 04 Jun 2003 11:54:03 EDT."
             <Pine.LNX.4.44.0306040920280.1028-100000@commander.av8.net> 
References: <Pine.LNX.4.44.0306040920280.1028-100000@commander.av8.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_227377808P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 04 Jun 2003 13:57:00 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Wed, 04 Jun 2003 11:54:03 EDT, Dean Anderson said:

> Implementors are not the only users of standards.  Businsess seek to
> purchase and sell "Standard" Services, and may receive just and public
> criticism for not providing the services they claim to provide. In some
> jurisdictions, this could conceivably be considered fraud, and/or unfair
> trade practices.  So if a business (SMTP client vendor, SMTP server
> vendor, ISP, etc) claims to provide "Standard SMTP Service", and comply
> with the "SMTP Standard", to which RFC should they be held accountable?

Given that the Cisco PIX claimed to have an SMTP implementation from the
very beginning, and they still sold lots of them, I don't think there's much
chance of leveraging a lawsuit over the distinction between 821 and 2821.

(For those not familiar with the early PIX software, the best that can be
said about it is "near-universal derision".  Cisco has, to its credit, fixed
all of the glaring bogosities that I'm aware of, so the current release of
software *is* at least a "plays well with others" SMTP).

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

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

iD8DBQE+3jLscC3lWbTT17ARAuD2AJ9nSvs5TyRNi0Omv7XR5aiMWJZdAQCgnkEd
82XSikw3CFjvR7s3udCjvkY=
=76aY
-----END PGP SIGNATURE-----

--==_Exmh_227377808P--



From owner-ietf@ietf.org  Wed Jun  4 14:46:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05941
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 14:46:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NdEF-00067O-Fm
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 14:43:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Nd8Q-0005Vv-Ce
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 14:37:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05426
	for <ietf@ietf.org>; Wed, 4 Jun 2003 14:37:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nd6c-0006cV-00
	for ietf@ietf.org; Wed, 04 Jun 2003 14:35:26 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nd6c-0006cG-00
	for ietf@ietf.org; Wed, 04 Jun 2003 14:35:26 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h54IafOq012822;
	Wed, 4 Jun 2003 11:36:42 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AET59911;
	Wed, 4 Jun 2003 11:36:40 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA02611; Wed, 4 Jun 2003 11:36:40 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16094.15416.404447.690684@thomasm-u1.cisco.com>
Date: Wed, 4 Jun 2003 11:36:40 -0700 (PDT)
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: "Michael Thomas" <mat@cisco.com>,
        "Harald Tveit Alvestrand" <harald@alvestrand.no>, <ietf@ietf.org>
Subject: Re: authenticated email
In-Reply-To: <010001c32ac2$934bdb70$afb58742@ssprunk>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
	<016c01c32960$56b1adb0$46124104@eagleswings>
	<16092.51912.740900.110873@thomasm-u1.cisco.com>
	<70660000.1054674804@askvoll.hjemme.alvestrand.no>
	<16093.10524.494835.396218@thomasm-u1.cisco.com>
	<010001c32ac2$934bdb70$afb58742@ssprunk>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Stephen Sprunk writes:
 > Thus spake "Michael Thomas" <mat@cisco.com>
 > > It depends on what you mean by signing. Signing a message in and
 > > of itself ought not hurt anything modulo software bugs, etc. But the
 > > real question is what does the receiving program (MTA, MUA) do
 > > with that signature? At the very least it could verify the signature,
 > > but then what? If it doesn't verify do you drop it? (transitive trust
 > > comes into play, but most likely). Does it do anything beyond that?
 > 
 > Well, if you use a score-based anti-spam system, the lack of a signature
 > could "cost" a message a few points, but that's  about it.

Or signed, uncost it.
 
 > The root problem here is we're trying to define an authentication system
 > without also defining the authorization or accounting systems to use it.

One could obviously start envisioning servers with
known spammer keys, etc. Some have mentioned
whitelists but blacklists seem also possible so
far as they'd go. This isn't actually much
different than current practices, afterall.

I'd love to have somebody refute my personal and
completely unobjective observation that most
spammers (like virii hackers) are not very smart.
It's quite obvious that djinning up new key pairs
would be pretty simple (if relatively CPU
intensive), but look at the lag time between where
the current crop of filters are and the spam
that's sophiciticated enough to get around it. My
filters seem to catch -- even now -- about 80% at
least, and I haven't even upgraded spamassasin to
the Baysian version. Could the interval between
prevalence of signatures and spammers getting wise
to both needing to sign and needing to djinn up
lots of keys buy enough time to keep one step
ahead? My feeling is that it might. And I'd think
there would be huge economic incentives to move to
the next step before or as that starts to happen.

 > > Let me ask something in return: do you think that
 > > just the act of signing mail -- with no trust
 > > roots implied -- could help?
 > 
 > It does, at least until spammers start signing their email too.
 > 
 > Does my signature on this message make you trust it more than, say, the ten
 > ads you got this morning for Viagra?  Why or why not?

Well, that's the implicit question. If the vast
majority of mail were signed -- with or without
trust roots -- would we be better off than the
current state of affairs? That is, could something
that hasn't been invented or utilized today be
possible if mail were simply signed? There's an
obvious bootstrap problem with all of this, and if
there were some marginal value of to what an MTA
or MUA could do *without* any messy trust issues
mandatory, then maybe the network effect might
allow more and more sophisticated schemes to
emerge.

		Mike



From owner-ietf@ietf.org  Wed Jun  4 15:22:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08743
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 15:22:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NdUE-0007As-9u
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 14:59:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NdEH-00067S-JN
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 14:43:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05659
	for <ietf@ietf.org>; Wed, 4 Jun 2003 14:43:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NdCU-0006gV-00
	for ietf@ietf.org; Wed, 04 Jun 2003 14:41:30 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NdCT-0006fI-00
	for ietf@ietf.org; Wed, 04 Jun 2003 14:41:29 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h54Igawc016732;
	Wed, 4 Jun 2003 11:42:37 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AET60644;
	Wed, 4 Jun 2003 11:42:36 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA02638; Wed, 4 Jun 2003 11:42:36 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16094.15771.928300.482312@thomasm-u1.cisco.com>
Date: Wed, 4 Jun 2003 11:42:35 -0700 (PDT)
To: Uri Blumenthal <uri@bell-labs.com>
Cc: Michael Thomas <mat@cisco.com>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: authenticated email
In-Reply-To: <3EDE3A34.8010407@bell-labs.com>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
	<016c01c32960$56b1adb0$46124104@eagleswings>
	<16092.51912.740900.110873@thomasm-u1.cisco.com>
	<70660000.1054674804@askvoll.hjemme.alvestrand.no>
	<16093.10524.494835.396218@thomasm-u1.cisco.com>
	<3EDE3A34.8010407@bell-labs.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Uri Blumenthal writes:
 > > Let me ask something in return: do you think that
 > > just the act of signing mail -- with no trust
 > > roots implied -- could help? My sense is that it
 > > might in a sow-the-seeds kind of way for some
 > > later goodness (it's as you say not a solution).
 > > I too would be happy to hear downsides.
 > 
 > It might be good - but I think it will be ineffective in
 > spam-war.

Well, "effective" is a relative term. I guess I
don't see this as having any ultimate solution;
it's an arms race. The question is whether doing
so would give enough marginal value in and of
itself (which might even be neutral value, but it
would be better if it were at least slightly
positive) to get us to the next step where we can
possibly apply third party vouching, authorization
etc to the mix.

Thus, my question -- and I think Harald's as well
-- is mostly a *tactical* one, not a technical
one. IMO, it's the tactics which will allow or
inhibit forward progress.

		Mike



From owner-ietf@ietf.org  Wed Jun  4 15:33:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09185
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 15:33:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NdZa-0003PA-Sq
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 15:05:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NdIP-0006uL-WA
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 14:47:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06013
	for <ietf@ietf.org>; Wed, 4 Jun 2003 14:47:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NdGc-0006lv-00
	for ietf@ietf.org; Wed, 04 Jun 2003 14:45:46 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NdGb-0006kb-00
	for ietf@ietf.org; Wed, 04 Jun 2003 14:45:45 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id OAA30750;
	Wed, 4 Jun 2003 14:41:53 -0400
Date: Wed, 4 Jun 2003 14:43:05 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Valdis.Kletnieks@vt.edu
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>
Subject: Re: IETF Standards Process 
In-Reply-To: <200306041757.h54Hv0IS003822@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0306041435350.1912-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

You made my point. Cisco was "justly and publicly" criticized with
"near-universal-derision" for not complying with the standard.  Most
companies want to avoid that.  False derision is actionable in many
jurisdictions.

		--Dean

On Wed, 4 Jun 2003 Valdis.Kletnieks@vt.edu wrote:

> On Wed, 04 Jun 2003 11:54:03 EDT, Dean Anderson said:
>
> > Implementors are not the only users of standards.  Businsess seek to
> > purchase and sell "Standard" Services, and may receive just and public
> > criticism for not providing the services they claim to provide. In some
> > jurisdictions, this could conceivably be considered fraud, and/or unfair
> > trade practices.  So if a business (SMTP client vendor, SMTP server
> > vendor, ISP, etc) claims to provide "Standard SMTP Service", and comply
> > with the "SMTP Standard", to which RFC should they be held accountable?
>
> Given that the Cisco PIX claimed to have an SMTP implementation from the
> very beginning, and they still sold lots of them, I don't think there's much
> chance of leveraging a lawsuit over the distinction between 821 and 2821.
>
> (For those not familiar with the early PIX software, the best that can be
> said about it is "near-universal derision".  Cisco has, to its credit, fixed
> all of the glaring bogosities that I'm aware of, so the current release of
> software *is* at least a "plays well with others" SMTP).
>




From owner-ietf@ietf.org  Wed Jun  4 15:36:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09490
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 15:36:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NdaJ-0003dS-2D
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 15:06:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NdNu-00070K-HU
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 14:53:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06388
	for <ietf@ietf.org>; Wed, 4 Jun 2003 14:53:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NdM6-0006sa-00
	for ietf@ietf.org; Wed, 04 Jun 2003 14:51:26 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NdM6-0006sF-00
	for ietf@ietf.org; Wed, 04 Jun 2003 14:51:26 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h54Iqgjc011304;
	Wed, 4 Jun 2003 11:52:42 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AET61937;
	Wed, 4 Jun 2003 11:52:41 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA02667; Wed, 4 Jun 2003 11:52:40 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16094.16376.290573.444139@thomasm-u1.cisco.com>
Date: Wed, 4 Jun 2003 11:52:40 -0700 (PDT)
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        "Michael Thomas" <mat@cisco.com>, <ietf@ietf.org>
Subject: Re: authenticated email
In-Reply-To: <00ff01c32ac2$93044b20$afb58742@ssprunk>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
	<016c01c32960$56b1adb0$46124104@eagleswings>
	<16092.51912.740900.110873@thomasm-u1.cisco.com>
	<70660000.1054674804@askvoll.hjemme.alvestrand.no>
	<00ff01c32ac2$93044b20$afb58742@ssprunk>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Stephen Sprunk writes:
 > Thus spake "Harald Tveit Alvestrand" <harald@alvestrand.no>
 > > I thought I'd try this....
 > >
 > > is there any particular disadvantage or centralization of power
 > > implied in me signing this message with my PGP key?
 > >
 > > If not, is there any particular reason that I shouldn't do this all the
 > > time?
 > >
 > > It's not a solution, but is there a downside?
 > 
 > Yes.  Automated responders, such as Majordomo, don't understand MIME at all,
 > and therefore all the nasty MIME markup confuses them.  The problem gets
 > even uglier when you send MIME to trouble ticket systems.

Note that the type of signature needed here is
more of a _transport_ signature, not necessarily a
body signature. Thus it need not a priori be MIME
encoded. 

	Mike, though I've never noticed Majordomo
	 barfing on MIME



From owner-ietf@ietf.org  Wed Jun  4 15:38:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09677
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 15:38:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NddU-0006lN-Q2
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 15:09:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NdRh-00075v-C2
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 14:57:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06576
	for <ietf@ietf.org>; Wed, 4 Jun 2003 14:57:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NdPt-0006vz-00
	for ietf@ietf.org; Wed, 04 Jun 2003 14:55:21 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NdPs-0006vw-00
	for ietf@ietf.org; Wed, 04 Jun 2003 14:55:21 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19NdRe-0005tZ-00; Wed, 04 Jun 2003 13:57:10 -0500
Date: Wed, 04 Jun 2003 14:57:10 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dan Kolis <dank@hq.lindsayelec.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Stray question, (a little bit) (What's the best
 practice on this?)
Message-ID: <121291107.1054738630@p3.JCK.COM>
In-Reply-To: <20030604175639742.AAA299@hq.lindsayelec.com@rflooker1>
References:  <20030604175639742.AAA299@hq.lindsayelec.com@rflooker
 1>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dan,

A partial solution to _part_ of this problem lies in the 
receiving MUA. To oversimplify quite a bit, there are three 
things a receiving MUA can do with an HTTP body part:

	* Discard it because it _might_ be dangerous.   This is,
	obviously, not a good general solution, but might well
	be rational if the mail were suspect for other reasons.
	
	* Hand the attachment off to a general-purpose browser,
	which would be likely to be configured to process almost
	anything.
	
	* Have a browser available that was, by implementation
	or configuration, able to process HTML mail without
	executing code or following links without explicit user
	involvement and information.

The second seems to be the norm.  The third can avoid a _lot_ of 
trouble.

This doesn't, of course, address the risks of sending malware 
out, but recipients need to defend themselves regardless.

    john


--On Wednesday, 04 June, 2003 13:56 -0400 Dan Kolis 
<dank@hq.lindsayelec.com> wrote:

> Hi,
>
> A little off the center of the road, but that's nothing new
> here.
>
> As users tend to use HTTP email accounts; (for privacy,
> flirting, whatever) in enterprises this makes it hard to snag
> viruses to some extent.
>
> If the preferred solution in some server farm of linux and
> NT's.... whatever is snagging virus attachments at SNMP and/or
> POP3 interfaces, this is great and can work really well.
>
> But on the HTTP side (even worse? https), all sorts of GETs
> and PUTs can move items to and from on 80. To Java apps...
> whatever. Like attachments carried by hotmail and Yahoo, etc.
>
> Trying to tackle people in the hall and tell them what to do
> or not do just doesn't work, for one thing. You can't or don't
> want to generally encoumber abstract use of http and/or port
> 80. And, programs scanning the file system are very robust /
> reliable for a host of reasons.
>
> Any option on that? In tribute to the main purpose of this
> list: This is a problem which might have a protocol solution
> of sorts. I'm not use I like it, but seemingly the trasports
> could maim attachments by altering there MIME type. Bad way to
> solve a problem is to make somebody elses program/process
> crash though!
>
> Regs to all,
> Dan
>
>
>
>
>







From owner-ietf@ietf.org  Wed Jun  4 16:24:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11081
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 16:24:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NeSD-0003EZ-0G
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 16:01:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ne21-0001ux-Rh
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 15:34:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09340
	for <ietf@ietf.org>; Wed, 4 Jun 2003 15:34:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ne0E-0007M4-00
	for ietf@ietf.org; Wed, 04 Jun 2003 15:32:54 -0400
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ne0D-0007M1-00
	for ietf@ietf.org; Wed, 04 Jun 2003 15:32:53 -0400
Received: from h-68-164-72-19.snvacaid.covad.net ([68.164.72.19] helo=oemcomputer)
	by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19Ne1z-00033h-00
	for ietf@ietf.org; Wed, 04 Jun 2003 12:34:43 -0700
Message-ID: <00eb01c32acf$62dc2fa0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <963621801C6D3E4A9CF454A1972AE8F504F857@server2000.arneill-py.sacramento.ca.us>
Subject: Re: This IETF discussion list
Date: Wed, 4 Jun 2003 12:27:19 -0700
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
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi -

> From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
> To: <william@elan.net>
> Cc: "IETF Discussion" <ietf@ietf.org>; <harald@alvestrand.no>
> Sent: Tuesday, June 03, 2003 8:04 PM
> Subject: RE: This IETF discussion list
...
> already and is supported by the community. If you don't like it, you can
> either keep it to yourself, unsubscribe from the list, or support the
> trolls with the consequences it will bring. Your call.
...

I think that threats like this are inimical to the open discourse on which
the standards community depends. Having experienced first hand the
"collateral damage" of over-zealous anti-spam measures, I'd hate to
see analogous problems arise in our discussion of how to address
the spam problem.

Randy





From owner-ietf@ietf.org  Wed Jun  4 17:05:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12424
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 17:05:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NfLj-0005QG-QJ
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 16:59:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Nf5s-00055a-96
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 16:42:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11597
	for <ietf@ietf.org>; Wed, 4 Jun 2003 16:42:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nf43-0000AG-00
	for ietf@ietf.org; Wed, 04 Jun 2003 16:40:56 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nf42-00009y-00
	for ietf@ietf.org; Wed, 04 Jun 2003 16:40:55 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h54Kgd1O014574
	for <ietf@ietf.org>; Wed, 4 Jun 2003 22:42:39 +0200 (CEST)
Message-ID: <013001c32ad9$d6d59fe0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu> <016c01c32960$56b1adb0$46124104@eagleswings> <16092.51912.740900.110873@thomasm-u1.cisco.com> <70660000.1054674804@askvoll.hjemme.alvestrand.no> <3EDDD1B3.9080700@nal.motlabs.com> <133600000.1054725926@askvoll.hjemme.alvestrand.no> <3EDDE332.7060402@nal.motlabs.com>
Subject: Re: authenticated email
Date: Wed, 4 Jun 2003 22:42:39 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Alexandru writes:

> Can't I just create a public key with the Harald's
> name and email address and then post to this list
> claiming I'm Harald?

Sure, but that wouldn't do much good, because of the way PGP's key
infrastructure works.

See, with PGP, you NEVER trust a key just because it claims to belong to a
specific entity.  You trust a key ONLY when the entity to whom that key
belongs communicates the key to you directly and securely (as by handing you
a diskette in person).  Thereafter, you can use that key, which you can now
trust to be valid, as a source of validation for other keys, in that you can
choose to trust any other key that is signed by the one key that you already
trust (the degree to which you do this is up to you, and depends mainly on
how much you trust the owner of the first key as a reliable "introducer" of
other entities and their keys).

Thus, you'd never trust a key just because it was on a public server, but
you might trust it if it were signed by someone whose key you already trust,
and you might trust it if you received the key directly from its owner.

PGP's great advantage is that it does not impose any specific trust model,
nor does it require that everyone trust a single certification authority.
This is a huge benefit compared to many other public-key infrastructures.





From owner-ietf@ietf.org  Wed Jun  4 17:07:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12666
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 17:07:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NfLq-0005Vd-8r
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 16:59:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Nf9q-0005AH-0n
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 16:46:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11788
	for <ietf@ietf.org>; Wed, 4 Jun 2003 16:46:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nf82-0000CP-00
	for ietf@ietf.org; Wed, 04 Jun 2003 16:45:02 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nf81-0000CM-00
	for ietf@ietf.org; Wed, 04 Jun 2003 16:45:01 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h54Kkp1O014608
	for <ietf@ietf.org>; Wed, 4 Jun 2003 22:46:51 +0200 (CEST)
Message-ID: <013701c32ada$6d0ef600$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu> <016c01c32960$56b1adb0$46124104@eagleswings> <16092.51912.740900.110873@thomasm-u1.cisco.com> <70660000.1054674804@askvoll.hjemme.alvestrand.no> <3EDDD1B3.9080700@nal.motlabs.com> <133600000.1054725926@askvoll.hjemme.alvestrand.no> <3EDDE332.7060402@nal.motlabs.com> <151700000.1054730073@askvoll.hjemme.alvestrand.no> <3EDDECB1.6060601@nal.motlabs.com>
Subject: Re: authenticated email
Date: Wed, 4 Jun 2003 22:46:51 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Alexandru asks:

> So the level of trust depends on the number of signatures?

No, it depends on who signed the key.  If you trust the people who signed
the key, then by extension, you can trust the key (because presumably
trustworthy individuals would not sign a key if they were not certain that
the key was truly what it claimed to be).

Similarly, you should never sign a key unless you've received it directly
from the owner.  Signing a key that you happened to find somewhere is very
bad practice, because signing a key implies that you are CERTAIN that the
key belongs to whomever it claims to belong to.

> Can I also ask other lots of people to sign the
> key I create and then pretend I'm Harald?

Sure, but trustworthy individuals aren't going to sign your key unless they
are certain that you really are who you claim to be.  Untrustworthy
individuals might sign your key in any case, but nobody is likely to trust
those individuals as "introducers" of your key.

> Otherwise, if certain of people who signed your
> key are "special", or are highly trusted, can I
> ask who are those people?

They are identified by their signatures.  Whether or not they are trusted is
up to you.

Ultimately, you have to start with a key that you receive directly at some
point.  This gives you a key that you can rely upon for signatures of other
keys.  The best policy is to reliably obtain the keys of several people whom
you'd trust as introducers for other keys, and then go from there.





From owner-ietf@ietf.org  Wed Jun  4 17:27:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13265
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 17:27:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NfLq-0005Vq-HR
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 16:59:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NfEU-0005JA-0L
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 16:51:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11891
	for <ietf@ietf.org>; Wed, 4 Jun 2003 16:51:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NfCg-0000EV-00
	for ietf@ietf.org; Wed, 04 Jun 2003 16:49:50 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NfCf-0000EQ-00
	for ietf@ietf.org; Wed, 04 Jun 2003 16:49:49 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h54Kpd1O014642
	for <ietf@ietf.org>; Wed, 4 Jun 2003 22:51:39 +0200 (CEST)
Message-ID: <014a01c32adb$18aab170$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000a01c326d1$47cddd00$56144104@eagleswings> <Pine.WNT.4.56.0305301608140.1436@TGX200>
Subject: Re: IMAP v. POP (Was: The utilitiy of IP is at stake here)
Date: Wed, 4 Jun 2003 22:51:39 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Terry writes:

> In contrast, I suspect that most enterprises use either
> Exchange/MAPI or an IMAP-based solution ...

Both solutions are extremely well suited to intracompany or
intraorganizational e-mail systems in relatively homogenous user
environments.  I'd always recommend Microsoft Exchange Server for such
applications over simple SMTP/POP3 solutions, if the bandwidth is not too
restricted.

However, for large, heterogenous, variable-bandwidth networks like the big,
wide Internet, SMTP/POP3 are far superior.  The more variables there are,
the simpler a system needs to be in order to have any chance of working
reliably for a large part of the user community.  SMTP/POP3 satisfy this
criterion; IMAP generally does not, and Exchange is an exercise in absurdity
in this context.





From owner-ietf@ietf.org  Wed Jun  4 17:44:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13881
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 17:44:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NfnT-0006vr-U3
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 17:27:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NfPP-0005Wm-B5
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 17:02:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12357
	for <ietf@ietf.org>; Wed, 4 Jun 2003 17:02:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NfNb-0000Lj-00
	for ietf@ietf.org; Wed, 04 Jun 2003 17:01:07 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NfNa-0000Lg-00
	for ietf@ietf.org; Wed, 04 Jun 2003 17:01:06 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h54L2s1O014746
	for <ietf@ietf.org>; Wed, 4 Jun 2003 23:02:54 +0200 (CEST)
Message-ID: <018c01c32adc$aaf17b30$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <963621801C6D3E4A9CF454A1972AE8F50671A7@server2000.arneill-py.sacramento.ca.us>
Subject: Re: IMAP v. POP (Was: The utilitiy of IP is at stake here)
Date: Wed, 4 Jun 2003 23:02:54 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Michel writes:

> In Enterprise networks using GroupWise or Notes
> or Exchange, a good 80% to 100% of the clients are
> using the client software that pairs with the
> server software. So there is a GroupWise client,
> a Notes client and there used to be an Exchange
> client but now everyone uses Outlook.

True.  This is why these fancy mail systems work so well in enterprise
environments.  It's a lot more homogenous and controlled than the wide-open
Internet.

> This is the setup that the helpdesk can support.

Yes.  Some of these client programs are able to access "non-native" servers
(i.e., Exchange from a Notes client, etc., although I don't remember the
possible combinations), but it gets very ugly, very fast, and most support
organizations will not support such configurations--and neither will
vendors.

> Although it might appear surprising, these other 10%
> or 20% of users that don't use the native client that
> came with the server software (for example, a Unix machine
> on an Exchange server, a Macintosh on a Notes server, or
> a user loosely related to the Enterprise located in the
> middle of nowhere) don't use IMAP but do use POP3, and
> I think it has to do mostly with IT not wanting to support
> fancy configurations and yes MAPI is fancy compared to POP3.

Quite so.  As soon as the environment starts to get a bit mixed up,
combinations and permutations multiply alarmingly, and it becomes impossible
to reliably support anything.  Thus, whenever two disparate systems must
communicate, the safest path is the lowest common denominator ... the
simplest protocol.  So a non-Outlook client accessing an Exchange server
will do so most reliably using SMTP and POP3, not IMAP or native MAPI or
anything.

> There are indeed some enterprises that have a Unix-based
> mail system accessed by the crowd of Windows clients ...

And one of them was Microsoft itself, until it migrated to Exchange.  It's
previous worldwide corporate e-mail system used Microsoft Mail clients, but
a proprietary Xenix-based MTA, instead of the MS-DOS-based MTA that the
company actually sold to customers.  The heat that Microsoft received from
its customer base due to this obvious hypocrisy was a major motivator to
move the entire corporate user base to Exchange as soon as Exchange worked
with some degree of reliability.




From owner-ietf@ietf.org  Wed Jun  4 17:51:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14212
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 17:51:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NfnV-00070v-VO
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 17:27:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NfUc-0006Hm-GC
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 17:08:22 -0400
Received: from freebie.atkielski.com (ASt-Lambert-110-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12781
	for <ietf@ietf.org>; Wed, 4 Jun 2003 17:08:18 -0400 (EDT)
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h54L8K1O014804
	for <ietf@ietf.org>; Wed, 4 Jun 2003 23:08:20 +0200 (CEST)
Message-ID: <01a101c32add$6d1caa40$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu><016c01c32960$56b1adb0$46124104@eagleswings><16092.51912.740900.110873@thomasm-u1.cisco.com><70660000.1054674804@askvoll.hjemme.alvestrand.no> <16093.10524.494835.396218@thomasm-u1.cisco.com> <010001c32ac2$934bdb70$afb58742@ssprunk>
Subject: Re: authenticated email
Date: Wed, 4 Jun 2003 23:08:07 +0200
MIME-Version: 1.0
Content-Type: multipart/signed;
	micalg=SHA1;
	boundary="----=_NextPart_000_019D_01C32AEE.290E6C60";
	protocol="application/x-pkcs7-signature"
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
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_019D_01C32AEE.290E6C60
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: 7bit

Stephen writes:

> Does my signature on this message make you trust
> it more than, say, the ten ads you got this morning
> for Viagra?

Yes.

> Why or why not?

It proves who you are, which means that you expose yourself to a certain
extent in the event that you do anything inappropriate with your e-mail.
This implies that your intentions are honorable; and even if they are not,
the signature makes you easier to track down and take action against.  So it
makes one feel a bit warmer and fuzzier.

------=_NextPart_000_019D_01C32AEE.290E6C60
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Disposition: attachment;
	filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKVjCCAj0w
ggGmAhEAzbp/VvDf5LxU/iKss3KqVTANBgkqhkiG9w0BAQIFADBfMQswCQYDVQQGEwJVUzEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xNzA1BgNVBAsTLkNsYXNzIDEgUHVibGljIFByaW1hcnkgQ2Vy
dGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNOTYwMTI5MDAwMDAwWhcNMjgwODAxMjM1OTU5WjBfMQsw
CQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNzA1BgNVBAsTLkNsYXNzIDEgUHVi
bGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwgZ8wDQYJKoZIhvcNAQEBBQADgY0A
MIGJAoGBAOUZv22jVmEtmUhx9mfeuY3rt56GgAqRDvo4Ja9GiILlc6igmyRdDR/MZW4MsNBWhBiH
mgabEKFz37RYOWtuwfYV1aioP6oSBo0xrH+wNNePNGeICc0UEeJORVZpH3gCgNrcR5EpuzbJY1zF
4Ncth3uhtzKwezC6Ki8xqu6jZ9rbAgMBAAEwDQYJKoZIhvcNAQECBQADgYEATD+4i8Zo3+5DMw5d
6abLB4RNejP/khv0Nq3YlSI2aBFsfELM85wuxAc/FLAPT/+Qknb54rxK6Y/NoIAK98Up8YIiXbix
3YEjo3slFUYweRb46gVLlH8dwhzI47f0EEA8E8NfH1PoSOSGtHuhNbB7Jbq4046rPzidADQAmPPR
cZQwggNiMIICy6ADAgECAhAL2gsXwT+JjqsJdHq0zi4zMA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNV
BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMg
UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIy
MzU5NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1
c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJ
bmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0GCSqGSIb3DQEB
AQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqdufBou5XZMUFweoFL
uUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIztW5UiE+HSr8Z2vkV6A+Hthzj
zMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQABo4GwMIGtMA8GA1UdEwQIMAYBAf8CAQAw
RwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUFBwIBFh93d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBMDEGA1UdHwQqMCgwJqAkoCKGIGh0dHA6Ly9jcmwudmVyaXNpZ24uY29t
L3BjYTEuY3JsMAsGA1UdDwQEAwIBBjARBglghkgBhvhCAQEEBAMCAQYwDQYJKoZIhvcNAQECBQAD
gYEAAn2eb0VLOKC43ulTZCG85Ewrjx7+kkCs2Ao5aqEyISwHm6tZ/tJiGn1VOLA3c9z0B2ZjYr3h
U3BSh+eo2FLpWy2q4d7PrDFU1IsZyNgjqO8EKzJ9LBgcyHyJqC538kTRZQpNdLXu0xuSc3QuiTs1
E3LnQDGa07LEq+dWvovj+xUwggSrMIIEFKADAgECAhAdlRDQU7I3ROsd8Kij07DEMA0GCSqGSIb3
DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1
c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJ
bmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDQxMjAwMDAw
MFoXDTA0MDQxMTIzNTk1OVowggEdMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMW
VmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0
b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTQwMgYDVQQLEytEaWdpdGFsIElEIENsYXNzIDEgLSBNaWNyb3NvZnQgRnVs
bCBTZXJ2aWNlMR0wGwYDVQQDFBRBbnRob255IEcuIEF0a2llbHNraTEkMCIGCSqGSIb3DQEJARYV
YW50aG9ueUBhdGtpZWxza2kuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDGUafMQZf4
eG90SDyCM2jh4hCT00JYUB1JXHQHx8kEVgyan4IYSxPpBb/iG88RHo/S7ShrhFX1I17XDweEuQ9k
h1ozeW8tPRATHhpWxuWynhWfXwmDo8lUqc23new2JjVCbZ7CQ1h6Kydck3gxrFY6TJEmI+zrrpKX
r+7+g+LkBwIDAQABo4IBODCCATQwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhF
AQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEF
BQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkg
cmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMDAG
CmCGSAGG+EUBBgcEIhYgMzE5YmJhYjJkMjMzMTQ0NDM0MDZhNzkzOTljMTIzM2UwMwYDVR0fBCww
KjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0BAQQF
AAOBgQBbj7tHSzURvZQoJPo8QdAxBM3U0dZDLDWtDFCWGwlyHpusnYsAKPs6Qo3bBUSmcbz8Wa4w
eN2VrbLiGrG1XDbO/stcS1OGlPcSQ2TjMkdDH87GXPD3wMZJGQxZmq6Ow/T80mMHlSwWcWLve0vG
5f4An35okIM9Q5Mxu8ynQftbszGCAkUwggJBAgEBMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwg
SW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlz
aWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYG
A1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO
b3QgVmFsaWRhdGVkAhAdlRDQU7I3ROsd8Kij07DEMAkGBSsOAwIaBQCggbowGAYJKoZIhvcNAQkD
MQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDMwNjA0MjEwODA3WjAjBgkqhkiG9w0BCQQx
FgQUVjIO6OpBZwa5Zcu0pO38oioAGEIwWwYJKoZIhvcNAQkPMU4wTDAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwBwYFKw4D
Ah0wDQYJKoZIhvcNAQEBBQAEgYCJLF6ipZQU+a1xqkivRD1ll2CE2RMFq/Wo4oP6TiRjLHQSRM/i
2XXUnQykQyQdL+zh7CgYgPCk2/mRqCbu1R8kPvxH9q/pScPAjuuIoqBOvbKxY78hp1gRUg3v1tAO
aeriEpCJ7vghbmmeN1R4Ei5uM4/OQi1LguVBJnG+TM/exQAAAAAAAA==

------=_NextPart_000_019D_01C32AEE.290E6C60--




From owner-ietf@ietf.org  Wed Jun  4 19:58:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18093
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 19:58:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nhh0-0008Dz-3n
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 19:29:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NhcB-00087S-Uk
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 19:24:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17122
	for <ietf@ietf.org>; Wed, 4 Jun 2003 19:24:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NhaN-00018o-00
	for ietf@ietf.org; Wed, 04 Jun 2003 19:22:27 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NhaM-00018Y-00
	for ietf@ietf.org; Wed, 04 Jun 2003 19:22:26 -0400
Content-class: urn:content-classes:message
Subject: RE: IMAP v. POP (Was: The utilitiy of IP is at stake here)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Wed, 4 Jun 2003 16:24:11 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F85B@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: IMAP v. POP (Was: The utilitiy of IP is at stake here)
Thread-Index: AcMquL1XWCygHaJmQVCnLeXsavzb4QAMhDWQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Dave Crocker" <dcrocker@brandenburg.com>,
        "Terry Gray" <gray@cac.washington.edu>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA18093

> Dave Crocker wrote:
> this is going to take us down a distracting path, but since
> you mention it, i would have switched to IMAP long ago, for
> exactly the multi-computer scenario you cite. but i have not
> come across an email user agent with features I need that
> also has support for IMAP that works acceptably.

Ditto. Among other things, my requirements for email are:
- It must be accessible from several computers.
- It must be accessible over https from anywhere, which pretty much
means the mail has to be stored on the server. Some loss of
functionality compared to the native client is acceptable.
- It must be accessible offline from a laptop (with a real keyboard, for
plane trips) that can synchronize over a dial-up and from a PDA/phone
that can synchronize over GPRS. Preferably it should not try to sync
that 5 meg spreadsheet that requires 1024x768 or better to view to the
PDA.

I would say that IMHO if IMAP has not replaced POP, it's because of two
things:
- No ISP would provide enough storage for _my_ mailbox and subfolders,
and I think that to large extent this would be true for most would-be
IMAP users.
- "enterprise" software has grabbed a large part of that potential
market by providing smoother off-line functionality and better
integration with calendar/contacts stuff.

I don't see why IMAP could not provide these features; I guess it's a
matter of implementation. I do see very good value in having a
standards-based system but unfortunately I've not found one that I like.

Michel.




From owner-ietf@ietf.org  Wed Jun  4 20:40:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19750
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 20:40:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nid8-0001zv-Cv
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 20:29:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NiMf-0001ea-Td
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 20:12:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18894
	for <ietf@ietf.org>; Wed, 4 Jun 2003 20:12:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NiKs-0001VB-00
	for ietf@ietf.org; Wed, 04 Jun 2003 20:10:30 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NiKr-0001V8-00
	for ietf@ietf.org; Wed, 04 Jun 2003 20:10:29 -0400
Received: from MOU1WNEXC03.verisign.com (verisign.com [65.205.251.57])
        by peacock.verisign.com (8.12.9/) with ESMTP id h550CJ53020751
        for <ietf@ietf.org>; Wed, 4 Jun 2003 17:12:19 -0700 (PDT)
Received: by mou1wnexc03.verisign.com with Internet Mail Service (5.5.2653.19)
	id <MG8G0YV3>; Wed, 4 Jun 2003 17:12:19 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D21CB@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: This IETF discussion list 
Date: Wed, 4 Jun 2003 17:12:18 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

It appears that this list is in danger of going the way of the ASRG list.
That is currently down to about 6 active posters and a chair that appears to
regard the primary purpose of the group as a platform for his media
appearences.

I suspected at an early stage that a faction within ASRG wanted to break up
the group. The tactics I saw used were the type of behavior that is more
commonly associated with Trotskyite entryism tactics. The pattern of
behavior was as follows:

Every constructive proposal to the list was drowned out by repeated postings
of ridiculous and abusive objections. My contention that spam frequently
contains forged headers was attacked repeatedly as 'lies' etc. It turned out
that the facts about spam sender behavior were not in dispute, only the
definition of forged.

Other people were driven away with simple abuse. One woman who is a leader
of one of the significant industry forums was described as "a snake" and
generally told her contributions are unwellcome.

Another form of trolling the group was to send offensive bounce messages to
other list members 'your message has been identified as spam and reported to
DCC so it will be blocked everywhere else'.

A large number of people have left the group and cited behavior of members
of the faction as the reason. Response from chair, block posts from people
who are not members of the faction! My posts have been blocked because I am
starting another anti-spam group in a different forum (I am happy to share
the message where the chair admits this).


At first I thought this was just standard IETF flamewars. After a while I
started to wonder if the faction was actually a group of spam senders who
were running anti-spam operations as cover. If you think about it this makes
a lot of sense, you could run a blacklist of open relays and unblacklist the
relays at exactly the time you want to use them. Result you can get more
mail through than your competitors.

This seemed unlikely though. After a while I realized the pattern, the
members of the faction who were being deliberately disruptive have a
position as known anti-spam crusaders. They simply do not want a solution to
the spam problem, if that goes away so does their position.

That also explains some of the positions in the arguments over the
definition of spam. Some people have been attempting to define spam to be
'that which my application detects and eliminates'. Even that would be OK if
they had not been so offensive in the way they said it.


Constructive criticism is good, but the type of criticism I have been seeing
is of the kind that is deliberately destructive, criticism for the sake of
criticism. 

I find it particularly telling that ideas that I introduced to the group
when it started are now being proposed by the people who attacked them in
unplesant terms. 

I do not think this model is working. A rational way to start a research
group would be to bring some people together and then let them elect someone
to organize and chair the group. I know this is not the IETF way, but it is
the only way I know that succeeds in being genuinely open and genuinely
inclusive.

I know this is the IRTF not the IETF, but the media is being told that the
group is the IETF answer to the spam problem. The subject of spam has major
media attention.

If the IETF is going to run itself on the experts protecting the Internet
from itself model then please stop trying to claim that it is somehow has
invented a mechanism that is more democratic than democracy. At least if the
IETF admitted its organization structure was really an oligarchy it could
then convene a blue riband panel to look at this problem or send experts to
the panels that do convene. 

Instead we have a structure that is failing and an organization that is
shrinking.  It is not just the end of the dotcom boom that is causing the
IETF to shrink. The standards are being developed in other fora, places
where there is real accountability and real inclusiveness. By inclusiveness
I don't just mean I get to say what I like and the chair then feels free to
ignore my opinion and that of the rest of the group and substitute their own
unilaterally because they are going to decide how they define consensus.  

When I first got involved in the IETF ten years ago the big issues were the
deployment of IPv6, DNSSEC and IPSEC. Today the same three big issues are on
the table with negligible progress for the time spent. The world is simply
not prepared to wait ten years for the IETF to think about perhaps
addressing the spam problem.

		Phill



From owner-ietf@ietf.org  Wed Jun  4 21:06:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20516
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 21:06:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nirb-0002kE-P6
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 20:44:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Nidn-000201-Ul
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 20:30:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19400
	for <ietf@ietf.org>; Wed, 4 Jun 2003 20:30:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nibz-0001c2-00
	for ietf@ietf.org; Wed, 04 Jun 2003 20:28:11 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nibz-0001bz-00
	for ietf@ietf.org; Wed, 04 Jun 2003 20:28:11 -0400
Received: from MOU1WNEXC03.verisign.com (verisign.com [65.205.251.57])
        by peacock.verisign.com (8.12.9/) with ESMTP id h550U153023529
        for <ietf@ietf.org>; Wed, 4 Jun 2003 17:30:01 -0700 (PDT)
Received: by mou1wnexc03.verisign.com with Internet Mail Service (5.5.2653.19)
	id <MG8G0Y8X>; Wed, 4 Jun 2003 17:30:01 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D21CC@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: authenticated email 
Date: Wed, 4 Jun 2003 17:30:01 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Stephen writes:

> Does my signature on this message make you trust
> it more than, say, the ten ads you got this morning
> for Viagra?

Your signature tells me nothing, its what I kinow about your private key
that is significant.

If there is someone I trust that signs a statement that says that they have
authenticated the business address of the preson sending the message I can
have a certain level of confidence that it is not spam. The vast majority of
the spams sent are out and out frauds. These people do not want to leave
behind contact addresses.

If there is someone who in addition says that they have audited the sender
or obtained some sort of anti-spam bond from them then the level of
confidence may be higher.

It there is someone who states that the private key corresponding to the
public key in question is embedded in secure hardware that enforces a
particular signing policy then you can have a higher degree of confidence
still (note, this is not a standards suggestion, certain implementations of
that concept are covered by pending patent claims).

PKI is a tried, tested and deployed solution at this stage. It works really
well at the enterprise level and there is a whole industry based on it.
Don't confuse the fact that PGP or webs of trust or whatever fail to solve a
problem with what PKI can and has achieved. There is a reason that
infrastructure is necessary.

	Phill



From owner-ietf@ietf.org  Wed Jun  4 21:10:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20839
	for <ietf-web-archive@odin.ietf.org>; Wed, 4 Jun 2003 21:10:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nird-0002ll-4k
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 20:44:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NikD-0002Cf-6e
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 20:36:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19626
	for <ietf@ietf.org>; Wed, 4 Jun 2003 20:36:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NiiP-0001dk-00
	for ietf@ietf.org; Wed, 04 Jun 2003 20:34:49 -0400
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=localhost)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nii9-0001dZ-00
	for ietf@ietf.org; Wed, 04 Jun 2003 20:34:43 -0400
Received: by localhost (Postfix, from userid 501)
	id DADFB4B69A; Thu,  5 Jun 2003 12:35:29 +1200 (FJT)
Subject: Re: authenticated email
From: Franck Martin <franck@sopac.org>
To: Stephen Sprunk <stephen@sprunk.org>
Cc: Michael Thomas <mat@cisco.com>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
In-Reply-To: <010001c32ac2$934bdb70$afb58742@ssprunk>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
	 <016c01c32960$56b1adb0$46124104@eagleswings>
	 <16092.51912.740900.110873@thomasm-u1.cisco.com>
	 <70660000.1054674804@askvoll.hjemme.alvestrand.no>
	 <16093.10524.494835.396218@thomasm-u1.cisco.com>
	 <010001c32ac2$934bdb70$afb58742@ssprunk>
Content-Type: multipart/alternative; boundary="=-UruLG4TRcI+XZYHyEFAE"
Organization: SOPAC
Message-Id: <1054773329.2720.10.camel@localhost>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2-3mdk 
Date: 05 Jun 2003 12:35:29 +1200
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-UruLG4TRcI+XZYHyEFAE
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

www.spamassassin.org is a cost based system which is quite useful but
has many false positives too....

The best system I have found is tmda.sourceforge.net which concept is
used on a couple of commercial individual systems...

The concept is quite simple... 

Someone unknown to me send me an e-mail. I do not receive this e-mail
yet but an automatic reply ask the person to perform a task to
authenticate itself... Like replying to a specific address after reading
the message (something like a simple Turing test to prove the person is
human). The e-mail of this person is then added to my whitelist, I
receive this person e-mail as well as all subsequent e-mails....

Any person that wants to talk to me will follow the procedure... any
spammer will not bother to follow the procedure because suddenly it
costs him time therefore money... Remember it is a Turing test so a
machine cannot pass it....

Now what digital signing should bring, the power to sue because of the
traceability.

Cheers

On Thu, 2003-06-05 at 05:55, Stephen Sprunk wrote:

> Thus spake "Michael Thomas" <mat@cisco.com>
> > It depends on what you mean by signing. Signing a message in and
> > of itself ought not hurt anything modulo software bugs, etc. But the
> > real question is what does the receiving program (MTA, MUA) do
> > with that signature? At the very least it could verify the signature,
> > but then what? If it doesn't verify do you drop it? (transitive trust
> > comes into play, but most likely). Does it do anything beyond that?
> 
> Well, if you use a score-based anti-spam system, the lack of a signature
> could "cost" a message a few points, but that's about it.
> 
> The root problem here is we're trying to define an authentication system
> without also defining the authorization or accounting systems to use it.



-- 
Franck Martin <franck@sopac.org>
SOPAC

--=-UruLG4TRcI+XZYHyEFAE
Content-Type: text/html; charset=utf-8

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/1.1.8">
</HEAD>
<BODY>
<A HREF="http://www.spamassassin.org">www.spamassassin.org</A> is a cost based system which is quite useful but has many false positives too....<BR>
<BR>
The best system I have found is tmda.sourceforge.net which concept is used on a couple of commercial individual systems...<BR>
<BR>
The concept is quite simple... <BR>
<BR>
Someone unknown to me send me an e-mail. I do not receive this e-mail yet but an automatic reply ask the person to perform a task to authenticate itself... Like replying to a specific address after reading the message (something like a simple Turing test to prove the person is human). The e-mail of this person is then added to my whitelist, I receive this person e-mail as well as all subsequent e-mails....<BR>
<BR>
Any person that wants to talk to me will follow the procedure... any spammer will not bother to follow the procedure because suddenly it costs him time therefore money... Remember it is a Turing test so a machine cannot pass it....<BR>
<BR>
Now what digital signing should bring, the power to sue because of the traceability.<BR>
<BR>
Cheers<BR>
<BR>
On Thu, 2003-06-05 at 05:55, Stephen Sprunk wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE><FONT COLOR="#737373" SIZE="3"><I>Thus spake &quot;Michael Thomas&quot; &lt;mat@cisco.com&gt;
&gt; It depends on what you mean by signing. Signing a message in and
&gt; of itself ought not hurt anything modulo software bugs, etc. But the
&gt; real question is what does the receiving program (MTA, MUA) do
&gt; with that signature? At the very least it could verify the signature,
&gt; but then what? If it doesn't verify do you drop it? (transitive trust
&gt; comes into play, but most likely). Does it do anything beyond that?

Well, if you use a score-based anti-spam system, the lack of a signature
could &quot;cost&quot; a message a few points, but that's about it.

The root problem here is we're trying to define an authentication system
without also defining the authorization or accounting systems to use it.</I></FONT></PRE>
</BLOCKQUOTE>
<FONT SIZE="3"></FONT><BR>
<PRE><TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
Franck Martin &lt;<A HREF="mailto:franck@sopac.org">franck@sopac.org</A>&gt;<BR>
SOPAC
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-UruLG4TRcI+XZYHyEFAE--



From owner-ietf@ietf.org  Thu Jun  5 03:45:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10114
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 03:45:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NpCJ-0007JC-Nm
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 03:30:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Np8j-0007FZ-Su
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 03:26:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09734
	for <ietf@ietf.org>; Thu, 5 Jun 2003 03:26:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Np6v-0003oF-00
	for ietf@ietf.org; Thu, 05 Jun 2003 03:24:33 -0400
Received: from vrx.net ([216.13.126.22] helo=ns1.vrx.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Np6u-0003oB-00
	for ietf@ietf.org; Thu, 05 Jun 2003 03:24:32 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-128-181.lsanca1.dsl-verizon.net [4.33.128.181])
	by ns1.vrx.net (Postfix) with ESMTP
	id 948C1D2A3; Thu,  5 Jun 2003 03:26:14 -0400 (EDT)
Mime-Version: 1.0
X-Sender: stef@vrx.net
Message-Id: <v04220817bb049d8a2dd4@[192.168.1.14]>
In-Reply-To: <01a101c32add$6d1caa40$0a00000a@atkielski.com>
References: 
 <200306022228.h52MS2gv016239@ginger.lcs.mit.edu><016c01c32960$56b1adb0$461
 24104@eagleswings><16092.51912.740900.110873@thomasm-u1.cisco.com><7066000
 0.1054674804@askvoll.hjemme.alvestrand.no>
 <16093.10524.494835.396218@thomasm-u1.cisco.com>
 <010001c32ac2$934bdb70$afb58742@ssprunk>
 <01a101c32add$6d1caa40$0a00000a@atkielski.com>
Date: Thu, 5 Jun 2003 00:26:06 -0700
To: "Anthony Atkielski" <anthony@atkielski.com>
From: Einar Stefferud <Stef@thor.nma.com>
Subject: Re: authenticated email
Cc: "IETF Discussion" <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

Wow!  What a mighty leap of faith!

Let me offer a different view...  

Stephen's CERT proves that the sender is a person who got a CERT from some CERT provider and has a contract with that provider, but has no contract with Anthony, 
so that when Steven does something bad to Anthony, like snd him some spam, and 
Anthony complains to the CERT provider, the CERT provider is going to say 
"You don't have any contract with us, so we do not owe you anything."

In fact, Anthony might not even be findable because of his holding a CERT, 
because he was able to obtain the CERT with false information.

So, I have to ask why you trust those CERTS.

I don't trust em just because they come with a contract that denies all kinds 
of liabilities in the reliance on or use of those CERTS.

The problem is that I do not trust the transitivity of trust as required by PKI.
This is because I have ever seen proof of trust transitivity.

Show me the proof of it and I will believe it, if your proof stands up!

Cheers...\Stef

At 23:08 +0200 6/4/03, Anthony Atkielski wrote:
>Stephen writes:
>
> > Does my signature on this message make you trust
> > it more than, say, the ten ads you got this morning
> > for Viagra?
>
>Yes.
>
> > Why or why not?
>
>It proves who you are, which means that you expose yourself to a certain
>extent in the event that you do anything inappropriate with your e-mail.
>This implies that your intentions are honorable; and even if they are not,
>the signature makes you easier to track down and take action against.  So it
>makes one feel a bit warmer and fuzzier.
>
>Content-Type: application/x-pkcs7-signature;
>	name="smime.p7s"
>Content-Disposition: attachment;
>	filename="smime.p7s"
>
>Attachment converted: Viking5:smime.p7s (????/----) (00097E08)




From owner-ietf@ietf.org  Thu Jun  5 04:08:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10787
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 04:08:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NpeR-0007ua-Ap
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 03:59:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Npds-0007sh-9S
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 03:58:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10603
	for <ietf@ietf.org>; Thu, 5 Jun 2003 03:58:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Npc3-00042L-00
	for ietf@ietf.org; Thu, 05 Jun 2003 03:56:43 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Npc2-00042I-00
	for ietf@ietf.org; Thu, 05 Jun 2003 03:56:42 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h557wX1O020531
	for <ietf@ietf.org>; Thu, 5 Jun 2003 09:58:33 +0200 (CEST)
Message-ID: <020001c32b38$42ca6830$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu> <016c01c32960$56b1adb0$46124104@eagleswings> <16092.51912.740900.110873@thomasm-u1.cisco.com> <70660000.1054674804@askvoll.hjemme.alvestrand.no> <16093.10524.494835.396218@thomasm-u1.cisco.com> <010001c32ac2$934bdb70$afb58742@ssprunk> <1054773329.2720.10.camel@localhost>
Subject: Re: authenticated email
Date: Thu, 5 Jun 2003 09:58:33 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Franck writes:

> Someone unknown to me send me an e-mail. I do not
> receive this e-mail yet but an automatic reply ask
> the person to perform a task to authenticate itself...
> Like replying to a specific address after reading
> the message (something like a simple Turing test to
> prove the person is human). The e-mail of this person
> is then added to my whitelist, I receive this person
> e-mail as well as all subsequent e-mails....

All well and good in principle, but many of your correspondents will be
confused by the automatic reply, and many also will not consider it
worthwhile to perform the authentication task just to join your whitelist.
So you will lose legitimate e-mail in this way, just as you would with
automated spam filter.

> Any person that wants to talk to me will follow
> the procedure ...

Any person who wants to talk to you badly enough will follow the procedure.
But other correspondents may find the task so time-consuming and troublesome
to carry out, and so will simply abandon their attempt to communicate
instead.  In some cases, these latter correspondents may have important
things to say.  So you risk the loss of important, legitimate e-mail.

> ... any spammer will not bother to follow the procedure
> because suddenly it costs him time therefore money ...

The problem is that it will cost ALL of your correspondents time and money.
Those who do not wish to spend extra time and money to talk to you will stop
communicating, even if they are not spammers.

Here again, the fundamental difficulty is that there is no way for a machine
to distinguish between spam and legitimate e-mail; any remedy applied to
spam will also reject legitimate e-mail, and any remedy that guarantees
passage of all legitimate e-mail will also allow spam to get through.  Only
individual human inspection of e-mail messages can separate spam and
legitimate e-mail with 100% accuracy.

> Now what digital signing should bring, the power
> to sue because of the traceability.

Not if the signing party is out of legal reach.  Once again, the problem is
a human problem, in that there is no fundamental, machine-readable
difference between a spammer's signature and a legitimate correspondent's
signature, so just putting signatures on e-mail will not allow spam to be
automatically excluded, and requiring signatures will reject legitimate
correspondents just as readily as it deters spammers.





From owner-ietf@ietf.org  Thu Jun  5 04:28:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11355
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 04:28:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Npt3-0008SZ-OO
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 04:14:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Npo2-0008L1-Jm
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 04:09:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10840
	for <ietf@ietf.org>; Thu, 5 Jun 2003 04:09:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NpmD-000468-00
	for ietf@ietf.org; Thu, 05 Jun 2003 04:07:14 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NpmC-000464-00
	for ietf@ietf.org; Thu, 05 Jun 2003 04:07:13 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h558931O020610
	for <ietf@ietf.org>; Thu, 5 Jun 2003 10:09:03 +0200 (CEST)
Message-ID: <020601c32b39$ba6494f0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References:  <200306022228.h52MS2gv016239@ginger.lcs.mit.edu><016c01c32960$56b1adb0$461 24104@eagleswings><16092.51912.740900.110873@thomasm-u1.cisco.com><7066000 0.1054674804@askvoll.hjemme.alvestrand.no> <16093.10524.494835.396218@thomasm-u1.cisco.com> <010001c32ac2$934bdb70$afb58742@ssprunk> <01a101c32add$6d1caa40$0a00000a@atkielski.com> <v04220817bb049d8a2dd4@[192.168.1.14]>
Subject: Re: authenticated email
Date: Thu, 5 Jun 2003 10:09:03 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Einar writes:

> Wow!  What a mighty leap of faith!

That's why they call it trust.

> Stephen's CERT proves that the sender is a person
> who got a CERT from some CERT provider and has a
> contract with that provider, but has no contract
> with Anthony ...

No.  In cryptographic authentication, signing a message with a private key
proves only that the signing entity had access to the private key--nothing
more.  Everything else is human interpretation.

If the human side is handled correctly, crypto authentication can be very
useful and secure indeed.  But if you cannot trust the human management, the
high technical security of the authentication method itself is of little
use.

> ... so that when Steven does something bad to Anthony,
> like snd him some spam, and Anthony complains to the
> CERT provider, the CERT provider is going to say
> "You don't have any contract with us, so we do not
> owe you anything."

The provider of the certificate is not a police organization, and there is
no reason why I would complain to them.  A certification authority does not
certify anything except the authenticity of a certificate, that is, the CA
guarantees that the identification information contained in the certificate
is true and correct.  CAs do not guarantee anything else, nor are they
responsible for the actions of the entities they certify.  As long as a
subscriber is not attempting to forge certificates or identities within
certificates, the CA is not involved.

Expecting the CA to act as a police organization is like complaining to the
Federal Reserve Board when you pay money to a tradesman and you have a
dispute with him.

> In fact, Anthony might not even be findable because
> of his holding a CERT, because he was able to obtain
> the CERT with false information.

It's up to the CA to verify entities sufficiently that falsification of
certificates is difficult.  The CA's business depends on the trustworthiness
of its verification.  However, if the identity does indeed check out, the CA
 has done its job and owes you nothing else.

> So, I have to ask why you trust those CERTS.

It depends on the CA.  Verisign seemed trustworthy until they handed a
brand-new Microsoft certificate to a complete stranger in an almost
unbelievably stupid breach of security, so I have my doubts about them now.
You have to trust a CA to a certain extent in order for it to be useful,
just as you have to trust a bank to a certain extent before you are willing
to put money on deposit with them.

> I don't trust em just because they come with a contract
> that denies all kinds of liabilities in the reliance
> on or use of those CERTS.

That's your decision, not mine.  Perhaps if the above explanation helps you
to understand the true purpose of certifying authorities, you'll adjust your
conclusions.

> The problem is that I do not trust the transitivity
> of trust as required by PKI.  This is because I have
> ever seen proof of trust transitivity.

There isn't any proof beyond the basic technical level of keys and
signatures.  The rest is a human issue.

> Show me the proof of it and I will believe it, if
> your proof stands up!

Whether you believe it or not is irrelevant to me.  I'm just explaining how
it is done.




From owner-ietf@ietf.org  Thu Jun  5 07:05:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14754
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 07:05:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NsNl-0001gW-OG
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 06:54:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NsMC-0001f5-Bm
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 06:52:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14469
	for <ietf@ietf.org>; Thu, 5 Jun 2003 06:52:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NsKN-0004rf-00
	for ietf@ietf.org; Thu, 05 Jun 2003 06:50:39 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NsKM-0004rH-00
	for ietf@ietf.org; Thu, 05 Jun 2003 06:50:38 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 0219562207
	for <ietf@ietf.org>; Thu,  5 Jun 2003 12:51:59 +0200 (CEST)
Date: Thu, 05 Jun 2003 12:51:59 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Result of test - authenticated email
Message-ID: <273700000.1054810319@askvoll.hjemme.alvestrand.no>
In-Reply-To: <70660000.1054674804@askvoll.hjemme.alvestrand.no>
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>
 <016c01c32960$56b1adb0$46124104@eagleswings>
 <16092.51912.740900.110873@thomasm-u1.cisco.com>
 <70660000.1054674804@askvoll.hjemme.alvestrand.no>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, juni 03, 2003 23:13:24 +0200 Harald Tveit Alvestrand 
<harald@alvestrand.no> wrote:

> I thought I'd try this....
>
> is there any particular disadvantage or centralization of power implied
> in me signing this message with my PGP key?
>
> If not, is there any particular reason that I shouldn't do this all the
> time?
>
> It's not a solution, but is there a downside?

well, it turns out that I have to answer this question with "yes".....

1) There is list software out there that munges headers on inner body 
parts, making the signature not verify. If people also discard "signature 
failed" messages, that means that some people will not hear what I say; for 
others, it will just irritate them and condition them to dismiss warnings 
about bad signatures - not a good idea in the long run.

2) There is MUA software out there that displays MIME security multiparts 
as an empty message with attachments. This means that some people will be 
irritated when I send messages in this signed format.

So there is still a downside to using signed mail. Not good.

[for those who advocate non-MIME signing schemes.... different topic.]

                  Harald




From owner-ietf@ietf.org  Thu Jun  5 07:18:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15160
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 07:18:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NscH-00028H-SI
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 07:09:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Nsb3-00025G-DT
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 07:07:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14901
	for <ietf@ietf.org>; Thu, 5 Jun 2003 07:07:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NsZE-0004we-00
	for ietf@ietf.org; Thu, 05 Jun 2003 07:06:00 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NsZD-0004wO-00
	for ietf@ietf.org; Thu, 05 Jun 2003 07:05:59 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id ED4E762207; Thu,  5 Jun 2003 13:07:20 +0200 (CEST)
Date: Thu, 05 Jun 2003 13:07:20 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dan Kolis <dank@hq.lindsayelec.com>, ietf@ietf.org
Subject: Re: IMAP v. POP 
Message-ID: <275720000.1054811240@askvoll.hjemme.alvestrand.no>
In-Reply-To: <20030604164134236.AAA178@hq.lindsayelec.com@rflooker1>
References:  <20030604164134236.AAA178@hq.lindsayelec.com@rflooker1>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On onsdag, juni 04, 2003 12:41:34 -0400 Dan Kolis 
<dank@hq.lindsayelec.com> wrote:

>
> It was said about IMAP versus POP mail:
>> Perhaps those folks should use an implementation that can manipulate mail
>> offline and then sync with the server later.
>
> Dan says:
> The group I know have an information technology group which raid and
> confiscate anything they don't install. They terrorize everyone in this
> huge fortune 100 company, and if they don't run the approved software
> they delete everything. They only allow IMAP (not POP), and its all
> connection oriented. The idea is this is more secure. But ultimately,
> obviously, people can screen capture and/or print anything, somehow. Then
> it can be reabsorbed in digital form; (scan, etc).
>
> I guess I realize, nearly by definition, you could make an offline/online
> IMAP implementation.

of course, that's what I use every day. [No advertisements on this list, so 
I won't mention which one it is....]

> I think POP is awefully functional though. If it just had passwords not in
> the clear, and a better way to defer big attachments, I think it would be
> nearly perfect protocol/service.

it has both.... if you use RFC 2595 TLS, or RFC 2195 CRAM-MD5, or even the 
RFC 1734 AUTHENTICATE, you won't have passwords in the clear; if you use 
the RFC 1939 POP LIST command, you get the size of all the messages, and 
can choose not to use the POP RETR command to get the big ones..... you 
have to use the TOP command to get the start of the long messages, though, 
and that doesn't know where attachments begin....

>
> For home and casual use though POP is cool. You can only expect so much
> from it. And with the extensions it can do a lot.
>
> There must be a pure 'push' email protocol either in the works or done,
> is't there?

yes - it's called "SMTP". (sorry, the "pure push" was just too juicy a 
target :-)

              Harald





From owner-ietf@ietf.org  Thu Jun  5 09:35:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24427
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 09:35:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NuRg-0005Zu-QE
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 09:06:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NZVn-0007Kr-V6
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 10:45:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24299
	for <ietf@ietf.org>; Wed, 4 Jun 2003 10:45:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NZU0-0003jE-00
	for ietf@ietf.org; Wed, 04 Jun 2003 10:43:20 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NZU0-0003jB-00
	for ietf@ietf.org; Wed, 04 Jun 2003 10:43:20 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0.6)
  with ESMTP-TLS id 210112 for ietf@ietf.org; Wed, 04 Jun 2003 09:44:41 -0500
Message-ID: <3EDE05F3.4010808@ehsco.com>
Date: Wed, 04 Jun 2003 09:45:07 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: discussion redirect
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


[I sent this yesterday but the message appears to have gotten lost. Sorry
for the duplicate if both of them eventually show up.]

I've setup a temporary mailing list to handle discussion of an alternate
mail transfer system, which I expect will get replaced by a real list
eventually, assuming that interest continues to progress. To subscribe to
that list, send an email message to mt2-subscribe@ehsco.com

I've also put together a basic outline proposal that shows what I'd like
to see in such a service. http://www.ehsco.com/misc/mt2/ has that proposal
(if it doesn't display right, you can download the original powerpoint
slides from http://www.ehsco.com/misc/mt2/MT2-00.ppt). I know that Keith
was scratching some ideas together for reusing SMTP and I'll post that if
he wants. Anybody that has any other proposals, let me know and I'll post
those too. We can discuss any or all of those on the mailing list. We
should probably move out of here anyway, before we get evicted.

Thanks

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






From owner-ietf@ietf.org  Thu Jun  5 09:42:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24869
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 09:42:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nugu-0005w2-Ft
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 09:22:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NdZ9-0003Ch-GE
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 15:04:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07150
	for <ietf@ietf.org>; Wed, 4 Jun 2003 15:04:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NdXK-00071b-00
	for ietf@ietf.org; Wed, 04 Jun 2003 15:03:02 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NdXI-00070s-00
	for ietf@ietf.org; Wed, 04 Jun 2003 15:03:00 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h54J47k00957;
        Wed, 4 Jun 2003 15:04:09 -0400 (EDT)
Date: Wed, 4 Jun 2003 15:04:07 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: discussion redirect
Message-Id: <20030604150407.038a60b3.moore@cs.utk.edu>
In-Reply-To: <3EDD3E2F.1000300@ehsco.com>
References: <3EDD3E2F.1000300@ehsco.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I've setup a temporary mailing list to handle discussion of an
> alternate mail transfer system, which I expect will get replaced by a
> real list eventually, assuming that interest continues to progress. To
> subscribe to that list, send an email message to
> mt2-subscribe@ehsco.com
> 
> I've also put together a basic outline proposal that shows what I'd
> like to see in such a service. http://www.ehsco.com/misc/mt2/ has that
> proposal(if it doesn't display right, you can download the original
> powerpoint slides from http://www.ehsco.com/misc/mt2/MT2-00.ppt). I
> know that Keith was scratching some ideas together for reusing SMTP
> and I'll post that if he wants.

I'm not going to join this list, because (a) it's almost certain to be
populated by naive crackpots, (b) we already have a perfectly good
public list to discuss solutions to the spam problem in ASRG, and (c)
I'm convinced that trying to solve the spam problem by re-inventing SMTP
is at best a useless distraction, and at worst a distraction that will
prevent real solutions from emerging.

Of course if the list distracts all of the crackpots, *that* might be
useful.





From owner-ietf@ietf.org  Thu Jun  5 10:28:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28110
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 10:28:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NvbS-0005sU-FI
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 10:20:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NvHn-0007uZ-Jp
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 10:00:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26005
	for <ietf@ietf.org>; Thu, 5 Jun 2003 10:00:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NvFy-0007AG-00
	for ietf@ietf.org; Thu, 05 Jun 2003 09:58:18 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NvFx-0007A6-00
	for ietf@ietf.org; Thu, 05 Jun 2003 09:58:17 -0400
Received: from mou1wnexc02.verisign.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.9/) with ESMTP id h55E0553022464
        for <ietf@ietf.org>; Thu, 5 Jun 2003 07:00:05 -0700 (PDT)
Received: by mou1wnexc02.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LYL9B6HP>; Thu, 5 Jun 2003 07:00:05 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D21D4@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Result of test - authenticated email
Date: Thu, 5 Jun 2003 07:00:03 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Harald points out some significant issues with pre-existing software.

I dispute his conclusion that a failed signature means that the message will
be thrown in the trash. Most filters (and certainly any compliant with the
criteria being discussed) would quarantine mail with a failed S/MIME
signature rather than discard.

The second point I would make is that the mailing list software is not
immutable. In fact mailing list software is likely to be rapidly upgraded to
support anti-spam filters very quickly since the manual anti-spam moderation
is a significant burden on the list admin.

The problem of broken, obsolete MUAs that do not support S/MIME cannot be
allowed to represent a veto. They have had plenty of time to upgrade, there
are plenty of free MUAs that work. I have a lot of time for deployment
problems when the people with the problem are not technologically
sophisticated and the only solutions are geekware. I have no time at all for
so-called technologists who refuse to eat their own dog food.

That said, yep, non-MIME based signatures may well be necessary. But this is
because the authentication model is diferent. We ae not authenticating at
the user level, we are authenticating at the domain level. Nobody is going
to block individual users of hotmail as spam senders, it is hotmail's job to
make sure that their customer's behave.


		Phill





From owner-ietf@ietf.org  Thu Jun  5 10:30:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24873
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 09:42:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nugu-0005vl-AV
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 09:22:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Nd0A-00051v-FV
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 14:28:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05022
	for <ietf@ietf.org>; Wed, 4 Jun 2003 14:28:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcyM-0006Wh-00
	for ietf@ietf.org; Wed, 04 Jun 2003 14:26:54 -0400
Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NcyM-0006Wc-00
	for ietf@ietf.org; Wed, 04 Jun 2003 14:26:54 -0400
Received: from nwmail.wh.lucent.com (h135-5-40-100.lucent.com [135.5.40.100])
	by ihemail2.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h54ISAt10513
	for <ietf@ietf.org>; Wed, 4 Jun 2003 13:28:10 -0500 (CDT)
Received: by nwmail.wh.lucent.com (8.11.7+Sun/EMS-1.5 sol2)
	id h54IS9C10054; Wed, 4 Jun 2003 14:28:09 -0400 (EDT)
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Received: from bell-labs.com by nwmail.wh.lucent.com (8.11.7+Sun/EMS-1.5 sol2)
	id h54IS6910036; Wed, 4 Jun 2003 14:28:06 -0400 (EDT)
Message-ID: <3EDE3A34.8010407@bell-labs.com>
Date: Wed, 04 Jun 2003 14:28:04 -0400
From: Uri Blumenthal <uri@bell-labs.com>
Organization: Lucent Tehcnologies / Bell Labs
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en, zh-cn, ru, de, he
MIME-Version: 1.0
To: Michael Thomas <mat@cisco.com>
Original-CC: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: authenticated email
References: <200306022228.h52MS2gv016239@ginger.lcs.mit.edu>	<016c01c32960$56b1adb0$46124104@eagleswings>	<16092.51912.740900.110873@thomasm-u1.cisco.com>	<70660000.1054674804@askvoll.hjemme.alvestrand.no> <16093.10524.494835.396218@thomasm-u1.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>  > is there any particular disadvantage or centralization of power implied in 
>  > me signing this message with my PGP key?

IMHO none (except for the extra inocnvenience of periodically
typing in the [long!] passphrase and hitting an extra key).

>  > If not, is there any particular reason that I shouldn't do this all the 
>  > time?

See above. :-)


>  > It's not a solution, but is there a downside?
> 
> It depends on what you mean by signing. Signing a
> message in and of itself ought not hurt anything
> modulo software bugs, etc. But the real question
> is what does the receiving program (MTA, MUA) do
> with that signature? At the very least it could
> verify the signature, but then what? If it doesn't
> verify do you drop it? (transitive trust comes
> into play, but most likely). Does it do anything
> beyond that?

1. IMHO if the sig doesn't verify - you drop the e-mail
    (just like if IPsec packet comes with a corrupted MAC,
     you drop it).

2. Spammers might just generate one-day PGP key, self-sign it,
    upload to a server - and voila! - for this day they're free
    to send.

    So the trust will have to be established, only certain
    signatures be accepted, etc. This means - a closed list.
    I'd be OK with that, actually.

> Let me ask something in return: do you think that
> just the act of signing mail -- with no trust
> roots implied -- could help? My sense is that it
> might in a sow-the-seeds kind of way for some
> later goodness (it's as you say not a solution).
> I too would be happy to hear downsides.

It might be good - but I think it will be ineffective in
spam-war.






From owner-ietf@ietf.org  Thu Jun  5 11:04:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29698
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 11:04:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nw7d-0006if-9c
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 10:53:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NvgY-000615-Dc
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 10:25:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27993
	for <ietf@ietf.org>; Thu, 5 Jun 2003 10:25:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nvei-0007NI-00
	for ietf@ietf.org; Thu, 05 Jun 2003 10:23:52 -0400
Received: from smtp.newsguy.com ([129.250.170.69] helo=newsguy.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nveh-0007N8-00
	for ietf@ietf.org; Thu, 05 Jun 2003 10:23:51 -0400
Received: (from root@localhost)
	by newsguy.com (8.9.1p2/8.9.1) id HAA06249;
	Thu, 5 Jun 2003 07:25:00 -0700 (PDT)
Mail-From: vn8d-b2qp@dea.spamcon.org  Wed Jun  4 16:59:20 2003
Received: from web01-nyc.clicvu.com (web01-nyc.clicvu.com [209.10.150.71])
	by newsguy.com (8.9.1p2/8.9.1) with ESMTP id QAA68980
	for <tedgavin@newsguy.com>; Wed, 4 Jun 2003 16:59:19 -0700 (PDT)
Received: from [192.168.0.71] by web01-nyc.clicvu.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-64039U1000L100S0V35)
          with SMTP id com for <tedgavin@newsguy.com>;
          Wed, 4 Jun 2003 19:52:18 -0400
Received: from [132.151.6.40] by web01-nyc.clicvu.com with SMTP (ClicVU Disposable Email Address Service) Tue, 03 Jun 2003 23:59:41 -500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nhh0-0008Dz-3n
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 19:29:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NhcB-00087S-Uk
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 19:24:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17122
	for <ietf@ietf.org>; Wed, 4 Jun 2003 19:24:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NhaN-00018o-00
	for ietf@ietf.org; Wed, 04 Jun 2003 19:22:27 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NhaM-00018Y-00
	for ietf@ietf.org; Wed, 04 Jun 2003 19:22:26 -0400
Content-class: urn:content-classes:message
Subject: RE: IMAP v. POP (Was: The utilitiy of IP is at stake here)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Date: Wed, 4 Jun 2003 16:24:11 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F85B@server2000.arneill-py.sacramento.ca.us>
Thread-Topic: IMAP v. POP (Was: The utilitiy of IP is at stake here)
Thread-Index: AcMquL1XWCygHaJmQVCnLeXsavzb4QAMhDWQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Reply-To: vn8d-b2qp@dea.spamcon.org
To: "Dave Crocker" <dcrocker@brandenburg.com>,
        "Terry Gray" <gray@cac.washington.edu>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA29698

-- Delivered via SpamCon Foundation DEA: http://dea.spamcon.org
-- Replies will be sent to michel@arneill-py.sacramento.ca.us
-- Additional Info: http://dea.spamcon.org/i/?v=3D938041

> Dave Crocker wrote:
> this is going to take us down a distracting path, but since
> you mention it, i would have switched to IMAP long ago, for
> exactly the multi-computer scenario you cite. but i have not
> come across an email user agent with features I need that
> also has support for IMAP that works acceptably.

Ditto. Among other things, my requirements for email are:
- It must be accessible from several computers.
- It must be accessible over https from anywhere, which pretty much
means the mail has to be stored on the server. Some loss of
functionality compared to the native client is acceptable.
- It must be accessible offline from a laptop (with a real keyboard, for
plane trips) that can synchronize over a dial-up and from a PDA/phone
that can synchronize over GPRS. Preferably it should not try to sync
that 5 meg spreadsheet that requires 1024x768 or better to view to the
PDA.

I would say that IMHO if IMAP has not replaced POP, it's because of two
things:
- No ISP would provide enough storage for _my_ mailbox and subfolders,
and I think that to large extent this would be true for most would-be
IMAP users.
- "enterprise" software has grabbed a large part of that potential
market by providing smoother off-line functionality and better
integration with calendar/contacts stuff.

I don't see why IMAP could not provide these features; I guess it's a
matter of implementation. I do see very good value in having a
standards-based system but unfortunately I've not found one that I like.

Michel.




From owner-ietf@ietf.org  Thu Jun  5 11:17:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01035
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 11:17:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nw7f-0006mw-8m
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 10:53:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Nvvs-0006aD-Vb
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 10:41:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28742
	for <ietf@ietf.org>; Thu, 5 Jun 2003 10:41:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nvu3-0007Um-00
	for ietf@ietf.org; Thu, 05 Jun 2003 10:39:43 -0400
Received: from smtp.newsguy.com ([129.250.170.69] helo=newsguy.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nvu2-0007Ud-00
	for ietf@ietf.org; Thu, 05 Jun 2003 10:39:42 -0400
Received: (from root@localhost)
	by newsguy.com (8.9.1p2/8.9.1) id HAA20729;
	Thu, 5 Jun 2003 07:41:04 -0700 (PDT)
Mail-From: ijsi-y7so@dea.spamcon.org  Wed Jun  4 17:41:35 2003
Received: from web01-nyc.clicvu.com (web01-nyc.clicvu.com [209.10.150.71])
	by newsguy.com (8.9.1p2/8.9.1) with ESMTP id RAA81114
	for <tedgavin@newsguy.com>; Wed, 4 Jun 2003 17:41:34 -0700 (PDT)
Received: from [192.168.0.71] by web01-nyc.clicvu.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-64039U1000L100S0V35)
          with SMTP id com for <tedgavin@newsguy.com>;
          Wed, 4 Jun 2003 20:34:33 -0400
Received: from [132.151.6.40] by web01-nyc.clicvu.com with SMTP (ClicVU Disposable Email Address Service) Tue, 03 Jun 2003 23:59:41 -500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nid8-0001zv-Cv
	for ietf-list@asgard.ietf.org; Wed, 04 Jun 2003 20:29:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NiMf-0001ea-Td
	for ietf@asgard.ietf.org; Wed, 04 Jun 2003 20:12:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18894
	for <ietf@ietf.org>; Wed, 4 Jun 2003 20:12:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NiKs-0001VB-00
	for ietf@ietf.org; Wed, 04 Jun 2003 20:10:30 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NiKr-0001V8-00
	for ietf@ietf.org; Wed, 04 Jun 2003 20:10:29 -0400
Received: from MOU1WNEXC03.verisign.com (verisign.com [65.205.251.57])
        by peacock.verisign.com (8.12.9/) with ESMTP id h550CJ53020751
        for <ietf@ietf.org>; Wed, 4 Jun 2003 17:12:19 -0700 (PDT)
Received: by mou1wnexc03.verisign.com with Internet Mail Service (5.5.2653.19)
	id <MG8G0YV3>; Wed, 4 Jun 2003 17:12:19 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D21CB@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Reply-To: ijsi-y7so@dea.spamcon.org
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: This IETF discussion list 
Date: Wed, 4 Jun 2003 17:12:18 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

-- Delivered via SpamCon Foundation DEA: http://dea.spamcon.org
-- Replies will be sent to pbaker@verisign.com
-- Additional Info: http://dea.spamcon.org/i/?v=1189197

It appears that this list is in danger of going the way of the ASRG list.
That is currently down to about 6 active posters and a chair that appears to
regard the primary purpose of the group as a platform for his media
appearences.

I suspected at an early stage that a faction within ASRG wanted to break up
the group. The tactics I saw used were the type of behavior that is more
commonly associated with Trotskyite entryism tactics. The pattern of
behavior was as follows:

Every constructive proposal to the list was drowned out by repeated postings
of ridiculous and abusive objections. My contention that spam frequently
contains forged headers was attacked repeatedly as 'lies' etc. It turned out
that the facts about spam sender behavior were not in dispute, only the
definition of forged.

Other people were driven away with simple abuse. One woman who is a leader
of one of the significant industry forums was described as "a snake" and
generally told her contributions are unwellcome.

Another form of trolling the group was to send offensive bounce messages to
other list members 'your message has been identified as spam and reported to
DCC so it will be blocked everywhere else'.

A large number of people have left the group and cited behavior of members
of the faction as the reason. Response from chair, block posts from people
who are not members of the faction! My posts have been blocked because I am
starting another anti-spam group in a different forum (I am happy to share
the message where the chair admits this).


At first I thought this was just standard IETF flamewars. After a while I
started to wonder if the faction was actually a group of spam senders who
were running anti-spam operations as cover. If you think about it this makes
a lot of sense, you could run a blacklist of open relays and unblacklist the
relays at exactly the time you want to use them. Result you can get more
mail through than your competitors.

This seemed unlikely though. After a while I realized the pattern, the
members of the faction who were being deliberately disruptive have a
position as known anti-spam crusaders. They simply do not want a solution to
the spam problem, if that goes away so does their position.

That also explains some of the positions in the arguments over the
definition of spam. Some people have been attempting to define spam to be
'that which my application detects and eliminates'. Even that would be OK if
they had not been so offensive in the way they said it.


Constructive criticism is good, but the type of criticism I have been seeing
is of the kind that is deliberately destructive, criticism for the sake of
criticism. 

I find it particularly telling that ideas that I introduced to the group
when it started are now being proposed by the people who attacked them in
unplesant terms. 

I do not think this model is working. A rational way to start a research
group would be to bring some people together and then let them elect someone
to organize and chair the group. I know this is not the IETF way, but it is
the only way I know that succeeds in being genuinely open and genuinely
inclusive.

I know this is the IRTF not the IETF, but the media is being told that the
group is the IETF answer to the spam problem. The subject of spam has major
media attention.

If the IETF is going to run itself on the experts protecting the Internet
from itself model then please stop trying to claim that it is somehow has
invented a mechanism that is more democratic than democracy. At least if the
IETF admitted its organization structure was really an oligarchy it could
then convene a blue riband panel to look at this problem or send experts to
the panels that do convene. 

Instead we have a structure that is failing and an organization that is
shrinking.  It is not just the end of the dotcom boom that is causing the
IETF to shrink. The standards are being developed in other fora, places
where there is real accountability and real inclusiveness. By inclusiveness
I don't just mean I get to say what I like and the chair then feels free to
ignore my opinion and that of the rest of the group and substitute their own
unilaterally because they are going to decide how they define consensus.  

When I first got involved in the IETF ten years ago the big issues were the
deployment of IPv6, DNSSEC and IPSEC. Today the same three big issues are on
the table with negligible progress for the time spent. The world is simply
not prepared to wait ten years for the IETF to think about perhaps
addressing the spam problem.

		Phill



From owner-ietf@ietf.org  Thu Jun  5 11:22:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02270
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 11:22:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NwRQ-0007Yb-SF
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 11:14:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Nw9S-0006qp-Qt
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 10:55:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29186
	for <ietf@ietf.org>; Thu, 5 Jun 2003 10:55:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nw7d-0007bZ-00
	for ietf@ietf.org; Thu, 05 Jun 2003 10:53:45 -0400
Received: from scaup.mail.pas.earthlink.net ([207.217.120.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Nw7d-0007bW-00
	for ietf@ietf.org; Thu, 05 Jun 2003 10:53:45 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by scaup.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19Nw9M-0007Uw-00; Thu, 05 Jun 2003 07:55:32 -0700
Date: Thu, 5 Jun 2003 10:53:23 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Result of test - authenticated email
Message-Id: <20030605105323.3b50929c.moore@cs.utk.edu>
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D21D4@mou1wnexm02.verisign.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D21D4@mou1wnexm02.verisign.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I dispute his conclusion that a failed signature means that the message will
> be thrown in the trash. Most filters (and certainly any compliant with the
> criteria being discussed) would quarantine mail with a failed S/MIME
> signature rather than discard.

That's a bit like saying that "most ISPs" would quarantine mail from dubious
sources rather than simply rejecting it or discarding it.  I agree with you
that it's more robust to quarantine suspect mail than to discard it, but 
the latter practice is already widespread.

> The second point I would make is that the mailing list software is not
> immutable. In fact mailing list software is likely to be rapidly upgraded to
> support anti-spam filters very quickly since the manual anti-spam moderation
> is a significant burden on the list admin.

What you cite as "fact" may not be supportable.  When a dozen or more
intermediaries might be involved in the handling of a message from sender to
recipient, and when many of these intermediaries leave little clue about what
modifications they might have made to a message (firewalls and virus filters
typicaly don't even leave a received field), it's difficult to track down the
culprits, even more difficult to get the vendors of those products to fix
them, and still more difficult to get the fixes deployed.

> The problem of broken, obsolete MUAs that do not support S/MIME cannot be
> allowed to represent a veto. 

Perhaps not, but it does seem useful to realize that such MUAs exist.

> I have no time at all for
> so-called technologists who refuse to eat their own dog food.

Welcome to the real world.  A huge number of so-called technologists are
forced to use Windows and Exchange even though they know better.



From owner-ietf@ietf.org  Thu Jun  5 12:11:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04905
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 12:11:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nwpa-0002Iy-1e
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 11:39:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NwjD-0000fH-Jn
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 11:32:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02869
	for <ietf@ietf.org>; Thu, 5 Jun 2003 11:32:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NwhO-0000QH-00
	for ietf@ietf.org; Thu, 05 Jun 2003 11:30:42 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NwhN-0000Px-00
	for ietf@ietf.org; Thu, 05 Jun 2003 11:30:41 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id LAA09643;
	Thu, 5 Jun 2003 11:20:04 -0400
Date: Thu, 5 Jun 2003 11:21:18 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Einar Stefferud <Stef@thor.nma.com>
cc: Anthony Atkielski <anthony@atkielski.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: authenticated email
In-Reply-To: <v04220817bb049d8a2dd4@[192.168.1.14]>
Message-ID: <Pine.LNX.4.44.0306051111560.1028-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

This is also true of drivers licenses, or any other identification.

The trust is transitive only to the extent you trust the CERT provider,
and to the extent that the CERT holder hasn't had they private key
compromised.  If the Cert authority can't be trusted, or can be fooled,
then all bets are off. The identity requirements for one large, well
respected Cert provider, for company certs, is a copy of the articles of
incorporation. This, just like birth certificates, can be obtained by
anyone who wants to pay the $15 fee.

Then there is the issue of sloppyiness with the key, or virus infection,
or other ways the private key can be compromised.  If the private key is
compromised, anyone with the private key can sign mail with your Cert.
Partly this is a function of computer hygiene. Not everyone on the planet
will be able to maintain this. It is quite easy to steal a password on a
shared PC.  This isn't hypothetical.  I have a customer where the
employees don't each have a personal computer.  Yet they all send email
via a webmail interface.

This type of solution isn't going to work, either. It might work for some
small groups, but it won't work for everyone, everywhere.

		--Dean

On Thu, 5 Jun 2003, Einar Stefferud wrote:

> Wow!  What a mighty leap of faith!
>
> Let me offer a different view...
>
> Stephen's CERT proves that the sender is a person who got a CERT from
> some CERT provider and has a contract with that provider, but has no
> contract with Anthony, so that when Steven does something bad to
> Anthony, like snd him some spam, and Anthony complains to the CERT
> provider, the CERT provider is going to say "You don't have any contract
> with us, so we do not owe you anything."
>
> In fact, Anthony might not even be findable because of his holding a CERT,
> because he was able to obtain the CERT with false information.
>
> So, I have to ask why you trust those CERTS.
>
> I don't trust em just because they come with a contract that denies all kinds
> of liabilities in the reliance on or use of those CERTS.
>
> The problem is that I do not trust the transitivity of trust as required by PKI.
> This is because I have ever seen proof of trust transitivity.
>
> Show me the proof of it and I will believe it, if your proof stands up!
>
> Cheers...\Stef
>
> At 23:08 +0200 6/4/03, Anthony Atkielski wrote:
> >Stephen writes:
> >
> > > Does my signature on this message make you trust
> > > it more than, say, the ten ads you got this morning
> > > for Viagra?
> >
> >Yes.
> >
> > > Why or why not?
> >
> >It proves who you are, which means that you expose yourself to a certain
> >extent in the event that you do anything inappropriate with your e-mail.
> >This implies that your intentions are honorable; and even if they are not,
> >the signature makes you easier to track down and take action against.  So it
> >makes one feel a bit warmer and fuzzier.
> >
> >Content-Type: application/x-pkcs7-signature;
> >	name="smime.p7s"
> >Content-Disposition: attachment;
> >	filename="smime.p7s"
> >
> >Attachment converted: Viking5:smime.p7s (????/----) (00097E08)
>
>
>




From owner-ietf@ietf.org  Thu Jun  5 13:50:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07816
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 13:50:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nyhf-00058N-Ry
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 13:39:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NyMH-0004tL-12
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 13:17:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06892
	for <ietf@ietf.org>; Thu, 5 Jun 2003 13:16:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NyKR-0001Ej-00
	for ietf@ietf.org; Thu, 05 Jun 2003 13:15:07 -0400
Received: from protactinium.btinternet.com ([194.73.73.176])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NyKP-0001Ea-00
	for ietf@ietf.org; Thu, 05 Jun 2003 13:15:06 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by protactinium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19NyLy-0005tm-00; Thu, 05 Jun 2003 18:16:42 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: <anthony@atkielski.com>, <ietf@ietf.org>
Subject: RE: authenticated email
Date: Thu, 5 Jun 2003 18:13:33 +0100
Message-ID: <004401c32b85$cb53d720$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> the CA guarantees that the identification information contained in the
certificate

Each CA has its own CPS. How do you the CA conduct its CPS accordingly? 





From owner-ietf@ietf.org  Thu Jun  5 13:59:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08287
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 13:59:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Nyhh-00059J-CO
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 13:39:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NyRv-0004vw-R1
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 13:22:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07167
	for <ietf@ietf.org>; Thu, 5 Jun 2003 13:22:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NyQ6-0001J6-00
	for ietf@ietf.org; Thu, 05 Jun 2003 13:20:58 -0400
Received: from einsteinium.btinternet.com ([194.73.73.147])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NyQ5-0001Iw-00
	for ietf@ietf.org; Thu, 05 Jun 2003 13:20:57 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by einsteinium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19NyRq-0000yL-00
	for ietf@ietf.org; Thu, 05 Jun 2003 18:22:46 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: <ietf@ietf.org>
Subject: Re: authenication email
Date: Thu, 5 Jun 2003 18:19:37 +0100
Message-ID: <004501c32b86$a4676f40$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

My question is how can you trust the CA?

According to http://mcg.org.br/cert.htm, you can trust the CA:

A characteristic of  X.509 is that it predicates that almost all issues
that involve semantics or trust are delegated to a CA's CPS  --
Certification Practice Statement -- which is declared out of scope in
relationship to X.509. The CA's CPS is the governing law that the CA
presents to potential clients and represents a top-down framework. While
some consider the CPS mechanism to be a good way to introduce
flexibility in X.509 because each CA can have their own rules for
different needs, such mechanism can be considered as X.509's
"black-hole" and cannot be harmonized for different CAs. Thus, while
this "black-hole" mechanism affords a "solution" to the undefined
semantic and trust features in X.509 (as they are declared out of scope
and delegated to the CPS), such "laissez faire" attitude leaves ample
room for strong differences between CAs and for a  biased
"take-it-or-leave it" attitude regarding what a CA subscriber can
expect. Further, it does not scale to a planetary Internet because even
though it could work in a parochial Internet where everyone knows what
to expect and share a common law and trust system, it is doubtful that
it could be always successfully applied between competing businesses or
different states in  a country -- much less between different countries.




From owner-ietf@ietf.org  Thu Jun  5 15:16:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12727
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 15:16:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19O05i-0006Ny-HD
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 15:08:02 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19NzrP-0000iP-9O
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 14:53:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10808
	for <ietf@ietf.org>; Thu, 5 Jun 2003 14:53:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NzpZ-0002Ck-00
	for ietf@ietf.org; Thu, 05 Jun 2003 14:51:21 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NzpY-0002CU-00
	for ietf@ietf.org; Thu, 05 Jun 2003 14:51:21 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 024AC625A2; Thu,  5 Jun 2003 20:52:42 +0200 (CEST)
Date: Thu, 05 Jun 2003 20:52:43 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: IETF Standards Process
Message-ID: <8800000.1054839163@askvoll.hjemme.alvestrand.no>
In-Reply-To: <Pine.LNX.4.44.0306040920280.1028-100000@commander.av8.net>
References:  <Pine.LNX.4.44.0306040920280.1028-100000@commander.av8.net>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On onsdag, juni 04, 2003 11:54:03 -0400 Dean Anderson <dean@av8.com> 
wrote:

> inline. I apologize in advance for so many questions. I have looked on the
> ISOC site, and IAB site, and other pages to find the answers to these
> questions.

since most of your questions can easily be answered "no", I don't see the 
point of going into details.

The "Obsoletes:" header is a protocol that is too weak to carry the full 
semantics of the relationship between documents.

Proposed Standards are being used in the real world, for reasons that the 
users of those standards find sufficient.

RFCs are never changed.

ISOC's code of conduct bullet 4 says:

>Avoid deploying technologies that defeat generally accepted technical 
>principles of the Internet, as documented primarily by the Internet 
>Engineering Task Force (IETF). In particular, avoid technologies that tend 
>to subdivide access to the Internet rather than preserving its universal, 
>unique, and international nature, except as required by security 
mechanisms >mentioned in the next paragraph

It is our fervent hope that we do not publish Proposed Standards that 
defeat generally accepted technical principles of the Internet.

                     Harald




From owner-ietf@ietf.org  Thu Jun  5 15:45:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13943
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 15:45:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19O0GR-00015E-Fc
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 15:19:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19O07Q-000755-Ds
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 15:09:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11875
	for <ietf@ietf.org>; Thu, 5 Jun 2003 15:09:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19O05a-0002KF-00
	for ietf@ietf.org; Thu, 05 Jun 2003 15:07:54 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19O05Z-0002KC-00
	for ietf@ietf.org; Thu, 05 Jun 2003 15:07:54 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h55J9ee0026052
	for <ietf@ietf.org>; Thu, 5 Jun 2003 21:09:40 +0200 (CEST)
Message-ID: <029d01c32b96$03c70810$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <004401c32b85$cb53d720$0100010a@MyHomeLAN.local>
Subject: Re: authenticated email
Date: Thu, 5 Jun 2003 21:09:40 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I'm not sure that I understand what you are asking.

----- Original Message ----- 
From: "Haren Visavadia" <haren@btopenworld.com>
To: <anthony@atkielski.com>; <ietf@ietf.org>
Sent: Thursday, June 05, 2003 19:13
Subject: RE: authenticated email


> > the CA guarantees that the identification information contained in the
> certificate
> 
> Each CA has its own CPS. How do you the CA conduct its CPS accordingly? 
> 
> 
> 



From owner-ietf@ietf.org  Thu Jun  5 15:47:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14213
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 15:47:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19O0GS-00015z-Ej
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 15:19:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19O0A1-0007om-3c
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 15:12:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12212
	for <ietf@ietf.org>; Thu, 5 Jun 2003 15:12:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19O08B-0002Lm-00
	for ietf@ietf.org; Thu, 05 Jun 2003 15:10:35 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19O08A-0002Lj-00
	for ietf@ietf.org; Thu, 05 Jun 2003 15:10:34 -0400
Received: from mou1wnexc02.verisign.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.9/) with ESMTP id h55JCP53026890
        for <ietf@ietf.org>; Thu, 5 Jun 2003 12:12:25 -0700 (PDT)
Received: by mou1wnexc02.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LYL9CSFC>; Thu, 5 Jun 2003 12:12:26 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D21DB@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Certificate / CPS issues
Date: Thu, 5 Jun 2003 12:12:25 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

The CPS states the authentication processes that the CA uses in issuing the
certificate or otherwise certifying the key (amongst other things).

You can trust the CPS in the sense that the CPS of a well known CA should
provide you with a reliable indication of the level of risk involved in
relying on the certificate.


Yes there are ways to get hold of a certificate even if you are a bad
person. In the credit card world every transaction carries insurance, so the
risk is acceptable. In the spam control world the risk is that you get
spammed, a problem but hardly a mission critical, can never happen
compromise. In the Web Services world someone can steal goods or services, a
real problem - so expect Web Services PKI services to be based on PKI models
such as XKMS where insurance can be sold with each transaction.

Ok so imagine the spam sender registers a bogus company, sends spam. What is
the redress, how long can they get away with it and how easy will it be to
get a replacement certificate?

It is likely that spam senders are going to get caught pretty quickly,
within the first 100,000 messages or so. Spam a honeypot, get your
credentials revoked. In theory you could revoke at that point. For technical
reasons I won't bore you with it is more likely you would want to not revoke
the cert and instead revoke a 'trustworthy sender' attribute. This can still
be advertised through XKMS.

It is even possible to push the revocation notice out so that the emails can
be retrospectively quarantined, this would require new protocol. 


A spam sender could attempt to use disposable certificates in the same way
that IP addresses and dialup accounts are considered disposable. This is
unlikely to work for long, the spam sender can set up lots of shell
companies at the same address but if the CA keeps authenticating to the same
address or phone number the pattern will soon become apparent.

There is even an empirical measurment of how effective a CA's processes are.
Just look at the scores that spamBayes is assigning to certs from different
CAs. The zero-Authentication CAs will quickly be attacked by spam senders.

		Phill



From owner-ietf@ietf.org  Thu Jun  5 15:48:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14328
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 15:48:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19O0Hh-0001DZ-5m
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 15:20:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19O0Ff-00010V-D6
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 15:18:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12976
	for <ietf@ietf.org>; Thu, 5 Jun 2003 15:18:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19O0Dp-0002U9-00
	for ietf@ietf.org; Thu, 05 Jun 2003 15:16:25 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19O0Do-0002U6-00
	for ietf@ietf.org; Thu, 05 Jun 2003 15:16:24 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h55JJCxS024509;
	Thu, 5 Jun 2003 21:19:12 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 5 Jun 2003 21:18:17 +0200
Subject: Re: authenticated email
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <anthony@atkielski.com>, <ietf@ietf.org>
To: "Haren Visavadia" <haren@btopenworld.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <004401c32b85$cb53d720$0100010a@MyHomeLAN.local>
Message-Id: <76202798-978A-11D7-BB6D-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On donderdag, jun 5, 2003, at 19:13 Europe/Amsterdam, Haren Visavadia 
wrote:

> Each CA has its own CPS. How do you the CA conduct its CPS accordingly?

Fortunately, as far as the spam issue is concerned, this question is 
moot: unlike a breach of confidentiality, a breach of spamfreeness is 
readily detectable. CAs that do a bad job here will be out of (this) 
business fast.




From owner-ietf@ietf.org  Thu Jun  5 16:18:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15418
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 16:18:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19O0jZ-00037k-IL
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 15:49:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19O0Qg-0001M6-OM
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 15:29:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13440
	for <ietf@ietf.org>; Thu, 5 Jun 2003 15:29:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19O0Or-0002Zu-00
	for ietf@ietf.org; Thu, 05 Jun 2003 15:27:49 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19O0Oq-0002Zq-00
	for ietf@ietf.org; Thu, 05 Jun 2003 15:27:48 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h55JM3S05700
	for <ietf@ietf.org>; Thu, 5 Jun 2003 12:22:03 -0700
Date: Thu, 5 Jun 2003 12:22:03 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: Result of test - authenticated email
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D21D4@mou1wnexm02.verisign.com>
Message-ID: <Pine.LNX.4.33.0306051214080.26569-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Thu, 5 Jun 2003, Hallam-Baker, Phillip wrote:

> I dispute his conclusion that a failed signature means that the message will
> be thrown in the trash. Most filters (and certainly any compliant with the
> criteria being discussed) would quarantine mail with a failed S/MIME
> signature rather than discard.

Acknowledging and ignoring your other points for this response since I
agree, I think that once a system exists and is reasonably deployed, I
will quickly throw away 'non-signed' mail and non-whiltelisted mail. The
whole point is to get ride of spam, not let me put off evaluating it.

My phone is set to block caller id. Every once in a while, I call someone
who had a phone company option which blocks calls which don't have caller
id. I have to unblock caller id and call again (though recently, I got to
give permission to reveal my phone number interactively).

Frankly, if somone doesn't think what they have to say is important
enough to them to use the proper 'signing' process or perhaps the
responder override, I don't need to hear from them. I've encounted this
process once or twice and it was trivial to reply to the query. Even my
80+ year old aunt and uncle who have been using email for less than 2
years would grok it.

So I will toss or bounce unidentified origin mail. And I can assure you
that 'civilians' I know will do it even faster than I will.

Dave Morris




From owner-ietf@ietf.org  Thu Jun  5 16:35:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13942
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 15:45:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19O0GR-00015r-Pu
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 15:19:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19O092-0007Vh-3Z
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 15:11:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12099
	for <ietf@ietf.org>; Thu, 5 Jun 2003 15:11:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19O07C-0002LX-00
	for ietf@ietf.org; Thu, 05 Jun 2003 15:09:34 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19O07B-0002LU-00
	for ietf@ietf.org; Thu, 05 Jun 2003 15:09:33 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h55JBOe0026065
	for <ietf@ietf.org>; Thu, 5 Jun 2003 21:11:24 +0200 (CEST)
Message-ID: <02a401c32b96$41bcd910$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <004501c32b86$a4676f40$0100010a@MyHomeLAN.local>
Subject: Re: authenication email
Date: Thu, 5 Jun 2003 21:11:24 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Haren writes:

> My question is how can you trust the CA?

You can't, or at least I cannot really imagine any CA that _everyone in the
world_ would be willing to trust.  This alone pretty much invalidates the
idea of using signatures as a way to reduce spam, unless you only wish to
reduce spam in certain microcosms of the Internet, instead of the whole
universe.





From owner-ietf@ietf.org  Thu Jun  5 19:46:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22573
	for <ietf-web-archive@odin.ietf.org>; Thu, 5 Jun 2003 19:46:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19O45W-000284-4G
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 19:24:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19O424-0001GO-4a
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 19:20:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21976
	for <ietf@ietf.org>; Thu, 5 Jun 2003 19:20:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19O40D-0004XF-00
	for ietf@ietf.org; Thu, 05 Jun 2003 19:18:37 -0400
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=localhost)
	by ietf-mx with esmtp (Exim 4.12)
	id 19O40C-0004Wj-00
	for ietf@ietf.org; Thu, 05 Jun 2003 19:18:36 -0400
Received: by localhost (Postfix, from userid 501)
	id 6E9A04B69A; Fri,  6 Jun 2003 11:19:56 +1200 (FJT)
Subject: [Fwd: Re: Progress on the Anti-Spam HOWTO]
From: Franck Martin <franck@sopac.org>
To: ietf@ietf.org, isdf@isoc.org
Content-Type: multipart/alternative; boundary="=-dCEPpPPsLPO9vwCxyEHI"
Organization: SOPAC
Message-Id: <1054855196.2660.28.camel@localhost>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2-3mdk 
Date: 06 Jun 2003 11:19:56 +1200
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-dCEPpPPsLPO9vwCxyEHI
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

For your Information

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


From: Hal Burgiss <hal@foobox.net>
To: discuss@en.tldp.org
Subject: Re: Progress on the Anti-Spam HOWTO
Date: 05 Jun 2003 19:13:06 -0400


Chris (hi!) has set up a mailing list for this HOWTO. Anyone
interested in contributing, or just hanging out, is welcome to
participate. 

The list server is a bit different than the open source ones most of
are used to. 

To subscribe, send a message to:

 LISTSERV@LISTS.MCGILL.CA

 with a blank subject line , and body without signature :

 SUB ANTI-SPAM-HOWTO firstname lastname


-- 
Hal Burgiss
 

______________________
http://lists.tldp.org/
-- 
Franck Martin <franck@sopac.org>
SOPAC

--=-dCEPpPPsLPO9vwCxyEHI
Content-Type: text/html; charset=utf-8

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/1.1.8">
</HEAD>
<BODY>
For your Information<BR>
<BR>
-----Forwarded Message-----<BR>
<BR>
<PRE><FONT SIZE="3"><B>From:</B></FONT> Hal Burgiss &lt;hal@foobox.net&gt;
<FONT SIZE="3"><B>To:</B></FONT> discuss@en.tldp.org
<FONT SIZE="3"><B>Subject:</B></FONT> Re: Progress on the Anti-Spam HOWTO
<FONT SIZE="3"><B>Date:</B></FONT> 05 Jun 2003 19:13:06 -0400


Chris (hi!) has set up a mailing list for this HOWTO. Anyone
interested in contributing, or just hanging out, is welcome to
participate. 

The list server is a bit different than the open source ones most of
are used to. 

To subscribe, send a message to:

 LISTSERV@LISTS.MCGILL.CA

 with a blank subject line , and body without signature :

 SUB ANTI-SPAM-HOWTO firstname lastname


-- 
Hal Burgiss
 

______________________
<A HREF="http://lists.tldp.org/">http://lists.tldp.org/</A>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
Franck Martin &lt;<A HREF="mailto:franck@sopac.org">franck@sopac.org</A>&gt;<BR>
SOPAC
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-dCEPpPPsLPO9vwCxyEHI--



From owner-ietf@ietf.org  Fri Jun  6 05:16:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14689
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 05:16:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OD6v-0004rA-Jf
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 05:02:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OCzL-0004qD-6C
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 04:54:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14366
	for <ietf@ietf.org>; Fri, 6 Jun 2003 04:54:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OCxU-0007TJ-00
	for ietf@ietf.org; Fri, 06 Jun 2003 04:52:24 -0400
Received: from einsteinium.btinternet.com ([194.73.73.147])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OCxT-0007TG-00
	for ietf@ietf.org; Fri, 06 Jun 2003 04:52:23 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by einsteinium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19OCzD-0005CW-00; Fri, 06 Jun 2003 09:54:11 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
Date: Fri, 6 Jun 2003 09:51:00 +0100
Message-ID: <000801c32c08$c12d0720$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D21DB@mou1wnexm02.verisign.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Verisign's declaimer which is part of the CPS. This would the CA simply
endorses the subscriber's information. How can you trust a CA with a
disclaimer like this?

"VERISIGN DISCLAIMS ANY WARRANTIES WITH RESPECT TO THE SERVICES PROVIDED
BY VERISIGN HEREUNDER INCLUDING WITHOUT LIMITATION ANY AND ALL IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
VERISIGN MAKES NO REPRESENTATION OR WARRANTY THAT ANY CA OR USER TO
WHICH IT HAS ISSUED A DIGITAL ID IN THE VERISIGN SECURE SERVER HIERARCHY
IS IN FACT THE PERSON OR ORGANIZATION IT CLAIMS TO BE WITH RESPECT TO
THE INFORMATION SUPPLIED TO VERISIGN. VERISIGN MAKES NO ASSURANCES OF
THE ACCURACY, AUTHENTICITY, INTEGRITY, OR RELIABILITY OF INFORMATION
CONTAINED IN DIGITAL IDS OR IN CRLs COMPILED, PUBLISHED OR DISSEMINATED
BY VERISIGN, OR OF THE RESULTS OF CRYPTOGRAPHIC METHODS IMPLEMENTED."





From owner-ietf@ietf.org  Fri Jun  6 05:17:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14733
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 05:17:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ODDY-0004tU-HH
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 05:09:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OD78-0004rC-Ka
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 05:02:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14488
	for <ietf@ietf.org>; Fri, 6 Jun 2003 05:02:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OD5H-0007Vg-00
	for ietf@ietf.org; Fri, 06 Jun 2003 05:00:27 -0400
Received: from gadolinium.btinternet.com ([194.73.73.111])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OD5H-0007Vd-00
	for ietf@ietf.org; Fri, 06 Jun 2003 05:00:27 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by gadolinium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19OD75-0005FE-00; Fri, 06 Jun 2003 10:02:19 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>, <ietf@ietf.org>
Subject: RE: authenticated email
Date: Fri, 6 Jun 2003 09:59:09 +0100
Message-ID: <000901c32c09$e47bc3f0$0100010a@MyHomeLAN.local>
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.2616
In-Reply-To: <76202798-978A-11D7-BB6D-00039388672E@muada.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

If SMTP server uses certification authentication to trace all messages
easily. And each mail adds the SMTP's server's public key and then is
signed by the SMTP on the message, so when you receive it you know if
the signature does not verify it has been tampered.




From owner-ietf@ietf.org  Fri Jun  6 05:28:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15128
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 05:28:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ODQL-0005fC-Bm
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 05:22:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ODMW-0005aH-Ce
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 05:18:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14906
	for <ietf@ietf.org>; Fri, 6 Jun 2003 05:18:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ODKf-0007dp-00
	for ietf@ietf.org; Fri, 06 Jun 2003 05:16:21 -0400
Received: from tungsten.btinternet.com ([194.73.73.81])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ODKf-0007dm-00
	for ietf@ietf.org; Fri, 06 Jun 2003 05:16:21 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by tungsten.btinternet.com with esmtp (Exim 3.22 #23)
	id 19ODMT-0007mK-00
	for ietf@ietf.org; Fri, 06 Jun 2003 10:18:13 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: <ietf@ietf.org>
Subject: RE: authenticated email
Date: Fri, 6 Jun 2003 10:15:03 +0100
Message-ID: <000a01c32c0c$1d1fd140$0100010a@MyHomeLAN.local>
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.2616
In-Reply-To: <76202798-978A-11D7-BB6D-00039388672E@muada.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

If message contains the public key of SMTP (which could be made-up), the
internet header and message is signed.

If public key stated does not encrypt the message digest. This would
mean it has been tampered/modified. 

If the public key stated is correct, when it verifies the message
digest. The message digest will include the message and the internet
headers. If this is successful, you certain trust the internet headers
which can used to trace. 




From owner-ietf@ietf.org  Fri Jun  6 06:20:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16135
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 06:20:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OE9c-0006K6-40
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 06:09:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OE51-0006Io-DA
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 06:04:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15933
	for <ietf@ietf.org>; Fri, 6 Jun 2003 06:04:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OE3A-00008f-00
	for ietf@ietf.org; Fri, 06 Jun 2003 06:02:20 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OE39-00008a-00
	for ietf@ietf.org; Fri, 06 Jun 2003 06:02:19 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h56A4Ce0033689
	for <ietf@ietf.org>; Fri, 6 Jun 2003 12:04:12 +0200 (CEST)
Message-ID: <005d01c32c12$fafeec70$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000801c32c08$c12d0720$0100010a@MyHomeLAN.local>
Subject: Re: Certificate / CPS issues
Date: Fri, 6 Jun 2003 12:04:12 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Verisign's declaimer which is part of the CPS.
> This would the CA simply endorses the subscriber's
> information. How can you trust a CA with a
> disclaimer like this?

You can't.

Furthermore, Verisign already compromised its trust model in the worst way
some time ago when it let a complete stranger obtain a Microsoft signing
certificate.  Since then, I've pretty much written them off as far as
trustworthiness goes.




From owner-ietf@ietf.org  Fri Jun  6 06:31:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16525
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 06:31:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OE9c-0006KC-Bj
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 06:09:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OE6R-0006JI-EB
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 06:05:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15944
	for <ietf@ietf.org>; Fri, 6 Jun 2003 06:05:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OE4a-000093-00
	for ietf@ietf.org; Fri, 06 Jun 2003 06:03:48 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OE4Z-000090-00
	for ietf@ietf.org; Fri, 06 Jun 2003 06:03:47 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h56A5de0033702
	for <ietf@ietf.org>; Fri, 6 Jun 2003 12:05:39 +0200 (CEST)
Message-ID: <006201c32c13$2ee339b0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000901c32c09$e47bc3f0$0100010a@MyHomeLAN.local>
Subject: Re: authenticated email
Date: Fri, 6 Jun 2003 12:05:39 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Haren writes:

> If SMTP server uses certification authentication
> to trace all messages easily. And each mail adds
> the SMTP's server's public key and then is
> signed by the SMTP on the message, so when you
> receive it you know if the signature does not verify
> it has been tampered.

This is a truckload of additional overhead, though.  Not only that, but even
a slight modification of the signed text will invalidate all the signatures.
Then what?




From owner-ietf@ietf.org  Fri Jun  6 06:45:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16956
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 06:45:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OEXo-00079L-P2
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 06:34:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OEVz-00075U-Nd
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 06:32:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16650
	for <ietf@ietf.org>; Fri, 6 Jun 2003 06:32:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OEU8-0000Li-00
	for ietf@ietf.org; Fri, 06 Jun 2003 06:30:12 -0400
Received: from zinc.btinternet.com ([194.73.73.148] helo=zinc)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OEU7-0000Lc-00
	for ietf@ietf.org; Fri, 06 Jun 2003 06:30:12 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by zinc with esmtp (Exim 3.22 #23)
	id 19OEVw-00049e-00; Fri, 06 Jun 2003 11:32:04 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Anthony Atkielski'" <anthony@atkielski.com>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
Date: Fri, 6 Jun 2003 11:28:53 +0100
Message-ID: <000b01c32c16$6e1999a0$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
In-Reply-To: <005d01c32c12$fafeec70$0a00000a@atkielski.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>Furthermore, Verisign already compromised its trust model in the worst
way
>some time ago when it let a complete stranger obtain a Microsoft
signing
>certificate. 

The trust model comprised due to failure on the CA's part. The CA had
failed to successfully identify who the person before issuing the
certificate.

This is one accident, but many more could occur in the future, resulting
potentially fake certificate which could being used, to sign e-mail.
Therefore the signature would not identify who the person is really.




From owner-ietf@ietf.org  Fri Jun  6 06:57:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17184
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 06:57:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OEpd-0007Yc-5R
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 06:52:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OEaU-0007AO-9w
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 06:36:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16782
	for <ietf@ietf.org>; Fri, 6 Jun 2003 06:36:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OEYd-0000Nd-00
	for ietf@ietf.org; Fri, 06 Jun 2003 06:34:51 -0400
Received: from protactinium.btinternet.com ([194.73.73.176])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OEYc-0000NY-00
	for ietf@ietf.org; Fri, 06 Jun 2003 06:34:50 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by protactinium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19OEaR-0005HG-00; Fri, 06 Jun 2003 11:36:43 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Anthony Atkielski'" <anthony@atkielski.com>, <ietf@ietf.org>
Subject: RE: authenticated email
Date: Fri, 6 Jun 2003 11:33:33 +0100
Message-ID: <000c01c32c17$14580a90$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
In-Reply-To: <006201c32c13$2ee339b0$0a00000a@atkielski.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>This is a truckload of additional overhead, though.  Not only that, but
>even
>a slight modification of the signed text will invalidate all the
>signatures.
>Then what?

I would personally delete the e-mail, since it can not be verified.




From owner-ietf@ietf.org  Fri Jun  6 07:07:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17643
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 07:07:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OErA-0007Zr-Pz
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 06:54:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OEfJ-0007Ap-Kc
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 06:41:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16892
	for <ietf@ietf.org>; Fri, 6 Jun 2003 06:41:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OEdS-0000Pt-00
	for ietf@ietf.org; Fri, 06 Jun 2003 06:39:50 -0400
Received: from carbon.btinternet.com ([194.73.73.92])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OEdS-0000Pq-00
	for ietf@ietf.org; Fri, 06 Jun 2003 06:39:50 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by carbon.btinternet.com with esmtp (Exim 3.22 #23)
	id 19OEfH-0004A7-00
	for ietf@ietf.org; Fri, 06 Jun 2003 11:41:43 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: <ietf@ietf.org>
Subject: Re: authenticated email
Date: Fri, 6 Jun 2003 11:38:30 +0100
Message-ID: <000d01c32c17$c72eaa20$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

As for SMTP Server forwarding to other SMTP servers, the message will
not signed until it reaches the receipt's domain SMTP server. Each of
the SMTP would authenticate themselves using a series of cryptography
challenges, to if the SMTP really holds the corresponding private key.




From owner-ietf@ietf.org  Fri Jun  6 09:34:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22940
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 09:34:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OHDt-0000mP-Qv
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 09:25:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OH48-0000X5-E0
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 09:15:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22277
	for <ietf@ietf.org>; Fri, 6 Jun 2003 09:15:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OH2H-0001st-00
	for ietf@ietf.org; Fri, 06 Jun 2003 09:13:37 -0400
Received: from jay.songbird.com ([208.184.79.253])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OH2G-0001sq-00
	for ietf@ietf.org; Fri, 06 Jun 2003 09:13:36 -0400
Received: from Rincewind.ninebynine.org (jay.songbird.com [208.184.79.253])
	(authenticated)
	by jay.songbird.com (8.11.6/8.11.3) with ESMTP id h56DFQ010360;
	Fri, 6 Jun 2003 06:15:26 -0700
Message-Id: <5.1.0.14.2.20030606113951.02d931c8@127.0.0.1>
X-Sender: gk-bulk@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 06 Jun 2003 11:50:13 +0100
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
From: Graham Klyne <GK@ninebynine.org>
Subject: Re: Certificate / CPS issues
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D21DB@mou1wnexm02.verisig
 n.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:12 05/06/03 -0700, Hallam-Baker, Phillip wrote:
>A spam sender could attempt to use disposable certificates in the same way
>that IP addresses and dialup accounts are considered disposable. This is
>unlikely to work for long, the spam sender can set up lots of shell
>companies at the same address but if the CA keeps authenticating to the same
>address or phone number the pattern will soon become apparent.

Hmmm... is there an economic play here?

<background>
First, briefly, my view of the spam situation.  I don't think it's 
fundamentally an Internet protocol design issue (though some design tweaks 
may help).  Essentially, I think people currently have the choice of
(1) putting filters in place and accept the loss of some non-spam mail, or
(2) accepting a deluge of spam, and not lose any mail.  In practice, I 
think this option doesn't exist, because I find that (lacking spam filters) 
I do lose a few pieces of non-spam mail because I don't recognize the 
sender or subject.  So I see a way forward to be a "passport" mechanism to 
reliably bypass automated spam filters, a kind of whitelist++.
</background>

So back to my question: is there an economic play here?

(I was offered the opinion once that a big *disadvantage* of email compared 
with fax for business transactions was that it has almost zero incremental 
cost of use.)

I'm thinking of a cert issued for a small sum of money, without any 
authentication other than the purchaser promises something like "I promise 
not to spam with this certificate".  At the earliest evidence of it being 
used for spamming, it is revoked.  The price should be small enough to be 
accessible to any reasonable person, but high enough that the bill for 
daily or hourly renewal would become significant.

Maybe crazy, just thinking aloud...

#g


-------------------
Graham Klyne
<GK@NineByNine.org>
PGP: 0FAA 69FF C083 000B A2E9  A131 01B9 1C7A DBCA CB5E




From owner-ietf@ietf.org  Fri Jun  6 11:08:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27708
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 11:08:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OIa3-0000mX-Ab
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 10:52:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OIP5-0000gj-MI
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 10:41:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26435
	for <ietf@ietf.org>; Fri, 6 Jun 2003 10:41:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OINE-0002dE-00
	for ietf@ietf.org; Fri, 06 Jun 2003 10:39:20 -0400
Received: from pigeon.verisign.com ([65.205.251.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OIND-0002dB-00
	for ietf@ietf.org; Fri, 06 Jun 2003 10:39:19 -0400
Received: from mou1wnexc01.verisign.com (verisign.com [65.205.251.53])
        by pigeon.verisign.com (8.12.9/) with ESMTP id h56EfDuv011119
        for <ietf@ietf.org>; Fri, 6 Jun 2003 07:41:13 -0700 (PDT)
Received: by mou1wnexc01.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LMLG2HB9>; Fri, 6 Jun 2003 07:41:13 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D21E5@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
Date: Fri, 6 Jun 2003 07:41:11 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Yes, the CPS disclaims all WARANTIES.

You do not want a CA that provides a recourse that depends on finding of
fault. WARANTIES are a specific legal instrument that provides recourse
through the courts under theories of merchantability and negligence. So you
have to PROVE the CA did something wrong... you don't want that.

What you want is insurance, read the relying party agreement. That
specifically provides insurance for certain specific failures. In other
words a NO-FAULT dispute procedure.

Do you think that folk signing PGP keys are undertaking unlimited liability
should the certification turn out to be incorrect?


Folk use our $15 a year certificates for some hair raising stuff. There is a
certain organization that moves very large sums of money every day whose PKI
consists of buying a few hundred certs from our consumer site via credit
card. So don't expect anyone to accept unlimited liability for a fixed $15
fee.

If you want to have insurance on a per transaction model you have to go to
an online technology. That is one of the many reasons we designed OCSP and
then XKMS.


I think the real problem here is that folk are demanding something that is
impossible. They want a PKI that is entirely costless, failure free and
provides unlimited liability. If you set that as the standard for existence
of a global PKI then you are never going to see one.

Security is risk control, not risk elimination.


		Phill



From owner-ietf@ietf.org  Fri Jun  6 11:50:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29275
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 11:50:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OJ5W-0001pa-Q9
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 11:25:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OIu4-0001aI-TX
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 11:13:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27947
	for <ietf@ietf.org>; Fri, 6 Jun 2003 11:13:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OIsD-0002xs-00
	for ietf@ietf.org; Fri, 06 Jun 2003 11:11:21 -0400
Received: from 66-120-210-136.ded.pacbell.net ([66.120.210.136] helo=exchange.ad.skymv.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OIsC-0002xp-00
	for ietf@ietf.org; Fri, 06 Jun 2003 11:11:21 -0400
Received: from exchange.ad.skymv.com ([192.168.1.71]) by exchange.ad.skymv.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 6 Jun 2003 08:12:48 -0700
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: RE: Certificate / CPS issues
Importance: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Date: Fri, 6 Jun 2003 08:12:48 -0700
Message-ID: <138AA78F80DCE84B8EE424399FFBF9C91B071B@exchange.ad.skymv.com>
Thread-Topic: Certificate / CPS issues
Thread-Index: AcMsMJfCYTEdjC7PRo6Xl08OJVyVHQADU4pg
From: "Dan Kohn" <dan@dankohn.com>
To: "Graham Klyne" <GK@ninebynine.org>, <ietf@ietf.org>
X-OriginalArrivalTime: 06 Jun 2003 15:12:48.0109 (UTC) FILETIME=[16F279D0:01C32C3E]
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam.  Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA29275

Regarding a "passport" mechanism, have you taken a look at
www.habeas.com?  Specifically, they offer such a "this is not spam"
warrant mark, and the pricing for individuals is free.  The trick is
that they use copyright and trademark law as the enforcement mechanism. 

(NB: I helped start the company.)

          - dan
--
Dan Kohn <mailto:dan@dankohn.com>
<http://www.dankohn.com/>  <tel:+1-650-327-2600>

-----Original Message-----
From: Graham Klyne [mailto:GK@ninebynine.org] 
Sent: Friday, June 06, 2003 03:50
To: Hallam-Baker, Phillip; 'ietf@ietf.org'

At 12:12 05/06/03 -0700, Hallam-Baker, Phillip wrote:
>A spam sender could attempt to use disposable certificates in the same
way
>that IP addresses and dialup accounts are considered disposable. This
is
>unlikely to work for long, the spam sender can set up lots of shell
>companies at the same address but if the CA keeps authenticating to the
same
>address or phone number the pattern will soon become apparent.

Hmmm... is there an economic play here?

<background>
First, briefly, my view of the spam situation.  I don't think it's 
fundamentally an Internet protocol design issue (though some design
tweaks 
may help).  Essentially, I think people currently have the choice of
(1) putting filters in place and accept the loss of some non-spam mail,
or
(2) accepting a deluge of spam, and not lose any mail.  In practice, I 
think this option doesn't exist, because I find that (lacking spam
filters) 
I do lose a few pieces of non-spam mail because I don't recognize the 
sender or subject.  So I see a way forward to be a "passport" mechanism
to 
reliably bypass automated spam filters, a kind of whitelist++.
</background>

So back to my question: is there an economic play here?

(I was offered the opinion once that a big *disadvantage* of email
compared 
with fax for business transactions was that it has almost zero
incremental 
cost of use.)

I'm thinking of a cert issued for a small sum of money, without any 
authentication other than the purchaser promises something like "I
promise 
not to spam with this certificate".  At the earliest evidence of it
being 
used for spamming, it is revoked.  The price should be small enough to
be 
accessible to any reasonable person, but high enough that the bill for 
daily or hourly renewal would become significant.

Maybe crazy, just thinking aloud...

#g


-------------------
Graham Klyne
<GK@NineByNine.org>
PGP: 0FAA 69FF C083 000B A2E9  A131 01B9 1C7A DBCA CB5E


_______________________________________________
This message was passed through ietf_censored@carmen.ipv6.cselt.it,
which is a sublist of ietf@ietf.org. Not all messages are passed.
Decisions on what to pass are made solely by Raffaele D'Albenzio.




From owner-ietf@ietf.org  Fri Jun  6 12:31:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01357
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 12:31:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OJtr-0003b4-Oy
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 12:17:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OJnw-0002z7-QO
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 12:11:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00374
	for <ietf@ietf.org>; Fri, 6 Jun 2003 12:10:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OJm5-0003aH-00
	for ietf@ietf.org; Fri, 06 Jun 2003 12:09:05 -0400
Received: from champdsl-25-66.mcleodusa.net ([216.43.25.66] helo=episteme-software.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OJm4-0003ZL-00
	for ietf@ietf.org; Fri, 06 Jun 2003 12:09:04 -0400
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server X 3.2.2b1);
 Fri, 6 Jun 2003 11:10:18 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p06001403bb066bdc01ea@[216.43.25.67]>
In-Reply-To: 
 <2A1D4C86842EE14CA9BC80474919782E0D21E5@mou1wnexm02.verisign.com>
References: 
 <2A1D4C86842EE14CA9BC80474919782E0D21E5@mou1wnexm02.verisign.com>
X-Mailer: Eudora [Macintosh version 6.0a15]
Date: Fri, 6 Jun 2003 11:10:25 -0500
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Pete Resnick <presnick@qualcomm.com>
Subject: RE: Certificate / CPS issues
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

On 6/6/03 at 7:41 AM -0700, Phillip Hallam-Baker wrote:

>Do you think that folk signing PGP keys are undertaking unlimited 
>liability should the certification turn out to be incorrect?

No, but if Mary turns out to be someone who signs PGP keys for people 
I don't like, I can simply say "Don't trust Mary" in my PGP 
application and the things she signs won't show up as valid unless 
someone I do trust signs them. If RSA screws up and signs keys for 
people I don't like, I can't (practically) say "Don't trust RSA" 
without invalidating a bunch of keys that I probably do want to trust.

I'm not by any means saying that PGP is a perfect solution. It's just 
that the liability scenario is very different because amount of 
damage any given signer can do is much different.

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102



From owner-ietf@ietf.org  Fri Jun  6 12:50:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02011
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 12:50:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OKCq-0004Gp-2d
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 12:36:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OK2p-0003kl-Na
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 12:26:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01196
	for <ietf@ietf.org>; Fri, 6 Jun 2003 12:26:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OK0y-0003oP-00
	for ietf@ietf.org; Fri, 06 Jun 2003 12:24:28 -0400
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OK0x-0003oG-00
	for ietf@ietf.org; Fri, 06 Jun 2003 12:24:27 -0400
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 19OK2g-0001jc-00; Fri, 06 Jun 2003 17:26:14 +0100
Date: Fri, 6 Jun 2003 17:26:13 +0100
To: Dan Kohn <dan@dankohn.com>
Cc: Graham Klyne <GK@ninebynine.org>, ietf@ietf.org
Subject: Re: Certificate / CPS issues
Message-ID: <20030606162613.GD4282@fysh.org>
References: <138AA78F80DCE84B8EE424399FFBF9C91B071B@exchange.ad.skymv.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <138AA78F80DCE84B8EE424399FFBF9C91B071B@exchange.ad.skymv.com>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

Dan Kohn wrote:
>Regarding a "passport" mechanism, have you taken a look at
>www.habeas.com?  Specifically, they offer such a "this is not spam"
>warrant mark, and the pricing for individuals is free.  The trick is
>that they use copyright and trademark law as the enforcement mechanism. 

I'm surprised that Habeas has caught on even to the extent it has, as I
see a fatal flaw in this use of copyright to get legal control.  It is
reminiscent of a legal case I recall where a games console refused to
execute any game unless a certain copyright notice (ascribing copyright to
the console manufacturer) appeared in a known location in the game ROM.
Third-party game manufacturers put the notice in their games, and were
hauled into court.  The court held that the copyright notice in question
was a functional part of the interface between the game and the console,
and that this overrode its normal semantic of signifying copyright
ownership.  The notice that the console looked for therefore didn't
mean anything legally, and the notice elsewhere in the game (the real
notice, ascribing ownership to the game manufacturer) was the legally
significant one.

What Habeas does is akin to publishing a protocol or file format in
a copyrighted document, and then suing implementors of the protocol
for copying sections of protocol data from the document.  It's mixing
expression with content (copyright protects one and not the other).
We wouldn't stand for it if Microsoft did that, and I don't think the
courts would either.  In fact, Microsoft has tried things very similar to
this, and we didn't stand for it.  I'm astonished that members of this
overwhelmingly pro-freedom and pro-reverse-engineering subculture have
themselves tried to deploy exactly the same odious trick.  Although I
approve of Habeas' aims, for the sake of our freedoms I hope that their
technique is held to be ineffective.

FWIW, my spam filter picks up Habeas headers as a strong ham indicator,
appearing in 0.4% of ham in my corpus and not at all in spam.  I'm waiting
to see which of these numbers is going to increase more significantly.

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



From owner-ietf@ietf.org  Fri Jun  6 13:16:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02896
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 13:16:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OKTX-0004oe-Rl
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 12:53:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OKO1-0004Pa-S3
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 12:48:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01953
	for <ietf@ietf.org>; Fri, 6 Jun 2003 12:48:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OKMA-000427-00
	for ietf@ietf.org; Fri, 06 Jun 2003 12:46:22 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OKM8-00041y-00
	for ietf@ietf.org; Fri, 06 Jun 2003 12:46:21 -0400
Received: from mou1wnexc02.verisign.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.9/) with ESMTP id h56Gm853024526;
        Fri, 6 Jun 2003 09:48:08 -0700 (PDT)
Received: by mou1wnexc02.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LYL91QM1>; Fri, 6 Jun 2003 09:48:08 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D21E8@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Pete Resnick'" <presnick@qualcomm.com>,
        "Hallam-Baker, Phillip"
	 <pbaker@verisign.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
Date: Fri, 6 Jun 2003 09:48:06 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Signs keys for people you don't LIKE?

I give (well sell) certs to plenty of people I don't LIKE. That is not the
issue, the issue is whether the authentication proceedure is being applied
as stated in the CPS or not.

If a bogus certificate is issued and the CA refuses to revoke it then you
have a big problem.

In your scenario what happens if you find out that Ted Tso or Jeff Schiller
has signed a bogus key. Do you then revoke every key they ever issued on
that account?


Please remember here that we are trying to solve the spam problem here. The
guys sending the stuff are organized criminals. It is bad if even one
criminal spam gets through. But it is also bad if you can't use email unless
you go pay $10,000 to some email good practice accreditation agency (yes
thay is what they charge).

So yes we can use certificates to address the spam problem, but don't expect
the criteria to be set at military security levels. Most people simply won't
pay for that.

		Phill

> -----Original Message-----
> From: Pete Resnick [mailto:presnick@qualcomm.com]
> Sent: Friday, June 06, 2003 12:10 PM
> To: Hallam-Baker, Phillip
> Cc: 'ietf@ietf.org'
> Subject: RE: Certificate / CPS issues
> 
> 
> On 6/6/03 at 7:41 AM -0700, Phillip Hallam-Baker wrote:
> 
> >Do you think that folk signing PGP keys are undertaking unlimited 
> >liability should the certification turn out to be incorrect?
> 
> No, but if Mary turns out to be someone who signs PGP keys for people 
> I don't like, I can simply say "Don't trust Mary" in my PGP 
> application and the things she signs won't show up as valid unless 
> someone I do trust signs them. If RSA screws up and signs keys for 
> people I don't like, I can't (practically) say "Don't trust RSA" 
> without invalidating a bunch of keys that I probably do want to trust.
> 
> I'm not by any means saying that PGP is a perfect solution. It's just 
> that the liability scenario is very different because amount of 
> damage any given signer can do is much different.
> 
> pr
> -- 
> Pete Resnick <mailto:presnick@qualcomm.com>
> QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: 
> (858)651-1102
> 



From owner-ietf@ietf.org  Fri Jun  6 13:32:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03511
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 13:32:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OKvf-0005Zx-PL
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 13:23:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OKiR-00051o-4K
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 13:09:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02643
	for <ietf@ietf.org>; Fri, 6 Jun 2003 13:09:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OKgZ-0004EE-00
	for ietf@ietf.org; Fri, 06 Jun 2003 13:07:27 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OKgX-0004DZ-00
	for ietf@ietf.org; Fri, 06 Jun 2003 13:07:25 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h56H1WS09053
	for <ietf@ietf.org>; Fri, 6 Jun 2003 10:01:32 -0700
Date: Fri, 6 Jun 2003 10:01:31 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D21E5@mou1wnexm02.verisign.com>
Message-ID: <Pine.LNX.4.33.0306060922440.26569-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Fri, 6 Jun 2003, Hallam-Baker, Phillip wrote:

>
> Security is risk control, not risk elimination.

Absolutely!

Extending that thought, managing risk is about the cost of loss vs. the
cost of protection.

Humans make mistakes. Systems fail. Sammy Sousa used the wrong bat. The
suttles failed. To reject a service because you have one presumed example
of failure is not realistic. A pattern of failures would be an issue, just
like you might avoid purchase of an automobile if Consumer Reports failure
statistics are abnormally high.

For the objectives we are discussing, I think the failure rate at Verisign
is not an issue. Most (perhaps all) folks in this discussion seem to agree
that the issue with spam is in the volume and not the mere existance of
spam. Social scientists could probably study the parallel growth of spam
and the corresponding growth in frustration and even end up with a volume
of spam which most people would be comfortable with. I strongly suspect
that reducing and keeping spam at 10% of current levels would probably be
success. Certainly, 1% would be.

On that premis, I'm certain it doesn't matter if 1 of the current 200
heavy duty spammers gets a fraudulant certificate. That might make final
identification more difficult, but most of the other mechanisms will still
function.

1. Proof of common source of the quantity of emails needed to be
   ruled as illegal
2. Source based filtering can still block mail identified with the
   cert
3. Once the fraud is discovered, the CA is likely to have process
   in place to avoid issuing new certs to the same entity

The last time I investigated, Verisign had certificates of different types
with different prices and levels of identification verification. Even the
cheapest have some cost and since I doubt that Verisign accepts cash
payment, there is identity associated with the payment. Worst case is a
stolen credit card is used to make payment. Since that is an immediate
felony, it may actually be the best case from anti-spam perspective.
Because of this cost (and the difficulty of obtaining and risk of using a
large number of stolen credit cards), it seems less likely that spammers
will follow the scenario of obtaining a large number of throw away
certificates.

Conclusion, I don't see the less than 100% trustworthiness of any CA to be
an impediment to the use of certificates as part of an email origin
identification scheme. Only a fool would accept a self-signed certificate
as having any significance so I think the suggestion that the ability of a
spammer to generate their own storm of certificates has little merit.

Dave Morris




From owner-ietf@ietf.org  Fri Jun  6 13:40:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03867
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 13:40:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OKvg-0005bl-Mv
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 13:23:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OKpS-0005LW-PI
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 13:16:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02921
	for <ietf@ietf.org>; Fri, 6 Jun 2003 13:16:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OKnb-0004Hk-00
	for ietf@ietf.org; Fri, 06 Jun 2003 13:14:43 -0400
Received: from mail12.speakeasy.net ([216.254.0.212] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OKnY-0004He-00
	for ietf@ietf.org; Fri, 06 Jun 2003 13:14:41 -0400
Received: (qmail 13460 invoked from network); 6 Jun 2003 17:16:27 -0000
Received: from unknown (HELO 192.168.254.124) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <zefram@fysh.org>; 6 Jun 2003 17:16:27 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: Zefram <zefram@fysh.org>
Subject: Habeas (was: Certificate / CPS issues)
Date: Fri, 6 Jun 2003 13:19:00 -0400
User-Agent: KMail/1.5
Cc: ietf@ietf.org
References: <138AA78F80DCE84B8EE424399FFBF9C91B071B@exchange.ad.skymv.com> <20030606162613.GD4282@fysh.org>
In-Reply-To: <20030606162613.GD4282@fysh.org>
Approved: Look, Ah say, look at me when Ah'm typin' at yew, boah!
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200306061319.00427.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Zefram <zefram@fysh.org> wrote:

 > I'm surprised that Habeas has caught on even to the extent it has, as
 > I see a fatal flaw in this use of copyright to get legal control.  It
 > is reminiscent of a legal case I recall where a games console refused
 > to execute any game unless a certain copyright notice (ascribing
 > copyright to the console manufacturer) appeared in a known location
 > in the game ROM. Third-party game manufacturers put the notice in
 > their games, and were hauled into court.  The court held that the
 > copyright notice in question was a functional part of the interface
 > between the game and the console, and that this overrode its normal
 > semantic of signifying copyright ownership.

Where this analogy breaks down, is that Habeas is not interfering with 
the functionality of non-Habeas email.  First, what to do with marked or 
unmarked email is entirely up to the recipient (or his ISP, or whoever 
else is doing spam filtering).  Second, it is not saying "everything 
else is spam" (and therefore delaying it getting through, except by 
comparison), just "this is not spam".

A better analogy would be, say, any sort of optional certification.  
You're perfectly welcome to buy electrical devices not approved by 
Underwriters Laboratories, but if you (or your electrician, or 
purchasing department) DO insist on UL-approved devices, you'll have a 
lower risk of shorts, shock, fire, etc.  I don't know for sure, but I 
ass-u-me UL would take a Very Dim View of manufacturers putting a 
UL-Approved label on devices that really weren't, and may have legal 
recourse through lawsuits asking for damages (especially punitive) that 
outweigh the faker's likely profit.

 > FWIW, my spam filter picks up Habeas headers as a strong ham
 > indicator, appearing in 0.4% of ham in my corpus

Their web site explains the name, but I just gotta wonder if they were 
punning on that as well....

-- 
David J. Aronson, Unemployed Software Engineer near Washington DC
See http://destined.to/program/ for online resume, and other info




From owner-ietf@ietf.org  Fri Jun  6 13:56:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04714
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 13:56:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OL5V-00060C-DE
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 13:33:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OKvf-0005Zz-QA
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 13:23:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03253
	for <ietf@ietf.org>; Fri, 6 Jun 2003 13:23:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OKtm-0004O5-00
	for ietf@ietf.org; Fri, 06 Jun 2003 13:21:06 -0400
Received: from protactinium.btinternet.com ([194.73.73.176])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OKtl-0004O2-00
	for ietf@ietf.org; Fri, 06 Jun 2003 13:21:05 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by protactinium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19OKva-0002ZK-00; Fri, 06 Jun 2003 18:22:58 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
Date: Fri, 6 Jun 2003 18:19:45 +0100
Message-ID: <000401c32c4f$d429e5e0$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D21E5@mou1wnexm02.verisign.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I think the real problem here is that folk are demanding something
that is
> impossible. They want a PKI that is entirely costless, failure free
and
>provides unlimited liability. If you set that as the standard for
existence
> of a global PKI then you are never going to see one.

Folks will pay a certain amount providing the certificate validity
period is not short time, for example issuing certificate that are valid
for 2 years instead 1 year or provide many different validity periods
for customers to choose from.

The issue is of implementation of the system.




From owner-ietf@ietf.org  Fri Jun  6 14:05:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05129
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 14:05:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OLUF-0007UK-KZ
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 13:58:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OLCf-0006gD-BS
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 13:40:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03927
	for <ietf@ietf.org>; Fri, 6 Jun 2003 13:40:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OLAl-0004YT-00
	for ietf@ietf.org; Fri, 06 Jun 2003 13:38:39 -0400
Received: from protactinium.btinternet.com ([194.73.73.176])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OLAl-0004YI-00
	for ietf@ietf.org; Fri, 06 Jun 2003 13:38:39 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by protactinium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19OLCa-0005Ca-00; Fri, 06 Jun 2003 18:40:33 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Pete Resnick'" <presnick@qualcomm.com>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
Date: Fri, 6 Jun 2003 18:37:20 +0100
Message-ID: <000501c32c52$49534440$0100010a@MyHomeLAN.local>
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.2616
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
In-Reply-To: <p06001403bb066bdc01ea@[216.43.25.67]>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pete wrote:
> No, but if Mary turns out to be someone who signs PGP keys for people 
> I don't like.

The job of the CA is NOT based on liking; it is one of authenticating
the subscriber and issuing a certificate.

The authentication of subscriber is defined by the CA's CPS.




From owner-ietf@ietf.org  Fri Jun  6 14:20:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05845
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 14:20:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OLUG-0007Yb-ME
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 13:58:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OLHL-0006wz-A5
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 13:45:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04250
	for <ietf@ietf.org>; Fri, 6 Jun 2003 13:45:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OLFR-0004en-00
	for ietf@ietf.org; Fri, 06 Jun 2003 13:43:29 -0400
Received: from champdsl-25-66.mcleodusa.net ([216.43.25.66] helo=episteme-software.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OLFQ-0004eg-00
	for ietf@ietf.org; Fri, 06 Jun 2003 13:43:29 -0400
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server X 3.2.2b1);
 Fri, 6 Jun 2003 12:44:43 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p06001404bb067f92a09e@[216.43.25.67]>
In-Reply-To: 
 <2A1D4C86842EE14CA9BC80474919782E0D21E8@mou1wnexm02.verisign.com>
References: 
 <2A1D4C86842EE14CA9BC80474919782E0D21E8@mou1wnexm02.verisign.com>
X-Mailer: Eudora [Macintosh version 6.0a15]
Date: Fri, 6 Jun 2003 12:44:50 -0500
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Pete Resnick <presnick@qualcomm.com>
Subject: RE: Certificate / CPS issues
Cc: "Hallam-Baker, Phillip"	 <pbaker@verisign.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

On 6/6/03 at 9:48 AM -0700, Phillip Hallam-Baker wrote:

>Signs keys for people you don't LIKE?

Well, I was referring to people who send spam, or aren't reputable 
business folk, or do any of a list of nasty things that I consider 
non-trustworthy. I should have put "don't like" in quotes.

>In your scenario what happens if you find out that Ted Tso or Jeff 
>Schiller has signed a bogus key. Do you then revoke every key they 
>ever issued on that account?

I might. It depends. If I think it was a fluke incident, I might not. 
But, if I thought that Ted and/or Jeff were repeatedly signing keys 
for disreputable folks, I might very well mark their keys as 
"untrusted" and not trust keys that were solely signed by them. Or 
(if we start talking about pie-in-the-sky kinds of things), I could 
imagine my e-mail filters saying, "Quarantine e-mail not signed by 
someone in this list of keys", and I might remove Ted and/or Jeff 
from that list of keys.

>Please remember here that we are trying to solve the spam problem here.

That's not what *I* was doing here. I was simply trying to point out 
that the liability model was different for a web of trust than for CA 
trust. Whether using either method is more or less applicable to 
solving the spam problem is not something I'm willing to discuss in 
this forum.
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102



From owner-ietf@ietf.org  Fri Jun  6 14:25:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03860
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 13:40:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OKvg-0005a5-1c
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 13:23:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OKjP-00051v-H1
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 13:10:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02664
	for <ietf@ietf.org>; Fri, 6 Jun 2003 13:10:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OKhY-0004EU-00
	for ietf@ietf.org; Fri, 06 Jun 2003 13:08:28 -0400
Received: from protactinium.btinternet.com ([194.73.73.176])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OKhW-0004EO-00
	for ietf@ietf.org; Fri, 06 Jun 2003 13:08:27 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by protactinium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19OKjH-0000k8-00; Fri, 06 Jun 2003 18:10:15 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
Date: Fri, 6 Jun 2003 18:07:03 +0100
Message-ID: <000301c32c4e$0d540ff0$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D21E5@mou1wnexm02.verisign.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>Do you think that folk signing PGP keys are undertaking unlimited
liability
>should the certification turn out to be incorrect?

The biggest difference between PGP and X.509, is that in PGP I can
choose the level of trust.

X.509 is based on doctorial model, where my browser is forced into
trusting the certificate from a server.




From owner-ietf@ietf.org  Fri Jun  6 14:31:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06421
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 14:31:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OLqo-0000CL-B3
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 14:22:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OLj1-00088a-9A
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 14:14:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05613
	for <ietf@ietf.org>; Fri, 6 Jun 2003 14:14:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OLh7-00053m-00
	for ietf@ietf.org; Fri, 06 Jun 2003 14:12:05 -0400
Received: from aragorn.bbn.com ([128.33.0.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OLh5-00052t-00
	for ietf@ietf.org; Fri, 06 Jun 2003 14:12:04 -0400
Received: from arsenaultd2 (dhcp33-244-172.bbn.com [128.33.244.172])
	by aragorn.bbn.com (8.12.7/8.12.7) with SMTP id h56ICwD8018567;
	Fri, 6 Jun 2003 14:12:58 -0400 (EDT)
Message-ID: <010801c32c57$29bf84e0$acf42180@arsenaultd2>
From: "Al Arsenault" <aarsenau@bbn.com>
To: "David Morris" <dwm@xpasc.com>
Cc: <ietf@ietf.org>
References: <Pine.LNX.4.33.0306060922440.26569-100000@egate.xpasc.com>
Subject: Re: Certificate / CPS issues
Date: Fri, 6 Jun 2003 14:12:16 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

While I'm in general a fan of PKI, and agree with some of what Phill has to
say, a number of things should be kept in mind:

1 - a number of popular applications have been designed to work a large
variety of "trusted root" certificates, by default.  For example, I just
popped up the list of "trusted root certificates" marked trusted by default
in IEv6.  I probably miscounted, but I got 106.  (YMMV, depending on
version, or if you use a different browser, or...) From a whole bunch of
different sources.

2 - a number of the entities behind those trusted roots go out of business,
or become somebody else, or...  A quick quiz, based on the root certs from
IEv6 (yes, I know the answer to these questions, but I've been working in
the PKI area for over 15 years - how about most people):

    - who owns the private keys associated with those 3 "GTE Cyber Trust"
root certificates?
    - what is that company doing that will conclude by June 30?
    - what about the private keys associated with those four "Equifax
Secure" root certificates?
    -  there are at least 10 trusted root certificates marked signed by
"DST".  What happened to DST?
    - there are six certificates marked as being from "Thawte".  Who's
"Thawte"?
    - what about Xcert?

3 - most users will never know enough to delete roots as no longer being
trusted (or do what some of us do, and delete them all at system install
time; then reinstall just the ones needed, on a need-to-exist basis).  Since
any cert that chains to any one of those roots will succeed silently in the
default configurations of many popular applications, who will know?

The point of this is that if you're going to use a PKI-based approach to
combatting SPAM, you have to look at the whole problem, as it exists today.
All it takes in the "real world" is a spammer (or friend of such) acquiring
the private key associated with any trusted root cert in popular
applications, and there you go - SPAM passes your tests/filters until you
figure out how to remove the cert from the list of trusted ones.  Not
something that my mother will easily know how to do.

        Al Arsenault



----- Original Message -----
From: "David Morris" <dwm@xpasc.com>
Cc: <ietf@ietf.org>
Sent: Friday, June 06, 2003 1:01 PM
Subject: RE: Certificate / CPS issues


>
>
> On Fri, 6 Jun 2003, Hallam-Baker, Phillip wrote:
>
> >
> > Security is risk control, not risk elimination.
>
> Absolutely!
>
> Extending that thought, managing risk is about the cost of loss vs. the
> cost of protection.
>
> Humans make mistakes. Systems fail. Sammy Sousa used the wrong bat. The
> suttles failed. To reject a service because you have one presumed example
> of failure is not realistic. A pattern of failures would be an issue, just
> like you might avoid purchase of an automobile if Consumer Reports failure
> statistics are abnormally high.
>
> For the objectives we are discussing, I think the failure rate at Verisign
> is not an issue. Most (perhaps all) folks in this discussion seem to agree
> that the issue with spam is in the volume and not the mere existance of
> spam. Social scientists could probably study the parallel growth of spam
> and the corresponding growth in frustration and even end up with a volume
> of spam which most people would be comfortable with. I strongly suspect
> that reducing and keeping spam at 10% of current levels would probably be
> success. Certainly, 1% would be.
>
> On that premis, I'm certain it doesn't matter if 1 of the current 200
> heavy duty spammers gets a fraudulant certificate. That might make final
> identification more difficult, but most of the other mechanisms will still
> function.
>
> 1. Proof of common source of the quantity of emails needed to be
>    ruled as illegal
> 2. Source based filtering can still block mail identified with the
>    cert
> 3. Once the fraud is discovered, the CA is likely to have process
>    in place to avoid issuing new certs to the same entity
>
> The last time I investigated, Verisign had certificates of different types
> with different prices and levels of identification verification. Even the
> cheapest have some cost and since I doubt that Verisign accepts cash
> payment, there is identity associated with the payment. Worst case is a
> stolen credit card is used to make payment. Since that is an immediate
> felony, it may actually be the best case from anti-spam perspective.
> Because of this cost (and the difficulty of obtaining and risk of using a
> large number of stolen credit cards), it seems less likely that spammers
> will follow the scenario of obtaining a large number of throw away
> certificates.
>
> Conclusion, I don't see the less than 100% trustworthiness of any CA to be
> an impediment to the use of certificates as part of an email origin
> identification scheme. Only a fool would accept a self-signed certificate
> as having any significance so I think the suggestion that the ability of a
> spammer to generate their own storm of certificates has little merit.
>
> Dave Morris
>




From owner-ietf@ietf.org  Fri Jun  6 14:48:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06959
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 14:48:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OLqo-0000Cy-MO
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 14:22:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OLkv-000890-Hx
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 14:16:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05715
	for <ietf@ietf.org>; Fri, 6 Jun 2003 14:15:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OLj1-00055C-00
	for ietf@ietf.org; Fri, 06 Jun 2003 14:14:03 -0400
Received: from tungsten.btinternet.com ([194.73.73.81])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OLj0-00054w-00
	for ietf@ietf.org; Fri, 06 Jun 2003 14:14:03 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by tungsten.btinternet.com with esmtp (Exim 3.22 #23)
	id 19OLkV-0002P7-00; Fri, 06 Jun 2003 19:15:35 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'David Morris'" <dwm@xpasc.com>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
Date: Fri, 6 Jun 2003 19:12:24 +0100
Message-ID: <000601c32c57$2e344420$0100010a@MyHomeLAN.local>
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.2616
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
In-Reply-To: <Pine.LNX.4.33.0306060922440.26569-100000@egate.xpasc.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave wrote:
> Only a fool would accept a self-signed certificate

CA certificate is self-signed.

Are you suggesting CA should cross sign each others certificates?




From owner-ietf@ietf.org  Fri Jun  6 16:05:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10497
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 16:05:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ON81-0001Iy-EV
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 15:43:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ON0Y-00018S-Dq
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 15:36:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09586
	for <ietf@ietf.org>; Fri, 6 Jun 2003 15:36:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OMye-0005hi-00
	for ietf@ietf.org; Fri, 06 Jun 2003 15:34:16 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OMyd-0005hf-00
	for ietf@ietf.org; Fri, 06 Jun 2003 15:34:15 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h56JSMS09405;
	Fri, 6 Jun 2003 12:28:22 -0700
Date: Fri, 6 Jun 2003 12:28:22 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: Haren Visavadia <haren@btopenworld.com>
cc: <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
In-Reply-To: <000601c32c57$2e344420$0100010a@MyHomeLAN.local>
Message-ID: <Pine.LNX.4.33.0306061215590.26569-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Fri, 6 Jun 2003, Haren Visavadia wrote:

> Dave wrote:
> > Only a fool would accept a self-signed certificate
>
> CA certificate is self-signed.
>
> Are you suggesting CA should cross sign each others certificates?
>

If a root certificate is installed by a process you choose to trust, it is
not self signed. Self signed in my experience refers to the ability
frequently used internally for QA labs where there is no accepted root
server. Even if the root cert, installed by my explicit or implicit
approval, is used to sign another cert from the same organization, that
second cert isn't self-signed.

FWIW, for UBM suppression, I'm not concerned about my grand parents
understanding trust models. Meaningful trust boundaries must begin with
the MTA. The MTA owns the trust issue between itself and individual MUAs.

As Phill implied, the cost of security must be less than the value of the
protected entity. If major operators of MTAs discover that a particular CA
root private key is compromised. Addressing the problem quicky should be
easy, if the possiblity was anticipated. Will that protect every user, no,
but costs here are based on the scale of the activity, not individual
occurances (as is any value received from sending the UBE) so getting
rapid response from 20-100 MTA operators is likely to be effective.

Dave Morris




From owner-ietf@ietf.org  Fri Jun  6 16:05:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10496
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 16:05:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ON81-0001JQ-Pe
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 15:43:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ON4n-0001B6-1G
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 15:40:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09728
	for <ietf@ietf.org>; Fri, 6 Jun 2003 15:40:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ON2t-0005jT-00
	for ietf@ietf.org; Fri, 06 Jun 2003 15:38:39 -0400
Received: from vrx.net ([216.13.126.22] helo=ns1.vrx.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ON2s-0005jN-00
	for ietf@ietf.org; Fri, 06 Jun 2003 15:38:38 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-128-181.lsanca1.dsl-verizon.net [4.33.128.181])
	by ns1.vrx.net (Postfix) with ESMTP
	id 71767D400; Fri,  6 Jun 2003 15:40:29 -0400 (EDT)
Mime-Version: 1.0
X-Sender: steflist@vrx.net
Message-Id: <v04220827bb069cc01bd5@[192.168.1.14]>
In-Reply-To: <5.1.0.14.2.20030606113951.02d931c8@127.0.0.1>
References: <5.1.0.14.2.20030606113951.02d931c8@127.0.0.1>
Date: Fri, 6 Jun 2003 12:40:18 -0700
To: Graham Klyne <GK@ninebynine.org>
From: Einar Stefferud <Steflist@thor.nma.com>
Subject: Re: Certificate / CPS issues
Cc: "Hallam-Baker, Phillip" <pbaker@verisign.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

OK, so what happens when someone else uses my address, perhaps using 
my passport, captured from some mail sent by me to someone? 

I think the term of art is "being Joe Jobbed".

Every now and then,  I get a bounced report that claims something I sent 
is being returned, but it was not sent by me.  This "something" is most 
often spam sent to someone else.  Sometimes it contains a virus.
Apparently this  is a trick to get me to open it.

Anyway, I think your Passport Scheme needs some more work.

Cheers...\Stef

At 11:50 +0100 6/6/03, Graham Klyne wrote:
>At 12:12 05/06/03 -0700, Hallam-Baker, Phillip wrote:
>>A spam sender could attempt to use disposable certificates in the same way
>>that IP addresses and dialup accounts are considered disposable. This is
>>unlikely to work for long, the spam sender can set up lots of shell
>>companies at the same address but if the CA keeps authenticating to the same
>>address or phone number the pattern will soon become apparent.
>
>Hmmm... is there an economic play here?
>
><background>
>First, briefly, my view of the spam situation.  I don't think it's fundamentally an Internet protocol design issue (though some design tweaks may help).  Essentially, I think people currently have the choice of
>(1) putting filters in place and accept the loss of some non-spam mail, or
>(2) accepting a deluge of spam, and not lose any mail.  In practice, I think this option doesn't exist, because I find that (lacking spam filters) I do lose a few pieces of non-spam mail because I don't recognize the sender or subject.  So I see a way forward to be a "passport" mechanism to reliably bypass automated spam filters, a kind of whitelist++.
></background>
>
>So back to my question: is there an economic play here?
>
>(I was offered the opinion once that a big *disadvantage* of email compared with fax for business transactions was that it has almost zero incremental cost of use.)
>
>I'm thinking of a cert issued for a small sum of money, without any authentication other than the purchaser promises something like "I promise not to spam with this certificate".  At the earliest evidence of it being used for spamming, it is revoked.  The price should be small enough to be accessible to any reasonable person, but high enough that the bill for daily or hourly renewal would become significant.
>
>Maybe crazy, just thinking aloud...
>
>#g
>
>
>-------------------
>Graham Klyne
><GK@NineByNine.org>
>PGP: 0FAA 69FF C083 000B A2E9  A131 01B9 1C7A DBCA CB5E




From owner-ietf@ietf.org  Fri Jun  6 16:17:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11019
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 16:17:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ONRQ-0001VZ-CY
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 16:04:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ONGW-0001NA-Cf
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 15:52:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10096
	for <ietf@ietf.org>; Fri, 6 Jun 2003 15:52:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONEc-0005qe-00
	for ietf@ietf.org; Fri, 06 Jun 2003 15:50:46 -0400
Received: from carbon.btinternet.com ([194.73.73.92])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ONEb-0005qb-00
	for ietf@ietf.org; Fri, 06 Jun 2003 15:50:46 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by carbon.btinternet.com with esmtp (Exim 3.22 #23)
	id 19ONGJ-0007G8-00; Fri, 06 Jun 2003 20:52:31 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'David Morris'" <dwm@xpasc.com>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
Date: Fri, 6 Jun 2003 20:49:20 +0100
Message-ID: <000a01c32c64$b903eda0$0100010a@MyHomeLAN.local>
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.2616
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
In-Reply-To: <Pine.LNX.4.33.0306061215590.26569-100000@egate.xpasc.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The trust chain will include the root cert, which is self-signed.

This means you would have to somehow trust the root cert. And that might
be difficult:

> Only a fool would accept a self-signed certificate




From owner-ietf@ietf.org  Fri Jun  6 16:45:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11853
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 16:45:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ONy5-00033D-Rp
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 16:37:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OM6H-0000kB-Qu
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 14:38:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06715
	for <ietf@ietf.org>; Fri, 6 Jun 2003 14:38:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OM4O-0005Io-00
	for ietf@ietf.org; Fri, 06 Jun 2003 14:36:08 -0400
Received: from tungsten.btinternet.com ([194.73.73.81])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OM4N-0005Il-00
	for ietf@ietf.org; Fri, 06 Jun 2003 14:36:07 -0400
Received: from host217-44-79-155.range217-44.btcentralplus.com ([217.44.79.155] helo=helios)
	by tungsten.btinternet.com with esmtp (Exim 3.22 #23)
	id 19OM5w-0006ce-00; Fri, 06 Jun 2003 19:37:44 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Al Arsenault'" <aarsenau@bbn.com>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
Date: Fri, 6 Jun 2003 19:34:33 +0100
Message-ID: <000701c32c5a$4642d650$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
In-Reply-To: <010801c32c57$29bf84e0$acf42180@arsenaultd2>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Al Arsenault:
> SPAM passes your tests/filters until you
> figure out how to remove the cert from the list of trusted ones. 

A filter could be set to filter out all e-mail containing a certain
certificate, regardless of the trust chain.






From owner-ietf@ietf.org  Fri Jun  6 17:36:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14337
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 17:36:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OOi8-00049v-G0
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 17:25:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OOYr-000443-1O
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 17:15:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13301
	for <ietf@ietf.org>; Fri, 6 Jun 2003 17:15:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OOWy-0006d0-00
	for ietf@ietf.org; Fri, 06 Jun 2003 17:13:48 -0400
Received: from jay.songbird.com ([208.184.79.253])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OOWx-0006cx-00
	for ietf@ietf.org; Fri, 06 Jun 2003 17:13:47 -0400
Received: from Rincewind.ninebynine.org (jay.songbird.com [208.184.79.253])
	(authenticated)
	by jay.songbird.com (8.11.6/8.11.3) with ESMTP id h56LFM011009;
	Fri, 6 Jun 2003 14:15:23 -0700
Message-Id: <5.1.0.14.2.20030606215531.0305aec0@127.0.0.1>
X-Sender: gk@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 06 Jun 2003 22:02:34 +0100
To: Einar Stefferud <Steflist@thor.nma.com>
From: Graham Klyne <gk@ninebynine.org>
Subject: Re: Certificate / CPS issues
Cc: "Hallam-Baker, Phillip" <pbaker@verisign.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
In-Reply-To: <v04220827bb069cc01bd5@[192.168.1.14]>
References: <5.1.0.14.2.20030606113951.02d931c8@127.0.0.1>
 <5.1.0.14.2.20030606113951.02d931c8@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:40 06/06/03 -0700, Einar Stefferud wrote:
>OK, so what happens when someone else uses my address, perhaps using
>my passport, captured from some mail sent by me to someone?
>
>I think the term of art is "being Joe Jobbed".
>
>Every now and then,  I get a bounced report that claims something I sent
>is being returned, but it was not sent by me.  This "something" is most
>often spam sent to someone else.  Sometimes it contains a virus.
>Apparently this  is a trick to get me to open it.

I see a couple of differences:  re-using someone's email address is easy 
... I've had a flurry of 'bounces' recently for messages I certainly did 
not send.  But the information to send those (deceitful) messages is very 
easily obtained.

By putting some of the information behind a cryptrographic screen, it 
becomes harder for others to casually use it.

And if security is compromised, then the cert gets revoked and the genuine 
owner has to buy another one.  Hey, don't we occasionally lose theatre 
tickets?  Tough, but not disastrous -- we just have to buy another one.

>Anyway, I think your Passport Scheme needs some more work.

I'm sure it does!

#g
--

>At 11:50 +0100 6/6/03, Graham Klyne wrote:
> >At 12:12 05/06/03 -0700, Hallam-Baker, Phillip wrote:
> >>A spam sender could attempt to use disposable certificates in the same way
> >>that IP addresses and dialup accounts are considered disposable. This is
> >>unlikely to work for long, the spam sender can set up lots of shell
> >>companies at the same address but if the CA keeps authenticating to the 
> same
> >>address or phone number the pattern will soon become apparent.
> >
> >Hmmm... is there an economic play here?
> >
> ><background>
> >First, briefly, my view of the spam situation.  I don't think it's 
> fundamentally an Internet protocol design issue (though some design 
> tweaks may help).  Essentially, I think people currently have the choice of
> >(1) putting filters in place and accept the loss of some non-spam mail, or
> >(2) accepting a deluge of spam, and not lose any mail.  In practice, I 
> think this option doesn't exist, because I find that (lacking spam 
> filters) I do lose a few pieces of non-spam mail because I don't 
> recognize the sender or subject.  So I see a way forward to be a 
> "passport" mechanism to reliably bypass automated spam filters, a kind of 
> whitelist++.
> ></background>
> >
> >So back to my question: is there an economic play here?
> >
> >(I was offered the opinion once that a big *disadvantage* of email 
> compared with fax for business transactions was that it has almost zero 
> incremental cost of use.)
> >
> >I'm thinking of a cert issued for a small sum of money, without any 
> authentication other than the purchaser promises something like "I 
> promise not to spam with this certificate".  At the earliest evidence of 
> it being used for spamming, it is revoked.  The price should be small 
> enough to be accessible to any reasonable person, but high enough that 
> the bill for daily or hourly renewal would become significant.
> >
> >Maybe crazy, just thinking aloud...
> >
> >#g
> >
> >
> >-------------------
> >Graham Klyne
> ><GK@NineByNine.org>
> >PGP: 0FAA 69FF C083 000B A2E9  A131 01B9 1C7A DBCA CB5E

-------------------
Graham Klyne
<GK@NineByNine.org>
PGP: 0FAA 69FF C083 000B A2E9  A131 01B9 1C7A DBCA CB5E




From owner-ietf@ietf.org  Fri Jun  6 19:19:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18105
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 19:19:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OQ44-00038j-Bd
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 18:52:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OPxs-00036L-BH
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 18:45:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17447
	for <ietf@ietf.org>; Fri, 6 Jun 2003 18:45:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPvz-0007G9-00
	for ietf@ietf.org; Fri, 06 Jun 2003 18:43:43 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OPvy-0007G6-00
	for ietf@ietf.org; Fri, 06 Jun 2003 18:43:42 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h56Mjbe0039880
	for <ietf@ietf.org>; Sat, 7 Jun 2003 00:45:37 +0200 (CEST)
Message-ID: <00f301c32c7d$5954ce10$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <138AA78F80DCE84B8EE424399FFBF9C91B071B@exchange.ad.skymv.com>
Subject: Re: Certificate / CPS issues
Date: Sat, 7 Jun 2003 00:45:37 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dan writes:

> Regarding a "passport" mechanism, have you
> taken a look at www.habeas.com?

Habeas represents one of the most egregious perversions of trademark and
copyright law that I've ever encountered.  Their copyright and trademark
claims are invalid prima facie, and they hope to get their way by
intimidation and distortion of the law to their ends.  I cannot condone
this, as it dramatically erodes the foundations of intellectual property
law.

Copyright law was intended to protect real, creative, original, non-trivial
works of the mind for the benefit of their creators--and not as a
techno-gadget to prevent spam.  Trademark law was intended to protect the
commercial value and goodwill of creative, real, original, non-trivial
identifying marks for specific products and services--and not as a
techno-gadget to prevent spam.

I've love to see Habeas lose a couple of lawsuits.  They are setting a very
unhealthy precedent.

> Specifically, they offer such a "this is not spam"
> warrant mark, and the pricing for individuals is
> free.

If I see that warrant mark on my incoming mail, I'll bounce it.

> The trick is that they use copyright and trademark law
> as the enforcement mechanism.

That's just it:  it's a trick, and a glaring abuse of intellectual property
law.

Incidentally, the name of my domain is a service mark, and so any e-mail
coming to me from Habeas is an infringement on my service mark, since it
will contain the name of my domain.  You can't argue with this, since it is
no less stupid than the premise conjured up by Habeas.




From owner-ietf@ietf.org  Fri Jun  6 23:05:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22493
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 23:05:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OTmX-00074G-5B
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 22:50:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OTf9-00070t-9p
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 22:42:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22069
	for <ietf@ietf.org>; Fri, 6 Jun 2003 22:42:32 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OTdF-0000jU-00
	for ietf@ietf.org; Fri, 06 Jun 2003 22:40:37 -0400
Received: from h80ad26cb.async.vt.edu ([128.173.38.203] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OTdD-0000jR-00
	for ietf@ietf.org; Fri, 06 Jun 2003 22:40:36 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h572gTnQ010924
	for <ietf@ietf.org>; Fri, 6 Jun 2003 22:42:29 -0400
Message-Id: <200306070242.h572gTnQ010924@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Certificate / CPS issues 
In-Reply-To: Your message of "Sat, 07 Jun 2003 00:45:37 +0200."
             <00f301c32c7d$5954ce10$0a00000a@atkielski.com> 
References: <138AA78F80DCE84B8EE424399FFBF9C91B071B@exchange.ad.skymv.com>
            <00f301c32c7d$5954ce10$0a00000a@atkielski.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1686267487P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 06 Jun 2003 22:42:29 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sat, 07 Jun 2003 00:45:37 +0200, Anthony Atkielski <anthony@atkielski.com>  said:

> Incidentally, the name of my domain is a service mark, and so any e-mail
> coming to me from Habeas is an infringement on my service mark, since it
> will contain the name of my domain.  You can't argue with this, since it is
> no less stupid than the premise conjured up by Habeas.

I hereby request the list management to remove Anthony's email address from
the subscriber list, so as to not expose the IETF to liability.  Hmm.. maybe
that's not the right attitude, Anthony. ;)

It's pretty clear that there's a fair-use exemption if you actually want to
USE that domain name for anything.

> Copyright law was intended to protect real, creative, original, non-trivial
> works of the mind for the benefit of their creators--and not as a

Given that the song "Happy Birthday" was/is copyrighted ( don't know when it
expires, especially after the whole Sonny Bono thing), I'd say that any haiku
that the Habeas crew comes up with qualifies.  And although you may find the
creative use of the law distasteful, to state that their claims are 'invalid
prima facie', you need to be able to show that they are in fact invalid.
Let's see... are the haiku original?  Do they meet the Bern Convention
requirements for copyrightability? Note that "total doggerel" is NOT a factor,
as Sturgeon's Law would put 90% of everything in the public domain then.

Note that major companies have had *no* trouble enforcing copyright/trademark
on slogans as short as "it's the real thing" or "you deserve a break today".
It may not be what the founding fathers had in mind in 1790, and it may not
match what you *wish* it was, but it's how the *current* laws are held to read
as of today.  Barring a major judicial reversal (such as was attempted in
Eldred), we're all stuck with the current laws as currently interpreted.

IANAL, but it looks to me like the Habeas crew is on fairly strong legal
footing.  Also, they're not trying to stop spam directly.  They're providing
two services:  (a) a header tag that you can use to filter your inbound
mail for *NON*-spam, and (b) the chance for any spammers to spend enough
money on legal fees to render it unprofitable.

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

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

iD8DBQE+4VEVcC3lWbTT17ARAvUKAJ9oATNBXtEHXcC1opGeIXf0CQwrbACfXz/M
kalbjteWf23fU/D7e+E5HgY=
=4I2s
-----END PGP SIGNATURE-----

--==_Exmh_1686267487P--



From owner-ietf@ietf.org  Fri Jun  6 23:48:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23202
	for <ietf-web-archive@odin.ietf.org>; Fri, 6 Jun 2003 23:48:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OUXg-0007rE-M0
	for ietf-list@asgard.ietf.org; Fri, 06 Jun 2003 23:38:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OUV1-0007oz-Er
	for ietf@asgard.ietf.org; Fri, 06 Jun 2003 23:36:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23056
	for <ietf@ietf.org>; Fri, 6 Jun 2003 23:36:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OUT7-000103-00
	for ietf@ietf.org; Fri, 06 Jun 2003 23:34:13 -0400
Received: from krusty-motorsports.com ([192.94.170.8] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OUT7-000100-00
	for ietf@ietf.org; Fri, 06 Jun 2003 23:34:13 -0400
Received: from [24.194.112.77] (helo=skipper.averillpark.net)
	by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.14)
	id 19OUUz-00005Z-6F
	for ietf@ietf.org; Sat, 07 Jun 2003 03:36:09 +0000
Received: from rwelty by skipper.averillpark.net with local (Exim 4.14)
	id 19OUUc-0000Wc-W4
	for ietf@ietf.org; Fri, 06 Jun 2003 23:35:46 -0400
Date: Fri, 6 Jun 2003 23:35:46 -0400 (EDT)
From: Richard Welty <rwelty@averillpark.net>
Subject: Re[2]: Certificate / CPS issues 
To: IETF Discussion <ietf@ietf.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE
References: <138AA78F80DCE84B8EE424399FFBF9C91B071B@exchange.ad.skymv.com>
            <00f301c32c7d$5954ce10$0a00000a@atkielski.com>
 <200306070242.h572gTnQ010924@turing-police.cc.vt.edu>
In-Reply-To: <200306070242.h572gTnQ010924@turing-police.cc.vt.edu>
X-Mailer: Mahogany 0.64 'Sparc', compiled for Linux 2.4.9-13 i686
Message-Id: <E19OUUc-0000Wc-W4@skipper.averillpark.net>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 06 Jun 2003 22:42:29 -0400 Valdis.Kletnieks@vt.edu wrote:
> IANAL, but it looks to me like the Habeas crew is on fairly strong legal
> footing. 

i might add that the CEO of Habeas, Anne Mitchell, is an actual lawyer. i
am not familiar with Anthony's credentials in the field of law. casually
throwing legal terms about does not impress.

this email happens to have Habeas headers, so i presume that he will not
see it if he is throwing such mail out the way he says he will.

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





From owner-ietf@ietf.org  Sat Jun  7 00:56:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24190
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 00:56:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OVYW-0000Hf-Sp
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 00:43:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OVUS-0000FK-BI
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 00:39:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24055
	for <ietf@ietf.org>; Sat, 7 Jun 2003 00:39:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OVSY-0001Er-00
	for ietf@ietf.org; Sat, 07 Jun 2003 00:37:43 -0400
Received: from spitfire.law.miami.edu ([129.171.187.10] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OVSY-0001Eo-00
	for ietf@ietf.org; Sat, 07 Jun 2003 00:37:42 -0400
Received: from spitfire.law.miami.edu (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id 55ED55C3ADF; Sat,  7 Jun 2003 00:39:38 -0400 (EDT)
Received: by spitfire.law.miami.edu (Postfix, from userid 1113)
	id D2E7F5C3ADF; Sat,  7 Jun 2003 00:39:37 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id BDC505D3AEE; Sat,  7 Jun 2003 00:39:37 -0400 (EDT)
Date: Sat, 7 Jun 2003 00:39:37 -0400 (EDT)
From: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
To: Valdis.Kletnieks@vt.edu
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Certificate / CPS issues 
In-Reply-To: <200306070242.h572gTnQ010924@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.10.10306070031430.3350-100000@spitfire.law.miami.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

You cannot get trademark protection for anything "functional".  To the
extent that the Habeus magic words are used functionally, I do not think
they are eligible for trademark protection.

Ditto copyright: "Works that may not be protectable by copyright include:
.... short phrases and slogans, familiar symbols or designs, and other
works lacking sufficient creativity or independent effort; designs of
useful articles or products where the designs are not conceptually
separable from the functional aspects of the article or product; works
consisting only of information that is in the public domain; and blank
forms and other works which are designed for recording information and
which do not in themselves convey information." 

(source: American Law Institute - American Bar Association Continuing
Legal Education April 10-11, 2003 Trademarks, Copyrights, and Unfair
Competition for the General Practitioner and the Corporate Counsel COURSE
OVERVIEW Ronald L. Panitch SH085 ALI-ABA 361)

Functional things are eligible to be patented.

Thus, I have grave doubts as to the strength of this footing under IP law.
There might be alternate legal theories that would work a little
better....

I could go into considerably greater detail as to why, and also as to what
the counter-argument might look like, but I'd have to charge you...

On Fri, 6 Jun 2003 Valdis.Kletnieks@vt.edu wrote:

[...]

> IANAL, but it looks to me like the Habeas crew is on fairly strong legal
> footing.  Also, they're not trying to stop spam directly.  They're providing
> two services:  (a) a header tag that you can use to filter your inbound
> mail for *NON*-spam, and (b) the chance for any spammers to spend enough
> money on legal fees to render it unprofitable.
> 

-- 
		Please visit http://www.icannwatch.org
A. Michael Froomkin   |    Professor of Law    |   froomkin@law.tm
U. Miami School of Law, P.O. Box 248087, Coral Gables, FL 33124 USA
+1 (305) 284-4285  |  +1 (305) 284-6506 (fax)  |  http://www.law.tm
                        -->It's hot here.<--




From owner-ietf@ietf.org  Sat Jun  7 01:11:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24496
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 01:11:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OVq5-0000jo-Q6
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 01:02:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OVjm-0000M7-Ev
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 00:55:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24177
	for <ietf@ietf.org>; Sat, 7 Jun 2003 00:55:27 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OVht-0001Hh-00
	for ietf@ietf.org; Sat, 07 Jun 2003 00:53:33 -0400
Received: from h80ad26cb.async.vt.edu ([128.173.38.203] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OVhr-0001He-00
	for ietf@ietf.org; Sat, 07 Jun 2003 00:53:32 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h574tQnQ012307;
	Sat, 7 Jun 2003 00:55:26 -0400
Message-Id: <200306070455.h574tQnQ012307@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Certificate / CPS issues 
In-Reply-To: Your message of "Sat, 07 Jun 2003 00:39:37 EDT."
             <Pine.LNX.4.10.10306070031430.3350-100000@spitfire.law.miami.edu> 
References: <Pine.LNX.4.10.10306070031430.3350-100000@spitfire.law.miami.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1318780113P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sat, 07 Jun 2003 00:55:25 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sat, 07 Jun 2003 00:39:37 EDT, "Michael Froomkin - U.Miami School of Law" said:
> You cannot get trademark protection for anything "functional".  To the
> extent that the Habeus magic words are used functionally, I do not think
> they are eligible for trademark protection.

I stand corrected.  :)

> Thus, I have grave doubts as to the strength of this footing under IP law.
> There might be alternate legal theories that would work a little
> better....

Of course, it's quite possible that Habeas's legal theory *is* a complete
load of dingo's kidneys - the biggest question is which spammer (if any)
is willing to risk the lawsuit to find out.  The same thing is going on
currently over on the patent law side of the fence - companies will just
fold and pay the licensing fees rather than fight an obviously bogus patent.

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

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

iD8DBQE+4XA9cC3lWbTT17ARAgteAJwJZH+bLfso4rtBh+P18T/g33+51wCggWGB
68Jr4E+JW64IrXFLJEPxWiA=
=Sil7
-----END PGP SIGNATURE-----

--==_Exmh_-1318780113P--



From owner-ietf@ietf.org  Sat Jun  7 03:47:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08085
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 03:47:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OYD1-0000Cx-Jz
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 03:33:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OYCz-0000AN-9a
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 03:33:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07917
	for <ietf@ietf.org>; Sat, 7 Jun 2003 03:33:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OYB5-0002Ao-00
	for ietf@ietf.org; Sat, 07 Jun 2003 03:31:51 -0400
Received: from zinc.btinternet.com ([194.73.73.148] helo=zinc)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OYB5-0002Al-00
	for ietf@ietf.org; Sat, 07 Jun 2003 03:31:51 -0400
Received: from host217-44-97-247.range217-44.btcentralplus.com ([217.44.97.247] helo=helios)
	by zinc with esmtp (Exim 3.22 #23)
	id 19OYCv-0000Ow-00; Sat, 07 Jun 2003 08:33:45 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Einar Stefferud'" <Steflist@thor.nma.com>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
Date: Sat, 7 Jun 2003 08:30:34 +0100
Message-ID: <001901c32cc6$af08eb90$0100010a@MyHomeLAN.local>
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.2616
In-Reply-To: <v04220827bb069cc01bd5@[192.168.1.14]>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>OK, so what happens when someone else uses my address, perhaps using 
> my passport, captured from some mail sent by me to someone? 

> I think the term of art is "being Joe Jobbed".

> Every now and then,  I get a bounced report that claims something I
sent 
> is being returned, but it was not sent by me.  This "something" is
most 
>often spam sent to someone else.  Sometimes it contains a virus.
> Apparently this  is a trick to get me to open it.

The CA holds no warranty, making the certificate invalid in legal terms,
since they can not prove the certificate is yours.




From owner-ietf@ietf.org  Sat Jun  7 07:06:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10711
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 07:06:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ObFi-0002Jj-43
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 06:48:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ObEp-0002Hz-Uq
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 06:47:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10542
	for <ietf@ietf.org>; Sat, 7 Jun 2003 06:47:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ObCw-0002xN-00
	for ietf@ietf.org; Sat, 07 Jun 2003 06:45:58 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ObCv-0002xK-00
	for ietf@ietf.org; Sat, 07 Jun 2003 06:45:57 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h57Alqe0048315
	for <ietf@ietf.org>; Sat, 7 Jun 2003 12:47:52 +0200 (CEST)
Message-ID: <016d01c32ce2$3f1d6d30$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <138AA78F80DCE84B8EE424399FFBF9C91B071B@exchange.ad.skymv.com>            <00f301c32c7d$5954ce10$0a00000a@atkielski.com> <200306070242.h572gTnQ010924@turing-police.cc.vt.edu>
Subject: Re: Certificate / CPS issues 
Date: Sat, 7 Jun 2003 12:47:52 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I hereby request the list management to remove
> Anthony's email address from the subscriber list,
> so as to not expose the IETF to liability.

Too late ... my incredibly valuable service mark has already been
distributed to the list many times in the headers of my messages.  Clearly
this dilutes the well-nigh awe-inspiring value of the mark and impacts the
staggering commercial value of my business.

> Hmm.. maybe that's not the right attitude, Anthony.

I agree.  But that's exactly what Habeas is trying to do.

> It's pretty clear that there's a fair-use exemption
> if you actually want to USE that domain name for anything.

Fair use doesn't apply to trademarks and service marks.

> Given that the song "Happy Birthday" was/is
> copyrighted ( don't know when it expires, especially
> after the whole Sonny Bono thing), I'd say that any haiku
> that the Habeas crew comes up with qualifies.

Not necessarily.  The Habeas haiku comes closer to a business form or
boilerplate text in a contract, which is not necessarily protected by
copyright.  Additionally, it's not clear that the appearance of the haiku in
(normally invisible) message headers is an infringement, even if it is
covered by copyright.

Overally, there are just too many questions in this case, and the intent to
pervert copyright law is patent.  It's difficult to quarrel with the
copyrightable nature of "Happy Birthday" and the infringing nature of
unauthorized performances; but it is easy to quarrel with Habeas' bizarre
distortion of IP law, and hopefully it would not hold up in court, as it
sets a bad precedent and would significantly chill freedom of speech if it
were upheld.

> And although you may find the creative use of the law
> distasteful, to state that their claims are 'invalid
> prima facie', you need to be able to show that they
> are in fact invalid.

The haiku in question is trivial, like the title of a book.  Additionally,
it is not published in the normal course of e-mail routing.  Users do not
see it, and simple transmission of the work is not necessarily infringement
(after all, the transmission of Web pages to your PC is not infringement,
either, and even caching of pages seems to be okay).  Just about every
principle of and behind copyright protection is being ignored by Habeas.

Odd that Habeas considers this okay, but if spammers went to the same
lengths to distort the law to their own ends, people would form lynch mobs.
I guess the law is great when it protects you, but bad when it protects
someone else, eh?

> Let's see... are the haiku original?  Do they
> meet the Bern Convention requirements for
> copyrightability?

Each message posted to this list is more subject to copyright than Habeas'
haiku.  In fact, the error messages I sent to domains that I reject in
sendmail are more validly protected by copyright than this haiku, and
domains that receive the messages and communicate them to end users are
infringing my copyright.  If that sounds absurd, keep in mind that it is no
more absurd than the ideas promoted by Habeas.

> Note that major companies have had *no* trouble
> enforcing copyright/trademark on slogans as short
> as "it's the real thing" or "you deserve a break today".

Actually, they do.  First of all, short phrases like this are not protected
by copyright; copyrighted works must be non-trivial.  And as trademarks,
they are protected only in narrow contexts (those that might lead to
confusion in the minds of consumers, or those that might dilute the value of
the marks for their proprietors).

> It may not be what the founding fathers had in
> mind in 1790, and it may not match what you *wish*
> it was, but it's how the *current* laws are held to read
> as of today.

No, they aren't.  See above.  Think about Xerox, Coke, and Aspirin, for
example.

> Barring a major judicial reversal (such as was
> attempted in Eldred), we're all stuck with the
> current laws as currently interpreted.

Habeas has not been tested, and there are no highly relevant guiding
precedents (I think).

> IANAL, but it looks to me like the Habeas crew is
> on fairly strong legal footing.

On the contrary, they appear to be treading on extremely thin ice.  But only
a legal test will say for sure.

> Also, they're not trying to stop spam directly.  They're
> providing two services:  (a) a header tag that you can use
> to filter your inbound mail for *NON*-spam, and (b) the
> chance for any spammers to spend enough money on legal
> fees to render it unprofitable.

And what if I consider unnecessary headers in my incoming e-mail as spam?
Then what?  Can I sue or prosecute Habeas?  If not, why not?  After all,
that application of law would be no less farfetched than Habeas' own
attempted application of IP law.




From owner-ietf@ietf.org  Sat Jun  7 07:09:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10859
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 07:09:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ObQJ-0002NZ-2H
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 06:59:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ObH0-0002Jo-Lx
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 06:50:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10581
	for <ietf@ietf.org>; Sat, 7 Jun 2003 06:50:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ObF6-0002xn-00
	for ietf@ietf.org; Sat, 07 Jun 2003 06:48:12 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ObF6-0002xk-00
	for ietf@ietf.org; Sat, 07 Jun 2003 06:48:12 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h57Ao8e0048335
	for <ietf@ietf.org>; Sat, 7 Jun 2003 12:50:08 +0200 (CEST)
Message-ID: <017201c32ce2$8fd248e0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <138AA78F80DCE84B8EE424399FFBF9C91B071B@exchange.ad.skymv.com>            <00f301c32c7d$5954ce10$0a00000a@atkielski.com> <200306070242.h572gTnQ010924@turing-police.cc.vt.edu> <E19OUUc-0000Wc-W4@skipper.averillpark.net>
Subject: Re: Re[2]: Certificate / CPS issues 
Date: Sat, 7 Jun 2003 12:50:08 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Richard writes:

> i might add that the CEO of Habeas, Anne Mitchell,
> is an actual lawyer.

So?  Is she the _only_ lawyer??

There are probably any number of lawyers who would enjoy eating Habeas for
breakfast.

> i am not familiar with Anthony's credentials in the
> field of law. casually throwing legal terms about
> does not impress.

Neither does distorting legal principles in an attempt to control spam.

> this email happens to have Habeas headers, so i presume
> that he will not see it if he is throwing such mail
> out the way he says he will.

I haven't started filtering on it, since Habeas really doesn't appear on the
radar to speak of.




From owner-ietf@ietf.org  Sat Jun  7 07:16:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11019
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 07:16:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ObQJ-0002Nq-MO
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 06:59:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ObNJ-0002Lf-DO
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 06:56:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10647
	for <ietf@ietf.org>; Sat, 7 Jun 2003 06:56:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ObLP-0002zT-00
	for ietf@ietf.org; Sat, 07 Jun 2003 06:54:43 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ObLO-0002zQ-00
	for ietf@ietf.org; Sat, 07 Jun 2003 06:54:42 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h57Aude0048384
	for <ietf@ietf.org>; Sat, 7 Jun 2003 12:56:39 +0200 (CEST)
Message-ID: <018101c32ce3$78ba00c0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.10.10306070031430.3350-100000@spitfire.law.miami.edu> <200306070455.h574tQnQ012307@turing-police.cc.vt.edu>
Subject: Re: Certificate / CPS issues 
Date: Sat, 7 Jun 2003 12:56:38 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Valdis writes:

> ... the biggest question is which spammer (if any)
> is willing to risk the lawsuit to find out.

There might be quite a few.  It might be easy to have Habeas' claims
invalidated, and it would be worthwhile to spammers to get that out of the
way.  Additionally, some organizations might back them, such as the DMA or
the ACLU.

> The same thing is going on currently over on the
> patent law side of the fence - companies will just
> fold and pay the licensing fees rather than fight
> an obviously bogus patent.

They aren't choosing between fighting and going out of business, though.
Would Habeas license its haiku to spammers?




From owner-ietf@ietf.org  Sat Jun  7 11:03:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15048
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 11:03:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Of2z-0002w1-Bv
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 10:51:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OezL-0002tu-10
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 10:48:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14857
	for <ietf@ietf.org>; Sat, 7 Jun 2003 10:48:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OexL-00041j-00
	for ietf@ietf.org; Sat, 07 Jun 2003 10:46:07 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OexL-00041c-00
	for ietf@ietf.org; Sat, 07 Jun 2003 10:46:07 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h57EoTF03944;
	Sat, 7 Jun 2003 07:50:31 -0700
Date: Sat, 7 Jun 2003 07:28:12 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <5680498000.20030607072812@brandenburg.com>
To: "Tony Hain" <alh-ietf@tndh.net>
CC: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
In-Reply-To: <01d901c32a33$d017df70$46124104@eagleswings>
References: <01d901c32a33$d017df70$46124104@eagleswings>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony,


TH> I would like to see the outcome of a bof be identification of an
TH> approach to globally verifiable authenticated email. I have no doubt
TH> there will be many gaps in our current tool set (starting with a
TH> deployable PKI), and a truck load of operational guidelines to develop.

What is wrong with PGP and/or S/MIME?

How do they fail to provide 'globally verifiable authenticated mail?"

How would something else be different?

Given 10 years of public key authenticated mail, why would something new
succeed?


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




From owner-ietf@ietf.org  Sat Jun  7 12:09:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16025
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 12:09:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Og3t-0003mS-6H
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 11:56:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Og04-0003kM-4E
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 11:53:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15819
	for <ietf@ietf.org>; Sat, 7 Jun 2003 11:52:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ofy9-0004LT-00
	for ietf@ietf.org; Sat, 07 Jun 2003 11:51:01 -0400
Received: from pigeon.verisign.com ([65.205.251.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ofy9-0004LQ-00
	for ietf@ietf.org; Sat, 07 Jun 2003 11:51:01 -0400
Received: from mou1wnexc01.verisign.com (verisign.com [65.205.251.53])
        by pigeon.verisign.com (8.12.9/) with ESMTP id h57Fqvuv014199
        for <ietf@ietf.org>; Sat, 7 Jun 2003 08:52:57 -0700 (PDT)
Received: by mou1wnexc01.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LMLGKJ2B>; Sat, 7 Jun 2003 08:52:58 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D21FB@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Habeas and spam
Date: Sat, 7 Jun 2003 08:52:57 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

IANAL but I don't take the fact that habeas was founded by a lawyer to
indicate that their idea of copyright law is necessarily enforceable.
Lawyers are notoriously bad judges of their own cases. The guy running
EMarkettingAmerica thinks he can file a case on behalf of unspecified
plaintifs...

The copyright and trademark claims arround the Haiku are a stretch because
Habeas are trying to use one IP regime to achieve the object of another -
patent law. There is case law in the video games area that indicates you
can't use a copyright or trademark claim to make an access control system
closed.

But there is a pretty good argument that unauthorized use of the statement
'approved by Habeas' or similar is a mark. That is like a restaurant
claiming to have three Egon Ronay stars when it does not have any, it is a
pretty clear trademark case.

The Haiku thing might work and is pretty costless, but overall I doubt that
it is necessary. 



From owner-ietf@ietf.org  Sat Jun  7 14:53:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18128
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 14:53:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OiaU-0005NY-NM
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 14:38:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OiYr-0005LR-PE
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 14:37:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17911
	for <ietf@ietf.org>; Sat, 7 Jun 2003 14:37:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OiWx-00052S-00
	for ietf@ietf.org; Sat, 07 Jun 2003 14:35:07 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OiWw-00052P-00
	for ietf@ietf.org; Sat, 07 Jun 2003 14:35:06 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 59FE813968; Sat,  7 Jun 2003 18:36:32 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <5680498000.20030607072812@brandenburg.com>
From: Paul Vixie <vixie@vix.com>
Date: 07 Jun 2003 18:36:32 +0000
In-Reply-To: <5680498000.20030607072812@brandenburg.com>
Message-ID: <g3llwdraz3.fsf@sa.vix.com>
Lines: 75
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> What is wrong with PGP and/or S/MIME?

both are unusable by average nontechnical personnel.  not just the daily
use but the initial setup and anything out of the ordinary requires too
much expertise, by far, for many of my current e-mail correspondants to
use.

both rely on nonpermuting gateways and forwarders.  as long as microsoft
outlook strips e-mail addresses out of forwarded e-mail, we're screwed.
as long as line wrapping, mime stripping/mangling, ascii->ebcdic->ascii
translations, and other foul arts are present in the world, neither s/mime
nor pgp can reach a wide enough population to create "the network effect"
whereby either one of them becomes useful, on average, to me or to others
who want them to be useful on average.

s/mime relies on the x.509 pks industry which in is turn based on the goal
of enriching a small number of ca's who have to pay for relationships to
browser/useragent vendors who then make the certs worthwhile.  that can't
scale and hasn't scaled, other than in the case of server certs.  no way
will the average user be willing to pay money for a personal cert signing
if the companies on the list have all spammed them.

> How do they fail to provide 'globally verifiable authenticated mail?"

by appealing only to small communities, they have never created enough
benefit for anyone, anywhere, ever, to be willing to say "if inbound mail
was not signed, just drop it, don't even store it in my inbox" which is
a slightly different question but more apropos to the issue of consensuality.

> How would something else be different?

by starting from the assumption that all successul communications must be
provably consensual, and by making the network agent (think "listening mta")
synchronous with user agent policy ("i don't want mail that isn't provably
beneficial to me, based on the sender's identity, on the trust path from
them to me, and on their authentic promises that this communication does not
have assymmetric benefit to the sender"), and by planning for universal
scalability (no way for thawte or verisign or even rsadsi to get monopoly
economic power or results from it).

> Given 10 years of public key authenticated mail, why would something new
> succeed?

because everything designed or deployed to date has been done by engineers
for engineers.  because this will be made to fit the full spectrum of the
global community, including those at the low end who want assymetric
benefit from nonconsensual communications, and those at the high end who
can't cope with mangled encodings or key rings or signatures.

because (e)smtp has run its course and its model (data model, security
model, you name the model) is bankrupt.  because holding onto it like it
was salvageable if only we could find a vaccine for the plague of spam
has limited the ambitions of all who have tread this path to date.

because the position of "trust broker" cannot be a tiered monopoly in a
system that has to have global scale, and the only people who can think
their way that far out of the loop think that "key signing parties" are
a reasonable alternative.

--------

nevertheless you are still asking the wrong questions and i almost feel bad
for trying (above) to answer them.  don't ask "is this really necessary?" or
"why do we have to discard the current system?" but rather "how long will
the world population tolerate current and increasing levels of mangled or
nonconsensual communication?" and also "who will develop technology to meet
this gaping and obvious need?"

(i don't hold out much hope that ietf will do it, now that i think harder;
the current mix of scientists and vendors and loudmouths aren't sensitive
to the needs or aware of the nature of the broader spectrum of humanity
outside themselves and their current customers.  damn.  i guess i'm wasting
my time and yours on these rants.)
-- 
Paul Vixie



From owner-ietf@ietf.org  Sat Jun  7 14:57:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18330
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 14:57:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OikA-0005S7-Kx
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 14:48:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Oid6-0005Nd-1F
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 14:41:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17949
	for <ietf@ietf.org>; Sat, 7 Jun 2003 14:41:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OibB-000540-00
	for ietf@ietf.org; Sat, 07 Jun 2003 14:39:29 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OibA-00053m-00
	for ietf@ietf.org; Sat, 07 Jun 2003 14:39:29 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 6239A13969; Sat,  7 Jun 2003 18:40:56 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <5680498000.20030607072812@brandenburg.com>
From: Paul Vixie <vixie@vix.com>
Date: 07 Jun 2003 18:40:56 +0000
In-Reply-To: <5680498000.20030607072812@brandenburg.com>
Message-ID: <g3fzmlrarr.fsf@sa.vix.com>
Lines: 18
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> I would like to see the outcome of a bof be identification of an
> approach to globally verifiable authenticated email. I have no doubt
> there will be many gaps in our current tool set (starting with a
> deployable PKI), and a truck load of operational guidelines to develop.

"globally verifiable" isn't a useful condition.  "universally consensual"
is what the market is demanding.  don't make people pay in bandwidth to
receive noncredentialled traffic.  don't let there be a mix of credentialled
and noncredentialled traffic that a user has to spend a percentage of their
lifetime sorting.  if traffic isn't provably desireable by the recipient
then it ought not be transmittable.  if that proof turns out to be based on
false data then the trust path (possibly including one or more trust brokers)
should be poisoned against future falsity.

and in this bof, i suggest that gateways to the current system be shat upon
and never again considered.  when we move, we'll MOVE.
-- 
Paul Vixie



From owner-ietf@ietf.org  Sat Jun  7 15:42:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20251
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 15:42:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OjSc-0005ue-Ou
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 15:34:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OjNB-0005sG-QT
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 15:29:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20100
	for <ietf@ietf.org>; Sat, 7 Jun 2003 15:29:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OjLH-0005OD-00
	for ietf@ietf.org; Sat, 07 Jun 2003 15:27:07 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OjLG-0005OA-00
	for ietf@ietf.org; Sat, 07 Jun 2003 15:27:06 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0.6)
  with ESMTP-TLS id 240429; Sat, 07 Jun 2003 14:28:31 -0500
Message-ID: <3EE23CF8.9060405@ehsco.com>
Date: Sat, 07 Jun 2003 14:28:56 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Paul Vixie <vixie@vix.com>
CC: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <5680498000.20030607072812@brandenburg.com> <g3fzmlrarr.fsf@sa.vix.com>
In-Reply-To: <g3fzmlrarr.fsf@sa.vix.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 6/7/2003 1:40 PM Paul Vixie wrote:

> and in this bof, i suggest that gateways to the current system be shat
> upon and never again considered.  when we move, we'll MOVE.

That's not globally-applicable. Probably better to specify the gateway
tagging, and then ~Paul can reject mail that has the markers, while ~Sales
can devalue mail with those markers in their post-transfer filters.

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




From owner-ietf@ietf.org  Sat Jun  7 16:30:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20866
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 16:30:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ok9G-0006ei-LX
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 16:18:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ojzi-0006Zh-Tq
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 16:08:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20576
	for <ietf@ietf.org>; Sat, 7 Jun 2003 16:08:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ojxo-0005YO-00
	for ietf@ietf.org; Sat, 07 Jun 2003 16:06:56 -0400
Received: from garlic.amaranth.net ([208.254.46.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ojxn-0005YL-00
	for ietf@ietf.org; Sat, 07 Jun 2003 16:06:55 -0400
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226])
	(authenticated (0 bits))
	by garlic.amaranth.net (8.11.7/8.11.7) with ESMTP id h57K8pg19626
	(using TLSv1/SSLv3 with cipher RC4-SHA (128 bits) verified NO)
	for <ietf@ietf.org>; Sat, 7 Jun 2003 16:08:53 -0400
Message-Id: <5.2.1.1.2.20030607160426.02d13e18@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Sat, 07 Jun 2003 16:06:18 -0400
To: ietf@ietf.org
From: Daniel Senie <dts@senie.com>
Subject: Re: Engineering to deal with the social problem of spam
In-Reply-To: <3EE23CF8.9060405@ehsco.com>
References: <g3fzmlrarr.fsf@sa.vix.com>
 <5680498000.20030607072812@brandenburg.com>
 <g3fzmlrarr.fsf@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 03:28 PM 6/7/2003, Eric A. Hall wrote:

>on 6/7/2003 1:40 PM Paul Vixie wrote:
>
> > and in this bof, i suggest that gateways to the current system be shat
> > upon and never again considered.  when we move, we'll MOVE.
>
>That's not globally-applicable. Probably better to specify the gateway
>tagging, and then ~Paul can reject mail that has the markers, while ~Sales
>can devalue mail with those markers in their post-transfer filters.

Indeed, some level of gatewaying will likely be necessary for transition, 
and to accomodate intra-company use of embedded devices which transmit 
email alerts (e.g. UPSs, NAS boxes, etc.).




From owner-ietf@ietf.org  Sat Jun  7 16:52:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21225
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 16:52:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OkXS-0007FJ-JO
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 16:43:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OkVK-0007A7-Ov
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 16:41:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21105
	for <ietf@ietf.org>; Sat, 7 Jun 2003 16:41:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OkTQ-0005i3-00
	for ietf@ietf.org; Sat, 07 Jun 2003 16:39:36 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OkTP-0005i0-00
	for ietf@ietf.org; Sat, 07 Jun 2003 16:39:35 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h57KfVHY027621
	for ietf@ietf.org env-from <vjs>;
	Sat, 7 Jun 2003 14:41:31 -0600 (MDT)
Date: Sat, 7 Jun 2003 14:41:31 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306072041.h57KfVHY027621@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References:  <g3llwdraz3.fsf@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Paul Vixie <vixie@vix.com>

> ...
> "why do we have to discard the current system?" but rather "how long will
> the world population tolerate current and increasing levels of mangled or
> nonconsensual communication?" and also "who will develop technology to meet
> this gaping and obvious need?"
> ...

A contrary view that we have seen the crest of the flood of spam
can be argued:

  - spam filtering is a major selling point for all major ISPs,

  - the mass media is talking about spam filtering and spam, with ever
     decreasing sympathy for the "ethikal biznezmen" who are harmed by
     various anti-spam mechanisms, decreasing talk about evil, nasty
     vigilantes, and increasing sympathy for even abusive spam defenses.

  - there are some amazing legal attacks going on.  See for example
     "Legislators Call for Fix to Law Against Unsolicited E-Mails" in
     http://online.wsj.com/article/0,,SB105484626839598400,00.html
     (may require a subscription)

  - the DMA is getting its fingers squashed in some state do-not-call
     lists and the continuing federal DNC evolution.  See
	http://www.the-dma.org/cgi/disppressrelease?article=444
	http://www.the-dma.org/government/donotcalllists.shtml

  - since the start of the recent series of legal attacks on the worst
      spammers, I've seen a possible leveling off in the total number of
      streams of spam in the system.  The bend in the curve on 
      http://www.dcc-servers.net/dcc/graphs/db-size 
      coincident with the announcement of some legal attacks on spam
      might be an artifact or it might be real.

All of those could be coincidences or illusions, but all of them were
either conceivable or silly jokes 12 months ago.  It is possible that
people have had enough and aren't going to take it any more, much as
people in neighborhoods in some cities in Iraq reportedly decided
enough lawlessness was enough and took steps to control it.

Extrapolating from peaks of lawlessness in Iraq, the Balkans, Lebanon,
and elsewhere implies that the old system of a few, easily broken
locks and a few lightly armed police must be replaced with a full-up
prison state.  However, the local residents eventually decide to deal
with the worst problem makers one way (e.g. vigilantes) or another
(e.g. cooperating with old or external/U.N. civil authorities) and
the apparent need for extreme measures ebbs.  Sometimes, it takes
years for the residents to decide and overcome the problems including
external pressures, but eventually things get better and the old system
prevails.

In other words, Paul, are you sure you're not calling for an ashcroft?

Personally I'm equally convinced of the validity of both Paul's and
the view above.  I'm not convinced either is all or even most of the truth.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sat Jun  7 17:11:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21760
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 17:11:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Oklx-0007kh-SF
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 16:58:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Okkn-0007i2-Un
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 16:57:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21393
	for <ietf@ietf.org>; Sat, 7 Jun 2003 16:57:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Okit-0005mj-00
	for ietf@ietf.org; Sat, 07 Jun 2003 16:55:35 -0400
Received: from web10906.mail.yahoo.com ([216.136.131.42])
	by ietf-mx with smtp (Exim 4.12)
	id 19Okis-0005mg-00
	for ietf@ietf.org; Sat, 07 Jun 2003 16:55:34 -0400
Message-ID: <20030607205731.95478.qmail@web10906.mail.yahoo.com>
Received: from [12.237.229.250] by web10906.mail.yahoo.com via HTTP; Sat, 07 Jun 2003 13:57:31 PDT
Date: Sat, 7 Jun 2003 13:57:31 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Re: Engineering to deal with the social problem of spam
To: ietf@ietf.org
In-Reply-To: <5.2.1.1.2.20030607160426.02d13e18@mail.amaranth.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Disclaimer: there are people who know more about e-mail than I
do, and some of them are on this list. But, to press on.

Ummm, I'm wondering... in my own naive way.

My memories of mail gateways involved SMTP-to-non-SMTP mail
gateways, and the ones I hung around existed because one network
didn't speak SMTP. I can't imagine that there's a meaningful
mail system deployed today that doesn't speak SMTP (even if it's
through a gateway).

Why wouldn't we have mail sending applications that spoke (I'm
making this up) SMTP and MT2, with different URL schemes
(mailto: for SMTP, mailtoauth: for MT2) associated with our
correspondents, let correspondents advertise both ways of being
reached on Vcards, etc., and not worry about gateways?

The idea would be that after I get my friends trained that they
can send me mail at mailtoauth:spencer@mcsr-labs.org, and get
subscribed to my mailing lists with this address, I could move
away from mailto:spencer@mcsr-labs.org on my own schedule. If I
hope I never miss an unsolicited e-mail (from my high school
reunion group, for example), I might never move away. If I get
tired of looking at UBE in languages I don't have the privilege
of understanding, I might move away more quickly. But waiting
for the deployment of a gateway infrastructure wouldn't affect
my timeline, either way.

I know this is the dual-stack IPv6 migration strategy two
protocol stack levels higher - would that make any difference?

He asked naively, hoping that an MT2-to-SMTP gateway wouldn't be
necessary... isn't a lot of our mail munging the result of
gateways now?

Spencer

--- Daniel Senie <dts@senie.com> wrote:
> At 03:28 PM 6/7/2003, Eric A. Hall wrote:
> 
> >on 6/7/2003 1:40 PM Paul Vixie wrote:
> >
> > > and in this bof, i suggest that gateways to the current
> system be shat
> > > upon and never again considered.  when we move, we'll
> MOVE.
> >
> >That's not globally-applicable. Probably better to specify
> the gateway
> >tagging, and then ~Paul can reject mail that has the markers,
> while ~Sales
> >can devalue mail with those markers in their post-transfer
> filters.
> 
> Indeed, some level of gatewaying will likely be necessary for
> transition, 
> and to accomodate intra-company use of embedded devices which
> transmit 
> email alerts (e.g. UPSs, NAS boxes, etc.).
> 
> 
> _______________________________________________
> This message was passed through
> ietf_censored@carmen.ipv6.cselt.it, which is a sublist of
> ietf@ietf.org. Not all messages are passed. Decisions on what
> to pass are made solely by Raffaele D'Albenzio.




From owner-ietf@ietf.org  Sat Jun  7 17:59:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22694
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 17:59:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OlYL-00009J-Ed
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 17:48:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OlVD-00006k-H1
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 17:45:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22544
	for <ietf@ietf.org>; Sat, 7 Jun 2003 17:45:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OlTI-00065o-00
	for ietf@ietf.org; Sat, 07 Jun 2003 17:43:32 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OlTI-00065l-00
	for ietf@ietf.org; Sat, 07 Jun 2003 17:43:32 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0.6)
  with ESMTP-TLS id 240446; Sat, 07 Jun 2003 16:45:01 -0500
Message-ID: <3EE25CF6.8050204@ehsco.com>
Date: Sat, 07 Jun 2003 16:45:26 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Spencer Dawkins <spencer_dawkins@yahoo.com>
CC: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <20030607205731.95478.qmail@web10906.mail.yahoo.com>
In-Reply-To: <20030607205731.95478.qmail@web10906.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 6/7/2003 3:57 PM Spencer Dawkins wrote:

> Why wouldn't we have mail sending applications that spoke (I'm
> making this up) SMTP and MT2, with different URL schemes
> (mailto: for SMTP, mailtoauth: for MT2) associated with our
> correspondents, let correspondents advertise both ways of being
> reached on Vcards, etc., and not worry about gateways?

Let's separate those concepts.

First, regarding the need for gateways, people will use them no matter
what we say, since there will always be people with mixed installations,
people who need mail from both networks (eg, sales and support), and so
forth. If we dont specify the gateway behavior, the only predictable
outcome is that people will build them without guidance. If we specify
that they cannot be made, people will still make them, and without
guidance. Clearly, the only workable strategy is to specify them, and to
do so in such a way that folks like Paul can reject mail that ever
travelled across a legacy network (that's going to be tough in toto,
considering that MUAs will probably be built to use SMTP as the first-hop
service for a very long time to come).

As for the use of an alternate URI, those are used to tell the viewer
which protocol to use. In the case of outbound mail, it would effectively
be a way for the message recipient to tell the message sender that they
have to use MT2 for the first-hop of the message, which doesn't make a lot
of sense outside closed environments. Furthermore, what happened to the
message after the first-hop would be a result of the mail-routing
information in between the first and last hops, and would not necessarily
be determined by the protocol that the sender used for the first-hop. So,
URIs can't really be used to control the delivery path.

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




From owner-ietf@ietf.org  Sat Jun  7 18:44:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24814
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 18:44:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OmE9-00076Q-Gk
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 18:31:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OmAA-00073B-VC
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 18:27:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24580
	for <ietf@ietf.org>; Sat, 7 Jun 2003 18:27:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Om8G-0006Lv-00
	for ietf@ietf.org; Sat, 07 Jun 2003 18:25:52 -0400
Received: from voo.doo.net ([81.17.45.210])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Om8F-0006Lr-00
	for ietf@ietf.org; Sat, 07 Jun 2003 18:25:51 -0400
Received: from localhost (localhost [127.0.0.1])
	by voo.doo.net (8.12.8/8.12.6) with ESMTP id h57MRkC8043273
	for <ietf@ietf.org>; Sun, 8 Jun 2003 00:27:47 +0200 (CEST)
	(envelope-from marc@schneiders.org)
Date: Sun, 8 Jun 2003 00:27:45 +0200 (CEST)
From: Marc Schneiders <ietf@schneiders.org>
To: <ietf@ietf.org>
Subject: The spam problem is political (Re: Engineering to deal with the
 social problem of spam)
Message-ID: <20030608002613.O40603-100000@voo.doo.net>
X-Preferred-email-to: marc@schneiders.org
X-Other-email-to: marc@venster.nl
X-Organization: Venster (Zeist - NL)
X-URL: http://www.bijt.net/
X-SOA: A.ROOT-SERVERS.ORSC.
X-OS: FreeBSD: The Power to Serve
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 7 Jun 2003, at 13:57 [=GMT-0700], Spencer Dawkins wrote:

> Disclaimer: there are people who know more about e-mail than I
> do, and some of them are on this list.

I know absolutely nothing more than the bare minimum needed to keep
sendmail running (so far). That is no reason to stop reading.  If my
idea has some merit, you can stop the spam topic on this list.

Why do people not fill my snail mailbox with junk letters, leaflets?
Because (1) it costs money to print a leaflet and get it distributed.
Also (2) there are (where I live) laws and political deals with
advertizers, that make it a bad idea to use addresses from cd-roms, or
just deliver leaflets to all addresses (direct distribution). If my
mailbox says "NO" I should not get them. And the great thing is, the
Dutch police and justice system can get at those who don't play by the
rules.(*)

Spam costs nothing. Spam comes from all corners of the world, where
the Dutch police doesn't dare to go. And even if they would the Dutch
judges would say it is without their jurisduction. Spam can only be
fought through a worldwide police and justice system. This cannot by
achieved by an RFC. Send this problem to ICANN.

(*) I know that in theory people could evade being prosecuted in
Holland by sending advertizing letters, using illegal address
databases from Tuvalu and contact addresses for themselves in Libya.
But this doesn't happen.





From owner-ietf@ietf.org  Sat Jun  7 18:51:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25063
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 18:51:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OmPY-0007Eu-TJ
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 18:43:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OmKi-00079d-4s
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 18:38:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24766
	for <ietf@ietf.org>; Sat, 7 Jun 2003 18:38:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OmIn-0006OD-00
	for ietf@ietf.org; Sat, 07 Jun 2003 18:36:45 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OmIm-0006OA-00
	for ietf@ietf.org; Sat, 07 Jun 2003 18:36:44 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h57Mcf6N054148
	for <ietf@ietf.org>; Sun, 8 Jun 2003 00:38:41 +0200 (CEST)
Message-ID: <022601c32d45$8bad4e50$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <01d901c32a33$d017df70$46124104@eagleswings> <5680498000.20030607072812@brandenburg.com>
Subject: Re: Engineering to deal with the social problem of spam
Date: Sun, 8 Jun 2003 00:38:41 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave writes:

> How do they fail to provide 'globally verifiable
> authenticated mail?"

Neither is universally supported.



From owner-ietf@ietf.org  Sat Jun  7 18:56:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25239
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 18:56:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OmPZ-0007F0-4m
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 18:43:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OmN4-0007BK-M5
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 18:41:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24793
	for <ietf@ietf.org>; Sat, 7 Jun 2003 18:41:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OmL9-0006PN-00
	for ietf@ietf.org; Sat, 07 Jun 2003 18:39:11 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OmL9-0006PK-00
	for ietf@ietf.org; Sat, 07 Jun 2003 18:39:11 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h57Mf86N054172
	for <ietf@ietf.org>; Sun, 8 Jun 2003 00:41:08 +0200 (CEST)
Message-ID: <022b01c32d45$e3064c60$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <2A1D4C86842EE14CA9BC80474919782E0D21FB@mou1wnexm02.verisign.com>
Subject: Re: Habeas and spam
Date: Sun, 8 Jun 2003 00:41:07 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Phillip writes:

> IANAL but I don't take the fact that habeas was founded
> by a lawyer to indicate that their idea of copyright law
> is necessarily enforceable.

Agreed.  Probably 95% of all corporations are founded by lawyers.  That
doesn't mean that they'll always win in court, or even that they have sound
business ideas.

> But there is a pretty good argument that unauthorized
> use of the statement 'approved by Habeas' or similar
> is a mark.

It would have to demonstrably lead to confusion in the eyes of consumers or
dilute the value of the mark.  Since this mark would not even be visible to
consumers, it's hard to see how that could be argued in this case.





From owner-ietf@ietf.org  Sat Jun  7 19:28:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25809
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 19:28:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Omj6-00007Y-1a
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 19:03:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OmhX-0008Vq-1i
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 19:02:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25443
	for <ietf@ietf.org>; Sat, 7 Jun 2003 19:02:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Omfb-0006ch-00
	for ietf@ietf.org; Sat, 07 Jun 2003 19:00:19 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Omfa-0006cS-00
	for ietf@ietf.org; Sat, 07 Jun 2003 19:00:18 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id A830E1396B; Sat,  7 Jun 2003 23:01:43 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <5.2.1.1.2.20030607160426.02d13e18@mail.amaranth.net>
From: Paul Vixie <vixie@vix.com>
Date: 07 Jun 2003 23:01:43 +0000
In-Reply-To: <5.2.1.1.2.20030607160426.02d13e18@mail.amaranth.net>
Message-ID: <g3brx9qyp4.fsf@sa.vix.com>
Lines: 59
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> > > and in this bof, i suggest that gateways to the current system be shat
> > > upon and never again considered.  when we move, we'll MOVE.
> >
> >That's not globally-applicable.

yes, it is.

> >Probably better to specify the gateway tagging, ...

and we're going to convey trust and credence through a nontrusted system How?

> Indeed, some level of gatewaying will likely be necessary for transition, 

no, it's not.  i really mean it.

> and to accomodate intra-company use of embedded devices which transmit 
> email alerts (e.g. UPSs, NAS boxes, etc.).

let me explain what i mean, in case there's room for compromise.  ibcs will
have to be an end to end system.  there won't be MX RRs for RHS's, but 
rather SRV RRs for destinations -- almost exactly like SIP, i suspect.  so,
rather than the current logic of

        ($lhs, $rhs) = split /@/, $dest;
        @mxset = &lookup($rhs, 'MX');
        foreach $mx (sort { $a->prio <=> $b->prio } @mxset) {
                return 1 if &try($mx->host, 25);
        }
        return 0;

we'll see logic of the form

        (($srvname = $dest) ~= s/\./\\./go) ~= s/@/./;
        @ibcsset = &lookup("_ibcs._tcp.$srvname", 'SRV');
        foreach $srv (sort { $a->prio <=> $b->prio } @srvset) {
                return 1 if &try($srv->host, $srv->port);
        }
        return 0;

this means any destination needs a SRV RR.  instead of cracking paul@vix.com
on the @ and looking for the MX RRset for vix.com, it'll get translated into
_ibcs._tcp.paul.vix.com and the SRV RRset will be used to find the possible
agents for this destination.

if smtp fallback is desired, it must be done in the sending user agent, who
upon not finding the SRV RR, could ask "try smtp instead?".  if there's a
NAT or firewall or gateway involved, then the submission protocol between
the user agent and local gateway has to have enough infowidth to express
these conditions and offer these choices.

the idea of an ibcs agent who nexthops through smtp is just right out, other
than because the user's own avatar decides to punch it through smtp to reach
a pager or something like that.

the idea of an smtp agent who can gain a sender's credentials in order to
make promises about mail that came from smtp and has to reach an ibcs
recipient is likewise nonsequitur.
-- 
Paul Vixie



From owner-ietf@ietf.org  Sat Jun  7 19:38:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26061
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 19:38:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19On2I-0000Kd-Br
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 19:23:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Omtt-0000El-Gr
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 19:15:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25629
	for <ietf@ietf.org>; Sat, 7 Jun 2003 19:15:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Omry-0006gc-00
	for ietf@ietf.org; Sat, 07 Jun 2003 19:13:06 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Omrx-0006gV-00
	for ietf@ietf.org; Sat, 07 Jun 2003 19:13:06 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id B6B6913969; Sat,  7 Jun 2003 23:14:33 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <200306072041.h57KfVHY027621@calcite.rhyolite.com>
From: Paul Vixie <vixie@vix.com>
Date: 07 Jun 2003 23:14:33 +0000
In-Reply-To: <200306072041.h57KfVHY027621@calcite.rhyolite.com>
Message-ID: <g37k7xqy3q.fsf@sa.vix.com>
Lines: 39
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> In other words, Paul, are you sure you're not calling for an ashcroft?

completely.  i have met the enemy, and i have also met the potential enemy,
and i know that recipient privacy is nowhere on anybody's mind.  consider
what would happen if the ITU ever finished its debate about e164.arpa and
there a few hundred million voip-reachable phones (either IP to the station
or IP to the central office and analog to the station).  all it would take
a telemarketer is a simple NAPTR/SRV sweep, with SYN-probe, to build a list
of tens of millions of reachable endpoints.  ten racks of linux PC's later,
we'd all be getting round the clock robotic calls from some telespamketer
with some viagra to sell.

i need ibcs to make it possible to keep doing what i used to do in e-mail,
but more importantly i need the "ashcroft" you speak of in order to gain
confidence about SIP callers, or instant messenger or SMS senders.  right
now the security people call this "the PKI problem" and calling it that is
exactly what makes it unsolvable.  i sweartagod the next time i meet an
ivorytowermathtype who wants to tell me how hard something is, i'm just
going to <do something unsavory>.  We Know How To Do This!  not only that,
but We Know What The Market Demands!

note that brokered anonymity will still be possible.  knowing someone's
identity means knowing that they are somebody in particular, and not 
necessarily knowing their meatspace-corredpondance identity.  i'd be one
of many people who would set my acceptance-filters to allow e-mail 
traffic based on transitive recourse toward a well-heeled trust broker
(who has much to lose if their clients misbehave), even if i might not
accept an e-commerce transaction from someone who didn't want me to know
their name and address in meatspace.

> Personally I'm equally convinced of the validity of both Paul's and the
> view above.  I'm not convinced either is all or even most of the truth.

i have faith in human nature.  if you build a world wide communications
system to make communications easier, It Will Be Used.  by the full
spectrum of humanity.  anybody who wants 10000:1 odds against this should
just gimme yer money right now, because it's not even a fair bet.
-- 
Paul Vixie



From owner-ietf@ietf.org  Sat Jun  7 19:48:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26299
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 19:48:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OnH5-00014z-MK
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 19:39:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OnCg-0000lv-VS
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 19:34:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26022
	for <ietf@ietf.org>; Sat, 7 Jun 2003 19:34:26 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OnAl-0006nb-00
	for ietf@ietf.org; Sat, 07 Jun 2003 19:32:31 -0400
Received: from h80ad265d.async.vt.edu ([128.173.38.93] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OnAj-0006nY-00
	for ietf@ietf.org; Sat, 07 Jun 2003 19:32:30 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h57NYMGF005523;
	Sat, 7 Jun 2003 19:34:22 -0400
Message-Id: <200306072334.h57NYMGF005523@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Haren Visavadia <haren@btopenworld.com>
Cc: ietf@ietf.org
Subject: Re: Certificate / CPS issues 
In-Reply-To: Your message of "Sat, 07 Jun 2003 08:30:34 BST."
             <001901c32cc6$af08eb90$0100010a@MyHomeLAN.local> 
References: <001901c32cc6$af08eb90$0100010a@MyHomeLAN.local>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1980170611P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sat, 07 Jun 2003 19:34:21 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sat, 07 Jun 2003 08:30:34 BST, Haren Visavadia <haren@btopenworld.com>  said:
> The CA holds no warranty, making the certificate invalid in legal terms,
> since they can not prove the certificate is yours.

IANAL, but you better check with a lawyer on that one.  Depending where you
live, a digital signature *could* be binding even if it's invalid... Yes,
there's some broken legislation out there...

Also, remember that a signature merely proves the signed data and the
public key were accessible to a computational device at the same time.
This is a LONG stretch from actually meaning you signed it intentionally.
See Schneier's "Secrets and Lies", there's a whole chapter on this point,
or just wait till somebody you know gets nailed with the next Sobig/Nimda/Klez
or whatever, and ask if any of the mail they sent out was intentional. ;)


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

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

iD8DBQE+4nZ9cC3lWbTT17ARAu8uAJ0UM++y/2aLJrS/p9BkZdaXyWXPdACgm2GD
hqmyIfP9obFd6jiV4FuVjro=
=btud
-----END PGP SIGNATURE-----

--==_Exmh_-1980170611P--



From owner-ietf@ietf.org  Sat Jun  7 20:14:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26734
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 20:14:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Oni4-0001vO-O8
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 20:06:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ondx-0001qw-Hg
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 20:02:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26639
	for <ietf@ietf.org>; Sat, 7 Jun 2003 20:02:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Onc1-00070o-00
	for ietf@ietf.org; Sat, 07 Jun 2003 20:00:41 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Onc0-00070l-00
	for ietf@ietf.org; Sat, 07 Jun 2003 20:00:40 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h5802a6N054870
	for <ietf@ietf.org>; Sun, 8 Jun 2003 02:02:36 +0200 (CEST)
Message-ID: <024d01c32d51$44e5fd30$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <20030608002613.O40603-100000@voo.doo.net>
Subject: Re: The spam problem is political (Re: Engineering to deal with the social problem of spam)
Date: Sun, 8 Jun 2003 02:02:36 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Marc writes:

> Spam can only be fought through a worldwide
> police and justice system.

If so, that does not bode well for the future.  As far as I can remember,
_nothing_ has been successfully fought worldwide, except perhaps smallpox.

> This cannot by achieved by an RFC. Send this
> problem to ICANN.

ICANN can't do anything about it.




From owner-ietf@ietf.org  Sat Jun  7 20:16:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26900
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 20:16:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Onjr-0001yN-5i
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 20:08:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ong8-0001tQ-1C
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 20:04:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26660
	for <ietf@ietf.org>; Sat, 7 Jun 2003 20:04:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OneC-000717-00
	for ietf@ietf.org; Sat, 07 Jun 2003 20:02:56 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OneB-000714-00
	for ietf@ietf.org; Sat, 07 Jun 2003 20:02:55 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h5804q6N054894
	for <ietf@ietf.org>; Sun, 8 Jun 2003 02:04:52 +0200 (CEST)
Message-ID: <025c01c32d51$95a8e2a0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <200306072041.h57KfVHY027621@calcite.rhyolite.com> <g37k7xqy3q.fsf@sa.vix.com>
Subject: Re: Engineering to deal with the social problem of spam
Date: Sun, 8 Jun 2003 02:04:52 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul writes:

> if you build a world wide communications
> system to make communications easier, It
> Will Be Used.  by the full spectrum of humanity.

Then logically, the only way to exclude any part of that spectrum is to make
a communications system harder to use.  I'm not sure that making things
harder is a desirable goal.




From owner-ietf@ietf.org  Sat Jun  7 21:14:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27710
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 21:14:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OoSJ-0003FP-Hp
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 20:54:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OoNo-0003CA-BJ
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 20:50:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27484
	for <ietf@ietf.org>; Sat, 7 Jun 2003 20:50:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OoLs-0007G4-00
	for ietf@ietf.org; Sat, 07 Jun 2003 20:48:04 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OoLr-0007G1-00
	for ietf@ietf.org; Sat, 07 Jun 2003 20:48:03 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0.6)
  with ESMTP-TLS id 240472; Sat, 07 Jun 2003 19:49:31 -0500
Message-ID: <3EE28834.4020703@ehsco.com>
Date: Sat, 07 Jun 2003 19:49:56 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Paul Vixie <vixie@vix.com>
CC: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <5.2.1.1.2.20030607160426.02d13e18@mail.amaranth.net> <g3brx9qyp4.fsf@sa.vix.com>
In-Reply-To: <g3brx9qyp4.fsf@sa.vix.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 6/7/2003 6:01 PM Paul Vixie wrote:

>>> Probably better to specify the gateway tagging, ...
> 
> and we're going to convey trust and credence through a nontrusted
> system How?

We can discover without question who the first MT2 system in the path was,
and (assuming that identity information is required, which I do) that
gateway will also have had to present identity information about the
sender. All rules, recommendations, and supportive integrity mechanisms
aside, those are going to be your primary actionable knobs.

Assume that somebody like AOL embraces this system for private transfers
with some other large-scale provider. They probably won't update all of
their submission services beforehand, but instead will just map their
existing authenticated submission services to this system. EG, they'll
see who a particular mail message is from, locate the appropriate user
certificate in their private directory, and feed that into the system.
This same model can hold true for private Exchange, GroupWise, or SMTP
AUTH submission services. All of these are examples of gateways that can
leverage authentication services to map a sender certificate, even if
those networks aren't running MT2 as the native service.

So the problem isn't with "gateways" it's with unauthenticated senders.
Simply put, messages won't make it to the next-hop inside the MT2 transfer
network UNLESS the gateway provides a user cert for the sender identity;
the next-hop would otherwise just reject the message.

Gateway rules (which weren't discussed in any of the above) can give you
more information to act on. For example, you can set your defenses higher
if you see remnants of more than one legacy Received header, or if there
are other characteristics you don't like. Obviously gateways are going to
be necessary, so it's really going to be a question of being able to apply
the right kind of heuristics.

> if smtp fallback is desired, it must be done in the sending user agent,
> who upon not finding the SRV RR, could ask "try smtp instead?".

Conversion in either direction could theoretically occur at any point.
What cannot easily happen is for any message to get past the first hop of
the MT2 network without having entered at a system which did not have
access to user credentials.

[not to Paul, who already gets it: On the subject of identity-tracking,
this subject is a non-starter. Folks can gather and use all of the
identities they want from any number of ISPs and mail services (you can
call yourself WonderWoman@yahoo and nobody will care as long as it
validates). This is, in the end, the same level of anonymity that is
available with SMTP today]

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




From owner-ietf@ietf.org  Sat Jun  7 21:14:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27712
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 21:14:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OoSJ-0003FV-OD
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 20:54:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OoQi-0003CC-4r
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 20:53:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27505
	for <ietf@ietf.org>; Sat, 7 Jun 2003 20:53:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OoOn-0007Gv-00
	for ietf@ietf.org; Sat, 07 Jun 2003 20:51:05 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OoOl-0007Gs-00
	for ietf@ietf.org; Sat, 07 Jun 2003 20:51:03 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h580r0Z9010983
	for ietf@ietf.org env-from <vjs>;
	Sat, 7 Jun 2003 18:53:00 -0600 (MDT)
Date: Sat, 7 Jun 2003 18:53:00 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306080053.h580r0Z9010983@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <g37k7xqy3q.fsf@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Paul Vixie <vixie@vix.com>

> > In other words, Paul, are you sure you're not calling for an ashcroft?
>
> completely.  i have met the enemy, and i have also met the potential enemy,
> and i know that recipient privacy is nowhere on anybody's mind.  consider
> what would happen if the ITU ever finished its debate about e164.arpa and
> there a few hundred million voip-reachable phones (either IP to the station
> or IP to the central office and analog to the station).  all it would take
> a telemarketer is a simple NAPTR/SRV sweep, with SYN-probe, to build a list
> of tens of millions of reachable endpoints.  ten racks of linux PC's later,
> we'd all be getting round the clock robotic calls from some telespamketer
> with some viagra to sell.

I can't see enough difference between that rhetoric and the doomsday
scenarios of anthrax in cropdusting airplanes, "dirty nuclear" bombs,
and the rest of the conceivable catastrophes that rationalize locking
us up in our homes in front network TV.

You can't and shouldn't even try to engineer perfect safety from all
conceivable disasters.  Before getting excited about such a
viagra-VoIP bomb, think the likelihood of the first bombing, whether
it could happen a second time after the perpetrators of the first were
drawn and quartered, and whether the costs (not just in money) of
preventing the first detonation are worthwhile.


> i need ibcs to make it possible to keep doing what i used to do in e-mail,
> but more importantly i need the "ashcroft" you speak of in order to gain
> confidence about SIP callers, or instant messenger or SMS senders.  right
> ...

By an "ashcroft" I mean extremely costly (mostly not in money),
insufficiently or entirely unjustified, so called defenses against
potential disasters, where the defenses are of dubious or no real use
(e.g. the new airplane passenger screening) against the ostensible
potential disaster.

I don't understand enough of your notions to see whether I think it
would work or be worse than spam, but I have dark suspicions that they
would turn out like the new and forthcoming "defenses" against "terrorism"
(and "drugs," "child porn," etc.) from the U.S. DOD and DOJ.

Cassandra was right, but her proscription was only to send one woman
home to her lawful husband.


So how about turning down the heat a little and being more technically
specific about your replacement for the Internet?  Since that viagra-VoIP
bomb has nothing to do with SMTP, it seems you're talking about a far
bigger progject than "merely" replacing SMTP.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sat Jun  7 21:59:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28539
	for <ietf-web-archive@odin.ietf.org>; Sat, 7 Jun 2003 21:59:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OpIb-0004cj-Fv
	for ietf-list@asgard.ietf.org; Sat, 07 Jun 2003 21:48:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OpHR-0004ZM-Vl
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 21:47:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28445
	for <ietf@ietf.org>; Sat, 7 Jun 2003 21:47:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OpFW-0007Xo-00
	for ietf@ietf.org; Sat, 07 Jun 2003 21:45:34 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OpFV-0007Xl-00
	for ietf@ietf.org; Sat, 07 Jun 2003 21:45:33 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id A766B13969; Sun,  8 Jun 2003 01:46:59 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <200306080053.h580r0Z9010983@calcite.rhyolite.com>
From: Paul Vixie <vixie@vix.com>
Date: 08 Jun 2003 01:46:59 +0000
In-Reply-To: <200306080053.h580r0Z9010983@calcite.rhyolite.com>
Message-ID: <g33cilqr1o.fsf@sa.vix.com>
Lines: 67
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> By an "ashcroft" I mean extremely costly (mostly not in money),
> insufficiently or entirely unjustified, so called defenses against
> potential disasters, where the defenses are of dubious or no real use
> (e.g. the new airplane passenger screening) against the ostensible
> potential disaster.

ah.  then that's not what i'm advocating.  i want the digital equivilent
of a peephole in my front door so i can ignore the doorbell if i don't
like what i see.  

> I don't understand enough of your notions to see whether I think it would
> work or be worse than spam, but I have dark suspicions that they would
> turn out like the new and forthcoming "defenses" against "terrorism" (and
> "drugs," "child porn," etc.) from the U.S. DOD and DOJ.

i believe, and have always believed, that all communications ought to be
mutually consensual.  that philosophy underlaid my initial thoughts about
both MAPS and DCC, and is part of my motive for trying to get DNSSEC deployed.

plenty, no, *many* are the humans who can reach me by digital
communications for whom my consent is seen as irrelevant (or worse.)  my
son has been receiving pornographic spam for five years, and he just now
turned twelve years old.  did you all who contributed to the creation of
e-mail as a media believe that it should be "rated R, no children under the
age of 17 admitted without a parent"?  for my part, i did not.

or consider the "e-mail appending" data miners, who believe that my consent
to receive a magazine by postal mail somehow implies my consent to receive
anything else that publishing conglomerate wants to send me by e-mail.  (one
is sender-paid, the other is not, and my consent cannot be implied.)

due to accidents of fate, the CIX.NET MX RR points at my personal server.
it turns out that there are now many millions of valid @COX.NET mailboxes,
and that through normal error rates i receive several dozen misaddressed
messages per day, usually several of them being microsoft passport ACK's
containing enough information for me to commit identity theft if i so
desired.  a lot of the mail is quite personal in nature, too.  is this
how we thought e-mail would grow up and meet its larger audience?  not me!

the current system is utterly laughable and if it were proposed apriori
it would be laughed out of the room.  that which was suitable for polite
early adopters in the R&E community is completely unsuiable for the full
global population, And This Should Come As No Surprise To Anybody.

> So how about turning down the heat a little and being more technically
> specific about your replacement for the Internet?  Since that viagra-VoIP
> bomb has nothing to do with SMTP, it seems you're talking about a far
> bigger progject than "merely" replacing SMTP.

here's the problem.  if we had end-to-end personal certificates that were
widely deployed and universally presented, it would become reasonable to
try to wire an smtp listener to reject all but certified traffic -- but
since pornospammers could and would acquire signed certificates, we'd
have to do some kind of pgp-like kevinbacon-like "degrees of separation"
logic to find out about trust.

it turns out both of those are missing.  and creating them is a bigger
problem than rewiring smtp would be.  and that once they exist they will
have equal applicability to IM/ICQ/SIP/etc.

as usual, i would be happiest if someone else would take this on: i'm Busy.
however, that's not why i don't write a detailed proposal.  my goal at the
moment is to discover whether the ietf possesses a "collective will" and
if so, whether it is "willing" to take on this much larger problem.  so far
the answer seems to be not just "no" but "hell no!"
-- 
Paul Vixie



From owner-ietf@ietf.org  Sun Jun  8 00:20:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00952
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 00:20:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OrU2-0006fV-Kq
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 00:08:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OrTD-0006cK-By
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 00:07:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00831
	for <ietf@ietf.org>; Sun, 8 Jun 2003 00:07:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OrRI-0000ND-00
	for ietf@ietf.org; Sun, 08 Jun 2003 00:05:52 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OrRH-0000NA-00
	for ietf@ietf.org; Sun, 08 Jun 2003 00:05:51 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5847iwY018694
	for ietf@ietf.org env-from <vjs>;
	Sat, 7 Jun 2003 22:07:44 -0600 (MDT)
Date: Sat, 7 Jun 2003 22:07:44 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306080407.h5847iwY018694@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <g33cilqr1o.fsf@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Paul Vixie <vixie@vix.com>

> ...
> > So how about turning down the heat a little and being more technically
> > specific about your replacement for the Internet?  ..

> here's the problem.  if we had end-to-end personal certificates that were
> widely deployed and universally presented, it would become reasonable to
> try to wire an smtp listener to reject all but certified traffic -- but
> since pornospammers could and would acquire signed certificates, we'd
> have to do some kind of pgp-like kevinbacon-like "degrees of separation"
> logic to find out about trust.
>
> it turns out both of those are missing.  and creating them is a bigger
> problem than rewiring smtp would be.  and that once they exist they will
> have equal applicability to IM/ICQ/SIP/etc.
>
> as usual, i would be happiest if someone else would take this on: i'm Busy.
> however, that's not why i don't write a detailed proposal.  my goal at the
> moment is to discover whether the ietf possesses a "collective will" and
> if so, whether it is "willing" to take on this much larger problem.  so far
> the answer seems to be not just "no" but "hell no!"

Imagine if you will (since it's true), that I don't have any real idea
what you're talking about.  I understand only that you think that PKI
is hopelessly broken (golly gee, what a surprise) and that something
else easy and obvious (to you but not me) is The Solution.  Assume
(since it's also true) that I've lost track of the number of times
someone has announced Third/Forth/Fifth Generation Computing, Artificial
Intelligence, True Artificial Intelligence, For Sure This Time Really
True Artifical Intelligence, the Solution to the Von Neumann Bottleneck,
Real Computer Security, Really Real Computer and Network Security,
The Solution To Spam, and any and everthing else.  Many of those
announcements came from bright and sincere people who were only
overstating their points.

All I can see is the truth of your point that pornospammers could and
would acquire signed certificates, that each of us have a single digit
kevinbacon-like separation from any pornospammers, and that most of
us are closer to some pornospammer than to someone else we'd like to
hear from.

What do you expect me to do?  I won't answer your draft notice
"hell no I won't go!" but I'm not going to enlist until I have a
glimmer of where you're sailing and what's under the decks.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sun Jun  8 00:57:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01658
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 00:57:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Os9b-0007U5-Cy
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 00:51:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Orxw-0007OM-Df
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 00:39:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01271
	for <ietf@ietf.org>; Sun, 8 Jun 2003 00:39:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Orw1-0000Vt-00
	for ietf@ietf.org; Sun, 08 Jun 2003 00:37:37 -0400
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Orw0-0000Vq-00
	for ietf@ietf.org; Sun, 08 Jun 2003 00:37:36 -0400
Received: from [66.92.109.27] (helo=think.thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:DES-CBC3-SHA:168)  (Exim 3.35 #1 (Debian))
	id 19Orxk-0004Nc-00; Sun, 08 Jun 2003 00:39:25 -0400
Received: from tytso authenticated as tytso by think.thunk.org with local   (Exim 3.35 #1 (Debian))
	id 19Orxk-0004Ez-00; Sun, 08 Jun 2003 00:39:24 -0400
Date: Sun, 8 Jun 2003 00:39:24 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: Tony Hain <alh-ietf@tndh.net>, ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
Message-ID: <20030608043924.GC12736@think>
References: <01d901c32a33$d017df70$46124104@eagleswings> <5680498000.20030607072812@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5680498000.20030607072812@brandenburg.com>
User-Agent: Mutt/1.5.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, Jun 07, 2003 at 07:28:12AM -0700, Dave Crocker wrote:
> Tony,
> 
> 
> TH> I would like to see the outcome of a bof be identification of an
> TH> approach to globally verifiable authenticated email. I have no doubt
> TH> there will be many gaps in our current tool set (starting with a
> TH> deployable PKI), and a truck load of operational guidelines to develop.
> 
> What is wrong with PGP and/or S/MIME?
> 
> How do they fail to provide 'globally verifiable authenticated mail?"

Again, I'd like to repeat my observation that we don't need to provide
"globally verifiable authenticated mail" in order to solve the SPAM
problem.  Given the notable lack of success in setting up a global PKI
after more than decade of trying, assuming that this is a prerequisite
for solving the SPAM problem is merely setting ourselves up for failure.

Bare keys will do; consider a system where people keep a list of those
keys that they will accept mail.  If someone tries to send mail and
their key is not on the recipient's list, the mail is returned to them
until they can perform a Hashcash calculation consuming a non-trivial
amount of CPU time, at which point their key is placed on the
recipient's list, and the sender can retry to send the message.  If a
recipient receives SPAM, they simply drop the key of the sender from
their "ok-to-receive" list.

This avoids the whole requirement of binding identities to names via a
global system that everyone trusts, and it avoids the problem of
determining who to trust regarding whether someone is or isn't a
spammer.

I'm sure this isn't the only way to do things, but I'm also sure this
is far more practical than any scheme that requires a global PKI.  

							- Ted



From owner-ietf@ietf.org  Sun Jun  8 03:39:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15797
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 03:39:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ouec-0007aj-JU
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 03:31:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OuWv-0007Ve-TK
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 03:23:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15653
	for <ietf@ietf.org>; Sun, 8 Jun 2003 03:23:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OuV0-0001Xq-00
	for ietf@ietf.org; Sun, 08 Jun 2003 03:21:54 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OuUz-0001Xn-00
	for ietf@ietf.org; Sun, 08 Jun 2003 03:21:53 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 327B813968; Sun,  8 Jun 2003 07:23:21 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <200306080407.h5847iwY018694@calcite.rhyolite.com>
From: Paul Vixie <vixie@vix.com>
Date: 08 Jun 2003 07:23:21 +0000
In-Reply-To: <200306080407.h5847iwY018694@calcite.rhyolite.com>
Message-ID: <g3of19owwm.fsf@sa.vix.com>
Lines: 27
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

vjs@calcite.rhyolite.com (Vernon Schryver) writes:

> What do you expect me to do?  I won't answer your draft notice
> "hell no I won't go!" but I'm not going to enlist until I have a
> glimmer of where you're sailing and what's under the decks.

at this point I'm still looking for the answer to some simple questions.

1. does the ietf as a community generally believe that provable
   mutual consent between a sender and recipient is an achievable
   (technically) and desireable (by the global user base) goal?

2. if #1, does this same community believe #1 can be accomplished
   by means of negative pressure (bayesian, dcc, blackhole lists,
   hashcash, etc) on the current e-mail system (smtp, rfc822, mime)?

3. if !#2, then does this same community have any interest in being
   a creative, ambitious force that brings this functionality to
   the masses, or should this work be pursued independently/elsewhere?

there are other issues, like whether there has to be a flag day for e-mail
and whether gateways into/outof "old style e-mail" can exist, but frankly
those are details which won't matter (to this mailing list) if the answers
to the above continue to be "not really", "well probably" and "elsewhere"
as they have been since may 25 when i entered this thread.
-- 
Paul Vixie



From owner-ietf@ietf.org  Sun Jun  8 03:41:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15922
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 03:41:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OugP-0007dv-K6
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 03:33:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Oucu-0007Zd-Np
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 03:30:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15749
	for <ietf@ietf.org>; Sun, 8 Jun 2003 03:30:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ouaz-0001Zo-00
	for ietf@ietf.org; Sun, 08 Jun 2003 03:28:05 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ouay-0001ZZ-00
	for ietf@ietf.org; Sun, 08 Jun 2003 03:28:04 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 0C8FD13969; Sun,  8 Jun 2003 07:29:33 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <5680498000.20030607072812@brandenburg.com>
	<20030608043924.GC12736@think>
From: Paul Vixie <vixie@vix.com>
Date: 08 Jun 2003 07:29:32 +0000
In-Reply-To: <20030608043924.GC12736@think>
Message-ID: <g3k7bxowmb.fsf@sa.vix.com>
Lines: 19
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

tytso@mit.edu ("Theodore Ts'o") writes:

> Bare keys will do; consider a system where people keep a list of those
> keys that they will accept mail.  If someone tries to send mail and
> their key is not on the recipient's list, the mail is returned to them
> until they can perform a Hashcash calculation consuming a non-trivial
> amount of CPU time, at which point their key is placed on the
> recipient's list, and the sender can retry to send the message.  If a
> recipient receives SPAM, they simply drop the key of the sender from
> their "ok-to-receive" list.

i think that we could write this up as open source and widely distribute
it and publicize the hell out of it for the rest of our careers without
ever having it become common practice to reject-with-explaination all
e-mail that comes from unauthorized senders.  therefore it can become,
at best, a system that radical and highly technical recipients can use.
we've got a number of those already.  (this one sounds new and better.)
-- 
Paul Vixie



From owner-ietf@ietf.org  Sun Jun  8 05:19:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17196
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 05:19:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OwDR-0002oH-3J
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 05:11:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OvbS-0002cZ-8d
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 04:32:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16511
	for <ietf@ietf.org>; Sun, 8 Jun 2003 04:32:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OvZW-0001rA-00
	for ietf@ietf.org; Sun, 08 Jun 2003 04:30:38 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OvZV-0001r7-00
	for ietf@ietf.org; Sun, 08 Jun 2003 04:30:37 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h588WZ6N059356
	for <ietf@ietf.org>; Sun, 8 Jun 2003 10:32:35 +0200 (CEST)
Message-ID: <028e01c32d98$83487a70$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <200306080053.h580r0Z9010983@calcite.rhyolite.com> <g33cilqr1o.fsf@sa.vix.com>
Subject: Re: Engineering to deal with the social problem of spam
Date: Sun, 8 Jun 2003 10:31:18 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul writes:

> i want the digital equivilent of a peephole
> in my front door so i can ignore the doorbell
> if i don't like what i see.

One of the big problems of spam is that it takes up more than half the total
bandwidth used by e-mail.  If you want a peephole, then all spam must still
be delivered, so that you can examine it and reject it.  That may keep it
out of your mailbox, but the entire network is still being used to route and
deliver it, which seems wasteful.

> i believe, and have always believed, that all
> communications ought to be mutually consensual.

Most human communications do not involve any explicit consent.  They are
initiated by one party and accepted by another.  If a person refuses any
communication to which he has not consented, he spends his life alone.

> plenty, no, *many* are the humans who can reach me
> by digital communications for whom my consent is
> seen as irrelevant (or worse.)

The same is true for your telephone, your postal mailbox, your person on the
street, radio, television, and newspapers.

> my son has been receiving pornographic spam for
> five years, and he just now turned twelve years old.

Another 24 months or so and you may not be the only person examining it.

> did you all who contributed to the creation of
> e-mail as a media believe that it should be "rated R,
> no children under the age of 17 admitted without
> a parent"?

Children are not interested in porn, so spamming them with it isn't nearly
as harmful as their elders would like to believe.  Only adults care about
sex.

> or consider the "e-mail appending" data miners,
> who believe that my consent to receive a magazine
> by postal mail somehow implies my consent to receive
> anything else that publishing conglomerate wants
> to send me by e-mail.

That seems like a rational assumption.  Did you tell them otherwise?

> ... one is sender-paid, the other is not, and my
> consent cannot be implied.

Why not?

> due to accidents of fate, the CIX.NET MX RR points
> at my personal server.  it turns out that there are
> now many millions of valid @COX.NET mailboxes,
> and that through normal error rates i receive
> several dozen misaddressed messages per day, usually
> several of them being microsoft passport ACK's containing
> enough information for me to commit identity theft if i so
> desired.  a lot of the mail is quite personal in
> nature, too.

How do you know the e-mail is quite personal in nature, if you are just
discarding it without reading it?

> is this how we thought e-mail would grow up and meet
> its larger audience?  not me!

It seems pretty inevitable with the increasing use of e-mail, even if it was
not a design goal.

> the current system is utterly laughable and if it
> were proposed apriori it would be laughed out of the room.

No, the current e-mail system works admirably well.  I don't care much for
spam, but the advantages to receiving legitimate e-mail are so great that
I'm not about to sacrifice the latter to eliminate the former.

> ... that which was suitable for polite early adopters
> in the R&E community is completely unsuiable for the full
> global population ...

They why have they embraced it so willingly?

> if we had end-to-end personal certificates that were
> widely deployed and universally presented, it would
> become reasonable to try to wire an smtp listener to
> reject all but certified traffic ...

Maybe, but how would you reduce the bandwidth expended on spam, and the
processor time required to screen for it?

> ... but since pornospammers could and would acquire
> signed certificates, we'd have to do some kind of
> pgp-like kevinbacon-like "degrees of separation"
> logic to find out about trust.

This is sounding more and more complicated.  Why not just use the delete
key?

> it turns out both of those are missing.  and creating
> them is a bigger problem than rewiring smtp would be.

SMTP is pretty much cast in concrete and will likely be with us for decades
to come, at the absolute minimum; so it's best to try to work within it.

> as usual, i would be happiest if someone else would
> take this on: i'm Busy.

No so busy that you don't have time to open spam messages and examine them
to see if they contain pornography, or personal messages to other people, or
the like.

> my goal at the moment is to discover whether the ietf
> possesses a "collective will" and if so, whether it is
> "willing" to take on this much larger problem.  so far
> the answer seems to be not just "no" but "hell no!"

Probably because, in the final analysis, spam is an annoyance, but that's
about all.  Like postal junk mail.




From owner-ietf@ietf.org  Sun Jun  8 05:21:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17376
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 05:21:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OwDR-0002oN-BA
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 05:11:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ovf6-0002cm-9g
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 04:36:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16537
	for <ietf@ietf.org>; Sun, 8 Jun 2003 04:36:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OvdA-0001ro-00
	for ietf@ietf.org; Sun, 08 Jun 2003 04:34:24 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ovd9-0001rl-00
	for ietf@ietf.org; Sun, 08 Jun 2003 04:34:23 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h588aL6N059383
	for <ietf@ietf.org>; Sun, 8 Jun 2003 10:36:21 +0200 (CEST)
Message-ID: <029201c32d99$0a2503b0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <200306080407.h5847iwY018694@calcite.rhyolite.com> <g3of19owwm.fsf@sa.vix.com>
Subject: Re: Engineering to deal with the social problem of spam
Date: Sun, 8 Jun 2003 10:36:21 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul writes:

> 1. does the ietf as a community generally believe
>    that provable mutual consent between a sender and
>    recipient is an achievable (technically) and
>    desireable (by the global user base) goal?

It's certainly achievable technically, since other protocols already do it.
I don't see it as desirable, though, since it would generate more overhead
than spam does, and it would significantly slow and impede e-mail
communication overall.  Additionally, it might take decades for everyone on
the Internet to adopt it, and those who did not would eventually be at a
disadvantage, even if they were not spammers.

> 2. if #1, does this same community believe #1 can be
>    accomplished by means of negative pressure (bayesian,
>    dcc, blackhole lists, hashcash, etc) on the current
>    e-mail system (smtp, rfc822, mime)?

No.

> 3. if !#2, then does this same community have any interest
>    in being a creative, ambitious force that brings this
>    functionality to the masses, or should this work be
>    pursued independently/elsewhere?

Not applicable, given the answer to #2.





From owner-ietf@ietf.org  Sun Jun  8 06:31:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18214
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 06:31:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OxG3-0004Mn-Qh
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 06:18:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OxCG-0004KC-IY
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 06:14:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17980
	for <ietf@ietf.org>; Sun, 8 Jun 2003 06:14:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OxAK-0002IO-00
	for ietf@ietf.org; Sun, 08 Jun 2003 06:12:44 -0400
Received: from tungsten.btinternet.com ([194.73.73.81])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OxAK-0002IL-00
	for ietf@ietf.org; Sun, 08 Jun 2003 06:12:44 -0400
Received: from host217-44-93-88.range217-44.btcentralplus.com ([217.44.93.88] helo=helios)
	by tungsten.btinternet.com with esmtp (Exim 3.22 #23)
	id 19OxCD-0002Jm-00; Sun, 08 Jun 2003 11:14:41 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: <Valdis.Kletnieks@vt.edu>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues 
Date: Sun, 8 Jun 2003 11:11:28 +0100
Message-ID: <002901c32da6$53dd9f00$0100010a@MyHomeLAN.local>
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.2616
In-Reply-To: <200306072334.h57NYMGF005523@turing-police.cc.vt.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>Also, remember that a signature merely proves the signed data and the
>public key were accessible to a computational device at the same time.
>This is a LONG stretch from actually meaning you signed it
intentionally.
>See Schneier's "Secrets and Lies", there's a whole chapter on this
point,
>or just wait till somebody you know gets nailed with the next
>Sobig/Nimda/Klez
>or whatever, and ask if any of the mail they sent out was intentional.
;)

You are telling if someone else was given a certificate in my name and
signed a virus code and distributed it. I would go to jail for it
because it was signed in my name.

I would challenge the law altogether and fill in a complaint against the
government for this.




From owner-ietf@ietf.org  Sun Jun  8 06:36:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18379
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 06:36:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OxPj-0004T0-TM
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 06:28:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OxNH-0004Pz-3F
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 06:26:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18139
	for <ietf@ietf.org>; Sun, 8 Jun 2003 06:26:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OxLL-0002La-00
	for ietf@ietf.org; Sun, 08 Jun 2003 06:24:07 -0400
Received: from zinc.btinternet.com ([194.73.73.148] helo=zinc)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OxLK-0002LX-00
	for ietf@ietf.org; Sun, 08 Jun 2003 06:24:06 -0400
Received: from host217-44-93-88.range217-44.btcentralplus.com ([217.44.93.88] helo=helios)
	by zinc with esmtp (Exim 3.22 #23)
	id 19OxNE-0002qz-00
	for ietf@ietf.org; Sun, 08 Jun 2003 11:26:04 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: <ietf@ietf.org>
Subject: RE: Engineering to deal with the social problem of spam
Date: Sun, 8 Jun 2003 11:22:51 +0100
Message-ID: <003001c32da7$eac986d0$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
In-Reply-To: <029201c32d99$0a2503b0$0a00000a@atkielski.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

One way to deal with is to use a firewall theory.

I contain a list of e-mail address of people.

So if I receive a e-mail, if it is not in my e-mail address list, it is
discarded.

The only problem is e-mail addresses can be faked.

For example, its configuration could be:

Allow <ietf@ietf.org>
Deny <*@*.com>




From owner-ietf@ietf.org  Sun Jun  8 06:47:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18634
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 06:47:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19OxZQ-0005I5-JI
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 06:38:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OxYN-0005BF-Oc
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 06:37:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18509
	for <ietf@ietf.org>; Sun, 8 Jun 2003 06:37:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OxWR-0002SQ-00
	for ietf@ietf.org; Sun, 08 Jun 2003 06:35:35 -0400
Received: from zinc.btinternet.com ([194.73.73.148] helo=zinc)
	by ietf-mx with esmtp (Exim 4.12)
	id 19OxWR-0002SN-00
	for ietf@ietf.org; Sun, 08 Jun 2003 06:35:35 -0400
Received: from host217-44-93-88.range217-44.btcentralplus.com ([217.44.93.88] helo=helios)
	by zinc with esmtp (Exim 3.22 #23)
	id 19OxYL-0004Vq-00; Sun, 08 Jun 2003 11:37:33 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: <Valdis.Kletnieks@vt.edu>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues 
Date: Sun, 8 Jun 2003 11:34:20 +0100
Message-ID: <004301c32da9$85a93e10$0100010a@MyHomeLAN.local>
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.2616
In-Reply-To: <200306072334.h57NYMGF005523@turing-police.cc.vt.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> a digital signature *could* be binding even if it's invalid

If it is legal binding, when if the CA signs my certificate would also
be a legal blinding act? Since a certificate is a document that has a
digital signature.

False certification would make CA in trouble regardless of their
disclaimer.




From owner-ietf@ietf.org  Sun Jun  8 09:06:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20191
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 09:06:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ozg3-0006uv-8C
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 08:53:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OzcA-0006sN-6Z
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 08:49:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19973
	for <ietf@ietf.org>; Sun, 8 Jun 2003 08:49:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Oza9-0002uQ-00
	for ietf@ietf.org; Sun, 08 Jun 2003 08:47:33 -0400
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Oza8-0002uN-00
	for ietf@ietf.org; Sun, 08 Jun 2003 08:47:32 -0400
Received: from syn.hamachi.org (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id 6CAD717939; Sun,  8 Jun 2003 08:49:30 -0400 (EDT)
Received: from syn.hamachi.org (sommerfeld@localhost)
	by syn.hamachi.org (8.12.7+Sun/8.8.8) with ESMTP id h58CnaT8001224;
	Sun, 8 Jun 2003 05:49:36 -0700 (PDT)
Message-Id: <200306081249.h58CnaT8001224@syn.hamachi.org>
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Dave Crocker <dcrocker@brandenburg.com>, Tony Hain <alh-ietf@tndh.net>,
        ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam 
In-Reply-To: Your message of "Sun, 08 Jun 2003 00:39:24 EDT."
             <20030608043924.GC12736@think> 
Reply-To: sommerfeld@orchard.arlington.ma.us
Date: Sun, 08 Jun 2003 05:49:36 -0700
Xender: sommerfeld@syn.hamachi.org
Sender: owner-ietf@ietf.org
Precedence: bulk

> If someone tries to send mail and their key is not on the
> recipient's list, the mail is returned to them until they can
> perform a Hashcash calculation consuming a non-trivial amount of CPU
> time, at which point their key is placed on the recipient's list,
> and the sender can retry to send the message.  

Hashcash has one big problem: worms.    CPU time is free for them..

There are many reports in the press suggesting that spammers are using
worms such as "Jeem" to deploy open relays; they could also use them
to deploy hashcash generators.

						- Bill




From owner-ietf@ietf.org  Sun Jun  8 09:45:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21099
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 09:45:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19P0Ik-0007fi-Ls
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 09:33:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19P0Bd-0007aC-Bi
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 09:26:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20531
	for <ietf@ietf.org>; Sun, 8 Jun 2003 09:26:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19P09h-000377-00
	for ietf@ietf.org; Sun, 08 Jun 2003 09:24:17 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19P09f-000374-00
	for ietf@ietf.org; Sun, 08 Jun 2003 09:24:16 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h58DQCcR013743
	for ietf@ietf.org env-from <vjs>;
	Sun, 8 Jun 2003 07:26:12 -0600 (MDT)
Date: Sun, 8 Jun 2003 07:26:12 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306081326.h58DQCcR013743@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <g3of19owwm.fsf@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Paul Vixie <vixie@vix.com>

> > What do you expect me to do?  I won't answer your draft notice
> > "hell no I won't go!" but I'm not going to enlist until I have a
> > glimmer of where you're sailing and what's under the decks.
>
> at this point I'm still looking for the answer to some simple questions.
>
> 1. does the ietf as a community generally believe that provable
>    mutual consent between a sender and recipient is an achievable
>    (technically) and desireable (by the global user base) goal?

What's that about a "community"?  Individuals can believe things, but
communities can only argue.  Communities also don't write code or even
Internet-drafts.  It's also not clear to me what "provable mutual
consent" means.  I suspect it's something other than PGP key servers
or PKI, but I've no clue if it's more interesting than the NSA's
Rainbow Series on Trusted Computer Systems on one hand or the unending
stream of unbreakable military grade one time pad psuedo-random number
based encryption products on the other.


> 2. if #1, does this same community believe #1 can be accomplished
>    by means of negative pressure (bayesian, dcc, blackhole lists,
>    hashcash, etc) on the current e-mail system (smtp, rfc822, mime)?

I see no consensus on what to do about spam and don't believe one is
possible for any of those efforts or any group of them.  It's
possible that something new would fair better, but pigs in pokes are
hard to sell except to those whose opinions are worthless.


> 3. if !#2, then does this same community have any interest in being
>    a creative, ambitious force that brings this functionality to
>    the masses, or should this work be pursued independently/elsewhere?

After passing that through an exhortation filter, I'm left with "should
work be pursued independently/elsewhere?" which is hard to gainsay.

The continuing history of IPng is cautionary for IETF Manhattan-project
style community efforts.

> there are other issues, like whether there has to be a flag day for e-mail
> and whether gateways into/outof "old style e-mail" can exist, but frankly
> those are details which won't matter (to this mailing list) if the answers
> to the above continue to be "not really", "well probably" and "elsewhere"
> as they have been since may 25 when i entered this thread.

The little I've understood is that you've said something about "mutual
consent" and vendors or notaries of the same, which for me evokes
"like Verisign?" and a little more best unsaid.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sun Jun  8 10:08:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22189
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 10:08:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19P0gw-0008R6-M8
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 09:58:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19P0dr-0008Nz-Nz
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 09:55:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21327
	for <ietf@ietf.org>; Sun, 8 Jun 2003 09:55:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19P0bv-0003L4-00
	for ietf@ietf.org; Sun, 08 Jun 2003 09:53:27 -0400
Received: from smtp018.mail.yahoo.com ([216.136.174.115])
	by ietf-mx with smtp (Exim 4.12)
	id 19P0bu-0003L1-00
	for ietf@ietf.org; Sun, 08 Jun 2003 09:53:26 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 8 Jun 2003 13:55:24 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'Anthony Atkielski'" <anthony@atkielski.com>
Cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: Engineering to deal with the social problem of spam
Date: Sun, 8 Jun 2003 15:55:13 +0200
Organization: Internet Society
Message-ID: <001601c32dc5$99a6ab70$a700a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <028e01c32d98$83487a70$0a00000a@atkielski.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

=>-----Original Message-----
=>From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On 
=>Behalf Of Anthony Atkielski

(...)
=>
=>Children are not interested in porn, so spamming them with it 
=>isn't nearly as harmful as their elders would like to 
=>believe.  Only adults care about sex.
=>
(...)

Anthony,

This sounds quite dangerous a way of thinking to me. And proven to be quite
erroneous : look at how the cigarette manufacturers focus on youth as the
ideal target for advertising. They know they must attack them very young to
bind them on the long run and make them addicted customers later, when they
are grown-up.

So, in short : *maybe* only adults care about cigarettes and sex (not sure
of), but I think both are - or could be - the target of choice for
advertisers, because it seems that when you catch them young enough, you
create a bigger, deeper addiction.

E.T.

P.S.: and it appears to be similar with alcohol, candies, cars, computers,
drugs, gambling, guns, pets, etc.





From owner-ietf@ietf.org  Sun Jun  8 10:23:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23031
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 10:23:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19P0qd-00040i-38
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 10:08:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19P0p2-0003WH-M2
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 10:07:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21992
	for <ietf@ietf.org>; Sun, 8 Jun 2003 10:06:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19P0n6-0003QZ-00
	for ietf@ietf.org; Sun, 08 Jun 2003 10:05:00 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19P0n5-0003QW-00
	for ietf@ietf.org; Sun, 08 Jun 2003 10:04:59 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h58E6voY062337
	for <ietf@ietf.org>; Sun, 8 Jun 2003 16:06:57 +0200 (CEST)
Message-ID: <03c901c32dc7$3952dee0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <001601c32dc5$99a6ab70$a700a8c0@tomson.be>
Subject: Re: Engineering to deal with the social problem of spam
Date: Sun, 8 Jun 2003 16:06:57 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric writes:

> This sounds quite dangerous a way of thinking to me.

Nothing particularly dangerous about it.  Adults seem to readily forget that
they were completely uninterested in sex prior to puberty; things sexual
(including pornography) were nothing more than curiosities that rapidly
became boring on those rare occasions when they were encountered.  Adults
have a built-in obsession with sex; prepubescent children do not.

It's rather like gambling addicts assuming that anyone who walks past a
casino cannot resist running in and squandering his life's savings on
gambling.  That may well be a danger for gambling addicts, but it is not a
danger for anyone else, and in fact the addict is just projecting his own
behavior and preoccupations onto others.  Thus, the general public doesn't
need to be kept away from casinos, because most people don't care about
casinos, anyway--even though gambling addicts may behave self-destructively
when exposed to casino activity.

> And proven to be quite erroneous ...

I'm not aware of any invalidation of this principle, and it is regularly
confirmed.

> ... look at how the cigarette manufacturers focus on
> youth as the ideal target for advertising.

Sex and cigarettes are not the same thing.  Nobody is interested in sex
prior to puberty; everyone is interested in it after puberty.  In contrast,
an interest in cigarettes is strictly acquired, and in fact must be
explicitly sought out, since smoking is not by nature a pleasant activity at
any age.

> They know they must attack them very young to
> bind them on the long run and make them addicted
> customers later, when they are grown-up.

There is no need to "attack" youngsters with pornography; they will become
potential consumers at puberty, whether they are exposed to it prior to that
age or not.  And conversely, they won't care about pornography until they
reach puberty--they'll just see it as something icky and boring, if they run
across it at all.

> So, in short : *maybe* only adults care about cigarettes
> and sex (not sure of), but I think both are - or could be
> - the target of choice for advertisers, because it seems
> that when you catch them young enough, you
> create a bigger, deeper addiction.

No spammers are deliberately advertising porn to children; apart from legal
risks, it's a waste of time, rather like advertising refrigerators to
Eskimos.  They are trying to spam _adults_ with porn ads.  And given how
much traffic on the Internet is dedicated to porn, they probably get quite a
return on their investment--from the grown-ups, not from kids.

> P.S.: and it appears to be similar with alcohol,
> candies, cars, computers, drugs, gambling, guns, pets, etc.

None of these have a biological basis.  Sex does.  The distinction is
important.




From owner-ietf@ietf.org  Sun Jun  8 12:04:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24361
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 12:04:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19P2UD-00089M-UV
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 11:53:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19P2Pz-00086L-GD
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 11:49:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24200
	for <ietf@ietf.org>; Sun, 8 Jun 2003 11:49:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19P2O3-0003vT-00
	for ietf@ietf.org; Sun, 08 Jun 2003 11:47:15 -0400
Received: from voo.doo.net ([81.17.45.210])
	by ietf-mx with esmtp (Exim 4.12)
	id 19P2O2-0003vQ-00
	for ietf@ietf.org; Sun, 08 Jun 2003 11:47:14 -0400
Received: from localhost (localhost [127.0.0.1])
	by voo.doo.net (8.12.8/8.12.6) with ESMTP id h58Fn4xd053764;
	Sun, 8 Jun 2003 17:49:07 +0200 (CEST)
	(envelope-from ietf@schneiders.org)
Date: Sun, 8 Jun 2003 17:49:04 +0200 (CEST)
From: Marc Schneiders <ietf@schneiders.org>
To: "vinton g. cerf" <vinton.g.cerf@mci.com>
cc: <ietf@ietf.org>
Subject: Send the problem not to ICANN but to ...  (Was: Re: Engineering to
 deal with the social problem of spam)
In-Reply-To: <5.2.0.9.2.20030607185043.0b913cc8@pop.mcilink.com>
Message-ID: <20030608024114.N44017-100000@voo.doo.net>
X-Preferred-email-to: marc@schneiders.org
X-Organization: Venster (Zeist - NL)
X-URL: http://www.bijt.net/
X-Legal: (c) Marc Schneiders
X-OS: FreeBSD: The Power to Serve
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 7 Jun 2003, at 18:51 [=GMT-0400], vinton g. cerf wrote:

[When I wrote: Send the problem to ICANN.]

> this is NOT an ICANN problem - ICANN has no jurisdiction at the
> email level.
>
> vint cerf
> chairman, ICANN

I was joking of course. A bad joke. Sorry.

"ICANN has no jurisdiction at the email level". Indeed. But who has?
So here is a serious idea, not involving the UN, but some effective
social engineering: Send the problem to Microsoft. Why?

Because a solution against spam I see is a combination of working
reverse DNS (also for dial in connections through DHCP and dynamic
DNS) and turning OutLook into a combined MUA/MTA with blacklist (of IP
numbers) and whitelist (of valid hostnames on the user level)
features. I call this new OutLook: OutPeer, since (most) mail will go
peer-to-peer in my scheme.

I have more to say about this. And since it is not about standards (no
new ones required, I think), and also likely stupid, I will not do it
here. I have put it up at

http://www.outpeer.com/

I appreciate comments to marc@schneiders.org.

-- 
[03] I thank you for your time and interest.
http://logoff.org/




From owner-ietf@ietf.org  Sun Jun  8 13:20:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25786
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 13:20:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19P3en-0000nL-6a
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 13:08:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19P3eI-0000lA-C6
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 13:08:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25371
	for <ietf@ietf.org>; Sun, 8 Jun 2003 13:07:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19P3c2-0004Ic-00
	for ietf@ietf.org; Sun, 08 Jun 2003 13:05:46 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19P3c1-0004IZ-00
	for ietf@ietf.org; Sun, 08 Jun 2003 13:05:45 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id NAA06963;
	Sun, 8 Jun 2003 13:04:30 -0400
Date: Sun, 8 Jun 2003 13:05:47 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Anthony Atkielski <anthony@atkielski.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Engineering to deal with the social problem of spam
In-Reply-To: <028e01c32d98$83487a70$0a00000a@atkielski.com>
Message-ID: <Pine.LNX.4.44.0306081300100.1037-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Sun, 8 Jun 2003, Anthony Atkielski wrote:

> Paul writes:
>
> > i want the digital equivilent of a peephole
> > in my front door so i can ignore the doorbell
> > if i don't like what i see.
>
> One of the big problems of spam is that it takes up more than half the total
> bandwidth used by e-mail.

Which is still practically nothing, compared to the bandwidth consumed by
http (gifs and jpegs), IM (and its picture sharing), (legal) movie and MP3
downloads, and other stuff.

Also, you mentioned something about porn to children. This is already
illegal. If its a Type 1 or Type 2 operation, they are easy to shutdown.
Unfortunately, quite a lot of this type of spam is Type 3 spam, just meant
to shock and annoy, and not meant to really sell porn.

> Probably because, in the final analysis, spam is an annoyance, but that's
> about all.  Like postal junk mail.

Agreed.

		--Dean




From owner-ietf@ietf.org  Sun Jun  8 14:02:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26562
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 14:02:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19P4MK-0003mO-Kb
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 13:53:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19P4Gp-0003hk-NF
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 13:47:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26394
	for <ietf@ietf.org>; Sun, 8 Jun 2003 13:47:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19P4EK-0004aG-00
	for ietf@ietf.org; Sun, 08 Jun 2003 13:45:20 -0400
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19P4EJ-0004aD-00
	for ietf@ietf.org; Sun, 08 Jun 2003 13:45:19 -0400
Received: from [208.54.131.107] (helo=think.thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:DES-CBC3-SHA:168)  (Exim 3.35 #1 (Debian))
	id 19P4G4-0000t2-00; Sun, 08 Jun 2003 13:47:08 -0400
Received: from tytso authenticated as tytso by think.thunk.org with local   (Exim 3.35 #1 (Debian))
	id 19P4G3-0000No-00; Sun, 08 Jun 2003 13:47:07 -0400
Date: Sun, 8 Jun 2003 13:47:07 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: Paul Vixie <vixie@vix.com>
Cc: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
Message-ID: <20030608174706.GA1364@think>
References: <5680498000.20030607072812@brandenburg.com> <20030608043924.GC12736@think> <g3k7bxowmb.fsf@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <g3k7bxowmb.fsf@sa.vix.com>
User-Agent: Mutt/1.5.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sun, Jun 08, 2003 at 07:29:32AM +0000, Paul Vixie wrote:
> tytso@mit.edu ("Theodore Ts'o") writes:
> 
> > Bare keys will do; consider a system where people keep a list of those
> > keys that they will accept mail.  If someone tries to send mail and
> > their key is not on the recipient's list, the mail is returned to them
> > until they can perform a Hashcash calculation consuming a non-trivial
> > amount of CPU time, at which point their key is placed on the
> > recipient's list, and the sender can retry to send the message.  If a
> > recipient receives SPAM, they simply drop the key of the sender from
> > their "ok-to-receive" list.
> 
> i think that we could write this up as open source and widely distribute
> it and publicize the hell out of it for the rest of our careers without
> ever having it become common practice to reject-with-explaination all
> e-mail that comes from unauthorized senders.  therefore it can become,
> at best, a system that radical and highly technical recipients can use.
> we've got a number of those already.  (this one sounds new and better.)

In order for this to work, the request for the Hashcalc calculation
has to be done automatically.  If it requires manual intervention
where the user sees the reject notice and then has to manually take
action --- of course, it's doomed to fail.  So this is something which
would require modification to the MTA's in order for this to work.

The easist way to automate such a scheme would be in the context of
your "replace SMTP" proposal; it's just a matter of using bare keys +
hashcash-style solution, instead of requiring a global PKI.

						- Ted



From owner-ietf@ietf.org  Sun Jun  8 17:57:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01168
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 17:57:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19P7wt-0005QM-Gf
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 17:43:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19P7u2-0005Nn-B7
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 17:40:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00830
	for <ietf@ietf.org>; Sun, 8 Jun 2003 17:40:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19P7s5-0005S6-00
	for ietf@ietf.org; Sun, 08 Jun 2003 17:38:37 -0400
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=localhost)
	by ietf-mx with esmtp (Exim 4.12)
	id 19P7s2-0005Ro-00
	for ietf@ietf.org; Sun, 08 Jun 2003 17:38:35 -0400
Received: by localhost (Postfix, from userid 501)
	id 90BE64B69A; Mon,  9 Jun 2003 09:39:49 +1200 (FJT)
Subject: Re: Certificate / CPS issues
From: Franck Martin <franck@sopac.org>
To: Al Arsenault <aarsenau@bbn.com>
Cc: David Morris <dwm@xpasc.com>, ietf@ietf.org
In-Reply-To: <010801c32c57$29bf84e0$acf42180@arsenaultd2>
References: <Pine.LNX.4.33.0306060922440.26569-100000@egate.xpasc.com>
	 <010801c32c57$29bf84e0$acf42180@arsenaultd2>
Content-Type: multipart/alternative; boundary="=-YbhGhQ/ufv0vYHqn965d"
Organization: SOPAC
Message-Id: <1055108389.2727.10.camel@localhost>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2-3mdk 
Date: 09 Jun 2003 09:39:49 +1200
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-YbhGhQ/ufv0vYHqn965d
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

I suggested a few month ago that the PKI to become gPKI should be
supported by the DNS system by using special DNS records and an ldap
naming scheme.

In short (go in the archive and look for GLOBAL PKI on DNS), I want to
send you an e-mail so I query the DNS with the domain bbn.com and it
reply to me that the PKI for this domain is located at
ldap://computer.bbn.com/ I then query this ldap server to extract your
public key/ certificate. The certificate of the PKI of bbn.com would
have been signed by the PKI of com which would have been signed by the
PKI of the root servers.

The DNS does not carry at any time a certificate (too big)

The DNS here is only offering a location service (small DNS
records/transfers)

Cheers
Franck


On Sat, 2003-06-07 at 06:12, Al Arsenault wrote:

> While I'm in general a fan of PKI, and agree with some of what Phill has to
> say, a number of things should be kept in mind:
> 
> 1 - a number of popular applications have been designed to work a large
> variety of "trusted root" certificates, by default.  For example, I just
> popped up the list of "trusted root certificates" marked trusted by default
> in IEv6.  I probably miscounted, but I got 106.  (YMMV, depending on
> version, or if you use a different browser, or...) From a whole bunch of
> different sources.
> 
> 2 - a number of the entities behind those trusted roots go out of business,
> or become somebody else, or...  A quick quiz, based on the root certs from
> IEv6 (yes, I know the answer to these questions, but I've been working in
> the PKI area for over 15 years - how about most people):
> 
>     - who owns the private keys associated with those 3 "GTE Cyber Trust"
> root certificates?
>     - what is that company doing that will conclude by June 30?
>     - what about the private keys associated with those four "Equifax
> Secure" root certificates?
>     -  there are at least 10 trusted root certificates marked signed by
> "DST".  What happened to DST?
>     - there are six certificates marked as being from "Thawte".  Who's
> "Thawte"?
>     - what about Xcert?
> 



-- 
Franck Martin <franck@sopac.org>
SOPAC

--=-YbhGhQ/ufv0vYHqn965d
Content-Type: text/html; charset=utf-8

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/1.1.8">
</HEAD>
<BODY>
I suggested a few month ago that the PKI to become gPKI should be supported by the DNS system by using special DNS records and an ldap naming scheme.<BR>
<BR>
In short (go in the archive and look for GLOBAL PKI on DNS), I want to send you an e-mail so I query the DNS with the domain bbn.com and it reply to me that the PKI for this domain is located at ldap://computer.bbn.com/ I then query this ldap server to extract your public key/ certificate. The certificate of the PKI of bbn.com would have been signed by the PKI of com which would have been signed by the PKI of the root servers.<BR>
<BR>
The DNS does not carry at any time a certificate (too big)<BR>
<BR>
The DNS here is only offering a location service (small DNS records/transfers)<BR>
<BR>
Cheers<BR>
Franck<BR>
<BR>
<BR>
On Sat, 2003-06-07 at 06:12, Al Arsenault wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE><FONT COLOR="#737373" SIZE="3"><I>While I'm in general a fan of PKI, and agree with some of what Phill has to
say, a number of things should be kept in mind:

1 - a number of popular applications have been designed to work a large
variety of &quot;trusted root&quot; certificates, by default.  For example, I just
popped up the list of &quot;trusted root certificates&quot; marked trusted by default
in IEv6.  I probably miscounted, but I got 106.  (YMMV, depending on
version, or if you use a different browser, or...) From a whole bunch of
different sources.

2 - a number of the entities behind those trusted roots go out of business,
or become somebody else, or...  A quick quiz, based on the root certs from
IEv6 (yes, I know the answer to these questions, but I've been working in
the PKI area for over 15 years - how about most people):

    - who owns the private keys associated with those 3 &quot;GTE Cyber Trust&quot;
root certificates?
    - what is that company doing that will conclude by June 30?
    - what about the private keys associated with those four &quot;Equifax
Secure&quot; root certificates?
    -  there are at least 10 trusted root certificates marked signed by
&quot;DST&quot;.  What happened to DST?
    - there are six certificates marked as being from &quot;Thawte&quot;.  Who's
&quot;Thawte&quot;?
    - what about Xcert?
</I></FONT></PRE>
</BLOCKQUOTE>
<FONT SIZE="3"></FONT><BR>
<PRE><TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
Franck Martin &lt;<A HREF="mailto:franck@sopac.org">franck@sopac.org</A>&gt;<BR>
SOPAC
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-YbhGhQ/ufv0vYHqn965d--



From owner-ietf@ietf.org  Sun Jun  8 19:00:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03145
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 19:00:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19P8o7-00044X-8w
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 18:38:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19P8jz-000420-5v
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 18:34:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02908
	for <ietf@ietf.org>; Sun, 8 Jun 2003 18:34:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19P8i2-0005j1-00
	for ietf@ietf.org; Sun, 08 Jun 2003 18:32:18 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19P8i0-0005iw-00
	for ietf@ietf.org; Sun, 08 Jun 2003 18:32:16 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h58MYFoY066360
	for <ietf@ietf.org>; Mon, 9 Jun 2003 00:34:15 +0200 (CEST)
Message-ID: <03ee01c32e0e$179c87a0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <Pine.LNX.4.44.0306081300100.1037-100000@commander.av8.net>
Subject: Re: Engineering to deal with the social problem of spam
Date: Mon, 9 Jun 2003 00:34:15 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dean writes:

> Which is still practically nothing, compared to the
> bandwidth consumed by http (gifs and jpegs), IM (and
> its picture sharing), (legal) movie and MP3
> downloads, and other stuff.

I know, which is why I specified e-mail bandwidth specifically.  One cannot
say that spam is actually putting a load on network bandwidth, since there
are much greater bandwidth hogs on the Internet

> Also, you mentioned something about porn to children.
> This is already illegal. If its a Type 1 or Type 2
> operation, they are easy to shutdown.

Of course, spammers tend to send to e-mail addresses, not to human beings.
Whoever has access to the mailbox receives the mail.  But I don't see any
reason why pornographers would target children, since their only real market
is adults.

> Unfortunately, quite a lot of this type of spam
> is Type 3 spam, just meant to shock and annoy, and
> not meant to really sell porn.

I don't even know what is Type 1 or Type 3 in my mailbox, since I delete it
all without reading it.




From owner-ietf@ietf.org  Sun Jun  8 19:43:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03656
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 19:43:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19P9dY-0004ru-FD
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 19:31:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19P9Z9-0004pT-VS
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 19:27:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03501
	for <ietf@ietf.org>; Sun, 8 Jun 2003 19:27:08 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19P9XC-0005v7-00
	for ietf@ietf.org; Sun, 08 Jun 2003 19:25:11 -0400
Received: from h80ad2683.async.vt.edu ([128.173.38.131] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19P9XB-0005v4-00
	for ietf@ietf.org; Sun, 08 Jun 2003 19:25:09 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h58NR3DU005328;
	Sun, 8 Jun 2003 19:27:03 -0400
Message-Id: <200306082327.h58NR3DU005328@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Haren Visavadia <haren@btopenworld.com>
Cc: ietf@ietf.org
Subject: Re: Certificate / CPS issues 
In-Reply-To: Your message of "Sun, 08 Jun 2003 11:11:28 BST."
             <002901c32da6$53dd9f00$0100010a@MyHomeLAN.local> 
References: <002901c32da6$53dd9f00$0100010a@MyHomeLAN.local>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_876848228P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sun, 08 Jun 2003 19:27:03 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sun, 08 Jun 2003 11:11:28 BST, you said:

> You are telling if someone else was given a certificate in my name and
> signed a virus code and distributed it. I would go to jail for it
> because it was signed in my name.

Check with a lawyer - and note that the spammers are *already* using things
like Jeem trojans to relay their spam.  If they've got that much of a
foothold on your machine, adding code to sign the spam with your private key
is pretty trivial, really....

> I would challenge the law altogether and fill in a complaint against the
> government for this.

There are any number of good political activism groups that will assist you
with that....

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

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

iD8DBQE+48ZHcC3lWbTT17ARAqXeAKD+BTlQb+k0KpL1s4PfnITvUqHp9QCgsDVc
OTLREd2uRXyb0bo/teLl43U=
=i2Xp
-----END PGP SIGNATURE-----

--==_Exmh_876848228P--



From owner-ietf@ietf.org  Sun Jun  8 19:46:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03817
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 19:46:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19P9kA-0004wb-Pk
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 19:38:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19P9jB-0004uD-3D
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 19:37:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03594
	for <ietf@ietf.org>; Sun, 8 Jun 2003 19:37:29 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19P9hE-0005wc-00
	for ietf@ietf.org; Sun, 08 Jun 2003 19:35:32 -0400
Received: from h80ad2683.async.vt.edu ([128.173.38.131] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19P9hC-0005wZ-00
	for ietf@ietf.org; Sun, 08 Jun 2003 19:35:31 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h58NbPDU005389;
	Sun, 8 Jun 2003 19:37:25 -0400
Message-Id: <200306082337.h58NbPDU005389@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Haren Visavadia <haren@btopenworld.com>
Cc: ietf@ietf.org
Subject: Re: Certificate / CPS issues 
In-Reply-To: Your message of "Sun, 08 Jun 2003 11:34:20 BST."
             <004301c32da9$85a93e10$0100010a@MyHomeLAN.local> 
References: <004301c32da9$85a93e10$0100010a@MyHomeLAN.local>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_879069860P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sun, 08 Jun 2003 19:37:11 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sun, 08 Jun 2003 11:34:20 BST, you said:
> > a digital signature *could* be binding even if it's invalid
> 
> If it is legal binding, when if the CA signs my certificate would also
> be a legal blinding act? Since a certificate is a document that has a
> digital signature.
> 
> False certification would make CA in trouble regardless of their
> disclaimer.

Verisign found that out the hard way with the bogus Microsoft certificate.

The *bigger* problem is that a very high percentage of the private keys out
there are probably stored on one particular series of operating systems that
are well known for their security flaws - and as such, attacking said machines
with malware designed to harvest keys is a high-profit attack.



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

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

iD8DBQE+48incC3lWbTT17ARAmQ9AJwOkaMau+M7Zvac0bqWyCrcyT38rwCgx1jb
OhqcfgxjSn0Hwbn/aEYH83w=
=6RzW
-----END PGP SIGNATURE-----

--==_Exmh_879069860P--



From owner-ietf@ietf.org  Sun Jun  8 20:43:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04944
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 20:43:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PAbT-0006H4-8s
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 20:33:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PAZb-0006Ec-VA
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 20:31:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04690
	for <ietf@ietf.org>; Sun, 8 Jun 2003 20:31:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PAXf-0006FG-00
	for ietf@ietf.org; Sun, 08 Jun 2003 20:29:43 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PAXe-0006F9-00
	for ietf@ietf.org; Sun, 08 Jun 2003 20:29:42 -0400
Received: from mou1wnexc02.verisign.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.9/) with ESMTP id h590VW53000707
        for <ietf@ietf.org>; Sun, 8 Jun 2003 17:31:32 -0700 (PDT)
Received: by mou1wnexc02.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LYL9H3RV>; Sun, 8 Jun 2003 17:31:33 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D21FF@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: Engineering to deal with the social problem of spam 
Date: Sun, 8 Jun 2003 17:31:32 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Paul writes:

>s/mime relies on the x.509 pks industry which in is turn based on the goal
>of enriching a small number of ca's who have to pay for relationships to
>browser/useragent vendors who then make the certs worthwhile

Hmm and the cost of MAPS would be?

It costs money to perform authentication and issue certificates, less than
the amount charged for but the total cost to the end user in terms of time
is still significant and in the case of spam control you have certified the
wrong party.

The party that is generally held responsible for users actions is the ISP,
not the user. So that is the level at which you want to certify, not the end
user. S/MIME is not designed to do the job being proposed here. You want to
hold the ISPs responsible, there is no point in having greater granularity
in your authentication system than you intend to use in the revocation
system.

I don't know what a class 3 cert for an ISP would cost but I would guess
rather less than is charged for MAPS these days.


		Phill






From owner-ietf@ietf.org  Sun Jun  8 21:26:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05733
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 21:26:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PBIv-0007oF-Ry
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 21:18:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PBH1-0007le-Oj
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 21:16:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05633
	for <ietf@ietf.org>; Sun, 8 Jun 2003 21:16:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PBF4-0006X6-00
	for ietf@ietf.org; Sun, 08 Jun 2003 21:14:34 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PBF3-0006X1-00
	for ietf@ietf.org; Sun, 08 Jun 2003 21:14:33 -0400
Received: from mou1wnexc02.verisign.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.9/) with ESMTP id h591GX53003618
        for <ietf@ietf.org>; Sun, 8 Jun 2003 18:16:33 -0700 (PDT)
Received: by mou1wnexc02.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LYL9HP3K>; Sun, 8 Jun 2003 18:16:33 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D2201@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: Certificate / CPS issues 
Date: Sun, 8 Jun 2003 18:16:32 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Lets try a thought experiment. Imagine for a moment someone came to this
forum in 1990 proposing say lossy packet routing could never possibly work
because nobody could rely on such a system, pointing out that the Internet
was minute compared to the telephone system and that therefore the Internet
could never possibly be built. Furthermore the fact that the OSI networking
stack was poorly specified and X.500 would inevitably fail meant that the
Internet could not possibly work.

Imagine what the response would be. Perhaps a pointer to an existence proof?

Perhaps RTFM?

Yes, there are serious problems with the PKIX model, there are also serious
problems with the PGP model. There are even bigger problems with the 'X.500
will come and solve the problems of PKI model'. That is why all the major
PKI vendors have abandonded those models (OK some cling to X.500 but only to
suck up to customers, they don't believe in that stuff any more than I do).

PKI is doing just fine thank you. If you need one to solve a specific
problem it can be done. If you start from the position that any solution
must be entirely costless you will have problems, but if you are realistic
there are solutions that save cost overall.

>> You are telling if someone else was given a certificate in my name and
>> signed a virus code and distributed it. I would go to jail for it
>> because it was signed in my name.

>Check with a lawyer - and note that the spammers are *already* using things
>like Jeem trojans to relay their spam.  If they've got that much of a
>foothold on your machine, adding code to sign the spam with your private
key
>is pretty trivial, really....

IANAL... and neither it appears are you...

According to the ABA digital signature guidelines a digital signature should
create a REBUTTABLE presumption of validity. That is exactly the same as the
standard for a written signature, it is assumed to be valid unless you
affirmatively claim it to be invalid.

You might well have other issues if your machine is cracked and used to
attack someone else. There might be claims of negligence etc. but I am not
aware of such claims being made in cases to date...

The grandmother loses her private key and loses her house thing was analyzed
to death when the laws were being written.

You probably don't want to ever use S/MIME as a mechanism to create
promiscuous contracts. You might however want to use the fact that all your
emails are S/MIME signed to defend yourself against claims that someone
appropriated your signature.

		Phill



From owner-ietf@ietf.org  Sun Jun  8 21:58:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06253
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 21:58:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PBh8-0008R9-2V
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 21:43:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PBf4-0008OQ-DD
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 21:41:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06078
	for <ietf@ietf.org>; Sun, 8 Jun 2003 21:41:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PBd7-0006fH-00
	for ietf@ietf.org; Sun, 08 Jun 2003 21:39:25 -0400
Received: from tx2.citynet.net ([66.118.64.4] helo=tx2.wvinternetservices.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19PBd6-0006fE-00
	for ietf@ietf.org; Sun, 08 Jun 2003 21:39:24 -0400
Received: from a (dhcp-69-43-8-041.park.dialup.citynet.net [69.43.8.41])
	by tx2.wvinternetservices.com (8.12.9/8.12.6=Outbound) with SMTP id h591fBt9009887;
	Sun, 8 Jun 2003 21:41:11 -0400
Message-ID: <000701c32e28$3092c340$29082b45@a>
From: "Bill Cunningham" <billc44@citynet.net>
To: "Theodore Ts'o" <tytso@mit.edu>, "Paul Vixie" <vixie@vix.com>
Cc: <ietf@ietf.org>
References: <5680498000.20030607072812@brandenburg.com> <20030608043924.GC12736@think> <g3k7bxowmb.fsf@sa.vix.com> <20030608174706.GA1364@think>
Subject: Re: Engineering to deal with the social problem of spam
Date: Sun, 8 Jun 2003 21:40:57 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Paul Vixie" <vixie@vix.com>
Cc: <ietf@ietf.org>
Sent: Sunday, June 08, 2003 1:47 PM
Subject: Re: Engineering to deal with the social problem of spam


> On Sun, Jun 08, 2003 at 07:29:32AM +0000, Paul Vixie wrote:
> > tytso@mit.edu ("Theodore Ts'o") writes:
> >
> > > Bare keys will do; consider a system where people keep a list of those
> > > keys that they will accept mail.  If someone tries to send mail and
> > > their key is not on the recipient's list, the mail is returned to them
> > > until they can perform a Hashcash calculation consuming a non-trivial
> > > amount of CPU time, at which point their key is placed on the
> > > recipient's list, and the sender can retry to send the message.  If a
> > > recipient receives SPAM, they simply drop the key of the sender from
> > > their "ok-to-receive" list.
> >
> > i think that we could write this up as open source and widely distribute
> > it and publicize the hell out of it for the rest of our careers without
> > ever having it become common practice to reject-with-explaination all
> > e-mail that comes from unauthorized senders.  therefore it can become,
> > at best, a system that radical and highly technical recipients can use.
> > we've got a number of those already.  (this one sounds new and better.)
>
> In order for this to work, the request for the Hashcalc calculation
> has to be done automatically.  If it requires manual intervention
> where the user sees the reject notice and then has to manually take
> action --- of course, it's doomed to fail.  So this is something which
> would require modification to the MTA's in order for this to work.
>
> The easist way to automate such a scheme would be in the context of
> your "replace SMTP" proposal; it's just a matter of using bare keys +
> hashcash-style solution, instead of requiring a global PKI.
>
> - Ted

Good Idea. Sounds like a Pretty Good Protocol.

>




From owner-ietf@ietf.org  Sun Jun  8 22:06:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06693
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 22:06:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PBvd-0000DF-I0
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 21:58:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PBh9-0008RB-C9
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 21:43:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06109
	for <ietf@ietf.org>; Sun, 8 Jun 2003 21:43:33 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PBfC-0006fl-00
	for ietf@ietf.org; Sun, 08 Jun 2003 21:41:34 -0400
Received: from h80ad2683.async.vt.edu ([128.173.38.131] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19PBfA-0006fi-00
	for ietf@ietf.org; Sun, 08 Jun 2003 21:41:33 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h591hUDU006459;
	Sun, 8 Jun 2003 21:43:30 -0400
Message-Id: <200306090143.h591hUDU006459@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: Certificate / CPS issues 
In-Reply-To: Your message of "Sun, 08 Jun 2003 18:16:32 PDT."
             <2A1D4C86842EE14CA9BC80474919782E0D2201@mou1wnexm02.verisign.com> 
References: <2A1D4C86842EE14CA9BC80474919782E0D2201@mou1wnexm02.verisign.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_924511932P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sun, 08 Jun 2003 21:43:30 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sun, 08 Jun 2003 18:16:32 PDT, "Hallam-Baker, Phillip" <pbaker@verisign.com>  said:

> According to the ABA digital signature guidelines a digital signature should
> create a REBUTTABLE presumption of validity. That is exactly the same as the
> standard for a written signature, it is assumed to be valid unless you
> affirmatively claim it to be invalid.

Yes, I'm sure those guidelines are all well and good and clearly thought out.
The problem is that what actually gets *LEGISLATED* may be a totally different
story - wander over to Ed Felton's www.freedom-to-tinker.org and read up on the
so-called 'Super-DMCA' which has, according to an number of people, made NAT
and firewalls technology illegal in Michigan.

No, I'm *not* a lawyer - but I would be quite surprised if in *no* jurisdictions
did the legislature unwittingly pass equally silly legislation regarding
digital signatures - which is why I said "Check with a lawyer".

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

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

iD8DBQE+4+ZBcC3lWbTT17ARApTQAKCDekQ+pPU30BSk6ZN5MLokdcmhfgCeOrNN
gB7q5XvZKfmrO3S0HHil5Wk=
=aDG7
-----END PGP SIGNATURE-----

--==_Exmh_924511932P--



From owner-ietf@ietf.org  Sun Jun  8 22:16:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06975
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 22:16:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PC5K-0000yL-3j
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 22:08:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PC25-0000Yz-8G
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 22:05:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06602
	for <ietf@ietf.org>; Sun, 8 Jun 2003 22:05:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PC07-0006p3-00
	for ietf@ietf.org; Sun, 08 Jun 2003 22:03:11 -0400
Received: from pigeon.verisign.com ([65.205.251.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PC06-0006oo-00
	for ietf@ietf.org; Sun, 08 Jun 2003 22:03:10 -0400
Received: from mou1wnexc01.verisign.com (verisign.com [65.205.251.53])
        by pigeon.verisign.com (8.12.9/) with ESMTP id h59259uv000754;
        Sun, 8 Jun 2003 19:05:09 -0700 (PDT)
Received: by mou1wnexc01.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LMLGM1QS>; Sun, 8 Jun 2003 19:05:09 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D2202@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Certificate / CPS issues 
Date: Sun, 8 Jun 2003 19:05:09 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

> Yes, I'm sure those guidelines are all well and good and 
> clearly thought out.
> The problem is that what actually gets *LEGISLATED* may be a 
> totally different
> story 

Well why not go and find out rather than raising a theoretical
problem that probably does not exist?

Most of the digital signature legislation was passed four or five
years ago.

	Phill



From owner-ietf@ietf.org  Sun Jun  8 23:29:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08005
	for <ietf-web-archive@odin.ietf.org>; Sun, 8 Jun 2003 23:29:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PD6D-0002AM-4m
	for ietf-list@asgard.ietf.org; Sun, 08 Jun 2003 23:13:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PD2J-000270-SO
	for ietf@asgard.ietf.org; Sun, 08 Jun 2003 23:09:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07811
	for <ietf@ietf.org>; Sun, 8 Jun 2003 23:09:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PD0M-00079n-00
	for ietf@ietf.org; Sun, 08 Jun 2003 23:07:30 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PD0M-00079k-00
	for ietf@ietf.org; Sun, 08 Jun 2003 23:07:30 -0400
Received: (from braden@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h5939Tg13752;
	Sun, 8 Jun 2003 20:09:29 -0700 (PDT)
Date: Sun, 8 Jun 2003 20:09:29 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Message-Id: <200306090309.h5939Tg13752@boreas.isi.edu>
To: ietf@ietf.org, pbaker@verisign.com
Subject: Re: Certificate / CPS issues
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


  *> From owner-ietf@ietf.org  Sun Jun  8 18:27:12 2003
  *> From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
  *> To: "'ietf@ietf.org'" <ietf@ietf.org>
  *> Subject: Re: Certificate / CPS issues 
  *> Date: Sun, 8 Jun 2003 18:16:32 -0700 
  *> MIME-Version: 1.0
  *> X-AntiVirus: scanned by AMaViS 0.2.1
  *> 
  *> Lets try a thought experiment. Imagine for a moment someone came to this
  *> forum in 1990 proposing say lossy packet routing could never possibly work
  *> because nobody could rely on such a system, pointing out that the Internet
  *> was minute compared to the telephone system and that therefore the Internet
  *> could never possibly be built. Furthermore the fact that the OSI networking
  *> stack was poorly specified and X.500 would inevitably fail meant that the
  *> Internet could not possibly work.
  *> 

Actually, in 1990 a vocal set of people *were* saying exactly those
things.

Bob Braden



From owner-ietf@ietf.org  Mon Jun  9 01:40:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09715
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 01:40:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PFCq-0004AB-9r
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 01:28:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PF97-000472-3l
	for ietf@asgard.ietf.org; Mon, 09 Jun 2003 01:24:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09467
	for <ietf@ietf.org>; Mon, 9 Jun 2003 01:24:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PF79-0007Vz-00
	for ietf@ietf.org; Mon, 09 Jun 2003 01:22:39 -0400
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19PF79-0007Vw-00
	for ietf@ietf.org; Mon, 09 Jun 2003 01:22:39 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0.6)
  with ESMTP-TLS id 240565; Mon, 09 Jun 2003 00:24:12 -0500
Message-ID: <3EE41A14.7020609@ehsco.com>
Date: Mon, 09 Jun 2003 00:24:36 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: "Theodore Ts'o" <tytso@mit.edu>
CC: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <5680498000.20030607072812@brandenburg.com> <20030608043924.GC12736@think> <g3k7bxowmb.fsf@sa.vix.com> <20030608174706.GA1364@think>
In-Reply-To: <20030608174706.GA1364@think>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 6/8/2003 12:47 PM Theodore Ts'o wrote:

> In order for this to work, the request for the Hashcalc calculation
> has to be done automatically.  If it requires manual intervention
> where the user sees the reject notice and then has to manually take
> action --- of course, it's doomed to fail.  So this is something which
> would require modification to the MTA's in order for this to work.
>
> The easist way to automate such a scheme would be in the context of
> your "replace SMTP" proposal; it's just a matter of using bare keys +
> hashcash-style solution, instead of requiring a global PKI.

If a key was linked to a sender address, wouldn't that give somebody
everything they'd need to send me mail (just send it as me, since I'm
going to read my own mail even if nobody else does)? What's to prevent a
group of blackhats in the ~Ukraine from having their farm of 3Ghz PCs
generate error responses all day, just to gather keys to sell along with
the associated addresses? How would I replace the key/address pair in all
of the good repositories -- but not the bad ones -- after my key were
compromised, especially if my own delivery server is responding to
requests on my behalf?

Isn't the only way out of this to require senders use certificates that
can be validated, proving that the sender has access to a private key
which roughly corresponds to that address?

I'm in agreement that we don't need a "global PKI" to do any of this. We
only (ha!) need a relatively simple and lightweight way to locate and
retrieve public keys associated with specific resources (additional
vouching systems would be useful but aren't immediately necessary). That
particular problem isn't too tough to solve when limited to a scope that
is somewhat smaller than "global PKI", and I think we'll actually get
something like that relatively quickly. I also think this is mostly a
chicken-and-egg problem at that level, and that we might find both the
chicken and the egg at the same time if we're willing to look a bit.

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




From owner-ietf@ietf.org  Mon Jun  9 05:55:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25529
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 05:55:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PJCq-0005W8-Bs
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 05:44:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PJ4b-0005Qj-2h
	for ietf@asgard.ietf.org; Mon, 09 Jun 2003 05:36:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25291
	for <ietf@ietf.org>; Mon, 9 Jun 2003 05:36:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PJ2c-00013Q-00
	for ietf@ietf.org; Mon, 09 Jun 2003 05:34:14 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PJ2b-000136-00
	for ietf@ietf.org; Mon, 09 Jun 2003 05:34:14 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id CB1941396C; Mon,  9 Jun 2003 09:35:43 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <g3k7bxowmb.fsf@sa.vix.com> <20030608174706.GA1364@think>
From: Paul Vixie <vixie@vix.com>
Date: 09 Jun 2003 09:35:43 +0000
In-Reply-To: <20030608174706.GA1364@think>
Message-ID: <g3ptlnwq34.fsf@sa.vix.com>
Lines: 42
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> > i think that we could write [hashcash] up as open source and widely
> > distribute it and publicize the hell out of it for the rest of our
> > careers without ever having it become common practice to
> > reject-with-explaination all e-mail that comes from unauthorized
> > senders.  therefore it can become, at best, a system that radical and
> > highly technical recipients can use.  we've got a number of those
> > already.  (this one sounds new and better.)
> 
> In order for this to work, the request for the Hashcalc calculation
> has to be done automatically.  If it requires manual intervention
> where the user sees the reject notice and then has to manually take
> action --- of course, it's doomed to fail.  So this is something which
> would require modification to the MTA's in order for this to work.

ah.  then the right way to think about this is "an option for trust" where
one way to "feel the trust" is to know that someone else has performed the
hashcash ritual on your behalf.  this is workable.

> The easist way to automate such a scheme would be in the context of
> your "replace SMTP" proposal; it's just a matter of using bare keys +
> hashcash-style solution, instead of requiring a global PKI.

hashcash-style solutions are prone to computational cost diversity problems,
such that someone you want to exchange e-mail with might still have a 2GHz
32-bit CPU even though 90GHz 64-bit CPU's are what's being sold at that time.
a requirement that someone do some work that takes 1 CPU minute on the fast
(future) CPU's will tend to "lock out" owners of older (current) CPU's.  a
requirement that would only take one CPU minute of time for an older (current)
CPU would "allow in" any spammer who wanted to buy (lots of) modern hardware.

but more germane to the problem at hand is the fact that the community Will
Not Move To A New Protocol if all it offers is hashcash, with or without the
computational cost diversity problems, with or without other problems.  my
children are relatively wise in the ways of the world but the age at which i
want them to have ibcs(*) access is lower than the age at which i'd be
comfortable letting anyone with hashcash in their pocket send us traffic.  so
while hashcash might be a form of trust for some, it wouldn't be one here.
-- 
Paul Vixie

(*) "ibcs" == interpersonal batch communication system, which is my generic
term for "whatever will follow 821/822 email".



From owner-ietf@ietf.org  Mon Jun  9 06:08:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25858
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 06:08:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PJQ6-000616-EZ
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 05:58:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PJNC-0005dJ-Vv
	for ietf@asgard.ietf.org; Mon, 09 Jun 2003 05:55:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25506
	for <ietf@ietf.org>; Mon, 9 Jun 2003 05:55:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PJLF-00017Y-00
	for ietf@ietf.org; Mon, 09 Jun 2003 05:53:29 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PJLE-00017K-00
	for ietf@ietf.org; Mon, 09 Jun 2003 05:53:28 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id B239F1396E; Mon,  9 Jun 2003 09:54:58 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <200306081326.h58DQCcR013743@calcite.rhyolite.com>
From: Paul Vixie <vixie@vix.com>
Date: 09 Jun 2003 09:54:58 +0000
In-Reply-To: <200306081326.h58DQCcR013743@calcite.rhyolite.com>
Message-ID: <g3llwbwp71.fsf@sa.vix.com>
Lines: 72
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> > 1. does the ietf as a community generally believe that provable
> >    mutual consent between a sender and recipient is an achievable
> >    (technically) and desireable (by the global user base) goal?
> 
> What's that about a "community"?  Individuals can believe things, but
> communities can only argue.

that's how it feels, i know.  however, even the most bitterly disappointed
individual contributor to the IPng effort knows that IPv6, warts and all,
could only have come from a "community."  because of the number of adopters
needed to deploy it before it could become relevant, the technology had to
be developed in a sausage factory of some kind.

note that i am not sure that ietf is the right such "community" for ibcs(*)
but i am very sure that it won't get done by a small team working in dark
and quiet and then thrusting a working solution into the spotlight with a
bit "USE ME!" sign painted on it.

> > 2. if #1, does this same community believe #1 can be accomplished
> >    by means of negative pressure (bayesian, dcc, blackhole lists,
> >    hashcash, etc) on the current e-mail system (smtp, rfc822, mime)?
> 
> I see no consensus on what to do about spam and don't believe one is
> possible for any of those efforts or any group of them.  

this isn't about spam, it's about trust.  with MAPS and DCC my early
thoughts were in terms of "disabling nonconsensual communications" and what
i've gone over to in recent years is "enabling consensual communications"
which is not at all as similar as it sounds.

> > 3. if !#2, then does this same community have any interest in being
> >    a creative, ambitious force that brings this functionality to
> >    the masses, or should this work be pursued independently/elsewhere?
> 
> The continuing history of IPng is cautionary for IETF Manhattan-project
> style community efforts.

therein lies the rub.  nothing like DNS or HTTP could be created in the
kind of sausage factory the ietf has become.  there are too many witnesses
now, and too many helpers.  if someone hears that something interesting is
going to be worked on, they join the mailing list and come to meetings
since they're at ietf for the week anyway.  with 750 people on the mailing
list and 300 in every meeting, all actual work stops, or moves into "design
teams" which mimic the IETF of olde (or so i'm told -- my first rfc was in
the 1800 series, so most of the history predates my participation.)

however, i do not consider IPng to be a failure.  it's taking a while to get
deployed, that's true, but at least (unlike DNSSEC) the last flag day has
passed and there are multiple interoperable implementations.

so the choice of whether to do ibcs inside IETF isn't dictated (in either
direction) by what's happened with IPng.

however, the choice to do ibcs outside IETF may be dictated by what's had
to happen with HTML and its related standards.

> The little I've understood is that you've said something about "mutual
> consent" and vendors or notaries of the same, which for me evokes
> "like Verisign?" and a little more best unsaid.

no, not like verisign.  in <g3llwdraz3.fsf@sa.vix.com> i wrote as follows:

| s/mime relies on the x.509 pks industry which in is turn based on the goal
| of enriching a small number of ca's who have to pay for relationships to
| browser/useragent vendors who then make the certs worthwhile.  that can't
| scale and hasn't scaled, other than in the case of server certs.  no way
| will the average user be willing to pay money for a personal cert signing
| if the companies on the list have all spammed them.

sorry to evoke the wrong thing.  i really am trying to be very clear, here.
-- 
Paul Vixie



From owner-ietf@ietf.org  Mon Jun  9 06:16:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26197
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 06:16:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PJZm-0006Aw-Ds
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 06:08:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PJZ2-00068C-GR
	for ietf@asgard.ietf.org; Mon, 09 Jun 2003 06:07:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25823
	for <ietf@ietf.org>; Mon, 9 Jun 2003 06:07:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PJX4-0001EB-00
	for ietf@ietf.org; Mon, 09 Jun 2003 06:05:42 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PJX4-0001E7-00
	for ietf@ietf.org; Mon, 09 Jun 2003 06:05:42 -0400
Received: from mou1wnexc02.verisign.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.9/) with ESMTP id h59A7g53029468;
        Mon, 9 Jun 2003 03:07:42 -0700 (PDT)
Received: by mou1wnexc02.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LYL92CWS>; Mon, 9 Jun 2003 03:07:42 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D2206@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Bob Braden'" <braden@ISI.EDU>, "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: Certificate / CPS issues
Date: Mon, 9 Jun 2003 03:07:41 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

Bob,

Yes I know, but how many of the vocal minority were pointing to the IPv4
addrss space issue as the achillies heel?

Pki works if you know how to make it work. The fact that some in this forum
don't know how to make it work for free does not devalue the concept.

The ietf is doing a good job these days on avoiding insecure protocols. It
is doing a lousy job creating secure protocols that can be used by real
people.

The perfect is the enemy of good security


 -----Original Message-----
From: 	Bob Braden
Sent:	Sun Jun 08 20:09:35 2003
To:	ietf@ietf.org; pbaker@verisign.com
Subject:	Re: Certificate / CPS issues


  *> From owner-ietf@ietf.org  Sun Jun  8 18:27:12 2003
  *> From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
  *> To: "'ietf@ietf.org'" <ietf@ietf.org>
  *> Subject: Re: Certificate / CPS issues 
  *> Date: Sun, 8 Jun 2003 18:16:32 -0700 
  *> MIME-Version: 1.0
  *> X-AntiVirus: scanned by AMaViS 0.2.1
  *> 
  *> Lets try a thought experiment. Imagine for a moment someone came to
this
  *> forum in 1990 proposing say lossy packet routing could never possibly
work
  *> because nobody could rely on such a system, pointing out that the
Internet
  *> was minute compared to the telephone system and that therefore the
Internet
  *> could never possibly be built. Furthermore the fact that the OSI
networking
  *> stack was poorly specified and X.500 would inevitably fail meant that
the
  *> Internet could not possibly work.
  *> 

Actually, in 1990 a vocal set of people *were* saying exactly those
things.

Bob Braden



From owner-ietf@ietf.org  Mon Jun  9 09:30:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04019
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 09:30:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PMPj-0003r4-L8
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 09:10:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Om7k-000733-30
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 18:25:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24532
	for <ietf@ietf.org>; Sat, 7 Jun 2003 18:25:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Om5p-0006Ku-00
	for ietf@ietf.org; Sat, 07 Jun 2003 18:23:21 -0400
Received: from voo.doo.net ([81.17.45.210])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Om5o-0006Kq-00
	for ietf@ietf.org; Sat, 07 Jun 2003 18:23:20 -0400
Received: from localhost (localhost [127.0.0.1])
	by voo.doo.net (8.12.8/8.12.6) with ESMTP id h57MP8C8043248;
	Sun, 8 Jun 2003 00:25:09 +0200 (CEST)
	(envelope-from marc@schneiders.org)
Date: Sun, 8 Jun 2003 00:25:07 +0200 (CEST)
From: Marc Schneiders <marc@schneiders.org>
To: Spencer Dawkins <spencer_dawkins@yahoo.com>
cc: <ietf@ietf.org>
Subject: The spam problem is political (Re: Engineering to deal with the
 social problem of spam)
In-Reply-To: <20030607205731.95478.qmail@web10906.mail.yahoo.com>
Message-ID: <20030608000223.K40603-100000@voo.doo.net>
X-Preferred-email-to: marc@schneiders.org
X-Other-email-to: marc@venster.nl
X-Organization: Venster (Zeist - NL)
X-URL: http://www.bijt.net/
X-SOA: A.ROOT-SERVERS.ORSC.
X-OS: FreeBSD: The Power to Serve
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 7 Jun 2003, at 13:57 [=GMT-0700], Spencer Dawkins wrote:

> Disclaimer: there are people who know more about e-mail than I
> do, and some of them are on this list.

I know absolutely nothing more than the bare minimum needed to keep
sendmail running (so far). That is no reason to stop reading.  If my
idea has some merit, you can stop the spam topic on this list.

Why do people not fill my snail mailbox with junk letters, leaflets?
Because (1) it costs money to print a leaflet and get it distributed.
Also (2) there are (where I live) laws and political deals with
advertizers, that make it a bad idea to use addresses from cd-roms, or
just deliver leaflets to all addresses (direct distribution). If my
mailbox says "NO" I should not get them. And the great thing is, the
Dutch police and justice system can get at those who don't play by the
rules.(*)

Spam costs nothing. Spam comes from all corners of the world, where
the Dutch police doesn't dare to go. And even if they would the Dutch
judges would say it is without their introduction. Spam can only be
fought through a worldwide police and justice system. This cannot by
achieved by an RFC. Send this problem to ICANN.

(*) I know that in theory people could evade being prosecuted in
Holland by sending advertizing letters, using illegal address
databases from Tuvalu and contact addresses for themselves in Libya.
But this doesn't happen.






From owner-ietf@ietf.org  Mon Jun  9 09:40:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04387
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 09:40:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PMPj-0003rA-Pr
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 09:10:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19OmXL-0007h2-O6
	for ietf@asgard.ietf.org; Sat, 07 Jun 2003 18:51:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25083
	for <ietf@ietf.org>; Sat, 7 Jun 2003 18:51:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OmVQ-0006Ub-00
	for ietf@ietf.org; Sat, 07 Jun 2003 18:49:49 -0400
Received: from dgesmtp01.wcom.com ([199.249.16.16])
	by ietf-mx with esmtp (Exim 4.12)
	id 19OmVQ-0006UP-00
	for ietf@ietf.org; Sat, 07 Jun 2003 18:49:48 -0400
Received: from pmismtp05.wcomnet.com ([166.38.62.53])
 by firewall.wcom.com (Iplanet MTA)
 with ESMTP id <0HG400DAYVHEQ7@firewall.wcom.com> for ietf@ietf.org; Sat,
 07 Jun 2003 22:51:14 +0000 (GMT)
Received: from pmismtp05.wcomnet.com by pmismtp05.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HG400501VHE4W@pmismtp05.wcomnet.com>; Sat,
 07 Jun 2003 22:51:14 +0000 (GMT)
Received: from vint.mci.com ([166.50.122.49])
 by pmismtp05.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HG40027FVHCZI@pmismtp05.wcomnet.com>; Sat,
 07 Jun 2003 22:51:14 +0000 (GMT)
Date: Sat, 07 Jun 2003 18:51:09 -0400
From: "vinton g. cerf" <vinton.g.cerf@mci.com>
Subject: Re: The spam problem is political (Re: Engineering to deal with the
 social problem of spam)
In-reply-to: <20030608002613.O40603-100000@voo.doo.net>
X-Sender: vcerf@pop.mcilink.com
To: Marc Schneiders <ietf@schneiders.org>, ietf@ietf.org
Message-id: <5.2.0.9.2.20030607185043.0b913cc8@pop.mcilink.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Content-type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

this is NOT an ICANN problem - ICANN has no jurisdiction at the email
level.

vint cerf
chairman, ICANN

At 12:27 AM 6/8/2003 +0200, Marc Schneiders wrote:
>Spam costs nothing. Spam comes from all corners of the world, where
>the Dutch police doesn't dare to go. And even if they would the Dutch
>judges would say it is without their jurisduction. Spam can only be
>fought through a worldwide police and justice system. This cannot by
>achieved by an RFC. Send this problem to ICANN.

Vint Cerf
SVP Architecture & Technology
MCI
22001 Loudoun County Parkway, F2-4115
Ashburn, VA 20147
703 886 1690 (v806 1690)
703 886 0047 fax
vinton.g.cerf@mci.com
www.mci.com/cerfsup 






From owner-ietf@ietf.org  Mon Jun  9 10:38:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06970
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 10:38:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PNQi-0003B9-O9
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 10:15:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PN9h-0005WJ-5L
	for ietf@asgard.ietf.org; Mon, 09 Jun 2003 09:57:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04883
	for <ietf@ietf.org>; Mon, 9 Jun 2003 09:57:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PN7j-0003gp-00
	for ietf@ietf.org; Mon, 09 Jun 2003 09:55:47 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PN7h-0003gm-00
	for ietf@ietf.org; Mon, 09 Jun 2003 09:55:45 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h59Dvir4001532
	for ietf@ietf.org env-from <vjs>;
	Mon, 9 Jun 2003 07:57:44 -0600 (MDT)
Date: Mon, 9 Jun 2003 07:57:44 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306091357.h59Dvir4001532@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Engineering to deal with the social problem of spam
References: <g3ptlnwq34.fsf@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Paul Vixie <vixie@vix.com>

> ...
> computational cost diversity problems, with or without other problems.  my
> children are relatively wise in the ways of the world but the age at which i
> want them to have ibcs(*) access is lower than the age at which i'd be
> comfortable letting anyone with hashcash in their pocket send us traffic.  so
> while hashcash might be a form of trust for some, it wouldn't be one here.

Why would you trust or even both with "ibcs"?  Why not just configure
your children's mail system to accept only mail that is signed with
any of a handful of cryptographic keys, using S/MIME, PGP, or whatever?

That solution is currently available only to a very few people, but
fixing that needs only modest work in user interfaces and no effort by
the IETF.  Some browser-MUAs can already be used to click on a URL to
add a certificate to a private, trusted list.  What would be wrong with
having the controls on your children's browser-MUAs locked with a
password that only you know, and then visiting the web sites of tour
children's teachers and sites of (the parents of) their peers to add
keys (certificates, or whatever) to a list of trusted senders?


] From: Paul Vixie <vixie@vix.com>

] ...
] > The little I've understood is that you've said something about "mutual
] > consent" and vendors or notaries of the same, which for me evokes
] > "like Verisign?" and a little more best unsaid.
]
] no, not like verisign.  in <g3llwdraz3.fsf@sa.vix.com> i wrote as follows:
]
] | s/mime relies on the x.509 pks industry which in is turn based on the goal
] | of enriching a small number of ca's who have to pay for relationships to
] | browser/useragent vendors who then make the certs worthwhile.  that can't
] | scale and hasn't scaled, other than in the case of server certs.  no way
] | will the average user be willing to pay money for a personal cert signing
] | if the companies on the list have all spammed them.
] ...

That Verisign is an industry pioneer and continuing leader in unsolicited
bulk commercial advertising is irrelevant.  Ethical outfits would not
suffer that problem.  The main problem is what you touched on by
talking about the x.509 pks industry.  The problem with third party
signers, notaries, and so forth is that at the price points that people
will pay in time and effort as well as money, the third parties cannot
do a competent job or anything useful.

People insist on using Outlook and Outlook Express instead of MUAs
that are not designed to be user friendly virus and worm transports.
They can't even be bothered to lock down their "security preferences."
I can't imagine people going to the equivalent of the trouble of
finding an old fashioned notary and paying $3 to get their keys or
whatever registered.

Note that those who know apparently don't trust old fashioned notaries.
Why else does the U.S. stock and bond industry refuse to use ordinary
notarized signatures?  From what I've seen, the few financial institutions
that can certify your signature on a stock certificate or similar
paper work are also ordinary notaries.

The problem is not lack of interest in the IETF, but among users.
Some of us are obsessed with some dangers, but most people have more
balanced views.  Most people don't pay any attention to the current
terrorism color scheme.  They did not buy generators and flee to the
woods to wait for the collapse of civilization due to the Y2K bug.
Only a few people in the military and civilian police prepared for
the great wave of terrorism that was supposed to sweep the nation
during the 1976 Bicentenial celebrations.  (The U.S. Army Reserve unit
in which I was working off my draft dodging was one.)

People who are really vulnerable to "nonconsensual communications"
such as your children can use whitelists to better effect than any
sevices from third parties.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Mon Jun  9 12:41:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11359
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 12:41:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PPQf-0006eD-Km
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 12:23:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PPQF-0006Zi-HD
	for ietf@asgard.ietf.org; Mon, 09 Jun 2003 12:23:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10418
	for <ietf@ietf.org>; Mon, 9 Jun 2003 12:23:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PPOH-0004mP-00
	for ietf@ietf.org; Mon, 09 Jun 2003 12:21:01 -0400
Received: from [202.99.160.5] (helo=mail2)
	by ietf-mx with smtp (Exim 4.12)
	id 19PPOF-0004m0-00
	for ietf@ietf.org; Mon, 09 Jun 2003 12:21:00 -0400
Received: from asgard.ietf.org([132.151.6.40]) by www.heinfo.net(AIMC 2.9.5.2)
	with SMTP id jm03edf44db; Thr, 05 Jun 2003 15:25:06 +0800
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19NpCJ-0007JC-Nm
	for ietf-list@asgard.ietf.org; Thu, 05 Jun 2003 03:30:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Np8j-0007FZ-Su
	for ietf@asgard.ietf.org; Thu, 05 Jun 2003 03:26:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09734
	for <ietf@ietf.org>; Thu, 5 Jun 2003 03:26:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Np6v-0003oF-00
	for ietf@ietf.org; Thu, 05 Jun 2003 03:24:33 -0400
Received: from vrx.net ([216.13.126.22] helo=ns1.vrx.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Np6u-0003oB-00
	for ietf@ietf.org; Thu, 05 Jun 2003 03:24:32 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-128-181.lsanca1.dsl-verizon.net [4.33.128.181])
	by ns1.vrx.net (Postfix) with ESMTP
	id 948C1D2A3; Thu,  5 Jun 2003 03:26:14 -0400 (EDT)
Mime-Version: 1.0
X-Sender: stef@vrx.net
Message-Id: <v04220817bb049d8a2dd4@[192.168.1.14]>
In-Reply-To: <01a101c32add$6d1caa40$0a00000a@atkielski.com>
References: 
 <200306022228.h52MS2gv016239@ginger.lcs.mit.edu><016c01c32960$56b1adb0$461
 24104@eagleswings><16092.51912.740900.110873@thomasm-u1.cisco.com><7066000
 0.1054674804@askvoll.hjemme.alvestrand.no>
 <16093.10524.494835.396218@thomasm-u1.cisco.com>
 <010001c32ac2$934bdb70$afb58742@ssprunk>
 <01a101c32add$6d1caa40$0a00000a@atkielski.com>
Date: Thu, 5 Jun 2003 00:26:06 -0700
To: "Anthony Atkielski" <anthony@atkielski.com>
From: Einar Stefferud <Stef@thor.nma.com>
Subject: Re: authenticated email
Cc: "IETF Discussion" <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

Wow!  What a mighty leap of faith!

Let me offer a different view...  

Stephen's CERT proves that the sender is a person who got a CERT from some CERT provider and has a contract with that provider, but has no contract with Anthony, 
so that when Steven does something bad to Anthony, like snd him some spam, and 
Anthony complains to the CERT provider, the CERT provider is going to say 
"You don't have any contract with us, so we do not owe you anything."

In fact, Anthony might not even be findable because of his holding a CERT, 
because he was able to obtain the CERT with false information.

So, I have to ask why you trust those CERTS.

I don't trust em just because they come with a contract that denies all kinds 
of liabilities in the reliance on or use of those CERTS.

The problem is that I do not trust the transitivity of trust as required by PKI.
This is because I have ever seen proof of trust transitivity.

Show me the proof of it and I will believe it, if your proof stands up!

Cheers...\Stef

At 23:08 +0200 6/4/03, Anthony Atkielski wrote:
>Stephen writes:
>
> > Does my signature on this message make you trust
> > it more than, say, the ten ads you got this morning
> > for Viagra?
>
>Yes.
>
> > Why or why not?
>
>It proves who you are, which means that you expose yourself to a certain
>extent in the event that you do anything inappropriate with your e-mail.
>This implies that your intentions are honorable; and even if they are not,
>the signature makes you easier to track down and take action against.  So it
>makes one feel a bit warmer and fuzzier.
>
>Content-Type: application/x-pkcs7-signature;
>	name="smime.p7s"
>Content-Disposition: attachment;
>	filename="smime.p7s"
>
>Attachment converted: Viking5:smime.p7s (????/----) (00097E08)





From owner-ietf@ietf.org  Mon Jun  9 12:51:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12037
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 12:51:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PPfN-0006yL-Gq
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 12:38:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PPZh-0006nt-CG
	for ietf@asgard.ietf.org; Mon, 09 Jun 2003 12:32:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10875
	for <ietf@ietf.org>; Mon, 9 Jun 2003 12:32:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PPXi-0004qx-00
	for ietf@ietf.org; Mon, 09 Jun 2003 12:30:46 -0400
Received: from rhenium.btinternet.com ([194.73.73.93])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PPXi-0004qu-00
	for ietf@ietf.org; Mon, 09 Jun 2003 12:30:46 -0400
Received: from host217-44-98-3.range217-44.btcentralplus.com ([217.44.98.3] helo=helios)
	by rhenium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19PPZY-0005ca-00; Mon, 09 Jun 2003 17:32:41 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Marc Schneiders'" <marc@schneiders.org>, <ietf@ietf.org>
Subject: RE: The spam problem is political (Re: Engineering to deal with the social problem of spam)
Date: Mon, 9 Jun 2003 17:29:20 +0100
Message-ID: <004401c32ea4$4b2cb040$0100010a@MyHomeLAN.local>
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.2616
In-Reply-To: <20030608000223.K40603-100000@voo.doo.net>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>Spam costs nothing.

It costs you using your bandwidth.




From owner-ietf@ietf.org  Mon Jun  9 13:54:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14122
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 13:54:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PQbQ-0002U7-Ls
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 13:38:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PQX5-0002Nb-Tl
	for ietf@asgard.ietf.org; Mon, 09 Jun 2003 13:34:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13642
	for <ietf@ietf.org>; Mon, 9 Jun 2003 13:34:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PQV7-0005WO-00
	for ietf@ietf.org; Mon, 09 Jun 2003 13:32:09 -0400
Received: from einsteinium.btinternet.com ([194.73.73.147])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PQV6-0005WL-00
	for ietf@ietf.org; Mon, 09 Jun 2003 13:32:09 -0400
Received: from host217-44-98-3.range217-44.btcentralplus.com ([217.44.98.3] helo=helios)
	by einsteinium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19PQWy-0006PA-00; Mon, 09 Jun 2003 18:34:04 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues 
Date: Mon, 9 Jun 2003 18:30:48 +0100
Message-ID: <00b701c32eac$de61a660$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D2201@mou1wnexm02.verisign.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> serious problems with the PGP model. 

PGP model offers a lower risk, since I can choose to trust the claimed
person or not.

I know PGP, may not scale globally.




From owner-ietf@ietf.org  Mon Jun  9 18:25:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23950
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 18:25:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PUtV-0007LN-W9
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 18:13:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PUsT-00072I-J0
	for ietf@asgard.ietf.org; Mon, 09 Jun 2003 18:12:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23432
	for <ietf@ietf.org>; Mon, 9 Jun 2003 18:12:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PUqU-0007QG-00
	for ietf@ietf.org; Mon, 09 Jun 2003 18:10:30 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PUqT-0007QD-00
	for ietf@ietf.org; Mon, 09 Jun 2003 18:10:29 -0400
Received: from mou1wnexc02.verisign.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.9/) with ESMTP id h59MCS53015896;
        Mon, 9 Jun 2003 15:12:28 -0700 (PDT)
Received: by mou1wnexc02.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LYL9JGV9>; Mon, 9 Jun 2003 15:12:28 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D220B@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Haren Visavadia'" <haren@btopenworld.com>,
        "'ietf@ietf.org'"
	 <ietf@ietf.org>
Subject: RE: Certificate / CPS issues 
Date: Mon, 9 Jun 2003 15:12:26 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

Pkix is busy grafting the pgp model on top in the shape of cross
certificates.

I dispute the lower risk claim. You have more control. More control does not
mean less risk.





 -----Original Message-----
From: 	Haren Visavadia
Sent:	Mon Jun 09 10:35:58 2003
To:	'Hallam-Baker, Phillip'; ietf@ietf.org
Subject:	RE: Certificate / CPS issues 

> serious problems with the PGP model. 

PGP model offers a lower risk, since I can choose to trust the claimed
person or not.

I know PGP, may not scale globally.



From owner-ietf@ietf.org  Mon Jun  9 20:46:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26531
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 20:46:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PX5g-0002H9-WF
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 20:34:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PX4j-0002Ep-Sk
	for ietf@asgard.ietf.org; Mon, 09 Jun 2003 20:33:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26333
	for <ietf@ietf.org>; Mon, 9 Jun 2003 20:33:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PX2l-0000Hw-00
	for ietf@ietf.org; Mon, 09 Jun 2003 20:31:19 -0400
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PX2k-0000Hi-00
	for ietf@ietf.org; Mon, 09 Jun 2003 20:31:18 -0400
Received: from inet-vrs-04.redmond.corp.microsoft.com ([157.54.8.149]) by mail4.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Mon, 9 Jun 2003 17:32:49 -0700
Received: from 157.54.8.23 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 09 Jun 2003 17:32:49 -0700
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-hub-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 9 Jun 2003 17:32:49 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 9 Jun 2003 17:32:48 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.82]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3788.0);
	 Mon, 9 Jun 2003 17:32:48 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6940.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: RE: Certificate / CPS issues 
Date: Mon, 9 Jun 2003 17:32:47 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA03A64334@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Certificate / CPS issues 
Thread-Index: AcMu1h9QToGPyiNORkaT2VVLL2i7PwAEO+hg
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 10 Jun 2003 00:32:48.0364 (UTC) FILETIME=[D17FC2C0:01C32EE7]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA26531

> I dispute the lower risk claim. You have more control. More control
does
> not mean less risk.

The PKI and the PGP model both have risks, just different risks. The PGP
model only involves the two parties; it brings the risk that the two
parties misidentify each other.  The PKI model involves a third party,
supposedly trusted by both players; it brings the risk that the third
party may make mistakes, or that the two parties mistakenly assign too
much trust to a third party. Also, any large centralized service is
bound to become a target for government and other entities.

-- Christian Huitema





From owner-ietf@ietf.org  Mon Jun  9 23:24:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29351
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 23:24:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PZcl-0005h0-Q8
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 23:16:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PZYG-0005dp-D7
	for ietf@asgard.ietf.org; Mon, 09 Jun 2003 23:12:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29191
	for <ietf@ietf.org>; Mon, 9 Jun 2003 23:11:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PZWH-00013k-00
	for ietf@ietf.org; Mon, 09 Jun 2003 23:09:57 -0400
Received: from pigeon.verisign.com ([65.205.251.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PZWG-00013h-00
	for ietf@ietf.org; Mon, 09 Jun 2003 23:09:56 -0400
Received: from mou1wnexc01.verisign.com (verisign.com [65.205.251.53])
        by pigeon.verisign.com (8.12.9/) with ESMTP id h5A3Bvuv022065;
        Mon, 9 Jun 2003 20:11:57 -0700 (PDT)
Received: by mou1wnexc01.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LMLG3SJA>; Mon, 9 Jun 2003 20:11:57 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D220C@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Christian Huitema'" <huitema@windows.microsoft.com>,
        "'ietf@ietf.org'"
	 <ietf@ietf.org>
Subject: RE: Certificate / CPS issues 
Date: Mon, 9 Jun 2003 20:11:56 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

Number of steps is not a determinant of security.

Strength of each step and of the agregate chain is what matters.

Strength comes from discipline and process.

The surest way to create insecurity is to fear everything you cannot control



 -----Original Message-----
From: 	Christian Huitema
Sent:	Mon Jun 09 17:32:51 2003
To:	Hallam-Baker, Phillip; ietf@ietf.org
Subject:	RE: Certificate / CPS issues 

> I dispute the lower risk claim. You have more control. More control
does
> not mean less risk.

The PKI and the PGP model both have risks, just different risks. The PGP
model only involves the two parties; it brings the risk that the two
parties misidentify each other.  The PKI model involves a third party,
supposedly trusted by both players; it brings the risk that the third
party may make mistakes, or that the two parties mistakenly assign too
much trust to a third party. Also, any large centralized service is
bound to become a target for government and other entities.

-- Christian Huitema




From owner-ietf@ietf.org  Mon Jun  9 23:53:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29840
	for <ietf-web-archive@odin.ietf.org>; Mon, 9 Jun 2003 23:53:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PZy0-0006L3-U2
	for ietf-list@asgard.ietf.org; Mon, 09 Jun 2003 23:38:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PZw7-0006IM-F2
	for ietf@asgard.ietf.org; Mon, 09 Jun 2003 23:36:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29627
	for <ietf@ietf.org>; Mon, 9 Jun 2003 23:36:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PZu8-0001BX-00
	for ietf@ietf.org; Mon, 09 Jun 2003 23:34:36 -0400
Received: from vrx.net ([216.13.126.22] helo=ns1.vrx.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19PZu7-0001BU-00
	for ietf@ietf.org; Mon, 09 Jun 2003 23:34:35 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-128-181.lsanca1.dsl-verizon.net [4.33.128.181])
	by ns1.vrx.net (Postfix) with ESMTP
	id DE13DD370; Mon,  9 Jun 2003 23:36:35 -0400 (EDT)
Mime-Version: 1.0
X-Sender: steflist@vrx.net
Message-Id: <v04220800bb0b024a1f84@[192.168.1.14]>
In-Reply-To: 
 <2A1D4C86842EE14CA9BC80474919782E0D220C@mou1wnexm02.verisign.com>
References: 
 <2A1D4C86842EE14CA9BC80474919782E0D220C@mou1wnexm02.verisign.com>
Date: Mon, 9 Jun 2003 20:36:32 -0700
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Einar Stefferud <Steflist@thor.nma.com>
Subject: RE: Certificate / CPS issues
Cc: <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

Seems to me that if it is a chain (?) ...
Then it is only as strong as its weakest link, which ever link it might be...\Stef

At 20:11 -0700 6/9/03, Hallam-Baker, Phillip wrote:
>Number of steps is not a determinant of security.
>
>Strength of each step and of the agregate chain is what matters.
>
>Strength comes from discipline and process.
>
>The surest way to create insecurity is to fear everything you cannot control
>
>
>
> -----Original Message-----
>From: 	Christian Huitema
>Sent:	Mon Jun 09 17:32:51 2003
>To:	Hallam-Baker, Phillip; ietf@ietf.org
>Subject:	RE: Certificate / CPS issues 
>
> > I dispute the lower risk claim. You have more control. More control
>does
> > not mean less risk.
>
>The PKI and the PGP model both have risks, just different risks. The PGP
>model only involves the two parties; it brings the risk that the two
>parties misidentify each other.  The PKI model involves a third party,
>supposedly trusted by both players; it brings the risk that the third
>party may make mistakes, or that the two parties mistakenly assign too
>much trust to a third party. Also, any large centralized service is
>bound to become a target for government and other entities.
>
>-- Christian Huitema




From owner-ietf@ietf.org  Tue Jun 10 00:58:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01083
	for <ietf-web-archive@odin.ietf.org>; Tue, 10 Jun 2003 00:58:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Pax6-0000Bd-BE
	for ietf-list@asgard.ietf.org; Tue, 10 Jun 2003 00:41:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Paqz-0008MC-FG
	for ietf@asgard.ietf.org; Tue, 10 Jun 2003 00:35:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00732
	for <ietf@ietf.org>; Tue, 10 Jun 2003 00:35:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pap0-0001PV-00
	for ietf@ietf.org; Tue, 10 Jun 2003 00:33:22 -0400
Received: from pigeon.verisign.com ([65.205.251.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Paoz-0001PS-00
	for ietf@ietf.org; Tue, 10 Jun 2003 00:33:21 -0400
Received: from mou1wnexc01.verisign.com (verisign.com [65.205.251.53])
        by pigeon.verisign.com (8.12.9/) with ESMTP id h5A4ZMuv028055;
        Mon, 9 Jun 2003 21:35:22 -0700 (PDT)
Received: by mou1wnexc01.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LMLG3VPJ>; Mon, 9 Jun 2003 21:35:22 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D220E@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Einar Stefferud'" <Steflist@thor.nma.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
Date: Mon, 9 Jun 2003 21:35:22 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

That depends how you connect the links.

A serial chain is only as strong as its weakest link.


Metaphor is no substitute for analysis, as stephen jay gould frequently
obsered humans are poor judges of probability

 -----Original Message-----
From: 	Einar Stefferud
Sent:	Mon Jun 09 20:38:27 2003
To:	Hallam-Baker, Phillip
Cc:	ietf@ietf.org
Subject:	RE: Certificate / CPS issues

Seems to me that if it is a chain (?) ...
Then it is only as strong as its weakest link, which ever link it might
be...\Stef

At 20:11 -0700 6/9/03, Hallam-Baker, Phillip wrote:
>Number of steps is not a determinant of security.
>
>Strength of each step and of the agregate chain is what matters.
>
>Strength comes from discipline and process.
>
>The surest way to create insecurity is to fear everything you cannot
control
>
>
>
> -----Original Message-----
>From: 	Christian Huitema
>Sent:	Mon Jun 09 17:32:51 2003
>To:	Hallam-Baker, Phillip; ietf@ietf.org
>Subject:	RE: Certificate / CPS issues 
>
> > I dispute the lower risk claim. You have more control. More control
>does
> > not mean less risk.
>
>The PKI and the PGP model both have risks, just different risks. The PGP
>model only involves the two parties; it brings the risk that the two
>parties misidentify each other.  The PKI model involves a third party,
>supposedly trusted by both players; it brings the risk that the third
>party may make mistakes, or that the two parties mistakenly assign too
>much trust to a third party. Also, any large centralized service is
>bound to become a target for government and other entities.
>
>-- Christian Huitema



From owner-ietf@ietf.org  Tue Jun 10 03:10:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15462
	for <ietf-web-archive@odin.ietf.org>; Tue, 10 Jun 2003 03:10:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Pd5J-0000mX-OX
	for ietf-list@asgard.ietf.org; Tue, 10 Jun 2003 02:58:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Pcuu-0000er-JB
	for ietf@asgard.ietf.org; Tue, 10 Jun 2003 02:47:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15079
	for <ietf@ietf.org>; Tue, 10 Jun 2003 02:47:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pcsv-0002OI-00
	for ietf@ietf.org; Tue, 10 Jun 2003 02:45:33 -0400
Received: from vrx.net ([216.13.126.22] helo=ns1.vrx.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pcsu-0002OF-00
	for ietf@ietf.org; Tue, 10 Jun 2003 02:45:32 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-128-181.lsanca1.dsl-verizon.net [4.33.128.181])
	by ns1.vrx.net (Postfix) with ESMTP
	id A5791D270; Tue, 10 Jun 2003 02:47:30 -0400 (EDT)
Mime-Version: 1.0
X-Sender: steflist@vrx.net
Message-Id: <v04220800bb0b2ad7bed0@[192.168.1.14]>
In-Reply-To: 
 <2A1D4C86842EE14CA9BC80474919782E0D220E@mou1wnexm02.verisign.com>
References: 
 <2A1D4C86842EE14CA9BC80474919782E0D220E@mou1wnexm02.verisign.com>
Date: Mon, 9 Jun 2003 23:47:25 -0700
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Einar Stefferud <Steflist@thor.nma.com>
Subject: RE: Certificate / CPS issues
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

OK, but in the interests of mutual group understanding, 
lets not call non-chains chains.

So, I must ask the question "When is a chain, not a chain?"

I have never seen a chain that had more than one strand of links.
Tire "chains" are not a chains.  They are a set of chains linked 
together to wrap around a three dimensional tire, which cannot be 
done with a single "chain"?

Do you think that when chains are linked in parallel, with 
multiple paths in parallel, which formed some kind of maze, that 
somehow this makes it not susceptible to our weakest link problem.

By my logic, putting a strong link in parallel with a weak link, 
does nothing to increase the strength of a maze of chains, in terms 
of making it harder to break security.  there still remains a 
weakest path, which uses that path with the weakest link.

So, I suggest we stop messing with such messy use of language and 
begin to agree on the meaning of our words.  So "What is a chain?"

Until we can decide what is a chain, all discussion about chains 
is just a waste of time.

Cheers...\Stef

At 21:35 -0700 6/9/03, Hallam-Baker, Phillip wrote:
>That depends how you connect the links.
>
>A serial chain is only as strong as its weakest link.
>
>
>Metaphor is no substitute for analysis, as stephen jay gould frequently
>obsered humans are poor judges of probability
>
> -----Original Message-----
>From: 	Einar Stefferud
>Sent:	Mon Jun 09 20:38:27 2003
>To:	Hallam-Baker, Phillip
>Cc:	ietf@ietf.org
>Subject:	RE: Certificate / CPS issues
>
>Seems to me that if it is a chain (?) ...
>Then it is only as strong as its weakest link, which ever link it might
>be...\Stef
>
>At 20:11 -0700 6/9/03, Hallam-Baker, Phillip wrote:
> >Number of steps is not a determinant of security.
> >
> >Strength of each step and of the agregate chain is what matters.
> >
> >Strength comes from discipline and process.
> >
> >The surest way to create insecurity is to fear everything you cannot
>control
> >
> >
> >
> > -----Original Message-----
> >From: 	Christian Huitema
> >Sent:	Mon Jun 09 17:32:51 2003
> >To:	Hallam-Baker, Phillip; ietf@ietf.org
> >Subject:	RE: Certificate / CPS issues 
> >
> > > I dispute the lower risk claim. You have more control. More control
> >does
> > > not mean less risk.
> >
> >The PKI and the PGP model both have risks, just different risks. The PGP
> >model only involves the two parties; it brings the risk that the two
> >parties misidentify each other.  The PKI model involves a third party,
> >supposedly trusted by both players; it brings the risk that the third
> >party may make mistakes, or that the two parties mistakenly assign too
> >much trust to a third party. Also, any large centralized service is
> >bound to become a target for government and other entities.
> >
> >-- Christian Huitema




From owner-ietf@ietf.org  Tue Jun 10 04:50:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17357
	for <ietf-web-archive@odin.ietf.org>; Tue, 10 Jun 2003 04:50:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PehC-0002Fr-Pe
	for ietf-list@asgard.ietf.org; Tue, 10 Jun 2003 04:41:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Pec2-00029M-DU
	for ietf@asgard.ietf.org; Tue, 10 Jun 2003 04:36:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17051
	for <ietf@ietf.org>; Tue, 10 Jun 2003 04:36:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pea2-0002ut-00
	for ietf@ietf.org; Tue, 10 Jun 2003 04:34:10 -0400
Received: from carbon.btinternet.com ([194.73.73.92])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pea2-0002up-00
	for ietf@ietf.org; Tue, 10 Jun 2003 04:34:10 -0400
Received: from host217-44-79-148.range217-44.btcentralplus.com ([217.44.79.148] helo=helios)
	by carbon.btinternet.com with esmtp (Exim 3.22 #23)
	id 19Pebz-000223-00; Tue, 10 Jun 2003 09:36:11 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues 
Date: Tue, 10 Jun 2003 09:32:54 +0100
Message-ID: <000501c32f2a$e3dc8dc0$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
Importance: Normal
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D220B@mou1wnexm02.verisign.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The risk is reduced by starting with an empty keystore, when I have
enough trust in the person then I added the person. When the trust is
comprised, I remove the person. And before using my private key, I must
enter a pass phrase as the private key is encrypted with this pass
phrase.

In X.509, it gives me a keystore with lots of certificates that I may
not be able to trust. How do trust these certificates?

I can not simply, they could be fake, and there is no establishment of
trust, especially if the keystore component is written by Microsoft.

"Make a determination in your mind whether this key actually belongs to
the person whom you think it belongs to, based on available evidence."




From owner-ietf@ietf.org  Tue Jun 10 04:51:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17534
	for <ietf-web-archive@odin.ietf.org>; Tue, 10 Jun 2003 04:51:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Pej1-0002Pp-Ep
	for ietf-list@asgard.ietf.org; Tue, 10 Jun 2003 04:43:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Peeq-0002FZ-Ii
	for ietf@asgard.ietf.org; Tue, 10 Jun 2003 04:39:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17138
	for <ietf@ietf.org>; Tue, 10 Jun 2003 04:39:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pecr-0002vn-00
	for ietf@ietf.org; Tue, 10 Jun 2003 04:37:05 -0400
Received: from carbon.btinternet.com ([194.73.73.92])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pecq-0002vk-00
	for ietf@ietf.org; Tue, 10 Jun 2003 04:37:04 -0400
Received: from host217-44-79-148.range217-44.btcentralplus.com ([217.44.79.148] helo=helios)
	by carbon.btinternet.com with esmtp (Exim 3.22 #23)
	id 19Peeo-0002VN-00; Tue, 10 Jun 2003 09:39:06 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues 
Date: Tue, 10 Jun 2003 09:35:50 +0100
Message-ID: <000601c32f2b$4c5c9160$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
Importance: Normal
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D220B@mou1wnexm02.verisign.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>You have more control. More control does not
> mean less risk.

You can not gain trust by someone showing me a certificate.

Trust is something that has to be controlled by the user and not trust
chains in the certificate.




From owner-ietf@ietf.org  Tue Jun 10 07:04:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19998
	for <ietf-web-archive@odin.ietf.org>; Tue, 10 Jun 2003 07:04:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Pgoo-0004KO-34
	for ietf-list@asgard.ietf.org; Tue, 10 Jun 2003 06:57:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PghO-0004HZ-1G
	for ietf@asgard.ietf.org; Tue, 10 Jun 2003 06:49:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19810
	for <ietf@ietf.org>; Tue, 10 Jun 2003 06:49:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PgfN-0003bi-00
	for ietf@ietf.org; Tue, 10 Jun 2003 06:47:49 -0400
Received: from rhenium.btinternet.com ([194.73.73.93])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PgfN-0003bf-00
	for ietf@ietf.org; Tue, 10 Jun 2003 06:47:49 -0400
Received: from host217-44-79-148.range217-44.btcentralplus.com ([217.44.79.148] helo=helios)
	by rhenium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19PghJ-000549-00; Tue, 10 Jun 2003 11:49:49 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, <ietf@ietf.org>
Subject: RE: Certificate / CPS issues 
Date: Tue, 10 Jun 2003 11:46:32 +0100
Message-ID: <000001c32f3d$8efc5d40$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
Importance: Normal
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D220B@mou1wnexm02.verisign.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>You have more control. More control does not
>mean less risk.

Control is needed in risk management.




From owner-ietf@ietf.org  Tue Jun 10 07:26:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20489
	for <ietf-web-archive@odin.ietf.org>; Tue, 10 Jun 2003 07:26:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ph8u-0004zK-7O
	for ietf-list@asgard.ietf.org; Tue, 10 Jun 2003 07:18:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ph8d-0004ws-FF
	for ietf@asgard.ietf.org; Tue, 10 Jun 2003 07:18:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20367
	for <ietf@ietf.org>; Tue, 10 Jun 2003 07:18:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ph6d-0003mG-00
	for ietf@ietf.org; Tue, 10 Jun 2003 07:15:59 -0400
Received: from rhenium.btinternet.com ([194.73.73.93])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ph6d-0003mD-00
	for ietf@ietf.org; Tue, 10 Jun 2003 07:15:59 -0400
Received: from host217-44-79-148.range217-44.btcentralplus.com ([217.44.79.148] helo=helios)
	by rhenium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19Ph8b-0001XA-00
	for ietf@ietf.org; Tue, 10 Jun 2003 12:18:01 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: <ietf@ietf.org>
Subject: RE: Certificate / CPS issues 
Date: Tue, 10 Jun 2003 12:14:44 +0100
Message-ID: <000101c32f41$7f6bb250$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
Importance: Normal
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D220B@mou1wnexm02.verisign.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Christian Huitema wrote:
> The PKI and the PGP model both have risks, just different risks. The
PGP
> model only involves the two parties; it brings the risk that the two
> parties misidentify each other.  The PKI model involves a third party,
> supposedly trusted by both players; it brings the risk that the third
> party may make mistakes, or that the two parties mistakenly assign too
> much trust to a third party. Also, any large centralized service is
> bound to become a target for government and other entities.

Absolutely!

The risk is narrower in PGP.

We have already had a case were the third-party made a mistake. 

Some CA has sold their private key to get out of bankruptcy.




From owner-ietf@ietf.org  Tue Jun 10 10:14:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02159
	for <ietf-web-archive@odin.ietf.org>; Tue, 10 Jun 2003 10:14:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PjCg-0001lH-79
	for ietf-list@asgard.ietf.org; Tue, 10 Jun 2003 09:30:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Pi2r-0005zZ-Pu
	for ietf@asgard.ietf.org; Tue, 10 Jun 2003 08:16:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22972
	for <ietf@ietf.org>; Tue, 10 Jun 2003 08:16:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pi0r-0004IO-00
	for ietf@ietf.org; Tue, 10 Jun 2003 08:14:05 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pi0r-0004IL-00
	for ietf@ietf.org; Tue, 10 Jun 2003 08:14:05 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h5ACG6oY085588
	for <ietf@ietf.org>; Tue, 10 Jun 2003 14:16:06 +0200 (CEST)
Message-ID: <05f501c32f4a$11ca6cb0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000501c32f2a$e3dc8dc0$0100010a@MyHomeLAN.local>
Subject: Re: Certificate / CPS issues 
Date: Tue, 10 Jun 2003 14:16:06 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Haren writes:

> I can not simply, they could be fake, and there
> is no establishment of trust, especially if the
> keystore component is written by Microsoft.

Why are keystore components written by Microsoft peculiarly unworthy of
trust?




From owner-ietf@ietf.org  Tue Jun 10 12:31:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07995
	for <ietf-web-archive@odin.ietf.org>; Tue, 10 Jun 2003 12:31:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Plt8-00070Z-PR
	for ietf-list@asgard.ietf.org; Tue, 10 Jun 2003 12:22:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Pljj-0006k4-2v
	for ietf@asgard.ietf.org; Tue, 10 Jun 2003 12:12:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07201
	for <ietf@ietf.org>; Tue, 10 Jun 2003 12:12:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Plhi-00000U-00
	for ietf@ietf.org; Tue, 10 Jun 2003 12:10:35 -0400
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Plhi-00000L-00
	for ietf@ietf.org; Tue, 10 Jun 2003 12:10:34 -0400
Received: from mail5.microsoft.com ([157.54.6.156]) by mail4.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Tue, 10 Jun 2003 09:12:06 -0700
Received: from inet-vrs-06.redmond.corp.microsoft.com ([157.54.6.181]) by mail5.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Tue, 10 Jun 2003 09:12:05 -0700
Received: from 157.54.6.150 by inet-vrs-06.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 10 Jun 2003 09:12:05 -0700
Received: from RED-IMC-04.redmond.corp.microsoft.com ([157.54.2.168]) by inet-hub-05.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 10 Jun 2003 09:12:04 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by RED-IMC-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 10 Jun 2003 09:12:04 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.82]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3788.0);
	 Tue, 10 Jun 2003 09:12:03 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6940.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Certificate / CPS issues 
Date: Tue, 10 Jun 2003 09:12:01 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA03A644B5@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Certificate / CPS issues 
Thread-Index: AcMvWrLYErUnB4GaT1ewPbyZCIFWxwAD9xmw
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "IETF Discussion" <ietf@ietf.org>
X-OriginalArrivalTime: 10 Jun 2003 16:12:04.0098 (UTC) FILETIME=[08225620:01C32F6B]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA07995

> > I can not simply, they could be fake, and there
> > is no establishment of trust, especially if the
> > keystore component is written by Microsoft.
> 
> Why are keystore components written by Microsoft peculiarly unworthy
of
> trust?

The procedures used to determine the list of certification authorities
in Windows XP, Internet Explorer and other Microsoft products are
documented at:

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/secur
ity/news/rootcert.asp

-- Christian Huitema




From owner-ietf@ietf.org  Tue Jun 10 13:27:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10020
	for <ietf-web-archive@odin.ietf.org>; Tue, 10 Jun 2003 13:27:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PmiI-0000Ci-HK
	for ietf-list@asgard.ietf.org; Tue, 10 Jun 2003 13:15:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Pmbx-0008TZ-Tl
	for ietf@asgard.ietf.org; Tue, 10 Jun 2003 13:08:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09360
	for <ietf@ietf.org>; Tue, 10 Jun 2003 13:08:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PmZx-0000aP-00
	for ietf@ietf.org; Tue, 10 Jun 2003 13:06:37 -0400
Received: from wetware.wetware.com ([199.108.16.1] helo=wetware.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19PmZw-0000a8-00
	for ietf@ietf.org; Tue, 10 Jun 2003 13:06:37 -0400
Received: from 208.177.152.18.ptr.us.xo.net ([208.177.152.18] helo=wetware.com)
	by wetware.com with esmtp (Exim 4.20)
	id 19PmbR-0000Hu-PJ
	for ietf@ietf.org; Tue, 10 Jun 2003 10:08:09 -0700
Date: Tue, 10 Jun 2003 10:08:15 -0700
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: Re: Engineering to deal with the social problem of spam
From: james woodyatt <jhw@wetware.com>
To: IETF list <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <1FE3766C-9B66-11D7-9A9A-000393BA7EBA@wetware.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

everyone--

Here's a silly idea: let's try adding an option for hashcash to APEX.  
(Or has someone already done that?)

If the problem with hashcash is that worms can steal CPU cycles to 
generate hashcash, then let's attack the problem of worms separately 
from the problem of spam suppression.  If the problem with hashcash is 
that poor people are taxed more heavily than rich people for the 
utility of spam suppression, then-- well-- they should upgrade their 
CPU's, now shouldn't they?

And as for those too poor to keep their CPU's current, Let Them Eat 
SMTP.  They clearly have an unhealthy interest in paying to receive 
MAKE MONEY FAST spam, so we should encourage them to continue using 
SMTP anyway.  The Internet interprets censorship as damage and routes 
around it.  Let SMTP continue to serve the useful function it serves: 
carrying spam messages.


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




From owner-ietf@ietf.org  Tue Jun 10 16:51:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17403
	for <ietf-web-archive@odin.ietf.org>; Tue, 10 Jun 2003 16:51:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ppsl-0003sV-Sk
	for ietf-list@asgard.ietf.org; Tue, 10 Jun 2003 16:38:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Pi3W-0005zb-4J
	for ietf@asgard.ietf.org; Tue, 10 Jun 2003 08:16:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22982
	for <ietf@ietf.org>; Tue, 10 Jun 2003 08:16:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pi1W-0004Ii-00
	for ietf@ietf.org; Tue, 10 Jun 2003 08:14:46 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pi1V-0004If-00
	for ietf@ietf.org; Tue, 10 Jun 2003 08:14:45 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h5ACGloY085591
	for <ietf@ietf.org>; Tue, 10 Jun 2003 14:16:47 +0200 (CEST)
Message-ID: <05fe01c32f4a$2a357e20$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000101c32f41$7f6bb250$0100010a@MyHomeLAN.local>
Subject: Re: Certificate / CPS issues 
Date: Tue, 10 Jun 2003 14:16:47 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Haren writes:

> Some CA has sold their private key to get out
> of bankruptcy.

Which one?





From owner-ietf@ietf.org  Tue Jun 10 18:20:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21291
	for <ietf-web-archive@odin.ietf.org>; Tue, 10 Jun 2003 18:20:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PrD5-0001lM-PM
	for ietf-list@asgard.ietf.org; Tue, 10 Jun 2003 18:03:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Pr3s-0007TI-Da
	for ietf@asgard.ietf.org; Tue, 10 Jun 2003 17:53:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19514
	for <ietf@ietf.org>; Tue, 10 Jun 2003 17:53:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pr1r-0002WF-00
	for ietf@ietf.org; Tue, 10 Jun 2003 17:51:43 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pr1r-0002WC-00
	for ietf@ietf.org; Tue, 10 Jun 2003 17:51:43 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19Pr3q-000Dpt-00; Tue, 10 Jun 2003 16:53:46 -0500
Date: Tue, 10 Jun 2003 17:53:46 -0400
From: John C Klensin <john-ietf@jck.com>
To: Christian Huitema <huitema@windows.microsoft.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: RE: Certificate / CPS issues
Message-ID: <112931587.1055267626@p3.JCK.COM>
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA03A644B5@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References:  <DAC3FCB50E31C54987CD10797DA511BA03A644B5@WIN-MSG-10.
 wingroup.windeploy.ntdev.microsoft.com>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Tuesday, 10 June, 2003 09:12 -0700 Christian Huitema 
<huitema@windows.microsoft.com> wrote:

> The procedures used to determine the list of certification
> authorities in Windows XP, Internet Explorer and other
> Microsoft products are documented at:
>
> http://www.microsoft.com/technet/treeview/default.asp?url=/tec
> hnet/security/news/rootcert.asp

Christian,

Others may respond differently, but I found one part of this 
very interesting.  The text says, in part:

	When a user visits a secure Web site (that is, by using
	HTTPS), reads a secure e-mail (that is, S/MIME), or
	downloads an ActiveX control that uses a new root
	certificate, the Windows XP certificate chain
	verification software checks the appropriate Windows
	Update location and downloads the necessary root
	certificate. To the user, the experience is seamless.
	The user does not see any security dialog boxes or
	warnings. The download happens automatically, behind the
	scenes.

Suppose a user has sufficient expertise and desire to make 
individual evaluations of which CA certs to accept and from what 
CAs.  With the earlier model, she could look through the list, 
adding and deleting root certs according to her preferences and 
using Microsoft's acceptance of a given cert as a guide (to 
whatever extent she saw that as appropriate).  Now, if I read 
this correctly, there is no more choice: any cert accepted by 
Microsoft is automatically trusted by the desktop software and 
the user can't say, e.g., "I know that XYZ Corp, who met 
Microsoft's criteria, was just bought out by ABC Corp; I believe 
that ABC are scum and don't want to trust any cert issued by any 
subsidiary of theirs, even if it was issued pre-merger."

Conversely, if I'm part of an enterprise that issues its own 
certs for internal purposes, it doesn't look as if I can make 
those certs usable in the XP environment, since such internal 
certs don't satisfy the "broad business value to Microsoft 
platform customers" criterion and hence will not be accepted by 
Microsoft for use in the specified environment.

I hope this is only part of the story, and that user options to 
accept some certs (even if they are not accepted by Microsoft) 
and reject others (even if they are accepted by Microsoft) still 
exist in some usable form.

regards,
     john






From owner-ietf@ietf.org  Tue Jun 10 19:18:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22430
	for <ietf-web-archive@odin.ietf.org>; Tue, 10 Jun 2003 19:18:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PsDw-000734-7q
	for ietf-list@asgard.ietf.org; Tue, 10 Jun 2003 19:08:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PsDB-0006xF-KV
	for ietf@asgard.ietf.org; Tue, 10 Jun 2003 19:07:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22209
	for <ietf@ietf.org>; Tue, 10 Jun 2003 19:07:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PsBA-0002wO-00
	for ietf@ietf.org; Tue, 10 Jun 2003 19:05:24 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19PsB9-0002wL-00
	for ietf@ietf.org; Tue, 10 Jun 2003 19:05:23 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h5AN7PoY090890
	for <ietf@ietf.org>; Wed, 11 Jun 2003 01:07:25 +0200 (CEST)
Message-ID: <06ba01c32fa5$0e8c2240$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References:  <DAC3FCB50E31C54987CD10797DA511BA03A644B5@WIN-MSG-10. wingroup.windeploy.ntdev.microsoft.com> <112931587.1055267626@p3.JCK.COM>
Subject: Re: Certificate / CPS issues
Date: Wed, 11 Jun 2003 01:07:25 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John writes:

> Now, if I read this correctly, there is no
> more choice ...

You read incorrectly.  Default behavior is not mandatory behavior.

> Conversely, if I'm part of an enterprise that
> issues its own certs for internal purposes, it
> doesn't look as if I can make those certs usable
> in the XP environment, since such internal
> certs don't satisfy the "broad business value to Microsoft
> platform customers" criterion and hence will not be accepted by
> Microsoft for use in the specified environment.

You read incorrectly, again.  You can add any certificates you want to your
machines.  You just can't get Microsoft to make them publicly available for
distribution by MS without convincing them that doing so is worthwhile for
Microsoft, which makes perfect sense.

> I hope this is only part of the story, and that
> user options to accept some certs (even if they are
> not accepted by Microsoft) and reject others (even
> if they are accepted by Microsoft) still
> exist in some usable form.

They do.  Look under Internet Options in Internet Explorer.




From owner-ietf@ietf.org  Tue Jun 10 20:04:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23360
	for <ietf-web-archive@odin.ietf.org>; Tue, 10 Jun 2003 20:04:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PsyV-0008Ew-Qs
	for ietf-list@asgard.ietf.org; Tue, 10 Jun 2003 19:56:23 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Psst-00088d-1j
	for ietf@asgard.ietf.org; Tue, 10 Jun 2003 19:50:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23142
	for <ietf@ietf.org>; Tue, 10 Jun 2003 19:50:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Psqs-0003Cn-00
	for ietf@ietf.org; Tue, 10 Jun 2003 19:48:30 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Psqr-0003Cj-00
	for ietf@ietf.org; Tue, 10 Jun 2003 19:48:29 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19Pssq-000EKw-00; Tue, 10 Jun 2003 18:50:32 -0500
Date: Tue, 10 Jun 2003 19:50:32 -0400
From: John C Klensin <john-ietf@jck.com>
To: Anthony Atkielski <anthony@atkielski.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: Certificate / CPS issues
Message-ID: <119937981.1055274632@p3.JCK.COM>
In-Reply-To: <06ba01c32fa5$0e8c2240$0a00000a@atkielski.com>
References:  <DAC3FCB50E31C54987CD10797DA511BA03A644B5@WIN-MSG-10.
  wingroup.windeploy.ntdev.microsoft.com>
 <112931587.1055267626@p3.JCK.COM>
 <06ba01c32fa5$0e8c2240$0a00000a@atkielski.com>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Anthony,

I asked Christian for a reason.  This appears to be relatively 
new. It isn't clear, from either the article or his note, how 
much of it  is deployed already.    It is linked, the article 
says, to Win XP and not to IE -- there are different procedures, 
it says, for IE under Win 2000, ME and earlier than are proposed 
(apparently going forward) for XP.  It strongly implies that, if 
there are options to control this, they are (will be?) Windows 
options, not (specifically) IE options (although IE might well 
be able to access them).    I don't have a copy of Win XP here, 
much less one with this kit installed, so I have no idea whether 
there is an easily-accessible option that permits turning "ask 
me before installing a cert" on, or what information that 
question provides.  The article might lead a reasonable person 
to believe that those things had been turned off, with no 
options available to the casual user, in the interest of a good 
user experience (something I can certainly make a case for, even 
while preferring that they not do it to me).   But, I don't 
know, which is why I asked.

And, unless you are in a position to speak authoritatively for 
Microsoft,...

    regards,
       john


--On Wednesday, 11 June, 2003 01:07 +0200 Anthony Atkielski 
<anthony@atkielski.com> wrote:

> John writes:
>
>> Now, if I read this correctly, there is no
>> more choice ...
>
> You read incorrectly.  Default behavior is not mandatory
> behavior.
>
>> Conversely, if I'm part of an enterprise that
>> issues its own certs for internal purposes, it
>> doesn't look as if I can make those certs usable
>> in the XP environment, since such internal
>> certs don't satisfy the "broad business value to Microsoft
>> platform customers" criterion and hence will not be accepted
>> by Microsoft for use in the specified environment.
>
> You read incorrectly, again.  You can add any certificates you
> want to your machines.  You just can't get Microsoft to make
> them publicly available for distribution by MS without
> convincing them that doing so is worthwhile for Microsoft,
> which makes perfect sense.
>
>> I hope this is only part of the story, and that
>> user options to accept some certs (even if they are
>> not accepted by Microsoft) and reject others (even
>> if they are accepted by Microsoft) still
>> exist in some usable form.
>
> They do.  Look under Internet Options in Internet Explorer.
>
>







From owner-ietf@ietf.org  Wed Jun 11 01:30:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29613
	for <ietf-web-archive@odin.ietf.org>; Wed, 11 Jun 2003 01:30:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PxvA-0004Xs-Uh
	for ietf-list@asgard.ietf.org; Wed, 11 Jun 2003 01:13:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Pxuk-0004UN-Oi
	for ietf@asgard.ietf.org; Wed, 11 Jun 2003 01:12:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29416
	for <ietf@ietf.org>; Wed, 11 Jun 2003 01:12:49 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pxsj-0004aH-00
	for ietf@ietf.org; Wed, 11 Jun 2003 01:10:45 -0400
Received: from h80ad24d6.async.vt.edu ([128.173.36.214] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pxsh-0004aE-00
	for ietf@ietf.org; Wed, 11 Jun 2003 01:10:44 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h5B5CkKB015314;
	Wed, 11 Jun 2003 01:12:46 -0400
Message-Id: <200306110512.h5B5CkKB015314@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: james woodyatt <jhw@wetware.com>
Cc: IETF list <ietf@ietf.org>
Subject: Re: Engineering to deal with the social problem of spam 
In-Reply-To: Your message of "Tue, 10 Jun 2003 10:08:15 PDT."
             <1FE3766C-9B66-11D7-9A9A-000393BA7EBA@wetware.com> 
References: <1FE3766C-9B66-11D7-9A9A-000393BA7EBA@wetware.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1423899152P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 11 Jun 2003 01:12:45 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Tue, 10 Jun 2003 10:08:15 PDT, james woodyatt <jhw@wetware.com>  said:
> And as for those too poor to keep their CPU's current, Let Them Eat 
> SMTP.  They clearly have an unhealthy interest in paying to receive 
> MAKE MONEY FAST spam, so we should encourage them to continue using 
> SMTP anyway.  The Internet interprets censorship as damage and routes 
> around it.  Let SMTP continue to serve the useful function it serves: 
> carrying spam messages.

Ahem.

I have several million dollars of compute resources at my disposal.
It will take a fairly large hashcash request to make it painful for
me.

There's a *large* number of people still in the 386 world, who are
financially unable to upgrade.  That same hashcash request that will
not inconvenience my hardware will probably kill their box for the
better part of an hour.  You are concluding that they therefor have an
interest in paying to receive spam???

If anything, spam is a *bigger* problem for those on older hardware,
simply because they have fewer computrons available to process it - so
you're basically creating a regressive tax here.

Just because the Internet routes around censorship doesn't mean that
we have the moral right to censor those people who need it the most -
those in underdeveloped countries with repressive regimes.

Just because the Great Firewall of China exists doesn't mean we should
add injury to insult by disenfranchising those who manage to get
around the firewall.

There is junk fax - and the Berlin Wall was brought down by fax machines.

Let's not get this wrong.

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

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

iD8DBQE+5rpNcC3lWbTT17ARAmV0AJ9Jc+9Rg6vC7LXp7hlGgxnKuUtfKgCfdCX8
Z2DsinEpIuAempi0E+2hskY=
=0rjs
-----END PGP SIGNATURE-----

--==_Exmh_1423899152P--



From owner-ietf@ietf.org  Wed Jun 11 01:42:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29903
	for <ietf-web-archive@odin.ietf.org>; Wed, 11 Jun 2003 01:42:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19PyER-0000ef-Vl
	for ietf-list@asgard.ietf.org; Wed, 11 Jun 2003 01:33:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PyC7-0000Pj-AP
	for ietf@asgard.ietf.org; Wed, 11 Jun 2003 01:30:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29636
	for <ietf@ietf.org>; Wed, 11 Jun 2003 01:30:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PyA6-0004d1-00
	for ietf@ietf.org; Wed, 11 Jun 2003 01:28:42 -0400
Received: from wetware.wetware.com ([199.108.16.1] helo=wetware.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19PyA5-0004cq-00
	for ietf@ietf.org; Wed, 11 Jun 2003 01:28:41 -0400
Received: from 208.177.152.18.ptr.us.xo.net ([208.177.152.18] helo=wetware.com)
	by wetware.com with esmtp (Exim 4.20)
	id 19PyBZ-0001VK-W6; Tue, 10 Jun 2003 22:30:14 -0700
Date: Tue, 10 Jun 2003 22:30:20 -0700
Subject: Re: Engineering to deal with the social problem of spam 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: IETF list <ietf@ietf.org>
To: Valdis.Kletnieks@vt.edu
From: james woodyatt <jhw@wetware.com>
In-Reply-To: <200306110512.h5B5CkKB015314@turing-police.cc.vt.edu>
Message-Id: <CABFA38E-9BCD-11D7-8C62-000393BA7EBA@wetware.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Tuesday, Jun 10, 2003, at 22:12 US/Pacific, Valdis.Kletnieks@vt.edu 
wrote:
> [...]
> There's a *large* number of people still in the 386 world, who are
> financially unable to upgrade.  That same hashcash request that will
> not inconvenience my hardware will probably kill their box for the
> better part of an hour.  You are concluding that they therefor have an
> interest in paying to receive spam???

Yup.  I am.

> If anything, spam is a *bigger* problem for those on older hardware,
> simply because they have fewer computrons available to process it - so
> you're basically creating a regressive tax here.

And I'm not going to apologize for proposing it.

Look, the phenomenon of spam is already a regressive tax, in and of 
itself.  I'm just looking for a way to get some useful work done in 
exchange for receiving it.  And I certainly won't mind if someone else 
is interested in paying me for the option to use the result of whatever 
useful work your CPU has to do to get your message in front of my 
eyeballs.

> Just because the Internet routes around censorship doesn't mean that
> we have the moral right to censor those people who need it the most -
> those in underdeveloped countries with repressive regimes.

Who's talking about censorship?  I'm not proposing that we outlaw SMTP.


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




From owner-ietf@ietf.org  Wed Jun 11 03:24:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28132
	for <ietf-web-archive@odin.ietf.org>; Wed, 11 Jun 2003 03:24:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Pzo6-0000VQ-Bm
	for ietf-list@asgard.ietf.org; Wed, 11 Jun 2003 03:14:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19PzlE-0000Rf-JY
	for ietf@asgard.ietf.org; Wed, 11 Jun 2003 03:11:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27903
	for <ietf@ietf.org>; Wed, 11 Jun 2003 03:11:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PzjD-0005V7-00
	for ietf@ietf.org; Wed, 11 Jun 2003 03:09:03 -0400
Received: from tungsten.btinternet.com ([194.73.73.81])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PzjC-0005V4-00
	for ietf@ietf.org; Wed, 11 Jun 2003 03:09:02 -0400
Received: from host217-44-97-250.range217-44.btcentralplus.com ([217.44.97.250] helo=helios)
	by tungsten.btinternet.com with esmtp (Exim 3.22 #23)
	id 19PzlB-0006oZ-00
	for ietf@ietf.org; Wed, 11 Jun 2003 08:11:06 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: <ietf@ietf.org>
Subject: Re: Certificate / CPS issues 
Date: Wed, 11 Jun 2003 08:07:45 +0100
Message-ID: <000101c32fe8$2a53a9b0$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Why are keystore components written by Microsoft peculiarly unworthy
of
> trust?

There was a flaw in IE, although it has been fixed, the flaw allows the
attackers to delete certificates from the keystore without any user
notification.

How can trust IE, it there is some very serious flaws like this one?

You cannot.

Also, have heard about Microsoft's Anti-Trust.




From owner-ietf@ietf.org  Wed Jun 11 03:31:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28325
	for <ietf-web-archive@odin.ietf.org>; Wed, 11 Jun 2003 03:31:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Pzwt-0000cG-R3
	for ietf-list@asgard.ietf.org; Wed, 11 Jun 2003 03:23:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Pztz-0000Yz-88
	for ietf@asgard.ietf.org; Wed, 11 Jun 2003 03:20:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28065
	for <ietf@ietf.org>; Wed, 11 Jun 2003 03:20:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pzrx-0005X9-00
	for ietf@ietf.org; Wed, 11 Jun 2003 03:18:05 -0400
Received: from tungsten.btinternet.com ([194.73.73.81])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Pzrx-0005X6-00
	for ietf@ietf.org; Wed, 11 Jun 2003 03:18:05 -0400
Received: from host217-44-97-250.range217-44.btcentralplus.com ([217.44.97.250] helo=helios)
	by tungsten.btinternet.com with esmtp (Exim 3.22 #23)
	id 19Pztx-0000C7-00
	for ietf@ietf.org; Wed, 11 Jun 2003 08:20:09 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: <ietf@ietf.org>
Subject: Re: Certificate / CPS issues 
Date: Wed, 11 Jun 2003 08:16:50 +0100
Message-ID: <000801c32fe9$6e106700$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Which one?

According to Al Arsenault:

> a number of the entities behind those trusted roots go out of
business, or become somebody else, or...  A quick quiz, > based on the
root certs from IEv6 (yes, I know the answer to these questions, but
I've been working in the PKI area  > for over 15 years - how about most
people):
>
>    - who owns the private keys associated with those 3 "GTE Cyber
Trust" root certificates?
>    - what is that company doing that will conclude by June 30?
>    - what about the private keys associated with those four "Equifax
Secure" root certificates?
>    -  there are at least 10 trusted root certificates marked signed by
"DST".  What happened to DST?
>    - there are six certificates marked as being from "Thawte".  Who's
"Thawte"?
>    - what about Xcert?





From owner-ietf@ietf.org  Wed Jun 11 07:24:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02722
	for <ietf-web-archive@odin.ietf.org>; Wed, 11 Jun 2003 07:24:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Q3Sh-00046B-2Z
	for ietf-list@asgard.ietf.org; Wed, 11 Jun 2003 07:08:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Q3S0-000430-3i
	for ietf@asgard.ietf.org; Wed, 11 Jun 2003 07:07:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02366
	for <ietf@ietf.org>; Wed, 11 Jun 2003 07:07:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q3Py-0006YT-00
	for ietf@ietf.org; Wed, 11 Jun 2003 07:05:26 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q3Px-0006YQ-00
	for ietf@ietf.org; Wed, 11 Jun 2003 07:05:25 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h5BB7ToY097150
	for <ietf@ietf.org>; Wed, 11 Jun 2003 13:07:29 +0200 (CEST)
Message-ID: <071f01c33009$a640a840$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000101c32fe8$2a53a9b0$0100010a@MyHomeLAN.local>
Subject: Re: Certificate / CPS issues 
Date: Wed, 11 Jun 2003 13:07:29 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Haren writes:

> There was a flaw in IE, although it has been fixed ...

Since it has been fixed, where's the problem?

> How can trust IE, it there is some very serious
> flaws like this one?

There are very serious flaws in just about all software; I have not
encountered any exceptions outside the very tiny world of rigorously
verified software, such as that traditionally used by NASA (not anymore),
and even that could still contain a bug.

Most commercial software today is riddled with bugs, because people won't
buy software that is bug-free, but they will buy software that is
feature-rich.  So that's what vendors provide.

> Also, have heard about Microsoft's Anti-Trust.

Antitrust refers to prevention of abuse of monopolistic dominance of a
market; it has nothing to do with trust in the sense of, say, PKI.  Overall,
Microsoft is much more trustworthy than average in this latter domain,
because it has to be--many eyes are watching, and any loss of reputation
could be catastrophic.




From owner-ietf@ietf.org  Wed Jun 11 07:24:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02748
	for <ietf-web-archive@odin.ietf.org>; Wed, 11 Jun 2003 07:24:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Q3Sg-00045q-PL
	for ietf-list@asgard.ietf.org; Wed, 11 Jun 2003 07:08:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Q3OC-00042m-Dm
	for ietf@asgard.ietf.org; Wed, 11 Jun 2003 07:03:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02319
	for <ietf@ietf.org>; Wed, 11 Jun 2003 07:03:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q3MA-0006XQ-00
	for ietf@ietf.org; Wed, 11 Jun 2003 07:01:30 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q3M9-0006XN-00
	for ietf@ietf.org; Wed, 11 Jun 2003 07:01:30 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h5BB3XoY097116
	for <ietf@ietf.org>; Wed, 11 Jun 2003 13:03:33 +0200 (CEST)
Message-ID: <070a01c33009$19481860$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References:  <DAC3FCB50E31C54987CD10797DA511BA03A644B5@WIN-MSG-10.  wingroup.windeploy.ntdev.microsoft.com> <112931587.1055267626@p3.JCK.COM> <06ba01c32fa5$0e8c2240$0a00000a@atkielski.com> <119937981.1055274632@p3.JCK.COM>
Subject: Re: Certificate / CPS issues
Date: Wed, 11 Jun 2003 13:03:33 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John writes:

> This appears to be relatively new.

The policies on shipping certificates with the product or making them
available via MS updates may be recent.  The mechanism of handling them in
software has been around for a long time.  You can see the certificates in
the Internet options in MSIE, and you can add or delete top-level CAs at
your discretion.  The current versions of MSIE and Windows ship with a
truckload of pre-loaded top-level CAs, I'm afraid.

> It isn't clear, from either the article or
> his note, how much of it is deployed already.

I see dozens of CAs defined in MSIE on XP and even on NT, so I'd say it is
well deployed.

> It is linked, the article says, to Win XP
> and not to IE -- there are different procedures,
> it says, for IE under Win 2000, ME and earlier
> than are proposed (apparently going forward)
> for XP.

XP has an auto update feature; that may be the difference.  They are all in
the Internet options dialog for configuration, however, as far as I know.

> It strongly implies that, if there are options
> to control this, they are (will be?) Windows
> options, not (specifically) IE options (although
> IE might well be able to access them).

Same thing, almost.  Calling up the Internet options from the Configuration
Panel in Windows brings up the same dialog as calling them up from MSIE or
Outlook Exprss.

> ... I have no idea whether there is an easily=
> accessible option that permits turning "ask
> me before installing a cert" on, or what
> information that question provides.

It hasn't often happened, but I seem to recall being asked if I wanted to
install a new top-level certificate.  You can examine the certificate before
approving it.

> And, unless you are in a position to speak
> authoritatively for Microsoft,...

Not anymore.




From owner-ietf@ietf.org  Wed Jun 11 09:09:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07439
	for <ietf-web-archive@odin.ietf.org>; Wed, 11 Jun 2003 09:09:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Q51a-0006Pq-B4
	for ietf-list@asgard.ietf.org; Wed, 11 Jun 2003 08:48:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Q4Zy-0005lH-EO
	for ietf@asgard.ietf.org; Wed, 11 Jun 2003 08:19:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04764
	for <ietf@ietf.org>; Wed, 11 Jun 2003 08:19:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q4Xw-00072E-00
	for ietf@ietf.org; Wed, 11 Jun 2003 08:17:44 -0400
Received: from protactinium.btinternet.com ([194.73.73.176])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q4Xv-00072B-00
	for ietf@ietf.org; Wed, 11 Jun 2003 08:17:44 -0400
Received: from host217-44-98-17.range217-44.btcentralplus.com ([217.44.98.17] helo=helios)
	by protactinium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19Q4Zv-0001AI-00
	for ietf@ietf.org; Wed, 11 Jun 2003 13:19:47 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: <ietf@ietf.org>
Subject: Re: Certificate / CPS issues
Date: Wed, 11 Jun 2003 13:16:30 +0100
Message-ID: <000301c33013$4a9cd590$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>Antitrust refers to prevention of abuse of monopolistic dominance of a
>market; it has nothing to do with trust in the sense

It is factor that contributes to building trust.




From owner-ietf@ietf.org  Wed Jun 11 09:17:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07673
	for <ietf-web-archive@odin.ietf.org>; Wed, 11 Jun 2003 09:17:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Q51f-0006bg-3q
	for ietf-list@asgard.ietf.org; Wed, 11 Jun 2003 08:48:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Q4wv-0004qh-Ay
	for ietf@asgard.ietf.org; Wed, 11 Jun 2003 08:43:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06588
	for <ietf@ietf.org>; Wed, 11 Jun 2003 08:43:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q4ur-0007bS-00
	for ietf@ietf.org; Wed, 11 Jun 2003 08:41:25 -0400
Received: from protactinium.btinternet.com ([194.73.73.176])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q4uq-0007bL-00
	for ietf@ietf.org; Wed, 11 Jun 2003 08:41:25 -0400
Received: from host217-44-98-17.range217-44.btcentralplus.com ([217.44.98.17] helo=helios)
	by protactinium.btinternet.com with esmtp (Exim 3.22 #23)
	id 19Q4wk-0004fj-00
	for ietf@ietf.org; Wed, 11 Jun 2003 13:43:22 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: <ietf@ietf.org>
Subject: RE: Re: Certificate / CPS issues
Date: Wed, 11 Jun 2003 13:40:05 +0100
Message-ID: <000a01c33016$95f019a0$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>Antitrust refers to prevention of abuse of monopolistic dominance of a
>market; it has nothing to do with trust in the sense

It is factor that contributes to building trust.




From owner-ietf@ietf.org  Wed Jun 11 16:38:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00552
	for <ietf-web-archive@odin.ietf.org>; Wed, 11 Jun 2003 16:38:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19QC3S-0002k0-2T
	for ietf-list@asgard.ietf.org; Wed, 11 Jun 2003 16:18:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19QByP-0002X3-K0
	for ietf@asgard.ietf.org; Wed, 11 Jun 2003 16:13:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00589
	for <ietf@ietf.org>; Wed, 11 Jun 2003 16:13:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QBwN-0003JG-00
	for ietf@ietf.org; Wed, 11 Jun 2003 16:11:27 -0400
Received: from [64.254.114.115] (helo=megisto-sql1.megisto.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19QBwM-0003J3-00
	for ietf@ietf.org; Wed, 11 Jun 2003 16:11:26 -0400
Received: by megisto-sql1 with Internet Mail Service (5.5.2653.19)
	id <MR2KL5FP>; Wed, 11 Jun 2003 16:04:55 -0400
Message-ID: <C3F7A1AD0781F84784B5528466CA09DD013A4FA6@megisto-sql1>
From: Phil Roberts <PRoberts@MEGISTO.com>
To: ietf@ietf.org
Subject: Internet Area call for nominations
Date: Wed, 11 Jun 2003 16:04:52 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C33054.B89FC390"
Sender: owner-ietf@ietf.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C33054.B89FC390
Content-Type: text/plain


The nominations committee has received notice to fill the vacancy in the
Internet Area created with Erik Nordmark's departure.  The nominations
committee is seeking nominees to fill the open position.  The chosen
candidate
will serve out the rest of the current term, which ends in March 2004,
and the two year term following, according to the rules documented in RFC
2727.
 
Members of the community are encouraged to contact the nomcom confidentially

1) to nominate someone for this position (please provide the email
address of any nominee), or 2) to provide input relating to potential
candidates.
 
All of this information will be considered during the deliberations of
the nominating committee and will be held in confidence by the nominating
committee.
 
We emphasize that comments sent to the nominations committee will be kept
in confidence. As noted in RFC 2727 "all deliberations and supporting 
information that relates to specific nominees, candidates, and confirmed
candidates are confidential."
 
Self-nominations are accepted. The deadline for nominations is midnight
Tuesday, June 17, 2003.  
 
The members of the NomCom can be contacted individually at the addresses
below or collectively at nomcom@ietf.org <mailto:nomcom@ietf.org> .
 
The 2002-2003 Nominations Committee
Edward Lewis <edlewis@arin.net <mailto:edlewis@arin.net> > 
Alec Brusilovsky <abrusilovsky@iee.org <mailto:abrusilovsky@iee.org> > 
Michael Richardson <mcr@sandelman.ca <mailto:mcr@sandelman.ca> > 
Eva Jonsson <eva.jonsson@utfors.se <mailto:eva.jonsson@utfors.se> > 
Stephen Trowbridge <sjtrowbridge@lucent.com <mailto:sjtrowbridge@lucent.com>
> 
Frank Alfano <falfano@lucent.com <mailto:falfano@lucent.com> > 
Thomas Kurien <kurien@kamputech.com <mailto:kurien@kamputech.com> > 
Dennis Beard <beardd@nortelnetworks.com <mailto:beardd@nortelnetworks.com> >

Richard Draves <richdr@microsoft.com <mailto:richdr@microsoft.com> > 
Eva Gustafsson <eva.gustafsson@ericsson.com
<mailto:eva.gustafsson@ericsson.com> >
 
Non-voting members:
Phil Roberts <proberts@megito.com <mailto:proberts@megito.com> > (chair)
Allison Mankin <mankin@psg.com <mailto:mankin@psg.com> > (IESG liaison)
Eric Rescorla <ekr@rtfm.com <mailto:ekr@rtfm.com> > (IAB liaison) 
Theodore Ts'o <tytso@mit.edu <mailto:tytso@mit.edu> > (previous nomcom
chair)
 
The role of non-voting members (from RFC 2727):
 
"The nominations committee comprises at least a non-voting Chair,
10 voting volunteers, and 3 non-voting liaisons.  The sitting IAB
and IESG members each appoint a non-voting liaison to the nominating
committee from their current membership who are not sitting in an 
open position.  The Chair of the prior year's nominating committee 
also serves as a non-voting liaison.


------_=_NextPart_001_01C33054.B89FC390
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2722.900" name=GENERATOR></HEAD>
<BODY><FONT face=Arial size=2>
<DIV><BR>The nominations committee has received notice to fill the vacancy in 
the<BR>Internet Area created with Erik Nordmark's departure.&nbsp; The 
nominations<BR>committee is seeking nominees to fill the open position.&nbsp; 
The chosen candidate<BR>will serve out the rest of the current term, which ends 
in March 2004,<BR>and the two year term following, according to the rules 
documented in RFC 2727.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Members of the community are encouraged to contact the nomcom 
confidentially <BR>1) to nominate someone for this position (please provide the 
email<BR>address of any nominee), or 2) to provide input relating to potential 
candidates.</DIV>
<DIV>&nbsp;</DIV>
<DIV>All of this information will be considered during the deliberations 
of<BR>the nominating committee and will be held in confidence by the 
nominating<BR>committee.</DIV>
<DIV>&nbsp;</DIV>
<DIV>We emphasize that comments sent to the nominations committee will be 
kept<BR>in confidence. As noted in RFC 2727 "all deliberations and supporting 
<BR>information that relates to specific nominees, candidates, and 
confirmed<BR>candidates are confidential."</DIV>
<DIV>&nbsp;</DIV>
<DIV>Self-nominations are accepted. The deadline for nominations is 
midnight<BR>Tuesday, June 17, 2003.&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>The members of the NomCom can be contacted individually at the 
addresses<BR>below or collectively at <A 
href="mailto:nomcom@ietf.org">nomcom@ietf.org</A>.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The 2002-2003 Nominations Committee<BR>Edward Lewis &lt;<A 
href="mailto:edlewis@arin.net">edlewis@arin.net</A>&gt; <BR>Alec Brusilovsky 
&lt;<A href="mailto:abrusilovsky@iee.org">abrusilovsky@iee.org</A>&gt; 
<BR>Michael Richardson &lt;<A 
href="mailto:mcr@sandelman.ca">mcr@sandelman.ca</A>&gt; <BR>Eva Jonsson &lt;<A 
href="mailto:eva.jonsson@utfors.se">eva.jonsson@utfors.se</A>&gt; <BR>Stephen 
Trowbridge &lt;<A 
href="mailto:sjtrowbridge@lucent.com">sjtrowbridge@lucent.com</A>&gt; <BR>Frank 
Alfano &lt;<A href="mailto:falfano@lucent.com">falfano@lucent.com</A>&gt; 
<BR>Thomas Kurien &lt;<A 
href="mailto:kurien@kamputech.com">kurien@kamputech.com</A>&gt; <BR>Dennis Beard 
&lt;<A href="mailto:beardd@nortelnetworks.com">beardd@nortelnetworks.com</A>&gt; 
<BR>Richard Draves &lt;<A 
href="mailto:richdr@microsoft.com">richdr@microsoft.com</A>&gt; <BR>Eva 
Gustafsson &lt;<A 
href="mailto:eva.gustafsson@ericsson.com">eva.gustafsson@ericsson.com</A>&gt;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Non-voting members:<BR>Phil Roberts &lt;<A 
href="mailto:proberts@megito.com">proberts@megito.com</A>&gt; (chair)<BR>Allison 
Mankin &lt;<A href="mailto:mankin@psg.com">mankin@psg.com</A>&gt; (IESG 
liaison)<BR>Eric Rescorla &lt;<A href="mailto:ekr@rtfm.com">ekr@rtfm.com</A>&gt; 
(IAB liaison) <BR>Theodore Ts'o &lt;<A 
href="mailto:tytso@mit.edu">tytso@mit.edu</A>&gt; (previous nomcom chair)</DIV>
<DIV>&nbsp;</DIV>
<DIV>The role of non-voting members (from RFC 2727):</DIV>
<DIV>&nbsp;</DIV>
<DIV>"The nominations committee comprises at least a non-voting Chair,<BR>10 
voting volunteers, and 3 non-voting liaisons.&nbsp; The sitting IAB<BR>and IESG 
members each appoint a non-voting liaison to the nominating<BR>committee from 
their current membership who are not sitting in an <BR>open position.&nbsp; The 
Chair of the prior year's nominating committee <BR>also serves as a non-voting 
liaison.<BR></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C33054.B89FC390--



From owner-ietf@ietf.org  Wed Jun 11 18:44:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07878
	for <ietf-web-archive@odin.ietf.org>; Wed, 11 Jun 2003 18:44:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19QE6o-0004zv-FP
	for ietf-list@asgard.ietf.org; Wed, 11 Jun 2003 18:30:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19QDuc-0004nw-Cx
	for ietf@asgard.ietf.org; Wed, 11 Jun 2003 18:17:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06761
	for <ietf@ietf.org>; Wed, 11 Jun 2003 18:17:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QDsZ-0004aJ-00
	for ietf@ietf.org; Wed, 11 Jun 2003 18:15:39 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19QDsY-0004ZZ-00
	for ietf@ietf.org; Wed, 11 Jun 2003 18:15:39 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id SAA28305;
	Wed, 11 Jun 2003 18:11:39 -0400
Date: Wed, 11 Jun 2003 18:12:59 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Valdis.Kletnieks@vt.edu
cc: james woodyatt <jhw@wetware.com>, IETF list <ietf@ietf.org>
Subject: Re: Engineering to deal with the social problem of spam 
In-Reply-To: <200306110512.h5B5CkKB015314@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0306111808030.8535-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Wed, 11 Jun 2003 Valdis.Kletnieks@vt.edu wrote:

> On Tue, 10 Jun 2003 10:08:15 PDT, james woodyatt <jhw@wetware.com>  said:
> > And as for those too poor to keep their CPU's current, Let Them Eat
> > SMTP.  They clearly have an unhealthy interest in paying to receive
> > MAKE MONEY FAST spam, so we should encourage them to continue using
> > SMTP anyway.  The Internet interprets censorship as damage and routes
> > around it.  Let SMTP continue to serve the useful function it serves:
> > carrying spam messages.
>
> Ahem.
>
> I have several million dollars of compute resources at my disposal.
> It will take a fairly large hashcash request to make it painful for
> me.

Then you obviously have too much compute power for the number of users
that you have.

If you get more users, the compute power to implement hashcash increases.
Hashcash just makes you more vulneralble to a DOS attack, and does nothing
to deter spam. Spammers will still send something that is cheaper than a
postcard.

If you make email cost more than a postcard, _that_ will kill email.
Nothing else will.

>
> There is junk fax - and the Berlin Wall was brought down by fax machines.
>
> Let's not get this wrong.

Let's not forget that it was UUCP and not the internet that foiled the
coup that imprisoned Gorbachev for 3 days.

		--Dean




From owner-ietf@ietf.org  Wed Jun 11 21:21:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11349
	for <ietf-web-archive@odin.ietf.org>; Wed, 11 Jun 2003 21:21:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19QGaJ-0008NP-0y
	for ietf-list@asgard.ietf.org; Wed, 11 Jun 2003 21:08:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19QGYc-0008JJ-9b
	for ietf@asgard.ietf.org; Wed, 11 Jun 2003 21:07:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11086
	for <ietf@ietf.org>; Wed, 11 Jun 2003 21:07:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QGWZ-0005ku-00
	for ietf@ietf.org; Wed, 11 Jun 2003 21:05:07 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19QGWY-0005kr-00
	for ietf@ietf.org; Wed, 11 Jun 2003 21:05:06 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h5C17BoY004664
	for <ietf@ietf.org>; Thu, 12 Jun 2003 03:07:11 +0200 (CEST)
Message-ID: <078801c3307e$f404be70$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <000301c33013$4a9cd590$0100010a@MyHomeLAN.local>
Subject: Re: Certificate / CPS issues
Date: Thu, 12 Jun 2003 03:07:11 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Haren writes:

> It is factor that contributes to building trust.

Not in the PKI sense.  Rather a matter of apples and oranges, in my view.



From owner-ietf@ietf.org  Thu Jun 12 10:10:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11852
	for <ietf-web-archive@odin.ietf.org>; Thu, 12 Jun 2003 10:10:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19QSeV-0001Ti-4a
	for ietf-list@asgard.ietf.org; Thu, 12 Jun 2003 10:02:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Q5Sd-0007VF-G2
	for ietf@asgard.ietf.org; Wed, 11 Jun 2003 09:16:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07650
	for <ietf@ietf.org>; Wed, 11 Jun 2003 09:16:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q5Qb-00005g-00
	for ietf@ietf.org; Wed, 11 Jun 2003 09:14:13 -0400
Received: from [64.254.114.115] (helo=megisto-sql1.megisto.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q5Qa-00005b-00
	for ietf@ietf.org; Wed, 11 Jun 2003 09:14:12 -0400
Received: by megisto-sql1 with Internet Mail Service (5.5.2653.19)
	id <MR2KLZ21>; Wed, 11 Jun 2003 09:07:41 -0400
Message-ID: <C3F7A1AD0781F84784B5528466CA09DD013A4F80@megisto-sql1>
From: Phil Roberts <PRoberts@MEGISTO.com>
To: ietf@ietf.org
Subject: Call for Nominations - Internet Area
Date: Wed, 11 Jun 2003 09:07:34 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3301A.6C412F00"
Sender: owner-ietf@ietf.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C3301A.6C412F00
Content-Type: text/plain


The nominations committee has received notice to fill the vacancy in the
Internet Area created with Erik Nordmark's departure.  The nominations
committee is seeking nominees to fill the open position.  The chosen
candidate
will serve out the rest of the current term, which ends in March 2004,
and the two year term following, according to the rules documented in RFC
2727.
 
Members of the community are encouraged to contact the nomcom confidentially

1) to nominate someone for this position (please provide the email
address of any nominee), or 2) to provide input relating to potential
candidates.
 
All of this information will be considered during the deliberations of
the nominating committee and will be held in confidence by the nominating
committee.
 
We emphasize that comments sent to the nominations committee will be kept
in confidence. As noted in RFC 2727 "all deliberations and supporting 
information that relates to specific nominees, candidates, and confirmed
candidates are confidential."
 
Self-nominations are accepted. The deadline for nominations is midnight
Tuesday, June 17, 2003.  
 
The members of the NomCom can be contacted individually at the addresses
below or collectively at nomcom@ietf.org <mailto:nomcom@ietf.org> .
 
The 2002-2003 Nominations Committee
Edward Lewis <edlewis@arin.net <mailto:edlewis@arin.net> > 
Alec Brusilovsky <abrusilovsky@iee.org <mailto:abrusilovsky@iee.org> > 
Michael Richardson <mcr@sandelman.ca <mailto:mcr@sandelman.ca> > 
Eva Jonsson <eva.jonsson@utfors.se <mailto:eva.jonsson@utfors.se> > 
Stephen Trowbridge <sjtrowbridge@lucent.com <mailto:sjtrowbridge@lucent.com>
> 
Frank Alfano <falfano@lucent.com <mailto:falfano@lucent.com> > 
Thomas Kurien <kurien@kamputech.com <mailto:kurien@kamputech.com> > 
Dennis Beard <beardd@nortelnetworks.com <mailto:beardd@nortelnetworks.com> >

Richard Draves <richdr@microsoft.com <mailto:richdr@microsoft.com> > 
Eva Gustafsson <eva.gustafsson@ericsson.com
<mailto:eva.gustafsson@ericsson.com> >
 
Non-voting members:
Phil Roberts <proberts@megito.com <mailto:proberts@megito.com> > (chair)
Allison Mankin <mankin@psg.com <mailto:mankin@psg.com> > (IESG liaison)
Eric Rescorla <ekr@rtfm.com <mailto:ekr@rtfm.com> > (IAB liaison) 
Theodore Ts'o <tytso@mit.edu <mailto:tytso@mit.edu> > (previous nomcom
chair)
 
The role of non-voting members (from RFC 2727):
 
"The nominations committee comprises at least a non-voting Chair,
10 voting volunteers, and 3 non-voting liaisons.  The sitting IAB
and IESG members each appoint a non-voting liaison to the nominating
committee from their current membership who are not sitting in an 
open position.  The Chair of the prior year's nominating committee 
also serves as a non-voting liaison.


------_=_NextPart_001_01C3301A.6C412F00
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2722.900" name=GENERATOR></HEAD>
<BODY><FONT face=Arial size=2>
<DIV><BR>The nominations committee has received notice to fill the vacancy in 
the<BR>Internet Area created with Erik Nordmark's departure.&nbsp; The 
nominations<BR>committee is seeking nominees to fill the open position.&nbsp; 
The chosen candidate<BR>will serve out the rest of the current term, which ends 
in March 2004,<BR>and the two year term following, according to the rules 
documented in RFC 2727.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Members of the community are encouraged to contact the nomcom 
confidentially <BR>1) to nominate someone for this position (please provide the 
email<BR>address of any nominee), or 2) to provide input relating to potential 
candidates.</DIV>
<DIV>&nbsp;</DIV>
<DIV>All of this information will be considered during the deliberations 
of<BR>the nominating committee and will be held in confidence by the 
nominating<BR>committee.</DIV>
<DIV>&nbsp;</DIV>
<DIV>We emphasize that comments sent to the nominations committee will be 
kept<BR>in confidence. As noted in RFC 2727 "all deliberations and supporting 
<BR>information that relates to specific nominees, candidates, and 
confirmed<BR>candidates are confidential."</DIV>
<DIV>&nbsp;</DIV>
<DIV>Self-nominations are accepted. The deadline for nominations is 
midnight<BR>Tuesday, June 17, 2003.&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>The members of the NomCom can be contacted individually at the 
addresses<BR>below or collectively at <A 
href="mailto:nomcom@ietf.org">nomcom@ietf.org</A>.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The 2002-2003 Nominations Committee<BR>Edward Lewis &lt;<A 
href="mailto:edlewis@arin.net">edlewis@arin.net</A>&gt; <BR>Alec Brusilovsky 
&lt;<A href="mailto:abrusilovsky@iee.org">abrusilovsky@iee.org</A>&gt; 
<BR>Michael Richardson &lt;<A 
href="mailto:mcr@sandelman.ca">mcr@sandelman.ca</A>&gt; <BR>Eva Jonsson &lt;<A 
href="mailto:eva.jonsson@utfors.se">eva.jonsson@utfors.se</A>&gt; <BR>Stephen 
Trowbridge &lt;<A 
href="mailto:sjtrowbridge@lucent.com">sjtrowbridge@lucent.com</A>&gt; <BR>Frank 
Alfano &lt;<A href="mailto:falfano@lucent.com">falfano@lucent.com</A>&gt; 
<BR>Thomas Kurien &lt;<A 
href="mailto:kurien@kamputech.com">kurien@kamputech.com</A>&gt; <BR>Dennis Beard 
&lt;<A href="mailto:beardd@nortelnetworks.com">beardd@nortelnetworks.com</A>&gt; 
<BR>Richard Draves &lt;<A 
href="mailto:richdr@microsoft.com">richdr@microsoft.com</A>&gt; <BR>Eva 
Gustafsson &lt;<A 
href="mailto:eva.gustafsson@ericsson.com">eva.gustafsson@ericsson.com</A>&gt;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Non-voting members:<BR>Phil Roberts &lt;<A 
href="mailto:proberts@megito.com">proberts@megito.com</A>&gt; (chair)<BR>Allison 
Mankin &lt;<A href="mailto:mankin@psg.com">mankin@psg.com</A>&gt; (IESG 
liaison)<BR>Eric Rescorla &lt;<A href="mailto:ekr@rtfm.com">ekr@rtfm.com</A>&gt; 
(IAB liaison) <BR>Theodore Ts'o &lt;<A 
href="mailto:tytso@mit.edu">tytso@mit.edu</A>&gt; (previous nomcom chair)</DIV>
<DIV>&nbsp;</DIV>
<DIV>The role of non-voting members (from RFC 2727):</DIV>
<DIV>&nbsp;</DIV>
<DIV>"The nominations committee comprises at least a non-voting Chair,<BR>10 
voting volunteers, and 3 non-voting liaisons.&nbsp; The sitting IAB<BR>and IESG 
members each appoint a non-voting liaison to the nominating<BR>committee from 
their current membership who are not sitting in an <BR>open position.&nbsp; The 
Chair of the prior year's nominating committee <BR>also serves as a non-voting 
liaison.<BR></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C3301A.6C412F00--





From owner-ietf@ietf.org  Thu Jun 12 10:11:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12129
	for <ietf-web-archive@odin.ietf.org>; Thu, 12 Jun 2003 10:11:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19QSeV-0001Tz-8a
	for ietf-list@asgard.ietf.org; Thu, 12 Jun 2003 10:02:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19QBhY-00024Y-I3
	for ietf@asgard.ietf.org; Wed, 11 Jun 2003 15:56:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13266
	for <ietf@ietf.org>; Wed, 11 Jun 2003 11:24:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q7QF-000155-00
	for ietf@ietf.org; Wed, 11 Jun 2003 11:21:59 -0400
Received: from main.gmane.org ([80.91.224.249])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Q7QE-000152-00
	for ietf@ietf.org; Wed, 11 Jun 2003 11:21:58 -0400
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 19Q7KS-0007SB-00
	for <ietf@ietf.org>; Wed, 11 Jun 2003 17:16:00 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 19Q7Ds-0006pC-00
	for <gmane-ietf-general@m.gmane.org>; Wed, 11 Jun 2003 17:09:12 +0200
From: mc@hack.org
Subject: Re: IMAP v. POP
Date: Wed, 11 Jun 2003 17:11:57 +0200
Organization: Temple of the Moby Hack
Lines: 13
Message-ID: <867k7s1wea.fsf@fuckup.hack.org>
References: <22448.5358609401$1054747611@news.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
X-URL: http://hack.org/~mc/
X-Waved: Chicken (dead). Curse all those damn UCE bots!
User-Agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.3 (berkeley-unix)
Cancel-Lock: sha1:YaYAEOMV98niU25LvtlPQXOkos4=
Sender: owner-ietf@ietf.org
Precedence: bulk

dank@hq.lindsayelec.com (Dan Kolis) writes:

> If [POP] just had passwords not in the clear, and a better way to
> defer big attachments, I think it would be nearly perfect
> protocol/service.

Are you aware of the APOP request in POP? It uses a simple
challenge/response scenario, but requires that you store the POP
passwords in cleartext at the server.

-- 
MC - mc@hack.org - http://hack.org/~mc/
"Are we THERE yet?"






From owner-ietf@ietf.org  Thu Jun 12 11:10:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15178
	for <ietf-web-archive@odin.ietf.org>; Thu, 12 Jun 2003 11:10:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19QTbT-00081d-7O
	for ietf-list@asgard.ietf.org; Thu, 12 Jun 2003 11:03:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19QTHT-0007no-N0
	for ietf@asgard.ietf.org; Thu, 12 Jun 2003 10:42:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14157
	for <ietf@ietf.org>; Thu, 12 Jun 2003 10:42:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QTFP-000376-00
	for ietf@ietf.org; Thu, 12 Jun 2003 10:40:15 -0400
Received: from carbon.btinternet.com ([194.73.73.92])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QTFP-000373-00
	for ietf@ietf.org; Thu, 12 Jun 2003 10:40:15 -0400
Received: from host217-44-79-134.range217-44.btcentralplus.com ([217.44.79.134] helo=helios)
	by carbon.btinternet.com with esmtp (Exim 3.22 #23)
	id 19QTHR-0006V6-00
	for ietf@ietf.org; Thu, 12 Jun 2003 15:42:21 +0100
From: "Haren Visavadia" <haren@btopenworld.com>
To: <ietf@ietf.org>
Subject: Re: Certificate / CPS issues 
Date: Thu, 12 Jun 2003 15:39:02 +0100
Message-ID: <000001c330f0$5e3d8440$0100010a@MyHomeLAN.local>
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, Build 10.0.2616
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Not in the PKI sense

PKI only works when there is trust.


If you think "Rather a matter of apples and oranges, in my view." you
are very blind to the trust element and its importance. I know you would
even trust the Soviet Union.




From owner-ietf@ietf.org  Thu Jun 12 13:27:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19796
	for <ietf-web-archive@odin.ietf.org>; Thu, 12 Jun 2003 13:27:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19QVYx-0002E9-KV
	for ietf-list@asgard.ietf.org; Thu, 12 Jun 2003 13:08:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19QVVf-0002B6-TG
	for ietf@asgard.ietf.org; Thu, 12 Jun 2003 13:05:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18879
	for <ietf@ietf.org>; Thu, 12 Jun 2003 13:05:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QVTb-0004FV-00
	for ietf@ietf.org; Thu, 12 Jun 2003 13:03:03 -0400
Received: from outbound04.telus.net ([199.185.220.223] helo=priv-edtnes16-hme0.telusplanet.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19QVTb-0004FK-00
	for ietf@ietf.org; Thu, 12 Jun 2003 13:03:03 -0400
Received: from orthanc.ab.ca ([209.89.195.21])
          by priv-edtnes16-hme0.telusplanet.net
          (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with ESMTP
          id <20030612170434.IXFP17379.priv-edtnes16-hme0.telusplanet.net@orthanc.ab.ca>;
          Thu, 12 Jun 2003 11:04:34 -0600
Date: Thu, 12 Jun 2003 11:04:33 -0600
Subject: Re: IMAP v. POP
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: mc@hack.org
From: Lyndon Nerenberg <lyndon@orthanc.ab.ca>
In-Reply-To: <867k7s1wea.fsf@fuckup.hack.org>
Message-Id: <F029BF67-9CF7-11D7-A10F-000393D34A62@orthanc.ab.ca>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Are you aware of the APOP request in POP?

Or the AUTH command (RFC 1734).

--lyndon




From owner-ietf@ietf.org  Thu Jun 12 14:19:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21603
	for <ietf-web-archive@odin.ietf.org>; Thu, 12 Jun 2003 14:19:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19QWV9-0003MW-Ld
	for ietf-list@asgard.ietf.org; Thu, 12 Jun 2003 14:08:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19QWTc-0003Jm-9l
	for ietf@asgard.ietf.org; Thu, 12 Jun 2003 14:07:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21315
	for <ietf@ietf.org>; Thu, 12 Jun 2003 14:07:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QWRY-0004vd-00
	for ietf@ietf.org; Thu, 12 Jun 2003 14:05:00 -0400
Received: from iserver.sj.symbol.com ([63.145.233.51])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QWRX-0004va-00
	for ietf@ietf.org; Thu, 12 Jun 2003 14:04:59 -0400
Received: from gwianameserver.sj.symbol.com (symsjdmz.sj.symbol.com [63.145.233.50])
	by iserver.sj.symbol.com (8.12.8/8.12.8) with ESMTP id h5CI3Vgf021731
	for <ietf@ietf.org>; Thu, 12 Jun 2003 11:03:31 -0700 (PDT)
Received: from SJ-DOM-MTA by gwianameserver.sj.symbol.com
	with Novell_GroupWise; Thu, 12 Jun 2003 11:07:00 -0700
Message-Id: <see85ed4.081@gwianameserver.sj.symbol.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2
Date: Thu, 12 Jun 2003 11:07:09 -0700
From: "Clint Chaplin" <cchaplin@sj.symbol.com>
To: <anthony@atkielski.com>, <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA21603

From the ISP.

Clint (JOATMON) Chaplin

>>> "Anthony Atkielski" <anthony@atkielski.com> 5/31/03 08:29:18 >>>
Terry writes:

> At least one of them is a combination of letters
> and numbers that I would have expected to
> resist most dictionary spam attacks.

To whom have you sent e-mail from that address?

If they didn't use a dictionary attack, and they didn't harvest the address,
how did they get it?



________________________________________________________________________
This email has been scanned for computer viruses.




From owner-ietf@ietf.org  Thu Jun 12 14:33:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22145
	for <ietf-web-archive@odin.ietf.org>; Thu, 12 Jun 2003 14:33:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19QWeg-0003U1-Ml
	for ietf-list@asgard.ietf.org; Thu, 12 Jun 2003 14:18:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19QWVV-0003MZ-S1
	for ietf@asgard.ietf.org; Thu, 12 Jun 2003 14:09:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21357
	for <ietf@ietf.org>; Thu, 12 Jun 2003 14:09:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QWTR-0004wM-00
	for ietf@ietf.org; Thu, 12 Jun 2003 14:06:57 -0400
Received: from iserver.sj.symbol.com ([63.145.233.51])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QWTQ-0004wJ-00
	for ietf@ietf.org; Thu, 12 Jun 2003 14:06:57 -0400
Received: from gwianameserver.sj.symbol.com (symsjdmz.sj.symbol.com [63.145.233.50])
	by iserver.sj.symbol.com (8.12.8/8.12.8) with ESMTP id h5CI5Tgf021760
	for <ietf@ietf.org>; Thu, 12 Jun 2003 11:05:29 -0700 (PDT)
Received: from SJ-DOM-MTA by gwianameserver.sj.symbol.com
	with Novell_GroupWise; Thu, 12 Jun 2003 11:08:57 -0700
Message-Id: <see85f49.085@gwianameserver.sj.symbol.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2
Date: Thu, 12 Jun 2003 11:09:20 -0700
From: "Clint Chaplin" <cchaplin@sj.symbol.com>
To: <ietf@ietf.org>
Subject: Re: The utilitiy of IP is at stake here
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA22145

Oh, please.  My MSN account (28.8K dial up) got spam from day one, and I only used it for private email.  MSN, at the time, had their directory wide open for anybody to vacuum up.



Clint (JOATMON) Chaplin

>>> "Anthony Atkielski" <anthony@atkielski.com> 5/30/03 18:57:31 >>>
Valdis writes:

> I'm glad that you have such a high-speed connection
> that you can connect, download hundreds of messages,
> and filter/delete them all in a minute or two.

I have a broadband connection, and my perpetually-open Outlook Express
client checks my e-mail every sixty seconds.  So I just delete the junk mail
in my inbox when I come across it.  I'd say that it actually takes 10-15
seconds each time I do it.

> My mother doesn't have that luxury - a 56K modem
> connection from Earthlink and Hotmail is as good as
> it's going to get on Social Security.

In that case, she isn't likely to be posting to USENET, participating in
mailing lists, or putting her e-mail address on Web sites, either, so she
probably won't receive much spam.

> And as long as spam doesn't find her, it's *sufficient*.

Exactly.  See above.

> But if she has to start worrying about more than a
> dozen spams a day, e-mail will become useless for her.

How will the spammer's find her address?

> I suggest that you keep in mind that my mother
> is probably a lot more representative of the net
> population at large than you are.

Yes.  A slow connection, and little or no spam.

> Unless you're a television critic, there's no real
> cost to the time commercials take up.

How can time spent watching television commercials be free, if the same time
spent deleting spam costs money?

> But who's getting the benefit from unsolicited spam
> that neither the user nor the provider agreed to?

The people who reply to the spam, apparently.  The only reason spammers send
it out is that some people reply to it.




________________________________________________________________________
This email has been scanned for computer viruses.




From owner-ietf@ietf.org  Thu Jun 12 15:07:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23570
	for <ietf-web-archive@odin.ietf.org>; Thu, 12 Jun 2003 15:07:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19QXHk-0004mK-3W
	for ietf-list@asgard.ietf.org; Thu, 12 Jun 2003 14:58:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19QX41-0004Sc-BR
	for ietf@asgard.ietf.org; Thu, 12 Jun 2003 14:44:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22619
	for <ietf@ietf.org>; Thu, 12 Jun 2003 14:44:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QX1x-0005Ev-00
	for ietf@ietf.org; Thu, 12 Jun 2003 14:42:37 -0400
Received: from iserver.sj.symbol.com ([63.145.233.51])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QX1w-0005Es-00
	for ietf@ietf.org; Thu, 12 Jun 2003 14:42:36 -0400
Received: from gwianameserver.sj.symbol.com (symsjdmz.sj.symbol.com [63.145.233.50])
	by iserver.sj.symbol.com (8.12.8/8.12.8) with ESMTP id h5CIf9gf022354
	for <ietf@ietf.org>; Thu, 12 Jun 2003 11:41:09 -0700 (PDT)
Received: from SJ-DOM-MTA by gwianameserver.sj.symbol.com
	with Novell_GroupWise; Thu, 12 Jun 2003 11:44:41 -0700
Message-Id: <see867a9.071@gwianameserver.sj.symbol.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2
Date: Thu, 12 Jun 2003 11:44:45 -0700
From: "Clint Chaplin" <cchaplin@sj.symbol.com>
To: <ietf@ietf.org>, <Tomson_Eric@Yahoo.fr>
Subject: Re: This IETF discussion list
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA23570

I wish to point out that IEEE is >not< open to just certified engineers.  I was never certified (which means that in many jurisdictions it would be illegal to call myself an engineer), but I have been a member of IEEE for over 27 years.

Even more interestingly, you can become a member of an IEEE standards committee without being a member of IEEE itself.  Many members of IEEE 802.11 are not members of IEEE.

Clint (JOATMON) Chaplin

>>> "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr> 6/1/03 10:43:04 >>>
Should this list be open to ANYbody (any curious/interested netizen), or
limited to proven... well... specialists? experts?

I think this IETF discussion list is like a combination of the IEEE and the
ISOC : the IEEE is limited to certified engineers, while the ISOC is open to
all netizens.






From owner-ietf@ietf.org  Thu Jun 12 16:34:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26033
	for <ietf-web-archive@odin.ietf.org>; Thu, 12 Jun 2003 16:34:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19QYN8-0005Yj-73
	for ietf-list@asgard.ietf.org; Thu, 12 Jun 2003 16:08:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19QYMk-0005W1-PR
	for ietf@asgard.ietf.org; Thu, 12 Jun 2003 16:08:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25422
	for <ietf@ietf.org>; Thu, 12 Jun 2003 16:08:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QYKb-0005cv-00
	for ietf@ietf.org; Thu, 12 Jun 2003 16:05:57 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19QYKa-0005cf-00
	for ietf@ietf.org; Thu, 12 Jun 2003 16:05:57 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id PAA18024;
	Thu, 12 Jun 2003 15:59:25 -0400
Date: Thu, 12 Jun 2003 16:00:31 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Clint Chaplin <cchaplin@sj.symbol.com>
cc: ietf@ietf.org, <Tomson_Eric@Yahoo.fr>
Subject: Re: This IETF discussion list
In-Reply-To: <see867a9.071@gwianameserver.sj.symbol.com>
Message-ID: <Pine.LNX.4.44.0306121557420.24545-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

This is true of every technical professional organization which I've ever
been a member of: IEEE, ACM, Usenix, and others.

		--Dean

On Thu, 12 Jun 2003, Clint Chaplin wrote:

> I wish to point out that IEEE is >not< open to just certified engineers.
> I was never certified (which means that in many jurisdictions it would
> be illegal to call myself an engineer), but I have been a member of IEEE
> for over 27 years.
>
> Even more interestingly, you can become a member of an IEEE standards
> committee without being a member of IEEE itself.  Many members of IEEE
> 802.11 are not members of IEEE.
>
> Clint (JOATMON) Chaplin
>
> >>> "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr> 6/1/03 10:43:04 >>>
> Should this list be open to ANYbody (any curious/interested netizen), or
> limited to proven... well... specialists? experts?
>
> I think this IETF discussion list is like a combination of the IEEE and the
> ISOC : the IEEE is limited to certified engineers, while the ISOC is open to
> all netizens.
>
>
>
>
>




From owner-ietf@ietf.org  Fri Jun 13 10:07:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05964
	for <ietf-web-archive@odin.ietf.org>; Fri, 13 Jun 2003 10:07:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Qok5-0005Rb-6c
	for ietf-list@asgard.ietf.org; Fri, 13 Jun 2003 09:37:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19QZ2h-0006f6-Ne
	for ietf@asgard.ietf.org; Thu, 12 Jun 2003 16:51:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26592
	for <ietf@ietf.org>; Thu, 12 Jun 2003 16:51:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QZ0d-0005t8-00
	for ietf@ietf.org; Thu, 12 Jun 2003 16:49:23 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19QZ0b-0005t4-00
	for ietf@ietf.org; Thu, 12 Jun 2003 16:49:22 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h5CKpPoY014245
	for <ietf@ietf.org>; Thu, 12 Jun 2003 22:51:25 +0200 (CEST)
Message-ID: <09d401c33124$639e2c80$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <see867a9.071@gwianameserver.sj.symbol.com>
Subject: Re: This IETF discussion list
Date: Thu, 12 Jun 2003 22:51:23 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Clint writes:

> ... which means that in many jurisdictions it
> would be illegal to call myself an engineer ...

Which ones?

In general, you can call yourself an engineer, a doctor, or even an attorney
legally, as long as you don't qualify the appellation.  If you call yourself
a medical doctor, an attorney at law, or a civil engineer, that's different,
and in some jurisdictions these appellations are regulated.






From owner-ietf@ietf.org  Fri Jun 13 10:07:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06008
	for <ietf-web-archive@odin.ietf.org>; Fri, 13 Jun 2003 10:07:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Qok5-0005Rs-9S
	for ietf-list@asgard.ietf.org; Fri, 13 Jun 2003 09:37:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ql1B-0006OJ-PF
	for ietf@asgard.ietf.org; Fri, 13 Jun 2003 05:38:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26585
	for <ietf@ietf.org>; Fri, 13 Jun 2003 05:38:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Qkz6-0003BY-00
	for ietf@ietf.org; Fri, 13 Jun 2003 05:36:36 -0400
Received: from apollo.xerox.com ([212.137.33.204] helo=apollo.eurgw.xerox.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Qkyw-0003BQ-00
	for ietf@ietf.org; Fri, 13 Jun 2003 05:36:31 -0400
Received: from eurodns2.eur.xerox.com (eurodns2.eur.xerox.com [13.202.66.10])
	by apollo.eurgw.xerox.com (8.12.9/8.12.9) with ESMTP id h5D9bqPr016220
	for <ietf@ietf.org>; Fri, 13 Jun 2003 10:38:12 +0100 (BST)
Received: from eurdubmg02.eur.xerox.com (eurdubmg02.eur.xerox.com [13.202.65.254])
	by eurodns2.eur.xerox.com (8.12.9/8.12.9) with ESMTP id h5D9baIj012813
	for <ietf@ietf.org>; Fri, 13 Jun 2003 10:37:36 +0100 (BST)
Received: from eurgbrbh03.emeacinops.xerox.com (unverified) by eurdubmg02.eur.xerox.com
 (Content Technologies SMTPRS 4.2.10) with ESMTP id <T62cd269f1a0dca41feaa4@eurdubmg02.eur.xerox.com> for <ietf@ietf.org>;
 Fri, 13 Jun 2003 10:37:35 +0100
Received: from gbrwgcbh01.wgc.gbr.xerox.com ([13.200.2.175]) by eurgbrbh03.emeacinops.xerox.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59)
	id MGJG1Y7G; Fri, 13 Jun 2003 10:37:34 +0100
Received: by gbrwgcbh01.wgc.gbr.xerox.com with Internet Mail Service (5.5.2654.89)
	id <K6YVVW8J>; Fri, 13 Jun 2003 10:39:52 +0100
Message-ID: <59697CCC6CE3D411B4CD00805FBB776704148127@gbrwgcms03.wgc.gbr.xerox.com>
From: "Brookes, Stuart P" <StuartP.Brookes@gbr.xerox.com>
To: "'ietf@IETF.ORG'" <ietf@ietf.org>
Subject: Implementing IPsec and SSL MIBS? How....
Date: Fri, 13 Jun 2003 10:39:49 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.89)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

I am new to SNMP/MIBs, so am trying to keep my head above water at the
moment.

I would like to implement three simple MIB objects to monitor the following;

SSL enabled/disabled (read only MIB object)
SSL port number (read only)
IPsec enabled/disabled (read only)

There does not appear to be any RFCs for either SSL (Secure Socket Layer) or
IPsec, only draft documents.  

I have found a high level IPsec Flow Monitoring MIB draft document.  I can't
find any sort of 'IPsec enabled/disabled' MIB object? Similarly, would we be
required to implement all the mandatory MIB objects or not?

With regards to SSL, I have looked at the draft document for this but it I
am struggling to understand the descriptions of the MIB objects, as they
don't seem to be laid out as they are in RFCs...  Also, I am specifically
after SSL and not TLS.

If anybody can help I'd be much obliged?

Regards
Stuart





From owner-ietf@ietf.org  Fri Jun 13 18:30:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26520
	for <ietf-web-archive@odin.ietf.org>; Fri, 13 Jun 2003 18:30:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19QwXZ-0006JN-RG
	for ietf-list@asgard.ietf.org; Fri, 13 Jun 2003 17:56:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Qw1S-0005tQ-I7
	for ietf@asgard.ietf.org; Fri, 13 Jun 2003 17:23:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23680;
	Fri, 13 Jun 2003 17:23:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QvzM-0001QK-00; Fri, 13 Jun 2003 17:21:36 -0400
Received: from webmail.movaz.com ([65.205.166.188] helo=jera.movaz.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19QvzL-0001QA-00; Fri, 13 Jun 2003 17:21:35 -0400
Received: from BLIULAPTOP (unknown [172.16.24.104])
	by jera.movaz.com (Postfix) with SMTP
	id 89E02178B; Fri, 13 Jun 2003 17:23:14 -0400 (EDT)
Message-ID: <07b701c331f1$ffeeb820$681810ac@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: <iesg@ietf.org>, <ietf@ietf.org>
Cc: <mpls@UU.NET>
References: <E19Qspn-0000Rd-3H@asgard.ietf.org>
Subject: Re: Last Call: LDP DoD Graceful Restart to Draft Standard 
Date: Fri, 13 Jun 2003 17:23:14 -0400
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-ietf@ietf.org
Precedence: bulk

With respect, this draft doesn't appear to have been through WG last call
(unless I was sleeping, but I can't find any reference in the mail archive).

It was only published as a WG draft on 5/7/2003 (despite carrying a date of
February 2003).

While I support the draft, I would like to see it discussed on the mailing list
and go through WG last call.

Thanks,
Adrian

----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: <IETF-Announce: ;>
Cc: <mpls@UU.NET>
Sent: Friday, June 13, 2003 1:59 PM
Subject: Last Call: LDP DoD Graceful Restart to Draft Standard


> ---------------
> The IESG has received a request from Multiprotocol Label Switching to
> consider the following Internet-Draft(s) as Draft Standard.
> o Multiprotocol Label Switching (MPLS): LDP DoD Graceful Restart
>   <draft-ietf-mpls-ldp-dod-restart-00.txt>
>   Draft Standard
>
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by .
>
> Files can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-dod-restart-00.txt
>





From owner-ietf@ietf.org  Fri Jun 13 21:08:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00527
	for <ietf-web-archive@odin.ietf.org>; Fri, 13 Jun 2003 21:08:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Qyx0-0007pl-Jy
	for ietf-list@asgard.ietf.org; Fri, 13 Jun 2003 20:31:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Qyc1-0007Vy-59
	for ietf@asgard.ietf.org; Fri, 13 Jun 2003 20:09:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29338
	for <ietf@ietf.org>; Fri, 13 Jun 2003 20:09:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QyZu-0002Yz-00
	for ietf@ietf.org; Fri, 13 Jun 2003 20:07:30 -0400
Received: from tc238-194.bbn.com ([128.33.238.194] helo=lawyers.ir.bbn.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19QyZr-0002Yp-00
	for ietf@ietf.org; Fri, 13 Jun 2003 20:07:30 -0400
Received: by lawyers.ir.bbn.com (Postfix, from userid 9076)
	id B0DEE6B2CD; Fri, 13 Jun 2003 12:03:55 -0400 (EDT)
To: ietf@ietf.org
From: Mark Allman <mallman@grc.nasa.gov>
Reply-To: mallman@grc.nasa.gov
Subject: Re: I-D ACTION:draft-hardie-category-descriptions-00.txt 
In-Reply-To: <200306111154.HAA03756@ietf.org> 
Organization: BBN Technologies/NASA GRC
Song-of-the-Day: Self Esteem
Date: Fri, 13 Jun 2003 12:03:55 -0400
Message-Id: <20030613160355.B0DEE6B2CD@lawyers.ir.bbn.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


> 	Title		: A proposal describing categories of IETF documents:
>                           unbaked, baking, baked, eaten, and boiled
> 	Author(s)	: T. Hardie
> 	Filename	: draft-hardie-category-descriptions-00.txt
> 	Pages		: 5
> 	Date		: 2003-6-10

overdone?

allman


--
Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/



From owner-ietf@ietf.org  Fri Jun 13 21:41:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01300
	for <ietf-web-archive@odin.ietf.org>; Fri, 13 Jun 2003 21:41:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Qzn2-0000Mv-UK
	for ietf-list@asgard.ietf.org; Fri, 13 Jun 2003 21:25:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19QzDi-00080X-DK
	for ietf@asgard.ietf.org; Fri, 13 Jun 2003 20:48:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00219
	for <ietf@ietf.org>; Fri, 13 Jun 2003 20:48:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QzBb-0002nC-00
	for ietf@ietf.org; Fri, 13 Jun 2003 20:46:27 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QzBb-0002mf-00
	for ietf@ietf.org; Fri, 13 Jun 2003 20:46:27 -0400
Received: from rshockeybox.shockey.us (h-69-3-5-197.MCLNVA23.covad.net [69.3.5.197])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h5E0pDF32397
	for <ietf@ietf.org>; Fri, 13 Jun 2003 17:51:13 -0700
Message-Id: <5.2.0.9.2.20030613204634.02266130@popd.ix.netcom.com>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 13 Jun 2003 20:47:34 -0400
To: ietf@ietf.org
From: Richard Shockey <richard@shockey.us>
Subject: US Defense Department formally adopts IPv6
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk


Significant news of note..

Vendors must be compliant by Oct 1

http://www.washingtonpost.com/wp-dyn/articles/A55558-2003Jun13.html?nav=hptoc_tn



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




From owner-ietf@ietf.org  Fri Jun 13 23:00:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03214
	for <ietf-web-archive@odin.ietf.org>; Fri, 13 Jun 2003 23:00:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19R0jz-0001cc-Ve
	for ietf-list@asgard.ietf.org; Fri, 13 Jun 2003 22:26:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19R06g-00014f-LO
	for ietf@asgard.ietf.org; Fri, 13 Jun 2003 21:45:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01598
	for <ietf@ietf.org>; Fri, 13 Jun 2003 21:45:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19R04Z-000396-00
	for ietf@ietf.org; Fri, 13 Jun 2003 21:43:15 -0400
Received: from ip166.usw12.rb1.bel.nwlink.com ([209.20.253.166] helo=ran.psg.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19R04Z-000392-00
	for ietf@ietf.org; Fri, 13 Jun 2003 21:43:15 -0400
Received: from localhost ([127.0.0.1] helo=ran.psg.com)
	by ran.psg.com with esmtp (Exim 4.20)
	id 19R06b-000Hfa-2Z; Fri, 13 Jun 2003 18:45:21 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 13 Jun 2003 18:45:20 -0700
To: Richard Shockey <richard@shockey.us>
Cc: ietf@ietf.org
Subject: Re: US Defense Department formally adopts IPv6
References: <5.2.0.9.2.20030613204634.02266130@popd.ix.netcom.com>
Message-Id: <E19R06b-000Hfa-2Z@ran.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

hyperbole alert!

> Vendors must be compliant by Oct 1
> http://www.washingtonpost.com/wp-dyn/articles/A55558-2003Jun13.html?nav=hptoc_tn

that's not what is says at all.  what is says is

"The evolution toward the new standard must be taken into account for all
purchases starting Oct. 1"

which, if you have played in that game, means little beyond powerpoint
and promises.

randy




From owner-ietf@ietf.org  Fri Jun 13 23:01:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03353
	for <ietf-web-archive@odin.ietf.org>; Fri, 13 Jun 2003 23:01:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19R0kD-0001di-48
	for ietf-list@asgard.ietf.org; Fri, 13 Jun 2003 22:26:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19R0Fh-00019n-Ap
	for ietf@asgard.ietf.org; Fri, 13 Jun 2003 21:54:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01890
	for <ietf@ietf.org>; Fri, 13 Jun 2003 21:54:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19R0Da-0003Ba-00
	for ietf@ietf.org; Fri, 13 Jun 2003 21:52:34 -0400
Received: from ds20-1.cc.swin.edu.au ([136.186.1.150] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 19R0DZ-0003BQ-00
	for ietf@ietf.org; Fri, 13 Jun 2003 21:52:33 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2/8.9.3) with ESMTP id LAA1956895;
	Sat, 14 Jun 2003 11:54:01 +1000 (EST)
Message-ID: <3EEA8039.BBF8718A@swin.edu.au>
Date: Sat, 14 Jun 2003 11:54:01 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Crocker <dcrocker@brandenburg.com>
CC: ietf@ietf.org, Brian E Carpenter <brian@hursley.ibm.com>
Subject: Re: Recruitment of Experimental SIRs
References: <13695462427.20030602131247@brandenburg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> We'd like to run a proof-of-concept version of the Senior Internet
> Reviewer (SIR) activity,

I keep waiting for someone to suggest adding

 MAture Document-Aquisition Moderator - MADAM

but then I realize everyone else has more self control.

cheers,
gja



From owner-ietf@ietf.org  Fri Jun 13 23:14:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03789
	for <ietf-web-archive@odin.ietf.org>; Fri, 13 Jun 2003 23:14:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19R11S-0001pw-5z
	for ietf-list@asgard.ietf.org; Fri, 13 Jun 2003 22:44:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19R0ZZ-0001Rq-AM
	for ietf@asgard.ietf.org; Fri, 13 Jun 2003 22:15:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02313
	for <ietf@ietf.org>; Fri, 13 Jun 2003 22:15:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19R0XS-0003Id-00
	for ietf@ietf.org; Fri, 13 Jun 2003 22:13:06 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19R0XR-0003Ia-00
	for ietf@ietf.org; Fri, 13 Jun 2003 22:13:05 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h5E2FEoY029339
	for <ietf@ietf.org>; Sat, 14 Jun 2003 04:15:14 +0200 (CEST)
Message-ID: <0b8701c3321a$ca4f02a0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <5.2.0.9.2.20030613204634.02266130@popd.ix.netcom.com>
Subject: Re: US Defense Department formally adopts IPv6
Date: Sat, 14 Jun 2003 04:15:13 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Didn't the DoD officially adopt Ada about 20 years ago?

----- Original Message -----
From: "Richard Shockey" <richard@shockey.us>
To: <ietf@ietf.org>
Sent: Saturday, June 14, 2003 02:47
Subject: US Defense Department formally adopts IPv6


>
> Significant news of note..
>
> Vendors must be compliant by Oct 1
>
>
http://www.washingtonpost.com/wp-dyn/articles/A55558-2003Jun13.html?nav=hpto
c_tn
>
>
>
>  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Richard Shockey, Senior Manager, Strategic Technology Initiatives
> NeuStar Inc.
> 46000 Center Oak Plaza  -   Sterling, VA  20166
> Voice +1 571.434.5651 Cell : +1 703.593.2683,  Fax: +1 815.333.1237
> <mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
>   <http://www.neustar.biz> ; <http://www.enum.org>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
>
>




From owner-ietf@ietf.org  Sat Jun 14 00:23:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05422
	for <ietf-web-archive@odin.ietf.org>; Sat, 14 Jun 2003 00:23:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19R24H-0003Zf-3v
	for ietf-list@asgard.ietf.org; Fri, 13 Jun 2003 23:51:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19R1K9-0002hT-Hp
	for ietf@asgard.ietf.org; Fri, 13 Jun 2003 23:03:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03528
	for <ietf@ietf.org>; Fri, 13 Jun 2003 23:03:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19R1I2-0003bA-00
	for ietf@ietf.org; Fri, 13 Jun 2003 23:01:14 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19R1I1-0003b2-00
	for ietf@ietf.org; Fri, 13 Jun 2003 23:01:13 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h5E360F05223;
	Fri, 13 Jun 2003 20:06:00 -0700
Date: Fri, 13 Jun 2003 20:02:54 -0700
From: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: The Bat! (v1.63 Beta/10) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <8140585729.20030613200254@brandenburg.com>
To: Richard Shockey <richard@shockey.us>
CC: ietf@ietf.org
Subject: Re: US Defense Department formally adopts IPv6
In-Reply-To: <5.2.0.9.2.20030613204634.02266130@popd.ix.netcom.com>
References: <5.2.0.9.2.20030613204634.02266130@popd.ix.netcom.com>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Richard,


RS> Significant news of note..

RS> Vendors must be compliant by Oct 1

RS> http://www.washingtonpost.com/wp-dyn/articles/A55558-2003Jun13.html?nav=hptoc_tn


So, let's see.  The guys says that the problems with IPv4 are:

     1) security

     2) data loss
   
     3) telephone-like numbering

and that IPv6 will fix them.

Are there enhancements in IPv6 that we haven't been hearing about?

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




From owner-ietf@ietf.org  Sat Jun 14 09:19:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24668
	for <ietf-web-archive@odin.ietf.org>; Sat, 14 Jun 2003 09:19:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RAE0-00070r-6W
	for ietf-list@asgard.ietf.org; Sat, 14 Jun 2003 08:33:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19R9xS-0006jK-C7
	for ietf@asgard.ietf.org; Sat, 14 Jun 2003 08:16:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23828
	for <ietf@ietf.org>; Sat, 14 Jun 2003 08:16:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19R9vK-0005tn-00
	for ietf@ietf.org; Sat, 14 Jun 2003 08:14:22 -0400
Received: from unknown-1-11.windriver.com ([147.11.1.11] helo=mail.wrs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19R9vK-0005td-00
	for ietf@ietf.org; Sat, 14 Jun 2003 08:14:22 -0400
Received: from IDLEWYLDE.windriver.com ([147.11.233.3])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id FAA19115;
	Sat, 14 Jun 2003 05:15:34 -0700 (PDT)
Message-Id: <5.1.0.14.2.20030614080530.035f5690@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 14 Jun 2003 08:11:40 -0400
To: Randy Bush <randy@psg.com>
From: Margaret Wasserman <mrw@windriver.com>
Subject: Re: US Defense Department formally adopts IPv6
Cc: ietf@ietf.org
In-Reply-To: <E19R06b-000Hfa-2Z@ran.psg.com>
References: <5.2.0.9.2.20030613204634.02266130@popd.ix.netcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 06:45 PM 6/13/2003 -0700, Randy Bush wrote:
>hyperbole alert!
>
> > Vendors must be compliant by Oct 1
> > 
> http://www.washingtonpost.com/wp-dyn/articles/A55558-2003Jun13.html?nav=hptoc_tn
>
>that's not what is says at all.  what is says is
>
>"The evolution toward the new standard must be taken into account for all
>purchases starting Oct. 1"

The U.S. DoD's actual press release (included below) says:

"A key element of the transition minimizes future transition
costs by requiring that, starting in October 2003, all network
capabilities purchased by DoD be both IPv6-capable and
interoperable with the department's extensive IPv4 installed
base."

I have not yet seen the actual policy memorandum -- I'm
still trying to get a copy.  So, I'm not sure how "IPv6-
capable" is defined.

Margaret


NEWS RELEASE from the United States Department of Defense
No. 413-03
IMMEDIATE RELEASE
Jun 13, 2003
(703)697-5131(media)
(703)428-0711(public/industry)

Next-Generation Internet Protocol to Enable Net-Centric Operations

Implementation of the next-generation Internet protocol that will
bring the Department of Defense closer to its goal of net-centric
warfare and operations was announced today by John P. Stenbit,
assistant secretary of defense for networks and information
integration and DoD chief information officer.

The new Internet protocol, known as IPv6, will facilitate integration
of the essential elements of DoD's Global Information Grid -- its
sensors, weapons, platforms, information and people. Secretary Stenbit
is directing the DoD-wide transition.

The current version of the Internet's operating system, IPv4, has been
in use by DoD for almost 30 years. Its fundamental limitations, along
with the world-wide explosion of Internet use, inhibit net-centric
operations. IPv6 is designed to overcome those limitations by expanding
available IP address space, improving end-to-end security, facilitating
mobile communications, enhancing quality of service and easing system
management burdens.

Enterprise-wide deployment of IPv6 will keep the warfighter secure and
connected in a fast-moving battlespace, Secretary Stenbit said. Achievement
of net-centric operations and warfare depends on effectively implementing
the transition.

Secretary Stenbit signed a policy memorandum on June 9 that outlines a
strategy to ensure an integrated, timely and effective transition. A key
element of the transition minimizes future transition costs by requiring
that, starting in October 2003, all network capabilities purchased by
DoD be both IPv6-capable and interoperable with the department's extensive
IPv4 installed base.

[Web Version: http://dod.mil/releases/2003/nr20030613-0097.html]
-- News Releases: http://www.defenselink.mil/news/releases.html
-- DoD News: http://www.defenselink.mil/news/dodnews.html
-- Subscribe/Unsubscribe:
http://www.defenselink.mil/news/dodnews.html#e-mail
-- Today in DoD: http://www.defenselink.mil/today





From owner-ietf@ietf.org  Sat Jun 14 10:12:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26178
	for <ietf-web-archive@odin.ietf.org>; Sat, 14 Jun 2003 10:12:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RBAF-0007nR-65
	for ietf-list@asgard.ietf.org; Sat, 14 Jun 2003 09:33:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RAhn-0007DY-Hx
	for ietf@asgard.ietf.org; Sat, 14 Jun 2003 09:04:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24505
	for <ietf@ietf.org>; Sat, 14 Jun 2003 09:04:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RAfg-00064b-00
	for ietf@ietf.org; Sat, 14 Jun 2003 09:02:16 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RAff-00064Y-00
	for ietf@ietf.org; Sat, 14 Jun 2003 09:02:15 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h5ED4KtU011582;
	Sat, 14 Jun 2003 09:04:20 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h5ED4JAK011581;
	Sat, 14 Jun 2003 09:04:19 -0400
Date: Sat, 14 Jun 2003 09:04:19 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200306141304.h5ED4JAK011581@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: US Defense Department formally adopts IPv6
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: "Anthony Atkielski" <anthony@atkielski.com>

    > Didn't the DoD officially adopt Ada about 20 years ago?

I do seem to recall that it was around the time that they "mandated" CLNP/TP
(instead of TCP/IP).

	Noel



From owner-ietf@ietf.org  Sat Jun 14 10:44:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27014
	for <ietf-web-archive@odin.ietf.org>; Sat, 14 Jun 2003 10:44:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RBre-0006E4-Ev
	for ietf-list@asgard.ietf.org; Sat, 14 Jun 2003 10:18:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RBD7-0007o4-TQ
	for ietf@asgard.ietf.org; Sat, 14 Jun 2003 09:36:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24955
	for <ietf@ietf.org>; Sat, 14 Jun 2003 09:36:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RBB0-0006Ck-00
	for ietf@ietf.org; Sat, 14 Jun 2003 09:34:38 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RBAz-0006Ch-00
	for ietf@ietf.org; Sat, 14 Jun 2003 09:34:37 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5EDajWp029565
	for ietf@ietf.org env-from <vjs>;
	Sat, 14 Jun 2003 07:36:45 -0600 (MDT)
Date: Sat, 14 Jun 2003 07:36:45 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306141336.h5EDajWp029565@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: US Defense Department formally adopts IPv6
References:  <5.1.0.14.2.20030614080530.035f5690@mail.windriver.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Margaret Wasserman <mrw@windriver.com>

> ...
> >"The evolution toward the new standard must be taken into account for all
> >purchases starting Oct. 1"

> ...
> I have not yet seen the actual policy memorandum -- I'm
> still trying to get a copy.  So, I'm not sure how "IPv6-
> capable" is defined.

We're using TCP/IP today, despite most of a decade of GOSIP
requirements requiring the switch to the ISO OSI protocol suite.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sat Jun 14 10:47:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27170
	for <ietf-web-archive@odin.ietf.org>; Sat, 14 Jun 2003 10:47:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RBzZ-0006HN-R3
	for ietf-list@asgard.ietf.org; Sat, 14 Jun 2003 10:26:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RBKB-0007rH-MN
	for ietf@asgard.ietf.org; Sat, 14 Jun 2003 09:44:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25005
	for <ietf@ietf.org>; Sat, 14 Jun 2003 09:44:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RBI3-0006De-00
	for ietf@ietf.org; Sat, 14 Jun 2003 09:41:55 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19RBI3-0006Db-00
	for ietf@ietf.org; Sat, 14 Jun 2003 09:41:55 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19RBK3-0009oX-00; Sat, 14 Jun 2003 08:43:59 -0500
Date: Sat, 14 Jun 2003 09:43:59 -0400
From: John C Klensin <john-ietf@jck.com>
To: Margaret Wasserman <mrw@windriver.com>, Randy Bush <randy@psg.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: US Defense Department formally adopts IPv6
Message-ID: <154604930.1055583839@p3.JCK.COM>
In-Reply-To: <5.1.0.14.2.20030614080530.035f5690@mail.windriver.com>
References: <5.2.0.9.2.20030613204634.02266130@popd.ix.netcom.com>
  <5.1.0.14.2.20030614080530.035f5690@mail.windriver.com>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

While this type of procurement announcement is certainly not bad 
news for IPv6 --almost independent of how the details are 
interpreted-- anyone planning to get really excited about it 
(positively or negatively) should examine RFC 942 and related 
documents and consider the impact of a previous time the DoD 
made one of these sweeping policy/procurement announcements 
related to the Internet.

      john


--On Saturday, 14 June, 2003 08:11 -0400 Margaret Wasserman 
<mrw@windriver.com> wrote:

> At 06:45 PM 6/13/2003 -0700, Randy Bush wrote:
>> hyperbole alert!
>>
>> > Vendors must be compliant by Oct 1
>> >
>> http://www.washingtonpost.com/wp-dyn/articles/A55558-2003Jun1
>> 3.html?nav=hptoc_tn
>>
>> that's not what is says at all.  what is says is
>>
>> "The evolution toward the new standard must be taken into
>> account for all purchases starting Oct. 1"
>
> The U.S. DoD's actual press release (included below) says:
>
> "A key element of the transition minimizes future transition
> costs by requiring that, starting in October 2003, all network
> capabilities purchased by DoD be both IPv6-capable and
> interoperable with the department's extensive IPv4 installed
> base."
>
> I have not yet seen the actual policy memorandum -- I'm
> still trying to get a copy.  So, I'm not sure how "IPv6-
> capable" is defined.
>
> Margaret
>
>
> NEWS RELEASE from the United States Department of Defense
> No. 413-03
> IMMEDIATE RELEASE
> Jun 13, 2003
> (703)697-5131(media)
> (703)428-0711(public/industry)
>
> Next-Generation Internet Protocol to Enable Net-Centric
> Operations
>
> Implementation of the next-generation Internet protocol that
> will bring the Department of Defense closer to its goal of
> net-centric warfare and operations was announced today by John
> P. Stenbit, assistant secretary of defense for networks and
> information integration and DoD chief information officer.
>
> The new Internet protocol, known as IPv6, will facilitate
> integration of the essential elements of DoD's Global
> Information Grid -- its sensors, weapons, platforms,
> information and people. Secretary Stenbit is directing the
> DoD-wide transition.
>
> The current version of the Internet's operating system, IPv4,
> has been in use by DoD for almost 30 years. Its fundamental
> limitations, along with the world-wide explosion of Internet
> use, inhibit net-centric operations. IPv6 is designed to
> overcome those limitations by expanding available IP address
> space, improving end-to-end security, facilitating mobile
> communications, enhancing quality of service and easing system
> management burdens.
>
> Enterprise-wide deployment of IPv6 will keep the warfighter
> secure and connected in a fast-moving battlespace, Secretary
> Stenbit said. Achievement of net-centric operations and
> warfare depends on effectively implementing the transition.
>
> Secretary Stenbit signed a policy memorandum on June 9 that
> outlines a strategy to ensure an integrated, timely and
> effective transition. A key element of the transition
> minimizes future transition costs by requiring that, starting
> in October 2003, all network capabilities purchased by DoD be
> both IPv6-capable and interoperable with the department's
> extensive IPv4 installed base.
>
> [Web Version:
> http://dod.mil/releases/2003/nr20030613-0097.html] -- News
> Releases: http://www.defenselink.mil/news/releases.html -- DoD
> News: http://www.defenselink.mil/news/dodnews.html --
> Subscribe/Unsubscribe:
> http://www.defenselink.mil/news/dodnews.html#e-mail
> -- Today in DoD: http://www.defenselink.mil/today
>
>
>







From owner-ietf@ietf.org  Sat Jun 14 12:21:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28532
	for <ietf-web-archive@odin.ietf.org>; Sat, 14 Jun 2003 12:21:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RD3t-0007dQ-3P
	for ietf-list@asgard.ietf.org; Sat, 14 Jun 2003 11:35:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RCaq-0007KK-Jy
	for ietf@asgard.ietf.org; Sat, 14 Jun 2003 11:05:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27475
	for <ietf@ietf.org>; Sat, 14 Jun 2003 11:05:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RCYi-0006Xv-00
	for ietf@ietf.org; Sat, 14 Jun 2003 11:03:12 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RCYi-0006Xq-00
	for ietf@ietf.org; Sat, 14 Jun 2003 11:03:12 -0400
Received: from rshockeybox.shockey.us (h-69-3-5-197.MCLNVA23.covad.net [69.3.5.197])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h5EF7xF29410;
	Sat, 14 Jun 2003 08:07:59 -0700
Message-Id: <5.2.0.9.2.20030614110342.01dd78c8@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sat, 14 Jun 2003 11:05:07 -0400
To: Randy Bush <randy@psg.com>
From: Richard Shockey <richard@shockey.us>
Subject: Re: US Defense Department formally adopts IPv6
Cc: ietf@ietf.org
In-Reply-To: <E19R06b-000Hfa-2Z@ran.psg.com>
References: <5.2.0.9.2.20030613204634.02266130@popd.ix.netcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 06:45 PM 6/13/2003 -0700, Randy Bush wrote:

>hyperbole alert!
>
> > Vendors must be compliant by Oct 1
> > 
> http://www.washingtonpost.com/wp-dyn/articles/A55558-2003Jun13.html?nav=hptoc_tn
>
>that's not what is says at all.  what is says is
>
>"The evolution toward the new standard must be taken into account for all
>purchases starting Oct. 1"
>
>which, if you have played in that game, means little beyond powerpoint
>and promises.

perhaps but you read the transcript

http://www.dod.gov/transcripts/2003/tr20030613-0274.html




>randy


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




From owner-ietf@ietf.org  Sat Jun 14 12:47:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28858
	for <ietf-web-archive@odin.ietf.org>; Sat, 14 Jun 2003 12:47:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RDev-0007vi-Vy
	for ietf-list@asgard.ietf.org; Sat, 14 Jun 2003 12:13:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RDEf-0007k0-AC
	for ietf@asgard.ietf.org; Sat, 14 Jun 2003 11:46:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28002
	for <ietf@ietf.org>; Sat, 14 Jun 2003 11:46:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RDCX-0006fA-00
	for ietf@ietf.org; Sat, 14 Jun 2003 11:44:21 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19RDCW-0006f0-00
	for ietf@ietf.org; Sat, 14 Jun 2003 11:44:20 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 2760962577; Sat, 14 Jun 2003 17:46:01 +0200 (CEST)
Date: Sat, 14 Jun 2003 17:46:01 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: grenville armitage <garmitage@swin.edu.au>
Cc: ietf@ietf.org
Subject: Re: Recruitment of Experimental SIRs
Message-ID: <136730000.1055605561@askvoll.hjemme.alvestrand.no>
In-Reply-To: <3EEA8039.BBF8718A@swin.edu.au>
References: <13695462427.20030602131247@brandenburg.com>
 <3EEA8039.BBF8718A@swin.edu.au>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA28858



--On lørdag, juni 14, 2003 11:54:01 +1000 grenville armitage 
<garmitage@swin.edu.au> wrote:

>
>> We'd like to run a proof-of-concept version of the Senior Internet
>> Reviewer (SIR) activity,
>
> I keep waiting for someone to suggest adding
>
>  MAture Document-Aquisition Moderator - MADAM
>
> but then I realize everyone else has more self control.

That's the new title for those who shepherd mailing list discussions....

Mail Activity Director And Moderator.

Proving once again that I have no self-control :-)




From owner-ietf@ietf.org  Sun Jun 15 08:35:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29465
	for <ietf-web-archive@odin.ietf.org>; Sun, 15 Jun 2003 08:35:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RWNc-0007Ma-QC
	for ietf-list@asgard.ietf.org; Sun, 15 Jun 2003 08:13:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RWLV-0007Jg-Dn
	for ietf@asgard.ietf.org; Sun, 15 Jun 2003 08:10:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29116;
	Sun, 15 Jun 2003 08:10:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RWJL-0003Co-00; Sun, 15 Jun 2003 08:08:39 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RWJK-0003Cl-00; Sun, 15 Jun 2003 08:08:38 -0400
Received: from MOU1WNEXC03.verisign.com (verisign.com [65.205.251.57])
        by peacock.verisign.com (8.12.9/) with ESMTP id h5FCAkh6029512;
        Sun, 15 Jun 2003 05:10:46 -0700 (PDT)
Received: by mou1wnexc03.verisign.com with Internet Mail Service (5.5.2653.19)
	id <MLJJRZ2Y>; Sun, 15 Jun 2003 05:10:46 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D222C@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Vern Paxson'" <vern@icir.org>,
        "Hallam-Baker, Phillip"
	 <pbaker@verisign.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Cc: "'Paul Judge'" <paul.judge@ciphertrust.com>,
        "'Kee Hinckley'"
	 <nazgul@somewhere.com>,
        "'Asrg@ietf.org'" <Asrg@ietf.org>
Subject: CLOSE ASRG NOW IT HAS FAILED
Date: Sun, 15 Jun 2003 05:10:43 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk


> But that's not the requirement.  The requirement is to 
> disclose knowledge
> of the existence of IPR, not to try to secure a license to it.
> 
> Given that, do you still disagree with the requirement?

I disagree with the requirement because I don't think there is 
an enforceable requirement. I think that if there is a problem
and a court case results, that the way the IPR policy has been
enacted will allow any barely competent lawyer to get arround
it.

The way to reference the RFC 2026 text is by stating that the 
group will be run according to RFC 2026. I am not a lawyer
but I do know something about the difference between specifying
a policy by reference and by direct quotation.


I disagree with any requirement imposed by a working group chair 
who believes he is not accountable to the group. I do not think
that the way an IPR regime should be specified is a unilateral
statement from the chair that a decision has been taken.

An IPR policy should not be something that members of a group 
discover when they are told it has been imposed from above. 


What happened to open and inclusive?


So far we have had a deliberate campaign of heckling that the 
chair did nothing to stop followed by the chair taking sanctions
against anyone who complained about the hecklers.

Five members of the group have resigned in disgust at the heckler
faction.

You will note that none of the posts I have sent on this topic
have made it to the list. So even if I do make a statement
concerning IPR the chances are that the post will be seen are
nil.

The chair has admitted that the reason my posts are blocked is 
that I am working on starting anti-spam groups in other forums,
I am not aware that that type of move has EVER been sanctioned
by IETF process.


The chair has contributed nothing of value to this debate, his sole interest
in the group appears to be exploiting it for PR value to promote his
company, not the group.

I have no confidence in Paul Judge as chair. I believe that his handling of
the group is damaging the IETF. The group may be in the IRTF but the mailing
list bears the name IETF and it the group is being presented to the press as
having been charged by the IETF to solve the problem.

The FTC testimony was dire. The ASRG chair stated that he believed the group
would come up with a technical solution. Every one of the other members of
the
technical panel then stated that they thought it had already failed. It made
the IETF look ridiculous. 

If group chairs are going to have this degree of power it would probably be
a good idea to have a process that is a little more formal for selecting
them than choosing the first person to make a proposal. It would probably be
a good idea to choose chairs that have some experience of being an ordinary
working group member before they act as chair.

It would be a really good idea to allow groups to have input into the
selection of chairs. This top heavy dictatorial style is not working, is not
open and is not inclusive.


At this point the heckler faction have been allowed to drive away most of
the productive members of the group. 

		Phill



From owner-ietf@ietf.org  Sun Jun 15 09:04:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00840
	for <ietf-web-archive@odin.ietf.org>; Sun, 15 Jun 2003 09:04:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RX2y-00082j-Rq
	for ietf-list@asgard.ietf.org; Sun, 15 Jun 2003 08:55:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RWzj-000810-LH
	for ietf@asgard.ietf.org; Sun, 15 Jun 2003 08:52:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29875
	for <ietf@ietf.org>; Sun, 15 Jun 2003 08:52:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RWxa-0003O6-00
	for ietf@ietf.org; Sun, 15 Jun 2003 08:50:14 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RWxZ-0003O3-00
	for ietf@ietf.org; Sun, 15 Jun 2003 08:50:13 -0400
Received: from mou1wnexc02.verisign.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.9/) with ESMTP id h5FCqPh6005173
        for <ietf@ietf.org>; Sun, 15 Jun 2003 05:52:25 -0700 (PDT)
Received: by mou1wnexc02.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LYL9VS5T>; Sun, 15 Jun 2003 05:52:25 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D2230@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: US Defense Department formally adopts IPv6
Date: Sun, 15 Jun 2003 05:52:24 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

In response to John's RFC 942 point:


Reading the document the gist of the argument appears to be 'there is no
real technical difference between the protocols that is significant enough
to decide the issue, but OSI is what everyone else is planning to use'.

So actually I would say it was the opposite of the ADA situation, quite
likely given the date even an attempt not to make the ADA mistake a second
time (ADA was a train wreck predicted long in advance).


OSI came far closer to succeeding despite the problems in the design than
many here appear to want to admit. Without classless addresses the IPv4
space would have run out in 1992. It is ironic that X.500 is one of the few
parts of the stack left, if X.500 had ever worked we might all be speaking
ASN.1...


		Phill






From owner-ietf@ietf.org  Mon Jun 16 01:33:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20086
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 01:33:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RmIa-0001IJ-SN
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 01:12:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RmHB-0001I2-JN
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 01:11:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19615
	for <ietf@ietf.org>; Mon, 16 Jun 2003 01:11:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RmF0-0007Ak-00
	for ietf@ietf.org; Mon, 16 Jun 2003 01:09:14 -0400
Received: from flat03.bekkoame.ne.jp ([202.231.202.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RmEu-0007Ah-00
	for ietf@ietf.org; Mon, 16 Jun 2003 01:09:08 -0400
Received: from Zsz (YahooBB218183048064.bbtec.net [218.183.48.64])
	by flat03.bekkoame.ne.jp (8.11.6+Sun/3.7W-FLAT) with SMTP id h5G5B8626771;
	Mon, 16 Jun 2003 14:11:08 +0900 (JST)
	(envelope-from n-asaoka@sg-assn.org)
Date: Mon, 16 Jun 2003 14:11:08 +0900 (JST)
Message-Id: <200306160511.h5G5B8626771@flat03.bekkoame.ne.jp>
From: mo <mo@ccr.org>
To: ietf@ietf.org
Subject: Cellspacing
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=Q52Hb45K5793kjz9Ys23aViasld1L
Sender: owner-ietf@ietf.org
Precedence: bulk

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

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

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

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

--Q52Hb45K5793kjz9Ys23aViasld1L

Content-Type: application/octet-stream;
	name=wli-isa-op.jpg
Content-Transfer-Encoding: base64
Content-ID: <I13B7I5E911>

/9j/4AAQSkZJRgABAQIAHAAcAAD/2wBDAAoHCAkIBgoJCAkMCwoMDxoRDw4ODx8WGBMaJSEn
JiQhJCMpLjsyKSw4LCMkM0Y0OD0/QkNCKDFITUhATTtBQj//2wBDAQsMDA8NDx4RER4/KiQq
Pz8/Pz8/Pz8/Pz8/Pz8/Pz8/Pz8/Pz8/Pz8/Pz8/Pz8/Pz8/Pz8/Pz8/Pz8/Pz8/Pz//wAAR
CABkAJYDASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAA
AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG
h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl
5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA
AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk
NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk
5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDt2PzGkpT1pkjeWjNjgDNakDqKxP7auT0s
F/7/AI/wo/tm7xn7AuP+uw/wpmftodzbpaxP7YvBn/QU4/6bD/CkOs3g/wCXKP8A7/f/AFqA
9tDublFYf9sXn/PnH/3+/wDrUv8Aat9k/wChR/8Af3/61Ae1h3NvJpKxDq19nH2OPP8A11/+
tQdS1H/nzi/7+H/CkHtYm3mkzWGdWv8A/n1h/wC/v/1qT+1r/wD59oP+/p/woF7aBuZNNJrD
/tXUP+fa3/7+n/CmPq2oKMm3tuTjiUn29KYe3gb4bnrUiEk9a5r+1dSB/wBRa4/66N/hUkGs
Xu4iWCHOPl8tiT1Geo9KLAq8JOyZ0rAgVHk+tZ0F1JKyBriQgdRtUZ+vFXt1I2sSAmimq1FA
iRhzUNyP9Hk/3T/KrBHNQ3Q/0aT/AHT/ACoB7HIF1sbSLzZ3Kg/fbJJ6nFTpdwyWpkhaRhjL
BEPP+c0ssrQxF8Haq1DazrcIZdhBORksehAz+eB+VB50eWzch6X6SFkZmjJJGN+QOvU/hTJJ
LkzGKOIKq872GQ3qOAT3/SoGIimkiXaLcYLIWYtjH/16tTyiKVfOJZNrDgtydpC9OepB/Cld
mrjFSVluUrZ7qPUPOmiuJoo3/wBXjaJB+ePWrV7fzNcym10yWCInIVmIPA547d6baXEki2zx
RMLpGYlt7DCkDA6c8ioZ7m4aYxwxoI4vlUuWdj+OMngn9aXmbrT3bD7G+b7dtkYCcSeXGpkK
knt68c1uC21gXKH7NMBuO758gjBI6+h/nXJjzGdGjkdAWXz1GQHO7IznsOMfSuwuvDeovr81
/bXwhWSfftSZ1JXHQgDH4dKLg6fUhbSr4klbVwPQ81EFa4vHt4kga4QYeFJF3LjHUA5FUNUt
idWvT5s3zTucea2Bz254+lUU0y3SUzIgWZusg4Y/U1WpxSdKLa1/A6T+zr/yyv2PORj3HT39
qz5o5obgWwMX2skFYGlXe34ZrP8AsnP33/77NQT6dAWE5TMwIxJn5hz69aLMSnT5k9TZvDea
PAl9NFCHYA7JXVRyCSBvxkj09exqDT/FEGqXNpafYgs21g0gIwc8g9PY1nyafFKR5u6TByN7
E/zqbS7C3g1q1aKNUOT0GKmUFuzpo4iCfJFbnSW8W3HFXlHFRxJVkLxTOwRVop6iimIkPWoL
r/j2k/3T/KrB61Bdf8e0v+6f5UCexyF8wFrLjp5fJx7VX0p1azwp+63X14FGoStgQ42xlRvc
nJx0wPc060aKQGVEZSRj5ifbtnFI813VN36st5z3zVW5QvdQOse4D5WGcDGRVoxu1jJcxFCk
L7ZdxIK8A5xjkfMKxLq5vjcq24xQOAeQOPXJ9ad0x06dWMrpE8dwYXkjQbYkypJOCGBI49sf
59M43B8/zFMQXou4N0B9qnka3kTy3lTHUEE4qpcAl/3Tkqo+YqpIHNJWOxqV7s1POE6llcyY
dcsF2jr6V6vgZzk15Hp7xRvHIytNDHNGWyMZAYEjH0r1K2aSMSCefzi0jMp2Bdqk8Lx1x60o
m72RxeqEDVLz/rs/86rg8VPqZzql3/12b+dVh0q0eLV+NjiajnP7lvw/nTs1HOf3DUzJPUkJ
qSx/5C9n/v1CTUticataH/bpPY0oP97E6mMVPjio4x0qUDipPbBRRTlFFMQ49ahuh/osv+4f
5VOetQXf/HpL/uH+VIHsefauyhyvBBROT/vVJpLhrEAYIB/oKffWkdxEsk0hUL8oIfrx0qpB
b21zHlHkjIPKIVA/NRihWuee/epNEl4Ns2zcViyJGQMdrN0yR07VUuzGbQiPsB+FSz7A7Ijl
giquSeeCf8ahlczxCCKJQejPu7DnP9KT3N6D0V2UpcbUGMEoDmp9LSOQOJQzAEHA79aU6dcP
k+YpC/L1P1x0pFW80/ey2vmq6gZByfXp17d6G77HTpbUnjjMdvKWjZT5i9T716jjcc7iPYV5
Kbt5VWIxeS7uo/esSX569OPxNdXdWl7PrMs8OuRwWxkBRftuBjjgAGhaEuVkrIj1Fh/ad0P+
mzVADV27tFnv7mZNQsQkkjFc3I5B6VQiAa+a1NxAgGcyvKBGcehqkzyqlGo5t2H5qOc/uH+l
XxYLj/kJ6fj/AK+BVG7QJcfZRcW7iQAeasy7Fz6nOf0p3IVCpfYUmpLQ41G3P+1SX8DWdoLg
PHcqcHEDhjgg4bnAxwaz7HVrabU7eOPeWLf3elJtWLo0akaibR6ClTVGlSUj2By0Uq0UxCN1
qC7H+iTf7h/lVkjmobv/AI9Jf9w/ypA9jijcxDT5Vfct0CQgC5yu0dfTuc+1ctazzQSNKZ5F
U/KOeW+n+NdE1mXZ5vtDgmMttCrjPksfT/ZA+hNRnw9aveiNp5iBJs6jp5yr6ehrFVYIXsZN
JHPxTvLcp/Cu7AUem2tGyhXy0lY4DOxz17kdPyqzHoVsLUSCaYNs38EdfJLenqKuQ6JbR3+w
TzkebsJLDJHnBPT0NOVWPQaoyRHNbSQWaXGd8bMV47HOMEH3FU7ydbS4eGQkOF3YxgH0qeHS
buO3imuLsmAxOyKqgYPlu47eo/Wrdzolte3m2eeYhH2rgqMDzUX09GNEpqLsyY0ubVbHPSRx
3brJ9qUKTgqwbA56/d+tTi3E9usEf2T5Od6x/MB7+vXvVuPQrX7NvE04JhLHDDqI3b09VFWB
4fsvtXlCa4CeZt+8OnmIvp6E1PtoocqFRr3XYx2sBCA1wqSRd9iBSvvwOasz6RbC2UxECWaP
zIwzDGNwGM9CeelVdWik06Kz+x3E/wC9j3MGOecA+nvWrpumR3en2CT3FxtULhQwAXc8YPb0
J/T0qnUikmZ06FTmfO7kVtaWipGk0ggQggMyg/NxweRjgk/hTJ4bfEill8oI22Rhjd0wQMn3
qcaJbfZUPnXORFvH7z+Lynb09QKr3mivd66NPimlaJULDec42uygZxxwBRGopOyY6lBKN7CS
wQSwi3ku2e3UfKjzEgYBx9Ov4VNYWenw29mY2UXqygyFGLfLz3P4VIvgiYgfvSPx/wDrVdsP
CDWUjztKWIXAGR6j2q5QT6k0vaw03v3/AOHO0i5UGpcU2IYUCn4qjcVBRSrRTEKetIyhlKsM
g9aeRzSYoApHTbX/AJ5j8hSjTrbOdnP4VcxRip5V2K5mUv7Ntumzj6ClGnWw52VdxRijlXYX
Mys1pC0YjKDaOlR/2bbf3Ku4oxRZBcpf2bb/ANz9KT+zLbOdnNX8UmKOVBdlL+zbcdFpDptu
T0q/ikxRZBdlD+zIPQ0+Oxiifco5q5ilxTsguyAp6VFcjFtLx/DVorzUV4v+hTcZ+Q8evFFg
uInFSUIvFOC0AItFPVaKYhxApMUUUgDFGBRRQAuKMCiigAApcUUUAGBRgUUUAGBSYoooAUAU
uBRRQAbRSEDFFFMBoUCnBRRRQA9QKKKKAP/Z
--Q52Hb45K5793kjz9Ys23aViasld1L--



From owner-ietf@ietf.org  Mon Jun 16 02:38:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03470
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 02:38:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RnOK-0008CY-Mq
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 02:22:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RnKA-0007WF-Ha
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 02:18:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02873;
	Mon, 16 Jun 2003 02:18:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RnHy-0007bU-00; Mon, 16 Jun 2003 02:16:22 -0400
Received: from jaguar.icir.org ([192.150.187.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RnHy-0007bR-00; Mon, 16 Jun 2003 02:16:22 -0400
Received: from jaguar.icir.org (localhost [127.0.0.1])
	by jaguar.icir.org (8.12.8p1/8.12.3) with ESMTP id h5G6ISWT000662;
	Sun, 15 Jun 2003 23:18:28 -0700 (PDT)
	(envelope-from vern@jaguar.icir.org)
Message-Id: <200306160618.h5G6ISWT000662@jaguar.icir.org>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>,
        "'Paul Judge'" <paul.judge@ciphertrust.com>,
        "'Kee Hinckley'" <nazgul@somewhere.com>,
        "'Asrg@ietf.org'" <Asrg@ietf.org>
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
In-reply-to: Your message of Sun, 15 Jun 2003 05:10:43 PDT.
Date: Sun, 15 Jun 2003 23:18:28 -0700
From: Vern Paxson <vern@icir.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

> I disagree with the requirement because I don't think there is 
> an enforceable requirement. I think that if there is a problem
> and a court case results, that the way the IPR policy has been
> enacted will allow any barely competent lawyer to get arround
> it.

As I previously stated, this is an *interim* policy because the IRTF does
not have a formal policy at this point, and putting one together is going
to take a fair amount of time.

Even if it is unenforceable, there is a notion of maintaining ethical
behavior; most of us comply with rules of professional conduct even if
they are not legally enforceable.

		Vern



From owner-ietf@ietf.org  Mon Jun 16 09:19:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13068
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 09:19:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RtTm-0004bM-JI
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 08:52:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RtN0-0002yp-1I
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 08:45:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11803
	for <ietf@ietf.org>; Mon, 16 Jun 2003 08:45:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RtKn-0002EH-00
	for ietf@ietf.org; Mon, 16 Jun 2003 08:43:41 -0400
Received: from aragorn.bbn.com ([128.33.0.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RtKh-0002CV-00
	for ietf@ietf.org; Mon, 16 Jun 2003 08:43:38 -0400
Received: from arsenaultd2 (dhcp33-244-172.bbn.com [128.33.244.172])
	by aragorn.bbn.com (8.12.7/8.12.7) with SMTP id h5GCj4D8005563;
	Mon, 16 Jun 2003 08:45:04 -0400 (EDT)
Message-ID: <00fb01c33404$fced9cd0$acf42180@arsenaultd2>
From: "Al Arsenault" <aarsenau@bbn.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>, <ietf@ietf.org>
References: <2A1D4C86842EE14CA9BC80474919782E0D2230@mou1wnexm02.verisign.com>
Subject: Re: US Defense Department formally adopts IPv6
Date: Mon, 16 Jun 2003 08:44:12 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Phill,

    Spot-on. And in fact, that's what appears to be happening with the IPv6
message.

    In the document that became RFC 942, DOD's expert panel says:

    - TCP/IP was custom built for DoD requirements; it's not useful for the
commercial world.

    - The commercial world is going to use ISO protocols; that decision's
been made. And the commercial world does things so much better, faster,
cheaper, etc. than the DoD.

    - DoD can't afford to have its own custom solutions that aren't
commercially available and won't interoperate with commercial or other
Government systems.

    - Therefore, DoD must ditch TCP/IP and hop on board the
commercially-driven OSI train.

    That "DoD must use commercially-provided solutions for everything"
viewpoint became popular in the early 1980's.  It went out of vogue for a
while, and came back in the early-to-mid 90's, with Gore's "Re-inventing
government" stuff.  It's still very popular with the current administration.
Reading the actual transcript of Stenbit's press conference, you see things
like:

...
"...that talks about the fact that we're going to insist that acquisitions
and programs that move on after the first of the next fiscal year, which is
October, will be IP 6-compatible. So, we need to build the inventory of
systems that have procured software and hardware on a scale which is
actually slower than the replication that happens in the commercial world --
they usually sort of roll over all of this stuff every two years or so. We
tend to be a little bit slower than that. So, we're trying to give ourselves
five years to go through what is, in effect, an obsolescence criteria here."
...
"I think it's an important validation of the work that's gone on,
absolutely, outside the Defense Department, although we have participated in
the forums; but that the Internet community is moving forward; they've
recognized these problems -- those are the kind of problems we have. We're
comfortable that they're moving toward solutions, however they come out,
that we'll adapt our systems to."
...
"We're actually -- we're actually taking advantage of the commercial
movement that's going on. The commercial industry has its own transition
difficulties. There are people who have vested interest in staying in the
past because that's how they made their money, building this little patch on
IP 4 that makes something go away and makes people happier in their service.
There are other people who would like to get this stuff all into a standard.
I think the real pressure here on the commercial side, at least as I
understand it -- and this is not -- I don't go out and -- this is not how I
spend my life -- the Europeans really need more addresses. So I think the
actual push to move from IP 4 to IP 6 will not be driven by us. Our
announcement today, and our execution on this policy will move it along
because we are a large buyer of Internet-compatible devices and
communications. But I think it's the commercial people that will actually
cause this trigger to be pulled, and we're assuming that will happen in a
time scale which is consistent with what I have just been describing."

...

"So this is actually a pretty intrusive change. But as I say, it's not
driven by the DoD's use. It is, in fact, driven by commercial uses. And we
have basically made the choice that we're going to -- we're comfortable
enough with the progress that's been made in the commercial world that we're
going to stick with that, however it evolves, because it will change over
time, but we're going to change with it because our suppliers are going to
change with it to meet that standard."

...

(The questions and answers about "IPv5" are sort of funny.)

Anyway, the point is, this is yet another case of a high official saying
"gee, we have some real problems.  And the commercial world is claiming
they've solved these same kinds of problems already, with this neat new
technology called (XYZ).  So that must be the answer - we have to migrate to
(XYZ) as well."

How well it gets implemented in practice is TBD.  It'll largely depend on
whether there are any viable commercial products that actually do IPv6 well
enough to get the job done.  Because fundamentally, Government folks just
like commercial folks have to make the bits flow and get the job done.  The
people who have to do the job every day will soon figure out whether this is
top-level smoke, or something real.  If IPv6 products are dogs that stand in
the way of getting the job done, this policy pronouncement will be good only
for the bottom of the bird cage in two years or less.  Oh, there will be
some high-level posturing and "work" done on it, but that's only to make the
top-level policy people feel better.  The people who have to get the job
done will do so.

                    Al Arsenault



----- Original Message -----
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: <ietf@ietf.org>
Sent: Sunday, June 15, 2003 8:52 AM
Subject: Re: US Defense Department formally adopts IPv6


> In response to John's RFC 942 point:
>
>
> Reading the document the gist of the argument appears to be 'there is no
> real technical difference between the protocols that is significant enough
> to decide the issue, but OSI is what everyone else is planning to use'.
>
> So actually I would say it was the opposite of the ADA situation, quite
> likely given the date even an attempt not to make the ADA mistake a second
> time (ADA was a train wreck predicted long in advance).
>
>
> OSI came far closer to succeeding despite the problems in the design than
> many here appear to want to admit. Without classless addresses the IPv4
> space would have run out in 1992. It is ironic that X.500 is one of the
few
> parts of the stack left, if X.500 had ever worked we might all be speaking
> ASN.1...
>
>
> Phill
>
>
>




From owner-ietf@ietf.org  Mon Jun 16 10:45:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16703
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 10:45:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ruxd-0004FI-NI
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 10:27:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Rus8-0004BM-51
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 10:22:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15706
	for <ietf@ietf.org>; Mon, 16 Jun 2003 10:22:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Rupw-0002u8-00
	for ietf@ietf.org; Mon, 16 Jun 2003 10:19:56 -0400
Received: from kunlun.nas.edu ([144.171.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Rupv-0002tv-00
	for ietf@ietf.org; Mon, 16 Jun 2003 10:19:55 -0400
Received: from smtpmta.nas.edu (smtpmta.nas.edu [144.171.1.40])
	by kunlun.nas.edu (8.11.7+Sun/8.11.6) with SMTP id h5GEJ6x02118
	for <ietf@ietf.org>; Mon, 16 Jun 2003 10:19:06 -0400 (EDT)
Received: by smtpmta.nas.edu(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 85256D47.004E9F43 ; Mon, 16 Jun 2003 10:18:45 -0400
X-Lotus-FromDomain: NAS
From: "Phil Hilliard" <PHilliard@nas.edu>
To: ietf@ietf.org
Message-ID: <85256D47.004E9D70.00@smtpmta.nas.edu>
Date: Mon, 16 Jun 2003 10:21:01 -0400
Subject: National Academies call for papers - Telecom R&D
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

IETF members may be interested in this opportunity to provide
input to a National Academies study on the state of
telecommunications R&D and possible responses.

The Computer Science and Telecommunications Board's
Committee on Telecommunications R&D, chaired by
Robert W. Lucky, is seeking comments on telecommunications
research in the United States, including how the
character of telecom research has changed, how
changes in telecom research might be measured/assessed,
implications of these changes for the telecom industry,
and possible mechanisms for strengthening U.S. telecom research.

For more information on the study and how to submit
comments, please see cstb.org/project_telecomrnd_solicitpapers.html


Questions that responders might address include:

* Is the U.S. marketplace adequately supporting
telecom research--and how would we know?
If not, what are the consequences of underinvestment
for the U.S. telecom industry and competitiveness
with nations that are making these investments?
What indicators should be used to measure research
(e.g., funding or research papers published)?

* Who should pay for long-term research aimed at
innovation 10 years out?  To what extent are
telecommunications research results appropriable
and thus likely to be adequately supported by industry?

* What can we learn from the experiences of other
countries (e.g., EU framework or national programs)?
Do other countries fare better because of either
greater government support or because their research
programs are better organized?  How effective have
they been historically, and how successful are they
likely to be in their present form?

* What can we learn from past experiences with
institutions in related fields (e.g., Sematech and MCC)?
How effective were these initiatives?   How did different
research strategies affect the outcome?  How can
government and industry best participate in these efforts?

* Could a greater university role in telecommunications
research be fostered?  What sort of role might
universities play in a telecom research initiative?
Would enhanced university-industry ties strengthen
research or improve research training?  Is there an
opportunity in the recent migration of researchers
to universities from industrial labs?

* What is the impact of the Internet and its applications
on the appropriate definition of telecommunications,
the needed research in telecommunications, the institutions
performing research, etc?

* How are changes in the industrial research environment
changing (or should change) the role of academic research?





From owner-ietf@ietf.org  Mon Jun 16 12:05:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19052
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 12:05:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RwHw-0005uM-Jt
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 11:52:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RwCm-0005gm-GR
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 11:47:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18348
	for <ietf@ietf.org>; Mon, 16 Jun 2003 11:47:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RwAa-0003SW-00
	for ietf@ietf.org; Mon, 16 Jun 2003 11:45:20 -0400
Received: from pigeon.verisign.com ([65.205.251.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RwAZ-0003ST-00
	for ietf@ietf.org; Mon, 16 Jun 2003 11:45:20 -0400
Received: from mou1wnexc01.verisign.com (verisign.com [65.205.251.53])
        by pigeon.verisign.com (8.12.9/) with ESMTP id h5GFlRuv011292;
        Mon, 16 Jun 2003 08:47:28 -0700 (PDT)
Received: by mou1wnexc01.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LMLG0HW2>; Mon, 16 Jun 2003 08:47:27 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D2238@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Al Arsenault'" <aarsenau@bbn.com>,
        "Hallam-Baker, Phillip"
	 <pbaker@verisign.com>, ietf@ietf.org
Subject: RE: US Defense Department formally adopts IPv6
Date: Mon, 16 Jun 2003 08:47:27 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

>     - DoD can't afford to have its own custom solutions that aren't
> commercially available and won't interoperate with commercial or other
> Government systems.

Exactly the COTS mantra is all. I think the decision to move to require IPv6
capability is entirely consistent with this approach.

> (The questions and answers about "IPv5" are sort of funny.)

Quite whatever happened to that?

The think I find mindboggling about all this is that I have yet to see a
concise explanation of how the great transition to IPv6 is going to be
managed and what the incentive for early adopters is going to be.

I don't buy the 'more addresses' argument. If China wants more IPv4
addresses there are plenty they can take without causing widespread
inconvenience. They could decide to simply advertise BGP routes to net 18 or
one of the other large class As grabbed early on by a US university.

I really would not lay bets on the rights of pioneers who got in early and
locked up all the water rights being respected in the case of severe
drought.

If I am right in my belief that IP beat OSI through inertia and luck rather
than technical superiority there is a big problem deploying IPv6. It may
well be that inertia wins again and IPv4 plus NAT is good enough for most
uses.


 		Phill



From owner-ietf@ietf.org  Mon Jun 16 12:28:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19789
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 12:28:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RwgZ-0006Z9-T6
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 12:18:23 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RwUF-0006MQ-QD
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 12:05:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19141
	for <ietf@ietf.org>; Mon, 16 Jun 2003 12:05:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RwS3-0003ad-00
	for ietf@ietf.org; Mon, 16 Jun 2003 12:03:23 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19RwS2-0003aa-00
	for ietf@ietf.org; Mon, 16 Jun 2003 12:03:23 -0400
Received: from bs.jck.com ([209.187.148.211] helo=localhost.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19RwUA-000L64-00; Mon, 16 Jun 2003 11:05:35 -0500
Date: Mon, 16 Jun 2003 12:05:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>,
        grenville armitage <garmitage@swin.edu.au>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Recruitment of Experimental SIRs
Message-ID: <19104021.1055765133@r3.jck.com>
In-Reply-To: <136730000.1055605561@askvoll.hjemme.alvestrand.no>
References: <13695462427.20030602131247@brandenburg.com>
 <3EEA8039.BBF8718A@swin.edu.au>
 <136730000.1055605561@askvoll.hjemme.alvestrand.no>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Saturday, June 14, 2003 17:46 +0200 Harald Tveit Alvestrand
<harald@alvestrand.no> wrote:

>>> We'd like to run a proof-of-concept version of the Senior
>>> Internet Reviewer (SIR) activity,
>> 
>> I keep waiting for someone to suggest adding
>> 
>>  MAture Document-Aquisition Moderator - MADAM
>> 
>> but then I realize everyone else has more self control.
> 
> That's the new title for those who shepherd mailing list
> discussions....
> 
> Mail Activity Director And Moderator.

To be supervised, presumably, by the

    Procedural Inspector and Manager of Processes
 
> Proving once again that I have no self-control :-)

Do we need this thread ?

(Which proves that I have no sense of humor as well as no
self-control. :-) )

         john








From owner-ietf@ietf.org  Mon Jun 16 12:46:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20432
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 12:46:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Rx2e-0007Av-9K
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 12:41:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Rwpq-0006m3-PS
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 12:27:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19773
	for <ietf@ietf.org>; Mon, 16 Jun 2003 12:27:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Rwne-0003ls-00
	for ietf@ietf.org; Mon, 16 Jun 2003 12:25:42 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Rwne-0003l9-00
	for ietf@ietf.org; Mon, 16 Jun 2003 12:25:42 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 5CA3C13969; Mon, 16 Jun 2003 16:27:26 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
References: <2A1D4C86842EE14CA9BC80474919782E0D222C@mou1wnexm02.verisign.com>
From: Paul Vixie <vixie@vix.com>
Date: 16 Jun 2003 16:27:26 +0000
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D222C@mou1wnexm02.verisign.com>
Message-ID: <g33ciavvgx.fsf@sa.vix.com>
Lines: 27
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

pbaker@verisign.com ("Hallam-Baker, Phillip") writes:

> What happened to open and inclusive?

it didn't scale.  but, rather than change the written rules, more emphasis
has been put on "design teams" and "directorates" in order to get work done
in ways the written rules don't cover.  note that i think this is bad, and
that the written rules should be changed, and then followed, and that the
way things are trying to get done now has scaled even less well than before.

> I have no confidence in Paul Judge as chair. I believe that his handling
> of the group is damaging the IETF. The group may be in the IRTF but the
> mailing list bears the name IETF and it the group is being presented to
> the press as having been charged by the IETF to solve the problem.
> 
> The FTC testimony was dire. The ASRG chair stated that he believed the
> group would come up with a technical solution. Every one of the other
> members of the technical panel then stated that they thought it had
> already failed. It made the IETF look ridiculous.

three different people came to me (as a known associate of verisign's) to
ask "who the hell is this hallam-baker idiot and why does verisign let him
out in public???" after your various tirades and misbehaviours at the ftc
thing.  therefore it's possible that your rant about paul judge's activities
lacks credibility.
-- 
Paul Vixie



From owner-ietf@ietf.org  Mon Jun 16 13:40:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21981
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 13:40:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Rxlu-00083M-TH
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 13:27:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RxlW-00081d-Em
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 13:27:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21651;
	Mon, 16 Jun 2003 13:27:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RxjK-0004DT-00; Mon, 16 Jun 2003 13:25:18 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RxjI-0004DQ-00; Mon, 16 Jun 2003 13:25:17 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5GHRNVn025361 env-from <vjs>;
	Mon, 16 Jun 2003 11:27:23 -0600 (MDT)
Date: Mon, 16 Jun 2003 11:27:23 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306161727.h5GHRNVn025361@calcite.rhyolite.com>
To: asrg@ietf.org, ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
References: <2A1D4C86842EE14CA9BC80474919782E0D222C@mou1wnexm02.verisign.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Paul Vixie <vixie@vix.com>

>  ...  therefore it's possible that your rant [about ASRG moderation]

That raises an issue that I think the IETF and IRTF and certainly the
ASRG moderator should consider.  All contributions that are rejected
by any moderators (including spam filters) of any IRTF or IETF mailing
lists must be archived and should be published on web pages somewhere.
Archiving is obviously critical for the defense of the moderators
against charges of unfairness, self-dealing, and so forth.  Publishing
the rejected contributions would go a long way toward defusing or even
refuting such charges with minimal embarrassment to those making them
and disruption of valuable IETF and IRTF activities.  There might be
some extreme contributions perhaps involving child pornography or
libel that could not be published, but those are surely rare and could
be dealt with individually.

I hope that all of the rejected contributions to the ASRG mailing list
have been archived.  Based on "courtesy" copies of messages that have
been sent to me, I suspect that publishing the messages rejected for
the ASRG list would be quite helpful.  Publishing them would do no
harm to the work of the mailing list.

The cycles of noise on the main IETF list about some other mailing
lists would be helped by this policy.  Besides squelching a lot of
the noise by making the moderation obviously justified, it might also
satisfy those who really want their words published.

An easy way to implement such a policy is to use the usual mailing
list software to create parallel "lists" which to not allow subscriptions
or contributions except from the moderator of the main list but that
has an open archive.  The moderator could send copies of any rejected
documents and any relevant coorespondence to the parallel "list."


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Mon Jun 16 13:45:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22215
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 13:45:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RxvT-0008GD-NE
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 13:37:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Rxno-0008A3-9q
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 13:29:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21694
	for <ietf@ietf.org>; Mon, 16 Jun 2003 13:29:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Rxlb-0004E8-00
	for ietf@ietf.org; Mon, 16 Jun 2003 13:27:40 -0400
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Rxlb-0004Dt-00
	for ietf@ietf.org; Mon, 16 Jun 2003 13:27:39 -0400
Received: from inet-vrs-04.redmond.corp.microsoft.com ([157.54.8.149]) by mail4.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Mon, 16 Jun 2003 10:29:22 -0700
Received: from 157.54.5.25 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 16 Jun 2003 10:29:22 -0700
Received: from RED-IMC-04.redmond.corp.microsoft.com ([157.54.2.168]) by inet-hub-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 16 Jun 2003 10:29:22 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by RED-IMC-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 16 Jun 2003 10:29:22 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.82]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3788.0);
	 Mon, 16 Jun 2003 10:29:21 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6940.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: US Defense Department formally adopts IPv6
Date: Mon, 16 Jun 2003 10:29:20 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA03B3D53D@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: US Defense Department formally adopts IPv6
Thread-Index: AcM0ISar98OactEnRse2WxjSqXPJKQACrJGg
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>,
        "Al Arsenault" <aarsenau@bbn.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 16 Jun 2003 17:29:21.0656 (UTC) FILETIME=[D2D00780:01C3342C]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA22215

> > (The questions and answers about "IPv5" are sort of funny.)
> 
> Quite whatever happened to that?

It is funny that the DoD wouldn't know, since they actually deployed it.
The code point 5 was used to differentiate packets belonging to the
"stream" service parallel to IP, ST-II (RFC 1190). It was used to carry
video conferences services. I remember taking part to one such
conference in a DARPA locale.

-- Christian Huitema




From owner-ietf@ietf.org  Mon Jun 16 13:56:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22749
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 13:56:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ry8M-00010R-FB
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 13:51:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ry49-0000hq-Bg
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 13:46:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22333;
	Mon, 16 Jun 2003 13:46:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ry1x-0004Og-00; Mon, 16 Jun 2003 13:44:33 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ry1w-0004Mp-00; Mon, 16 Jun 2003 13:44:32 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h5GHk7Tc003246;
	Mon, 16 Jun 2003 10:46:12 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AFC79469;
	Mon, 16 Jun 2003 10:46:05 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA01751; Mon, 16 Jun 2003 10:46:04 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16110.604.867852.22162@thomasm-u1.cisco.com>
Date: Mon, 16 Jun 2003 10:46:04 -0700 (PDT)
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: asrg@ietf.org, ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
In-Reply-To: <200306161727.h5GHRNVn025361@calcite.rhyolite.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D222C@mou1wnexm02.verisign.com>
	<200306161727.h5GHRNVn025361@calcite.rhyolite.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Vernon Schryver writes:
 > I hope that all of the rejected contributions to the ASRG mailing list
 > have been archived.  Based on "courtesy" copies of messages that have
 > been sent to me, I suspect that publishing the messages rejected for
 > the ASRG list would be quite helpful.  Publishing them would do no
 > harm to the work of the mailing list.

Why not just have two lists, a -signal and a -noise
list in parallel and let people choose which list they
want to read?


	Mike



From owner-ietf@ietf.org  Mon Jun 16 14:05:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23168
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 14:05:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RyA0-00013Q-HW
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 13:52:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ry5b-0000rO-6o
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 13:48:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22467
	for <ietf@ietf.org>; Mon, 16 Jun 2003 13:48:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ry3P-0004Qv-00
	for ietf@ietf.org; Mon, 16 Jun 2003 13:46:03 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ry3O-0004Qa-00
	for ietf@ietf.org; Mon, 16 Jun 2003 13:46:02 -0400
Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h5GHliTa004601
	for <ietf@ietf.org>; Mon, 16 Jun 2003 10:47:45 -0700 (PDT)
Received: from cisco.com (sjc-vpn2-169.cisco.com [10.21.112.169])
	by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with SMTP id AHE51993;
	Mon, 16 Jun 2003 10:43:52 -0700 (PDT)
Received: by cisco.com (sSMTP sendmail emulation); Mon, 16 Jun 2003 13:47:33 -0400
Date: Mon, 16 Jun 2003 13:47:33 -0400
From: Scott W Brim <swb@employees.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Recruitment of Experimental SIRs
Message-ID: <20030616174733.GH2624@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <swb@employees.org>,
	"ietf@ietf.org" <ietf@ietf.org>
References: <13695462427.20030602131247@brandenburg.com> <3EEA8039.BBF8718A@swin.edu.au> <136730000.1055605561@askvoll.hjemme.alvestrand.no> <19104021.1055765133@r3.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <19104021.1055765133@r3.jck.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Jun 16, 2003 12:05:33PM -0400, John C Klensin allegedly wrote:
> > Mail Activity Director And Moderator.
> 
> To be supervised, presumably, by the
> 
>     Procedural Inspector and Manager of Processes

Yes, but watch out, some of these might really be agents for COPS.



From owner-ietf@ietf.org  Mon Jun 16 14:11:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23599
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 14:11:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RyA1-00013n-2v
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 13:52:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ry7t-0000v1-RW
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 13:50:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22542
	for <ietf@ietf.org>; Mon, 16 Jun 2003 13:50:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ry5h-0004Rm-00
	for ietf@ietf.org; Mon, 16 Jun 2003 13:48:25 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ry5g-0004Rc-00
	for ietf@ietf.org; Mon, 16 Jun 2003 13:48:25 -0400
Received: from [63.202.92.152] (adsl-66-125-125-65.dsl.pltn13.pacbell.net [66.125.125.65])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h5GHoarc016110
	for <ietf@ietf.org>; Mon, 16 Jun 2003 10:50:37 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05210620bb13b2531d86@[63.202.92.152]>
In-Reply-To: <200306161727.h5GHRNVn025361@calcite.rhyolite.com>
References: 
 <2A1D4C86842EE14CA9BC80474919782E0D222C@mou1wnexm02.verisign.com>
 <200306161727.h5GHRNVn025361@calcite.rhyolite.com>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Mon, 16 Jun 2003 10:50:16 -0700
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 11:27 AM -0600 6/16/03, Vernon Schryver wrote:
>All contributions that are rejected
>by any moderators (including spam filters) of any IRTF or IETF mailing
>lists must be archived and should be published on web pages somewhere.

FWIW, some of the IETF WG mailing lists that IMC runs get >10 spams a 
day, and often get the virus/trojans that are >120K each. This is not 
an insignificant amount of junk to wade through when looking for 
proof of moderator badness/goodness.

And there's also the problem of robots that harvest everything, 
regardless of your robots.txt file. If we had a system like you 
describe, it would be believable that the archives would get a fair 
number of hits from people searching for pr0n but finding our archive 
of spam instead.

I think that having all bounces (for whatever reason) archived is 
fine; I think having it as "web pages somewhere" is overkill. Access 
to one of the big text archives can be a trivial password given to 
anyone who wants it for research purposes.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Mon Jun 16 14:26:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24305
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 14:26:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RyWi-0002su-Eh
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 14:16:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RyF1-0001Qj-J8
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 13:58:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22892
	for <ietf@ietf.org>; Mon, 16 Jun 2003 13:58:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RyCp-0004Wq-00
	for ietf@ietf.org; Mon, 16 Jun 2003 13:55:47 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19RyCo-0004We-00
	for ietf@ietf.org; Mon, 16 Jun 2003 13:55:46 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.19.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id NAA21968;
	Mon, 16 Jun 2003 13:54:44 -0400
Date: Mon, 16 Jun 2003 13:56:10 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Paul Vixie <vixie@vix.com>
cc: ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
In-Reply-To: <g33ciavvgx.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0306161348120.5200-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

I think this is just a smokescreen. The real problem is that it didn't get
the outcomes desired by a certain group.  It has nothing whatsoever to do
with scaling. Democracy scales just fine.

Also, the last paragraph is nothing but an inappropriate ad hominem attack
on Mr. Hallam-Baker. I am speaking as someone who has some disagreements
with Mr. Hallam-Baker, but I prefer to couch those disagreements in facts,
rather than hyperbole.  Despite my disagreements, Mr. Hallam-Baker makes
some credible points that can't be dismissed as easilly as Mr Vixie would
like.  Such ad hominems are a violation of the Code of Conduct of the IETF
as documented in RFC 3184. I ask that the chair take the appropriate
action to halt this inappropriate activity.


		--Dean

On 16 Jun 2003, Paul Vixie wrote:

> pbaker@verisign.com ("Hallam-Baker, Phillip") writes:
>
> > What happened to open and inclusive?
>
> it didn't scale.  but, rather than change the written rules, more emphasis
> has been put on "design teams" and "directorates" in order to get work done
> in ways the written rules don't cover.  note that i think this is bad, and
> that the written rules should be changed, and then followed, and that the
> way things are trying to get done now has scaled even less well than before.
>
> > I have no confidence in Paul Judge as chair. I believe that his handling
> > of the group is damaging the IETF. The group may be in the IRTF but the
> > mailing list bears the name IETF and it the group is being presented to
> > the press as having been charged by the IETF to solve the problem.
> >
> > The FTC testimony was dire. The ASRG chair stated that he believed the
> > group would come up with a technical solution. Every one of the other
> > members of the technical panel then stated that they thought it had
> > already failed. It made the IETF look ridiculous.
>
> three different people came to me (as a known associate of verisign's) to
> ask "who the hell is this hallam-baker idiot and why does verisign let him
> out in public???" after your various tirades and misbehaviours at the ftc
> thing.  therefore it's possible that your rant about paul judge's activities
> lacks credibility.
> --
> Paul Vixie
>
>




From owner-ietf@ietf.org  Mon Jun 16 14:54:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25260
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 14:54:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RywO-0003hW-R9
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 14:42:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ryoi-0003Zf-9X
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 14:34:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24726
	for <ietf@ietf.org>; Mon, 16 Jun 2003 14:34:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RymW-00051k-00
	for ietf@ietf.org; Mon, 16 Jun 2003 14:32:40 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RymV-00050z-00
	for ietf@ietf.org; Mon, 16 Jun 2003 14:32:39 -0400
Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h5GIYM6p010992
	for <ietf@ietf.org>; Mon, 16 Jun 2003 11:34:22 -0700 (PDT)
Received: from cisco.com (sjc-vpn2-169.cisco.com [10.21.112.169])
	by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with SMTP id AHE57555;
	Mon, 16 Jun 2003 11:30:29 -0700 (PDT)
Received: by cisco.com (sSMTP sendmail emulation); Mon, 16 Jun 2003 14:34:08 -0400
Date: Mon, 16 Jun 2003 14:34:08 -0400
From: Scott W Brim <swb@employees.org>
To: ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
Message-ID: <20030616183407.GI2624@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <swb@employees.org>, ietf@ietf.org
References: <g33ciavvgx.fsf@sa.vix.com> <Pine.LNX.4.44.0306161348120.5200-100000@commander.av8.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0306161348120.5200-100000@commander.av8.net>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Jun 16, 2003 01:56:10PM -0400, Dean Anderson allegedly wrote:
> I think this is just a smokescreen. The real problem is that it didn't
> get the outcomes desired by a certain group.  It has nothing
> whatsoever to do with scaling. Democracy scales just fine.
> 
> On 16 Jun 2003, Paul Vixie wrote:
> >
> > > What happened to open and inclusive?
> >
> > it didn't scale.  but, rather than change the written rules, more
> > emphasis has been put on "design teams" and "directorates" in order
> > to get work done in ways the written rules don't cover.  note that i
> > think this is bad, and that the written rules should be changed, and
> > then followed, and that the way things are trying to get done now
> > has scaled even less well than before.

The original issue was that he felt like "they" were imposing an IPR
policy on him "from above".  The IETF IPR policy, which ASRG was copying
from, has been worked out over more than ten years with lots of input
and a number of iterations.  This has nothing to do with democracy or
design teams.



From owner-ietf@ietf.org  Mon Jun 16 15:11:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26468
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 15:11:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RzFo-0008Pv-Q6
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 15:02:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ryz8-0003i2-Bf
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 14:45:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25001
	for <ietf@ietf.org>; Mon, 16 Jun 2003 14:45:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ryww-00058P-00
	for ietf@ietf.org; Mon, 16 Jun 2003 14:43:26 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Rywu-00058H-00
	for ietf@ietf.org; Mon, 16 Jun 2003 14:43:25 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5GIjYra017070 env-from <vjs>;
	Mon, 16 Jun 2003 12:45:34 -0600 (MDT)
Date: Mon, 16 Jun 2003 12:45:34 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306161845.h5GIjYra017070@calcite.rhyolite.com>
To: ietf@ietf.org, phoffman@imc.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
References: <p05210620bb13b2531d86@[63.202.92.152]>
Sender: owner-ietf@ietf.org
Precedence: bulk

> To: ietf@ietf.org
> From: Paul Hoffman / IMC <phoffman@imc.org>

> >All contributions that are rejected
> >by any moderators (including spam filters) of any IRTF or IETF mailing
> >lists must be archived and should be published on web pages somewhere.
>
> FWIW, some of the IETF WG mailing lists that IMC runs get >10 spams a 
> day, and often get the virus/trojans that are >120K each. This is not 
> an insignificant amount of junk to wade through when looking for 
> proof of moderator badness/goodness.

I disagree in general, but perhaps that's because I look at several
100 spam every day.
Not logging messages > 30 Kbytes (or 10K or even 10K) would be fine
Even better would be logging but truncating.


> And there's also the problem of robots that harvest everything, 
> regardless of your robots.txt file. If we had a system like you 
> describe, it would be believable that the archives would get a fair 
> number of hits from people searching for pr0n but finding our archive 
> of spam instead.

You say that as if it's a bad thing.  I really don't see the problem.

> I think that having all bounces (for whatever reason) archived is 
> fine; I think having it as "web pages somewhere" is overkill. Access 
> to one of the big text archives can be a trivial password given to 
> anyone who wants it for research purposes.

"Openness" and "transparency" are good things in general but best and
most effective when you don't notice them.  Keeping things secret not
only feeds the paranoia of kooks, but does no good and it makes it
hard to check a suspicion or a charge without making a federal case.
The proximate example is a perfect case.  It is impossible to check
whether the other person's charge that the ASRG moderator is rejecting
contributions because of some sort of self-dealing without the IETF
equivalent of going to court to get a subpoena.  That's not any sort
of "openness and transparency."

The suggestion of having two lists, one filtered and a second named
whatever-noise, both with open archives, sounds fine to me, but wouldn't
help the ASRG case.  I think that the ASRG case would be instantly
resolved if the moderator would publish all of the rejected messages
and related corresponce without any additional commentary...not that
I think there's any case there, but passers-by might not have seen the
first several weeks of traffic in the ASRG mailing list not to mention
those "courtesy" copies I mentioned.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Mon Jun 16 15:15:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26991
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 15:15:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RzFp-0008QT-4l
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 15:02:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Rz1C-00046d-SZ
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 14:47:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25141
	for <ietf@ietf.org>; Mon, 16 Jun 2003 14:47:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ryz0-00059C-00
	for ietf@ietf.org; Mon, 16 Jun 2003 14:45:34 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ryyz-000591-00
	for ietf@ietf.org; Mon, 16 Jun 2003 14:45:33 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.19.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id OAA32503;
	Mon, 16 Jun 2003 14:40:35 -0400
Date: Mon, 16 Jun 2003 14:42:01 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Paul Hoffman / IMC <phoffman@imc.org>
cc: ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
In-Reply-To: <p05210620bb13b2531d86@[63.202.92.152]>
Message-ID: <Pine.LNX.4.44.0306161441290.5200-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Disks are cheap.  250Gig is under $400, and works just fine for slightly
long term storage.

		--Dean

On Mon, 16 Jun 2003, Paul Hoffman / IMC wrote:

> At 11:27 AM -0600 6/16/03, Vernon Schryver wrote:
> >All contributions that are rejected
> >by any moderators (including spam filters) of any IRTF or IETF mailing
> >lists must be archived and should be published on web pages somewhere.
>
> FWIW, some of the IETF WG mailing lists that IMC runs get >10 spams a
> day, and often get the virus/trojans that are >120K each. This is not
> an insignificant amount of junk to wade through when looking for
> proof of moderator badness/goodness.
>
> And there's also the problem of robots that harvest everything,
> regardless of your robots.txt file. If we had a system like you
> describe, it would be believable that the archives would get a fair
> number of hits from people searching for pr0n but finding our archive
> of spam instead.
>
> I think that having all bounces (for whatever reason) archived is
> fine; I think having it as "web pages somewhere" is overkill. Access
> to one of the big text archives can be a trivial password given to
> anyone who wants it for research purposes.
>
> --Paul Hoffman, Director
> --Internet Mail Consortium
>
>




From owner-ietf@ietf.org  Mon Jun 16 15:57:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28784
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 15:57:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RzvJ-0000s4-Ge
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 15:45:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RzhC-0000hv-22
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 15:31:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27641
	for <ietf@ietf.org>; Mon, 16 Jun 2003 15:31:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Rzez-0005ZP-00
	for ietf@ietf.org; Mon, 16 Jun 2003 15:28:57 -0400
Received: from tomts10.bellnexxia.net ([209.226.175.54] helo=tomts10-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Rzez-0005ZM-00
	for ietf@ietf.org; Mon, 16 Jun 2003 15:28:57 -0400
Received: from yahoo.com ([65.93.182.57]) by tomts17-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030616192342.FIVU8537.tomts17-srv.bellnexxia.net@yahoo.com>
          for <ietf@ietf.org>; Mon, 16 Jun 2003 15:23:42 -0400
Date: Mon, 16 Jun 2003 15:23:40 -0400
Subject: SIRs
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: S Woodside <sbwoodside@yahoo.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <20030616174733.GH2624@sbrim-w2k01>
Message-Id: <08FEBA48-A030-11D7-9DF9-000393414368@yahoo.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

It might be interesting to have a facility where comments can be 
attached to I-Ds (like in bug tracking systems / bugzilla).

simon




From owner-ietf@ietf.org  Mon Jun 16 16:13:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29741
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 16:13:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19RzxO-0000zi-Jn
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 15:47:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RzoO-0000kY-R2
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 15:38:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27813
	for <ietf@ietf.org>; Mon, 16 Jun 2003 15:38:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RzmC-0005ch-00
	for ietf@ietf.org; Mon, 16 Jun 2003 15:36:24 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RzmC-0005ce-00
	for ietf@ietf.org; Mon, 16 Jun 2003 15:36:24 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5GJcYN29325;
        Mon, 16 Jun 2003 15:38:36 -0400 (EDT)
Date: Mon, 16 Jun 2003 15:38:34 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Paul Hoffman / IMC <phoffman@imc.org>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: archiving of spam (was CLOSE ARSG etc...)
Message-Id: <20030616153834.47aa4809.moore@cs.utk.edu>
In-Reply-To: <p05210620bb13b2531d86@[63.202.92.152]>
References: <2A1D4C86842EE14CA9BC80474919782E0D222C@mou1wnexm02.verisign.com>
	<200306161727.h5GHRNVn025361@calcite.rhyolite.com>
	<p05210620bb13b2531d86@[63.202.92.152]>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I think that having all bounces (for whatever reason) archived is 
> fine; I think having it as "web pages somewhere" is overkill.

both the volume of spam, and the ratio of spam to legitimate content are
so high, that I'm not sure how much longer it will be practical to
archive it.  if we were to archive rejected messages, it should probably
only be for a few weeks.



From owner-ietf@ietf.org  Mon Jun 16 16:30:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00856
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 16:30:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S0Lo-0004Q9-CC
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 16:13:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S09x-0002ZH-02
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 16:00:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29035
	for <ietf@ietf.org>; Mon, 16 Jun 2003 16:00:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S07k-0005uR-00
	for ietf@ietf.org; Mon, 16 Jun 2003 15:58:40 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S07k-0005u1-00
	for ietf@ietf.org; Mon, 16 Jun 2003 15:58:40 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h5GK0MB22168;
	Mon, 16 Jun 2003 23:00:22 +0300
Date: Mon, 16 Jun 2003 23:00:21 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: S Woodside <sbwoodside@yahoo.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: SIRs
In-Reply-To: <08FEBA48-A030-11D7-9DF9-000393414368@yahoo.com>
Message-ID: <Pine.LNX.4.44.0306162258340.22096-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 16 Jun 2003, S Woodside wrote:
> It might be interesting to have a facility where comments can be 
> attached to I-Ds (like in bug tracking systems / bugzilla).

I'm not sure what kind of comments you refer to?

"I think this and this is a bad idea, for these reasons, but naturally the 
document authors/editors won't add that in the next revision of the ID" ?

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From owner-ietf@ietf.org  Mon Jun 16 16:39:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01258
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 16:39:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S0Mw-0004h5-RL
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 16:14:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S0HL-00047w-7O
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 16:08:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29583
	for <ietf@ietf.org>; Mon, 16 Jun 2003 16:08:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S0F8-00063v-00
	for ietf@ietf.org; Mon, 16 Jun 2003 16:06:18 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19S0F8-00063r-00
	for ietf@ietf.org; Mon, 16 Jun 2003 16:06:18 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.19.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id QAA04084;
	Mon, 16 Jun 2003 16:00:10 -0400
Date: Mon, 16 Jun 2003 16:01:37 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Scott W Brim <swb@employees.org>
cc: ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
In-Reply-To: <20030616183407.GI2624@sbrim-w2k01>
Message-ID: <Pine.LNX.4.44.0306161542320.5200-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

The IPR policy (controversial as it might be), has nothing to do with who
can post to an IETF list. There is no reasonable basis to limit posts
because a person is involved in other groups. It has nothing to do with
any so-called 'emphasis on design teams and directorates', which seems to
be little more than a codeword for suppression of certain viewpoints.

This is merely a transparent and inappropriate attempt to suppress certain
viewpoints, in apparent violation of RFC 2026 10.4(A). The IETF is to take
no position on the topic.

I note that Mr. Vixie has told me in the past that he supports the concept
of software patents. This is something that I and others involved with the
LPF, and John McCarthy, Don Knuth, Richard Stallman, and many, many other
luminaries of Computer Science, have fought against for many years.
Indeed, there is recently renewed interest in changing these laws, as
venture capitalists are finally beginning to come over to our side of the
debate.

It is quite clear where some people stand on the issue of intellectual
property. However, it is inappropriate for them to use their influence at
the IETF to suppress competing viewpoints in violation of the IETF
non-position.

Dean Anderson
Speaking as President of the League for Progamming Freedom

On Mon, 16 Jun 2003, Scott W Brim wrote:

> On Mon, Jun 16, 2003 01:56:10PM -0400, Dean Anderson allegedly wrote:
> > I think this is just a smokescreen. The real problem is that it didn't
> > get the outcomes desired by a certain group.  It has nothing
> > whatsoever to do with scaling. Democracy scales just fine.
> >
> > On 16 Jun 2003, Paul Vixie wrote:
> > >
> > > > What happened to open and inclusive?
> > >
> > > it didn't scale.  but, rather than change the written rules, more
> > > emphasis has been put on "design teams" and "directorates" in order
> > > to get work done in ways the written rules don't cover.  note that i
> > > think this is bad, and that the written rules should be changed, and
> > > then followed, and that the way things are trying to get done now
> > > has scaled even less well than before.
>
> The original issue was that he felt like "they" were imposing an IPR
> policy on him "from above".  The IETF IPR policy, which ASRG was copying
> from, has been worked out over more than ten years with lots of input
> and a number of iterations.  This has nothing to do with democracy or
> design teams.
>
>





From owner-ietf@ietf.org  Mon Jun 16 16:59:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02056
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 16:59:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S0xw-0000Zl-NW
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 16:52:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S0bN-0006ar-PK
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 16:29:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00732
	for <ietf@ietf.org>; Mon, 16 Jun 2003 16:29:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S0ZB-0006Nk-00
	for ietf@ietf.org; Mon, 16 Jun 2003 16:27:01 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S0ZA-0006NT-00
	for ietf@ietf.org; Mon, 16 Jun 2003 16:27:01 -0400
Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h5GKSiUm010690
	for <ietf@ietf.org>; Mon, 16 Jun 2003 13:28:44 -0700 (PDT)
Received: from cisco.com (sjc-vpn2-169.cisco.com [10.21.112.169])
	by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with SMTP id AHE69447;
	Mon, 16 Jun 2003 13:24:50 -0700 (PDT)
Received: by cisco.com (sSMTP sendmail emulation); Mon, 16 Jun 2003 16:28:33 -0400
Date: Mon, 16 Jun 2003 16:28:33 -0400
From: Scott W Brim <swb@employees.org>
To: ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
Message-ID: <20030616202832.GO2624@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <swb@employees.org>, ietf@ietf.org
References: <20030616183407.GI2624@sbrim-w2k01> <Pine.LNX.4.44.0306161542320.5200-100000@commander.av8.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0306161542320.5200-100000@commander.av8.net>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Jun 16, 2003 04:01:37PM -0400, Dean Anderson allegedly wrote:
> The IPR policy (controversial as it might be), has nothing to do with who
> can post to an IETF list. There is no reasonable basis to limit posts
> because a person is involved in other groups. It has nothing to do with
> any so-called 'emphasis on design teams and directorates', which seems to
> be little more than a codeword for suppression of certain viewpoints.

Go back and look at Phillip's original message.  The complaint about
democracy was not about posting rights.  Enclosed:

> > I disagree with any requirement imposed by a working group chair who
> > believes he is not accountable to the group. I do not think that the
> > way an IPR regime should be specified is a unilateral statement from
> > the chair that a decision has been taken.
> > 
> > An IPR policy should not be something that members of a group
> > discover when they are told it has been imposed from above. 
> > 
> > 
> > What happened to open and inclusive?





From owner-ietf@ietf.org  Mon Jun 16 17:00:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02155
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 17:00:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S0xy-0000dO-0g
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 16:52:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S0k9-0007DQ-I4
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 16:38:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01237
	for <ietf@ietf.org>; Mon, 16 Jun 2003 16:38:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S0hx-0006TE-00
	for ietf@ietf.org; Mon, 16 Jun 2003 16:36:05 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S0hv-0006TB-00
	for ietf@ietf.org; Mon, 16 Jun 2003 16:36:04 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5GKcFsn014174
	for ietf@ietf.org env-from <vjs>;
	Mon, 16 Jun 2003 14:38:15 -0600 (MDT)
Date: Mon, 16 Jun 2003 14:38:15 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306162038.h5GKcFsn014174@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: archiving of spam (was CLOSE ARSG etc...)
References:  <20030616153834.47aa4809.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> > I think that having all bounces (for whatever reason) archived is 
> > fine; I think having it as "web pages somewhere" is overkill.
>
> both the volume of spam, and the ratio of spam to legitimate content are
> so high, that I'm not sure how much longer it will be practical to
> archive it.  if we were to archive rejected messages, it should probably
> only be for a few weeks.

My rolling 40 day log of all spam sent to my traps or real addresses
contains about 34,484 samples in a total of about 242 Mbytes or an
average of about 7 KBytes/spam.  (Each sample is truncated to ~32 KBytes.)

Judging from DCC numbers from a bunch of medium sized ISPs, the typical
consumer mailbox receives about 10 messages/day (more than 5, less
than 20), of which about half are spam.  (Never mind that judicious
"unsubscribing" can reduce that by about 50%.)

So in round numbers, assume 10 spam/list/day.  If the IETF has 100
mailing lists, archiving all IETF list spam would involve 1000 spam/day
or about 7 MBytes/day or 2.5 GBytes/year.  

I remember quite well when a large disk drive was a ~2 meter cube,
weighed over a ton, used 220 volts and compressed air, and held only
48 MByte, but those days are long past.  2.5 Gbytes would fit on a
single DVD, not to mention modern magnetic media.

I keep unique (as determined by DCC checksums) copies of all of the
spam sent to my trap addresses permanently on CDROM.  I have ~1000
trap addresses, although only a several dozen are hit more than half
dozen times/week.  (These records help me answer complaints about my
blacklist.)


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Mon Jun 16 17:06:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02572
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 17:06:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S0zC-0000ko-FP
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 16:53:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S0oy-00085d-Nt
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 16:43:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01612
	for <ietf@ietf.org>; Mon, 16 Jun 2003 16:43:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S0mm-0006Zh-00
	for ietf@ietf.org; Mon, 16 Jun 2003 16:41:04 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19S0ml-0006ZY-00
	for ietf@ietf.org; Mon, 16 Jun 2003 16:41:03 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.19.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id QAA31407;
	Mon, 16 Jun 2003 16:37:00 -0400
Date: Mon, 16 Jun 2003 16:38:27 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Keith Moore <moore@cs.utk.edu>
cc: Paul Hoffman / IMC <phoffman@imc.org>, <ietf@ietf.org>
Subject: Re: archiving of spam (was CLOSE ARSG etc...)
In-Reply-To: <20030616153834.47aa4809.moore@cs.utk.edu>
Message-ID: <Pine.LNX.4.44.0306161638020.5200-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

What sort of message volume do you see?

How much disk storage do you have?

		--Dean

On Mon, 16 Jun 2003, Keith Moore wrote:

> > I think that having all bounces (for whatever reason) archived is
> > fine; I think having it as "web pages somewhere" is overkill.
>
> both the volume of spam, and the ratio of spam to legitimate content are
> so high, that I'm not sure how much longer it will be practical to
> archive it.  if we were to archive rejected messages, it should probably
> only be for a few weeks.
>
>




From owner-ietf@ietf.org  Mon Jun 16 17:26:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01257
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 16:39:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S0Mw-0004gG-CK
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 16:14:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S0Fi-0003xB-Hq
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 16:06:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27261
	for <ietf@ietf.org>; Mon, 16 Jun 2003 15:18:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RzT5-0005UA-00
	for ietf@ietf.org; Mon, 16 Jun 2003 15:16:39 -0400
Received: from spitfire.law.miami.edu ([129.171.187.10] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 19RzT4-0005U7-00
	for ietf@ietf.org; Mon, 16 Jun 2003 15:16:38 -0400
Received: from spitfire.law.miami.edu (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id 8D1445C3B84; Mon, 16 Jun 2003 15:18:53 -0400 (EDT)
Received: by spitfire.law.miami.edu (Postfix, from userid 1113)
	id 2E1A45C3B84; Mon, 16 Jun 2003 15:18:48 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id 221425D3A6E; Mon, 16 Jun 2003 15:18:48 -0400 (EDT)
Date: Mon, 16 Jun 2003 15:18:48 -0400 (EDT)
From: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
To: Dean Anderson <dean@av8.com>
Cc: Paul Hoffman / IMC <phoffman@imc.org>, ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
In-Reply-To: <Pine.LNX.4.44.0306161441290.5200-100000@commander.av8.net>
Message-ID: <Pine.LNX.4.10.10306161516570.24659-100000@spitfire.law.miami.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

My understanding is that The Mail Archive
(http://www.mail-archive.com/lists.html)  will provide free storage for
mailing lists.  I think every WG list should be permanetly archived in
this manner.

On Mon, 16 Jun 2003, Dean Anderson wrote:

> Disks are cheap.  250Gig is under $400, and works just fine for slightly
> long term storage.
> 
> 		--Dean
> 
> On Mon, 16 Jun 2003, Paul Hoffman / IMC wrote:
> 
> > At 11:27 AM -0600 6/16/03, Vernon Schryver wrote:
> > >All contributions that are rejected
> > >by any moderators (including spam filters) of any IRTF or IETF mailing
> > >lists must be archived and should be published on web pages somewhere.
> >
> > FWIW, some of the IETF WG mailing lists that IMC runs get >10 spams a
> > day, and often get the virus/trojans that are >120K each. This is not
> > an insignificant amount of junk to wade through when looking for
> > proof of moderator badness/goodness.
> >
> > And there's also the problem of robots that harvest everything,
> > regardless of your robots.txt file. If we had a system like you
> > describe, it would be believable that the archives would get a fair
> > number of hits from people searching for pr0n but finding our archive
> > of spam instead.
> >
> > I think that having all bounces (for whatever reason) archived is
> > fine; I think having it as "web pages somewhere" is overkill. Access
> > to one of the big text archives can be a trivial password given to
> > anyone who wants it for research purposes.
> >
> > --Paul Hoffman, Director
> > --Internet Mail Consortium
> >
> >
> 
> 
> 

-- 
		Please visit http://www.icannwatch.org
A. Michael Froomkin   |    Professor of Law    |   froomkin@law.tm
U. Miami School of Law, P.O. Box 248087, Coral Gables, FL 33124 USA
+1 (305) 284-4285  |  +1 (305) 284-6506 (fax)  |  http://www.law.tm
                        -->It's hot here.<--




From owner-ietf@ietf.org  Mon Jun 16 17:39:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03694
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 17:39:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S1Tw-0002VP-Hb
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 17:25:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S1Ci-00025P-Lh
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 17:07:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02700
	for <ietf@ietf.org>; Mon, 16 Jun 2003 17:07:50 -0400 (EDT)
From: william@elan.net
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S1AW-0006t2-00
	for ietf@ietf.org; Mon, 16 Jun 2003 17:05:36 -0400
Received: from sokol.elan.net ([216.151.192.200])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S1AV-0006sr-00
	for ietf@ietf.org; Mon, 16 Jun 2003 17:05:35 -0400
Received: from sokol.elan.net (localhost.localdomain [127.0.0.1])
	by sokol.elan.net (8.12.5/8.12.5) with ESMTP id h5GIOwFX023612
	for <ietf@ietf.org>; Mon, 16 Jun 2003 11:24:58 -0700
Received: from localhost (william@localhost)
	by sokol.elan.net (8.12.5/8.12.5/Submit) with ESMTP id h5GIOve3023608
	for <ietf@ietf.org>; Mon, 16 Jun 2003 11:24:57 -0700
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Mon, 16 Jun 2003 11:24:57 -0700 (PDT)
To: ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
In-Reply-To: <g33ciavvgx.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0306161106190.1291-100000@sokol.elan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On 16 Jun 2003, Paul Vixie wrote:

> pbaker@verisign.com ("Hallam-Baker, Phillip") writes:
>
> > The FTC testimony was dire. The ASRG chair stated that he believed the
> > group would come up with a technical solution. Every one of the other
> > members of the technical panel then stated that they thought it had
> > already failed. It made the IETF look ridiculous.
> 
> > What happened to open and inclusive?
> 
> it didn't scale.  but, rather than change the written rules, more emphasis
> has been put on "design teams" and "directorates" in order to get work done
> in ways the written rules don't cover.  note that i think this is bad, and
> that the written rules should be changed, and then followed, and that the
> way things are trying to get done now has scaled even less well than before.

I'm not big fan of rules... But the way it is now is not working too well 
- especially for ASRG. I do agree with Paul Judge that we CAN come with 
tecnical solution (but it may still need to be backed up by some laws as 
well). But the problem is with ASRG itself, there are some there who are 
truly interested in spam research issues, but nothing is really being done
and one or two topics are complete predominant (plus couple additional 
people on the list who just try to critisize everything) and the group 
itself is not producing the results as a result of that. I would personally
very much like to work withing ASRG but I stayed away lately because of 
the above problems and I'm just keeping some watch over what is happening.

I do agree that problem with ASRG is in part due to its chair and his inability 
to get things in order, in which case ultimate control would fall on IRTF
and IETF leadership which has not done anything either and in fact IETF as
many pointed out has tried to avoid taking on the spam issue. Good thing 
is IPR issue is now being worked on there (I've that needs to be looked at 
3 months ago and that no IPR for ASRG is worst scenarioa - nobody listed then)
but that is small step and rather procedural one at that.

And BTW - is this correct that I'm hearing that Phillip is not being allowed
to post at ASRG? If this is so - that is completely inappropriate - whatever
his comments and work outside ASRG is, I've not seen anything within ASRG 
that should have prompted removal of posting priviliges - he's been good 
contributor for ASRG early one and shutting him up is just improper 
exerscise of his powers by ASRG chair (if that is what is going on).

---
William Leibzon
Elan Communications Inc. 
william@elan.net




From owner-ietf@ietf.org  Mon Jun 16 17:40:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03797
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 17:40:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S1cq-0002jt-Iy
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 17:34:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S1MX-0002OZ-EY
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 17:18:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03187
	for <ietf@ietf.org>; Mon, 16 Jun 2003 17:17:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S1KL-00070z-00
	for ietf@ietf.org; Mon, 16 Jun 2003 17:15:45 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S1KK-00070w-00
	for ietf@ietf.org; Mon, 16 Jun 2003 17:15:44 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h5GLIrxS080076;
	Mon, 16 Jun 2003 23:18:53 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Mon, 16 Jun 2003 23:17:56 +0200
Subject: Re: US Defense Department formally adopts IPv6
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D2238@mou1wnexm02.verisign.com>
Message-Id: <FF7898CB-A03F-11D7-9B70-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On maandag, jun 16, 2003, at 17:47 Europe/Amsterdam, Hallam-Baker, 
Phillip wrote:

> The think I find mindboggling about all this is that I have yet to see 
> a
> concise explanation of how the great transition to IPv6 is going to be
> managed and what the incentive for early adopters is going to be.

Nostalgia.  :-)

If you find yourself yearning for a simpler time and place, where 
spamming is unknown, nameservice is still a novelty and people are more 
interested in the network itself than in the content it may carry, IPv6 
is the thing for you.

The trouble with IPv6 adoption is that you don't see a huge, immediate 
gain. But in the long run, the costs of staying with IPv4 are going to 
be higher than the costs of changing to IPv6. We still have enough time 
to do it fairly painlessly.

> I don't buy the 'more addresses' argument. If China wants more IPv4
> addresses there are plenty they can take without causing widespread
> inconvenience. They could decide to simply advertise BGP routes to net 
> 18 or
> one of the other large class As grabbed early on by a US university.

Organizations in China can also simply request the address space from 
APNIC and get them if the request is within reason, just like American 
organizations can request address space from ARIN. APNIC, ARIN, LACNIC 
and RIPE policies regarding IPv4 address assignments are as good as 
identical. Just because some US organizations were able to get large 
blocks of address space in the past doesn't mean all US organizations 
now have all the address space they need.

A few stats: if we squint, 40% of the usable IPv4 address space is 
unallocated, 20% allocated by the RIRs (= reasonably efficient) and 40% 
allocated pre-RIR (= mostly rather inefficient).

> If I am right in my belief that IP beat OSI through inertia and luck 
> rather
> than technical superiority there is a big problem deploying IPv6. It 
> may
> well be that inertia wins again and IPv4 plus NAT is good enough for 
> most
> uses.

Vendors will have to implement IPv6 because SOME customers require it. 
(Note that supporting IPv4+IPv6 in applications by using the IPv6 
system calls is fairly trivial. The trouble is supporting both the old 
and new system calls side by side in case you need to run on a system 
that doesn't have the IPv6 compatible system calls.) Once all hard- and 
software supports IPv6, the question is no longer "why move to IPv6" 
but rather "why stick with IPv4".

But we'll really see sparks fly once the Linksyses of this world start 
to implement automatic 6to4 based on a dynamic IPv4 address (= 
automatically create, tunnel and give out IPv6 addresses without any 
need for ISP support) so Gnutella and Kazaa users get to run NATless.




From owner-ietf@ietf.org  Mon Jun 16 17:51:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04340
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 17:51:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S1fu-0002r6-U2
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 17:38:02 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S1Vq-0002Vi-0U
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 17:27:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03437
	for <ietf@ietf.org>; Mon, 16 Jun 2003 17:27:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S1Td-00075s-00
	for ietf@ietf.org; Mon, 16 Jun 2003 17:25:21 -0400
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 19S1Tc-00075j-00
	for ietf@ietf.org; Mon, 16 Jun 2003 17:25:20 -0400
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 19S1Vb-0005Rg-00
	for <ietf@ietf.org>; Mon, 16 Jun 2003 22:27:23 +0100
Date: Mon, 16 Jun 2003 22:27:23 +0100
To: ietf@ietf.org
Subject: Re: Impending Publication: draft-iab-service-id-considerations-01.txt
Message-ID: <20030616212723.GA3390@fysh.org>
References: <200306161747.NAA22457@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200306161747.NAA22457@ietf.org>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

|    If intermediate systems take actions on behalf of one or more parties
|    to the communication or affecting the communication, a good rule of
|    thumb is they should only take actions that are beneficial to or
|    approved by one or more of the parties, within the operational
|    parameters of the service-specific protocol, or otherwise unlikely to
|    lead to widespread evasion by the user community.

I think this statement gives dangerously wide latitude for intermediate
systems to damage end-to-end-ness.  It seems to me that a router should
only do something outside fundamental routing behaviour when this has
been explicitly approved, either through protocol negotiation or through
manual configuration, by sufficiently many affected parties that the
others can't tell that anything out of the ordinary is happening.

To perceive some action as "beneficial to ... one or more of the parties"
does not make it so.  Not only is human history in general littered
with examples of evil done "for their own good", but also within recent
networking history some of the problems that the draft is responding to
have been caused by intermediate systems trying to be helpful.  A major
problem is that most of these attempts to be helpful are attempts to
be helpful to humans, which end up being unhelpful to computers and to
those humans that interact with computers as we do; few people outside
the IETF are truly competent to judge what is beneficial to someone
else within the context of computer networking.  Do not underestimate
the degree to which computer systems are designed by managers.

In the nexxt clause, it's not clear whether "within the operational
parameters of the service-specific protocol" is intended to be ANDed
or ORed with the "beneficial ... or approved ..." clause.  If it is
intended to be ORed, I find this also to be dangerously broad.  Finally,
"unlikely to lead to widespread evasion" is another criterion that anyone
who needs to be told this rule won't be competent to judge.

Overall, I think that, particularly in such an official statement as
this, the IAB needs to be very conservative about Internet architectural
matters.  We should maintain the current situation wherein firewalls are
recognisably a breach of the Internet architecture, at least until we've
worked out a way to do them that doesn't cause surprising behaviour.
This Internet works (ish), and we need to keep it that way: if we break
it now, we'll probably never be able to get the popular momentum required
to replace it with a new one that works.

-zefram



From owner-ietf@ietf.org  Mon Jun 16 18:15:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06251
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 18:15:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S286-00012h-MD
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 18:07:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S1lJ-0003gB-0A
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 17:43:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04001
	for <ietf@ietf.org>; Mon, 16 Jun 2003 17:43:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S1j6-0007GT-00
	for ietf@ietf.org; Mon, 16 Jun 2003 17:41:20 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19S1j5-0007G0-00
	for ietf@ietf.org; Mon, 16 Jun 2003 17:41:19 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.19.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA28325;
	Mon, 16 Jun 2003 17:36:40 -0400
Date: Mon, 16 Jun 2003 17:38:06 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Scott W Brim <swb@employees.org>
cc: ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
In-Reply-To: <20030616202832.GO2624@sbrim-w2k01>
Message-ID: <Pine.LNX.4.44.0306161728430.5940-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Apparently, you didn't read the entire message:

Here is the rest of it:
------------------- From pbaker@verisign.com ("Hallam-Baker, Phillip")
What happened to open and inclusive?


So far we have had a deliberate campaign of heckling that the
chair did nothing to stop followed by the chair taking sanctions
against anyone who complained about the hecklers.

Five members of the group have resigned in disgust at the heckler
faction.

You will note that none of the posts I have sent on this topic
have made it to the list. So even if I do make a statement
concerning IPR the chances are that the post will be seen are
nil.

The chair has admitted that the reason my posts are blocked is
that I am working on starting anti-spam groups in other forums,
I am not aware that that type of move has EVER been sanctioned
by IETF process.
---------------------

Phillip has a complaint about the IPR policies. This complaint is not
getting to the list, which is another complaint.  Vixie tries to justify
this suppression in his message:

On 16 Jun 2003, Paul Vixie wrote:

> pbaker@verisign.com ("Hallam-Baker, Phillip") writes:
>
> > What happened to open and inclusive?
>
> it didn't scale.  but, rather than change the written rules, more
> emphasis has been put on "design teams" and "directorates" in order to
> get work done in ways the written rules don't cover.  note that i think
> this is bad, and that the written rules should be changed, and then
> followed, and that the way things are trying to get done now has scaled
> even less well than before.


To which I refute Vixie, as you quote me:


On Mon, 16 Jun 2003, Scott W Brim wrote:

> On Mon, Jun 16, 2003 04:01:37PM -0400, Dean Anderson allegedly wrote:
> > The IPR policy (controversial as it might be), has nothing to do with who
> > can post to an IETF list. There is no reasonable basis to limit posts
> > because a person is involved in other groups. It has nothing to do with
> > any so-called 'emphasis on design teams and directorates', which seems to
> > be little more than a codeword for suppression of certain viewpoints.
>
> Go back and look at Phillip's original message.  The complaint about
> democracy was not about posting rights.  Enclosed:
>
> > > I disagree with any requirement imposed by a working group chair who
> > > believes he is not accountable to the group. I do not think that the
> > > way an IPR regime should be specified is a unilateral statement from
> > > the chair that a decision has been taken.
> > >
> > > An IPR policy should not be something that members of a group
> > > discover when they are told it has been imposed from above.
> > >
> > >
> > > What happened to open and inclusive?
>
>
>
>







From owner-ietf@ietf.org  Mon Jun 16 18:36:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07024
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 18:36:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S2Dh-00031d-Rm
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 18:12:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S28k-0001Ec-KI
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 18:07:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05436
	for <ietf@ietf.org>; Mon, 16 Jun 2003 18:07:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S26X-0007Uf-00
	for ietf@ietf.org; Mon, 16 Jun 2003 18:05:33 -0400
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S26W-0007Ub-00
	for ietf@ietf.org; Mon, 16 Jun 2003 18:05:32 -0400
Received: from localhost (bill@localhost)
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id h5GLnvP14725;
	Mon, 16 Jun 2003 17:49:57 -0400
Date: Mon, 16 Jun 2003 17:49:57 -0400 (EDT)
From: Bill Strahm <bill@strahm.net>
X-X-Sender:  <bill@Kairos.dsa.uqam.ca>
To: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
cc: Dean Anderson <dean@av8.com>, Paul Hoffman / IMC <phoffman@imc.org>,
        <ietf@ietf.org>
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
In-Reply-To: <Pine.LNX.4.10.10306161516570.24659-100000@spitfire.law.miami.edu>
Message-ID: <Pine.LNX.4.33.0306161748200.14714-100000@Kairos.dsa.uqam.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

I am always leary about business models that I don't understand how they
make money.  So tell me, how will mail-archive.com make money to guarantee
that it will be around in 2050, 2100, and beyond.

I am not all that interested in a mail archive that might exist for a few
months, or a year, frankly I prefer the mail archives that the IETF
provides for my list, if the IETF goes out of business, then I don't think
the archives of the IETF will be all that interesting anymore

Bill

On Mon, 16 Jun 2003, Michael Froomkin - U.Miami School of Law wrote:

> My understanding is that The Mail Archive
> (http://www.mail-archive.com/lists.html)  will provide free storage for
> mailing lists.  I think every WG list should be permanetly archived in
> this manner.
>
> On Mon, 16 Jun 2003, Dean Anderson wrote:
>
> > Disks are cheap.  250Gig is under $400, and works just fine for slightly
> > long term storage.
> >
> > 		--Dean
> >
> > On Mon, 16 Jun 2003, Paul Hoffman / IMC wrote:
> >
> > > At 11:27 AM -0600 6/16/03, Vernon Schryver wrote:
> > > >All contributions that are rejected
> > > >by any moderators (including spam filters) of any IRTF or IETF mailing
> > > >lists must be archived and should be published on web pages somewhere.
> > >
> > > FWIW, some of the IETF WG mailing lists that IMC runs get >10 spams a
> > > day, and often get the virus/trojans that are >120K each. This is not
> > > an insignificant amount of junk to wade through when looking for
> > > proof of moderator badness/goodness.
> > >
> > > And there's also the problem of robots that harvest everything,
> > > regardless of your robots.txt file. If we had a system like you
> > > describe, it would be believable that the archives would get a fair
> > > number of hits from people searching for pr0n but finding our archive
> > > of spam instead.
> > >
> > > I think that having all bounces (for whatever reason) archived is
> > > fine; I think having it as "web pages somewhere" is overkill. Access
> > > to one of the big text archives can be a trivial password given to
> > > anyone who wants it for research purposes.
> > >
> > > --Paul Hoffman, Director
> > > --Internet Mail Consortium
> > >
> > >
> >
> >
> >
>
> --
> 		Please visit http://www.icannwatch.org
> A. Michael Froomkin   |    Professor of Law    |   froomkin@law.tm
> U. Miami School of Law, P.O. Box 248087, Coral Gables, FL 33124 USA
> +1 (305) 284-4285  |  +1 (305) 284-6506 (fax)  |  http://www.law.tm
>                         -->It's hot here.<--
>
>




From owner-ietf@ietf.org  Mon Jun 16 18:46:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07307
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 18:46:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S2bt-0005Kg-Uf
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 18:37:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S2LQ-0004kR-NI
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 18:20:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06499
	for <ietf@ietf.org>; Mon, 16 Jun 2003 18:20:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S2JE-0007bT-00
	for ietf@ietf.org; Mon, 16 Jun 2003 18:18:40 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S2JD-0007b9-00
	for ietf@ietf.org; Mon, 16 Jun 2003 18:18:39 -0400
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h5GMJpTa015653;
	Mon, 16 Jun 2003 15:19:51 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AIL24358;
	Mon, 16 Jun 2003 15:19:50 -0700 (PDT)
Message-Id: <200306162219.AIL24358@mira-sjc5-c.cisco.com>
To: Zefram <zefram@fysh.org>
cc: ietf@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: Impending Publication: draft-iab-service-id-considerations-01.txt 
In-Reply-To: Message from zefram@fysh.org
   of "Mon, 16 Jun 2003 22:27:23 BST." <20030616212723.GA3390@fysh.org> 
Date: Mon, 16 Jun 2003 18:19:50 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

> I think this statement gives dangerously wide latitude for intermediate
> systems to damage end-to-end-ness.  It seems to me that a router should
> only do something outside fundamental routing behaviour when this has
> been explicitly approved, either through protocol negotiation or through
> manual configuration, by sufficiently many affected parties that the
> others can't tell that anything out of the ordinary is happening.

Where do you think this leaves rewriting DSCPs at network
boundaries?

But anyway, the document is a statement of principle rather
than a standard, and I'm not sure that it's possible to be
absolute about these things when the interests of the user
may be counter to the interests of the network
administrator.  That's not quite true - it is possible to be
absolute.  But I don't think it's likely to produce good
results or progress on what really are some rather difficult
and sometimes subtle questions about what happens between a
sender and a receiver.

Melinda



From owner-ietf@ietf.org  Mon Jun 16 19:38:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08586
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 19:38:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S3Kx-0006Pv-2J
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 19:24:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S3EP-0006HQ-HY
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 19:17:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08291
	for <ietf@ietf.org>; Mon, 16 Jun 2003 19:17:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S3CC-0000F1-00
	for ietf@ietf.org; Mon, 16 Jun 2003 19:15:28 -0400
Received: from ds20-1.cc.swin.edu.au ([136.186.1.150] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 19S3C7-0000Ea-00
	for ietf@ietf.org; Mon, 16 Jun 2003 19:15:23 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2/8.9.3) with ESMTP id JAA1717072;
	Tue, 17 Jun 2003 09:17:05 +1000 (EST)
Message-ID: <3EEE4FF1.4BE58AE@swin.edu.au>
Date: Tue, 17 Jun 2003 09:17:05 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: SIRs
References: <08FEBA48-A030-11D7-9DF9-000393414368@yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


S Woodside wrote:
> 
> It might be interesting to have a facility where comments can be
> attached to I-Ds (like in bug tracking systems / bugzilla).

they're called WG mailing lists, aren't they?

cheers,
gja



From owner-ietf@ietf.org  Mon Jun 16 19:51:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08994
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 19:51:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S3da-0007Bv-CE
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 19:43:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S3ZI-00076k-Df
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 19:39:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08751
	for <ietf@ietf.org>; Mon, 16 Jun 2003 19:39:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S3X5-0000Nb-00
	for ietf@ietf.org; Mon, 16 Jun 2003 19:37:03 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19S3X4-0000LQ-00
	for ietf@ietf.org; Mon, 16 Jun 2003 19:37:03 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h5GNUES19575;
	Mon, 16 Jun 2003 16:30:14 -0700
Date: Mon, 16 Jun 2003 16:30:11 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
cc: Dean Anderson <dean@av8.com>, Paul Hoffman / IMC <phoffman@imc.org>,
        <ietf@ietf.org>
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
In-Reply-To: <Pine.LNX.4.10.10306161516570.24659-100000@spitfire.law.miami.edu>
Message-ID: <Pine.LNX.4.33.0306161557040.18994-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Mon, 16 Jun 2003, Michael Froomkin - U.Miami School of Law wrote:

> My understanding is that The Mail Archive
> (http://www.mail-archive.com/lists.html)  will provide free storage for
> mailing lists.  I think every WG list should be permanetly archived in
> this manner.

What a great way to help address harvesters ... one site ... one 'API' to
program against to harvest many valid addresses. This particular archive
example hides email addresses, but it took me less that 5 minutes to
determine how to recover addresses from the page data.

So I don't think the suggested policy is a good idea without much more
effective blocking of access to email addresses.

Dave Morris




From owner-ietf@ietf.org  Mon Jun 16 20:59:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10973
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 20:59:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S4gq-0000cS-AN
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 20:51:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S4Wj-0000Df-IC
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 20:40:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10441
	for <ietf@ietf.org>; Mon, 16 Jun 2003 20:40:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S4UW-0000qO-00
	for ietf@ietf.org; Mon, 16 Jun 2003 20:38:28 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S4UV-0000qL-00
	for ietf@ietf.org; Mon, 16 Jun 2003 20:38:28 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5H0eg7Q001285
	for ietf@ietf.org env-from <vjs>;
	Mon, 16 Jun 2003 18:40:42 -0600 (MDT)
Date: Mon, 16 Jun 2003 18:40:42 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306170040.h5H0eg7Q001285@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
References: <Pine.LNX.4.33.0306161557040.18994-100000@egate.xpasc.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: David Morris <dwm@xpasc.com>


> > My understanding is that The Mail Archive
> > (http://www.mail-archive.com/lists.html)  will provide free storage for
> > mailing lists.  I think every WG list should be permanetly archived in
> > this manner.
>
> What a great way to help address harvesters ... one site ... one 'API' to
> program against to harvest many valid addresses. This particular archive
> example hides email addresses, but it took me less that 5 minutes to
> determine how to recover addresses from the page data.
>
> So I don't think the suggested policy is a good idea without much more
> effective blocking of access to email addresses.

Hmmmph!  So only the addresses of authors of messages that are not
spam or otherwise rejected by IETF and IRTF moderation should be
harvested from the existing archives?

It's clear that the price of admission to a public, technical anti-spam
mailing list like the ASRG list should include sufficient practical
knowledge of spam including enough spam defenses to obviate any worries
about exposing one's address.  A similar de facto policy in other IRTF
and IETF lists to discourage tourists would not be a bad thing.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Mon Jun 16 21:11:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11403
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 21:11:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S4sD-0001An-Gz
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 21:02:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S4rf-00015X-Fw
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 21:02:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11176
	for <ietf@ietf.org>; Mon, 16 Jun 2003 21:02:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S4pS-00014r-00
	for ietf@ietf.org; Mon, 16 Jun 2003 21:00:06 -0400
Received: from gull.mail.pas.earthlink.net ([207.217.120.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S4pS-00014o-00
	for ietf@ietf.org; Mon, 16 Jun 2003 21:00:06 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19S4ra-0003na-00; Mon, 16 Jun 2003 18:02:19 -0700
Date: Mon, 16 Jun 2003 20:59:33 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: archiving of spam (was CLOSE ARSG etc...)
Message-Id: <20030616205933.4f865040.moore@cs.utk.edu>
In-Reply-To: <200306162038.h5GKcFsn014174@calcite.rhyolite.com>
References: <20030616153834.47aa4809.moore@cs.utk.edu>
	<200306162038.h5GKcFsn014174@calcite.rhyolite.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > > I think that having all bounces (for whatever reason) archived is 
> > > fine; I think having it as "web pages somewhere" is overkill.
> >
> > both the volume of spam, and the ratio of spam to legitimate content are
> > so high, that I'm not sure how much longer it will be practical to
> > archive it.  if we were to archive rejected messages, it should probably
> > only be for a few weeks.
> 
> My rolling 40 day log of all spam sent to my traps or real addresses
> contains about 34,484 samples in a total of about 242 Mbytes or an
> average of about 7 KBytes/spam.  (Each sample is truncated to ~32 KBytes.)
> 
> Judging from DCC numbers from a bunch of medium sized ISPs, the typical
> consumer mailbox receives about 10 messages/day (more than 5, less
> than 20), of which about half are spam.  (Never mind that judicious
> "unsubscribing" can reduce that by about 50%.)

well, some of the IETF lists that I maintain seem to get around 50 spams/day
(at least, if I go away for a day before I cull through the posts from 
nonsubscribers, I am likely to wind up with 60+ messages on some of those
lists, of which 59.5 are spam)

but it's not the cost of the disk that matters, it's the cost of backing it
up.  I can think of better things to spend IETF money on.



From owner-ietf@ietf.org  Mon Jun 16 21:20:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11763
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 21:20:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S51s-0001bx-Hf
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 21:12:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S50Z-0001Nj-UL
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 21:11:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11423;
	Mon, 16 Jun 2003 21:11:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S4yM-0001A7-00; Mon, 16 Jun 2003 21:09:18 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S4yL-0001A2-00; Mon, 16 Jun 2003 21:09:17 -0400
Received: from MOU1WNEXC03.verisign.com (verisign.com [65.205.251.57])
        by peacock.verisign.com (8.12.9/) with ESMTP id h5H1BTh6026332;
        Mon, 16 Jun 2003 18:11:29 -0700 (PDT)
Received: by mou1wnexc03.verisign.com with Internet Mail Service (5.5.2653.19)
	id <MLJJTX9W>; Mon, 16 Jun 2003 18:11:29 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D223A@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>, asrg@ietf.org
Subject: ASRG Censorship and IPR
Date: Mon, 16 Jun 2003 18:11:29 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk


Concerning the censorship issue, the chair gives as his reason for blocking
my posts as follows:

Your request to the Asrg mailing list

    Posting of your message titled "Reverse DNS modem pool records."

has been rejected by the list moderator.  The moderator gave the
following reason for rejecting your request:

"I need you to decide if you are a member of this group or not. You
have stated that you are an ex-member and you have stated that you
plan to form a competing group. If you do not believe in the goals of
this group, then I can not expect meaningful contributions from you.
Therefore, I do not see the purpose of you posting your opinions to
this research group's mailing list. Thank you. If at some point, you
decide that you would like to contribute to the research group's
efforts to address the problem, then please let me know."



The group has not been allowed to see that this is the basis for the
censorship policy - forming a group which the chair perceives as being in
competition. I do not think in this case the actions qualify as moderation.
I have complained to the IRTF chair and got nowhere.

After I pointed out this was hardly a legitimate use of moderation most of
of the posts I sent following were blocked without any form of comment.
Presumably to avoid any more embarassing comments that might reveal the true
motive.

There are two reasons why ASRG is not an adequate forum for anti-spam
standards. First it is a research group, the IPR regime is simply not viable
for building an open standard given the amount of IP claims existing. An ad
hoc post to the list does not fix that. Second, none of the principal
stakeholders with the ability to effect change are participating and a
number have explicitly rejected any participation with IETF/IRTF on this
topic. Hence the need for an alternate forum. I see no reason why membership
of one should cause automatic blacklisting in what is pretending to be an
open process in the IRTF.


The problem with the IPR policy is the WAY in which it was imposed. It was
not even a statement that RFC 2062 rules were in force which might at least
be readily understood and have some chance of being enforceable. Instead we
just got told that a decision had been taken by unspecified persons and some
text copied out of RFC 2062 with no indication that that is where they had
been taken from or any changes that might have been made.

My objection was one which anyone faced with a unilateral contract would be,
just what are you trying to spring here? 

The group is not even being allowed to discuss this issue because the posts
are still being blocked.


		Phill




From owner-ietf@ietf.org  Mon Jun 16 21:56:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12454
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 21:56:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S5Zn-0002OA-VK
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 21:47:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S5U4-0002IK-6M
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 21:42:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12276
	for <ietf@ietf.org>; Mon, 16 Jun 2003 21:42:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S5Rr-0001Q3-00
	for ietf@ietf.org; Mon, 16 Jun 2003 21:39:47 -0400
Received: from swan.mail.pas.earthlink.net ([207.217.120.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S5Rq-0001Q0-00
	for ietf@ietf.org; Mon, 16 Jun 2003 21:39:46 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by swan.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19S5Tp-0000Rp-00; Mon, 16 Jun 2003 18:41:49 -0700
Date: Mon, 16 Jun 2003 21:39:03 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: moore@cs.utk.edu, aarsenau@bbn.com, pbaker@verisign.com, ietf@ietf.org
Subject: myth of the great transition (was US Defense Department formally
 adopts IPv6)
Message-Id: <20030616213903.695cadc1.moore@cs.utk.edu>
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D2238@mou1wnexm02.verisign.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D2238@mou1wnexm02.verisign.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> The think I find mindboggling about all this is that I have yet to see a
> concise explanation of how the great transition to IPv6 is going to be
> managed and what the incentive for early adopters is going to be.

There isn't going to be a great transition to IPv6 in the sense that 
you seem to mean.  IPv4 and IPv6 will coexist for a long time.  The most
popular IPv4 applications - web and email - will be the last to abandon
IPv4, and they won't do so until IPv6 is ubiquitous.

The incentive for IPv6 adopters is obvious - they'll use IPv6 to do 
things they cannot do with IPv4.  Those things include:  deploying lots of
distinctly addressible pieces of hardware (e.g. things that get monitored or
controlled remotely), alleviating an actual or imposed, global or local,
shortage of IPv4  addresses (this applies both to China and home networks),
talking to IPv6-only devices (that use IPv6 because they cannot reliably get
enough IPv4 addresses), and any apps that cannot reliably operate through NAT.

You might say that there isn't much use of these things today.  But when you
think about it, enabling new kinds of ways to use the Internet infrastructure
is about the only way for ISPs in saturated markets to get new customers.



From owner-ietf@ietf.org  Mon Jun 16 22:14:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12893
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 22:14:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S5jP-0002t8-WE
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 21:57:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S5eR-0002TJ-Km
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 21:52:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12391
	for <ietf@ietf.org>; Mon, 16 Jun 2003 21:52:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S5cE-0001SX-00
	for ietf@ietf.org; Mon, 16 Jun 2003 21:50:30 -0400
Received: from tomts17.bellnexxia.net ([209.226.175.71] helo=tomts17-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19S5cD-0001SU-00
	for ietf@ietf.org; Mon, 16 Jun 2003 21:50:29 -0400
Received: from yahoo.com ([65.93.184.200]) by tomts17-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030616233712.QZQL8537.tomts17-srv.bellnexxia.net@yahoo.com>;
          Mon, 16 Jun 2003 19:37:12 -0400
Date: Mon, 16 Jun 2003 19:37:09 -0400
Subject: Re: SIRs
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "ietf@ietf.org" <ietf@ietf.org>
To: Pekka Savola <pekkas@netcore.fi>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <Pine.LNX.4.44.0306162258340.22096-100000@netcore.fi>
Message-Id: <72AF32E0-A053-11D7-93B4-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Monday, June 16, 2003, at 04:00  PM, Pekka Savola wrote:

> On Mon, 16 Jun 2003, S Woodside wrote:
>> It might be interesting to have a facility where comments can be
>> attached to I-Ds (like in bug tracking systems / bugzilla).
>
> I'm not sure what kind of comments you refer to?
>
> "I think this and this is a bad idea, for these reasons, but naturally 
> the
> document authors/editors won't add that in the next revision of the 
> ID" ?

Create a document-based thread rather than a WG-based or 
mailing-list-based thread. Patches could also be posted and revision 
history (changes between revisions) would be easier to keep track of. 
People who have negative comments could post them, and they'd be part 
of the history record of the draft even if their comments are 
ignored/rejected.

simon




From owner-ietf@ietf.org  Mon Jun 16 23:18:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14345
	for <ietf-web-archive@odin.ietf.org>; Mon, 16 Jun 2003 23:18:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19S6sM-0004Rs-9I
	for ietf-list@asgard.ietf.org; Mon, 16 Jun 2003 23:11:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S6mz-0004Ov-CL
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 23:05:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14045
	for <ietf@ietf.org>; Mon, 16 Jun 2003 23:05:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S6km-0001ry-00
	for ietf@ietf.org; Mon, 16 Jun 2003 23:03:24 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19S6kl-0001rv-00
	for ietf@ietf.org; Mon, 16 Jun 2003 23:03:24 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19S6ms-000Niv-00; Mon, 16 Jun 2003 22:05:34 -0500
Date: Mon, 16 Jun 2003 23:05:34 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@cs.utk.edu>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: myth of the great transition (was US Defense
 Department formally adopts IPv6)
Message-ID: <54469623.1055804734@p3.JCK.COM>
In-Reply-To: <20030616213903.695cadc1.moore@cs.utk.edu>
References: <2A1D4C86842EE14CA9BC80474919782E0D2238@mou1wnexm02.ve
 risign.com> <20030616213903.695cadc1.moore@cs.utk.edu>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Monday, 16 June, 2003 21:39 -0400 Keith Moore 
<moore@cs.utk.edu> wrote:

>> The think I find mindboggling about all this is that I have
>> yet to see a concise explanation of how the great transition
>> to IPv6 is going to be managed and what the incentive for
>> early adopters is going to be.
>
> There isn't going to be a great transition to IPv6 in the
> sense that  you seem to mean.  IPv4 and IPv6 will coexist for
> a long time.  The most popular IPv4 applications - web and
> email - will be the last to abandon IPv4, and they won't do so
> until IPv6 is ubiquitous.
>
> The incentive for IPv6 adopters is obvious - they'll use IPv6
> to do  things they cannot do with IPv4.  Those things include:
> deploying lots of distinctly addressible pieces of hardware
> (e.g. things that get monitored or controlled remotely),
> alleviating an actual or imposed, global or local, shortage of
> IPv4  addresses (this applies both to China and home networks),
> talking to IPv6-only devices (that use IPv6 because they
> cannot reliably get enough IPv4 addresses), and any apps that
> cannot reliably operate through NAT.
>...

And, if IETF gets its act sufficiently together early enough, 
the capability for someone who doesn't qualify for PI space 
under current IPv4 rules to do multihoming -- perhaps to 
compensate for two incompetent ISPs by hoping they won't be out 
of service at the same time-- at plausible total costs.   My own 
guess is that, as reliable Internet connections become more 
important to people, and if the trend toward lowering skill 
levels at ISPs continues, small enterprise and SOHO multihoming 
may turn out to be one of the driving applications for IPv6. 
If we get our act sufficiently together...

       john






From owner-ietf@ietf.org  Tue Jun 17 03:56:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02366
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 03:56:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SB2U-0005Tf-LE
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 03:37:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SB0A-0005RC-Ad
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 03:35:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01949
	for <ietf@ietf.org>; Tue, 17 Jun 2003 03:35:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SAxx-0003js-00
	for ietf@ietf.org; Tue, 17 Jun 2003 03:33:17 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SAxw-0003jp-00
	for ietf@ietf.org; Tue, 17 Jun 2003 03:33:16 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h5H7aMxS086771;
	Tue, 17 Jun 2003 09:36:22 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Tue, 17 Jun 2003 09:35:27 +0200
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Keith Moore <moore@cs.utk.edu>, "ietf@ietf.org" <ietf@ietf.org>
To: John C Klensin <john-ietf@jck.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <54469623.1055804734@p3.JCK.COM>
Message-Id: <4422EEB8-A096-11D7-B708-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On dinsdag, jun 17, 2003, at 05:05 Europe/Amsterdam, John C Klensin 
wrote:

>> The incentive for IPv6 adopters is obvious - they'll use IPv6
>> to do  things they cannot do with IPv4.

Obviously that would be a very good reason to adopt IPv6, but due to 
the ever evolving hacks in IPv4 there is very little you absolutely, 
positively cannot do in IPv4. Other reasons to adopt IPv6 are that it's 
cool (I mean it - for some people this is all the reason they need), 
because it's The Right Thing To Do, to impress governments that require 
or desire it and finally, because it makes life easier in some 
respects. Personally, I love the way I can connect to a router or host 
over IPv6, completely screw up IPv4 addressing and routing and fix it 
again without fear of locking myself out.

> And, if IETF gets its act sufficiently together early enough, the 
> capability for someone who doesn't qualify for PI space under current 
> IPv4 rules to do multihoming

At some point in the future when IPv6 becomes reasonably common but 
before people start to ditch IPv4, you get to multihome by connecting 
to the net over IPv4 and IPv6 through different networks. This works 
very well and doesn't have any of the scaling issues that current 
multihoming has.




From owner-ietf@ietf.org  Tue Jun 17 05:14:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04277
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 05:14:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SCMe-0006xY-Uz
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 05:02:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SCMC-0006uy-An
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 05:02:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04097
	for <ietf@ietf.org>; Tue, 17 Jun 2003 05:02:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SCJz-0004Br-00
	for ietf@ietf.org; Tue, 17 Jun 2003 05:00:07 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SCJy-0004Bl-00
	for ietf@ietf.org; Tue, 17 Jun 2003 05:00:06 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 184AE62595; Tue, 17 Jun 2003 11:01:52 +0200 (CEST)
Date: Tue, 17 Jun 2003 11:01:52 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org,
        phoffman@imc.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
Message-ID: <368470000.1055840512@askvoll.hjemme.alvestrand.no>
In-Reply-To: <200306161845.h5GIjYra017070@calcite.rhyolite.com>
References: <p05210620bb13b2531d86@[63.202.92.152]>
 <200306161845.h5GIjYra017070@calcite.rhyolite.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On mandag, juni 16, 2003 12:45:34 -0600 Vernon Schryver 
<vjs@calcite.rhyolite.com> wrote:

> The suggestion of having two lists, one filtered and a second named
> whatever-noise, both with open archives, sounds fine to me, but wouldn't
> help the ASRG case.  I think that the ASRG case would be instantly
> resolved if the moderator would publish all of the rejected messages
> and related corresponce without any additional commentary...not that
> I think there's any case there, but passers-by might not have seen the
> first several weeks of traffic in the ASRG mailing list not to mention
> those "courtesy" copies I mentioned.

the ICANN DNSO GA list operated with "ga" and "ga-full" lists ("full" being 
all spam, crosspostings and postings from moderated posters in addition to 
the normal list traffic).

the ga-full list was, I believe, not archived.

it served to silence the complaints that it wouldn't be possible to see if 
moderation was fair or not, which richly repaid the work of setting it up - 
I think it had approximately 5 memebers.

               Harald




From owner-ietf@ietf.org  Tue Jun 17 05:39:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04803
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 05:39:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SCkq-0007cs-RK
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 05:27:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SCkd-0007Zq-GD
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 05:27:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04633
	for <ietf@ietf.org>; Tue, 17 Jun 2003 05:27:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SCiQ-0004MF-00
	for ietf@ietf.org; Tue, 17 Jun 2003 05:25:22 -0400
Received: from kirk.rvdp.org ([80.126.101.63])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SCiP-0004MC-00
	for ietf@ietf.org; Tue, 17 Jun 2003 05:25:21 -0400
Received: (from rvdp@localhost)
	by kirk.rvdp.org (8.11.6p2/8.11.6) id h5H9RIk23089;
	Tue, 17 Jun 2003 11:27:18 +0200 (CEST)
Date: Tue, 17 Jun 2003 11:27:18 +0200
From: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
To: Keith Moore <moore@cs.utk.edu>
Cc: "Hallam-Baker, Phillip" <pbaker@verisign.com>, aarsenau@bbn.com,
        ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
Message-ID: <20030617092718.GA22843@rvdp.org>
References: <2A1D4C86842EE14CA9BC80474919782E0D2238@mou1wnexm02.verisign.com> <20030616213903.695cadc1.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030616213903.695cadc1.moore@cs.utk.edu>
User-Agent: Mutt/1.4.1i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Jun 16, 2003 at 21:39:03 -0400, Keith Moore wrote:

> There isn't going to be a great transition to IPv6 in the sense that 
> you seem to mean.  IPv4 and IPv6 will coexist for a long time.

Yes, but I am afraid that underestimates the overhead of running
dual stack.

o address administration (dns, number plans, firewall rules, etc)
  has to be done twice
o network management systems have to monitor both protocols
o when there is a problem, you first have to figure out if it
  is v4 or v6 related
o new services (software/hardware) have to be setup and tested for
  both protocols
...

To be clear, I do think dual stack is the best strategy for the
present early stage of _transition_.

	rvdp



From owner-ietf@ietf.org  Tue Jun 17 06:07:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05431
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 06:07:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SDDs-00024K-0r
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 05:57:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SD9d-00021j-92
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 05:53:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05139
	for <ietf@ietf.org>; Tue, 17 Jun 2003 05:53:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SD7P-0004Ts-00
	for ietf@ietf.org; Tue, 17 Jun 2003 05:51:12 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SD7P-0004Tp-00
	for ietf@ietf.org; Tue, 17 Jun 2003 05:51:11 -0400
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id KAA01306
	for <ietf@ietf.org>; Tue, 17 Jun 2003 10:53:26 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3p2/8.9.3) with ESMTP id KAA12942
	for <ietf@ietf.org>; Tue, 17 Jun 2003 10:53:26 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h5H9rQF06073
	for ietf@ietf.org; Tue, 17 Jun 2003 10:53:26 +0100
Date: Tue, 17 Jun 2003 10:53:26 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
Message-ID: <20030617095325.GQ4610@login.ecs.soton.ac.uk>
References: <2A1D4C86842EE14CA9BC80474919782E0D2238@mou1wnexm02.verisign.com> <20030616213903.695cadc1.moore@cs.utk.edu> <20030617092718.GA22843@rvdp.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030617092718.GA22843@rvdp.org>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, Jun 17, 2003 at 11:27:18AM +0200, Ronald van der Pol wrote:
> On Mon, Jun 16, 2003 at 21:39:03 -0400, Keith Moore wrote:
> 
> > There isn't going to be a great transition to IPv6 in the sense that 
> > you seem to mean.  IPv4 and IPv6 will coexist for a long time.
> 
> Yes, but I am afraid that underestimates the overhead of running
> dual stack.

Indeed, everything you suggest means that there is an increase in costs
to adopt IPv6, because at this stage you would be very brave to launch
an IPv6-only service, and thus dual-stack is the only way to go.   This 
ramp in expenses is a barrier to IPv6 adoption, when no clear and 
significant additonal revenues can be seen.

However, an operator that does go dual-stack, and is able to become proficient
in managing and operating such an infrastructure, will be well placed to
take advantage of the new IPv6 services as they emerge.  We hear Sony saying
all consumer networked appliances will support IPv6 by 2005.  We hear MS
talk about IPv6 for pervasive collaborative communication (p2p, conferencing
and messaging).  The services and applications are coming.

Question is, who are the early operator adoptors, especially in the home
and enterprise solutions space,  and what are their business plans?

At the moment the academic research networks are taking the lead, because
they do not need a business case to deploy IPv6.  Their philosophy is that
if they deploy IPv6 to some of the best minds in the universities, new
applications and innovation will follow.   Their experience, and
the fact that they iron out the early adoptor bugs with the likes of
Cisco and Juniper, is good news for the second wave commercial adoptors,
which we're just beginning to see the tip of now.

I don't see the DoD adopting IPv6 on a whim; they'll have done their
homework...

Tim



From owner-ietf@ietf.org  Tue Jun 17 06:37:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06142
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 06:37:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SDgu-0007Oh-2Z
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 06:27:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SDfA-0007L4-Ut
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 06:26:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05882
	for <ietf@ietf.org>; Tue, 17 Jun 2003 06:26:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SDcx-0004fh-00
	for ietf@ietf.org; Tue, 17 Jun 2003 06:23:47 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SDcw-0004fa-00
	for ietf@ietf.org; Tue, 17 Jun 2003 06:23:46 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h5HAPxtU026394;
	Tue, 17 Jun 2003 06:25:59 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h5HAPxJA026393;
	Tue, 17 Jun 2003 06:25:59 -0400
Date: Tue, 17 Jun 2003 06:25:59 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200306171025.h5HAPxJA026393@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Tim Chown <tjc@ecs.soton.ac.uk>

    > We hear Sony saying all consumer networked appliances will support IPv6
    > by 2005. We hear MS talk about IPv6 for pervasive collaborative
    > communication

I wish I could get $10 for every time I heard one of these predictions. I've
got a huge stack of them, dating back to the 1990's. I think the one I liked
the best was how G3 phones were going to be the killer app for v6.

I must say, the latest pronouncement from the DoD was really amusing - it
just increased the "deja vu" level one more delicious notch. I really should
make those T-shirts I talked about...

	Noel



From owner-ietf@ietf.org  Tue Jun 17 07:07:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06700
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 07:07:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SE57-00083T-0C
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 06:52:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SE51-00080c-Nf
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 06:52:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06520
	for <ietf@ietf.org>; Tue, 17 Jun 2003 06:52:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SE2o-0004oB-00
	for ietf@ietf.org; Tue, 17 Jun 2003 06:50:30 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SE2n-0004o8-00
	for ietf@ietf.org; Tue, 17 Jun 2003 06:50:29 -0400
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id LAA02746
	for <ietf@ietf.org>; Tue, 17 Jun 2003 11:52:45 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3p2/8.9.3) with ESMTP id LAA18074
	for <ietf@ietf.org>; Tue, 17 Jun 2003 11:52:45 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h5HAqjE07322
	for ietf@ietf.org; Tue, 17 Jun 2003 11:52:45 +0100
Date: Tue, 17 Jun 2003 11:52:45 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
Message-ID: <20030617105244.GV4610@login.ecs.soton.ac.uk>
References: <200306171025.h5HAPxJA026393@ginger.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200306171025.h5HAPxJA026393@ginger.lcs.mit.edu>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, Jun 17, 2003 at 06:25:59AM -0400, J. Noel Chiappa wrote:
>     > From: Tim Chown <tjc@ecs.soton.ac.uk>
> 
>     > We hear Sony saying all consumer networked appliances will support IPv6
>     > by 2005. We hear MS talk about IPv6 for pervasive collaborative
>     > communication
> 
> I wish I could get $10 for every time I heard one of these predictions. I've
> got a huge stack of them, dating back to the 1990's. I think the one I liked
> the best was how G3 phones were going to be the killer app for v6.

Fair point.  But a year ago we didn't have Abilene, GEANT or a large number
of European NRENs offering a native IPv6 service.  Cisco and Juniper's 
support has come on in leaps and bounds, and now we do see US and European
real deployment, overlaid on the production IPv4 network, and we see dual-stack
transatlantic links.   On the coal face, we can see real progress.  

A year ago we didn't have official IPv6 support in Windows XP.  We didn't
have prototypes from Sony and Panasnic being shown publicly.   We didn't
have a pilot IPv6 deployment project from Microsoft (threedegrees).  Things 
are moving on.  Sure, we'll get hype from the marketing people, but that's 
what they're paid to produce :)  

And noone's forcing IPv6 on anybody.  If you want to keep running IPv4, with
or without NAT, feel free.

Tim



From owner-ietf@ietf.org  Tue Jun 17 09:37:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15099
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 09:37:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SFUE-0002mW-W8
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 08:22:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SFGK-0001Ng-71
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 08:08:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09084
	for <ietf@ietf.org>; Tue, 17 Jun 2003 08:08:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SFE6-0005H5-00
	for ietf@ietf.org; Tue, 17 Jun 2003 08:06:14 -0400
Received: from grouse.mail.pas.earthlink.net ([207.217.120.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SFE5-0005H1-00
	for ietf@ietf.org; Tue, 17 Jun 2003 08:06:14 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by grouse.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19SFFz-00056L-00; Tue, 17 Jun 2003 05:08:11 -0700
Date: Tue, 17 Jun 2003 08:05:23 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
Cc: moore@cs.utk.edu, pbaker@verisign.com, aarsenau@bbn.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department
 formally adopts IPv6)
Message-Id: <20030617080523.0b525f59.moore@cs.utk.edu>
In-Reply-To: <20030617092718.GA22843@rvdp.org>
References: <2A1D4C86842EE14CA9BC80474919782E0D2238@mou1wnexm02.verisign.com>
	<20030616213903.695cadc1.moore@cs.utk.edu>
	<20030617092718.GA22843@rvdp.org>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > There isn't going to be a great transition to IPv6 in the sense that 
> > you seem to mean.  IPv4 and IPv6 will coexist for a long time.
> 
> Yes, but I am afraid that underestimates the overhead of running
> dual stack.

Actually, I can imagine that a lot of enterprise networks will try moving
to single stack, and will almost get there.  I also imagine that tools
will emerge to reduce some of the overhead of dual-stack administration -
e.g. managing address administration and router filters with one set of
rules.  I don't think we'll see that many apps run on both protocols in
practice - I think network admins will say "within our network, apps a, b, c
run on v4, apps x, y, z runs on v6".

> To be clear, I do think dual stack is the best strategy for the
> present early stage of _transition_.

I see it as a transition also.  But I think there will be a long period
in which v6 is used mostly for new things, and only when v6 is more 
ubiquitious than v4 will we see some of the core services migrate.



From owner-ietf@ietf.org  Tue Jun 17 09:38:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15153
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 09:38:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SFUF-0002nR-In
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 08:22:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SFLi-0001S6-KD
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 08:14:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09268
	for <ietf@ietf.org>; Tue, 17 Jun 2003 08:14:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SFJV-0005KS-00
	for ietf@ietf.org; Tue, 17 Jun 2003 08:11:49 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SFJU-0005KP-00
	for ietf@ietf.org; Tue, 17 Jun 2003 08:11:48 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h5HCE4tU026783;
	Tue, 17 Jun 2003 08:14:04 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h5HCE3KX026782;
	Tue, 17 Jun 2003 08:14:03 -0400
Date: Tue, 17 Jun 2003 08:14:03 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200306171214.h5HCE3KX026782@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Tim Chown <tjc@ecs.soton.ac.uk>

    > But a year ago we didn't have ... Things are moving on.

Got a big stack of these too.

	Noel



From owner-ietf@ietf.org  Tue Jun 17 09:46:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15590
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 09:46:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SGdU-0002iO-2T
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 09:36:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SFWk-0003MN-AI
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 08:25:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09920
	for <ietf@ietf.org>; Tue, 17 Jun 2003 08:25:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SFUW-0005U3-00
	for ietf@ietf.org; Tue, 17 Jun 2003 08:23:12 -0400
Received: from ast-lambert-110-2-1-3.w81-50.abo.wanadoo.fr ([81.50.80.3] helo=freebie.atkielski.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SFUV-0005U0-00
	for ietf@ietf.org; Tue, 17 Jun 2003 08:23:11 -0400
Received: from contactdish (contactdish.atkielski.com [10.0.0.10])
	by freebie.atkielski.com (8.12.9/8.12.9) with SMTP id h5HCPRca032922
	for <ietf@ietf.org>; Tue, 17 Jun 2003 14:25:27 +0200 (CEST)
Message-ID: <016901c334cb$88900090$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <200306171025.h5HAPxJA026393@ginger.lcs.mit.edu> <20030617105244.GV4610@login.ecs.soton.ac.uk>
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
Date: Tue, 17 Jun 2003 14:25:26 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tim writes:

> But a year ago we didn't have Abilene, GEANT
> or a large number of European NRENs offering
> a native IPv6 service.

A year ago, my parents weren't using IPv6, whereas today ... they still
aren't using it.  When their connection is IPv6, I'll know that it has
arrived.

The more pervasive a technology becomes, the more slowly its widespread
implementation changes, and the greater the gap between the leading edge in
that technology and the actual state of implementation in the field.

Computerland isn't the way it used to be.  A large chunk of the world uses
computers now.  Nothing happens quickly anymore.  It's getting further and
further away from the halcyon days of what was then called EDP, when things
could change overnight, and closer and closer to the worlds of automobiles
and telephones, ubiquitous technologues that change only with imperceptibly
glacial slowness.

It's entirely possible that IPv6 may _still_ be planned for "real soon now"
ten or fifteen years from today.

> On the coal face, we can see real progress.

Wait until the coal is producing power for your microwave before you
celebrate.

> If you want to keep running IPv4, with or without NAT,
> feel free.

That's exactly what people will do, until and unless they encounter a
problem with IPv4 that can only be solved by IPv6.




From owner-ietf@ietf.org  Tue Jun 17 10:10:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17373
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 10:10:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SGk0-0003rh-5q
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 09:43:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19R1Kv-0002hl-2V
	for ietf@asgard.ietf.org; Fri, 13 Jun 2003 23:04:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03538
	for <ietf@ietf.org>; Fri, 13 Jun 2003 23:04:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19R1Io-0003bK-00
	for ietf@ietf.org; Fri, 13 Jun 2003 23:02:02 -0400
Received: from adsl-67-113-9-82.dsl.snfc21.pacbell.net ([67.113.9.82] helo=gwydion.dragon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19R1In-0003bE-00
	for ietf@ietf.org; Fri, 13 Jun 2003 23:02:01 -0400
Received: from gwydion.dragon.net (localhost [127.0.0.1])
	by gwydion.dragon.net (8.12.8/8.12.8) with ESMTP id h5E34Acq068911
	for <ietf@ietf.org>; Fri, 13 Jun 2003 20:04:10 -0700 (PDT)
Message-Id: <200306140304.h5E34Acq068911@gwydion.dragon.net>
To: ietf@ietf.org
From: Paul Ebersman <list-ietf@dragon.net>
Subject: Re: US Defense Department formally adopts IPv6 
In-Reply-To: Message from Richard Shockey <richard@shockey.us> 
   of "Fri, 13 Jun 2003 20:47:34 EDT." <5.2.0.9.2.20030613204634.02266130@popd.ix.netcom.com> 
X-Mailer: MH-E 7.1; nmh 1.0.4; XEmacs 21.4
Date: Fri, 13 Jun 2003 20:04:10 -0700
Sender: owner-ietf@ietf.org
Precedence: bulk


richard> Vendors must be compliant by Oct 1

richard> http://www.washingtonpost.com/wp-dyn/articles/A55558-2003Jun13.html?nav=hptoc_tn

For those of us around to remember ADA:

  phase 1: *ALL* coding for DOD/GOv must be done in ADA

  phase 2: Gee, no compliant ADA compilers and not enough ADA
    coders. Ok, Must be ADA (or C).

  phase 3: What's ADA?

Let's also stroll down memory lane and think about TP4/CLNS with
CMIP. How many governments are running it as their exclusive backbone?

>From the article above:

  "The evolution toward the new standard must be taken into account for
  all purchases starting Oct. 1, Stenbit, assistant secretary of defense
  for networks and information integration, told the armed services in a
  memo."

"must be taken into account"

"Gee, we can't buy what we need in IPv6 only. Guess we'll still use IPv4
and use IPv6 where it works."

The more things change...





From owner-ietf@ietf.org  Tue Jun 17 10:18:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18316
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 10:18:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SGk0-0003rp-Ab
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 09:43:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19R1Oj-0002kX-9K
	for ietf@asgard.ietf.org; Fri, 13 Jun 2003 23:08:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03650
	for <ietf@ietf.org>; Fri, 13 Jun 2003 23:08:06 -0400 (EDT)
From: RickGall1@aol.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19R1Mc-0003du-00
	for ietf@ietf.org; Fri, 13 Jun 2003 23:05:58 -0400
Received: from imo-r07.mx.aol.com ([152.163.225.103])
	by ietf-mx with esmtp (Exim 4.12)
	id 19R1Mb-0003dl-00
	for ietf@ietf.org; Fri, 13 Jun 2003 23:05:57 -0400
Received: from RickGall1@aol.com
	by imo-r07.mx.aol.com (mail_out_v36.3.) id l.16c.1ff51789 (3657)
	 for <ietf@ietf.org>; Fri, 13 Jun 2003 23:07:34 -0400 (EDT)
Message-ID: <16c.1ff51789.2c1beb76@aol.com>
Date: Fri, 13 Jun 2003 23:07:34 EDT
Subject: CRAPS BOF and WIFI
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 5.0 for Windows sub 138
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Can anyone tell me if CRAPS is still in operations?





From owner-ietf@ietf.org  Tue Jun 17 10:20:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18632
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 10:20:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SGk3-0003zf-S5
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 09:43:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S4dp-0000Y3-1c
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 20:48:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10732
	for <ietf@ietf.org>; Mon, 16 Jun 2003 20:48:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S4bc-0000wP-00
	for ietf@ietf.org; Mon, 16 Jun 2003 20:45:48 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19S4bb-0000vw-00
	for ietf@ietf.org; Mon, 16 Jun 2003 20:45:47 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.19.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id UAA05989;
	Mon, 16 Jun 2003 20:42:25 -0400
Date: Mon, 16 Jun 2003 20:43:51 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: David Morris <dwm@xpasc.com>
cc: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>,
        Paul Hoffman / IMC <phoffman@imc.org>, <ietf@ietf.org>
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
In-Reply-To: <Pine.LNX.4.33.0306161557040.18994-100000@egate.xpasc.com>
Message-ID: <Pine.LNX.4.44.0306162038030.5940-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Anyone interested in harvesting addresses would simply subscribe to the
various lists.  There is no way to prevent this type of abuse.  It is a
non-issue. Only certain radical anti-spammers (and those duped by them)
believe it to be problem. Coincidentally, only lists frequented by such
radical antispammers seem to suffer these problems. I guess they've proven
the point: Mail lists can be abused.

Of course, that isn't the same point as "(Type 1) Spammers abuse mail
lists".

		--Dean

On Mon, 16 Jun 2003, David Morris wrote:

>
>
> On Mon, 16 Jun 2003, Michael Froomkin - U.Miami School of Law wrote:
>
> > My understanding is that The Mail Archive
> > (http://www.mail-archive.com/lists.html)  will provide free storage for
> > mailing lists.  I think every WG list should be permanetly archived in
> > this manner.
>
> What a great way to help address harvesters ... one site ... one 'API' to
> program against to harvest many valid addresses. This particular archive
> example hides email addresses, but it took me less that 5 minutes to
> determine how to recover addresses from the page data.
>
> So I don't think the suggested policy is a good idea without much more
> effective blocking of access to email addresses.
>
> Dave Morris
>
>
>






From owner-ietf@ietf.org  Tue Jun 17 10:23:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18959
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 10:23:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SGk4-00040j-G0
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 09:43:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SGTJ-0000DJ-1C
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 09:26:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14326
	for <ietf@ietf.org>; Tue, 17 Jun 2003 09:25:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SGR5-0006oA-00
	for ietf@ietf.org; Tue, 17 Jun 2003 09:23:43 -0400
Received: from one.elistx.com ([209.116.252.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SGR4-0006o5-00
	for ietf@ietf.org; Tue, 17 Jun 2003 09:23:42 -0400
Received: from localhost (one.elistx.com [209.116.252.130])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HGM007CSO0SA1@eListX.com>
 for ietf@ietf.org; Tue, 17 Jun 2003 09:26:53 -0400 (EDT)
Date: Tue, 17 Jun 2003 09:26:24 -0400 (Eastern Daylight Time)
From: James M Galvin <galvin+ietf@elistx.com>
Subject: full list for moderated list (was: CLOSE ASRG NOW IT HAS FAILED)
In-reply-to: <368470000.1055840512@askvoll.hjemme.alvestrand.no>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org,
        Paul Hoffman <phoffman@imc.org>
Message-id: <Pine.WNT.4.51.0306170903430.2732@office.elistx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
References: <p05210620bb13b2531d86@[63.202.92.152]>
 <200306161845.h5GIjYra017070@calcite.rhyolite.com>
 <368470000.1055840512@askvoll.hjemme.alvestrand.no>
Sender: owner-ietf@ietf.org
Precedence: bulk


On Tue, 17 Jun 2003, Harald Tveit Alvestrand wrote:

    > The suggestion of having two lists, one filtered and a second named
    > whatever-noise, both with open archives, sounds fine to me, but wouldn't
    > help the ASRG case.

    the ICANN DNSO GA list operated with "ga" and "ga-full" lists
    ("full" being all spam, crosspostings and postings from moderated
    posters in addition to the normal list traffic).

    the ga-full list was, I believe, not archived.

    it served to silence the complaints that it wouldn't be possible to
    see if moderation was fair or not, which richly repaid the work of
    setting it up - I think it had approximately 5 memebers.

The presence of the second list may have served its purpose in this case
but I believe the mechanism is flawed.  A temporary archive is also
required.

The point should not be to require people to subscribe to the "full"
list in order to review the actions of the moderator but rather to
have the full list available for review should an issue arise.

To require the subscription begs the question of why have two lists?
Two lists give the *perception* of fairness and positive action but
provide marginal (at best) support for review beyond what can be done
when only the "moderated" list is available.  You still have to contact
one of the members to get prior messages or depend on the "victim" to
provide copies of messages submitted that were rejected.

What is required is a full list (with or without subscribers) with an
archive that includes everything (except viruses and obvious spam) for a
period of time.  I happen to like 10 days but I've heard others suggest
that it really needs to be much longer, perhaps 30, 60, or even 90 days.

Jim



From owner-ietf@ietf.org  Tue Jun 17 10:49:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20316
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 10:49:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SHMu-0004wL-B3
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 10:23:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SGmF-0004AF-Oy
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 09:45:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15557
	for <ietf@ietf.org>; Tue, 17 Jun 2003 09:45:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SGk2-0007Ah-00
	for ietf@ietf.org; Tue, 17 Jun 2003 09:43:18 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SGk1-0007Ae-00
	for ietf@ietf.org; Tue, 17 Jun 2003 09:43:17 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5HDjWXn014909
	for ietf@ietf.org env-from <vjs>;
	Tue, 17 Jun 2003 07:45:32 -0600 (MDT)
Date: Tue, 17 Jun 2003 07:45:32 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306171345.h5HDjWXn014909@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: full list for moderated list 
References:  <Pine.WNT.4.51.0306170903430.2732@office.elistx.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: James M Galvin <galvin+ietf@elistx.com>

> ...
> What is required is a full list (with or without subscribers) with an
> archive that includes everything (except viruses and obvious spam) for a
> period of time. 

yes, provided you error on the side of inclusion when it comes to anything
that might or might not be spam.  I'd forward any spam or viruss to
news.admin.net-abuse.sightings for permanent archiving by Google.

>                  I happen to like 10 days but I've heard others suggest
> that it really needs to be much longer, perhaps 30, 60, or even 90 days.

The ASRG case, including the recent effort involving out of context
quoting, demonstrates that more than 90 days is required.  
If there were a problem with permanent archiving, the one could archive
the full list but not the filtered list, with some kind of added X-header
indicating messages that were filtered.  The non-spam that is not
filtered had better be a trivial number of bytes (for this century)
or someone should be cut off by an ISP.

About the supposed high costs of archiving spam--perhaps Google's
archive of spam has been overlooked.  See
http://groups.google.com/groups?scoring=d&q=group%3A*.sightings
It's valuable when dealing with spammers claiming to not be spammers.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Tue Jun 17 10:49:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20355
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 10:49:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SHMx-00051S-SO
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 10:23:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SH2d-0006pa-Fj
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 10:02:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16404
	for <ietf@ietf.org>; Tue, 17 Jun 2003 10:02:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SH0P-0007My-00
	for ietf@ietf.org; Tue, 17 Jun 2003 10:00:13 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SH0P-0007Mt-00
	for ietf@ietf.org; Tue, 17 Jun 2003 10:00:13 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h5HE2Qw24283;
	Tue, 17 Jun 2003 07:02:26 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200306171402.h5HE2Qw24283@boreas.isi.edu>
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
In-Reply-To: <016901c334cb$88900090$0a00000a@atkielski.com> from Anthony Atkielski at "Jun 17, 3 02:25:26 pm"
To: anthony@atkielski.com (Anthony Atkielski)
Date: Tue, 17 Jun 2003 07:02:26 -0700 (PDT)
Cc: 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
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

% Tim writes:
% 
% > But a year ago we didn't have Abilene, GEANT
% > or a large number of European NRENs offering
% > a native IPv6 service.
% 
% A year ago, my parents weren't using IPv6, whereas today ... they still
% aren't using it.  When their connection is IPv6, I'll know that it has
% arrived.

	so, you expect your parents to adopt new technology before
	you do?

% > On the coal face, we can see real progress.
% Wait until the coal is producing power for your microwave before you
% celebrate.

	for many, this is true now. coal is the fuel used to
	generate much of the electrical power... unless, like
	some, they have a "Mr. Fusion"

% > If you want to keep running IPv4, with or without NAT,
% > feel free.
% 
% That's exactly what people will do, until and unless they encounter a
% problem with IPv4 that can only be solved by IPv6.

	Your sweeping generalization does not ring true. 
	
	However with a willing suspension of disbelief, this 
	might be why the DoD has decided to adopt IPv6.  
	It wants to do things that can't be done w/ IPv4.
	And the IETF should be excited that someone is actually
	considering adopting an IETF work product.

--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  Tue Jun 17 10:55:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20707
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 10:55:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SHnQ-0007DM-9Q
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 10:50:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SHS0-0005wX-GY
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 10:28:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19407
	for <ietf@ietf.org>; Tue, 17 Jun 2003 10:28:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SHPm-0007nQ-00
	for ietf@ietf.org; Tue, 17 Jun 2003 10:26:26 -0400
Received: from ip166.usw12.rb1.bel.nwlink.com ([209.20.253.166] helo=ran.psg.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SHPl-0007n9-00
	for ietf@ietf.org; Tue, 17 Jun 2003 10:26:25 -0400
Received: from localhost ([127.0.0.1] helo=ran.psg.com)
	by ran.psg.com with esmtp (Exim 4.20)
	id 19SHRo-000Lse-Ey; Tue, 17 Jun 2003 07:28:32 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 17 Jun 2003 07:28:31 -0700
To: James M Galvin <galvin+ietf@elistx.com>
Cc: ietf@ietf.org
Subject: Re: full list for moderated list (was: CLOSE ASRG NOW IT HAS FAILED)
References: <p05210620bb13b2531d86@[63.202.92.152]>
	<200306161845.h5GIjYra017070@calcite.rhyolite.com>
	<368470000.1055840512@askvoll.hjemme.alvestrand.no>
	<Pine.WNT.4.51.0306170903430.2732@office.elistx.com>
Message-Id: <E19SHRo-000Lse-Ey@ran.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

a look at the paper post i receive every day would lead me to believe
that an archive that includes unsolicited commercial post would be
on the order of ten times as large as that for legitimate post.  why
will the internet email be any less polluted?  and you want folk to
archive the <bleep>?  so the search engines can have even more hits
on the slime?  cool.

randy




From owner-ietf@ietf.org  Tue Jun 17 11:07:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18315
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 10:18:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SGk2-0003xC-WD
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 09:43:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19RysT-0003bU-UL
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 14:38:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24838
	for <ietf@ietf.org>; Mon, 16 Jun 2003 14:38:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RyqH-000547-00
	for ietf@ietf.org; Mon, 16 Jun 2003 14:36:33 -0400
Received: from pmesmtp02.wcom.com ([199.249.20.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 19RyqG-00053s-00
	for ietf@ietf.org; Mon, 16 Jun 2003 14:36:32 -0400
Received: from pmismtp04.wcomnet.com ([166.38.62.39])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HGL00L507KRE2@firewall.wcom.com> for ietf@ietf.org; Mon,
 16 Jun 2003 18:34:03 +0000 (GMT)
Received: from pmismtp04.wcomnet.com by pmismtp04.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HGL00M017CVV8@pmismtp04.wcomnet.com>; Mon,
 16 Jun 2003 18:34:03 +0000 (GMT)
Received: from vint.mci.com ([166.50.142.112])
 by pmismtp04.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HGL00LPT7J4ID@pmismtp04.wcomnet.com>; Mon,
 16 Jun 2003 18:33:05 +0000 (GMT)
Date: Mon, 16 Jun 2003 14:33:00 -0400
From: "vinton g. cerf" <vinton.g.cerf@mci.com>
Subject: RE: US Defense Department formally adopts IPv6
X-Sender: vcerf@pop.mcilink.com
To: Christian Huitema <huitema@windows.microsoft.com>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>,
        Al Arsenault <aarsenau@bbn.com>, ietf@ietf.org
Message-id: <5.2.0.9.2.20030616143157.027da260@pop.mcilink.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Content-type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

That is correct - eventually we concluded that IPv5 (which was an experiment)
was a dead end for purposes of carrying real-time, quasi-synchronous traffic.
It was somewhat complex and as I recall was thought not to scale well.

vint

At 10:29 AM 6/16/2003 -0700, Christian Huitema wrote:
>> > (The questions and answers about "IPv5" are sort of funny.)
>> 
>> Quite whatever happened to that?
>
>It is funny that the DoD wouldn't know, since they actually deployed it.
>The code point 5 was used to differentiate packets belonging to the
>"stream" service parallel to IP, ST-II (RFC 1190). It was used to carry
>video conferences services. I remember taking part to one such
>conference in a DARPA locale.
>
>-- Christian Huitema

Vint Cerf
SVP Architecture & Technology
MCI
22001 Loudoun County Parkway, F2-4115
Ashburn, VA 20147
703 886 1690 (v806 1690)
703 886 0047 fax
vinton.g.cerf@mci.com
www.mci.com/cerfsup 






From owner-ietf@ietf.org  Tue Jun 17 11:07:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21361
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 11:07:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SHnQ-0007Ed-P8
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 10:50:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SHY6-00062a-Pe
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 10:35:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19620
	for <ietf@ietf.org>; Tue, 17 Jun 2003 10:35:01 -0400 (EDT)
From: william@elan.net
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SHVt-00002f-00
	for ietf@ietf.org; Tue, 17 Jun 2003 10:32:45 -0400
Received: from sokol.elan.net ([216.151.192.200])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SHVs-00002b-00
	for ietf@ietf.org; Tue, 17 Jun 2003 10:32:44 -0400
Received: from sokol.elan.net (localhost.localdomain [127.0.0.1])
	by sokol.elan.net (8.12.5/8.12.5) with ESMTP id h5HBq80N009428;
	Tue, 17 Jun 2003 04:52:08 -0700
Received: from localhost (william@localhost)
	by sokol.elan.net (8.12.5/8.12.5/Submit) with ESMTP id h5HBq8w9009424;
	Tue, 17 Jun 2003 04:52:08 -0700
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Tue, 17 Jun 2003 04:52:08 -0700 (PDT)
To: James M Galvin <galvin+ietf@elistx.com>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>,
        Vernon Schryver <vjs@calcite.rhyolite.com>, <ietf@ietf.org>,
        Paul Hoffman <phoffman@imc.org>
Subject: Re: full list for moderated list (was: CLOSE ASRG NOW IT HAS FAILED)
In-Reply-To: <Pine.WNT.4.51.0306170903430.2732@office.elistx.com>
Message-ID: <Pine.LNX.4.44.0306170449240.6482-100000@sokol.elan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

I think the original idea was better - to only have web archive of those
posts that did not make it through to the main list. If technically easily 
possible I'd also suggest marking on the main index if post was denied by
moderator or denied by spam filter. And having this archive for only past 
3 months seems just fine for that purpose.

On Tue, 17 Jun 2003, James M Galvin wrote:

> 
> On Tue, 17 Jun 2003, Harald Tveit Alvestrand wrote:
> 
>     > The suggestion of having two lists, one filtered and a second named
>     > whatever-noise, both with open archives, sounds fine to me, but wouldn't
>     > help the ASRG case.
> 
>     the ICANN DNSO GA list operated with "ga" and "ga-full" lists
>     ("full" being all spam, crosspostings and postings from moderated
>     posters in addition to the normal list traffic).
> 
>     the ga-full list was, I believe, not archived.
> 
>     it served to silence the complaints that it wouldn't be possible to
>     see if moderation was fair or not, which richly repaid the work of
>     setting it up - I think it had approximately 5 memebers.
> 
> The presence of the second list may have served its purpose in this case
> but I believe the mechanism is flawed.  A temporary archive is also
> required.
> 
> The point should not be to require people to subscribe to the "full"
> list in order to review the actions of the moderator but rather to
> have the full list available for review should an issue arise.
> 
> To require the subscription begs the question of why have two lists?
> Two lists give the *perception* of fairness and positive action but
> provide marginal (at best) support for review beyond what can be done
> when only the "moderated" list is available.  You still have to contact
> one of the members to get prior messages or depend on the "victim" to
> provide copies of messages submitted that were rejected.
> 
> What is required is a full list (with or without subscribers) with an
> archive that includes everything (except viruses and obvious spam) for a
> period of time.  I happen to like 10 days but I've heard others suggest
> that it really needs to be much longer, perhaps 30, 60, or even 90 days.
> 
> Jim




From owner-ietf@ietf.org  Tue Jun 17 11:15:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18957
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 10:23:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SGk4-000416-Mc
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 09:43:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19S536-0001ea-2S
	for ietf@asgard.ietf.org; Mon, 16 Jun 2003 21:14:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11624
	for <ietf@ietf.org>; Mon, 16 Jun 2003 21:14:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S50t-0001EG-00
	for ietf@ietf.org; Mon, 16 Jun 2003 21:11:55 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S50s-0001EC-00
	for ietf@ietf.org; Mon, 16 Jun 2003 21:11:54 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5H1E8La013921
	for ietf@ietf.org env-from <vjs>;
	Mon, 16 Jun 2003 19:14:08 -0600 (MDT)
Date: Mon, 16 Jun 2003 19:14:08 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306170114.h5H1E8La013921@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: archiving of spam (was CLOSE ARSG etc...)
References: <20030616205933.4f865040.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> well, some of the IETF lists that I maintain seem to get around 50 spams/day
> (at least, if I go away for a day before I cull through the posts from 
> nonsubscribers, I am likely to wind up with 60+ messages on some of those
> lists, of which 59.5 are spam)

Some judicious unsubscribing and reporting of spam can reduce that load
radically.  Contrary to the religous claims of some commentators,
many spammers do try to avoid "internet anti-commerze netcop nazi flamers."
Many just try to avoid send to those who care enough to object.
Of course, some spammers take "remove" requests as confirmation, but
an address that is receiving 50 spam/day doesn't need to worry about not
already being confirmed.


> but it's not the cost of the disk that matters, it's the cost of backing it
> up.  I can think of better things to spend IETF money on.

What's the cost of backup it up?  Writing a CDROM once a week is
essentially free in materials and can be pertty cheap in labor costs.
A CDROM is cheaper than even plain oiled (no Mylar) paper tape used
to be.  It's not as if anyone suggested making serious archives that
would be available within 30 minutes for disaster recovery or that
will survive the end of civilization as we know it.

One hopes that the real mailing list archives are already backed up
sufficiently.  Adding several dozen MBytes of spam and moderation
rejects to those datasets would be literally free if you are using giant
media like CDROMs--not to mention DVDs.


Vernon Schryver    vjs@rhyolite.com





From owner-ietf@ietf.org  Tue Jun 17 11:16:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21910
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 11:16:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SHpL-0007N6-Cl
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 10:52:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SHev-00069I-Jc
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 10:42:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20066
	for <ietf@ietf.org>; Tue, 17 Jun 2003 10:42:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SHch-00007d-00
	for ietf@ietf.org; Tue, 17 Jun 2003 10:39:47 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SHcg-00007E-00
	for ietf@ietf.org; Tue, 17 Jun 2003 10:39:46 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 99FCD622BB; Tue, 17 Jun 2003 16:41:26 +0200 (CEST)
Date: Tue, 17 Jun 2003 16:41:26 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: James M Galvin <galvin+ietf@eListX.com>
Cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org,
        Paul Hoffman <phoffman@imc.org>
Subject: Re: full list for moderated list (was: CLOSE ASRG NOW IT HAS
 FAILED)
Message-ID: <415400000.1055860886@askvoll.hjemme.alvestrand.no>
In-Reply-To: <Pine.WNT.4.51.0306170903430.2732@office.elistx.com>
References: <p05210620bb13b2531d86@[63.202.92.152]>
 <200306161845.h5GIjYra017070@calcite.rhyolite.com>
 <368470000.1055840512@askvoll.hjemme.alvestrand.no>
 <Pine.WNT.4.51.0306170903430.2732@office.elistx.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, juni 17, 2003 09:26:24 -0400 James M Galvin 
<galvin+ietf@eListX.com> wrote:

>
> On Tue, 17 Jun 2003, Harald Tveit Alvestrand wrote:
>
>     > The suggestion of having two lists, one filtered and a second named
>     > whatever-noise, both with open archives, sounds fine to me, but
> wouldn't     > help the ASRG case.
>
>     the ICANN DNSO GA list operated with "ga" and "ga-full" lists
>     ("full" being all spam, crosspostings and postings from moderated
>     posters in addition to the normal list traffic).
>
>     the ga-full list was, I believe, not archived.
>
>     it served to silence the complaints that it wouldn't be possible to
>     see if moderation was fair or not, which richly repaid the work of
>     setting it up - I think it had approximately 5 memebers.
>
> The presence of the second list may have served its purpose in this case
> but I believe the mechanism is flawed.  A temporary archive is also
> required.
>
> The point should not be to require people to subscribe to the "full"
> list in order to review the actions of the moderator but rather to
> have the full list available for review should an issue arise.
>
> To require the subscription begs the question of why have two lists?
> Two lists give the *perception* of fairness and positive action but
> provide marginal (at best) support for review beyond what can be done
> when only the "moderated" list is available.  You still have to contact
> one of the members to get prior messages or depend on the "victim" to
> provide copies of messages submitted that were rejected.
>
> What is required is a full list (with or without subscribers) with an
> archive that includes everything (except viruses and obvious spam) for a
> period of time.  I happen to like 10 days but I've heard others suggest
> that it really needs to be much longer, perhaps 30, 60, or even 90 days.

In that particular instance, some people even questioned the integrity of 
the archives at the hosting site. So telling them "if you don't trust us, 
just archive this yourself, here's the feed" was actually a feature.

Now that I think of it, the list *was* archived on the server of the list, 
and the archives are even still available.... 
http://www.dnso.org/clubpublic/ga-full/Arc00/maillist.html contains the 
archive, if anyone's interested...

                Harald




From owner-ietf@ietf.org  Tue Jun 17 11:17:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21940
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 11:17:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SHpM-0007OJ-IJ
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 10:52:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SFOt-0001Sj-6O
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 08:17:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09404
	for <ietf@ietf.org>; Tue, 17 Jun 2003 08:17:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SFMf-0005Lb-00
	for ietf@ietf.org; Tue, 17 Jun 2003 08:15:05 -0400
Received: from basie.internet2.edu ([207.75.164.22])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SFMf-0005LY-00
	for ietf@ietf.org; Tue, 17 Jun 2003 08:15:05 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by basie.internet2.edu (Postfix) with ESMTP
	id 812447B4AE; Tue, 17 Jun 2003 08:17:21 -0400 (EDT)
Received: from localhost (basie.internet2.edu [207.75.164.22])
	by basie.internet2.edu (Postfix) with ESMTP
	id 87B657B493; Tue, 17 Jun 2003 08:17:20 -0400 (EDT)
Date: Tue, 17 Jun 2003 08:17:20 -0400
From: Guy T Almes <almes@internet2.edu>
To: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department
 formally adopts IPv6)
Message-ID: <146410000.1055852240@localhost>
In-Reply-To: <20030617105244.GV4610@login.ecs.soton.ac.uk>
References: <200306171025.h5HAPxJA026393@ginger.lcs.mit.edu>
 <20030617105244.GV4610@login.ecs.soton.ac.uk>
X-Mailer: Mulberry/3.0.3 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by AMaViS 0.3.12pre8
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tim,
  Exactly right.
  Increasingly, the plumbing is there.  And, particularly (but not only) 
within the worldwide university networks, it is there with good and 
increasingly good performance.  And it's there where the current university 
student population, a community famously and occasionally infamously 
receptive to new applications, can use it.
  I am very interested in seeing whether the applications folks effectively 
take up this opportunity.
  Regards,
        -- Guy

--On Tuesday, June 17, 2003 11:52:45 +0100 Tim Chown <tjc@ecs.soton.ac.uk> 
wrote:

> On Tue, Jun 17, 2003 at 06:25:59AM -0400, J. Noel Chiappa wrote:
>> I wish I could get $10 for every time I heard one of these predictions.
>> I've got a huge stack of them, dating back to the 1990's. I think the
>> one I liked the best was how G3 phones were going to be the killer app
>> for v6.
>
> Fair point.  But a year ago we didn't have Abilene, GEANT or a large
> number of European NRENs offering a native IPv6 service.  Cisco and
> Juniper's  support has come on in leaps and bounds, and now we do see US
> and European real deployment, overlaid on the production IPv4 network,
> and we see dual-stack transatlantic links.   On the coal face, we can see
> real progress.
>
> A year ago we didn't have official IPv6 support in Windows XP.  We didn't
> have prototypes from Sony and Panasonic being shown publicly.   We didn't
> have a pilot IPv6 deployment project from Microsoft (threedegrees).
> Things  are moving on.  Sure, we'll get hype from the marketing people,
> but that's  what they're paid to produce :)
>
> And noone's forcing IPv6 on anybody.  If you want to keep running IPv4,
> with or without NAT, feel free.
>
> Tim





From owner-ietf@ietf.org  Tue Jun 17 11:21:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22243
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 11:21:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SI41-0008It-Qu
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 11:08:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SHp8-0007H7-8S
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 10:52:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20603
	for <ietf@ietf.org>; Tue, 17 Jun 2003 10:52:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SHmu-0000F0-00
	for ietf@ietf.org; Tue, 17 Jun 2003 10:50:20 -0400
Received: from one.elistx.com ([209.116.252.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SHmt-0000Ex-00
	for ietf@ietf.org; Tue, 17 Jun 2003 10:50:19 -0400
Received: from localhost (one.elistx.com [209.116.252.130])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HGM00E1AS150T@eListX.com>
 for ietf@ietf.org; Tue, 17 Jun 2003 10:53:30 -0400 (EDT)
Date: Tue, 17 Jun 2003 10:53:01 -0400 (Eastern Daylight Time)
From: James M Galvin <galvin+ietf@eListX.com>
Subject: Re: full list for moderated list (was: CLOSE ASRG NOW IT HAS FAILED)
In-reply-to: <E19SHRo-000Lse-Ey@ran.psg.com>
To: Randy Bush <randy@psg.com>
Cc: ietf@ietf.org
Message-id: <Pine.WNT.4.51.0306171037520.2288@office.elistx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
References: <p05210620bb13b2531d86@[63.202.92.152]>
 <200306161845.h5GIjYra017070@calcite.rhyolite.com>
 <368470000.1055840512@askvoll.hjemme.alvestrand.no>
 <Pine.WNT.4.51.0306170903430.2732@office.elistx.com>
 <E19SHRo-000Lse-Ey@ran.psg.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


On Tue, 17 Jun 2003, Randy Bush wrote:

    a look at the paper post i receive every day would lead me to
    believe that an archive that includes unsolicited commercial post
    would be on the order of ten times as large as that for legitimate
    post.  why will the internet email be any less polluted?  and you
    want folk to archive the <bleep>?  so the search engines can have
    even more hits on the slime?  cool.

Spam and other kinds of unsolicited commercial post are a second order
problem.  The issue on the table was objective review of moderator
actions.

In any case, I did say the archive need not contain "obvious" spam.  For
me, "obvious spam" means I set a medium-high threshold for SpamAssassin
and discard it if it crosses the threshold.  Other methods will work
equally well, including doing nothing.

Search engines are not our problem.  In my experience they will figure
it out if they need to and deal with it.  "Harvesters" are a second
order problem.

This is not rocket science.  Many "second order" tweaks are possible.
Conceptually, the proposal is no different than the way local sites
would previously manage USENET newsgroups (roll off after 10, 20, or 30
days).  Yes, lots of disk, but that is cheap enough these days.  Heck, I
wouldn't even backup these particular archives.

Jim



From owner-ietf@ietf.org  Tue Jun 17 11:37:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22926
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 11:37:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SIE9-0001X3-NR
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 11:18:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SI1q-0007zp-Bv
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 11:05:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21235
	for <ietf@ietf.org>; Tue, 17 Jun 2003 11:05:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SHzc-0000PF-00
	for ietf@ietf.org; Tue, 17 Jun 2003 11:03:28 -0400
Received: from kirk.rvdp.org ([80.126.101.63])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SHzb-0000Os-00
	for ietf@ietf.org; Tue, 17 Jun 2003 11:03:27 -0400
Received: (from rvdp@localhost)
	by kirk.rvdp.org (8.11.6p2/8.11.6) id h5HF5Nm24893;
	Tue, 17 Jun 2003 17:05:23 +0200 (CEST)
Date: Tue, 17 Jun 2003 17:05:23 +0200
From: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
To: Keith Moore <moore@cs.utk.edu>
Cc: Ronald van der Pol <Ronald.vanderPol@rvdp.org>, pbaker@verisign.com,
        aarsenau@bbn.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
Message-ID: <20030617150523.GM22970@rvdp.org>
References: <2A1D4C86842EE14CA9BC80474919782E0D2238@mou1wnexm02.verisign.com> <20030616213903.695cadc1.moore@cs.utk.edu> <20030617092718.GA22843@rvdp.org> <20030617080523.0b525f59.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030617080523.0b525f59.moore@cs.utk.edu>
User-Agent: Mutt/1.4.1i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, Jun 17, 2003 at 08:05:23 -0400, Keith Moore wrote:

> I see it as a transition also.  But I think there will be a long period
> in which v6 is used mostly for new things, and only when v6 is more 
> ubiquitious than v4 will we see some of the core services migrate.

There is a big difference between planning/engineering for a transition
and planning/engineering for a coexistance. There seem to be forces
trying to steer to the latter. Seems like an important question. Why
would we want an internet with two protocols with the same functionality
running in parallel? Should that be the goal?

	rvdp



From owner-ietf@ietf.org  Tue Jun 17 11:46:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23362
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 11:46:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SIJs-0002EC-K7
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 11:24:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SI4R-00006i-Im
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 11:08:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21442
	for <ietf@ietf.org>; Tue, 17 Jun 2003 11:08:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SI2D-0000Sy-00
	for ietf@ietf.org; Tue, 17 Jun 2003 11:06:09 -0400
Received: from [131.107.8.3] (helo=exchange.microsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SI2C-0000S4-00
	for ietf@ietf.org; Tue, 17 Jun 2003 11:06:08 -0400
Received: from DF-VRS-01.redmond.corp.microsoft.com ([157.54.4.14]) by exchange.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 17 Jun 2003 08:07:51 -0700
Received: from 10.197.0.83 by DF-VRS-01.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 17 Jun 2003 08:07:51 -0700
Received: from DF-DINKY.platinum.corp.microsoft.com ([10.197.0.118]) by DF-BEG.platinum.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 17 Jun 2003 08:03:40 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Subject: RE: myth of the great transition (was US Defense Department formally adopts IPv6)
Date: Tue, 17 Jun 2003 08:03:39 -0700
Message-ID: <01C133474E27D04FABA48D02078CF41D014D1AA7@DF-DINKY.platinum.corp.microsoft.com>
Thread-Topic: myth of the great transition (was US Defense Department formally adopts IPv6)
Thread-Index: AcM0c7bgvzOo4SkPRKStzzW8cNkk4gAaWqwd
From: "Peter Ford" <peterf@exchange.microsoft.com>
To: "Keith Moore" <moore@cs.utk.edu>, <ietf@ietf.org>
X-OriginalArrivalTime: 17 Jun 2003 15:03:40.0908 (UTC) FILETIME=[A3557AC0:01C334E1]
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C334E1.A2C504DD"

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

=20
If you think of IPv6 as an end to end technology that can gracefully =
ride on top of the global IPv4 ISP provided infrastructure, you don't =
have to have the "Internet Infrastructure" transition to IPv6 for a =
long, long time. =20
=20
Peer to Peer applications are going to be sufficient to get people to =
upgrade their "NAT infrastructures" to support IPv6 over IPv4 tunneling. =
 This is all aided by the plummeting cost of NAT replacement (e.g. < =
$50, which is a lot cheaper than the early Internet upgrade days of =
modem replacement for v.34, v.90, cable modem, etc.).    Thus, the =
tunnel phase of IPv6 is quite viable, and has the FEATURE that you don't =
need massive shifts/upgrades in public Internet infrastructure.   This =
is relatively simple to promote to end users as well: your old and new =
can work together  ...  ( I have observed: not too many end users are =
into the "management" of their networks.)
=20
IPv6 only networks can be created to support closed IPv6-only device =
networks such as the cell phone networks.  Thus, HUGE networks with =
application relays/proxies between ipv6 and ipv4 infrastructures will be =
created where global interop is essential, such as email, web browsing, =
etc.  The incentives to the cell phone operators are obvious.  One might =
also observe: the cell phone operators and their suppliers are not keen =
on building open host platforms for deployment of arbitrary applications =
and protocols.  This will turn out to be a feature for IPv6 deployment.  =
Thus, a new breed of ISPs will drive IPv6 deployment in ISP space.
=20
Enterprises will be last to go.  Why?  Because in fact they run =
relatively small networks, and the core value of IPv6 is large =
addressability.   The extent to which better security is available for =
IPv6 may be a sufficient draw for many companies, but not all.  Thus, =
the current "revenue champion" for networking will not be the early =
revenue driver for IPv6 as we have seen for routers and ethernet =
switches.  Since enterprise also drives a huge amount of ISP =
deployments, I would not expect the current ISPs to be the first to =
transition to, or augment with, IPv6.
=20
The transition will occur based on technologies and deployments as  =
discussed and planned in the IETF oh so long ago.   Much like it took =
the world many, many years to realize the value of transitioning to IPv4 =
in the first place, transition to a new infrastructure protocol is going =
to take a long time.   IPv6 was created for a world with tons and tons =
of hosts and devices.  That time is almost here, so it is only now that =
IPv6 deployment is going to be economically relevant and viable.  =
Pushing in front of this time horizon is good for getting the deployment =
issues worked out, but people can't expect that just because the =
technology is good to go, that it will just go.
=20
regards,
=20
peterf
=20
P.S.   The IETF might want to spend more time working on topics germane =
to the cell phone industry. Not that IPv6 hasn't taken a lot of time ... =
:-)
=20
=20
=20
=20
=20

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

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">=0A=
<HTML>=0A=
<HEAD>=0A=
=0A=
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.6944.0">=0A=
<TITLE>myth of the great transition (was US Defense Department formally =
adopts IPv6)</TITLE>=0A=
</HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText254 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>If you think of IPv6 as an =
end to end =0A=
technology that can gracefully ride on top of the global IPv4 ISP =
provided =0A=
infrastructure, you don't have to have the "Internet Infrastructure" =
transition =0A=
to IPv6 for a long, long time.&nbsp;&nbsp;</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Peer to Peer applications are =
going to be =0A=
sufficient to get people to upgrade their "NAT infrastructures" to =
support IPv6 =0A=
over IPv4 tunneling.&nbsp; This is all aided by the plummeting cost of =
NAT =0A=
replacement (e.g. &lt; $50, which is a lot cheaper than the early =
Internet =0A=
upgrade days of modem replacement for v.34, v.90, cable modem, =0A=
etc.).&nbsp;&nbsp;&nbsp; Thus, the tunnel phase of IPv6 is quite viable, =
and has =0A=
the FEATURE that you don't need massive shifts/upgrades in public =
Internet =0A=
infrastructure.&nbsp;&nbsp; This is relatively simple to promote to end =
users as =0A=
well: your old and new can work together&nbsp; ...&nbsp; ( I have =
observed: not =0A=
too many end users are into the "management" of their =
networks.)</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>IPv6 only networks can be =
created to =0A=
support closed IPv6-only device networks such as the cell phone =
networks.&nbsp; =0A=
Thus, HUGE networks with application relays/proxies between ipv6 and =
ipv4 =0A=
infrastructures will be created where global interop is essential, such =
as =0A=
email, web browsing, etc.&nbsp; The incentives to the cell phone =0A=
operators&nbsp;are obvious.&nbsp;&nbsp;One might also observe: the cell =
phone =0A=
operators and their suppliers are not keen on building open host =
platforms for =0A=
deployment of arbitrary applications and protocols.&nbsp; This will turn =
out to =0A=
be a feature for IPv6 deployment.&nbsp; Thus, a new breed of ISPs will =
drive =0A=
IPv6 deployment in ISP space.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Enterprises will be last to =
go.&nbsp; =0A=
Why?&nbsp; Because in fact they run relatively small networks, and the =
core =0A=
value of IPv6 is large addressability.&nbsp;&nbsp; The extent to which =
better =0A=
security is available for IPv6 may be a sufficient draw for many =
companies, but =0A=
not all.&nbsp; Thus, the current "revenue champion" for networking will =
not be =0A=
the early revenue driver for IPv6 as we have seen for routers and =
ethernet =0A=
switches.&nbsp; Since enterprise also drives a huge amount of ISP =
deployments, I =0A=
would not expect the current ISPs to be the first to transition to, or =
augment =0A=
with,&nbsp;IPv6.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>The transition =
will&nbsp;occur based on =0A=
technologies and deployments&nbsp;as&nbsp; discussed and planned in the =
IETF oh =0A=
so long ago.&nbsp;&nbsp; Much like it took the world many, many years to =
realize =0A=
the value of transitioning to IPv4 in the first place, transition to a =
new =0A=
infrastructure protocol is going to take a long time.&nbsp;&nbsp; IPv6 =
was =0A=
created for a world with tons and tons of hosts and devices.&nbsp; That =
time is =0A=
almost here, so it is only now that IPv6 deployment is going to be =
economically =0A=
relevant and viable.&nbsp; Pushing in front of this time horizon is good =
for =0A=
getting the deployment issues worked out, but people can't expect that =
just =0A=
because the technology is good to go, that it will just go.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>regards,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>peterf</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>P.S.&nbsp;&nbsp; The IETF =
might want to =0A=
spend more time working on topics germane to&nbsp;the cell phone =
industry. Not =0A=
that IPv6 hasn't taken a lot of time ... :-)</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV>=0A=
=0A=
</BODY>=0A=
</HTML>
------_=_NextPart_001_01C334E1.A2C504DD--

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




From owner-ietf@ietf.org  Tue Jun 17 11:58:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24096
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 11:58:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SIJu-0002Jn-IT
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 11:24:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SIDU-0001Go-By
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 11:17:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22031
	for <ietf@ietf.org>; Tue, 17 Jun 2003 11:17:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SIBG-0000cP-00
	for ietf@ietf.org; Tue, 17 Jun 2003 11:15:30 -0400
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SIBF-0000ah-00
	for ietf@ietf.org; Tue, 17 Jun 2003 11:15:29 -0400
Received: from INET-VRS-03.redmond.corp.microsoft.com ([157.54.5.27]) by mail3.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Tue, 17 Jun 2003 08:17:14 -0700
Received: from 157.54.8.23 by INET-VRS-03.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 17 Jun 2003 08:17:13 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 17 Jun 2003 08:17:13 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 17 Jun 2003 08:17:12 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.82]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3788.0);
	 Tue, 17 Jun 2003 08:17:12 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6940.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: myth of the great transition (was US Defense Department formally adopts IPv6)
Date: Tue, 17 Jun 2003 08:17:11 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA03C40488@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: myth of the great transition (was US Defense Department formally adopts IPv6)
Thread-Index: AcM03/f8sEpssfJfT7aNncn1Ktsq5AAAiEfg
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Bill Manning" <bmanning@ISI.EDU>
Cc: <ietf@ietf.org>
X-OriginalArrivalTime: 17 Jun 2003 15:17:12.0528 (UTC) FILETIME=[8718DD00:01C334E3]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA24096

> % > If you want to keep running IPv4, with or without NAT,
> % > feel free.
> %
> % That's exactly what people will do, until and unless they encounter
a
> % problem with IPv4 that can only be solved by IPv6.
> 
> 	Your sweeping generalization does not ring true.
> 
> 	However with a willing suspension of disbelief, this
> 	might be why the DoD has decided to adopt IPv6.
> 	It wants to do things that can't be done w/ IPv4.
> 	And the IETF should be excited that someone is actually
> 	considering adopting an IETF work product.

It's amusing how a relatively minor DoD pronouncement can generate so
much argument on the IETF list. What the DoD announcement boils down to
is a requirement that new products bought by the DoS be IPv6 capable.
Guess what? Most of the products bought by the DoD today are already
IPv6 capable. In fact, it is probably that very observation that caused
the DoD to issue such requirement with confidence. This is not really a
watershed event, but it is also definitely a push for IPv6 deployment --
after all, the DoD is not putting a press release saying that it will
wait another 10 years before considering IPv6.

Now, I certainly share a lot of the concerns that were expressed by Noel
and others. Those who rely on governments for pushing a technology have
seldom been rewarded with success. I remember the time when we could not
get a European research funded unless it mentioned ATM... 

IPv6 will be deployed if it solves at least some of the current problems
with IPv4, and if applications get written that take advantage of the
way IPv6 solves these problems. I personally believe so, and I am busy
enabling application writers doing that. We shall see...

-- Christian Huitema




From owner-ietf@ietf.org  Tue Jun 17 12:00:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24323
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 12:00:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SInm-00057y-Er
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 11:55:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SIYY-0003q0-RJ
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 11:39:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23111
	for <ietf@ietf.org>; Tue, 17 Jun 2003 11:39:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SIWL-0000v2-00
	for ietf@ietf.org; Tue, 17 Jun 2003 11:37:17 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SIWG-0000uv-00
	for ietf@ietf.org; Tue, 17 Jun 2003 11:37:13 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5HFdH6g019626
	for ietf@ietf.org env-from <vjs>;
	Tue, 17 Jun 2003 09:39:17 -0600 (MDT)
Date: Tue, 17 Jun 2003 09:39:17 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306171539.h5HFdH6g019626@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: full list for moderated list 
References:  <415400000.1055860886@askvoll.hjemme.alvestrand.no>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Harald Tveit Alvestrand <harald@alvestrand.no>

> ...
> In that particular instance, some people even questioned the integrity of 
> the archives at the hosting site. So telling them "if you don't trust us, 
> just archive this yourself, here's the feed" was actually a feature.
> ...

Agreed, but the interesting purposes can only involve convincing
reasonable people.  Giving a kook a feed won't convince it of anything
except that the feed is fake.  The goal should be to support quiet
inquiries by third parties, without forcing them to file IESG equivalents
of freedom of information act paperwork.  What the kooks, spammers,
and others subject to moderation think or say is entirely uninteresting.

As for giving more search engine hits to spammers--I've found Google's
pointers to spammers' work in IETF lists useful.  Such pointers tend
to shut up "cartooneys."


I've not noticed any real opposition to at least open archiving of
moderation rejections.  Is there anything that needs to be done to
make this an official recommendation, IESG policy, or whatever?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Tue Jun 17 12:11:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24936
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 12:11:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SIqF-0005Ol-V1
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 11:57:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SIkj-0004Ve-DL
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 11:52:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23680
	for <ietf@ietf.org>; Tue, 17 Jun 2003 11:52:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SIiV-00014C-00
	for ietf@ietf.org; Tue, 17 Jun 2003 11:49:51 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SIiU-000149-00
	for ietf@ietf.org; Tue, 17 Jun 2003 11:49:50 -0400
Received: from MOU1WNEXC03.verisign.com (verisign.com [65.205.251.57])
        by peacock.verisign.com (8.12.9/) with ESMTP id h5HFpvh6001778;
        Tue, 17 Jun 2003 08:51:58 -0700 (PDT)
Received: by mou1wnexc03.verisign.com with Internet Mail Service (5.5.2653.19)
	id <MLJJ413X>; Tue, 17 Jun 2003 08:51:57 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D223F@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Ronald van der Pol'" <Ronald.vanderPol@rvdp.org>,
        "'Keith Moore'"
	 <moore@cs.utk.edu>
Cc: "'Ronald van der Pol'" <Ronald.vanderPol@rvdp.org>,
        "'aarsenau@bbn.com'"
	 <aarsenau@bbn.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: myth of the great transition (was US Defense Department forma
	lly adopts IPv6)
Date: Tue, 17 Jun 2003 08:51:57 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

I think a transition is possible but only if people stop sitting arround
waiting for it to happen.

The key in my view is to work on the NAT vendors, instead of viewing NAT
boxes as an obstacle they should be seen for what they really are, an
essential and important part of the internet infrastructure.

Simply repeating the end to end dogma is not going to provide a solution.
The internet people are using is not end to end. NAT boxes and firewalls
play an important and necessary security role.

We need a standard for a superNAT box that provides both security and
protocol bridging functions. 

There is no reason this transition cannot be made seamless from the enduser
pint of view. 

Phill




 -----Original Message-----
From: 	Ronald van der Pol
Sent:	Tue Jun 17 08:05:32 2003
To:	Keith Moore
Cc:	Ronald van der Pol; pbaker@verisign.com; aarsenau@bbn.com;
ietf@ietf.org
Subject:	Re: myth of the great transition (was US Defense Department
formally adopts IPv6)

On Tue, Jun 17, 2003 at 08:05:23 -0400, Keith Moore wrote:

> I see it as a transition also.  But I think there will be a long period
> in which v6 is used mostly for new things, and only when v6 is more 
> ubiquitious than v4 will we see some of the core services migrate.

There is a big difference between planning/engineering for a transition
and planning/engineering for a coexistance. There seem to be forces
trying to steer to the latter. Seems like an important question. Why
would we want an internet with two protocols with the same functionality
running in parallel? Should that be the goal?

	rvdp



From owner-ietf@ietf.org  Tue Jun 17 12:38:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25718
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 12:38:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SJJO-0007OB-KX
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 12:27:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SJDS-0007Cy-0y
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 12:21:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25264
	for <ietf@ietf.org>; Tue, 17 Jun 2003 12:21:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SJBE-0001To-00
	for ietf@ietf.org; Tue, 17 Jun 2003 12:19:32 -0400
Received: from tnt.isi.edu ([128.9.128.128])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SJBD-0001Tl-00
	for ietf@ietf.org; Tue, 17 Jun 2003 12:19:31 -0400
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6p2/8.11.2) with ESMTP id h5HGLli12400;
	Tue, 17 Jun 2003 09:21:47 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.9.3/8.8.6) id JAA15141;
	Tue, 17 Jun 2003 09:17:21 -0700 (PDT)
Date: Tue, 17 Jun 2003 09:17:21 -0700 (PDT)
Message-Id: <200306171617.JAA15141@gra.isi.edu>
To: pekkas@netcore.fi, sbwoodside@yahoo.com
Subject: Re: SIRs
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


  *> 
  *> Create a document-based thread rather than a WG-based or 
  *> mailing-list-based thread. Patches could also be posted and revision 
  *> history (changes between revisions) would be easier to keep track of. 
  *> People who have negative comments could post them, and they'd be part 
  *> of the history record of the draft even if their comments are 
  *> ignored/rejected.
  *> 
  *> simon
  *> 
  *> 

I really wonder whether people have thought through the can of
worms (Pandora's box) that you people may be opening...?  This is not
to deny the need to improve the quality of some I-Ds and RFCs,
goodness knows, but be careful of social consequences...

Bob Braden



From owner-ietf@ietf.org  Tue Jun 17 13:13:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26763
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 13:13:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SJsS-0000Ga-Mm
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 13:04:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SJhs-0008Sl-S1
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 12:53:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26109
	for <ietf@ietf.org>; Tue, 17 Jun 2003 12:53:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SJfe-0001i8-00
	for ietf@ietf.org; Tue, 17 Jun 2003 12:50:59 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SJfe-0001hv-00
	for ietf@ietf.org; Tue, 17 Jun 2003 12:50:58 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h5HGtLF07101;
	Tue, 17 Jun 2003 09:55:21 -0700
Date: Tue, 17 Jun 2003 09:52:03 -0700
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/10) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <11537728160.20030617095203@brandenburg.com>
To: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
CC: Keith Moore <moore@cs.utk.edu>, pbaker@verisign.com, aarsenau@bbn.com,
        ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
In-Reply-To: <20030617150523.GM22970@rvdp.org>
References: <2A1D4C86842EE14CA9BC80474919782E0D2238@mou1wnexm02.verisign.com>
 <20030616213903.695cadc1.moore@cs.utk.edu> <20030617092718.GA22843@rvdp.org>
 <20030617080523.0b525f59.moore@cs.utk.edu> <20030617150523.GM22970@rvdp.org>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ronald,

RvdP> There is a big difference between planning/engineering for a transition
RvdP> and planning/engineering for a coexistance. There seem to be forces
RvdP> trying to steer to the latter. Seems like an important question. Why
RvdP> would we want an internet with two protocols with the same functionality
RvdP> running in parallel? Should that be the goal?


It is not possible to have a flag-day event for switching to a
replacement service.

Hence, there must be a transition that takes some time.

Remember that this involves thousands of independent administrations and
many tens of millions of systems

Any detailed consideration of the mechanics and time-frame required of
such a transition -- and, yes, I said required; not desirable, not
likely, but required -- you will discover that those details look
exactly like "coexistence".


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




From owner-ietf@ietf.org  Tue Jun 17 13:21:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27159
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 13:21:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SJtW-0000HY-Is
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 13:05:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SJmY-0008WL-VG
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 12:58:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26209
	for <ietf@ietf.org>; Tue, 17 Jun 2003 12:58:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SJkK-0001j8-00
	for ietf@ietf.org; Tue, 17 Jun 2003 12:55:48 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SJkH-0001j5-00
	for ietf@ietf.org; Tue, 17 Jun 2003 12:55:45 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h5HGvpo01679;
	Tue, 17 Jun 2003 09:57:51 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200306171657.h5HGvpo01679@boreas.isi.edu>
Subject: Re: SIRs
In-Reply-To: <200306171617.JAA15141@gra.isi.edu> from Bob Braden at "Jun 17, 3 09:17:21 am"
To: braden@ISI.EDU (Bob Braden)
Date: Tue, 17 Jun 2003 09:57:51 -0700 (PDT)
Cc: pekkas@netcore.fi, sbwoodside@yahoo.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
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

% 
%   *> 
%   *> Create a document-based thread rather than a WG-based or 
%   *> mailing-list-based thread. Patches could also be posted and revision 
%   *> history (changes between revisions) would be easier to keep track of. 
%   *> People who have negative comments could post them, and they'd be part 
%   *> of the history record of the draft even if their comments are 
%   *> ignored/rejected.
%   *> 
%   *> simon
%   *> 
%   *> 
% 
% I really wonder whether people have thought through the can of
% worms (Pandora's box) that you people may be opening...?  This is not
% to deny the need to improve the quality of some I-Ds and RFCs,
% goodness knows, but be careful of social consequences...
% 
% Bob Braden
% 

amen.
http://www.interesting-people.org/archives/interesting-people/200306/msg00096.html


--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  Tue Jun 17 14:20:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00504
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 14:20:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SKv4-00032q-UX
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 14:10:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SKkS-0002eW-HF
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 14:00:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28614
	for <ietf@ietf.org>; Tue, 17 Jun 2003 13:59:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SKiE-0002K4-00
	for ietf@ietf.org; Tue, 17 Jun 2003 13:57:42 -0400
Received: from spitfire.law.miami.edu ([129.171.187.10] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SKiD-0002K1-00
	for ietf@ietf.org; Tue, 17 Jun 2003 13:57:41 -0400
Received: from spitfire.law.miami.edu (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id CE8665C3AC1; Tue, 17 Jun 2003 13:59:57 -0400 (EDT)
Received: by spitfire.law.miami.edu (Postfix, from userid 1113)
	id 85DE95C3AC1; Tue, 17 Jun 2003 13:59:57 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id 8192B5D3A6E; Tue, 17 Jun 2003 13:59:57 -0400 (EDT)
Date: Tue, 17 Jun 2003 13:59:57 -0400 (EDT)
From: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
To: David Morris <dwm@xpasc.com>
Cc: Dean Anderson <dean@av8.com>, Paul Hoffman / IMC <phoffman@imc.org>,
        ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
In-Reply-To: <Pine.LNX.4.33.0306161557040.18994-100000@egate.xpasc.com>
Message-ID: <Pine.LNX.4.10.10306171358580.26019-100000@spitfire.law.miami.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

I submit that it's better than the alternative of no archive at all.  If
you can think of solution that is likely to be implemented and has fewer
faults, I'm all for it.

On Mon, 16 Jun 2003, David Morris wrote:

> 
> 
> On Mon, 16 Jun 2003, Michael Froomkin - U.Miami School of Law wrote:
> 
> > My understanding is that The Mail Archive
> > (http://www.mail-archive.com/lists.html)  will provide free storage for
> > mailing lists.  I think every WG list should be permanetly archived in
> > this manner.
> 
> What a great way to help address harvesters ... one site ... one 'API' to
> program against to harvest many valid addresses. This particular archive
> example hides email addresses, but it took me less that 5 minutes to
> determine how to recover addresses from the page data.
> 
> So I don't think the suggested policy is a good idea without much more
> effective blocking of access to email addresses.
> 
> Dave Morris
> 
> 

-- 
		Please visit http://www.icannwatch.org
A. Michael Froomkin   |    Professor of Law    |   froomkin@law.tm
U. Miami School of Law, P.O. Box 248087, Coral Gables, FL 33124 USA
+1 (305) 284-4285  |  +1 (305) 284-6506 (fax)  |  http://www.law.tm
                        -->It's hot here.<--




From owner-ietf@ietf.org  Tue Jun 17 14:26:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00898
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 14:26:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SKv5-000353-IS
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 14:10:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SKpH-0002ib-3I
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 14:04:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28958
	for <ietf@ietf.org>; Tue, 17 Jun 2003 14:04:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SKn3-0002Pk-00
	for ietf@ietf.org; Tue, 17 Jun 2003 14:02:41 -0400
Received: from spitfire.law.miami.edu ([129.171.187.10] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SKn2-0002Ph-00
	for ietf@ietf.org; Tue, 17 Jun 2003 14:02:40 -0400
Received: from spitfire.law.miami.edu (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id 5F37E5C3AC1; Tue, 17 Jun 2003 14:04:57 -0400 (EDT)
Received: by spitfire.law.miami.edu (Postfix, from userid 1113)
	id E135A5C3AC1; Tue, 17 Jun 2003 14:04:56 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id DCA425D3A6E; Tue, 17 Jun 2003 14:04:56 -0400 (EDT)
Date: Tue, 17 Jun 2003 14:04:56 -0400 (EDT)
From: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org,
        phoffman@imc.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED
In-Reply-To: <368470000.1055840512@askvoll.hjemme.alvestrand.no>
Message-ID: <Pine.LNX.4.10.10306171402330.26019-100000@spitfire.law.miami.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

I was one of the ga-full subscribers.  I thought it was a great mistake
not to archive it -- further institutionalizing the idea that only
approved persons could speak, and creating a santized public record.  The
calculus was different for ICANN, as it's quasi-governmental in a way the
IETF is not, so what was necessary there might not be necessary here.

I sould also note that ICANN killed the ga-full list with no discussion
and essentially no notice.

The ga-full list, as used by ICANN, certainly served to silence people,
but not quite exactly in the manner described below.

On Tue, 17 Jun 2003, Harald Tveit Alvestrand wrote:

> 
> 
> --On mandag, juni 16, 2003 12:45:34 -0600 Vernon Schryver 
> <vjs@calcite.rhyolite.com> wrote:
> 
> > The suggestion of having two lists, one filtered and a second named
> > whatever-noise, both with open archives, sounds fine to me, but wouldn't
> > help the ASRG case.  I think that the ASRG case would be instantly
> > resolved if the moderator would publish all of the rejected messages
> > and related corresponce without any additional commentary...not that
> > I think there's any case there, but passers-by might not have seen the
> > first several weeks of traffic in the ASRG mailing list not to mention
> > those "courtesy" copies I mentioned.
> 
> the ICANN DNSO GA list operated with "ga" and "ga-full" lists ("full" being 
> all spam, crosspostings and postings from moderated posters in addition to 
> the normal list traffic).
> 
> the ga-full list was, I believe, not archived.
> 
> it served to silence the complaints that it wouldn't be possible to see if 
> moderation was fair or not, which richly repaid the work of setting it up - 
> I think it had approximately 5 memebers.
> 
>                Harald
> 
> 
> 

-- 
		Please visit http://www.icannwatch.org
A. Michael Froomkin   |    Professor of Law    |   froomkin@law.tm
U. Miami School of Law, P.O. Box 248087, Coral Gables, FL 33124 USA
+1 (305) 284-4285  |  +1 (305) 284-6506 (fax)  |  http://www.law.tm
                        -->It's hot here.<--




From owner-ietf@ietf.org  Tue Jun 17 14:26:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00955
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 14:26:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SKwr-0003Ep-Ml
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 14:12:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SKu3-0002z1-5J
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 14:09:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29232
	for <ietf@ietf.org>; Tue, 17 Jun 2003 14:09:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SKrp-0002Vv-00
	for ietf@ietf.org; Tue, 17 Jun 2003 14:07:37 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SKro-0002VE-00
	for ietf@ietf.org; Tue, 17 Jun 2003 14:07:36 -0400
Subject: RE: myth of the great transition (was US Defense Department formally adopts IPv6)
Date: Tue, 17 Jun 2003 11:09:55 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F89C@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: myth of the great transition (was US Defense Department formally adopts IPv6)
Thread-Index: AcM060Wfwwi8oHg4SZidIPfZArWUwwAD01Iw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA00955

Phill,

> Hallam-Baker, Phillip
> Simply repeating the end to end dogma is not going to provide
> a solution. The internet people are using is not end to end.
> NAT boxes and firewalls play an important and necessary
> security role. We need a standard for a superNAT box that
> provides both security and protocol bridging functions.

This is a politically courageous post but I'm afraid that the end-to-end
dogma _is_ the IETF. WRT IPv6, the pragmatic point of view of doing
something along the lines of what you proposed is that it will raise so
much opposition that it will go nowhere, so why bother in the first
place?

Michel.




From owner-ietf@ietf.org  Tue Jun 17 15:02:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03216
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 15:02:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SLcp-0005u3-Hy
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 14:56:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SLW7-0005iB-Pm
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 14:49:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02479
	for <ietf@ietf.org>; Tue, 17 Jun 2003 14:49:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SLTt-0003CC-00
	for ietf@ietf.org; Tue, 17 Jun 2003 14:46:57 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SLTs-0003C9-00
	for ietf@ietf.org; Tue, 17 Jun 2003 14:46:57 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h5HIo8xS093989;
	Tue, 17 Jun 2003 20:50:08 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Tue, 17 Jun 2003 20:49:10 +0200
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <20030617150523.GM22970@rvdp.org>
Message-Id: <61AC0EDA-A0F4-11D7-82AB-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On dinsdag, jun 17, 2003, at 17:05 Europe/Amsterdam, Ronald van der Pol 
wrote:

> There is a big difference between planning/engineering for a transition
> and planning/engineering for a coexistance. There seem to be forces
> trying to steer to the latter. Seems like an important question. Why
> would we want an internet with two protocols with the same 
> functionality
> running in parallel? Should that be the goal?

I'm sure there are people who are sabotaging v6 in a subtle way by 
encouraging dual stack: after all, if everyone still runs IPv4 in 
addition to IPv6, _they_ can continue to run v4-only. Other than that I 
think the implied assumption is that people will drop v4 at some point 
in the (distant) future.

For any particular application and group of users, and in order to 
switch over seamlessly, it is necessary that all servers become dual 
stack, then clients can switch (without the need to run dual stack) and 
after that the servers can drop IPv4. The problem here is that for 
client-server applications such as the web and email, IPv4 isn't an 
issue because the relative number of servers is tiny and clients can 
use NAT without problems. And for peer-to-peer, _everyone_ is a server 
so _everyone_ has to run dual stack before it's possible to drop IPv4.

Good thing switching to IPv6 is so easy, or it would never happen.




From owner-ietf@ietf.org  Tue Jun 17 17:09:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11762
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 17:09:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SNXB-0005iv-D7
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 16:58:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SNW6-0005ap-N7
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 16:57:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11174
	for <ietf@ietf.org>; Tue, 17 Jun 2003 16:57:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SNTs-00053B-00
	for ietf@ietf.org; Tue, 17 Jun 2003 16:55:04 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SNTr-000538-00
	for ietf@ietf.org; Tue, 17 Jun 2003 16:55:03 -0400
Received: from mou1wnexc02.verisign.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.9/) with ESMTP id h5HKvHh6016010;
        Tue, 17 Jun 2003 13:57:17 -0700 (PDT)
Received: by mou1wnexc02.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LYL95ZCS>; Tue, 17 Jun 2003 13:57:17 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D2241@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Michel Py'" <michel@arneill-py.sacramento.ca.us>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: ietf@ietf.org
Subject: RE: myth of the great transition (was US Defense Department forma
	lly adopts IPv6)
Date: Tue, 17 Jun 2003 13:57:08 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Michel,

	Yep, I am aware that there are some folk wedged. However I believe
that there are also folk who are not wedged and I want to reach them and
their managers.

	There are other standards bodies where work can take place. Clearly
there is a certain advantage to that particular piece of work taking place
in the IETF. However as Tim Berners-Lee told me the key to getting anywhere
in IETF is to have a credible threat of succession.

	In the past three years I have worked on three specs, one is an
OASIS standard, one has just completed W3C last call, the third just started
interop testing. None of the committees took more than eighteen months. All
the specs are being actively deployed by real users and real companies.

	I don't think it is necessary for the IETF to compromise its
principles to be effective. Open and inclusive is not incompatible with
Roberts Rules of Order.

	As with spam, I would very much like the IETF to be a part of the
solution. What I will not allow is for IETF inertia and cliques to become a
part of the problem.  


		Phill

> -----Original Message-----
> From: Michel Py [mailto:michel@arneill-py.sacramento.ca.us]
> Sent: Tuesday, June 17, 2003 2:10 PM
> To: Hallam-Baker, Phillip
> Cc: ietf@ietf.org
> Subject: RE: myth of the great transition (was US Defense Department
> formally adopts IPv6)
> 
> 
> Phill,
> 
> > Hallam-Baker, Phillip
> > Simply repeating the end to end dogma is not going to provide
> > a solution. The internet people are using is not end to end.
> > NAT boxes and firewalls play an important and necessary
> > security role. We need a standard for a superNAT box that
> > provides both security and protocol bridging functions.
> 
> This is a politically courageous post but I'm afraid that the 
> end-to-end
> dogma _is_ the IETF. WRT IPv6, the pragmatic point of view of doing
> something along the lines of what you proposed is that it 
> will raise so
> much opposition that it will go nowhere, so why bother in the first
> place?
> 
> Michel.
> 



From owner-ietf@ietf.org  Tue Jun 17 21:44:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18330
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 21:44:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SRs1-0005z2-H3
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 21:36:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SRlY-0005hI-LC
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 21:29:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18129
	for <ietf@ietf.org>; Tue, 17 Jun 2003 21:29:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SRjJ-0006Q5-00
	for ietf@ietf.org; Tue, 17 Jun 2003 21:27:17 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SRjJ-0006Pz-00
	for ietf@ietf.org; Tue, 17 Jun 2003 21:27:17 -0400
Received: from MOU1WNEXC03.verisign.com (verisign.com [65.205.251.57])
        by peacock.verisign.com (8.12.9/) with ESMTP id h5I1TXh6007246
        for <ietf@ietf.org>; Tue, 17 Jun 2003 18:29:33 -0700 (PDT)
Received: by mou1wnexc03.verisign.com with Internet Mail Service (5.5.2653.19)
	id <MLJJ4VVP>; Tue, 17 Jun 2003 18:29:33 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D224A@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: full list for moderated list
Date: Tue, 17 Jun 2003 18:29:31 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

>I've not noticed any real opposition to at least open archiving of
>moderation rejections.  Is there anything that needs to be done to
>make this an official recommendation, IESG policy, or whatever?

I think we are talking about very different issues here. 

We are not talking about moderation for spam or immoderate language.
We are talking about moderation to supress criticism, in the first
instance of particular spam control approaches but subsequently of
criticism of the chair's own activities both on and off list.

Ironically it was my criticism of Vernon's DCC scheme that led to
the chair's censorship. In particular I am very concerned that DCC
has the same weaknesses as blacklists in that they can be co-opted 
as censorship mechanisms. Cindy Cohen of the EFF has described cases
where groups have run organized campaigns to get opposing groups 
such as moveon.org blacklisted by first subscribing to the list then
making a complaint.

Unfortunately many people are weasels and it is very difficult to 
stop weaselish activities. The slashdot approach may be best in this 
respect, moderation is frequently malicious but it is difficult to 
organize campaigns because nobody chooses to be a moderator.

So here we have kind of a recursive/self-referential situation.

	Phill



From owner-ietf@ietf.org  Tue Jun 17 21:55:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18717
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 21:55:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SS39-0006eW-Di
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 21:47:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SS2u-0006Wu-T3
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 21:47:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18579
	for <ietf@ietf.org>; Tue, 17 Jun 2003 21:47:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SS0g-0006X8-00
	for ietf@ietf.org; Tue, 17 Jun 2003 21:45:14 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SS0f-0006X5-00
	for ietf@ietf.org; Tue, 17 Jun 2003 21:45:13 -0400
Received: from localhost (localhost [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 63B6E1402E; Tue, 17 Jun 2003 21:47:31 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 13888-08; Tue, 17 Jun 2003 21:47:31 -0400 (EDT)
Received: from cs.utk.edu (unknown [68.24.3.213])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 7EBDE1404B; Tue, 17 Jun 2003 21:47:21 -0400 (EDT)
Date: Tue, 17 Jun 2003 21:47:18 -0400
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Keith Moore <moore@cs.utk.edu>, pbaker@verisign.com, aarsenau@bbn.com,
        ietf@ietf.org
To: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
From: Keith Moore <moore@cs.utk.edu>
In-Reply-To: <20030617150523.GM22970@rvdp.org>
Message-Id: <CBABB1BE-A12E-11D7-8A11-000393DB5366@cs.utk.edu>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Tuesday, June 17, 2003, at 11:05  AM, Ronald van der Pol wrote:

> Why
> would we want an internet with two protocols with the same 
> functionality
> running in parallel?

they don't have the same functionality.




From owner-ietf@ietf.org  Tue Jun 17 22:05:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19036
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 22:05:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SSCq-00079v-0B
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 21:57:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SS56-0006ef-4R
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 21:49:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18631
	for <ietf@ietf.org>; Tue, 17 Jun 2003 21:49:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SS2r-0006YB-00
	for ietf@ietf.org; Tue, 17 Jun 2003 21:47:29 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SS2r-0006Y8-00
	for ietf@ietf.org; Tue, 17 Jun 2003 21:47:29 -0400
Received: from localhost (localhost [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id D50891402E; Tue, 17 Jun 2003 21:49:46 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 13888-10; Tue, 17 Jun 2003 21:49:46 -0400 (EDT)
Received: from cs.utk.edu (unknown [68.24.3.213])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 0E51A14028; Tue, 17 Jun 2003 21:49:34 -0400 (EDT)
Date: Tue, 17 Jun 2003 21:49:24 -0400
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Keith Moore <moore@cs.utk.edu>,
        "'Ronald van der Pol'" <Ronald.vanderPol@rvdp.org>,
        "'aarsenau@bbn.com'" <aarsenau@bbn.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Keith Moore <moore@cs.utk.edu>
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D223F@mou1wnexm02.verisign.com>
Message-Id: <167CA66B-A12F-11D7-8A11-000393DB5366@cs.utk.edu>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Tuesday, June 17, 2003, at 11:51  AM, Hallam-Baker, Phillip wrote:

> The key in my view is to work on the NAT vendors, instead of viewing 
> NAT
> boxes as an obstacle they should be seen for what they really are, an
> essential and important part of the internet infrastructure.

you obviously don't write applications.





From owner-ietf@ietf.org  Tue Jun 17 22:36:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19758
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 22:36:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SSfq-0008Ks-Bb
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 22:27:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SScv-0008Bw-Og
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 22:24:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19559
	for <ietf@ietf.org>; Tue, 17 Jun 2003 22:24:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SSag-0006mO-00
	for ietf@ietf.org; Tue, 17 Jun 2003 22:22:26 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SSaf-0006mL-00
	for ietf@ietf.org; Tue, 17 Jun 2003 22:22:26 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5I2Ogir019195
	for ietf@ietf.org env-from <vjs>;
	Tue, 17 Jun 2003 20:24:42 -0600 (MDT)
Date: Tue, 17 Jun 2003 20:24:42 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306180224.h5I2Ogir019195@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: full list for moderated list
References:  <2A1D4C86842EE14CA9BC80474919782E0D224A@mou1wnexm02.verisign.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "Hallam-Baker, Phillip" <pbaker@verisign.com>

> ...
> We are not talking about moderation for spam or immoderate language.
> We are talking about moderation to supress criticism, in the first
> instance of particular spam control approaches but subsequently of
> criticism of the chair's own activities both on and off list.
>
> Ironically it was my criticism of Vernon's DCC scheme that led to
> the chair's censorship. 

I think Phillip Hallam-Baker knows that statement is inaccurate
and that technical criticisms of the DCC that have not been filtered.
Other sorts of comments from him have been rejected.


>                         In particular I am very concerned that DCC
> has the same weaknesses as blacklists in that they can be co-opted 
> as censorship mechanisms. Cindy Cohen of the EFF has described cases
> where groups have run organized campaigns to get opposing groups 
> such as moveon.org blacklisted by first subscribing to the list then
> making a complaint.

He feels that way about the DCC because his mail is not welcome at
any SMTP server I control.  He persistently misrepresents the nature
of the DCC as somehow related to blacklists, and implicitly rejects
the fact that his envelope sender value is in sendmail access_DB files
I control.  One might excuse his misrepresentation of the DCC as a
mental block causing a persistent misunderstanding.  The DCC is
uninteresting to most people and so misunderstanding it is not a fault.

In fact and as has been pointed out to him, the DCC does not detect
spam, but only bulk mail.  It is impossible for the DCC to have a "false
positive" or to be used for blacklisting provided that the fuzzy
checksums are not too fuzzy and that your private mail is not the same
as the private mail of lots of other people.  Private mail can't be
known to the DCC and so cannot be blacklisted.  On the other hand,
bulk mail can be known, but that's the point of the DCC.  Users of
the DCC must use whitelists to distinguish wanted from unwanted bulk
mail, whether the bulk mail comes from the IETF, Verisign, or Ralsky.


> Unfortunately many people are weasels and it is very difficult to 
> stop weaselish activities. The slashdot approach may be best in this 
> respect, moderation is frequently malicious but it is difficult to 
> organize campaigns because nobody chooses to be a moderator.
>
> So here we have kind of a recursive/self-referential situation.

That last sentence is right or at least not far wrong.

Perhaps he has not considered implications of my recent claim to
archive unique samples of all mail caught by my filters.  One is that
messages he submitted to the ASRG list with "courtesy" copies sent
toward my mailbox have been archived by my filters even when the ASRG
moderator did not pass them to the list.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Tue Jun 17 23:03:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20327
	for <ietf-web-archive@odin.ietf.org>; Tue, 17 Jun 2003 23:03:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SSye-0000Wu-Rd
	for ietf-list@asgard.ietf.org; Tue, 17 Jun 2003 22:47:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SSlR-0008R5-SH
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 22:33:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19739
	for <ietf@ietf.org>; Tue, 17 Jun 2003 22:33:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SSjD-0006pA-00
	for ietf@ietf.org; Tue, 17 Jun 2003 22:31:15 -0400
Received: from pigeon.verisign.com ([65.205.251.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SSjC-0006p7-00
	for ietf@ietf.org; Tue, 17 Jun 2003 22:31:14 -0400
Received: from mou1wnexc01.verisign.com (verisign.com [65.205.251.53])
        by pigeon.verisign.com (8.12.9/) with ESMTP id h5I2XPuv017123;
        Tue, 17 Jun 2003 19:33:25 -0700 (PDT)
Received: by mou1wnexc01.verisign.com with Internet Mail Service (5.5.2653.19)
	id <LMLHDL1X>; Tue, 17 Jun 2003 19:33:25 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D224C@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Keith Moore'" <moore@cs.utk.edu>,
        "Hallam-Baker, Phillip"
	 <pbaker@verisign.com>
Cc: "'Ronald van der Pol'" <Ronald.vanderPol@rvdp.org>,
        "'aarsenau@bbn.com'"
	 <aarsenau@bbn.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: myth of the great transition (was US Defense Department forma
	 lly adopts IPv6)
Date: Tue, 17 Jun 2003 19:33:24 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk


> On Tuesday, June 17, 2003, at 11:51  AM, Hallam-Baker, Phillip wrote:
> 
> > The key in my view is to work on the NAT vendors, instead 
> of viewing 
> > NAT
> > boxes as an obstacle they should be seen for what they 
> really are, an
> > essential and important part of the internet infrastructure.
> 
> you obviously don't write applications.

No, because I design and use applications I really wish that the IETF
had designed a decent NAT box spec rather than adopting the ostrich
position.

		Phill



From owner-ietf@ietf.org  Wed Jun 18 00:25:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22597
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 00:25:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SU9l-0002Q0-AQ
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 00:02:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SU6U-0002J6-5Z
	for ietf@asgard.ietf.org; Tue, 17 Jun 2003 23:59:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21644
	for <ietf@ietf.org>; Tue, 17 Jun 2003 23:59:19 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SU4E-0007Gw-00
	for ietf@ietf.org; Tue, 17 Jun 2003 23:57:03 -0400
Received: from h80ad275a.async.vt.edu ([128.173.39.90] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SU4D-0007Gt-00
	for ietf@ietf.org; Tue, 17 Jun 2003 23:57:01 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h5I3xBPZ014669;
	Tue, 17 Jun 2003 23:59:11 -0400
Message-Id: <200306180359.h5I3xBPZ014669@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: CLOSE ASRG NOW IT HAS FAILED 
In-Reply-To: Your message of "Mon, 16 Jun 2003 20:43:51 EDT."
             <Pine.LNX.4.44.0306162038030.5940-100000@commander.av8.net> 
References: <Pine.LNX.4.44.0306162038030.5940-100000@commander.av8.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_632384638P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 17 Jun 2003 23:59:10 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Mon, 16 Jun 2003 20:43:51 EDT, Dean Anderson said:
> believe it to be problem. Coincidentally, only lists frequented by such
> radical antispammers seem to suffer these problems.

This is no more surprising than the realization that DNA forensic evidence
is only being found by labs that have the capability of DNA forensic analysis,
or that Uri Geller wasn't debunked until he happened to run into
James Randi.

If (for instance) a list of poodle enthusiasts gets trawled for addresses,
and said list doesn't have any radical anti-spammers on it, then the victims
of the subsequent spamming runs will merely say "Oh Foo.  I wonder how they
got my address".

If one of the subscribers is a radical anti-spammer who is subscribed to
the list using the address k-rad-poodle-cookie-239DfjIqM@isp.com, and said
address gets spammed, the radical anti-spammer knows *VERY* well *exactly*
how the spammers got the address.....

When only radical anti-spammers are deploying methods for tracing how a
spammer gets addresses, *of course* only lists that have said anti-spammers
on it will have this problem.



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

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

iD8DBQE+7+OOcC3lWbTT17ARAn/MAJ44kGGf+FVvxQ9wH0U8mozU9M8UAgCg644p
wT08vS5xA9Q339zCrm+l34Q=
=rufi
-----END PGP SIGNATURE-----

--==_Exmh_632384638P--



From owner-ietf@ietf.org  Wed Jun 18 00:56:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23331
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 00:56:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SUrJ-0003rd-DN
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 00:47:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SUpQ-0003lk-F9
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 00:45:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23019
	for <ietf@ietf.org>; Wed, 18 Jun 2003 00:45:45 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SUnB-0007bm-00
	for ietf@ietf.org; Wed, 18 Jun 2003 00:43:29 -0400
Received: from h80ad275a.async.vt.edu ([128.173.39.90] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SUn9-0007bi-00
	for ietf@ietf.org; Wed, 18 Jun 2003 00:43:28 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h5I4jiPZ015021;
	Wed, 18 Jun 2003 00:45:44 -0400
Message-Id: <200306180445.h5I4jiPZ015021@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Your message of "Tue, 17 Jun 2003 19:33:24 PDT."
             <2A1D4C86842EE14CA9BC80474919782E0D224C@mou1wnexm02.verisign.com> 
References: <2A1D4C86842EE14CA9BC80474919782E0D224C@mou1wnexm02.verisign.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_2001321792P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 18 Jun 2003 00:45:44 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Tue, 17 Jun 2003 19:33:24 PDT, "Hallam-Baker, Phillip" said:

> No, because I design and use applications I really wish that the IETF
> had designed a decent NAT box spec rather than adopting the ostrich
> position.

If my un-NAT'ed box does a LISTEN on some TCP port, that generates no
outbound traffic.  However, if a SYN packet arrives at my upstream router
for my IP address and that port, the router still knows how to deliver it.

If my same box running the same software does a LISTEN on a TCP port while
behind a NAT, it also generates no outbound traffic.  However, if a SYN
packet shows up at the NAT box with the NAT box's IP address and that port
number on it, the NAT box HAS NO CLUE who to deliver it to.

It's pretty easy to show that there is no *transparent* way to make both
cases work.  If you handwave some magical-pixie-dust packet that is sent
out that says "Hey NAT box, I'm doing a LISTEN on port NNNN", then you have
to deal with (a) scaling when lots of clients do this, (b) information leakage
security issues, and (c) what happens when the application is started in
a NON-NAT environment.  If you don't sprinkle pixie dust, then the NAT doesn't
know what to do without manual configuration...

All the while noting that it could very well be 3-4 hops or more across a
large enterprise network before you reach a NAT... or your large enterprise
network might be acquisition-legacy hell and a packet can traverse 5 NAT
boxes without leaving the corporate network.  And deciding what the proper
behavior of the corporate NAT to the Internet in Chicago should be when
an application in the San Fran and Zurich offices both open port 31337 is
left as an exercise for the reader.

More "gotchas" can be found in RFC3027.

Now, what were you saying about ostriches?

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

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

iD8DBQE+7+54cC3lWbTT17ARAm0HAKCWIwhEFN3nLsZOyiNOjDmCk9PS6wCbBm7t
xv6cTv49CP+WNUpawlfMsao=
=f40g
-----END PGP SIGNATURE-----

--==_Exmh_2001321792P--



From owner-ietf@ietf.org  Wed Jun 18 02:08:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03249
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 02:08:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SVxw-0005np-6M
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 01:58:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SVvS-0005il-1N
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 01:56:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24228
	for <ietf@ietf.org>; Wed, 18 Jun 2003 01:56:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SVtC-00006L-00
	for ietf@ietf.org; Wed, 18 Jun 2003 01:53:46 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SVtC-00005w-00
	for ietf@ietf.org; Wed, 18 Jun 2003 01:53:46 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id B970B62251; Wed, 18 Jun 2003 07:55:33 +0200 (CEST)
Date: Wed, 18 Jun 2003 07:55:34 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: NAT box spec? (RE: myth of the great transition)
Message-ID: <444710000.1055915734@askvoll.hjemme.alvestrand.no>
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D224C@mou1wnexm02.verisign.com>
References:  <2A1D4C86842EE14CA9BC80474919782E0D224C@mou1wnexm02.verisign.com
 >
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, juni 17, 2003 19:33:24 -0700 "Hallam-Baker, Phillip" 
<pbaker@verisign.com> wrote:

>
>> On Tuesday, June 17, 2003, at 11:51  AM, Hallam-Baker, Phillip wrote:
>>
>> > The key in my view is to work on the NAT vendors, instead
>> of viewing
>> > NAT
>> > boxes as an obstacle they should be seen for what they
>> really are, an
>> > essential and important part of the internet infrastructure.
>>
>> you obviously don't write applications.
>
> No, because I design and use applications I really wish that the IETF
> had designed a decent NAT box spec rather than adopting the ostrich
> position.

Phil,

at the risk of feeding into a long-burning flamewar:
when you say "a decent NAT box spec", what do you think of?

As far as I can tell, a NAT box contains, over and above what it does 
because it's a router, a firewall or any other thing it might do:

- Address translation
- Application layer gatewaying
- Remote control of the NAT functionality (already being worked on in 
MIDCOM)

So what did you want a "decent NAT box spec" to say?

                Harald, genuinely curious



From owner-ietf@ietf.org  Wed Jun 18 02:52:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21762
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 02:52:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SWfo-00058n-Ns
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 02:44:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SWQg-0004tL-HT
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 02:28:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18071
	for <ietf@ietf.org>; Wed, 18 Jun 2003 02:28:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SWOR-0000LB-00
	for ietf@ietf.org; Wed, 18 Jun 2003 02:26:03 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SWOQ-0000L6-00
	for ietf@ietf.org; Wed, 18 Jun 2003 02:26:02 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h5I6Rnh05053
	for <ietf@ietf.org>; Wed, 18 Jun 2003 09:27:49 +0300
Date: Wed, 18 Jun 2003 09:27:49 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
In-Reply-To: <200306172026.QAA09324@ietf.org>
Message-ID: <Pine.LNX.4.44.0306180924460.4731-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


Hi,

I do not think this WG should be chartered.

On Tue, 17 Jun 2003, The IESG wrote:
> 
>  1. Virtual Private LAN Service (VPLS)--L2 service that emulates LAN
>        across an IP and an MPLS-enabled IP network, allowing standard
>        Ethernet devices communicate with each other as if they were
>        connected to a common LAN segment.

I *definitely* think we should *NOT* be working on this.

>  2. Virtual Private Wire Service (VPWS)--L2 service that provides L2
>        point-to-point connectivity (e.g. Frame Relay DLCI, ATM VPI/VCI,
>        point-to-point Ethernet) across an IP and an MPLS-enabled IP network.

We shouldn't be working on this.
 
>  3. IP-only L2 VPNs--L2 service across an IP and an MPLS-enabled
>        IP network, allowing standard IP devices to communicate with each
>        other as if they were connected to a common LAN segment or a point-
>        to-point circuit.

We may have to work on the point-to-point L2 VPN case, but I'd like to see 
alternative approaches to this.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From owner-ietf@ietf.org  Wed Jun 18 03:17:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22376
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 03:17:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SWxu-0005y2-QP
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 03:02:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SWvr-0005us-GJ
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 03:00:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22032
	for <ietf@ietf.org>; Wed, 18 Jun 2003 03:00:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SWtc-0000pt-00
	for ietf@ietf.org; Wed, 18 Jun 2003 02:58:16 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SWtb-0000pf-00
	for ietf@ietf.org; Wed, 18 Jun 2003 02:58:15 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 8D2BE6223F; Wed, 18 Jun 2003 09:00:03 +0200 (CEST)
Date: Wed, 18 Jun 2003 09:00:03 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department
 formally adopts IPv6)
Message-ID: <459350000.1055919603@askvoll.hjemme.alvestrand.no>
In-Reply-To: <20030617105244.GV4610@login.ecs.soton.ac.uk>
References: <200306171025.h5HAPxJA026393@ginger.lcs.mit.edu>
 <20030617105244.GV4610@login.ecs.soton.ac.uk>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, juni 17, 2003 11:52:45 +0100 Tim Chown <tjc@ecs.soton.ac.uk> 
wrote:

> Fair point.  But a year ago we didn't have Abilene, GEANT or a large
> number of European NRENs offering a native IPv6 service.  Cisco and
> Juniper's  support has come on in leaps and bounds, and now we do see US
> and European real deployment, overlaid on the production IPv4 network,
> and we see dual-stack transatlantic links.   On the coal face, we can see
> real progress.
>
> A year ago we didn't have official IPv6 support in Windows XP.  We didn't
> have prototypes from Sony and Panasnic being shown publicly.   We didn't
> have a pilot IPv6 deployment project from Microsoft (threedegrees).
> Things  are moving on.  Sure, we'll get hype from the marketing people,
> but that's  what they're paid to produce :)
>
> And noone's forcing IPv6 on anybody.  If you want to keep running IPv4,
> with or without NAT, feel free.

I actually think the last point is important.

I run IPv6 on some of my boxes now - the only part that gives me a headache 
is when someone else is running an IPv6 service that is less reliable than 
their IPv4 service. Experience breeds confidence.
(and my ISP doesn't know or care that I'm doing it. So much for relying on 
the ISPs....)

The difference I see between GOSIP and the US DoD announcement is that 
GOSIP was an attempt to bring something into existence by buying it; the US 
DoD IPv6 announcement says that they have evaluated something that exists, 
and found it useful enough to require it to be present "everywhere".

And I find that a *huge* difference.







From owner-ietf@ietf.org  Wed Jun 18 03:34:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22680
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 03:34:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SXCQ-0006Fi-Tb
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 03:17:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SX6k-00063I-M2
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 03:11:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22194
	for <ietf@ietf.org>; Wed, 18 Jun 2003 03:11:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SX4V-0000sd-00
	for ietf@ietf.org; Wed, 18 Jun 2003 03:09:31 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SX4U-0000sa-00
	for ietf@ietf.org; Wed, 18 Jun 2003 03:09:30 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h5I7CgxS002036;
	Wed, 18 Jun 2003 09:12:42 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Wed, 18 Jun 2003 09:11:46 +0200
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D224C@mou1wnexm02.verisign.com>
Message-Id: <1F72991D-A15C-11D7-A325-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, jun 18, 2003, at 04:33 Europe/Amsterdam, Hallam-Baker, 
Phillip wrote:

> I really wish that the IETF had designed a decent NAT box spec rather 
> than adopting the ostrich position.

http://www.ietf.org/html.charters/nat-charter.html




From owner-ietf@ietf.org  Wed Jun 18 04:32:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23846
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 04:32:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SY8U-0007q1-Nl
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 04:17:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SXxK-0007fc-Lv
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 04:06:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23365
	for <ietf@ietf.org>; Wed, 18 Jun 2003 04:06:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SXv5-0001CC-00
	for ietf@ietf.org; Wed, 18 Jun 2003 04:03:51 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SXv4-0001BY-00
	for ietf@ietf.org; Wed, 18 Jun 2003 04:03:50 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 7E4076223F; Wed, 18 Jun 2003 10:05:38 +0200 (CEST)
Date: Wed, 18 Jun 2003 10:05:38 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: full list for moderated list 
Message-ID: <473700000.1055923538@askvoll.hjemme.alvestrand.no>
In-Reply-To: <200306171539.h5HFdH6g019626@calcite.rhyolite.com>
References: <415400000.1055860886@askvoll.hjemme.alvestrand.no>
 <200306171539.h5HFdH6g019626@calcite.rhyolite.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, juni 17, 2003 09:39:17 -0600 Vernon Schryver 
<vjs@calcite.rhyolite.com> wrote:

> I've not noticed any real opposition to at least open archiving of
> moderation rejections.  Is there anything that needs to be done to
> make this an official recommendation, IESG policy, or whatever?

IETF mailing list policy is supposed to be grounded in RFC 2418 (WG 
guidelines), RFC 2026 (standard process) and RFC 3005 (IETF list charter).
But these documents are a bit high-level to be useful.

at the moment the only documents of any status that talk about how to run 
IETF mailing lists in any kind of detail are IESG policy documents:

http://www.ietf.org/IESG/STATEMENTS/mail-submit-policy.txt
http://www.ietf.org/IESG/STATEMENTS/moderated-lists.txt

Since the posting of the spamcontrol one (mail-submit-policy), the spam 
problem has grown significantly worse. So it should probably be updated.

And we've had calls for such policy-like things to be more reviewed by the 
community and permanently archived - which usually translates to "RFC 
publication".

It might be a good idea to think about a document or two in this space; I'm 
thinking of:

- IETF mailing list policy: what you should and should not do (BCP)

- IETF mailing list guidance: How to implement the policy using Mailman, 
Majordomo, xxx and yyyy (Info)

A good thing for someone to start writing.....?





From owner-ietf@ietf.org  Wed Jun 18 04:33:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23940
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 04:33:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SY8V-0007qa-9H
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 04:17:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SY6r-0007m6-S2
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 04:16:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23504
	for <ietf@ietf.org>; Wed, 18 Jun 2003 04:16:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SY4c-0001Er-00
	for ietf@ietf.org; Wed, 18 Jun 2003 04:13:42 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SY4b-0001EL-00
	for ietf@ietf.org; Wed, 18 Jun 2003 04:13:41 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 92F8B62251; Wed, 18 Jun 2003 10:15:29 +0200 (CEST)
Date: Wed, 18 Jun 2003 10:15:29 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Pekka Savola <pekkas@netcore.fi>, ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
Message-ID: <474900000.1055924129@askvoll.hjemme.alvestrand.no>
In-Reply-To: <Pine.LNX.4.44.0306180924460.4731-100000@netcore.fi>
References:  <Pine.LNX.4.44.0306180924460.4731-100000@netcore.fi>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pekka,

why?

I can think of some possible reasons, not necessarily exclusive

- this is a bad idea/impossible to do well, so we shouldn't do it
- some other organization is already doing it, so we shouldn't
- we're too stupid to get it right, so we shouldn't do it
- the IETF is too large, so we shouldn't be adding more work

>From your message, I can't tell which of those, or of any number of other 
possible objections, is the basis of your objection.

BTW - all these things were already being worked on in PPVPN. Some were 
even described in the charter.


--On onsdag, juni 18, 2003 09:27:49 +0300 Pekka Savola <pekkas@netcore.fi> 
wrote:

>
> Hi,
>
> I do not think this WG should be chartered.
>
> On Tue, 17 Jun 2003, The IESG wrote:
>>
>>  1. Virtual Private LAN Service (VPLS)--L2 service that emulates LAN
>>        across an IP and an MPLS-enabled IP network, allowing standard
>>        Ethernet devices communicate with each other as if they were
>>        connected to a common LAN segment.
>
> I *definitely* think we should *NOT* be working on this.
>
>>  2. Virtual Private Wire Service (VPWS)--L2 service that provides L2
>>        point-to-point connectivity (e.g. Frame Relay DLCI, ATM VPI/VCI,
>>        point-to-point Ethernet) across an IP and an MPLS-enabled IP
>>        network.
>
> We shouldn't be working on this.
>
>>  3. IP-only L2 VPNs--L2 service across an IP and an MPLS-enabled
>>        IP network, allowing standard IP devices to communicate with each
>>        other as if they were connected to a common LAN segment or a
>>        point- to-point circuit.
>
> We may have to work on the point-to-point L2 VPN case, but I'd like to
> see  alternative approaches to this.
>
> --
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which
> is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on
> what to pass are made solely by Raffaele D'Albenzio.
>





From owner-ietf@ietf.org  Wed Jun 18 05:27:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25002
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 05:27:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SZ4Y-0003Cm-7C
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 05:17:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SYzh-00036y-QN
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 05:12:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24740
	for <ietf@ietf.org>; Wed, 18 Jun 2003 05:12:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SYxS-0001ZC-00
	for ietf@ietf.org; Wed, 18 Jun 2003 05:10:22 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SYxR-0001Z7-00
	for ietf@ietf.org; Wed, 18 Jun 2003 05:10:21 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h5I9C5E06233;
	Wed, 18 Jun 2003 12:12:05 +0300
Date: Wed, 18 Jun 2003 12:12:05 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
In-Reply-To: <474900000.1055924129@askvoll.hjemme.alvestrand.no>
Message-ID: <Pine.LNX.4.44.0306181149130.6057-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

On Wed, 18 Jun 2003, Harald Tveit Alvestrand wrote:
> I can think of some possible reasons, not necessarily exclusive
> 
> - this is a bad idea/impossible to do well, so we shouldn't do it

Yes to both.

> - some other organization is already doing it, so we shouldn't

No idea about that.

> - we're too stupid to get it right, so we shouldn't do it

Yes.

> - the IETF is too large, so we shouldn't be adding more work

Yes.
 
> From your message, I can't tell which of those, or of any number of other 
> possible objections, is the basis of your objection.
> 
> BTW - all these things were already being worked on in PPVPN. Some were 
> even described in the charter.

Fair question, I probably should have included more text in the first 
place :-).

1. Virtual Private LAN Service.  This is Internet-wise ethernet bridging
over routing protocols such as BGP, IS-IS, etc; further, this has
typically little respect for security implications which are implicit (or 
even explicit) in LAN networks.

So, my main points are:

 - we must not overload routing protocols and such infrastructure (IMHO,
this seems an inevitable path the work would go towards..)

 - we must not create complexity by deploying ethernet bridging all over
the Internet.  Our work should be focused on making IP work, not
specifying Ethernet-over-IP (or worse, Ethernet-over-IP as a *service*).

 - it is architecturally wrong: use different subnets, period -- that's 
what those are meant for in the first place!

 - the model has significant security modifications.

Seems like some operators want to move their frame relay (and what have 
you) customers to be bridged over IP, instead of fixing their networks. 
(I'm allowed to say that because I work for an ISP :-).  And vendors are 
desperate to provide to solutions for these "needs".  But is this the 
right approach?  I don't think so.

2. Virtual Private Wire Service

This is slightly better as you're "only" performing point-to-point 
communication.  Same considerations as above apply, to a slightly lesser 
extent.

Btw. how is this different from currently-specified GRE tunneling?  It 
being made a "service"?

3. IP-only L2 VPNs

This seems a subset of case 1), which seems almost reasonable when it's
made for point-to-point links.  I just don't see why folks would really
want anything like this.  I can't figure out *one* area of applicability 
where using layer 3 mechanisms couldn't be made to work around the issue.

> --On onsdag, juni 18, 2003 09:27:49 +0300 Pekka Savola <pekkas@netcore.fi> 
> wrote:
> 
> >
> > Hi,
> >
> > I do not think this WG should be chartered.
> >
> > On Tue, 17 Jun 2003, The IESG wrote:
> >>
> >>  1. Virtual Private LAN Service (VPLS)--L2 service that emulates LAN
> >>        across an IP and an MPLS-enabled IP network, allowing standard
> >>        Ethernet devices communicate with each other as if they were
> >>        connected to a common LAN segment.
> >
> > I *definitely* think we should *NOT* be working on this.
> >
> >>  2. Virtual Private Wire Service (VPWS)--L2 service that provides L2
> >>        point-to-point connectivity (e.g. Frame Relay DLCI, ATM VPI/VCI,
> >>        point-to-point Ethernet) across an IP and an MPLS-enabled IP
> >>        network.
> >
> > We shouldn't be working on this.
> >
> >>  3. IP-only L2 VPNs--L2 service across an IP and an MPLS-enabled
> >>        IP network, allowing standard IP devices to communicate with each
> >>        other as if they were connected to a common LAN segment or a
> >>        point- to-point circuit.
> >
> > We may have to work on the point-to-point L2 VPN case, but I'd like to
> > see  alternative approaches to this.
> >
> > --
> > Pekka Savola                 "You each name yourselves king, yet the
> > Netcore Oy                    kingdom bleeds."
> > Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
> >
> >
> > _______________________________________________
> > This message was passed through ietf_censored@carmen.ipv6.cselt.it, which
> > is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on
> > what to pass are made solely by Raffaele D'Albenzio.
> >
> 
> 

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings





From owner-ietf@ietf.org  Wed Jun 18 10:08:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08331
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 10:08:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sd7O-0001VO-EF
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 09:36:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Scne-0005Yg-3O
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 09:16:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05096
	for <ietf@ietf.org>; Wed, 18 Jun 2003 09:16:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SclO-0004Gl-00
	for ietf@ietf.org; Wed, 18 Jun 2003 09:14:10 -0400
Received: from smtp03.mrf.mail.rcn.net ([207.172.4.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SclN-0004G8-00
	for ietf@ietf.org; Wed, 18 Jun 2003 09:14:09 -0400
Received: from 208-59-178-53.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com ([208.59.178.53] helo=localhost.localdomain)
	by smtp03.mrf.mail.rcn.net with esmtp (Exim 3.35 #4)
	id 19ScnW-0006S1-00; Wed, 18 Jun 2003 09:16:22 -0400
Subject: Re: full list for moderated list (was: CLOSE ASRG NOW IT HAS
	FAILED)
From: Frank Solensky <solenskyf@acm.org>
To: william@elan.net
Cc: ietf@ietf.org
In-Reply-To: <Pine.LNX.4.44.0306170449240.6482-100000@sokol.elan.net>
References: <Pine.LNX.4.44.0306170449240.6482-100000@sokol.elan.net>
Content-Type: text/plain
Message-Id: <1055940757.1243.18.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.3.92 (Preview Release)
Date: 18 Jun 2003 08:52:37 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Tue, 2003-06-17 at 07:52, william@elan.net wrote:
> I think the original idea was better - to only have web archive of those
> posts that did not make it through to the main list...

The downside of this approach, though, is that one would lose the
context in which the discarded message was offered.  OTOH,..

>  If technically easily 
> possible I'd also suggest marking on the main index if post was denied by
> moderator or denied by spam filter.

you'd want to differentiate between the two.

>  And having this archive for only past 
> 3 months seems just fine for that purpose.

The spam, yes.  The other, I'm not so sure -- if someone's making a
charge of unfairness or whatnot, you need to keep that longer.





From owner-ietf@ietf.org  Wed Jun 18 10:49:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10616
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 10:49:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Se3G-0004Be-EL
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 10:36:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SdrL-00043s-EI
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 10:24:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09650
	for <ietf@ietf.org>; Wed, 18 Jun 2003 10:24:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sdp5-000597-00
	for ietf@ietf.org; Wed, 18 Jun 2003 10:22:03 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sdp2-000594-00
	for ietf@ietf.org; Wed, 18 Jun 2003 10:22:01 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5IEO1MU002296
	for ietf@ietf.org env-from <vjs>;
	Wed, 18 Jun 2003 08:24:01 -0600 (MDT)
Date: Wed, 18 Jun 2003 08:24:01 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306181424.h5IEO1MU002296@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
References: <459350000.1055919603@askvoll.hjemme.alvestrand.no>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Harald Tveit Alvestrand <harald@alvestrand.no>

> ...
> The difference I see between GOSIP and the US DoD announcement is that 
> GOSIP was an attempt to bring something into existence by buying it; the US 
> DoD IPv6 announcement says that they have evaluated something that exists, 
> and found it useful enough to require it to be present "everywhere".
>
> And I find that a *huge* difference.

At the start of the GOSIP nonsense, that might have been a reasonable
charge.  By the middle, there were at least as many ISO OSI
applications as there are now IPv6 applications, and there was a
lot of real OSI traffic in Europe.  (A "lot" for that era if not
today.)  Major host vendors were supporting OSI protocols by the
end of GOSIP as well as they are now supporting IPv6.  OSI support
was a required checklist item in a lot of sales situations.

The GOSIP history shows that the recent U.S. DOD IPv6 announcement
should neither be overplayed or nor completely ignored.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Wed Jun 18 11:37:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13099
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 11:37:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Seqe-0006A1-Dh
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 11:27:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sepj-00060b-UC
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 11:26:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12492
	for <ietf@ietf.org>; Wed, 18 Jun 2003 11:26:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SenT-0005lf-00
	for ietf@ietf.org; Wed, 18 Jun 2003 11:24:28 -0400
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SenT-0005lb-00
	for ietf@ietf.org; Wed, 18 Jun 2003 11:24:27 -0400
Received: from inet-vrs-04.redmond.corp.microsoft.com ([157.54.8.149]) by mail4.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Wed, 18 Jun 2003 08:26:14 -0700
Received: from 157.54.6.150 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 18 Jun 2003 08:26:14 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-05.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 18 Jun 2003 08:26:14 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 18 Jun 2003 08:26:14 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.82]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3788.0);
	 Wed, 18 Jun 2003 08:26:13 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6940.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: myth of the great transition (was US Defense Department formally adopts IPv6)
Date: Wed, 18 Jun 2003 08:26:12 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA03C40BB7@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: myth of the great transition (was US Defense Department formally adopts IPv6)
Thread-Index: AcM1qNo27LtC2mCzSti9Rvp3IL7EqwAAvHZA
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Vernon Schryver" <vjs@calcite.rhyolite.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 18 Jun 2003 15:26:13.0720 (UTC) FILETIME=[F415F580:01C335AD]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA13099

> At the start of the GOSIP nonsense, that might have been a reasonable
> charge.  By the middle, there were at least as many ISO OSI
> applications as there are now IPv6 applications, and there was a
> lot of real OSI traffic in Europe.  (A "lot" for that era if not
> today.)  Major host vendors were supporting OSI protocols by the
> end of GOSIP as well as they are now supporting IPv6.  OSI support
> was a required checklist item in a lot of sales situations.

Well, you have to seriously qualify what you call "a lot". The only
non-TCP-IP network service that got widely deployed in Europe was X.25.
Most of its use was not strictly OSI: asynchronous modem connections
according to X.28 and X.29, or enterprise networks using X.25 as a lease
line replacement, much like modern-day VPN. Some of that is still in use
today, e.g. for the French "Minitel" service.

The only OSI service that had significant deployment was the mail
system, X.400. It was used for some research networks, very often
through gateways with SMTP mail. It was also used for exchange of
documents between enterprises in specialized EDI networks.

An aggravating factor in the GOSIP story was the lack of agreement on
the network + transport stack. The US proposed the IP-like CLNP and the
TCP-like TP4, the European X.400 deployments mostly used X.25 and TP0
(null transport), and ECMA was pushing a null network layer combined
with TP4 for European enterprise networks. 

The academics who were using X.400 and experimenting with X.500 quickly
moved to a combination of TCP-IP and TP0 (RFC 987, RFC 1006), because
TCP-IP was more accessible than either X.25 or CLNP. Most X.400 MTA used
in academic networks where dual stack, i.e. able to translate between
X.400 and RFC 822, and most of the traffic moved quickly to plain SMTP.
Similarly, the X.500 experiments resulted in LDAP, i.e. a TCP-IP
application.

Bottom line, there never was a significant usage of CLNP in Europe.

-- Christian Huitema




From owner-ietf@ietf.org  Wed Jun 18 12:33:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15392
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 12:33:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sfku-0007jy-9w
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 12:25:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sfh9-0007el-8I
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 12:21:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14994
	for <ietf@ietf.org>; Wed, 18 Jun 2003 12:21:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sfet-0006P5-00
	for ietf@ietf.org; Wed, 18 Jun 2003 12:19:39 -0400
Received: from tnt.isi.edu ([128.9.128.128])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sfes-0006P2-00
	for ietf@ietf.org; Wed, 18 Jun 2003 12:19:38 -0400
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6p2/8.11.2) with ESMTP id h5IGLpi24470;
	Wed, 18 Jun 2003 09:21:51 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.9.3/8.8.6) id JAA15366;
	Wed, 18 Jun 2003 09:09:03 -0700 (PDT)
Date: Wed, 18 Jun 2003 09:09:03 -0700 (PDT)
Message-Id: <200306181609.JAA15366@gra.isi.edu>
To: pekkas@netcore.fi, ietf@ietf.org, harald@alvestrand.no
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

  *> 
  *> I can think of some possible reasons, not necessarily exclusive
  *> 
  *> - this is a bad idea/impossible to do well, so we shouldn't do it
  *> - some other organization is already doing it, so we shouldn't
  *> - we're too stupid to get it right, so we shouldn't do it
  *> - the IETF is too large, so we shouldn't be adding more work
  *> 

Harald,

Here is one more to consider: maybe it is outside the mainstream of the
Internet architecture.  [Optimizing to leave IP out of the stack and do
direct L2 communication certainly SOUNDS like a retrograde step to me,
too.  Twenty years ago I was arguing with a UCLA professor, who
insisted that IP was too much overhead and that he needed to do direct
LAN transmission to get adequate performance for his distributed file
system.  He eventually figured out the fallacy, because the product
produced by his company had the IP layer in place.  Have we forgotten
these lessons?]

There is an infinite number of variations on the technology that the
IETF COULD develop, and for every one, there is some vendor or set of
vendors who would love to be able to sell sanctioned boxes.  That does
not mean it is in the best interest of the community or the technology
to develop them all.  I believe that the IESG needs to say NO more
often.  I know that's tough, but that's why we chose such excellent
members of the IESG.

Bob Braden




From owner-ietf@ietf.org  Wed Jun 18 12:55:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15849
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 12:55:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sg6b-0008Si-Cw
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 12:48:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sg50-0008OQ-W3
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 12:46:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15710
	for <ietf@ietf.org>; Wed, 18 Jun 2003 12:46:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sg2K-0006ag-00
	for ietf@ietf.org; Wed, 18 Jun 2003 12:43:52 -0400
Received: from grouse.mail.pas.earthlink.net ([207.217.120.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sg2J-0006ad-00
	for ietf@ietf.org; Wed, 18 Jun 2003 12:43:51 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by grouse.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19Sg4A-0004lR-00; Wed, 18 Jun 2003 09:45:46 -0700
Date: Wed, 18 Jun 2003 12:42:53 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: moore@cs.utk.edu, pbaker@verisign.com, Ronald.vanderPol@rvdp.org,
        aarsenau@bbn.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030618124253.21a62af8.moore@cs.utk.edu>
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D224C@mou1wnexm02.verisign.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D224C@mou1wnexm02.verisign.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I really wish that the IETF
> had designed a decent NAT box spec

that's an oxymoron.  the basic premis of NAT is fundamnetally broken.




From owner-ietf@ietf.org  Wed Jun 18 12:59:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16078
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 12:59:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sg6b-0008So-UR
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 12:48:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sg51-0008OR-1Q
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 12:46:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15714
	for <ietf@ietf.org>; Wed, 18 Jun 2003 12:46:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sg2X-0006al-00
	for ietf@ietf.org; Wed, 18 Jun 2003 12:44:05 -0400
Received: from [64.47.48.7] (helo=exchange.timetra.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sg2W-0006aV-00
	for ietf@ietf.org; Wed, 18 Jun 2003 12:44:04 -0400
Received: from vkompella ([64.47.48.10] RDNS failed) by exchange.timetra.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 18 Jun 2003 09:45:48 -0700
Reply-To: <vkompella@timetra.com>
From: "Vach Kompella" <vkompella@timetra.com>
To: "Pekka Savola" <pekkas@netcore.fi>,
        "Harald Tveit Alvestrand" <harald@alvestrand.no>
Cc: <ietf@ietf.org>
Subject: RE: WG review: Layer 2 Virtual Private Networks (l2vpn)
Date: Wed, 18 Jun 2003 09:46:30 -0700
Message-ID: <FNEFIPCNJKDDONJGBCNEOENBEBAA.vkompella@timetra.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <Pine.LNX.4.44.0306181149130.6057-100000@netcore.fi>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
X-OriginalArrivalTime: 18 Jun 2003 16:45:48.0948 (UTC) FILETIME=[1257ED40:01C335B9]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pekka,

>
> On Wed, 18 Jun 2003, Harald Tveit Alvestrand wrote:
> > I can think of some possible reasons, not necessarily exclusive
> >
> > - this is a bad idea/impossible to do well, so we shouldn't do it
>
> Yes to both.

As a meaningless response, I could just say - it's a good idea.  And it is
possible to do well.  That is, of course, as useless as saying it can't be done
well and is a bad idea because it is unsubstantiated.

>
>
> > - we're too stupid to get it right, so we shouldn't do it
>
> Yes.

Speak for yourself :-)

We're doing it.  Hopefully, we're going to get it mostly right if we don't think
that this is a service that scales to infinity.

>
> > - the IETF is too large, so we shouldn't be adding more work
>
> Yes.

So we should not do any new work?!

>
> > From your message, I can't tell which of those, or of any number of other
> > possible objections, is the basis of your objection.
> >
> > BTW - all these things were already being worked on in PPVPN. Some were
> > even described in the charter.
>
> Fair question, I probably should have included more text in the first
> place :-).
>
> 1. Virtual Private LAN Service.  This is Internet-wise ethernet bridging
> over routing protocols such as BGP, IS-IS, etc; further, this has
> typically little respect for security implications which are implicit (or
> even explicit) in LAN networks.
>
> So, my main points are:
>
>  - we must not overload routing protocols and such infrastructure (IMHO,
> this seems an inevitable path the work would go towards..)
>

If you use LDP, it is NOT a routing protocol.  The specific mode of use
(targeted LDP) is already described in RFC 3036.  The FECs are different, but
the FEC TLV was defined in such a way as to be extensible.

>  - we must not create complexity by deploying ethernet bridging all over
> the Internet.  Our work should be focused on making IP work, not
> specifying Ethernet-over-IP (or worse, Ethernet-over-IP as a *service*).
>

Primarily, folks want to use it as in "Ethernet-over-MPLS".  That may not
necessarily go down well with you either, but think of MPLS as a logical FR.
Providers do not want to change their infrastructure, e.g., replace a FR cloud
with an ATM cloud, then with SONET or GigE.  That's mega-expensive.  By
abstracting the L2 using MPLS, they can provide the L2VPN service without
wholesale infrastructure replacement.

>  - it is architecturally wrong: use different subnets, period -- that's
> what those are meant for in the first place!

Use different subnets to create VPNs?  I don't understand what you mean.  VPLS
and VPWS address a requirement for multiple domains (aka VPNs), logically
distinct from and invisible to each other.

>
>  - the model has significant security modifications.
>
> Seems like some operators want to move their frame relay (and what have
> you) customers to be bridged over IP, instead of fixing their networks.
> (I'm allowed to say that because I work for an ISP :-).  And vendors are
> desperate to provide to solutions for these "needs".  But is this the
> right approach?  I don't think so.
>
> 2. Virtual Private Wire Service
>
> This is slightly better as you're "only" performing point-to-point
> communication.  Same considerations as above apply, to a slightly lesser
> extent.
>
> Btw. how is this different from currently-specified GRE tunneling?  It
> being made a "service"?

GRE-tunneling is one option, but only for the transport of the VC.  However, you
need a demux field to identify the VC that you are carrying.  Carrying one
customer VC between a pair of PEs is obviously not adequate.

Tunneling is not new in the IETF.  The fact that you are tunneling what may be
non-IP packets seems to be giving you the heebie-jeebies.  Why?  What about the
tn3270, dlsw, netbios over ip work that has gone on in the past?  A little
massaging to make the packet look like data to be carried over an IP network,
and some implementation details at the edges.

>
> 3. IP-only L2 VPNs
>
> This seems a subset of case 1), which seems almost reasonable when it's
> made for point-to-point links.  I just don't see why folks would really
> want anything like this.  I can't figure out *one* area of applicability
> where using layer 3 mechanisms couldn't be made to work around the issue.

I agree with you on this.  The reason this is there is because some folks want
to do VPLS for IP only, and learn the MACs through the control plane.  I think
once you have VPLS, you don't really need this.

-Vach





From owner-ietf@ietf.org  Wed Jun 18 13:17:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16904
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 13:17:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SgTR-0000wT-1f
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 13:11:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SgHO-0000RU-Gt
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 12:59:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16051
	for <ietf@ietf.org>; Wed, 18 Jun 2003 12:59:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SgF8-0006gS-00
	for ietf@ietf.org; Wed, 18 Jun 2003 12:57:06 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SgF8-0006gP-00
	for ietf@ietf.org; Wed, 18 Jun 2003 12:57:06 -0400
Received: from MOU1WNEXC03.verisign.com (verisign.com [65.205.251.57])
        by peacock.verisign.com (8.12.9/) with ESMTP id h5IGxHh6000311;
        Wed, 18 Jun 2003 09:59:17 -0700 (PDT)
Received: by mou1wnexc03.verisign.com with Internet Mail Service (5.5.2653.19)
	id <MLJJV102>; Wed, 18 Jun 2003 09:59:16 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: "'moore@cs.utk.edu'" <moore@cs.utk.edu>,
        "'Ronald.vanderPol@rvdp.org'"
	 <Ronald.vanderPol@rvdp.org>,
        "'aarsenau@bbn.com'" <aarsenau@bbn.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: myth of the great transition (was US Defense Department forma
	 lly adopts IPv6)
Date: Wed, 18 Jun 2003 09:59:15 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

Not at all.

If you want to address denial of service issues you need protocol
enforcement points.

The INTERnet is a bidging architecture between networks. Lets put asside the
dogma and build the infrastucture the users need.

 -----Original Message-----
From: 	Keith Moore
Sent:	Wed Jun 18 09:47:42 2003
To:	Hallam-Baker, Phillip
Cc:	moore@cs.utk.edu; pbaker@verisign.com; Ronald.vanderPol@rvdp.org;
aarsenau@bbn.com; ietf@ietf.org
Subject:	Re: myth of the great transition (was US Defense Department
forma lly adopts IPv6)

> I really wish that the IETF
> had designed a decent NAT box spec

that's an oxymoron.  the basic premis of NAT is fundamnetally broken.



From owner-ietf@ietf.org  Wed Jun 18 13:20:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17122
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 13:20:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SgVC-00014D-Ij
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 13:13:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SgQV-0000qK-N5
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 13:08:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16593
	for <ietf@ietf.org>; Wed, 18 Jun 2003 13:08:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SgOF-0006nk-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:06:31 -0400
Received: from swan.mail.pas.earthlink.net ([207.217.120.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SgOF-0006nh-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:06:31 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by swan.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19SgQ0-000639-00; Wed, 18 Jun 2003 10:08:20 -0700
Date: Wed, 18 Jun 2003 13:05:28 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: moore@cs.utk.edu, Ronald.vanderPol@rvdp.org, aarsenau@bbn.com,
        ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030618130528.400b1f39.moore@cs.utk.edu>
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> If you want to address denial of service issues you need protocol
> enforcement points.

NAT is a denial of service attack, not a means of policy enforcement.





From owner-ietf@ietf.org  Wed Jun 18 13:46:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17955
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 13:46:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sgds-0001sh-IF
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 13:22:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sga6-0001T0-FR
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 13:18:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17057
	for <ietf@ietf.org>; Wed, 18 Jun 2003 13:18:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SgXq-0006vI-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:16:26 -0400
Received: from sj-core-3.cisco.com ([171.68.223.137])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SgXo-0006tn-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:16:25 -0400
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h5IHIBTr014561;
	Wed, 18 Jun 2003 10:18:12 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AIN41035;
	Wed, 18 Jun 2003 10:18:11 -0700 (PDT)
Message-Id: <200306181718.AIN41035@mira-sjc5-c.cisco.com>
To: vkompella@timetra.com
cc: ietf@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
In-Reply-To: Message from vkompella@timetra.com
   of "Wed, 18 Jun 2003 09:46:30 PDT." <FNEFIPCNJKDDONJGBCNEOENBEBAA.vkompella@timetra.com> 
Date: Wed, 18 Jun 2003 13:18:10 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

> We're doing it.

That's an "uh-oh" comment.  It's very common to hear people
say that the IETF doesn't know how to say "no" to new work.
I think the real problem is that many people bringing new
work to the IETF don't know how to accept being told "no"
and it leads to harass-a-thons of the IESG on the one hand
and dubious work on the other.  I think part of committing
to working in collaborative organizations like the IETF is
arguing your case the best you can but agreeing to accept
community consensus even if it doesn't come out the way
you'd like.

> Primarily, folks want to use it as in
> "Ethernet-over-MPLS".  That may not necessarily go down
> well with you either, but think of MPLS as a logical FR.

I think we need to retain a focus on connectionless,
packet-oriented delivery and how to build on that.  I wonder
if we aren't going considerably astray with the growing
emphasis on pseudo-circuits.

Melinda



From owner-ietf@ietf.org  Wed Jun 18 13:50:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18150
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 13:50:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sgvf-00025F-A7
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 13:41:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sgqr-0001yg-Ag
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 13:36:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17539
	for <ietf@ietf.org>; Wed, 18 Jun 2003 13:36:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sgob-00074u-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:33:45 -0400
Received: from [64.47.48.7] (helo=exchange.timetra.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sgoa-00074Z-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:33:44 -0400
Received: from vkompella ([64.47.48.10] RDNS failed) by exchange.timetra.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 18 Jun 2003 10:35:31 -0700
Reply-To: <vkompella@timetra.com>
From: "Vach Kompella" <vkompella@timetra.com>
To: "Melinda Shore" <mshore@cisco.com>
Cc: <ietf@ietf.org>
Subject: RE: WG review: Layer 2 Virtual Private Networks (l2vpn) 
Date: Wed, 18 Jun 2003 10:36:14 -0700
Message-ID: <FNEFIPCNJKDDONJGBCNEAENDEBAA.vkompella@timetra.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <200306181718.AIN41035@mira-sjc5-c.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
X-OriginalArrivalTime: 18 Jun 2003 17:35:31.0712 (UTC) FILETIME=[04359800:01C335C0]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Melinda,

"We're doing it" is a statement of fact.  However, we've been doing it for over
two years.  Pseudo-wire work has been ongoing for over 4 years.  MPLS has been
ongoing since 1996 or thereabouts.

I know there are some who think the IETF shouldn't be working on MPLS and its
applications.  I think there are those who think it should be.  I haven't heard
anything that says we are doing this in opposition to a consensus who would like
to see MPLS disappear or move to some other organization.

So you may voice your personal "uh-oh" but show me the consensus "uh-oh" before
I stop.

-Vach

> -----Original Message-----
> From: Melinda Shore [mailto:mshore@cisco.com]
> Sent: Wednesday, June 18, 2003 10:18 AM
> To: vkompella@timetra.com
> Cc: ietf@ietf.org
> Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
>
>
> > We're doing it.
>
> That's an "uh-oh" comment.  It's very common to hear people
> say that the IETF doesn't know how to say "no" to new work.
> I think the real problem is that many people bringing new
> work to the IETF don't know how to accept being told "no"
> and it leads to harass-a-thons of the IESG on the one hand
> and dubious work on the other.  I think part of committing
> to working in collaborative organizations like the IETF is
> arguing your case the best you can but agreeing to accept
> community consensus even if it doesn't come out the way
> you'd like.
>
> > Primarily, folks want to use it as in
> > "Ethernet-over-MPLS".  That may not necessarily go down
> > well with you either, but think of MPLS as a logical FR.
>
> I think we need to retain a focus on connectionless,
> packet-oriented delivery and how to build on that.  I wonder
> if we aren't going considerably astray with the growing
> emphasis on pseudo-circuits.
>
> Melinda
>





From owner-ietf@ietf.org  Wed Jun 18 13:51:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18196
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 13:51:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sgvf-00025s-Lm
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 13:41:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sgro-0001z5-Ju
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 13:37:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17609
	for <ietf@ietf.org>; Wed, 18 Jun 2003 13:37:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SgpY-00075k-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:34:44 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SgpX-00075a-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:34:44 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id C123FABB5; Wed, 18 Jun 2003 10:42:38 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: "Hallam-Baker, Phillip" <pbaker@verisign.com>, Ronald.vanderPol@rvdp.org,
        aarsenau@bbn.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 18 Jun 2003 10:42:38 -0700
In-Reply-To: <20030618130528.400b1f39.moore@cs.utk.edu>
Message-ID: <kj65n3mgdt.fsf@romeo.rtfm.com>
Lines: 20
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> > If you want to address denial of service issues you need protocol
> > enforcement points.
> 
> NAT is a denial of service attack, not a means of policy enforcement.

I don't think this is really accurate.

The difference between denial of service and policy enforcement
is primarily a question of authorization. Since the people who
install NAT generally own the networks in question, characterizing
NAT as a DoS attack doesn't really seem right.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
           Web Log: http://www.rtfm.com/movabletype




From owner-ietf@ietf.org  Wed Jun 18 14:14:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19237
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 14:14:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sh6t-0003Gj-34
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 13:52:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sh2D-0002W4-0B
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 13:47:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18028
	for <ietf@ietf.org>; Wed, 18 Jun 2003 13:47:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sgzw-0007Cd-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:45:29 -0400
Received: from pintail.mail.pas.earthlink.net ([207.217.120.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sgzr-0007CP-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:45:28 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by pintail.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19Sh1g-000592-00; Wed, 18 Jun 2003 10:47:16 -0700
Date: Wed, 18 Jun 2003 13:44:24 -0400
From: Keith Moore <moore@cs.utk.edu>
To: EKR <ekr@rtfm.com>
Cc: moore@cs.utk.edu, pbaker@verisign.com, Ronald.vanderPol@rvdp.org,
        aarsenau@bbn.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030618134424.410d29d1.moore@cs.utk.edu>
In-Reply-To: <kj65n3mgdt.fsf@romeo.rtfm.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > NAT is a denial of service attack, not a means of policy enforcement.
> 
> I don't think this is really accurate.
> 
> The difference between denial of service and policy enforcement
> is primarily a question of authorization. Since the people who
> install NAT generally own the networks in question, characterizing
> NAT as a DoS attack doesn't really seem right.

people who run virus-laden programs are doing so because they want the
advertised functionality of that program, not because they want to infect
their systems or spread the virus.   people who use Microsoft mail readers do
so because they want to read mail, not because they want to expose their
systems to attack.

similarly, people who install NAT usually don't realize how much this
costs them in lost functionality and reliability.

perhaps DoS isn't quite the right term, but it's not far off.




From owner-ietf@ietf.org  Wed Jun 18 14:14:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19240
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 14:14:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sh6s-0003FT-H7
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 13:52:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sgz0-00028O-9z
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 13:44:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17912
	for <ietf@ietf.org>; Wed, 18 Jun 2003 13:44:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sgwk-0007AE-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:42:10 -0400
Received: from wetware.wetware.com ([199.108.16.1] helo=wetware.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sgwj-0007A6-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:42:09 -0400
Received: from 208.177.152.18.ptr.us.xo.net ([208.177.152.18] helo=wetware.com)
	by wetware.com with esmtp (Exim 4.20)
	id 19SgyS-0006fE-GS
	for ietf@ietf.org; Wed, 18 Jun 2003 10:43:56 -0700
Date: Wed, 18 Jun 2003 10:44:05 -0700
Subject: Re: NAT box spec? (RE: myth of the great transition)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: james woodyatt <jhw@wetware.com>
To: IETF list <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <444710000.1055915734@askvoll.hjemme.alvestrand.no>
Message-Id: <74E08DEB-A1B4-11D7-A096-000393BA7EBA@wetware.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Tuesday, Jun 17, 2003, at 22:55 US/Pacific, Harald Tveit Alvestrand 
wrote:
>
> at the risk of feeding into a long-burning flamewar:
> when you say "a decent NAT box spec", what do you think of?

Now, you've done it.

> As far as I can tell, a NAT box contains, over and above what it does 
> because it's a router, a firewall or any other thing it might do:
>
> - Address translation
> - Application layer gatewaying
> - Remote control of the NAT functionality (already being worked on in 
> MIDCOM)
>
> So what did you want a "decent NAT box spec" to say?
>
>                Harald, genuinely curious

I maintain the NAT code (among other things) in the firmware of a 
consumer Wi-Fi/router product.  I'm not sure I can think of anything 
the IETF needs to do here beyond what it has already done-- or is in 
the process of finishing up.

I think the spec that Mr. Hallam-Baker would like to see is likely to 
emerge from outside the IETF.  In fact, I predict that several 
competing de facto standards will emerge in the market, and eventually 
one of them may win out-- but I'm pessimistic about that.

When customers of retail Internet service start demanding a NAT 
standard, then that's when the IETF might want to think about 
documenting the standard that the market seems to want.  Not before, I 
think.

I see no evidence that such demand exists now, or that it's very likely 
to exist in the foreseeable future.  Piteous whines from applications 
developers complaining about the weird menagerie of NAT implementations 
do *NOT* constitute an indication of real demand from retail Internet 
service customers.

The IETF has already decided how to proceed with addressing the 
limitations in IPv4 that make the deployment of NAT devices an optimal 
strategy in some cases.  We've seen how successful the IETF has been in 
persuading users that a new protocol is superior because it comes 
stamped with the magick 'Draft Standard' label.  I doubt that providing 
such a magick stamp for NAT devices would be worth the effort if the 
market isn't interested in products that claim to be compliant with it.


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




From owner-ietf@ietf.org  Wed Jun 18 14:53:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21051
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 14:53:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ShQF-0003jY-N0
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 14:12:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ShHs-0003RU-GA
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:04:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18771
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:03:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShFc-0007PQ-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:01:40 -0400
Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShFb-0007PN-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:01:40 -0400
Received: from cs.columbia.edu (10.34.76.81 [10.34.76.81]) by w2ksjexg01.ciena.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id K04AG1TM; Wed, 18 Jun 2003 11:03:31 -0700
Message-ID: <3EF0A9AE.7000202@cs.columbia.edu>
Date: Wed, 18 Jun 2003 11:04:30 -0700
From: Ping Pan <pingpan@cs.columbia.edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bob Braden <braden@ISI.EDU>
CC: ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
References: <200306181609.JAA15366@gra.isi.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bob Braden wrote:
> Harald,
> 
> Here is one more to consider: maybe it is outside the mainstream of the
> Internet architecture.  [Optimizing to leave IP out of the stack and do
> direct L2 communication certainly SOUNDS like a retrograde step to me,
> too.  Twenty years ago I was arguing with a UCLA professor, who
> insisted that IP was too much overhead and that he needed to do direct
> LAN transmission to get adequate performance for his distributed file
> system.  He eventually figured out the fallacy, because the product
> produced by his company had the IP layer in place.  Have we forgotten
> these lessons?]
> 

Bob,

I think not. If you look like what people are working on in this area, 
it is all IP-driven:
  - at data plane, L2 flows are aggregated through GRE, MPLS... tunnels.
  - at control layer, it all IP: LDP, BGP, Radius...

Along with L3VPN, I argue this is mainstream Internet. If there is a 
problem, I start to worry if we are overloading some of the protocols. 
Well... if it aint broken, why fix it? :-)

If you concern about building nation-wide L2 bridging backbones with 
spanning trees running off the roof, :-) so far, I have not seen people 
seriously moving toward that direction.

As for IESG, the problem is not about having a new IETF WG. Rather, why 
are we spending so much time and energy on standardization? How many 
times are people going to write architecture and framework RFC's?

2 cents,

- Ping




From owner-ietf@ietf.org  Wed Jun 18 14:54:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21370
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 14:54:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ShQG-0003k5-GV
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 14:12:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ShKJ-0003TY-8L
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:06:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18917
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:06:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShI3-0007RO-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:04:11 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShI2-0007RG-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:04:10 -0400
Received: from [67.126.41.36] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h5II6Prc096077
	for <ietf@ietf.org>; Wed, 18 Jun 2003 11:06:26 -0700 (PDT)
	(envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
X-Sender: phoffvpnc@mail.vpnc.org
Message-Id: <p05210606bb1655fef91b@[67.126.41.36]>
In-Reply-To: <474900000.1055924129@askvoll.hjemme.alvestrand.no>
References: <Pine.LNX.4.44.0306180924460.4731-100000@netcore.fi>
 <474900000.1055924129@askvoll.hjemme.alvestrand.no>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Wed, 18 Jun 2003 11:04:52 -0700
To: ietf@ietf.org
From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:15 AM +0200 6/18/03, Harald Tveit Alvestrand wrote:
>I can think of some possible reasons, not necessarily exclusive
>
>- this is a bad idea/impossible to do well, so we shouldn't do it
>- some other organization is already doing it, so we shouldn't
>- we're too stupid to get it right, so we shouldn't do it
>- the IETF is too large, so we shouldn't be adding more work

This might be a combination of the latter three, but I think it is 
clearer for this WG:

- the IETF's track record for this work so far is quite poor

We have not shown any ability to create standards in this area with 
due speed or predictability. We have not shown the good judgement 
needed to limit the scope of the work we do. (Look at the number of 
L2VPN-based Working Group drafts in PWE3 and PPVPN, much less the 
large number of non-WG documents being actively discussed.

The IETF understands the need for layer 2 technologies for OAM much 
better than we understand the Internet customer's need (or even 
concern) for layer 2 transport of their IP packets. This is because 
we have a tighter relationship with operators than we do with 
Internet users, and because Internet users generally could care less 
about how their ISPs move their traffic as long as they meet the 
service level agreements. The ISPs would love to have better 
cross-vendor interop for the L2VPN technologies, but so far the 
vendors haven't had time to think about that because they have been 
overloaded with the literally dozens of flavors that are being 
discussed in the IETF.

We will never know if there is another organization who could do a 
better job than this because no other organization will take on the 
work while the 800-pound gorilla of standards bodies is flailing 
around in the area. There are certainly other organizations that can 
take it on, such as the MPLS and Frame Relay Alliance. They might do 
just as bad of a job as we have so far, but they could also do much 
better because they are much more focused.

--Paul Hoffman, Director
--VPN Consortium



From owner-ietf@ietf.org  Wed Jun 18 14:56:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21550
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 14:56:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ShQH-0003kr-6D
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 14:12:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ShOA-0003eh-SQ
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:10:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19115
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:10:29 -0400 (EDT)
From: matthew.ford@bt.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShLv-0007W2-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:08:11 -0400
Received: from saturn.bt.com ([193.113.57.20] helo=cbibipnt08.hc.bt.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShLu-0007Vq-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:08:10 -0400
Received: by cbibipnt08.hc.bt.com with Internet Mail Service (5.5.2654.89)
	id <NF4KJQCD>; Wed, 18 Jun 2003 19:10:07 +0100
Message-ID: <ADEC16A81CFF17489F5A2A9E1D2226DE401C90@i2km41-ukdy.domain1.systemhost.net>
To: ietf@ietf.org
Subject: Network 7
Date: Wed, 18 Jun 2003 19:09:51 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.89)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Anyone know whether network 007/8 is 'IANA - Reserved' as IANA state here:
http://www.iana.org/assignments/ipv4-address-space or 'Allocated' as ARIN
state here:
ftp://ftp.arin.net/pub/stats/arin/arin.20030601?

Mat



From owner-ietf@ietf.org  Wed Jun 18 15:16:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23682
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:16:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Si52-000618-7A
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 14:54:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ShSO-0004Ax-6w
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:14:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19307
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:14:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShQ8-0007Ys-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:12:32 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShQ7-0007Y3-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:12:31 -0400
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h5IIEIUm003787;
	Wed, 18 Jun 2003 11:14:18 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AIN51100;
	Wed, 18 Jun 2003 11:14:17 -0700 (PDT)
Message-Id: <200306181814.AIN51100@mira-sjc5-c.cisco.com>
To: EKR <ekr@rtfm.com>
cc: ietf@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Message from ekr@rtfm.com
   of "18 Jun 2003 10:42:38 PDT." <kj65n3mgdt.fsf@romeo.rtfm.com> 
Date: Wed, 18 Jun 2003 14:14:17 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

> The difference between denial of service and policy enforcement
> is primarily a question of authorization. Since the people who
> install NAT generally own the networks in question, characterizing
> NAT as a DoS attack doesn't really seem right.

Well, yeah, but ...  NAT is far too crude in its policy
capabilities to be able to credibly claim that it's a policy
enforcement device.  That's why we have all these ghastly
work-arounds - effectively they're for the purposes of
refining the policy semantics.  I think this may be one of
those cases where it's neither a furniture polish nor a
dessert topping.

I'm not sure that labelling it a "DoS attack" is
particularly helpful, though.

Melinda




From owner-ietf@ietf.org  Wed Jun 18 15:20:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23949
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:20:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Si53-00066H-Ay
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 14:54:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ShU6-0004Rr-Mk
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:16:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19540
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:16:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShRq-0007db-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:14:18 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShRp-0007cx-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:14:17 -0400
Received: from cisco.com (sjc-vpn4-303.cisco.com [10.21.81.47])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with SMTP id h5IIG36p025909
	for <ietf@ietf.org>; Wed, 18 Jun 2003 11:16:04 -0700 (PDT)
Received: by cisco.com (sSMTP sendmail emulation); Wed, 18 Jun 2003 14:16:02 -0400
Date: Wed, 18 Jun 2003 14:16:02 -0400
From: Scott W Brim <swb@employees.org>
To: ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
Message-ID: <20030618181602.GL2044@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <swb@employees.org>, ietf@ietf.org
References: <FNEFIPCNJKDDONJGBCNEOENBEBAA.vkompella@timetra.com> <200306181718.AIN41035@mira-sjc5-c.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200306181718.AIN41035@mira-sjc5-c.cisco.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Jun 18, 2003 01:18:10PM -0400, Melinda Shore allegedly wrote:
> I think we need to retain a focus on connectionless,
> packet-oriented delivery and how to build on that.  I wonder
> if we aren't going considerably astray with the growing
> emphasis on pseudo-circuits.

The IETF does continue to have an emphasis on connectionless,
packet-oriented delivery.  That's our fundamental architecture, without
question.  In the meantime there are customers who want to transition to
c, p-o d but need mechanisms for doing so.  Why did we spend any time on
transition from IPv4 to IPv6?  In order to make transition easier.  They
want to convert.  Do we say outsiders can't convert to our religion,
they can only be born into it?  Do you want them to define their own
ways to do [virtual] circuit emulation?  



From owner-ietf@ietf.org  Wed Jun 18 15:23:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24096
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:23:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Si7p-0007A0-He
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 14:57:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Shcb-0004WD-DM
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:25:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19852
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:25:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShaL-0007he-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:23:05 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShaK-0007hW-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:23:04 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id DDAA2ABB5; Wed, 18 Jun 2003 11:31:00 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 18 Jun 2003 11:31:00 -0700
In-Reply-To: <20030618140538.103ea88b.moore@cs.utk.edu>
Message-ID: <kju1ankzkr.fsf@romeo.rtfm.com>
Lines: 40
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> > > similarly, people who install NAT usually don't realize how much this
> > > costs them in lost functionality and reliability.
> > Really? You have evidence of this?
> 
> the evidence I have is from reading vendor advertisements for NAT boxes,
> and from talking to people who run networks that use NAT.  it's not 
> a random sample, perhaps not a statistically significant one, but it's
> been enough to convince me personally that the delusion is widespread.
You can perhaps understand why I wouldn't consider this a particularly
convincing line of argument.

> > I don't either, but my intuition is that you're wrong.  Once you have
> > decided to have a firewall in place (which you may think is evil, but
> > I consider pretty much a necessary evil), I suspect that most people
> > suffer almost not at all from having a NAT.
> 
> depends on what you mean by "firewall"  (which these days is a pretty
> vague term).  but there are several primary effects of NAT - one being
> that addresses are not maintained end-to-end, another being that NATs
> cause address-to-host bindings to be ephemeral when they would otherwise
> not be, and another being that (for NAPTs anyway) attempts to initiate
> traffic across the NAPT are blocked in one direction.  there is rarely
> a significant benefit in a firewall doing the first two of these.  a good
> firewall has the capability to block traffic in either direction, or not, on a
> case-by-case basis, and can be adjusted according to the needs of its users. 
Yes, but these are philosophical objections.

What applications that people want to run--and the IT managers would
want to enable--are actually inhibited by NAT? It seems to me that
most of the applications inconvenienced by NAT are ones that IT
managers would want to screen off anyway.
        
-Ekr
-- 
[Eric Rescorla                                   ekr@rtfm.com]
           Web Log: http://www.rtfm.com/movabletype

        



From owner-ietf@ietf.org  Wed Jun 18 15:25:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24242
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:25:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Si7p-0007A8-PN
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 14:57:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Shcm-0004WF-Sk
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:25:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19857
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:25:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShaW-0007hl-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:23:17 -0400
Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShaW-0007hY-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:23:16 -0400
Received: from nwmail.wh.lucent.com (h135-5-40-100.lucent.com [135.5.40.100])
	by ihemail2.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h5IIP0t09929
	for <ietf@ietf.org>; Wed, 18 Jun 2003 13:25:01 -0500 (CDT)
Received: by nwmail.wh.lucent.com (8.11.7+Sun/EMS-1.5 sol2)
	id h5IIOxr00356; Wed, 18 Jun 2003 14:24:59 -0400 (EDT)
Received: from lucent.com by nwmail.wh.lucent.com (8.11.7+Sun/EMS-1.5 sol2)
	id h5IIOwn00350; Wed, 18 Jun 2003 14:24:58 -0400 (EDT)
Message-ID: <3EF0AE78.3010704@lucent.com>
Date: Wed, 18 Jun 2003 14:24:56 -0400
From: Uri Blumenthal <uri@lucent.com>
Organization: Lucent Technologies
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 (CK-LucentTPES)
X-Accept-Language: en-us, en, zh-cn, ru, de, he
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
References: <200306181718.AIN41035@mira-sjc5-c.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 6/18/2003 1:18 PM, Melinda Shore wrote:
>>We're doing it.
> 
> .......the real problem is that many people bringing new
> work to the IETF don't know how to accept being told "no"
> and it leads to harass-a-thons of the IESG on the one hand
> and dubious work on the other. 

:-) :-)

I agree.

>>Primarily, folks want to use it as in
>>"Ethernet-over-MPLS".  That may not necessarily go down
>>well with you either, but think of MPLS as a logical FR.
> 
> I think we need to retain a focus on connectionless,
> packet-oriented delivery and how to build on that.  I wonder
> if we aren't going considerably astray with the growing
> emphasis on pseudo-circuits.

Again, I agree and support.




From owner-ietf@ietf.org  Wed Jun 18 15:28:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24456
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:28:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SiHL-00047O-Vm
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 15:07:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Shr1-0004iF-Pp
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:40:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20418
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:40:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Shol-00000G-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:37:59 -0400
Received: from dhcp1.se.kurtis.pp.se ([195.43.225.70] helo=laptop2.kurtis.autonomica.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Shok-0007nW-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:37:58 -0400
Received: from kurtis.pp.se (localhost [127.0.0.1])
	by laptop2.kurtis.autonomica.se (8.12.9/8.10.2) with ESMTP id h5IIe6FT013506;
	Wed, 18 Jun 2003 20:40:06 +0200 (CEST)
Date: Wed, 18 Jun 2003 20:40:02 +0200
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
Content-Type: text/plain; charset=US-ASCII; format=fixed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "Pekka Savola" <pekkas@netcore.fi>,
        "Harald Tveit Alvestrand" <harald@alvestrand.no>, <ietf@ietf.org>
To: <vkompella@timetra.com>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <FNEFIPCNJKDDONJGBCNEOENBEBAA.vkompella@timetra.com>
Message-Id: <45712F09-A1BC-11D7-9791-000393A638B2@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
X-Pgp-Rfc2646-Fix: 1
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>  - we must not overload routing protocols and such infrastructure 
>> (IMHO,
>> this seems an inevitable path the work would go towards..)
>>
>
> If you use LDP, it is NOT a routing protocol.  The specific mode of use
> (targeted LDP) is already described in RFC 3036.  The FECs are 
> different, but
> the FEC TLV was defined in such a way as to be extensible.

And when you want to do this inter-domain? Everything else seems to 
have made it's way into BGP so I think that Pekkas concerns are valid...

>>  - we must not create complexity by deploying ethernet bridging all 
>> over
>> the Internet.  Our work should be focused on making IP work, not
>> specifying Ethernet-over-IP (or worse, Ethernet-over-IP as a 
>> *service*).
>>
>
> Primarily, folks want to use it as in "Ethernet-over-MPLS".  That may 
> not
> necessarily go down well with you either, but think of MPLS as a 
> logical FR.
> Providers do not want to change their infrastructure, e.g., replace a 
> FR cloud
> with an ATM cloud, then with SONET or GigE.  That's mega-expensive.  By
> abstracting the L2 using MPLS, they can provide the L2VPN service 
> without
> wholesale infrastructure replacement.

Most of these providers have bought what their vendor told them to buy, 
but let's not go into that here.

>
>>  - it is architecturally wrong: use different subnets, period -- 
>> that's
>> what those are meant for in the first place!
>
> Use different subnets to create VPNs?  I don't understand what you 
> mean.  VPLS
> and VPWS address a requirement for multiple domains (aka VPNs), 
> logically
> distinct from and invisible to each other.

Pekka is right in that most of the applications of VPNs today could 
actually be solved as good with "real addresses" and routing across 
networks.

>> Btw. how is this different from currently-specified GRE tunneling?  It
>> being made a "service"?
>
> GRE-tunneling is one option, but only for the transport of the VC.  
> However, you
> need a demux field to identify the VC that you are carrying.  Carrying 
> one
> customer VC between a pair of PEs is obviously not adequate.

L2TPv3? Whats the advantage with this over the existing protocol that 
the IETF have?

> - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.2

iQA/AwUBPvCyBKarNKXTPFCVEQL6DQCfSLe3xKzNpU+Me8j4lFuGJojeu+oAoKAP
WdkmzQyNXqX4UfhZdIc8XX1g
=iysk
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Wed Jun 18 15:31:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24681
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:31:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SiHM-00048a-Gw
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 15:07:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Shsd-0004jq-LJ
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:41:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20546
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:41:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShqN-00001r-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:39:39 -0400
Received: from dhcp1.se.kurtis.pp.se ([195.43.225.70] helo=laptop2.kurtis.autonomica.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShqM-00001o-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:39:38 -0400
Received: from kurtis.pp.se (localhost [127.0.0.1])
	by laptop2.kurtis.autonomica.se (8.12.9/8.10.2) with ESMTP id h5IIfaFT013509;
	Wed, 18 Jun 2003 20:41:37 +0200 (CEST)
Date: Wed, 18 Jun 2003 20:41:33 +0200
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=fixed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "'Keith Moore'" <moore@cs.utk.edu>,
        "'Ronald.vanderPol@rvdp.org'" <Ronald.vanderPol@rvdp.org>,
        "'aarsenau@bbn.com'" <aarsenau@bbn.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
Message-Id: <7B9C16C6-A1BC-11D7-9791-000393A638B2@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
X-Pgp-Rfc2646-Fix: 1
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> If you want to address denial of service issues you need protocol
> enforcement points.

Protocol enforcement points have so far failed to scale (today called 
border routers). What you need is to fix a much wider problem.

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.2

iQA/AwUBPvCyXqarNKXTPFCVEQLk9QCeKez7+Z+rMZ0NAsTSads75v9bP3wAmgP7
WG3EHWur0S0G+pjg/eahGGTC
=mVIP
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Wed Jun 18 15:37:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24929
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:37:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SiHM-00049D-UT
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 15:07:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ShtN-0004kn-NS
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:42:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20586
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:42:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Shr7-00002C-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:40:25 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Shr7-000029-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:40:25 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5IIgdN09482;
        Wed, 18 Jun 2003 14:42:41 -0400 (EDT)
Date: Wed, 18 Jun 2003 14:42:39 -0400
From: Keith Moore <moore@cs.utk.edu>
To: EKR <ekr@rtfm.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030618144239.0c31eb88.moore@cs.utk.edu>
In-Reply-To: <kju1ankzkr.fsf@romeo.rtfm.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
	<kju1ankzkr.fsf@romeo.rtfm.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > the evidence I have is from reading vendor advertisements for NAT
> > boxes, and from talking to people who run networks that use NAT. 
> > it's not a random sample, perhaps not a statistically significant
> > one, but it's been enough to convince me personally that the
> > delusion is widespread.
>
> You can perhaps understand why I wouldn't consider this a particularly
> convincing line of argument.

of course.  but you can perhaps understand why I don't consider your 
intiution to the contrary convincing either?

> What applications that people want to run--and the IT managers would
> want to enable--are actually inhibited by NAT? 

depends on the people.  the people I work with want to run large-scale
distributed computing problems.  other people want to use SIP to support
internet telephony or for some other purpose.  others want to use
IPsec...  yes there are workarounds for many of these, but they have to
be invented on a case-by-case basis, and often they're expensive.




From owner-ietf@ietf.org  Wed Jun 18 15:39:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25154
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:39:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SiMI-0005hj-1b
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 15:12:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Si3J-0005SH-7y
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:53:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21033
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:52:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Si13-00008p-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:50:41 -0400
Received: from tomts7.bellnexxia.net ([209.226.175.40] helo=tomts7-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Si12-00008F-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:50:40 -0400
Received: from yahoo.com ([65.93.180.122]) by tomts7-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030618183450.CZKE25372.tomts7-srv.bellnexxia.net@yahoo.com>;
          Wed, 18 Jun 2003 14:34:50 -0400
Date: Wed, 18 Jun 2003 14:34:42 -0400
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
Message-Id: <86E97E06-A1BB-11D7-84BB-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Wednesday, June 18, 2003, at 12:59  PM, Hallam-Baker, Phillip wrote:

> Not at all.
>
> If you want to address denial of service issues you need protocol
> enforcement points.

This sounds like you are equating a NAT box with a firewall, which 
seems to be common.

I would like to know:
- Is a NAT box a protocol enforcement point?
- is it an EFFECTIVE protocol enforcement point?
- is a NAT a firewall? (many people seem to think it is ...)
- is a firewall a protocol enforcement point? (yes)
- does a protocol enforcement point, have to include a NAT?
- does an EFFECTIVE one have to include a NAT?
- is it even EASIER to enforce protocol issues with a NAT as opposed to 
other means?

simon

>> I really wish that the IETF
>> had designed a decent NAT box spec
>
> that's an oxymoron.  the basic premis of NAT is fundamnetally broken.

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Wed Jun 18 15:45:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25364
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:45:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SiSr-0007SQ-56
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 15:19:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Si6b-0006Q1-Ea
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:56:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21533
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:56:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Si4L-0000Gm-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:54:05 -0400
Received: from fmr02.intel.com ([192.55.52.25] helo=caduceus.fm.intel.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Si4K-0000Gj-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:54:04 -0400
Received: from petasus.fm.intel.com (petasus.fm.intel.com [10.1.192.37])
	by caduceus.fm.intel.com (8.11.6p2/8.11.6/d: outer.mc,v 1.66 2003/05/22 21:17:36 rfjohns1 Exp $) with ESMTP id h5IImIs02811
	for <ietf@ietf.org>; Wed, 18 Jun 2003 18:48:18 GMT
Received: from fmsmsxvs041.fm.intel.com (fmsmsxvs041.fm.intel.com [132.233.42.126])
	by petasus.fm.intel.com (8.11.6p2/8.11.6/d: inner.mc,v 1.35 2003/05/22 21:18:01 rfjohns1 Exp $) with SMTP id h5IHvlX01435
	for <ietf@ietf.org>; Wed, 18 Jun 2003 17:57:47 GMT
Received: from FMSMSX017.fm.intel.com ([132.233.42.196])
 by fmsmsxvs041.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2003061811010906077
 ; Wed, 18 Jun 2003 11:01:09 -0700
Received: by fmsmsx017.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <MYJK8XZ8>; Wed, 18 Jun 2003 11:04:34 -0700
Message-ID: <FD2423AA68A7D511A5A20002A50729E10E1AF615@orsmsx115.jf.intel.com>
From: "Putzolu, David" <david.putzolu@intel.com>
To: "'Keith Moore'" <moore@cs.utk.edu>,
        "Hallam-Baker, Phillip"
	 <pbaker@verisign.com>
Cc: pbaker@verisign.com, Ronald.vanderPol@rvdp.org, aarsenau@bbn.com,
        ietf@ietf.org
Subject: RE: myth of the great transition (was US Defense Department forma
	 lly adopts IPv6)
Date: Wed, 18 Jun 2003 11:04:32 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

> NAT is a denial of service attack, not a means of policy enforcement.

I wonder if NAT is to ietf discussions as Nazis was 
to Usenet discussions.

That is, will every heated IETF debate eventually lead to
invoking the NAT bogyman?

And if that where to be true, would the corollary apply
that the discussion is no longer fruitful?

Cheers,
David



From owner-ietf@ietf.org  Wed Jun 18 15:46:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25396
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:46:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SiMJ-0005me-9B
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 15:12:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Si4j-0005zf-KB
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:54:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21301
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:54:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Si2T-0000Cv-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:52:09 -0400
Received: from tomts7.bellnexxia.net ([209.226.175.40] helo=tomts7-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Si2T-0000Cs-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:52:09 -0400
Received: from yahoo.com ([65.93.180.122]) by tomts7-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030618184501.DITA25372.tomts7-srv.bellnexxia.net@yahoo.com>;
          Wed, 18 Jun 2003 14:45:01 -0400
Date: Wed, 18 Jun 2003 14:45:00 -0400
Subject: Re: SIRs
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org, pekkas@netcore.fi
To: Bob Braden <braden@ISI.EDU>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <200306171617.JAA15141@gra.isi.edu>
Message-Id: <F7083F6E-A1BC-11D7-84BB-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Tuesday, June 17, 2003, at 12:17  PM, Bob Braden wrote:

>   *> Create a document-based thread rather than a WG-based or
>   *> mailing-list-based thread. Patches could also be posted and 
> revision
>   *> history (changes between revisions) would be easier to keep track 
> of.
>   *> People who have negative comments could post them, and they'd be 
> part
>   *> of the history record of the draft even if their comments are
>   *> ignored/rejected.
>   *>
>   *> simon

> I really wonder whether people have thought through the can of
> worms (Pandora's box) that you people may be opening...?  This is not
> to deny the need to improve the quality of some I-Ds and RFCs,
> goodness knows, but be careful of social consequences...

I've observed several bug-database oriented cultures, including the 
public mozilla bugzilla database. One interesting observation of 
bugzilla is that they do not permit referral from slashdot ... most 
obviously that would be to avoid the /. effect, but also, to avoid the 
kind of spamming effect that could occur if some influential person 
says "this thing at url XYZ is evil, go post a negative comment on it".

There is no reason otherwise, that the bugtracker would engender a 
reduced quality of discourse about an I-D. Since, the technical level 
of sophistication to read and understand an I-D would still be there, 
and the sophistication to post a message on a website is just as high 
as posting on a mailing list (and see the bugzilla page, they do make 
it difficult enough). Whereas, it would greatly help the situation 
where I read an I-D and think -- but wait, what about foo, they seem to 
have missed that -- and jump to the bugtracker and can easily find that 
the issue has already been raised and see if/what justifications are.

simon




From owner-ietf@ietf.org  Wed Jun 18 15:47:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21054
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 14:53:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ShQF-0003ih-7S
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 14:12:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sh8b-0003Mc-OY
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 13:54:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18517
	for <ietf@ietf.org>; Wed, 18 Jun 2003 13:54:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sh6L-0007Lt-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:52:05 -0400
Received: from ip166.usw12.rb1.bel.nwlink.com ([209.20.253.166] helo=ran.psg.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sh6L-0007Lq-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:52:05 -0400
Received: from localhost ([127.0.0.1] helo=ran.psg.com)
	by ran.psg.com with esmtp (Exim 4.20)
	id 19Sh8X-0007Gw-W3; Wed, 18 Jun 2003 10:54:22 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 18 Jun 2003 10:54:21 -0700
To: Vach Kompella <vkompella@timetra.com>
Cc: <ietf@ietf.org>
Subject: RE: WG review: Layer 2 Virtual Private Networks (l2vpn) 
References: <200306181718.AIN41035@mira-sjc5-c.cisco.com>
	<FNEFIPCNJKDDONJGBCNEAENDEBAA.vkompella@timetra.com>
Message-Id: <E19Sh8X-0007Gw-W3@ran.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> "We're doing it" is a statement of fact.  However, we've been
> doing it for over two years.  Pseudo-wire work has been ongoing
> for over 4 years.  MPLS has been ongoing since 1996 or
> thereabouts.

no disagreement.  the question i am hearing is not why is this
being done, but rather why is the ietf working on a an l2 over l2
protocol.  should we be doing frame over atm?  ether over atm?

randy




From owner-ietf@ietf.org  Wed Jun 18 15:47:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21553
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 14:56:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ShQG-0003kb-UD
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 14:12:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19ShMI-0003Xo-Sk
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:08:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19041
	for <ietf@ietf.org>; Wed, 18 Jun 2003 14:08:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShK2-0007UH-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:06:15 -0400
Received: from gull.mail.pas.earthlink.net ([207.217.120.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ShK2-0007UE-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:06:14 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19ShME-00069F-00; Wed, 18 Jun 2003 11:08:30 -0700
Date: Wed, 18 Jun 2003 14:05:38 -0400
From: Keith Moore <moore@cs.utk.edu>
To: EKR <ekr@rtfm.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030618140538.103ea88b.moore@cs.utk.edu>
In-Reply-To: <kj1xxrmfln.fsf@romeo.rtfm.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > similarly, people who install NAT usually don't realize how much this
> > costs them in lost functionality and reliability.
> Really? You have evidence of this?

the evidence I have is from reading vendor advertisements for NAT boxes,
and from talking to people who run networks that use NAT.  it's not 
a random sample, perhaps not a statistically significant one, but it's
been enough to convince me personally that the delusion is widespread.

> I don't either, but my intuition is that you're wrong.  Once you have
> decided to have a firewall in place (which you may think is evil, but
> I consider pretty much a necessary evil), I suspect that most people
> suffer almost not at all from having a NAT.

depends on what you mean by "firewall"  (which these days is a pretty
vague term).  but there are several primary effects of NAT - one being
that addresses are not maintained end-to-end, another being that NATs
cause address-to-host bindings to be ephemeral when they would otherwise
not be, and another being that (for NAPTs anyway) attempts to initiate
traffic across the NAPT are blocked in one direction.  there is rarely
a significant benefit in a firewall doing the first two of these.  a good
firewall has the capability to block traffic in either direction, or not, on a
case-by-case basis, and can be adjusted according to the needs of its users. 




From owner-ietf@ietf.org  Wed Jun 18 15:47:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21049
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 14:53:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19ShQF-0003iR-0o
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 14:12:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sh89-0003MW-If
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 13:53:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18498
	for <ietf@ietf.org>; Wed, 18 Jun 2003 13:53:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sh5t-0007LU-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:51:37 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sh5s-0007LG-00
	for ietf@ietf.org; Wed, 18 Jun 2003 13:51:37 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id C4090ABB5; Wed, 18 Jun 2003 10:59:32 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: pbaker@verisign.com, Ronald.vanderPol@rvdp.org, aarsenau@bbn.com,
        ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 18 Jun 2003 10:59:32 -0700
In-Reply-To: <20030618134424.410d29d1.moore@cs.utk.edu>
Message-ID: <kj1xxrmfln.fsf@romeo.rtfm.com>
Lines: 35
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> > > NAT is a denial of service attack, not a means of policy enforcement.
> > 
> > I don't think this is really accurate.
> > 
> > The difference between denial of service and policy enforcement
> > is primarily a question of authorization. Since the people who
> > install NAT generally own the networks in question, characterizing
> > NAT as a DoS attack doesn't really seem right.
> 
> people who run virus-laden programs are doing so because they want the
> advertised functionality of that program, not because they want to infect
> their systems or spread the virus.   people who use Microsoft mail readers do
> so because they want to read mail, not because they want to expose their
> systems to attack.
Yes, I totally agree with that. What's your point?

> similarly, people who install NAT usually don't realize how much this
> costs them in lost functionality and reliability.
Really? You have evidence of this?

I don't either, but my intuition is that you're wrong.  Once you have
decided to have a firewall in place (which you may think is evil, but
I consider pretty much a necessary evil), I suspect that most people
suffer almost not at all from having a NAT.

> perhaps DoS isn't quite the right term, but it's not far off.
I'm not sold.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Wed Jun 18 15:47:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25653
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:47:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SiZ4-00005f-4X
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 15:25:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Si7s-0007AW-Bz
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 14:57:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21713;
	Wed, 18 Jun 2003 14:57:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Si5b-0000Jw-00; Wed, 18 Jun 2003 14:55:23 -0400
Received: from webmail.movaz.com ([65.205.166.188] helo=jera.movaz.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Si5Y-0000HB-00; Wed, 18 Jun 2003 14:55:22 -0400
Received: from BLIULAPTOP (unknown [172.16.24.104])
	by jera.movaz.com (Postfix) with SMTP
	id D5EB517D2; Wed, 18 Jun 2003 14:56:51 -0400 (EDT)
Message-ID: <0aa001c335cb$610e5bb0$681810ac@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: <iesg@ietf.org>, <ietf@ietf.org>
Cc: <mpls@UU.NET>
References: <E19Qspn-0000Rd-3H@asgard.ietf.org> <07b701c331f1$ffeeb820$681810ac@movaz.com>
Subject: Re: Last Call: LDP DoD Graceful Restart to Draft Standard 
Date: Wed, 18 Jun 2003 14:56:51 -0400
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-ietf@ietf.org
Precedence: bulk

Did anyone decide there was an error here, or is this draft really in IETF last
call?

Thanks
Adrian
----- Original Message -----
From: "Adrian Farrel" <afarrel@movaz.com>
To: <iesg@ietf.org>; <ietf@ietf.org>
Cc: <mpls@UU.NET>
Sent: Friday, June 13, 2003 5:23 PM
Subject: Re: Last Call: LDP DoD Graceful Restart to Draft Standard


> With respect, this draft doesn't appear to have been through WG last call
> (unless I was sleeping, but I can't find any reference in the mail archive).
>
> It was only published as a WG draft on 5/7/2003 (despite carrying a date of
> February 2003).
>
> While I support the draft, I would like to see it discussed on the mailing
list
> and go through WG last call.
>
> Thanks,
> Adrian
>
> ----- Original Message -----
> From: "The IESG" <iesg-secretary@ietf.org>
> To: <IETF-Announce: ;>
> Cc: <mpls@UU.NET>
> Sent: Friday, June 13, 2003 1:59 PM
> Subject: Last Call: LDP DoD Graceful Restart to Draft Standard
>
>
> > ---------------
> > The IESG has received a request from Multiprotocol Label Switching to
> > consider the following Internet-Draft(s) as Draft Standard.
> > o Multiprotocol Label Switching (MPLS): LDP DoD Graceful Restart
> >   <draft-ietf-mpls-ldp-dod-restart-00.txt>
> >   Draft Standard
> >
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action.  Please send any comments to the
> > iesg@ietf.org or ietf@ietf.org mailing lists by .
> >
> > Files can be obtained via
> > http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-dod-restart-00.txt
> >
>
>





From owner-ietf@ietf.org  Wed Jun 18 15:56:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26085
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:56:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SiZ5-00008c-07
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 15:25:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SiBh-0000zY-Ex
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 15:01:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22005
	for <ietf@ietf.org>; Wed, 18 Jun 2003 15:01:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Si9R-0000O9-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:59:21 -0400
Received: from tomts16.bellnexxia.net ([209.226.175.4] helo=tomts16-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Si9Q-0000O6-00
	for ietf@ietf.org; Wed, 18 Jun 2003 14:59:20 -0400
Received: from yahoo.com ([65.93.180.122]) by tomts16-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030618190139.CACS26560.tomts16-srv.bellnexxia.net@yahoo.com>
          for <ietf@ietf.org>; Wed, 18 Jun 2003 15:01:39 -0400
Date: Wed, 18 Jun 2003 15:01:39 -0400
Subject: Re: myth of the great transition
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: S Woodside <sbwoodside@yahoo.com>
To: ietf@ietf.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <20030618140538.103ea88b.moore@cs.utk.edu>
Message-Id: <4AB1FDC0-A1BF-11D7-84BB-000393414368@yahoo.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


>> Once you have
>> decided to have a firewall in place (which you may think is evil, but
>> I consider pretty much a necessary evil)

If by firewall, you mean "a box that can perform policy enforcement" 
then I don't think that many people in the IETF would think that's an 
evil thing. The problem is more that the general public seems to 
conflate firewall and NAT. Perhaps a new word is needed for "a box that 
can perform policy enforcement".

simon

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Wed Jun 18 15:58:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26242
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 15:58:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SiZ5-000091-CW
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 15:25:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SiCi-00028r-CE
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 15:02:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22060
	for <ietf@ietf.org>; Wed, 18 Jun 2003 15:02:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SiAS-0000P9-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:00:24 -0400
Received: from sj-core-3.cisco.com ([171.68.223.137])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SiAR-0000Oo-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:00:23 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h5IJ22Tr016887;
	Wed, 18 Jun 2003 12:02:03 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AFF03858;
	Wed, 18 Jun 2003 12:02:00 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id MAA06766; Wed, 18 Jun 2003 12:02:00 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16112.46888.181090.757189@thomasm-u1.cisco.com>
Date: Wed, 18 Jun 2003 12:02:00 -0700 (PDT)
To: EKR <ekr@rtfm.com>
Cc: Keith Moore <moore@cs.utk.edu>, pbaker@verisign.com,
        Ronald.vanderPol@rvdp.org, aarsenau@bbn.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
In-Reply-To: <kj1xxrmfln.fsf@romeo.rtfm.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric Rescorla writes:
 > Keith Moore <moore@cs.utk.edu> writes:
 > > similarly, people who install NAT usually don't realize how much this
 > > costs them in lost functionality and reliability.
 > Really? You have evidence of this?
 > 
 > I don't either, but my intuition is that you're wrong.  Once you have
 > decided to have a firewall in place (which you may think is evil, but
 > I consider pretty much a necessary evil), I suspect that most people
 > suffer almost not at all from having a NAT.

I think Keith's point is that most people don't
realize what voodoo their box is doing until
something doesn't work. And then it just doesn't
work because it doesn't work. It's an attack of
engineering cynicism.

	     Mike



From owner-ietf@ietf.org  Wed Jun 18 16:02:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26468
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 16:02:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SiZ5-0000AB-SD
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 15:25:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SiFV-0003Wm-Ah
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 15:05:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22377
	for <ietf@ietf.org>; Wed, 18 Jun 2003 15:05:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SiDF-0000Qb-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:03:17 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SiDE-0000QE-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:03:16 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 5DC60ABB5; Wed, 18 Jun 2003 12:11:12 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
	<kju1ankzkr.fsf@romeo.rtfm.com>
	<20030618144239.0c31eb88.moore@cs.utk.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 18 Jun 2003 12:11:12 -0700
In-Reply-To: <20030618144239.0c31eb88.moore@cs.utk.edu>
Message-ID: <kjptlbkxpr.fsf@romeo.rtfm.com>
Lines: 43
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> > > the evidence I have is from reading vendor advertisements for NAT
> > > boxes, and from talking to people who run networks that use NAT. 
> > > it's not a random sample, perhaps not a statistically significant
> > > one, but it's been enough to convince me personally that the
> > > delusion is widespread.
> >
> > You can perhaps understand why I wouldn't consider this a particularly
> > convincing line of argument.
> 
> of course.  but you can perhaps understand why I don't consider your 
> intiution to the contrary convincing either?

Yes, but I'm not the one calling widely sold and deployed network
devices "Denial of service attacks". 


> depends on the people.  the people I work with want to run large-scale
> distributed computing problems.  other people want to use SIP to support
> internet telephony or for some other purpose.  others want to use
> IPsec...  yes there are workarounds for many of these, but they have to
> be invented on a case-by-case basis, and often they're expensive.
I don't know enough about how you're doing your distributing computing
to have an opinion, but as for the other two... In my experience,
IT managers are pretty unhappy punching holes in their firewalls
for incoming SIP and IPsec, whether they run NAT or not. I'm
not sure that NAT is much of an impediment in these cases.

The bottom line here is what economists call "revealed preference".
People buy NATs and install them. I suppose it's possible that all
those people are stupid and the marginal utility of a NAT box is
actually negative, but that seems like a claim that would require some
pretty strong evidence.

-Ekr


-- 
[Eric Rescorla                                   ekr@rtfm.com]
           Web Log: http://www.rtfm.com/movabletype





From owner-ietf@ietf.org  Wed Jun 18 16:08:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26782
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 16:08:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SiiN-00017a-Hu
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 15:35:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SiJA-0004ei-GJ
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 15:09:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22946
	for <ietf@ietf.org>; Wed, 18 Jun 2003 15:09:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SiGu-0000UB-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:07:04 -0400
Received: from tomts16.bellnexxia.net ([209.226.175.4] helo=tomts16-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SiGt-0000U8-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:07:03 -0400
Received: from yahoo.com ([65.93.180.122]) by tomts16-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030618190922.CHYX26560.tomts16-srv.bellnexxia.net@yahoo.com>;
          Wed, 18 Jun 2003 15:09:22 -0400
Date: Wed, 18 Jun 2003 15:09:23 -0400
Subject: Re: myth of the great transition
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "ietf@ietf.org" <ietf@ietf.org>
To: John C Klensin <john-ietf@jck.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <54469623.1055804734@p3.JCK.COM>
Message-Id: <5F0F414E-A1C0-11D7-84BB-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Monday, June 16, 2003, at 11:05  PM, John C Klensin wrote:

> small enterprise and SOHO multihoming may turn out to be one of the 
> driving applications for IPv6. If we get our act sufficiently 
> together...

Absolutely. This and the peer2peer advantages sound to me like the most 
obvious drivers for v6 adoption.

The only problem with the p2p is the risk that the 
RIAA/MPAA/evilcopyrightholders will brand IPv6 as a bad technology 
that's contributing to infringement ;-)

simon

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Wed Jun 18 16:13:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27080
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 16:13:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sis5-0001y1-98
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 15:45:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SiVF-0007q1-PK
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 15:21:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24060
	for <ietf@ietf.org>; Wed, 18 Jun 2003 15:21:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SiSz-0000dj-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:19:33 -0400
Received: from tnt.isi.edu ([128.9.128.128])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SiSz-0000dg-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:19:33 -0400
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6p2/8.11.2) with ESMTP id h5IJLpi07637;
	Wed, 18 Jun 2003 12:21:51 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.9.3/8.8.6) id MAA15517;
	Wed, 18 Jun 2003 12:17:05 -0700 (PDT)
Date: Wed, 18 Jun 2003 12:17:05 -0700 (PDT)
Message-Id: <200306181917.MAA15517@gra.isi.edu>
To: moore@cs.utk.edu
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

  *> 
  *> > If you want to address denial of service issues you need protocol
  *> > enforcement points.
  *> 
  *> NAT is a denial of service attack, not a means of policy enforcement.
  *> 
  *> 
  *> 

Keith,

I think it would be more accurate to say that a NAT contravenes
the basic Internet prnciple of universal connectivity.

Since 1980 we have believed that universal connectivity was one of the
great achievements of the Internet design.  Today, one must
unfortunately question whether universal connectivity can be sustained
(or is even the right goal) in a networking environment without
universal trust.  Maybe NATs are, in fact, a result of a very deep
problem with our architecture.  If you accept that, then there is no
point in attacking NATs until you can propose a better architectural
solution to the trust problem (hopefully, there will be one!)

Bob Braden





From owner-ietf@ietf.org  Wed Jun 18 16:15:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27293
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 16:15:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SjBj-0004iP-7P
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 16:05:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SigG-00015x-Kq
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 15:33:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24840
	for <ietf@ietf.org>; Wed, 18 Jun 2003 15:33:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sie0-0000r8-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:30:56 -0400
Received: from sj-core-3.cisco.com ([171.68.223.137])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sidz-0000r2-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:30:55 -0400
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h5IJVvTr002515;
	Wed, 18 Jun 2003 12:31:57 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AIN63758;
	Wed, 18 Jun 2003 12:31:56 -0700 (PDT)
Message-Id: <200306181931.AIN63758@mira-sjc5-c.cisco.com>
To: Scott W Brim <swb@employees.org>, ietf@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
In-Reply-To: Message from swb@employees.org
   of "Wed, 18 Jun 2003 14:16:02 EDT." <20030618181602.GL2044@sbrim-w2k01> 
Date: Wed, 18 Jun 2003 15:31:56 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

> The IETF does continue to have an emphasis on connectionless,
> packet-oriented delivery.  That's our fundamental architecture, without
> question.  In the meantime there are customers who want to transition to
> c, p-o d but need mechanisms for doing so.

Personally I'd find this proposal more compelling if it
were being presented as being oriented towards transitional
mechanisms.  We're seeing circuit-y proposals show up in
other working groups and I'm concerned that these reflect a
shift in basic assumptions about the characteristics of the
underlying network, at least among a non-trivial number of
participants.  

As a process kind of thing, I'm also concerned about the
growth of the "temporary" sub-IP area, so I think there are
issues here with both the work itself and in how the IETF
goes about taking on and structuring its work.

Melinda



From owner-ietf@ietf.org  Wed Jun 18 16:24:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27687
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 16:24:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SjBj-0004if-K6
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 16:05:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SigY-000163-NL
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 15:33:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24859
	for <ietf@ietf.org>; Wed, 18 Jun 2003 15:33:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SieI-0000rR-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:31:14 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SieI-0000rO-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:31:14 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5IJXUN09530;
        Wed, 18 Jun 2003 15:33:30 -0400 (EDT)
Date: Wed, 18 Jun 2003 15:33:29 -0400
From: Keith Moore <moore@cs.utk.edu>
To: EKR <ekr@rtfm.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030618153329.4fe1ab1c.moore@cs.utk.edu>
In-Reply-To: <kjptlbkxpr.fsf@romeo.rtfm.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
	<kju1ankzkr.fsf@romeo.rtfm.com>
	<20030618144239.0c31eb88.moore@cs.utk.edu>
	<kjptlbkxpr.fsf@romeo.rtfm.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > of course.  but you can perhaps understand why I don't consider your
> > 
> > intiution to the contrary convincing either?
> 
> Yes, but I'm not the one calling widely sold and deployed network
> devices "Denial of service attacks". 

Just for comparison against Phil's use of the term.  It's not how I
normally describe them (though I'm not exactly glowing in my praise...)

> I don't know enough about how you're doing your distributing computing
> to have an opinion, but as for the other two... In my experience,
> IT managers are pretty unhappy punching holes in their firewalls
> for incoming SIP and IPsec, whether they run NAT or not.

In my experience, IT managers are generally pretty unhappy changing
anything to support their users.  People who actually use the computers
or the network are regarded as a nuisance.

> The bottom line here is what economists call "revealed preference".

Maybe "revealed ignorance" would be a better term.  Though I prefer
"unintended consequence".

Keith



From owner-ietf@ietf.org  Wed Jun 18 16:28:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27973
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 16:28:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SjGe-0005FW-UA
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 16:10:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SilA-0001WV-MA
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 15:38:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25074
	for <ietf@ietf.org>; Wed, 18 Jun 2003 15:38:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Siiu-0000vf-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:36:00 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Siit-0000ud-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:35:59 -0400
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h5IJblUm017523;
	Wed, 18 Jun 2003 12:37:47 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AIN64606;
	Wed, 18 Jun 2003 12:37:46 -0700 (PDT)
Message-Id: <200306181937.AIN64606@mira-sjc5-c.cisco.com>
To: EKR <ekr@rtfm.com>, ietf@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Your message of "18 Jun 2003 11:31:00 PDT."
             <kju1ankzkr.fsf@romeo.rtfm.com> 
Date: Wed, 18 Jun 2003 15:37:46 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

> What applications that people want to run--and the IT managers would
> want to enable--are actually inhibited by NAT? It seems to me that
> most of the applications inconvenienced by NAT are ones that IT
> managers would want to screen off anyway.

Not really.  For example, ftp as originally defined doesn't
work through NATs, and no standard VoIP or multimedia
conferencing protocol works through NAT.  

What I think is a huge problem that people tend to be pretty
hand-wavy about is that many of the mechanisms that are
introduced to help complex applications work through NATs
introduce new security exposures, whether it's the
"pseudo-NAT attack" described by Dupont and that we've run
into with STUN, or external relays allowing internal users
to run unauthorized servers, or stateful inspection/rewrite
forcing application users not to use encryption or integrity
protection, or ...  NAT has a surprisingly wide ripple
effect that's almost completely negative.

Melinda



From owner-ietf@ietf.org  Wed Jun 18 16:32:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28217
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 16:32:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SjGf-0005Fx-Aj
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 16:10:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sim6-0001Wi-4o
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 15:39:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25143
	for <ietf@ietf.org>; Wed, 18 Jun 2003 15:39:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sijq-0000w0-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:36:58 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sijp-0000vx-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:36:57 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5IJdCN09535;
        Wed, 18 Jun 2003 15:39:13 -0400 (EDT)
Date: Wed, 18 Jun 2003 15:39:11 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Bob Braden <braden@ISI.EDU>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030618153911.49945ac0.moore@cs.utk.edu>
In-Reply-To: <200306181917.MAA15517@gra.isi.edu>
References: <200306181917.MAA15517@gra.isi.edu>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I think it would be more accurate to say that a NAT contravenes
> the basic Internet prnciple of universal connectivity.

well, if we're going to try to get accurate (or even precise) I'd
venture that the basic principle being contravened is not universal
connectivity, but separation of function between the network and the
endpoints - where the network's job is to make a best effort to deliver
packets to where the endpoints want them to go.  expecting the network
to isolate insecure hosts from untrustworthy attackers, or more
generally, to enforce policy about what kinds of content are
permitted to pass, has always been a stretch.  

Keith



From owner-ietf@ietf.org  Wed Jun 18 16:38:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28587
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 16:38:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SjHW-0005Ik-Go
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 16:11:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sis9-00021D-0z
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 15:45:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25348
	for <ietf@ietf.org>; Wed, 18 Jun 2003 15:45:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sips-0000zi-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:43:13 -0400
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sips-0000za-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:43:12 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0.6)
  with ESMTP-TLS id 242068; Wed, 18 Jun 2003 14:45:03 -0500
Message-ID: <3EF0C153.6030502@ehsco.com>
Date: Wed, 18 Jun 2003 14:45:23 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: EKR <ekr@rtfm.com>
CC: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>	<20030618130528.400b1f39.moore@cs.utk.edu>	<kj65n3mgdt.fsf@romeo.rtfm.com>	<20030618134424.410d29d1.moore@cs.utk.edu>	<kj1xxrmfln.fsf@romeo.rtfm.com>	<20030618140538.103ea88b.moore@cs.utk.edu> <kju1ankzkr.fsf@romeo.rtfm.com>
In-Reply-To: <kju1ankzkr.fsf@romeo.rtfm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 6/18/2003 1:31 PM Eric Rescorla wrote:

> What applications that people want to run--and the IT managers would 
> want to enable--are actually inhibited by NAT? It seems to me that most
> of the applications inconvenienced by NAT are ones that IT managers
> would want to screen off anyway.

Oracle and H.323 have both been historically problematic, and are both
reasonable applications. Home users also suffer a lot with perfectly
innocent services like games. Ignoring the rifle-shot arguments, requiring
an application to be rebuilt or that a middlebox learn to ~emulate an
active end-point are both miserable choices, and generally unnecessary.

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




From owner-ietf@ietf.org  Wed Jun 18 16:39:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28686
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 16:39:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SjHY-0005Pq-No
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 16:11:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SiyG-00037Z-Dn
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 15:51:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25888
	for <ietf@ietf.org>; Wed, 18 Jun 2003 15:51:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Siw0-00019L-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:49:32 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sivz-00019I-00
	for ietf@ietf.org; Wed, 18 Jun 2003 15:49:31 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5IJpmN09576;
        Wed, 18 Jun 2003 15:51:49 -0400 (EDT)
Date: Wed, 18 Jun 2003 15:51:48 -0400
From: Keith Moore <moore@cs.utk.edu>
To: james woodyatt <jhw@wetware.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: NAT box spec? (RE: myth of the great transition)
Message-Id: <20030618155148.5906fb79.moore@cs.utk.edu>
In-Reply-To: <74E08DEB-A1B4-11D7-A096-000393BA7EBA@wetware.com>
References: <444710000.1055915734@askvoll.hjemme.alvestrand.no>
	<74E08DEB-A1B4-11D7-A096-000393BA7EBA@wetware.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> When customers of retail Internet service start demanding a NAT 
> standard, then that's when the IETF might want to think about 
> documenting the standard that the market seems to want.  

here's the only thing that a NAT standard should say:

an intermediary MUST NOT alter the source or destination field in an IP
header.

an intermediary MUST NOT route an IP packet to other than its intended
destination.

an intermediary MUST NOT alter the payload of an IP packet.




From owner-ietf@ietf.org  Wed Jun 18 16:42:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28972
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 16:42:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SjVJ-0006oi-1S
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 16:26:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SjCW-0004jK-TU
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 16:06:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26710
	for <ietf@ietf.org>; Wed, 18 Jun 2003 16:06:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SjAG-0001MN-00
	for ietf@ietf.org; Wed, 18 Jun 2003 16:04:16 -0400
Received: from [64.47.48.7] (helo=exchange.timetra.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SjAF-0001M9-00
	for ietf@ietf.org; Wed, 18 Jun 2003 16:04:15 -0400
Received: from vkompella ([64.47.48.10] RDNS failed) by exchange.timetra.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 18 Jun 2003 13:06:03 -0700
Reply-To: <vkompella@timetra.com>
From: "Vach Kompella" <vkompella@timetra.com>
To: "Kurt Erik Lindqvist" <kurtis@kurtis.pp.se>
Cc: "Pekka Savola" <pekkas@netcore.fi>,
        "Harald Tveit Alvestrand" <harald@alvestrand.no>, <ietf@ietf.org>
Subject: RE: WG review: Layer 2 Virtual Private Networks (l2vpn)
Date: Wed, 18 Jun 2003 13:06:46 -0700
Message-ID: <FNEFIPCNJKDDONJGBCNEGENIEBAA.vkompella@timetra.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <45712F09-A1BC-11D7-9791-000393A638B2@kurtis.pp.se>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
X-OriginalArrivalTime: 18 Jun 2003 20:06:03.0876 (UTC) FILETIME=[0BCC7240:01C335D5]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> >
> > If you use LDP, it is NOT a routing protocol.  The specific mode of use
> > (targeted LDP) is already described in RFC 3036.  The FECs are
> > different, but
> > the FEC TLV was defined in such a way as to be extensible.
>
> And when you want to do this inter-domain? Everything else seems to
> have made it's way into BGP so I think that Pekkas concerns are valid...

That's only because the IETF hasn't made security easy enough, light enough, or
something.  Now some people use the argument that everything should go into BGP
because "opening another port into the provider network is a security breach."
Why is port 646 (LDP) any more insecure than port 179 (BGP)?

>
> >>  - we must not create complexity by deploying ethernet bridging all
> >> over
> >> the Internet.  Our work should be focused on making IP work, not
> >> specifying Ethernet-over-IP (or worse, Ethernet-over-IP as a
> >> *service*).
> >>
> >
> > Primarily, folks want to use it as in "Ethernet-over-MPLS".  That may
> > not
> > necessarily go down well with you either, but think of MPLS as a
> > logical FR.
> > Providers do not want to change their infrastructure, e.g., replace a
> > FR cloud
> > with an ATM cloud, then with SONET or GigE.  That's mega-expensive.  By
> > abstracting the L2 using MPLS, they can provide the L2VPN service
> > without
> > wholesale infrastructure replacement.
>
> Most of these providers have bought what their vendor told them to buy,
> but let's not go into that here.
>

Sheesh!  No, let's go there.  You're talking about my potential customers, and I
want to know if they really are so dense that I shouldn't have been spending all
this time working on a protocol - I could have just given them a couple of
high-priced tin cans and a piece of string.

Who exactly the IETF is going to be providing protocols for?  For protocols such
as these, it is the providers who deploy them.  You claim that most of the
providers have little or no discernment.  Let's give credit to the providers.
There are a large number of them who know what they are doing.  Many of them
participate in the standards.

> >
> >>  - it is architecturally wrong: use different subnets, period --
> >> that's
> >> what those are meant for in the first place!
> >
> > Use different subnets to create VPNs?  I don't understand what you
> > mean.  VPLS
> > and VPWS address a requirement for multiple domains (aka VPNs),
> > logically
> > distinct from and invisible to each other.
>
> Pekka is right in that most of the applications of VPNs today could
> actually be solved as good with "real addresses" and routing across
> networks.

You probably haven't read the requirements documents then.

>
> >> Btw. how is this different from currently-specified GRE tunneling?  It
> >> being made a "service"?
> >
> > GRE-tunneling is one option, but only for the transport of the VC.
> > However, you
> > need a demux field to identify the VC that you are carrying.  Carrying
> > one
> > customer VC between a pair of PEs is obviously not adequate.
>
> L2TPv3? Whats the advantage with this over the existing protocol that
> the IETF have?
>
> > - kurtis -
>

-Vach





From owner-ietf@ietf.org  Wed Jun 18 16:58:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29486
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 16:58:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SjqQ-0000fp-NK
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 16:47:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sjaa-0007JM-9S
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 16:31:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28183
	for <ietf@ietf.org>; Wed, 18 Jun 2003 16:31:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SjYK-0001kj-00
	for ietf@ietf.org; Wed, 18 Jun 2003 16:29:08 -0400
Received: from [64.47.48.7] (helo=exchange.timetra.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SjYJ-0001kF-00
	for ietf@ietf.org; Wed, 18 Jun 2003 16:29:07 -0400
Received: from vkompella ([64.47.48.10] RDNS failed) by exchange.timetra.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 18 Jun 2003 13:30:55 -0700
Reply-To: <vkompella@timetra.com>
From: "Vach Kompella" <vkompella@timetra.com>
To: "Paul Hoffman / VPNC" <paul.hoffman@vpnc.org>, <ietf@ietf.org>
Subject: RE: WG review: Layer 2 Virtual Private Networks (l2vpn)
Date: Wed, 18 Jun 2003 13:31:38 -0700
Message-ID: <FNEFIPCNJKDDONJGBCNEIENJEBAA.vkompella@timetra.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <p05210606bb1655fef91b@[67.126.41.36]>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
X-OriginalArrivalTime: 18 Jun 2003 20:30:55.0813 (UTC) FILETIME=[850FF750:01C335D8]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul,

>
> At 10:15 AM +0200 6/18/03, Harald Tveit Alvestrand wrote:
> >I can think of some possible reasons, not necessarily exclusive
> >
> >- this is a bad idea/impossible to do well, so we shouldn't do it
> >- some other organization is already doing it, so we shouldn't
> >- we're too stupid to get it right, so we shouldn't do it
> >- the IETF is too large, so we shouldn't be adding more work
>
> This might be a combination of the latter three, but I think it is
> clearer for this WG:
>
> - the IETF's track record for this work so far is quite poor
>

That's not a problem of the ppvpn group only.  It is a problem of the IETF.

I don't need to refresh your memory about IPSec, do I?  SKIP, Skeme, Oakley,
IKE.  AH or ESP with auth?  5 years of bloody fighting.

It's wherever the action is that the political jostling for position is the most
prominent.  That's also where the leadership needs to be strong and participants
need to have a "nose to the grindstone" attitude.  That's hardly an indication
that the work should not be chartered or worked upon.

> We have not shown any ability to create standards in this area with
> due speed or predictability. We have not shown the good judgement
> needed to limit the scope of the work we do. (Look at the number of
> L2VPN-based Working Group drafts in PWE3 and PPVPN, much less the
> large number of non-WG documents being actively discussed.

Do you think the new L2VPN charter addresses these concerns of scoping?  How
about the timelines?  Basically, it's going to be a WG issue, chairs and
participants, to finish the WG charter items first.

>
> The IETF understands the need for layer 2 technologies for OAM much
> better than we understand the Internet customer's need (or even
> concern) for layer 2 transport of their IP packets. This is because
> we have a tighter relationship with operators than we do with
> Internet users, and because Internet users generally could care less
> about how their ISPs move their traffic as long as they meet the
> service level agreements. The ISPs would love to have better
> cross-vendor interop for the L2VPN technologies, but so far the
> vendors haven't had time to think about that because they have been
> overloaded with the literally dozens of flavors that are being
> discussed in the IETF.

Are you talking PWE3 or L2VPN?

The gazillion drafts is in PWE3.  The interop issues are localized to the drafts
with contention, silly issues of where bits should go.

There are 16 pseudowire types:
           0x0001   Frame Relay DLCI
           0x0002   ATM AAL5 SDU VCC transport
           0x0003   ATM transparent cell transport
           0x0004   Ethernet Tagged Mode
           0x0005   Ethernet
           0x0006   HDLC
           0x0007   PPP
           0x0008   SONET/SDH Circuit Emulation Service Over MPLS (CEM) [8]
           0x0009   ATM n-to-one VCC cell transport
           0x000A   ATM n-to-one VPC cell transport
           0x000B   IP Layer2 Transport
           0x000C   ATM one-to-one VCC Cell Mode
           0x000D   ATM one-to-one VPC Cell Mode
           0x000E   ATM AAL5 PDU VCC transport
           0x000F   Frame-Relay Port mode
           0x0010   SONET/SDH Circuit Emulation over Packet (CEP)

At least half of these are and have been interoperable.  It is the harder (and
more arcane, IMHO) PW types that people are having a hard time coming to some
sort of compromise.

BTW, I'm glad to see you have a healthier respect for providers than Kurtis who
claims that "most of these providers have bought what their vendor told them to
buy."

>
> We will never know if there is another organization who could do a
> better job than this because no other organization will take on the
> work while the 800-pound gorilla of standards bodies is flailing
> around in the area. There are certainly other organizations that can
> take it on, such as the MPLS and Frame Relay Alliance. They might do
> just as bad of a job as we have so far, but they could also do much
> better because they are much more focused.

An 800-pound gorilla conjures up images of one less nimble of foot.  IMHO, not
the right metaphor for the IETF.

>
> --Paul Hoffman, Director
> --VPN Consortium
>
>

-Vach





From owner-ietf@ietf.org  Wed Jun 18 17:10:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00193
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 17:10:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SjqT-0000jw-8y
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 16:47:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SjiK-00086g-KU
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 16:39:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28635
	for <ietf@ietf.org>; Wed, 18 Jun 2003 16:39:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sjg4-0001rj-00
	for ietf@ietf.org; Wed, 18 Jun 2003 16:37:08 -0400
Received: from [64.47.48.7] (helo=exchange.timetra.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sjg3-0001qm-00
	for ietf@ietf.org; Wed, 18 Jun 2003 16:37:07 -0400
Received: from vkompella ([64.47.48.10] RDNS failed) by exchange.timetra.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 18 Jun 2003 13:38:56 -0700
Reply-To: <vkompella@timetra.com>
From: "Vach Kompella" <vkompella@timetra.com>
To: "Melinda Shore" <mshore@cisco.com>, "Scott W Brim" <swb@employees.org>,
        <ietf@ietf.org>
Subject: RE: WG review: Layer 2 Virtual Private Networks (l2vpn) 
Date: Wed, 18 Jun 2003 13:39:39 -0700
Message-ID: <FNEFIPCNJKDDONJGBCNECENKEBAA.vkompella@timetra.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <200306181931.AIN63758@mira-sjc5-c.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
X-OriginalArrivalTime: 18 Jun 2003 20:38:56.0719 (UTC) FILETIME=[A3B465F0:01C335D9]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Melinda,

>
> As a process kind of thing, I'm also concerned about the
> growth of the "temporary" sub-IP area, so I think there are
> issues here with both the work itself and in how the IETF
> goes about taking on and structuring its work.

And proposals have been made to dismantle the SUBIP area and place the remaining
WGs in the most appropriate areas (some of them are pretty much done with their
chartered work).  The chartering of L2 and L3VPN WGs gives a little more focus,
and limits the solution space.

It's not the creation of the temporary SUBIP area that caused the growth of the
WGs.  It's the natural progression of the opportunities that MPLS provided that
led to the application WGs such as PWE3, PPVPN, etc.

>
> Melinda
>

-Vach





From owner-ietf@ietf.org  Wed Jun 18 17:27:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00800
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 17:27:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SkJG-0002DI-SQ
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 17:17:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SkIo-00020X-0t
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 17:17:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00524
	for <ietf@ietf.org>; Wed, 18 Jun 2003 17:17:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SkGX-0002Ow-00
	for ietf@ietf.org; Wed, 18 Jun 2003 17:14:49 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SkGX-0002Oo-00
	for ietf@ietf.org; Wed, 18 Jun 2003 17:14:49 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h5ILHbxS011271;
	Wed, 18 Jun 2003 23:17:37 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Wed, 18 Jun 2003 23:16:40 +0200
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: moore@cs.utk.edu, ietf@ietf.org
To: Bob Braden <braden@ISI.EDU>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200306181917.MAA15517@gra.isi.edu>
Message-Id: <27644537-A1D2-11D7-9C85-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, jun 18, 2003, at 21:17 Europe/Amsterdam, Bob Braden wrote:

> Since 1980 we have believed that universal connectivity was one of the
> great achievements of the Internet design.  Today, one must
> unfortunately question whether universal connectivity can be sustained
> (or is even the right goal) in a networking environment without
> universal trust.

I think we can safely say that 99.99% of all systems that run IP don't 
want to talk to 99.99% of all systems that run IP. For most people, 
with a network this large, universal connectivity isn't a goal but a 
threat. But this shouldn't be confused with universal addressability 
being undesirable, because this only gets more important as the size of 
the network increases.

> Maybe NATs are, in fact, a result of a very deep
> problem with our architecture.

Yes, that IP addresses are only 32 bits. So people decided to usurp the 
16 bit port number to create virtual 48 bit IP addresses.

> If you accept that, then there is no
> point in attacking NATs until you can propose a better architectural
> solution to the trust problem (hopefully, there will be one!)

What we need is a good way to limit access to systems. Firewalls look 
at addresses and port numbers, which are mostly meaningless. So people 
hide their boxes behind NATs and bastion hosts to gain some security. 
If we can solve this IPv6 will take care of the rest.




From owner-ietf@ietf.org  Wed Jun 18 17:56:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01581
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 17:56:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SkpW-000330-Bm
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 17:50:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SkYT-0002oj-1c
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 17:33:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01042
	for <ietf@ietf.org>; Wed, 18 Jun 2003 17:33:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SkWC-0002Xu-00
	for ietf@ietf.org; Wed, 18 Jun 2003 17:31:00 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SkWC-0002Xq-00
	for ietf@ietf.org; Wed, 18 Jun 2003 17:31:00 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h5ILWgwq010513;
	Wed, 18 Jun 2003 14:32:46 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AFF21318;
	Wed, 18 Jun 2003 14:32:42 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id OAA07333; Wed, 18 Jun 2003 14:32:42 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16112.55930.184521.866913@thomasm-u1.cisco.com>
Date: Wed, 18 Jun 2003 14:32:42 -0700 (PDT)
To: Bob Braden <braden@ISI.EDU>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
In-Reply-To: <200306181917.MAA15517@gra.isi.edu>
References: <200306181917.MAA15517@gra.isi.edu>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bob Braden writes:
 > Since 1980 we have believed that universal connectivity was one of the
 > great achievements of the Internet design.  Today, one must
 > unfortunately question whether universal connectivity can be sustained
 > (or is even the right goal) in a networking environment without
 > universal trust.  Maybe NATs are, in fact, a result of a very deep
 > problem with our architecture.  If you accept that, then there is no
 > point in attacking NATs until you can propose a better architectural
 > solution to the trust problem (hopefully, there will be one!)

I sort of wonder the same thing, but I don't draw
the major distinction with trust. In fact, NAT's
are lousy at that, unless you're talking about
NAT's qua ALG's. 

My big bugaboo here is whether the factors driving
people to want address space they control beyond
the illusion of NAT security -- mostly renumbering
immunity, IMO -- is so hard to counter with the
universal end to end model version of the world
(eg, IPv6) that addressing realms are a given and
need to be dealt with just like civil engineers
need to deal with politicians who want to put
busts of their likeness into the faces of dams,
etc.

I personally am not ready to give up on the
promise and architectural tidiness of e2e, but I
have to say as an engineer it's never a bad plan
to make certain the intertia of the world is kept
in mind. Systems which are "correct" but
undeployed are a dime a dozen in the ash heap of
history.

		Mike



From owner-ietf@ietf.org  Wed Jun 18 18:01:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01955
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 18:01:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SkqA-00035c-Rz
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 17:51:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sken-0002rE-Om
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 17:39:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01210
	for <ietf@ietf.org>; Wed, 18 Jun 2003 17:39:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SkcX-0002aQ-00
	for ietf@ietf.org; Wed, 18 Jun 2003 17:37:33 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SkcW-0002aN-00
	for ietf@ietf.org; Wed, 18 Jun 2003 17:37:32 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h5ILdotU006195;
	Wed, 18 Jun 2003 17:39:50 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h5ILdoQ4006194;
	Wed, 18 Jun 2003 17:39:50 -0400
Date: Wed, 18 Jun 2003 17:39:50 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200306182139.h5ILdoQ4006194@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

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

    > that's an oxymoron. the basic premis of NAT is fundamnetally broken.

Just out of interest, do you complain about gravity too?

We lost our chance to avoid NAT's when variable length addresses were removed
from TCPv2.5 (IIRC the version number correctly). NAT's are here, like it or
not, and the only question is how to make lemonade out of them. 

	Noel

PS: Speaking of gravity, does anyone have a copy of that great hack CMU memo
about how they were going to turn gravity off in the CS building on the
weekend to help everyone move offices?



From owner-ietf@ietf.org  Wed Jun 18 18:28:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03718
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 18:28:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sl5h-0007hy-Mh
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 18:07:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SkyQ-0003dw-3o
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 18:00:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01834
	for <ietf@ietf.org>; Wed, 18 Jun 2003 18:00:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Skw9-0002lY-00
	for ietf@ietf.org; Wed, 18 Jun 2003 17:57:49 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Skw8-0002lV-00
	for ietf@ietf.org; Wed, 18 Jun 2003 17:57:48 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5IM03N10337;
        Wed, 18 Jun 2003 18:00:04 -0400 (EDT)
Date: Wed, 18 Jun 2003 18:00:03 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Putzolu, David" <david.putzolu@intel.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030618180003.173167c1.moore@cs.utk.edu>
In-Reply-To: <FD2423AA68A7D511A5A20002A50729E10E1AF615@orsmsx115.jf.intel.com>
References: <FD2423AA68A7D511A5A20002A50729E10E1AF615@orsmsx115.jf.intel.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > NAT is a denial of service attack, not a means of policy
> > enforcement.
> 
> I wonder if NAT is to ietf discussions as Nazis was 
> to Usenet discussions.
> 
> That is, will every heated IETF debate eventually lead to
> invoking the NAT bogyman?

The national socialist party is (hopefully) a thing of the distant past.
NATs, OTOH, are very much still with us.

I think we often end up talking about NATs because NATs are a symptom
that our architecture has fundamental unsolved problems that we so far
have failed to address (or that the market has failed to adopt, but
it's closer to the former, I think.)

The SPAM problem is another one of those recurring discussions that
never seems to be resolved, for similar reasons.

If we had a workable solution in hand for either problem, there would be
little point in our talking about them.  As it is, we keep revisiting
them in the hope that some new idea will emerge, or that some bit of
denial about those problems will go away.

Keith



From owner-ietf@ietf.org  Wed Jun 18 18:30:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03870
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 18:30:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SlIi-0002CR-IQ
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 18:21:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sl0p-0005qU-Vg
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 18:02:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02075
	for <ietf@ietf.org>; Wed, 18 Jun 2003 18:02:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SkyZ-0002oW-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:00:19 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SkyY-0002oT-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:00:18 -0400
Received: from MOU1WNEXC03.verisign.com (verisign.com [65.205.251.57])
        by peacock.verisign.com (8.12.9/) with ESMTP id h5IM2Th6012748;
        Wed, 18 Jun 2003 15:02:29 -0700 (PDT)
Received: by mou1wnexc03.verisign.com with Internet Mail Service (5.5.2653.19)
	id <MLJJVPJN>; Wed, 18 Jun 2003 15:02:29 -0700
Message-ID: <2A1D4C86842EE14CA9BC80474919782E0D2255@mou1wnexm02.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Putzolu, David'" <david.putzolu@intel.com>,
        "'Keith Moore'"
	 <moore@cs.utk.edu>
Cc: "'Ronald.vanderPol@rvdp.org'" <Ronald.vanderPol@rvdp.org>,
        "'aarsenau@bbn.com'" <aarsenau@bbn.com>,
        "'ietf@ietf.org'"
	 <ietf@ietf.org>
Subject: RE: myth of the great transition (was US Defense Department forma
	 lly adopts IPv6)
Date: Wed, 18 Jun 2003 15:02:29 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

That is how we got here. Ignore it, hope it will go away.

What I am suggesting is that there is no reason nat had to reusult in being
on the interNOT rather than the internet.

Further folk are going to buy these and put them at the border of their home
networks. 

Trying to secure end point computers is futile. There will always be holes,
the attackers only need to own one percent of the internet to be able to
create havoc.

I note also that even though linux boxes are not a large percentage of net
they are prime targets for hackers. I suspect because they tend to be
connected to unrestircted dsl lines more often than capability limited cable
modems.

If I dot run a local mail server why should I let a machine have
unrestricted net access if it does not need it? Why allow one of my machines
to syn flood? Present a smaller prize to the hackers and you are less likely
to have severe problems.

End to end only security dogma is like saying buildings should be fireproof
and sprikler systems are evil and unnecessary



 -----Original Message-----
From: 	Putzolu, David
Sent:	Wed Jun 18 13:59:43 2003
To:	'Keith Moore'; Hallam-Baker, Phillip
Cc:	pbaker@verisign.com; Ronald.vanderPol@rvdp.org; aarsenau@bbn.com;
ietf@ietf.org
Subject:	RE: myth of the great transition (was US Defense Department
forma lly adopts IPv6)

> NAT is a denial of service attack, not a means of policy enforcement.

I wonder if NAT is to ietf discussions as Nazis was 
to Usenet discussions.

That is, will every heated IETF debate eventually lead to
invoking the NAT bogyman?

And if that where to be true, would the corollary apply
that the discussion is no longer fruitful?

Cheers,
David



From owner-ietf@ietf.org  Wed Jun 18 18:40:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04367
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 18:40:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SlP2-0002Oe-Hx
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 18:27:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SlIi-0002CQ-Fw
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 18:21:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03587
	for <ietf@ietf.org>; Wed, 18 Jun 2003 18:21:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SlGR-0002vP-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:18:48 -0400
Received: from fmr02.intel.com ([192.55.52.25] helo=caduceus.fm.intel.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SlGR-0002vL-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:18:47 -0400
Received: from petasus.fm.intel.com (petasus.fm.intel.com [10.1.192.37])
	by caduceus.fm.intel.com (8.11.6p2/8.11.6/d: outer.mc,v 1.66 2003/05/22 21:17:36 rfjohns1 Exp $) with ESMTP id h5IMD0T23509
	for <ietf@ietf.org>; Wed, 18 Jun 2003 22:13:00 GMT
Received: from fmsmsxvs041.fm.intel.com (fmsmsxvs041.fm.intel.com [132.233.42.126])
	by petasus.fm.intel.com (8.11.6p2/8.11.6/d: inner.mc,v 1.35 2003/05/22 21:18:01 rfjohns1 Exp $) with SMTP id h5IMEHv21322
	for <ietf@ietf.org>; Wed, 18 Jun 2003 22:14:17 GMT
Received: from FMSMSX016.fm.intel.com ([132.233.42.195])
 by fmsmsxvs041.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2003061815174026247
 ; Wed, 18 Jun 2003 15:17:40 -0700
Received: by fmsmsx016.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <MSY9YCBA>; Wed, 18 Jun 2003 15:21:04 -0700
Message-ID: <FD2423AA68A7D511A5A20002A50729E1105BAA1C@orsmsx115.jf.intel.com>
From: "Putzolu, David" <david.putzolu@intel.com>
To: "'Keith Moore'" <moore@cs.utk.edu>,
        "Putzolu, David"
	 <david.putzolu@intel.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: myth of the great transition (was US Defense Department forma
	 lly adopts IPv6)
Date: Wed, 18 Jun 2003 15:21:03 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

The IAB has talked about NAT.  A WG has produced a bunch of
RFCs about NAT.  NAT is very widely deployed and comes in
10 different flavors.  NAT has a bunch of architectural 
ugliness and technical problems.  So?

How about some lemonade?  An Internet draft that says 
something new about NATs would be a lot more helpful than 
rehashing the same old arguments.

Cheers,
David


> I think we often end up talking about NATs because NATs are a symptom
> that our architecture has fundamental unsolved problems that we so far
> have failed to address (or that the market has failed to adopt, but
> it's closer to the former, I think.)
> 
> The SPAM problem is another one of those recurring discussions that
> never seems to be resolved, for similar reasons.
> 
> If we had a workable solution in hand for either problem, 
> there would be
> little point in our talking about them.  As it is, we keep revisiting
> them in the hope that some new idea will emerge, or that some bit of
> denial about those problems will go away.
> 
> Keith
> 



From owner-ietf@ietf.org  Wed Jun 18 19:08:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05109
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 19:08:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SlYf-0003Kb-Vp
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 18:37:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SlPj-0002Ok-NL
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 18:28:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03705
	for <ietf@ietf.org>; Wed, 18 Jun 2003 18:28:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SlNT-0002xw-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:26:03 -0400
Received: from smtp100.mail.sc5.yahoo.com ([216.136.174.138])
	by ietf-mx with smtp (Exim 4.12)
	id 19SlNS-0002xt-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:26:02 -0400
Received: from 212.68.224.51.brutele.be (HELO isoc) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 18 Jun 2003 22:28:20 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'S Woodside'" <sbwoodside@yahoo.com>
Cc: <ietf@ietf.org>
Subject: NATs are NOT Firewalls
Date: Thu, 19 Jun 2003 00:28:09 +0200
Organization: Internet Society
Message-ID: <008201c335e8$ea19f3c0$6f00a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <86E97E06-A1BB-11D7-84BB-000393414368@yahoo.com>
Importance: Normal
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA05109

First of all, for the purists : I apologize for this simplified explanation
of what firewalls are. I guess we could start a very long thread about
firewalls and NATs, but the idea is to give a (somewhat) short answer (maybe
over-simplified) to some short questions asked by Simon Woodside (see
bottom).
-------------

There is not ONE firewall. A firewall is not a product, it's more like a
concept. The idea of a firewall is to build a protecting wall between an
external (public) network and an internal (private) network, by granting or
denying incoming/outgoing packets based on specified/configured
rules/policies. In the real world, there are different kinds of firewalls.

Compared to the OSI or TCP/IP layers, firewalls can work at different
layers.

There are mainly :
1.packet filters (analyze the IP packet and identify the IP addresses and
port numbers, then apply a set of rules),
2.circuit level gateways (work mainly at session layer, by identifying flows
of data and established connections),
3.application level gateways or proxies (application specific : http, ftp,
telnet,... with possible extended features, like caching possibilities,
logging of user activity,...), and
4.stateful inspection firewalls (more recent, combinations of types 1. 2.
and 3., more performant than 1. and 2., less complex than 3.).

A simple router, using access lists based on the IP addresses, analyzing
each packet one by one, is a basic firewall of type 1.
A more advanced device, able to identify "conversations", "sessions", is a
bit more advanced firewall of type 2.
A complex software, configured to analyze the addresses, the port numbers,
the protocols in use, possibly the contents of the applications data, is a
very complex firewall of type 3.

A basic router (not a firewall) will "transparently" interconnect different
networks, maintain routing tables, and advertise those tables to its
neighbors.
A NAT will "mask" the internal addresses, only maintain its own private
translation table, and not transmit it to any other device.

A Network Address Translator will usually translate "n" public, official IP
addresses into "n" private, internal IP addresses and keep the current port
numbers unchanged.
A Network Address and Port Translator will usually translate ONE public,
official IP address into SEVERAL private, internal IP addresses by
translating the external port numbers to correspond to the different
internal combinations of <network address + port> (external packets will
only transport ONE IP address - the public, official one).

Pure NATs will only translate network addresses. PATs and NAPTs will
translate port numbers, too. In no case will any of them translate the
protocols - that would prevent clients and servers from understanding each
other (a web client with a telnet server, etc.).

NATs will mask the internal addresses from outside view, but won't use
policies, control the traffic, perform authentication, or prevent spoofing :
NATs ARE NOT FIREWALLS!!!

On the other hand, circuit level gateways and application level gateways
transparently perform address translation!!! The addresses of the internal,
private network are masked from outside view!
Packet filters and stateful inspection firewalls don't translate IP
addresses and port numbers.

So, in short :
1/ a NAT is not equal to a firewall, it's not a firewall! Some firewalls DO
perform Network Address Translation, but NATs DO NOT perform firewalling!
2/ the main, primary purpose of a NAT is to use a limited set of public
(external) IP addresses and make them correspond to a wider range of private
(internal) IP addresses, in order to make savings, either in terms of IPv4
addresses, or because it's simply cheaper than buying several public IPv4
addresses. Now, the fact that masking the internal addresses to the external
world - so that internal hosts can initiate traffic to the outside, but no
external host can initiate traffic to the inside - brings some basic
security, is an interesting corollary, but not the primary objective of a
NAT.

Hope this helps. And sorry again for the purists. ;)

E.T.
ICT Consultant and Trainer.
Member of IEEE, IPv6 Task Force, ISOC, PIR.

=>-----Original Message-----
=>From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On 
=>Behalf Of S Woodside
=>
(...)
=>
=>This sounds like you are equating a NAT box with a firewall, which 
=>seems to be common.
=>
=>I would like to know:
=>- Is a NAT box a protocol enforcement point?
=>- is it an EFFECTIVE protocol enforcement point?
=>- is a NAT a firewall? (many people seem to think it is ...)
=>- is a firewall a protocol enforcement point? (yes)
=>- does a protocol enforcement point, have to include a NAT?
=>- does an EFFECTIVE one have to include a NAT?
=>- is it even EASIER to enforce protocol issues with a NAT as 
=>opposed to 
=>other means?
=>
=>simon
(...)





From owner-ietf@ietf.org  Wed Jun 18 19:08:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05104
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 19:08:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SlYh-0003Qs-LH
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 18:37:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SlXc-00038L-Cx
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 18:36:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04123
	for <ietf@ietf.org>; Wed, 18 Jun 2003 18:36:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SlVM-00035f-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:34:12 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SlVL-00035Y-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:34:11 -0400
Received: from slb-av-02.boeing.com ([129.172.13.7])
	by slb-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id PAA29067;
	Wed, 18 Jun 2003 15:35:39 -0700 (PDT)
Received: from blv-hub-01.boeing.com (localhost [127.0.0.1])
	by slb-av-02.boeing.com (8.9.3p2/8.9.2/MBS-AV-02) with ESMTP id PAA02243;
	Wed, 18 Jun 2003 15:36:10 -0700 (PDT)
Received: from XCH-NWBH-01.nw.nos.boeing.com (xch-nwbh-01.nw.nos.boeing.com [192.33.62.231])
	by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id h5IMa8t16554;
	Wed, 18 Jun 2003 15:36:08 -0700 (PDT)
Received: from XCH-NW-09.nw.nos.boeing.com ([192.42.226.84]) by XCH-NWBH-01.nw.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.6662);
	 Wed, 18 Jun 2003 15:36:08 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Date: Wed, 18 Jun 2003 15:36:08 -0700
Message-ID: <5B58696DB20B9140AD20E0685C573A6402992D7B@xch-nw-09.nw.nos.boeing.com>
Thread-Topic: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Thread-Index: AcM15s0G21y4p+oxQ4asjI+wBM1DugAAYEzg
From: "Fleischman, Eric" <eric.w.fleischman@boeing.com>
To: "EKR" <ekr@rtfm.com>, "Keith Moore" <moore@cs.utk.edu>
Cc: <pbaker@verisign.com>, <Ronald.vanderPol@rvdp.org>, <aarsenau@bbn.com>,
        <ietf@ietf.org>
X-OriginalArrivalTime: 18 Jun 2003 22:36:08.0419 (UTC) FILETIME=[02ECAB30:01C335EA]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA05104

Eric Rescorla [mailto:ekr@rtfm.com] wrote:

>> similarly, people who install NAT usually don't realize how much this
>> costs them in lost functionality and reliability.

>Really? You have evidence of this?

>I don't either, but my intuition is that you're wrong.  Once you have
>decided to have a firewall in place (which you may think is evil, but
>I consider pretty much a necessary evil), I suspect that most people
>suffer almost not at all from having a NAT.

I believe that Eric is pointing out an important point: many deployments of NATs have nothing to do with IPv4 address conservation. Rather, they are firewall adjuncts implemented to hide internal networks from outside scrutiny and direct access. 

One point where I disagree with my IPv6-advocating friends is that I expect firewall-related NATs to continue to be deployed within Internet (including IPv6) environments until such a time as real-time-protocol and peer-to-peer-protocol friendly "distributed firewall" (policy zones) variants become the preferable "due diligence" alternative for CIOs.



From owner-ietf@ietf.org  Wed Jun 18 19:20:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05756
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 19:20:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sm52-0005cV-A3
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 19:11:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Slf2-0004CN-UG
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 18:44:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04580
	for <ietf@ietf.org>; Wed, 18 Jun 2003 18:44:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Slcm-0003EG-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:41:52 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Slcl-0003ED-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:41:51 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5IMi8N10435;
        Wed, 18 Jun 2003 18:44:08 -0400 (EDT)
Date: Wed, 18 Jun 2003 18:44:08 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Putzolu, David" <david.putzolu@intel.com>
Cc: moore@cs.utk.edu, david.putzolu@intel.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030618184408.2605bb78.moore@cs.utk.edu>
In-Reply-To: <FD2423AA68A7D511A5A20002A50729E1105BAA1C@orsmsx115.jf.intel.com>
References: <FD2423AA68A7D511A5A20002A50729E1105BAA1C@orsmsx115.jf.intel.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> The IAB has talked about NAT.  A WG has produced a bunch of
> RFCs about NAT.  

the WG ended up being full of NAT vendors trying to legitimize NAT
(and grossly exceeding the bounds of their charter in the process)

> How about some lemonade?  An Internet draft that says 
> something new about NATs would be a lot more helpful than 
> rehashing the same old arguments.

for one attempt to make lemonade, see RFC 3056.
for another, see draft-ietf-ngtrans-shipworm-08.txt
for another, see draft-moore-nat-tolerance-recommendations-00.txt
(it's expired - look in http://www.cs.utk.edu/~moore/I-D/ )

but looking for a way to magically turn NATs into something that works
well that doesn't require both significant infrastructure investment and
significant changes to the endpoints and apps is tantamount to wishing
for magic pixie dust.

Keith




From owner-ietf@ietf.org  Wed Jun 18 19:32:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06127
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 19:32:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sm9a-0005hc-Mo
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 19:15:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Slqf-0004J4-D1
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 18:56:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04786
	for <ietf@ietf.org>; Wed, 18 Jun 2003 18:56:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SloP-0003I2-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:53:53 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SloO-0003Hy-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:53:52 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h5IMtcFh014550;
	Wed, 18 Jun 2003 15:55:39 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AFF31253;
	Wed, 18 Jun 2003 15:55:37 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id PAA07516; Wed, 18 Jun 2003 15:55:37 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16112.60905.486123.254138@thomasm-u1.cisco.com>
Date: Wed, 18 Jun 2003 15:55:37 -0700 (PDT)
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: Bob Braden <braden@ISI.EDU>, moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
In-Reply-To: <27644537-A1D2-11D7-9C85-00039388672E@muada.com>
References: <200306181917.MAA15517@gra.isi.edu>
	<27644537-A1D2-11D7-9C85-00039388672E@muada.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum writes:
 > On woensdag, jun 18, 2003, at 21:17 Europe/Amsterdam, Bob Braden wrote:
 > 
 > > Since 1980 we have believed that universal connectivity was one of the
 > > great achievements of the Internet design.  Today, one must
 > > unfortunately question whether universal connectivity can be sustained
 > > (or is even the right goal) in a networking environment without
 > > universal trust.
 > 
 > I think we can safely say that 99.99% of all systems that run IP don't 
 > want to talk to 99.99% of all systems that run IP. For most people, 
 > with a network this large, universal connectivity isn't a goal but a 
 > threat. But this shouldn't be confused with universal addressability 
 > being undesirable, because this only gets more important as the size of 
 > the network increases.

Voice challenges this assumption to a very large
degree. In fact, I not only want access to 99.99%
of the other nodes on the net willing to speak
RTP, but I most certainly don't want to be forced
to go through some forced eavesdrop-tapping,
terrorist-witchhunting intermediary that is
subject to the whims of certain fanatics from
Missouri and Utah who are convinced that peetopee
is the spawn of Satan.

	     Mike



From owner-ietf@ietf.org  Wed Jun 18 19:42:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06402
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 19:42:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SmBR-0005lf-GI
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 19:17:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Slsw-0004Ke-8Q
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 18:58:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04896
	for <ietf@ietf.org>; Wed, 18 Jun 2003 18:58:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Slqf-0003Jj-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:56:14 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Slqe-0003JG-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:56:13 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 39423ABB5; Wed, 18 Jun 2003 16:04:06 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
	<kju1ankzkr.fsf@romeo.rtfm.com>
	<20030618144239.0c31eb88.moore@cs.utk.edu>
	<kjptlbkxpr.fsf@romeo.rtfm.com>
	<20030618153329.4fe1ab1c.moore@cs.utk.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 18 Jun 2003 16:04:06 -0700
In-Reply-To: <20030618153329.4fe1ab1c.moore@cs.utk.edu>
Message-ID: <kjfzm7kmxl.fsf@romeo.rtfm.com>
Lines: 27
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Keith Moore <moore@cs.utk.edu> writes:
> > I don't know enough about how you're doing your distributing computing
> > to have an opinion, but as for the other two... In my experience,
> > IT managers are pretty unhappy punching holes in their firewalls
> > for incoming SIP and IPsec, whether they run NAT or not.
> 
> In my experience, IT managers are generally pretty unhappy changing
> anything to support their users.  People who actually use the computers
> or the network are regarded as a nuisance.
Exactly. So, why do you it's NATs that are the cause of users
not getting the things they want, as opposed to the usual IT
manager behavior.

> > The bottom line here is what economists call "revealed preference".
> 
> Maybe "revealed ignorance" would be a better term.  Though I prefer
> "unintended consequence".
Huh? The IT managers could not use NAT if they wanted. What
evidence do you have that they consider them a bad tradeoff?

-Ekr



-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Wed Jun 18 19:46:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06597
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 19:46:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SmBR-0005ll-R5
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 19:17:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SluT-0004NU-F5
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 19:00:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04980
	for <ietf@ietf.org>; Wed, 18 Jun 2003 19:00:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SlsD-0003Kh-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:57:49 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SlsB-0003Kc-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:57:47 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5IN00N10462;
        Wed, 18 Jun 2003 19:00:00 -0400 (EDT)
Date: Wed, 18 Jun 2003 18:59:59 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030618185959.10515e0a.moore@cs.utk.edu>
In-Reply-To: <200306182139.h5ILdoQ4006194@ginger.lcs.mit.edu>
References: <200306182139.h5ILdoQ4006194@ginger.lcs.mit.edu>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> We lost our chance to avoid NAT's when variable length addresses were
> removed from TCPv2.5 (IIRC the version number correctly). 

or maybe when IAB was shot down after Kobe :)

> NAT's are here, like it or not, and the only question is how to make
> lemonade out of them. 

see my other comment about magic pixie dust.

the way to fix NATs is to obsolete them.  IPv6 is the best shot we have
at that.



From owner-ietf@ietf.org  Wed Jun 18 19:50:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06841
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 19:50:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SmBS-0005lr-2x
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 19:17:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SlvD-0004NW-1p
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 19:00:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05000
	for <ietf@ietf.org>; Wed, 18 Jun 2003 19:00:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Slsw-0003LN-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:58:34 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Slsf-0003KR-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:58:34 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 22410ABB5; Wed, 18 Jun 2003 16:06:09 -0700 (PDT)
To: Melinda Shore <mshore@cisco.com>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <200306181937.AIN64606@mira-sjc5-c.cisco.com>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 18 Jun 2003 16:06:08 -0700
In-Reply-To: <200306181937.AIN64606@mira-sjc5-c.cisco.com>
Message-ID: <kjbrwvkmu7.fsf@romeo.rtfm.com>
Lines: 18
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Melinda Shore <mshore@cisco.com> writes:

> > What applications that people want to run--and the IT managers would
> > want to enable--are actually inhibited by NAT? It seems to me that
> > most of the applications inconvenienced by NAT are ones that IT
> > managers would want to screen off anyway.
> 
> Not really.  For example, ftp as originally defined doesn't
> work through NATs, and no standard VoIP or multimedia
> conferencing protocol works through NAT.  
None of these things worked real well through firewalls either,
which is sort of my point.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Wed Jun 18 19:55:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07072
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 19:55:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SmBS-0005lx-Ed
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 19:17:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SlyS-0004WD-1M
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 19:04:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05046
	for <ietf@ietf.org>; Wed, 18 Jun 2003 19:04:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SlwB-0003MX-00
	for ietf@ietf.org; Wed, 18 Jun 2003 19:01:55 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SlwA-0003MU-00
	for ietf@ietf.org; Wed, 18 Jun 2003 19:01:54 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5IN4BN10477;
        Wed, 18 Jun 2003 19:04:11 -0400 (EDT)
Date: Wed, 18 Jun 2003 19:04:10 -0400
From: Keith Moore <moore@cs.utk.edu>
To: EKR <ekr@rtfm.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030618190410.57eda79a.moore@cs.utk.edu>
In-Reply-To: <kjfzm7kmxl.fsf@romeo.rtfm.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
	<kju1ankzkr.fsf@romeo.rtfm.com>
	<20030618144239.0c31eb88.moore@cs.utk.edu>
	<kjptlbkxpr.fsf@romeo.rtfm.com>
	<20030618153329.4fe1ab1c.moore@cs.utk.edu>
	<kjfzm7kmxl.fsf@romeo.rtfm.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > In my experience, IT managers are generally pretty unhappy changing
> > anything to support their users.  People who actually use the
> > computers or the network are regarded as a nuisance.
>
> Exactly. So, why do you it's NATs that are the cause of users
> not getting the things they want, as opposed to the usual IT
> manager behavior.

good point.  maybe the very reason that IT managers like NATs is that
they make the users' lives more difficult, and they provide job security
for IT managers who have to sort out NAT problems just so that things
can work at all.  but from the ones I've talked to, some combination of
ignorance, brainwashing, and stupidity seems more likely.

Keith
 



From owner-ietf@ietf.org  Wed Jun 18 19:57:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05110
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 19:08:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SlYi-0003RK-1w
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 18:37:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SlYJ-00038Q-N5
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 18:37:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04165
	for <ietf@ietf.org>; Wed, 18 Jun 2003 18:37:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SlW3-00036C-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:34:55 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SlW2-000369-00
	for ietf@ietf.org; Wed, 18 Jun 2003 18:34:54 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5IMbAN10408;
        Wed, 18 Jun 2003 18:37:11 -0400 (EDT)
Date: Wed, 18 Jun 2003 18:37:10 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030618183710.1accbf19.moore@cs.utk.edu>
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E0D2255@mou1wnexm02.verisign.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D2255@mou1wnexm02.verisign.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> What I am suggesting is that there is no reason nat had to reusult in
> being on the interNOT rather than the internet.

you're simply wrong about that, at least for anything resembling today's
NATs.   except for a shortage of IPv4 addresses, NATs would not be
needed at all.  (yes, they're sold for other purposes, but they're
not needed for those purposes)  and there's no way to fix that shortage
in a sane fashion (or as you put it, without producing the interNOT)
that does not require changes to the endpoints - and in many cases, the
applications - to make them work. once you do that you're within epsilon
of the deployment barrier to IPv6.  (had IPv6 been designed
differently we might have been able to avoid having those changes affect
the network core, but not leaf networks or endpoints.)

> Further folk are going to buy these and put them at the border of
> their home networks. 

yup, and there will continue to be vendors selling snake oil.  it's not
our problem.

> Trying to secure end point computers is futile.

it's even more futile to expect the network to do it.  firewalls can
raise the bar for some kinds of threats, but they can't make your
insecure systems secure.

> If I dot run a local mail server why should I let a machine have
> unrestricted net access if it does not need it? 

no reason that I know of.  but the relevant question for this dicussion
is, why do you need a NAT to impose access control?  answer: you don't.




From owner-ietf@ietf.org  Wed Jun 18 19:58:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07232
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 19:58:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SmMv-0006Qo-5k
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 19:29:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sm7M-0005g9-9V
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 19:13:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05619
	for <ietf@ietf.org>; Wed, 18 Jun 2003 19:13:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sm55-0003WA-00
	for ietf@ietf.org; Wed, 18 Jun 2003 19:11:07 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sm50-0003W1-00
	for ietf@ietf.org; Wed, 18 Jun 2003 19:11:02 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 0A2A5ABB5; Wed, 18 Jun 2003 16:19:00 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
	<kju1ankzkr.fsf@romeo.rtfm.com>
	<20030618144239.0c31eb88.moore@cs.utk.edu>
	<kjptlbkxpr.fsf@romeo.rtfm.com>
	<20030618153329.4fe1ab1c.moore@cs.utk.edu>
	<kjfzm7kmxl.fsf@romeo.rtfm.com>
	<20030618190410.57eda79a.moore@cs.utk.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 18 Jun 2003 16:18:59 -0700
In-Reply-To: <20030618190410.57eda79a.moore@cs.utk.edu>
Message-ID: <kj65n3km8s.fsf@romeo.rtfm.com>
Lines: 27
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> > > In my experience, IT managers are generally pretty unhappy changing
> > > anything to support their users.  People who actually use the
> > > computers or the network are regarded as a nuisance.
> >
> > Exactly. So, why do you it's NATs that are the cause of users
> > not getting the things they want, as opposed to the usual IT
> > manager behavior.
> 
> good point.  maybe the very reason that IT managers like NATs is that
> they make the users' lives more difficult, and they provide job security
> for IT managers who have to sort out NAT problems just so that things
> can work at all.  but from the ones I've talked to, some combination of
> ignorance, brainwashing, and stupidity seems more likely.

One of the things I've always find endearing about IETFers is their
utter confidence that whenever the world disagrees with them about the
value of some technical approach, it must be because everyone else in
the world is stupid.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
           Web Log: http://www.rtfm.com/movabletype




From owner-ietf@ietf.org  Wed Jun 18 19:59:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07361
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 19:59:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Smjf-0008N1-Ez
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 19:53:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SmBZ-0005qd-KX
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 19:17:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05672
	for <ietf@ietf.org>; Wed, 18 Jun 2003 19:17:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sm9J-0003XU-00
	for ietf@ietf.org; Wed, 18 Jun 2003 19:15:29 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sm9I-0003XR-00
	for ietf@ietf.org; Wed, 18 Jun 2003 19:15:28 -0400
Received: from [67.126.41.36] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h5INHirc010563
	for <ietf@ietf.org>; Wed, 18 Jun 2003 16:17:44 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05210609bb169f5d968a@[67.126.41.36]>
In-Reply-To: <FNEFIPCNJKDDONJGBCNEIENJEBAA.vkompella@timetra.com>
References: <FNEFIPCNJKDDONJGBCNEIENJEBAA.vkompella@timetra.com>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Wed, 18 Jun 2003 16:17:18 -0700
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: RE: WG review: Layer 2 Virtual Private Networks (l2vpn)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 1:31 PM -0700 6/18/03, Vach Kompella wrote:
>  > - the IETF's track record for this work so far is quite poor
>>
>
>That's not a problem of the ppvpn group only.  It is a problem of the IETF.

Generally agree.

>I don't need to refresh your memory about IPSec, do I?  SKIP, Skeme, Oakley,
>IKE.  AH or ESP with auth?  5 years of bloody fighting.

I'm not sure how to argue with the statement "the IETF has done a 
horrible job with a similar working group, so we want our working 
group in the IETF".

First off, I agree with you about the IPsec WG, and think it is a 
very good indicator of what the IETF does poorly, particularly in the 
area of focus. (Hint: look at the number of WG Internet Drafts there 
are right now in IPsec that no one is working on.) The problems in 
the IPsec WG and others are typical of the problems of the WGs that 
are working on trusted VPN technologies.

>It's wherever the action is that the political jostling for position 
>is the most
>prominent.  That's also where the leadership needs to be strong and 
>participants
>need to have a "nose to the grindstone" attitude.  That's hardly an indication
>that the work should not be chartered or worked upon.

Er, yes it is. There is no indication that we will do a better job 
than the terrible job we are doing now. What you propose sounds like 
"we're terrible parents for our six children and barely have enough 
time to pay attention to them, but maybe we'll be better with the 
seventh."

>  > We have not shown any ability to create standards in this area with
>>  due speed or predictability. We have not shown the good judgement
>>  needed to limit the scope of the work we do. (Look at the number of
>>  L2VPN-based Working Group drafts in PWE3 and PPVPN, much less the
>>  large number of non-WG documents being actively discussed.
>
>Do you think the new L2VPN charter addresses these concerns of scoping?  How
>about the timelines?  Basically, it's going to be a WG issue, chairs and
>participants, to finish the WG charter items first.

Why do you think that the re-chartered WG will have any more luck 
with these than the current one? There are a zillion hardware vendors 
and service providers who have reasons to want the dozens of 
documents that are in the current WGs, and it takes very little 
effort on their part to promote their views. The IETF structure does 
poorly in such an environment; maybe a different standards body would 
do better.

>  > The IETF understands the need for layer 2 technologies for OAM much
>>  better than we understand the Internet customer's need (or even
>>  concern) for layer 2 transport of their IP packets. This is because
>>  we have a tighter relationship with operators than we do with
>>  Internet users, and because Internet users generally could care less
>>  about how their ISPs move their traffic as long as they meet the
>>  service level agreements. The ISPs would love to have better
>>  cross-vendor interop for the L2VPN technologies, but so far the
>>  vendors haven't had time to think about that because they have been
>>  overloaded with the literally dozens of flavors that are being
>>  discussed in the IETF.
>
>Are you talking PWE3 or L2VPN?

Yes. There is a significant amount of spillage between the two.

>The gazillion drafts is in PWE3.  The interop issues are localized 
>to the drafts
>with contention, silly issues of where bits should go.
>
>There are 16 pseudowire types:
>            0x0001   Frame Relay DLCI
>            0x0002   ATM AAL5 SDU VCC transport
>            0x0003   ATM transparent cell transport
>            0x0004   Ethernet Tagged Mode
>            0x0005   Ethernet
>            0x0006   HDLC
>            0x0007   PPP
>            0x0008   SONET/SDH Circuit Emulation Service Over MPLS (CEM) [8]
>            0x0009   ATM n-to-one VCC cell transport
>            0x000A   ATM n-to-one VPC cell transport
>            0x000B   IP Layer2 Transport
>            0x000C   ATM one-to-one VCC Cell Mode
>            0x000D   ATM one-to-one VPC Cell Mode
>            0x000E   ATM AAL5 PDU VCC transport
>            0x000F   Frame-Relay Port mode
>            0x0010   SONET/SDH Circuit Emulation over Packet (CEP)
>
>At least half of these are and have been interoperable.  It is the harder (and
>more arcane, IMHO) PW types that people are having a hard time coming to some
>sort of compromise.

And why should the IETF care at all about these? There are other fora 
for layer-2 interworking.

>BTW, I'm glad to see you have a healthier respect for providers than 
>Kurtis who
>claims that "most of these providers have bought what their vendor 
>told them to
>buy."

He and I might both be right. In my talks with service providers, I 
find that many of them who want to expand their presence in, or just 
get into, the "IP VPN" market look at what hardware they have on hand 
in their core (they certainly can't buy any significant new hardware 
these days) and base their decision on the layer-2 technologies on 
that. Usually, the customers don't know or care. If the customers 
care, they only care enough to ask "are you using MPLS" and then node 
sagely when their service provider says yes. (Humorously, the very 
large service provider who doesn't use MPLS in their core says that 
it usually only takes one or more sentences to convince the 
prospective customer that MPLS is not needed.)

>  > We will never know if there is another organization who could do a
>>  better job than this because no other organization will take on the
>>  work while the 800-pound gorilla of standards bodies is flailing
>>  around in the area. There are certainly other organizations that can
>>  take it on, such as the MPLS and Frame Relay Alliance. They might do
>>  just as bad of a job as we have so far, but they could also do much
>>  better because they are much more focused.
>
>An 800-pound gorilla conjures up images of one less nimble of foot.

Exactly.

>   IMHO, not
>the right metaphor for the IETF.

But one that I believe is apt, at least for all of the trusted VPN 
work the IETF is doing currently.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Wed Jun 18 20:14:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07886
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 20:14:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Smjf-0008No-UO
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 19:53:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SmEK-00068G-Hk
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 19:20:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05779
	for <ietf@ietf.org>; Wed, 18 Jun 2003 19:20:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SmC4-0003Yi-00
	for ietf@ietf.org; Wed, 18 Jun 2003 19:18:20 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SmC3-0003Ye-00
	for ietf@ietf.org; Wed, 18 Jun 2003 19:18:19 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5INKaN10499;
        Wed, 18 Jun 2003 19:20:36 -0400 (EDT)
Date: Wed, 18 Jun 2003 19:20:35 -0400
From: Keith Moore <moore@cs.utk.edu>
To: EKR <ekr@rtfm.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030618192035.507e9a9f.moore@cs.utk.edu>
In-Reply-To: <kj65n3km8s.fsf@romeo.rtfm.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
	<kju1ankzkr.fsf@romeo.rtfm.com>
	<20030618144239.0c31eb88.moore@cs.utk.edu>
	<kjptlbkxpr.fsf@romeo.rtfm.com>
	<20030618153329.4fe1ab1c.moore@cs.utk.edu>
	<kjfzm7kmxl.fsf@romeo.rtfm.com>
	<20030618190410.57eda79a.moore@cs.utk.edu>
	<kj65n3km8s.fsf@romeo.rtfm.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> One of the things I've always find endearing about IETFers is their
> utter confidence that whenever the world disagrees with them about the
> value of some technical approach, it must be because everyone else in
> the world is stupid.

hey, not everyone else is an IT manager :)

investing in nat boxes is a lot like investing in lottery tickets.
but for some reason both sell well...



From owner-ietf@ietf.org  Wed Jun 18 20:20:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08125
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 20:20:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sn6a-00022y-O6
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 20:16:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Smya-0001Rc-IQ
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 20:08:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07757
	for <ietf@ietf.org>; Wed, 18 Jun 2003 20:08:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SmwJ-00048b-00
	for ietf@ietf.org; Wed, 18 Jun 2003 20:06:07 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SmwJ-00048A-00
	for ietf@ietf.org; Wed, 18 Jun 2003 20:06:07 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id A809013969; Thu, 19 Jun 2003 00:07:55 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <16112.60905.486123.254138@thomasm-u1.cisco.com>
From: Paul Vixie <vixie@vix.com>
Date: 19 Jun 2003 00:07:55 +0000
In-Reply-To: <16112.60905.486123.254138@thomasm-u1.cisco.com>
Message-ID: <g3r85rvsis.fsf@sa.vix.com>
Lines: 36
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

mat@cisco.com (Michael Thomas) writes:

> Voice challenges this assumption to a very large
> degree. In fact, I not only want access to 99.99%
> of the other nodes on the net willing to speak RTP ...

actually i think you probably don't, or rather, won't.

telemarketing by robot is illegal in some places but is
widely used to detect fax machines or voice-answered
lines for later use by other robots or by humans.  one
of the cost components for this kind of activity today
is a room full of CTI hardware and a DS1 (or better) and
a willingness to buy blocks of long distance minutes.

assuming VoIP takes off, the costs of robotic telemarketing
are going to go way way down.  in particular, it may become
popular to sweep the E164.ARPA address space looking for
endpoints, then sweep the resulting RTP endpoints looking
for live reachable instruments like humans and fax machines.

it's safe to say that the same people who call you at home
during dinner to sell you chemicals for your septic tank
are going to team up with the same people who send you spam
or who do "e-mail appending" or who spam your fax machine
with vacation offers...

...and that your RTP instrument will have to be one of the
most violently over-firewalled devices on your network in
order to remain useful for its intended (by you that is)
purpose.

maybe i should get back into the blackhole business, but for
VoIP this time, since it'll be a HUUUUGE market.
-- 
Paul Vixie



From owner-ietf@ietf.org  Wed Jun 18 20:36:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08902
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 20:36:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sn6b-00023E-26
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 20:16:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Smyt-0001S1-6L
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 20:08:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07770;
	Wed, 18 Jun 2003 20:08:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Smwc-00048z-00; Wed, 18 Jun 2003 20:06:26 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Smwb-00048v-00; Wed, 18 Jun 2003 20:06:25 -0400
Received: from [147.28.0.62] (helo=127.0.0.1 ident=zinin)
	by psg.com with esmtp (Exim 4.14)
	id 19Smyq-000EI6-1j; Thu, 19 Jun 2003 00:08:44 +0000
Date: Wed, 18 Jun 2003 17:03:32 -0700
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: <14915584869.20030618170332@psg.com>
To: "Adrian Farrel" <afarrel@movaz.com>
CC: iesg@ietf.org, ietf@ietf.org, mpls@UU.NET
Subject: Re: Last Call: LDP DoD Graceful Restart to Draft Standard
In-Reply-To: <0aa001c335cb$610e5bb0$681810ac@movaz.com>
References: <E19Qspn-0000Rd-3H@asgard.ietf.org>
 <07b701c331f1$ffeeb820$681810ac@movaz.com>
 <0aa001c335cb$610e5bb0$681810ac@movaz.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Adrian, folks-

 I opened a ticket with the secretariat about this error a couple
 of days ago:
 
  [iesg-secretary #8150] Wrong Document Action: draft-ietf-mpls-ldp-dod-restart-00.txt

 I will ping them again.

-- 
Alex
http://www.psg.com/~zinin/

Wednesday, June 18, 2003, 11:56:51 AM, Adrian Farrel wrote:
> Did anyone decide there was an error here, or is this draft really in IETF last
> call?

> Thanks
> Adrian
> ----- Original Message -----
> From: "Adrian Farrel" <afarrel@movaz.com>
> To: <iesg@ietf.org>; <ietf@ietf.org>
> Cc: <mpls@UU.NET>
> Sent: Friday, June 13, 2003 5:23 PM
> Subject: Re: Last Call: LDP DoD Graceful Restart to Draft Standard


>> With respect, this draft doesn't appear to have been through WG last call
>> (unless I was sleeping, but I can't find any reference in the mail archive).
>>
>> It was only published as a WG draft on 5/7/2003 (despite carrying a date of
>> February 2003).
>>
>> While I support the draft, I would like to see it discussed on the mailing
> list
>> and go through WG last call.
>>
>> Thanks,
>> Adrian
>>
>> ----- Original Message -----
>> From: "The IESG" <iesg-secretary@ietf.org>
>> To: <IETF-Announce: ;>
>> Cc: <mpls@UU.NET>
>> Sent: Friday, June 13, 2003 1:59 PM
>> Subject: Last Call: LDP DoD Graceful Restart to Draft Standard
>>
>>
>> > ---------------
>> > The IESG has received a request from Multiprotocol Label Switching to
>> > consider the following Internet-Draft(s) as Draft Standard.
>> > o Multiprotocol Label Switching (MPLS): LDP DoD Graceful Restart
>> >   <draft-ietf-mpls-ldp-dod-restart-00.txt>
>> >   Draft Standard
>> >
>> >
>> > The IESG plans to make a decision in the next few weeks, and solicits
>> > final comments on this action.  Please send any comments to the
>> > iesg@ietf.org or ietf@ietf.org mailing lists by .
>> >
>> > Files can be obtained via
>> > http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-dod-restart-00.txt
>> >
>>
>>




From owner-ietf@ietf.org  Wed Jun 18 20:45:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09174
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 20:45:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SnSD-0003Bg-UH
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 20:39:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SnCT-0002X8-FU
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 20:22:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08316
	for <ietf@ietf.org>; Wed, 18 Jun 2003 20:22:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SnAD-0004JI-00
	for ietf@ietf.org; Wed, 18 Jun 2003 20:20:29 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SnAB-0004JF-00
	for ietf@ietf.org; Wed, 18 Jun 2003 20:20:28 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5J0Mjr1007690
	for ietf@ietf.org env-from <vjs>;
	Wed, 18 Jun 2003 18:22:45 -0600 (MDT)
Date: Wed, 18 Jun 2003 18:22:45 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306190022.h5J0Mjr1007690@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: WG review: Layer 2 Virtual Private Networks (l2vpn)
References: <p05210609bb169f5d968a@[67.126.41.36]>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Paul Hoffman / IMC <phoffman@imc.org>

> ...
> Why do you think that the re-chartered WG will have any more luck 
> with these than the current one? There are a zillion hardware vendors 
> and service providers who have reasons to want the dozens of 
> documents that are in the current WGs, and it takes very little 
> effort on their part to promote their views. The IETF structure does 
> poorly in such an environment; maybe a different standards body would 
> do better.

> ...
> And why should the IETF care at all about these? There are other fora 
> for layer-2 interworking.

That's an interesting pair of thoughts.  The obvious guess is that
interested parties are happy with the bad job the IETF has been doing and
are doing a little forum shopping.  In the areas I've been watching (which
do not include IPSEC, DNSSEC, or VPNs), the bad jobs consist of rubber
stamping ideas whose lameness is exceeded only by their complete lack of
interest and any trace of originality.  It's amazing how many people feel
compelled to take a well established idea with many ancient implementations
and write an RFC standardizing a redundant, unnecessary version elsewhere.
(Is that also the deal with this tunnel stuff?)

I suspect the IESG is overtaxed, overextended, and doesn't have enough
thumbs to stick in all of holes in the dikes holding back the floods
of wonderful ideas from marketing departments and junior, not-quite
engineers with ambitions in marketing.

A modest proposal:  Limit the supply of RFC (not to mention BCP)
numbers.  If only 50 RFC numbers were available for the next 12 months,
there would be an incentive for competent people to stick their necks
out and stomp on some of the nonsense to ensure that things that need
consideration would get it.  I doubt the IETF could produce 10 good
RFCs in the next 12 months, so 50 numbers would be generous.

Without that, an equivalent of the IEEE PAR, or some other effective
mechanism, the IETF is going to suffer the fate dictated by Gresham's
Law of any mint that fails to control its output.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Wed Jun 18 20:55:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09473
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 20:55:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SnVc-0003MW-L5
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 20:42:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SnN3-0002ko-JU
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 20:33:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08818
	for <ietf@ietf.org>; Wed, 18 Jun 2003 20:33:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SnKn-0004Rx-00
	for ietf@ietf.org; Wed, 18 Jun 2003 20:31:25 -0400
Received: from ns2.sea.interquest.net ([66.135.144.2] helo=ns2.sea)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SnKm-0004Rr-00
	for ietf@ietf.org; Wed, 18 Jun 2003 20:31:24 -0400
Received: from ssprunk (ip175.post-vineyard.dfw.interquest.net [66.135.181.175])
	by ns2.sea (8.12.9/8.12.5) with SMTP id h5J0XYE9027434;
	Wed, 18 Jun 2003 17:33:37 -0700
Message-ID: <015601c335fa$6d13b4d0$afb58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Ronald van der Pol" <Ronald.vanderPol@rvdp.org>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>
Cc: <ietf@ietf.org>
References: <61AC0EDA-A0F4-11D7-82AB-00039388672E@muada.com>
Subject: Re: myth of the great transition (was US Defense Department formally adopts IPv6)
Date: Wed, 18 Jun 2003 19:18:10 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Iljitsch van Beijnum" <iljitsch@muada.com>
> For any particular application and group of users, and in order to
> switch over seamlessly, it is necessary that all servers become dual
> stack, then clients can switch (without the need to run dual stack) and
> after that the servers can drop IPv4.

That is one scenario; there are others.

> And for peer-to-peer, _everyone_ is a server so _everyone_ has to
> run dual stack before it's possible to drop IPv4.

Out of curiosity I sniffed my own P2P applications and found that over 50%
of the hosts my client tried to contact weren't available, presumably due to
NATs, firewalls, or other connectivity impediments.  In spite of this
problem, the P2P networks work well enough nobody cares about the problem.

I conclude, therefore, that as long as a sizable minority of P2P users are
dual stack, the majority can safely speak only v4 or only v6.

S

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




From owner-ietf@ietf.org  Wed Jun 18 21:18:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10174
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 21:18:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Snsn-0004lu-Iv
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 21:06:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SngN-0003tS-4I
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 20:53:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09366
	for <ietf@ietf.org>; Wed, 18 Jun 2003 20:53:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sne6-0004cG-00
	for ietf@ietf.org; Wed, 18 Jun 2003 20:51:22 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sne5-0004c6-00
	for ietf@ietf.org; Wed, 18 Jun 2003 20:51:21 -0400
Received: from cisco.com (sjc-vpn2-391.cisco.com [10.21.113.135])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with SMTP id h5J0r7wm028992
	for <ietf@ietf.org>; Wed, 18 Jun 2003 17:53:08 -0700 (PDT)
Received: by cisco.com (sSMTP sendmail emulation); Wed, 18 Jun 2003 20:53:07 -0400
Date: Wed, 18 Jun 2003 20:53:07 -0400
From: Scott W Brim <swb@employees.org>
To: ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
Message-ID: <20030619005306.GV2044@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <swb@employees.org>, ietf@ietf.org
References: <20030618181602.GL2044@sbrim-w2k01> <200306181931.AIN63758@mira-sjc5-c.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200306181931.AIN63758@mira-sjc5-c.cisco.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Jun 18, 2003 03:31:56PM -0400, Melinda Shore allegedly wrote:
> > The IETF does continue to have an emphasis on connectionless,
> > packet-oriented delivery.  That's our fundamental architecture,
> > without question.  In the meantime there are customers who want to
> > transition to c, p-o d but need mechanisms for doing so.
> 
> Personally I'd find this proposal more compelling if it were being
> presented as being oriented towards transitional mechanisms.  

You're right, that doesn't get mentioned.  However, many providers see
it that way.  (Admittedly there are some who don't.)

> We're seeing circuit-y proposals show up in other working groups and
> I'm concerned that these reflect a shift in basic assumptions about
> the characteristics of the underlying network, at least among a
> non-trivial number of participants.  

People who can't see beyond the circuit approach shouldn't be given
responsibility for Internet architectural thinking, and right now
fundamental architectural thinking is what we need more than anything.

.swb



From owner-ietf@ietf.org  Wed Jun 18 21:19:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10349
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 21:19:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Snyv-00078u-OJ
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 21:12:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SnkB-0004cY-Nl
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 20:57:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09762
	for <ietf@ietf.org>; Wed, 18 Jun 2003 20:57:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Snhv-0004jC-00
	for ietf@ietf.org; Wed, 18 Jun 2003 20:55:19 -0400
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Snhu-0004j9-00
	for ietf@ietf.org; Wed, 18 Jun 2003 20:55:18 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0.6)
  with ESMTP-TLS id 242144; Wed, 18 Jun 2003 19:57:14 -0500
Message-ID: <3EF10A7F.7020009@ehsco.com>
Date: Wed, 18 Jun 2003 19:57:35 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
References: <2A1D4C86842EE14CA9BC80474919782E0D2255@mou1wnexm02.verisign.com> <20030618183710.1accbf19.moore@cs.utk.edu>
In-Reply-To: <20030618183710.1accbf19.moore@cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 6/18/2003 5:37 PM Keith Moore wrote:

> you're simply wrong about that, at least for anything resembling
> today's NATs.  except for a shortage of IPv4 addresses, NATs would not
> be needed at all.

...and a routing grid that could handle a squared table size. No use in
opening allocations to everybody that can justify ~/29 if filters are
still going to be dropping everything after /20.

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




From owner-ietf@ietf.org  Wed Jun 18 21:42:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09474
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 20:55:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SnVc-0003MQ-AU
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 20:42:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SnMY-0002k1-KR
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 20:33:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08807
	for <ietf@ietf.org>; Wed, 18 Jun 2003 20:33:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SnKI-0004Ro-00
	for ietf@ietf.org; Wed, 18 Jun 2003 20:30:54 -0400
Received: from garlic.apnic.net ([202.12.29.224])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SnKG-0004Rk-00
	for ietf@ietf.org; Wed, 18 Jun 2003 20:30:53 -0400
Received: from garlic.apnic.net (localhost [127.0.0.1])
	by garlic.apnic.net (8.12.9/8.12.9) with ESMTP id h5J0X2GM000955
	for <ietf@ietf.org>; Thu, 19 Jun 2003 10:33:02 +1000 (EST)
Received: (from ggm@localhost)
	by garlic.apnic.net (8.12.9/8.12.9/Submit) id h5J0X1Rh000484;
	Thu, 19 Jun 2003 10:33:01 +1000 (EST)
Date: Thu, 19 Jun 2003 10:33:00 +1000
From: George Michaelson <ggm@apnic.net>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619103300.5798d310.ggm@apnic.net>
In-Reply-To: <20030618192035.507e9a9f.moore@cs.utk.edu>
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
	<kju1ankzkr.fsf@romeo.rtfm.com>
	<20030618144239.0c31eb88.moore@cs.utk.edu>
	<kjptlbkxpr.fsf@romeo.rtfm.com>
	<20030618153329.4fe1ab1c.moore@cs.utk.edu>
	<kjfzm7kmxl.fsf@romeo.rtfm.com>
	<20030618190410.57eda79a.moore@cs.utk.edu>
	<kj65n3km8s.fsf@romeo.rtfm.com>
	<20030618192035.507e9a9f.moore@cs.utk.edu>
Organization: APNIC Pty Ltd
X-Mailer: Sylpheed version 0.9.0claws38 (GTK+ 1.2.10; i386-pc-netbsdelf1.6T)
X-Fruit-Of-The-Month-Club: persimmon
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Just because I *have* a NAT box to use at home doesn't mean I *like* NAT.

I expect to find deployment of IPv6 at home challenging, in part because I've
already spent my 'five-year-plan' funds on networks for home. 

Its the same road-trap digital TV is caught in: people do not rush out and buy
even small communications/technology investments as throw-away devices. TV sets
last for 5-10 years. Hi-Fi sets last even longer. $5 low-fi radios last almost
forever, sliding down the hierarchy from the living room, to the kitchen, to the
garage. 

I expect my Nat box to last another two or three years. I do not expect the
vendor to be able to ship an IPv6 ready image for this box. Therefore I will
have to convince the 'house funding committee' to let me replace this box before
its real end-of-life window. That is hard, set against the cost of painting the
house, or urgent repairs to the steps, or replacing the VHS recorder by a DVD
player.

If a massive volume of IPv6 ready NAT or other boxes arrived on the market right
now, I do not think the take-up would be explosive. The early adopters might buy
in but it would require the *default* configuration to new players to be fully
V6 enabled, and even then the rollover time in the home segment would be
measured in years.

NAT is irrelevant to this IPv6 deployment thing. its neither an obstruction nor
a benefit. The business cycle and non-financial motivations about spending and
lifestyle are just as relevant, if not more so.

If my home network supplier let me have multiple IPv4 DHCP addresses that
were routable behind the cable box, I would probably still keep this NAT box,
even if I did turn off NAT. 

I still have my recordplayer connected to my Hi-Fi even if I don't play records
much.

 cheers

-George




From owner-ietf@ietf.org  Wed Jun 18 21:56:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11059
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 21:56:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SoWe-0002LP-Lx
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 21:47:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SoO9-0002Da-B5
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 21:38:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10744
	for <ietf@ietf.org>; Wed, 18 Jun 2003 21:38:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SoLs-000520-00
	for ietf@ietf.org; Wed, 18 Jun 2003 21:36:36 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SoLr-00051x-00
	for ietf@ietf.org; Wed, 18 Jun 2003 21:36:35 -0400
Received: from rshockeybox.shockey.us (h-69-3-5-197.MCLNVA23.covad.net [69.3.5.197])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h5J1fP704501;
	Wed, 18 Jun 2003 18:41:25 -0700
Message-Id: <5.2.0.9.2.20030618211441.02203e80@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 18 Jun 2003 21:35:12 -0400
To: Paul Vixie <vixie@vix.com>, ietf@ietf.org
From: Richard Shockey <richard@shockey.us>
Subject: Re: myth of the great transition (was US Defense Department
  forma lly adopts IPv6)
In-Reply-To: <g3r85rvsis.fsf@sa.vix.com>
References: <16112.60905.486123.254138@thomasm-u1.cisco.com>
 <16112.60905.486123.254138@thomasm-u1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:07 AM 6/19/2003 +0000, Paul Vixie wrote:

>mat@cisco.com (Michael Thomas) writes:
>
> > Voice challenges this assumption to a very large
> > degree. In fact, I not only want access to 99.99%
> > of the other nodes on the net willing to speak RTP ...
>
>actually i think you probably don't, or rather, won't.
>
>telemarketing by robot is illegal in some places but is
>widely used to detect fax machines or voice-answered
>lines for later use by other robots or by humans.  one
>of the cost components for this kind of activity today
>is a room full of CTI hardware and a DS1 (or better) and
>a willingness to buy blocks of long distance minutes.

Which BTW come July 1 becomes illegal in the US with the implementation of 
the Federal Trade Commission Do Not Call list.

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


>assuming VoIP takes off, the costs of robotic telemarketing
>are going to go way way down.  in particular, it may become
>popular to sweep the E164.ARPA address space looking for
>endpoints, then sweep the resulting RTP endpoints looking
>for live reachable instruments like humans and fax machines.

I'm personally asked this all the time since I co-chair the ENUM WG. I 
think there is going to be some differences here..

A. The way the FTC DNC law was written it is transport neutral. Some of us 
are confident we can apply the law directly to ENUM enabled VoIP.

People forget that the TCPA Telephone Consumer Protection Act in the US and 
the anti junk fax laws were generally effective if a private cause of 
action was permitted. That BTW is the central issue now being debated in 
Congress in the mark up of the Burns-Wyden bill tomorrow.

http://www.spamlaws.com/federal/108s877.html

I would have loved to be able to insert into the bill a provision to make 
RFC 3261 header spoofing illegal as well.

B. The real key here in the protection of VoIP will be my ability to 
control my SIP proxy at the edge as a policy control mechanism.

Personally I would have preferred Charlie Schumers bill which would have 
had a do not spam list but it seems its not going to make it this session.

http://www.spamlaws.com/federal/108s1231.html


>...and that your RTP instrument will have to be one of the
>most violently over-firewalled devices on your network in
>order to remain useful for its intended (by you that is)
>purpose.
>
>maybe i should get back into the blackhole business, but for
>VoIP this time, since it'll be a HUUUUGE market.

The Feds will beat you to market on this one...

>--
>Paul Vixie


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




From owner-ietf@ietf.org  Wed Jun 18 22:00:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11216
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 22:00:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SobL-0002Ts-CM
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 21:52:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SoSn-0002GI-KJ
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 21:43:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10826
	for <ietf@ietf.org>; Wed, 18 Jun 2003 21:43:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SoQX-00052i-00
	for ietf@ietf.org; Wed, 18 Jun 2003 21:41:25 -0400
Received: from [64.47.48.7] (helo=exchange.timetra.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SoQW-00052e-00
	for ietf@ietf.org; Wed, 18 Jun 2003 21:41:24 -0400
Received: from vkompella ([64.47.48.10] RDNS failed) by exchange.timetra.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 18 Jun 2003 18:43:13 -0700
Reply-To: <vkompella@timetra.com>
From: "Vach Kompella" <vkompella@timetra.com>
To: "Paul Hoffman / IMC" <phoffman@imc.org>, <ietf@ietf.org>
Subject: RE: WG review: Layer 2 Virtual Private Networks (l2vpn)
Date: Wed, 18 Jun 2003 18:43:53 -0700
Message-ID: <FNEFIPCNJKDDONJGBCNEOEOAEBAA.vkompella@timetra.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <p05210609bb169f5d968a@[67.126.41.36]>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Importance: Normal
X-OriginalArrivalTime: 19 Jun 2003 01:43:13.0526 (UTC) FILETIME=[259C1160:01C33604]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul,

>
>
> At 1:31 PM -0700 6/18/03, Vach Kompella wrote:
>
> I'm not sure how to argue with the statement "the IETF has done a
> horrible job with a similar working group, so we want our working
> group in the IETF".

Well, how about, we can't agree on IPv6 numbering schemes, so let's find another
standards org to fix that problem.  We can't decide whether site-local is good
for IPv6 or not, so let's find another standards org. ...  What kind of
unmitigated disaster would IKE have been if we had just punted it over to, say,
the ITU?

Alternatively, we can own up that it is OUR problem, i.e., the IETF, and if we
want a solution, we will create one here.  E.g., I'm happier having IPSec than
no security.

<similar problems in IPSEC snipped>

> Er, yes it is. There is no indication that we will do a better job
> than the terrible job we are doing now. What you propose sounds like
> "we're terrible parents for our six children and barely have enough
> time to pay attention to them, but maybe we'll be better with the
> seventh."

No, it's not.  Having a seventh child is an option.  No-one is clamoring for
that seventh child.

It's more like having seven kids and not having enough money for 7 holiday
gifts, and so declaring that one of the kids should go to a foster parent.

> >
> >Do you think the new L2VPN charter addresses these concerns of scoping?  How
> >about the timelines?  Basically, it's going to be a WG issue, chairs and
> >participants, to finish the WG charter items first.
>
> Why do you think that the re-chartered WG will have any more luck
> with these than the current one? There are a zillion hardware vendors
> and service providers who have reasons to want the dozens of
> documents that are in the current WGs, and it takes very little
> effort on their part to promote their views. The IETF structure does
> poorly in such an environment; maybe a different standards body would
> do better.

I thought that Moskowitz and Tso did a pretty good job of not letting new stuff
into IPSec towards the end.

Is there no perceptible difference between the rather open-ended ppvpn charter
and the rather more focused l2vpn/l3vpn charters?  Maybe that was a leading
question :-)

I have rather studiously avoided submitting three new drafts that may address
issues that some folks have raised concerns about.  As usual, thinking up new
thoughts and solutions is a lot more fun than finishing the job at hand.  That's
where individual submissions should stay until the current plate is cleaned up.
No time in the agenda, nothing but mailing list and individual submission
opportunity.

> >
> >Are you talking PWE3 or L2VPN?
>
> Yes. There is a significant amount of spillage between the two.
>

Not really.

> >
> >There are 16 pseudowire types:
> >            0x0001   Frame Relay DLCI
> >            0x0002   ATM AAL5 SDU VCC transport
> >            0x0003   ATM transparent cell transport
> >            0x0004   Ethernet Tagged Mode
> >            0x0005   Ethernet
> >            0x0006   HDLC
> >            0x0007   PPP
> >            0x0008   SONET/SDH Circuit Emulation Service Over MPLS (CEM) [8]
> >            0x0009   ATM n-to-one VCC cell transport
> >            0x000A   ATM n-to-one VPC cell transport
> >            0x000B   IP Layer2 Transport
> >            0x000C   ATM one-to-one VCC Cell Mode
> >            0x000D   ATM one-to-one VPC Cell Mode
> >            0x000E   ATM AAL5 PDU VCC transport
> >            0x000F   Frame-Relay Port mode
> >            0x0010   SONET/SDH Circuit Emulation over Packet (CEP)
> >
> >At least half of these are and have been interoperable.  It is the
> harder (and
> >more arcane, IMHO) PW types that people are having a hard time coming to some
> >sort of compromise.
>
> And why should the IETF care at all about these? There are other fora
> for layer-2 interworking.

OK.  Which of those arcane PWs is relevant to ppvpn?  The ones ppvpn is
concerned with are pretty well established and interoperable.

>
> --Paul Hoffman, Director
> --Internet Mail Consortium
>

-Vach





From owner-ietf@ietf.org  Wed Jun 18 22:52:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12242
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 22:52:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SpNs-00043W-1x
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 22:42:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SpAA-0003su-N3
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 22:28:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11944
	for <ietf@ietf.org>; Wed, 18 Jun 2003 22:28:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sp7r-0005NO-00
	for ietf@ietf.org; Wed, 18 Jun 2003 22:26:11 -0400
Received: from u33.gpu114.samsung.co.kr ([203.254.224.33] helo=mailout3.samsung.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sp7q-0005NJ-00
	for ietf@ietf.org; Wed, 18 Jun 2003 22:26:10 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov  6 2002))
 id <0HGP00901IUMG2@mailout3.samsung.com> for ietf@ietf.org; Thu,
 19 Jun 2003 11:27:58 +0900 (KST)
Received: from ep_mmp1 (localhost [127.0.0.1])
 by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6
 2002)) with ESMTP id <0HGP00JTJIUMIX@mailout3.samsung.com> for ietf@ietf.org;
 Thu, 19 Jun 2003 11:27:58 +0900 (KST)
Received: from daniel7209 ([168.219.203.183])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18
 2003)) with ESMTPA id <0HGP009LBIULHJ@mmp1.samsung.com> for ietf@ietf.org;
 Thu, 19 Jun 2003 11:27:58 +0900 (KST)
Date: Thu, 19 Jun 2003 11:28:11 +0900
From: Soohong Daniel Park <soohong.park@samsung.com>
Subject: test mail
To: ietf@ietf.org
Message-id: <00e101c3360a$6e0b40f0$b7cbdba8@daniel7209>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

sorry








From owner-ietf@ietf.org  Wed Jun 18 23:00:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12552
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 23:00:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SpXQ-0004GP-1U
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 22:52:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SpR7-00044M-NY
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 22:46:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12126
	for <ietf@ietf.org>; Wed, 18 Jun 2003 22:46:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SpOq-0005Qf-00
	for ietf@ietf.org; Wed, 18 Jun 2003 22:43:44 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SpOq-0005Qb-00
	for ietf@ietf.org; Wed, 18 Jun 2003 22:43:44 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP
	id B653C13969; Thu, 19 Jun 2003 02:45:32 +0000 (GMT)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: Richard Shockey <richard@shockey.us>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Message from Richard Shockey <richard@shockey.us> 
	of "Wed, 18 Jun 2003 21:35:12 -0400."
	<5.2.0.9.2.20030618211441.02203e80@shockey.us> 
X-Mailer: MH-E 7.3; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 19 Jun 2003 02:45:32 +0000
Message-Id: <20030619024532.B653C13969@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> Which BTW come July 1 becomes illegal in the US with the implementation of
> the Federal Trade Commission Do Not Call list.

which country's "federal" do you mean?

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

oh, that one.  i guess that means the function will have to move offshore.
THAT'll sure teach those spammers a lesson.



From owner-ietf@ietf.org  Wed Jun 18 23:26:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13099
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 23:26:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Spyg-0005Kw-FU
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 23:20:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SptF-0005CS-DH
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 23:15:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12973
	for <ietf@ietf.org>; Wed, 18 Jun 2003 23:15:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Spqy-0005eO-00
	for ietf@ietf.org; Wed, 18 Jun 2003 23:12:48 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Spqx-0005eL-00
	for ietf@ietf.org; Wed, 18 Jun 2003 23:12:48 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5J3F5M3003358
	for ietf@ietf.org env-from <vjs>;
	Wed, 18 Jun 2003 21:15:05 -0600 (MDT)
Date: Wed, 18 Jun 2003 21:15:05 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306190315.h5J3F5M3003358@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: myth of the great transition 
References: <20030619024532.B653C13969@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Paul Vixie <paul@vix.com>

> ...
> > http://www.ftc.gov/bcp/conline/edcams/donotcall/index.html
>
> oh, that one.  i guess that means the function will have to move offshore.
> THAT'll sure teach those spammers a lesson.

The U.S. FCC wielded the TCPA with reasonable effect against the
(supposedly?) English or Canadian 21st Century "1-900 vote" junk
fax blasters.  See http://www.fcc.gov/eb/News_Releases/nrtcf.html
and http://www.fcc.gov/eb/News_Releases/nr21cen1.html

Related to what you wrote a little while ago, blackhole routes are
easier to deploy against overseas senders of junk IP packets (for most
localized notions of "overseas") than nearby spammers.  Do you get
much spam direct from China or Korea?

But what does this have to L2VPN or the IETF?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Wed Jun 18 23:40:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13436
	for <ietf-web-archive@odin.ietf.org>; Wed, 18 Jun 2003 23:40:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sq0R-0005PG-CD
	for ietf-list@asgard.ietf.org; Wed, 18 Jun 2003 23:22:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Spx0-0005Ko-Gy
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 23:19:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13013
	for <ietf@ietf.org>; Wed, 18 Jun 2003 23:19:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Spuj-0005fB-00
	for ietf@ietf.org; Wed, 18 Jun 2003 23:16:41 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Spuj-0005f2-00
	for ietf@ietf.org; Wed, 18 Jun 2003 23:16:41 -0400
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h5J3ISO1009898;
	Wed, 18 Jun 2003 23:18:29 -0400 (EDT)
Message-Id: <200306190318.h5J3ISO1009898@rtp-core-1.cisco.com>
To: vkompella@timetra.com
cc: "Paul Hoffman / IMC" <phoffman@imc.org>, ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
In-reply-to: Your message of Wed, 18 Jun 2003 18:43:53 -0700.
             <FNEFIPCNJKDDONJGBCNEOEOAEBAA.vkompella@timetra.com> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 18 Jun 2003 23:18:28 -0400
From: Eric Rosen <erosen@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


People need to understand that the purpose of the Pseudowire stuff (PWE3) is
to enable service providers to  offer existing services over IP networks, so
that they can convert their backbones to IP without first requiring that all
their  customers change  their  access equipment.   Producing the  protocols
needed to enable  migration from legacy networks to IP  networks seems to me
to  be quite in  the mainstream  of IETF.   The technical  issues, involving
creating tunnels, multiplexing  sessions through tunnels, performing service
emulation at the  session endpoints, are all issues that  the IETF has taken
up in the past, there is nothing radically different going on here. 

(To those  who think that other  standards organizations can  do this better,
well, representatives from those other organizations feel free to drop in on
the WGs  in question, so  we are familiar  with their level of  expertise on
IP.   Let's just  say that  if we  want to  aid in  the migration  of legacy
networks to IP, these other organizations are not what we would want to rely
on.) 

One can think of the VPWS work  in L2VPN as taking the PWE3 stuff and adding
some IP-based auto-discovery  mechanisms to facilitate provisioning.  Again,
this isn't out of line with what the IETF typically does. 

The VPLS work is  more difficult to position within the IETF,  as it is hard
to  avoid a lot  of stuff  that overlaps  with IEEE  (a standards  org which
really is  worthy of  respect, unlike some  others), and  extending ethernet
over an IP network  is arguably a bad idea.  On the  other hand, the purpose
is the  same as  indicated above; service  providers can migrate  from their
Q-in-Q  ethernet networks  to  IP networks,  without  first requiring  their
customers to switch from an ethernet service to an IP service.  










From owner-ietf@ietf.org  Thu Jun 19 00:13:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14308
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 00:13:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SqdC-0006eg-Sr
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 00:02:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SqLE-0006PZ-Su
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 23:44:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13641
	for <ietf@ietf.org>; Wed, 18 Jun 2003 23:44:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SqIy-0005qZ-00
	for ietf@ietf.org; Wed, 18 Jun 2003 23:41:44 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SqIx-0005qM-00
	for ietf@ietf.org; Wed, 18 Jun 2003 23:41:43 -0400
Subject: RE: NATs are NOT Firewalls
Date: Wed, 18 Jun 2003 20:44:05 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8A4@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: NATs are NOT Firewalls
Thread-Index: AcM17twlGLDuXOI9SQuLyC+nJ16pmgAIP5gw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <Tomson_Eric@Yahoo.fr>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA14308

Eric,

I agree with most of your post but there is something that you have not
grasped IMHO.

It is true that "dissimulating" the private (RFC1918?) address does not
achieve much in terms of security: in order to access:
http://arneill-py.sacramento.ca.us/ipv6mh/ you do not need to know nor
care that the IP address of the web server is 192.168.1.4. Knowing it
might provide limited help way farther down the hacking process though
and is likely to be leaked in things such as SMTP headers anyway.

However, if you are correct in saying that NAT != firewall, you are
mostly _not_ correct in saying that a NATs are not firewalls, as most
NAT boxes indeed are NAT+PAT boxes and {NAT != firewall} applies to
non-PAT things such as one-to-one static NAT (not overloaded) or subnet
natting.
Refrigerator = Frigidaire
Copy machine = Xerox
NAT box      = Linksys

> Eric Tomson wrote:
> 2.circuit level gateways (work mainly at session layer, by
> identifying flows of data and established connections),
> A more advanced device, able to identify "conversations",
> "sessions", is a bit more advanced firewall of type 2.

By your own definition a NAT+PAT box is a type 2 firewall or circuit
level gateway. A pure NAT device (rare) does not care about flows but a
NAT+PAT box (very common) does and maintains hard state about them as
show below:

cisco3640#sh ip nat tr
Pro Inside global        Inside local      Outside local      Outside
global
udp 209.233.126.65:1060  192.168.1.4:1060  206.13.31.12:53
206.13.31.12:53
tcp 209.233.126.65:1263  192.168.1.7:1263  198.133.219.25:80
198.133.219.25:80
tcp 209.233.126.65:25    192.168.1.4:25    ---                ---
tcp 209.233.126.65:80    192.168.1.4:80    ---                ---

Linksys/Netgear/misc home/soho NAT boxes have similar mechanisms. The
first two are originated-from-inside dynamic flows, the last two are
statically punched holes. Note that TCP flows are torn down as soon as
the TCP connection is terminated where UDP flows are torn down with a
timeout; on a Cisco 'show ip nat trans verbose' will show the timeouts.

This hard state is why NAT+PAT boxes have often been compared to
firewalls because _one_ of the features of firewalls is to build this
hard state that allows only return traffic related to traffic originated
from the inside (unless a hole is punched). The security brought by the
NAT+PAT process comes from this hard state; no entry in the translation
table, no traffic. A firewall (or a reflective access-list for Cisco
geeks) builds hard state the same way except that of course it does not
change the address.


> NATs [...] won't control the traffic

This is incorrect for most NAT boxes. Although it is true that the main
two purposes of NAT are saving IPs (one-to-many NAT) and ease
renumbering, it is equally true that if there is no open flow originated
from the inside (or hole punched administratively), a NAT+PAT _DOES_ by
default block traffic originated from the outside, which is a
significant part of why people buy firewalls in the first place: Allow
users to surf but don't open anything except a few ports to a few IPs in
the other direction.

In other words, a NAT+PAT device blocks by default all traffic except
statically punched holes and transient return traffic related to a flow
opened from the inside (specific to a pair of IP addresses and a pair of
ports).

This circuit-level gateway feature is not enough security and must be
complemented with access-lists and stateful inspection but it's one of
the third major building blocks of a firewall. But that's for network
geeks; the sad truth is that when the network admin is lame (grandma or
Joe's Pizza) a windoze 9x PC is safer behind a Linksys than connected
directly to the cable modem.

As of myself I would not call a firewall any device that does not have
stateful packet inspection (free hint to IPv6 vendors ;-)

But by your own definition a NAT+PAT box is a firewall of type 2. Add to
this that when combined with RFC1918 they bring very easy renumbering as
only the outside address has to be changed and you'll understand why
there are so many of them around.

For the record, and since this thread started with IPv6, I am totally
against IPv6 NAT. With IPv4, all we have left at this time are lemons so
there's nothing wrong in making lemonade with them even if we prefer
beer. Although it is part of the job, IPv4 NAT is a royal pain in the
butt that I would gladly live without. But for IPv6 it is not too late.
If the end-to-end principle is a dogma it's not only because IETFers
like dogmas but mostly because NAT plain stinks.

Michel.




From owner-ietf@ietf.org  Thu Jun 19 00:15:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14494
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 00:15:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SqdD-0006em-3e
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 00:02:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SqLn-0006Pb-Iv
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 23:44:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13647
	for <ietf@ietf.org>; Wed, 18 Jun 2003 23:44:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SqJW-0005qi-00
	for ietf@ietf.org; Wed, 18 Jun 2003 23:42:18 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SqJV-0005qf-00
	for ietf@ietf.org; Wed, 18 Jun 2003 23:42:18 -0400
Received: from [63.202.92.152] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h5J3iXrc018932;
	Wed, 18 Jun 2003 20:44:33 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05210606bb16d08451dd@[63.202.92.152]>
In-Reply-To: <FNEFIPCNJKDDONJGBCNEOEOAEBAA.vkompella@timetra.com>
References: <FNEFIPCNJKDDONJGBCNEOEOAEBAA.vkompella@timetra.com>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Wed, 18 Jun 2003 19:40:52 -0700
To: <vkompella@timetra.com>, <ietf@ietf.org>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: RE: WG review: Layer 2 Virtual Private Networks (l2vpn)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 6:43 PM -0700 6/18/03, Vach Kompella wrote:
>  > I'm not sure how to argue with the statement "the IETF has done a
>>  horrible job with a similar working group, so we want our working
>>  group in the IETF".
>
>Well, how about, we can't agree on IPv6 numbering schemes, so let's 
>find another
>standards org to fix that problem. We can't decide whether site-local is good
>for IPv6 or not, so let's find another standards org.

IPv6 is an IP technology. We are supposed to know how to make it 
work. L2VPNs (and half of the interesting parts of 2547bis L2VPNs) 
are outside the scope of our expertise.

>  ...  What kind of
>unmitigated disaster would IKE have been if we had just punted it 
>over to, say,
>the ITU?

Worse, no doubt. But I'm not proposing to send the L2VPN work to an 
organization with no expertise or credibility in the L2 area.

>Alternatively, we can own up that it is OUR problem, i.e., the IETF, and if we
>want a solution, we will create one here.

If we decide that "the problem" is one in our realm, I fully agree. 
But transporting layer 2 stuff over IP is not a problem that affects 
the Internet. It is a problem for the service providers marketing 
departments. The past three yeas have proven that service providers 
can satisfy their customers needs with L3VPNs, with 
somewhat-interoperable L2VPNs, with non-interoperable L2VPNs, and 
with just plain layer 2 circuits. What is "the problem" that the IETF 
needs to standardize?

>   E.g., I'm happier having IPSec than
>no security.

Of course. But we'd both be happier if IPsec worked better as a VPN 
technology, and applications folks would be happier if it worked 
better as an application security technology.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Thu Jun 19 00:25:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14932
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 00:25:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SqdD-0006es-Bl
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 00:02:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SqMF-0006Pd-0z
	for ietf@asgard.ietf.org; Wed, 18 Jun 2003 23:45:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13702
	for <ietf@ietf.org>; Wed, 18 Jun 2003 23:45:04 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SqJy-0005qp-00
	for ietf@ietf.org; Wed, 18 Jun 2003 23:42:46 -0400
Received: from h80ad266c.async.vt.edu ([128.173.38.108] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SqJw-0005ql-00
	for ietf@ietf.org; Wed, 18 Jun 2003 23:42:45 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h5J3iqPZ030084;
	Wed, 18 Jun 2003 23:44:52 -0400
Message-Id: <200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: EKR <ekr@rtfm.com>
Cc: Melinda Shore <mshore@cisco.com>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Your message of "Wed, 18 Jun 2003 16:06:08 PDT."
             <kjbrwvkmu7.fsf@romeo.rtfm.com> 
References: <200306181937.AIN64606@mira-sjc5-c.cisco.com>
            <kjbrwvkmu7.fsf@romeo.rtfm.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1884181137P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 18 Jun 2003 23:44:51 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Wed, 18 Jun 2003 16:06:08 PDT, Eric Rescorla said:
> Melinda Shore <mshore@cisco.com> writes:

> > Not really.  For example, ftp as originally defined doesn't
> > work through NATs, and no standard VoIP or multimedia
> > conferencing protocol works through NAT.  
> None of these things worked real well through firewalls either,
> which is sort of my point.

There's a *crucial* distinction here:

If it doesn't work through a firewall, it's because the firewall is doing
what you ASKED it to do - block certain classes of connections.

If it doesn't work through a NAT, it's because the NAT is FAILING to do what
you asked it to do - allow transparent connections from boxes behind the NAT.

Unless of course you're deploying NAT for some reason *OTHER* than
transparent connections?  Are you trying to get your money's worth because
you paid for the extra-deluxe "works most of the time but breaks some apps"
version?

Or is the only reason you have NAT at all because you bought some vendor's
"connection appliance in a box" that proceeded to NAT you regardless of your
desires?

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

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

iD8DBQE+8TGzcC3lWbTT17ARAh37AKCx4dVLfZxLeJMK7bCvbq/YCt/u4gCgjD6N
Nh3Xr2EjBd4gSFEHuUYD+uc=
=O7Ip
-----END PGP SIGNATURE-----

--==_Exmh_-1884181137P--



From owner-ietf@ietf.org  Thu Jun 19 00:41:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15401
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 00:41:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sr1L-0008A9-TX
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 00:27:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sqyr-0007eu-6R
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 00:25:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14922
	for <ietf@ietf.org>; Thu, 19 Jun 2003 00:24:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sqwa-000671-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:22:40 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SqwZ-00066m-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:22:39 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id CD433ABB5; Wed, 18 Jun 2003 21:30:35 -0700 (PDT)
To: Valdis.Kletnieks@vt.edu
Cc: Melinda Shore <mshore@cisco.com>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 18 Jun 2003 21:30:35 -0700
In-Reply-To: <200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
Message-ID: <kjptlak7tg.fsf@romeo.rtfm.com>
Lines: 41
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Valdis.Kletnieks@vt.edu writes:

> On Wed, 18 Jun 2003 16:06:08 PDT, Eric Rescorla said:
> > Melinda Shore <mshore@cisco.com> writes:
> 
> > > Not really.  For example, ftp as originally defined doesn't
> > > work through NATs, and no standard VoIP or multimedia
> > > conferencing protocol works through NAT.  
> > None of these things worked real well through firewalls either,
> > which is sort of my point.
> 
> There's a *crucial* distinction here:
> 
> If it doesn't work through a firewall, it's because the firewall is doing
> what you ASKED it to do - block certain classes of connections.
> 
> If it doesn't work through a NAT, it's because the NAT is FAILING to do what
> you asked it to do - allow transparent connections from boxes behind the NAT.
> 
> Unless of course you're deploying NAT for some reason *OTHER* than
> transparent connections?  Are you trying to get your money's worth because
> you paid for the extra-deluxe "works most of the time but breaks some apps"
> version?
This seems to me like a false dichotomy. If I were deploying a NAT 
(which I didn't) there would be certain things I would care about
and others I didn't. If I'm already firewalling off these services,
why should I care if NAT blocks them?

> Or is the only reason you have NAT at all because you bought some vendor's
> "connection appliance in a box" that proceeded to NAT you regardless of your
> desires?
Why is it so hard for people here to believe that customers might
actually know what they want, even if you don't happen to think
it's a good idea?

-Ekr


-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 01:10:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15938
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 01:10:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SrQn-0000X3-7V
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 00:53:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SrJ7-0000NU-N0
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 00:45:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15607
	for <ietf@ietf.org>; Thu, 19 Jun 2003 00:45:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrGq-0006Hu-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:43:36 -0400
Received: from tomts10.bellnexxia.net ([209.226.175.54] helo=tomts10-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrGq-0006Hr-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:43:36 -0400
Received: from yahoo.com ([65.93.186.123]) by tomts10-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030619044555.JGMP17964.tomts10-srv.bellnexxia.net@yahoo.com>;
          Thu, 19 Jun 2003 00:45:55 -0400
Date: Thu, 19 Jun 2003 00:45:53 -0400
Subject: Re: myth of the great transition
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Keith Moore <moore@cs.utk.edu>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <20030618153911.49945ac0.moore@cs.utk.edu>
Message-Id: <E8CA8EC9-A210-11D7-84BB-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Wednesday, June 18, 2003, at 03:39  PM, Keith Moore wrote:

>> I think it would be more accurate to say that a NAT contravenes
>> the basic Internet prnciple of universal connectivity.
>
> expecting the network
> to isolate insecure hosts from untrustworthy attackers, or more
> generally, to enforce policy about what kinds of content are
> permitted to pass, has always been a stretch.
>

So where do firewalls fit into your picture? Do they represent for the 
network or for the hosts?

simon


--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Thu Jun 19 01:21:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16223
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 01:21:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sre3-0000nG-GK
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 01:07:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SrSj-0000Yd-8O
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 00:55:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15770
	for <ietf@ietf.org>; Thu, 19 Jun 2003 00:55:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrQS-0006Ka-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:53:32 -0400
Received: from tomts22.bellnexxia.net ([209.226.175.184] helo=tomts22-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrQR-0006KX-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:53:31 -0400
Received: from yahoo.com ([65.93.186.123]) by tomts22-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030619045550.PMEN19768.tomts22-srv.bellnexxia.net@yahoo.com>;
          Thu, 19 Jun 2003 00:55:50 -0400
Date: Thu, 19 Jun 2003 00:55:49 -0400
Subject: Re: NATs are NOT Firewalls
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <ietf@ietf.org>
To: <Tomson_Eric@Yahoo.fr>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <008201c335e8$ea19f3c0$6f00a8c0@tomson.be>
Message-Id: <4B9CE103-A212-11D7-84BB-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wednesday, June 18, 2003, at 06:28  PM, Tomson Eric ((Yahoo.fr)) 
wrote:

> Now, the fact that masking the internal addresses to the external
> world - so that internal hosts can initiate traffic to the outside, 
> but no
> external host can initiate traffic to the inside - brings some basic
> security, is an interesting corollary, but not the primary objective 
> of a
> NAT.

Is this just security through obscurity, or something better?

simon


--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Thu Jun 19 01:21:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16222
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 01:21:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sre3-0000n1-6H
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 01:07:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SrSO-0000YZ-2O
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 00:55:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15766
	for <ietf@ietf.org>; Thu, 19 Jun 2003 00:55:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrQ7-0006KU-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:53:11 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrQ6-0006KR-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:53:10 -0400
Subject: RE: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
Date: Wed, 18 Jun 2003 21:55:34 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8A7@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
Thread-Index: AcM2Gu9Lkb34tBOzR6G+tqF/wLNPqwAA1LHQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <Valdis.Kletnieks@vt.edu>
Cc: "Melinda Shore" <mshore@cisco.com>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA16222

Valdis,

> Valdis Kletnieks wrote:
> If it doesn't work through a firewall, it's because the
> firewall is doing what you ASKED it to do - block certain
> classes of connections.

I'm sorry but it is nothing near being that simple. Although if it does
not work through a firewall, it MAYBE because the firewall does block a
class of traffic (more likely because someone forgot to punch the right
hole), there are _plenty_ of other reasons why it does not work through
a firewall, one of the top ones being asymmetric traffic when there is
more than one exit point and the firewall hard state not being
distributed.
 
> Melinda Shore <mshore@cisco.com> writes:
> None of these things worked real well through firewalls
> either, which is sort of my point.

Melinda's point is perfectly valid. To quote Brian Carpenter, state is
evil and distributed state is worse.
Unfortunately, they are part of the network engineer's life.

Michel.




From owner-ietf@ietf.org  Thu Jun 19 01:30:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16596
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 01:30:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SrfT-0000ne-Uy
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 01:09:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SrUT-0000by-5B
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 00:57:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15802
	for <ietf@ietf.org>; Thu, 19 Jun 2003 00:57:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrSC-0006Kx-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:55:20 -0400
Received: from tomts25.bellnexxia.net ([209.226.175.188] helo=tomts25-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrSB-0006Ku-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:55:19 -0400
Received: from yahoo.com ([65.93.186.123]) by tomts25-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030619045738.OGIP21522.tomts25-srv.bellnexxia.net@yahoo.com>;
          Thu, 19 Jun 2003 00:57:38 -0400
Date: Thu, 19 Jun 2003 00:57:37 -0400
Subject: Re: myth of the great transition
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org, "Putzolu, David" <david.putzolu@intel.com>
To: Keith Moore <moore@cs.utk.edu>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <20030618180003.173167c1.moore@cs.utk.edu>
Message-Id: <8C34455E-A212-11D7-84BB-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>> I wonder if NAT is to ietf discussions as Nazis was
>> to Usenet discussions.

You mean NATzis?

simon

^_^

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Thu Jun 19 01:30:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16624
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 01:30:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sre3-0000nX-QX
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 01:07:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SrTa-0000Zn-JX
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 00:56:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15782
	for <ietf@ietf.org>; Thu, 19 Jun 2003 00:56:43 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrRJ-0006Kr-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:54:25 -0400
Received: from h80ad266c.async.vt.edu ([128.173.38.108] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrRI-0006Ko-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:54:24 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h5J4ugPZ032549;
	Thu, 19 Jun 2003 00:56:42 -0400
Message-Id: <200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: EKR <ekr@rtfm.com>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Your message of "Wed, 18 Jun 2003 21:30:35 PDT."
             <kjptlak7tg.fsf@romeo.rtfm.com> 
References: <200306181937.AIN64606@mira-sjc5-c.cisco.com> <kjbrwvkmu7.fsf@romeo.rtfm.com> <200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
            <kjptlak7tg.fsf@romeo.rtfm.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-510689966P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 19 Jun 2003 00:56:42 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Wed, 18 Jun 2003 21:30:35 PDT, Eric Rescorla said:

> This seems to me like a false dichotomy. If I were deploying a NAT 
> (which I didn't) there would be certain things I would care about
> and others I didn't. If I'm already firewalling off these services,
> why should I care if NAT blocks them?

So it's OK for NAT to break any application that *you* don't want to
let through *your* firewall anyhow.

What's wrong with this picture?  Well.. Sure, if you currently only allow
3 ports through your firewall anyhow, and those 3 applications happen to
be NAT-tolerant, it's probably no impact on YOUR site.

Of course, if you *ever* encounter an application that your site wants to
allow through the firewall, but you discover that you STILL can't deploy it
because NAT breaks it, you'll be wanting some mayonnaise to make that crow
sandwich go down more easily.

You're missing the point that when a firewall breaks things, it's doing
its job.  When a NAT breaks things, it's failing to do its job.

Now let's say a firewall is a pair of suspenders, and a NAT is a belt.  This
makes your position:

"I don't care that my belt unzips my trousers every time I go through a
revolving door, because I'm never in a situation where failure of my
suspenders would be an embarassment".

As Randy Bush says: "I invite my competitors to design their networks this way".

>> Or is the only reason you have NAT at all because you bought some vendor's
>> "connection appliance in a box" that proceeded to NAT you regardless of your
>> desires?
> Why is it so hard for people here to believe that customers might
> actually know what they want, even if you don't happen to think
> it's a good idea?

Tell you what - you round up all the big domains that actually have a clue
about what they want, and who understand the distinction between a firewall and
a NAT (even if they are in the same box), and I'll round up all the users who
are scratching their heads because they have a cablemodem or an ADSL modem
(either ISP-provided or off the shelf at Walmart) that is an all-in-one modem/
router/firewall/NAT, and some stuff Just Does Not Work.

And unfortunately, a lot of the Just Does Not Work stuff are applications
like H.323 and VOIP that Joe Sixpack actually *might* be interested in.


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

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

iD8DBQE+8UKJcC3lWbTT17ARAisHAJ4kXai5UQGrsJQgbLUKkP7qOh8qdACcCQh9
tCrmp5vN5PGjsmSfu1oJf8s=
=y/cv
-----END PGP SIGNATURE-----

--==_Exmh_-510689966P--



From owner-ietf@ietf.org  Thu Jun 19 01:32:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16884
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 01:32:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SrfU-0000nk-Ah
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 01:09:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SrVw-0000c0-AY
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 00:59:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15806
	for <ietf@ietf.org>; Thu, 19 Jun 2003 00:59:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrTf-0006L4-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:56:51 -0400
Received: from vrx.net ([216.13.126.22] helo=ns1.vrx.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SrTe-0006L1-00
	for ietf@ietf.org; Thu, 19 Jun 2003 00:56:50 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-128-181.lsanca1.dsl-verizon.net [4.33.128.181])
	by ns1.vrx.net (Postfix) with ESMTP id 05265D211
	for <ietf@ietf.org>; Thu, 19 Jun 2003 00:59:06 -0400 (EDT)
Mime-Version: 1.0
X-Sender: stef@vrx.net (Unverified)
Message-Id: <v04220804bb169585189c@[192.168.1.14]>
In-Reply-To: <200306181917.MAA15517@gra.isi.edu>
References: <200306181917.MAA15517@gra.isi.edu>
Date: Wed, 18 Jun 2003 17:56:06 -0700
To: ietf@ietf.org
From: Einar Stefferud <Stef@thor.nma.com>
Subject: Re: myth of the great transition (was US Defense Department
 formally adopts IPv6)
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Bob;-)...  And all;-)...

At 12:17 -0700 6/18/03, Bob Braden wrote:
>  *> Keith wrote:
>  *> > If you want to address denial of service issues you need protocol
>  *> > enforcement points.
>  *> 
>  *> NAT is a denial of service attack, not a means of policy enforcement.
>  *> 
>  *> 
>  *> 
>
>Keith,
>
>I think it would be more accurate to say that a NAT contravenes
>the basic Internet prnciple of universal connectivity.
>
>Since 1980 we have believed that universal connectivity was one of the
>great achievements of the Internet design.  Today, one must
>unfortunately question whether universal connectivity can be sustained
>(or is even the right goal) in a networking environment without
>universal trust.  Maybe NATs are, in fact, a result of a very deep
>problem with our architecture.  If you accept that, then there is no
>point in attacking NATs until you can propose a better architectural
>solution to the trust problem (hopefully, there will be one!)
>
>Bob Braden


Here!  Here!  Exactly --  Trust in all the people on the net all the time 
failed with the well received demise of the NSF AUP (1994) and the fact that 
misbehavior then no longer threatened loss of Internet access privileges.

This was not widely recognized as a possible at the time, much like the 
fact that the Internet has no center and hence has no place to locate a 
"Central Control Center" which is another contributor to the loss of trust, 
and which prohibits solving the trust problem with centralized enforcement 
of rules of trust, if any such rules might possibly exist.

This of course is one reason why PKIX is not able to deliver public trust, 
because PKIX requires a single Central Control Center to enforce rules of 
trust (whatever those rules might be), and we have already discussed how it 
is that PKIX CA's suffer from lack of trust induction among their users.

So, one fundamental issue in this whole situation is that the basic "Internet 
Operational Model" that underlays these aspects being discussed here is not a 
realistic model for situations with no available "Center".

I model the Internet more accurately with our present International Economy, 
where again, there is NO CENTER, and thus no place to locate a control center 
for that economy.  The decisions that drive the economy depend on interpersonal 
trust which is developed via multiple channels of information flow derived 
from many different communication paths.  

Trust is only derived from accumulated information obtained from multiple 
channels of information flow.

In the U.S. there is no central control for the National Economy.  And, I have 
been saying for years that pretty much every one that ever had a centrally 
controlled Economy, by now wishes they did not have one.  Even China is 
working its way as carefully as possible to become a free economy, trying 
to avoid the collapse that Russia experienced during such a period of change.

The Internet did it like Russia did it, without understanding that it was 
happening and not dealing with the need for new trust induction tools and 
processes.

So, I think all of you out there will agree that we do not want a return to 
a centrally controlled Internet, even if we could have one, so let's stop 
pretending that such a thing can exist, and start working on ways to induce 
trust among ourselves for all of our own private reasons to have trust among 
us in this "uncontrolled space".

Many hark back to the good old days of the trusted users of he ARPAnet, but 
those days are long gone, when we all had to worry about losing our access 
privileges.  I very well recall my efforts to retain my privileges over those 
years of serving as an independent consultant with no permanent sponsor!

Serving as the "Moderator" of MsgGroup for 11 years from 1975-1986 helped to 
carry me along until 1987 when NSFnet made it easier for me to manage.

From my management consulting experience along the way, I strongly recommend 
that we learn to live together in our "open information economy" and avoid 
attempts to apply central controls to build mutual trust.  

The Internet is a Internetwork of Internets.  It is not a network!

To repeat, it has no center, and further, does not even have any edges.

It is just a manifold of information transit pipes, each of which can be made 
to communicate with any other transmission pipe, by taking appropriate actions,
without permission from any central governing agency!  Not even ICANNic.

Cheers...\Stef;-)... 




From owner-ietf@ietf.org  Thu Jun 19 01:54:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17515
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 01:54:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ss2F-00031v-0O
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 01:32:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Srh6-0000x9-Ek
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 01:10:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15958
	for <ietf@ietf.org>; Thu, 19 Jun 2003 01:10:43 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sreo-0006NW-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:08:23 -0400
Received: from h80ad266c.async.vt.edu ([128.173.38.108] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sren-0006NN-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:08:22 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h5J5AaPZ000402;
	Thu, 19 Jun 2003 01:10:36 -0400
Message-Id: <200306190510.h5J5AaPZ000402@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Michel Py <michel@arneill-py.sacramento.ca.us>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Your message of "Wed, 18 Jun 2003 21:55:34 PDT."
             <963621801C6D3E4A9CF454A1972AE8F504F8A7@server2000.arneill-py.sacramento.ca.us> 
References: <963621801C6D3E4A9CF454A1972AE8F504F8A7@server2000.arneill-py.sacramento.ca.us>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-501085033P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 19 Jun 2003 01:10:35 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Wed, 18 Jun 2003 21:55:34 PDT, Michel Py said:

> I'm sorry but it is nothing near being that simple. Although if it does
> not work through a firewall, it MAYBE because the firewall does block a
> class of traffic (more likely because someone forgot to punch the right
> hole), there are _plenty_ of other reasons why it does not work through
> a firewall, one of the top ones being asymmetric traffic when there is
> more than one exit point and the firewall hard state not being
> distributed.

OK, so firewalls can fail because they're misconfigured or mis-deployed.

Death of the Internet Predicted.  Film at 11.  This is hardly news. Stuff
doesn't work right if you mis-set your netmask, or your default route, or
your nameserver, or whatever...

The point I was making is that if an NNTP connection fails because the firewall
is *configured* to say 'None Shall Pass' (insert Monty Python .wav here ;)
then that is *proper* behavior.  If a VOIP connection fails because the NAT
is saying 'None Shall Pass', then that's *broken* behavior.

I checked RFC3027.  20 *pages* of things that either break horribly over a NAT,
or (as in the Activision example) say "We can hack this to work if we make
the permanent restriction that there has to be a server that's NOT behind a NAT
and clients have to contact it".  Sounds a lot like RFC3344, actually.

Great.  WHo would *EVER* have thought that the biggest market for IP Mobility
was to hack through NAT dain bramage?

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

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

iD8DBQE+8UXKcC3lWbTT17ARAtoUAJ9vyr2uYU2R/Es+8LDbLs1e+OhWHgCgx2U1
OSXBGD6XKAXSCO6onoW8Gq4=
=AhUd
-----END PGP SIGNATURE-----

--==_Exmh_-501085033P--



From owner-ietf@ietf.org  Thu Jun 19 02:06:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24287
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:06:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ss2F-00034q-SK
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 01:32:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Srjt-0001Cs-Cp
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 01:13:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16148
	for <ietf@ietf.org>; Thu, 19 Jun 2003 01:13:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Srhc-0006Qg-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:11:16 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Srhb-0006QY-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:11:15 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 1A033ABB5; Wed, 18 Jun 2003 22:19:13 -0700 (PDT)
To: Valdis.Kletnieks@vt.edu
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 18 Jun 2003 22:19:12 -0700
In-Reply-To: <200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
Message-ID: <kju1amod9r.fsf@romeo.rtfm.com>
Lines: 60
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Valdis.Kletnieks@vt.edu writes:

> On Wed, 18 Jun 2003 21:30:35 PDT, Eric Rescorla said:
> 
> > This seems to me like a false dichotomy. If I were deploying a NAT 
> > (which I didn't) there would be certain things I would care about
> > and others I didn't. If I'm already firewalling off these services,
> > why should I care if NAT blocks them?
> 
> So it's OK for NAT to break any application that *you* don't want to
> let through *your* firewall anyhow.
Yes, it's ok for *my* NAT to do so.

> What's wrong with this picture?  Well.. Sure, if you currently only allow
> 3 ports through your firewall anyhow, and those 3 applications happen to
> be NAT-tolerant, it's probably no impact on YOUR site.
> 
> Of course, if you *ever* encounter an application that your site wants to
> allow through the firewall, but you discover that you STILL can't deploy it
> because NAT breaks it, you'll be wanting some mayonnaise to make that crow
> sandwich go down more easily.
>
> You're missing the point that when a firewall breaks things, it's doing
> its job.  When a NAT breaks things, it's failing to do its job.
Obviously, I disagree.

> Now let's say a firewall is a pair of suspenders, and a NAT is a belt.  This
> makes your position:
> 
> "I don't care that my belt unzips my trousers every time I go through a
> revolving door, because I'm never in a situation where failure of my
> suspenders would be an embarassment".
You've got it absolutely backwards. The fact that the NAT breaks applications
that I don't want to run anyway is a FEATURE, not a bug.

> Tell you what - you round up all the big domains that actually have a clue
> about what they want, and who understand the distinction between a firewall and
> a NAT (even if they are in the same box), and I'll round up all the users who
> are scratching their heads because they have a cablemodem or an ADSL modem
> (either ISP-provided or off the shelf at Walmart) that is an all-in-one modem/
> router/firewall/NAT, and some stuff Just Does Not Work.
> 
> And unfortunately, a lot of the Just Does Not Work stuff are applications
> like H.323 and VOIP that Joe Sixpack actually *might* be interested in.

Ah, the eternal lament of the technocrat who can't understand why the
customers don't want what he knows is so obviously good for them. 

If this were actually a real problem, I'd expect that someone would
be making good money offering service which didn't have this 
problem. Strangely, however, people still seem to buy these products
of which you so obviously disapprove. I guess they don't think the
downside is so terrible.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
           Web Log: http://www.rtfm.com/movabletype




From owner-ietf@ietf.org  Thu Jun 19 02:07:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25428
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:07:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ss2H-00039q-5R
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 01:32:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SrvC-0001zF-PM
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 01:25:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16533
	for <ietf@ietf.org>; Thu, 19 Jun 2003 01:25:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Srsv-0006Xg-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:22:57 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Srsv-0006XS-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:22:57 -0400
Subject: RE: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
Date: Wed, 18 Jun 2003 22:25:21 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8A8@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
Thread-Index: AcM2ITS6kj2o1NFOTSirpC0/X/M5ewAAByKA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <Valdis.Kletnieks@vt.edu>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id CAA25428

> Valdis Kletnieks wrote:
> The point I was making is that if an NNTP connection fails because
> the firewall is *configured* to say 'None Shall Pass' (insert Monty
> Python .wav here ;) then that is *proper* behavior.  If a VOIP
> connection fails because the NAT is saying 'None Shall Pass', then
> that's *broken* behavior.

IMHO what you don't get is that in most cases, BOTH say 'None Shall
Pass' and that would be a normal behavior for both.

Don't get me wrong, I do not defend NAT. The point I was trying to make
is this: it is a waste of time to say that NAT sucks. We know it. For
IPv4, it's too late to change. IMHO, here is the deal: IPv4 NAT does
suck, but there is nothing we can do to remove it; so the only worthy
efforts are 1) maybe try to make it less worse (I will not go as far as
saying better) and 2) let's not make the same mistake with IPv6.

Michel.




From owner-ietf@ietf.org  Thu Jun 19 02:10:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28049
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:10:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ss2I-0003Dn-7w
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 01:32:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ss0m-0002j9-EY
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 01:31:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16776
	for <ietf@ietf.org>; Thu, 19 Jun 2003 01:31:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SryV-0006by-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:28:43 -0400
Received: from sentosa.post1.com ([202.27.17.100])
	by ietf-mx with smtp (Exim 4.12)
	id 19SryU-0006Zb-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:28:42 -0400
Received: (qmail 75822 invoked from network); 19 Jun 2003 05:37:57 -0000
Received: from ida120.ida.gov.sg (HELO pobox.org.sg) (210.24.194.120)
  by sentosa.post1.com with SMTP; 19 Jun 2003 05:37:57 -0000
Message-ID: <3EF14A74.7090504@pobox.org.sg>
Date: Thu, 19 Jun 2003 13:30:28 +0800
From: James Seng <jseng@pobox.org.sg>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en, zh-cn, zh-tw, ja, ko
MIME-Version: 1.0
To: EKR <ekr@rtfm.com>
CC: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>	<20030618130528.400b1f39.moore@cs.utk.edu>	<kj65n3mgdt.fsf@romeo.rtfm.com>	<20030618134424.410d29d1.moore@cs.utk.edu>	<kj1xxrmfln.fsf@romeo.rtfm.com>	<20030618140538.103ea88b.moore@cs.utk.edu> <kju1ankzkr.fsf@romeo.rtfm.com>
In-Reply-To: <kju1ankzkr.fsf@romeo.rtfm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Why should the users be limited to what IT managers decide is good or bad?

Internet is build on dumb network, smart terminal. End-users are suppose 
to be able to put up their own services, not just running some apps. 
This has been the Internet principles and have serves us well so far.

(The telcos model, OTOH, is the inverse, assuming smart network and very 
very dumb terminal.)

-James Seng

> What applications that people want to run--and the IT managers would
> want to enable--are actually inhibited by NAT? It seems to me that
> most of the applications inconvenienced by NAT are ones that IT
> managers would want to screen off anyway.




From owner-ietf@ietf.org  Thu Jun 19 02:11:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28898
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:11:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ss2I-0003EL-Ih
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 01:32:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ss0s-0002jH-9y
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 01:31:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16792
	for <ietf@ietf.org>; Thu, 19 Jun 2003 01:31:09 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sryb-0006cM-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:28:49 -0400
Received: from h80ad266c.async.vt.edu ([128.173.38.108] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SryZ-0006cJ-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:28:48 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h5J5V5PZ001358;
	Thu, 19 Jun 2003 01:31:05 -0400
Message-Id: <200306190531.h5J5V5PZ001358@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: EKR <ekr@rtfm.com>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
             <kju1amod9r.fsf@romeo.rtfm.com> 
References: <200306181937.AIN64606@mira-sjc5-c.cisco.com> <kjbrwvkmu7.fsf@romeo.rtfm.com> <200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu> <kjptlak7tg.fsf@romeo.rtfm.com> <200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
            <kju1amod9r.fsf@romeo.rtfm.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-497407268P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 19 Jun 2003 01:31:00 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Wed, 18 Jun 2003 22:19:12 PDT, Eric Rescorla said:

> You've got it absolutely backwards. The fact that the NAT breaks applications
> that I don't want to run anyway is a FEATURE, not a bug.

And the fact that NAT breaks things that you DO want to run is a <?>

> > And unfortunately, a lot of the Just Does Not Work stuff are applications
> > like H.323 and VOIP that Joe Sixpack actually *might* be interested in.
> 
> Ah, the eternal lament of the technocrat who can't understand why the
> customers don't want what he knows is so obviously good for them. 

No, the lament of a technocrat who can't deploy things that customers DO want
because NAT breaks them.

Find a user.  See if they'd be interested in video or voice over IP.  Watch
them say "ooh... that sounds cool".  Then tell them it would be unreliable
and you could only use it to talk to other users some of the time, because
a lot of users are on these things called NATs, and watch enthusiasm wane.


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

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

iD8DBQE+8UqUcC3lWbTT17ARAr35AKDqvHhpZIMmNUh1sW/n/OKsCRBu2wCgh9y9
05pisnzYtTrmo8kIRq+q2nk=
=YuYM
-----END PGP SIGNATURE-----

--==_Exmh_-497407268P--



From owner-ietf@ietf.org  Thu Jun 19 02:15:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29891
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:15:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SseY-00011t-Ac
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 02:12:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ss3l-0003LC-68
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 01:34:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17054
	for <ietf@ietf.org>; Thu, 19 Jun 2003 01:34:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ss1U-0006h7-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:31:48 -0400
Received: from dhcp1.se.kurtis.pp.se ([195.43.225.70] helo=laptop2.kurtis.autonomica.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ss1T-0006h4-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:31:47 -0400
Received: from kurtis.pp.se (localhost [127.0.0.1])
	by laptop2.kurtis.autonomica.se (8.12.9/8.10.2) with ESMTP id h5J5Y0FT013709;
	Thu, 19 Jun 2003 07:34:01 +0200 (CEST)
Date: Thu, 19 Jun 2003 07:33:54 +0200
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
Content-Type: text/plain; charset=US-ASCII; format=fixed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "Pekka Savola" <pekkas@netcore.fi>,
        "Harald Tveit Alvestrand" <harald@alvestrand.no>, <ietf@ietf.org>
To: <vkompella@timetra.com>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <FNEFIPCNJKDDONJGBCNEGENIEBAA.vkompella@timetra.com>
Message-Id: <9DC81556-A217-11D7-9791-000393A638B2@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
X-Pgp-Rfc2646-Fix: 1
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>> If you use LDP, it is NOT a routing protocol.  The specific mode of 
>>> use
>>> (targeted LDP) is already described in RFC 3036.  The FECs are
>>> different, but
>>> the FEC TLV was defined in such a way as to be extensible.
>>
>> And when you want to do this inter-domain? Everything else seems to
>> have made it's way into BGP so I think that Pekkas concerns are 
>> valid...
>
> That's only because the IETF hasn't made security easy enough, light 
> enough, or
> something.  Now some people use the argument that everything should go 
> into BGP
> because "opening another port into the provider network is a security 
> breach."
> Why is port 646 (LDP) any more insecure than port 179 (BGP)?

Well, I think it's more to it than this. BGP doesn't traverse 
firewalls, at least not in most cases. I think the reason more and more 
is being put into these protocols is because "they are there". It's 
simply easier than thinking about the implications of doing this.
>>>
>>> not
>>> necessarily go down well with you either, but think of MPLS as a
>>> logical FR.
>>> Providers do not want to change their infrastructure, e.g., replace a
>>> FR cloud
>>> with an ATM cloud, then with SONET or GigE.  That's mega-expensive.  
>>> By
>>> abstracting the L2 using MPLS, they can provide the L2VPN service
>>> without
>>> wholesale infrastructure replacement.
>>
>> Most of these providers have bought what their vendor told them to 
>> buy,
>> but let's not go into that here.
>>

Somehow I didn't think this comment would go unnoticed.  ;-)

>
> Sheesh!  No, let's go there.  You're talking about my potential 
> customers, and I
> want to know if they really are so dense that I shouldn't have been 
> spending all
> this time working on a protocol - I could have just given them a 
> couple of
> high-priced tin cans and a piece of string.

Notice that I have been one of those customers. Actually one of the 
largest outside the US. I have spent more time listening and talking to 
vendors on these issues than I like to think about. What struck me was 
how often vendors would come and tell me that provider Y bought this, 
so this should work for you to. When you then asked the vendors to go 
the economics of these decisions, and also the economics of the 
alternatives - you get everything from false and fabricated figures to 
vendors who simply can not answer. I actually remember very few 
occasions  when I got a full explanation of why a certain technology 
would help me and where I could see the benefits.

> Who exactly the IETF is going to be providing protocols for?  For 
> protocols such
> as these, it is the providers who deploy them.  You claim that most of 
> the
> providers have little or no discernment.  Let's give credit to the 
> providers.
> There are a large number of them who know what they are doing.  Many 
> of them
> participate in the standards.

Providers go with technology that is a) cheap b) hight margin. Did 
providers start selling MPLS based VPNs (L2 & L3) because the demand 
was so huge? No, some providers and vendors created the demand. For 
some providers this works very well and fitted the strategy.

Yes, there are providers who work on standards in the IETF. 
Unfortunately I think they are way to few though.

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.2

iQA/AwUBPvFLR6arNKXTPFCVEQJ3LgCgzDrvaeUi0j/xWKhBhPNWic9fC2oAoMEj
sTC9ToVkbZP6CRHO/q1uXp64
=rSyl
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Thu Jun 19 02:29:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00893
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:29:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SseY-00012E-Kg
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 02:12:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ss49-0003LK-5V
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 01:34:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17074
	for <ietf@ietf.org>; Thu, 19 Jun 2003 01:34:32 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ss1s-0006hV-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:32:12 -0400
Received: from h80ad266c.async.vt.edu ([128.173.38.108] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ss1q-0006hS-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:32:11 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h5J5YTPZ001409;
	Thu, 19 Jun 2003 01:34:29 -0400
Message-Id: <200306190534.h5J5YTPZ001409@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: S Woodside <sbwoodside@yahoo.com>
Cc: Tomson_Eric@Yahoo.fr, ietf@ietf.org
Subject: Re: NATs are NOT Firewalls 
In-Reply-To: Your message of "Thu, 19 Jun 2003 00:55:49 EDT."
             <4B9CE103-A212-11D7-84BB-000393414368@yahoo.com> 
References: <4B9CE103-A212-11D7-84BB-000393414368@yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-496823100P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 19 Jun 2003 01:34:28 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Thu, 19 Jun 2003 00:55:49 EDT, S Woodside said:
> On Wednesday, June 18, 2003, at 06:28  PM, Tomson Eric ((Yahoo.fr)) 
> wrote:
> 
> > Now, the fact that masking the internal addresses to the external
> > world - so that internal hosts can initiate traffic to the outside, 
> > but no
> > external host can initiate traffic to the inside - brings some basic
> > security, is an interesting corollary, but not the primary objective 
> > of a
> > NAT.
> 
> Is this just security through obscurity, or something better?

Security through obscurity.  See Bellovin's paper on enumerating through a NAT.

Steven M. Bellovin, "A Technique for Counting NATted Hosts. Proc. Second
Internet Measurement Workshop, November 2002.

http://www.research.att.com/~smb/papers/fnat.pdf  (or fnat.ps if you prefer)

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

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

iD8DBQE+8UtkcC3lWbTT17ARAsoiAJ47kcIEja1OwHXn+pXyHPI2mHxlHQCePd6I
IZFJmQowyly9e8+yZUNrc1Y=
=tg0z
-----END PGP SIGNATURE-----

--==_Exmh_-496823100P--



From owner-ietf@ietf.org  Thu Jun 19 02:40:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01264
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:40:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SseZ-00013G-0w
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 02:12:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ss8P-0003Ph-Km
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 01:38:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17133
	for <ietf@ietf.org>; Thu, 19 Jun 2003 01:38:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ss68-0006ii-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:36:36 -0400
Received: from sentosa.post1.com ([202.27.17.100])
	by ietf-mx with smtp (Exim 4.12)
	id 19Ss67-0006iV-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:36:35 -0400
Received: (qmail 75902 invoked from network); 19 Jun 2003 05:45:57 -0000
Received: from ida120.ida.gov.sg (HELO pobox.org.sg) (210.24.194.120)
  by sentosa.post1.com with SMTP; 19 Jun 2003 05:45:57 -0000
Message-ID: <3EF14C55.9020409@pobox.org.sg>
Date: Thu, 19 Jun 2003 13:38:29 +0800
From: James Seng <jseng@pobox.org.sg>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en, zh-cn, zh-tw, ja, ko
MIME-Version: 1.0
To: "Fleischman, Eric" <eric.w.fleischman@boeing.com>
CC: EKR <ekr@rtfm.com>, Keith Moore <moore@cs.utk.edu>, pbaker@verisign.com,
        Ronald.vanderPol@rvdp.org, aarsenau@bbn.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
References: <5B58696DB20B9140AD20E0685C573A6402992D7B@xch-nw-09.nw.nos.boeing.com>
In-Reply-To: <5B58696DB20B9140AD20E0685C573A6402992D7B@xch-nw-09.nw.nos.boeing.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

If you need a secure zone, and you want a firewall, then should install 
a firewall. You should not put an NAT thinking that it is also a firewall.

But I agree with you that NAT is here to stay.

-James Seng

Fleischman, Eric wrote:
> Eric Rescorla [mailto:ekr@rtfm.com] wrote:
> 
> 
>>>similarly, people who install NAT usually don't realize how much this
>>>costs them in lost functionality and reliability.
> 
> 
>>Really? You have evidence of this?
> 
> 
>>I don't either, but my intuition is that you're wrong.  Once you have
>>decided to have a firewall in place (which you may think is evil, but
>>I consider pretty much a necessary evil), I suspect that most people
>>suffer almost not at all from having a NAT.
> 
> 
> I believe that Eric is pointing out an important point: many deployments of NATs have nothing to do with IPv4 address conservation. Rather, they are firewall adjuncts implemented to hide internal networks from outside scrutiny and direct access. 
> 
> One point where I disagree with my IPv6-advocating friends is that I expect firewall-related NATs to continue to be deployed within Internet (including IPv6) environments until such a time as real-time-protocol and peer-to-peer-protocol friendly "distributed firewall" (policy zones) variants become the preferable "due diligence" alternative for CIOs.
> 
> 
> 
> 




From owner-ietf@ietf.org  Thu Jun 19 02:40:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01292
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:40:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SseZ-00014R-Hc
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 02:12:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SsE4-0003YV-Ey
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 01:44:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17261
	for <ietf@ietf.org>; Thu, 19 Jun 2003 01:44:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SsBn-0006ko-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:42:27 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SsBm-0006kf-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:42:27 -0400
Subject: RE: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
Date: Wed, 18 Jun 2003 22:44:50 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8A9@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
Thread-Index: AcM2JAPq3XW23pJQTjaa4gnXrgYfbgAAIIkw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <Valdis.Kletnieks@vt.edu>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id CAA01292

Valdis,


> Valdis Kletnieks wrote:
> And unfortunately, a lot of the Just Does Not Work stuff are
> applications like H.323 and VOIP that Joe Sixpack actually
> *might* be interested in.

Unfortunately, there is no single reason [protocol or app xyz] does not
work over NAT. When [protocol or app xyz] does not work, it's a
combination of _two_ things.

1. The protocol designer designed a protocol that is not NAT-capable
therefore the protocol designer is stupid.

2. The network administrator tries to run a protocol that is not
NAT-capable over NAT therefore the network administrator is stupid.

As a protocol designer, I will say that the network administrator is the
one being stupid because if s/he even understood the basics of protocol
design s/he would understand why I have to embed the port number in the
packet.

As a network administrator, I will say that the protocol designer is the
one being stupid because if s/he had any clue about what it takes to
operate a network s/he would not have designed a protocol that could not
cross NAT.

Conclusion: this leads us nowhere.

Michel.




From owner-ietf@ietf.org  Thu Jun 19 02:43:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01601
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:43:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sseb-00018M-3E
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 02:12:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SsOz-0003yF-Lq
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 01:56:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17651
	for <ietf@ietf.org>; Thu, 19 Jun 2003 01:56:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SsMi-0006sn-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:53:44 -0400
Received: from cust-smtp1.radiolinja.fi ([213.161.33.208])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SsMi-0006sk-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:53:44 -0400
Received: from EMCL (rl045112.radiolinja.net [213.161.45.112])
	by cust-smtp1.radiolinja.fi (Postfix) with SMTP
	id 8FA0A4000B; Thu, 19 Jun 2003 08:55:57 +0300 (EEST)
From: "=?UTF-8?Q?John_Loughney?=" <john.loughney@kolumbus.fi>
To: <mshore@cisco.com>, <ekr@rtfm.com>, <ietf@ietf.org>
Subject: =?UTF-8?Q?Re:_myth_of_the_great_transition_(was_US_Defense_D?=
	=?UTF-8?Q?epartment_forma_lly_adopts_IPv6)?=
Date: Fri, 20 Jun 2003 08:53:04 +0000
Message-Id: <1056099184948>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Mailer: EMCL v2.20
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id CAA01601

Eric,

With due respects, there is a flaw in your thinking. Many ISPs give users NATed adresses, without users really knowing or understanding what they are.  When the users try applications or serves which fail because of the non-transparency, the users may not know the cause of the failures.
I had some VPN software that fails due to NATs in hotels, for example. Support people told me that the hotel used NATs for security - I sent a log showing all of the probes my macine had from inside the network.
My main point is that users & providers are often confused about NATs.
John 

> What applications that people want to run--and the IT managers would
> want to enable--are actually inhibited by NAT? It seems to me that
> most of the applications inconvenienced by NAT are ones that IT
> managers would want to screen off anyway.                   



From owner-ietf@ietf.org  Thu Jun 19 02:44:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01705
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:44:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sseb-00018h-Ev
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 02:12:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SsPz-0003yV-DG
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 01:57:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17677
	for <ietf@ietf.org>; Thu, 19 Jun 2003 01:57:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SsNi-0006tD-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:54:46 -0400
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SsNh-0006tA-00
	for ietf@ietf.org; Thu, 19 Jun 2003 01:54:46 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0.6)
  with ESMTP-TLS id 242173; Thu, 19 Jun 2003 00:56:42 -0500
Message-ID: <3EF150AF.6080703@ehsco.com>
Date: Thu, 19 Jun 2003 00:57:03 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: Melinda Shore <mshore@cisco.com>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
References: <200306181937.AIN64606@mira-sjc5-c.cisco.com>            <kjbrwvkmu7.fsf@romeo.rtfm.com> <200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
In-Reply-To: <200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 6/18/2003 10:44 PM Valdis.Kletnieks@vt.edu wrote:

>> Melinda Shore <mshore@cisco.com> writes:

>> None of these things worked real well through firewalls either, which
>> is sort of my point.

> If it doesn't work through a firewall, it's because the firewall is
> doing what you ASKED it to do - block certain classes of connections.
>
> If it doesn't work through a NAT, it's because the NAT is FAILING to do
> what you asked it to do - allow transparent connections from boxes
> behind the NAT.

Exactly. I can tell a firewall to get out of the way (stupid as that may
be in some cases) and the application protocols will function as designed
and expected. I cannot tell a NAT to do that, but instead must first
educate the vendor about the protocol that's being blocked, wait for them
to do their market research and/or prioritize the application among their
Great List of Applications They Have Broken, and then maybe one day get a
patch that actually spoofs the protocol well enough for it to work with a
middlebox in the way. There are some (very few) exceptions to the latter
routine, but that's the usual dance.

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




From owner-ietf@ietf.org  Thu Jun 19 02:44:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01881
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:44:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ssew-0001JI-Eh
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 02:12:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SsXz-0006h2-51
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 02:05:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23185
	for <ietf@ietf.org>; Thu, 19 Jun 2003 02:05:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SsVi-0006um-00
	for ietf@ietf.org; Thu, 19 Jun 2003 02:03:02 -0400
Received: from laptop2.kurtis.autonomica.se ([192.71.80.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SsVg-0006ub-00
	for ietf@ietf.org; Thu, 19 Jun 2003 02:03:01 -0400
Received: from kurtis.pp.se (localhost [127.0.0.1])
	by laptop2.kurtis.autonomica.se (8.12.9/8.10.2) with ESMTP id h5J64kFT013765;
	Thu, 19 Jun 2003 08:04:46 +0200 (CEST)
Date: Thu, 19 Jun 2003 08:00:10 +0200
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
Content-Type: text/plain; charset=US-ASCII; format=fixed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Paul Hoffman / IMC <phoffman@imc.org>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <p05210609bb169f5d968a@[67.126.41.36]>
Message-Id: <490A5B80-A21B-11D7-9791-000393A638B2@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
X-Pgp-Rfc2646-Fix: 1
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On torsdag, jun 19, 2003, at 01:17 Europe/Stockholm, Paul Hoffman / IMC 
wrote:

> (Humorously, the very large service provider who doesn't use MPLS in 
> their core says that it usually only takes one or more sentences to 
> convince the prospective customer that MPLS is not needed.)

My experience as well. I lost count of how many times I had the 
following conversation :

C: But MPLS gives me encryption!
Me: Err, nope.
C: Oh? But that is what Vendor X and provider Y told me?
Me: Have you looked at the technology?
C: No....

Re-iterate.

I have had the same discussion with C replaced with provides. That is 
when I got scared.

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.2

iQA/AwUBPvFRbaarNKXTPFCVEQJ2ZQCgxe6vitUPn/VRssdCiXcXeJicTicAnAyk
ahH4o/EXIRMcShIVmTKaA9NO
=cC4C
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Thu Jun 19 02:48:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02202
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 02:48:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ssex-0001Nr-Ll
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 02:12:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ssc9-0008KU-0u
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 02:09:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27387
	for <ietf@ietf.org>; Thu, 19 Jun 2003 02:09:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SsZr-00070M-00
	for ietf@ietf.org; Thu, 19 Jun 2003 02:07:19 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SsZr-00070J-00
	for ietf@ietf.org; Thu, 19 Jun 2003 02:07:19 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 5E38C13968; Thu, 19 Jun 2003 06:09:05 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department
References: <v04220804bb169585189c@[192.168.1.14]>
From: Paul Vixie <vixie@vix.com>
Date: 19 Jun 2003 06:09:05 +0000
In-Reply-To: <v04220804bb169585189c@[192.168.1.14]>
Message-ID: <g3llvyvbsu.fsf@sa.vix.com>
Lines: 28
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> The Internet is a Internetwork of Internets.  It is not a network!
> 
> To repeat, it has no center, and further, does not even have any edges.

that's not a useful vocabulary.  try this one:

   1 - Connection Taxonomy

   1.1. The Internet is a "network of networks", where the component
   networks are called Autonomous Systems (AS), each having a unique AS
   Number (ASN).

   1.2. Connections inside an AS are called "Interior" (or sometimes
   "backbone"), and their security policies are set according to local
   needs, usually based on business or technical requirements.

   1.3. Connections between ASs are called "Border" (or sometimes
   "peering"), and their security policies are set bilaterally according to
   the joint needs of the interconnecting parties.

   1.4. Connections between an AS and its traffic sources (generators) and
   traffic sinks (consumers) are called "Edge" (or sometimes "customer"),
   and their security policies are generally, by long standing tradition,
   inconsistent.

that's from http://www.icann.org/committees/security/sac004.txt, fyi.
-- 
Paul Vixie



From owner-ietf@ietf.org  Thu Jun 19 03:08:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02825
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 03:08:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19StCu-00074m-JL
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 02:47:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ssgi-00027W-UL
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 02:14:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29787
	for <ietf@ietf.org>; Thu, 19 Jun 2003 02:14:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SseR-00078J-00
	for ietf@ietf.org; Thu, 19 Jun 2003 02:12:03 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SseR-000780-00
	for ietf@ietf.org; Thu, 19 Jun 2003 02:12:03 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 575D813968; Thu, 19 Jun 2003 06:13:53 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: myth of the great transition
References: <200306190315.h5J3F5M3003358@calcite.rhyolite.com>
From: Paul Vixie <vixie@vix.com>
Date: 19 Jun 2003 06:13:53 +0000
In-Reply-To: <200306190315.h5J3F5M3003358@calcite.rhyolite.com>
Message-ID: <g3he6mvbku.fsf@sa.vix.com>
Lines: 21
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

vjs@calcite.rhyolite.com (Vernon Schryver) writes:

> Related to what you wrote a little while ago, blackhole routes are
> easier to deploy against overseas senders of junk IP packets (for most
> localized notions of "overseas") than nearby spammers.  Do you get
> much spam direct from China or Korea?

before i started adding /8's to my personal mail filtering system, i used
to get a hell of a lot of direct spam from chinanet customers.  nowadays
i get very little direct spam from china or korea, just a lot of open proxy
and open relay spam.  so, i see your point.

i guess where this has to lead to is respected and enforced treaties
involving property and privacy, which is like saying everything will be
OK once we invent faster than light communications.

> But what does this have to L2VPN or the IETF?

now that, i just don't know.  i was just walking by and smelled the fire.
-- 
Paul Vixie



From owner-ietf@ietf.org  Thu Jun 19 03:10:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02951
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 03:10:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19StUd-00089J-Sv
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 03:05:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19StJy-0007pw-Eu
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 02:54:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02389
	for <ietf@ietf.org>; Thu, 19 Jun 2003 02:54:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19StHh-0000Az-00
	for ietf@ietf.org; Thu, 19 Jun 2003 02:52:37 -0400
Received: from laptop2.kurtis.autonomica.se ([192.71.80.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 19StHg-0000Aw-00
	for ietf@ietf.org; Thu, 19 Jun 2003 02:52:36 -0400
Received: from kurtis.pp.se (localhost [127.0.0.1])
	by laptop2.kurtis.autonomica.se (8.12.9/8.10.2) with ESMTP id h5J6snFT013788;
	Thu, 19 Jun 2003 08:54:49 +0200 (CEST)
Date: Thu, 19 Jun 2003 08:54:44 +0200
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
Content-Type: text/plain; charset=US-ASCII; format=fixed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: vkompella@timetra.com, "Paul Hoffman / IMC" <phoffman@imc.org>,
        ietf@ietf.org
To: erosen@cisco.com
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <200306190318.h5J3ISO1009898@rtp-core-1.cisco.com>
Message-Id: <E852B0C2-A222-11D7-9791-000393A638B2@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
X-Pgp-Rfc2646-Fix: 1
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On torsdag, jun 19, 2003, at 05:18 Europe/Stockholm, Eric Rosen wrote:

> People need to understand that the purpose of the Pseudowire stuff 
> (PWE3) is
> to enable service providers to  offer existing services over IP 
> networks, so
> that they can convert their backbones to IP without first requiring 
> that all
> their  customers change  their  access equipment.   Producing the  
> protocols
> needed to enable  migration from legacy networks to IP  networks seems 
> to me
> to  be quite in  the mainstream  of IETF.   The technical  issues, 
> involving
> creating tunnels, multiplexing  sessions through tunnels, performing 
> service
> emulation at the  session endpoints, are all issues that  the IETF has 
> taken
> up in the past, there is nothing radically different going on here.

But how many of these protocols do we need? And how do we want this 
done?

We are complaining that the IETF have to much work, and still we 
replicate the same functionality in several WGs....

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.2

iQA/AwUBPvFeN6arNKXTPFCVEQLVIgCfXq5oAs5gjeynps93pJOp/ssGNAMAn1ne
a9jFlbHw84uSCivXKDF4Sex7
=kaRD
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Thu Jun 19 03:52:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03812
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 03:52:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Su42-00022t-MD
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 03:42:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Su1D-0001eR-FI
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 03:39:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03504
	for <ietf@ietf.org>; Thu, 19 Jun 2003 03:39:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Styw-0000SU-00
	for ietf@ietf.org; Thu, 19 Jun 2003 03:37:18 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Styv-0000SK-00
	for ietf@ietf.org; Thu, 19 Jun 2003 03:37:17 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h5J7d0016249;
	Thu, 19 Jun 2003 10:39:01 +0300
Date: Thu, 19 Jun 2003 10:39:00 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Vach Kompella <vkompella@timetra.com>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>
Subject: RE: WG review: Layer 2 Virtual Private Networks (l2vpn)
In-Reply-To: <FNEFIPCNJKDDONJGBCNEOENBEBAA.vkompella@timetra.com>
Message-ID: <Pine.LNX.4.44.0306191024360.14861-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 18 Jun 2003, Vach Kompella wrote:
> > > - the IETF is too large, so we shouldn't be adding more work
> >
> > Yes.
> 
> So we should not do any new work?!

We should focus on the work that is more integral to IP and the Internet.

> > 1. Virtual Private LAN Service.  This is Internet-wise ethernet bridging
> > over routing protocols such as BGP, IS-IS, etc; further, this has
> > typically little respect for security implications which are implicit (or
> > even explicit) in LAN networks.
> >
> > So, my main points are:
> >
> >  - we must not overload routing protocols and such infrastructure (IMHO,
> > this seems an inevitable path the work would go towards..)
> 
> If you use LDP, it is NOT a routing protocol.  The specific mode of use
> (targeted LDP) is already described in RFC 3036.  The FECs are different, but
> the FEC TLV was defined in such a way as to be extensible.

Then LDP has been quite carefully cloaked as being one ("graceful restart 
for LDP, ..") :-)

The problem is of course also with the statement "If you use LDP..".  But
there also seem to be some interests in placing stuff elsewhere, like 
in BGP.

> >  - we must not create complexity by deploying ethernet bridging all over
> > the Internet.  Our work should be focused on making IP work, not
> > specifying Ethernet-over-IP (or worse, Ethernet-over-IP as a *service*).
> 
> Primarily, folks want to use it as in "Ethernet-over-MPLS".  That may not
> necessarily go down well with you either, but think of MPLS as a logical FR.
> Providers do not want to change their infrastructure, e.g., replace a FR cloud
> with an ATM cloud, then with SONET or GigE.  That's mega-expensive.  By
> abstracting the L2 using MPLS, they can provide the L2VPN service without
> wholesale infrastructure replacement.

Bridging networks at layer _3_ with VPN's is a bit questionable, but that 
is a bit more in our radar.  I don't think this is something we can 
endorse, as a model.
 
> >  - it is architecturally wrong: use different subnets, period -- that's
> > what those are meant for in the first place!
> 
> Use different subnets to create VPNs?  I don't understand what you mean.  VPLS
> and VPWS address a requirement for multiple domains (aka VPNs), logically
> distinct from and invisible to each other.

Why would you want to do something like:

                     __-----___
 Ethernet           (          )         The _same_ Ethernet
  segment =======  (  Internet  )  ===== segment!
                    (__     ___)
                       -----
Instead, build two separate ethernet segments: one with IP addressing from 
1.1.1.0/24 and the other from 1.1.2.0/24.  You may even want to build a L3 
VPN between the two.

But Ethernet?  That seems misguided.

> > 2. Virtual Private Wire Service
> >
> > This is slightly better as you're "only" performing point-to-point
> > communication.  Same considerations as above apply, to a slightly lesser
> > extent.
> >
> > Btw. how is this different from currently-specified GRE tunneling?  It
> > being made a "service"?
> 
> GRE-tunneling is one option, but only for the transport of the VC.  However, you
> need a demux field to identify the VC that you are carrying.  Carrying one
> customer VC between a pair of PEs is obviously not adequate.

I meant GRE tunneling between CPE's. :-)

> Tunneling is not new in the IETF.  The fact that you are tunneling what may be
> non-IP packets seems to be giving you the heebie-jeebies.  Why?  What about the
> tn3270, dlsw, netbios over ip work that has gone on in the past?  A little
> massaging to make the packet look like data to be carried over an IP network,
> and some implementation details at the edges.

I remember the multipoint media happen to have some assumptions about the 
network, e.g. the use of interpacket delay and the use collision 
detection.  These change a lot of when you expand the scope of an Ethernet 
beyond a physical segment.  Of course, these may not be always 
problematic, if you require switched Ethernet segments, but the thought is 
worrisome regardless.

Moreover, we work on an IP layer.  We enable IP layer to be able to handle 
our tasks.  If there is some problem why we cannot just use different IP 
subnets between the two (or multiple) end-points, we need to fix that 
problem, not burrow even further down the ISO layers.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From owner-ietf@ietf.org  Thu Jun 19 04:10:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04310
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 04:10:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SuNT-0002xs-7B
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 04:02:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SuKe-0002ik-TY
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 03:59:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04055
	for <ietf@ietf.org>; Thu, 19 Jun 2003 03:59:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SuIN-0000ak-00
	for ietf@ietf.org; Thu, 19 Jun 2003 03:57:23 -0400
Received: from garlic.amaranth.net ([208.254.46.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SuIN-0000ah-00
	for ietf@ietf.org; Thu, 19 Jun 2003 03:57:23 -0400
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226])
	(authenticated (0 bits))
	by garlic.amaranth.net (8.11.7/8.11.7) with ESMTP id h5J7xfq19435
	(using TLSv1/SSLv3 with cipher RC4-SHA (128 bits) verified NO);
	Thu, 19 Jun 2003 03:59:42 -0400
Message-Id: <5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 19 Jun 2003 03:46:40 -0400
To: ietf@ietf.org
From: Daniel Senie <dts@senie.com>
Subject: Re: myth of the great transition (was US Defense Department
  forma lly adopts IPv6) 
Cc: ietf@ietf.org
In-Reply-To: <200306190531.h5J5V5PZ001358@turing-police.cc.vt.edu>
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT." <kju1amod9r.fsf@romeo.rtfm.com>
 <200306181937.AIN64606@mira-sjc5-c.cisco.com>
 <kjbrwvkmu7.fsf@romeo.rtfm.com>
 <200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
 <kjptlak7tg.fsf@romeo.rtfm.com>
 <200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
 <kju1amod9r.fsf@romeo.rtfm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 01:31 AM 6/19/2003, Valdis.Kletnieks@vt.edu wrote:

>On Wed, 18 Jun 2003 22:19:12 PDT, Eric Rescorla said:
>
> > You've got it absolutely backwards. The fact that the NAT breaks 
> applications
> > that I don't want to run anyway is a FEATURE, not a bug.
>
>And the fact that NAT breaks things that you DO want to run is a <?>
>
> > > And unfortunately, a lot of the Just Does Not Work stuff are applications
> > > like H.323 and VOIP that Joe Sixpack actually *might* be interested in.
> >
> > Ah, the eternal lament of the technocrat who can't understand why the
> > customers don't want what he knows is so obviously good for them.
>
>No, the lament of a technocrat who can't deploy things that customers DO want
>because NAT breaks them.
>
>Find a user.  See if they'd be interested in video or voice over IP.  Watch
>them say "ooh... that sounds cool".  Then tell them it would be unreliable
>and you could only use it to talk to other users some of the time, because
>a lot of users are on these things called NATs, and watch enthusiasm wane.

Find innovative company that finds a way to make VOIP work across NAT 
boxes. Watch them collect lots of customers (example: www.vonage.com).

The NAT working group produced a number of documents. Some explained the 
limitations, while one explained to application writers how to live in the 
real world that includes NATs. Read RFC 3235.

A $50 NAPT box (using terminology from the NAT WG's terminology RFC) 
provides sufficient firewalling and purposeful interruption of applications 
for the typical DSL or cable modem user. It runs somewhere OTHER than on 
the user's computer, so when a virus gets in and tries to disable the 
user's firewall software, less damage is done.

If you have users who want/need services that you can't manage to make 
function over NAT, then buy those folks a higher grade of access. The 
reality of the marketplace is broadband connections generally have 
inexpensive NAPT/router boxes. That's been driven by the economics of the 
service model. In great measure the service agreement with broadband 
vendors also stipulates users are not permitted to run servers. If you 
don't like the model, buy service elsewhere.

Sadly, the IETF seems to find ways to generate immense amounts of heat over 
NAT, while sticking its collective head in the sand with regards to 
activity in the marketplace. If the organization wishes to retain ANY 
relevance, it will have to find a way to deal with reality. 




From owner-ietf@ietf.org  Thu Jun 19 04:18:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04514
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 04:18:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SuNT-0002xy-Dq
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 04:02:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SuKf-0002im-DG
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 03:59:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04059
	for <ietf@ietf.org>; Thu, 19 Jun 2003 03:59:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SuIO-0000ao-00
	for ietf@ietf.org; Thu, 19 Jun 2003 03:57:24 -0400
Received: from garlic.amaranth.net ([208.254.46.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SuIN-0000al-00
	for ietf@ietf.org; Thu, 19 Jun 2003 03:57:23 -0400
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226])
	(authenticated (0 bits))
	by garlic.amaranth.net (8.11.7/8.11.7) with ESMTP id h5J7xfs19435
	(using TLSv1/SSLv3 with cipher RC4-SHA (128 bits) verified NO)
	for <ietf@ietf.org>; Thu, 19 Jun 2003 03:59:43 -0400
Message-Id: <5.2.1.1.2.20030619034918.0268f4d0@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 19 Jun 2003 03:57:40 -0400
To: ietf@ietf.org
From: Daniel Senie <dts@senie.com>
Subject: Re: NATs are NOT Firewalls 
In-Reply-To: <200306190534.h5J5YTPZ001409@turing-police.cc.vt.edu>
References: <Your message of "Thu, 19 Jun 2003 00:55:49 EDT." <4B9CE103-A212-11D7-84BB-000393414368@yahoo.com>
 <4B9CE103-A212-11D7-84BB-000393414368@yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 01:34 AM 6/19/2003, Valdis.Kletnieks@vt.edu wrote:

>On Thu, 19 Jun 2003 00:55:49 EDT, S Woodside said:
> > On Wednesday, June 18, 2003, at 06:28  PM, Tomson Eric ((Yahoo.fr))
> > wrote:
> >
> > > Now, the fact that masking the internal addresses to the external
> > > world - so that internal hosts can initiate traffic to the outside,
> > > but no
> > > external host can initiate traffic to the inside - brings some basic
> > > security, is an interesting corollary, but not the primary objective
> > > of a
> > > NAT.
> >
> > Is this just security through obscurity, or something better?
>
>Security through obscurity.  See Bellovin's paper on enumerating through a 
>NAT.

Maybe YOU should read it, and explain how this is useful for attacking the 
hosts behind a NAPT box. The technique described in this paper uses 
variations in the IPid field as evidence of more than one host generating 
packets. Fine. So you plunk a box just upstream of the NAT box, and now you 
can determine how many ACTIVE hosts are talking to sites outside the NAPT box.

Since NAPT uses stateful inspection to operate, it only permits packets in 
to the private network in response to outbound packets. Sitting directly 
upstream of the NAPT box, you could try spoofing reply packets. This would 
work equally well for any stateful-inspection firewall.

So what is really at risk, described in Steve's paper? It is possible to 
determine if NAPT is in use, if the NAPT implementation is insufficiently 
careful in its handling of the IPid field (and likely most do allow 
analysis of this sort). In essence, Steve's paper provides useful 
information for improving NAPT implementations if anyone is worried about 
having upstreams learn of the presence of a NAPT box.

I reject your contention of NAPT as "security through obscurity." 




From owner-ietf@ietf.org  Thu Jun 19 04:18:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04566
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 04:18:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SuNT-0002y4-OX
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 04:02:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SuMB-0002jN-4X
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 04:01:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04094
	for <ietf@ietf.org>; Thu, 19 Jun 2003 04:01:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SuJu-0000b6-00
	for ietf@ietf.org; Thu, 19 Jun 2003 03:58:58 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SuJt-0000b0-00
	for ietf@ietf.org; Thu, 19 Jun 2003 03:58:57 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 4EB94625A5; Thu, 19 Jun 2003 10:00:47 +0200 (CEST)
Date: Thu, 19 Jun 2003 10:00:47 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Ping Pan <pingpan@cs.columbia.edu>
Cc: ietf@ietf.org
Subject: Architectures and frameworks (Re: WG review: Layer 2 Virtual
 Private Networks) (l2vpn)
Message-ID: <604740000.1056009647@askvoll.hjemme.alvestrand.no>
In-Reply-To: <3EF0A9AE.7000202@cs.columbia.edu>
References: <200306181609.JAA15366@gra.isi.edu>
 <3EF0A9AE.7000202@cs.columbia.edu>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On onsdag, juni 18, 2003 11:04:30 -0700 Ping Pan 
<pingpan@cs.columbia.edu> wrote:

> As for IESG, the problem is not about having a new IETF WG. Rather, why
> are we spending so much time and energy on standardization? How many
> times are people going to write architecture and framework RFC's?

until they learn to express their architectures and frameworks concisely?

in many cases, I think the important parts of an architecture or framework 
could be expressed in four pages. But most architecture and framework 
documents go on for fifty pages.

why?




From owner-ietf@ietf.org  Thu Jun 19 06:08:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06970
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 06:08:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sw5o-000615-Ma
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 05:52:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sw1C-0005xv-E1
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 05:47:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06378
	for <ietf@ietf.org>; Thu, 19 Jun 2003 05:47:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Svyv-0001D6-00
	for ietf@ietf.org; Thu, 19 Jun 2003 05:45:25 -0400
Received: from grouse.mail.pas.earthlink.net ([207.217.120.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Svyu-0001D3-00
	for ietf@ietf.org; Thu, 19 Jun 2003 05:45:24 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by grouse.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19Sw19-0002ed-00; Thu, 19 Jun 2003 02:47:43 -0700
Date: Thu, 19 Jun 2003 05:44:49 -0400
From: Keith Moore <moore@cs.utk.edu>
To: S Woodside <sbwoodside@yahoo.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition
Message-Id: <20030619054449.1d4aec68.moore@cs.utk.edu>
In-Reply-To: <E8CA8EC9-A210-11D7-84BB-000393414368@yahoo.com>
References: <20030618153911.49945ac0.moore@cs.utk.edu>
	<E8CA8EC9-A210-11D7-84BB-000393414368@yahoo.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > expecting the network
> > to isolate insecure hosts from untrustworthy attackers, or more
> > generally, to enforce policy about what kinds of content are
> > permitted to pass, has always been a stretch.
> >
> 
> So where do firewalls fit into your picture? Do they represent for the 
> network or for the hosts?

I believe the primary purpose of firewalls should be to protect the network,
not the hosts, from abusive or unauthorized usage. 



From owner-ietf@ietf.org  Thu Jun 19 06:12:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07161
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 06:12:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SwFU-00067U-MG
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 06:02:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SwAY-00061N-Mm
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 05:57:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06594
	for <ietf@ietf.org>; Thu, 19 Jun 2003 05:57:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sw8G-0001FK-00
	for ietf@ietf.org; Thu, 19 Jun 2003 05:55:04 -0400
Received: from flamingo.mail.pas.earthlink.net ([207.217.120.232])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sw8G-0001FH-00
	for ietf@ietf.org; Thu, 19 Jun 2003 05:55:04 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by flamingo.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19SwAT-0000OG-00; Thu, 19 Jun 2003 02:57:22 -0700
Date: Thu, 19 Jun 2003 05:54:27 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "John Loughney" <john.loughney@kolumbus.fi>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: ISPs giving users NATted addresses (was myth of the great
 transition)
Message-Id: <20030619055427.44dce39b.moore@cs.utk.edu>
In-Reply-To: <1056099184948>
References: <1056099184948>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> With due respects, there is a flaw in your thinking. Many ISPs give users
> NATed adresses, without users really knowing or understanding what they are.

I ordered a static IP from my ISP (so I could run 6to4 :).   The DSL modem
that they sent me speaks PPPoE over ATM to the ISP and DHCP to the host.
Even though I had a static IP address, the modem NATed the address and
assigned an RFC 1918 address over DHCP.  And no, this isn't so it can support
multiple hosts - the modem refuses to talk to more than one Ethernet address.

Fortunately it was possible to configure the DSL modem to disable the NAT
and have the host talk PPPoE directly to the ISP.  But this demonstrates to me
that ISPs will give customers NATted service even when there's absolutely no
reason to do so.  And my current ISP is one of the larger ones in the US.



From owner-ietf@ietf.org  Thu Jun 19 06:21:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07357
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 06:21:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SwPB-0006vl-SQ
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 06:12:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SwNS-0006VW-D6
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 06:10:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07129
	for <ietf@ietf.org>; Thu, 19 Jun 2003 06:10:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SwLB-0001MN-00
	for ietf@ietf.org; Thu, 19 Jun 2003 06:08:25 -0400
Received: from scaup.mail.pas.earthlink.net ([207.217.120.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SwLA-0001MK-00
	for ietf@ietf.org; Thu, 19 Jun 2003 06:08:24 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by scaup.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19SwNK-0003D8-00; Thu, 19 Jun 2003 03:10:38 -0700
Date: Thu, 19 Jun 2003 06:07:44 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Daniel Senie <dts@senie.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619060744.391b92e6.moore@cs.utk.edu>
In-Reply-To: <5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT." <kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> The NAT working group produced a number of documents. Some explained the 
> limitations, while one explained to application writers how to live in the 
> real world that includes NATs. Read RFC 3235.

nope, RFC 3235 doesn't explain how to make your applications work in the
presence of NATs.  it essentially says: there are lots of things you can't do
in the presence of NATs, so don't do them.  never mind that they make the 
network dysfunctional, the document is written as if this is somehow a
feature.

> A $50 NAPT box (using terminology from the NAT WG's terminology RFC) 
> provides sufficient firewalling and purposeful interruption of applications 
> for the typical DSL or cable modem user. 

and kills that user's ability to run valuable applications.  in fact, the NAT
is not a firewall at all.  it isn't implementing any policy specified by the
user.  what it's doing is imposing some arbitrary restrictions on the user's
network that may or may not serve the user's interests at all.  it's snake
oil.

> It runs somewhere OTHER than on 
> the user's computer, so when a virus gets in and tries to disable the 
> user's firewall software, less damage is done.

well, the user's computer gets infected anyway.   the NAT is left unharmed,
but I don't consider this a feature.
 
> Sadly, the IETF seems to find ways to generate immense amounts of heat over 
> NAT, while sticking its collective head in the sand with regards to 
> activity in the marketplace.

the NAT vendors are the irresponsible ones.  they create a mess out of the
network and then expect IETF to clean it up, then claim that IETF is in denial
for not doing so.  and of course IETF has tried to do so, more than once,
and failed.  not for lack of effort, but because it's simply not possible to
fix NATs.

maybe you are the one who needs to get his head out of a dark place.

Keith






From owner-ietf@ietf.org  Thu Jun 19 06:55:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08078
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 06:55:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SwnM-0007e3-SW
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 06:37:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Swkx-0007aM-16
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 06:35:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07811
	for <ietf@ietf.org>; Thu, 19 Jun 2003 06:35:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Swif-0001Xg-00
	for ietf@ietf.org; Thu, 19 Jun 2003 06:32:41 -0400
Received: from snipe.mail.pas.earthlink.net ([207.217.120.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Swia-0001Xd-00
	for ietf@ietf.org; Thu, 19 Jun 2003 06:32:41 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by snipe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19Swkl-000088-00; Thu, 19 Jun 2003 03:34:52 -0700
Date: Thu, 19 Jun 2003 06:31:57 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: moore@cs.utk.edu, Valdis.Kletnieks@vt.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619063157.663064f4.moore@cs.utk.edu>
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F8A8@server2000.arneill-py.sacramento.ca.us>
References: <963621801C6D3E4A9CF454A1972AE8F504F8A8@server2000.arneill-py.sacramento.ca.us>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Don't get me wrong, I do not defend NAT. The point I was trying to make
> is this: it is a waste of time to say that NAT sucks. We know it. For
> IPv4, it's too late to change. 

The reason that we are explaining (once again) why NAT sucks is that some
people in this community are still in denial about that, and those people
impair our ability to do useful work.  So we're trying to educate them, or at
least beat them senseless, so they'll get out of the way.

> IMHO, here is the deal: IPv4 NAT does
> suck, but there is nothing we can do to remove it; so the only worthy
> efforts are 1) maybe try to make it less worse (I will not go as far as
> saying better) and 2) let's not make the same mistake with IPv6.

that's it in a nutshell.



From owner-ietf@ietf.org  Thu Jun 19 07:42:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09967
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 07:42:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sxa4-0000K5-Fo
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 07:27:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SxWP-0000Fp-1J
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 07:24:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08884
	for <ietf@ietf.org>; Thu, 19 Jun 2003 07:24:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SxU7-0001nK-00
	for ietf@ietf.org; Thu, 19 Jun 2003 07:21:43 -0400
Received: from ds20-1.cc.swin.edu.au ([136.186.1.150] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SxU6-0001nG-00
	for ietf@ietf.org; Thu, 19 Jun 2003 07:21:42 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2/8.9.3) with ESMTP id VAA2066573;
	Thu, 19 Jun 2003 21:23:29 +1000 (EST)
Message-ID: <3EF19D31.118FDF1E@swin.edu.au>
Date: Thu, 19 Jun 2003 21:23:29 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: SIRs
References: <F7083F6E-A1BC-11D7-84BB-000393414368@yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


S Woodside wrote:
	[..]
> There is no reason otherwise, that the bugtracker would engender a
> reduced quality of discourse about an I-D.

I'd be afraid of encouraging a new "toss the complaint
over the wall into the bugtracker, don't bother engaging the
WG to discuss/refine my proposed solution/edit" style of
interaction with I-D authors. No?

cheers,
gja



From owner-ietf@ietf.org  Thu Jun 19 07:44:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10150
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 07:44:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Sxa4-0000KN-RS
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 07:27:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SxZK-0000Fv-Ag
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 07:27:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08918
	for <ietf@ietf.org>; Thu, 19 Jun 2003 07:27:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SxX2-0001o0-00
	for ietf@ietf.org; Thu, 19 Jun 2003 07:24:44 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SxX2-0001nx-00
	for ietf@ietf.org; Thu, 19 Jun 2003 07:24:44 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h5JBR3tU009795;
	Thu, 19 Jun 2003 07:27:03 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h5JBR3ih009794;
	Thu, 19 Jun 2003 07:27:03 -0400
Date: Thu, 19 Jun 2003 07:27:03 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200306191127.h5JBR3ih009794@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

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

    > The reason that we are explaining (once again) why NAT sucks is that
    > some people in this community are still in denial about that

The person who's most in denial around here is you - about how definitively
the market has, for the moment, chosen IPv4+NAT as the best balance between
cost and effectiveness.

Get a grip. We all know you don't like NAT. You don't need to reply to
*every* *single* *message* *about* *NAT* explaining for the 145,378,295th
time how bad they are.

    > and those people impair our ability to do useful work. So we're trying
    > to educate them, or at least beat them senseless, so they'll get out of
    > the way.

Nicely put - your continual flaming about NAT really gets in the way.

	Noel



From owner-ietf@ietf.org  Thu Jun 19 08:28:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12850
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 08:28:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SxoI-0000Yu-JJ
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 07:42:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sxcz-0000L6-St
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 07:30:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09216
	for <ietf@ietf.org>; Thu, 19 Jun 2003 07:30:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sxai-0001oU-00
	for ietf@ietf.org; Thu, 19 Jun 2003 07:28:32 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sxah-0001oO-00
	for ietf@ietf.org; Thu, 19 Jun 2003 07:28:31 -0400
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h5JBUKwm016087;
	Thu, 19 Jun 2003 04:30:21 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AIO47217;
	Thu, 19 Jun 2003 04:30:19 -0700 (PDT)
Message-Id: <200306191130.AIO47217@mira-sjc5-c.cisco.com>
To: EKR <ekr@rtfm.com>
cc: ietf@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Message from ekr@rtfm.com
   of "18 Jun 2003 21:30:35 PDT." <kjptlak7tg.fsf@romeo.rtfm.com> 
Date: Thu, 19 Jun 2003 07:30:19 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

> Why is it so hard for people here to believe that customers might
> actually know what they want, even if you don't happen to think
> it's a good idea?

Going back a message or two, the firewall problem is more
tractible than the NAT problem but you're right, it's
similar in some of its impediments.

Anyway, I do think that people know what they want, but from
talking with the denizens of, say, comp.security.firewalls
there's a lot of confusion about the technology, what it
accomplishes, and what problems it introduces.

My take on it is that users and network administrators
really - I mean *really* - don't want universal reachability
anymore.  They want to be reachable by the people they want
to be reachable by and nobody else, and that's technology
that we don't know how to provide.  In the absence of better
technology they're relying on firewalls and NATs.  I think
there's a gross mismatch between the economic model
underlying IP and the ones underlying how networking is
practiced today, and that the resulting problems are
inevitable.  I'm pretty sure that standing around cursing
the darkness isn't a useful response.

Melinda



From owner-ietf@ietf.org  Thu Jun 19 09:11:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16415
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 09:11:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SyxI-0002u2-7H
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 08:55:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SxtS-0001Lb-8F
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 07:47:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10370
	for <ietf@ietf.org>; Thu, 19 Jun 2003 07:47:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SxrA-0001zG-00
	for ietf@ietf.org; Thu, 19 Jun 2003 07:45:32 -0400
Received: from ds20-1.cc.swin.edu.au ([136.186.1.150] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Sxr9-0001z3-00
	for ietf@ietf.org; Thu, 19 Jun 2003 07:45:32 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2/8.9.3) with ESMTP id VAA2067998;
	Thu, 19 Jun 2003 21:47:20 +1000 (EST)
Message-ID: <3EF1A2C8.5D17F254@swin.edu.au>
Date: Thu, 19 Jun 2003 21:47:20 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Layering purity Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
References: <Pine.LNX.4.44.0306191024360.14861-100000@netcore.fi>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Pekka Savola wrote:
	[..]
> Moreover, we work on an IP layer.  We enable IP layer to be able to handle
> our tasks.  If there is some problem why we cannot just use different IP
> subnets between the two (or multiple) end-points, we need to fix that
> problem, not burrow even further down the ISO layers.

Oh. A layering purist. I knew something didn't seem quite right.

And "just use different IP subnets" would solve mobile IP?

cheers,
gja  (who should probably be disbarred for having once run IP over ATM
over UDP/IP between New Jersey and Georgia because, well, there
just wasn't a 'real' ATM link at the time and moving ATM cells
was my task...)



From owner-ietf@ietf.org  Thu Jun 19 09:14:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16666
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 09:14:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19SyxI-0002u9-Jf
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 08:55:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sxun-0001Ld-JN
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 07:49:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10395
	for <ietf@ietf.org>; Thu, 19 Jun 2003 07:49:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SxsW-0001za-00
	for ietf@ietf.org; Thu, 19 Jun 2003 07:46:56 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SxsV-0001zX-00
	for ietf@ietf.org; Thu, 19 Jun 2003 07:46:55 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h5JBnEtU009893;
	Thu, 19 Jun 2003 07:49:15 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h5JBnEEk009892;
	Thu, 19 Jun 2003 07:49:14 -0400
Date: Thu, 19 Jun 2003 07:49:14 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200306191149.h5JBnEEk009892@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Bob Braden <braden@ISI.EDU>

    > Today, one must unfortunately question whether universal connectivity
    > can be sustained (or is even the right goal) in a networking
    > environment without universal trust. Maybe NATs are, in fact, a result
    > of a very deep problem with our architecture.

My take is that NAT's respond to several flaws in the IPv4 architecture:

- 1) Not enough addresses - this being the one that brought them into
	existence.
- 1a) Local allocation of addresses - a variant of the preceeding one, but
	subtly different; NAT's do allow you to allocate more addresses
	locally without going back to a central number allocation authority,
	which is very convenient.
- 2) Easy renumbering when switching ISP's - a benefit that only was realized
	later in time, but a significant one all the same - especially for
	those people who reckon that switching addresses is a really painful
	undertaking.

I don't really believe the rationale that they are useful as a firewall. For
one thing, most NAT boxes includes a real firewall (i.e. packet filtering
separate from the NAT functionality). I think that even if we had plenty of
addresses, people would still install boxes with firewall functionality at
the edges of their networks.

Which gets to your original point - "whether universal connectivity .. is
even the right goal .. in a networking environment without universal trust".
Which is an interesting and complex point, but I think one we can put off to
a separate discussion, because I think it's unrelated to the reasons that NAT
boxes have been a success. (It's also good to put if off because including it
will muddy the discussion water.)


    > If you accept that, then there is no point in attacking NATs until you
    > can propose a better architectural solution to the trust problem
    > (hopefully, there will be one!)

Well, not so much the trust problem, because I don't think that's what drove
NAT. But your basic point is a good one.

I think that if you look at the points I listed above, the market has clearly
decided that IPv4+NAT (for all its problems, with which people are I'm sure
reasonably familiar, given the many years NAT has been in service widely) is
the most cost-effective solution to providing them. The IETF really needs to
sit and ponder the implications of that.

	Noel



From owner-ietf@ietf.org  Thu Jun 19 09:57:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18342
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 09:57:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Szmu-0005yE-90
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 09:49:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SzhC-0005pu-Ep
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 09:43:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17586
	for <ietf@ietf.org>; Thu, 19 Jun 2003 09:43:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Szeu-0004Gn-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:41:00 -0400
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Szeg-0004Gd-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:41:00 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19Szgq-0005yc-00; Thu, 19 Jun 2003 06:43:00 -0700
Date: Thu, 19 Jun 2003 09:40:05 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619094005.2a4730a7.moore@cs.utk.edu>
In-Reply-To: <200306191149.h5JBnEEk009892@ginger.lcs.mit.edu>
References: <200306191149.h5JBnEEk009892@ginger.lcs.mit.edu>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> My take is that NAT's respond to several flaws in the IPv4 architecture:
> 
> - 1) Not enough addresses - this being the one that brought them into
> 	existence.
> - 1a) Local allocation of addresses - a variant of the preceeding one, but
> 	subtly different; NAT's do allow you to allocate more addresses
> 	locally without going back to a central number allocation authority,
> 	which is very convenient.
> - 2) Easy renumbering when switching ISP's - a benefit that only was
>       realized later in time, but a significant one all the same -
>       especially for those people who reckon that switching addresses is a
>       really painful undertaking.

You might be surprised to find that I agree with the above.  But I also think
it's useful to consider technical reasons for wanting NATs in IPv4 separately
from the things that motivate people to install NATs - and many of the latter
have no technical basis.  e.g. people have been sold on NAT functionality by
being told that it's a firewall and that the NAT protects them from attacks.

> I think that if you look at the points I listed above, the market has
> clearly decided that IPv4+NAT (for all its problems, with which people are
> I'm sure reasonably familiar, given the many years NAT has been in service
> widely) is the most cost-effective solution to providing them. 

Again, there are sound technical justifications and there are uninformed 
motiviations, and both affect people's purchasing decisions.  Whether NAT+IPv4
is cost-effective has a lot to do with what you want to do with your network;
the answer will be different for different user communities.  I think it's
more realistic to say that IPv4+NAT was the easiest thing to try first to
alleviate the flaws you list above, since it claimed (unrealistically) to
solve those problems without upgrading hosts, applications, or the packet
format.



From owner-ietf@ietf.org  Thu Jun 19 09:59:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18528
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 09:59:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Szmu-0005zk-Vv
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 09:49:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SzjZ-0005r5-4n
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 09:45:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17746
	for <ietf@ietf.org>; Thu, 19 Jun 2003 09:45:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzhH-0004Ir-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:43:27 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzhG-0004IO-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:43:26 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 233E4ABB5; Thu, 19 Jun 2003 06:51:17 -0700 (PDT)
To: James Seng <jseng@pobox.org.sg>
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
	<kju1ankzkr.fsf@romeo.rtfm.com> <3EF14A74.7090504@pobox.org.sg>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 06:51:16 -0700
In-Reply-To: <3EF14A74.7090504@pobox.org.sg>
Message-ID: <kjhe6mnpkb.fsf@romeo.rtfm.com>
Lines: 17
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

James Seng <jseng@pobox.org.sg> writes:

> Why should the users be limited to what IT managers decide is good or bad?
> 
> Internet is build on dumb network, smart terminal. End-users are
> suppose to be able to put up their own services, not just running some
> apps. This has been the Internet principles and have serves us well so
> far.
No large production network can run this way. The end machines are 
simply too vulnerable. Without firewally and service restriction,
you'll have your entire network compromised very quickly.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 10:17:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20451
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 10:17:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Szzz-0008WC-7d
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 10:02:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19SznZ-000606-Vp
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 09:49:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17930
	for <ietf@ietf.org>; Thu, 19 Jun 2003 09:49:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzlH-0004M4-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:47:35 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzlG-0004M1-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:47:34 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 5D16DABB5; Thu, 19 Jun 2003 06:55:32 -0700 (PDT)
To: "John Loughney" <john.loughney@kolumbus.fi>
Cc: <mshore@cisco.com>, <ietf@ietf.org>
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <1056099184948>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 06:55:32 -0700
In-Reply-To: <1056099184948>
Message-ID: <kjd6hanpd7.fsf@romeo.rtfm.com>
Lines: 32
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

"John Loughney" <john.loughney@kolumbus.fi> writes:
> With due respects, there is a flaw in your thinking. Many ISPs give
> users NATed adresses, without users really knowing or understanding
> what they are.  When the users try applications or serves which fail
> because of the non-transparency, the users may not know the cause of
> the failures.
>
> I had some VPN software that fails due to NATs in hotels, for
> example. Support people told me that the hotel used NATs for
> security - I sent a log showing all of the probes my macine had from
> inside the network.
>
> My main point is that users & providers are often confused about NATs.
Yes, I hear this a lot, but I don't buy it--or, rather, I don't
think it's relevant.

I'm absolutely sure that users don't understand about NATs, however,
they don't need to. All they need to understand is that things
ought to work and that they don't. If there is really a substantial
class of applications that users want to run that NATs disable,
I would expect someone to start advertising Internet service without
NAT as "now you can use application X". 

Look, consumers don't understand how Viagra works, but it didn't
take them long to figure out that it solved a problem they wanted
solved.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 10:17:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20452
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 10:17:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Szzz-000055-K0
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 10:02:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Sznn-00060J-9O
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 09:50:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17941
	for <ietf@ietf.org>; Thu, 19 Jun 2003 09:50:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzlV-0004MH-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:47:49 -0400
Received: from grouse.mail.pas.earthlink.net ([207.217.120.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzlV-0004ME-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:47:49 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by grouse.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19Sznj-0003FU-00; Thu, 19 Jun 2003 06:50:07 -0700
Date: Thu, 19 Jun 2003 09:47:12 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619094712.4bcdbe48.moore@cs.utk.edu>
In-Reply-To: <200306191127.h5JBR3ih009794@ginger.lcs.mit.edu>
References: <200306191127.h5JBR3ih009794@ginger.lcs.mit.edu>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


>     > The reason that we are explaining (once again) why NAT sucks is that
>     > some people in this community are still in denial about that
> 
> The person who's most in denial around here is you - about how definitively
> the market has, for the moment, chosen IPv4+NAT as the best balance between
> cost and effectiveness.

"for the moment".  NATs are not carved in stone.  and it's not our job in IETF
to defend or reinforce the market's bad decisions in the past, but to ensure
that the network works well in the future.

Keith



From owner-ietf@ietf.org  Thu Jun 19 10:26:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21226
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 10:26:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T055-0002Je-LE
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 10:08:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Szr6-00067D-4c
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 09:53:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18094
	for <ietf@ietf.org>; Thu, 19 Jun 2003 09:53:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Szoo-0004Oo-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:51:14 -0400
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Szoo-0004Ok-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:51:14 -0400
Received: from [192.35.232.241] (helo=think.thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:DES-CBC3-SHA:168)  (Exim 3.35 #1 (Debian))
	id 19Szqz-0000si-00; Thu, 19 Jun 2003 09:53:29 -0400
Received: from tytso authenticated as tytso by think.thunk.org with local   (Exim 3.35 #1 (Debian))
	id 19Szqj-0000ik-00; Thu, 19 Jun 2003 09:53:13 -0400
Date: Thu, 19 Jun 2003 09:53:13 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Message-ID: <20030619135313.GA2757@think>
References: <200306191149.h5JBnEEk009892@ginger.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200306191149.h5JBnEEk009892@ginger.lcs.mit.edu>
User-Agent: Mutt/1.5.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, Jun 19, 2003 at 07:49:14AM -0400, J. Noel Chiappa wrote:
> 
> My take is that NAT's respond to several flaws in the IPv4 architecture:
> 
> - 1) Not enough addresses - this being the one that brought them into
> 	existence.
> - 1a) Local allocation of addresses - a variant of the preceeding one, but
> 	subtly different; NAT's do allow you to allocate more addresses
> 	locally without going back to a central number allocation authority,
> 	which is very convenient.
> - 2) Easy renumbering when switching ISP's - a benefit that only was realized
> 	later in time, but a significant one all the same - especially for
> 	those people who reckon that switching addresses is a really painful
> 	undertaking.

I have to agree with Noel here.  As much as I hate NAT's because they
screw up various protocols --- not the least of which are Kerberos,
Zephyr, AFS, etc. --- I am running a NAT at home precisely because it
solves the above issues.

Unfortunately, it hasn't been clear to me IPv6 necessarily solves
these problems.  If it's true that some address registries have been
handing out IPv6 addrs. with the same parsimony that they've been
handing IPv4 address, and that routing concerns means that we won't
have provider independent addressing, and various application writers
are using promoting the use of explicit IPv6 addresses in
configuration files, license managers, etc., then we may end up with
NAT's even in IPv6 land.  And that would be most unfortunate.

					- Ted



From owner-ietf@ietf.org  Thu Jun 19 10:27:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21295
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 10:27:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T055-0002Jk-U9
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 10:08:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Szrp-00068b-AG
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 09:54:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18104
	for <ietf@ietf.org>; Thu, 19 Jun 2003 09:54:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzpX-0004P9-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:51:59 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzpW-0004Or-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:51:59 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 6C4D0ABB5; Thu, 19 Jun 2003 06:59:56 -0700 (PDT)
To: Valdis.Kletnieks@vt.edu
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306190531.h5J5V5PZ001358@turing-police.cc.vt.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 06:59:56 -0700
In-Reply-To: <200306190531.h5J5V5PZ001358@turing-police.cc.vt.edu>
Message-ID: <kj8yrynp5v.fsf@romeo.rtfm.com>
Lines: 35
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Valdis.Kletnieks@vt.edu writes:

> On Wed, 18 Jun 2003 22:19:12 PDT, Eric Rescorla said:
> 
> > You've got it absolutely backwards. The fact that the NAT breaks applications
> > that I don't want to run anyway is a FEATURE, not a bug.
> 
> And the fact that NAT breaks things that you DO want to run is a <?>
I'm not convinced that this is happening... if it is,
why isn't there a market reaction.

> > > And unfortunately, a lot of the Just Does Not Work stuff are applications
> > > like H.323 and VOIP that Joe Sixpack actually *might* be interested in.
> > 
> > Ah, the eternal lament of the technocrat who can't understand why the
> > customers don't want what he knows is so obviously good for them. 
> 
> No, the lament of a technocrat who can't deploy things that customers DO want
> because NAT breaks them.
>
> Find a user.  See if they'd be interested in video or voice over IP.  Watch
> them say "ooh... that sounds cool".  Then tell them it would be unreliable
> and you could only use it to talk to other users some of the time, because
> a lot of users are on these things called NATs, and watch enthusiasm wane.

Given that there are workarounds for these, I find this explanation
pretty unlikely. More likely is that people's revealed preference
is that they don't actually want this stuff.
                                   
-Ekr


-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 10:38:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21978
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 10:38:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T056-0002KC-8f
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 10:08:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Szun-0006Df-1Q
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 09:57:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18328
	for <ietf@ietf.org>; Thu, 19 Jun 2003 09:57:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzsV-0004Pw-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:55:03 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SzsU-0004Ph-00
	for ietf@ietf.org; Thu, 19 Jun 2003 09:55:02 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 930C1ABB5; Thu, 19 Jun 2003 07:03:00 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: Daniel Senie <dts@senie.com>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
	<20030619060744.391b92e6.moore@cs.utk.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 07:03:00 -0700
In-Reply-To: <20030619060744.391b92e6.moore@cs.utk.edu>
Message-ID: <kj4r2mnp0r.fsf@romeo.rtfm.com>
Lines: 22
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Keith Moore <moore@cs.utk.edu> writes:
> > Sadly, the IETF seems to find ways to generate immense amounts of heat over 
> > NAT, while sticking its collective head in the sand with regards to 
> > activity in the marketplace.
> 
> the NAT vendors are the irresponsible ones.  they create a mess out of the
> network and then expect IETF to clean it up, then claim that IETF is in denial
> for not doing so.  and of course IETF has tried to do so, more than once,
> and failed.  not for lack of effort, but because it's simply not possible to
> fix NATs.
This is more hyperbole. How have NATs created a mess out of the network?
Yes, I understand that they've made the network environment more 
complicated which makes life hard on protocols designers. So what?
If the customers are getting what they want, that seems to me that it
can hardly be characterized as a "mess". And you have yet to establish
that they're not getting what they want.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 10:59:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23041
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 10:59:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T0Uf-0007qK-Vy
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 10:34:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T0Ai-0004iA-7b
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 10:13:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20071
	for <ietf@ietf.org>; Thu, 19 Jun 2003 10:13:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T08Q-0004cq-00
	for ietf@ietf.org; Thu, 19 Jun 2003 10:11:30 -0400
Received: from grebe.mail.pas.earthlink.net ([207.217.120.46])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T08P-0004cn-00
	for ietf@ietf.org; Thu, 19 Jun 2003 10:11:29 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by grebe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19T0Ab-0002Qb-00; Thu, 19 Jun 2003 07:13:45 -0700
Date: Thu, 19 Jun 2003 10:10:50 -0400
From: Keith Moore <moore@cs.utk.edu>
To: EKR <ekr@rtfm.com>
Cc: moore@cs.utk.edu, dts@senie.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619101050.2eb0bd0f.moore@cs.utk.edu>
In-Reply-To: <kj4r2mnp0r.fsf@romeo.rtfm.com>
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
	<20030619060744.391b92e6.moore@cs.utk.edu>
	<kj4r2mnp0r.fsf@romeo.rtfm.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> If the customers are getting what they want, that seems to me that it
> can hardly be characterized as a "mess". And you have yet to establish
> that they're not getting what they want.

certainly the users I deal with are not getting what they want.
others seem to be reporting similar experiences.



From owner-ietf@ietf.org  Thu Jun 19 11:00:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23210
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 11:00:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T0nu-00018p-Gw
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 10:54:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T0Vu-0007vw-4j
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 10:35:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21816;
	Thu, 19 Jun 2003 10:35:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T0Tc-0004wQ-00; Thu, 19 Jun 2003 10:33:24 -0400
Received: from scaup.mail.pas.earthlink.net ([207.217.120.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T0Tb-0004wN-00; Thu, 19 Jun 2003 10:33:23 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by scaup.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19T0Vr-0007W4-00; Thu, 19 Jun 2003 07:35:43 -0700
Date: Thu, 19 Jun 2003 10:32:48 -0400
From: Keith Moore <moore@cs.utk.edu>
To: The IESG <iesg-secretary@ietf.org>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
Message-Id: <20030619103248.6419c22b.moore@cs.utk.edu>
In-Reply-To: <200306172026.QAA09324@ietf.org>
References: <200306172026.QAA09324@ietf.org>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>  1. Virtual Private LAN Service (VPLS)--L2 service that emulates LAN
>        across an IP and an MPLS-enabled IP network, allowing standard
>        Ethernet devices communicate with each other as if they were
>        connected to a common LAN segment.

I do not believe this is a technically reasonable goal.  if even switched
Ethernets do not work right for multicast (which, remember, is essential for
IPv6) how do you expect tunneled and routed Ethernet to work right? and don't
tell me you want the routers to snoop for multicast join/leave messages --
that's just too broken.

Now, if you want to define a pseudo-L2 service that uses Ethernet hardware and
framing as a substrate, but has explicit L2 multicast control, that might be
worth considering.  But don't make it just for tunneling L2 over IP networks,
design it so it can be a truly general-purpose means of gaining access to 
the Internet over an Ethernet - replacing PPPoE and other kludges.

Really, we need a plug-and-play way by which hosts can figure out how to
connect to the Internet and authenticate themselves, one that gives each host
the address and connectivity it's supposed to have independently (within
reason) of where it's plugged in to the network, and one that would be general
enough for every network to use instead of this hodgepodge of DHCP/PPP/etc.



From owner-ietf@ietf.org  Thu Jun 19 11:06:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23802
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 11:06:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T0nu-000196-Vw
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 10:54:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T0WY-0007w0-Bh
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 10:36:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21853
	for <ietf@ietf.org>; Thu, 19 Jun 2003 10:36:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T0UG-0004x0-00
	for ietf@ietf.org; Thu, 19 Jun 2003 10:34:04 -0400
Received: from [131.107.8.3] (helo=exchange.microsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T0UF-0004wq-00
	for ietf@ietf.org; Thu, 19 Jun 2003 10:34:03 -0400
Received: from DF-VRS-01.redmond.corp.microsoft.com ([157.54.4.14]) by exchange.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 19 Jun 2003 07:35:53 -0700
Received: from 10.197.0.83 by DF-VRS-01.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 19 Jun 2003 07:35:52 -0700
Received: from DF-DINKY.platinum.corp.microsoft.com ([10.197.0.118]) by DF-BEG.platinum.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 19 Jun 2003 07:35:52 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Subject: RE: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Date: Thu, 19 Jun 2003 07:35:52 -0700
Message-ID: <01C133474E27D04FABA48D02078CF41D014D1ABA@DF-DINKY.platinum.corp.microsoft.com>
Thread-Topic: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Thread-Index: AcM2ZMjQC1AYYag3RxOHysBt4WSQwwACfMyo
From: "Peter Ford" <peterf@exchange.microsoft.com>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, <ietf@ietf.org>
Cc: <jnc@ginger.lcs.mit.edu>
X-OriginalArrivalTime: 19 Jun 2003 14:35:52.0653 (UTC) FILETIME=[15CD77D0:01C33670]
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C33670.15920FE9"

------_=_NextPart_001_01C33670.15920FE9
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Noel,
=20
You are getting too cerebral.  We can look at the marketing info on the =
box of a NAT product to see what people think they are getting:
=20
1) Instant Internet Sharing for cable and DSL ....
2) Firewall Security against ...  USING NAT technology.
3) Simultaneous Internet Access for up to NNN PCs
4) 4 port 10/100 switch
5) Built in print server ...
=20
=20
It really doesn't matter what you think wrt the firewall security of =
NATs.   People think they are getting additional security.   Here is a =
common sequence we see: 1) person puts on a software firewall solution =
on their PC, 2) their solution then continually inundates the user with =
warnings due to all the scanning going on, 3) they get a NAT based on =
security recommendations from PC magazines, CNET, ZD, etc., it is a =
trivial install of a now < $50 devicce,  4) the warnings are =
significantly reduced, 5) customer feels they have done something about =
their vulnerability, probably akin to installing a deadbolt lock into a =
wooden door frame (sure, a crowbar will go right through it like =
butter).
=20
regards, peterf
=20
P.S. NATng - it's time has come!
=20

________________________________

From: owner-ietf@ietf.org on behalf of J. Noel Chiappa
Sent: Thu 6/19/2003 4:49 AM
To: ietf@ietf.org
Cc: jnc@ginger.lcs.mit.edu
Subject: Re: myth of the great transition (was US Defense Department =
forma lly adopts IPv6)



    > From: Bob Braden <braden@ISI.EDU>

    > Today, one must unfortunately question whether universal =
connectivity
    > can be sustained (or is even the right goal) in a networking
    > environment without universal trust. Maybe NATs are, in fact, a =
result
    > of a very deep problem with our architecture.

My take is that NAT's respond to several flaws in the IPv4 architecture:

- 1) Not enough addresses - this being the one that brought them into
        existence.
- 1a) Local allocation of addresses - a variant of the preceeding one, =
but
        subtly different; NAT's do allow you to allocate more addresses
        locally without going back to a central number allocation =
authority,
        which is very convenient.
- 2) Easy renumbering when switching ISP's - a benefit that only was =
realized
        later in time, but a significant one all the same - especially =
for
        those people who reckon that switching addresses is a really =
painful
        undertaking.

I don't really believe the rationale that they are useful as a firewall. =
For
one thing, most NAT boxes includes a real firewall (i.e. packet =
filtering
separate from the NAT functionality). I think that even if we had plenty =
of
addresses, people would still install boxes with firewall functionality =
at
the edges of their networks.

Which gets to your original point - "whether universal connectivity .. =
is
even the right goal .. in a networking environment without universal =
trust".
Which is an interesting and complex point, but I think one we can put =
off to
a separate discussion, because I think it's unrelated to the reasons =
that NAT
boxes have been a success. (It's also good to put if off because =
including it
will muddy the discussion water.)


    > If you accept that, then there is no point in attacking NATs until =
you
    > can propose a better architectural solution to the trust problem
    > (hopefully, there will be one!)

Well, not so much the trust problem, because I don't think that's what =
drove
NAT. But your basic point is a good one.

I think that if you look at the points I listed above, the market has =
clearly
decided that IPv4+NAT (for all its problems, with which people are I'm =
sure
reasonably familiar, given the many years NAT has been in service =
widely) is
the most cost-effective solution to providing them. The IETF really =
needs to
sit and ponder the implications of that.

        Noel




------_=_NextPart_001_01C33670.15920FE9
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">=0A=
<HTML>=0A=
<HEAD>=0A=
=0A=
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.6944.0">=0A=
<TITLE>Re: myth of the great transition (was US Defense Department forma =
lly adopts IPv6)</TITLE>=0A=
</HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText34079 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2>Noel,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>You are getting too =
cerebral.&nbsp; We can =0A=
look at the marketing info on the box of a NAT product to see what =
people think =0A=
they are getting:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>1) Instant Internet Sharing =
for cable and =0A=
DSL ....</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>2) Firewall Security against =
...&nbsp; =0A=
USING NAT technology.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>3) Simultaneous Internet =
Access for up to =0A=
NNN PCs</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>4) 4 port 10/100 =
switch</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>5) Built in print server =
...</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>It really doesn't matter what =
you think wrt =0A=
the firewall security of NATs.&nbsp;&nbsp; People think they are getting =0A=
additional security.&nbsp;&nbsp; Here is a common sequence we see: 1) =
person =0A=
puts on a software firewall solution on their PC, 2) their solution then =0A=
continually inundates the user with warnings due to all the scanning =
going on, =0A=
3) they get a NAT based on security recommendations from PC magazines, =
CNET, ZD, =0A=
etc., it is a trivial install of a now &lt; $50 devicce, &nbsp;4) the =
warnings =0A=
are significantly reduced, 5) customer feels they have done something =
about =0A=
their vulnerability, probably akin to installing a deadbolt lock into a =
wooden =0A=
door frame (sure, a crowbar will go right through it like =
butter).</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>regards, peterf</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>P.S. NATng - it's time has =0A=
come!</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> owner-ietf@ietf.org on behalf =
of J. Noel =0A=
Chiappa<BR><B>Sent:</B> Thu 6/19/2003 4:49 AM<BR><B>To:</B> =0A=
ietf@ietf.org<BR><B>Cc:</B> jnc@ginger.lcs.mit.edu<BR><B>Subject:</B> =
Re: myth =0A=
of the great transition (was US Defense Department forma lly adopts =0A=
IPv6)<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>&nbsp;&nbsp;&nbsp; &gt; From: Bob Braden =0A=
&lt;braden@ISI.EDU&gt;<BR><BR>&nbsp;&nbsp;&nbsp; &gt; Today, one must =0A=
unfortunately question whether universal =
connectivity<BR>&nbsp;&nbsp;&nbsp; &gt; =0A=
can be sustained (or is even the right goal) in a =0A=
networking<BR>&nbsp;&nbsp;&nbsp; &gt; environment without universal =
trust. Maybe =0A=
NATs are, in fact, a result<BR>&nbsp;&nbsp;&nbsp; &gt; of a very deep =
problem =0A=
with our architecture.<BR><BR>My take is that NAT's respond to several =
flaws in =0A=
the IPv4 architecture:<BR><BR>- 1) Not enough addresses - this being the =
one =0A=
that brought them into<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
existence.<BR>- 1a) Local allocation of addresses - a variant of the =
preceeding =0A=
one, but<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; subtly different; =
NAT's =0A=
do allow you to allocate more =0A=
addresses<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; locally without =
going =0A=
back to a central number allocation =0A=
authority,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; which is very =0A=
convenient.<BR>- 2) Easy renumbering when switching ISP's - a benefit =
that only =0A=
was realized<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; later in =
time, but a =0A=
significant one all the same - especially =0A=
for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; those people who =
reckon that =0A=
switching addresses is a really =0A=
painful<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
undertaking.<BR><BR>I =0A=
don't really believe the rationale that they are useful as a firewall. =0A=
For<BR>one thing, most NAT boxes includes a real firewall (i.e. packet =0A=
filtering<BR>separate from the NAT functionality). I think that even if =
we had =0A=
plenty of<BR>addresses, people would still install boxes with firewall =0A=
functionality at<BR>the edges of their networks.<BR><BR>Which gets to =
your =0A=
original point - "whether universal connectivity .. is<BR>even the right =
goal .. =0A=
in a networking environment without universal trust".<BR>Which is an =
interesting =0A=
and complex point, but I think one we can put off to<BR>a separate =
discussion, =0A=
because I think it's unrelated to the reasons that NAT<BR>boxes have =
been a =0A=
success. (It's also good to put if off because including it<BR>will =
muddy the =0A=
discussion water.)<BR><BR><BR>&nbsp;&nbsp;&nbsp; &gt; If you accept =
that, then =0A=
there is no point in attacking NATs until you<BR>&nbsp;&nbsp;&nbsp; &gt; =
can =0A=
propose a better architectural solution to the trust =0A=
problem<BR>&nbsp;&nbsp;&nbsp; &gt; (hopefully, there will be =
one!)<BR><BR>Well, =0A=
not so much the trust problem, because I don't think that's what =
drove<BR>NAT. =0A=
But your basic point is a good one.<BR><BR>I think that if you look at =
the =0A=
points I listed above, the market has clearly<BR>decided that IPv4+NAT =
(for all =0A=
its problems, with which people are I'm sure<BR>reasonably familiar, =
given the =0A=
many years NAT has been in service widely) is<BR>the most cost-effective =0A=
solution to providing them. The IETF really needs to<BR>sit and ponder =
the =0A=
implications of that.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
Noel<BR><BR></FONT></P></DIV>=0A=
=0A=
</BODY>=0A=
</HTML>
------_=_NextPart_001_01C33670.15920FE9--

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




From owner-ietf@ietf.org  Thu Jun 19 11:21:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24607
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 11:21:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T0qz-0001J4-F1
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 10:57:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T0dC-0000hc-KI
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 10:43:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22438
	for <ietf@ietf.org>; Thu, 19 Jun 2003 10:43:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T0au-000543-00
	for ietf@ietf.org; Thu, 19 Jun 2003 10:40:57 -0400
Received: from grouse.mail.pas.earthlink.net ([207.217.120.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T0au-000540-00
	for ietf@ietf.org; Thu, 19 Jun 2003 10:40:56 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by grouse.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19T0d3-0003ac-00; Thu, 19 Jun 2003 07:43:09 -0700
Date: Thu, 19 Jun 2003 10:40:13 -0400
From: Keith Moore <moore@cs.utk.edu>
To: EKR <ekr@rtfm.com>
Cc: moore@cs.utk.edu, dts@senie.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619104013.57201da1.moore@cs.utk.edu>
In-Reply-To: <kjznkem8qr.fsf@romeo.rtfm.com>
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
	<20030619060744.391b92e6.moore@cs.utk.edu>
	<kj4r2mnp0r.fsf@romeo.rtfm.com>
	<20030619101050.2eb0bd0f.moore@cs.utk.edu>
	<kjznkem8qr.fsf@romeo.rtfm.com>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > certainly the users I deal with are not getting what they want.
> > others seem to be reporting similar experiences.
> 
> Then why don't they switch providers.

variety of reasons: often the provider is not the problem, it's the local
network admins, and the users aren't free to go elsewhere.  some of the time
when the provider is the problem, there are no alternatives.  until recently
the only way I could get even one static IP address for my home was through a
special deal with a friend of mine who had a small ISP, and the best bandwidth
I could get was 128kbps.  none of the other local providers would sell me one.

> Revealed preference suggests that they *are* getting what they want, no
> matter how much complaining.

so if you can't come up with a rational explanation for something, just
pretend that the market is wise and cite it as an unimpeachable authority.

Keith



From owner-ietf@ietf.org  Thu Jun 19 11:21:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24642
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 11:21:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T0qz-0001Jn-VH
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 10:57:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T0iS-0000rf-N0
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 10:48:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22596
	for <ietf@ietf.org>; Thu, 19 Jun 2003 10:48:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T0gB-00055G-00
	for ietf@ietf.org; Thu, 19 Jun 2003 10:46:23 -0400
Received: from sj-core-3.cisco.com ([171.68.223.137])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T0g9-000558-00
	for ietf@ietf.org; Thu, 19 Jun 2003 10:46:22 -0400
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h5JEmAlQ018647;
	Thu, 19 Jun 2003 07:48:10 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AIO59278;
	Thu, 19 Jun 2003 07:48:08 -0700 (PDT)
Message-Id: <200306191448.AIO59278@mira-sjc5-c.cisco.com>
To: EKR <ekr@rtfm.com>
cc: ietf@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Message from ekr@rtfm.com
   of "19 Jun 2003 07:03:00 PDT." <kj4r2mnp0r.fsf@romeo.rtfm.com> 
Date: Thu, 19 Jun 2003 10:48:08 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

> This is more hyperbole. How have NATs created a mess out of the network?
> Yes, I understand that they've made the network environment more 
> complicated which makes life hard on protocols designers. So what?
> If the customers are getting what they want, that seems to me that it
> can hardly be characterized as a "mess". And you have yet to establish
> that they're not getting what they want.

NAT (and, to a less extent, firewalls) are definitely
interfering with the deployment of some new services,
including VoIP and multimedia conferencing, of course, but
large-scale distributed scientific computing is a problem as
well.

I'm highly uncomfortable with your argument.  I don't think
that the IETF should be architecturally fundamentalist (that
is to say, it's not that I think that we need to roll over
and play dead for every popular bad idea that's out there,
but that I think we should learn to be smart about where and
when to compromise) but I really take exception to the
notion that as long as users are happy there's really no
problem.  As I said before, the workarounds that are being
used to help facilitate application traversal of NATs are
definitely introducing new security problems that wouldn't
exist if the NAT weren't there.  There are other problems
around robustness and routing.  I think this is a bad thing,
myself.

Melinda



From owner-ietf@ietf.org  Thu Jun 19 11:29:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25240
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 11:29:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T141-0002z0-7W
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 11:11:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T0qF-00019v-5C
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 10:56:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22822
	for <ietf@ietf.org>; Thu, 19 Jun 2003 10:56:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T0nx-00057f-00
	for ietf@ietf.org; Thu, 19 Jun 2003 10:54:25 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T0nw-00057c-00
	for ietf@ietf.org; Thu, 19 Jun 2003 10:54:24 -0400
Received: from blv-av-02.boeing.com ([192.42.227.217])
	by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id HAA26391;
	Thu, 19 Jun 2003 07:56:26 -0700 (PDT)
Received: from slb-hub-01.boeing.com (localhost [127.0.0.1])
	by blv-av-02.boeing.com (8.9.3p2/8.9.2/MBS-AV-02) with ESMTP id HAA14029;
	Thu, 19 Jun 2003 07:56:25 -0700 (PDT)
Received: from XCH-NWBH-01.nw.nos.boeing.com (xch-nwbh-01.nw.nos.boeing.com [192.33.62.231])
	by slb-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id h5JEuKB27244;
	Thu, 19 Jun 2003 07:56:20 -0700 (PDT)
Received: from XCH-NW-09.nw.nos.boeing.com ([192.42.226.84]) by XCH-NWBH-01.nw.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.6662);
	 Thu, 19 Jun 2003 07:56:12 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Date: Thu, 19 Jun 2003 07:56:12 -0700
Message-ID: <5B58696DB20B9140AD20E0685C573A6402992D7E@xch-nw-09.nw.nos.boeing.com>
Thread-Topic: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Thread-Index: AcM2LajCO9idaeC1Rx6Hn7FnbhoOAwARLzlw
From: "Fleischman, Eric" <eric.w.fleischman@boeing.com>
To: "James Seng" <jseng@pobox.org.sg>
Cc: "EKR" <ekr@rtfm.com>, "Keith Moore" <moore@cs.utk.edu>,
        <pbaker@verisign.com>, <Ronald.vanderPol@rvdp.org>, <aarsenau@bbn.com>,
        <ietf@ietf.org>
X-OriginalArrivalTime: 19 Jun 2003 14:56:12.0782 (UTC) FILETIME=[ED0E60E0:01C33672]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA25240

My posting wasn't concerning what I think, it was concerning what is commonly done today in industry. I also didn't intend to imply that the NAT was being used as a firewall, rather that the NAT is commonly used today as an element within firewalls.

My own thoughts (which is off-topic) is that traditional firewalls have had their day and remain valuable. However, I am actively pursuing alternatives which perform the same functions without impacting the end-to-end performance of the protocols. Research into several approaches like this have excited me. But then, I've wandered far off topic.

-----Original Message-----
From: James Seng [mailto:jseng@pobox.org.sg]
Sent: Wednesday, June 18, 2003 10:38 PM
To: Fleischman, Eric
Cc: EKR; Keith Moore; pbaker@verisign.com; Ronald.vanderPol@rvdp.org;
aarsenau@bbn.com; ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department
forma lly adopts IPv6)


If you need a secure zone, and you want a firewall, then should install 
a firewall. You should not put an NAT thinking that it is also a firewall.

But I agree with you that NAT is here to stay.

-James Seng

Fleischman, Eric wrote:
> Eric Rescorla [mailto:ekr@rtfm.com] wrote:
> 
> 
>>>similarly, people who install NAT usually don't realize how much this
>>>costs them in lost functionality and reliability.
> 
> 
>>Really? You have evidence of this?
> 
> 
>>I don't either, but my intuition is that you're wrong.  Once you have
>>decided to have a firewall in place (which you may think is evil, but
>>I consider pretty much a necessary evil), I suspect that most people
>>suffer almost not at all from having a NAT.
> 
> 
> I believe that Eric is pointing out an important point: many deployments of NATs have nothing to do with IPv4 address conservation. Rather, they are firewall adjuncts implemented to hide internal networks from outside scrutiny and direct access. 
> 
> One point where I disagree with my IPv6-advocating friends is that I expect firewall-related NATs to continue to be deployed within Internet (including IPv6) environments until such a time as real-time-protocol and peer-to-peer-protocol friendly "distributed firewall" (policy zones) variants become the preferable "due diligence" alternative for CIOs.
> 
> 
> 
> 





From owner-ietf@ietf.org  Thu Jun 19 11:29:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25278
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 11:29:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T1I6-0004Lc-DM
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 11:25:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T12Z-0002yX-JV
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 11:09:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24095
	for <ietf@ietf.org>; Thu, 19 Jun 2003 11:09:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T10H-0005UN-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:07:10 -0400
Received: from pop017pub.verizon.net ([206.46.170.210] helo=pop017.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T10H-0005UC-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:07:09 -0400
Received: from earthlink.net ([4.65.83.168]) by pop017.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030619150859.IUNB27254.pop017.verizon.net@earthlink.net>;
          Thu, 19 Jun 2003 10:08:59 -0500
Message-ID: <3EF1D0F9.6226A70D@earthlink.net>
Date: Thu, 19 Jun 2003 08:04:25 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
CC: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly 
 adopts IPv6)
References: <200306191127.h5JBR3ih009794@ginger.lcs.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at pop017.verizon.net from [4.65.83.168] at Thu, 19 Jun 2003 10:08:59 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"J. Noel Chiappa" wrote:
> 
>     > From: Keith Moore <moore@cs.utk.edu>
> 
>     > The reason that we are explaining (once again) why NAT sucks is that
>     > some people in this community are still in denial about that
> 
> The person who's most in denial around here is you - about how definitively
> the market has, for the moment, chosen IPv4+NAT as the best balance between
> cost and effectiveness.
> 
> Get a grip. We all know you don't like NAT. You don't need to reply to
> *every* *single* *message* *about* *NAT* explaining for the 145,378,295th
> time how bad they are.

Legend tells us Cato, a Roman senator during the Punic Wars, finished
every speech he made in the Senate with the words "Carthage Must Be
Destroyed". It didn't matter if it was a speech about defense, or
monetary policy or the Roman water works. His one-eyed devotion to this
task was, well, determined. Keith sort of puts me in mind of Cato...


			- peterd (CMBD)

PDF: I've decided that as punishment for joining in "Yet Another
Flamewar About NATs" (YAFAN), I must now append something suitable to
every message.



From owner-ietf@ietf.org  Thu Jun 19 11:41:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26042
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 11:41:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T1I6-0004Li-KR
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 11:25:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T12z-0002yi-1V
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 11:09:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24104
	for <ietf@ietf.org>; Thu, 19 Jun 2003 11:09:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T10h-0005UY-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:07:35 -0400
Received: from pop018pub.verizon.net ([206.46.170.212] helo=pop018.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T10g-0005UK-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:07:34 -0400
Received: from earthlink.net ([4.65.83.168]) by pop018.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030619150924.EINX11703.pop018.verizon.net@earthlink.net>;
          Thu, 19 Jun 2003 10:09:24 -0500
Message-ID: <3EF1D113.CF3AAB36@earthlink.net>
Date: Thu, 19 Jun 2003 08:04:51 -0700
From: Peter Deutsch <pdeutsch@earthlink.net>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: S Woodside <sbwoodside@yahoo.com>, ietf@ietf.org
Subject: Re: myth of the great transition
References: <20030618153911.49945ac0.moore@cs.utk.edu>
		<E8CA8EC9-A210-11D7-84BB-000393414368@yahoo.com> <20030619054449.1d4aec68.moore@cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at pop018.verizon.net from [4.65.83.168] at Thu, 19 Jun 2003 10:09:24 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Keith Moore wrote:
> 
> > > expecting the network
> > > to isolate insecure hosts from untrustworthy attackers, or more
> > > generally, to enforce policy about what kinds of content are
> > > permitted to pass, has always been a stretch.
> > >
> >
> > So where do firewalls fit into your picture? Do they represent for the
> > network or for the hosts?
> 
> I believe the primary purpose of firewalls should be to protect the network,
> not the hosts, from abusive or unauthorized usage.

So for every firewall you purchase and install, you can focus its
configuration and operation on protecting the network from your users. I
trust you agree that it's appropriate for the rest of the world to be
free to make similar decisions in what they choose to be their own
perceived best interest? And I hope you'll not be *too* surprised when
the vast majority decide that protecting their own machines from the
network is more important than protecting the network from their own
machines...



				- peterd (CMBD)



From owner-ietf@ietf.org  Thu Jun 19 11:47:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26488
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 11:47:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T1K6-0004a6-4j
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 11:27:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T17c-00037m-2a
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 11:14:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24250
	for <ietf@ietf.org>; Thu, 19 Jun 2003 11:14:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T15K-0005X2-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:12:22 -0400
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 19T15J-0005Wt-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:12:21 -0400
Received: from cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 19 Jun 2003 08:12:09 -0800
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h5JFE9IX000102;
	Thu, 19 Jun 2003 08:14:10 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AFF86683;
	Thu, 19 Jun 2003 08:14:09 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id IAA09169; Thu, 19 Jun 2003 08:14:09 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16113.54080.993819.863810@thomasm-u1.cisco.com>
Date: Thu, 19 Jun 2003 08:14:08 -0700 (PDT)
To: EKR <ekr@rtfm.com>
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
In-Reply-To: <kju1ankzkr.fsf@romeo.rtfm.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
	<kju1ankzkr.fsf@romeo.rtfm.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric Rescorla writes:
 > What applications that people want to run--and the IT managers would
 > want to enable--are actually inhibited by NAT? It seems to me that
 > most of the applications inconvenienced by NAT are ones that IT
 > managers would want to screen off anyway.

Uh, have you paid no attention to voice? It
qualifies on both counts. We get complaints from
customers each and every day... the ones that are
lucky enough to figure out that NAT is why their
IP phone doesn't work that is.

	 Mike



From owner-ietf@ietf.org  Thu Jun 19 11:56:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26999
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 11:56:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T1K8-0004fv-EH
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 11:27:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T1F8-00045K-Q8
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 11:22:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24948
	for <ietf@ietf.org>; Thu, 19 Jun 2003 11:22:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T1Cr-0005eA-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:20:09 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T1Cq-0005cU-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:20:08 -0400
Received: from rshockeybox.shockey.us (neustargw.va.neustar.com [209.173.53.233])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h5JFPA707646;
	Thu, 19 Jun 2003 08:25:10 -0700
Message-Id: <5.2.0.9.2.20030619111208.064833e0@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 19 Jun 2003 11:18:46 -0400
To: Paul Vixie <paul@vix.com>
From: Richard Shockey <richard@shockey.us>
Subject: Re: myth of the great transition (was US Defense Department
  forma lly adopts IPv6) 
Cc: ietf@ietf.org
In-Reply-To: <20030619024532.B653C13969@sa.vix.com>
References: <Message from Richard Shockey <richard@shockey.us>
 <5.2.0.9.2.20030618211441.02203e80@shockey.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 02:45 AM 6/19/2003 +0000, Paul Vixie wrote:

> > Which BTW come July 1 becomes illegal in the US with the implementation of
> > the Federal Trade Commission Do Not Call list.
>
>which country's "federal" do you mean?
>
> > http://www.ftc.gov/bcp/conline/edcams/donotcall/index.html
>
>oh, that one.  i guess that means the function will have to move offshore.
>THAT'll sure teach those spammers a lesson.

Remember Paul ..the issue in most of these laws is to go after the company 
offering the products, porn, whatever _via_ spam.

The spam in most cases is trying to induce you to buy something ..they have 
to give out some site that collects a credit card or phone number for 
contact or something that is clearly traceable. That the spam itself was 
sent from a open relay in Pakistan makes no difference .. if the company 
offering the stuff has a nexus in the US bank account etc it can be traced 
and prosecuted.





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




From owner-ietf@ietf.org  Thu Jun 19 11:56:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26998
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 11:56:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T1K8-0004ga-Sz
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 11:27:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T1Fx-00045j-LS
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 11:23:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25011
	for <ietf@ietf.org>; Thu, 19 Jun 2003 11:23:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T1Df-0005f7-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:21:00 -0400
Received: from albatross.mail.pas.earthlink.net ([207.217.120.120])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T1Da-0005f3-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:20:59 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by albatross.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19T1Fm-0000Rl-00; Thu, 19 Jun 2003 08:23:11 -0700
Date: Thu, 19 Jun 2003 11:20:15 -0400
From: Keith Moore <moore@cs.utk.edu>
To: pdeutsch@earthlink.net
Cc: moore@cs.utk.edu, sbwoodside@yahoo.com, ietf@ietf.org
Subject: firewall logic (was Re: myth of the great transition)
Message-Id: <20030619112015.66c23a14.moore@cs.utk.edu>
In-Reply-To: <3EF1D113.CF3AAB36@earthlink.net>
References: <20030618153911.49945ac0.moore@cs.utk.edu>
	<E8CA8EC9-A210-11D7-84BB-000393414368@yahoo.com>
	<20030619054449.1d4aec68.moore@cs.utk.edu>
	<3EF1D113.CF3AAB36@earthlink.net>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > I believe the primary purpose of firewalls should be to protect the
> > network, not the hosts, from abusive or unauthorized usage.
> 
> So for every firewall you purchase and install, you can focus its
> configuration and operation on protecting the network from your users. I
> trust you agree that it's appropriate for the rest of the world to be
> free to make similar decisions in what they choose to be their own
> perceived best interest? 

we're talking about different things.  I'm talking about architecture and
specifically what separation of function/responsibility between firewalls and
the network would allow both security and flexibility to be maximized.
you're talking about decisions that people make between products that work
with (or against) the existing architecture.



From owner-ietf@ietf.org  Thu Jun 19 11:57:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23038
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 10:59:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T0Xh-0008CV-2x
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 10:37:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T0UX-0007o8-EQ
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 10:34:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21774
	for <ietf@ietf.org>; Thu, 19 Jun 2003 10:34:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T0SF-0004vv-00
	for ietf@ietf.org; Thu, 19 Jun 2003 10:31:59 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T0SE-0004vg-00
	for ietf@ietf.org; Thu, 19 Jun 2003 10:31:59 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 0436CABB5; Thu, 19 Jun 2003 07:39:56 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: dts@senie.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
	<20030619060744.391b92e6.moore@cs.utk.edu>
	<kj4r2mnp0r.fsf@romeo.rtfm.com>
	<20030619101050.2eb0bd0f.moore@cs.utk.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 07:39:56 -0700
In-Reply-To: <20030619101050.2eb0bd0f.moore@cs.utk.edu>
Message-ID: <kjznkem8qr.fsf@romeo.rtfm.com>
Lines: 18
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> > If the customers are getting what they want, that seems to me that it
> > can hardly be characterized as a "mess". And you have yet to establish
> > that they're not getting what they want.
> 
> certainly the users I deal with are not getting what they want.
> others seem to be reporting similar experiences.

Then why don't they switch providers. Revealed preference suggests
that they *are* getting what they want, no matter how much
complaining.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 12:02:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27595
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 12:02:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T1jg-0006yk-Vw
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 11:54:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T1QS-0005SA-Ct
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 11:34:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25654
	for <ietf@ietf.org>; Thu, 19 Jun 2003 11:34:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T1OA-0005nc-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:31:50 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T1OA-0005nM-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:31:50 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 1BE4913948
	for <ietf@ietf.org>; Thu, 19 Jun 2003 15:33:40 +0000 (GMT)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Message from Richard Shockey <richard@shockey.us> 
	of "Thu, 19 Jun 2003 11:18:46 -0400."
	<5.2.0.9.2.20030619111208.064833e0@shockey.us> 
X-Mailer: MH-E 7.3; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 19 Jun 2003 15:33:40 +0000
Message-Id: <20030619153340.1BE4913948@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> Remember Paul ..the issue in most of these laws is to go after the
> company offering the products, porn, whatever _via_ spam.

and when they are syn-scanning me from outside the us i can tell who
their client is how?

and when the robot calls back asking me to hold on the line for a human
operator, exactly what law is being broken?

here's the broken record, one more time.  if you build a worldwide
communications infrastructure, you should expect it to get Used.



From owner-ietf@ietf.org  Thu Jun 19 12:05:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28012
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 12:05:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T1jh-00070N-Jh
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 11:54:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T1Wu-0005j9-AM
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 11:40:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26021
	for <ietf@ietf.org>; Thu, 19 Jun 2003 11:40:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T1Uc-0005uD-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:38:30 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T1Ub-0005u9-00
	for ietf@ietf.org; Thu, 19 Jun 2003 11:38:30 -0400
Subject: RE: NATs are NOT Firewalls 
Date: Thu, 19 Jun 2003 08:40:54 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <963621801C6D3E4A9CF454A1972AE8F506722B@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: NATs are NOT Firewalls 
Thread-Index: AcM2O3YtSG7PKeJNQROUpRfjrn2sZwAOah3wAAEB6jA=
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Daniel Senie" <dts@senie.com>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA28012

Daniel,

I agree with the rest of your post, however

> Since NAPT uses stateful inspection to operate,

I think I don't agree with this. I would say that NAPT is a stateful
process but not that it uses inspection. By "inspection" I understand a
more intelligent process that decapsulates packets and looks for "bad"
things inside them, which is a separate function.

In other words, there is a difference between 'stateful' and 'stateful
inspection'. 'Stateful' is a feature of both NAPT boxes and firewalls;
'stateful inspection' is a feature of more sophisticated firewalls only;
if you happen to find a NAPT box that does stateful inspection (the $50
ones don't) it could indeed be called a firewall.

Michel.




From owner-ietf@ietf.org  Thu Jun 19 12:24:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28953
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 12:24:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T27L-0001rJ-5O
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 12:18:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T24e-0001R8-7C
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 12:15:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28609
	for <ietf@ietf.org>; Thu, 19 Jun 2003 12:15:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T22M-0006Zi-00
	for ietf@ietf.org; Thu, 19 Jun 2003 12:13:22 -0400
Received: from krusty-motorsports.com ([192.94.170.8] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T22L-0006Zf-00
	for ietf@ietf.org; Thu, 19 Jun 2003 12:13:21 -0400
Received: from [24.194.112.77] (helo=skipper.averillpark.net)
	by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.14)
	id 19T24c-0000sU-5S
	for ietf@ietf.org; Thu, 19 Jun 2003 16:15:42 +0000
Received: from rwelty by skipper.averillpark.net with local (Exim 4.14)
	id 19T23j-0004is-Dp
	for ietf@ietf.org; Thu, 19 Jun 2003 12:14:47 -0400
Date: Thu, 19 Jun 2003 12:14:47 -0400 (EDT)
From: Richard Welty <rwelty@averillpark.net>
Subject: Re[2]: myth of the great transition (was US Defense Department forma lly adopts IPv6)
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE
References: <200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306190531.h5J5V5PZ001358@turing-police.cc.vt.edu>
 <kj8yrynp5v.fsf@romeo.rtfm.com>
In-Reply-To: <kj8yrynp5v.fsf@romeo.rtfm.com>
X-Mailer: Mahogany 0.64 'Sparc', compiled for Linux 2.4.9-13 i686
Message-Id: <E19T23j-0004is-Dp@skipper.averillpark.net>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Sender: owner-ietf@ietf.org
Precedence: bulk

On 19 Jun 2003 06:59:56 -0700 Eric Rescorla <ekr@rtfm.com> wrote:

> Valdis.Kletnieks@vt.edu writes:
> > And the fact that NAT breaks things that you DO want to run is a <?>
> I'm not convinced that this is happening... if it is,
> why isn't there a market reaction.

such maybe building. i have a client who for budgetary reasons are using an
inexpensive Ameritech DSL line. because of their location, they have
extremely limited broadband options.

Ameritech only gives them a /29, with no option for additional IPs
available. a third party vendor also requires IPSec for an application they
need, and the third party only supports pre-shared keys.

the needed three legged firewall, bridging two interfaces and using NAT on
the third one, is rather more complicated than i wanted to deploy for a
budget-constrained customer. neither i nor my client feel that there was a
much of a win here, but there weren't any other options, either.

i'll wager that increasing use of IPSec will start to create pressure. just
a hunch. but my customer can't create meaningful pressure when the phone
company is involved; it takes thousands of small customers screaming to get
an RBOC to take notice, maybe more. it could be a few years...
 
> Given that there are workarounds for these, I find this explanation
> pretty unlikely. More likely is that people's revealed preference
> is that they don't actually want this stuff.

all too often, for small customers, the workarounds are expensive or unknown
to them. in the particular case i cited above, my customer would have spent
a lot less money on my time if they could have simply gotten a /27 from
Ameritech and dispensed with port NAT entirely, and they and i both know
that this was the preferred option.

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





From owner-ietf@ietf.org  Thu Jun 19 12:28:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29188
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 12:28:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T2Ci-0002v1-Ov
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 12:24:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T2BC-0002ZZ-98
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 12:22:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28888
	for <ietf@ietf.org>; Thu, 19 Jun 2003 12:22:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T28u-0006dl-00
	for ietf@ietf.org; Thu, 19 Jun 2003 12:20:08 -0400
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T28t-0006d0-00
	for ietf@ietf.org; Thu, 19 Jun 2003 12:20:07 -0400
Received: from mail5.microsoft.com ([157.54.6.156]) by mail4.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Thu, 19 Jun 2003 09:21:57 -0700
Received: from inet-vrs-05.redmond.corp.microsoft.com ([157.54.6.157]) by mail5.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Thu, 19 Jun 2003 09:21:53 -0700
Received: from 157.54.8.109 by inet-vrs-05.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 19 Jun 2003 09:21:53 -0700
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-hub-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 19 Jun 2003 09:21:52 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 19 Jun 2003 09:21:51 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.82]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3788.0);
	 Thu, 19 Jun 2003 09:21:53 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6940.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: myth of the great transition (was US Defense Department forma lly  adopts IPv6)
Date: Thu, 19 Jun 2003 09:21:45 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA03CFC3F4@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: myth of the great transition (was US Defense Department forma lly  adopts IPv6)
Thread-Index: AcM2d7noOHMrl/qTQN+Uij/cHHVPHwABwxTg
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: <pdeutsch@earthlink.net>, "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: <ietf@ietf.org>
X-OriginalArrivalTime: 19 Jun 2003 16:21:53.0055 (UTC) FILETIME=[E4E5CAF0:01C3367E]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA29188

> > The person who's most in denial around here is you - about how
> definitively
> > the market has, for the moment, chosen IPv4+NAT as the best balance
> between
> > cost and effectiveness.
> >
> > Get a grip. We all know you don't like NAT. You don't need to reply
to
> > *every* *single* *message* *about* *NAT* explaining for the
> 145,378,295th
> > time how bad they are.
> 
> Legend tells us Cato, a Roman senator during the Punic Wars, finished
> every speech he made in the Senate with the words "Carthage Must Be
> Destroyed". It didn't matter if it was a speech about defense, or
> monetary policy or the Roman water works. His one-eyed devotion to
this
> task was, well, determined. Keith sort of puts me in mind of Cato...

Carthage was eventually destroyed, but Cato died before that.

-- Christian Huitema




From owner-ietf@ietf.org  Thu Jun 19 12:41:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00112
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 12:41:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T2PT-0006DO-Ez
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 12:37:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T2Oy-0005pI-3V
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 12:36:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29806
	for <ietf@ietf.org>; Thu, 19 Jun 2003 12:36:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T2Mg-0006r5-00
	for ietf@ietf.org; Thu, 19 Jun 2003 12:34:22 -0400
Received: from krusty-motorsports.com ([192.94.170.8] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T2Mf-0006r1-00
	for ietf@ietf.org; Thu, 19 Jun 2003 12:34:21 -0400
Received: from [24.194.112.77] (helo=skipper.averillpark.net)
	by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.14)
	id 19T2Ow-0001Bx-68
	for ietf@ietf.org; Thu, 19 Jun 2003 16:36:42 +0000
Received: from rwelty by skipper.averillpark.net with local (Exim 4.14)
	id 19T2MJ-0004jo-WB
	for ietf@ietf.org; Thu, 19 Jun 2003 12:33:59 -0400
Date: Thu, 19 Jun 2003 12:33:59 -0400 (EDT)
From: Richard Welty <rwelty@averillpark.net>
Subject: Re[2]: myth of the great transition (was US Defense Department forma lly adopts IPv6)
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
	<20030619060744.391b92e6.moore@cs.utk.edu>
	<kj4r2mnp0r.fsf@romeo.rtfm.com>
	<20030619101050.2eb0bd0f.moore@cs.utk.edu>
 <kjznkem8qr.fsf@romeo.rtfm.com>
In-Reply-To: <kjznkem8qr.fsf@romeo.rtfm.com>
X-Mailer: Mahogany 0.64 'Sparc', compiled for Linux 2.4.9-13 i686
Message-Id: <E19T2MJ-0004jo-WB@skipper.averillpark.net>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Sender: owner-ietf@ietf.org
Precedence: bulk

On 19 Jun 2003 07:39:56 -0700 Eric Rescorla <ekr@rtfm.com> wrote:
> Then why don't they switch providers. Revealed preference suggests
> that they *are* getting what they want, no matter how much
> complaining.

in many places, the choice of broadband providers is quite poor. see my
earlier posting about my client for whom Ameritech DSL was the only
affordable choice, and we just barely made it work for their application.

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





From owner-ietf@ietf.org  Thu Jun 19 13:09:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01445
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 13:09:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T2nT-00014y-7f
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:02:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T2mT-0000rw-4H
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:01:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01105
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:00:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T2kB-0007BE-00
	for ietf@ietf.org; Thu, 19 Jun 2003 12:58:39 -0400
Received: from barry.mail.mindspring.net ([207.69.200.25])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T2kA-0007BB-00
	for ietf@ietf.org; Thu, 19 Jun 2003 12:58:38 -0400
Received: from h-66-167-50-101.atlngahp.covad.net ([66.167.50.101] helo=primate)
	by barry.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 19T2mM-0003SY-00; Thu, 19 Jun 2003 13:00:54 -0400
From: "Neil Carpenter" <primate@mindspring.com>
To: "'Richard Welty'" <rwelty@averillpark.net>, <ietf@ietf.org>
Subject: RE: Re[2]: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Date: Thu, 19 Jun 2003 13:00:47 -0400
Message-ID: <003601c33684$582468f0$3200a8c0@primate>
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.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <E19T2MJ-0004jo-WB@skipper.averillpark.net>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> in many places, the choice of broadband providers is quite poor. see
my
> earlier posting about my client for whom Ameritech DSL was the only
> affordable choice, and we just barely made it work for their
application.
> 

This seems like a specious argument.  The client had chosen, as you
indicate, to scrimp on their broadband provider to save money.  You also
indicate that other providers were available.

The nature of picking any product is cost vs. benefit.  In this case,
the customer chose to favor cost and, thus, received less benefit.




From owner-ietf@ietf.org  Thu Jun 19 13:09:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01444
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 13:09:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T2pP-0001J0-GM
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:04:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T2nf-000158-RO
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:02:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01151
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:02:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T2lO-0007Bq-00
	for ietf@ietf.org; Thu, 19 Jun 2003 12:59:54 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T2lN-0007Ba-00
	for ietf@ietf.org; Thu, 19 Jun 2003 12:59:53 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 77AC2ABB5; Thu, 19 Jun 2003 10:07:45 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: dts@senie.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
	<20030619060744.391b92e6.moore@cs.utk.edu>
	<kj4r2mnp0r.fsf@romeo.rtfm.com>
	<20030619101050.2eb0bd0f.moore@cs.utk.edu>
	<kjznkem8qr.fsf@romeo.rtfm.com>
	<20030619104013.57201da1.moore@cs.utk.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 10:07:45 -0700
In-Reply-To: <20030619104013.57201da1.moore@cs.utk.edu>
Message-ID: <kjof0um1we.fsf@romeo.rtfm.com>
Lines: 36
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> > > certainly the users I deal with are not getting what they want.
> > > others seem to be reporting similar experiences.
> > 
> > Then why don't they switch providers.
> 
> variety of reasons: often the provider is not the problem, it's the local
> network admins, and the users aren't free to go elsewhere.  some of the time
> when the provider is the problem, there are no alternatives.  until recently
> the only way I could get even one static IP address for my home was through a
> special deal with a friend of mine who had a small ISP, and the best bandwidth
> I could get was 128kbps.  none of the other local providers would sell me one.
Doesn't the fact that there's not enough demand for this product
to make it available suggest anything to you?

> > Revealed preference suggests that they *are* getting what they want, no
> > matter how much complaining.
> 
> so if you can't come up with a rational explanation for something, just
> pretend that the market is wise and cite it as an unimpeachable authority.

I do have a rational explanation: the customers don't actually care
at all about your fundamentalist commitment to end-to-end connectivity.

So, on the one hand, we have the actual behavior of millions of people.
On the other hand we have Keith Moore's opinion about what they ought
to prefer. I don't have any trouble figuring out which one I believe.

-Ekr



-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 13:15:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01874
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 13:15:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T2rl-0001Y0-Jm
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:06:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T2px-0001Ja-UR
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:04:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01223
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:04:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T2ng-0007D3-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:02:16 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T2nf-0007D0-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:02:15 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 38511ABB5; Thu, 19 Jun 2003 10:10:13 -0700 (PDT)
To: Michael Thomas <mat@cisco.com>
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
	<kju1ankzkr.fsf@romeo.rtfm.com>
	<16113.54080.993819.863810@thomasm-u1.cisco.com>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 10:10:13 -0700
In-Reply-To: <16113.54080.993819.863810@thomasm-u1.cisco.com>
Message-ID: <kjisr2m1sa.fsf@romeo.rtfm.com>
Lines: 22
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Michael Thomas <mat@cisco.com> writes:

> Eric Rescorla writes:
>  > What applications that people want to run--and the IT managers would
>  > want to enable--are actually inhibited by NAT? It seems to me that
>  > most of the applications inconvenienced by NAT are ones that IT
>  > managers would want to screen off anyway.
> 
> Uh, have you paid no attention to voice? It
> qualifies on both counts. We get complaints from
> customers each and every day... the ones that are
> lucky enough to figure out that NAT is why their
> IP phone doesn't work that is.

As I said, these would be screened off by corporate firewalls in most
cases anyway.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 13:16:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02023
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 13:16:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T2wB-0002dC-Lm
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:11:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T2vb-0002LH-RS
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:10:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01544
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:10:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T2tK-0007Gt-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:08:06 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T2tJ-0007Fx-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:08:05 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id B0846ABB5; Thu, 19 Jun 2003 10:16:00 -0700 (PDT)
To: Melinda Shore <mshore@cisco.com>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <200306191448.AIO59278@mira-sjc5-c.cisco.com>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 10:16:00 -0700
In-Reply-To: <200306191448.AIO59278@mira-sjc5-c.cisco.com>
Message-ID: <kjfzm6m1in.fsf@romeo.rtfm.com>
Lines: 24
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Melinda Shore <mshore@cisco.com> writes:
> As I said before, the workarounds that are being
> used to help facilitate application traversal of NATs are
> definitely introducing new security problems that wouldn't
> exist if the NAT weren't there. There are other problems
> around robustness and routing.  I think this is a bad thing,
> myself.
No doubt it's a bad thing. Very few technical solutions are unalloyed
goods. I think of these sorts of things as sort of the networking
equipment of drug side effects--an undesirable side effect of things
that are otherwise desirable. Now, reasonable people can disagree as
to the relative importance of the good and bad effects, but absent
evidence to the contrary, I generally assume that people are able
to make those choices for themselves.

I'm not sure what you mean by routing above. Are you suggesting there's
some negative externality in that NAT makes the routing infrastructure
more complicated? If so, what is it?

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 13:25:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02458
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 13:25:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T33v-00054S-Bi
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:19:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T33M-0004xk-Na
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:18:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02207
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:18:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T314-0007TD-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:16:06 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T314-0007ST-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:16:06 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h5JHHqFh004530;
	Thu, 19 Jun 2003 10:17:52 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AFG00154;
	Thu, 19 Jun 2003 10:17:51 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA09689; Thu, 19 Jun 2003 10:17:51 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16113.61503.713004.490359@thomasm-u1.cisco.com>
Date: Thu, 19 Jun 2003 10:17:51 -0700 (PDT)
To: EKR <ekr@rtfm.com>
Cc: Michael Thomas <mat@cisco.com>, Keith Moore <moore@cs.utk.edu>,
        ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
In-Reply-To: <kjisr2m1sa.fsf@romeo.rtfm.com>
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
	<kju1ankzkr.fsf@romeo.rtfm.com>
	<16113.54080.993819.863810@thomasm-u1.cisco.com>
	<kjisr2m1sa.fsf@romeo.rtfm.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric Rescorla writes:
 > Michael Thomas <mat@cisco.com> writes:
 > 
 > > Eric Rescorla writes:
 > >  > What applications that people want to run--and the IT managers would
 > >  > want to enable--are actually inhibited by NAT? It seems to me that
 > >  > most of the applications inconvenienced by NAT are ones that IT
 > >  > managers would want to screen off anyway.
 > > 
 > > Uh, have you paid no attention to voice? It
 > > qualifies on both counts. We get complaints from
 > > customers each and every day... the ones that are
 > > lucky enough to figure out that NAT is why their
 > > IP phone doesn't work that is.
 > 
 > As I said, these would be screened off by corporate firewalls in most
 > cases anyway.

That there are also issues with firewalls is
entirely beside the point. And firewall traversal
using a VPN is a trivial and deployed solution to
the firewall traversal problem. And is often a
good one, modulo inflated packet size for RTP
streams which generate small packets.

Thus the point stands: NAT's are right now a
serious problem for the deployment of voice. By
real customers who have real desires for
deployment. Your handwaving here is not borne out
in the reality of our business or anybody else's
who's involved with voice. And frankly your
uninformed dismissive tone here is rather
unbecoming for those of us who've had to actually
deal with this issue for years.

	  Mike



From owner-ietf@ietf.org  Thu Jun 19 13:33:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03075
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 13:33:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3Ak-00068Q-RV
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:26:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T36h-0005L0-2z
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:21:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02376
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:21:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T34P-0007VC-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:19:33 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T34O-0007V8-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:19:32 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5JHLlN29862;
        Thu, 19 Jun 2003 13:21:49 -0400 (EDT)
Date: Thu, 19 Jun 2003 13:21:47 -0400
From: Keith Moore <moore@cs.utk.edu>
To: EKR <ekr@rtfm.com>
Cc: moore@cs.utk.edu, dts@senie.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619132147.4eeb4def.moore@cs.utk.edu>
In-Reply-To: <kjof0um1we.fsf@romeo.rtfm.com>
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
	<20030619060744.391b92e6.moore@cs.utk.edu>
	<kj4r2mnp0r.fsf@romeo.rtfm.com>
	<20030619101050.2eb0bd0f.moore@cs.utk.edu>
	<kjznkem8qr.fsf@romeo.rtfm.com>
	<20030619104013.57201da1.moore@cs.utk.edu>
	<kjof0um1we.fsf@romeo.rtfm.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > until recently the only way I could get even one
> > static IP address for my home was through a special deal with a
> > friend of mine who had a small ISP, and the best bandwidth I could
> > get was 128kbps.  none of the other local providers would sell me
> > one.
>
> Doesn't the fact that there's not enough demand for this product
> to make it available suggest anything to you?

does the fact that there was enough demand for the product that it
eventually became available suggest anything to you?

> > so if you can't come up with a rational explanation for something,
> > just pretend that the market is wise and cite it as an unimpeachable
> > authority.
> 
> I do have a rational explanation: the customers don't actually care
> at all about your fundamentalist commitment to end-to-end
> connectivity.

true, customers don't care about e2e.  they do, however, care about
running apps that won't work when e2e is broken.

> So, on the one hand, we have the actual behavior of millions of
> people.

no, we have your biased interpretation of that behavior, as observed
from a great distance, through a dirty lens. 

Keith



From owner-ietf@ietf.org  Thu Jun 19 13:34:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03220
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 13:34:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3Dc-0006rg-Id
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:29:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3Ck-0006hM-0F
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:28:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02710
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:28:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3AR-0007ak-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:25:47 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3AQ-0007aY-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:25:47 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h5JHSuxS024645;
	Thu, 19 Jun 2003 19:28:56 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Thu, 19 Jun 2003 19:28:02 +0200
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200306191149.h5JBnEEk009892@ginger.lcs.mit.edu>
Message-Id: <611017A2-A27B-11D7-A48D-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On donderdag, jun 19, 2003, at 13:49 Europe/Amsterdam, J. Noel Chiappa 
wrote:

>> Maybe NATs are, in fact, a result
>> of a very deep problem with our architecture.

> My take is that NAT's respond to several flaws in the IPv4 
> architecture:

> - 1) Not enough addresses - this being the one that brought them into
> 	existence.

Since there are 1.5 billion unallocated addresses lying around in some 
storage room at IANA, the IPv4 address shortage problem in itself can't 
be the reason for the existence of NAT. The real problem is that ISPs 
are unwilling to give out addresses to customers in a way that 
customers find acceptable and affordable.

> - 1a) Local allocation of addresses - a variant of the preceeding one, 
> but
> 	subtly different; NAT's do allow you to allocate more addresses
> 	locally without going back to a central number allocation authority,
> 	which is very convenient.

Right.

> I think that if you look at the points I listed above, the market has 
> clearly
> decided that IPv4+NAT (for all its problems, with which people are I'm 
> sure
> reasonably familiar, given the many years NAT has been in service 
> widely) is
> the most cost-effective solution to providing them. The IETF really 
> needs to
> sit and ponder the implications of that.

Designing a NAT architecture that doesn't have the disadvantages 
current NAT has wouldn't be much of a challenge. A little outside 
address discovery here, some dynamic server port assignment there, and 
we're well on our way. However, this would still require massive 
changes to all applications (not just the ones that don't work with NAT 
today) and to deployed NATs. But instant deployability is exactly what 
makes NAT so prevalent today. If implementing NATng is as much trouble 
as implementing IPv6, why bother?




From owner-ietf@ietf.org  Thu Jun 19 13:37:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03636
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 13:37:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3GW-0007O5-44
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:32:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3FF-0006zK-Pw
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:30:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02919
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:30:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3Cx-0007dd-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:28:24 -0400
Received: from krusty-motorsports.com ([192.94.170.8] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3Cw-0007da-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:28:23 -0400
Received: from [24.194.112.77] (helo=skipper.averillpark.net)
	by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.14)
	id 19T3FC-0002Ht-CX
	for ietf@ietf.org; Thu, 19 Jun 2003 17:30:42 +0000
Received: from rwelty by skipper.averillpark.net with local (Exim 4.14)
	id 19T3CS-0004nw-9b
	for ietf@ietf.org; Thu, 19 Jun 2003 13:27:52 -0400
Date: Thu, 19 Jun 2003 13:27:51 -0400 (EDT)
From: Richard Welty <rwelty@averillpark.net>
Subject: Re[4]: myth of the great transition (was US Defense Department forma lly adopts IPv6)
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE
References: <003601c33684$582468f0$3200a8c0@primate>
In-Reply-To: <003601c33684$582468f0$3200a8c0@primate>
X-Mailer: Mahogany 0.64 'Sparc', compiled for Linux 2.4.9-13 i686
Message-Id: <E19T3CS-0004nw-9b@skipper.averillpark.net>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 19 Jun 2003 13:00:47 -0400 Neil Carpenter <primate@mindspring.com> wrote:

> > in many places, the choice of broadband providers is quite poor. see
> > my earlier posting about my client for whom Ameritech DSL was the
> > only affordable choice, and we just barely made it work for their
> > application.

> This seems like a specious argument.  The client had chosen, as you
> indicate, to scrimp on their broadband provider to save money.  You also
> indicate that other providers were available.
 
> The nature of picking any product is cost vs. benefit.  In this case,
> the customer chose to favor cost and, thus, received less benefit.

well, they'd dumped Covad for abysmal service. anyone else was so pricy
that the project would not go forward at all; the monthly recurring cost
was simply a budget buster.

it's not a matter of scrimping so much as a matter of whether the project
is even feasible under the budgetary constraints. port NAT enables some
folks to run lots of computers behind small subnets, sure, but it also has
the side effect of disabling or nearly disabling lots of other
technologies. the folks who have the hardest problems are the ones with the
least cash. telling someone with a small budget that they can solve their
problem with an application of more money (to get a better provider) isn't
advice that goes down so well.

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





From owner-ietf@ietf.org  Thu Jun 19 13:52:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04583
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 13:52:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3U4-0001r2-Nv
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:46:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3Rf-0001R0-PS
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:43:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04228
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:43:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3PN-0000Ag-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:41:13 -0400
Received: from tomts16.bellnexxia.net ([209.226.175.4] helo=tomts16-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3PM-0000Ad-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:41:12 -0400
Received: from yahoo.com ([65.93.185.42]) by tomts16-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030619174331.QMDJ26560.tomts16-srv.bellnexxia.net@yahoo.com>;
          Thu, 19 Jun 2003 13:43:31 -0400
Date: Thu, 19 Jun 2003 13:43:30 -0400
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Daniel Senie <dts@senie.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
Message-Id: <8A263D04-A27D-11D7-A41F-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Exactly. A NAPT  (not a NA(!P)T ......) is in fact a perfectly good 
firewall* for the home user. So all this argumentation that a "NAPT is 
not a firewall" is bunk.

* where firewall = a device that protect my internal net from external 
threats

simon

On Thursday, June 19, 2003, at 03:46  AM, Daniel Senie wrote:

> A $50 NAPT box (using terminology from the NAT WG's terminology RFC) 
> provides sufficient firewalling and purposeful interruption of 
> applications for the typical DSL or cable modem user. It runs 
> somewhere OTHER than on the user's computer, so when a virus gets in 
> and tries to disable the user's firewall software, less damage is > done.
>

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Thu Jun 19 13:54:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04865
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 13:54:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3VI-00020W-EV
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:47:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3U3-0001po-1Q
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:46:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04301
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:46:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3Rl-0000Bb-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:43:41 -0400
Received: from tomts26.bellnexxia.net ([209.226.175.189] helo=tomts26-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3Rk-0000BY-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:43:40 -0400
Received: from yahoo.com ([65.93.185.42]) by tomts26-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030619174555.IAAN22441.tomts26-srv.bellnexxia.net@yahoo.com>;
          Thu, 19 Jun 2003 13:45:55 -0400
Date: Thu, 19 Jun 2003 13:45:53 -0400
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org, Daniel Senie <dts@senie.com>
To: Keith Moore <moore@cs.utk.edu>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <20030619060744.391b92e6.moore@cs.utk.edu>
Message-Id: <DFA73ED0-A27D-11D7-A41F-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith, I don't get this argument. A NAPT is a firewall by your own 
definition "I believe the primary purpose of firewalls should be to 
protect the network, not the hosts, from abusive or unauthorized 
usage." It's implementing a very simple policy, protect me from the 
outside world.

simon

On Thursday, June 19, 2003, at 06:07  AM, Keith Moore wrote:

> and kills that user's ability to run valuable applications.  in fact, 
> the NAT
> is not a firewall at all.  it isn't implementing any policy specified 
> by the
> user.  what it's doing is imposing some arbitrary restrictions on the 
> user's
> network that may or may not serve the user's interests at all.  it's 
> snake
> oil.
>

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Thu Jun 19 14:00:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05280
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 14:00:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3cn-0003m8-0i
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:55:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3VV-00021G-07
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:47:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04324
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:47:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3TD-0000C7-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:45:11 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3TC-0000Bt-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:45:10 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id AD945ABB5; Thu, 19 Jun 2003 10:53:07 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: dts@senie.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
	<20030619060744.391b92e6.moore@cs.utk.edu>
	<kj4r2mnp0r.fsf@romeo.rtfm.com>
	<20030619101050.2eb0bd0f.moore@cs.utk.edu>
	<kjznkem8qr.fsf@romeo.rtfm.com>
	<20030619104013.57201da1.moore@cs.utk.edu>
	<kjof0um1we.fsf@romeo.rtfm.com>
	<20030619132147.4eeb4def.moore@cs.utk.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 10:53:07 -0700
In-Reply-To: <20030619132147.4eeb4def.moore@cs.utk.edu>
Message-ID: <kjhe6mj6nw.fsf@romeo.rtfm.com>
Lines: 52
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> > > until recently the only way I could get even one
> > > static IP address for my home was through a special deal with a
> > > friend of mine who had a small ISP, and the best bandwidth I could
> > > get was 128kbps.  none of the other local providers would sell me
> > > one.
> >
> > Doesn't the fact that there's not enough demand for this product
> > to make it available suggest anything to you?
> 
> does the fact that there was enough demand for the product that it
> eventually became available suggest anything to you?
Yeah, that there's a subset who cares. They got it. The market is
working. Why are you complaining?

> > > so if you can't come up with a rational explanation for something,
> > > just pretend that the market is wise and cite it as an unimpeachable
> > > authority.
> > 
> > I do have a rational explanation: the customers don't actually care
> > at all about your fundamentalist commitment to end-to-end
> > connectivity.
> 
> true, customers don't care about e2e.  they do, however, care about
> running apps that won't work when e2e is broken.
Apparently not, or they wold switch.

> > So, on the one hand, we have the actual behavior of millions of
> > people.
> 
> no, we have your biased interpretation of that behavior, as observed
> from a great distance, through a dirty lens. 
Huh? Are you claiming that people don't 
(1) Buy NATs
(2) Use them?

Of course they do. 

I'm not sure why you're accusing me of bias, Keith. Frankly, I hate
NAT. It makes my life as a protocol designer miserable and I don't use
it myself. I just don't fool myself that my preferences represent
those of people at large.

-Ekr




-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 14:03:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05559
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 14:03:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3cn-0003mG-B0
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:55:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3Vc-00021w-MB
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:47:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04328
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:47:39 -0400 (EDT)
From: ned.freed@mrochek.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3TK-0000CD-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:45:18 -0400
Received: from mauve.mrochek.com ([209.55.107.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3TJ-0000CA-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:45:18 -0400
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
 id <01KX9S49797K00CUGD@mauve.mrochek.com> for ietf@ietf.org; Thu,
 19 Jun 2003 10:47:30 -0700 (PDT)
Date: Thu, 19 Jun 2003 10:35:01 -0700 (PDT)
Subject: Re: myth of the great transition (was US Defense Department forma lly
 adopts IPv6)
In-reply-to: "Your message dated Wed, 18 Jun 2003 16:06:08 -0700"
 <kjbrwvkmu7.fsf@romeo.rtfm.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Melinda Shore <mshore@cisco.com>, ietf@ietf.org
Message-id: <01KX9Y5Q7F9K00CUGD@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Content-transfer-encoding: 7BIT
References: <200306181937.AIN64606@mira-sjc5-c.cisco.com>
 <kjbrwvkmu7.fsf@romeo.rtfm.com>
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

> Melinda Shore <mshore@cisco.com> writes:

> > > What applications that people want to run--and the IT managers would
> > > want to enable--are actually inhibited by NAT? It seems to me that
> > > most of the applications inconvenienced by NAT are ones that IT
> > > managers would want to screen off anyway.
> >
> > Not really.  For example, ftp as originally defined doesn't
> > work through NATs, and no standard VoIP or multimedia
> > conferencing protocol works through NAT.
> None of these things worked real well through firewalls either,
> which is sort of my point.

This certainly has not been my experience. All of my equipment is behind a
firewall, but I have two sets of IP address - a small set of carefully hoarded
global addresses and a much larger set of NATed addresses.

Whenever I add something (which it seems is often) I first try it with a NATted
address. If that doesn't work I am forced to switch it to a global address.

All too often (VoIP phone, video conferencing, file sharing, etc.) I am
forced to switch to a global address before things work properly.

The firewall, on the other hand, has only been a problem once, and that was
because of an unfortunate lack of flexibility in its handling of a fairly
unusual setup involving FTP. A patch readily solved the problem.

NAT being an issue hasn't escaped the notice of vendors. My VoIP phone's
documentation discussed NAT problems at some length, but the proposed
solution -- use a specific NAT product that has been gimmicked to work
correctly -- isn't always a viable option.

				Ned



From owner-ietf@ietf.org  Thu Jun 19 14:05:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05781
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 14:05:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3cn-0003mt-NA
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:55:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3WV-0002DJ-KB
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:48:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04390
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:48:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3UD-0000DA-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:46:13 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3UC-0000CO-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:46:13 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id E5B78ABB5; Thu, 19 Jun 2003 10:54:10 -0700 (PDT)
To: Michael Thomas <mat@cisco.com>
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>
	<20030618130528.400b1f39.moore@cs.utk.edu>
	<kj65n3mgdt.fsf@romeo.rtfm.com>
	<20030618134424.410d29d1.moore@cs.utk.edu>
	<kj1xxrmfln.fsf@romeo.rtfm.com>
	<20030618140538.103ea88b.moore@cs.utk.edu>
	<kju1ankzkr.fsf@romeo.rtfm.com>
	<16113.54080.993819.863810@thomasm-u1.cisco.com>
	<kjisr2m1sa.fsf@romeo.rtfm.com>
	<16113.61503.713004.490359@thomasm-u1.cisco.com>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 10:54:10 -0700
In-Reply-To: <16113.61503.713004.490359@thomasm-u1.cisco.com>
Message-ID: <kjd6haj6m5.fsf@romeo.rtfm.com>
Lines: 32
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Michael Thomas <mat@cisco.com> writes:

> Eric Rescorla writes:
>  > Michael Thomas <mat@cisco.com> writes:
>  > 
>  > > Eric Rescorla writes:
>  > >  > What applications that people want to run--and the IT managers would
>  > >  > want to enable--are actually inhibited by NAT? It seems to me that
>  > >  > most of the applications inconvenienced by NAT are ones that IT
>  > >  > managers would want to screen off anyway.
>  > > 
>  > > Uh, have you paid no attention to voice? It
>  > > qualifies on both counts. We get complaints from
>  > > customers each and every day... the ones that are
>  > > lucky enough to figure out that NAT is why their
>  > > IP phone doesn't work that is.
>  > 
>  > As I said, these would be screened off by corporate firewalls in most
>  > cases anyway.
> 
> That there are also issues with firewalls is
> entirely beside the point. And firewall traversal
> using a VPN is a trivial and deployed solution to
> the firewall traversal problem.
And you can use similar solutions to traverse NATs, albeit
with slightly similar technology.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 14:07:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06013
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 14:07:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3e1-00044R-Qx
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:56:21 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3Zk-0002ZF-RK
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:51:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04562
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:51:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3XS-0000GI-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:49:34 -0400
Received: from tnt.isi.edu ([128.9.128.128])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3XS-0000GF-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:49:34 -0400
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6p2/8.11.2) with ESMTP id h5JHpsK19896;
	Thu, 19 Jun 2003 10:51:54 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.9.3/8.8.6) id KAA15984;
	Thu, 19 Jun 2003 10:37:48 -0700 (PDT)
Date: Thu, 19 Jun 2003 10:37:48 -0700 (PDT)
Message-Id: <200306191737.KAA15984@gra.isi.edu>
To: moore@cs.utk.edu, ekr@rtfm.com
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



  *> 
  *> So, on the one hand, we have the actual behavior of millions of people.
  *> On the other hand we have Keith Moore's opinion about what they ought
  *> to prefer. I don't have any trouble figuring out which one I believe.
  *> 
  *> -Ekr
  *> 

Erik,

Errr, let's see if I understand your argument.  You advocate boxes that
have the effect of disallowing a large class of services.  We all
understand that such boxes are in fact in heavy use in today's
Internet, so there is a large set of users who cannot use any of the
services from this class.  So, your argument is that you can
demonstrate that users don't want any of these blocked services,
because they aren't using them today.

Huh?

Repeating this argument endlessly and fervently does not make
it any less a contradiction.  Can we move on to something more useful?

Bob Braden



From owner-ietf@ietf.org  Thu Jun 19 14:14:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06567
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 14:14:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3e3-000483-IT
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:56:23 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3ca-0003al-PJ
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:54:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04903
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:54:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3aI-0000L8-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:52:30 -0400
Received: from tomts16.bellnexxia.net ([209.226.175.4] helo=tomts16-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3aI-0000L5-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:52:30 -0400
Received: from yahoo.com ([65.93.185.42]) by tomts16-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030619175451.QWKU26560.tomts16-srv.bellnexxia.net@yahoo.com>
          for <ietf@ietf.org>; Thu, 19 Jun 2003 13:54:51 -0400
Date: Thu, 19 Jun 2003 13:54:50 -0400
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: use of (the term) NAT considered dangerous
From: S Woodside <sbwoodside@yahoo.com>
To: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <1F8E2695-A27F-11D7-A41F-000393414368@yahoo.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

since usually you mean NAPT. Realistically speaking, almost every NAT 
that's out there in the real world is actually a NAPT. In fact I think 
that NAT is so rare that it really should be called NA(!P)T to be 
completely clear that there is no port translation going on.

simon

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Thu Jun 19 14:14:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06565
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 14:14:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3e3-00047c-6n
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:56:23 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3bz-0003Ah-Hh
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:54:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04811
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:54:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3Zh-0000Kb-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:51:53 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3Zg-0000KW-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:51:52 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5JHs6N29927;
        Thu, 19 Jun 2003 13:54:06 -0400 (EDT)
Date: Thu, 19 Jun 2003 13:54:05 -0400
From: Keith Moore <moore@cs.utk.edu>
To: S Woodside <sbwoodside@yahoo.com>
Cc: moore@cs.utk.edu, ietf@ietf.org, dts@senie.com
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619135405.66885658.moore@cs.utk.edu>
In-Reply-To: <DFA73ED0-A27D-11D7-A41F-000393414368@yahoo.com>
References: <20030619060744.391b92e6.moore@cs.utk.edu>
	<DFA73ED0-A27D-11D7-A41F-000393414368@yahoo.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Keith, I don't get this argument. A NAPT is a firewall by your own 
> definition "I believe the primary purpose of firewalls should be to 
> protect the network, not the hosts, from abusive or unauthorized 
> usage." 

only if the policy that the user wants is exactly what the NAPT
provides.  it's unrealistic to assume that most NAPT users do not want
to run any apps that accept externally-originated traffic, ever.  it's
also unrealistic to assume that most threats to the networks are from
outside the network, or that any kind of perimeter security will protect
a network of significant size from attack.



From owner-ietf@ietf.org  Thu Jun 19 14:16:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07132
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 14:16:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3rT-0007IM-N2
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 14:10:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3h2-0004Rc-Su
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:59:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05211
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:59:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3ek-0000Qv-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:57:07 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3ek-0000Qs-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:57:06 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5JHxNN29932;
        Thu, 19 Jun 2003 13:59:23 -0400 (EDT)
Date: Thu, 19 Jun 2003 13:59:23 -0400
From: Keith Moore <moore@cs.utk.edu>
To: EKR <ekr@rtfm.com>
Cc: moore@cs.utk.edu, dts@senie.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619135923.151a663b.moore@cs.utk.edu>
In-Reply-To: <kjhe6mj6nw.fsf@romeo.rtfm.com>
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
	<20030619060744.391b92e6.moore@cs.utk.edu>
	<kj4r2mnp0r.fsf@romeo.rtfm.com>
	<20030619101050.2eb0bd0f.moore@cs.utk.edu>
	<kjznkem8qr.fsf@romeo.rtfm.com>
	<20030619104013.57201da1.moore@cs.utk.edu>
	<kjof0um1we.fsf@romeo.rtfm.com>
	<20030619132147.4eeb4def.moore@cs.utk.edu>
	<kjhe6mj6nw.fsf@romeo.rtfm.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > > Doesn't the fact that there's not enough demand for this product
> > > to make it available suggest anything to you?
> > 
> > does the fact that there was enough demand for the product that it
> > eventually became available suggest anything to you?
>
> Yeah, that there's a subset who cares. They got it. The market is
> working.

the market is dysfunctional.  it doesn't always fail to deliver what is
needed, but it often does. 

> > true, customers don't care about e2e.  they do, however, care about
> > running apps that won't work when e2e is broken.
>
> Apparently not, or they wold switch.

they would switch if they had alternatives available.  but people like
you keep claiming that alternatives aren't needed because the market has
spoken.

> > > So, on the one hand, we have the actual behavior of millions of
> > > people.
> > 
> > no, we have your biased interpretation of that behavior, as observed
> > from a great distance, through a dirty lens.
> 
> Huh? Are you claiming that people don't 
> (1) Buy NATs
> (2) Use them?

nope.  I'm claiming that your explanation of why they don't do something
else is unsupportable.

> I'm not sure why you're accusing me of bias, Keith. Frankly, I hate
> NAT. It makes my life as a protocol designer miserable and I don't use
> it myself. I just don't fool myself that my preferences represent
> those of people at large.

nor do I fool myself about such things.  but I'm capable of seeing how
much NAT impairs the ability of the Internet to support apps, and some
of those apps seem attractive enough that I believe people would eagerly
adopt them - if NATs weren't preventing them from achieving critical
mass.

Keith



From owner-ietf@ietf.org  Thu Jun 19 14:19:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07407
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 14:19:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3ra-0007JU-0c
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 14:10:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3iP-0004kv-0C
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 14:00:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05304
	for <ietf@ietf.org>; Thu, 19 Jun 2003 14:00:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3g7-0000RU-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:58:31 -0400
Received: from 96.136.33.65.cfl.rr.com ([65.33.136.96] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3g6-0000RR-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:58:30 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 19SviI-0007dv-00; Thu, 19 Jun 2003 05:28:14 -0400
Date: Thu, 19 Jun 2003 05:28:13 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
cc: Daniel Senie <dts@senie.com>, <ietf@ietf.org>
Subject: RE: NATs are NOT Firewalls 
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F506722B@server2000.arneill-py.sacramento.ca.us>
Message-ID: <Pine.LNX.4.44.0306190523520.29319-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 19 Jun 2003, Michel Py wrote:

> Daniel,
>
> I agree with the rest of your post, however
>
> > Since NAPT uses stateful inspection to operate,

when referring to NAPT, we are talking about rinetd, right?  you can run
that on a linux box with two network interfaces (ethernet, ppp, token
ring, serial, whatever) to distribute the network service load around your lan
(or across the internet, for that matter).  combine that with snort or so,
and iptables, and you have a firewall, do you not?


>
> I think I don't agree with this. I would say that NAPT is a stateful
> process but not that it uses inspection. By "inspection" I understand a
> more intelligent process that decapsulates packets and looks for "bad"
> things inside them, which is a separate function.
>
> In other words, there is a difference between 'stateful' and 'stateful
> inspection'. 'Stateful' is a feature of both NAPT boxes and firewalls;
> 'stateful inspection' is a feature of more sophisticated firewalls only;
> if you happen to find a NAPT box that does stateful inspection (the $50
> ones don't) it could indeed be called a firewall.
>
> Michel.
>
>
>

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




From owner-ietf@ietf.org  Thu Jun 19 14:23:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07793
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 14:23:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3tZ-0007bJ-Db
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 14:12:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3no-0006LL-3i
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 14:06:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05945
	for <ietf@ietf.org>; Thu, 19 Jun 2003 14:06:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3lW-0000d0-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:04:06 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3lV-0000bf-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:04:05 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 767C9ABB5; Thu, 19 Jun 2003 11:12:03 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: dts@senie.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
	<20030619060744.391b92e6.moore@cs.utk.edu>
	<kj4r2mnp0r.fsf@romeo.rtfm.com>
	<20030619101050.2eb0bd0f.moore@cs.utk.edu>
	<kjznkem8qr.fsf@romeo.rtfm.com>
	<20030619104013.57201da1.moore@cs.utk.edu>
	<kjof0um1we.fsf@romeo.rtfm.com>
	<20030619132147.4eeb4def.moore@cs.utk.edu>
	<kjhe6mj6nw.fsf@romeo.rtfm.com>
	<20030619135923.151a663b.moore@cs.utk.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 11:12:03 -0700
In-Reply-To: <20030619135923.151a663b.moore@cs.utk.edu>
Message-ID: <kju1amhr7w.fsf@romeo.rtfm.com>
Lines: 21
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Keith Moore <moore@cs.utk.edu> writes:
> > Yeah, that there's a subset who cares. They got it. The market is
> > working.
> 
> the market is dysfunctional.  it doesn't always fail to deliver what is
> needed, but it often does. 
That's your claim. I don't buy it.

> > Apparently not, or they wold switch.
> 
> they would switch if they had alternatives available.  but people like
> you keep claiming that alternatives aren't needed because the market has
> spoken.
Nonsense. I'd love to see an alternative. Obviously, NATS have costs
and a solution that reduced those costs would be better. What alternative,
exactly, are you offering?

-Ekr
-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 14:56:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09399
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 14:56:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T45K-0002qZ-Cl
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 14:24:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T410-0001OK-9w
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 14:20:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07439
	for <ietf@ietf.org>; Thu, 19 Jun 2003 14:20:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3yh-0000ys-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:17:43 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3yg-0000ym-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:17:42 -0400
Received: from isi.edu (nib.isi.edu [128.9.160.144])
	by boreas.isi.edu (8.11.6p2/8.11.2) with ESMTP id h5JIJB105831;
	Thu, 19 Jun 2003 11:19:11 -0700 (PDT)
Message-ID: <3EF1FE66.2030400@isi.edu>
Date: Thu, 19 Jun 2003 11:18:14 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: vkompella@timetra.com
CC: Melinda Shore <mshore@cisco.com>, Scott W Brim <swb@employees.org>,
        ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
References: <FNEFIPCNJKDDONJGBCNECENKEBAA.vkompella@timetra.com>
In-Reply-To: <FNEFIPCNJKDDONJGBCNECENKEBAA.vkompella@timetra.com>
X-Enigmail-Version: 0.74.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Vach Kompella wrote:
> Melinda,
> 
> 
>>As a process kind of thing, I'm also concerned about the
>>growth of the "temporary" sub-IP area, so I think there are
>>issues here with both the work itself and in how the IETF
>>goes about taking on and structuring its work.
> 
> 
> And proposals have been made to dismantle the SUBIP area and place the remaining
> WGs in the most appropriate areas (some of them are pretty much done with their
> chartered work).  The chartering of L2 and L3VPN WGs gives a little more focus,
> and limits the solution space.
> 
> It's not the creation of the temporary SUBIP area that caused the growth of the
> WGs.  It's the natural progression of the opportunities that MPLS provided that
> led to the application WGs such as PWE3, PPVPN, etc.

Not all of PPVPN is based on MPLS. Some of us are doing real IP VPNs, 
using IPsec, etc.

Joe




From owner-ietf@ietf.org  Thu Jun 19 15:02:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10046
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:02:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T4W1-0004ak-Gw
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 14:52:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T484-00035P-0A
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 14:27:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08153
	for <ietf@ietf.org>; Thu, 19 Jun 2003 14:27:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T45m-0001AJ-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:25:02 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T45l-0001A3-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:25:01 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 59F91ABB5; Thu, 19 Jun 2003 11:32:59 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: dts@senie.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
	<20030619060744.391b92e6.moore@cs.utk.edu>
	<kj4r2mnp0r.fsf@romeo.rtfm.com>
	<20030619101050.2eb0bd0f.moore@cs.utk.edu>
	<kjznkem8qr.fsf@romeo.rtfm.com>
	<20030619104013.57201da1.moore@cs.utk.edu>
	<kjof0um1we.fsf@romeo.rtfm.com>
	<20030619132147.4eeb4def.moore@cs.utk.edu>
	<kjhe6mj6nw.fsf@romeo.rtfm.com>
	<20030619135923.151a663b.moore@cs.utk.edu>
	<kju1amhr7w.fsf@romeo.rtfm.com>
	<20030619142313.724b5ceb.moore@cs.utk.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 11:32:59 -0700
In-Reply-To: <20030619142313.724b5ceb.moore@cs.utk.edu>
Message-ID: <kjbrwtj4tg.fsf@romeo.rtfm.com>
Lines: 36
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> > > they would switch if they had alternatives available.  but people
> > > like you keep claiming that alternatives aren't needed because the
> > > market has spoken.
> >
> > Nonsense. I'd love to see an alternative. Obviously, NATS have costs
> > and a solution that reduced those costs would be better. What
> > alternative, exactly, are you offering?
> 
> 6to4 is one.  and before Christian wrote his shipworm/teredo proposal I
> had my own proposal to tunnel v6 over v4+NAT.   there's also my draft
> describing my best effort to produce a mechanism that would allow v4
> apps to tolerate NATs and still have general connectivity.  (I tried,
> but it turns out that it's far easier to support 6to4 and/or teredo)
> 
> so it's not like I haven't actually been working on solving the problem.
I didn't say you haven't been. So, my question at this point is:

(1) If these solutions aren't available, why not?
(2) If they are available and people don't want them, why not?

Rather than complaining about NAT, it seems like we would be better
served assuming that people have reasons for making the choices
they have and trying to accomodate those.

Anyway, I've said all I have to say about this topic. I'll
let other people on this thread have the last word if they 
like.

-Ekr


-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 15:02:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10049
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:02:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T4W1-0004aq-Pq
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 14:52:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T4A3-00036K-3H
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 14:29:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08256
	for <ietf@ietf.org>; Thu, 19 Jun 2003 14:29:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T47l-0001BX-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:27:05 -0400
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T47k-0001BU-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:27:04 -0400
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0.6)
  with ESMTP-TLS id 242354; Thu, 19 Jun 2003 13:29:02 -0500
Message-ID: <3EF20103.4040009@ehsco.com>
Date: Thu, 19 Jun 2003 13:29:23 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: EKR <ekr@rtfm.com>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."	<kju1amod9r.fsf@romeo.rtfm.com>	<200306181937.AIN64606@mira-sjc5-c.cisco.com>	<kjbrwvkmu7.fsf@romeo.rtfm.com>	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>	<kjptlak7tg.fsf@romeo.rtfm.com>	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>	<kju1amod9r.fsf@romeo.rtfm.com>	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>	<20030619060744.391b92e6.moore@cs.utk.edu>	<kj4r2mnp0r.fsf@romeo.rtfm.com>	<20030619101050.2eb0bd0f.moore@cs.utk.edu>	<kjznkem8qr.fsf@romeo.rtfm.com>	<20030619104013.57201da1.moore@cs.utk.edu>	<kjof0um1we.fsf@romeo.rtfm.com>	<20030619132147.4eeb4def.moore@cs.utk.edu>	<kjhe6mj6nw.fsf@romeo.rtfm.com> <20030619135923.151a663b.moore@cs.utk.edu>
In-Reply-To: <20030619135923.151a663b.moore@cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


on 6/19/2003 12:59 PM Keith Moore wrote:

>>Yeah, that there's a subset who cares. They got it. The market is
>>working.
> 
> the market is dysfunctional.  it doesn't always fail to deliver what is
> needed, but it often does. 

I wouldn't say that this market is dysfunctional, more that markets aren't
always self-deterministic (regulations and laws are another form of this),
and that the market is as functional as can be expected considering the
restrictions that folks usually work under. Folks can't always get a range
of addresses from their provider, or can't get a routable block of private
addresses, or don't want to depend on a single provider, or whatever. I
mean, I certainly wouldn't be using a NAT on my home network if I had kept
the multiple Class C blocks I used to have, so really the problem is that
the market isn't offering the full range of appropriate choices. People
have chosen something that mostly works (or have been lied to), rather
than chosing the best option (which is not available).

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




From owner-ietf@ietf.org  Thu Jun 19 15:05:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10703
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:05:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T4bk-0005un-N2
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 14:58:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T4Vo-0004aD-Rf
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 14:51:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09215
	for <ietf@ietf.org>; Thu, 19 Jun 2003 14:51:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4TW-0001P9-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:49:34 -0400
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4TW-0001P6-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:49:34 -0400
Received: from [192.35.232.241] (helo=think.thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:DES-CBC3-SHA:168)  (Exim 3.35 #1 (Debian))
	id 19T4Vb-00020V-00; Thu, 19 Jun 2003 14:51:43 -0400
Received: from tytso authenticated as tytso by think.thunk.org with local   (Exim 3.35 #1 (Debian))
	id 19T4VV-0000G1-00; Thu, 19 Jun 2003 14:51:37 -0400
Date: Thu, 19 Jun 2003 14:51:37 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Bob Braden <braden@ISI.EDU>, moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Message-ID: <20030619185137.GA907@think>
References: <200306191737.KAA15984@gra.isi.edu> <kjy8zyhrb8.fsf@romeo.rtfm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <kjy8zyhrb8.fsf@romeo.rtfm.com>
User-Agent: Mutt/1.5.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, Jun 19, 2003 at 11:10:03AM -0700, Eric Rescorla wrote:
> Users aren't physically handcuffed to their Internet connections.
> They have choices as to who to purchase connectivity from. Those
> users, if they chose, could purchase connectivity with static IP
> addresses and no NAT. They by and large don't do so. Therefore, it's
> reasonable to conclude that they don't in fact want them. Or, to put
> it more precisely, that the marginal disutility of getting rid of NAT
> exceeds the marginal utility of these new services.

And to make things even more specific, in the suburb of Boston where I
live, I have a couple of different options:

$230/month	DSL.net 400kbps SDSL, with 30 IP addresses (/28)
$ 99/month	Speakeasy.net, 768kbps down, 384kbps up, with 2 
			static addresses
$ 44/month	Comcast 640kbps down, 256 kbps up, with dynamic addresses

So 30 static IP addresses, with a slower service, is over *five* times
more expensive, and over twice as expensive as faster service with
only 2 static IP addresses.  

As much as I hate NAT, from an aesthetic perspective, using two static
IP addresses and a NAT box was the expedient solution.  We could I
suppose blame the ISP's for their charging policies, but these
economic pressures are going to drive people in certain directions,
and as Ekr as pointed out, saying that people are either misinformed
or non-rationale isn't going to help matters.

(Put another way, sure, Voice over IP would be nice.  But if I have to
pay 2x or 5x a month to an ISP in order to not have a NAT box so I can
use VoIP, wouldn't it be much more rational to stick with a wired POTS
line?)

I'm not defending the current system; I certainly wish I could have a
/22 all to myself, and not have to play NAT games.  (And I'm kicking
myself for not simply registering one back when they were essentially
free for the asking.)  But the reality is that NAT boxes are here to
stay, and we have lost that battle for IPv4.  It would be nice not to
lose that battle for IPv6, but I suspect the jury is still out on that
point; and burying our heads in the sand about why people chose NAT's
is not going to help us assure a NAT-free world for IPv6.

						- Ted



From owner-ietf@ietf.org  Thu Jun 19 15:07:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11259
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:07:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T4fU-0000XU-0d
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 15:01:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T4d1-00061Z-RL
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 14:59:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09856
	for <ietf@ietf.org>; Thu, 19 Jun 2003 14:59:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4aj-0001Y1-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:57:01 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4aj-0001Xy-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:57:01 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5JIxKN00132;
        Thu, 19 Jun 2003 14:59:20 -0400 (EDT)
Date: Thu, 19 Jun 2003 14:59:19 -0400
From: Keith Moore <moore@cs.utk.edu>
To: S Woodside <sbwoodside@yahoo.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619145919.0389ffb5.moore@cs.utk.edu>
In-Reply-To: <9D3A6FC0-A282-11D7-A41F-000393414368@yahoo.com>
References: <20030619135405.66885658.moore@cs.utk.edu>
	<9D3A6FC0-A282-11D7-A41F-000393414368@yahoo.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Yes, I agree, that NAPTs have tons of side effects, and that's a bad 
> thing. But, for the average home user on DSL, they have purchased 
> millions upon millions of these things. It's a tiny little network and
> they have full control over all the hosts. So for them, the NAPT 
> firewalling function is very useful. 

the firewall without the NAT would be even more useful.



From owner-ietf@ietf.org  Thu Jun 19 15:09:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11734
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:09:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T4gE-0001eC-0c
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 15:02:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T4dt-0007LB-My
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 15:00:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09927
	for <ietf@ietf.org>; Thu, 19 Jun 2003 15:00:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4bb-0001Yh-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:57:55 -0400
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 19T4bZ-0001YG-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:57:53 -0400
Received: from cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 19 Jun 2003 12:02:25 -0800
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h5JIxeIX013908;
	Thu, 19 Jun 2003 11:59:41 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AFG14806;
	Thu, 19 Jun 2003 11:59:40 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA10179; Thu, 19 Jun 2003 11:59:39 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16114.2075.793143.737837@thomasm-u1.cisco.com>
Date: Thu, 19 Jun 2003 11:59:39 -0700 (PDT)
To: EKR <ekr@rtfm.com>
Cc: Bob Braden <braden@ISI.EDU>, moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
In-Reply-To: <kjy8zyhrb8.fsf@romeo.rtfm.com>
References: <200306191737.KAA15984@gra.isi.edu>
	<kjy8zyhrb8.fsf@romeo.rtfm.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric Rescorla writes:
 > P.S. And btw, I'm not advocating NAT. What I'm advocating is that
 > we stop behaving as if we think that anyone who uses NAT is obviously
 > an idiot.

I don't think that I've seen anybody say that.
Most people who use NAT have no clue one way or
the other about NAT any more than they possess
clue about, oh say, 8086 instruction sets on
modern day processors. They aren't "idiots"
because they aren't claiming any (deep) knowledge
about the subject. They're merely ignorant and
just trying to get by with limited knowledge.

However, it's quite a leap to go from general
ignorance about the inner workings of computers
and networks to divining user's True Intents based
on their purchasing habits. I doubt that many
people go out with the intent of getting cancer
when they buy a pack of ciggies, but that is often
the end result. And people today have far more
clue about smoking than they do about NAT's. 
People use NAT's for all kinds of perfectly
good reasons (I agree with Noel's analysis too,
btw), but it doesn't mean that cancer isn't an end
result there too. Voice is a great example of the
malignant chickens coming home to roost.

So I just don't see what the value is in
introducing the Voice of the Masses as indicative
of anything one way or the other about NAT. They
have requirements, and NAT's provide solutions for
some of those requirements, in much the same way
that smoking provides teenagers with a solution to
the requirement to be cool. Our job, however, is
to look at the *all* of the requirements and see
if they are best served with a given set of
technology. That's because we're paid to
understand this stuff and look out for the long
term health of the net. Which isn't to say that
we're infallible or incapable of indulging in
religious fervor, but we're at least semi informed
unlike the great unwashed masses.

Thus, I think it's *far* more productive to
actually limit the arguments to not whether NAT is
good or bad, but what requirements are we not
fulfilling which is leading people to NAT's as an
acceptible alternative (cf Noel's post). Some
people have obviously throw in the towel and would
like to have NAT's/ALG's to replace or augment the
end to end principle. Others aren't ready to give
up on end to end. I think it's premature to
declare the latter dead though. Some of the
requirements have simply not been hashed out to
any great degree. Fred's draft on operational
renumbering is a great example of something for
which there is more handwaving on our part than
actual experience. That doesn't mean that it's a
dead end though. All it means that it's something
that still needs to be dealt with. After all of
that is done can we actually have an intelligent
argument about what the right path is. This is,
IMO, quite literally a race.

	   Mike



From owner-ietf@ietf.org  Thu Jun 19 15:12:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07800
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 14:23:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3rc-0007Ol-6E
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 14:10:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3lt-0005mK-MI
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 14:04:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05686
	for <ietf@ietf.org>; Thu, 19 Jun 2003 14:04:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3jb-0000Yk-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:02:07 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3ja-0000XD-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:02:07 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id C64C6ABB5; Thu, 19 Jun 2003 11:10:03 -0700 (PDT)
To: Bob Braden <braden@ISI.EDU>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <200306191737.KAA15984@gra.isi.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 11:10:03 -0700
In-Reply-To: <200306191737.KAA15984@gra.isi.edu>
Message-ID: <kjy8zyhrb8.fsf@romeo.rtfm.com>
Lines: 52
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Bob Braden <braden@ISI.EDU> writes:

>   *> 
>   *> So, on the one hand, we have the actual behavior of millions of people.
>   *> On the other hand we have Keith Moore's opinion about what they ought
>   *> to prefer. I don't have any trouble figuring out which one I believe.
>   *> 
>   *> -Ekr
>   *> 
> 
> Erik,
Eric.

> Errr, let's see if I understand your argument.  You advocate boxes that
> have the effect of disallowing a large class of services.  We all
> understand that such boxes are in fact in heavy use in today's
> Internet, so there is a large set of users who cannot use any of the
> services from this class.  So, your argument is that you can
> demonstrate that users don't want any of these blocked services,
> because they aren't using them today.
>
> Huh?
> 
> Repeating this argument endlessly and fervently does not make
> it any less a contradiction.  Can we move on to something more useful?
Instead, maybe we should start by you taking the time to understand 
the argument properly.

Users aren't physically handcuffed to their Internet connections.
They have choices as to who to purchase connectivity from. Those
users, if they chose, could purchase connectivity with static IP
addresses and no NAT. They by and large don't do so. Therefore, it's
reasonable to conclude that they don't in fact want them. Or, to put
it more precisely, that the marginal disutility of getting rid of NAT
exceeds the marginal utility of these new services.

Now, the situation is a little different when we're talking about
people who are on corporate networks, but I view the corporation,
not the users, as the customer here and so the same logic applies.
If the corporation wished the users to have those services enough
to disable NAT, then they would do so.

-Ekr

P.S. And btw, I'm not advocating NAT. What I'm advocating is that
we stop behaving as if we think that anyone who uses NAT is obviously
an idiot.

-- 
[Eric Rescorla                                   ekr@rtfm.com]
           Web Log: http://www.rtfm.com/movabletype




From owner-ietf@ietf.org  Thu Jun 19 15:18:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12918
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:18:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T4pA-0000hf-Aa
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 15:11:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T4ox-0000TO-RJ
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 15:11:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12138
	for <ietf@ietf.org>; Thu, 19 Jun 2003 15:11:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4mf-0001xg-00
	for ietf@ietf.org; Thu, 19 Jun 2003 15:09:21 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4mf-0001xd-00
	for ietf@ietf.org; Thu, 19 Jun 2003 15:09:21 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5JJBcN00162;
        Thu, 19 Jun 2003 15:11:39 -0400 (EDT)
Date: Thu, 19 Jun 2003 15:11:38 -0400
From: Keith Moore <moore@cs.utk.edu>
To: EKR <ekr@rtfm.com>
Cc: moore@cs.utk.edu, dts@senie.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619151138.4e345aa6.moore@cs.utk.edu>
In-Reply-To: <kjbrwtj4tg.fsf@romeo.rtfm.com>
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
	<20030619060744.391b92e6.moore@cs.utk.edu>
	<kj4r2mnp0r.fsf@romeo.rtfm.com>
	<20030619101050.2eb0bd0f.moore@cs.utk.edu>
	<kjznkem8qr.fsf@romeo.rtfm.com>
	<20030619104013.57201da1.moore@cs.utk.edu>
	<kjof0um1we.fsf@romeo.rtfm.com>
	<20030619132147.4eeb4def.moore@cs.utk.edu>
	<kjhe6mj6nw.fsf@romeo.rtfm.com>
	<20030619135923.151a663b.moore@cs.utk.edu>
	<kju1amhr7w.fsf@romeo.rtfm.com>
	<20030619142313.724b5ceb.moore@cs.utk.edu>
	<kjbrwtj4tg.fsf@romeo.rtfm.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > so it's not like I haven't actually been working on solving the
> > problem.
>
> I didn't say you haven't been. So, my question at this point is:
> 
> (1) If these solutions aren't available, why not?
> (2) If they are available and people don't want them, why not?

it may be too early, and lots of people are still misinformed.

> Rather than complaining about NAT, it seems like we would be better
> served assuming that people have reasons for making the choices
> they have and trying to accomodate those.

the two are not mutually exclusive.   and though I do assume that people
have reasons for making they choices they make, why should I assume
either that the people have much of a choice, or that the reasons that
the people give are valid, in the presence of ample evidence to the
contrary? 



From owner-ietf@ietf.org  Thu Jun 19 15:30:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14004
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:30:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T50x-0004Qj-MS
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 15:24:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T4xx-0003vB-Qd
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 15:21:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13176
	for <ietf@ietf.org>; Thu, 19 Jun 2003 15:20:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4vf-00026U-00
	for ietf@ietf.org; Thu, 19 Jun 2003 15:18:39 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T4vf-000263-00
	for ietf@ietf.org; Thu, 19 Jun 2003 15:18:39 -0400
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h5JJKSaZ012462;
	Thu, 19 Jun 2003 12:20:28 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AIO99844;
	Thu, 19 Jun 2003 12:20:27 -0700 (PDT)
Message-Id: <200306191920.AIO99844@mira-sjc5-c.cisco.com>
To: EKR <ekr@rtfm.com>
cc: ietf@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Message from ekr@rtfm.com
   of "19 Jun 2003 10:16:00 PDT." <kjfzm6m1in.fsf@romeo.rtfm.com> 
Date: Thu, 19 Jun 2003 15:20:27 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

> I'm not sure what you mean by routing above. Are you suggesting there's
> some negative externality in that NAT makes the routing infrastructure
> more complicated? If so, what is it?

If you're multihomed and your route changes, your address
changes.  (Yes, this happens).

I am profoundly weirded out by reading an IAB member argue
that something that's got broad market acceptance is
tautologically okay.  I agree that there's a real problem
here that NAT is trying to solve, but I certainly wouldn't
treat it as a given that NAT is the best, or even a good,
solution.  

Melinda



From owner-ietf@ietf.org  Thu Jun 19 15:32:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14239
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:32:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T563-0006IG-QD
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 15:29:23 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T54a-0005TB-FI
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 15:27:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13757
	for <ietf@ietf.org>; Thu, 19 Jun 2003 15:27:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T52I-0002Fh-00
	for ietf@ietf.org; Thu, 19 Jun 2003 15:25:30 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T52H-0002EB-00
	for ietf@ietf.org; Thu, 19 Jun 2003 15:25:29 -0400
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h5JJRIaZ016592;
	Thu, 19 Jun 2003 12:27:18 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AIP00803;
	Thu, 19 Jun 2003 12:27:16 -0700 (PDT)
Message-Id: <200306191927.AIP00803@mira-sjc5-c.cisco.com>
To: S Woodside <sbwoodside@yahoo.com>
cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org,
        Daniel Senie <dts@senie.com>
From: Melinda Shore <mshore@cisco.com>
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Message from sbwoodside@yahoo.com
   of "Thu, 19 Jun 2003 13:45:53 EDT." <DFA73ED0-A27D-11D7-A41F-000393414368@yahoo.com> 
Date: Thu, 19 Jun 2003 15:27:16 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

> Keith, I don't get this argument. A NAPT is a firewall by your own 
> definition "I believe the primary purpose of firewalls should be to 
> protect the network, not the hosts, from abusive or unauthorized 
> usage." It's implementing a very simple policy, protect me from the 
> outside world.

NAT has problematically constrained policy capabilities.

Melinda



From owner-ietf@ietf.org  Thu Jun 19 15:42:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09398
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 14:56:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T45J-0002q9-Vy
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 14:24:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T40r-0001Co-Kc
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 14:19:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07433
	for <ietf@ietf.org>; Thu, 19 Jun 2003 14:19:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3yZ-0000yd-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:17:35 -0400
Received: from tomts13.bellnexxia.net ([209.226.175.34] helo=tomts13-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3yY-0000yX-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:17:34 -0400
Received: from yahoo.com ([65.93.185.42]) by tomts13-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030619181953.OICZ29645.tomts13-srv.bellnexxia.net@yahoo.com>;
          Thu, 19 Jun 2003 14:19:53 -0400
Date: Thu, 19 Jun 2003 14:19:49 -0400
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Keith Moore <moore@cs.utk.edu>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <20030619135405.66885658.moore@cs.utk.edu>
Message-Id: <9D3A6FC0-A282-11D7-A41F-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Thursday, June 19, 2003, at 01:54  PM, Keith Moore wrote:

>> Keith, I don't get this argument. A NAPT is a firewall by your own
>> definition "I believe the primary purpose of firewalls should be to
>> protect the network, not the hosts, from abusive or unauthorized
>> usage."
>
> only if the policy that the user wants is exactly what the NAPT
> provides.  it's unrealistic to assume that most NAPT users do not want
> to run any apps that accept externally-originated traffic, ever.  it's
> also unrealistic to assume that most threats to the networks are from
> outside the network, or that any kind of perimeter security will 
> protect
> a network of significant size from attack.

Yes, I agree, that NAPTs have tons of side effects, and that's a bad 
thing. But, for the average home user on DSL, they have purchased 
millions upon millions of these things. It's a tiny little network and 
they have full control over all the hosts. So for them, the NAPT 
firewalling function is very useful. (and the network vs. hosts 
distinction doesn't make sense, does it?)

simon




From owner-ietf@ietf.org  Thu Jun 19 15:52:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10040
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 15:02:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T4V8-0004TM-0J
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 14:51:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T44A-0002EP-I2
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 14:23:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07771
	for <ietf@ietf.org>; Thu, 19 Jun 2003 14:23:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T41s-00014Z-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:21:00 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T41r-00014W-00
	for ietf@ietf.org; Thu, 19 Jun 2003 14:21:00 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5JINDN29968;
        Thu, 19 Jun 2003 14:23:13 -0400 (EDT)
Date: Thu, 19 Jun 2003 14:23:13 -0400
From: Keith Moore <moore@cs.utk.edu>
To: EKR <ekr@rtfm.com>
Cc: moore@cs.utk.edu, dts@senie.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619142313.724b5ceb.moore@cs.utk.edu>
In-Reply-To: <kju1amhr7w.fsf@romeo.rtfm.com>
References: <Your message of "Wed, 18 Jun 2003 22:19:12 PDT."
	<kju1amod9r.fsf@romeo.rtfm.com>
	<200306181937.AIN64606@mira-sjc5-c.cisco.com>
	<kjbrwvkmu7.fsf@romeo.rtfm.com>
	<200306190344.h5J3iqPZ030084@turing-police.cc.vt.edu>
	<kjptlak7tg.fsf@romeo.rtfm.com>
	<200306190456.h5J4ugPZ032549@turing-police.cc.vt.edu>
	<kju1amod9r.fsf@romeo.rtfm.com>
	<5.2.1.1.2.20030619033719.0268e9c0@mail.amaranth.net>
	<20030619060744.391b92e6.moore@cs.utk.edu>
	<kj4r2mnp0r.fsf@romeo.rtfm.com>
	<20030619101050.2eb0bd0f.moore@cs.utk.edu>
	<kjznkem8qr.fsf@romeo.rtfm.com>
	<20030619104013.57201da1.moore@cs.utk.edu>
	<kjof0um1we.fsf@romeo.rtfm.com>
	<20030619132147.4eeb4def.moore@cs.utk.edu>
	<kjhe6mj6nw.fsf@romeo.rtfm.com>
	<20030619135923.151a663b.moore@cs.utk.edu>
	<kju1amhr7w.fsf@romeo.rtfm.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > they would switch if they had alternatives available.  but people
> > like you keep claiming that alternatives aren't needed because the
> > market has spoken.
>
> Nonsense. I'd love to see an alternative. Obviously, NATS have costs
> and a solution that reduced those costs would be better. What
> alternative, exactly, are you offering?

6to4 is one.  and before Christian wrote his shipworm/teredo proposal I
had my own proposal to tunnel v6 over v4+NAT.   there's also my draft
describing my best effort to produce a mechanism that would allow v4
apps to tolerate NATs and still have general connectivity.  (I tried,
but it turns out that it's far easier to support 6to4 and/or teredo)

so it's not like I haven't actually been working on solving the problem.

Keith




From owner-ietf@ietf.org  Thu Jun 19 15:52:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06570
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 14:14:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T3e2-00046d-MQ
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 13:56:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T3an-0002xv-4e
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 13:53:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04725
	for <ietf@ietf.org>; Thu, 19 Jun 2003 13:52:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3YV-0000J8-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:50:39 -0400
Received: from tomts8.bellnexxia.net ([209.226.175.52] helo=tomts8-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T3YU-0000Iz-00
	for ietf@ietf.org; Thu, 19 Jun 2003 13:50:38 -0400
Received: from yahoo.com ([65.93.185.42]) by tomts8-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030619175257.DTXZ16740.tomts8-srv.bellnexxia.net@yahoo.com>;
          Thu, 19 Jun 2003 13:52:57 -0400
Date: Thu, 19 Jun 2003 13:52:57 -0400
Subject: Re: NATs are NOT Firewalls 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Valdis.Kletnieks@vt.edu
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <200306190534.h5J5YTPZ001409@turing-police.cc.vt.edu>
Message-Id: <DC490D05-A27E-11D7-A41F-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Thursday, June 19, 2003, at 01:34  AM, Valdis.Kletnieks@vt.edu wrote:

>> Is this just security through obscurity, or something better?
>
> Security through obscurity.  See Bellovin's paper on enumerating 
> through a NAT.
>
> http://www.research.att.com/~smb/papers/fnat.pdf

This paper has nothing to do with security. it's just counting hosts.

simon

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Thu Jun 19 16:40:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17187
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 16:40:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T67O-0000ey-Uq
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 16:34:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T62I-0008S3-GA
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 16:29:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16832
	for <ietf@ietf.org>; Thu, 19 Jun 2003 16:29:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T600-0002yQ-00
	for ietf@ietf.org; Thu, 19 Jun 2003 16:27:12 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T5zz-0002xz-00
	for ietf@ietf.org; Thu, 19 Jun 2003 16:27:11 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 4DA85ABB5; Thu, 19 Jun 2003 13:35:08 -0700 (PDT)
To: Melinda Shore <mshore@cisco.com>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <200306191920.AIO99844@mira-sjc5-c.cisco.com>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 13:35:08 -0700
In-Reply-To: <200306191920.AIO99844@mira-sjc5-c.cisco.com>
Message-ID: <kju1alhklf.fsf@romeo.rtfm.com>
Lines: 72
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

I said I was done with this discussion, but I think Melinda
deserves a response here.

Melinda Shore <mshore@cisco.com> writes:

> > I'm not sure what you mean by routing above. Are you suggesting there's
> > some negative externality in that NAT makes the routing infrastructure
> > more complicated? If so, what is it?
> 
> If you're multihomed and your route changes, your address
> changes.  (Yes, this happens).
Agreed.

> I am profoundly weirded out by reading an IAB member argue
> that something that's got broad market acceptance is
> tautologically okay.  I agree that there's a real problem
> here that NAT is trying to solve, but I certainly wouldn't
> treat it as a given that NAT is the best, or even a good,
> solution.  
I can understand how this would bother you, and I think
part of the problem is that I haven't been writing as clearly
as I could have. A series of e-mail replies isn't a good
way to elucidate your position.

Here's what I mean to be arguing:

(1) There are some set of problems that users have or
    believe they have.

(2) NAT solves at least some of those problems, at some
    cost (say Cn), both financial and operational and
    that solution has benefit Bn.

(3) The fact that a large number of people have chosen
    to use NAT is a strong argument that B>C. (Here's
    where the invocation of revealed preference comes in).

(4) It may well be the case that some other solution S
    would have some other costs Cs and benefit Bs such
    that (Bs - Cs) > (Bn - Cn). It may be that S doesn't
    exist yet, in which case it would be good for us
    to design and build it.

(5) It's also possible that at some time in the future
    Cn will exceed Bn, in which case I would expect people
    to stop using NAT and (probably) demand something else.

(6) The argument that I thought I heard people (though not
    you) making is that Cn > Bn. I don't think that this
    is likely to be the case. In that sense, I think
    NAT is OK. I think that if we believe this, it will likely
    lead to us designing a long series of S'es that are
    inferior to NAT (in the sense that users do not
    prefer them because (Bs - Cs) < (Bn - Cn). That's a waste
    of time.

Does this seem like a weird position for an IAB member to take?
I don't think so. 

There certainly are cases where it's appropriate for the IETF to say
that something users want to do is not OK. Most of those cases are
ones where their behavior has negative external effects on everyone
else. I don't think a strong argument has been made that this is
such a case.


-Ekr
--
[Eric Rescorla                                   ekr@rtfm.com]
           Web Log: http://www.rtfm.com/movabletype





From owner-ietf@ietf.org  Thu Jun 19 17:03:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18273
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 17:03:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T6Qq-0003s3-20
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 16:54:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T6QY-0003k0-3K
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 16:54:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17828
	for <ietf@ietf.org>; Thu, 19 Jun 2003 16:54:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T6OF-0003Bg-00
	for ietf@ietf.org; Thu, 19 Jun 2003 16:52:16 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19T6OF-0003BU-00
	for ietf@ietf.org; Thu, 19 Jun 2003 16:52:15 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003061917020426407
 for <ietf@ietf.org>; Thu, 19 Jun 2003 17:02:04 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 19 Jun 2003 16:51:39 -0400
Message-ID: <3EF2225B.10201@centive.com>
Date: Thu, 19 Jun 2003 16:51:39 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
References: <200306191920.AIO99844@mira-sjc5-c.cisco.com> <kju1alhklf.fsf@romeo.rtfm.com>
In-Reply-To: <kju1alhklf.fsf@romeo.rtfm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jun 2003 20:51:39.0600 (UTC) FILETIME=[94D48D00:01C336A4]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric Rescorla wrote:

>(2) NAT solves at least some of those problems, at some
>    cost (say Cn), both financial and operational and
>    that solution has benefit Bn.
>
>(5) It's also possible that at some time in the future
>    Cn will exceed Bn, in which case I would expect people
>    to stop using NAT and (probably) demand something else.
>  
>
I think this is the point of contention: Keith asserts that Cn exceeds 
Bn if you consider long-term costs; your invocation of revealed 
preferences is based on the market, which tends to be short-term.  Cn<Bn 
if all you run is client-server apps; but NAT locks you in to using just 
those apps, which means that Cn has a hidden component that isn't 
visible to most consumers.

-- 
/=============================================================\
|John Stracke      |jstracke@centive.com                      |
|Principal Engineer|http://www.centive.com                    |
|Centive           |My opinions are my own.                   |
|=============================================================|
|Beware of wizards, for you are crunchy and good with ketchup.|
\=============================================================/





From owner-ietf@ietf.org  Thu Jun 19 17:06:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18444
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 17:06:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T6Xc-0004ku-1t
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 17:01:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T6Wn-0004cz-56
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 17:01:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18186
	for <ietf@ietf.org>; Thu, 19 Jun 2003 17:01:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T6UU-0003GR-00
	for ietf@ietf.org; Thu, 19 Jun 2003 16:58:42 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T6UU-0003GO-00
	for ietf@ietf.org; Thu, 19 Jun 2003 16:58:42 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5JL0uN00312;
        Thu, 19 Jun 2003 17:00:57 -0400 (EDT)
Date: Thu, 19 Jun 2003 17:00:56 -0400
From: Keith Moore <moore@cs.utk.edu>
To: EKR <ekr@rtfm.com>
Cc: moore@cs.utk.edu, mshore@cisco.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030619170056.05849bfc.moore@cs.utk.edu>
In-Reply-To: <kju1alhklf.fsf@romeo.rtfm.com>
References: <200306191920.AIO99844@mira-sjc5-c.cisco.com>
	<kju1alhklf.fsf@romeo.rtfm.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> (1) There are some set of problems that users have or
>     believe they have.
> 
> (2) NAT solves at least some of those problems, at some
>     cost (say Cn), both financial and operational and
>     that solution has benefit Bn.
> 
> (3) The fact that a large number of people have chosen
>     to use NAT is a strong argument that B>C. (Here's
>     where the invocation of revealed preference comes in).

There's ample evidence that many users aren't aware of the costs of
using NAT, or especially, weren't aware of those costs before they
started using NAT - so their choices were poorly informed.   So no, it's
not reasonable to conclude that decisions to use NATs are justified by
realistic cost-benefit estimations of doing so.

There's also ample evidence that many users are not free to make this
choice, or that the costs of not using NAT are artificially inflated.

Note also that cost optimization by individual users (even if
well-informed) does not necessarily produce a cost-optimized result for
the overall community.

> (6) The argument that I thought I heard people (though not
>     you) making is that Cn > Bn. 

I think it would be more realistic to say that the cost of using NAT
for everything (that is, of not providing any e2e connectivity) is
greater than the benefit of using NAT for everything.  e.g. If you run a
home network, you can often configure your NAT to accept external
traffic on some ports and pass it to a single designated host.  (you
might argue that the fact that this option is popular indicates a
revealed preference among users to not NAT everything.)  But while this
works in corner cases,  it doesn't scale.

Keith



From owner-ietf@ietf.org  Thu Jun 19 17:21:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19092
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 17:21:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T6jC-00075D-JW
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 17:13:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T6iD-0006y9-Fn
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 17:12:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18771
	for <ietf@ietf.org>; Thu, 19 Jun 2003 17:12:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T6fv-0003PJ-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:10:31 -0400
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 19T6fu-0003Oo-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:10:30 -0400
Received: from cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 19 Jun 2003 14:10:23 -0800
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h5JLCKIX014280;
	Thu, 19 Jun 2003 14:12:20 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AIP17729;
	Thu, 19 Jun 2003 14:12:19 -0700 (PDT)
Message-Id: <200306192112.AIP17729@mira-sjc5-c.cisco.com>
To: EKR <ekr@rtfm.com>
cc: ietf@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Message from ekr@rtfm.com
   of "19 Jun 2003 13:35:08 PDT." <kju1alhklf.fsf@romeo.rtfm.com> 
Date: Thu, 19 Jun 2003 17:12:19 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

> Does this seem like a weird position for an IAB member to take?
> I don't think so. 

I think economics provides useful tools for talking about
and evaluating this stuff, too, but I think it's pretty
evident that you can optimize for anything you like and get
different results.  I question whether it's in this
organization's charter to privilege the individual user over
the good of the network.  If you choose to put yourself
behind a NAT that's possibly good for you (although I think
it's bad for you over the longer term) and always bad for
the people who want to reach you.

> There certainly are cases where it's appropriate for the IETF to say
> that something users want to do is not OK. Most of those cases are
> ones where their behavior has negative external effects on everyone
> else. I don't think a strong argument has been made that this is
> such a case.

That last sentence left me speechless, for which I suppose
some number of people are now in your debt.

Melinda



From owner-ietf@ietf.org  Thu Jun 19 17:30:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19499
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 17:30:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T6st-0008M7-BD
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 17:23:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T6sd-0008GB-78
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 17:23:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19309
	for <ietf@ietf.org>; Thu, 19 Jun 2003 17:23:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T6qL-0003Wh-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:21:17 -0400
Received: from tomts10.bellnexxia.net ([209.226.175.54] helo=tomts10-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T6qK-0003We-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:21:16 -0400
Received: from yahoo.com ([65.93.185.42]) by tomts10-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030619212336.NFOD17964.tomts10-srv.bellnexxia.net@yahoo.com>;
          Thu, 19 Jun 2003 17:23:36 -0400
Date: Thu, 19 Jun 2003 17:23:34 -0400
Subject: Re: myth of the great transition
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Melinda Shore <mshore@cisco.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <200306191927.AIP00803@mira-sjc5-c.cisco.com>
Message-Id: <48B032EF-A29C-11D7-A41F-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Thursday, June 19, 2003, at 03:27  PM, Melinda Shore wrote:

>> Keith, I don't get this argument. A NAPT is a firewall by your own
>> definition "I believe the primary purpose of firewalls should be to
>> protect the network, not the hosts, from abusive or unauthorized
>> usage." It's implementing a very simple policy, protect me from the
>> outside world.
>
> NAT has problematically constrained policy capabilities.
>

Does that mean that a NAT is a workable firewall but introduces 
undesirable side effects? Is it (or could it be) possible to make an 
equally workable firewall, at a low price, that doesn't introduce to 
constrained policy capabilities?

simon




From owner-ietf@ietf.org  Thu Jun 19 17:40:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20039
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 17:40:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T73X-0001iv-MV
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 17:34:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T734-0001bG-29
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 17:34:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19758
	for <ietf@ietf.org>; Thu, 19 Jun 2003 17:34:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T70l-0003e2-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:32:03 -0400
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 19T70l-0003dt-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:32:03 -0400
Received: from cisco.com (171.68.223.137)
  by sj-iport-3.cisco.com with ESMTP; 19 Jun 2003 14:36:36 -0800
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h5JLXrEP004410;
	Thu, 19 Jun 2003 14:33:53 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AIP21116;
	Thu, 19 Jun 2003 14:33:51 -0700 (PDT)
Message-Id: <200306192133.AIP21116@mira-sjc5-c.cisco.com>
To: S Woodside <sbwoodside@yahoo.com>
cc: ietf@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: myth of the great transition 
In-Reply-To: Message from sbwoodside@yahoo.com
   of "Thu, 19 Jun 2003 17:23:34 EDT." <48B032EF-A29C-11D7-A41F-000393414368@yahoo.com> 
Date: Thu, 19 Jun 2003 17:33:51 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

> > NAT has problematically constrained policy capabilities.
> Does that mean that a NAT is a workable firewall but introduces 
> undesirable side effects? 

No, it means that NAT is inherently incapable of
enforcing policy decisions at a granularity that's useful.

Melinda



From owner-ietf@ietf.org  Thu Jun 19 17:42:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20238
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 17:42:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T76R-000277-QW
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 17:37:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T75V-0001zR-09
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 17:36:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19895
	for <ietf@ietf.org>; Thu, 19 Jun 2003 17:36:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T73C-0003fL-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:34:34 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T73B-0003f2-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:34:34 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 35DDAABB5; Thu, 19 Jun 2003 14:42:26 -0700 (PDT)
>To: Melinda Shore <mshore@cisco.com>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <200306192112.AIP17729@mira-sjc5-c.cisco.com>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 14:42:25 -0700
In-Reply-To: <200306192112.AIP17729@mira-sjc5-c.cisco.com>
Message-ID: <kjllvxhhha.fsf@romeo.rtfm.com>
Lines: 73
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Melinda Shore <mshore@cisco.com> writes:

> > Does this seem like a weird position for an IAB member to take?
> > I don't think so. 
> 
> I think economics provides useful tools for talking about
> and evaluating this stuff, too, but I think it's pretty
> evident that you can optimize for anything you like and get
> different results.  I question whether it's in this
> organization's charter to privilege the individual user over
> the good of the network.  If you choose to put yourself
> behind a NAT that's possibly good for you (although I think
> it's bad for you over the longer term) and always bad for
> the people who want to reach you.
Well, my view, as I think I expressed on P-S, is that the
"good of the network" is some function of the individual
goods of the people on it, so I don't think of these as two
separate things, really. Obviously, one could take a less
utilitarian view.

> > There certainly are cases where it's appropriate for the IETF to say
> > that something users want to do is not OK. Most of those cases are
> > ones where their behavior has negative external effects on everyone
> > else. I don't think a strong argument has been made that this is
> > such a case.
> 
> That last sentence left me speechless, for which I suppose
> some number of people are now in your debt.
Heh.

I think we're talking differently about externalities, which,
as you say, is always a problem with this sort of utility
analysis. Realistically, there are three kinds of utility
effects of someone choosing to install a NAT:

(1) The effect on them personally.
(2) The effect on other people who might potentially correspond
    with them (a rather small set).
(3) The effect on the network as a whole, or to speak more
    precisely, the effect on a large set of people who
    have no relationship with the individual in question.

When I said "no strong argument" I was thinking about class (3), not
class (2), which I agree there is a much stronger argument to be had
about. I don't know of a strong argument for (3).

It's pretty clear that we have a mandate to deal with effects of type
(3). So, for instance, we go to a lot of effort to block things like
congestion collapse and DoS amplification, which impinge on all sorts
of innocent people. On the other hand, we mostly keep our hands out of
type (1), though not entirely. If people want to use RTP to listen to
Britney Spears, it doesn't harm anyone but themselves and we don't
care about that at all. 

Class (2) is trickier to know what to do, since on the one hand we
wouldn't try to force people to avail themselves of new services. On
the other, to the extent to which NAT encourages people not to make
themselves available, that does decrease welfare. As you say, these
costs are difficult to account for, and I had forgotten to account
for them. 

Assuming for the moment that those costs exceed the benefits, then we
would be in quite a difficult situation, since we've just described a
classic market failure where negative externalities aren't built into
price. But the problem isn't that people are stupid but rather that
they're rational. Getting them to do the efficient thing in such
situations is generally not easy.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 17:54:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20897
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 17:54:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T7Fg-0003te-39
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 17:47:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T78W-0002ML-5d
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 17:40:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19978
	for <ietf@ietf.org>; Thu, 19 Jun 2003 17:40:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T76D-0003gm-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:37:41 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T76D-0003gX-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:37:41 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 7A305ABB5; Thu, 19 Jun 2003 14:45:39 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: mshore@cisco.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <200306191920.AIO99844@mira-sjc5-c.cisco.com>
	<kju1alhklf.fsf@romeo.rtfm.com>
	<20030619170056.05849bfc.moore@cs.utk.edu>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 14:45:39 -0700
In-Reply-To: <20030619170056.05849bfc.moore@cs.utk.edu>
Message-ID: <kjfzm5hhbw.fsf@romeo.rtfm.com>
Lines: 34
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> > (1) There are some set of problems that users have or
> >     believe they have.
> > 
> > (2) NAT solves at least some of those problems, at some
> >     cost (say Cn), both financial and operational and
> >     that solution has benefit Bn.
> > 
> > (3) The fact that a large number of people have chosen
> >     to use NAT is a strong argument that B>C. (Here's
> >     where the invocation of revealed preference comes in).
> 
> There's ample evidence that many users aren't aware of the costs of
> using NAT, or especially, weren't aware of those costs before they
> started using NAT - so their choices were poorly informed. So no, it's
> not reasonable to conclude that decisions to use NATs are justified by
> realistic cost-benefit estimations of doing so.
NATs have been around for quite a while. This might have been 
a convincing argument 5 years ago, but I don't find it very 
convincing now, particularly in view of the fact that some
people who clearly understand the cost/benefits choose to use them.

> Note also that cost optimization by individual users (even if
> well-informed) does not necessarily produce a cost-optimized result for
> the overall community.
Of course. But then you have to describe the negative externality.
See my response to Melinda for more on this.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Thu Jun 19 18:01:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21266
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 18:01:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T7Nr-0005Xn-UF
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 17:55:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T7Mv-0005Dq-6o
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 17:54:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20922
	for <ietf@ietf.org>; Thu, 19 Jun 2003 17:54:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T7Kc-0003uU-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:52:35 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T7Kc-0003uR-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:52:34 -0400
Received: from localhost (localhost [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id A796014167; Thu, 19 Jun 2003 17:54:55 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 18128-04; Thu, 19 Jun 2003 17:54:55 -0400 (EDT)
Received: from cs.utk.edu (adsl-068-016-143-061.sip.tys.bellsouth.net [68.16.143.61])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id B178714160; Thu, 19 Jun 2003 17:54:54 -0400 (EDT)
Date: Thu, 19 Jun 2003 17:55:06 -0400
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Keith Moore <moore@cs.utk.edu>, mshore@cisco.com, ietf@ietf.org
To: EKR <ekr@rtfm.com>
From: Keith Moore <moore@cs.utk.edu>
In-Reply-To: <kjfzm5hhbw.fsf@romeo.rtfm.com>
Message-Id: <B046D74C-A2A0-11D7-87C8-000393DB5366@cs.utk.edu>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>> There's ample evidence that many users aren't aware of the costs of
>> using NAT, or especially, weren't aware of those costs before they
>> started using NAT - so their choices were poorly informed. So no, it's
>> not reasonable to conclude that decisions to use NATs are justified by
>> realistic cost-benefit estimations of doing so.

> NATs have been around for quite a while. This might have been
> a convincing argument 5 years ago, but I don't find it very
> convincing now, particularly in view of the fact that some
> people who clearly understand the cost/benefits choose to use them.

NATs have been around for awhile but not everyone has been using them 
for 5 years.  Some of those who thought NATs were a good idea are now 
looking for alternatives.  For other people, NATs work just fine for 
their current needs, and this has never been disputed.

>> Note also that cost optimization by individual users (even if
>> well-informed) does not necessarily produce a cost-optimized result 
>> for
>> the overall community.
> Of course. But then you have to describe the negative externality.

plenty of examples have already been given.

Keith




From owner-ietf@ietf.org  Thu Jun 19 18:08:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22164
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 18:08:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T7Rj-00065e-Ov
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 17:59:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T7R5-0005xt-Fy
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 17:59:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21152
	for <ietf@ietf.org>; Thu, 19 Jun 2003 17:59:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T7On-0003z9-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:56:53 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T7Om-0003z6-00
	for ietf@ietf.org; Thu, 19 Jun 2003 17:56:52 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h5JLx9tU014555;
	Thu, 19 Jun 2003 17:59:09 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h5JLx8ub014553;
	Thu, 19 Jun 2003 17:59:08 -0400
Date: Thu, 19 Jun 2003 17:59:08 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200306192159.h5JLx8ub014553@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: myth of the great transition
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: S Woodside <sbwoodside@yahoo.com>

    > Does that mean that a NAT is a workable firewall but introduces
    > undesirable side effects? Is it (or could it be) possible to make an
    > equally workable firewall, at a low price, that doesn't introduce to
    > constrained policy capabilities?

This is an incredibly pointless and idiotic discussion.

If the Internet architecture provided i) plenty of addresses, ii) locally
allocatable addresses, and iii) the ability change providers easily, there
would be *no* NAT boxes - none, zero, nada, zip.

People who needed firewall capability would install a real firewall. They'd
be just as cheap to make, simpler, have less side effects, etc, etc, etc.

End of story.

Now, can we please stop talking about whether or not NAT boxes are useful as
access control devices, please?

	Noel



From owner-ietf@ietf.org  Thu Jun 19 19:44:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25622
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 19:44:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19T8vh-000870-EL
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 19:34:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19T8uJ-0007tE-LP
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 19:33:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25314
	for <ietf@ietf.org>; Thu, 19 Jun 2003 19:33:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19T8s1-0004gd-00
	for ietf@ietf.org; Thu, 19 Jun 2003 19:31:09 -0400
Received: from tomts13.bellnexxia.net ([209.226.175.34] helo=tomts13-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19T8s0-0004ga-00
	for ietf@ietf.org; Thu, 19 Jun 2003 19:31:08 -0400
Received: from yahoo.com ([65.93.189.79]) by tomts13-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030619233328.BDO29645.tomts13-srv.bellnexxia.net@yahoo.com>;
          Thu, 19 Jun 2003 19:33:28 -0400
Date: Thu, 19 Jun 2003 19:33:26 -0400
Subject: Re: myth of the great transition
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <200306192159.h5JLx8ub014553@ginger.lcs.mit.edu>
Message-Id: <6C9ADA66-A2AE-11D7-A41F-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Thursday, June 19, 2003, at 05:59  PM, J. Noel Chiappa wrote:

>> From: S Woodside <sbwoodside@yahoo.com>
>
>> Does that mean that a NAT is a workable firewall but introduces
>> undesirable side effects? Is it (or could it be) possible to make an
>> equally workable firewall, at a low price, that doesn't introduce to
>> constrained policy capabilities?

oops, I meant to say:

Is it (or could it be) possible to make an equally workable {{{{{local 
address isolation system}}}}}, at a low price, that doesn't introduce 
the drawbacks of NAPT.

simon

>
> This is an incredibly pointless and idiotic discussion.
>
> If the Internet architecture provided i) plenty of addresses, ii) 
> locally
> allocatable addresses, and iii) the ability change providers easily, 
> there
> would be *no* NAT boxes - none, zero, nada, zip.
>
> People who needed firewall capability would install a real firewall. 
> They'd
> be just as cheap to make, simpler, have less side effects, etc, etc, 
> etc.
>
> End of story.
>
> Now, can we please stop talking about whether or not NAT boxes are 
> useful as
> access control devices, please?
>

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Thu Jun 19 21:12:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27578
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 21:12:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TAJn-0002gn-8G
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 21:03:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TAJR-0002Yx-4N
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 21:03:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27431
	for <ietf@ietf.org>; Thu, 19 Jun 2003 21:03:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TAH8-0005Az-00
	for ietf@ietf.org; Thu, 19 Jun 2003 21:01:10 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TAH8-0005Ap-00
	for ietf@ietf.org; Thu, 19 Jun 2003 21:01:10 -0400
Subject: RE: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Date: Thu, 19 Jun 2003 18:03:35 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8AD@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Thread-Index: AcM2o0CiBNJ4nShcSJ+S/qdbQtkwUAAI/cbA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "EKR" <ekr@rtfm.com>, "Melinda Shore" <mshore@cisco.com>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA27578

Eric,

> Eric Rescorla wrote:
> The fact that a large number of people have chosen
> to use NAT is a strong argument that B>C. (Here's
> where the invocation of revealed preference comes in).

This is not the point. What you are saying is that since B>C it makes
NAT OK. What I am saying (and possibly what Melinda was trying to say)
is this: NAT is a necessary evil. I don't challenge the fact that it is
necessary (for IPv4) and here to stay but the fact that it is necessary
does not make it less evil.

Michel.




From owner-ietf@ietf.org  Thu Jun 19 21:32:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28208
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 21:32:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TAh1-0005wQ-C8
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 21:27:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TAfO-0005e5-9Y
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 21:26:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28113
	for <ietf@ietf.org>; Thu, 19 Jun 2003 21:26:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TAd5-0005L7-00
	for ietf@ietf.org; Thu, 19 Jun 2003 21:23:51 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TAd5-0005Kl-00
	for ietf@ietf.org; Thu, 19 Jun 2003 21:23:51 -0400
Subject: RE: Re[2]: myth of the great transition (was US Defense Department forma lly adopts IPv6)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Thu, 19 Jun 2003 18:26:17 -0700
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8B0@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: Re[2]: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Thread-Index: AcM2f2JNNomUa0s6SSW8RoSXQ4mEDgASvjAg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Richard Welty" <rwelty@averillpark.net>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA28208

> Richard Welty wrote:
> the needed three legged firewall, bridging two interfaces and
> using NAT on the third one, is rather more complicated than i
> wanted to deploy for a budget-constrained customer. neither i
> nor my client feel that there was a much of a win here, but
> there weren't any other options, either.

This is a clever setup; am I guessing correctly in saying that
fortunately the IPSEC part needed to terminate on only one or two
servers and not on each host? 

Michel.




From owner-ietf@ietf.org  Thu Jun 19 21:53:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28724
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 21:53:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TB1L-0000oP-5l
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 21:48:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TB1B-0000gS-I2
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 21:48:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28645
	for <ietf@ietf.org>; Thu, 19 Jun 2003 21:48:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TAyt-0005Sw-00
	for ietf@ietf.org; Thu, 19 Jun 2003 21:46:23 -0400
Received: from krusty-motorsports.com ([192.94.170.8] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TAys-0005St-00
	for ietf@ietf.org; Thu, 19 Jun 2003 21:46:22 -0400
Received: from [24.194.112.77] (helo=skipper.averillpark.net)
	by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.14)
	id 19TB1A-0001MM-1C
	for ietf@ietf.org; Fri, 20 Jun 2003 01:48:44 +0000
Received: from rwelty by skipper.averillpark.net with local (Exim 4.14)
	id 19TAzE-0005Sd-T9
	for ietf@ietf.org; Thu, 19 Jun 2003 21:46:44 -0400
Date: Thu, 19 Jun 2003 21:46:44 -0400 (EDT)
From: Richard Welty <rwelty@averillpark.net>
Subject: Re[4]: myth of the great transition (was US Defense Department forma lly adopts IPv6)
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE
References: <963621801C6D3E4A9CF454A1972AE8F504F8B0@server2000.arneill-py.sacramento.ca.us>
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F8B0@server2000.arneill-py.sacramento.ca.us>
X-Mailer: Mahogany 0.64 'Sparc', compiled for Linux 2.4.9-13 i686
Message-Id: <E19TAzE-0005Sd-T9@skipper.averillpark.net>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 19 Jun 2003 18:26:17 -0700 Michel Py <michel@arneill-py.sacramento.ca.us> wrote:

> > Richard Welty wrote:
> > the needed three legged firewall, bridging two interfaces and
> > using NAT on the third one, is rather more complicated than i
> > wanted to deploy for a budget-constrained customer. neither i
> > nor my client feel that there was a much of a win here, but
> > there weren't any other options, either.
 
> This is a clever setup; am I guessing correctly in saying that
> fortunately the IPSEC part needed to terminate on only one or two
> servers and not on each host? 

yes, it only needed to terminate on the server in the DMZ (the internet
facing interface and the DMZ interface are the two that were bridged,
obviously.)

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





From owner-ietf@ietf.org  Thu Jun 19 21:56:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28932
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 21:56:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TB4F-0001Bt-6I
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 21:51:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TB3w-000143-81
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 21:51:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28681
	for <ietf@ietf.org>; Thu, 19 Jun 2003 21:51:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TB1d-0005TY-00
	for ietf@ietf.org; Thu, 19 Jun 2003 21:49:13 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TB1d-0005TT-00
	for ietf@ietf.org; Thu, 19 Jun 2003 21:49:13 -0400
Subject: RE: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Date: Thu, 19 Jun 2003 18:51:39 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8B1@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Thread-Index: AcM2Tn/v6IIeuqiWRgSpPlOPEK+OFwAfpJbw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA28932

Keith,

>> Michel Py wrote:
>> IMHO, here is the deal: IPv4 NAT does suck, but there is
>> nothing we can do to remove it; so the only worthy
>> efforts are 1) maybe try to make it less worse (I will
>> not go as far as  saying better) and 2) let's not make
>> the same mistake with IPv6.

> Keith Moore wrote:
> that's it in a nutshell.

I'm glad we could find something to agree on.


> I believe the primary purpose of firewalls should be to
> protect the network, not the hosts, from abusive or
> unauthorized usage.

I do not agree with this. The primary purpose of firewalls is to protect
BOTH the network and the hosts.


> the firewall without the NAT would be even more useful.

No argument here, but the way it is going to happen is not by bashing at
NAT but by developing the missing piece, namely a scalable solution for
portable identifiers.


> an intermediary MUST NOT alter the source or destination
> field in an IP header.

There is nothing wrong with this if another intermediary puts it back
the way it was originally, preserving end-to-end traffic.

Michel.




From owner-ietf@ietf.org  Thu Jun 19 22:09:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29407
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 22:09:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TBFr-0003W5-8O
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 22:03:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TBEV-0003G2-Eh
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 22:02:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29221
	for <ietf@ietf.org>; Thu, 19 Jun 2003 22:02:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TBCC-0005cn-00
	for ietf@ietf.org; Thu, 19 Jun 2003 22:00:08 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TBCC-0005cc-00
	for ietf@ietf.org; Thu, 19 Jun 2003 22:00:08 -0400
Subject: RE: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Date: Thu, 19 Jun 2003 19:02:34 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8B2@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Thread-Index: AcM2leYxNeU98gi5Rg6C4AT+Pdv08gAOLEdw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id WAA29407

Ted,

> Theodore Ts'o wrote:
> So 30 static IP addresses, with a slower service, is over
> *five* times more expensive, and over twice as expensive
> as faster service with only 2 static IP addresses.  
> As much as I hate NAT, from an aesthetic perspective,
> using two static IP addresses and a NAT box was the
> expedient solution.  We could I suppose blame the ISP's
> for their charging policies, but these economic pressures
> are going to drive people in certain directions, and as
> Ekr as pointed out, saying that people are either
> misinformed or non-rationale isn't going to help matters.

In other words, for your setup the inconveniences of NAT are not worth
spending $100/mo more. Same here.


> (Put another way, sure, Voice over IP would be nice.  But
> if I have to pay 2x or 5x a month to an ISP in order to
> not have a NAT box so I can use VoIP, wouldn't it be much
> more rational to stick with a wired POTS line?)

Not to mention that after 8pm cell phone calls are free. Besides, I do
voice over IP with ipip tunnels that cross NAT just fine.


> But the reality is that NAT boxes are here to stay, and
> we have lost that battle for IPv4. It would be nice not to
> lose that battle for IPv6, but I suspect the jury is still
> out on that point; and burying our heads in the sand about
> why people chose NAT's is not going to help us assure a
> NAT-free world for IPv6.

Ditto.

Michel.




From owner-ietf@ietf.org  Thu Jun 19 22:11:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29602
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 22:11:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TBFr-0003WB-JH
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 22:03:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TBFl-0003O4-Qr
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 22:03:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29245
	for <ietf@ietf.org>; Thu, 19 Jun 2003 22:03:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TBDT-0005dA-00
	for ietf@ietf.org; Thu, 19 Jun 2003 22:01:27 -0400
Received: from turkey.mail.pas.earthlink.net ([207.217.120.126])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TBDS-0005d2-00
	for ietf@ietf.org; Thu, 19 Jun 2003 22:01:26 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by turkey.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19TBFh-00001p-00; Thu, 19 Jun 2003 19:03:45 -0700
Date: Thu, 19 Jun 2003 22:00:48 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: primary purpose of firewalls
Message-Id: <20030619220048.1adee4de.moore@cs.utk.edu>
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F8B1@server2000.arneill-py.sacramento.ca.us>
References: <963621801C6D3E4A9CF454A1972AE8F504F8B1@server2000.arneill-py.sacramento.ca.us>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > I believe the primary purpose of firewalls should be to
> > protect the network, not the hosts, from abusive or
> > unauthorized usage.
> 
> I do not agree with this. The primary purpose of firewalls is to protect
> BOTH the network and the hosts.

the reason I disagree is that fundamentally, there's no way that a firewall
can reliably distinguish legitimate traffic from illegitimate traffic, and
there's no way that a firewall can exclude all (or in many cases even most)
threats.  to do that it would have to be smarter than the application.  a
firewall can thwart some subset of threats, or a firewall can block legitimate
traffic.  what it cannot do is remove the burden from hosts and applications
to implement reliable security.

OTOH, the network cannot expect hosts to protect it; it must protect itself.
that's why I say that the primary purpose of firewalls is to protect the
network. if the firewall can also provide security in depth for hosts, that's
useful, but that's just a backup - there's no way to have confidence in the
security of a host that relies on firewalls as its primary means of
protection. 

> > an intermediary MUST NOT alter the source or destination
> > field in an IP header.
> 
> There is nothing wrong with this if another intermediary puts it back
> the way it was originally, preserving end-to-end traffic.

if you're talking about RSIP, I don't think that's true, because IIRC it still
requires hosts and apps to be aware of addressing realms.



From owner-ietf@ietf.org  Thu Jun 19 22:47:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00569
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 22:47:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TBpf-0000mP-9V
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 22:40:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TBot-0000dK-CH
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 22:40:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00411
	for <ietf@ietf.org>; Thu, 19 Jun 2003 22:40:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TBma-0005uQ-00
	for ietf@ietf.org; Thu, 19 Jun 2003 22:37:44 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TBma-0005uN-00
	for ietf@ietf.org; Thu, 19 Jun 2003 22:37:44 -0400
Subject: RE: myth of the great transition
Date: Thu, 19 Jun 2003 19:40:09 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8B3@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: myth of the great transition
Thread-Index: AcM2vNrfu3dhOTrnTAmRu0JdTWGhZAAFxJiA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "S Woodside" <sbwoodside@yahoo.com>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id WAA00569

Simon,

> Simon Woodside wrote:
> Is it (or could it be) possible to make an equally workable
> {{{{{local address isolation system}}}}}, at a low price, that
> doesn't introduce the drawbacks of NAPT.

If you are talking about the actual hardware, yes. It already exists,
just a matter of how it is marketed. But this is not the issue; the
issue is providing users with something good enough to replace NAPT,
which is 1) portable identifiers or addresses "owned" by the user
(because renumbering is a pain) and 2) a scalable way to route all of
these.

Michel.



From owner-ietf@ietf.org  Thu Jun 19 23:02:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00986
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 23:02:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TC67-0003dj-Ba
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 22:57:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TC5T-0003VV-JW
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 22:57:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00847
	for <ietf@ietf.org>; Thu, 19 Jun 2003 22:57:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TC3A-00061T-00
	for ietf@ietf.org; Thu, 19 Jun 2003 22:54:52 -0400
Received: from sentosa.post1.com ([202.27.17.100])
	by ietf-mx with smtp (Exim 4.12)
	id 19TC39-00061K-00
	for ietf@ietf.org; Thu, 19 Jun 2003 22:54:51 -0400
Received: (qmail 89248 invoked from network); 20 Jun 2003 03:04:10 -0000
Received: from ida120.ida.gov.sg (HELO pobox.org.sg) (210.24.194.120)
  by sentosa.post1.com with SMTP; 20 Jun 2003 03:04:10 -0000
Message-ID: <3EF26217.2000005@pobox.org.sg>
Date: Fri, 20 Jun 2003 09:23:35 +0800
From: James Seng <jseng@pobox.org.sg>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en, zh-cn, zh-tw, ja, ko
MIME-Version: 1.0
To: EKR <ekr@rtfm.com>
CC: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>	<20030618130528.400b1f39.moore@cs.utk.edu>	<kj65n3mgdt.fsf@romeo.rtfm.com>	<20030618134424.410d29d1.moore@cs.utk.edu>	<kj1xxrmfln.fsf@romeo.rtfm.com>	<20030618140538.103ea88b.moore@cs.utk.edu>	<kju1ankzkr.fsf@romeo.rtfm.com> <3EF14A74.7090504@pobox.org.sg> <kjhe6mnpkb.fsf@romeo.rtfm.com>
In-Reply-To: <kjhe6mnpkb.fsf@romeo.rtfm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The question: smart terminal or smart network?

I believe in smart terminal. Nothing there suggest you should not run 
your firewall or any other filtering software on your end-terminal.

End-machine are vulnerable? Then fixed the end-machine. It isnt rocket 
science.

-James Seng

Eric Rescorla wrote:
> James Seng <jseng@pobox.org.sg> writes:
> 
> 
>>Why should the users be limited to what IT managers decide is good or bad?
>>
>>Internet is build on dumb network, smart terminal. End-users are
>>suppose to be able to put up their own services, not just running some
>>apps. This has been the Internet principles and have serves us well so
>>far.
> 
> No large production network can run this way. The end machines are 
> simply too vulnerable. Without firewally and service restriction,
> you'll have your entire network compromised very quickly.
> 
> -Ekr
> 





From owner-ietf@ietf.org  Thu Jun 19 23:19:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01410
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 23:19:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TCJf-0005wA-E2
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 23:11:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TCJW-0005ni-VF
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 23:11:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01328
	for <ietf@ietf.org>; Thu, 19 Jun 2003 23:11:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TCHE-00068i-00
	for ietf@ietf.org; Thu, 19 Jun 2003 23:09:24 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TCHD-00068N-00
	for ietf@ietf.org; Thu, 19 Jun 2003 23:09:23 -0400
Subject: RE: primary purpose of firewalls
Date: Thu, 19 Jun 2003 20:11:49 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <963621801C6D3E4A9CF454A1972AE8F506723A@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: primary purpose of firewalls
Thread-Index: AcM20EQZgh6AtiOfTbSiqMSxEEm1KgABamHw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id XAA01410

Keith,

>>> Keith Moore wrote:
>>> I believe the primary purpose of firewalls should be to
>>> protect the network, not the hosts, from abusive or
>>> unauthorized usage.
 
>> Michel Py wrote:
>> I do not agree with this. The primary purpose of firewalls is
>> to protect BOTH the network and the hosts.

> the reason I disagree is that fundamentally, there's no way
> that a firewall can reliably distinguish legitimate traffic
> from illegitimate traffic,

This is flat out untrue. Below are a few examples of illegitimate
traffic that my firewall trashed recently.

Jun 16 17:05:38.324 PST: %IDS-4-HTTP_WWW_HOST_FIELD_OVFLOW_SIG:
Sig:5123:WWW Host Field overflow - from 204.116.211.240 to 192.168.1.4

Jun 16 23:22:54.319 PST: %IDS-4-UDP_BOMB_SIG: Sig:4050:UDP Bomb
- from 206.13.31.12 to 209.233.126.65

Jun 18 11:28:58.906 PST: %IDS-4-HTTP_IIS_DOTDOT_EXE_SIG: Sig:3215:
IIS DOT DOT EXECUTE Attack - from 200.38.190.140 to 192.168.1.4


> what it cannot do is remove the burden from hosts and
> applications to implement reliable security.

This is unexpected coming from you. Look again at the last example I
pasted. Do _you_ suggest that I should trust _that_ vendor to implement
reliable security?



>>> an intermediary MUST NOT alter the source or destination
>>> field in an IP header.

>> There is nothing wrong with this if another intermediary puts it
>> back the way it was originally, preserving end-to-end traffic.

> if you're talking about RSIP, I don't think that's true, because
> IIRC it still requires hosts and apps to be aware of addressing
> realms.

I was talking about MHAP which is transparent to hosts and apps.

Michel.




From owner-ietf@ietf.org  Thu Jun 19 23:31:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01836
	for <ietf-web-archive@odin.ietf.org>; Thu, 19 Jun 2003 23:31:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TCWO-0007xl-7q
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 23:25:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TCR5-0006vo-Rf
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 23:19:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01456
	for <ietf@ietf.org>; Thu, 19 Jun 2003 23:19:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TCOm-00069v-00
	for ietf@ietf.org; Thu, 19 Jun 2003 23:17:12 -0400
Received: from falcon.mail.pas.earthlink.net ([207.217.120.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TCOm-00069s-00
	for ietf@ietf.org; Thu, 19 Jun 2003 23:17:12 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by falcon.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19TCR2-0002MG-00; Thu, 19 Jun 2003 20:19:32 -0700
Date: Thu, 19 Jun 2003 23:16:35 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: primary purpose of firewalls
Message-Id: <20030619231635.2b7a61c5.moore@cs.utk.edu>
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F506723A@server2000.arneill-py.sacramento.ca.us>
References: <963621801C6D3E4A9CF454A1972AE8F506723A@server2000.arneill-py.sacramento.ca.us>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> >>> Keith Moore wrote:
> >>> I believe the primary purpose of firewalls should be to
> >>> protect the network, not the hosts, from abusive or
> >>> unauthorized usage.
>  
> >> Michel Py wrote:
> >> I do not agree with this. The primary purpose of firewalls is
> >> to protect BOTH the network and the hosts.
> 
> > the reason I disagree is that fundamentally, there's no way
> > that a firewall can reliably distinguish legitimate traffic
> > from illegitimate traffic,
> 
> This is flat out untrue. Below are a few examples of illegitimate
> traffic that my firewall trashed recently.

read what I wrote again.  yes it can catch some things that are illegitimate. 
it cannot reliably catch all things that are illegitimate without also
blocking legitimate traffic.

> > what it cannot do is remove the burden from hosts and
> > applications to implement reliable security.
> 
> This is unexpected coming from you. Look again at the last example I
> pasted. Do _you_ suggest that I should trust _that_ vendor to implement
> reliable security?

I believe you should buy or write applications that ensure their own security
and protect the security of the machines on which they are hosted.  I believe
you should buy computing platforms that provide facilities to isolate
applications from one another, so that a single compromised application
doesn't compromise your entire platform.  I didn't say you should trust
others' applications to not try to attack your system.

> >>> an intermediary MUST NOT alter the source or destination
> >>> field in an IP header.
> 
> >> There is nothing wrong with this if another intermediary puts it
> >> back the way it was originally, preserving end-to-end traffic.
> 
> > if you're talking about RSIP, I don't think that's true, because
> > IIRC it still requires hosts and apps to be aware of addressing
> > realms.
> 
> I was talking about MHAP which is transparent to hosts and apps.

I'm not familiar with that acronym.  pointer to a spec?

Keith



From owner-ietf@ietf.org  Fri Jun 20 00:05:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02754
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 00:05:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TD38-0004Cq-R8
	for ietf-list@asgard.ietf.org; Thu, 19 Jun 2003 23:58:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TD2o-00045e-Nv
	for ietf@asgard.ietf.org; Thu, 19 Jun 2003 23:58:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02654
	for <ietf@ietf.org>; Thu, 19 Jun 2003 23:58:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TD0V-0006Rh-00
	for ietf@ietf.org; Thu, 19 Jun 2003 23:56:11 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TD0V-0006RS-00
	for ietf@ietf.org; Thu, 19 Jun 2003 23:56:11 -0400
Subject: RE: primary purpose of firewalls
Date: Thu, 19 Jun 2003 20:58:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8B5@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: primary purpose of firewalls
Thread-Index: AcM22tnBfw0ien41Ts+XkLE+xXTr2QAAKqYg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA02754

Keith,


> Keith Moore wrote:
> I believe you should buy or write applications that ensure their
> own security and protect the security of the machines on which
> they are hosted. I believe you should buy computing platforms
> that provide facilities to isolate applications from one another,
> so that a single compromised application doesn't compromise your
> entire platform.

On this one half of the mailing list can read what's in the back of your
mind, that can be summarized in a few words: Windows is not a real OS.
Don't try to say that's not what you think, everyone would laugh.

Keith, we are building the Internet for everyone, including the innocent
users that access a web server across the world that happens to run IIS.
Even you think that the person that chose to implement IIS on top of w2k
is stupid because s/he had half a brain s/he would have chosen apache on
top of unix, that's not the user's problem and if there is something I
can do as the firewall guy to shield that IIS server, I will.

> read what I wrote again.

I did and I pasted it again:

> the reason I disagree is that fundamentally, there's no way
> that a firewall can reliably distinguish legitimate traffic
> from illegitimate traffic,

Yes there is a way as I just demonstrated; a firewall with up-to-date
code can reliably distinguish legitimate traffic from illegitimate
traffic the same way an anti-virus can reliably detect viruses. And if
Microsoft sucks as much as you say it is fortunate that it can, because
a web server compromised by a nasty worm is bad for the entire
community. As of myself, I try to do my part of keeping a clean
Internet, which is configuring firewalls in front of web servers,
instead of saying that people should buy web servers that can't be
hacked.

Michel.




From owner-ietf@ietf.org  Fri Jun 20 00:26:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03434
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 00:26:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TDPK-000787-VH
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 00:21:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TDNT-00070j-VO
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 00:19:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03098
	for <ietf@ietf.org>; Fri, 20 Jun 2003 00:19:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TDLB-0006Yb-00
	for ietf@ietf.org; Fri, 20 Jun 2003 00:17:33 -0400
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 19TDL9-0006YR-00
	for ietf@ietf.org; Fri, 20 Jun 2003 00:17:32 -0400
Received: from cisco.com (171.68.223.138)
  by sj-iport-2.cisco.com with ESMTP; 19 Jun 2003 21:17:28 -0800
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h5K4JK9b007320;
	Thu, 19 Jun 2003 21:19:21 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AFG67531;
	Thu, 19 Jun 2003 21:19:19 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id VAA11137; Thu, 19 Jun 2003 21:19:19 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16114.35655.528305.71409@thomasm-u1.cisco.com>
Date: Thu, 19 Jun 2003 21:19:19 -0700 (PDT)
To: EKR <ekr@rtfm.com>
Cc: Melinda Shore <mshore@cisco.com>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
In-Reply-To: <kju1alhklf.fsf@romeo.rtfm.com>
References: <200306191920.AIO99844@mira-sjc5-c.cisco.com>
	<kju1alhklf.fsf@romeo.rtfm.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric Rescorla writes:
 > I said I was done with this discussion, but I think Melinda
 > deserves a response here.
 > 
 > Melinda Shore <mshore@cisco.com> writes:
 > 
 > > > I'm not sure what you mean by routing above. Are you suggesting there's
 > > > some negative externality in that NAT makes the routing infrastructure
 > > > more complicated? If so, what is it?
 > > 
 > > If you're multihomed and your route changes, your address
 > > changes.  (Yes, this happens).
 > Agreed.
 > 
 > > I am profoundly weirded out by reading an IAB member argue
 > > that something that's got broad market acceptance is
 > > tautologically okay.  I agree that there's a real problem
 > > here that NAT is trying to solve, but I certainly wouldn't
 > > treat it as a given that NAT is the best, or even a good,
 > > solution.  
 > I can understand how this would bother you, and I think
 > part of the problem is that I haven't been writing as clearly
 > as I could have. A series of e-mail replies isn't a good
 > way to elucidate your position.
 > 
 > Here's what I mean to be arguing:
 > 
 > (1) There are some set of problems that users have or
 >     believe they have.
 > 
 > (2) NAT solves at least some of those problems, at some
 >     cost (say Cn), both financial and operational and
 >     that solution has benefit Bn.
 > 
 > (3) The fact that a large number of people have chosen
 >     to use NAT is a strong argument that B>C. (Here's
 >     where the invocation of revealed preference comes in).
 > 
 > (4) It may well be the case that some other solution S
 >     would have some other costs Cs and benefit Bs such
 >     that (Bs - Cs) > (Bn - Cn). It may be that S doesn't
 >     exist yet, in which case it would be good for us
 >     to design and build it.
 > 
 > (5) It's also possible that at some time in the future
 >     Cn will exceed Bn, in which case I would expect people
 >     to stop using NAT and (probably) demand something else.
 > 
 > (6) The argument that I thought I heard people (though not
 >     you) making is that Cn > Bn. I don't think that this
 >     is likely to be the case. In that sense, I think
 >     NAT is OK. I think that if we believe this, it will likely
 >     lead to us designing a long series of S'es that are
 >     inferior to NAT (in the sense that users do not
 >     prefer them because (Bs - Cs) < (Bn - Cn). That's a waste
 >     of time.
 > 
 > Does this seem like a weird position for an IAB member to take?
 > I don't think so. 

The problem here is that your cost functions are
averages when what is far more interesting are the
trends. Voice is one trend and it pretty
fundamentally challenges one of the base
assumptions of NAT: private-client/public-server.
But instead of realizing that NAT is
architecturally incapable of dealing with private
servers and switching back to the model that does
accommodate that model fine, we're being driven as
a community to do both with the ensuing insanity
of two broken models being forced to cohabitate,
all the while neither meeting the actual
requirements.

So just saying that NAT is here get used to it is,
architecturally, not helpful. The split of effort
is to put it mildly a huge drain on engineering
talent, but more importantly the net is becoming
more and more incomprehensible because of it, both
intellectually as well as operationally. That
strikes me as a profound architectural issue, one
that should scare anybody who cares about the net.

So yes, to my mind saying "get used to it" is a
weird position because it discounts the problems
of the status quo and doesn't really express any
vision for what the architecture *ought* to be, or
drive us in a direction which will make that
determination possible. What NAT's are telling us
is that there are requirements that aren't being
met with the current Internet. But that's really
the only thing they should be telling us because
we already know that NAT's fail miserably on other
requirements.  We want an architecture that meets
all of the requirements, not a hodgepodge of half
solutions which fall over in the first stiff
breeze.



From owner-ietf@ietf.org  Fri Jun 20 00:33:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03722
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 00:33:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TDWA-0008Sa-Tp
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 00:28:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TDVt-0008Kg-Qb
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 00:28:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03604
	for <ietf@ietf.org>; Fri, 20 Jun 2003 00:28:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TDTb-0006hA-00
	for ietf@ietf.org; Fri, 20 Jun 2003 00:26:15 -0400
Received: from pintail.mail.pas.earthlink.net ([207.217.120.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TDTV-0006h7-00
	for ietf@ietf.org; Fri, 20 Jun 2003 00:26:14 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by pintail.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19TDVl-0000Dz-00; Thu, 19 Jun 2003 21:28:29 -0700
Date: Fri, 20 Jun 2003 00:25:32 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: primary purpose of firewalls
Message-Id: <20030620002532.41c0df95.moore@cs.utk.edu>
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F8B5@server2000.arneill-py.sacramento.ca.us>
References: <963621801C6D3E4A9CF454A1972AE8F504F8B5@server2000.arneill-py.sacramento.ca.us>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > Keith Moore wrote:
> > I believe you should buy or write applications that ensure their
> > own security and protect the security of the machines on which
> > they are hosted. I believe you should buy computing platforms
> > that provide facilities to isolate applications from one another,
> > so that a single compromised application doesn't compromise your
> > entire platform.
> 
> On this one half of the mailing list can read what's in the back of your
> mind, that can be summarized in a few words: Windows is not a real OS.
> Don't try to say that's not what you think, everyone would laugh.

you know, I'm happy to say that I don't really know enough about Windows
internals (for any version of Windows) to know for sure whether it provides
those facilities or not.  my honest guess is that recent versions do provide
them, and that the reason Windows boxes are insecure is because of poor
application implementation more than poor OS implementation.  

still, pretending that a firewall can make up for a lack of security on the
host (ANY host) or in the apps is simply unrealistic, no matter who wrote the
host OS.  and nothing we do in IETF can change that.

> I did and I pasted it again:
> 
> > the reason I disagree is that fundamentally, there's no way
> > that a firewall can reliably distinguish legitimate traffic
> > from illegitimate traffic,
> 
> Yes there is a way as I just demonstrated; a firewall with up-to-date
> code can reliably distinguish legitimate traffic from illegitimate
> traffic the same way an anti-virus can reliably detect viruses.

no, you demonstrated that it can do so in some cases, but not with reliability
- which would mean that you have the ability to rely on the firewall doing the
right thing.  for instance, "doing the right thing" often means being able to 
know which applications are enabled on a host, and to decide whether an
application peer has valid credentials, etc.  and the firewall simply can't do
that.  the app has to protect itself.

> And if Microsoft sucks as much as you say it is fortunate that it can,
> because a web server compromised by a nasty worm is bad for the entire
> community. 

you're the one who brought up Microsoft.  if you can't understand things that
I actually did say, don't delude yourself into thinking you understand things
that you think I thought but didn't say.

Keith



From owner-ietf@ietf.org  Fri Jun 20 00:45:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04155
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 00:45:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TDhs-0001jB-7J
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 00:41:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TDhj-0001bl-E0
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 00:40:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04028
	for <ietf@ietf.org>; Fri, 20 Jun 2003 00:40:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TDfQ-0006oT-00
	for ietf@ietf.org; Fri, 20 Jun 2003 00:38:28 -0400
Received: from ns2.sea.interquest.net ([66.135.144.2] helo=ns2.sea)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TDfP-0006oQ-00
	for ietf@ietf.org; Fri, 20 Jun 2003 00:38:27 -0400
Received: from ssprunk (ip175.post-vineyard.dfw.interquest.net [66.135.181.175])
	by ns2.sea (8.12.9/8.12.5) with SMTP id h5K4ekE9031353;
	Thu, 19 Jun 2003 21:40:47 -0700
Message-ID: <004b01c336e6$1ed50200$afb58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "James Seng" <jseng@pobox.org.sg>, "EKR" <ekr@rtfm.com>
Cc: "Keith Moore" <moore@cs.utk.edu>, <ietf@ietf.org>
References: <2A1D4C86842EE14CA9BC80474919782E0D2252@mou1wnexm02.verisign.com>	<20030618130528.400b1f39.moore@cs.utk.edu>	<kj65n3mgdt.fsf@romeo.rtfm.com>	<20030618134424.410d29d1.moore@cs.utk.edu>	<kj1xxrmfln.fsf@romeo.rtfm.com>	<20030618140538.103ea88b.moore@cs.utk.edu>	<kju1ankzkr.fsf@romeo.rtfm.com> <3EF14A74.7090504@pobox.org.sg> <kjhe6mnpkb.fsf@romeo.rtfm.com> <3EF26217.2000005@pobox.org.sg>
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Date: Thu, 19 Jun 2003 23:40:37 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "James Seng" <jseng@pobox.org.sg>
> The question: smart terminal or smart network?
>
> I believe in smart terminal. Nothing there suggest you should not run
> your firewall or any other filtering software on your end-terminal.
>
> End-machine are vulnerable? Then fixed the end-machine. It isnt rocket
> science.

Perhaps it _is_ rocket science, since I have yet to see an OS and suite of
applications which are capable of meeting modern productivity needs while
providing even rudimentary security.  Surely if it were simple, someone
would be selling it and get rich...

Humans are lazy and cheap.  It is significantly easier, not to mention more
effective, to manage a single firewall accessible by a handful of highly
trained security experts than it is to ensure the security of thousands,
possibly tens of thousands, of hosts that are managed by users who are
neither skilled at nor interested in evaluating and compensating for
application security flaws.

End to end is good, and dumb networks are good.  But at the edge (by that I
refer to all non-transit AS's) it's more cost effective to create a strong
perimeter and give up on anything inside that perimeter.  Perhaps it's not
the strongest solution in the end, but the people paying the bill rarely
care.

Of course, we all know the oft-quoted figure that 80% of electronic crime is
committed by insiders.  I'm pretty sure this is a direct effect of the above
trend, but corporate types seem to feel punishing insiders after the fact is
good enough, and prevention only applies to strangers.

S

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




From owner-ietf@ietf.org  Fri Jun 20 00:51:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04355
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 00:51:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TDna-0002sw-Pq
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 00:46:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TDmm-0002ka-P8
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 00:46:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04201
	for <ietf@ietf.org>; Fri, 20 Jun 2003 00:46:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TDkT-0006rJ-00
	for ietf@ietf.org; Fri, 20 Jun 2003 00:43:41 -0400
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TDkS-0006qK-00
	for ietf@ietf.org; Fri, 20 Jun 2003 00:43:41 -0400
Received: by romeo.rtfm.com (Postfix, from userid 556)
	id 86D7DABB5; Thu, 19 Jun 2003 21:51:35 -0700 (PDT)
To: Michael Thomas <mat@cisco.com>
Cc: Melinda Shore <mshore@cisco.com>, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <200306191920.AIO99844@mira-sjc5-c.cisco.com>
	<kju1alhklf.fsf@romeo.rtfm.com>
	<16114.35655.528305.71409@thomasm-u1.cisco.com>
Reply-To: EKR <ekr@rtfm.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: 19 Jun 2003 21:51:35 -0700
In-Reply-To: <16114.35655.528305.71409@thomasm-u1.cisco.com>
Message-ID: <kjy8zxfj1k.fsf@romeo.rtfm.com>
Lines: 35
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Portable Code)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Michael Thomas <mat@cisco.com> writes:
> So just saying that NAT is here get used to it is,
> architecturally, not helpful. The split of effort
> is to put it mildly a huge drain on engineering
> talent, but more importantly the net is becoming
> more and more incomprehensible because of it, both
> intellectually as well as operationally. That
> strikes me as a profound architectural issue, one
> that should scare anybody who cares about the net.
>
> So yes, to my mind saying "get used to it" is a
> weird position because it discounts the problems
> of the status quo and doesn't really express any
> vision for what the architecture *ought* to be, or
> drive us in a direction which will make that
> determination possible. What NAT's are telling us
> is that there are requirements that aren't being
> met with the current Internet. But that's really
> the only thing they should be telling us because
> we already know that NAT's fail miserably on other
> requirements.  We want an architecture that meets
> all of the requirements, not a hodgepodge of half
> solutions which fall over in the first stiff
> breeze.
I can agree with most of this, but I don't think that it's
incompatible with "get used to it". Look at it this way: I'm used to
the fact that I'm bald, even though I don't like it. At some point
there may be something I can do about that and at that point I would
do it. In the meantime, I wear a hat.

-Ekr

-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/



From owner-ietf@ietf.org  Fri Jun 20 01:09:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04858
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 01:09:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TE43-0005LV-BO
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 01:03:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TE1G-0004xP-Hc
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 01:01:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04719
	for <ietf@ietf.org>; Fri, 20 Jun 2003 01:01:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TDyx-0006zi-00
	for ietf@ietf.org; Fri, 20 Jun 2003 00:58:39 -0400
Received: from ns2.sea.interquest.net ([66.135.144.2] helo=ns2.sea)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TDyx-0006zf-00
	for ietf@ietf.org; Fri, 20 Jun 2003 00:58:39 -0400
Received: from ssprunk (ip175.post-vineyard.dfw.interquest.net [66.135.181.175])
	by ns2.sea (8.12.9/8.12.5) with SMTP id h5K50wE9032190;
	Thu, 19 Jun 2003 22:00:58 -0700
Message-ID: <006301c336e8$f08f6db0$afb58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Keith Moore" <moore@cs.utk.edu>,
        "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: <moore@cs.utk.edu>, <ietf@ietf.org>
References: <963621801C6D3E4A9CF454A1972AE8F504F8B5@server2000.arneill-py.sacramento.ca.us> <20030620002532.41c0df95.moore@cs.utk.edu>
Subject: Re: primary purpose of firewalls
Date: Thu, 19 Jun 2003 23:59:42 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Keith Moore" <moore@cs.utk.edu>
> you know, I'm happy to say that I don't really know enough about Windows
> internals (for any version of Windows) to know for sure whether it
provides
> those facilities or not.  my honest guess is that recent versions do
provide
> them, and that the reason Windows boxes are insecure is because of poor
> application implementation more than poor OS implementation.

Perhaps.  Most "server" applications on any commercial OS run as the
superuser, which by its nature can't be contained in the event of a security
breach.  The obvious next question is, why do most daemons run as superuser,
and is there a way to either configure or rewrite portions of those daemons
such that they can run as containable "normal" users and still provide 100%
of the functionality?

I also wonder if such containment even has much use.  Generally any
sensitive information a hacker wants to capture or destroy will be stored
inside the containment area of the hacked application.  Containment only
protects one application from another on the same machine, while large
servers typically have one or more machines dedicated to each application;
in many cases containment will only protect the OS from damage while the
sensitive _data_ is freely captured or destroyed.

>  for instance, "doing the right thing" often means being able to
> know which applications are enabled on a host, and to decide whether an
> application peer has valid credentials, etc.  and the firewall simply
can't do
> that.  the app has to protect itself.

The biggest problem I've seen in Enterprise environments is that people
running Internet-accessible servers (e.g. in the DMZ) often have no interest
or motivation to follow security policy; security is secondary to
functionality.

US DoD defines a trusted system as any system which is capable of breaking
your security policy.  Placing trusted systems in the hands of people you
don't or can't trust (in the normal sense) is a recipe for disaster, IMHO.
If you don't trust the owner, you have no reason to trust the machine, and a
trusted firewall is the only place left to enforce security policies.

S

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




From owner-ietf@ietf.org  Fri Jun 20 01:29:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05452
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 01:29:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TEJW-0007ua-MI
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 01:19:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TEJ8-0007nT-Km
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 01:19:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05223
	for <ietf@ietf.org>; Fri, 20 Jun 2003 01:19:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TEGp-00079S-00
	for ietf@ietf.org; Fri, 20 Jun 2003 01:17:07 -0400
Received: from cust-smtp1.radiolinja.fi ([213.161.33.208])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TEGo-00079J-00
	for ietf@ietf.org; Fri, 20 Jun 2003 01:17:07 -0400
Received: from EMCL (rl045112.radiolinja.net [213.161.45.112])
	by cust-smtp1.radiolinja.fi (Postfix) with SMTP id E071540008
	for <ietf@ietf.org>; Fri, 20 Jun 2003 08:19:20 +0300 (EEST)
From: "=?UTF-8?Q?John_Loughney?=" <john.loughney@kolumbus.fi>
To: <ietf@ietf.org>
Subject: =?UTF-8?Q?COACHES_bof_announcement?=
Date: Fri, 20 Jun 2003 08:16:27 +0000
Message-Id: <1056096987953>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Mailer: EMCL v2.20
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA05452

Hi all,

Here is a heads-up on a new BOF for Vienna.

br,
John

BOF NAME & ACRONYM: Comprehensive apprOACH to quality (COACH)
AREA:               General
BOF CHAIR(S):       Bernard Aboba, John Loughney

MAILING LIST:
List:               ietf-quality@bogus.com
Subscribe:          majordomo@psg.com
Body:               subscribe ietf-quality@bogus.com
Archive:            http://psg.com/lists/ietf-quality

FULL DESCRIPTION:

This BOF will focus on proposals for quality improvement within the IETF process, and
determine if there is enough substance to work on a framework within which these
proposals are evaluated. The outcome of the BOF will be to determine how best to 
proceed with these issues in the IETF.

There are concerns about the quality and timeliness of IETF output. These problems 
are enumerated in the IETF Problem Statement, currently under development in the Problem 
Statement Working Group. The current IETF Problem Resolution Process document suggests 
that a Working Group be formed to improve the quality processes, including review 
processes, used by IETF Working Groups.

The goals of this BOF will be to determine a basic approach that the IETF could take 
to WG process improvement, examine some of the documented proposal for process 
improvement, and determine if there is enough interest and content to warrant the creation 
of a WG to improve the quality processes used by Working Groups.

One goal is to write one or more documents on aspects of a WG quality plan.  For example, 
a document on tracking tools - what's available, and more importantly, how to use them 
to improve quality.  Another document on reviews - how they might be conducted, 
the rules for reviewing, choosing reviewers, etc.  The benefit of this is that it while 
it requires Working Groups to think about the issue, it doesn't require that all working 
groups come up with the same plan.

READING LIST:

http://www.ietf.org/internet-drafts/draft-ietf-problem-issue-statement-01.txt
http://www.ietf.org/internet-drafts/draft-ietf-problem-process-00.txt
http://www.ietf.org/internet-drafts/draft-klensin-overload-00.txt
http://www.ietf.org/internet-drafts/draft-carpenter-solution-sirs-00.txt

AGENDA:

Agenda Bashing (5 minutes)

Introduction (10 minutes)
	Existing RFC editorial guidelines - Scott Bradner
	

Quality: Overview and Framework (15 minutes)
  IETF  Problem Resolution Processes - Margaret Wasserman
  draft-ietf-problem-process-00.txt

Starting New Work (20 minutes)

  The BOF Process: A Critique
  Leslie Daigle

  IESG Overload and Quality of WGs - John Klensin
  draft-klensin-overload-00.txt

The WG Process (10 minutes)

  Decision points/milestones in the WG process - Margaret Wasserman
  TBA

The Review Process (20 minutes)

  Careful Additional Review of Documents (CARD) - Brian Carpenter
  draft-carpenter-solution-sirs-00.txt

  The Review Process in Action: The DCCP WG - Aaron Falk/Allison Mankin

Issue tracking tools (10 minutes)

  Requirements for IETF Tracking Tools
  TBA

Summary and Discussion (20 minutes)




From owner-ietf@ietf.org  Fri Jun 20 01:29:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05451
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 01:29:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TEJW-0007uK-AG
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 01:19:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TEIa-0007mJ-Jl
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 01:18:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05196
	for <ietf@ietf.org>; Fri, 20 Jun 2003 01:18:55 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TEGH-00078g-00
	for ietf@ietf.org; Fri, 20 Jun 2003 01:16:33 -0400
Received: from h80ad2547.async.vt.edu ([128.173.37.71] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TEGG-00078c-00
	for ietf@ietf.org; Fri, 20 Jun 2003 01:16:32 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h5K5ImPZ015067;
	Fri, 20 Jun 2003 01:18:48 -0400
Message-Id: <200306200518.h5K5ImPZ015067@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Your message of "Thu, 19 Jun 2003 07:27:03 EDT."
             <200306191127.h5JBR3ih009794@ginger.lcs.mit.edu> 
References: <200306191127.h5JBR3ih009794@ginger.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_604897608P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 20 Jun 2003 01:18:48 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Thu, 19 Jun 2003 07:27:03 EDT, "J. Noel Chiappa" said:

> The person who's most in denial around here is you - about how definitively
> the market has, for the moment, chosen IPv4+NAT as the best balance between
> cost and effectiveness.

Actually Noel, I think what he's in denial about is the fact that "the market"
may not have a *CLUE* on how to properly evaluate the balances.

The market has also "chosen" a certain specific MUA for its outstanding ability
to balance security and functionality.  Note that even upper management of
the vendor in question admits that errors were made:

"We really haven't done everything we could to protect our customers. Our
products just aren't engineered for security." -- Microsoft executive Brian
Valentine, on the painful realization that a $100 million, two-month-long
codeathon still hasn't fixed the glaring holes in its software, InfoWorld, 5
September 2002 (from http://www.ditherati.net/archive/2002/36/)

So should we conclude that "the market" doesn't care a rat's posterior about
security? Or should we conclude that it simply didn't realize the size of the
exposure and the downstream costs of lack of security?


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

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

iD8DBQE+8pk4cC3lWbTT17ARApiEAJ0eEPmMSukiagEpfVPM2SGUucvGAACfU9pA
0rJ93JQ7bUQo4cFUn0jwg74=
=Rmdm
-----END PGP SIGNATURE-----

--==_Exmh_604897608P--



From owner-ietf@ietf.org  Fri Jun 20 01:57:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04860
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 01:09:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TE42-0005L7-FX
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 01:03:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TE0e-0004qi-85
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 01:00:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04683
	for <ietf@ietf.org>; Fri, 20 Jun 2003 01:00:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TDyL-0006zF-00
	for ietf@ietf.org; Fri, 20 Jun 2003 00:58:01 -0400
Received: from wetware.wetware.com ([199.108.16.1] helo=wetware.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TDyK-0006yv-00
	for ietf@ietf.org; Fri, 20 Jun 2003 00:58:00 -0400
Received: from 208.177.152.18.ptr.us.xo.net ([208.177.152.18] helo=wetware.com)
	by wetware.com with esmtp (Exim 4.20)
	id 19TE07-0003PL-Mi; Thu, 19 Jun 2003 21:59:51 -0700
Date: Thu, 19 Jun 2003 22:00:00 -0700
Subject: Re: NAT box spec? (RE: myth of the great transition)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Keith Moore <moore@cs.utk.edu>
To: IETF list <ietf@ietf.org>
From: james woodyatt <jhw@wetware.com>
In-Reply-To: <20030618155148.5906fb79.moore@cs.utk.edu>
Message-Id: <0BD993D8-A2DC-11D7-8892-000393BA7EBA@wetware.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wednesday, Jun 18, 2003, at 12:51 US/Pacific, Keith Moore wrote:
> [I wrote:]
>> When customers of retail Internet service start demanding a NAT
>> standard, then that's when the IETF might want to think about
>> documenting the standard that the market seems to want.
>
> here's the only thing that a NAT standard should say:
>
> an intermediary MUST NOT alter the source or destination field in an IP
> header.
>
> an intermediary MUST NOT route an IP packet to other than its intended
> destination.
>
> an intermediary MUST NOT alter the payload of an IP packet.

I don't dispute this.  However, I will observe that customers of retail 
Internet service seem to rarely have much interest in whether their 
network intermediaries comply with this proposition.

And, your list is incomplete.  The NAT code I maintain does all of the 
things above that your proposal would explicitly forbid-- but it does a 
few other nasty things as well.  For example, 1) it *should* be 
rewriting IP datagram identifiers (but I haven't coded it yet), and 2) 
it hides path-MTU discovery black-holes by rewriting TCP MSS fields.

Basically, once you've committed to rewriting the forwarding 
information in an IP datagram, then it's open season on all manner of 
horrible opportunities for intermediaries to engage in Internet abuse.

You want to know what made my blood run cold in the latest release of 
the product's firmware?  I had to change it so that it would propose an 
impossible MRU in a PPPoE LCP negotiation.  Apparently, a lot of PPPoE 
implementations are happily proposing an MRU of 1500 octets, because 
there are a lot of PPPoE servers out there that will refuse to 
negotiate down to the more realistic value of 1492.  Consequently, when 
the product doesn't connect to a buggy PPPoE server, and every other 
product people try seems to work fine (as long as you don't stress test 
it), the customer blames the firmware that actually complies with the 
actual standard for refusing to work the way everyone else's 
non-compliant system works.

So yeah-- I'm very excited about the prospects of the IETF proposing 
standards.  I'm even more excited when they're standards that customers 
regard as actually valuable parts of their lifestyles.  I have yet to 
see a proposal for a NAT box spec that would seem like a valuable 
addition to the RFC library.  Including yours, Keith... no disrespect 
intended, honest.


-- 
j h woodyatt <jhw@wetware.com>
stop me before i rewrite your IP header again.




From owner-ietf@ietf.org  Fri Jun 20 04:19:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21028
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 04:19:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TGz0-0001CI-29
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 04:10:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TGyc-00015B-Ef
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 04:10:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20799
	for <ietf@ietf.org>; Fri, 20 Jun 2003 04:10:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TGwJ-0000TQ-00
	for ietf@ietf.org; Fri, 20 Jun 2003 04:08:07 -0400
Received: from [202.54.16.83] (helo=hemant.gsslco.co.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TGwH-0000TM-00
	for ietf@ietf.org; Fri, 20 Jun 2003 04:08:06 -0400
Received: from agni.bombay.gsslco.co.in (agni.bombay..gsslco.co.in [10.1.100.6])
	by hemant.gsslco.co.in (8.11.6/8.11.6) with ESMTP id h5K8N8K21970
	for <ietf@ietf.org>; Fri, 20 Jun 2003 13:53:08 +0530
Received: (from root@localhost)
	by agni.bombay.gsslco.co.in (8.11.2/8.11.2) id h5K8EVQ16837
	for ietf@ietf.org; Fri, 20 Jun 2003 13:44:31 +0530
Received: from MANOJD1 ([10.1.5.41])
	by agni.bombay.gsslco.co.in (8.11.2/8.11.2) with SMTP id h5K8EUA16811
	for <ietf@ietf.org>; Fri, 20 Jun 2003 13:44:30 +0530
From: "manojd" <manojd@geometricsoftware.com>
To: <ietf@ietf.org>
Subject: RE: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Date: Fri, 20 Jun 2003 13:47:35 +0530
Message-ID: <006601c33704$6760cd60$2905010a@MANOJD1>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <20030619132147.4eeb4def.moore@cs.utk.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
X-scanner: scanned by Inflex 1.0.12.3 - (http://pldaniels.com/inflex/)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Since the issue is stable end-points, could something like this be a patch
for v4 NATs?

a) Applications running behind NAT are constrained to have only 8-bit
effective port numbers. Means no more than 256 ports.

b) If there are no more than 256 devices hiding behind NAT, NAT could
allocate a stable 8-bit per-device number for each device.

c) Externally visible port number used by an application on some device is
composed of its stable 8-bit number known to NAT, plus 8-bit port number it
locally allocates.

Device & app config is more complex. And the idea of "well known port
numbers" for certain protocols goes for a toss. But at least the apps work.

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org]On Behalf Of Keith
Moore
Sent: Thursday, June 19, 2003 10:52 PM
To: EKR
Cc: moore@cs.utk.edu; dts@senie.com; ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department
forma lly adopts IPv6)


> > until recently the only way I could get even one
> > static IP address for my home was through a special deal with a
> > friend of mine who had a small ISP, and the best bandwidth I could
> > get was 128kbps.  none of the other local providers would sell me
> > one.
>
> Doesn't the fact that there's not enough demand for this product
> to make it available suggest anything to you?

does the fact that there was enough demand for the product that it
eventually became available suggest anything to you?

> > so if you can't come up with a rational explanation for something,
> > just pretend that the market is wise and cite it as an unimpeachable
> > authority.
>
> I do have a rational explanation: the customers don't actually care
> at all about your fundamentalist commitment to end-to-end
> connectivity.

true, customers don't care about e2e.  they do, however, care about
running apps that won't work when e2e is broken.

> So, on the one hand, we have the actual behavior of millions of
> people.

no, we have your biased interpretation of that behavior, as observed
from a great distance, through a dirty lens.

Keith




From owner-ietf@ietf.org  Fri Jun 20 04:44:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21654
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 04:44:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19THS2-00057G-7O
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 04:40:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19THR1-0004v1-T5
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 04:39:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21565
	for <ietf@ietf.org>; Fri, 20 Jun 2003 04:39:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19THOi-0000fB-00
	for ietf@ietf.org; Fri, 20 Jun 2003 04:37:28 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19THOi-0000f3-00
	for ietf@ietf.org; Fri, 20 Jun 2003 04:37:28 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 9A56E62278; Fri, 20 Jun 2003 10:39:19 +0200 (CEST)
Date: Fri, 20 Jun 2003 10:39:19 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org
Subject: Re: primary purpose of firewalls
Message-ID: <732370000.1056098359@askvoll.hjemme.alvestrand.no>
In-Reply-To: <20030619220048.1adee4de.moore@cs.utk.edu>
References: <963621801C6D3E4A9CF454A1972AE8F504F8B1@server2000.arneill-py.sac
 ramento.ca.us> <20030619220048.1adee4de.moore@cs.utk.edu>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On torsdag, juni 19, 2003 22:00:48 -0400 Keith Moore <moore@cs.utk.edu> 
wrote:

>> > I believe the primary purpose of firewalls should be to
>> > protect the network, not the hosts, from abusive or
>> > unauthorized usage.
>>
>> I do not agree with this. The primary purpose of firewalls is to protect
>> BOTH the network and the hosts.
>
> the reason I disagree is that fundamentally, there's no way that a
> firewall can reliably distinguish legitimate traffic from illegitimate
> traffic, and there's no way that a firewall can exclude all (or in many
> cases even most) threats.  to do that it would have to be smarter than
> the application.

I actually agree with both of the statements that are double-quoted above...

- the primary purpose of firewalls SHOULD BE to protect the network
- the primary purpose of firewalls IS to protect the hosts

The reasoning is that I think most hosts SHOULD be hardened enough to do 
their job while standing "naked" on the network, while in the current state 
of affairs, the proportion of hosts that are capable of standing up to 
serious attacks from the Internet without the firewalls' comfort blankets 
is probably better measured as parts per million than as a percentage.

(the proportion of hosts that are able to survive serious attacks WITH the 
firewalls' help may be all the way up into single digit percentages....)

                Harald




From owner-ietf@ietf.org  Fri Jun 20 04:46:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21779
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 04:46:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19THTy-0005Lu-8F
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 04:42:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19THTS-0005EY-6D
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 04:42:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21615
	for <ietf@ietf.org>; Fri, 20 Jun 2003 04:42:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19THR9-0000fj-00
	for ietf@ietf.org; Fri, 20 Jun 2003 04:39:59 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19THR8-0000fY-00
	for ietf@ietf.org; Fri, 20 Jun 2003 04:39:58 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 3E8B462278
	for <ietf@ietf.org>; Fri, 20 Jun 2003 10:41:50 +0200 (CEST)
Date: Fri, 20 Jun 2003 10:41:50 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
Message-ID: <734660000.1056098510@askvoll.hjemme.alvestrand.no>
In-Reply-To: <200306181931.AIN63758@mira-sjc5-c.cisco.com>
References:  <200306181931.AIN63758@mira-sjc5-c.cisco.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On onsdag, juni 18, 2003 15:31:56 -0400 Melinda Shore <mshore@cisco.com> 
wrote:

> As a process kind of thing, I'm also concerned about the
> growth of the "temporary" sub-IP area, so I think there are
> issues here with both the work itself and in how the IETF
> goes about taking on and structuring its work.

in case someone missed it.... both the L2VPN and L3VPN WGs are being 
proposed within the *INTERNET* area.

                     Harald




From owner-ietf@ietf.org  Fri Jun 20 08:42:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03859
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 08:42:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TL3G-0003ei-E2
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 08:31:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TKkB-0005RW-3P
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 08:11:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01466
	for <ietf@ietf.org>; Fri, 20 Jun 2003 08:11:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TKhp-0002vC-00
	for ietf@ietf.org; Fri, 20 Jun 2003 08:09:25 -0400
Received: from turkey.mail.pas.earthlink.net ([207.217.120.126])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TKhp-0002v9-00
	for ietf@ietf.org; Fri, 20 Jun 2003 08:09:25 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by turkey.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19TKjo-0005XO-00; Fri, 20 Jun 2003 05:11:28 -0700
Date: Fri, 20 Jun 2003 08:08:30 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "manojd" <manojd@geometricsoftware.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030620080830.20825147.moore@cs.utk.edu>
In-Reply-To: <006601c33704$6760cd60$2905010a@MANOJD1>
References: <20030619132147.4eeb4def.moore@cs.utk.edu>
	<006601c33704$6760cd60$2905010a@MANOJD1>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Since the issue is stable end-points, could something like this be a patch
> for v4 NATs?

since you have to change NATs, apps, and DNS to make this work, you might as
well just use IPv6 - and the changes for v6 are already in the pipeline.




From owner-ietf@ietf.org  Fri Jun 20 08:42:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03856
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 08:42:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TKzQ-0002fG-45
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 08:27:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TKO7-00028C-P8
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 07:49:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27938
	for <ietf@ietf.org>; Fri, 20 Jun 2003 07:49:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TKLl-00023L-00
	for ietf@ietf.org; Fri, 20 Jun 2003 07:46:37 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TKLi-000223-00
	for ietf@ietf.org; Fri, 20 Jun 2003 07:46:36 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h5KBmVtU017862;
	Fri, 20 Jun 2003 07:48:31 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h5KBmVAW017861;
	Fri, 20 Jun 2003 07:48:31 -0400
Date: Fri, 20 Jun 2003 07:48:31 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200306201148.h5KBmVAW017861@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Eric Rescorla <ekr@rtfm.com>

    > (2) NAT solves at least some of those problems, at some
    >    cost (say Cn), both financial and operational and
    >    that solution has benefit Bn.

    > (3) The fact that a large number of people have chosen
    >     to use NAT is a strong argument that B>C.

Ah, I think your model has a fatal oversimplification here - but it's one I'm
glad you made, since it has given me a clue to a deeper understanding of why
NAT's are doing so well. Here goes...

The problem with your analysis is that there's no single value of C and B for
everyone; those numbers depend on what you're trying to do. So for *some*
people, B>C (we'll call this group NAT-Users, or N-U for short) - but for
*other* people, C>B (and we'll call them NAT-Avoiders, or N-A).

We've heard from a number of the latter group - people who want to run voice
(not over tunnels), people who want to run IPSEC (not over tunnels), etc.
However...


The interesting point that I get from thinking about this is that we need to
think about the size of the two groups - and in particular, how large the N-U
group is likely to be down the line.

That group has no reason to deploy any new technology - what they have
already works fine for them. So if there is a very large population of N-U,
especially if they are a big enough group to be a majority of the Internet
user base, then I think we're going to have to continue to interoperate with
those people.

That means that i) NAT+v4 is here to stay, permanently, as the
packet-forwarding substrate on which we have to live, and ii) many
"solutions" to the "NAT problem" have a badly faulty key premise - which is
that the solution will fix IPv4's problems by replacing it.

The notion of a system with a single, globally unique namespace at the lowest
level is a really nice one, one we had for a while - and *one we think we can
reclaim*. I now think we've been deluding ourselves; that past (like so many
others, e.g. the one where we didn't have spam) is gone for good.


I think the IETF needs to face that painful reality, or become increasingly
irrelevant.

	Noel



From owner-ietf@ietf.org  Fri Jun 20 10:57:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10530
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 10:57:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TN0K-0003x5-VT
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 10:36:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TMxg-0003gX-77
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 10:33:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08563
	for <ietf@ietf.org>; Fri, 20 Jun 2003 10:33:53 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TMxe-0004MK-00
	for ietf@ietf.org; Fri, 20 Jun 2003 10:33:54 -0400
Received: from h80ad25d3.async.vt.edu ([128.173.37.211] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TMxc-0004MH-00
	for ietf@ietf.org; Fri, 20 Jun 2003 10:33:53 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h5KEXfPZ020826;
	Fri, 20 Jun 2003 10:33:41 -0400
Message-Id: <200306201433.h5KEXfPZ020826@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: manojd <manojd@geometricsoftware.com>
Cc: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Your message of "Fri, 20 Jun 2003 13:47:35 +0530."
             <006601c33704$6760cd60$2905010a@MANOJD1> 
References: <006601c33704$6760cd60$2905010a@MANOJD1>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1137844333P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 20 Jun 2003 10:33:41 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Fri, 20 Jun 2003 13:47:35 +0530, manojd <manojd@geometricsoftware.com>  said:
> Since the issue is stable end-points, could something like this be a patch
> for v4 NATs?

No.

> c) Externally visible port number used by an application on some device is
> composed of its stable 8-bit number known to NAT, plus 8-bit port number it
> locally allocates.

As you note below, this totally breaks the idea of "well known ports".

> Device & app config is more complex. And the idea of "well known port
> numbers" for certain protocols goes for a toss. But at least the apps work.

Hmm... 21, 23, 25, 80, etc etc etc.  This is even worse than the usual
"you have to pick exactly one destination machine and hand-tunnel it to
the server" solution.

I suppose if you had absolutely NO intent to have inbound connections,
you could make it work.

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

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

iD8DBQE+8xtFcC3lWbTT17ARAhgjAKDcJnSA/BRrzHhYiWkwtLcLvIwmRwCfS4Jn
yH1gqYL4hbPOm6YjKnBFdh4=
=Lcyu
-----END PGP SIGNATURE-----

--==_Exmh_1137844333P--



From owner-ietf@ietf.org  Fri Jun 20 11:04:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11050
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 11:04:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TNJf-0006dc-Au
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 10:56:39 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TNHb-0006UY-Jm
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 10:54:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10008
	for <ietf@ietf.org>; Fri, 20 Jun 2003 10:54:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TNHa-0004n6-00
	for ietf@ietf.org; Fri, 20 Jun 2003 10:54:30 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TNHa-0004n3-00
	for ietf@ietf.org; Fri, 20 Jun 2003 10:54:30 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5KEsKN20140;
        Fri, 20 Jun 2003 10:54:21 -0400 (EDT)
Date: Fri, 20 Jun 2003 10:54:20 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030620105420.73f8bbc9.moore@cs.utk.edu>
In-Reply-To: <200306201148.h5KBmVAW017861@ginger.lcs.mit.edu>
References: <200306201148.h5KBmVAW017861@ginger.lcs.mit.edu>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> That means that i) NAT+v4 is here to stay, permanently, as the
> packet-forwarding substrate on which we have to live, and ii) many
> "solutions" to the "NAT problem" have a badly faulty key premise -
> which is that the solution will fix IPv4's problems by replacing it.

almost agree.  NAT is here to stay on v4, and apps that work fine with
NAT+v4 will continue to use NAT+v4, at least for the near to medium
term.   nor is there likely to be a replacement for NAT in v4, because
there's no way to get any more addresses out of 32 bits.

so I don't see us replacing NAT in v4. but I do see us building another
network that uses the same layer 1-2 links as the IPv4+NAT network but
also provides an alternate layer 3.

the reason I point out the flaws with NAT is not that I think we can get
rid of them in v4. it's because some people are still of the belief that
NATs are mostly harmless and that we should not only permit them
into v6, but extend our architecture to embrace them.  that's simply
insane.

Keith



From owner-ietf@ietf.org  Fri Jun 20 11:06:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11293
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 11:06:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TNNh-0007iX-0S
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 11:00:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TNLM-000795-Hz
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 10:58:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10807;
	Fri, 20 Jun 2003 10:58:22 -0400 (EDT)
From: ned.freed@mrochek.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TNLL-00058M-00; Fri, 20 Jun 2003 10:58:23 -0400
Received: from mauve.mrochek.com ([209.55.107.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TNLK-00058F-00; Fri, 20 Jun 2003 10:58:23 -0400
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
 id <01KX9YXV5TSW00CUGD@mauve.mrochek.com>; Fri,
 20 Jun 2003 07:58:18 -0700 (PDT)
Date: Fri, 20 Jun 2003 07:44:09 -0700 (PDT)
Subject: Re: Last Call: SDP attribute for qualifying Media Formats with Generic
 Parameters to a Proposed Standard
In-reply-to: "Your message dated Thu, 19 Jun 2003 15:22:22 -0400"
 <E19T4zG-00044l-CY@asgard.ietf.org>
To: iesg@ietf.org
Cc: ietf@ietf.org
Message-id: <01KXB6JAPVBE00CUGD@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Content-transfer-encoding: 7BIT
References: <E19T4zG-00044l-CY@asgard.ietf.org>
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

> The IESG has received a request from Individual Submissions WG to consider
> the following Internet-Draft(s) as a Proposed Standard. This has been
> reviewed in the IETF but is not the product of an IETF Working Group.
> o Individual Submissions (NONE): SDP attribute for qualifying Media
>   Formats with Generic Parameters
>     <draft-rajeshkumar-mmusic-gpmd-03.txt>
>     Proposed Standard

This looks to me like a substantive duplication of the media features facility
defined in RFC 2533 and elaborated on in RFCs 2506, 2530, 2534, 2738, 2912,
2913, 2938, and 2987. Not only does this set of documents provide a
full-featured media feature tagging and content negotiation facility, the
relationship to MIME media types and parameters has also been worked out.

Although the media features facility defined in these various RFCs is perhaps
too elaborate for SDP's needs, it should at least be possible to reuse the
basic descriptive elements of media features and the corresponding media
features registry.

At a minimum this draft needs to explain why the existing media features
facility is unsuitable for SDP's use and another, similar facility needs to
be defined.

				Ned



From owner-ietf@ietf.org  Fri Jun 20 11:27:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12218
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 11:27:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TNeg-0002sY-EC
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 11:18:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TNaA-0002Ik-9B
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 11:13:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11754
	for <ietf@ietf.org>; Fri, 20 Jun 2003 11:13:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TNa9-0005NW-00
	for ietf@ietf.org; Fri, 20 Jun 2003 11:13:41 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TNa8-0005N6-00
	for ietf@ietf.org; Fri, 20 Jun 2003 11:13:41 -0400
Subject: RE: primary purpose of firewalls
Date: Fri, 20 Jun 2003 08:13:45 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8B6@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: primary purpose of firewalls
Thread-Index: AcM26QXCv5Baj78PQbiWBEDnicMj1wAVMVYw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA12218

Stephen,

> Stephen Sprunk wrote:
> The biggest problem I've seen in Enterprise environments
> is that people running Internet-accessible servers (e.g.
> in the DMZ) often have no interest or motivation to follow
> security policy; security is secondary to functionality.

Sigh. Yes; to the point that they don't even apply services packs or
patches unless they bring more functionality.


> If you don't trust the owner, you have no reason to trust
> the machine, and a trusted firewall is the only place left
> to enforce security policies.

This is especially true in colos; not only it is simpler for me to
manage 2 firewalls instead of a farm of 300 servers but the fact of the
matter is that two thirds of this servers are colos that I don't have
control over and some of their owners are rather lame in terms of
security.

Michel.




From owner-ietf@ietf.org  Fri Jun 20 11:34:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13060
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 11:34:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TNnM-0004LV-VY
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 11:27:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TNi4-0003aU-LK
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 11:21:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12022
	for <ietf@ietf.org>; Fri, 20 Jun 2003 11:21:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TNi3-0005Rc-00
	for ietf@ietf.org; Fri, 20 Jun 2003 11:21:51 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TNi3-0005Qk-00
	for ietf@ietf.org; Fri, 20 Jun 2003 11:21:51 -0400
Subject: RE: primary purpose of firewalls
Date: Fri, 20 Jun 2003 08:13:45 -0700
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8B6@server2000.arneill-py.sacramento.ca.us>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Thread-Topic: primary purpose of firewalls
Thread-Index: AcM26QXCv5Baj78PQbiWBEDnicMj1wAVMVYw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Stephen Sprunk" <stephen@sprunk.org>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Cc: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA13060

Stephen,

> Stephen Sprunk wrote:
> The biggest problem I've seen in Enterprise environments
> is that people running Internet-accessible servers (e.g.
> in the DMZ) often have no interest or motivation to follow
> security policy; security is secondary to functionality.

Sigh. Yes; to the point that they don't even apply services packs or
patches unless they bring more functionality.


> If you don't trust the owner, you have no reason to trust
> the machine, and a trusted firewall is the only place left
> to enforce security policies.

This is especially true in colos; not only it is simpler for me to
manage 2 firewalls instead of a farm of 300 servers but the fact of the
matter is that two thirds of this servers are colos that I don't have
control over and some of their owners are rather lame in terms of
security.

Michel.




From owner-ietf@ietf.org  Fri Jun 20 11:55:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14550
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 11:55:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TO35-0007DJ-9E
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 11:43:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TNwa-0006L1-61
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 11:36:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13310
	for <ietf@ietf.org>; Fri, 20 Jun 2003 11:36:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TNwZ-0005mB-00
	for ietf@ietf.org; Fri, 20 Jun 2003 11:36:51 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TNwY-0005m8-00
	for ietf@ietf.org; Fri, 20 Jun 2003 11:36:50 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5KFanc4000900
	for ietf@ietf.org env-from <vjs>;
	Fri, 20 Jun 2003 09:36:49 -0600 (MDT)
Date: Fri, 20 Jun 2003 09:36:49 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306201536.h5KFanc4000900@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
References: <20030620105420.73f8bbc9.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> ...
> the reason I point out the flaws with NAT is not that I think we can get
> rid of them in v4. it's because some people are still of the belief that
> NATs are mostly harmless and that we should not only permit them
> into v6, but extend our architecture to embrace them.  that's simply
> insane.

The current combatants seemed to fail to notice a long time ago when
those who started this thread by claiming NAT boxes are clearly good
and desirable things were convinced, or more likely, went elsewhere
to peddle their views.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri Jun 20 13:30:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18756
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 13:30:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TPTV-0002uC-4m
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 13:14:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TPLp-0001sh-NA
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 13:07:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17699
	for <ietf@ietf.org>; Fri, 20 Jun 2003 13:06:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TPLo-0006jr-00
	for ietf@ietf.org; Fri, 20 Jun 2003 13:07:00 -0400
Received: from tnt.isi.edu ([128.9.128.128])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TPLo-0006jo-00
	for ietf@ietf.org; Fri, 20 Jun 2003 13:07:00 -0400
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6p2/8.11.2) with ESMTP id h5KH6xK25803;
	Fri, 20 Jun 2003 10:06:59 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.9.3/8.8.6) id JAA16318;
	Fri, 20 Jun 2003 09:53:43 -0700 (PDT)
Date: Fri, 20 Jun 2003 09:53:43 -0700 (PDT)
Message-Id: <200306201653.JAA16318@gra.isi.edu>
To: ekr@rtfm.com
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

  *> do it. In the meantime, I wear a hat.
  *> 
  *> -Ekr
  *> 

Perhaps that was Keith's point... a hat as a cure for baldness is
akin to a NAT box as a cure for end system insecurity.

Bob Braden



From owner-ietf@ietf.org  Fri Jun 20 14:17:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21872
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 14:17:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TQEW-00021H-5M
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 14:03:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TQ5M-0000sv-GS
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 13:54:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20486
	for <ietf@ietf.org>; Fri, 20 Jun 2003 13:54:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TQ5L-0007LG-00
	for ietf@ietf.org; Fri, 20 Jun 2003 13:54:03 -0400
Received: from tomts23.bellnexxia.net ([209.226.175.185] helo=tomts23-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TQ5K-0007LA-00
	for ietf@ietf.org; Fri, 20 Jun 2003 13:54:02 -0400
Received: from yahoo.com ([65.93.181.94]) by tomts23-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030620175400.DGHZ15813.tomts23-srv.bellnexxia.net@yahoo.com>;
          Fri, 20 Jun 2003 13:54:00 -0400
Date: Fri, 20 Jun 2003 13:54:00 -0400
Subject: Fwd: myth of the great transition
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "'Keith Moore'" <moore@cs.utk.edu>
To: ietf@ietf.org
From: S Woodside <sbwoodside@yahoo.com>
Content-Transfer-Encoding: 7bit
Message-Id: <2C61E934-A348-11D7-A764-000393414368@yahoo.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Begin forwarded message:

> From: Keith Moore <moore@cs.utk.edu>
> Date: Thu Jun 19, 2003  8:43:18  PM America/Montreal
> To: S Woodside <sbwoodside@yahoo.com>
> Cc: moore@cs.utk.edu
> Subject: Re: myth of the great transition
>
>> OK, so let's say I'm the author of a voice over IP application on a
>> platform that supports IPv6, like, say, Mac OS X. What part of IPv6 is
>> going to make this work. I would need NAPT-replacement box to support
>> IPv6 as well, right? It would assign an IPv6 address to each of the
>> inner systems, and then ... what? I guess my caller who's trying to
>> phone me, I give her my IPv6 address. She connects to that address, 
>> and
>> her magic box sets up an IPv6 tunnel to my magic box automatically.
>> Then my magic box forwards the packets to the right machine in my
>> network.
>>
>> Add a firewall to that, and you've got something that replaces NAPT.
>>
>> I'm thinking maybe you could keep IPv4 NAPT as a legacy feature for
>> inside hosts and applications that don't support IPv6 yet. But apps
>> that do support IPv6, would not have to do any work to traverse the
>> NAPT.
>
> you've just described my router at home, I think.  except that there's 
> really
> no overhead in setting up a tunnel to your magic box - the sending 
> router
> just encapsulates the IPv6 packet within an IPv4 packet and sends it.
> there's no negotiation or per-tunnel state required.
>
> and yes, it does have NAPT as a legacy feature - I use it for web 
> browsing and
> reading email.
>
>

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Fri Jun 20 14:35:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25065
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 14:35:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TQXi-00065I-IH
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 14:23:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TQRG-0003mL-F0
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 14:16:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21844
	for <ietf@ietf.org>; Fri, 20 Jun 2003 14:16:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TQRF-0007fA-00
	for ietf@ietf.org; Fri, 20 Jun 2003 14:16:41 -0400
Received: from tomts26.bellnexxia.net ([209.226.175.189] helo=tomts26-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TQRE-0007f6-00
	for ietf@ietf.org; Fri, 20 Jun 2003 14:16:40 -0400
Received: from yahoo.com ([65.93.181.94]) by tomts26-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030620181638.LYKL28104.tomts26-srv.bellnexxia.net@yahoo.com>;
          Fri, 20 Jun 2003 14:16:38 -0400
Date: Fri, 20 Jun 2003 14:16:38 -0400
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <200306201148.h5KBmVAW017861@ginger.lcs.mit.edu>
Message-Id: <555470D4-A34B-11D7-A764-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Friday, June 20, 2003, at 07:48  AM, J. Noel Chiappa wrote:

> That group has no reason to deploy any new technology - what they have
> already works fine for them. So if there is a very large population of 
> N-U,
> especially if they are a big enough group to be a majority of the 
> Internet
> user base, then I think we're going to have to continue to 
> interoperate with
> those people.

A lot of these people would like to be voice users, which you grouped 
as NAPT Avoiders. They might use v6, if there were a dead-easy box that 
would make it work with v6, and the voice apps upgraded to v6, and the 
OS supports v6.

simon




From owner-ietf@ietf.org  Fri Jun 20 14:36:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25324
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 14:36:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TQb7-00007d-8O
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 14:26:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TQVq-0004lF-UF
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 14:21:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22183
	for <ietf@ietf.org>; Fri, 20 Jun 2003 14:21:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TQVp-0007kQ-00
	for ietf@ietf.org; Fri, 20 Jun 2003 14:21:25 -0400
Received: from tomts11.bellnexxia.net ([209.226.175.55] helo=tomts11-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TQVo-0007kM-00
	for ietf@ietf.org; Fri, 20 Jun 2003 14:21:24 -0400
Received: from yahoo.com ([65.93.181.94]) by tomts11-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030620182123.ZHYR25800.tomts11-srv.bellnexxia.net@yahoo.com>;
          Fri, 20 Jun 2003 14:21:23 -0400
Date: Fri, 20 Jun 2003 14:16:38 -0400
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <200306201148.h5KBmVAW017861@ginger.lcs.mit.edu>
Message-Id: <555470D4-A34B-11D7-A764-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Friday, June 20, 2003, at 07:48  AM, J. Noel Chiappa wrote:

> That group has no reason to deploy any new technology - what they have
> already works fine for them. So if there is a very large population of 
> N-U,
> especially if they are a big enough group to be a majority of the 
> Internet
> user base, then I think we're going to have to continue to 
> interoperate with
> those people.

A lot of these people would like to be voice users, which you grouped 
as NAPT Avoiders. They might use v6, if there were a dead-easy box that 
would make it work with v6, and the voice apps upgraded to v6, and the 
OS supports v6.

simon




From owner-ietf@ietf.org  Fri Jun 20 16:43:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07422
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 16:43:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TRvt-0006xx-RM
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 15:52:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TR1U-0002xf-3U
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 14:54:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27415
	for <ietf@ietf.org>; Fri, 20 Jun 2003 14:54:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TR1S-0000i6-00
	for ietf@ietf.org; Fri, 20 Jun 2003 14:54:06 -0400
Received: from tomts24.bellnexxia.net ([209.226.175.187] helo=tomts24-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TR1S-0000hq-00
	for ietf@ietf.org; Fri, 20 Jun 2003 14:54:06 -0400
Received: from yahoo.com ([65.93.181.94]) by tomts24-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030620185401.CSYK17571.tomts24-srv.bellnexxia.net@yahoo.com>;
          Fri, 20 Jun 2003 14:54:01 -0400
Date: Fri, 20 Jun 2003 14:53:59 -0400
Subject: replacing NAPT
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Daniel Senie <dts@senie.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <5.2.1.1.2.20030620144014.01b0e688@mail.amaranth.net>
Message-Id: <8D4EECF3-A350-11D7-A764-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Friday, June 20, 2003, at 02:48  PM, Daniel Senie wrote:

> At 02:16 PM 6/20/2003, you wrote:
>
>> A lot of these people would like to be voice users, which you grouped 
>> as NAPT Avoiders. They might use v6, if there were a dead-easy box 
>> that would make it work with v6, and the voice apps upgraded to v6, 
>> and the OS supports v6.
>
> They might go pay for vonage, which works fine with NAPT, and be 
> really happy. There are service vendors who are working with the 
> assumption that NAPT is pervasive. They'll win, while those who don't 
> take NAPT into account will have trouble. So while you say above a lot 
> of these folks using NAPT would like to be voice users, the reality is 
> they can.

But they have to pay for it. If you can sell them a $50 magic box that 
lets them use VoIP and NOT pay any monthly fees to Vonage, they will 
buy it.

simon




From owner-ietf@ietf.org  Fri Jun 20 16:44:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07516
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 16:44:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TRw5-0007W2-ER
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 15:52:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TRUX-00065V-1q
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 15:24:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02079
	for <ietf@ietf.org>; Fri, 20 Jun 2003 15:24:07 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TRUV-0001fv-00
	for ietf@ietf.org; Fri, 20 Jun 2003 15:24:07 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TRUU-0001fq-00
	for ietf@ietf.org; Fri, 20 Jun 2003 15:24:06 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h5KJO3cg004903;
	Fri, 20 Jun 2003 15:24:03 -0400
Message-Id: <200306201924.h5KJO3cg004903@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Daniel Senie <dts@senie.com>
Cc: ietf@ietf.org
Subject: Re: NATs are NOT Firewalls 
In-Reply-To: Your message of "Thu, 19 Jun 2003 03:57:40 EDT."
             <5.2.1.1.2.20030619034918.0268f4d0@mail.amaranth.net> 
References: <4B9CE103-A212-11D7-84BB-000393414368@yahoo.com>
            <5.2.1.1.2.20030619034918.0268f4d0@mail.amaranth.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_108387133P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 20 Jun 2003 15:24:03 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Thu, 19 Jun 2003 03:57:40 EDT, Daniel Senie <dts@senie.com>  said:

> Maybe YOU should read it, and explain how this is useful for attacking the 
> hosts behind a NAPT box. The technique described in this paper uses 
> variations in the IPid field as evidence of more than one host generating 
> packets. Fine. So you plunk a box just upstream of the NAT box, and now you 
> can determine how many ACTIVE hosts are talking to sites outside the NAPT box

*sigh*. OK. You're correct.  *BY ITSELF*, there's not much of an attack
vector here.  On the other hand, every hacker who has graduated from the
ranks of the ankle-biting script kiddies knows that target recon is something
that you want to do if feasible.

Information leakage makes it a lot easier....

Let's pretend you're a hacker.  You've found a box that you suspect is a NAT.
What's the FIRST thing you want to know? Yep - verify that it IS a NAT.  And lo
and behold, if you can enumerate more than one host behind it, it's probably a
NAT.

What's the second thing you probably want to know?  What techniques are likely
to work, of course.  And your choice of attack tools will quite likely be
swayed dramatically if you suspect there's only 3-4 boxes behind the NAT
because the NAT is a front end for a SOHO or similar, or if there's only 3-4
boxes because there's a DMZ behind it, or if you suspect there's hundreds back
there.

And all sorts of info leaks out in the oddest ways.  For instance, I save the
rfc822 headers from my mail.  So far in June, I've caught 38,836 Received:
lines from off-campus hosts, with 12,211 unique sources.  Of these, 2,597, from
409 different sources, contain an IP address literal from 1918 space.  Those
often give (a) a target IP inside the 1918 space and (b) the clue (dependent on
the MTA) that perhaps the site doesn't have care/clue enough to get PTR records
set up....



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

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

iD8DBQE+819TcC3lWbTT17ARAicLAJ45Cc41tNNdkI+EelSgbdEXa86uIwCfVG1T
dUhEdklMoBsOJGqOPJC+A2w=
=Htio
-----END PGP SIGNATURE-----

--==_Exmh_108387133P--



From owner-ietf@ietf.org  Fri Jun 20 17:05:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08783
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 17:05:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TSjj-0004cD-Id
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 16:43:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TSQJ-0001fQ-8d
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 16:23:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06567
	for <ietf@ietf.org>; Fri, 20 Jun 2003 16:23:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TSQH-0002p6-00
	for ietf@ietf.org; Fri, 20 Jun 2003 16:23:49 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TSQH-0002ov-00
	for ietf@ietf.org; Fri, 20 Jun 2003 16:23:49 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 081A8621FB
	for <ietf@ietf.org>; Fri, 20 Jun 2003 22:23:19 +0200 (CEST)
Date: Fri, 20 Jun 2003 22:23:11 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Checking if signed mail works now
Message-ID: <830990000.1056140591@askvoll.hjemme.alvestrand.no>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========2020771422=========="
Sender: owner-ietf@ietf.org
Precedence: bulk

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

A couple of systems at the secretariat were upgraded. I'm just curious to=20
see if we got the MIME-damaging bug as a side effect.

(btw, if you saw major delays on IETF lists recently - the upgrade was the=20
result of observing the delay. It shouldn't be happening any more.)

          Harald
--==========2020771422==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

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

iD8DBQE+8203OMj+2+WY0F4RAtw3AJ9T11405tEkGKS3z0jZvFVHN6nS1wCfTFeX
myIhiDe8a1+4cLDDqIR1X+4=
=RQnl
-----END PGP SIGNATURE-----

--==========2020771422==========--




From owner-ietf@ietf.org  Fri Jun 20 20:12:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15053
	for <ietf-web-archive@odin.ietf.org>; Fri, 20 Jun 2003 20:12:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TViy-0002UO-4j
	for ietf-list@asgard.ietf.org; Fri, 20 Jun 2003 19:55:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TVaQ-0002C0-B1
	for ietf@asgard.ietf.org; Fri, 20 Jun 2003 19:46:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14664
	for <ietf@ietf.org>; Fri, 20 Jun 2003 19:46:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TVaO-0004PX-00
	for ietf@ietf.org; Fri, 20 Jun 2003 19:46:28 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TVaO-0004PC-00
	for ietf@ietf.org; Fri, 20 Jun 2003 19:46:28 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.19.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA04301;
	Fri, 20 Jun 2003 19:44:46 -0400
Date: Fri, 20 Jun 2003 19:44:47 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Valdis.Kletnieks@vt.edu
cc: Daniel Senie <dts@senie.com>, <ietf@ietf.org>
Subject: Re: NATs are NOT Firewalls 
In-Reply-To: <200306201924.h5KJO3cg004903@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0306201930520.19409-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


Hackers first crack the exposed host. Then they see if it has multiple
interfaces. The local ARP cache will tell them the RFC1918 addresses if it
is a NAT.

The "NAT" just clusters several machines together in one machine.

Whether there are multiple machines behind a NAT is of little consequence.
Those machines that have exploitable ports available are still
exploitable. A good example is HTTP buffer overflows. A number of NATs
will happily forward the overflow attacks right through to the web server,
which is still exploited. SIP phones are similarly exploitable.

And how many NATs will forward external packets addressed to RFC1918 space
between both interfaces?  A lot used to. The limited access depended on
the assertion that RFC1918 packets couldn't be transmitted beyond the
external interface due to routing configuration. This assertion cannot be
guaranteed.  Change that routing, and there is frequently complete
transparancy.  But the fact that it doesn't usually work has caused many
people to make the false assumption that it can't ever work, and wrongly
conclude that NAT is an access control device when it isn't.


		--Dean


On Fri, 20 Jun 2003 Valdis.Kletnieks@vt.edu wrote:

> On Thu, 19 Jun 2003 03:57:40 EDT, Daniel Senie <dts@senie.com>  said:
>
> > Maybe YOU should read it, and explain how this is useful for attacking the
> > hosts behind a NAPT box. The technique described in this paper uses
> > variations in the IPid field as evidence of more than one host generating
> > packets. Fine. So you plunk a box just upstream of the NAT box, and now you
> > can determine how many ACTIVE hosts are talking to sites outside the NAPT box
>
> *sigh*. OK. You're correct.  *BY ITSELF*, there's not much of an attack
> vector here.  On the other hand, every hacker who has graduated from the
> ranks of the ankle-biting script kiddies knows that target recon is something
> that you want to do if feasible.
>
> Information leakage makes it a lot easier....
>
> Let's pretend you're a hacker.  You've found a box that you suspect is a NAT.
> What's the FIRST thing you want to know? Yep - verify that it IS a NAT.  And lo
> and behold, if you can enumerate more than one host behind it, it's probably a
> NAT.
>
> What's the second thing you probably want to know?  What techniques are likely
> to work, of course.  And your choice of attack tools will quite likely be
> swayed dramatically if you suspect there's only 3-4 boxes behind the NAT
> because the NAT is a front end for a SOHO or similar, or if there's only 3-4
> boxes because there's a DMZ behind it, or if you suspect there's hundreds back
> there.
>
> And all sorts of info leaks out in the oddest ways.  For instance, I save the
> rfc822 headers from my mail.  So far in June, I've caught 38,836 Received:
> lines from off-campus hosts, with 12,211 unique sources.  Of these, 2,597, from
> 409 different sources, contain an IP address literal from 1918 space.  Those
> often give (a) a target IP inside the 1918 space and (b) the clue (dependent on
> the MTA) that perhaps the site doesn't have care/clue enough to get PTR records
> set up....
>
>
>




From owner-ietf@ietf.org  Sat Jun 21 12:13:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10637
	for <ietf-web-archive@odin.ietf.org>; Sat, 21 Jun 2003 12:13:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TkfR-0000M3-F0
	for ietf-list@asgard.ietf.org; Sat, 21 Jun 2003 11:52:41 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Tkee-0000Lc-71
	for ietf@asgard.ietf.org; Sat, 21 Jun 2003 11:51:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10291
	for <ietf@ietf.org>; Sat, 21 Jun 2003 11:51:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Tked-00001B-00
	for ietf@ietf.org; Sat, 21 Jun 2003 11:51:51 -0400
Received: from d235-158-148.home1.cgocable.net ([24.235.158.148] helo=dot-god.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Tkec-000018-00
	for ietf@ietf.org; Sat, 21 Jun 2003 11:51:50 -0400
Received: from baptista (helo=localhost)
	by dot-god.com with local-esmtp (Exim 4.12)
	id 19Tkek-0000Uy-00; Sat, 21 Jun 2003 11:51:58 -0400
Date: Sat, 21 Jun 2003 11:51:58 -0400 (EDT)
From: Joe Baptista <baptista@dot-god.com>
To: <isp-wireless@isp-wireless.com>
cc: <ietf@ietf.org>
Subject: UWB - Ultra Wide Band - still experimental
Message-ID: <Pine.LNX.4.33.0306211145150.23377-100000@dot-god.com>
Organization: .GOD domains @ www.dot-god.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


Hi Folk:

I'm investigating Ultra Wide Band and TCP/IP applications.

Anyone here heard of UWB - ultra wide band.  A technology which looks to
have alot of potential to support TCP/IP protocols.  Unfortunately so far
all i have found are a few research papers - some news hype - and your FCC
regulations in the making but not much in the area of working networks
using UWB nor equipment.

Can anyone give me some pointers on equipment available, and pretty well
anything else which might be helpful from a tcp/ip point of view .. etc.
etc.

thanks
joe

---------- Forwarded message ----------
Date: Sat, 21 Jun 2003 11:43:34 -0400 (EDT)
From: Joe Baptista <baptista@dot-god.com>
To: Robert Ross
Subject: ultra wide band - still experimental


from what i have seen any commerical application is mainly experimental -
still.  I checked the ietf www.ietf.org for transmission or protocol
standards and there are non listed in the RFC directories.

the only standard so far in development relates to packet transmission
over uwb.  the potential is enormous but also the FCC is trying to
regulate UWB.  without a detailed review of the FCC regulations all i can
say is they look rushed - based on my initial examination yesturday.

i'm on a wifi email list i'll ask their opinions and see if i can get some
better focus on it.

regards
joe

Joe Baptista - only at www.baptista.god

  Free Tibet http://free.tibet/





From owner-ietf@ietf.org  Sat Jun 21 17:41:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16097
	for <ietf-web-archive@odin.ietf.org>; Sat, 21 Jun 2003 17:41:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TpxS-0002wN-Vh
	for ietf-list@asgard.ietf.org; Sat, 21 Jun 2003 17:31:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TpwY-0002vp-RO
	for ietf@asgard.ietf.org; Sat, 21 Jun 2003 17:30:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15951
	for <ietf@ietf.org>; Sat, 21 Jun 2003 17:30:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TpwX-000193-00
	for ietf@ietf.org; Sat, 21 Jun 2003 17:30:41 -0400
Received: from cyphermail.sandelman.ottawa.on.ca ([192.139.46.78] helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TpwW-000190-00
	for ietf@ietf.org; Sat, 21 Jun 2003 17:30:40 -0400
Received: from lox.sandelman.ottawa.on.ca (IDENT:root@lox.sandelman.ottawa.on.ca [192.139.46.2])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p2/8.11.6) with ESMTP id h5LLUaq08091
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO)
	for <ietf@ietf.org>; Sat, 21 Jun 2003 17:30:38 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca [192.139.46.20])
	by lox.sandelman.ottawa.on.ca (8.11.6/8.11.6) with ESMTP id h5LLWGT00798
	for <ietf@ietf.org>; Sat, 21 Jun 2003 17:32:16 -0400 (EDT)
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian -4) with ESMTP id h5LLUPT4021755
	for <ietf@ietf.org>; Sat, 21 Jun 2003 17:30:25 -0400
Message-Id: <200306212130.h5LLUPT4021755@sandelman.ottawa.on.ca>
To: ietf@ietf.org
Subject: Re: primary purpose of firewalls 
In-reply-to: Your message of "Thu, 19 Jun 2003 22:00:48 EDT."
             <20030619220048.1adee4de.moore@cs.utk.edu> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Sat, 21 Jun 2003 17:30:24 -0400
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-ietf@ietf.org
Precedence: bulk

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


>>>>> "Keith" == Keith Moore <moore@cs.utk.edu> writes:
    Keith> OTOH, the network cannot expect hosts to protect it; it must
    Keith> protect itself. that's why I say that the primary purpose of
    Keith> firewalls is to protect the network. if the firewall can also
    Keith> provide security in depth for hosts, that's useful, but that's
    Keith> just a backup - there's no way to have confidence in the 
    Keith> security of a host that relies on firewalls as its primary means of
    Keith> protection. 

  As former lead developer at an early firewall company, who made lots of
money selling firewalls before the age of the LookOut-Virus, I concur with
Keith. 

  Firewalls are about *belt and suspenders*
  They can provide auditing functions as well (and I still think that
this is the main argument for them), but firewall vendors have screwed that
up so badly, that this is now better done by dedicated IDS. 

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

iQCVAwUBPvTOboqHRg3pndX9AQGFgAQA1m1XL2TgV/9FX8GPLvzZe7Wr8qW1fsF5
GDsNcXTTlZDu0f7l4Ov/fXDzyRhWzLyo0J1Im2SVJ1Bf40JtRp2SqMYbbtS9IO8a
YHc6S6vjSE0UQpXwbfsFWSmqYXO2FBVQ1DCTfeelkF9vZv0eJTRxh6i3Z8hCCLaq
RgP+FILHAxc=
=1VN1
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Sat Jun 21 20:38:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19255
	for <ietf-web-archive@odin.ietf.org>; Sat, 21 Jun 2003 20:38:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Tsgn-0002eW-LF
	for ietf-list@asgard.ietf.org; Sat, 21 Jun 2003 20:26:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Tsgm-0002dx-9K
	for ietf@asgard.ietf.org; Sat, 21 Jun 2003 20:26:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19044
	for <ietf@ietf.org>; Sat, 21 Jun 2003 20:26:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Tsgk-0001bM-00
	for ietf@ietf.org; Sat, 21 Jun 2003 20:26:34 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Tsgj-0001bJ-00
	for ietf@ietf.org; Sat, 21 Jun 2003 20:26:33 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h5M0Hts15168
	for <ietf@ietf.org>; Sat, 21 Jun 2003 17:17:55 -0700
Date: Sat, 21 Jun 2003 17:17:54 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
Subject: Re: primary purpose of firewalls
In-Reply-To: <20030620002532.41c0df95.moore@cs.utk.edu>
Message-ID: <Pine.LNX.4.33.0306211705040.14478-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Fri, 20 Jun 2003, Keith Moore wrote:

> still, pretending that a firewall can make up for a lack of security on the
> host (ANY host) or in the apps is simply unrealistic, no matter who wrote the
> host OS.

That statement is simply not true. Based on policies that reject inbound
connections to all computers except those carefully hardended and
sequestered an their own 'DMZ' will dramatically reduce the potential of
compromize from many risky applications ranging from TELNET on Solaris to
SMB on Windows.

More sophisticated firewalls examine data flow for viruses, and other
problematic code.

Securing networks and hosts requires a whole quiver of arrows. A competent
firewall is a significant set of arrows but can't solve the whole problem.
But it will makeup for many security flaws in the hosts and/or
applications. Potential problems can be reduced to almost 0 if careful
users avoid risky behaviors and live behind a solid firewall.

Sure there will be things they can't do, but there are a wealth of things
then can safely do thanks to the Internet accessed thru a firewall.

Dave Morris




From owner-ietf@ietf.org  Sat Jun 21 22:15:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20640
	for <ietf-web-archive@odin.ietf.org>; Sat, 21 Jun 2003 22:15:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Tu8n-000441-9R
	for ietf-list@asgard.ietf.org; Sat, 21 Jun 2003 21:59:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Tu8V-00043K-Jq
	for ietf@asgard.ietf.org; Sat, 21 Jun 2003 21:59:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20443
	for <ietf@ietf.org>; Sat, 21 Jun 2003 21:59:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Tu8T-0001wF-00
	for ietf@ietf.org; Sat, 21 Jun 2003 21:59:17 -0400
Received: from tomts23.bellnexxia.net ([209.226.175.185] helo=tomts23-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Tu8R-0001wB-00
	for ietf@ietf.org; Sat, 21 Jun 2003 21:59:16 -0400
Received: from yahoo.com ([65.93.181.230]) by tomts23-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030622015903.VLIH15813.tomts23-srv.bellnexxia.net@yahoo.com>;
          Sat, 21 Jun 2003 21:59:03 -0400
Date: Sat, 21 Jun 2003 21:59:02 -0400
Subject: Re: primary purpose of firewalls
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <ietf@ietf.org>
To: David Morris <dwm@xpasc.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <Pine.LNX.4.33.0306211705040.14478-100000@egate.xpasc.com>
Message-Id: <1892857A-A455-11D7-B9E0-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Saturday, June 21, 2003, at 08:17  PM, David Morris wrote:

> Based on policies that reject inbound
> connections to all computers except those carefully hardended and
> sequestered an their own 'DMZ' will dramatically reduce the potential 
> of
> compromize from many risky applications ranging from TELNET on Solaris 
> to
> SMB on Windows.

It would be just as hard to traverse that firewall, then (for voice), 
as it would be to traverse a NAPT, no?

simon


--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Sat Jun 21 22:58:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21172
	for <ietf-web-archive@odin.ietf.org>; Sat, 21 Jun 2003 22:58:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Tux7-00063W-43
	for ietf-list@asgard.ietf.org; Sat, 21 Jun 2003 22:51:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Tux2-00062o-LD
	for ietf@asgard.ietf.org; Sat, 21 Jun 2003 22:51:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21088
	for <ietf@ietf.org>; Sat, 21 Jun 2003 22:51:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Tux0-00027E-00
	for ietf@ietf.org; Sat, 21 Jun 2003 22:51:30 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Tuwz-00027B-00
	for ietf@ietf.org; Sat, 21 Jun 2003 22:51:29 -0400
Subject: RE: primary purpose of firewalls 
Date: Sat, 21 Jun 2003 19:51:34 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8C3@server2000.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: primary purpose of firewalls 
Thread-Index: AcM4PfxW4HX0xFiRRjyfk+2jHJLjPQAKnKLQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Michael Richardson" <mcr@sandelman.ottawa.on.ca>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Michael Richardson wrote:
> but firewall vendors have screwed that up so badly, that
> this is now better done by dedicated IDS.

I don't pretend to be a firewall expert but the IDS I use (and pasted
examples of earlier) is built-in the firewall and works for my needs. I
don't care much about an IDS that generates 100 alarms per second, the
reason being I have not enough qualified staff to analyze 100 IDS alarms
per second. IDS systems that generate tons of alarms are primarily a
means of selling an IDS system to the unsuspecting decision maker that
does not know jack about them.

Michel.




From owner-ietf@ietf.org  Sun Jun 22 01:36:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23666
	for <ietf-web-archive@odin.ietf.org>; Sun, 22 Jun 2003 01:36:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Tvzw-000780-VV
	for ietf-list@asgard.ietf.org; Sat, 21 Jun 2003 23:58:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Tvz6-00077K-Jp
	for ietf@asgard.ietf.org; Sat, 21 Jun 2003 23:57:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22266
	for <ietf@ietf.org>; Sat, 21 Jun 2003 23:57:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Tvz4-0002Nl-00
	for ietf@ietf.org; Sat, 21 Jun 2003 23:57:42 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Tvz3-0002Nh-00
	for ietf@ietf.org; Sat, 21 Jun 2003 23:57:41 -0400
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h5M3n4s15593;
	Sat, 21 Jun 2003 20:49:04 -0700
Date: Sat, 21 Jun 2003 20:49:03 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: S Woodside <sbwoodside@yahoo.com>
cc: <ietf@ietf.org>
Subject: Re: primary purpose of firewalls
In-Reply-To: <1892857A-A455-11D7-B9E0-000393414368@yahoo.com>
Message-ID: <Pine.LNX.4.33.0306212040190.14478-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Sat, 21 Jun 2003, S Woodside wrote:

> On Saturday, June 21, 2003, at 08:17  PM, David Morris wrote:
>
> > Based on policies that reject inbound
> > connections to all computers except those carefully hardended and
> > sequestered an their own 'DMZ' will dramatically reduce the potential
> > of
> > compromize from many risky applications ranging from TELNET on Solaris
> > to
> > SMB on Windows.
>
> It would be just as hard to traverse that firewall, then (for voice),
> as it would be to traverse a NAPT, no?

In the case of the product I use, 'NAPT' is a default behavior, but
alternate configurations are possible including no NAT. Opening inbound
connections to arbitrary hosts is always a risk since there are many
reasons that one can't trust the security status of desktop machines for
at least some percentage of the user population. I'm certainly not ready
to allow connection to any application I know of from outside of my
firewall when I can't control the machine.

So I guess my short answer is I hope so.

Dave Morris




From owner-ietf@ietf.org  Sun Jun 22 04:19:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07414
	for <ietf-web-archive@odin.ietf.org>; Sun, 22 Jun 2003 04:19:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19TxO4-00087D-N5
	for ietf-list@asgard.ietf.org; Sun, 22 Jun 2003 01:27:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19TxNs-00086U-BT
	for ietf@asgard.ietf.org; Sun, 22 Jun 2003 01:27:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23612
	for <ietf@ietf.org>; Sun, 22 Jun 2003 01:27:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19TxNq-0002k2-00
	for ietf@ietf.org; Sun, 22 Jun 2003 01:27:22 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19TxNf-0002jz-00
	for ietf@ietf.org; Sun, 22 Jun 2003 01:27:11 -0400
Received: from [147.28.0.62] (helo=127.0.0.1 ident=zinin)
	by psg.com with esmtp (Exim 4.14)
	id 19TxNM-0009F4-At
	for ietf@ietf.org; Sun, 22 Jun 2003 05:26:52 +0000
Date: Sat, 21 Jun 2003 22:26:35 -0700
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: <68108272848.20030621222635@psg.com>
To: ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
In-Reply-To: <Pine.LNX.4.44.0306180924460.4731-100000@netcore.fi>
References: <Pine.LNX.4.44.0306180924460.4731-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks-

 Having watched this discussion, it seems a couple of data points
 might be helpful:

 1. L2VPN and L3VPN proposed WGs are part of PPVPN WG split

    Creation of L2VPN and L3VPN WG does not represent addition of new
    work to the IETF. They are created as part of the process of
    splitting the PPVPN WG to improve progress and focus it by setting
    clear directions in the charters.

 2. L2VPN work is already chartered within the IETF

    The discussion about whether this work should be chartered or not
    happened when the PPVPN WG was being created. Please see minutes
    and slides from the PPVPN BOF at IETF 49. L2VPN solutions are
    within the PPVPN charter and milestones.

 Hope this helps.

Alex




From owner-ietf@ietf.org  Sun Jun 22 20:50:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23006
	for <ietf-web-archive@odin.ietf.org>; Sun, 22 Jun 2003 20:50:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UB5i-0001Y9-9E
	for ietf-list@asgard.ietf.org; Sun, 22 Jun 2003 16:05:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UB5I-0001Xg-4O
	for ietf@asgard.ietf.org; Sun, 22 Jun 2003 16:05:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17508
	for <ietf@ietf.org>; Sun, 22 Jun 2003 16:04:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UB4I-0005IC-00
	for ietf@ietf.org; Sun, 22 Jun 2003 16:04:06 -0400
Received: from cyphermail.sandelman.ottawa.on.ca ([192.139.46.78] helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx with esmtp (Exim 4.12)
	id 19UB43-0005I4-00
	for ietf@ietf.org; Sun, 22 Jun 2003 16:03:51 -0400
Received: from lox.sandelman.ottawa.on.ca (IDENT:root@lox.sandelman.ottawa.on.ca [192.139.46.2])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p2/8.11.6) with ESMTP id h5MK1vq12231
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO);
	Sun, 22 Jun 2003 16:02:00 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca [192.139.46.20])
	by lox.sandelman.ottawa.on.ca (8.11.6/8.11.6) with ESMTP id h5MK3Zt04049;
	Sun, 22 Jun 2003 16:03:36 -0400 (EDT)
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian -4) with ESMTP id h5MK1et1018976;
	Sun, 22 Jun 2003 16:01:40 -0400
Message-Id: <200306222001.h5MK1et1018976@sandelman.ottawa.on.ca>
To: postmaster@alcatel.com, dns-tech@alcatel.com, dns-admin@alcatel.com,
        alain.sabban@alcatel.fr, hostmaster@alcanet.no
cc: info@cira.ca, ietf@ietf.org
Subject: non-complain mail system at alcatel.com
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Sun, 22 Jun 2003 16:01:39 -0400
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-ietf@ietf.org
Precedence: bulk

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


Alcatel.com does not have a functional email system. It believes that
all domains must have full NS-record delegations. I.e. that my domain
"sandelman.ottawa.on.ca" must be a delegation from "ottawa.on.ca",
rather than from "ca". (The .CA namespace has a single ccTLD)

I have contacted Alcatel repeatedly by email and by phone in the
past months, and I have gotten no response to this. A major problem is that 
I think that only one of their MX's has this behaviour.

So, I'm resorting to the only other way I have - embarassment.

Specifically, it says:

The original message was received at Sat, 21 Jun 2003 14:27:27 -0400 (EDT)
from IDENT:root@lox.sandelman.ottawa.on.ca [192.139.46.2]

   ----- The following addresses had permanent fatal errors -----
<Donna.Hogan@alcatel.com>
    (reason: 550 sender ignored: ottawa.on.ca does not have a name server record)

   ----- Transcript of session follows -----
... while talking to primary.alcatel.com.:
>>> MAIL From:<mcr@sandelman.ottawa.on.ca>
<<< 550 sender ignored: ottawa.on.ca does not have a name server record
554 5.0.0 Service unavailable

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBPvYLIYqHRg3pndX9AQH+1QP/fe0rInX+kaX3QQFFlnF6qNEzDyVGsTcf
NptzvtrzSUqQC1TMXYMII25nkvk4G2p73qWDxmoTxGhax/CYhJyZwPfPpLO/AqV9
Nl8wmGE6sLMMCorgsX+O52Q5Rdni/LK/yMz0RYf/wkZnhIBTpqINww6TtANnsAZ5
RkOSQjDwrLc=
=7AxR
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Mon Jun 23 02:54:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10879
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 02:54:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UI89-0003n0-39
	for ietf-list@asgard.ietf.org; Sun, 22 Jun 2003 23:36:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UI7B-0003mi-5A
	for ietf@asgard.ietf.org; Sun, 22 Jun 2003 23:35:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25274
	for <ietf@ietf.org>; Sun, 22 Jun 2003 23:35:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UI79-0006rO-00
	for ietf@ietf.org; Sun, 22 Jun 2003 23:35:31 -0400
Received: from flamingo.mail.pas.earthlink.net ([207.217.120.232])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UI6y-0006rD-00
	for ietf@ietf.org; Sun, 22 Jun 2003 23:35:20 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by flamingo.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19UI6U-0004Vj-00; Sun, 22 Jun 2003 20:34:50 -0700
Date: Sun, 22 Jun 2003 23:31:40 -0400
From: Keith Moore <moore@cs.utk.edu>
To: David Morris <dwm@xpasc.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: primary purpose of firewalls
Message-Id: <20030622233140.74ecc19a.moore@cs.utk.edu>
In-Reply-To: <Pine.LNX.4.33.0306211705040.14478-100000@egate.xpasc.com>
References: <20030620002532.41c0df95.moore@cs.utk.edu>
	<Pine.LNX.4.33.0306211705040.14478-100000@egate.xpasc.com>
X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > still, pretending that a firewall can make up for a lack of security on
> > the host (ANY host) or in the apps is simply unrealistic, no matter who
> > wrote the host OS.
> 
> That statement is simply not true. Based on policies that reject inbound
> connections to all computers except those carefully hardended and
> sequestered an their own 'DMZ' will dramatically reduce the potential of
> compromize from many risky applications ranging from TELNET on Solaris to
> SMB on Windows.

actually, it sounds like you're agreeing with me.  you're having the firewall
completely block traffic except to those hosts that you trust to provide
adequate security.  my only question would be whether there are threats behind
your firewall, e.g. any machine that runs windows and is used to read email.

> More sophisticated firewalls examine data flow for viruses, and other
> problematic code.
> 
> Securing networks and hosts requires a whole quiver of arrows. A competent
> firewall is a significant set of arrows but can't solve the whole problem.
> But it will makeup for many security flaws in the hosts and/or
> applications.

yes indeed.  my point is that it's still not good enough to make those hosts
secure.  and sometimes those sophisticated firewalls break protocol
interoperation even when they're trying to permit the traffic.

> Potential problems can be reduced to almost 0 if careful
> users avoid risky behaviors and live behind a solid firewall.
> 
> Sure there will be things they can't do, but there are a wealth of things
> then can safely do thanks to the Internet accessed thru a firewall.

all I can say is I'm glad I don't have to depend on you to secure my networks.

Keith




From owner-ietf@ietf.org  Mon Jun 23 11:25:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24367
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 11:25:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19URdT-0001RF-Ir
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 09:45:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19URdL-0001Qh-PM
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 09:45:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20266
	for <ietf@ietf.org>; Mon, 23 Jun 2003 09:45:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19URd6-0002JP-00
	for ietf@ietf.org; Mon, 23 Jun 2003 09:45:08 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19URcv-0002Iv-00
	for ietf@ietf.org; Mon, 23 Jun 2003 09:44:57 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h5NDiQtU011075;
	Mon, 23 Jun 2003 09:44:26 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h5NDiQA2011074;
	Mon, 23 Jun 2003 09:44:26 -0400
Date: Mon, 23 Jun 2003 09:44:26 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200306231344.h5NDiQA2011074@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

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

    >>> the reason I point out the flaws with NAT is .. because some people
    >>> are still of the belief that NATs are mostly harmless and that we
    >>> should not only permit them into v6, but extend our architecture to
    >>> embrace them.

    >> Keith, that's not the only reason, and you know it. You want to point
    >> out to people how screwed up NAT's are in the hope that they will be
    >> more inclined to move *from* IPv4+NAT *to* your perfect future, one in
    >> which we once again have a global namespace.

    > when you try to guess what my motivations are, you are likely to be
    > wrong enough that you'll misrepresent them. 

OK, so I'm wrong - and you have nothing to say against NAT if we are only
proposing to use IPv4+NAT, and have no intention of adding NAT to IPv6?

	Noel




From owner-ietf@ietf.org  Mon Jun 23 11:25:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24334
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 11:25:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UQQx-0000px-Pu
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 08:28:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UQQd-0000pQ-Ew
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 08:28:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17967
	for <ietf@ietf.org>; Mon, 23 Jun 2003 08:27:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UQQN-0001mX-00
	for ietf@ietf.org; Mon, 23 Jun 2003 08:27:55 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UQQD-0001mU-00
	for ietf@ietf.org; Mon, 23 Jun 2003 08:27:45 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h5NCRNtU010670;
	Mon, 23 Jun 2003 08:27:23 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h5NCRNUN010669;
	Mon, 23 Jun 2003 08:27:23 -0400
Date: Mon, 23 Jun 2003 08:27:23 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200306231227.h5NCRNUN010669@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Michael Thomas <mat@cisco.com>

    > we're being driven as a community to do both with the ensuing insanity
    > of two broken models being forced to cohabitate, all the while neither
    > meeting the actual requirements.

Time to hit the "reset" button on our current direction, I would say.

    > So just saying that NAT is here get used to it is, architecturally, not
    > helpful. .. more importantly the net is becoming more and more
    > incomprehensible because of it, both intellectually as well as
    > operationally.
    > ..
    > saying "get used to it" is a weird position because it discounts the
    > problems of the status quo and doesn't really express any vision for
    > what the architecture *ought* to be

Look, in my comments about NAT, I'm *not* saying "just get used to the
current level of poor design", we're stuck. What I am saying is that it's
time to stop acting like NAT is this awful icky thing that we refuse to touch
in any way because it's so bad, and that if we stick our heads in the sand
hard enough it will go away. It won't.

Here, again, is the nub of what we have to deal with:

    >> The notion of a system with a single, globally unique namespace at the
    >> lowest level is a really nice one, one we had for a while - and *one
    >> we think we can reclaim*. I now think we've been deluding ourselves;
    >> that past .. is gone for good.

How would I move forward from there, constructively, to try and produce a
less broken architecture/system?


The very first thing I would so would be to actually write a "NAT spec" (or
perhaps a small number of them, for different flavours that are useful in
different ways).

There are many different flavors of NAT, and so it's hard to make an
application "work with NAT" when you don't know exactly what the NAT box is
going to do. E.g. the recent point about most NAT boxes being port mappers,
not address mappers - I don't know about that, actually, and none of the NAT
boxes I've seen come with specs that say *exactly* what they do.

For another example:

    > Voice is one trend and it pretty fundamentally challenges one of the
    > base assumptions of NAT: private-client/public-server. But instead of
    > realizing that NAT is architecturally incapable of dealing with private
    > servers

That's true of the current crop of NAT boxes, but the first NAT boxes (both
Paul Tsuchuchiya's and Van Jacobsen's) did indeed handle incoming connections
(albeit in a really ugly way, by intercepting incoming DNS requests and
modifying the responses, and setting up external->internal mappings based on
that.) The little boxes people running home networks use don't do that.

We first need to really get a definitive handle on what these things are
doing.


The next step would be to add a "NAT considerations" section to all protocol
specifications, just like the "Security considerations" we have now.
Protocols can be designed to be less NAT-hostile - e.g. no giving addresses
to third parties as a way to contact someone, etc.

NAT boxes are here, and are very widespread, and will be for a long time to
come, and it's doing the users (not to mention the IETF) a tremdous
disservice to roll out protocols that won't work with NAT boxes.


Finally, there are some hard technical issues involved with NAT we need to
think about.

We can, if we feel its needed, define a new namespace which is used for
long-term identification of entities, and deploy that on an
application-by-application basis for new applications.

(I've thought about how to modify existing transport protocols on an
upwardly-compatible basis to use such a global namespace for entities, and it
can be done [I have a complete draft spec for TCP]. However, I don't think
that's very useful - too many old installations will remain. I think the same
logic applies to old applications. So only new applications, I think.)

The big problem is incoming connections - how do you set up the mappings they
will need? Wiretapping DNS is ugly, but it doesn't require changing anything
(for existing applications). On the other hand, if you only want to support
incoming connections for new applications, you can define them to include
some sort of MidCom-like setup.


    > We want an architecture that meets all of the requirements, not a
    > hodgepodge of half solutions which fall over in the first stiff breeze.

Nothing positive can happen as long as we keep acting as NAT i) is too
disgusting to seriously try and deal with, and ii) will go away if we stick
our heads in the sand hard enough

	Noel



From owner-ietf@ietf.org  Mon Jun 23 11:25:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24349
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 11:25:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19URCN-0001DW-Jo
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 09:17:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19URBn-0001D8-09
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 09:16:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19427
	for <ietf@ietf.org>; Mon, 23 Jun 2003 09:16:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19URBm-00026w-00
	for ietf@ietf.org; Mon, 23 Jun 2003 09:16:54 -0400
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19URBb-00024z-00
	for ietf@ietf.org; Mon, 23 Jun 2003 09:16:43 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19UR9k-0001mH-00; Mon, 23 Jun 2003 06:14:49 -0700
Date: Mon, 23 Jun 2003 09:11:37 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030623091137.41c7f866.moore@cs.utk.edu>
In-Reply-To: <200306231258.h5NCwuru010865@ginger.lcs.mit.edu>
References: <200306231258.h5NCwuru010865@ginger.lcs.mit.edu>
X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>     > the reason I point out the flaws with NAT is not that I think we can
>     > get rid of them in v4. it's because some people are still of the
>     > belief that NATs are mostly harmless and that we should not only
>     > permit them into v6, but extend our architecture to embrace them.
> 
> Keith, that's not the only reason, and you know it. You want to point out to
> people how screwed up NAT's are in the hope that they will be more inclined
> to move *from* IPv4+NAT *to* your perfect future, one in which we once again
> have a global namespace.

Noel,

I have immense respect for you.  But even as smart as you are - when you try
to guess what my motivations are, you are likely to be wrong enough that
you'll misrepresent them.

> IPv4+NAT, as ugly as it is, is the future. Now can we please stop sticking
> our heads in the sand, and start dealing with that?

We *are* dealing with that.  And the fix is called using IPv6 alongside
IPv4+NAT.  Because all of the other fixes are even harder to deploy and less
likely to work.

Keith




From owner-ietf@ietf.org  Mon Jun 23 11:25:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24333
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 11:25:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UQq7-00010f-FK
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 08:54:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UPQ8-0000Tp-Uw
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 07:23:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16429
	for <ietf@ietf.org>; Mon, 23 Jun 2003 07:22:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UPOl-0001Sc-00
	for ietf@ietf.org; Mon, 23 Jun 2003 07:22:11 -0400
Received: from pmesmtp02.wcom.com ([199.249.20.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UPOa-0001Rj-00
	for ietf@ietf.org; Mon, 23 Jun 2003 07:22:00 -0400
Received: from pmismtp03.wcomnet.com ([166.38.62.38])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HGX00KAMLUSFB@firewall.wcom.com> for ietf@ietf.org; Mon,
 23 Jun 2003 11:13:40 +0000 (GMT)
Received: from pmismtp03.wcomnet.com by pmismtp03.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HGX00L01LUSVU@pmismtp03.wcomnet.com>; Mon,
 23 Jun 2003 11:13:40 +0000 (GMT)
Received: from vint.mci.com ([166.50.96.45])
 by pmismtp03.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HGX00JNELUMEJ@pmismtp03.wcomnet.com>; Mon,
 23 Jun 2003 11:13:40 +0000 (GMT)
Date: Mon, 23 Jun 2003 06:26:03 -0400
From: "vinton g. cerf" <vinton.g.cerf@mci.com>
Subject: Re: non-complain mail system at alcatel.com
In-reply-to: <200306222001.h5MK1et1018976@sandelman.ottawa.on.ca>
X-Sender: vcerf@pop.mcilink.com
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>, postmaster@alcatel.com,
        dns-tech@alcatel.com, dns-admin@alcatel.com, alain.sabban@alcatel.fr,
        hostmaster@alcanet.no
Cc: info@cira.ca, ietf@ietf.org
Message-id: <5.2.0.9.2.20030623062509.047f9ac8@pop.mcilink.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Content-type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

I would be interested to know whether Alcatel really believes that DNS behaves in such a way that one MUST delegate at each "dot" - as far as I know, it is NOT required to do so.

vint

At 04:01 PM 6/22/2003 -0400, Michael Richardson wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>
>
>Alcatel.com does not have a functional email system. It believes that
>all domains must have full NS-record delegations. I.e. that my domain
>"sandelman.ottawa.on.ca" must be a delegation from "ottawa.on.ca",
>rather than from "ca". (The .CA namespace has a single ccTLD)
>
>I have contacted Alcatel repeatedly by email and by phone in the
>past months, and I have gotten no response to this. A major problem is that 
>I think that only one of their MX's has this behaviour.
>
>So, I'm resorting to the only other way I have - embarassment.
>
>Specifically, it says:
>
>The original message was received at Sat, 21 Jun 2003 14:27:27 -0400 (EDT)
>from IDENT:root@lox.sandelman.ottawa.on.ca [192.139.46.2]
>
>   ----- The following addresses had permanent fatal errors -----
><Donna.Hogan@alcatel.com>
>    (reason: 550 sender ignored: ottawa.on.ca does not have a name server record)
>
>   ----- Transcript of session follows -----
>... while talking to primary.alcatel.com.:
>>>> MAIL From:<mcr@sandelman.ottawa.on.ca>
><<< 550 sender ignored: ottawa.on.ca does not have a name server record
>554 5.0.0 Service unavailable
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.0.7 (GNU/Linux)
>Comment: Finger me for keys
>
>iQCVAwUBPvYLIYqHRg3pndX9AQH+1QP/fe0rInX+kaX3QQFFlnF6qNEzDyVGsTcf
>NptzvtrzSUqQC1TMXYMII25nkvk4G2p73qWDxmoTxGhax/CYhJyZwPfPpLO/AqV9
>Nl8wmGE6sLMMCorgsX+O52Q5Rdni/LK/yMz0RYf/wkZnhIBTpqINww6TtANnsAZ5
>RkOSQjDwrLc=
>=7AxR
>-----END PGP SIGNATURE-----

Vint Cerf
SVP Architecture & Technology
MCI
22001 Loudoun County Parkway, F2-4115
Ashburn, VA 20147
703 886 1690 (v806 1690)
703 886 0047 fax
vinton.g.cerf@mci.com
www.mci.com/cerfsup 






From owner-ietf@ietf.org  Mon Jun 23 11:41:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25370
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 11:41:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19US8R-0001rc-FF
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 10:17:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19US7h-0001YL-C9
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 10:16:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22066
	for <ietf@ietf.org>; Mon, 23 Jun 2003 10:16:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19US7R-0002Sh-00
	for ietf@ietf.org; Mon, 23 Jun 2003 10:16:29 -0400
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19US7G-0002SY-00
	for ietf@ietf.org; Mon, 23 Jun 2003 10:16:19 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19US6y-0004WX-00; Mon, 23 Jun 2003 07:16:00 -0700
Date: Mon, 23 Jun 2003 10:12:49 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030623101249.0063aba2.moore@cs.utk.edu>
In-Reply-To: <200306231344.h5NDiQA2011074@ginger.lcs.mit.edu>
References: <200306231344.h5NDiQA2011074@ginger.lcs.mit.edu>
X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> OK, so I'm wrong - and you have nothing to say against NAT if we are only
> proposing to use IPv4+NAT, and have no intention of adding NAT to IPv6?

I'm certainly not going to pretend that NAT doesn't have problems - and when
people argue that NAT is mostly harmless, I'm likely to try to counter that
idea because IMHO it's dangerous misinformation.  But I recognize that NAT is
here to stay in IPv4, that people will continue to use IPv4+NAT for the apps
that it works for, and that for some users, this is currently 100% of their
apps.  For now those users have little incentive to support IPv6, though I
think those users might be encouraged to adopt IPv6 in addition to IPv4+NAT as
IPv6 enables new apps that can't run on IPv4+NAT.  Which is why I've done some
work to try to make the barrier to adopting IPv6 on an existing IPv4 network
as low as possible.

I think we might get rid of IPv4+NAT eventually, simply because sites will
find it easier to maintain one set of addresses, filters, etc., rather than
two.   But I see this as a long way away.

my main goals are:

- combat the idea that NAT as a concept makes good sense from an architectural
  point of view
- keep IPv6 safe for distributed and/or p2p apps.





From owner-ietf@ietf.org  Mon Jun 23 12:13:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24335
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 11:25:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UQux-00012c-Lb
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 08:59:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UQuw-00012H-F7
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 08:59:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18814
	for <ietf@ietf.org>; Mon, 23 Jun 2003 08:59:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UQug-0001xd-00
	for ietf@ietf.org; Mon, 23 Jun 2003 08:59:14 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UQuW-0001xU-00
	for ietf@ietf.org; Mon, 23 Jun 2003 08:59:04 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h5NCwvtU010866;
	Mon, 23 Jun 2003 08:58:57 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h5NCwuru010865;
	Mon, 23 Jun 2003 08:58:56 -0400
Date: Mon, 23 Jun 2003 08:58:56 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200306231258.h5NCwuru010865@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

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

    >> That means that i) NAT+v4 is here to stay, permanently, as the
    >> packet-forwarding substrate on which we have to live, and ii) many
    >> "solutions" to the "NAT problem" have a badly faulty key premise -
    >> which is that the solution will fix IPv4's problems by replacing it.

    > almost agree. NAT is here to stay on v4, and apps that work fine with
    > NAT+v4 will continue to use NAT+v4 ..
    > but I do see us building another network that uses the same layer 1-2
    > links as the IPv4+NAT network but also provides an alternate layer 3.

In other words you buy into faulty premise #ii - "the solution will fix
IPv4's problems by replacing it".

Look, I understand the attraction of a single global namespace. I've designed
several myself (one for routing purposes, and another for naming endpoints),
and put a fair amount of work into each. So please take what I have to say
here (and said previously) seriously, because I'm saying it *in spite* of
what I'd like to see happen:

    >> The notion of a system with a single, globally unique namespace at the
    >> lowest level is a really nice one, one we had for a while - and *one
    >> we think we can reclaim*. I now think we've been deluding ourselves;
    >> that past .. is gone for good.

I'm not saying this because I *like* it (I positively *hate* it), I'm saying
it because it's the reality we have to deal with, and we can either deal with
it as best we can, or waste our time in dream-land.


    > the reason I point out the flaws with NAT is not that I think we can
    > get rid of them in v4. it's because some people are still of the belief
    > that NATs are mostly harmless and that we should not only permit them
    > into v6, but extend our architecture to embrace them.

Keith, that's not the only reason, and you know it. You want to point out to
people how screwed up NAT's are in the hope that they will be more inclined
to move *from* IPv4+NAT *to* your perfect future, one in which we once again
have a global namespace.

Well, we *won't* - we *aren't* going there.

There are too many people for whom IPv4+NAT works fine - and as for new
applications, as Daniel Senie pointed out, there are going to be two kinds of
applications/etc - those that work through NAT boxes, and some will succeed
in getting widely deployed, and those which don't work through NAT boxes,
which will *uniformly and inevitably* have a very much lower success level.

Look at IPSec and SSL. SSL works through a NAT box, and is basically
ubiquitous - every PC connected to the Internet uses it every day. I'll bet
the monthly (if not weekly) growth in the number of SSL users is larger than
the entire number of IPSec users.


IPv4+NAT, as ugly as it is, is the future. Now can we please stop sticking
our heads in the sand, and start dealing with that?

	Noel



From owner-ietf@ietf.org  Mon Jun 23 12:26:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27471
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 12:26:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19USaY-0002TT-MR
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 10:46:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19USaP-0002Sv-B1
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 10:46:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23200
	for <ietf@ietf.org>; Mon, 23 Jun 2003 10:46:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19USaO-0002f8-00
	for ietf@ietf.org; Mon, 23 Jun 2003 10:46:24 -0400
Received: from stoneport.math.uic.edu ([131.193.178.160])
	by ietf-mx with smtp (Exim 4.12)
	id 19USaD-0002eZ-00
	for ietf@ietf.org; Mon, 23 Jun 2003 10:46:13 -0400
Received: (qmail 28168 invoked by uid 1016); 23 Jun 2003 14:44:43 -0000
Date: 23 Jun 2003 14:44:43 -0000
Message-ID: <20030623144443.28167.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: namedroppers@ops.ietf.org
Cc: ietf@ietf.org
Subject: axfr-clarify, again
References: <20030623095857.1d2da0bb.olaf@ripe.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Olaf M. Kolkman writes:
> 	 + RFC3??? AXFR clarify to Draft Standard.

Replacement charter item: ``See whether consensus can be achieved on
AXFR clarifications.'' I fully understand the desire to clarify how the
DNS protocol works---but that doesn't justify pushing a horribly flawed
document to ``Proposed Standard,'' never mind ``Draft Standard.''

At least seven people have gone on record as objecting to axfr-clarify;
see http://cr.yp.to/djbdns/axfr-clarify.html for details. The BIND
company admits that axfr-clarify does not correctly describe the
behavior of most DNS servers on the Internet.

My web page http://cr.yp.to/djbdns/axfr-notes.html contains an accurate
description of the AXFR protocol, quite different from axfr-clarify.
Along the way, it identifies nine clear errors in axfr-clarify: six
points where axfr-clarify (in violation of RFC 2119 section 6) prohibits
existing working behavior, and three points where axfr-clarify creates
new interoperability problems.

What the BIND company has given us is not, in fact, ``clarification.''
It is BIND 9 documentation fraudulently posing as clarification. It is
blatantly biased in favor of one vendor---the same vendor that produced
the document, that has generated most of the messages supporting the
document, and that previously paid one of the WG chairs (Gudmundsson) to
work on its software.

The problems with axfr-clarify, both in content and in procedure, have
been thoroughly documented. Anyone who wants to ignore IETF documents---
even the occasional high-quality ones, the ones that are important for
interoperability---simply has to point to the progress of axfr-clarify
as an IETF ``standard.'' A legitimate standards organization would never
have allowed axfr-clarify to get anywhere.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Mon Jun 23 14:02:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01469
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 14:02:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UTiB-0007mg-9l
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 11:58:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UTi3-0007ly-Ik
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 11:58:23 -0400
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26198
	for <ietf@ietf.org>; Mon, 23 Jun 2003 11:58:20 -0400 (EDT)
Received: from [63.202.92.152] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h5NFwJrc063950;
	Mon, 23 Jun 2003 08:58:20 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05210604bb1cd22bf3e4@[63.202.92.152]>
In-Reply-To: <68108272848.20030621222635@psg.com>
References: <Pine.LNX.4.44.0306180924460.4731-100000@netcore.fi>
 <68108272848.20030621222635@psg.com>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Mon, 23 Jun 2003 08:52:34 -0700
To: Alex Zinin <zinin@psg.com>, ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:26 PM -0700 6/21/03, Alex Zinin wrote:
>Folks-
>
>  Having watched this discussion, it seems a couple of data points
>  might be helpful:
>
>  1. L2VPN and L3VPN proposed WGs are part of PPVPN WG split
>
>     Creation of L2VPN and L3VPN WG does not represent addition of new
>     work to the IETF. They are created as part of the process of
>     splitting the PPVPN WG to improve progress and focus it by setting
>     clear directions in the charters.
>
>  2. L2VPN work is already chartered within the IETF
>
>     The discussion about whether this work should be chartered or not
>     happened when the PPVPN WG was being created. Please see minutes
>     and slides from the PPVPN BOF at IETF 49. L2VPN solutions are
>     within the PPVPN charter and milestones.
>
>  Hope this helps.

My comments about possibly moving this work to a different standards 
body is based on our track record with this work so far in the IETF, 
not a worry about new work.

Just because we chartered some work doesn't mean we shouldn't revisit 
the question of whether or not doing so was a good idea, particularly 
after we see the kind of progress that has been made and the problems 
that have come up under those charters.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Mon Jun 23 14:02:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01527
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 14:02:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UU0Y-00082v-R0
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 12:17:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UTvp-000819-EU
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 12:12:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26744
	for <ietf@ietf.org>; Mon, 23 Jun 2003 12:12:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UTvo-0003P9-00
	for ietf@ietf.org; Mon, 23 Jun 2003 12:12:36 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19UTvb-0003Ov-00
	for ietf@ietf.org; Mon, 23 Jun 2003 12:12:23 -0400
Received: from vista.av8.net (vista.av8.net [130.105.36.10])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id MAA18443;
	Mon, 23 Jun 2003 12:08:09 -0400
Date: Mon, 23 Jun 2003 12:08:10 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: "Olaf M. Kolkman" <olaf@ripe.net>
cc: namedroppers@ops.ietf.org, <ietf@ietf.org>
Subject: Re AXFR clarify to Draft standard
In-Reply-To: <20030623095857.1d2da0bb.olaf@ripe.net>
Message-ID: <Pine.LNX.4.44.0306231159550.10246-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


This document was previously shown to be a major change and an unnecessary
change at that.  There is quite obviously no consensus on the merits of
the document.

While a clarification on AXFR is order due to vague language in the
present specification, such clarification should take into account how
multiple existing implementations interpreted the vague specification,
rather than try to push through an unnecessary change made by the Bind9
developers.

		--Dean

On Mon, 23 Jun 2003, Olaf M. Kolkman wrote:

> 	 + RFC3??? AXFR clarify to Draft Standard.




From owner-ietf@ietf.org  Mon Jun 23 14:02:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01454
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 14:02:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UTmA-0007ph-Pa
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 12:02:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UTl4-0007nz-1P
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 12:01:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26303
	for <ietf@ietf.org>; Mon, 23 Jun 2003 12:01:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UTko-0003Ii-00
	for ietf@ietf.org; Mon, 23 Jun 2003 12:01:14 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19UTkd-0003G6-00
	for ietf@ietf.org; Mon, 23 Jun 2003 12:01:03 -0400
Content-class: urn:content-classes:message
Subject: RE: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Date: Mon, 23 Jun 2003 08:55:30 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8CA@server2000.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Thread-Index: AcM5nfgZRfDVSpgdRl+57/qvdGq+iwAAXI+g
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Keith Moore" <moore@cs.utk.edu>,
        "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Keith Moore wrote:
> Which is why I've done some work to try to make the barrier to
> adopting IPv6 on an existing IPv4 network as low as possible.

What you don't realize is that the only thing that you have left to do
is to get 6to4 implemented in NAT boxes. If every Linksys had 6to4 code
and was acting as a 6to4 gateway every home network would be IPv6
capable without the annoyances of crossing NAT when trying to implement
6to4 at the host level.

Michel.




From owner-ietf@ietf.org  Mon Jun 23 14:02:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01542
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 14:02:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UTYV-0007ZO-Ms
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 11:48:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UTYD-0007Xd-MT
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 11:48:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25647
	for <ietf@ietf.org>; Mon, 23 Jun 2003 11:47:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UTXi-0003CG-00
	for ietf@ietf.org; Mon, 23 Jun 2003 11:47:42 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UTXX-0003C1-00
	for ietf@ietf.org; Mon, 23 Jun 2003 11:47:32 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h5NFmU708121;
	Mon, 23 Jun 2003 08:48:30 -0700
Date: Mon, 23 Jun 2003 08:45:06 -0700
From: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: The Bat! (v1.63 Beta/10) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <128220718776.20030623084506@brandenburg.com>
To: "vinton g. cerf" <vinton.g.cerf@mci.com>
CC: Michael Richardson <mcr@sandelman.ottawa.on.ca>, postmaster@alcatel.com,
        dns-tech@alcatel.com, <dns-admin@alcatel.com>,
        <alain.sabban@alcatel.fr>, <hostmaster@alcanet.no>, <info@cira.ca>,
        <ietf@ietf.org>
Subject: Re: non-complain mail system at alcatel.com
In-Reply-To: <5.2.0.9.2.20030623062509.047f9ac8@pop.mcilink.com>
References: <200306222001.h5MK1et1018976@sandelman.ottawa.on.ca>
 <5.2.0.9.2.20030623062509.047f9ac8@pop.mcilink.com>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


vgc> I would be interested to know whether Alcatel really believes that DNS behaves in
vgc> such a way that one MUST delegate at each "dot" - as far as I know, it is NOT
vgc> required to do so.

It is not required.  That's the difference between a 'zone' and a
'sub-domain'.  The latter is a subset of the former.


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




From owner-ietf@ietf.org  Mon Jun 23 14:02:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01455
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 14:02:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UU6M-0008DT-NA
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 12:23:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UU6K-0008Cx-DD
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 12:23:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27379
	for <ietf@ietf.org>; Mon, 23 Jun 2003 12:23:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UU6J-0003Xd-00
	for ietf@ietf.org; Mon, 23 Jun 2003 12:23:27 -0400
Received: from tnt.isi.edu ([128.9.128.128])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UU68-0003XB-00
	for ietf@ietf.org; Mon, 23 Jun 2003 12:23:16 -0400
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6p2/8.11.2) with ESMTP id h5NGMAK09926;
	Mon, 23 Jun 2003 09:22:10 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.9.3/8.8.6) id JAA17225;
	Mon, 23 Jun 2003 09:07:38 -0700 (PDT)
Date: Mon, 23 Jun 2003 09:07:38 -0700 (PDT)
Message-Id: <200306231607.JAA17225@gra.isi.edu>
To: mcr@sandelman.ottawa.on.ca, postmaster@alcatel.com, dns-tech@alcatel.com,
        dns-admin@alcatel.com, alain.sabban@alcatel.fr, hostmaster@alcanet.no,
        vinton.g.cerf@mci.com
Subject: Re: non-complain mail system at alcatel.com
Cc: info@cira.ca, ietf@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


  *> From owner-ietf@ietf.org  Mon Jun 23 08:26:17 2003
  *> Date: Mon, 23 Jun 2003 06:26:03 -0400
  *> From: "vinton g. cerf" <vinton.g.cerf@mci.com>
  *> Subject: Re: non-complain mail system at alcatel.com
  *> X-Sender: vcerf@pop.mcilink.com
  *> To: Michael Richardson <mcr@sandelman.ottawa.on.ca>, postmaster@alcatel.com,
  *>    dns-tech@alcatel.com, dns-admin@alcatel.com, alain.sabban@alcatel.fr,
  *>    hostmaster@alcanet.no
  *> Cc: info@cira.ca, ietf@ietf.org
  *> MIME-version: 1.0
  *> X-AntiVirus: scanned by AMaViS 0.2.1
  *> 
  *> I would be interested to know whether Alcatel really believes that DNS behaves in such a way that one MUST delegate at each "dot" - as far as I know, it is NOT required to do so.

Of course it is not!!  I'll bet you will find a counter example in
the DNS RFCs.

Bob

  *> 
  *> vint
  *> 
  *> At 04:01 PM 6/22/2003 -0400, Michael Richardson wrote:
  *> >-----BEGIN PGP SIGNED MESSAGE-----
  *> >
  *> >
  *> >Alcatel.com does not have a functional email system. It believes that
  *> >all domains must have full NS-record delegations. I.e. that my domain
  *> >"sandelman.ottawa.on.ca" must be a delegation from "ottawa.on.ca",
  *> >rather than from "ca". (The .CA namespace has a single ccTLD)
  *> >
  *> >I have contacted Alcatel repeatedly by email and by phone in the
  *> >past months, and I have gotten no response to this. A major problem is that 
  *> >I think that only one of their MX's has this behaviour.
  *> >
  *> >So, I'm resorting to the only other way I have - embarassment.
  *> >
  *> >Specifically, it says:
  *> >
  *> >The original message was received at Sat, 21 Jun 2003 14:27:27 -0400 (EDT)
  *> >from IDENT:root@lox.sandelman.ottawa.on.ca [192.139.46.2]
  *> >
  *> >   ----- The following addresses had permanent fatal errors -----
  *> ><Donna.Hogan@alcatel.com>
  *> >    (reason: 550 sender ignored: ottawa.on.ca does not have a name server record)
  *> >
  *> >   ----- Transcript of session follows -----
  *> >... while talking to primary.alcatel.com.:
  *> >>>> MAIL From:<mcr@sandelman.ottawa.on.ca>
  *> ><<< 550 sender ignored: ottawa.on.ca does not have a name server record
  *> >554 5.0.0 Service unavailable
  *> >
  *> >-----BEGIN PGP SIGNATURE-----
  *> >Version: GnuPG v1.0.7 (GNU/Linux)
  *> >Comment: Finger me for keys
  *> >
  *> >iQCVAwUBPvYLIYqHRg3pndX9AQH+1QP/fe0rInX+kaX3QQFFlnF6qNEzDyVGsTcf
  *> >NptzvtrzSUqQC1TMXYMII25nkvk4G2p73qWDxmoTxGhax/CYhJyZwPfPpLO/AqV9
  *> >Nl8wmGE6sLMMCorgsX+O52Q5Rdni/LK/yMz0RYf/wkZnhIBTpqINww6TtANnsAZ5
  *> >RkOSQjDwrLc=
  *> >=7AxR
  *> >-----END PGP SIGNATURE-----
  *> 
  *> Vint Cerf
  *> SVP Architecture & Technology
  *> MCI
  *> 22001 Loudoun County Parkway, F2-4115
  *> Ashburn, VA 20147
  *> 703 886 1690 (v806 1690)
  *> 703 886 0047 fax
  *> vinton.g.cerf@mci.com
  *> www.mci.com/cerfsup 
  *> 
  *> 
  *> 
  *> 



From owner-ietf@ietf.org  Mon Jun 23 15:06:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04639
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 15:06:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UUaN-0000aL-1y
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 12:54:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UUZ3-0000Z0-HS
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 12:53:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28562
	for <ietf@ietf.org>; Mon, 23 Jun 2003 12:53:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UUZ2-0003nj-00
	for ietf@ietf.org; Mon, 23 Jun 2003 12:53:08 -0400
Received: from [80.75.64.137] (helo=budokit.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19UUYr-0003nY-00
	for ietf@ietf.org; Mon, 23 Jun 2003 12:52:57 -0400
Received: from [213.219.58.242] (account jonathan@seventh-wave-systems.com HELO [10.20.15.6])
  by budokit.com (CommuniGate Pro SMTP 4.0.6)
  with ESMTP id 441566 for ietf@ietf.org; Mon, 23 Jun 2003 17:52:01 +0100
Date: Mon, 23 Jun 2003 17:52:36 +0100
Subject: Re: myth of the great transition (was US Defense Department forma
	lly adopts IPv6)
From: Jonathan Hogg <jonathan.hogg@seventh-wave-systems.com>
To: IETF <ietf@ietf.org>
Message-ID: <BB1CEEE4.1C0A5%jonathan.hogg@seventh-wave-systems.com>
In-Reply-To: <200306231227.h5NCRNUN010669@ginger.lcs.mit.edu>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 23/6/03 13:27, J. Noel Chiappa wrote:

> The big problem is incoming connections - how do you set up the mappings they
> will need? Wiretapping DNS is ugly, but it doesn't require changing anything
> (for existing applications). On the other hand, if you only want to support
> incoming connections for new applications, you can define them to include
> some sort of MidCom-like setup.

Aren't Microsoft already "standardizing" this with their Universal Plug and
Play (UPnP) architecture?

I'm a little fuzzy on the details, but I believe the concept is that
applications that understand this can communicate with the router (the NAPT
box in the case of SoHo networks) and request ports to be opened externally
and forwarded back to the host. I think Microsoft's NetMeeting conferencing
program supports this already and there are a few ADSL modem/routers that
implement it.

I agree that NAPT is here for a long time and it would be better to work
towards controlling it.

Jonathan

-- 
Jonathan Hogg
Director, Technology

Seventh Wave Systems Ltd.
4-14 Tabernacle Street
London EC2A 4LU
Telephone: +44 20 7074 0423

<http://www.seventh-wave-systems.com/>




From owner-ietf@ietf.org  Mon Jun 23 15:06:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04633
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 15:06:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UVTW-0002s2-1c
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 13:51:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UVSh-0002ou-73
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 13:50:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00944
	for <ietf@ietf.org>; Mon, 23 Jun 2003 13:50:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UVSg-0004GO-00
	for ietf@ietf.org; Mon, 23 Jun 2003 13:50:38 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UVSV-0004Ft-00
	for ietf@ietf.org; Mon, 23 Jun 2003 13:50:27 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id E86FA1396B; Mon, 23 Jun 2003 17:49:51 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: non-complain mail system at alcatel.com
References: <5.2.0.9.2.20030623062509.047f9ac8@pop.mcilink.com>
From: Paul Vixie <vixie@vix.com>
Date: 23 Jun 2003 17:49:51 +0000
In-Reply-To: <5.2.0.9.2.20030623062509.047f9ac8@pop.mcilink.com>
Message-ID: <g3he6gk7k0.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
Sender: owner-ietf@ietf.org
Precedence: bulk

vinton.g.cerf@mci.com ("vinton g. cerf") writes:
> I would be interested to know whether Alcatel really believes that DNS
> behaves in such a way that one MUST delegate at each "dot" - as far as I
> know, it is NOT required to do so.

it's not required to do so.  see for example

	;; QUERY SECTION:
        ;;      _kerberos._udp.vix.com, type = SRV, class = IN

        ;; ANSWER SECTION:
        _kerberos._udp.vix.com.  1H IN SRV  1 0 88 kerberos-2.vix.com.
        _kerberos._udp.vix.com.  1H IN SRV  0 1 88 kerberos-0.vix.com.
        _kerberos._udp.vix.com.  1H IN SRV  1 0 88 kerberos-1.vix.com.

        ;; AUTHORITY SECTION:
        vix.com.                1H IN NS        ns1.gnac.com.
        vix.com.                1H IN NS        ns-ext.vix.com.

        ;; ADDITIONAL SECTION:
        ns1.gnac.com.           1d5h15m35s IN A  64.124.44.166
        ns-ext.vix.com.         1H IN AAAA      2001:4f8:0:2::13
        ns-ext.vix.com.         1H IN A         204.152.184.64

the apex of the enclosing zone is two labels above the qname and answer.
alcatel is just confused.  however, this confusion is pretty common, and
i know that a lot of domain integrity checkers get it wrong.
-- 
Paul Vixie



From owner-ietf@ietf.org  Mon Jun 23 15:06:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04637
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 15:06:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UV8E-0002NM-FP
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 13:29:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UV7b-0002MM-Qr
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 13:28:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29970
	for <ietf@ietf.org>; Mon, 23 Jun 2003 13:28:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UV7L-00047U-00
	for ietf@ietf.org; Mon, 23 Jun 2003 13:28:35 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UV7B-00047D-00
	for ietf@ietf.org; Mon, 23 Jun 2003 13:28:25 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5NHS0N23568;
        Mon, 23 Jun 2003 13:28:01 -0400 (EDT)
Date: Mon, 23 Jun 2003 13:28:00 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030623132800.4e5a55d8.moore@cs.utk.edu>
In-Reply-To: <200306231227.h5NCRNUN010669@ginger.lcs.mit.edu>
References: <200306231227.h5NCRNUN010669@ginger.lcs.mit.edu>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Here, again, is the nub of what we have to deal with:
> 
>     >> The notion of a system with a single, globally unique namespace
>     >at the> lowest level is a really nice one, one we had for a while
>     >- and *one> we think we can reclaim*. I now think we've been
>     >deluding ourselves;> that past .. is gone for good.
> 
> How would I move forward from there, constructively, to try and
> produce a less broken architecture/system?

the only way I can see to do so is to provide tools to ease migration to
a less broken system.  I don't see any way to make the NAT technique
significantly less broken (and I have tried) that takes less effort than
supporting IPv6 alongside NAT.   basically you end up trying to create a
new network with a new address space on top of a NATted network,
instead of alongside it. and to do this you have to upgrade the NAT
boxes, and the hosts, and the apps that can't deal with status quo NAT -
at which point you're imposing about the same deployment barrier as IPv6
imposes.  IPv6 is both cleaner and ahead of the curve.

> There are many different flavors of NAT, and so it's hard to make an
> application "work with NAT" when you don't know exactly what the NAT
> box is going to do.

indeed, this is a problem - and NATs are also a moving target.  but it's
almost as difficult to "work with NAT" even when you do know exactly
what the NAT box is going to do.  

also, the argument is often made that NATs are "here to stay" precisely
because they are already so widely deployed.  if one accepts that,
doesn't it follow that broken NATs with their inconsistent behavior are
"here to stay" also, for the same reasons?  and if we assume we can
upgrade the NATs anyway, why not make them support something cleaner
than IPv4+NAT+MIDCOM-style application hooks?

> The next step would be to add a "NAT considerations" section to all
> protocol specifications, just like the "Security considerations" we
> have now. Protocols can be designed to be less NAT-hostile - e.g. no
> giving addresses to third parties as a way to contact someone, etc.

many protocols cannot be designed to be less NAT hostile without
imposing significant overhead both in bandwidth and in extra
infrastructure, and degrading performance and reliability.  if we want
to set up proxies for each protocol outside of every NAT we can make
those protocols work. IPv6 is a lot simpler and more robust.

> Nothing positive can happen as long as we keep acting as NAT i) is too
> disgusting to seriously try and deal with, and ii) will go away if we
> stick our heads in the sand hard enough

nothing positive can happen as long as we keep acting as if NAT is
here to stay and that it's going to be forced on all future apps.

Keith



From owner-ietf@ietf.org  Mon Jun 23 18:44:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14041
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 18:44:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UX0L-0007gP-NE
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 15:29:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UWwC-0007CR-6P
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 15:25:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06709
	for <ietf@ietf.org>; Mon, 23 Jun 2003 15:25:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UWwA-00055A-00
	for ietf@ietf.org; Mon, 23 Jun 2003 15:25:10 -0400
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 19UWw0-00054d-00
	for ietf@ietf.org; Mon, 23 Jun 2003 15:25:00 -0400
Received: from cisco.com (171.71.177.254)
  by sj-iport-2.cisco.com with ESMTP; 23 Jun 2003 12:23:26 -0800
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h5NJONgE003440;
	Mon, 23 Jun 2003 12:24:23 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AIS29404;
	Mon, 23 Jun 2003 12:24:22 -0700 (PDT)
Message-Id: <200306231924.AIS29404@mira-sjc5-c.cisco.com>
To: Jonathan Hogg <jonathan.hogg@seventh-wave-systems.com>
cc: IETF <ietf@ietf.org>
From: Melinda Shore <mshore@cisco.com>
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Message from jonathan.hogg@seventh-wave-systems.com
   of "Mon, 23 Jun 2003 17:52:36 BST." <BB1CEEE4.1C0A5%jonathan.hogg@seventh-wave-systems.com> 
Date: Mon, 23 Jun 2003 15:24:22 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

> Aren't Microsoft already "standardizing" this with their Universal Plug and
> Play (UPnP) architecture?

That's just midcom, which the IETF is standardizing.  We
started before they did but Microsoft got there first and
worst (there's even midcom language in their documents).  So
that's something that was started in the IETF and
expropriated.  Note that it still handles incoming
connections pretty badly.
  
There are other IETF efforts, as well, which I think are
more sound, but may take some time to become fully ramped
up.

Melinda



From owner-ietf@ietf.org  Mon Jun 23 18:44:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14044
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 18:44:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UXXF-0008RE-GK
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 16:03:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UXWm-0008QQ-SR
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 16:03:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08285
	for <ietf@ietf.org>; Mon, 23 Jun 2003 16:02:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UXWl-0005Np-00
	for ietf@ietf.org; Mon, 23 Jun 2003 16:02:59 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UXWa-0005MP-00
	for ietf@ietf.org; Mon, 23 Jun 2003 16:02:48 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h5NK2AxS089799;
	Mon, 23 Jun 2003 22:02:11 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Mon, 23 Jun 2003 22:01:17 +0200
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: EKR <ekr@rtfm.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <kjllvxhhha.fsf@romeo.rtfm.com>
Message-Id: <7386F374-A5B5-11D7-949E-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On donderdag, jun 19, 2003, at 23:42 Europe/Amsterdam, Eric Rescorla 
wrote:

> Realistically, there are three kinds of utility
> effects of someone choosing to install a NAT:

> (1) The effect on them personally.
> (2) The effect on other people who might potentially correspond
>     with them (a rather small set).
> (3) The effect on the network as a whole, or to speak more
>     precisely, the effect on a large set of people who
>     have no relationship with the individual in question.

> When I said "no strong argument" I was thinking about class (3), not
> class (2), which I agree there is a much stronger argument to be had
> about. I don't know of a strong argument for (3).

Vendors are forced to expend considerable engineering effort to support 
NAT users. I think this qualifies as a class 3 effect.

It would be interesting to see how much of the IETF's resources are 
used up by NAT issues. It must be a significant amount if a simple 
announcement about the advancement of IPv6 deployment turns into a 
discussion about the exact level of NAT's evilness.




From owner-ietf@ietf.org  Mon Jun 23 19:31:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14053
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 18:44:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UXB3-0007zQ-KI
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 15:40:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UXA9-0007yp-Ud
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 15:39:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07325
	for <ietf@ietf.org>; Mon, 23 Jun 2003 15:39:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UX9e-0005CY-00
	for ietf@ietf.org; Mon, 23 Jun 2003 15:39:06 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UX9T-0005CL-00
	for ietf@ietf.org; Mon, 23 Jun 2003 15:38:55 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5NJcRN25270;
        Mon, 23 Jun 2003 15:38:30 -0400 (EDT)
Date: Mon, 23 Jun 2003 15:38:26 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Jonathan Hogg <jonathan.hogg@seventh-wave-systems.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030623153826.27a22c13.moore@cs.utk.edu>
In-Reply-To: <BB1CEEE4.1C0A5%jonathan.hogg@seventh-wave-systems.com>
References: <200306231227.h5NCRNUN010669@ginger.lcs.mit.edu>
	<BB1CEEE4.1C0A5%jonathan.hogg@seventh-wave-systems.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I agree that NAPT is here for a long time and it would be better to
> work towards controlling it.

in other words, we should keep beating our heads against the wall trying
to solve insurmountable problems.  

trying to make NATs work is the modern task of Sisyphus.



From owner-ietf@ietf.org  Mon Jun 23 21:56:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17921
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 21:56:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UZof-00017a-9W
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 18:29:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UZoC-000166-Pr
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 18:29:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13620
	for <ietf@ietf.org>; Mon, 23 Jun 2003 18:29:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UZoB-0006Cd-00
	for ietf@ietf.org; Mon, 23 Jun 2003 18:29:07 -0400
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 19UZo0-0006Bq-00
	for ietf@ietf.org; Mon, 23 Jun 2003 18:28:56 -0400
Received: from cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 23 Jun 2003 15:29:30 -0800
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h5NMQL4v028297;
	Mon, 23 Jun 2003 15:26:22 -0700 (PDT)
Received: from cisco.com (ssh-rtp-1.cisco.com [161.44.11.166])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id AIS56308;
	Mon, 23 Jun 2003 15:26:20 -0700 (PDT)
Message-Id: <200306232226.AIS56308@mira-sjc5-c.cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: ietf@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: myth of the great transition (was US Defense Department forma lly adopts IPv6) 
In-Reply-To: Message from iljitsch@muada.com
   of "Mon, 23 Jun 2003 22:01:17 +0200." <7386F374-A5B5-11D7-949E-00039388672E@muada.com> 
Date: Mon, 23 Jun 2003 18:26:20 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

> It would be interesting to see how much of the IETF's resources are 
> used up by NAT issues. 

Probably not as much as needed, actually.  

Be that as it may, let's do some arithmetic: I would guess
that the really huge equipment vendors probably have about
50 FTEs each working on NAT workarounds (not NAT
implementation per se - just NAT workarounds).  Caveat: I
don't have any real numbers, this is just an estimate based
on what I've encountered in talking to people/companies
about NAT.  These workarounds include things like stateful
inspection/rewrite, relaying and encapsulation protocols,
etc., plus the associated coding, QA, standardization work,
and documentation, and includes everything from workarounds
for voice to workarounds for IPSec.  If you average about
$200,000 per employee per year (including salary, benefits,
office space, parking, telecom costs, etc.) that comes to
$10,000,000/year per really big company.  That sounds like a
lot of money to me.

Melinda



From owner-ietf@ietf.org  Mon Jun 23 21:56:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17918
	for <ietf-web-archive@odin.ietf.org>; Mon, 23 Jun 2003 21:56:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UZTE-0005Rf-VY
	for ietf-list@asgard.ietf.org; Mon, 23 Jun 2003 18:07:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UZSW-0005F4-8b
	for ietf@asgard.ietf.org; Mon, 23 Jun 2003 18:06:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12175
	for <ietf@ietf.org>; Mon, 23 Jun 2003 18:06:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UZS0-00063e-00
	for ietf@ietf.org; Mon, 23 Jun 2003 18:06:12 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19UZRq-00063a-00
	for ietf@ietf.org; Mon, 23 Jun 2003 18:06:02 -0400
Content-class: urn:content-classes:message
Subject: RE: myth of the great transition (was US Defense Department formally adopts IPv6)
Date: Mon, 23 Jun 2003 15:05:49 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8CF@server2000.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: myth of the great transition (was US Defense Department formally adopts IPv6)
Thread-Index: AcM5urpEWiIph8t1SUeGl8RHtkHUiQAF9j+A
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Jonathan Hogg" <jonathan.hogg@seventh-wave-systems.com>,
        "IETF" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Jonathan,


> Jonathan Hogg wrote:
> Aren't Microsoft already "standardizing" this with their Universal
> Plug and Play (UPnP) architecture?
> I'm a little fuzzy on the details, but I believe the concept is
> that applications that understand this can communicate with the
> router (the NAPT box in the case of SoHo networks) and request
> ports to be opened externally and forwarded back to the host. I
> think Microsoft's NetMeeting conferencing program supports this
> already and there are a few ADSL modem/routers that implement it.

That is the little my feeble understanding of it has grasped too.
However, I still don't fully understand how it resolves the problem of
originated-from-the-outside connections: Let's say there are 3 web
servers in the inside, all three talk to the NAPT box and all three have
the NAPT box open a translation port. The part I don't get is where the
NAPT box chooses which one of the three gets the traffic without
something like decapsulating the http header.

Michel.




From owner-ietf@ietf.org  Tue Jun 24 04:48:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07465
	for <ietf-web-archive@odin.ietf.org>; Tue, 24 Jun 2003 04:48:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UgI6-00076H-GC
	for ietf-list@asgard.ietf.org; Tue, 24 Jun 2003 01:24:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UgHg-000763-E2
	for ietf@asgard.ietf.org; Tue, 24 Jun 2003 01:24:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21804
	for <ietf@ietf.org>; Tue, 24 Jun 2003 01:23:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UgHA-0000NG-00
	for ietf@ietf.org; Tue, 24 Jun 2003 01:23:28 -0400
Received: from harrier.mail.pas.earthlink.net ([207.217.120.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UgGz-0000N7-00
	for ietf@ietf.org; Tue, 24 Jun 2003 01:23:17 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by harrier.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19UgGR-0007iK-00; Mon, 23 Jun 2003 22:22:43 -0700
Date: Tue, 24 Jun 2003 01:19:29 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Melinda Shore <mshore@cisco.com>
Cc: moore@cs.utk.edu, iljitsch@muada.com, ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030624011929.035c8b05.moore@cs.utk.edu>
In-Reply-To: <200306232226.AIS56308@mira-sjc5-c.cisco.com>
References: <7386F374-A5B5-11D7-949E-00039388672E@muada.com>
	<200306232226.AIS56308@mira-sjc5-c.cisco.com>
X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > It would be interesting to see how much of the IETF's resources are 
> > used up by NAT issues. 
> 
> Probably not as much as needed, actually.  

any amount is too much IMHO.




From owner-ietf@ietf.org  Tue Jun 24 09:33:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15562
	for <ietf-web-archive@odin.ietf.org>; Tue, 24 Jun 2003 09:33:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UjEz-0005uk-7Q
	for ietf-list@asgard.ietf.org; Tue, 24 Jun 2003 04:33:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UjEE-0005uY-8j
	for ietf@asgard.ietf.org; Tue, 24 Jun 2003 04:32:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07191
	for <ietf@ietf.org>; Tue, 24 Jun 2003 04:32:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UjEB-0001RJ-00
	for ietf@ietf.org; Tue, 24 Jun 2003 04:32:35 -0400
Received: from babar.switch.ch ([130.59.4.85])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UjE1-0001Qq-00
	for ietf@ietf.org; Tue, 24 Jun 2003 04:32:25 -0400
Received: from babar (localhost [IPv6:::1])
	by babar.switch.ch (8.12.9+Sun/8.12.2) with ESMTP id h5O8UmEI018024;
	Tue, 24 Jun 2003 10:30:49 +0200 (CEST)
From: Simon Leinen <simon@limmat.switch.ch>
Message-ID: <16120.3128.481731.649012@limmat.switch.ch>
Date: Tue, 24 Jun 2003 10:30:48 +0200
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="ryhF77cOvI"
Content-Transfer-Encoding: 7bit
To: ietf@ietf.org
Subject: Re: non-complain mail system at alcatel.com
In-Reply-To: <200306231607.JAA17225@gra.isi.edu> (Bob Braden's message of "Mon, 23 Jun 2003 09:07:38 -0700 (PDT)")
References: <200306231607.JAA17225@gra.isi.edu>
X-Mailer: VM 7.16 under Emacs 21.2.95.1
X-Face: 1Nk*r=:$IBBb8|TyRB'2WSY6u:BzMO7N)#id#-4_}MsU5?vTI?dez|JiutW4sKBLjp.l7,F
 7QOld^hORRtpCUj)!cP]gtK_SyK5FW(+o"!or:v^C^]OxX^3+IPd\z,@ttmwYVO7l`6OXXYR`
Sender: owner-ietf@ietf.org
Precedence: bulk


--ryhF77cOvI
Content-Type: text/plain; charset=us-ascii
Content-Description: message body and .signature
Content-Transfer-Encoding: 7bit

This seems to be collateral damage of an anti-spam mechanism, and I
sent the following complaint to the Alcatel postmaster and the
bug-report address of the anti-spam software in question.
-- 
Simon.


--ryhF77cOvI
Content-Type: message/rfc822
Content-Description: forwarded message

MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Received: from babar ([130.59.4.85] helo=babar.switch.ch)
	by central.switch.ch with esmtp (Exim 3.20 #1)
	id 19UNkC-0004uV-00
	for simon@limmat.switch.ch; Mon, 23 Jun 2003 11:36:12 +0200
Received: from babar.switch.ch (localhost [IPv6:::1])
	by babar.switch.ch (8.12.9+Sun/8.12.2) with ESMTP id h5N9Z3EI015925;
	Mon, 23 Jun 2003 11:35:03 +0200 (CEST)
Received: (from leinen@localhost)
	by babar.switch.ch (8.12.9+Sun/8.12.2/Submit) id h5N9YwX3015922;
	Mon, 23 Jun 2003 11:34:58 +0200 (CEST)
X-Authentication-Warning: babar.switch.ch: leinen set sender to simon@limmat.switch.ch using -f
X-Face: 1Nk*r=:$IBBb8|TyRB'2WSY6u:BzMO7N)#id#-4_}MsU5?vTI?dez|JiutW4sKBLjp.l7,F
   7QOld^hORRtpCUj)!cP]gtK_SyK5FW(+o"!or:v^C^]OxX^3+IPd\z,@ttmwYVO7l`6OXXYR`
In-Reply-To: <200306222001.h5MK1et1018976@sandelman.ottawa.on.ca> (Michael
 Richardson's message of "Sun, 22 Jun 2003 16:01:39 -0400")
References: <200306222001.h5MK1et1018976@sandelman.ottawa.on.ca>
Message-ID: <aa65mxw30e.fsf@limmat.switch.ch>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.2.95 (usg-unix-v)
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.54 (1.174.2.17-2003-05-11-exp)
From: Simon Leinen <simon@limmat.switch.ch>
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Cc: postmaster@alcatel.com, dns-tech@alcatel.com, dns-admin@alcatel.com,
   alain.sabban@alcatel.fr, hostmaster@alcanet.no, info@cira.ca,
   bugs@sabernet.net
Subject: Re: non-complain mail system at alcatel.com
Date: Mon, 23 Jun 2003 11:34:57 +0200
X-Spam-Status: No, hits=-7.6 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_GNUS_UA,
	      X_AUTH_WARNING
	autolearn=ham version=2.54

[removed IETF mailing list from CC:; added bugs@sabernet.net]

Michael Richardson writes:
> So, I'm resorting to the only other way I have - embarassment.

> Specifically, it says:

> The original message was received at Sat, 21 Jun 2003 14:27:27 -0400 (EDT)
> from IDENT:root@lox.sandelman.ottawa.on.ca [192.139.46.2]

>    ----- The following addresses had permanent fatal errors -----
> <Donna.Hogan@alcatel.com>
>     (reason: 550 sender ignored: ottawa.on.ca does not have a name server record)

>    ----- Transcript of session follows -----
> ... while talking to primary.alcatel.com.:
>>>> MAIL From:<mcr@sandelman.ottawa.on.ca>
> <<< 550 sender ignored: ottawa.on.ca does not have a name server record
> 554 5.0.0 Service unavailable

Apparently, Alcatel implements "Sender Verification" on this gateway,
see:

http://sabernet.home.attbi.com/software/nospam.html

    Sender Verification:
    
        Verification of the sender's email address can be turned on by
        adding the following line to your netperm-table:
    
        smap:  nospam ns-required
    
        When a sender's email address is received, a DNS lookup is
        performed to verify that an NS record exists for the given
        domain. For example, assume that 001232.com does not exist:
    
        220 mailhost SMTP/smap Ready.
        mail from: <spam@001232.com>
        550 sender ignored: 001232.com does not have a name server record
    
        This is useful if you receive lots of spam from nonexistent
        domains.

This code is obviously buggy in that it returns "false positives" in
valid setups such as Michael's.  I hope this will be fixed, and
Alcatel would be well-advised to turn off the "ns-required" option
until it is.
-- 
Simon Leinen.
SWITCH

--ryhF77cOvI--




From owner-ietf@ietf.org  Tue Jun 24 11:51:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21157
	for <ietf-web-archive@odin.ietf.org>; Tue, 24 Jun 2003 11:51:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Untp-0004Nu-Jy
	for ietf-list@asgard.ietf.org; Tue, 24 Jun 2003 09:31:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UmsV-0003tl-9q
	for ietf@asgard.ietf.org; Tue, 24 Jun 2003 08:26:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13690
	for <ietf@ietf.org>; Tue, 24 Jun 2003 08:25:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ums0-0002aH-00
	for ietf@ietf.org; Tue, 24 Jun 2003 08:25:56 -0400
Received: from mail1.microsoft.com ([131.107.3.125])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Umrp-0002aA-00
	for ietf@ietf.org; Tue, 24 Jun 2003 08:25:45 -0400
Received: from mail5.microsoft.com ([157.54.6.156]) by mail1.microsoft.com with Microsoft SMTPSVC(5.0.2195.6659);
	 Tue, 24 Jun 2003 05:24:54 -0700
Received: from inet-vrs-05.redmond.corp.microsoft.com ([157.54.6.157]) by mail5.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Tue, 24 Jun 2003 05:24:54 -0700
Received: from 157.54.5.25 by inet-vrs-05.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 24 Jun 2003 05:24:54 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 24 Jun 2003 05:24:53 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 24 Jun 2003 05:24:53 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.82]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3788.0);
	 Tue, 24 Jun 2003 05:24:52 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6940.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Date: Tue, 24 Jun 2003 05:24:47 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA0246F1AB@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Thread-Index: AcM51RmxgjfL/ALdT6iIq8Uxeq7B5wAdWHxo
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Melinda Shore" <mshore@cisco.com>,
        "Jonathan Hogg" <jonathan.hogg@seventh-wave-systems.com>
Cc: "IETF" <ietf@ietf.org>
X-OriginalArrivalTime: 24 Jun 2003 12:24:52.0897 (UTC) FILETIME=[9D16A110:01C33A4B]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

>> Aren't Microsoft already "standardizing" this with their Universal =
Plug and
>> Play (UPnP) architecture?
>
> That's just midcom, which the IETF is standardizing.  We
> started before they did but Microsoft got there first and
> worst (there's even midcom language in their documents).  So
> that's something that was started in the IETF and
> expropriated.  Note that it still handles incoming
> connections pretty badly.

The UPNP "Internet Gateway Device" working group and the MIDCOM WG =
effort started at about the same time, but the UPNP specification was =
published about 2 years ago, while MIDCOM is not quite finished yet. =
Looks like an interesting case study for the "problem statement" working =
group...=20
=20
I don't quite get the point on the handling of incoming connections -- =
basically, the UPNP/IGD specification has functions for reserving port =
mappings, that allow a host behind a NAT to listen on an external port =
number. The host can definitely receive incoming connections.
=20
The UPNP/IGD approach has limitations: it is designed for a "home  =
network" rather than an enterprise network, and it will not work if =
there are two "stacked NAT". However, it does solve a large fraction of =
the problem.
=20
By the way, while Microsoft certainly contributed to the fundation of =
the UPNP Forum, the UPNP/IGD is not exactly a Microsoft specification.
=20
-- Christian Huitema



From owner-ietf@ietf.org  Tue Jun 24 14:18:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29341
	for <ietf-web-archive@odin.ietf.org>; Tue, 24 Jun 2003 14:18:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19UqKf-00071S-T7
	for ietf-list@asgard.ietf.org; Tue, 24 Jun 2003 12:07:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19UqKf-00071N-Ge
	for ietf@asgard.ietf.org; Tue, 24 Jun 2003 12:07:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21905
	for <ietf@ietf.org>; Tue, 24 Jun 2003 12:07:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UqKe-0003xU-00
	for ietf@ietf.org; Tue, 24 Jun 2003 12:07:44 -0400
Received: from falcon.mail.pas.earthlink.net ([207.217.120.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UqKT-0003ws-00
	for ietf@ietf.org; Tue, 24 Jun 2003 12:07:34 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by falcon.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19UqJM-0000Us-00; Tue, 24 Jun 2003 09:06:24 -0700
Date: Tue, 24 Jun 2003 12:03:08 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Christian Huitema" <huitema@windows.microsoft.com>
Cc: moore@cs.utk.edu, mshore@cisco.com, jonathan.hogg@seventh-wave-systems.com,
        ietf@ietf.org
Subject: Re: myth of the great transition (was US Defense Department forma
 lly adopts IPv6)
Message-Id: <20030624120308.3679707e.moore@cs.utk.edu>
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA0246F1AB@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References: <DAC3FCB50E31C54987CD10797DA511BA0246F1AB@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> The UPNP "Internet Gateway Device" working group and the MIDCOM WG effort
> started at about the same time, but the UPNP specification was published
> about 2 years ago, while MIDCOM is not quite finished yet. Looks like an
> interesting case study for the "problem statement" working group... 

producing bad stuff more quickly is not what I would regard as a useful goal.



From owner-ietf@ietf.org  Wed Jun 25 14:16:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23656
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 14:16:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VBz7-0002ig-9j
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 11:14:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VByr-0002YK-CF
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 11:14:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05341
	for <ietf@ietf.org>; Wed, 25 Jun 2003 00:13:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19V1fG-0001tu-00
	for ietf@ietf.org; Wed, 25 Jun 2003 00:13:46 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19V1f5-0001tm-00
	for ietf@ietf.org; Wed, 25 Jun 2003 00:13:35 -0400
Content-class: urn:content-classes:message
Subject: UPNP was:RE: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Date: Tue, 24 Jun 2003 21:13:23 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8E2@server2000.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: UPNP was:RE: myth of the great transition (was US Defense Department forma lly adopts IPv6)
Thread-Index: AcM51RmxgjfL/ALdT6iIq8Uxeq7B5wAdWHxoACCvjJA=
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Christian Huitema" <huitema@windows.microsoft.com>
Cc: "IETF" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Christian,


> Christian Huitema wrote:
> I don't quite get the point on the handling of
> incoming connections

The way I understand UPNP is that it will allow the automation (meaning,
no manual config of the NAPT box) of:

Server1: 192.168.1.10:80 <-> x.y.z.t:81
Server2: 192.168.1.11:80 <-> x.y.z.t:82
Server3: 192.168.1.12:80 <-> x.y.z.t:83

[x.y.z.t is the global public address]

In DNS you publish:
x.y.z.t server1.example.com
x.y.z.t server2.example.com
x.y.z.t server3.example.com

and you access the servers by:
http://server1.example.com:81
http://server2.example.com:82
http://server3.example.com:83



But what would be _really_ cool is if you could do this:

Server1: 192.168.1.10:80 <-> x.y.z.t:80
Server2: 192.168.1.11:80 <-> x.y.z.t:80
Server3: 192.168.1.12:80 <-> x.y.z.t:80
** and ** have the UPNP box select the proper NAT association based on
the requests.

In DNS you would still publish:
x.y.z.t server1.example.com
x.y.z.t server2.example.com
x.y.z.t server3.example.com

_BUT_ you could access the servers by:
http://server1.example.com
http://server2.example.com
http://server3.example.com
That's were the coolness is; no stinkin' port number.

As mentioned earlier there are some dirty ways to do it (hard state
piggied back on DNS requests) and less dirty (!=3D clean) (decapsulate
http host headers).

Michel.




From owner-ietf@ietf.org  Wed Jun 25 14:16:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23655
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 14:16:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VCnS-0005Bl-F6
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 12:06:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VCnS-0005Bg-7s
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 12:06:58 -0400
Received: from merlot.juniper.net (natint.juniper.net [207.17.136.129])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19071
	for <ietf@ietf.org>; Wed, 25 Jun 2003 12:06:24 -0400 (EDT)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h5PG0pu90386;
	Wed, 25 Jun 2003 09:00:51 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200306251600.h5PG0pu90386@merlot.juniper.net>
To: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
cc: ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
In-Reply-To: Your message of "Wed, 18 Jun 2003 11:04:52 PDT."
             <p05210606bb1655fef91b@[67.126.41.36]> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <35011.1056556828.1@juniper.net>
Date: Wed, 25 Jun 2003 09:00:28 -0700
From: Yakov Rekhter <yakov@juniper.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

Paul,

> At 10:15 AM +0200 6/18/03, Harald Tveit Alvestrand wrote:
> >I can think of some possible reasons, not necessarily exclusive
> >
> >- this is a bad idea/impossible to do well, so we shouldn't do it
> >- some other organization is already doing it, so we shouldn't
> >- we're too stupid to get it right, so we shouldn't do it
> >- the IETF is too large, so we shouldn't be adding more work
> 
> This might be a combination of the latter three, but I think it is 
> clearer for this WG:
> 
> - the IETF's track record for this work so far is quite poor
> 
> We have not shown any ability to create standards in this area with 
> due speed or predictability. 

I certainly agree with your on the "track record". But I think we
need to be a bit more specific on why the track record is "quite
poor". For example, why the IESG didn't approve 2547bis as a Proposed
Standard 2 years ago ?  Ditto for draft-martini... Perhaps folks
from the IESG would care to explain this...

Yakov.



From owner-ietf@ietf.org  Wed Jun 25 14:16:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23641
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 14:16:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VCcg-0004fQ-Or
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 11:55:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VCcg-0004fL-Hl
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 11:55:50 -0400
Received: from merlot.juniper.net (natint.juniper.net [207.17.136.129])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18410
	for <ietf@ietf.org>; Wed, 25 Jun 2003 11:55:47 -0400 (EDT)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h5PFi4u89126;
	Wed, 25 Jun 2003 08:44:04 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200306251544.h5PFi4u89126@merlot.juniper.net>
To: Paul Hoffman / IMC <phoffman@imc.org>
cc: vkompella@timetra.com, ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
In-Reply-To: Your message of "Wed, 18 Jun 2003 19:40:52 PDT."
             <p05210606bb16d08451dd@[63.202.92.152]> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <31227.1056555821.1@juniper.net>
Date: Wed, 25 Jun 2003 08:43:41 -0700
From: Yakov Rekhter <yakov@juniper.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

Paul,

> >Alternatively, we can own up that it is OUR problem, i.e., the IETF, and if 
> >we want a solution, we will create one here.
> 
> If we decide that "the problem" is one in our realm, I fully agree. 
> But transporting layer 2 stuff over IP is not a problem that affects 
> the Internet. It is a problem for the service providers marketing 
> departments. The past three yeas have proven that service providers 
> can satisfy their customers needs with L3VPNs, with 
> somewhat-interoperable L2VPNs, with non-interoperable L2VPNs, and 
> with just plain layer 2 circuits. 

I certainly agree with you that there are enough examples that
clearly show that service providers can satisfy their customers
needs with *multi-vendor* *interoperable* implementations based on
the *open* specs, where the spec is an Internet Draft, rather than
an IETF standard. In other words, an Internet Draft + working code
is both necessary *and* sufficient.

Yakov.



From owner-ietf@ietf.org  Wed Jun 25 14:22:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23994
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 14:22:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VDMt-0006iY-Ll
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 12:43:35 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VDMt-0006iT-D8
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 12:43:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20815
	for <ietf@ietf.org>; Wed, 25 Jun 2003 12:43:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VDMr-0005Jt-00
	for ietf@ietf.org; Wed, 25 Jun 2003 12:43:33 -0400
Received: from natint.juniper.net ([207.17.136.129] helo=merlot.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19VDMg-0005JQ-00
	for ietf@ietf.org; Wed, 25 Jun 2003 12:43:22 -0400
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h5PGgfu93505;
	Wed, 25 Jun 2003 09:42:41 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200306251642.h5PGgfu93505@merlot.juniper.net>
To: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
cc: ietf@ietf.org, yakov@juniper.net
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
In-Reply-To: Your message of "Wed, 18 Jun 2003 11:04:52 PDT."
             <p05210606bb1655fef91b@[67.126.41.36]> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <48030.1056559339.1@juniper.net>
Date: Wed, 25 Jun 2003 09:42:19 -0700
From: Yakov Rekhter <yakov@juniper.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

Paul,

> At 10:15 AM +0200 6/18/03, Harald Tveit Alvestrand wrote:
> >I can think of some possible reasons, not necessarily exclusive
> >
> >- this is a bad idea/impossible to do well, so we shouldn't do it
> >- some other organization is already doing it, so we shouldn't
> >- we're too stupid to get it right, so we shouldn't do it
> >- the IETF is too large, so we shouldn't be adding more work
> 
> This might be a combination of the latter three, but I think it is 
> clearer for this WG:
> 
> - the IETF's track record for this work so far is quite poor

the attached e-mail that have been posted to the PPVPN mailing
list sheds some light on why the IETF's track record for this
work so far is quite poor.

Yakov.
---------------------------------------------------------------------
Date:         Sun, 4 May 2003 13:24:58 -0700
Reply-To:     PPVPN <PPVPN@NORTELNETWORKS.COM>
Sender:       PPVPN <PPVPN@NORTELNETWORKS.COM>
From:         auto92679@HUSHMAIL.COM
Subject:      Strategy for VPN work in IETF
Comments: To: ppvpn@nortelnetworks.com
Comments: cc: problem-statement@alvestrand.no
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex Zinin writes:

> Since San Francisco IETF meeting the IESG has been considering the
> situation in the SUB-IP area and in the PPVPN Working Group in
> particular.

> Such close attention to this WG was triggered by numerous concerns

> thatthe IESG members received from the WG participants about limited
> and slow progress within the WG despite the efforts of the WG chairs
> and its members. The IESG also used this opportunity to consider
> the IETF area that the PPVPN work would fit best.

> After much deliberation, the involved ADs (Bert, Thomas, and I) are
> considering the following organizational changes in order to
> improve WG focus and productivity and ensure faster progress of the
> VPN-related work:

> 1. Split of Layer-2 and Layer-3 VPN work in separate Working Groups.

>   The L2 and L3 VPN work spaces are each big enough to warrant a
>   separate WG. While concentration of all VPN-related work in a
>   single forum was the right thing to do to ensure coordination
>   of efforts when the PPVPN WG was created and L2 VPN work came in,

>   such concentration is causing scaling problems within the WG at
>   this moment.

>   Migration of work into two separate WGs for L2 and L3 VPN
>   technologies with more specific WG charters will help to focus
>   discussions, prevent staff and meeting time overloading, and will
>   aid faster progress of corresponding technologies.

Alex,
The proposed solution ignores the origins of the problem.

The fact that PPVPN has been making any progress at all, despite the
bureaucracy imposed on it by the IESG is rather comendable.

This is a typically example of a WG which was setup despite many architectural
objections that it doesn't fit in the "internet" design. One cannot help
but to suspect that there was the hope ammoung the inner circles that
it would fail altogether. At least giving the ammount of "framework"
nonsense required and the interdiction to discuss solutions before a
framework is agreed upon.

The work of this working group is particularly harder given that this
is todays "fashion" area... work is much harder on such areas (like mpls
was a couple of years ago). One would suspect that the IESG
efforts to slow the WG steem also from concerns that fashion areas tend
to create a fair ammount of nonsense proposals most of which tend to
be naturally eliminated by the WGs.

Given the environment the performance of the ppvpn WG seems to me to
rather positive. It has actually come up with several documents that
are useful and deserve publication.

One of the reasons given here for this proposed disolution of the WG
is that the "L2VPN and L3VPN work spaces are big enought". However both
in the list and WG meetings it seems to me that the current l3vpn WG
is close to 0. The base document on l3vpn has been rather stable for
a while and it is not likely to change. The IESG/inner-circle has chosen
for mostly ideological reasons to attempt to marginalize this work so
it can hardly expect to be heard now.

It seems to me that if there is a problem w/ PPVPN that problem lies
within the IESG itself. As such i would like to propose to split the
IESG in two WGs: one that concerns itself w/ architecture and one group
that concerns itself with the process of documenting interoperable solutions
that are not known to be good or bad ideas until used in pratice. This
latter group should have the task to assure that the process is fair
and that both the pluses and minus of a solution are considered and documented.


One of the ideal caractheristics of the latter group would be if they
where to realize that by definition an IESG member is much less of an
expert in a given domain than the membership of the WG it steers. It
is humanly impossible for it to be otherwise. Unless you assume that
the membership of WG is 100% incompetent which is never the case. A steerer
cannot possibly be an expert in 20 groups it oversees... usually it can't
even keep up with the problems and technology due to the fact that there
is only 24 hours in each day.

In the rather arrogant terms of internet engineering, the IESG is by
definition the set of people that are "clueless". It is not possible
for it to be the other way around. No matter how wise and inteligent
IESG memebers are...

It is necessarly that the IESG understands that latter point and restricts
its job to document in a timely manner interoperable solutions for the
problems at hand regardless of personal opinion on the value of such
problems and technologies.
- ----
-----BEGIN PGP SIGNATURE-----
Version: Hush 2.2 (Java)
Note: This signature can be verified at https://www.hushtools.com/verify

wl4EARECAB4FAj61dxQXHGF1dG85MjY3OUBodXNobWFpbC5jb20ACgkQEMGDJWtDWfpc
ewCfaWN5FVNhieXVzimDk9cNYOZlgKAAnj3Hf8eWFmikSCDmAw1eMQVdEUb/
=GLPS
-----END PGP SIGNATURE-----





From owner-ietf@ietf.org  Wed Jun 25 15:10:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26509
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 15:10:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VFTP-0004Xc-C0
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 14:58:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VFTP-0004XX-11
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 14:58:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25425
	for <ietf@ietf.org>; Wed, 25 Jun 2003 14:58:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VFT8-0006CJ-00
	for ietf@ietf.org; Wed, 25 Jun 2003 14:58:10 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19VFSx-0006Bp-00
	for ietf@ietf.org; Wed, 25 Jun 2003 14:57:59 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003062514340220584
 for <ietf@ietf.org>; Wed, 25 Jun 2003 14:34:02 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 25 Jun 2003 14:23:36 -0400
Message-ID: <3EF9E8A7.1090101@centive.com>
Date: Wed, 25 Jun 2003 14:23:35 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: UPNP was:RE: myth of the great transition (was US Defense Department
 forma lly adopts IPv6)
References: <963621801C6D3E4A9CF454A1972AE8F504F8E2@server2000.arneill-py.sacramento.ca.us>
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F8E2@server2000.arneill-py.sacramento.ca.us>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Jun 2003 18:23:36.0119 (UTC) FILETIME=[E4576C70:01C33B46]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Michel Py wrote:

>In DNS you publish:
>x.y.z.t server1.example.com
>x.y.z.t server2.example.com
>x.y.z.t server3.example.com
>  
>
[...]

>That's were the coolness is; no stinkin' port number.
>  
>
You could publish URLs without port numbers if you could count on the 
clients recognizing SRV records.

-- 
/=====================================================\
|John Stracke      |jstracke@centive.com              |
|Principal Engineer|http://www.centive.com            |
|Centive           |My opinions are my own.           |
|=====================================================|
|"The Reality Check's in the mail." --L. Peter Deutsch|
\=====================================================/





From owner-ietf@ietf.org  Wed Jun 25 15:51:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28401
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 15:51:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VFIX-000462-00
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 14:47:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VFIW-00045x-Q7
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 14:47:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25090
	for <ietf@ietf.org>; Wed, 25 Jun 2003 14:47:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VFIV-000672-00
	for ietf@ietf.org; Wed, 25 Jun 2003 14:47:11 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VFII-00066x-00
	for ietf@ietf.org; Wed, 25 Jun 2003 14:46:59 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5PIkbn2022209
	for ietf@ietf.org env-from <vjs>;
	Wed, 25 Jun 2003 12:46:37 -0600 (MDT)
Date: Wed, 25 Jun 2003 12:46:37 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306251846.h5PIkbn2022209@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
References: <200306251642.h5PGgfu93505@merlot.juniper.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Yakov Rekhter <yakov@juniper.net>

> ...
> In the rather arrogant terms of internet engineering, the IESG is by
> definition the set of people that are "clueless". It is not possible
> for it to be the other way around. No matter how wise and inteligent
> IESG memebers are...
>
> It is necessarly that the IESG understands that latter point and restricts
> its job to document in a timely manner interoperable solutions for the
> problems at hand regardless of personal opinion on the value of such
> problems and technologies.

That is a valid position only if you assume the premise that the
IETF should publish RFCs on any and all subjects.

If you don't accept that premise but instead think the IETF should
only publish RFCs related to the Internet, then the inevitable
ignorance of the IESG is a valuable feature.  If the IESG is clueless
about something, then it is likely that whatever it is should be
handled outside the IETF.

It seems clear that much of the pressure for the IETF to deal with
this particular area as well as some other areas that have nothing
to do with "Internet engineering" is due to "forum shopping" by
people and organizations that also see the inevitable ignorance of
the IESG and IAB as a positive feature.  However, their intended
utilization of that ignorance is not respectable.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Wed Jun 25 16:11:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29774
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 16:11:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VGYT-0001dD-Tp
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 16:07:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VGUR-0001AI-Lu
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 16:03:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28983
	for <ietf@ietf.org>; Wed, 25 Jun 2003 16:03:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VGJ0-0006tQ-00
	for ietf@ietf.org; Wed, 25 Jun 2003 15:51:46 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19VGIp-0006sA-00
	for ietf@ietf.org; Wed, 25 Jun 2003 15:51:35 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003062515584123514
 for <ietf@ietf.org>; Wed, 25 Jun 2003 15:58:41 -0400
Received: from centive.com ([10.10.48.105]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 25 Jun 2003 15:48:15 -0400
Message-ID: <3EF9FC7F.30802@centive.com>
Date: Wed, 25 Jun 2003 15:48:15 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: UPNP was:RE: myth of the great transition (was US Defense Department
 forma lly adopts IPv6)
References: <963621801C6D3E4A9CF454A1972AE8F504F8E2@server2000.arneill-py.sacramento.ca.us>	<3EF9E8A7.1090101@centive.com> <20030625154144.3e9400d3.moore@cs.utk.edu>
In-Reply-To: <20030625154144.3e9400d3.moore@cs.utk.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Jun 2003 19:48:15.0656 (UTC) FILETIME=[B7FB4280:01C33B52]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:

>] You could publish URLs without port numbers if you could count on the 
>] cliens recognizing SRV records.
>
>use of SRV records for apps that aren't specified to use them is a
>violation of both those apps' protocols and the SRV specification.
>  
>
Agreed.  But it's an option for people who need to build new apps to 
kludge around NATs.

-- 
/=============================================================\
|John Stracke      |jstracke@centive.com                      |
|Principal Engineer|http://www.centive.com                    |
|Centive           |My opinions are my own.                   |
|=============================================================|
|*BOOM* "Thank you, Beaker. Now we know that is definitely too|
|much gunpowder." -- Dr. Bunsen Honeydew                      |
\=============================================================/





From owner-ietf@ietf.org  Wed Jun 25 16:12:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29851
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 16:12:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VGYT-0001dE-Os
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 16:07:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VGUb-0001BN-QI
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 16:03:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29104
	for <ietf@ietf.org>; Wed, 25 Jun 2003 16:03:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VGDn-0006pB-00
	for ietf@ietf.org; Wed, 25 Jun 2003 15:46:23 -0400
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VGDc-0006p7-00
	for ietf@ietf.org; Wed, 25 Jun 2003 15:46:12 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19VGCW-0003lo-00; Wed, 25 Jun 2003 12:45:04 -0700
Date: Wed, 25 Jun 2003 15:41:44 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John Stracke <jstracke@centive.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: UPNP was:RE: myth of the great transition (was US Defense
 Department forma lly adopts IPv6)
Message-Id: <20030625154144.3e9400d3.moore@cs.utk.edu>
In-Reply-To: <3EF9E8A7.1090101@centive.com>
References: <963621801C6D3E4A9CF454A1972AE8F504F8E2@server2000.arneill-py.sacramento.ca.us>
	<3EF9E8A7.1090101@centive.com>
X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

] >That's were the coolness is; no stinkin' port number.
] >  
] >
] You could publish URLs without port numbers if you could count on the 
] cliens recognizing SRV records.

but you can't, because this would break interoperability with the vast
majority of existing protocols; it also would not work with protocols that
don't use fixed port numbers. 

use of SRV records for apps that aren't specified to use them is a
violation of both those apps' protocols and the SRV specification.

Keith

p.s. yes, I know there are people who think it's okay to break the entire
installed base of Internet protocols in order to accomodate their pet kludge.




From owner-ietf@ietf.org  Wed Jun 25 16:28:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00516
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 16:28:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VGkk-0003Jk-3S
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 16:20:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VGg4-0002dW-9W
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 16:15:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29979
	for <ietf@ietf.org>; Wed, 25 Jun 2003 16:15:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VGg1-0007G8-00
	for ietf@ietf.org; Wed, 25 Jun 2003 16:15:33 -0400
Received: from natint.juniper.net ([207.17.136.129] helo=merlot.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19VGfq-0007Ff-00
	for ietf@ietf.org; Wed, 25 Jun 2003 16:15:22 -0400
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h5PKEeu13359;
	Wed, 25 Jun 2003 13:14:40 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200306252014.h5PKEeu13359@merlot.juniper.net>
To: Melinda Shore <mshore@cisco.com>
cc: vkompella@timetra.com, ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <19314.1056572059.1@juniper.net>
Date: Wed, 25 Jun 2003 13:14:19 -0700
From: Yakov Rekhter <yakov@juniper.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

Melinda,

> > Primarily, folks want to use it as in
> > "Ethernet-over-MPLS".  That may not necessarily go down
> > well with you either, but think of MPLS as a logical FR.
> 
> I think we need to retain a focus on connectionless,
> packet-oriented delivery and how to build on that.  

What makes you think that MPLS does not support "connectionless
packet-oriented delivery" ?

Yakov.



From owner-ietf@ietf.org  Wed Jun 25 16:37:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01117
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 16:37:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VFzA-0005D1-Vu
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 15:31:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VFyC-00054g-Mr
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 15:30:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27538
	for <ietf@ietf.org>; Wed, 25 Jun 2003 15:29:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VFxv-0006dh-00
	for ietf@ietf.org; Wed, 25 Jun 2003 15:29:59 -0400
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VFxk-0006cP-00
	for ietf@ietf.org; Wed, 25 Jun 2003 15:29:48 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19VFur-0005hN-00; Wed, 25 Jun 2003 12:26:49 -0700
Date: Wed, 25 Jun 2003 15:23:29 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: moore@cs.utk.edu, huitema@windows.microsoft.com, ietf@ietf.org
Subject: stupid nat tricks (was Re: UPNP )
Message-Id: <20030625152329.6093e6be.moore@cs.utk.edu>
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F8E2@server2000.arneill-py.sacramento.ca.us>
References: <963621801C6D3E4A9CF454A1972AE8F504F8E2@server2000.arneill-py.sacramento.ca.us>
X-Mailer: Sylpheed version 0.9.1 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

] But what would be _really_ cool is if you could do this:
] 
] Server1: 192.168.1.10:80 <-> x.y.z.t:80
] Server2: 192.168.1.11:80 <-> x.y.z.t:80
] Server3: 192.168.1.12:80 <-> x.y.z.t:80
] ** and ** have the UPNP box select the proper NAT association based on
] the requests.

no, that would be *really* ugly.  because then you'd expect the NAT box
to know how to intercept every application you'd want to use, despite the
fact that those applications are evolving and the set of those apps is
changing constantly.  so you'd have to upgrade your NAT every time you upgraded
installed a new app.

stupidity has no bounds.





From owner-ietf@ietf.org  Wed Jun 25 16:52:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01803
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 16:52:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VH6l-0006SQ-2D
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 16:43:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VH1n-0005mB-AI
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 16:38:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01166
	for <ietf@ietf.org>; Wed, 25 Jun 2003 16:38:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VH1l-0007Tj-00
	for ietf@ietf.org; Wed, 25 Jun 2003 16:38:01 -0400
Received: from natint.juniper.net ([207.17.136.129] helo=merlot.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19VH1a-0007TY-00
	for ietf@ietf.org; Wed, 25 Jun 2003 16:37:50 -0400
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h5PKb3u15664;
	Wed, 25 Jun 2003 13:37:03 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200306252037.h5PKb3u15664@merlot.juniper.net>
To: Pekka Savola <pekkas@netcore.fi>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <28281.1056573377.1@juniper.net>
Date: Wed, 25 Jun 2003 13:36:43 -0700
From: Yakov Rekhter <yakov@juniper.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

Pekka,

[clipped...]

> > From your message, I can't tell which of those, or of any number of other 
> > possible objections, is the basis of your objection.
> > 
> > BTW - all these things were already being worked on in PPVPN. Some were 
> > even described in the charter.
> 
> Fair question, I probably should have included more text in the first 
> place :-).
> 
> 1. Virtual Private LAN Service.  This is Internet-wise ethernet bridging
> over routing protocols such as BGP, IS-IS, etc; further, this has
> typically little respect for security implications which are implicit (or 
> even explicit) in LAN networks.
> 
> So, my main points are:
> 
>  - we must not overload routing protocols and such infrastructure (IMHO,
> this seems an inevitable path the work would go towards..)
> 
>  - we must not create complexity by deploying ethernet bridging all over
> the Internet.  Our work should be focused on making IP work, not
> specifying Ethernet-over-IP (or worse, Ethernet-over-IP as a *service*).

The proposed charter talks about VPLS "across an IP and an MPLS-enabled
IP network". Such a network does not have to be the Internet.

Yakov.



From owner-ietf@ietf.org  Wed Jun 25 17:15:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03510
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 17:15:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VGgP-0002ii-Cn
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 16:15:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VGch-0002Bc-Iv
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 16:12:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29751
	for <ietf@ietf.org>; Wed, 25 Jun 2003 16:11:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VGcC-0007Cz-00
	for ietf@ietf.org; Wed, 25 Jun 2003 16:11:36 -0400
Received: from natint.juniper.net ([207.17.136.129] helo=merlot.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19VGc1-0007C1-00
	for ietf@ietf.org; Wed, 25 Jun 2003 16:11:25 -0400
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h5PK9Su13001;
	Wed, 25 Jun 2003 13:09:28 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200306252009.h5PK9Su13001@merlot.juniper.net>
To: Randy Bush <randy@psg.com>
cc: Vach Kompella <vkompella@timetra.com>, ietf@ietf.org
Subject: RE: WG review: Layer 2 Virtual Private Networks (l2vpn)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <17407.1056571747.1@juniper.net>
Date: Wed, 25 Jun 2003 13:09:07 -0700
From: Yakov Rekhter <yakov@juniper.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

Randy,
 
> > "We're doing it" is a statement of fact.  However, we've been
> > doing it for over two years.  Pseudo-wire work has been ongoing
> > for over 4 years.  MPLS has been ongoing since 1996 or
> > thereabouts.
>  
> no disagreement.  the question i am hearing is not why is this
> being done, but rather why is the ietf working on a an l2 over l2
> protocol.  

Would you please elaborate on what makes MPLS an L2. For that matter
would you also explain what makes MPLS a layer on its own.
 
randy




From owner-ietf@ietf.org  Wed Jun 25 17:29:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04127
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 17:29:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VHdX-0002ts-3C
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 17:17:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VHWH-0001m8-Qs
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 17:09:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02895
	for <ietf@ietf.org>; Wed, 25 Jun 2003 17:09:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VHGY-0007eX-00
	for ietf@ietf.org; Wed, 25 Jun 2003 16:53:18 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VHGN-0007cl-00
	for ietf@ietf.org; Wed, 25 Jun 2003 16:53:07 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h5PKqJ521318;
	Wed, 25 Jun 2003 23:52:19 +0300
Date: Wed, 25 Jun 2003 23:52:18 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Yakov Rekhter <yakov@juniper.net>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
In-Reply-To: <200306252037.h5PKb3u15664@merlot.juniper.net>
Message-ID: <Pine.LNX.4.44.0306252351140.20992-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 25 Jun 2003, Yakov Rekhter wrote:
> > > From your message, I can't tell which of those, or of any number of other 
> > > possible objections, is the basis of your objection.
> > > 
> > > BTW - all these things were already being worked on in PPVPN. Some were 
> > > even described in the charter.
> > 
> > Fair question, I probably should have included more text in the first 
> > place :-).
> > 
> > 1. Virtual Private LAN Service.  This is Internet-wise ethernet bridging
> > over routing protocols such as BGP, IS-IS, etc; further, this has
> > typically little respect for security implications which are implicit (or 
> > even explicit) in LAN networks.
> > 
> > So, my main points are:
> > 
> >  - we must not overload routing protocols and such infrastructure (IMHO,
> > this seems an inevitable path the work would go towards..)
> > 
> >  - we must not create complexity by deploying ethernet bridging all over
> > the Internet.  Our work should be focused on making IP work, not
> > specifying Ethernet-over-IP (or worse, Ethernet-over-IP as a *service*).
> 
> The proposed charter talks about VPLS "across an IP and an MPLS-enabled
> IP network". Such a network does not have to be the Internet.

Of course; but I think it is reasonable to assume that in most cases it 
is.

Also, remember where the I in IETF comes from.  That's what our main focus 
should be at.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From owner-ietf@ietf.org  Wed Jun 25 17:29:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04131
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 17:29:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VHdM-0002sO-CP
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 17:16:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VHWM-0001mq-47
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 17:09:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02991
	for <ietf@ietf.org>; Wed, 25 Jun 2003 17:09:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VHD9-0007aW-00
	for ietf@ietf.org; Wed, 25 Jun 2003 16:49:47 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VHCo-0007ZW-00
	for ietf@ietf.org; Wed, 25 Jun 2003 16:49:26 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h5PKkOb21276;
	Wed, 25 Jun 2003 23:46:25 +0300
Date: Wed, 25 Jun 2003 23:46:23 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: grenville armitage <garmitage@swin.edu.au>
cc: ietf@ietf.org
Subject: Re: Layering purity Re: WG review: Layer 2 Virtual Private Networks
 (l2vpn)
In-Reply-To: <3EF1A2C8.5D17F254@swin.edu.au>
Message-ID: <Pine.LNX.4.44.0306252345280.20992-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 19 Jun 2003, grenville armitage wrote:
> Pekka Savola wrote:
> 	[..]
> > Moreover, we work on an IP layer.  We enable IP layer to be able to handle
> > our tasks.  If there is some problem why we cannot just use different IP
> > subnets between the two (or multiple) end-points, we need to fix that
> > problem, not burrow even further down the ISO layers.
> 
> Oh. A layering purist. I knew something didn't seem quite right.
> 
> And "just use different IP subnets" would solve mobile IP?

No; the primary goal of Mobile IP to provide connection survability.  
Unchanging IP address is just a means to get that.

> gja  (who should probably be disbarred for having once run IP over ATM
> over UDP/IP between New Jersey and Georgia because, well, there
> just wasn't a 'real' ATM link at the time and moving ATM cells
> was my task...)
> 

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From owner-ietf@ietf.org  Wed Jun 25 17:40:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04710
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 17:40:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VHrR-00055J-8Y
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 17:31:25 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VHnn-0004d2-1O
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 17:27:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04046
	for <ietf@ietf.org>; Wed, 25 Jun 2003 17:27:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VHnl-0000dM-00
	for ietf@ietf.org; Wed, 25 Jun 2003 17:27:37 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19VHna-0000c3-00
	for ietf@ietf.org; Wed, 25 Jun 2003 17:27:26 -0400
Content-class: urn:content-classes:message
Subject: RE: stupid nat tricks (was Re: UPNP )
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 25 Jun 2003 14:25:48 -0700
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F8E8@server2000.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: stupid nat tricks (was Re: UPNP )
Thread-Index: AcM7T9D03K/tzDcqQcuBF0nhH27clwADudWw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: "Christian Huitema" <huitema@windows.microsoft.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

] Michel Py wrote:
] But what would be _really_ cool is if you could do this:
] Server1: 192.168.1.10:80 <-> x.y.z.t:80
] Server2: 192.168.1.11:80 <-> x.y.z.t:80
] Server3: 192.168.1.12:80 <-> x.y.z.t:80
] ** and ** have the UPNP box select the proper NAT association
] based on the requests.

> Keith Moore wrote:
> no, that would be *really* ugly.  because then you'd expect the
> NAT box to know how to intercept every application you'd want
> to use, despite the fact that those applications are evolving
> and the set of those apps is changing constantly. so you'd have
> to upgrade your NAT every time you upgraded installed a new app.

What's the difference with the way it already is? The ALG component does
need to know about the app already.

Michel.




From owner-ietf@ietf.org  Wed Jun 25 19:52:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12512
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 19:52:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VJnw-0004Jz-EV
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 19:35:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VJgt-0002sL-AD
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 19:28:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11224
	for <ietf@ietf.org>; Wed, 25 Jun 2003 19:28:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VJgM-0002BB-00
	for ietf@ietf.org; Wed, 25 Jun 2003 19:28:06 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VJgB-0002Ae-00
	for ietf@ietf.org; Wed, 25 Jun 2003 19:27:55 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5PNR4N27654;
        Wed, 25 Jun 2003 19:27:05 -0400 (EDT)
Date: Wed, 25 Jun 2003 19:27:03 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: moore@cs.utk.edu, huitema@windows.microsoft.com, ietf@ietf.org
Subject: Re: stupid nat tricks (was Re: UPNP )
Message-Id: <20030625192703.63fa065e.moore@cs.utk.edu>
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F8E8@server2000.arneill-py.sacramento.ca.us>
References: <963621801C6D3E4A9CF454A1972AE8F504F8E8@server2000.arneill-py.sacramento.ca.us>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > no, that would be *really* ugly.  because then you'd expect the
> > NAT box to know how to intercept every application you'd want
> > to use, despite the fact that those applications are evolving
> > and the set of those apps is changing constantly. so you'd have
> > to upgrade your NAT every time you upgraded installed a new app.
> 
> What's the difference with the way it already is? The ALG component
> does need to know about the app already.

only for those apps that are NAT-sensitive.

what you propose would make every app NAT-sensitive, and increase the
rate of failures due to intermediaries that intercept protocol
interactions and botch them.



From owner-ietf@ietf.org  Wed Jun 25 19:52:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12517
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 19:52:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VJmX-00046y-H8
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 19:34:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VJiQ-0003Iq-KO
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 19:30:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11316
	for <ietf@ietf.org>; Wed, 25 Jun 2003 19:30:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VJiO-0002Cp-00
	for ietf@ietf.org; Wed, 25 Jun 2003 19:30:12 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19VJiD-0002CG-00
	for ietf@ietf.org; Wed, 25 Jun 2003 19:30:02 -0400
Content-class: urn:content-classes:message
Subject: RE: stupid nat tricks (was Re: UPNP )
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 25 Jun 2003 16:29:49 -0700
Message-ID: <963621801C6D3E4A9CF454A1972AE8F5067292@server2000.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: stupid nat tricks (was Re: UPNP )
Thread-Index: AcM7cWQ5IXJkQ9GRRv6Bm2SnItVHJQAAAVTg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: "Christian Huitema" <huitema@windows.microsoft.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> what you propose would make every app NAT-sensitive, and
> increase the rate of failures due to intermediaries that
> intercept protocol interactions and botch them.

You do have a point here. Stupid idea it was.

Michel.




From owner-ietf@ietf.org  Wed Jun 25 19:53:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12561
	for <ietf-web-archive@odin.ietf.org>; Wed, 25 Jun 2003 19:53:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VJnz-0004L0-LF
	for ietf-list@asgard.ietf.org; Wed, 25 Jun 2003 19:35:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VJld-0003wS-TL
	for ietf@asgard.ietf.org; Wed, 25 Jun 2003 19:33:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11503
	for <ietf@ietf.org>; Wed, 25 Jun 2003 19:33:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VJlc-0002FZ-00
	for ietf@ietf.org; Wed, 25 Jun 2003 19:33:32 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VJlR-0002FW-00
	for ietf@ietf.org; Wed, 25 Jun 2003 19:33:21 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h5PNWSN27664;
        Wed, 25 Jun 2003 19:32:29 -0400 (EDT)
Date: Wed, 25 Jun 2003 19:32:27 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John Stracke <jstracke@centive.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: SRV (was Re: UPNP was :RE: myth ...)
Message-Id: <20030625193227.753652bb.moore@cs.utk.edu>
In-Reply-To: <3EF9FC7F.30802@centive.com>
References: <963621801C6D3E4A9CF454A1972AE8F504F8E2@server2000.arneill-py.sacramento.ca.us>
	<3EF9E8A7.1090101@centive.com>
	<20030625154144.3e9400d3.moore@cs.utk.edu>
	<3EF9FC7F.30802@centive.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> >use of SRV records for apps that aren't specified to use them is a
> >violation of both those apps' protocols and the SRV specification.
> >  
> >
> Agreed.  But it's an option for people who need to build new apps to 
> kludge around NATs.

presuming, of course, that the app only needs to communicate with peers
in a single addressing realm outside the nat, and the app knows what
its external address/port is, and the app is able to arrange for the SRV
records to reflect that, and the address binding doesn't change during
the TTL of the SRV records. which, taken together, is a big stretch.




From owner-ietf@ietf.org  Thu Jun 26 10:11:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26638
	for <ietf-web-archive@odin.ietf.org>; Thu, 26 Jun 2003 10:11:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VXCy-000074-Ku
	for ietf-list@asgard.ietf.org; Thu, 26 Jun 2003 09:54:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Urpm-00046G-WB
	for ietf@asgard.ietf.org; Tue, 24 Jun 2003 13:43:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26527;
	Tue, 24 Jun 2003 13:42:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Uroi-0004oJ-00; Tue, 24 Jun 2003 13:42:52 -0400
Received: from wireless206.east.isi.edu ([65.123.202.206] helo=purple.nge.isi.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19UroX-0004ne-00; Tue, 24 Jun 2003 13:42:41 -0400
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.9/8.12.9) with SMTP id h5OHJYFp042862;
	Tue, 24 Jun 2003 13:19:34 -0400 (EDT)
	(envelope-from csp@csperkins.org)
Date: Tue, 24 Jun 2003 13:19:33 -0400
From: Colin Perkins <csp@csperkins.org>
To: ned.freed@mrochek.com
Cc: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: SDP attribute for qualifying Media Formats with
 Generic Parameters to a Proposed Standard
Message-Id: <20030624131933.461184dd.csp@csperkins.org>
In-Reply-To: <01KXB6JAPVBE00CUGD@mauve.mrochek.com>
References: <E19T4zG-00044l-CY@asgard.ietf.org>
	<01KXB6JAPVBE00CUGD@mauve.mrochek.com>
Organization: http://csperkins.org/
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386-unknown-freebsd4.8)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--> ned.freed@mrochek.com writes:
> > The IESG has received a request from Individual Submissions WG to
> > consider the following Internet-Draft(s) as a Proposed Standard. This
> > has been reviewed in the IETF but is not the product of an IETF Working
> > Group. o Individual Submissions (NONE): SDP attribute for qualifying
> > Media
> >   Formats with Generic Parameters
> >     <draft-rajeshkumar-mmusic-gpmd-03.txt>
> >     Proposed Standard
> 
> This looks to me like a substantive duplication of the media features
> facility defined in RFC 2533 and elaborated on in RFCs 2506, 2530, 2534,
> 2738, 2912, 2913, 2938, and 2987. Not only does this set of documents
> provide a full-featured media feature tagging and content negotiation
> facility, the relationship to MIME media types and parameters has also
> been worked out.

This draft adds a new namespace within the existing feature description
syntax (RFC 2327) and parameter negotiation (RFC 3264) model of SDP. It
is intentionally independent of MIME types, and their parameters, which
are mapped onto SDP in other ways (typically through RTP Payload Type
registrations).

> Although the media features facility defined in these various RFCs is
> perhaps too elaborate for SDP's needs, it should at least be possible to
> reuse the basic descriptive elements of media features and the
> corresponding media features registry.
> 
> At a minimum this draft needs to explain why the existing media features
> facility is unsuitable for SDP's use and another, similar facility needs
> to be defined.

That's an issue for SDP in general, which has a feature description and
negotiation mechanism incompatible with - and to large extent predating -
the RFCs you mention, but is out of scope of this draft. 

The SDPng work in MMUSIC references the RFCs you mention, and is looking to
reuse as much as possible from them. I think it's too late for SDP to adopt
them, because of the need to maintain backwards compatibility with a large
installed base.

Colin





From owner-ietf@ietf.org  Thu Jun 26 12:51:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08784
	for <ietf-web-archive@odin.ietf.org>; Thu, 26 Jun 2003 12:51:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VZ6y-0007gU-2P
	for ietf-list@asgard.ietf.org; Thu, 26 Jun 2003 11:56:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VYjV-0004hg-7s
	for ietf@asgard.ietf.org; Thu, 26 Jun 2003 11:32:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03203
	for <ietf@ietf.org>; Thu, 26 Jun 2003 11:30:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VYiC-0002k2-00
	for ietf@ietf.org; Thu, 26 Jun 2003 11:31:00 -0400
Received: from coconut.itojun.org ([219.101.47.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VYhy-0002j8-00
	for ietf@ietf.org; Thu, 26 Jun 2003 11:30:49 -0400
Received: from itojun.org (localhost [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP id A61859A
	for <ietf@ietf.org>; Fri, 27 Jun 2003 00:01:48 +0900 (JST)
To: ietf@ietf.org
In-reply-to: ietf-secretariat's message of Thu, 26 Jun 2003 10:45:06 -0400.  <200306261445.KAA28611@ietf.org> 
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
Subject: Re: 57th IETF - Social Event 
From: itojun@iijlab.net
Date: Fri, 27 Jun 2003 00:01:48 +0900
Message-Id: <20030626150148.A61859A@coconut.itojun.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

>You can register on-line for the social event at:
>http://files.aon.at/ietf/payment.htm

	what kind of social event will it be?  there's no hints given.
	is it a surprise party?

itojun



From owner-ietf@ietf.org  Thu Jun 26 13:39:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10658
	for <ietf-web-archive@odin.ietf.org>; Thu, 26 Jun 2003 13:39:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VaN8-0001k7-P7
	for ietf-list@asgard.ietf.org; Thu, 26 Jun 2003 13:17:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VaMf-0001Gf-Co
	for ietf@asgard.ietf.org; Thu, 26 Jun 2003 13:16:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10014
	for <ietf@ietf.org>; Thu, 26 Jun 2003 13:16:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VaMP-00041U-00
	for ietf@ietf.org; Thu, 26 Jun 2003 13:16:37 -0400
Received: from mail.siemenscom.com ([12.146.131.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VaME-00041D-00
	for ietf@ietf.org; Thu, 26 Jun 2003 13:16:26 -0400
Received: from mail-stc.rolm.com (mail-stc.siemenscom.com [12.146.131.7])
	by mail.siemenscom.com (8.9.3p2/8.9.3) with ESMTP id KAA04290;
	Thu, 26 Jun 2003 10:15:05 -0700 (PDT)
Received: from stca200a.bus.sc.rolm.com (stca200a.bus.sc.rolm.com [165.218.68.180])
	by mail-stc.rolm.com (8.11.6/8.11.6) with ESMTP id h5QH2vB15022;
	Thu, 26 Jun 2003 10:02:58 -0700 (PDT)
Received: by stca200a.bus.sc.rolm.com with Internet Mail Service (5.5.2653.19)
	id <MDLQRZM0>; Thu, 26 Jun 2003 10:15:46 -0700
Message-ID: <DA2CCB2AC5F7E447B18E19D786093BB201D3F17E@stca952a.eng.sc.rolm.com>
From: "Kozdon, Peter" <Peter.Kozdon@icn.siemens.com>
To: "'itojun@iijlab.net'" <itojun@iijlab.net>, ietf@ietf.org
Subject: RE: 57th IETF - Social Event 
Date: Thu, 26 Jun 2003 10:12:29 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

Check out the "home" link on this page for details 

http://files.aon.at/ietf/index.htm 


Peter Kozdon


-----Original Message-----
From: itojun@iijlab.net [mailto:itojun@iijlab.net] 
Sent: Thursday, June 26, 2003 8:02 AM
To: ietf@ietf.org
Subject: Re: 57th IETF - Social Event 

>You can register on-line for the social event at:
>http://files.aon.at/ietf/payment.htm

	what kind of social event will it be?  there's no hints given.
	is it a surprise party?

itojun



From owner-ietf@ietf.org  Thu Jun 26 13:57:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11500
	for <ietf-web-archive@odin.ietf.org>; Thu, 26 Jun 2003 13:57:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VayJ-0004uA-JR
	for ietf-list@asgard.ietf.org; Thu, 26 Jun 2003 13:55:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VaxV-0004ar-Mu
	for ietf@asgard.ietf.org; Thu, 26 Jun 2003 13:54:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11359
	for <ietf@ietf.org>; Thu, 26 Jun 2003 13:54:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VaxU-0004Ib-00
	for ietf@ietf.org; Thu, 26 Jun 2003 13:54:56 -0400
Received: from tomts21-srv.bellnexxia.net ([209.226.175.183])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VaxJ-0004IG-00
	for ietf@ietf.org; Thu, 26 Jun 2003 13:54:45 -0400
Received: from yahoo.com ([65.93.188.174]) by tomts21-srv.bellnexxia.net
          (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP
          id <20030626175422.KPKG25826.tomts21-srv.bellnexxia.net@yahoo.com>
          for <ietf@ietf.org>; Thu, 26 Jun 2003 13:54:22 -0400
Date: Thu, 26 Jun 2003 13:54:24 -0400
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: microsoft nat comment
From: S Woodside <sbwoodside@yahoo.com>
To: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <38C4700C-A7FF-11D7-B51A-000393414368@yahoo.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

     http://wifinetnews.com/archives/001828.html

[Microsoft's Jawad Khaki (Corporate Vice President, Windows Networking 
and Communications Technologies, Microsoft Corporation) ]

One of his remarks: "What I call the evil NATs" are stifling the 
ability for people to get connected. (Interestingly, Bob Frankston, who 
worked at Microsoft to develop home networking the mid-90s, told me in 
late 2002 that he calls himself the father of NAT and said that NAT was 
one of the biggest mistakes he made. He shoulda gone with IPv6, he 
said.)

simon




From owner-ietf@ietf.org  Thu Jun 26 15:43:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18201
	for <ietf-web-archive@odin.ietf.org>; Thu, 26 Jun 2003 15:43:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VcMy-0004jZ-TR
	for ietf-list@asgard.ietf.org; Thu, 26 Jun 2003 15:25:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VcMl-0004SA-Fc
	for ietf@asgard.ietf.org; Thu, 26 Jun 2003 15:25:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17172
	for <ietf@ietf.org>; Thu, 26 Jun 2003 15:24:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VcMV-00059z-00
	for ietf@ietf.org; Thu, 26 Jun 2003 15:24:51 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VcMK-00059W-00
	for ietf@ietf.org; Thu, 26 Jun 2003 15:24:40 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 9241F1390E
	for <ietf@ietf.org>; Thu, 26 Jun 2003 19:11:47 +0000 (GMT)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ietf@ietf.org
Subject: concerning draft-josefsson-dns-url-08.txt
X-Mailer: MH-E 7.4; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 26 Jun 2003 19:11:47 +0000
Message-Id: <20030626191147.9241F1390E@sa.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the 
> iesg@ietf.org or ietf@ietf.org mailing lists by 2003-7-22.

i have one comment on document quality (DQ) and one protocol quality (PQ).

DQ: the url scheme syntax allows a given dnsqueryelement to be validly
specified more than once, but does not explain whether the first or last
instance of a duplicate dnsqueryelement will be the one in effect.  this
ambiguity could be resolved by changing the syntax so that duplicates
are invalid, or by stating that the first or last dnsqueryelement
instance "wins".

PQ: the url scheme does not allow the RD bit to be set.  of all the DNS
and EDNS flags and options which might affect the results of the query,
only RD can really be thought to be "missing" from this specification,
and only in the case where the "hostport" is given.  however, it may be
wise to permit the specification of other flags, and EDNS OPT options, so
that if a future flag or option block is added which affects the results
of a query in the way RD can do, the URI syntax for it will already be known.



From owner-ietf@ietf.org  Thu Jun 26 16:24:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20053
	for <ietf-web-archive@odin.ietf.org>; Thu, 26 Jun 2003 16:24:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VdEC-0003F4-3b
	for ietf-list@asgard.ietf.org; Thu, 26 Jun 2003 16:20:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VdDa-0002xy-9w
	for ietf@asgard.ietf.org; Thu, 26 Jun 2003 16:19:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19761
	for <ietf@ietf.org>; Thu, 26 Jun 2003 16:19:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VdDK-0005c4-00
	for ietf@ietf.org; Thu, 26 Jun 2003 16:19:26 -0400
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 19VdD9-0005bu-00
	for ietf@ietf.org; Thu, 26 Jun 2003 16:19:15 -0400
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 19VdCZ-0002yS-00
	for <ietf@ietf.org>; Thu, 26 Jun 2003 21:18:39 +0100
Date: Thu, 26 Jun 2003 21:18:39 +0100
To: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
Message-ID: <20030626201839.GA6888@fysh.org>
References: <20030626191147.9241F1390E@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030626191147.9241F1390E@sa.vix.com>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

Paul Vixie wrote:
>PQ: the url scheme does not allow the RD bit to be set.

The draft says "A DNS URI designates a DNS resource record set ... by
domain name, type, class and server.".  That is, it identifies a location
within the abstract domain name space, a location which may contain
an RRset.  The setting of the RD bit doesn't affect which RRset is
designated; all it can affect is whether a query succeeds in returning
the requested RRset.  Nothing in the DNS URI so far refers to a specific
query mechanism, and indeed I can see reasonable uses for the URI form
that don't involve making any queries, via the DNS protocol or otherwise.

In summary, adding control of the RD bit would turn the DNS URI into
something else, something that I don't think it should be.

I see a couple of editorial nits, quite separate from the above:

0. The ABNF for <dnsqueryelement> uses "|" instead of "/" characters to
separate branches.

1. The grammar allows <dnsname> to be zero-length.

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



From owner-ietf@ietf.org  Thu Jun 26 19:21:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26830
	for <ietf-web-archive@odin.ietf.org>; Thu, 26 Jun 2003 19:21:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Vfmt-00060R-Nw
	for ietf-list@asgard.ietf.org; Thu, 26 Jun 2003 19:04:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VfmO-0005jH-Bh
	for ietf@asgard.ietf.org; Thu, 26 Jun 2003 19:03:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26228
	for <ietf@ietf.org>; Thu, 26 Jun 2003 19:03:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vflm-0006qB-00
	for ietf@ietf.org; Thu, 26 Jun 2003 19:03:10 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vflb-0006p5-00
	for ietf@ietf.org; Thu, 26 Jun 2003 19:02:59 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 42B3513973; Thu, 26 Jun 2003 23:02:09 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
References: <20030626191147.9241F1390E@sa.vix.com>
	<20030626201839.GA6888@fysh.org>
From: Paul Vixie <vixie@vix.com>
Date: 26 Jun 2003 23:02:09 +0000
In-Reply-To: <20030626201839.GA6888@fysh.org>
Message-ID: <g365msqw7i.fsf@sa.vix.com>
Lines: 16
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> >PQ: the url scheme does not allow the RD bit to be set.
> 
> The draft says "A DNS URI designates a DNS resource record set ... by
> domain name, type, class and server.".  That is, it identifies a location
> within the abstract domain name space, a location which may contain
> an RRset.

this statement would only be an answer to my concern if there were no way
to direct the query to a particular server using the "hostport" syntax.  if
we're going to give the URL syntax a way to designate a server other than
the one which is authoritatively responsible for the data, or a local caching
resolver (also called a "recursive nameserver"), then we need to be able to
set the RD bit.  personally, i like your answer better, but to reach that
answer we would have to remove the "hostport" syntax from the proposal.
-- 
Paul Vixie



From owner-ietf@ietf.org  Thu Jun 26 19:43:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27531
	for <ietf-web-archive@odin.ietf.org>; Thu, 26 Jun 2003 19:43:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VgLj-0007ds-VY
	for ietf-list@asgard.ietf.org; Thu, 26 Jun 2003 19:40:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VgL5-0007MH-RT
	for ietf@asgard.ietf.org; Thu, 26 Jun 2003 19:39:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27385;
	Thu, 26 Jun 2003 19:39:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VgL3-00078a-00; Thu, 26 Jun 2003 19:39:37 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VgKs-00077e-00; Thu, 26 Jun 2003 19:39:26 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h5QNfJF07319;
	Thu, 26 Jun 2003 16:41:19 -0700
Date: Thu, 26 Jun 2003 16:37:50 -0700
From: Dave Crocker <dhc@dcrocker.net>, Marshall Rose  <mrose@dbc.mtview.ca.us>
X-Mailer: The Bat! (v1.63 Beta/11) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
X-Priority: 3 (Normal)
Message-ID: <27241731952.20030626163750@brandenburg.com>
To: iesg@ietf.org
CC: impp@iastate.edu, ietf <IETF@ietf.org>
Subject: Re: Last Call: A Model for Presence and Instant Messaging to Proposed Standard
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Folks,

This note cites substantive process and technical problems with the
candidate specifications being submitted from the Instant Messaging and
Presence (IMPP) working group. The group's charter specifies the scope
to be to "define protocols and data formats necessary to build an
Internet-scale end-user presence awareness, notification and instant
messaging system".

IMPP discussions began January, 1997 -- 5 1/2 years ago. It took one
year to get chartered and another year to develop requirements, which
were finally issued on February, 2000 (RFCs 2778-9). There have been no
RFCs issued in the 3 1/2 years since then.

Protocol development efforts were thwarted by the existence of several
different technical constituencies and much effort, but no progress, at
reconciling them. Two and a half years ago, the area directors
acknowledged that a single, homogeneous protocol was not going to be
developed, so they called for development of a "gatewaying"
specification -- CPIM. They hoped to permit interconnection among the
heterogeneous protocols being proposed, with the possibility of also
interconnecting the various and popular services already in use.
Unfortunately, this fundamental change in working group direction was
never formally documented or approved through a charter revision.

The issues discussed below have previously been raised in the working
group, over the last year. The concerns raised were not resolved.

The working group's output suffers from:

     1.   PROCESS FAILURES
     1.1. Lack of participation and constituency
     1.2. Out of scope with charter
     1.3. Failure to resolve issues raised in the working group

     2.   TECHNICAL FAILURES
     2.1. Confused and conflicting goals
     2.2. Incomplete and unclear specifications.

IMPP has a long and erratic history. It has incurred multiple changes in
direction and multiple changes in its staff and oversight. The proffered
work reflects this.


Let's consider each of these points:



1.   PROCESS FAILURES

1.1. Lack of participation and constituency

Who is the audience for this work and what is the basis for believing
the work will be used?  The documents claim a goal of interoperability
among heterogeneous IM and Presence services, but the normative content
of the work precludes that goal.

In fact the normative work is for an end-to-end, homogeneous service.
Who will implement and use such work, and why?

A strong indication that the work is not relevant to the Internet
technical and operations community has been a dramatic drop-off in
participation.

The working group has been essentially inactive for the 6 months of
2003, except for a post hoc exercise to write a "charter".

During the 12 months before that, no more than 15 people made regular
contributions (using roughly one posting per month as the threshold.)
Only 10 of these participants posted 2 or more messages per month during
that time.

In reality, for the last 18 months, the real working group activity has
been a dialogue among 4-5 people, with very few other participants.

This does not bode well at all for industry interest in -- and use of --
this work product.


1.2. Out of scope with charter

For the last 2.5 years, the working group has been operating without a
meaningful charter. All of the work done during that time is out of
scope with the text of the original charter.

The lack of a concrete, updated charter has allowed the WG to behave in
an arbitrary fashion with respect to its choice of technical goals and
the soundness of the engineering decisions it has made. This explains,
for example, why there is no rationale for honoring some IMPP
requirements, but not others.
    
Recently, at the request of an Area Director, the co-chairs authored
draft-day-atkins-impp-defacto-00 as a "de facto" charter. Several
participants have objected to this contribution, but its authors have
not responded to the issues raised.

Although proposing a "de facto" charter is one way of appearing to
legitimize the WG's behavior, the ADs would be well served by returning
to first principles and asking themselves whether the WG has adhered to
architectural and engineering principles that are sound, and whether
there is a reasonable basis for believing that this work will get
serious use on the Internet.

Equally importantly, we either believe in the rules or we don't. The
rules say that work-product has to conform to charter. The rules do not
say "do some work, then write a charter to reflect the work-product".
Even if the proffered work was a marvel of architectural soundness and
engineering quality (which, as we'll discuss below, it clearly isn't),
this "ex post facto" approach would raise the hackles of anyone who
considers consistent IETF process to be a mandatory thing.


1.3. Failure to resolve issues raised in the working group

The issues listed in the Section 2 below (Technical Failures) were all
raised carefully during the working group process. They remain
unresolved and some received no response.

The problem with the group's dichotomy between end-to-end vs. gateway
goals was discussed repeatedly.  Only towards the end of the working
group's effort did this appear to become resolved -- in the direction of
an end-to-end content standard.  However, even then it was clear that the
few remaining participants in the group continued to hold very different
understandings of the goal.  Consequently, the confusion in the working
group documents, on this point, is a regrettable, though accurate,
rendition of the unresolved problem within the group.



2.   TECHNICAL FAILURES

2.1. Confused and conflicting goals

The nature and the detail of these specifications are incomplete and
often unclear. The work shows a split between the claimed goal of
interconnecting heterogeneous IM and Presence services, versus the
actual goal of specifying homogeneous, end-to-end IM and Presence
services.

The specifications call for features that go beyond what is required for
a minimal functional core of interoperability. These added features
serve to severely reduce the likelihood that the specifications will be
used for interconnecting heterogeneous services.

As noted in a curious discussion within the working group, recently, the
IMPP Requirements documents were used arbitrarily for justifying some
design decisions, but not others.  There is no basis for knowing why
those requirements sometimes applied to the IM and Presence "gatewaying"
work but at other times did not.
    
Consider this fragment from Section 3.3 (Format of Instant Messages) of
draft-ietf-impp-im-03:

     This specification defines an abstract interoperability mechanism for
     instant messaging protocols; the message content definition given
     here pertains to semantics rather than syntax.  However, some
     important properties for interoperability can only be provided if a
     common end-to-end format for instant messaging is employed by the
     interoperating instant messaging protocols, especially with respect

In other words, this specifies (and requires implementation of support
for) an end-to-end syntax as well as semantics.

It should be noted that the message format, defined by the working
group, is new and will require a new suite of parsers, generators, and
editors.  Although it purports to be a sub-set of RFC822, the format has
notable requirements -- such as Unicode -- that are not in RFC822. While
the desire to improve on existing practise is laudable, it defeats the
goal of gatewaying heterogeneous systems.


2.2. Incomplete and unclear specifications.

(Lest there be any misunderstanding about this title of this
sub-section, it is meant to cover the reasons that -- independent of
process and goal debates -- the specifications "won't work".)

Simply put, the specification suffer key omissions and ambiguities which
make development of interoperable implementations highly unlikely.
Consider this fragment Section 3.1 (Overview of Instant Messaging
Service) of draft-ietf-impp-im-03:

     its initial value is set by the originator.  The TransID is a unique
     identifier used to correlate message operations to response

"Unique" is not specified in any of the documents.  The obvious
question is: unique with what scope?

Ensuring uniqueness in transaction identifiers is a well-known
challenge, with well-known resolutions -- notably from the transport
arena. Yet the specification does not mention it.  This makes it likely
that some implementations will create ambiguous TransIDs.

    
Alternatively, consider this fragment from Section 3.4.1 (The Message
Operation) of draft-ietf-impp-im-03:

     When an application wants to send an INSTANT MESSAGE, it invokes the
     message operation.

     When an instant messaging service receives the message operation, it
     performs the following preliminary checks:

Does this refer to the application/im-client interaction, the
im-client/im-server interaction, or what?

Or consider this other fragment from draft-ietf-impp-im-03:
    
     4.  Provided these checks are successful:

     If the instant messaging service is able to successfully
     deliver the message, a response operation having status
     "success" is invoked.

     If the service is unable to successfully deliver the message,
     a response operation having status "failure" is invoked.

     If the service must delegate responsibility for delivery (i.e.
     if it is acting as a gateway or proxying the operation), and
     if the delegation will not result in a future authoritative
     indication to the service, a response operation having status

This demonstrates a very serious effect from using the fuzzy term
'service' rather than citing specific component-component interactions:
It appears to mean that there is an end-to-end, real-time dependency
chain for generating a response to a request. Each node along a relay
path must withhold generating a response until the next node gives it
the delivery -- i.e., the final -- status result.

Note that this is fundamentally different from Email. In effect, it uses
the equivalent to the Email SMTP Delivery Status Notification as the
*sole* operations response mechanisms, with no intermediate (hop-by-hop)
relaying report.

    
Similarly, consider Section 3.1 (3.1 Overview of the Presence Service)
of draft-ietf-impp-pres-03:

     The duration specifies the
     maximum number of seconds that the SUBSCRIPTION should be active
     (which may be zero, in which case this is a one-time request for
     presence information).
     ...
     If the duration parameter is non-zero, then for up to the specified
     duration, the service invokes the notify operation whenever there are
     any changes to the PRESENTITY's presence information.

How can "duration" have any useful meaning when there is no baseline
reference for the starting point or ending point of the duration and
when Internet exchange latencies are completely unpredictable? In other
words, when a participant receives a duration value from another
participant, what does it mean? Duration relative to what point of time?
We do not know how many seconds it took for the service data to reach
the receiving participant.

But wait! Here are three more examples:
    
This fragment is from Section 3 (Address Resolution) of
draft-ietf-impp-srv-03:

     A client determines the address of an appropriate system running a
     server, on behalf of the system referenced by the domain, by
     resolving the destination domain name that is part of the identifier
     to either an intermediate relay system or a final target system.

This is the first, normative section in the document.  Yet it does not
define 'address' nor refer to URI or URLs. There is no sense of what
"appropriate' means, nor what "system referenced by the domain" means.

Use of the term "identifier" suggests at least some confusion with the
otherwise-used term "address".

Or consider this fragment from Section 5 (Processing SRV RRs), ibid:
    
     ...
     The choice of IM transfer protocol is a local configuration option
     for each system.

Besides not indicating *whose* choice is being cited, this text leaves
quite a bit unspecified.  The change that was previously suggested was
intended to make the roles and actions of participating parties
explicitly clear:

"Receiving systems that are registered for this DNS-based SRV resolution
service list the transfer protocols by which they can be reached, either
directly or through a translating gateway. The transfer-time choice of
the IM transfer protocol to be used (and, therefore, to be resolved) is
a local configuration option for each sending system."
    
Or consider this fine gem from from Section 5 (Processing SRV RRs), ibid:    
    
     Using this mechanism, seamless routing of IM traffic is possible,
     regardless of whether a gateway is necessary for interoperation.  To
     achieve this transparency, a separate RR for a gateway must be
     present for each transfer protocol and domain pair that it serves.

"domain <<pair>> that it serves"?

I suspect that this should be "transfer protocol and target domain that
it serves".
    
Let's face it: the proffered work has no realistic chance of meaningful
interoperable implementation.



CONCLUSIONS:
    
The proffered specifications represent many person-hours of
well-intentioned effort. However the documents suffer fatally from
delay, lack of focus, and lack of a clear charter. In their current
form, they represent a fundamental violation of IETF process; they have
no obvious user community to embrace them; and they would not work if
there were one.


/Dave
/Marshall

-----
Dave Crocker <dcrocker@brandenburg.com> (Brandenburg InternetWorking)
Marshall Rose  <mrose@dbc.mtview.ca.us> (Dover Beach Consulting)




From owner-ietf@ietf.org  Thu Jun 26 20:12:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28252
	for <ietf-web-archive@odin.ietf.org>; Thu, 26 Jun 2003 20:12:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Vgmq-0007Ie-1R
	for ietf-list@asgard.ietf.org; Thu, 26 Jun 2003 20:08:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VgmW-00071H-7f
	for ietf@asgard.ietf.org; Thu, 26 Jun 2003 20:08:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28089;
	Thu, 26 Jun 2003 20:07:42 -0400 (EDT)
From: hardie@qualcomm.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VgkX-0007J1-00; Thu, 26 Jun 2003 20:05:57 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VgkM-0007Iw-00; Thu, 26 Jun 2003 20:05:46 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by ithilien.qualcomm.com (8.12.9/8.12.5/1.0) with ESMTP id h5R05KZf023429;
	Thu, 26 Jun 2003 17:05:20 -0700 (PDT)
Received: from [129.46.227.161] (carbuncle.qualcomm.com [129.46.227.161])
	by neophyte.qualcomm.com (8.12.9/8.12.5/1.0) with ESMTP id h5R05Huh026713;
	Thu, 26 Jun 2003 17:05:18 -0700 (PDT)
Mime-Version: 1.0
X-Sender: hardie@mage.qualcomm.com
Message-Id: <p0600120abb21385f5f07@[129.46.227.161]>
In-Reply-To: <27241731952.20030626163750@brandenburg.com>
References: <27241731952.20030626163750@brandenburg.com>
Date: Thu, 26 Jun 2003 17:05:14 -0700
To: Dave Crocker <dcrocker@brandenburg.com>, iesg@ietf.org
Subject: Re: Last Call: A Model for Presence and Instant Messaging to
 Proposed Standard
Cc: impp@iastate.edu, Dave Crocker <dhc@dcrocker.net>,
        Marshall Rose  <mrose@dbc.mtview.ca.us>, ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

Dave, Marshall,
	Given a previous exchange with Marshall on his proposed actions,
I'd like to be absolutely clear here on the intent of the message:

	Is this message your joint response to the Last Call?

	(If so, it and any subsequent discussion will be considered
                by the full IESG during its discussion of these documents)

	Is this message an appeal of one or more decisions?

               (If so, clarifications of exactly which decisions are 
being appealed
                and specifications of on which grounds will be needed.  This is
                necessary because one or more members of the IESG might have
                to recuse themselves from the discussion of an appeal of their
                own decisions.)

	Thanks for clarifying this point.
					Ted Hardie


At 4:37 PM -0700 6/26/03, Dave Crocker <dhc@dcrocker.net>, Marshall Rose wrote:
>Folks,
>
>This note cites substantive process and technical problems with the
>candidate specifications being submitted from the Instant Messaging and
>Presence (IMPP) working group. The group's charter specifies the scope
>to be to "define protocols and data formats necessary to build an
>Internet-scale end-user presence awareness, notification and instant
>messaging system".
>
>IMPP discussions began January, 1997 -- 5 1/2 years ago. It took one
>year to get chartered and another year to develop requirements, which
>were finally issued on February, 2000 (RFCs 2778-9). There have been no
>RFCs issued in the 3 1/2 years since then.
>
>Protocol development efforts were thwarted by the existence of several
>different technical constituencies and much effort, but no progress, at
>reconciling them. Two and a half years ago, the area directors
>acknowledged that a single, homogeneous protocol was not going to be
>developed, so they called for development of a "gatewaying"
>specification -- CPIM. They hoped to permit interconnection among the
>heterogeneous protocols being proposed, with the possibility of also
>interconnecting the various and popular services already in use.
>Unfortunately, this fundamental change in working group direction was
>never formally documented or approved through a charter revision.
>
>The issues discussed below have previously been raised in the working
>group, over the last year. The concerns raised were not resolved.
>
>The working group's output suffers from:
>
>      1.   PROCESS FAILURES
>      1.1. Lack of participation and constituency
>      1.2. Out of scope with charter
>      1.3. Failure to resolve issues raised in the working group
>
>      2.   TECHNICAL FAILURES
>      2.1. Confused and conflicting goals
>      2.2. Incomplete and unclear specifications.
>
>IMPP has a long and erratic history. It has incurred multiple changes in
>direction and multiple changes in its staff and oversight. The proffered
>work reflects this.
>
>
>Let's consider each of these points:
>
>
>
>1.   PROCESS FAILURES
>
>1.1. Lack of participation and constituency
>
>Who is the audience for this work and what is the basis for believing
>the work will be used?  The documents claim a goal of interoperability
>among heterogeneous IM and Presence services, but the normative content
>of the work precludes that goal.
>
>In fact the normative work is for an end-to-end, homogeneous service.
>Who will implement and use such work, and why?
>
>A strong indication that the work is not relevant to the Internet
>technical and operations community has been a dramatic drop-off in
>participation.
>
>The working group has been essentially inactive for the 6 months of
>2003, except for a post hoc exercise to write a "charter".
>
>During the 12 months before that, no more than 15 people made regular
>contributions (using roughly one posting per month as the threshold.)
>Only 10 of these participants posted 2 or more messages per month during
>that time.
>
>In reality, for the last 18 months, the real working group activity has
>been a dialogue among 4-5 people, with very few other participants.
>
>This does not bode well at all for industry interest in -- and use of --
>this work product.
>
>
>1.2. Out of scope with charter
>
>For the last 2.5 years, the working group has been operating without a
>meaningful charter. All of the work done during that time is out of
>scope with the text of the original charter.
>
>The lack of a concrete, updated charter has allowed the WG to behave in
>an arbitrary fashion with respect to its choice of technical goals and
>the soundness of the engineering decisions it has made. This explains,
>for example, why there is no rationale for honoring some IMPP
>requirements, but not others.
>    
>Recently, at the request of an Area Director, the co-chairs authored
>draft-day-atkins-impp-defacto-00 as a "de facto" charter. Several
>participants have objected to this contribution, but its authors have
>not responded to the issues raised.
>
>Although proposing a "de facto" charter is one way of appearing to
>legitimize the WG's behavior, the ADs would be well served by returning
>to first principles and asking themselves whether the WG has adhered to
>architectural and engineering principles that are sound, and whether
>there is a reasonable basis for believing that this work will get
>serious use on the Internet.
>
>Equally importantly, we either believe in the rules or we don't. The
>rules say that work-product has to conform to charter. The rules do not
>say "do some work, then write a charter to reflect the work-product".
>Even if the proffered work was a marvel of architectural soundness and
>engineering quality (which, as we'll discuss below, it clearly isn't),
>this "ex post facto" approach would raise the hackles of anyone who
>considers consistent IETF process to be a mandatory thing.
>
>
>1.3. Failure to resolve issues raised in the working group
>
>The issues listed in the Section 2 below (Technical Failures) were all
>raised carefully during the working group process. They remain
>unresolved and some received no response.
>
>The problem with the group's dichotomy between end-to-end vs. gateway
>goals was discussed repeatedly.  Only towards the end of the working
>group's effort did this appear to become resolved -- in the direction of
>an end-to-end content standard.  However, even then it was clear that the
>few remaining participants in the group continued to hold very different
>understandings of the goal.  Consequently, the confusion in the working
>group documents, on this point, is a regrettable, though accurate,
>rendition of the unresolved problem within the group.
>
>
>
>2.   TECHNICAL FAILURES
>
>2.1. Confused and conflicting goals
>
>The nature and the detail of these specifications are incomplete and
>often unclear. The work shows a split between the claimed goal of
>interconnecting heterogeneous IM and Presence services, versus the
>actual goal of specifying homogeneous, end-to-end IM and Presence
>services.
>
>The specifications call for features that go beyond what is required for
>a minimal functional core of interoperability. These added features
>serve to severely reduce the likelihood that the specifications will be
>used for interconnecting heterogeneous services.
>
>As noted in a curious discussion within the working group, recently, the
>IMPP Requirements documents were used arbitrarily for justifying some
>design decisions, but not others.  There is no basis for knowing why
>those requirements sometimes applied to the IM and Presence "gatewaying"
>work but at other times did not.
>    
>Consider this fragment from Section 3.3 (Format of Instant Messages) of
>draft-ietf-impp-im-03:
>
>      This specification defines an abstract interoperability mechanism for
>      instant messaging protocols; the message content definition given
>      here pertains to semantics rather than syntax.  However, some
>      important properties for interoperability can only be provided if a
>      common end-to-end format for instant messaging is employed by the
>      interoperating instant messaging protocols, especially with respect
>
>In other words, this specifies (and requires implementation of support
>for) an end-to-end syntax as well as semantics.
>
>It should be noted that the message format, defined by the working
>group, is new and will require a new suite of parsers, generators, and
>editors.  Although it purports to be a sub-set of RFC822, the format has
>notable requirements -- such as Unicode -- that are not in RFC822. While
>the desire to improve on existing practise is laudable, it defeats the
>goal of gatewaying heterogeneous systems.
>
>
>2.2. Incomplete and unclear specifications.
>
>(Lest there be any misunderstanding about this title of this
>sub-section, it is meant to cover the reasons that -- independent of
>process and goal debates -- the specifications "won't work".)
>
>Simply put, the specification suffer key omissions and ambiguities which
>make development of interoperable implementations highly unlikely.
>Consider this fragment Section 3.1 (Overview of Instant Messaging
>Service) of draft-ietf-impp-im-03:
>
>      its initial value is set by the originator.  The TransID is a unique
>      identifier used to correlate message operations to response
>
>"Unique" is not specified in any of the documents.  The obvious
>question is: unique with what scope?
>
>Ensuring uniqueness in transaction identifiers is a well-known
>challenge, with well-known resolutions -- notably from the transport
>arena. Yet the specification does not mention it.  This makes it likely
>that some implementations will create ambiguous TransIDs.
>
>    
>Alternatively, consider this fragment from Section 3.4.1 (The Message
>Operation) of draft-ietf-impp-im-03:
>
>      When an application wants to send an INSTANT MESSAGE, it invokes the
>      message operation.
>
>      When an instant messaging service receives the message operation, it
>      performs the following preliminary checks:
>
>Does this refer to the application/im-client interaction, the
>im-client/im-server interaction, or what?
>
>Or consider this other fragment from draft-ietf-impp-im-03:
>    
>      4.  Provided these checks are successful:
>
>      If the instant messaging service is able to successfully
>      deliver the message, a response operation having status
>      "success" is invoked.
>
>      If the service is unable to successfully deliver the message,
>      a response operation having status "failure" is invoked.
>
>      If the service must delegate responsibility for delivery (i.e.
>      if it is acting as a gateway or proxying the operation), and
>      if the delegation will not result in a future authoritative
>      indication to the service, a response operation having status
>
>This demonstrates a very serious effect from using the fuzzy term
>'service' rather than citing specific component-component interactions:
>It appears to mean that there is an end-to-end, real-time dependency
>chain for generating a response to a request. Each node along a relay
>path must withhold generating a response until the next node gives it
>the delivery -- i.e., the final -- status result.
>
>Note that this is fundamentally different from Email. In effect, it uses
>the equivalent to the Email SMTP Delivery Status Notification as the
>*sole* operations response mechanisms, with no intermediate (hop-by-hop)
>relaying report.
>
>    
>Similarly, consider Section 3.1 (3.1 Overview of the Presence Service)
>of draft-ietf-impp-pres-03:
>
>      The duration specifies the
>      maximum number of seconds that the SUBSCRIPTION should be active
>      (which may be zero, in which case this is a one-time request for
>      presence information).
>      ...
>      If the duration parameter is non-zero, then for up to the specified
>      duration, the service invokes the notify operation whenever there are
>      any changes to the PRESENTITY's presence information.
>
>How can "duration" have any useful meaning when there is no baseline
>reference for the starting point or ending point of the duration and
>when Internet exchange latencies are completely unpredictable? In other
>words, when a participant receives a duration value from another
>participant, what does it mean? Duration relative to what point of time?
>We do not know how many seconds it took for the service data to reach
>the receiving participant.
>
>But wait! Here are three more examples:
>    
>This fragment is from Section 3 (Address Resolution) of
>draft-ietf-impp-srv-03:
>
>      A client determines the address of an appropriate system running a
>      server, on behalf of the system referenced by the domain, by
>      resolving the destination domain name that is part of the identifier
>      to either an intermediate relay system or a final target system.
>
>This is the first, normative section in the document.  Yet it does not
>define 'address' nor refer to URI or URLs. There is no sense of what
>"appropriate' means, nor what "system referenced by the domain" means.
>
>Use of the term "identifier" suggests at least some confusion with the
>otherwise-used term "address".
>
>Or consider this fragment from Section 5 (Processing SRV RRs), ibid:
>    
>      ...
>      The choice of IM transfer protocol is a local configuration option
>      for each system.
>
>Besides not indicating *whose* choice is being cited, this text leaves
>quite a bit unspecified.  The change that was previously suggested was
>intended to make the roles and actions of participating parties
>explicitly clear:
>
>"Receiving systems that are registered for this DNS-based SRV resolution
>service list the transfer protocols by which they can be reached, either
>directly or through a translating gateway. The transfer-time choice of
>the IM transfer protocol to be used (and, therefore, to be resolved) is
>a local configuration option for each sending system."
>    
>Or consider this fine gem from from Section 5 (Processing SRV RRs), ibid:   
>    
>      Using this mechanism, seamless routing of IM traffic is possible,
>      regardless of whether a gateway is necessary for interoperation.  To
>      achieve this transparency, a separate RR for a gateway must be
>      present for each transfer protocol and domain pair that it serves.
>
>"domain <<pair>> that it serves"?
>
>I suspect that this should be "transfer protocol and target domain that
>it serves".
>    
>Let's face it: the proffered work has no realistic chance of meaningful
>interoperable implementation.
>
>
>
>CONCLUSIONS:
>    
>The proffered specifications represent many person-hours of
>well-intentioned effort. However the documents suffer fatally from
>delay, lack of focus, and lack of a clear charter. In their current
>form, they represent a fundamental violation of IETF process; they have
>no obvious user community to embrace them; and they would not work if
>there were one.
>
>
>/Dave
>/Marshall
>
>-----
>Dave Crocker <dcrocker@brandenburg.com> (Brandenburg InternetWorking)
>Marshall Rose  <mrose@dbc.mtview.ca.us> (Dover Beach Consulting)




From owner-ietf@ietf.org  Thu Jun 26 20:27:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28593
	for <ietf-web-archive@odin.ietf.org>; Thu, 26 Jun 2003 20:27:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Vh0N-0002GX-AF
	for ietf-list@asgard.ietf.org; Thu, 26 Jun 2003 20:22:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VgxU-0001gm-1E
	for ietf@asgard.ietf.org; Thu, 26 Jun 2003 20:19:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28512
	for <ietf@ietf.org>; Thu, 26 Jun 2003 20:19:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VgxS-0007QD-00
	for ietf@ietf.org; Thu, 26 Jun 2003 20:19:18 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VgxH-0007QA-00
	for ietf@ietf.org; Thu, 26 Jun 2003 20:19:07 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h5R0J22i013987
	for ietf@ietf.org env-from <vjs>;
	Thu, 26 Jun 2003 18:19:02 -0600 (MDT)
Date: Thu, 26 Jun 2003 18:19:02 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306270019.h5R0J22i013987@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Last Call: A Model for Presence and Instant Messaging to Proposed Standard
References:  <p0600120abb21385f5f07@[129.46.227.161]>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: hardie@qualcomm.com
> To: Dave Crocker <dcrocker@brandenburg.com>, iesg@ietf.org

> ...
> I'd like to be absolutely clear here on the intent of the message:
> ...

I took it as two things:

  - a test or slap in the face of many naive, broken by design
     spam filters that don't know that senders can be lists

  - a call for the IETF to fix a general problem of which this is merely
     a complete story of an example.  Isn't this story about the
     same as the controversy about tunnel, except that this story has
     is more complete?

It sounds to me as if they are saying that the WG should have been
shut down years ago.  Or too paraphrase Dirty Harry, "A standards
committee has got to know its limitations."


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Thu Jun 26 20:27:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28609
	for <ietf-web-archive@odin.ietf.org>; Thu, 26 Jun 2003 20:27:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Vh0N-0002Gi-Lf
	for ietf-list@asgard.ietf.org; Thu, 26 Jun 2003 20:22:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Vgyi-0001h2-5E
	for ietf@asgard.ietf.org; Thu, 26 Jun 2003 20:20:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28522;
	Thu, 26 Jun 2003 20:20:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vgyg-0007QP-00; Thu, 26 Jun 2003 20:20:34 -0400
Received: from [65.125.189.56] (helo=shego.dbc.mtview.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 19VgyV-0007QJ-00; Thu, 26 Jun 2003 20:20:23 -0400
Received: from shego.dbc.mtview.ca.us (localhost [127.0.0.1])
	by shego.dbc.mtview.ca.us (8.12.6/8.12.6) with SMTP id h5R0K6eU002555;
	Thu, 26 Jun 2003 17:20:06 -0700 (PDT)
Date: Thu, 26 Jun 2003 17:20:06 -0700
From: Marshall Rose <mrose@dbc.mtview.ca.us>
To: hardie@qualcomm.com
Cc: dcrocker@brandenburg.com, iesg@ietf.org, impp@iastate.edu,
        dhc@dcrocker.net, ietf@ietf.org
Subject: Re: Last Call: A Model for Presence and Instant Messaging to
 Proposed Standard
Message-Id: <20030626172006.4176ab2d.mrose@dbc.mtview.ca.us>
In-Reply-To: <p0600120abb21385f5f07@[129.46.227.161]>
References: <27241731952.20030626163750@brandenburg.com>
	<p0600120abb21385f5f07@[129.46.227.161]>
Organization: Dover Beach Consulting, Inc.
X-Mailer: Sylpheed version 0.8.8claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Given a previous exchange with Marshall on his proposed actions,
> I'd like to be absolutely clear here on the intent of the message:
> 
> 	Is this message your joint response to the Last Call?

yes.

    
> 	Is this message an appeal of one or more decisions?

no.
    
thanks!

/mtr



From owner-ietf@ietf.org  Fri Jun 27 01:57:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06267
	for <ietf-web-archive@odin.ietf.org>; Fri, 27 Jun 2003 01:57:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Vm5o-0003yu-U9
	for ietf-list@asgard.ietf.org; Fri, 27 Jun 2003 01:48:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Vm4x-0003h7-Cu
	for ietf@asgard.ietf.org; Fri, 27 Jun 2003 01:47:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06074
	for <ietf@ietf.org>; Fri, 27 Jun 2003 01:47:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vm4v-0001Vr-00
	for ietf@ietf.org; Fri, 27 Jun 2003 01:47:21 -0400
Received: from thing.verisignlabs.com ([65.201.175.62] helo=cliffie.verisignlabs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vm4k-0001Vj-00
	for ietf@ietf.org; Fri, 27 Jun 2003 01:47:10 -0400
Received: from thinkingcat.com (dialup-67.73.49.154.Dial1.LosAngeles1.Level3.net [::ffff:67.73.49.154])
  (AUTH: PLAIN leslie, TLS: TLSv1/SSLv3,128bits,RC4-MD5)
  by cliffie.verisignlabs.com with esmtp; Fri, 27 Jun 2003 01:46:33 -0400
Message-ID: <3EFBDA19.7090309@thinkingcat.com>
Date: Fri, 27 Jun 2003 01:46:01 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: IAB open architecture meeting in Vienna
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


FYI -- this is the description/agenda for the IAB
open architecture meeting, which the agenda shows
as scheduled for Monday, July 14, 15h30-17h30.

This is a different format of meeting we're trying 
out -- it's a working session, not a plenary event.

Since it does have cross-area implications, scheduling
was challenging, and yes,it does collide with other 
sessions it would have been better to avoid.  My
apologies for that, but know that when
we looked it over from all sides, we agreed with
the Secretariat that it was the least bad slot
we could find.

Leslie.

====8<==========8<=========8<=========



IAB Open Architecture Meeting, IETF57

We have specified an Internet that works, at the network layer,
using relatively stable but not permanent identifiers for connection
endpoints, which are allocated and administered using a topology dependent
model, implying a service provider dependent model.
But we run into problems (the architecture doesn't quite fit) when
we try to address some scenarios encountered in real life:

    . multihoming
    . assembling a local network without necessarily
      having to contact an ISP to obtain address space
      (e.g., home net)
    . renumbering local networks without significant pain

Some proposed solutions are challenged in terms of:

    . providing referential integrity - how is referential
      integrity maintained when identifiers are not globally 
      unique or are overloaded?

    . choosing between different identifiers for an object which
      has different "reachability" and the reachability is 
      context-dependent

    . security/transiting trust in layered address 
      resolution - how do we secure dynamic update of the 
      "reverse path" if the trust relationship between a 
      DHCP server and a DHCP client is very weak?

    . providing solutions that work across all layers of 
      the stack and all areas - how do we find a solution 
      that is great for routing but also great for security?


Specific cases where we have encountered these discussions:

    . the proposal of site-local addresses for IPv6
    . globally-unique but not globally routable addresses
    . IPv4 link-local addresses
    . local naming (LLMNR)
          . when used with global names (e.g. www.ietf.org)
        . when used with local names (e.g. laptop.local.arpa)


The IAB will hold an open meeting during IETF57 to collect input
from the IETF community at large to gain a better understanding
of where there are stresses and strains.  The purpose of the meeting 
will be to capture a list of the actual issues encountered, not to propose
solutions, nor to debate the merits of solutions that have been
proposed in the past.  The output of the meeting will be used
to update the IAB's list of "current known architectural issues",
and will ultimately help focus future IETF work on architectural
improvements for protocols that work across areas.

The planned meeting format is to have 60-90min of presentations
from people who haverequested a slot (and prepared at MOST 3 slides) 
in advance, followed by 30-45min of further contributions
from the room, and wrapup.

Agenda

    0. Intro, agenda bash [Chair, 1min]
    1. Set stage for discussion [Chair, 5min]
    2. Prepared input [Individual contributors; 5min presentation
       of problem; 2-3 min clarifying questions from the room]
    3. Input from the room
    4. Wrapup


Folks wishing to say a few words about the problems they
perceive needing addressing (i.e., agenda item #2) should
send a note to the IAB (iab@iab.org) before July 4.


-- 

-------------------------------------------------------------------
"Reality:
      Yours to discover."
                                 -- ThinkingCat 

Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------





From owner-ietf@ietf.org  Fri Jun 27 05:15:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20866
	for <ietf-web-archive@odin.ietf.org>; Fri, 27 Jun 2003 05:15:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Vp8V-0007bI-RX
	for ietf-list@asgard.ietf.org; Fri, 27 Jun 2003 05:03:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Vp7d-0007Ir-C7
	for ietf@asgard.ietf.org; Fri, 27 Jun 2003 05:02:21 -0400
Received: from bowl.fysh.org (mail@[195.167.170.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20756
	for <ietf@ietf.org>; Fri, 27 Jun 2003 05:02:18 -0400 (EDT)
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 19Vp6I-00089n-00
	for <ietf@ietf.org>; Fri, 27 Jun 2003 10:00:58 +0100
Date: Fri, 27 Jun 2003 10:00:58 +0100
To: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
Message-ID: <20030627090058.GC25509@fysh.org>
References: <20030626191147.9241F1390E@sa.vix.com> <20030626201839.GA6888@fysh.org> <g365msqw7i.fsf@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <g365msqw7i.fsf@sa.vix.com>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

Paul Vixie wrote:
>we're going to give the URL syntax a way to designate a server other than
>the one which is authoritatively responsible for the data, or a local caching
>resolver (also called a "recursive nameserver"), then we need to be able to
>set the RD bit.

What I understand you saying in the above is that when querying a
non-authoritative nameserver we need to have RD=1 in the query so
that we'll get an answer even if the nameserver doesn't have the answer
already cached.  This is true, but it is a detail of the query mechanism;
why does it need to be represented explicitly in the URI?  Or, to put it
another way, what about the current URI definition requires queries to
be made with RD=0?  I'm not sure I've correctly understood what you've
said, so these questions might not make much sense.

My understanding of the hostport part of the syntax is that it allows
one to specify which server's view of the domain name space one will
look at.  (Particularly with split DNS, this makes a difference.)
Where it's not specified, presumably the default will be one's configured
recursive resolver, which actually is not necessarily accessed by the DNS
protocol over UDP as is implied where the hostport part is specified.
(The draft says "Unless specified in the URI, the server ("hostport")
is assumed to be locally known".)  You seem to see the default as being
whatever nameserver is authoritative for the data addressed by the URI,
which suggests that you have a radically different idea of the semantics
of the hostport syntax.  How do you see it working?

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



From owner-ietf@ietf.org  Fri Jun 27 10:20:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29427
	for <ietf-web-archive@odin.ietf.org>; Fri, 27 Jun 2003 10:20:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VtyU-0000Z2-Sf
	for ietf-list@asgard.ietf.org; Fri, 27 Jun 2003 10:13:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19VtvU-0007G1-Rl
	for ietf@asgard.ietf.org; Fri, 27 Jun 2003 10:10:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28189;
	Fri, 27 Jun 2003 10:09:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VtvF-0002ql-00; Fri, 27 Jun 2003 10:09:53 -0400
Received: from mtiwmhc11.worldnet.att.net ([204.127.131.115])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vtv4-0002qf-00; Fri, 27 Jun 2003 10:09:42 -0400
Received: from tsg1 (84.sanjose-03-04rs16rt.ca.dial-access.att.net[12.81.1.84])
          by mtiwmhc11.worldnet.att.net (mtiwmhc11) with SMTP
          id <2003062714084811100rfq67e>; Fri, 27 Jun 2003 14:08:49 +0000
Message-ID: <018601c33cb5$988201f0$020aff0a@tsg1>
From: "todd glassey" <todd.glassey@worldnet.att.net>
To: "Jeff Williams" <jwkckid1@ix.netcom.com>,
        "Harald Tveit Alvestrand" <harald@Alvestrand.no>
Cc: "IETF" <ietf@ietf.org>, <iesg@ietf.org>, <poised@lists.tislabs.com>
References: <200301312106.h0VL6gt00339@rotala.raleigh.ibm.com> <166408723.1044181809@localhost> <3E3DFDA8.4F50DD55@ix.netcom.com>
Subject: Re: What review is required for "IETF Consensus"?
Date: Fri, 27 Jun 2003 06:46:37 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The real problem Jeff, is that there is no want of a true consensus here, or
a more formalized description of the vetting process or what is involved in
it. The cost in making the IETF what the descriptions of it paint it as,
would in fact break it financially with the current operations and funding
models. So what you are really asking for (*and reasonably so by the way) is
a total rethinking of the bigger-picture issue of what actually constitutes
vetting and the advancement of an initiative.

There is also this underlying concept that all members of a WG ***must***
participate in the vetting of each and every project or initiative that is
vetted within a WG's operations and this is also completely untrue except in
the rare case where a WG only has ONE initiative.

Todd


----- Original Message ----- 
From: "Jeff Williams" <jwkckid1@ix.netcom.com>
To: "Harald Tveit Alvestrand" <harald@Alvestrand.no>
Cc: "IETF" <ietf@ietf.org>; <iesg@ietf.org>; <poised@lists.tislabs.com>
Sent: Sunday, February 02, 2003 10:27 PM
Subject: Re: What review is required for "IETF Consensus"?


> Harald and all,
>
>   I "Guess" that a IETF consensus really means whatever you Harald
> says it means much like what consensus meant while you were
> Chair of the DNSO GA.  But to be honest, no consensus can be
> determined unless it is measured, which means a VOTE must be
> held amongst IETF participants.  Perish the thought, eh Harald?!  >;)
>
> Harald Tveit Alvestrand wrote:
>
> > Thread B from my previous message..... this is being CCed to the POISED
> > list, for reasons that may be obvious after reading the message; for
POISED
> > subscribers - this is followup to an IETF list thread.
> >
> > Question:
> >
> > What review process must the IESG take before taking the action to block
or
> > allow publication of such an internet-draft (ie "what does IETF
Consensus
> > mean")?
> >
> > This is not written in RFC 2434.
> > Some tactics that have been used in the past to gather information for
the
> > IESG's decision include:
> >
> > - "It's obviously OK". Approved WG document, or competently written
> > documentation from subject matter experts, reviewed by people with
> > competence on the specific registry. The IESG looks at it and thinks
that
> > it's obvioiusly right. Example: application/ogg, documented in
> > draft-walleij-ogg-mediatype.
> >
> > - Subject matter expert group review. For instance, posting to the DHC
WG
> > asking for opinions on a DHCP extension. WG chairs' feedback will carry
a
> > lot of weight.
> >
> > - IETF Last Call for Informational/Experimental, with the IESG
evaluating
> > the feedback.
> >
> > In all cases, the IESG has to evaluate; there's no other established
body
> > to do it. "The buck stops here".
> >
> > Among the cases to consider:
> >
> > - Everyone approves. Go for it.
> >
> > - Nobody cares. No comments; the IESG will usually decide that nobody
saw
> > any looming danger to the Internet, and allow the registration.
> >
> > - Serious objections. The comments clearly indicate that the
registration
> > would be harmful to the Internet (and how), and the IESG agrees with
that
> > evaluation. The IESG will refuse.
> >
> > - Incompetent or incomplete document. The IESG will usually object to
this
> > on its own - without documentation clear enough to determine whether
this
> > is OK or harmful, it would be remiss of the IESG to let the document go
> > forward even to an IETF Last Call.
> > We can't claim IETF consensus on something we can't understand.
> >
> > - Dissension within the IETF. Like in the case of a WG, the IESG has to
> > evaluate the arguments on their merits; obviously the proposers think
that
> > the registration should be allowed, and opposition without a rational
basis
> > should no more be allowed to block this registration than it should be
> > allowed to block WG progress. But as the saying goes - "this is why you
get
> > the big bucks".
> > Among the things to consider here is that the determination must be made
in
> > a timely fashion - sometimes there are reasons why letting debate rage
for
> > another 6 months doesn't seem like an attractive option.
> >
> > Questions for the audience:
> >
> > - should this description, or something like it, go into
> > draft-iesg-procedures?
> > - are there guidelines that the IESG should use when trying to determine
> > the right outcome in the "dissension" case?
> > - does this debate belong on the POISED list, together with the
discussion
> > of the IESG charter and the IESG procedures?
> >
> > Thoughts?
> >
> >                  Harald
>
> Regards,
> --
> Jeffrey A. Williams
> Spokesman for INEGroup LLA. - (Over 129k members/stakeholders strong!)
> ================================================================
> CEO/DIR. Internet Network Eng. SR. Eng. Network data security
> Information Network Eng. Group. INEG. INC.
> E-Mail jwkckid1@ix.netcom.com
> Contact Number: 214-244-4827 or 214-244-3801
>
>




From owner-ietf@ietf.org  Fri Jun 27 13:05:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07587
	for <ietf-web-archive@odin.ietf.org>; Fri, 27 Jun 2003 13:05:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19VwZ6-0000Yi-8r
	for ietf-list@asgard.ietf.org; Fri, 27 Jun 2003 12:59:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Vd5U-0000gM-GY
	for ietf@asgard.ietf.org; Thu, 26 Jun 2003 16:11:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19472;
	Thu, 26 Jun 2003 16:11:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vd5E-0005XZ-00; Thu, 26 Jun 2003 16:11:04 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Vd52-0005XI-00; Thu, 26 Jun 2003 16:10:52 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h5QKDIF29873;
	Thu, 26 Jun 2003 13:13:18 -0700
Date: Thu, 26 Jun 2003 13:09:53 -0700
From: Dave Crocker <dcrocker@brandenburg.com>,
        Marshall Rose  <mrose@dbc.mtview.ca.us>
X-Mailer: The Bat! (v1.63 Beta/11) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <135229254410.20030626130953@brandenburg.com>
To: iesg@ietf.org
CC: impp@iastate.edu, ietf <IETF@ietf.org>
Subject: Re: Last Call: A Model for Presence and Instant Messaging to Proposed Standard
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Folks,

This note cites substantive process and technical problems with the
candidate specifications being submitted from the Instant Messaging and
Presence (IMPP) working group. The group's charter specifies the scope
to be to "define protocols and data formats necessary to build an
Internet-scale end-user presence awareness, notification and instant
messaging system".

IMPP discussions began January, 1997 -- 5 1/2 years ago. It took one
year to get chartered and another year to develop requirements, which
were finally issued on February, 2000 (RFCs 2778-9). There have been no
RFCs issued in the 3 1/2 years since then.

Protocol development efforts were thwarted by the existence of several
different technical constituencies and much effort, but no progress, at
reconciling them. Two and a half years ago, the area directors
acknowledged that a single, homogeneous protocol was not going to be
developed, so they called for development of a "gatewaying"
specification -- CPIM. They hoped to permit interconnection among the
heterogeneous protocols being proposed, with the possibility of also
interconnecting the various and popular services already in use.
Unfortunately, this fundamental change in working group direction was
never formally documented or approved through a charter revision.

The issues discussed below have previously been raised in the working
group, over the last year. The concerns raised were not resolved.

The working group's output suffers from:

     1.   PROCESS FAILURES
     1.1. Lack of participation and constituency
     1.2. Out of scope with charter
     1.3. Failure to resolve issues raised in the working group

     2.   TECHNICAL FAILURES
     2.1. Confused and conflicting goals
     2.2. Incomplete and unclear specifications.

IMPP has a long and erratic history. It has incurred multiple changes in
direction and multiple changes in its staff and oversight. The proffered
work reflects this.


Let's consider each of these points:



1.   PROCESS FAILURES

1.1. Lack of participation and constituency

Who is the audience for this work and what is the basis for believing
the work will be used?  The documents claim a goal of interoperability
among heterogeneous IM and Presence services, but the normative content
of the work precludes that goal.

In fact the normative work is for an end-to-end, homogeneous service.
Who will implement and use such work, and why?

A strong indication that the work is not relevant to the Internet
technical and operations community has been a dramatic drop-off in
participation.

The working group has been essentially inactive for the 6 months of
2003, except for a post hoc exercise to write a "charter".

During the 12 months before that, no more than 15 people made regular
contributions (using roughly one posting per month as the threshold.)
Only 10 of these participants posted 2 or more messages per month during
that time.

In reality, for the last 18 months, the real working group activity has
been a dialogue among 4-5 people, with very few other participants.

This does not bode well at all for industry interest in -- and use of --
this work product.


1.2. Out of scope with charter

For the last 2.5 years, the working group has been operating without a
meaningful charter. All of the work done during that time is out of
scope with the text of the original charter.

The lack of a concrete, updated charter has allowed the WG to behave in
an arbitrary fashion with respect to its choice of technical goals and
the soundness of the engineering decisions it has made. This explains,
for example, why there is no rationale for honoring some IMPP
requirements, but not others.
    
Recently, at the request of an Area Director, the co-chairs authored
draft-day-atkins-impp-defacto-00 as a "de facto" charter. Several
participants have objected to this contribution, but its authors have
not responded to the issues raised.

Although proposing a "de facto" charter is one way of appearing to
legitimize the WG's behavior, the ADs would be well served by returning
to first principles and asking themselves whether the WG has adhered to
architectural and engineering principles that are sound, and whether
there is a reasonable basis for believing that this work will get
serious use on the Internet.

Equally importantly, we either believe in the rules or we don't. The
rules say that work-product has to conform to charter. The rules do not
say "do some work, then write a charter to reflect the work-product".
Even if the proffered work was a marvel of architectural soundness and
engineering quality (which, as we'll discuss below, it clearly isn't),
this "ex post facto" approach would raise the hackles of anyone who
considers consistent IETF process to be a mandatory thing.


1.3. Failure to resolve issues raised in the working group

The issues listed in the Section 2 below (Technical Failures) were all
raised carefully during the working group process. They remain
unresolved and some received no response.

The problem with the group's dichotomy between end-to-end vs. gateway
goals was discussed repeatedly.  Only towards the end of the working
group's effort did this appear to become resolved -- in the direction of
an end-to-end content standard.  However, even then it was clear that the
few remaining participants in the group continued to hold very different
understandings of the goal.  Consequently, the confusion in the working
group documents, on this point, is a regrettable, though accurate,
rendition of the unresolved problem within the group.



2.   TECHNICAL FAILURES

2.1. Confused and conflicting goals

The nature and the detail of these specifications are incomplete and
often unclear. The work shows a split between the claimed goal of
interconnecting heterogeneous IM and Presence services, versus the
actual goal of specifying homogeneous, end-to-end IM and Presence
services.

The specifications call for features that go beyond what is required for
a minimal functional core of interoperability. These added features
serve to severely reduce the likelihood that the specifications will be
used for interconnecting heterogeneous services.

As noted in a curious discussion within the working group, recently, the
IMPP Requirements documents were used arbitrarily for justifying some
design decisions, but not others.  There is no basis for knowing why
those requirements sometimes applied to the IM and Presence "gatewaying"
work but at other times did not.
    
Consider this fragment from Section 3.3 (Format of Instant Messages) of
draft-ietf-impp-im-03:

     This specification defines an abstract interoperability mechanism for
     instant messaging protocols; the message content definition given
     here pertains to semantics rather than syntax.  However, some
     important properties for interoperability can only be provided if a
     common end-to-end format for instant messaging is employed by the
     interoperating instant messaging protocols, especially with respect

In other words, this specifies (and requires implementation of support
for) an end-to-end syntax as well as semantics.

It should be noted that the message format, defined by the working
group, is new and will require a new suite of parsers, generators, and
editors.  Although it purports to be a sub-set of RFC822, the format has
notable requirements -- such as Unicode -- that are not in RFC822. While
the desire to improve on existing practise is laudable, it defeats the
goal of gatewaying heterogeneous systems.


2.2. Incomplete and unclear specifications.

(Lest there be any misunderstanding about this title of this
sub-section, it is meant to cover the reasons that -- independent of
process and goal debates -- the specifications "won't work".)

Simply put, the specification suffer key omissions and ambiguities which
make development of interoperable implementations highly unlikely.
Consider this fragment Section 3.1 (Overview of Instant Messaging
Service) of draft-ietf-impp-im-03:

     its initial value is set by the originator.  The TransID is a unique
     identifier used to correlate message operations to response

"Unique" is not specified in any of the documents.  The obvious
question is: unique with what scope?

Ensuring uniqueness in transaction identifiers is a well-known
challenge, with well-known resolutions -- notably from the transport
arena. Yet the specification does not mention it.  This makes it likely
that some implementations will create ambiguous TransIDs.

    
Alternatively, consider this fragment from Section 3.4.1 (The Message
Operation) of draft-ietf-impp-im-03:

     When an application wants to send an INSTANT MESSAGE, it invokes the
     message operation.

     When an instant messaging service receives the message operation, it
     performs the following preliminary checks:

Does this refer to the application/im-client interaction, the
im-client/im-server interaction, or what?

Or consider this other fragment from draft-ietf-impp-im-03:
    
     4.  Provided these checks are successful:

     If the instant messaging service is able to successfully
     deliver the message, a response operation having status
     "success" is invoked.

     If the service is unable to successfully deliver the message,
     a response operation having status "failure" is invoked.

     If the service must delegate responsibility for delivery (i.e.
     if it is acting as a gateway or proxying the operation), and
     if the delegation will not result in a future authoritative
     indication to the service, a response operation having status

This demonstrates a very serious effect from using the fuzzy term
'service' rather than citing specific component-component interactions:
It appears to mean that there is an end-to-end, real-time dependency
chain for generating a response to a request. Each node along a relay
path must withhold generating a response until the next node gives it
the delivery -- i.e., the final -- status result.

Note that this is fundamentally different from Email. In effect, it uses
the equivalent to the Email SMTP Delivery Status Notification as the
*sole* operations response mechanisms, with no intermediate (hop-by-hop)
relaying report.

    
Similarly, consider Section 3.1 (3.1 Overview of the Presence Service)
of draft-ietf-impp-pres-03:

     The duration specifies the
     maximum number of seconds that the SUBSCRIPTION should be active
     (which may be zero, in which case this is a one-time request for
     presence information).
     ...
     If the duration parameter is non-zero, then for up to the specified
     duration, the service invokes the notify operation whenever there are
     any changes to the PRESENTITY's presence information.

How can "duration" have any useful meaning when there is no baseline
reference for the starting point or ending point of the duration and
when Internet exchange latencies are completely unpredictable? In other
words, when a participant receives a duration value from another
participant, what does it mean? Duration relative to what point of time?
We do not know how many seconds it took for the service data to reach
the receiving participant.

But wait! Here are three more examples:
    
This fragment is from Section 3 (Address Resolution) of
draft-ietf-impp-srv-03:

     A client determines the address of an appropriate system running a
     server, on behalf of the system referenced by the domain, by
     resolving the destination domain name that is part of the identifier
     to either an intermediate relay system or a final target system.

This is the first, normative section in the document.  Yet it does not
define 'address' nor refer to URI or URLs. There is no sense of what
"appropriate' means, nor what "system referenced by the domain" means.

Use of the term "identifier" suggests at least some confusion with the
otherwise-used term "address".

Or consider this fragment from Section 5 (Processing SRV RRs), ibid:
    
     ...
     The choice of IM transfer protocol is a local configuration option
     for each system.

Besides not indicating *whose* choice is being cited, this text leaves
quite a bit unspecified.  The change that was previously suggested was
intended to make the roles and actions of participating parties
explicitly clear:

"Receiving systems that are registered for this DNS-based SRV resolution
service list the transfer protocols by which they can be reached, either
directly or through a translating gateway. The transfer-time choice of
the IM transfer protocol to be used (and, therefore, to be resolved) is
a local configuration option for each sending system."
    
Or consider this fine gem from from Section 5 (Processing SRV RRs), ibid:    
    
     Using this mechanism, seamless routing of IM traffic is possible,
     regardless of whether a gateway is necessary for interoperation.  To
     achieve this transparency, a separate RR for a gateway must be
     present for each transfer protocol and domain pair that it serves.

"domain <<pair>> that it serves"?

I suspect that this should be "transfer protocol and target domain that
it serves".
    
Let's face it: the proffered work has no realistic chance of meaningful
interoperable implementation.



CONCLUSIONS:
    
The proffered specifications represent many person-hours of
well-intentioned effort. However the documents suffer fatally from
delay, lack of focus, and lack of a clear charter. In their current
form, they represent a fundamental violation of IETF process; they have
no obvious user community to embrace them; and they would not work if
there were one.


/Dave
/Marshall

-----
Dave Crocker <dcrocker@brandenburg.com> (Brandenburg InternetWorking)
Marshall Rose  <mrose@dbc.mtview.ca.us> (Dover Beach Consulting)






From owner-ietf@ietf.org  Fri Jun 27 18:58:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24971
	for <ietf-web-archive@odin.ietf.org>; Fri, 27 Jun 2003 18:58:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19W1q9-0003ct-2I
	for ietf-list@asgard.ietf.org; Fri, 27 Jun 2003 18:37:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19W1pC-0003Up-Hp
	for ietf@asgard.ietf.org; Fri, 27 Jun 2003 18:36:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24162
	for <ietf@ietf.org>; Fri, 27 Jun 2003 18:35:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W1oh-0006tK-00
	for ietf@ietf.org; Fri, 27 Jun 2003 18:35:39 -0400
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19W1oV-0006r6-00
	for ietf@ietf.org; Fri, 27 Jun 2003 18:35:28 -0400
Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.12.9/8.12.9) with ESMTP id h5RMV54V001464
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK);
	Sat, 28 Jun 2003 00:31:06 +0200
To: Paul Vixie <paul@vix.com>
Cc: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
References: <20030626191147.9241F1390E@sa.vix.com>
From: Simon Josefsson <jas@extundo.com>
X-Payment: hashcash 1.2 0:030627:paul@vix.com:d61a2313a52c89f8
X-Hashcash: 0:030627:paul@vix.com:d61a2313a52c89f8
X-Payment: hashcash 1.2 0:030627:ietf@ietf.org:1b43101809d523ca
X-Hashcash: 0:030627:ietf@ietf.org:1b43101809d523ca
Date: Sat, 28 Jun 2003 00:31:05 +0200
In-Reply-To: <20030626191147.9241F1390E@sa.vix.com> (Paul Vixie's message of
 "Thu, 26 Jun 2003 19:11:47 +0000")
Message-ID: <ilur85fkv9y.fsf@latte.josefsson.org>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=-32.4 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT_GNUS_UA
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-ietf@ietf.org
Precedence: bulk

Paul,

Thank you for the comments.  Answers inline below.

Paul Vixie <paul@vix.com> writes:

>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action.  Please send any comments to the 
>> iesg@ietf.org or ietf@ietf.org mailing lists by 2003-7-22.
>
> i have one comment on document quality (DQ) and one protocol quality (PQ).
>
> DQ: the url scheme syntax allows a given dnsqueryelement to be validly
> specified more than once, but does not explain whether the first or last
> instance of a duplicate dnsqueryelement will be the one in effect.  this
> ambiguity could be resolved by changing the syntax so that duplicates
> are invalid, or by stating that the first or last dnsqueryelement
> instance "wins".

I have fixed this, by letting the first element win.

   dnsquery        = dnsqueryelement [";" dnsquery]
                                ; First matching element MUST be used.
                                ; E.g., dns:host.example.org?TYPE=A;TYPE=TXT
                                ; means type A.

Making such URIs invalid seems to be asking for implementation
problems, but I don't have a strong opinion about it.  Please suggest
text if this is unsatisfactory.

> PQ: the url scheme does not allow the RD bit to be set.  of all the DNS
> and EDNS flags and options which might affect the results of the query,
> only RD can really be thought to be "missing" from this specification,
> and only in the case where the "hostport" is given.  however, it may be
> wise to permit the specification of other flags, and EDNS OPT options, so
> that if a future flag or option block is added which affects the results
> of a query in the way RD can do, the URI syntax for it will already be known.

I don't believe this belong in a URI specification.  There are many
things which the URI do not allow to be expressed, but which do affect
the answer that is eventually returned.  E.g., originator address of
the DNS query, use of IPSEC or no IPSEC, whether your network cable is
plugged in or not.

Furthermore, DNS URIs do not require the use of the DNS protocol at
all, it just denote a DNS resource.  DNS URIs can be resolved via HTTP
or something else.  Having the RD bit present is a hint to the DNS
protocol; the RD bit has no connection with the DNS resource that the
URI denote.

Leaving the protocol logic up to the implementation using URIs makes
for greater flexibility.  A generic implementation, e.g. within a web
browser, might always set the RD bit.  Streamlined implementations
could set the RD bit when the default server is used (i.e., no
"hostport"), but clear the RD bit when a specific server is given in
"hostport".  Special applications, that only use the URI to trigger
certain requests, could always clear the RD bit.

Other applications, that do not use the DNS protocol at all, could use
DNS URIs when displaying DNS zone files for a DNS administrator, and
need not worry about DNS-protocol specific parts of the URI.  For this
application, the "hostport" string is simply used to find the server
view to look for the RR in.

Thanks again,
Simon




From owner-ietf@ietf.org  Fri Jun 27 19:47:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24973
	for <ietf-web-archive@odin.ietf.org>; Fri, 27 Jun 2003 18:58:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19W1t3-0003ti-1x
	for ietf-list@asgard.ietf.org; Fri, 27 Jun 2003 18:40:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19W1sA-0003o4-Cg
	for ietf@asgard.ietf.org; Fri, 27 Jun 2003 18:39:14 -0400
Received: from yxa.extundo.com (178.230.13.217.in-addr.dgcsystems.net [217.13.230.178])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24288
	for <ietf@ietf.org>; Fri, 27 Jun 2003 18:38:40 -0400 (EDT)
Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.12.9/8.12.9) with ESMTP id h5RMb74V001569
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK);
	Sat, 28 Jun 2003 00:37:07 +0200
To: Zefram <zefram@fysh.org>
Cc: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
References: <20030626191147.9241F1390E@sa.vix.com>
	<20030626201839.GA6888@fysh.org>
From: Simon Josefsson <jas@extundo.com>
X-Payment: hashcash 1.2 0:030627:zefram@fysh.org:1c61ba8958131f98
X-Hashcash: 0:030627:zefram@fysh.org:1c61ba8958131f98
X-Payment: hashcash 1.2 0:030627:ietf@ietf.org:dbbe46137e7c0833
X-Hashcash: 0:030627:ietf@ietf.org:dbbe46137e7c0833
Date: Sat, 28 Jun 2003 00:37:07 +0200
In-Reply-To: <20030626201839.GA6888@fysh.org> (zefram@fysh.org's message of
 "Thu, 26 Jun 2003 21:18:39 +0100")
Message-ID: <iluk7b7kuzw.fsf@latte.josefsson.org>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=-32.4 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT_GNUS_UA
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-ietf@ietf.org
Precedence: bulk

Andrew, I have incorporated your first suggestion, and for the second
one added some text to clarify that it was actually intended to allow
for zero length dnsname's (to denote the DNS root).  Let me know if
you believe further modifications would improve the document.  As for
the RD issue, I guess we agree.

   dnsname         = *pchar
                                ; See RFC 2396 for "pchar" definition
                                ; NB! Can be empty.

   dnsqueryelement = ( "CLASS=" dnsclassval ) / ( "TYPE=" dnstypeval ) /
                     ( 1*alphanum "=" 1*alphanum )

Thanks,
Simon

Zefram <zefram@fysh.org> writes:

> Paul Vixie wrote:
>>PQ: the url scheme does not allow the RD bit to be set.
>
> The draft says "A DNS URI designates a DNS resource record set ... by
> domain name, type, class and server.".  That is, it identifies a location
> within the abstract domain name space, a location which may contain
> an RRset.  The setting of the RD bit doesn't affect which RRset is
> designated; all it can affect is whether a query succeeds in returning
> the requested RRset.  Nothing in the DNS URI so far refers to a specific
> query mechanism, and indeed I can see reasonable uses for the URI form
> that don't involve making any queries, via the DNS protocol or otherwise.
>
> In summary, adding control of the RD bit would turn the DNS URI into
> something else, something that I don't think it should be.
>
> I see a couple of editorial nits, quite separate from the above:
>
> 0. The ABNF for <dnsqueryelement> uses "|" instead of "/" characters to
> separate branches.
>
> 1. The grammar allows <dnsname> to be zero-length.
>
> -zefram
> -- 
> Andrew Main (Zefram) <zefram@fyssh.org>




From owner-ietf@ietf.org  Fri Jun 27 20:05:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27183
	for <ietf-web-archive@odin.ietf.org>; Fri, 27 Jun 2003 20:05:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19W35Y-0003fZ-S9
	for ietf-list@asgard.ietf.org; Fri, 27 Jun 2003 19:57:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19W34a-0003a7-Py
	for ietf@asgard.ietf.org; Fri, 27 Jun 2003 19:56:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26903
	for <ietf@ietf.org>; Fri, 27 Jun 2003 19:56:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W34Z-0007YL-00
	for ietf@ietf.org; Fri, 27 Jun 2003 19:56:07 -0400
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19W34O-0007YB-00
	for ietf@ietf.org; Fri, 27 Jun 2003 19:55:56 -0400
Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.12.9/8.12.9) with ESMTP id h5RNtS4V002829
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK);
	Sat, 28 Jun 2003 01:55:28 +0200
To: Paul Vixie <vixie@fh.vix.com>
Cc: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
References: <20030627225905.38F7F23000C@fh.vix.com>
From: Simon Josefsson <jas@extundo.com>
X-Payment: hashcash 1.2 0:030627:vixie@fh.vix.com:33fcfa14f5bad42f
X-Hashcash: 0:030627:vixie@fh.vix.com:33fcfa14f5bad42f
X-Payment: hashcash 1.2 0:030627:ietf@ietf.org:0dd06e74eebd7bde
X-Hashcash: 0:030627:ietf@ietf.org:0dd06e74eebd7bde
Date: Sat, 28 Jun 2003 01:55:28 +0200
In-Reply-To: <20030627225905.38F7F23000C@fh.vix.com> (Paul Vixie's message
 of "Fri, 27 Jun 2003 22:59:05 +0000")
Message-ID: <iluel1fkrdb.fsf@latte.josefsson.org>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=-32.4 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT_GNUS_UA
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-ietf@ietf.org
Precedence: bulk

Paul Vixie <vixie@fh.vix.com> writes:

>> ...
>> Furthermore, DNS URIs do not require the use of the DNS protocol at
>> all, it just denote a DNS resource.  DNS URIs can be resolved via HTTP
>> or something else.  Having the RD bit present is a hint to the DNS
>> protocol; the RD bit has no connection with the DNS resource that the
>> URI denote.
>> ...
>
> very well.  then i request that you remove the "hostport" from the syntax.

The rationale being?

The hostport describes the authority that know the intended DNS
resource.  An authority is useful even for abstract, non-DNS-protocol,
DNS resources.  DNS resources themselves are indexed by (NAME, CLASS,
TYPE), but to distinguish between the answer that entity A
knows/generate, and the answer that entity B knows/generate, an
authority scope like "hostport" is needed.

Most applications probably will not care, and use the "default"
authority, trusting the local server to do the right thing.  But for
internal DNS environments, specifying the authority could be required.

I agree it is less confusing if the word "hostport" was avoided, and
the word "authority" is used instead.  Also, using the word
"authority" instead of "server" elsewhere would also improve matters.
I have made this change for the next revision, a snapshot is available
from <http://josefsson.org/draft-josefsson-dns-url.txt>.

Thanks,
Simon




From owner-ietf@ietf.org  Fri Jun 27 20:51:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28363
	for <ietf-web-archive@odin.ietf.org>; Fri, 27 Jun 2003 20:51:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19W3su-0001qg-Q9
	for ietf-list@asgard.ietf.org; Fri, 27 Jun 2003 20:48:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19W3sb-0001iF-SM
	for ietf@asgard.ietf.org; Fri, 27 Jun 2003 20:47:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28139
	for <ietf@ietf.org>; Fri, 27 Jun 2003 20:46:43 -0400 (EDT)
From: hardie@qualcomm.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W3rX-00002l-00
	for ietf@ietf.org; Fri, 27 Jun 2003 20:46:43 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W3rM-00002g-00
	for ietf@ietf.org; Fri, 27 Jun 2003 20:46:32 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.12.9/8.12.5/1.0) with ESMTP id h5S0jvZf025738;
	Fri, 27 Jun 2003 17:45:57 -0700 (PDT)
Received: from [129.46.227.161] (carbuncle.qualcomm.com [129.46.227.161])
	by sabrina.qualcomm.com (8.12.9/8.12.5/1.0) with ESMTP id h5S0jtBC005577;
	Fri, 27 Jun 2003 17:45:55 -0700 (PDT)
Mime-Version: 1.0
X-Sender: hardie@mage.qualcomm.com
Message-Id: <p06001205bb22942a43f7@[129.46.227.161]>
In-Reply-To: <ilur85fkv9y.fsf@latte.josefsson.org>
References: <20030626191147.9241F1390E@sa.vix.com>
 <ilur85fkv9y.fsf@latte.josefsson.org>
Date: Fri, 27 Jun 2003 17:45:53 -0700
To: Simon Josefsson <jas@extundo.com>, Paul Vixie <paul@vix.com>
Subject: Re: concerning draft-josefsson-dns-url-08.txt
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

Simon writes:
>
>Furthermore, DNS URIs do not require the use of the DNS protocol at
>all, it just denote a DNS resource.  DNS URIs can be resolved via HTTP
>or something else.

This is a can of worms at the bottom of a very steep rat-hole.  If you
would like to spend the time from now to Vienna (no sleeping, no breaks
for food!) reading email archives of folks bitterly arguing the finer points of
when a URI is a URL and when it is not, let me know and I'll send you
the pointers.  But let's not go back over that tired ground here.

 From my perspective, the *value* of this proposed URI scheme relates
to how well it can be used to point to things stored in the DNS.   Let's
focus on that, as the other uses are likely to be of marginal utility
compared to that.
			regards,
				Ted Hardie



From owner-ietf@ietf.org  Sat Jun 28 10:01:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22588
	for <ietf-web-archive@odin.ietf.org>; Sat, 28 Jun 2003 10:00:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19WG5f-0005on-18
	for ietf-list@asgard.ietf.org; Sat, 28 Jun 2003 09:50:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19WG5T-0005m1-UH
	for ietf@asgard.ietf.org; Sat, 28 Jun 2003 09:49:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22522
	for <ietf@ietf.org>; Sat, 28 Jun 2003 09:49:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WG5E-0003Gw-00
	for ietf@ietf.org; Sat, 28 Jun 2003 09:49:40 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WG4y-0003Gt-00
	for ietf@ietf.org; Sat, 28 Jun 2003 09:49:24 -0400
Received: (from falk@localhost)
	by nit.isi.edu (8.11.6/8.11.6) id h5SDmwH06313
	for ietf@ietf.org; Sat, 28 Jun 2003 06:48:58 -0700
Date: Sat, 28 Jun 2003 06:48:58 -0700
From: Aaron Falk <falk@isi.edu>
To: ietf@ietf.org
Subject: what's a PWG?
Message-ID: <20030628134858.GD5145@isi.edu>
Mail-Followup-To: ietf@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

Appears twice in http://www.ietf.org/meetings/agenda_57.html (pmtud &
lemonade).

--aaron



From owner-ietf@ietf.org  Sat Jun 28 18:52:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05754
	for <ietf-web-archive@odin.ietf.org>; Sat, 28 Jun 2003 18:52:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19WONU-0006tg-Gh
	for ietf-list@asgard.ietf.org; Sat, 28 Jun 2003 18:41:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19WON8-0006rh-Kv
	for ietf@asgard.ietf.org; Sat, 28 Jun 2003 18:40:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05536
	for <ietf@ietf.org>; Sat, 28 Jun 2003 18:40:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WOMk-00060i-00
	for ietf@ietf.org; Sat, 28 Jun 2003 18:40:18 -0400
Received: from sccrmhc11.attbi.com ([204.127.202.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WOMP-00060N-00
	for ietf@ietf.org; Sat, 28 Jun 2003 18:39:57 -0400
Received: from mobilebill (12-225-210-60.client.attbi.com[12.225.210.60](untrusted sender))
          by attbi.com (sccrmhc11) with SMTP
          id <2003062822385201100nul42e>; Sat, 28 Jun 2003 22:38:52 +0000
From: "bill" <bill@strahm.net>
To: "'Aaron Falk'" <falk@isi.edu>, <ietf@ietf.org>
Subject: RE: what's a PWG?
Date: Sat, 28 Jun 2003 15:38:36 -0700
Message-ID: <002901c33dc6$091a66d0$6501a8c0@mobilebill>
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.2627
In-Reply-To: <20030628134858.GD5145@isi.edu>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I'd  vote for "Proposed Working Group" (BOF ???)

I know that pmtud is a BOF, and lemonade is new (don't know its status)

Bill

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of
Aaron Falk
Sent: Saturday, June 28, 2003 6:49 AM
To: ietf@ietf.org
Subject: what's a PWG?


Appears twice in http://www.ietf.org/meetings/agenda_57.html (pmtud &
lemonade).

--aaron






From owner-ietf@ietf.org  Sun Jun 29 02:13:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22431
	for <ietf-web-archive@odin.ietf.org>; Sun, 29 Jun 2003 02:13:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19WVBN-0004Th-BF
	for ietf-list@asgard.ietf.org; Sun, 29 Jun 2003 01:57:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19WVAc-0004Rf-7R
	for ietf@asgard.ietf.org; Sun, 29 Jun 2003 01:56:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10748
	for <ietf@ietf.org>; Sun, 29 Jun 2003 01:55:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WVAC-0007Lb-00
	for ietf@ietf.org; Sun, 29 Jun 2003 01:55:48 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19WVA2-0007LQ-00
	for ietf@ietf.org; Sun, 29 Jun 2003 01:55:38 -0400
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 5FCD76259E; Sun, 29 Jun 2003 07:54:40 +0200 (CEST)
Date: Sat, 28 Jun 2003 15:53:19 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Aaron Falk <falk@isi.edu>, ietf@ietf.org
Subject: Re: what's a PWG?
Message-ID: <660445460.1056815599@localhost>
In-Reply-To: <20030628134858.GD5145@isi.edu>
References:  <20030628134858.GD5145@isi.edu>
X-Mailer: Mulberry/3.0.2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

PMTUD was approved as a WG yesterday, so it's probably "Probably a WG" or 
"Proto-WG".

Listing LEMONADE as such is, of course, an error.

--On 28. juni 2003 06:48 -0700 Aaron Falk <falk@isi.edu> wrote:

> Appears twice in http://www.ietf.org/meetings/agenda_57.html (pmtud &
> lemonade).
>
> --aaron
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which
> is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on
> what to pass are made solely by Raffaele D'Albenzio.
>
>







From owner-ietf@ietf.org  Sun Jun 29 09:10:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27786
	for <ietf-web-archive@odin.ietf.org>; Sun, 29 Jun 2003 09:10:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Wbod-00012T-IC
	for ietf-list@asgard.ietf.org; Sun, 29 Jun 2003 09:01:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Wbo5-00010z-Sl
	for ietf@asgard.ietf.org; Sun, 29 Jun 2003 09:01:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27620
	for <ietf@ietf.org>; Sun, 29 Jun 2003 09:01:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Wbnz-0000my-00
	for ietf@ietf.org; Sun, 29 Jun 2003 09:01:19 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Wbnk-0000mp-00
	for ietf@ietf.org; Sun, 29 Jun 2003 09:01:04 -0400
Received: (from falk@localhost)
	by nit.isi.edu (8.11.6/8.11.6) id h5TD0Zq00849;
	Sun, 29 Jun 2003 06:00:35 -0700
Date: Sun, 29 Jun 2003 06:00:35 -0700
From: Aaron Falk <falk@isi.edu>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org
Subject: Re: what's a PWG?
Message-ID: <20030629130035.GB690@isi.edu>
Mail-Followup-To: Harald Tveit Alvestrand <harald@alvestrand.no>,
	ietf@ietf.org
References: <20030628134858.GD5145@isi.edu> <660445460.1056815599@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <660445460.1056815599@localhost>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

Harald Tveit Alvestrand wrote:
> PMTUD was approved as a WG yesterday, so it's probably "Probably a WG" or 
> "Proto-WG".

"Proto" was my first guess, too.  However, I've changed my mind and
now think it's "pending."  

Interestingly, I received a some private responses indicating other
folks didn't know either and hoping for a conclusive definitions.
Suggest either expanding or avoiding this new acronym.

--aaron



From owner-ietf@ietf.org  Sun Jun 29 14:47:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03813
	for <ietf-web-archive@odin.ietf.org>; Sun, 29 Jun 2003 14:47:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Wh4k-0005fu-CF
	for ietf-list@asgard.ietf.org; Sun, 29 Jun 2003 14:38:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Wh3q-0005fA-PL
	for ietf@asgard.ietf.org; Sun, 29 Jun 2003 14:38:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03682
	for <ietf@ietf.org>; Sun, 29 Jun 2003 14:37:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Wh3V-0003vO-00
	for ietf@ietf.org; Sun, 29 Jun 2003 14:37:41 -0400
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Wh3K-0003v3-00
	for ietf@ietf.org; Sun, 29 Jun 2003 14:37:30 -0400
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 19Wh2z-0007NF-00
	for <ietf@ietf.org>; Sun, 29 Jun 2003 19:37:09 +0100
Date: Sun, 29 Jun 2003 19:37:09 +0100
To: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
Message-ID: <20030629183709.GA23233@fysh.org>
References: <20030626191147.9241F1390E@sa.vix.com> <20030626201839.GA6888@fysh.org> <iluk7b7kuzw.fsf@latte.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <iluk7b7kuzw.fsf@latte.josefsson.org>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

Simon Josefsson wrote:
>one added some text to clarify that it was actually intended to allow
>for zero length dnsname's (to denote the DNS root).

This is technically correct, according to RFC 1034, but will be confusing.
"dns:" intuitively looks incomplete.  It's more conventional to name
the root domain in absolute form, as ".".  An interesting comparison:
the "dig" DNS lookup tool from the BIND folks doesn't accept "" as a
domain name; it insists on the root domain being specified as ".".

So I argue that requiring the root domain to be represented as "." in the
context of the URI, forbidding a zero-length <dnsname>, will make for a
clearer protocol, more likely to be implemented correctly.  This isn't
an absolute matter, though; both versions of the protocol are workable.

-zefram



From owner-ietf@ietf.org  Sun Jun 29 16:46:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07365
	for <ietf-web-archive@odin.ietf.org>; Sun, 29 Jun 2003 16:46:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Wiws-0006cJ-1B
	for ietf-list@asgard.ietf.org; Sun, 29 Jun 2003 16:38:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Wiv9-0006bm-Q2
	for ietf@asgard.ietf.org; Sun, 29 Jun 2003 16:37:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07296
	for <ietf@ietf.org>; Sun, 29 Jun 2003 16:36:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WiuF-0005R8-00
	for ietf@ietf.org; Sun, 29 Jun 2003 16:36:15 -0400
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Wiu4-0005Qc-00
	for ietf@ietf.org; Sun, 29 Jun 2003 16:36:05 -0400
Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.12.9/8.12.9) with ESMTP id h5TKZObd029959
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK);
	Sun, 29 Jun 2003 22:35:25 +0200
To: Zefram <zefram@fysh.org>
Cc: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
References: <20030626191147.9241F1390E@sa.vix.com>
	<20030626201839.GA6888@fysh.org> <iluk7b7kuzw.fsf@latte.josefsson.org>
	<20030629183709.GA23233@fysh.org>
From: Simon Josefsson <jas@extundo.com>
X-Payment: hashcash 1.2 0:030629:zefram@fysh.org:27bf094c35ed9091
X-Hashcash: 0:030629:zefram@fysh.org:27bf094c35ed9091
X-Payment: hashcash 1.2 0:030629:ietf@ietf.org:10fdff5b4768d105
X-Hashcash: 0:030629:ietf@ietf.org:10fdff5b4768d105
Date: Sun, 29 Jun 2003 22:35:24 +0200
In-Reply-To: <20030629183709.GA23233@fysh.org> (zefram@fysh.org's message of
 "Sun, 29 Jun 2003 19:37:09 +0100")
Message-ID: <ilu4r28ipv7.fsf@latte.josefsson.org>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=-32.4 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT_GNUS_UA
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-ietf@ietf.org
Precedence: bulk

Zefram <zefram@fysh.org> writes:

> Simon Josefsson wrote:
>>one added some text to clarify that it was actually intended to allow
>>for zero length dnsname's (to denote the DNS root).
>
> This is technically correct, according to RFC 1034, but will be confusing.
> "dns:" intuitively looks incomplete.  It's more conventional to name
> the root domain in absolute form, as ".".  An interesting comparison:
> the "dig" DNS lookup tool from the BIND folks doesn't accept "" as a
> domain name; it insists on the root domain being specified as ".".
>
> So I argue that requiring the root domain to be represented as "." in the
> context of the URI, forbidding a zero-length <dnsname>, will make for a
> clearer protocol, more likely to be implemented correctly.  This isn't
> an absolute matter, though; both versions of the protocol are workable.

The current specification allows for both dns: and dns:., and they
refer to the same thing, the root.  People used to dig syntax will
have no problems, and people working with strict RFC 1034 conforming
applications will also have no problems.  Is there a need to forbid
zero length dnsname's?  I don't see what benefit that would bring,
could you please elaborate?

Thanks,
Simon




From owner-ietf@ietf.org  Mon Jun 30 02:20:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01960
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 02:20:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Wrma-0002VP-EQ
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 02:04:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Wrm4-0002V3-Pr
	for ietf@asgard.ietf.org; Mon, 30 Jun 2003 02:04:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25376
	for <ietf@ietf.org>; Mon, 30 Jun 2003 02:04:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Wrm2-0003mr-00
	for ietf@ietf.org; Mon, 30 Jun 2003 02:04:22 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Wrlr-0003mo-00
	for ietf@ietf.org; Mon, 30 Jun 2003 02:04:11 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 1722C62590; Mon, 30 Jun 2003 08:03:32 +0200 (CEST)
Date: Mon, 30 Jun 2003 08:03:32 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Yakov Rekhter <yakov@juniper.net>
Cc: ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
Message-ID: <69130000.1056953012@askvoll.hjemme.alvestrand.no>
In-Reply-To: <200306251642.h5PGgfu93505@merlot.juniper.net>
References:  <200306251642.h5PGgfu93505@merlot.juniper.net>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On onsdag, juni 25, 2003 09:42:19 -0700 Yakov Rekhter <yakov@juniper.net> 
wrote:

>
> the attached e-mail that have been posted to the PPVPN mailing
> list sheds some light on why the IETF's track record for this
> work so far is quite poor.
>

since we've started recycling other people's arguments, let me repost what 
Brian Carpenter replied on problem-statement too... nobody else rose up to 
refute him there on this issue.

> My spam filters decided to put it in the junk. But it neatly
> illustrates the issue we have when the I* tries to look at
> the big picture, and a special interest group looks only at its
> own small area - there is a genuine conflict of interest, and
> the IETF and its processes are set up to favour the big picture.
> That is not a problem IMHO. It's exactly correct, except that we
> have to explain it better to the special interest groups.
>
>    Brian





From owner-ietf@ietf.org  Mon Jun 30 03:47:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04319
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 03:47:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19WtFX-0001cs-Mn
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 03:38:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19WtEl-0001cQ-CD
	for ietf@asgard.ietf.org; Mon, 30 Jun 2003 03:38:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04051
	for <ietf@ietf.org>; Mon, 30 Jun 2003 03:37:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WtET-0004HO-00
	for ietf@ietf.org; Mon, 30 Jun 2003 03:37:49 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WtEJ-0004Gr-00
	for ietf@ietf.org; Mon, 30 Jun 2003 03:37:39 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 6AA991398C; Mon, 30 Jun 2003 07:36:24 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn)
References: <69130000.1056953012@askvoll.hjemme.alvestrand.no>
From: Paul Vixie <vixie@vix.com>
Date: 30 Jun 2003 07:36:24 +0000
In-Reply-To: <69130000.1056953012@askvoll.hjemme.alvestrand.no>
Message-ID: <g3n0g02f0n.fsf@sa.vix.com>
Lines: 27
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

harald@alvestrand.no (Harald Tveit Alvestrand) writes:

> ... nobody else rose up to refute him there on this issue.

ok, i'll bite.

> > My spam filters decided to put it in the junk. But it neatly
> > illustrates the issue we have when the I* tries to look at the big
> > picture, and a special interest group looks only at its own small area
> > - there is a genuine conflict of interest, and the IETF and its
> > processes are set up to favour the big picture.  That is not a problem
> > IMHO. It's exactly correct, except that we have to explain it better to
> > the special interest groups.

if the ietf could have goals, and one of them was to become dilute and
ineffectual, then the words "exactly right" above are, well, exactly right.
(priority focus on the big picture used to be more exactly right than it
is today, since the big picture in 1989 had fewer moving parts than today.)

so, i don't know if i'm refuting him exactly, but i do surely disagree.
it's only "not a problem" if someone takes a nondilute "bite sized" ("useful")
view of cross-special groups.  otherwise we'll have the special groups
in heads-down sandbox mode, doing work with no architectural connection to
their brothers and sisters in the next sandbox over, while the general
interest groups are trying to move continents but getting no traction. (oops.)
-- 
Paul Vixie



From owner-ietf@ietf.org  Mon Jun 30 05:52:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07420
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 05:52:49 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19WvCU-0003If-Py
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 05:43:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19WvAs-0003Hq-Tc
	for ietf@asgard.ietf.org; Mon, 30 Jun 2003 05:42:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07119
	for <ietf@ietf.org>; Mon, 30 Jun 2003 05:42:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WvAq-0005CE-00
	for ietf@ietf.org; Mon, 30 Jun 2003 05:42:12 -0400
Received: from web20711.mail.yahoo.com ([66.163.169.152])
	by ietf-mx with smtp (Exim 4.12)
	id 19WvAf-0005C4-00
	for ietf@ietf.org; Mon, 30 Jun 2003 05:42:01 -0400
Message-ID: <20030630094137.89089.qmail@web20711.mail.yahoo.com>
Received: from [80.240.192.37] by web20711.mail.yahoo.com via HTTP; Mon, 30 Jun 2003 02:41:37 PDT
Date: Mon, 30 Jun 2003 02:41:37 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: A Quantum Cryptography ( QC ) Critique
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1434957357-1056966097=:87628"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-1434957357-1056966097=:87628
Content-Type: text/plain; charset=us-ascii

(1) QC assumes that most of the photons from the transmitter of a 
"quantum" message, reach the receiver.  This assumption is therefore used to
errorneously deduce that the communicating parties will therefore be 
able to detect interception or interference.
Problem(a):  This is  not true for blue laser transceiver technology, 
as the receiver of a "quantum" message in this case needs far less than 
0.0001% of photons routed through blue laser routing satelittes, to receive a 
message.
Problem(b): Optical fibre losses an appreciable amount of photons which 
can be "tapped" non-intrusively.

(2) Traditional intelligence gathering can be used to intercept or 
reveal quantum cryptography keys and settings - e.g. the tapping of computer
monitor radiation, or intrusion into a network via weaknesses in 
wireless security or simply by way of deployment of corrupt practices.

(3) Quantum cryptographic communications is based on monoplex and not 
the duplex model of channel usage - I stand to be corrected.

(4) Intrusive penetration into a quantum cryptography secured network 
causes inteference which results into the jamming or shutdown of the system, 
while intrusive penetration into a "standard code" network will not result in 
the stoppage of communications.  
Note :  Those who intercept or retrieve standard code security 
information, I many cases never get to interprete it.  The intentions of a hacker 
may simply be to interfere - DoS ( Denial of Service ).

(5) Commercially available Quantum Cryptography technology is only 
optical fibre based, and cannot secure satelitte based blue laser quantum
communications technology.


Nyagudi Musandu
Consultant / Researcher
Tel.: 254-722-484730




---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
--0-1434957357-1056966097=:87628
Content-Type: text/html; charset=us-ascii

<DIV>
<DIV>(1) QC assumes that most of the photons from the transmitter of a <BR>"quantum" message, reach the receiver.&nbsp; This assumption is therefore used to<BR>errorneously deduce that the communicating parties will therefore be <BR>able to detect interception or interference.<BR>Problem(a):&nbsp; This is&nbsp; not true for blue laser transceiver technology, <BR>as the receiver of a "quantum" message in this case needs far less than <BR>0.0001% of photons routed through blue laser routing satelittes, to receive a <BR>message.<BR>Problem(b): Optical fibre losses an appreciable amount of photons which <BR>can be "tapped" non-intrusively.<BR><BR>(2) Traditional intelligence gathering can be used to intercept or <BR>reveal quantum cryptography keys and settings - e.g. the tapping of computer<BR>monitor radiation, or intrusion into a network via weaknesses in <BR>wireless security or simply by way of deployment of corrupt practices.<BR><BR>(3) Quantum cryptographic communications!
  is based
 on monoplex and not <BR>the duplex model of channel usage - I stand to be corrected.<BR><BR>(4) Intrusive penetration into a quantum cryptography secured network <BR>causes inteference which results into the jamming or shutdown of the system, <BR>while intrusive penetration into a "standard code" network will not result in <BR>the stoppage of communications.&nbsp; <BR>Note :&nbsp; Those who intercept or retrieve standard code security <BR>information, I many cases never get to interprete it.&nbsp; The intentions of a hacker <BR>may simply be to interfere - DoS ( Denial of Service ).<BR><BR>(5) Commercially available Quantum Cryptography technology is only <BR>optical fibre based, and cannot secure satelitte based blue laser quantum<BR>communications technology.<BR><BR><BR>Nyagudi Musandu<BR>Consultant / Researcher<BR>Tel.: 254-722-484730<BR></DIV></DIV><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://pa.yahoo.com/*http://rd.yahoo.com/evt=1207/*http://promo.yahoo.com/sbc/">SBC Yahoo! DSL</a> - Now only $29.95 per month!
--0-1434957357-1056966097=:87628--



From owner-ietf@ietf.org  Mon Jun 30 06:36:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08515
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 06:36:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Wvww-00046d-NE
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 06:31:54 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19WvwY-000462-QG
	for ietf@asgard.ietf.org; Mon, 30 Jun 2003 06:31:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08460
	for <ietf@ietf.org>; Mon, 30 Jun 2003 06:31:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19WvwV-0005V2-00
	for ietf@ietf.org; Mon, 30 Jun 2003 06:31:27 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 19WvwL-0005Uz-00
	for ietf@ietf.org; Mon, 30 Jun 2003 06:31:17 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 5D6A9625BC; Mon, 30 Jun 2003 12:30:43 +0200 (CEST)
Date: Mon, 30 Jun 2003 12:30:43 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Yakov Rekhter <yakov@juniper.net>
Cc: ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
Message-ID: <91040000.1056969043@askvoll.hjemme.alvestrand.no>
In-Reply-To: <200306251600.h5PG0pu90386@merlot.juniper.net>
References:  <200306251600.h5PG0pu90386@merlot.juniper.net>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On onsdag, juni 25, 2003 09:00:28 -0700 Yakov Rekhter <yakov@juniper.net> 
wrote:

> I certainly agree with your on the "track record". But I think we
> need to be a bit more specific on why the track record is "quite
> poor". For example, why the IESG didn't approve 2547bis as a Proposed
> Standard 2 years ago ?  Ditto for draft-martini... Perhaps folks
> from the IESG would care to explain this...

It might have something to do with the fact that the WG has not requested 
that the IESG process these drafts.... if the WG has not come to consensus 
on asking for the drafts to be published, I'm afraid the IESG cannot do 
anything.

NOTE: I am completely aware that IESG members have been active in the 
architectural discussions that have led to the WG not asking for 
standards-track publication on these drafts. But the reason for these 
non-actions is, I believe, to be found in the *working group* process.

                Harald, who is NOT active in ppvpn




From owner-ietf@ietf.org  Mon Jun 30 06:47:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08879
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 06:47:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Ww8Z-0004ZU-Dd
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 06:43:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19Ww7h-0004YZ-Hd
	for ietf@asgard.ietf.org; Mon, 30 Jun 2003 06:43:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08749;
	Mon, 30 Jun 2003 06:42:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ww7A-0005Zz-00; Mon, 30 Jun 2003 06:42:28 -0400
Received: from natint.juniper.net ([207.17.136.129] helo=merlot.juniper.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ww6z-0005ZW-00; Mon, 30 Jun 2003 06:42:17 -0400
Received: from kummer.juniper.net (kummer.juniper.net [172.17.12.90])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h5UAenu43927;
	Mon, 30 Jun 2003 03:40:49 -0700 (PDT)
	(envelope-from kireeti@juniper.net)
Received: from localhost (kireeti@localhost)
	by kummer.juniper.net (8.11.6/8.9.3) with ESMTP id h5UAemo32782;
	Mon, 30 Jun 2003 03:40:48 -0700 (PDT)
	(envelope-from kireeti@juniper.net)
X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs
Date: Mon, 30 Jun 2003 03:40:48 -0700 (PDT)
From: Kireeti Kompella <kireeti@juniper.net>
To: Jonathan Sadler <jonathan.sadler@tellabs.com>
cc: iesg@ietf.org, "" <ietf@ietf.org>, "" <ccamp@ops.ietf.org>
Subject: Re: Last Call: Routing Extensions in Support of Generalized MPLS 
 vto  Proposed Standard
In-Reply-To: <3E59A5B4.880B91D2@tellabs.com>
Message-ID: <20030630033022.C32724@kummer.juniper.net>
References: <H0000c08064ac643.1044985131.mailw02@MHS> <3E59A5B4.880B91D2@tellabs.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Jonathan,

On Sun, 23 Feb 2003, Jonathan Sadler wrote:

> Please consider the following comments on these drafts:
>     draft-ietf-ccamp-gmpls-routing-05.txt
>     draft-ietf-ccamp-ospf-gmpls-extensions-09.txt
> Many of the comments are based on implementation experience.  These comments are
> marked with a (*).
>
> Jonathan Sadler
>
> ==========
>
> 1. In section 4.4.2 of draft-ietf-ccamp-gmpls-routing-05.txt, the operations for
> Packet Switch Capable (PSC) are defined.  Reference is made to Minimum LSP bandwidth
> for SDH encoding.  None of the examples in section 5 of
> draft-ietf-ccamp-gmpls-routing-05.txt show how this field should filled.

Is the suggestion that Min LSP bw be removed for PSC?

> 2. The mechanism for showing relationships between server and client layers is not
> generalized*.  Specifically:

I've incorporated most of Stephen Shew's text on layer relations
almost as is.  Most of the specific comments you have should really
be addressed (IMO) to a document on routing for SONET/SDH (such as
draft-mannie-ccamp-gmpls-sonet-sdh-isis[ospf]-00.txt).  Please review
the new text, and let us know if there are issues to be addressed by
*this* document.

> 3. Layer specific attributes are not supported*.  Specifically:
>  - It is not possible to have a link with different costs at
>    different layers (ex. VC-11, VC-4, VC4-4c).
...
>  - Many attributes discussed actually refer to a specific layer*.
...
>  - Combining layer specific attributes with layer relationships can
>    provide a more efficient encoding mechanism than requiring
>    separate link announcements per layer*.
...
> 4. The "TDM" Interface Switching Capability presumably includes
>    layers other than SONET/SDH, such as PDH* (DS1, DS3, E1, E3) and
>    G.709.  The interaction with these layers needs to be defined.
...
> 5. In many cases, 8 levels of priority are not necessary*.  A more
>    compact encoding that has a bitfield stating the priority levels
>    being announced would reduce the size of the announcement.

Do you have specific text that you think falls under the realm of
the overall functional spec (as opposed to layer-specific docs)?

Thanks,
Kireeti.



From owner-ietf@ietf.org  Mon Jun 30 10:04:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25202
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 10:04:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Wz6y-0003I7-20
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 09:54:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19W3to-000218-3X
	for ietf@asgard.ietf.org; Fri, 27 Jun 2003 20:49:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28227
	for <ietf@ietf.org>; Fri, 27 Jun 2003 20:49:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W3tm-00004W-00
	for ietf@ietf.org; Fri, 27 Jun 2003 20:49:02 -0400
Received: from fh.vix.com ([204.152.188.20])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W3tW-00002t-00
	for ietf@ietf.org; Fri, 27 Jun 2003 20:48:46 -0400
Received: from fh.vix.com (localhost [127.0.0.1])
	by fh.vix.com (Postfix) with ESMTP id 4EDE2230012
	for <ietf@ietf.org>; Sat, 28 Jun 2003 00:47:26 +0000 (GMT)
	(envelope-from vixie@fh.vix.com)
To: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt 
In-Reply-To: Message from Simon Josefsson <jas@extundo.com> 
   of "Sat, 28 Jun 2003 01:55:28 +0200." <iluel1fkrdb.fsf@latte.josefsson.org> 
X-Mailer: MH-E 7.1; nmh 1.0.4; Emacs 21.3
Date: Sat, 28 Jun 2003 00:47:26 +0000
From: Paul Vixie <vixie@fh.vix.com>
Message-Id: <20030628004726.4EDE2230012@fh.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> > very well.  then i request that you remove the "hostport" from the syntax.
> 
> The rationale being?

you said it best, earlier:

> >> ... Furthermore, DNS URIs do not require the use of the DNS protocol at
> >> all, it just denote a DNS resource. ...

a dns resource lives where its parent NS RRs say it lives -- and not, as
you also suggest...

> The hostport describes the authority that know the intended DNS
> resource.  An authority is useful even for abstract, non-DNS-protocol,
> DNS resources.  DNS resources themselves are indexed by (NAME, CLASS,
> TYPE), but to distinguish between the answer that entity A
> knows/generate, and the answer that entity B knows/generate, an
> authority scope like "hostport" is needed.

...in the answers that different entities can generate.

> Most applications probably will not care, and use the "default"
> authority, trusting the local server to do the right thing.  But for
> internal DNS environments, specifying the authority could be required.

you can't have it both ways.  either you're trying to represent dns data
using the <qname,qtype,qclass> tuple, or you're trying to represent
the query itself.  if you want to represent the query, you need RD and
hostport and lots of other things like the EDNS0 buffer size and so on.
if you want to represent a metatuple, then there can be no hostport since
the name itself gives rise to the places (either through recursion or not)
where the data can be found.

> I agree it is less confusing if the word "hostport" was avoided, and
> the word "authority" is used instead.  Also, using the word
> "authority" instead of "server" elsewhere would also improve matters.
> I have made this change for the next revision, a snapshot is available
> from <http://josefsson.org/draft-josefsson-dns-url.txt>.

no, that won't fix the problem.  you have fundamentally got to choose whether
you are representing a query (which can have a hostpart but which ought to
also have RD, buffer size, and other options as defined in the future) or
or whether you are representing the data itself by specifying the name,
type, and class.  calling it an authority won't change the layering violation.

dns is a distributed, autonomous, coherent, reliable database.  a syntax
that allows entity A and entity B to speak incoherently about a given <qname,
qtype,qclass> would violate the coherency of the design.  the only exception
would be if you intended to be able to represent all attributes of a dns
query, which i think would be useless, but would allow hostport but require
RD, buffer size, and other EDNS OPT options to be invented later.





From owner-ietf@ietf.org  Mon Jun 30 10:04:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25214
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 10:04:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Wz6x-0003H4-Ii
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 09:54:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19W4A1-0004Hb-9u
	for ietf@asgard.ietf.org; Fri, 27 Jun 2003 21:05:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28737;
	Fri, 27 Jun 2003 21:05:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W49z-0000BY-00; Fri, 27 Jun 2003 21:05:47 -0400
Received: from mclean.mail.mindspring.net ([207.69.200.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 19W49o-0000BE-00; Fri, 27 Jun 2003 21:05:36 -0400
Received: from dialup-67.30.21.192.dial1.dallas1.level3.net ([67.30.21.192] helo=ix.netcom.com)
	by mclean.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 19W48q-0007Pb-00; Fri, 27 Jun 2003 21:04:37 -0400
Message-ID: <3EFD04EF.2FE8B504@ix.netcom.com>
Date: Fri, 27 Jun 2003 20:01:03 -0700
From: Jeff Williams <jwkckid1@ix.netcom.com>
Organization: INEGroup Spokesman
X-Mailer: Mozilla 4.08 [en] (Win95; U; 16bit)
MIME-Version: 1.0
To: todd glassey <todd.glassey@worldnet.att.net>
CC: Harald Tveit Alvestrand <harald@Alvestrand.no>, IETF <ietf@ietf.org>,
        iesg@ietf.org, poised@lists.tislabs.com
Subject: Re: What review is required for "IETF Consensus"?
References: <200301312106.h0VL6gt00339@rotala.raleigh.ibm.com> <166408723.1044181809@localhost> <3E3DFDA8.4F50DD55@ix.netcom.com> <018601c33cb5$988201f0$020aff0a@tsg1>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Todd, Harald and all,

  I agree with you here Todd, unfortunately and sadly.  Hence
perhaps leaving the stakeholders/users, most of which will be
unaware and many will be unnecessarily taken advantage of
from time to time...

todd glassey wrote:

> The real problem Jeff, is that there is no want of a true consensus here, or
> a more formalized description of the vetting process or what is involved in
> it. The cost in making the IETF what the descriptions of it paint it as,
> would in fact break it financially with the current operations and funding
> models. So what you are really asking for (*and reasonably so by the way) is
> a total rethinking of the bigger-picture issue of what actually constitutes
> vetting and the advancement of an initiative.
>
> There is also this underlying concept that all members of a WG ***must***
> participate in the vetting of each and every project or initiative that is
> vetted within a WG's operations and this is also completely untrue except in
> the rare case where a WG only has ONE initiative.
>
> Todd
>
> ----- Original Message -----
> From: "Jeff Williams" <jwkckid1@ix.netcom.com>
> To: "Harald Tveit Alvestrand" <harald@Alvestrand.no>
> Cc: "IETF" <ietf@ietf.org>; <iesg@ietf.org>; <poised@lists.tislabs.com>
> Sent: Sunday, February 02, 2003 10:27 PM
> Subject: Re: What review is required for "IETF Consensus"?
>
> > Harald and all,
> >
> >   I "Guess" that a IETF consensus really means whatever you Harald
> > says it means much like what consensus meant while you were
> > Chair of the DNSO GA.  But to be honest, no consensus can be
> > determined unless it is measured, which means a VOTE must be
> > held amongst IETF participants.  Perish the thought, eh Harald?!  >;)
> >
> > Harald Tveit Alvestrand wrote:
> >
> > > Thread B from my previous message..... this is being CCed to the POISED
> > > list, for reasons that may be obvious after reading the message; for
> POISED
> > > subscribers - this is followup to an IETF list thread.
> > >
> > > Question:
> > >
> > > What review process must the IESG take before taking the action to block
> or
> > > allow publication of such an internet-draft (ie "what does IETF
> Consensus
> > > mean")?
> > >
> > > This is not written in RFC 2434.
> > > Some tactics that have been used in the past to gather information for
> the
> > > IESG's decision include:
> > >
> > > - "It's obviously OK". Approved WG document, or competently written
> > > documentation from subject matter experts, reviewed by people with
> > > competence on the specific registry. The IESG looks at it and thinks
> that
> > > it's obvioiusly right. Example: application/ogg, documented in
> > > draft-walleij-ogg-mediatype.
> > >
> > > - Subject matter expert group review. For instance, posting to the DHC
> WG
> > > asking for opinions on a DHCP extension. WG chairs' feedback will carry
> a
> > > lot of weight.
> > >
> > > - IETF Last Call for Informational/Experimental, with the IESG
> evaluating
> > > the feedback.
> > >
> > > In all cases, the IESG has to evaluate; there's no other established
> body
> > > to do it. "The buck stops here".
> > >
> > > Among the cases to consider:
> > >
> > > - Everyone approves. Go for it.
> > >
> > > - Nobody cares. No comments; the IESG will usually decide that nobody
> saw
> > > any looming danger to the Internet, and allow the registration.
> > >
> > > - Serious objections. The comments clearly indicate that the
> registration
> > > would be harmful to the Internet (and how), and the IESG agrees with
> that
> > > evaluation. The IESG will refuse.
> > >
> > > - Incompetent or incomplete document. The IESG will usually object to
> this
> > > on its own - without documentation clear enough to determine whether
> this
> > > is OK or harmful, it would be remiss of the IESG to let the document go
> > > forward even to an IETF Last Call.
> > > We can't claim IETF consensus on something we can't understand.
> > >
> > > - Dissension within the IETF. Like in the case of a WG, the IESG has to
> > > evaluate the arguments on their merits; obviously the proposers think
> that
> > > the registration should be allowed, and opposition without a rational
> basis
> > > should no more be allowed to block this registration than it should be
> > > allowed to block WG progress. But as the saying goes - "this is why you
> get
> > > the big bucks".
> > > Among the things to consider here is that the determination must be made
> in
> > > a timely fashion - sometimes there are reasons why letting debate rage
> for
> > > another 6 months doesn't seem like an attractive option.
> > >
> > > Questions for the audience:
> > >
> > > - should this description, or something like it, go into
> > > draft-iesg-procedures?
> > > - are there guidelines that the IESG should use when trying to determine
> > > the right outcome in the "dissension" case?
> > > - does this debate belong on the POISED list, together with the
> discussion
> > > of the IESG charter and the IESG procedures?
> > >
> > > Thoughts?
> > >
> > >                  Harald
> >
> > Regards,
> > --
> > Jeffrey A. Williams
> > Spokesman for INEGroup LLA. - (Over 129k members/stakeholders strong!)
> > ================================================================
> > CEO/DIR. Internet Network Eng. SR. Eng. Network data security
> > Information Network Eng. Group. INEG. INC.
> > E-Mail jwkckid1@ix.netcom.com
> > Contact Number: 214-244-4827 or 214-244-3801
> >
> >

Regards,

--
Jeffrey A. Williams
Spokesman for INEGroup LLA. - (Over 131k members/stakeholders strong!)
"Be precise in the use of words and expect precision from others" -
    Pierre Abelard
===============================================================
CEO/DIR. Internet Network Eng. SR. Eng. Network data security
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number: 214-244-4827 or 214-244-3801







From owner-ietf@ietf.org  Mon Jun 30 10:04:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25196
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 10:04:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19Wz6x-0003Hx-TF
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 09:54:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19W2IF-00070V-F3
	for ietf@asgard.ietf.org; Fri, 27 Jun 2003 19:06:11 -0400
Received: from fh.vix.com (fh.vix.com [204.152.188.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25216
	for <ietf@ietf.org>; Fri, 27 Jun 2003 19:05:07 -0400 (EDT)
Received: from fh.vix.com (localhost [127.0.0.1])
	by fh.vix.com (Postfix) with ESMTP
	id 38F7F23000C; Fri, 27 Jun 2003 22:59:05 +0000 (GMT)
	(envelope-from vixie@fh.vix.com)
To: Simon Josefsson <jas@extundo.com>
Cc: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt 
In-Reply-To: Message from Simon Josefsson <jas@extundo.com> 
   of "Sat, 28 Jun 2003 00:31:05 +0200." <ilur85fkv9y.fsf@latte.josefsson.org> 
X-Mailer: MH-E 7.1; nmh 1.0.4; Emacs 21.3
Date: Fri, 27 Jun 2003 22:59:05 +0000
From: Paul Vixie <vixie@fh.vix.com>
Message-Id: <20030627225905.38F7F23000C@fh.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> ...
> Furthermore, DNS URIs do not require the use of the DNS protocol at
> all, it just denote a DNS resource.  DNS URIs can be resolved via HTTP
> or something else.  Having the RD bit present is a hint to the DNS
> protocol; the RD bit has no connection with the DNS resource that the
> URI denote.
> ...

very well.  then i request that you remove the "hostport" from the syntax.





From owner-ietf@ietf.org  Mon Jun 30 11:38:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01606
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 11:38:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19X0ZN-0007tO-2g
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 11:27:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19X0Yf-0007oO-Om
	for ietf@asgard.ietf.org; Mon, 30 Jun 2003 11:27:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01124
	for <ietf@ietf.org>; Mon, 30 Jun 2003 11:27:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19X0Yd-0001pH-00
	for ietf@ietf.org; Mon, 30 Jun 2003 11:27:07 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 19X0YO-0001ox-00
	for ietf@ietf.org; Mon, 30 Jun 2003 11:26:52 -0400
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h5UFQCg5026476;
	Mon, 30 Jun 2003 11:26:12 -0400 (EDT)
Message-Id: <200306301526.h5UFQCg5026476@rtp-core-1.cisco.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: Yakov Rekhter <yakov@juniper.net>, ietf@ietf.org
Subject: Re: WG review: Layer 2 Virtual Private Networks (l2vpn) 
In-reply-to: Your message of Mon, 30 Jun 2003 12:30:43 +0200.
             <91040000.1056969043@askvoll.hjemme.alvestrand.no> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Mon, 30 Jun 2003 11:26:12 -0400
From: Eric Rosen <erosen@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


Harald> It might  have something  to do with  the fact  that the WG  has not
Harald> requested that the  IESG process these drafts.... if  the WG has not
Harald> come  to consensus on  asking for  the drafts  to be  published, I'm
Harald> afraid the IESG cannot do anything. 

I consider this answer to be rather disingenuous.

The WG has  not requested that the IESG process these  drafts because the WG
chairs have  told the  WG that  the ADs have  told them  that the  drafts in
question cannot be submitted to the IESG until numerous other drafts that no
one  will  ever  read  (requirements,  framework,  architecture)  have  been
approved by the  IESG.  Of course, most of those  numerous other drafts were
completed about 18 months ago, though a few of them have now come out of the
seemingly endless  "IESG reviews,  WG makes minor  change, IESG  reviews, WG
change" cycle.  

So you  can't honestly  answer Yakov by  saying "the  WG hasn't asked  us to
process  these  drafts";  the  answer   to  Yakov's  question  would  be  an
explanation of (a) why all these  prior drafts are really necessary, (b) why
it is reasonable for such a long  review cycle, and (c) why it is reasonable
to delay  starting to process the  protocol specs until the  prior specs are
already on the RFC Editor's queue. 











From owner-ietf@ietf.org  Mon Jun 30 12:27:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04374
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 12:27:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19X1Oe-0002ES-5R
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 12:20:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19X1Mr-00020E-69
	for ietf@asgard.ietf.org; Mon, 30 Jun 2003 12:19:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03848
	for <ietf@ietf.org>; Mon, 30 Jun 2003 12:18:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19X1Mn-0002KT-00
	for ietf@ietf.org; Mon, 30 Jun 2003 12:18:57 -0400
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 19X1MX-0002Jp-00
	for ietf@ietf.org; Mon, 30 Jun 2003 12:18:43 -0400
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 19X1Ku-0007ES-00
	for <ietf@ietf.org>; Mon, 30 Jun 2003 17:17:00 +0100
Date: Mon, 30 Jun 2003 17:17:00 +0100
To: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
Message-ID: <20030630161659.GB9368@fysh.org>
References: <iluel1fkrdb.fsf@latte.josefsson.org> <20030628004726.4EDE2230012@fh.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030628004726.4EDE2230012@fh.vix.com>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

Paul Vixie wrote:
>you can't have it both ways.  either you're trying to represent dns data
>using the <qname,qtype,qclass> tuple, or you're trying to represent
>the query itself.

I recognise what Paul describes as the layering violation, but I don't
think that it is sufficient to require that the <hostport> syntax
should go.  Information from two different layers is being presented
together, but the two layers are adjacent, so they can be treated as a
single layer when looking from the outside.  We have similar features in
other deployed URL types.  (By the way, I see the RD bit, and other things
Paul has mentioned, as being at a third layer, below the authority layer.
We can sensibly have authority location data without giving details of
the DNS query.)

What *is* a concern is that some URI schemes have much worse layering
issues, such as the overloading of the authority component in the http
URL scheme (the authority is used for both location and naming).  It is
arguable that having the <hostport> syntax in URI schemes encourages the
development of this kind of misfeature, and that this mixing of location
and naming data should be avoided for this reason.

This touches on an issue that I've been wondering about.  I'm not entirely
clear on what the <dnsqueryelement> extension mechanism is for.  What kind
of information might it represent?  If the URI scheme is intended purely
to represent a <name,type,class> tuple then there is no possible use for
the extension mechanism -- no additional information that one would ever
want to add to the tuple.  In considering reasonable usage scenarios I
came up with only one additional element that one might want to use: a
flag meaning "insist on the data being cryptographically authenticated".
On reflection, I think such a flag belongs in the authority section:
it's the same layer, and if we are going to include information at both
layers then I'd like to keep them syntactically separate.  Certainly this
flag should exist in the syntax iff the authority section exists.

Outside the context of any specific query elements, it seems that the
primary purpose (though, if there is an authority section, not the
sole purpose) of the URI scheme is to represent a <name,type,class>
tuple -- a location in abstract domain name space -- and, that being
a closed coordinate system, there is no additional element that can
usefully be added to that part of the URI.  I'd like to see a syntax
(either this URI scheme or a syntactically distinct part of it) to
express a pure <name,class,type> tuple, with no general extensibility.
If the URI scheme needs an extension mechanism, it should be separate
from the <name,class,type> syntax.

I have more opinions about how a distinct <name,class,type> tuple syntax
should look, which I'll save for a separate message, since this one is
dealing more with philosophical issues than concrete syntax.

Yet another protocol matter that hasn't been addressed so far: how are
domain name labels other than character labels (e.g., binary labels)
to be represented in the URI syntax?  Most applications that need to
represent these kinds of labels in character strings use the master file
format defined in the RFCs, but draft-josefsson-dns-url is quite clear
that it doesn't use that syntax.  It offers no syntax for binary labels,
and no extension mechanism for future label types.

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



From owner-ietf@ietf.org  Mon Jun 30 13:46:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08061
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 13:46:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19X2b4-0006Dv-6Y
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 13:37:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19X2ZA-00069w-3V
	for ietf@asgard.ietf.org; Mon, 30 Jun 2003 13:35:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07470
	for <ietf@ietf.org>; Mon, 30 Jun 2003 13:33:53 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19X2XI-000304-00
	for ietf@ietf.org; Mon, 30 Jun 2003 13:33:52 -0400
Received: from h80ad2713.async.vt.edu ([128.173.39.19] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19X2X7-0002zl-00
	for ietf@ietf.org; Mon, 30 Jun 2003 13:33:41 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10.Beta0/8.12.10.Beta0) with ESMTP id h5UHWPNS029090;
	Mon, 30 Jun 2003 13:32:25 -0400
Message-Id: <200306301732.h5UHWPNS029090@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: NM Research <nm_research@yahoo.com>
Cc: ietf@ietf.org
Subject: Re: A Quantum Cryptography ( QC ) Critique 
In-Reply-To: Your message of "Mon, 30 Jun 2003 02:41:37 PDT."
             <20030630094137.89089.qmail@web20711.mail.yahoo.com> 
References: <20030630094137.89089.qmail@web20711.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1962267592P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 30 Jun 2003 13:32:24 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Mon, 30 Jun 2003 02:41:37 PDT, NM Research <nm_research@yahoo.com>  said:

> (1) QC assumes that most of the photons from the transmitter of a 
> "quantum" message, reach the receiver.  This assumption is therefore used to
> errorneously deduce that the communicating parties will therefore be 
> able to detect interception or interference.
> Problem(a):  This is  not true for blue laser transceiver technology, 
> as the receiver of a "quantum" message in this case needs far less than 
> 0.0001% of photons routed through blue laser routing satelittes, to receive a
> message.
> Problem(b): Optical fibre losses an appreciable amount of photons which 
> can be "tapped" non-intrusively.

You're missing the point.  You can tap the cable, but you can't actually peek
at the photons as they go by without tipping off that you're peeking *at those
particular photons*.

> (2) Traditional intelligence gathering can be used to intercept or 
> reveal quantum cryptography keys and settings - e.g. the tapping of computer
> monitor radiation, or intrusion into a network via weaknesses in 
> wireless security or simply by way of deployment of corrupt practices.

Marcus Ranum coined the phrase "Rubber Hose Cryptography" for this. No amount
of 1024-versus-2048 bit key arguing is going to matter if The Bad Guys tell you
"Give us the key or we'll beat the snot out of you" (not that such people are
ready available to most criminal organizations and governments), and it's long
been known that most off-the-shelf crypto's biggest weakness is deployment by
stupid users....

> (3) Quantum cryptographic communications is based on monoplex and not 
> the duplex model of channel usage - I stand to be corrected.

Ever actually *looked* at the average GBIC?  There's a send side and a receive
side, just because it's easier to build a fiber *pair* of unidirectional
links....

> (4) Intrusive penetration into a quantum cryptography secured network 
> causes inteference which results into the jamming or shutdown of the system, 
> while intrusive penetration into a "standard code" network will not result in
> the stoppage of communications.  
> Note :  Those who intercept or retrieve standard code security 
> information, I many cases never get to interprete it.  The intentions of a hacker 
> may simply be to interfere - DoS ( Denial of Service ).

Actually, no.

Most QC implementations are *poor* at transmitting data - they're only good for
giving both participants the same truly random unsnoopable session key.  So for
any *practical* use, you'd use QC to exchange the session key and then some
other scheme to encrypt the session using the key.

Such hybrid operations are standard practice in practical cryptography - for
instance, RSA is very nice but takes an inordinate amount of time to do a
"real" amount of data (for instance, a 10K E-mail) as you have to treat that
10K as an 80,000 bit integer and do math on it.  So what PGP (for instance)
does is use RSA to secure a very much smaller session key (256 or so bits), and
then use that key to initialize some symmetric cypher such as IDEA.

Remember that this has to be discussed in the context of threat models.

The people likely to be deploying QC anytime soon are *ALSO* the people who
worry about things like the physical diversity of their network, so a motivated
attacker can't cut them off the network by hitting one target. I'm *NOT* going
to say much on this topic, other that to mention "Just how many ways *are*
there to run a fiber path into Manhattan?"

Sure, a dedicated hacker could disrupt my QC.  On the other hand, I have to do
my day-to-day work in a Real World where a credible estimate has 3 million
compromised machines (http://www.vnunet.com/News/1141901) - and it probably
would not take more than a few thousand to totally DDoS our 2xOC12.  Of course,
our net is engineered to give 2xOC12 reliably, and hacker resilience is just a
by product. If our goal had been to resist intrusions and we cared enough to
deploy QC, you can be *sure* that our network design would be hardened against
other attacks as well.... ;)

> (5) Commercially available Quantum Cryptography technology is only 
> optical fibre based, and cannot secure satelitte based blue laser quantum
> communications technology.

Comment 1:  New technology, it's not surprising that it's not available in every
flavor yet.  How many colors were cars available in when the Model T came out? ;)

Comment 2: Is there a *market* for satellite based blue laser?  Seems to me that
the first heavy rainstorm would cause packet loss unless you had enough power
budget to punch through - in which case it's not a comm device, it's a weapon.


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

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

iD8DBQE/AHQocC3lWbTT17ARAlYmAJwKK4q+swvcklb3K+kzcyBlxkA62gCfYnfQ
Ai1Y9KfC8Ue4+ApCYvhH2P4=
=dxXc
-----END PGP SIGNATURE-----

--==_Exmh_-1962267592P--



From owner-ietf@ietf.org  Mon Jun 30 15:02:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11157
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 15:02:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19X3nf-0001mT-UV
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 14:54:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19X3nU-0001jX-Rm
	for ietf@asgard.ietf.org; Mon, 30 Jun 2003 14:54:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10738
	for <ietf@ietf.org>; Mon, 30 Jun 2003 14:54:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19X3nT-0003Wj-00
	for ietf@ietf.org; Mon, 30 Jun 2003 14:54:39 -0400
Received: from [206.112.85.61] (helo=mail.cdt.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19X3nJ-0003WQ-00
	for ietf@ietf.org; Mon, 30 Jun 2003 14:54:29 -0400
Received: from [10.0.1.19] (66.safeclick.net [63.119.245.66])
	by mail.cdt.org (Postfix) with ESMTP
	id 0100A4900F5; Mon, 30 Jun 2003 14:51:31 -0400 (EDT)
Mime-Version: 1.0
X-Sender: john@mail.cdt.org
Message-Id: <a05200f06bb26318de147@[10.0.1.19]>
Date: Mon, 30 Jun 2003 14:54:24 -0400
To: ietf@ietf.org
From: John Morris <jmorris@cdt.org>
Subject: Seeking feedback on I-D discussing "public policy considerations"
Cc: "Davidson, Alan " <abd@cdt.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

As some of you may have noticed, last week we submitted an 
Internet-Draft entitled "Public Policy Considerations for Internet 
Design Decisions."  The abstract and link are below.

The draft uses the same basic approach as was used by the IAB in RFC 
3426 on "General Architectural and Policy Considerations" -- our 
draft suggests questions relating to public policy concerns that 
should be considered in working on protocols, without suggesting that 
any particular answer or result should flow from the questions.  The 
draft also advances an argument about why the IETF should try to be 
aware of public policy issues in the first place.

This draft is very much a "work in progress," and we welcome input, 
suggestions, criticism, etc.  In particular, the draft would benefit 
from additional concrete examples of public policy issues that have 
cropped up in the past.

Send feedback to jmorris@cdt.org (or for the moment to the ietf list 
if it is a broader comment).  If there is enough feedback and 
interest, we could set up a separate mailing list to discuss the 
draft.  John also would be interested in getting together for a "bar 
bof" in Vienna with anyone interested in commenting on or 
contributing to the draft -- e-mail if interested.
Thanks for looking at this draft.

John Morris & Alan Davidson

>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
>	Title		: Public Policy Considerations for Internet Design
>                           Decisions
>	Author(s)	: J. Morris, A. Davidson
>	Filename	: draft-morris-policy-considerations-00.txt
>	Pages		: 21
>	Date		: 2003-6-24
>
>This document suggests public policy questions that the IETF should
>consider and possibly address when developing new standards and
>protocols, and modifying or enhancing old standards and protocols. 
>This document contains questions to be considered, as opposed to
>guidelines or rules that should in all cases be followed.  This first
>draft provides a framework for identifying and discussing questions
>of public policy concern, and invites members of the IETF community
>to contribute to the questions and discussions raised here.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-morris-policy-considerations-00.txt
>



From owner-ietf@ietf.org  Mon Jun 30 22:01:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26137
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 22:01:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19XAK8-0002Wu-E5
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 21:52:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19XAJg-0002Tk-Bc
	for ietf@asgard.ietf.org; Mon, 30 Jun 2003 21:52:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25841
	for <ietf@ietf.org>; Mon, 30 Jun 2003 21:52:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XAJe-00061L-00
	for ietf@ietf.org; Mon, 30 Jun 2003 21:52:18 -0400
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19XAJT-00060v-00
	for ietf@ietf.org; Mon, 30 Jun 2003 21:52:07 -0400
Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.12.9/8.12.9) with ESMTP id h611pIG9028554
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK);
	Tue, 1 Jul 2003 03:51:19 +0200
To: Paul Vixie <vixie@fh.vix.com>
Cc: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
References: <20030628004726.4EDE2230012@fh.vix.com>
From: Simon Josefsson <jas@extundo.com>
X-Payment: hashcash 1.2 0:030701:vixie@fh.vix.com:1525910b4debfc69
X-Hashcash: 0:030701:vixie@fh.vix.com:1525910b4debfc69
X-Payment: hashcash 1.2 0:030701:ietf@ietf.org:a8d491945365d54b
X-Hashcash: 0:030701:ietf@ietf.org:a8d491945365d54b
Date: Tue, 01 Jul 2003 03:51:18 +0200
In-Reply-To: <20030628004726.4EDE2230012@fh.vix.com> (Paul Vixie's message
 of "Sat, 28 Jun 2003 00:47:26 +0000")
Message-ID: <iluof0fggkp.fsf@latte.josefsson.org>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=-32.4 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT_GNUS_UA
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-ietf@ietf.org
Precedence: bulk

Paul Vixie <vixie@fh.vix.com> writes:

>> > very well.  then i request that you remove the "hostport" from the syntax.
>> 
>> The rationale being?
>
> you said it best, earlier:
>
>> >> ... Furthermore, DNS URIs do not require the use of the DNS protocol at
>> >> all, it just denote a DNS resource. ...
>
> a dns resource lives where its parent NS RRs say it lives -- and not, as
> you also suggest...
>
>> The hostport describes the authority that know the intended DNS
>> resource.  An authority is useful even for abstract, non-DNS-protocol,
>> DNS resources.  DNS resources themselves are indexed by (NAME, CLASS,
>> TYPE), but to distinguish between the answer that entity A
>> knows/generate, and the answer that entity B knows/generate, an
>> authority scope like "hostport" is needed.
>
> ...in the answers that different entities can generate.

This view limit the usefulness of the URI, as it cannot be used to
refer to, e.g., not-yet delegated data.  It can be useful to use DNS
URIs to denote DNS data in a delegation request, to indicate where the
new data will be placed, so it can be checked for conformance with
various rules.

>> Most applications probably will not care, and use the "default"
>> authority, trusting the local server to do the right thing.  But for
>> internal DNS environments, specifying the authority could be required.
>
> you can't have it both ways.  either you're trying to represent dns data
> using the <qname,qtype,qclass> tuple, or you're trying to represent
> the query itself.

I'm trying, like the document says, to represent dns data using the
<qname,qtype,qclass> tuple together with the authority/server.  The
authority was added to be able to denote data that, for some reason,
is not linked into the global DNS.  The reason could be multiple
roots, split-view DNS, disconnected operation, efficiency or whatnot.

I could remove the hostport element if the consensus is that doing so
would improve the usefulness of the URI.  Anyone else with an opinion?
Remove hostport or keep it?

Thanks,
Simon




From owner-ietf@ietf.org  Mon Jun 30 22:05:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26239
	for <ietf-web-archive@odin.ietf.org>; Mon, 30 Jun 2003 22:05:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19XARs-0002p0-A9
	for ietf-list@asgard.ietf.org; Mon, 30 Jun 2003 22:00:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19XAPs-0002iE-PI
	for ietf@asgard.ietf.org; Mon, 30 Jun 2003 21:58:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26040
	for <ietf@ietf.org>; Mon, 30 Jun 2003 21:58:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19XAPq-00064k-00
	for ietf@ietf.org; Mon, 30 Jun 2003 21:58:43 -0400
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19XAPg-00064h-00
	for ietf@ietf.org; Mon, 30 Jun 2003 21:58:32 -0400
Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.12.9/8.12.9) with ESMTP id h611wNG9028646
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK);
	Tue, 1 Jul 2003 03:58:23 +0200
To: Zefram <zefram@fysh.org>
Cc: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
References: <iluel1fkrdb.fsf@latte.josefsson.org>
	<20030628004726.4EDE2230012@fh.vix.com>
	<20030630161659.GB9368@fysh.org>
From: Simon Josefsson <jas@extundo.com>
X-Payment: hashcash 1.2 0:030701:zefram@fysh.org:52da38a2cf752a25
X-Hashcash: 0:030701:zefram@fysh.org:52da38a2cf752a25
X-Payment: hashcash 1.2 0:030701:ietf@ietf.org:42365fe5490687ba
X-Hashcash: 0:030701:ietf@ietf.org:42365fe5490687ba
Date: Tue, 01 Jul 2003 03:58:23 +0200
In-Reply-To: <20030630161659.GB9368@fysh.org> (zefram@fysh.org's message of
 "Mon, 30 Jun 2003 17:17:00 +0100")
Message-ID: <iluk7b3gg8w.fsf@latte.josefsson.org>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=-32.4 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT_GNUS_UA
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-ietf@ietf.org
Precedence: bulk

Zefram <zefram@fysh.org> writes:

> This touches on an issue that I've been wondering about.  I'm not entirely
> clear on what the <dnsqueryelement> extension mechanism is for.  What kind
> of information might it represent?  If the URI scheme is intended purely
> to represent a <name,type,class> tuple then there is no possible use for
> the extension mechanism -- no additional information that one would ever
> want to add to the tuple.  In considering reasonable usage scenarios I
> came up with only one additional element that one might want to use: a
> flag meaning "insist on the data being cryptographically authenticated".

The intention was to make sure future extensions aren't disallowed by
the syntax.  It could be used to indicate, e.g., that the RD flag
should be set or cleared, if someone do find it useful in the future,
and document it, and there is consensus for it.

> Yet another protocol matter that hasn't been addressed so far: how are
> domain name labels other than character labels (e.g., binary labels)
> to be represented in the URI syntax?  Most applications that need to
> represent these kinds of labels in character strings use the master file
> format defined in the RFCs, but draft-josefsson-dns-url is quite clear
> that it doesn't use that syntax.  It offers no syntax for binary labels,
> and no extension mechanism for future label types.

Can you elaborate?  The intention is that, e.g., a binary label with
the ASCII value 0x17 is expressed as dns:%17.  There are some text and
examples for this.

Thanks,
Simon




