From owner-ietf@ietf.org  Thu Jan  1 02:19:06 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22439
	for <ietf-web-archive@odin.ietf.org>; Thu, 1 Jan 2004 02:19:06 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AbwvU-00052L-CQ
	for ietf-list@asgard.ietf.org; Thu, 01 Jan 2004 02:07:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AbwuV-0004Vu-Pd
	for ietf@asgard.ietf.org; Thu, 01 Jan 2004 02:06:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14733
	for <ietf@ietf.org>; Thu, 1 Jan 2004 02:06:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbwuM-0005XP-00
	for ietf@ietf.org; Thu, 01 Jan 2004 02:06:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Abwrj-0005Uv-00
	for ietf@ietf.org; Thu, 01 Jan 2004 02:03:34 -0500
Received: from [202.108.44.212] (helo=163.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1Abwo7-0005SB-00
	for ietf@ietf.org; Thu, 01 Jan 2004 01:59:47 -0500
Received: from wl302 (unknown [211.67.24.168])
	by 192.168.1.212 (Coremail) with SMTP id +mcFAFPF8z82ABio.1
	for <iljitsch@muada.com>; Thu, 01 Jan 2004 14:59:41 +0800 (CST)
X-Originating-IP: [211.67.24.168]
Message-ID: <003901c3d035$0a1aabb0$a81843d3@wl302>
From: "wang liang" <wangliang_f@163.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
Cc: <ietf@ietf.org>
References: <002e01c3cc32$0463db30$a81843d3@wl302> <3FF1C43A.8040606@iconoplex.co.uk> <002001c3cf85$da167250$a81843d3@wl302> <274ED83C-3B81-11D8-B8F6-000A95CD987A@muada.com>
Subject: Re: Propose some information retrieval protocols for Internet
Date: Thu, 1 Jan 2004 15:01:01 +0800
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

For some reason, the IP in CERNET isn't accessible outside China.
I will solve this problem as soon as possible.


> but I'm more interested in something else: I'd like to see more semantic
> information in search engines. Eventually, this would allow queries
> like "which actors played in movies after books written by authors born
> in Chili in 1961?"


DRIS will give a promising solution for this demand. Only as a web pages
search system, DRIS will download and index all the web pages in three
levels domain and provide standard search interface in every node. The data
format for input and output of this interface is standard XML but not HTML.
DRIS is not a final search engine, but provide the data source for other
personal intelligent system, which is designed by your interest and
knowledge background. XML may be the best data format for most application
system. You can consider DRIS is a mechanism that arranges all HTML source
to XML source.

Certainly, the XML data in DIRS can comply with the W3C's seven
levels'semantic module, which will give great help to design the intelligent
search systems. But now, there still no a system that can understand you
query "which actors played in movies after books written by authors born in
Chili in 1961?" very well and give you a precise answer.

So DRIS just builds the information retrieval infrastructure for Internet,
other work will be left to AI experts.





From owner-ietf@ietf.org  Thu Jan  1 03:02:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24110
	for <ietf-web-archive@odin.ietf.org>; Thu, 1 Jan 2004 03:02:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Abxgu-0001lj-0U
	for ietf-list@asgard.ietf.org; Thu, 01 Jan 2004 02:56:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AbxgR-0001kc-OY
	for ietf@asgard.ietf.org; Thu, 01 Jan 2004 02:55:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23994
	for <ietf@ietf.org>; Thu, 1 Jan 2004 02:55:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbxgN-0006uN-00
	for ietf@ietf.org; Thu, 01 Jan 2004 02:55:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbxfG-0006rW-00
	for ietf@ietf.org; Thu, 01 Jan 2004 02:54:45 -0500
Received: from [202.108.44.212] (helo=163.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1Abxdf-0006o8-00
	for ietf@ietf.org; Thu, 01 Jan 2004 02:53:03 -0500
Received: from wl302 (unknown [211.67.24.168])
	by 192.168.1.212 (Coremail) with SMTP id Cm0FAM3R8z8OABio.1
	for <stephen@sprunk.org>; Thu, 01 Jan 2004 15:52:58 +0800 (CST)
X-Originating-IP: [211.67.24.168]
Message-ID: <006001c3d03c$7be869b0$a81843d3@wl302>
From: "wang liang" <wangliang_f@163.com>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: <ietf@ietf.org>
References: <003701c3cb5e$ce697d10$a81843d3@wl302> <042701c3cf97$21f82df0$6401a8c0@ssprunk>
Subject: Re: Propose some information retrieval protocols for Internet
Date: Thu, 1 Jan 2004 15:54:16 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
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: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id CAA23996
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Your original post presents several arguments against the current crop =
of
> search engines and proposes a new distributed search engine system, but
this
> is an _indexing_ function, not a _retrieval_ function.

DRIS's a real search engine.

  Although we say DRIS just builds the information retrieval infrastructu=
re
for Internet, it provides two kinds of search interface, user interface l=
ike
Google=92s service and API for other intelligent search system. Do you fe=
ll
very satisfied with the search results of current search engines? It's ju=
st
the crude results. So we say DRIS is information retrieval infrastructure.

> The architecture of DRIS is organization level-sub country Internet
> level-country level-whole Internet level.
> Can you demonstrate why country-level databases are a technical advanta=
ge,
> other than providing certain governments the ability to restrict the
> information their citizens can access?

In fact, if governments want to block out a web site, there are many othe=
r
efficient methods. They needn't restrict it in information retrieval stag=
e.
On the other hand,applying DRIS,every one will have his own search engine=
 ,
so some restriction could be set in children's search engine.





From owner-ietf@ietf.org  Thu Jan  1 13:56:43 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19104
	for <ietf-web-archive@odin.ietf.org>; Thu, 1 Jan 2004 13:56:43 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ac7fD-0000rJ-TM
	for ietf-list@asgard.ietf.org; Thu, 01 Jan 2004 13:35:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ac7eK-0000qd-MW
	for ietf@asgard.ietf.org; Thu, 01 Jan 2004 13:34:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18499
	for <ietf@ietf.org>; Thu, 1 Jan 2004 13:34:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ac7eJ-0000CG-00
	for ietf@ietf.org; Thu, 01 Jan 2004 13:34:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ac7bf-00003B-00
	for ietf@ietf.org; Thu, 01 Jan 2004 13:31:42 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ac7Zk-00001J-00
	for ietf@ietf.org; Thu, 01 Jan 2004 13:29:40 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i01ISeZN075915;
	Thu, 1 Jan 2004 19:28:41 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20031231164711.GU1928@sbrim-w2k01>
References: <002e01c3cc32$0463db30$a81843d3@wl302> <3FF1C43A.8040606@iconoplex.co.uk> <002001c3cf85$da167250$a81843d3@wl302> <274ED83C-3B81-11D8-B8F6-000A95CD987A@muada.com> <20031231164711.GU1928@sbrim-w2k01>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5519BDAE-3C88-11D8-860B-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Propose some information retrieval protocols for Internet
Date: Thu, 1 Jan 2004 19:28:44 +0100
To: Scott W Brim <swb@employees.org>
X-Mailer: Apple Mail (2.609)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 31-dec-03, at 17:47, Scott W Brim wrote:

>> I'd like to see more semantic
>> information in search engines. Eventually, this would allow queries
>> like "which actors played in movies after books written by authors 
>> born
>> in Chili in 1961?"

> Is SCORM useful to you?  http://www.adlnet.org

As far as I can tell from the information presented at this location: 
not really, although there could be significant synergy. The difference 
is that computer aided learning is still based on content developed by 
humans, while intelligent searching should be handled completely 
automatically to be useful. On the other hand, the content to be 
searched must be tagged appropriately first so the search engines know 
whether "bgp" means "border gateway protocol" or "borders group inc" so 
maybe the difference isn't all that huge.

I don't think AI is the (full) solution here, as some ambiguities are 
simply not resolvable from the source information, even by reasonably 
informed humans. For instance, there are seven people with the name 
"robert rodriguez" in the movie industry alone.




From owner-ietf@ietf.org  Thu Jan  1 17:26:43 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24169
	for <ietf-web-archive@odin.ietf.org>; Thu, 1 Jan 2004 17:26:43 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcB75-0003nA-BJ
	for ietf-list@asgard.ietf.org; Thu, 01 Jan 2004 17:16:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcB6u-0003mU-QE
	for ietf@asgard.ietf.org; Thu, 01 Jan 2004 17:16:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23875
	for <ietf@ietf.org>; Thu, 1 Jan 2004 17:16:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcB6t-0006oh-00
	for ietf@ietf.org; Thu, 01 Jan 2004 17:16:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcB4n-0006jY-00
	for ietf@ietf.org; Thu, 01 Jan 2004 17:14:00 -0500
Received: from kc-msxproto3.kc.umkc.edu ([134.193.143.160])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcB2z-0006gF-00
	for ietf@ietf.org; Thu, 01 Jan 2004 17:12:05 -0500
Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211] RDNS failed) by kc-msxproto3.kc.umkc.edu with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 1 Jan 2004 16:12:05 -0600
x-mimeole: Produced By Microsoft Exchange V6.5.6944.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: Propose some information retrieval protocols for Internet
Date: Thu, 1 Jan 2004 16:12:05 -0600
Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B01108205@KC-MAIL4.kc.umkc.edu>
Thread-Topic: Propose some information retrieval protocols for Internet
Thread-Index: AcPQtEn8jhPqyj8tS5aLkGji7JyyKg==
From: "Ayyasamy, Senthilkumar  \(UMKC-Student\)" <saq66@umkc.edu>
To: <ietf@ietf.org>
Cc: <iljitsch@muada.com>, <swb@employees.org>
X-OriginalArrivalTime: 01 Jan 2004 22:12:05.0725 (UTC) FILETIME=[4A63C8D0:01C3D0B4]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> As far as I can tell from the information presented at this location: =
not
> really, although there could be significant synergy. The difference is =

> that computer aided learning is still based on content developed by =
humans,
> while intelligent searching should be handled completely automatically =
to=20
> be useful.=20
=20
I don't think it is possible to architect a semantic search engine(to =
resolve=20
complex queries you mentioned before) without human-in-loop content mark =
up.=20
For example, Sir Timbl's vision( semantic web) can be used for doing =
semantic=20
based keyword match-making. But, it requires us to mark-up in a =
AI-tinted=20
language like RDF. It is hard to come up with a pure algorithmic =
solution=20
(like page ranking) for semantic search/query.=20
=20
> On the other hand, the content to be searched must be tagged =
appropriately=20
> first so the search engines know whether "bgp" means "border  gateway=20
> protocol" or "borders group inc" so maybe the difference isn't all  =
that=20
> huge.
=20
yes. This kind of *intelligent* metadata tagging can be done using RDF.=20
But, who is going to semantically annotate the bulk of existing html =
data=20
pool? =20

> I don't think AI is the (full) solution here, as some ambiguities are=20
> simply not resolvable from the source information, even by reasonably=20
> informed humans. For instance, there are seven people with the name=20
> "robert rodriguez" in the movie industry alone.
=20
Any kind of metadata based solution can resolve this context ambiguity.=20
Digital library folks have been doing this for years.
=20
 or how about
=20
http://www.irtf.org/siren/draft-klensin-dns-search-05.txt ?



From owner-ietf@ietf.org  Fri Jan  2 00:52:17 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04164
	for <ietf-web-archive@odin.ietf.org>; Fri, 2 Jan 2004 00:52:16 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcI2i-00079z-PC
	for ietf-list@asgard.ietf.org; Fri, 02 Jan 2004 00:40:16 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcI2K-00079N-B2
	for ietf@asgard.ietf.org; Fri, 02 Jan 2004 00:39:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03999
	for <ietf@ietf.org>; Fri, 2 Jan 2004 00:39:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcI2H-0003PR-00
	for ietf@ietf.org; Fri, 02 Jan 2004 00:39:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcI0P-0003Lb-00
	for ietf@ietf.org; Fri, 02 Jan 2004 00:37:56 -0500
Received: from [202.108.44.206] (helo=163.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AcHya-0003HP-00
	for ietf@ietf.org; Fri, 02 Jan 2004 00:36:00 -0500
Received: from wl302 (unknown [211.67.24.168])
	by 192.168.1.206 (Coremail) with SMTP id sHwGAP0C9T8zABio.1
	for <saq66@umkc.edu>; Fri, 02 Jan 2004 13:35:04 +0800 (CST)
X-Originating-IP: [211.67.24.168]
Message-ID: <001401c3d0f2$624814e0$a81843d3@wl302>
From: "wang liang" <wangliang_f@163.com>
To: "Ayyasamy, Senthilkumar  \(UMKC-Student\)" <saq66@umkc.edu>,
        <ietf@ietf.org>
Cc: <iljitsch@muada.com>, <swb@employees.org>
References: <5EF7D95E17BDAD4A968C812E5ABC390B01108205@KC-MAIL4.kc.umkc.edu>
Subject: Re: Propose some information retrieval protocols for Internet
Date: Fri, 2 Jan 2004 13:36:23 +0800
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

In fact, our project is just a digital library project. DRIS is its main
part. Another part is Mylibrary@HUST, a intellitent search system, which
will directly answer all your question in the future. But now it can only
answer some questions about routine of libray. Such system is also called
virtual consulting system, which is a traditional research subject in
digital library. There has been some excellent systems in some libraries.

But the main disadvantage of these systems lie that its knowledge database
is too small and can only answer few questions. Internet may be the biggest
knowledge database, so we proposed the DRIS, which will act as the knowledge
source of such personal intelligent systems.

At all, we need an answer, but not piles of jumbled hyperlinks.




>Any kind of metadata based solution can resolve this context ambiguity.
>Digital library folks have been doing this for years.

> or how about

>http://www.irtf.org/siren/draft-klensin-dns-search-05.txt ?






From owner-ietf@ietf.org  Fri Jan  2 01:13:09 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04677
	for <ietf-web-archive@odin.ietf.org>; Fri, 2 Jan 2004 01:13:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcISq-0007rq-IZ
	for ietf-list@asgard.ietf.org; Fri, 02 Jan 2004 01:07:16 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcISV-0007rD-Ok
	for ietf@asgard.ietf.org; Fri, 02 Jan 2004 01:06:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04545
	for <ietf@ietf.org>; Fri, 2 Jan 2004 01:06:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcISO-0004JX-00
	for ietf@ietf.org; Fri, 02 Jan 2004 01:06:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcIOU-0004FJ-00
	for ietf@ietf.org; Fri, 02 Jan 2004 01:02:49 -0500
Received: from kc-msxproto2.kc.umkc.edu ([134.193.143.155])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcILM-00048V-00
	for ietf@ietf.org; Fri, 02 Jan 2004 00:59:32 -0500
Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211]) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 1 Jan 2004 23:59:32 -0600
x-mimeole: Produced By Microsoft Exchange V6.5.6944.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: Propose some information retrieval protocols for Internet
Date: Thu, 1 Jan 2004 23:59:31 -0600
Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B01108206@KC-MAIL4.kc.umkc.edu>
Thread-Topic: Propose some information retrieval protocols for Internet
Thread-Index: AcPQ8lwIsZgHnhOYTh6i7JRlglcD5QAAMDJM
From: "Ayyasamy, Senthilkumar  \(UMKC-Student\)" <saq66@umkc.edu>
To: "wang liang" <wangliang_f@163.com>, <ietf@ietf.org>
Cc: <iljitsch@muada.com>, <swb@employees.org>
X-OriginalArrivalTime: 02 Jan 2004 05:59:32.0651 (UTC) FILETIME=[97A90FB0:01C3D0F5]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


> But the main disadvantage of these systems lie that its knowledge =
database
> is too small and can only answer few questions. Internet may be the =
biggest
> knowledge database, so we proposed the DRIS, which will act as the=20
> knowledge source of such personal intelligent systems.
=20
without looking into DRIS...
=20
Knowledge base for the whole Internet? The Internet based information=20
is so dynamic (see the use SRV and dynamic DNS.) IMO, the hierarchy and=20
zone delegation nature of DNS is a scalable one. It is hard to populate
the knowledge base for the whole Internet. I know Dave clark et all has
recently proposed a overlay knowledge plane architecture which use=20
sensors and actuators to feed knowledge (but, it is for network=20
management purpose.)

In any case, you should take this issue to the right forum. SIREN RG?=20
=20
> At all, we need an answer, but not piles of jumbled hyperlinks.
=20
you should provide us with a link(http://202.114.9.200/English/main.htm)
that works.=20



From owner-ietf@ietf.org  Fri Jan  2 07:33:42 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05324
	for <ietf-web-archive@odin.ietf.org>; Fri, 2 Jan 2004 07:33:42 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcOKf-0004PE-Rd
	for ietf-list@asgard.ietf.org; Fri, 02 Jan 2004 07:23:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcOJj-0004Nh-AW
	for ietf@asgard.ietf.org; Fri, 02 Jan 2004 07:22:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04375
	for <ietf@ietf.org>; Fri, 2 Jan 2004 07:22:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcOJi-0003DX-00
	for ietf@ietf.org; Fri, 02 Jan 2004 07:22:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcOGU-0002wY-00
	for ietf@ietf.org; Fri, 02 Jan 2004 07:18:57 -0500
Received: from mail.gmx.net ([213.165.64.20])
	by ietf-mx with smtp (Exim 4.12)
	id 1AcODj-0002bT-00
	for ietf@ietf.org; Fri, 02 Jan 2004 07:16:03 -0500
Received: (qmail 12819 invoked by uid 65534); 2 Jan 2004 12:14:56 -0000
Received: from p5082403A.dip0.t-ipconnect.de (EHLO gmx.de) (80.130.64.58)
  by mail.gmx.net (mp008) with SMTP; 02 Jan 2004 13:14:56 +0100
X-Authenticated: #1915285
Message-ID: <3FF560BE.8050503@gmx.de>
Date: Fri, 02 Jan 2004 13:14:54 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: rfc2223bis draft 07, "updates" clarification
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

Hi,

I'd like to see the concept of an RFC "updating" another RFC clarified. 
Currently the draft says:

          Updates

             Specifies an earlier document whose contents are modified or
             augmented by the new document.  The new document cannot be
             used alone, it can only be used in conjunction with the
             earlier document.

The second statement seems to be misleading. For instance, RFC2396 (URI 
syntax) updates previous RFCs that also contained specific URI scheme 
descriptions (such as "ftp"). Thus, it doesn't obsolete them. However, 
RFC2396 clearly can be used without the documents it's updating.

Regards, Julian





From owner-ietf@ietf.org  Fri Jan  2 10:07:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11483
	for <ietf-web-archive@odin.ietf.org>; Fri, 2 Jan 2004 10:07:29 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcQji-0002ww-2x
	for ietf-list@asgard.ietf.org; Fri, 02 Jan 2004 09:57:14 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcQiu-0002s8-Kz
	for ietf@asgard.ietf.org; Fri, 02 Jan 2004 09:56:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10890
	for <ietf@ietf.org>; Fri, 2 Jan 2004 09:56:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcQit-0004SW-00
	for ietf@ietf.org; Fri, 02 Jan 2004 09:56:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcQgs-0004PJ-00
	for ietf@ietf.org; Fri, 02 Jan 2004 09:54:21 -0500
Received: from [202.108.44.181] (helo=163.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AcQfl-0004MQ-00
	for ietf@ietf.org; Fri, 02 Jan 2004 09:53:09 -0500
Received: from wl302 (unknown [211.67.24.168])
	by 192.168.1.181 (Coremail) with SMTP id M9wEAMaF9T8QABio.1
	for <saq66@umkc.edu>; Fri, 02 Jan 2004 22:53:01 +0800 (CST)
X-Originating-IP: [211.67.24.168]
Message-ID: <002301c3d140$58375800$a81843d3@wl302>
From: "wang liang" <wangliang_f@163.com>
To: "Ayyasamy, Senthilkumar  \(UMKC-Student\)" <saq66@umkc.edu>
Cc: <ietf@ietf.org>
References: <5EF7D95E17BDAD4A968C812E5ABC390B01108206@KC-MAIL4.kc.umkc.edu>
Subject: Re: Propose some information retrieval protocols for Internet
Date: Fri, 2 Jan 2004 22:54:31 +0800
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


Please,please learn some basic knowledge about search engine.
Now we are discussing the search engine, one of most important services of
Internet.


Asking  for advices is first step, then a work group may be proposed.  So
don't  worry about where we discuss this issue.

>without looking into DRIS...

>Knowledge base for the whole Internet? The Internet based information
>is so dynamic (see the use SRV and dynamic DNS.) IMO, the hierarchy and
>zone delegation nature of DNS is a scalable one. It is hard to populate
>the knowledge base for the whole Internet. I know Dave clark et all has
>recently proposed a overlay knowledge plane architecture which use
>sensors and actuators to feed knowledge (but, it is for network
>management purpose.)

>In any case, you should take this issue to the right forum. SIREN RG?








From owner-ietf@ietf.org  Fri Jan  2 13:34:04 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17837
	for <ietf-web-archive@odin.ietf.org>; Fri, 2 Jan 2004 13:34:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcTxy-0007yd-W7
	for ietf-list@asgard.ietf.org; Fri, 02 Jan 2004 13:24:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcTw5-0007xl-Bz
	for ietf@asgard.ietf.org; Fri, 02 Jan 2004 13:22:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17429
	for <ietf@ietf.org>; Fri, 2 Jan 2004 13:21:54 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcTvk-0004NX-00
	for ietf@ietf.org; Fri, 02 Jan 2004 13:21:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcTs5-0004Im-00
	for ietf@ietf.org; Fri, 02 Jan 2004 13:18:08 -0500
Received: from h80ad254a.async.vt.edu ([128.173.37.74] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcTpm-0004Cz-00
	for ietf@ietf.org; Fri, 02 Jan 2004 13:15:42 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i02IF9tv010278;
	Fri, 2 Jan 2004 13:15:09 -0500
Message-Id: <200401021815.i02IF9tv010278@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Julian Reschke <julian.reschke@gmx.de>
Cc: ietf@ietf.org
Subject: Re: rfc2223bis draft 07, "updates" clarification 
In-Reply-To: Your message of "Fri, 02 Jan 2004 13:14:54 +0100."
             <3FF560BE.8050503@gmx.de> 
References: <3FF560BE.8050503@gmx.de>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_2072013460P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 02 Jan 2004 13:15:09 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Fri, 02 Jan 2004 13:14:54 +0100, Julian Reschke <julian.reschke@gmx.de>  said:

> The second statement seems to be misleading. For instance, RFC2396 (URI 
> syntax) updates previous RFCs that also contained specific URI scheme 
> descriptions (such as "ftp"). Thus, it doesn't obsolete them. However, 
> RFC2396 clearly can be used without the documents it's updating.

OK.  Maybe I'm just caffeine-deficient today, but I'm totally failing to
understand how you can use the parts of rfc2396 that update the rfc1808
definitions of relative URI's, if you're not using relative URI's as specified
by 1808.

Or is your comment addressing the fact that although some sections of 2396 are
dependent on 1808 and are left dangling if 1808 isn't included, that *other*
sections of 2396 are stand-alone and not dependent on it? (i.e. if your
situation doesn't use relative URI's, you can disregard both 1808 and the
update to it)?

If so, there's likely a little bit of confusion between what the standard
actually specifies (a large number of URI classes), and what any given
application may actually implement.  So while for you *as implementor* large
sections of 2396 may be irrelevant, in order to make the *standard* consistent,
it must be dependent on 1808 (otherwise, some *other* coder who *does* have to
worry about relative URI's will get burnt).

Does that clarify things any?

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

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

iD8DBQE/9bUtcC3lWbTT17ARAmN7AJ9RROul4VtVPNRTVfMM8RSvIZrlXgCg5BoV
T0FwyCMsG1oNpaX/hP+lVX8=
=SITO
-----END PGP SIGNATURE-----

--==_Exmh_2072013460P--



From owner-ietf@ietf.org  Fri Jan  2 13:54:50 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18580
	for <ietf-web-archive@odin.ietf.org>; Fri, 2 Jan 2004 13:54:50 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcUGN-0000Ch-0K
	for ietf-list@asgard.ietf.org; Fri, 02 Jan 2004 13:43:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcUFu-0000C2-0v
	for ietf@asgard.ietf.org; Fri, 02 Jan 2004 13:42:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18225
	for <ietf@ietf.org>; Fri, 2 Jan 2004 13:42:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcUFs-0005Np-00
	for ietf@ietf.org; Fri, 02 Jan 2004 13:42:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcUDy-0005Jo-00
	for ietf@ietf.org; Fri, 02 Jan 2004 13:40:45 -0500
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by ietf-mx with smtp (Exim 4.12)
	id 1AcUCr-0005BY-00
	for ietf@ietf.org; Fri, 02 Jan 2004 13:39:34 -0500
Received: (qmail 7967 invoked by uid 65534); 2 Jan 2004 18:38:57 -0000
Received: from p3EE2477A.dip.t-dialin.net (EHLO gmx.de) (62.226.71.122)
  by mail.gmx.net (mp027) with SMTP; 02 Jan 2004 19:38:57 +0100
X-Authenticated: #1915285
Message-ID: <3FF5BAAA.60102@gmx.de>
Date: Fri, 02 Jan 2004 19:38:34 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: ietf@ietf.org
Subject: Re: rfc2223bis draft 07, "updates" clarification
References: <3FF560BE.8050503@gmx.de> <200401021815.i02IF9tv010278@turing-police.cc.vt.edu>
In-Reply-To: <200401021815.i02IF9tv010278@turing-police.cc.vt.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

Valdis.Kletnieks@vt.edu wrote:

> On Fri, 02 Jan 2004 13:14:54 +0100, Julian Reschke <julian.reschke@gmx.de>  said:
> 
> 
>>The second statement seems to be misleading. For instance, RFC2396 (URI 
>>syntax) updates previous RFCs that also contained specific URI scheme 
>>descriptions (such as "ftp"). Thus, it doesn't obsolete them. However, 
>>RFC2396 clearly can be used without the documents it's updating.
> 
> 
> OK.  Maybe I'm just caffeine-deficient today, but I'm totally failing to
> understand how you can use the parts of rfc2396 that update the rfc1808
> definitions of relative URI's, if you're not using relative URI's as specified
> by 1808.

Relative URIs are fully specified by RFC2396, section 5.

> Or is your comment addressing the fact that although some sections of 2396 are
> dependent on 1808 and are left dangling if 1808 isn't included, that *other*
> sections of 2396 are stand-alone and not dependent on it? (i.e. if your
> situation doesn't use relative URI's, you can disregard both 1808 and the
> update to it)?

No, RFC2396 doesn't rely in any way on RFC1808.

> If so, there's likely a little bit of confusion between what the standard
> actually specifies (a large number of URI classes), and what any given
> application may actually implement.  So while for you *as implementor* large
> sections of 2396 may be irrelevant, in order to make the *standard* consistent,
> it must be dependent on 1808 (otherwise, some *other* coder who *does* have to
> worry about relative URI's will get burnt).
> 
> Does that clarify things any?

Not at all. IMHO the situation is as follows: RFC2396 completely 
replaces all previous definitions of URI syntax and resolution 
(including the syntax for relative URI references).

However, previous documents *also* contained definitions of particular 
schemes which were not included in RFC2396, thus it doesn't obsolete 
these documents. Nevertheless, RFC2396 can be read without reading the 
previous documents (unless you happen for instance to be interested in 
the "ftp" URI scheme).

Julian


-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760



From owner-ietf@ietf.org  Fri Jan  2 14:43:33 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20198
	for <ietf-web-archive@odin.ietf.org>; Fri, 2 Jan 2004 14:43:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcV3i-0001K7-Ls
	for ietf-list@asgard.ietf.org; Fri, 02 Jan 2004 14:34:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcV3Q-0001JT-V4
	for ietf@asgard.ietf.org; Fri, 02 Jan 2004 14:33:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19763
	for <ietf@ietf.org>; Fri, 2 Jan 2004 14:33:50 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcV3P-0007b9-00
	for ietf@ietf.org; Fri, 02 Jan 2004 14:33:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcV0s-0007SG-00
	for ietf@ietf.org; Fri, 02 Jan 2004 14:31:17 -0500
Received: from h80ad254a.async.vt.edu ([128.173.37.74] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcUzR-0007IP-00
	for ietf@ietf.org; Fri, 02 Jan 2004 14:29:46 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i02JTSjm011991;
	Fri, 2 Jan 2004 14:29:28 -0500
Message-Id: <200401021929.i02JTSjm011991@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Julian Reschke <julian.reschke@gmx.de>
Cc: ietf@ietf.org
Subject: Re: rfc2223bis draft 07, "updates" clarification 
In-Reply-To: Your message of "Fri, 02 Jan 2004 19:38:34 +0100."
             <3FF5BAAA.60102@gmx.de> 
References: <3FF560BE.8050503@gmx.de> <200401021815.i02IF9tv010278@turing-police.cc.vt.edu>
            <3FF5BAAA.60102@gmx.de>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-2027797380P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 02 Jan 2004 14:29:27 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Fri, 02 Jan 2004 19:38:34 +0100, Julian Reschke said:

> Not at all. IMHO the situation is as follows: RFC2396 completely 
> replaces all previous definitions of URI syntax and resolution 
> (including the syntax for relative URI references).
> 
> However, previous documents *also* contained definitions of particular 
> schemes which were not included in RFC2396, thus it doesn't obsolete 
> these documents. Nevertheless, RFC2396 can be read without reading the 
> previous documents (unless you happen for instance to be interested in 
> the "ftp" URI scheme).

OK.. I'm obviously caffeine-deficient today. ;)

I see what you mean now, I had it 100% backwards. ;)  And yes, there's a buglet
in the wording, but I'm not sure how to fix it for what is probably a special
case. I'm pretty sure that it's relatively rare for an updating RFC to do a
wholesale clean replacement of one section in such a way that the new RFC
updates the old but still stands on its own.  Much more common are the cases
like 3445 (updating 2535) or 3442 (updating 2132), where it *really* can't
stand on its own.

As far as I can tell, the text in 2223bis-07 is only inaccurate in the rare
case where the base document is an aggregation of several registration-type
definitions, as is the case for 1808 (or rfc2046 for MIME types), and the
proper classification for the base *would* have been 'obsoletes' if the one
section had been published on its own.  So for instance, RFC2112 was able to
obsolete 1872 (Multipart/Related), and was itself obsoleted by 2387 - but doing
the same for multipart/mixed isn't feasible without either:

a) Doing a full rev of 2046 that 'obsoletes 2046'.
b) Live with the fact that the 2223bis wording says that the new definition
depends on 2046 when it really doesn't.

Are there really enough documents like 1808 or 2046 for it to matter?

And if so, do you have any good verbiage to recommend that will in fact make
things cleared, rather than making it murkier due to special-casing?


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

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

iD8DBQE/9caXcC3lWbTT17ARAhuCAJ97YBuAMzVTMn3KpgRTboCLOQzjtgCcCdb3
pVePnVnSQkDK7Ddb6EqMg7M=
=1DPj
-----END PGP SIGNATURE-----

--==_Exmh_-2027797380P--



From owner-ietf@ietf.org  Fri Jan  2 14:47:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20312
	for <ietf-web-archive@odin.ietf.org>; Fri, 2 Jan 2004 14:47:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcVCQ-0001Ra-UP
	for ietf-list@asgard.ietf.org; Fri, 02 Jan 2004 14:43:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcVBo-0001Qm-M0
	for ietf@asgard.ietf.org; Fri, 02 Jan 2004 14:42:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20179
	for <ietf@ietf.org>; Fri, 2 Jan 2004 14:42:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcVBn-0000IX-00
	for ietf@ietf.org; Fri, 02 Jan 2004 14:42:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcVA9-0000EH-00
	for ietf@ietf.org; Fri, 02 Jan 2004 14:40:52 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcV98-00009k-00
	for ietf@ietf.org; Fri, 02 Jan 2004 14:39:46 -0500
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i02JdhZ14100;
	Fri, 2 Jan 2004 11:39:43 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.9.3/8.8.6) id LAA13713;
	Fri, 2 Jan 2004 11:39:43 -0800 (PST)
Date: Fri, 2 Jan 2004 11:39:43 -0800 (PST)
Message-Id: <200401021939.LAA13713@gra.isi.edu>
To: ietf@ietf.org, julian.reschke@gmx.de
Subject: Re: rfc2223bis draft 07, "updates" clarification
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


Julian,

Hi.  I believe that the problem your pointing out is real, common, and
not so easy to solve.

First, you might regard the given definition of Updates as a
"best-effort" definition, with all that "best-effort" implies.  ;-)  I
am sure that serious suggestions on a more precise definition would be
welcome, but it is unclear how much effort one ought to lavish on
word-smithing here.  The word "updates" in its common usage seems to
carry the desired meaning.

The RFC Editor and the IESG frequently struggle with the semantics
of the relationships among related RFCs.  It is clear that the categories
"Obsoletes" and "Updates" are only the high-order bits of often complex
relationships.  One could add "Partially Updates" and "Partially
Obsoletes" I suppose, but it is not clear where to stop or whether this
will really meet the need. We have recently been advocating the
creation of a series of area-specific "road-map" documents to
summarize these relationships; this would get around the limited
number of bits in the present categories.

Finally, we note that there is an alternative way to do business: the
IETF could shape its documents to fit the categories.  That is
essentially what more formal standards bodies do.  The IETF, for good
reason, chooses instead to let documents develop in the most expedient
fashion, and then notate them with (approximate) notations like
Obsoletes and Updates.

Bob Braden





  *> 
  *> Hi,
  *> 
  *> I'd like to see the concept of an RFC "updating" another RFC clarified. 
  *> Currently the draft says:
  *> 
  *>           Updates
  *> 
  *>              Specifies an earlier document whose contents are modified or
  *>              augmented by the new document.  The new document cannot be
  *>              used alone, it can only be used in conjunction with the
  *>              earlier document.
  *> 
  *> The second statement seems to be misleading. For instance, RFC2396 (URI 
  *> syntax) updates previous RFCs that also contained specific URI scheme 
  *> descriptions (such as "ftp"). Thus, it doesn't obsolete them. However, 
  *> RFC2396 clearly can be used without the documents it's updating.
  *> 
  *> Regards, Julian
  *> 
  *> 
  *> 



From owner-ietf@ietf.org  Fri Jan  2 14:53:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20829
	for <ietf-web-archive@odin.ietf.org>; Fri, 2 Jan 2004 14:53:13 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcVIE-0002cL-OM
	for ietf-list@asgard.ietf.org; Fri, 02 Jan 2004 14:49:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcVHm-0002au-6B
	for ietf@asgard.ietf.org; Fri, 02 Jan 2004 14:48:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20404
	for <ietf@ietf.org>; Fri, 2 Jan 2004 14:48:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcVHl-0000gD-00
	for ietf@ietf.org; Fri, 02 Jan 2004 14:48:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcVFf-0000Uy-00
	for ietf@ietf.org; Fri, 02 Jan 2004 14:46:34 -0500
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by ietf-mx with smtp (Exim 4.12)
	id 1AcVDg-0000KU-00
	for ietf@ietf.org; Fri, 02 Jan 2004 14:44:28 -0500
Received: (qmail 9123 invoked by uid 65534); 2 Jan 2004 19:43:51 -0000
Received: from p3EE2477A.dip.t-dialin.net (EHLO gmx.de) (62.226.71.122)
  by mail.gmx.net (mp005) with SMTP; 02 Jan 2004 20:43:51 +0100
X-Authenticated: #1915285
Message-ID: <3FF5C9DB.9090904@gmx.de>
Date: Fri, 02 Jan 2004 20:43:23 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: ietf@ietf.org
Subject: Re: rfc2223bis draft 07, "updates" clarification
References: <3FF560BE.8050503@gmx.de> <200401021815.i02IF9tv010278@turing-police.cc.vt.edu>            <3FF5BAAA.60102@gmx.de> <200401021929.i02JTSjm011991@turing-police.cc.vt.edu>
In-Reply-To: <200401021929.i02JTSjm011991@turing-police.cc.vt.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

Valdis.Kletnieks@vt.edu wrote:

> OK.. I'm obviously caffeine-deficient today. ;)
> 
> I see what you mean now, I had it 100% backwards. ;)  And yes, there's a buglet
> in the wording, but I'm not sure how to fix it for what is probably a special
> case. I'm pretty sure that it's relatively rare for an updating RFC to do a
> wholesale clean replacement of one section in such a way that the new RFC
> updates the old but still stands on its own.  Much more common are the cases
> like 3445 (updating 2535) or 3442 (updating 2132), where it *really* can't
> stand on its own.

Well, I was asking because we (the WebDAV working group) are just now 
discussing a similar issue. We've got a new spec (the BIND protocol) 
which updates parts of RFC2518 and RFC3253, and thus we'd like the RFC 
Index to have "forward references" from those to the new spec.

> As far as I can tell, the text in 2223bis-07 is only inaccurate in the rare
> case where the base document is an aggregation of several registration-type
> definitions, as is the case for 1808 (or rfc2046 for MIME types), and the
> proper classification for the base *would* have been 'obsoletes' if the one
> section had been published on its own.  So for instance, RFC2112 was able to
> obsolete 1872 (Multipart/Related), and was itself obsoleted by 2387 - but doing
> the same for multipart/mixed isn't feasible without either:
> 
> a) Doing a full rev of 2046 that 'obsoletes 2046'.
> b) Live with the fact that the 2223bis wording says that the new definition
> depends on 2046 when it really doesn't.
> 
> Are there really enough documents like 1808 or 2046 for it to matter?

I don't know. But as we have the very situation right now in the WebDAV 
working group, and the same things occured for RFC2396, I'd say yes. 
Basically it will always happen when a particular part of a spec is 
"factored out" into a separate spec (like specific URI scheme 
registrations in the old URL RFC, or the "binding" functionality in WebDAV).

> And if so, do you have any good verbiage to recommend that will in fact make
> things cleared, rather than making it murkier due to special-casing?

Good question. Looking at the current text:

          Updates

             Specifies an earlier document whose contents are modified or
             augmented by the new document.  The new document cannot be
             used alone, it can only be used in conjunction with the
             earlier document.

I'd say that just removing the second sentence should be fine. May just 
say...:

          Updates

             Specifies an earlier document whose content
             augmented by the new document.

Regards, Julian


-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760



From owner-ietf@ietf.org  Fri Jan  2 14:59:09 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21128
	for <ietf-web-archive@odin.ietf.org>; Fri, 2 Jan 2004 14:59:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcVO2-0003Am-Mr
	for ietf-list@asgard.ietf.org; Fri, 02 Jan 2004 14:55:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcVNG-000340-Bu
	for ietf@asgard.ietf.org; Fri, 02 Jan 2004 14:54:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20865
	for <ietf@ietf.org>; Fri, 2 Jan 2004 14:54:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcVNF-00017W-00
	for ietf@ietf.org; Fri, 02 Jan 2004 14:54:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcVLb-00010h-00
	for ietf@ietf.org; Fri, 02 Jan 2004 14:52:42 -0500
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by ietf-mx with smtp (Exim 4.12)
	id 1AcVJf-0000mz-00
	for ietf@ietf.org; Fri, 02 Jan 2004 14:50:39 -0500
Received: (qmail 8227 invoked by uid 65534); 2 Jan 2004 19:50:03 -0000
Received: from p3EE2477A.dip.t-dialin.net (EHLO gmx.de) (62.226.71.122)
  by mail.gmx.net (mp017) with SMTP; 02 Jan 2004 20:50:03 +0100
X-Authenticated: #1915285
Message-ID: <3FF5CB4F.7090609@gmx.de>
Date: Fri, 02 Jan 2004 20:49:35 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bob Braden <braden@ISI.EDU>
CC: ietf@ietf.org
Subject: Re: rfc2223bis draft 07, "updates" clarification
References: <200401021939.LAA13713@gra.isi.edu>
In-Reply-To: <200401021939.LAA13713@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:

> Julian,
> 
> Hi.  I believe that the problem your pointing out is real, common, and
> not so easy to solve.
> 
> First, you might regard the given definition of Updates as a
> "best-effort" definition, with all that "best-effort" implies.  ;-)  I
> am sure that serious suggestions on a more precise definition would be
> welcome, but it is unclear how much effort one ought to lavish on
> word-smithing here.  The word "updates" in its common usage seems to
> carry the desired meaning.
> 
> The RFC Editor and the IESG frequently struggle with the semantics
> of the relationships among related RFCs.  It is clear that the categories
> "Obsoletes" and "Updates" are only the high-order bits of often complex
> relationships.  One could add "Partially Updates" and "Partially
> Obsoletes" I suppose, but it is not clear where to stop or whether this
> will really meet the need. We have recently been advocating the
> creation of a series of area-specific "road-map" documents to
> summarize these relationships; this would get around the limited
> number of bits in the present categories.
> 
> Finally, we note that there is an alternative way to do business: the
> IETF could shape its documents to fit the categories.  That is
> essentially what more formal standards bodies do.  The IETF, for good
> reason, chooses instead to let documents develop in the most expedient
> fashion, and then notate them with (approximate) notations like
> Obsoletes and Updates.
> 
> Bob Braden

Bob,

thanks for the clarification. I think that "updates" and "obsoletes" is 
really sufficient (if there's more to say the new spec should clearly 
state that in the introduction anyway). The only issue seems to be that 
RFC2223bis is very restrictive in what "updates" is supposed to mean, 
both not matching what I happen to need :-), and what historically is't 
been used for. Looking at the original text in RFC2223:

    Updates

       To be used as a reference from a new item that cannot be used
       alone (i.e., one that supplements a previous document), to refer
       to the previous document.  The newer publication is a part that
       will supplement or be added on to the existing document; e.g., an
       addendum, or separate, extra information that is to be added to
       the original document.

This seems to be less restrictive and explicitly allows for instance 
what RFC2396 does (updating the definitions of URI syntax without 
updating the descriptions of particular URI schemes).

Regards, Julian


-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760



From owner-ietf@ietf.org  Fri Jan  2 15:29:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23166
	for <ietf-web-archive@odin.ietf.org>; Fri, 2 Jan 2004 15:29:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcVqB-0004lD-G7
	for ietf-list@asgard.ietf.org; Fri, 02 Jan 2004 15:24:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcVpQ-0004kK-Cj
	for ietf@asgard.ietf.org; Fri, 02 Jan 2004 15:23:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22923
	for <ietf@ietf.org>; Fri, 2 Jan 2004 15:23:26 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcVpK-0002R0-00
	for ietf@ietf.org; Fri, 02 Jan 2004 15:23:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcVjX-0002DQ-00
	for ietf@ietf.org; Fri, 02 Jan 2004 15:17:26 -0500
Received: from h80ad254a.async.vt.edu ([128.173.37.74] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcVel-0001z6-00
	for ietf@ietf.org; Fri, 02 Jan 2004 15:12:27 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i02KCA2G013087;
	Fri, 2 Jan 2004 15:12:10 -0500
Message-Id: <200401022012.i02KCA2G013087@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Julian Reschke <julian.reschke@gmx.de>
Cc: ietf@ietf.org
Subject: Re: rfc2223bis draft 07, "updates" clarification 
In-Reply-To: Your message of "Fri, 02 Jan 2004 20:43:23 +0100."
             <3FF5C9DB.9090904@gmx.de> 
References: <3FF560BE.8050503@gmx.de> <200401021815.i02IF9tv010278@turing-police.cc.vt.edu> <3FF5BAAA.60102@gmx.de> <200401021929.i02JTSjm011991@turing-police.cc.vt.edu>
            <3FF5C9DB.9090904@gmx.de>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1886224344P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 02 Jan 2004 15:12:10 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Fri, 02 Jan 2004 20:43:23 +0100, Julian Reschke said:

> Well, I was asking because we (the WebDAV working group) are just now 
> discussing a similar issue. We've got a new spec (the BIND protocol) 
> which updates parts of RFC2518 and RFC3253, and thus we'd like the RFC 
> Index to have "forward references" from those to the new spec.

The RFC Editor should update the rfc-index.txt entries for 2518 and 3253 with a
'(Updated by NNNN)' when your RFC comes out.  I don't think you need to do
anything other than make sure the Last Call says it's an update for 2518/3253/
whatever, the IESG and RFC Editor should make the right things happen after
that.

A quick reading of the 2518 and 3253 tables of contents doesn't seem to show
that this is likely to result in an 1808/2046 style punchout - for instance,
you almost certainly can't take section 11 (MERGE feature) out of 3253 and replace
it with something totally stand-alone (for starters, section 11.1 says:

11.1 Additional Checked-Out Resource Properties

   The merge feature introduces the following REQUIRED properties for a
   checked-out resource.

which means you need section 4.2 (Checked-out Resource Properties) (plus any
other implicit references) for it to make sense.

> Basically it will always happen when a particular part of a spec is 
> "factored out" into a separate spec (like specific URI scheme 
> registrations in the old URL RFC, or the "binding" functionality in WebDAV).

Yes, the URI is a case of the 'collection of registrations'.  On the other hand,
rfc3253 has references to binding all over the place - it's totally unclear to me
that any RFC that factors the binding out will be any less dependent on 3253
than 3445 or 3442 were dependent on their base RFCs.

What section(s) of 2518/3253 were you planning to update in such a way that
the result would be standalone and not require 2518/3253 to make sense?

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

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

iD8DBQE/9dCacC3lWbTT17ARAo82AKD9f0w9DglI8j4NUuJGV4OKqP++0gCfeKZx
jVnZoTRtjpHt55mUdx8/W0s=
=Ifnd
-----END PGP SIGNATURE-----

--==_Exmh_-1886224344P--



From owner-ietf@ietf.org  Fri Jan  2 15:45:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24083
	for <ietf-web-archive@odin.ietf.org>; Fri, 2 Jan 2004 15:45:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcW3h-0005Os-LV
	for ietf-list@asgard.ietf.org; Fri, 02 Jan 2004 15:38:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcW3O-0005NA-0C
	for ietf@asgard.ietf.org; Fri, 02 Jan 2004 15:37:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23757
	for <ietf@ietf.org>; Fri, 2 Jan 2004 15:37:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcW3M-0003Xw-00
	for ietf@ietf.org; Fri, 02 Jan 2004 15:37:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcW18-0003M6-00
	for ietf@ietf.org; Fri, 02 Jan 2004 15:35:37 -0500
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by ietf-mx with smtp (Exim 4.12)
	id 1AcVyO-00033g-00
	for ietf@ietf.org; Fri, 02 Jan 2004 15:32:44 -0500
Received: (qmail 5040 invoked by uid 65534); 2 Jan 2004 20:32:06 -0000
Received: from p3EE2477A.dip.t-dialin.net (EHLO gmx.de) (62.226.71.122)
  by mail.gmx.net (mp017) with SMTP; 02 Jan 2004 21:32:06 +0100
X-Authenticated: #1915285
Message-ID: <3FF5D522.8070802@gmx.de>
Date: Fri, 02 Jan 2004 21:31:30 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: ietf@ietf.org
Subject: Re: rfc2223bis draft 07, "updates" clarification
References: <3FF560BE.8050503@gmx.de> <200401021815.i02IF9tv010278@turing-police.cc.vt.edu> <3FF5BAAA.60102@gmx.de> <200401021929.i02JTSjm011991@turing-police.cc.vt.edu>            <3FF5C9DB.9090904@gmx.de> <200401022012.i02KCA2G013087@turing-police.cc.vt.edu>
In-Reply-To: <200401022012.i02KCA2G013087@turing-police.cc.vt.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

Valdis.Kletnieks@vt.edu wrote:

> On Fri, 02 Jan 2004 20:43:23 +0100, Julian Reschke said:
> 
> 
>>Well, I was asking because we (the WebDAV working group) are just now 
>>discussing a similar issue. We've got a new spec (the BIND protocol) 
>>which updates parts of RFC2518 and RFC3253, and thus we'd like the RFC 
>>Index to have "forward references" from those to the new spec.
> 
> 
> The RFC Editor should update the rfc-index.txt entries for 2518 and 3253 with a
> '(Updated by NNNN)' when your RFC comes out.  I don't think you need to do
> anything other than make sure the Last Call says it's an update for 2518/3253/
> whatever, the IESG and RFC Editor should make the right things happen after
> that.

OK, so basically the new RFC should state "updates: 2518, 3253", just 
like I thought.

> A quick reading of the 2518 and 3253 tables of contents doesn't seem to show
> that this is likely to result in an 1808/2046 style punchout - for instance,
> you almost certainly can't take section 11 (MERGE feature) out of 3253 and replace
> it with something totally stand-alone (for starters, section 11.1 says:
> 
> 11.1 Additional Checked-Out Resource Properties
> 
>    The merge feature introduces the following REQUIRED properties for a
>    checked-out resource.
> 
> which means you need section 4.2 (Checked-out Resource Properties) (plus any
> other implicit references) for it to make sense.

Yes.

However, RFC3253 uses the term "binding", and in particular introduces 
operations that create additional bindings to the same resource.

On the other hand, RFC2518's description of the DELETE method is deeply 
incompatible to the concept of having multiple bindings (think POSIX 
hard links) to the same resource, because it states that if you remove 
any binding to the resource, all other bindings that refer to the same 
resource must be removed as well.

Thus, a new spec (BIND, 
http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-latest.html), 
updates both specs by finally saying what a binding is, how it behaves 
when existing HTTP methods are applied to it (such as MOVE or DELETE) 
and *in addition* defines specific methods/properties/status codes that 
help to deal with multiple bindings (such as determining that two 
bindings refer to the same resource, a method for explicitly creating 
new bindings, and status codes to be used for recursive operations when 
thy encounter bind loops).

>>Basically it will always happen when a particular part of a spec is 
>>"factored out" into a separate spec (like specific URI scheme 
>>registrations in the old URL RFC, or the "binding" functionality in WebDAV).
> 
> 
> Yes, the URI is a case of the 'collection of registrations'.  On the other hand,

Ah, now I understand the term. Thanks.

> rfc3253 has references to binding all over the place - it's totally unclear to me
> that any RFC that factors the binding out will be any less dependent on 3253
> than 3445 or 3442 were dependent on their base RFCs.

Right, and the case of factoring out isn't the one we were discussing 
here (RFC2518 vs RFC3253 bs BIND) - sorry for the confusion.

> What section(s) of 2518/3253 were you planning to update in such a way that
> the result would be standalone and not require 2518/3253 to make sense?

The BIND spec must be used in conjuction with RFC2518 (which is the base 
WebDAV spec), however it does not in any way rely on RFC3253. In this 
particular case, the relations were caused by the fact that the WebDAV 
working group split the base spec into WebDAV (RFC2518), Versioning 
(RFC3253) and several Advanced Collections specs (Redirects, Ordering, 
Bindings), and unfortunately, the latter are getting finished years 
later than they should have (basically, the BIND spec should have been 
in place when RFC3253 was finished).

Regards, Julian




-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760



From owner-ietf@ietf.org  Fri Jan  2 16:50:36 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25888
	for <ietf-web-archive@odin.ietf.org>; Fri, 2 Jan 2004 16:50:36 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AcX4Y-0000QV-AT
	for ietf-list@asgard.ietf.org; Fri, 02 Jan 2004 16:43:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AcX3b-0000PY-Mb
	for ietf@asgard.ietf.org; Fri, 02 Jan 2004 16:42:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25643
	for <ietf@ietf.org>; Fri, 2 Jan 2004 16:42:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcX3Z-0006LY-00
	for ietf@ietf.org; Fri, 02 Jan 2004 16:42:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AcX1l-0006G9-00
	for ietf@ietf.org; Fri, 02 Jan 2004 16:40:18 -0500
Received: from kahuna.telstra.net ([203.50.0.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AcWzw-00067E-00
	for ietf@ietf.org; Fri, 02 Jan 2004 16:38:24 -0500
Received: from r505gih.telstra.net (dhcp18.potaroo.net [203.10.60.18])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id i02LbquW072277
	for <ietf@ietf.org>; Sat, 3 Jan 2004 08:37:53 +1100 (EST)
	(envelope-from gih@telstra.net)
Message-Id: <6.0.1.1.2.20040103083419.01d8a140@kahuna.telstra.net>
X-Sender: gih@kahuna.telstra.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sat, 03 Jan 2004 08:37:41 +1100
To: ietf@ietf.org
From: Geoff Huston <gih@telstra.net>
Subject: Call for Nominations: IETF-Nominated ISOC Trustee
In-Reply-To: <3FF5D522.8070802@gmx.de>
References: <3FF560BE.8050503@gmx.de>
 <200401021815.i02IF9tv010278@turing-police.cc.vt.edu>
 <3FF5BAAA.60102@gmx.de>
 <200401021929.i02JTSjm011991@turing-police.cc.vt.edu>
 <3FF5C9DB.9090904@gmx.de>
 <200401022012.i02KCA2G013087@turing-police.cc.vt.edu>
 <3FF5D522.8070802@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

[A copy will be posted on the ietf-announce list sometime soon.]

The Internet Society (ISOC) provides organizational and financial
support for the IETF. As part of the arrangements between ISOC and the
IETF, the IETF is called upon to name 3 Trustees to its Board (BoT),
with staggered 3 year terms. This requires that the IETF select one
Trustee each year.

A description of the process for selecting the Trustee each year can
be found in RFC3677.

The timeline the IAB is using this year is as follows: 

  January 2:  Open nominations period 

  February 6: Close of nominations period.
              Publication of list of nominated candidates 
              IAB connences consideration of candidates
 
  On or before
  March 5:    IAB selection delivered to IESG for confirmation 

  On or before
  April 2:    Delivery of final confirmed selection to the ISOC 
              Elections Committee for announcement with the rest
              of the new ISOC BoT slate 


Nominations (including self-nominations) should be sent to the IAB --
iab@iab.org.

Nomination Details: 

  Nominees should be aware that ISOC Trustees are elected to three
  year terms with approximately one third of the Board of Trustees
  elected each year. The responsibilities of a Trustee include fiscal
  management of the Internet Society, fundraising, and participation
  in 2 to 3 Board meetings per year. The desirable characteristics of
  a candidate that are specific to the IETF's selected ISOC BoT member
  are outlined in section 2 of RFC 3677.

  Nominees will be asked to provide to the IAB: 

    1. Confirmation of their willingness to be considered within this
       process.

    2. Full name and contact information.

    3. A statement confirming willingness and ability to devote an
       appropriate level of time to activities associated with the
       position of Trustee.

    4. A brief biography outlining experience and background.

    5. A statement of interests, concerns about the Internet Society,
       goals as a Trustee and motivation to serve as a Trustee.

    6. Any further information that is relevant to the work of the IAB in
       considering your nomination.

    Care of Personal Information. 

    The following procedures will be used by the IAB in managing this
    process:

      - The candidate's name will be published, with all other
	candidate names, at the close of the nominations period

      - Excerpts of the information provided to the IAB by the
	nominated candidate will be passed to the IESG as part of the
	confirmation process. The IESG will be requested to maintain
	confidentiality of the candidate's information

      - Except as noted above, all information provided to the IAB
	during this process will be kept confidential to the IAB.

Current IETF-Nominated Trustees 

  The current IETF-Appointed ISOC Trustees and their term of
  appointment are:

    Eric Huizer  2002 - 2004 (*) 

    Fred Baker  2002 - 2005 

    Margaret Wasserman  2003 - 2006 

      (*) Current term expires May 2004 

Thanks,

   Geoff Huston
   Executive Director, IAB




From owner-ietf@ietf.org  Sat Jan  3 23:47:12 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24053
	for <ietf-web-archive@odin.ietf.org>; Sat, 3 Jan 2004 23:47:12 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aczsm-0002FT-VC
	for ietf-list@asgard.ietf.org; Sat, 03 Jan 2004 23:28:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aczsa-0002F6-6X
	for ietf@asgard.ietf.org; Sat, 03 Jan 2004 23:28:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23593
	for <ietf@ietf.org>; Sat, 3 Jan 2004 23:28:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AczsV-0002v7-00
	for ietf@ietf.org; Sat, 03 Jan 2004 23:28:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aczqc-0002qt-00
	for ietf@ietf.org; Sat, 03 Jan 2004 23:26:42 -0500
Received: from [202.108.44.206] (helo=163.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1Aczop-0002nk-00
	for ietf@ietf.org; Sat, 03 Jan 2004 23:24:51 -0500
Received: from wl302 (unknown [211.67.24.168])
	by 192.168.1.206 (Coremail) with SMTP id CzIHAHaV9z8uABio.1
	for <saq66@umkc.edu>; Sun, 04 Jan 2004 12:24:43 +0800 (CST)
X-Originating-IP: [211.67.24.168]
Message-ID: <001301c3d27a$e7159420$a81843d3@wl302>
From: "wang liang" <wangliang_f@163.com>
To: "Ayyasamy, Senthilkumar  \(UMKC-Student\)" <saq66@umkc.edu>,
        <ietf@ietf.org>
Cc: <iljitsch@muada.com>, <swb@employees.org>
References: <5EF7D95E17BDAD4A968C812E5ABC390B01108206@KC-MAIL4.kc.umkc.edu>
Subject: Re: Propose some information retrieval protocols for Internet
Date: Sun, 4 Jan 2004 12:25:58 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,NORMAL_HTTP_TO_IP 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


The link is moved to http://www.lib.hust.edu.cn/dl-lib/English/main.htm
More content will be translated.
 
>you should provide us with a link(http://202.114.9.200/English/main.htm)
>that works. 





From owner-ietf@ietf.org  Mon Jan  5 07:01:05 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14446
	for <ietf-web-archive@odin.ietf.org>; Mon, 5 Jan 2004 07:01:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AdT4L-0005Y9-Iw
	for ietf-list@asgard.ietf.org; Mon, 05 Jan 2004 06:38:49 -0500
Date: Sat, 03 Jan 2004 07:53:04 -0500
From: owner-ietf@ietf.org
To: ietf-approval@ietf.org
Subject: BOUNCE ietf@ietf.org:    Non-member submission from [mose
    <mose@mose.fr>]   
Sender: owner-ietf@ietf.org
Precedence: bulk
Message-Id: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>

>From owner-ietf@ietf.org Sat Jan 03 07:53:04 2004
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AclGa-000348-7i
	for ietf@asgard.ietf.org; Sat, 03 Jan 2004 07:52:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00689
	for <ietf@ietf.org>; Sat, 3 Jan 2004 07:52:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AclGW-00034q-00
	for ietf@ietf.org; Sat, 03 Jan 2004 07:52:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AclEg-00031b-00
	for ietf@ietf.org; Sat, 03 Jan 2004 07:50:35 -0500
Received: from smtp6.wanadoo.fr ([193.252.22.25] helo=mwinf0604.wanadoo.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AclDD-0002xP-00
	for ietf@ietf.org; Sat, 03 Jan 2004 07:49:03 -0500
Received: from liber.mose.fr (APh-Aug-108-1-4-148.w81-248.abo.wanadoo.fr [81.248.240.148])
	by mwinf0604.wanadoo.fr (SMTP Server) with ESMTP
	id DA72128000D7; Sat,  3 Jan 2004 13:48:31 +0100 (CET)
Received: by liber.mose.fr (Postfix, from userid 1000)
	id 9D8B230037; Sat,  3 Jan 2004 13:48:16 +0100 (CET)
Date: Sat, 3 Jan 2004 13:48:16 +0100
From: mose <mose@mose.fr>
To: Paul Robinson <paul@iconoplex.co.uk>
Cc: ietf@ietf.org, isdf@isoc.org
Subject: Re: [isdf] Re: www.internetforce.org
Message-ID: <20040103124816.GQ10070@mose.fr>
Mail-Followup-To: Paul Robinson <paul@iconoplex.co.uk>,
	ietf@ietf.org, isdf@isoc.org
References: <1072620368.2651.18.camel@franck-lxnb.sopac.org.fj> <3FF037F5.2060907@iconoplex.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3FF037F5.2060907@iconoplex.co.uk>
X-OS: Linux Debian
User-Agent: Mutt/1.5.4i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

le Mon, Dec 29, 2003 at 02:19:33PM +0000 par Paul Robinson :
> Franck Martin wrote:
> 
> >Who are we to recommend things as Mike Todd suggests?
> >
> End-users. We're end-users of the Internet. Everybody who uses it should 
> be entitled to join any body that determines it's future, and any body 
> that has influence that is free to join therefore has the right to 
> recommend actions for it's future. Think of it as an abstract form of 
> democracy. I live in the UK and Paliament has every right to pass laws 
> because I voted them into that position, and likewise if I want to 
> become a politician I can do so and pass my own laws... Same thing here, 
> except you actually need a clue to participate in IETF rather than just 
> look good kissing babies.


- I have to say something there. 

No internet user is an end-user very long. The broadcast era of massmedia 
is still in people habits but it's from the last century and there is no 
technical reason anymore to limit the decisionnal/informational processes 
to an elit of either good-looking babes either wise diplomed experts.

About politician, I don't vote them because they vote their own laws,
not mine. I don't understand how it would be a solution if I switch
and become politician to vote my own laws. Politics is very cool for
peace in material world because it's a convention to make everybody to 
say 'yes' before knowing what will be decided (notice that the 'no' 
alternative usually requires unusual creative abilities or direct 
exclusion, with various degrees of subtility in the way to exclude).

I think that online it's different. People decide by 'not saying no', as
it's rather pointless to say 'yes' when you are in a consensual situation 
with thousand, millions or more of people it would be very noisy. It's
working like that for more than 30 years now and I think we could learn
from it.

Every standard proposed can be of any quality, if nobody apply them
it's only intellectual research with no societal impact. I take as 
example the ipv6 implementation that we wonder "why we don't have it 
yet" for years, the story of the HTML specifications and the respect
of it.

In such context, a more participative behaviour should be welcome. Elits 
should help and educate rather than keeping the steering so firmly.
RFC aren't they meaning "Request For Comments" ? Why did I never find 
the button "add your comment", yet, on any of them ?


my $cents = 2;
mose






From owner-ietf@ietf.org  Mon Jan  5 07:33:09 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15895
	for <ietf-web-archive@odin.ietf.org>; Mon, 5 Jan 2004 07:33:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AdTpl-0006OF-RW
	for ietf-list@asgard.ietf.org; Mon, 05 Jan 2004 07:27:49 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AdTor-0006Nj-VX
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 07:26:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15223
	for <ietf@ietf.org>; Mon, 5 Jan 2004 07:26:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdTor-0007So-00
	for ietf@ietf.org; Mon, 05 Jan 2004 07:26:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdTlF-00070q-00
	for ietf@ietf.org; Mon, 05 Jan 2004 07:23:10 -0500
Received: from 3.cust16.nsw.dsl.ozemail.com.au ([203.102.111.3] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdTfV-0006hz-00
	for ietf@ietf.org; Mon, 05 Jan 2004 07:17:13 -0500
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 3996D3F02A; Mon,  5 Jan 2004 22:45:43 +1030 (CST)
Date: Mon, 5 Jan 2004 22:45:43 +1030
From: Mark Smith <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
To: mose@mose.fr
Cc: ietf@ietf.org, isdf@isoc.org
Subject: Re: [isdf] Re: www.internetforce.org
Message-Id: <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
In-Reply-To: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
Organization: The No Sense Organisation (http://www.nosense.org)
X-Mailer: Sylpheed version 0.9.8a (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Sat, 03 Jan 2004 07:53:04 -0500
> 
> In such context, a more participative behaviour should be
> welcome. Elits should help and educate rather than keeping the
> steering so firmly. RFC aren't they meaning "Request For
> Comments" ? Why did I never find the button "add your comment",
> yet, on any of them ?

Because that is not how they are updated.

The RFC faq would a place to seek your ansers.

http://www.rfc-editor.org/rfcfaq.html

Regards,
Mark.



From owner-ietf@ietf.org  Mon Jan  5 10:51:06 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21557
	for <ietf-web-archive@odin.ietf.org>; Mon, 5 Jan 2004 10:51:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AdWnd-0007AG-5X
	for ietf-list@asgard.ietf.org; Mon, 05 Jan 2004 10:37:49 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AdWn7-00079W-9n
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 10:37:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21308
	for <ietf@ietf.org>; Mon, 5 Jan 2004 10:37:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdWn6-000790-00
	for ietf@ietf.org; Mon, 05 Jan 2004 10:37:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdWlJ-00076q-00
	for ietf@ietf.org; Mon, 05 Jan 2004 10:35:25 -0500
Received: from 3.cust16.nsw.dsl.ozemail.com.au ([203.102.111.3] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdWkV-00073M-00
	for ietf@ietf.org; Mon, 05 Jan 2004 10:34:35 -0500
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id F01713F02A; Tue,  6 Jan 2004 02:03:28 +1030 (CST)
Date: Tue, 6 Jan 2004 02:03:28 +1030
From: Mark Smith <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
To: "Peter Hunter" <phunter@capecodhomefinder.com>
Cc: ietf@ietf.org
Subject: Re: hish email
Message-Id: <20040106020328.654b3643.ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
In-Reply-To: <000001c3d398$3aa9eb90$c801000a@station10>
References: <000001c3d398$3aa9eb90$c801000a@station10>
Organization: The No Sense Organisation (http://www.nosense.org)
X-Mailer: Sylpheed version 0.9.8a (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Mon, 5 Jan 2004 09:28:46 -0500
"Peter Hunter" <phunter@capecodhomefinder.com> wrote:

> Hi...
> 
>  
> 
> Congratulations on your perspicacity. I too was suspicious of
> this VISA email and immediately went phishing on Google until I
> saw your email. There must be thousands who were taken in by
> this despicable ruse.
> 
>

Thanks, although I had to look up "perspicacity" :-), which,
according to the Cambridge Advanced Learner's Dictionary, means 

"the ability to understand things quickly and make accurate
judgments"

Regards,
Mark.

  
> 
> Pete Hunter
> 
> 



From owner-ietf@ietf.org  Mon Jan  5 15:09:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00736
	for <ietf-web-archive@odin.ietf.org>; Mon, 5 Jan 2004 15:09:16 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AdarD-0004xc-To
	for ietf-list@asgard.ietf.org; Mon, 05 Jan 2004 14:57:47 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Adaqo-0004wx-WA
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 14:57:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00013
	for <ietf@ietf.org>; Mon, 5 Jan 2004 14:57:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adaqn-0002YA-00
	for ietf@ietf.org; Mon, 05 Jan 2004 14:57:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adaor-0002VG-00
	for ietf@ietf.org; Mon, 05 Jan 2004 14:55:21 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdanD-0002QF-00
	for ietf@ietf.org; Mon, 05 Jan 2004 14:53:39 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 05 Jan 2004 12:00:25 +0000
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 i05Jr3J8014407
	for <ietf@ietf.org>; Mon, 5 Jan 2004 11:53:05 -0800 (PST)
Received: from [10.32.245.157] (stealth-10-32-245-157.cisco.com [10.32.245.157])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id ALD98746;
	Mon, 5 Jan 2004 11:53:02 -0800 (PST)
Date: Mon, 05 Jan 2004 14:52:34 -0500
From: "David R. Oran" <oran@cisco.com>
To: ietf@ietf.org
Subject: Has anybody heard back from the Hotel in Seoul?
Message-ID: <2147483647.1073314354@[10.32.245.157]>
X-Mailer: Mulberry/3.1.0 (Mac OS X)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========5104458CFF8415D54F71=========="
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

I sent in my reservation request the day after registration opened and I=20
have heard nothing back at all.

Have others similarly gotten no response, or is it likely my room request=20
got dropped and I need to retransmit?

(Probably better to reply to me rather than the list unless people suspect=20
we have a generic problem).

Dave Oran

------------------------
David R. Oran
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720
Office: +1 978 264 2048
VoIP: +1 408 571 4576
Email: oran@cisco.com
--==========5104458CFF8415D54F71==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

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

iD8DBQE/+cCbjWaEtlTdKuYRAvUJAKC1m1qaTAgzBH9qPLbuq6p8X+gfFACeLq5X
IlU6E3Oz4L6iuaCzp/AewnM=
=CJxb
-----END PGP SIGNATURE-----

--==========5104458CFF8415D54F71==========--




From owner-ietf@ietf.org  Mon Jan  5 15:36:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02525
	for <ietf-web-archive@odin.ietf.org>; Mon, 5 Jan 2004 15:36:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AdbO7-0006Di-Jj
	for ietf-list@asgard.ietf.org; Mon, 05 Jan 2004 15:31:47 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AdbLJ-0006CH-TE
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 15:28:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01962
	for <ietf@ietf.org>; Mon, 5 Jan 2004 15:28:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdbL8-0003dD-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:28:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdbFe-0003NN-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:23:03 -0500
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adb9A-00035N-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:16:20 -0500
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id C1894BDD43; Mon,  5 Jan 2004 15:15:25 -0500 (EST)
To: ietf@ietf.org, oran@cisco.com
Subject: Re: Has anybody heard back from the Hotel in Seoul?
In-Reply-To: <2147483647.1073314354@[10.32.245.157]>
Message-Id: <20040105201525.C1894BDD43@newdev.harvard.edu>
Date: Mon,  5 Jan 2004 15:15:25 -0500 (EST)
From: sob@harvard.edu (Scott Bradner)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I have not heard

----
From owner-ietf@ietf.org  Mon Jan  5 15:14:02 2004
X-Original-To: sob@newdev.harvard.edu
Delivered-To: sob@newdev.harvard.edu
Date: Mon, 05 Jan 2004 14:52:34 -0500
From: "David R. Oran" <oran@cisco.com>
To: ietf@ietf.org
Subject: Has anybody heard back from the Hotel in Seoul?
X-Mailer: Mulberry/3.1.0 (Mac OS X)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========5104458CFF8415D54F71=========="
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

I sent in my reservation request the day after registration opened and I=20
have heard nothing back at all.

Have others similarly gotten no response, or is it likely my room request=20
got dropped and I need to retransmit?

(Probably better to reply to me rather than the list unless people suspect=20
we have a generic problem).

Dave Oran

------------------------
David R. Oran
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720
Office: +1 978 264 2048
VoIP: +1 408 571 4576
Email: oran@cisco.com
--==========5104458CFF8415D54F71==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

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

iD8DBQE/+cCbjWaEtlTdKuYRAvUJAKC1m1qaTAgzBH9qPLbuq6p8X+gfFACeLq5X
IlU6E3Oz4L6iuaCzp/AewnM=
=CJxb
-----END PGP SIGNATURE-----

--==========5104458CFF8415D54F71==========--





From owner-ietf@ietf.org  Mon Jan  5 15:47:57 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03170
	for <ietf-web-archive@odin.ietf.org>; Mon, 5 Jan 2004 15:47:57 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AdbZj-0006sp-Ew
	for ietf-list@asgard.ietf.org; Mon, 05 Jan 2004 15:43:47 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AdbZP-0006rt-Hx
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 15:43:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02983
	for <ietf@ietf.org>; Mon, 5 Jan 2004 15:43:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdbZO-0004fV-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:43:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdbXZ-0004ZZ-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:41:33 -0500
Received: from 216-43-25-66.ip.mcleodusa.net ([216.43.25.66] helo=episteme-software.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdbVw-0004O3-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:39:52 -0500
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server X 3.2.3b3);
 Mon, 5 Jan 2004 14:39:22 -0600
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p06100704bc1f7bb26a47@[216.43.25.67]>
In-Reply-To: <2147483647.1073314354@[10.32.245.157]>
References: <2147483647.1073314354@[10.32.245.157]>
X-Mailer: Eudora [Macintosh version 6.1a7]
Date: Mon, 5 Jan 2004 14:39:20 -0600
To: "David R. Oran" <oran@cisco.com>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Has anybody heard back from the Hotel in Seoul?
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=2.0 required=5.0 tests=AWL,FORGED_MUA_EUDORA 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On 1/5/04 at 2:52 PM -0500, David R. Oran wrote:

>Have others similarly gotten no response, or is it likely my room 
>request got dropped and I need to retransmit?

I got no response (other than an initial e-mail telling me I filled 
out part of the form incorrectly, which I answered by e-mail). After 
hearing nothing, I called them and got a confirmation number. Perhaps 
it is a NACK rather than an ACK protocol?

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102



From owner-ietf@ietf.org  Mon Jan  5 15:48:36 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03249
	for <ietf-web-archive@odin.ietf.org>; Mon, 5 Jan 2004 15:48:36 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Adbbf-0007Jo-Px
	for ietf-list@asgard.ietf.org; Mon, 05 Jan 2004 15:45:47 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AdbbL-0007DR-OB
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 15:45:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03079
	for <ietf@ietf.org>; Mon, 5 Jan 2004 15:45:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdbbK-0004kk-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:45:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdbZV-0004gk-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:43:34 -0500
Received: from mail4.dynamicsoft.com ([63.110.3.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdbYa-0004cm-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:42:36 -0500
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id i05KfeMZ010590;
	Mon, 5 Jan 2004 14:41:40 -0600 (CST)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <YBTH6HTH>; Mon, 5 Jan 2004 14:41:40 -0600
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3E86738@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'sob@harvard.edu'" <sob@harvard.edu>, ietf@ietf.org, oran@cisco.com
Subject: RE: Has anybody heard back from the Hotel in Seoul?
Date: Mon, 5 Jan 2004 14:41:40 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I sent in an e-mail the day of, and haven't heard back, either.
This sounds like a systemic problem.

/a

> -----Original Message-----
> From: sob@harvard.edu [mailto:sob@harvard.edu]
> Sent: Monday, January 05, 2004 14:15
> To: ietf@ietf.org; oran@cisco.com
> Subject: Re: Has anybody heard back from the Hotel in Seoul?
> 
> 
> I have not heard
> 
> ----
> From owner-ietf@ietf.org  Mon Jan  5 15:14:02 2004
> X-Original-To: sob@newdev.harvard.edu
> Delivered-To: sob@newdev.harvard.edu
> Date: Mon, 05 Jan 2004 14:52:34 -0500
> From: "David R. Oran" <oran@cisco.com>
> To: ietf@ietf.org
> Subject: Has anybody heard back from the Hotel in Seoul?
> X-Mailer: Mulberry/3.1.0 (Mac OS X)
> MIME-Version: 1.0
> Content-Type: multipart/signed; micalg=pgp-sha1;
>  protocol="application/pgp-signature";
>  boundary="==========5104458CFF8415D54F71=========="
> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
> 	ietf-mx.ietf.org
> X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL 
> autolearn=no version=2.60
> Sender: owner-ietf@ietf.org
> Precedence: bulk
> 
> --==========5104458CFF8415D54F71==========
> Content-Type: text/plain; charset=us-ascii; format=flowed
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> I sent in my reservation request the day after registration 
> opened and I=20
> have heard nothing back at all.
> 
> Have others similarly gotten no response, or is it likely my 
> room request=20
> got dropped and I need to retransmit?
> 
> (Probably better to reply to me rather than the list unless 
> people suspect=20
> we have a generic problem).
> 
> Dave Oran
> 
> ------------------------
> David R. Oran
> Cisco Systems
> 7 Ladyslipper Lane
> Acton, MA 01720
> Office: +1 978 264 2048
> VoIP: +1 408 571 4576
> Email: oran@cisco.com
> --==========5104458CFF8415D54F71==========
> Content-Type: application/pgp-signature
> Content-Transfer-Encoding: 7bit
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (Darwin)
> 
> iD8DBQE/+cCbjWaEtlTdKuYRAvUJAKC1m1qaTAgzBH9qPLbuq6p8X+gfFACeLq5X
> IlU6E3Oz4L6iuaCzp/AewnM=
> =CJxb
> -----END PGP SIGNATURE-----
> 
> --==========5104458CFF8415D54F71==========--
> 
> 
> 



From owner-ietf@ietf.org  Mon Jan  5 16:07:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04237
	for <ietf-web-archive@odin.ietf.org>; Mon, 5 Jan 2004 16:07:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AdbpE-0000fr-1q
	for ietf-list@asgard.ietf.org; Mon, 05 Jan 2004 15:59:48 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Adbom-0000f5-Bo
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 15:59:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04120
	for <ietf@ietf.org>; Mon, 5 Jan 2004 15:59:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adbol-0005rq-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:59:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adbmv-0005pj-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:57:25 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdbmF-0005nD-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:56:43 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-2.cisco.com with ESMTP; 05 Jan 2004 13:03:09 +0000
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 i05KuBVM015282;
	Mon, 5 Jan 2004 12:56:11 -0800 (PST)
Received: from cisco.com ([10.25.65.180])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id APP02859;
	Mon, 5 Jan 2004 12:56:09 -0800 (PST)
Date: Mon, 5 Jan 2004 15:56:03 -0500
Subject: Re: Has anybody heard back from the Hotel in Seoul?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: ietf@ietf.org
To: Adam Roach <adam@dynamicsoft.com>
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <9BF66EBF6BEFD942915B4D4D45C051F3E86738@dyn-tx-exch-001.dynamicsoft.com>
Message-Id: <931B65F5-3FC1-11D8-AFFF-000A95E35274@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Monday, January 5, 2004, at 03:41 PM, Adam Roach wrote:
> I sent in an e-mail the day of, and haven't heard back, either.
> This sounds like a systemic problem.

I faxed my reservation request in the day after and received a 
confirmation
via email on the 26th.  Perhaps they've acked faxed requests and not 
email
requests or there's some other pattern.

Melinda




From owner-ietf@ietf.org  Mon Jan  5 16:14:06 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04426
	for <ietf-web-archive@odin.ietf.org>; Mon, 5 Jan 2004 16:14:06 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Adbxw-00015y-3V
	for ietf-list@asgard.ietf.org; Mon, 05 Jan 2004 16:08:48 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AdbvM-0000lE-GM
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 16:06:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04222
	for <ietf@ietf.org>; Mon, 5 Jan 2004 16:06:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdbvG-0005zR-00
	for ietf@ietf.org; Mon, 05 Jan 2004 16:06:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adbsv-0005wQ-00
	for ietf@ietf.org; Mon, 05 Jan 2004 16:03:38 -0500
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adbr3-0005sx-00
	for ietf@ietf.org; Mon, 05 Jan 2004 16:01:41 -0500
Received: from [63.202.92.157] (adsl-63-202-92-157.dsl.snfc21.pacbell.net [63.202.92.157])
	(authenticated bits=0)
	by above.proper.com (8.12.10/8.12.8) with ESMTP id i05L1Dic014855
	for <ietf@ietf.org>; Mon, 5 Jan 2004 13:01:14 -0800 (PST)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p06020443bc1f8180bbca@[63.202.92.157]>
In-Reply-To: <p06100704bc1f7bb26a47@[216.43.25.67]>
References: <2147483647.1073314354@[10.32.245.157]>
 <p06100704bc1f7bb26a47@[216.43.25.67]>
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, 5 Jan 2004 13:04:11 -0800
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: Has anybody heard back from the Hotel in Seoul?
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-8.0 required=5.0 tests=HABEAS_SWE autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 2:39 PM -0600 1/5/04, Pete Resnick wrote:
>I got no response (other than an initial e-mail telling me I filled 
>out part of the form incorrectly, which I answered by e-mail). After 
>hearing nothing, I called them and got a confirmation number. 
>Perhaps it is a NACK rather than an ACK protocol?

Not to worry everyone, but I got an ACK via FAX a few days after I 
faxed them my reservation.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Mon Jan  5 16:39:52 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05801
	for <ietf-web-archive@odin.ietf.org>; Mon, 5 Jan 2004 16:39:52 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AdcKD-0002PL-6t
	for ietf-list@asgard.ietf.org; Mon, 05 Jan 2004 16:31:49 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AdcJv-0002NG-VY
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 16:31:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05157
	for <ietf@ietf.org>; Mon, 5 Jan 2004 16:31:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdcJu-00078x-00
	for ietf@ietf.org; Mon, 05 Jan 2004 16:31:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdcDt-0006si-00
	for ietf@ietf.org; Mon, 05 Jan 2004 16:25:17 -0500
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adc9w-0006Xl-00
	for ietf@ietf.org; Mon, 05 Jan 2004 16:21:13 -0500
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 0C376BDEFB; Mon,  5 Jan 2004 16:20:18 -0500 (EST)
To: adam@dynamicsoft.com, mshore@cisco.com
Subject: Re: Has anybody heard back from the Hotel in Seoul?
Cc: ietf@ietf.org
In-Reply-To: <931B65F5-3FC1-11D8-AFFF-000A95E35274@cisco.com>
Message-Id: <20040105212018.0C376BDEFB@newdev.harvard.edu>
Date: Mon,  5 Jan 2004 16:20:18 -0500 (EST)
From: sob@harvard.edu (Scott Bradner)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

my request was a faxed on and I have not heard back

---
From owner-ietf@ietf.org  Mon Jan  5 16:08:50 2004
X-Original-To: sob@newdev.harvard.edu
Delivered-To: sob@newdev.harvard.edu
Date: Mon, 5 Jan 2004 15:56:03 -0500
Subject: Re: Has anybody heard back from the Hotel in Seoul?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: ietf@ietf.org
To: Adam Roach <adam@dynamicsoft.com>
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <9BF66EBF6BEFD942915B4D4D45C051F3E86738@dyn-tx-exch-001.dynamicsoft.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk

On Monday, January 5, 2004, at 03:41 PM, Adam Roach wrote:
> I sent in an e-mail the day of, and haven't heard back, either.
> This sounds like a systemic problem.

I faxed my reservation request in the day after and received a 
confirmation
via email on the 26th.  Perhaps they've acked faxed requests and not 
email
requests or there's some other pattern.

Melinda





From owner-ietf@ietf.org  Mon Jan  5 16:39:53 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05807
	for <ietf-web-archive@odin.ietf.org>; Mon, 5 Jan 2004 16:39:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AdcKE-0002PX-17
	for ietf-list@asgard.ietf.org; Mon, 05 Jan 2004 16:31:50 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AdcJx-0002NK-SA
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 16:31:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05166
	for <ietf@ietf.org>; Mon, 5 Jan 2004 16:31:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdcJw-00079c-00
	for ietf@ietf.org; Mon, 05 Jan 2004 16:31:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdcDz-0006tR-00
	for ietf@ietf.org; Mon, 05 Jan 2004 16:25:23 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdcAs-0006aG-00
	for ietf@ietf.org; Mon, 05 Jan 2004 16:22:10 -0500
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 i05LLDVM009389
	for <ietf@ietf.org>; Mon, 5 Jan 2004 13:21:14 -0800 (PST)
Received: from [10.32.245.157] (stealth-10-32-245-157.cisco.com [10.32.245.157])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id ALE07348;
	Mon, 5 Jan 2004 13:21:12 -0800 (PST)
Date: Mon, 05 Jan 2004 16:21:10 -0500
From: David Oran <oran@cisco.com>
To: ietf@ietf.org
Subject: Re: Has anybody heard back from the Hotel in Seoul?
Message-ID: <2147483647.1073319670@[10.32.245.157]>
In-Reply-To: <6.0.1.1.2.20040105160957.0328ec18@mail.comcast.net>
References: <2147483647.1073314354@[10.32.245.157]>
 <6.0.1.1.2.20040105160957.0328ec18@mail.comcast.net>
X-Mailer: Mulberry/3.1.0 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

OK, I resent the email and will also fax again. I'll report back in a few 
dayts either way. Thanks to all who responded.

--On Monday, January 5, 2004 4:12 PM -0500 "Andrew G. Malis" 
<andymalis@comcast.net> wrote:

> I both faxed and emailed the form and received a fax confirmation several
> days later.  I don't know which one did the trick.  I suspect the fax,
> since I was faxed a reply.
>
> Cheers,
> Andy
>
> -----------
>
> At 1/5/2004 02:52 PM -0500, David R. Oran wrote:
>> I sent in my reservation request the day after registration opened and I
>> have heard nothing back at all.
>>
>> Have others similarly gotten no response, or is it likely my room
>> request  got dropped and I need to retransmit?
>>
>> (Probably better to reply to me rather than the list unless people
>> suspect  we have a generic problem).
>>
>> Dave Oran
>







From owner-ietf@ietf.org  Mon Jan  5 18:47:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14217
	for <ietf-web-archive@odin.ietf.org>; Mon, 5 Jan 2004 18:47:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AdeKE-0004gl-7y
	for ietf-list@asgard.ietf.org; Mon, 05 Jan 2004 18:39:58 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AdeI3-0004e8-0t
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 18:37:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12241
	for <ietf@ietf.org>; Mon, 5 Jan 2004 18:37:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdeI1-0001oI-00
	for ietf@ietf.org; Mon, 05 Jan 2004 18:37:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdeCk-0000f5-00
	for ietf@ietf.org; Mon, 05 Jan 2004 18:32:15 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ade2q-00071R-00
	for ietf@ietf.org; Mon, 05 Jan 2004 18:22:01 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-2.cisco.com with ESMTP; 05 Jan 2004 15:28:05 +0000
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id i05NL5J6006735;
	Mon, 5 Jan 2004 15:21:05 -0800 (PST)
Received: from cisco.com (gargi-u5.cisco.com [128.107.162.118])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AOY90854;
	Mon, 5 Jan 2004 15:21:04 -0800 (PST)
Message-ID: <3FF9F160.5050907@cisco.com>
Date: Mon, 05 Jan 2004 15:21:04 -0800
From: Gargi Nalawade <gargi@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Melinda Shore <mshore@cisco.com>
CC: Adam Roach <adam@dynamicsoft.com>, ietf@ietf.org
Subject: Re: Has anybody heard back from the Hotel in Seoul?
References: <931B65F5-3FC1-11D8-AFFF-000A95E35274@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


With me it was reverse. I reserved it online and got back a confirmation 
through fax.

-Gargi

Melinda Shore wrote:
> On Monday, January 5, 2004, at 03:41 PM, Adam Roach wrote:
> 
>> I sent in an e-mail the day of, and haven't heard back, either.
>> This sounds like a systemic problem.
> 
> 
> I faxed my reservation request in the day after and received a confirmation
> via email on the 26th.  Perhaps they've acked faxed requests and not email
> requests or there's some other pattern.
> 
> Melinda
> 
> 





From owner-ietf@ietf.org  Mon Jan  5 22:41:01 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20183
	for <ietf-web-archive@odin.ietf.org>; Mon, 5 Jan 2004 22:41:01 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AdhwW-0000Nr-6c
	for ietf-list@asgard.ietf.org; Mon, 05 Jan 2004 22:31:44 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AdhwF-0000ND-4y
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 22:31:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20110
	for <ietf@ietf.org>; Mon, 5 Jan 2004 22:31:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdhwD-0004MT-00
	for ietf@ietf.org; Mon, 05 Jan 2004 22:31:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdhuO-0004Kf-00
	for ietf@ietf.org; Mon, 05 Jan 2004 22:29:33 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adhtd-0004Hk-00
	for ietf@ietf.org; Mon, 05 Jan 2004 22:28:45 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-2.cisco.com with ESMTP; 05 Jan 2004 19:35:15 +0000
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 i063SEJ6011368
	for <ietf@ietf.org>; Mon, 5 Jan 2004 19:28:14 -0800 (PST)
Received: from [10.32.245.157] (stealth-10-32-245-157.cisco.com [10.32.245.157])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id ALE39670;
	Mon, 5 Jan 2004 19:28:13 -0800 (PST)
Date: Mon, 05 Jan 2004 22:28:11 -0500
From: David Oran <oran@cisco.com>
To: ietf@ietf.org
Subject: Seould Hotel reservtions - update
Message-ID: <2147483647.1073341691@[10.32.245.157]>
X-Mailer: Mulberry/3.1.0 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I retransmitted my hotel request by both email and fax. I received an email 
confirmation (with the actual confirmation as a fax attachment) this 
evening - less than 12 hours after retransmit.

I suggest any of you who have not heard back yet time out and retransmit.

There may have been a burst loss in the day or two following registration 
opening.

Thanks to all who responded with both positive ack and no response data.

Dave.



From owner-ietf@ietf.org  Tue Jan  6 10:02:53 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20197
	for <ietf-web-archive@odin.ietf.org>; Tue, 6 Jan 2004 10:02:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AdsJy-0007Go-Sa
	for ietf-list@asgard.ietf.org; Tue, 06 Jan 2004 09:36:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Adbjo-0000Xe-9Q
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 15:54:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03987
	for <ietf@ietf.org>; Mon, 5 Jan 2004 15:54:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adbjm-0005in-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:54:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adbiq-0005ZP-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:53:13 -0500
Received: from tyholt.uninett.no ([158.38.60.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdbgW-0005G6-00
	for ietf@ietf.org; Mon, 05 Jan 2004 15:50:49 -0500
Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id i05Ko61k030111;
	Mon, 5 Jan 2004 21:50:06 +0100
Received: from sverresborg.uninett.no (localhost.localdomain [127.0.0.1])
	by sverresborg.uninett.no (8.12.8/8.12.9) with ESMTP id i05Ko6kj024056;
	Mon, 5 Jan 2004 21:50:06 +0100
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i05Ko6S9024055;
	Mon, 5 Jan 2004 21:50:06 +0100
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Mon, 5 Jan 2004 21:50:06 +0100
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Scott Bradner <sob@harvard.edu>
Cc: ietf@ietf.org, oran@cisco.com
Subject: Re: Has anybody heard back from the Hotel in Seoul?
Message-ID: <20040105205006.GB24030@sverresborg.uninett.no>
References: <2147483647.1073314354@[10.32.245.157]> <20040105201525.C1894BDD43@newdev.harvard.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040105201525.C1894BDD43@newdev.harvard.edu>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Jan 05, 2004 at 03:15:25PM -0500, Scott Bradner wrote:
> I have not heard
[...]

I faxed the hotel day after registration opened, and got a fax back
at about the 26th I think, I need to go to office to check details.

One interesting thing though, is that I also got someone elses
confirmation faxed to me!

The person I got confirmation for had first name Stuart I remember.
So those called Stuart missing a confirmation, may want to contact
me. I don't remember the last name, but can check in office tomorrow.

Stig





From owner-ietf@ietf.org  Tue Jan  6 10:02:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20214
	for <ietf-web-archive@odin.ietf.org>; Tue, 6 Jan 2004 10:02:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AdsJz-0007Gu-1U
	for ietf-list@asgard.ietf.org; Tue, 06 Jan 2004 09:36:39 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AdcEA-00025P-JP
	for ietf@asgard.ietf.org; Mon, 05 Jan 2004 16:25:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04829
	for <ietf@ietf.org>; Mon, 5 Jan 2004 16:25:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdcDz-0006rf-00
	for ietf@ietf.org; Mon, 05 Jan 2004 16:25:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adc9u-0006Zt-00
	for ietf@ietf.org; Mon, 05 Jan 2004 16:21:11 -0500
Received: from sccrmhc12.comcast.net ([204.127.202.56])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adc2Z-0006HI-00
	for ietf@ietf.org; Mon, 05 Jan 2004 16:13:36 -0500
Received: from amalist40.comcast.net (unknown[12.46.111.114])
          by comcast.net (sccrmhc12) with SMTP
          id <2004010521123401200e15tne>
          (Authid: andymalis@comcast.net);
          Mon, 5 Jan 2004 21:12:37 +0000
Message-Id: <6.0.1.1.2.20040105160957.0328ec18@mail.comcast.net>
X-Sender: andymalis@comcast.net@mail.comcast.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Mon, 05 Jan 2004 16:12:31 -0500
To: "David R. Oran" <oran@cisco.com>
From: "Andrew G. Malis" <andymalis@comcast.net>
Subject: Re: Has anybody heard back from the Hotel in Seoul?
Cc: ietf@ietf.org
In-Reply-To: <2147483647.1073314354@[10.32.245.157]>
References: <2147483647.1073314354@[10.32.245.157]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I both faxed and emailed the form and received a fax confirmation several 
days later.  I don't know which one did the trick.  I suspect the fax, 
since I was faxed a reply.

Cheers,
Andy

-----------

At 1/5/2004 02:52 PM -0500, David R. Oran wrote:
>I sent in my reservation request the day after registration opened and I 
>have heard nothing back at all.
>
>Have others similarly gotten no response, or is it likely my room request 
>got dropped and I need to retransmit?
>
>(Probably better to reply to me rather than the list unless people suspect 
>we have a generic problem).
>
>Dave Oran






From owner-ietf@ietf.org  Wed Jan  7 14:05:20 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24829
	for <ietf-web-archive@odin.ietf.org>; Wed, 7 Jan 2004 14:05:20 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AeIpN-0004ni-LB
	for ietf-list@asgard.ietf.org; Wed, 07 Jan 2004 13:54:49 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ae3SD-0006Mz-A7
	for ietf@asgard.ietf.org; Tue, 06 Jan 2004 21:29:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16947
	for <ietf@ietf.org>; Tue, 6 Jan 2004 21:29:51 -0500 (EST)
From: avri@acm.org
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae3SB-0007HT-00
	for ietf@ietf.org; Tue, 06 Jan 2004 21:29:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae3QR-0007E0-00
	for ietf@ietf.org; Tue, 06 Jan 2004 21:28:03 -0500
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae3PT-00079a-00
	for ietf@ietf.org; Tue, 06 Jan 2004 21:27:03 -0500
Received: from [147.28.0.62] (helo=acm.org)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Ae3PT-000G4E-0U
	for ietf@ietf.org; Wed, 07 Jan 2004 02:27:03 +0000
Date: Wed, 7 Jan 2004 11:26:58 +0900
Subject: Re: Has anybody heard back from the Hotel in Seoul?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
To: ietf@ietf.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <6.0.1.1.2.20040105160957.0328ec18@mail.comcast.net>
Message-Id: <F7E94F34-40B8-11D8-8852-000393CC2112@acm.org>
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

Just as another check point.  I sent mine in by email.  And on not 
receiving a confirmation by email, even after a second request, I 
decided to call them and confirm.  They had indeed received it and were 
able to give me the confirmation number over the phone.  Now, since I 
currently live in Korea, this was a relatively local phone call, so I 
am not necessarily recommending that everyone call them.  But this is 
an indicator that they are processing the email reservations.

a.






From owner-ietf@ietf.org  Wed Jan  7 15:50:19 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00392
	for <ietf-web-archive@odin.ietf.org>; Wed, 7 Jan 2004 15:50:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AeKVZ-0001iy-VT
	for ietf-list@asgard.ietf.org; Wed, 07 Jan 2004 15:42:29 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AeKTc-0001gU-UA
	for ietf@asgard.ietf.org; Wed, 07 Jan 2004 15:40:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29716
	for <ietf@ietf.org>; Wed, 7 Jan 2004 15:40:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeKTb-0002Er-00
	for ietf@ietf.org; Wed, 07 Jan 2004 15:40:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeKS5-00025M-00
	for ietf@ietf.org; Wed, 07 Jan 2004 15:38:54 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeKO3-0001qm-00
	for ietf@ietf.org; Wed, 07 Jan 2004 15:34:43 -0500
Received: from ibm-eyjgx9r6nqt.shockey.us (neustargw.va.neustar.com [209.173.53.233])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i07KeWc19657;
	Wed, 7 Jan 2004 12:40:32 -0800
Message-Id: <6.0.1.1.2.20040107153154.04985ec0@joy.songbird.com>
X-Sender: richard@joy.songbird.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 07 Jan 2004 15:32:32 -0500
To: avri@acm.org, ietf@ietf.org
From: Richard Shockey <richard@shockey.us>
Subject: Re: Has anybody heard back from the Hotel in Seoul?
In-Reply-To: <F7E94F34-40B8-11D8-8852-000393CC2112@acm.org>
References: <6.0.1.1.2.20040105160957.0328ec18@mail.comcast.net>
 <F7E94F34-40B8-11D8-8852-000393CC2112@acm.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=BIZ_TLD autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 09:26 PM 1/6/2004, avri@acm.org wrote:

>Hi,
>
>Just as another check point.  I sent mine in by email.  And on not 
>receiving a confirmation by email, even after a second request, I decided 
>to call them and confirm.  They had indeed received it and were able to 
>give me the confirmation number over the phone.  Now, since I currently 
>live in Korea, this was a relatively local phone call, so I am not 
>necessarily recommending that everyone call them.  But this is an 
>indicator that they are processing the email reservations.


I processed by fax and got a prompt response....





 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
<http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<




From owner-ietf@ietf.org  Thu Jan  8 02:51:56 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11923
	for <ietf-web-archive@odin.ietf.org>; Thu, 8 Jan 2004 02:51:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AeUkK-0003fs-PH
	for ietf-list@asgard.ietf.org; Thu, 08 Jan 2004 02:38:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AeUkF-0003eB-LA
	for ietf@asgard.ietf.org; Thu, 08 Jan 2004 02:38:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11584
	for <ietf@ietf.org>; Thu, 8 Jan 2004 02:38:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeUkD-0007ly-00
	for ietf@ietf.org; Thu, 08 Jan 2004 02:38:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeUiJ-0007fE-00
	for ietf@ietf.org; Thu, 08 Jan 2004 02:36:21 -0500
Received: from [202.108.44.205] (helo=163.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AeUgS-0007XS-00
	for ietf@ietf.org; Thu, 08 Jan 2004 02:34:24 -0500
Received: from wl302 (unknown [211.67.24.168])
	by 192.168.1.205 (Coremail) with SMTP id DUQIAF0E_T8IABio.1
	for <ietf@ietf.org>; Thu, 08 Jan 2004 15:19:01 +0800 (CST)
X-Originating-IP: [211.67.24.168]
Message-ID: <004d01c3d5b7$f2dda7d0$a81843d3@wl302>
From: "wang liang" <wangliang_f@163.com>
To: <ietf@ietf.org>
Subject: Building a new work group for public information retrieval protocol, ask for advices.
Date: Thu, 8 Jan 2004 15:20:46 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

After publishing the message "propose some information retrieval protocols
for Internet", we received many advices. Now we
want to build a new work group for this issue, asking for more advices.
Information retrieval service may exceed E-mail
service and become the most import service of Internet, so we can't neglect
it.

The reason to build a work group for public information retrieval protocols
lies in the disadvantage of current commercial
search engines and the improvement in future public search system.

The faults in commercial search engines.

1 In technology. Now no search engine can cover 60% of all the pages on
Internet. The average update interval of their web
pages database is almost one month. This is mainly because no of them can
close keep up with the explosive web pages on
Internet. But the web page is only one kind of information resources. There
are still many other resources such as video,
special databases, BBS, etc. Could you image single search engine company
can efficiently administer all these information
resources?

2 In business model. Now many search engine companies are concerned with how
to make profit from company users by
advertisement and ranking prominence, but never consider what its real
customers will feel. Search engine originally is tools
for the convenience of Internet customers, but search engine companies have
to apply advertisement or selling ranking
prominence, somewhat inconvenient to information retrieval, to maintain
their subsistence. In other words, search engines
make money at the cost of inconvenience of most Internet users, but not its
high quality of search service.

3 Except search engine, all the services of Internet such as E-mail, BBS,
and FTP are all based on public protocol. There is
no secret technology in these services. But the information retrieval
service, may be the most important service on Internet,
is still dominated by few search engine companies. Many experts know the
basic "Pages Ranking" algorithm, but no one know its
detail, which is commercial secret. No public surveillance, no real candid
ranking algorithm. but We all know another world
famous algorithm very well, "money can elevate ranking score". This may not
comply with the basic rules of Internet, a public
and free world.

4 In any free market, customers should be the God forever, but not few
companies.


The improvement in new public search system, DRIS (Domain resources
integrated system)

1 In technology. DRIS will build the information retrieval infrastructure of
Internet. DRIS applies a hierarchical
distributed architecture to manage all the information on Internet, just
like DNS. Its main principle is (organization level
-conventional database system)-(main sub country Internet level-metadata
harvest system)-(country level-distributed search
system).In easy words, like web pages system, every DRIS server in bottom
level like a university will download and index all
the web pages in its local network and then send the metadata to higher
layer. All the other resources are also integrated in
this method. So DRIS will improve the performance of Internet search engine
in recency, coverage and so on.

2 Management. Who will control the DRIS? It's administrated by none of us
but every of us. DRIS is managed by its users and
coordinated by a public organization, just like management method of DNS.
Every organization is its customer and also its
builder. It's just the real truth of Internet. DRIS is an opening system,
which needn't any profits from its users and of
course need not any advertisements.

3 The basic idea of DRIS : "search should be the internal function of
Internet and every one should have his own search
engine". DRIS just provide the rude search results (like the results in
current search engine). Many intelligent search
systems can apply DRIS as their data source and provide high quality of
personal or commercial search service. So commercial
search engine can still survive in the way it should be.

4 Although DRIS gives us an excellent and promising solution for the new
public Internet search system, this can't ensure the
establishment of DRIS. One important principle in technology, the best
technology is the technology that can meet the urgent
demand in society. This is just the secret of DRIS. In our testbed, in
organization level, only few universities have the web
search engine for the school network. Say nothing of union search system
that can efficiently integrate all its information
resources such as ftp, BBS and special databases in library. It's the demand
in third layer. Sharing the information
resources between different organizations is also an attraction, which is
the demand to build the second layer's DRIS. In the
top layer, integrating all the information resources on Internet may be the
dream of everyone.

5 Practice is the only principle to judge a theory. Now we have built some
experimental third layer's DRIS servers in HuBei
Province. I can only say that things just should like this.



                                                    Protocol Series of
DRIS(for work group)
Description of Working Group:

With the rapid increase of the web pages, the coverage of search engines
will become poorer and the update interval will be much longer. If the
current architecture of search engines is still in use, it will be an
impossible mission to find the precise and comprehensive information in the
future. This problem will be more serious when IPV6 technology is widely
implemented in communication networks. The problem of "Too much information
means no information" may become a disaster with information explosion. To
solve this problem, there should be an efficient information management
system for Internet.

In this group, Domain Resource Integrated System--DRIS will be proposed.
DRIS is a distributed information retrieval system, which will build the
information retrieval infrastructure for the Internet and also can be
regarded as a kind of Internet information management system.

DRIS is a hierarchical distributed search system and comprise three kinds of
information retrieval system, conventional
database system, distributed search system and metadata harvest system. We
will first define the basic search system and then
define the entire DRIS.

Specific work items are:

1 Standard distributed search system. It defines the platform-independent
search interface and a collection description
standard for heterogeneous information resources. An I-D "information
retrieval protocol for digital resources" has been
proposed.  (http://www.ietf.org/internet-drafts/draft-liang-irpdl-03.txt)

2 Standard metadata harvest system. A protocol based some available opening
standard like OAI will be proposed. It will
define a standard metadata that can be compatible with most database system.

3 Standard public web pages search system. There are many kinds of database
system. As long as they can provide the standard
distributed search interface or comply with the metadata harvest format,
they can be brought into DRIS in appropriate layer.
But web pages are special for its distributed character and astronomical
amount. To efficiently integrate web pages on
Internet, DRIS will build a public opening web pages database, which will
strictly comply with the principle of (organization
level-conventional database system)-(sub country Internet level-metadata
harvest system)-(country level-distributed system).
(More information: Make search become the internal function of Internet.
http://arxiv.org/abs/cs.IR/0311015)

4 DRIS. It will define entire DRIS. It includes its whole architecture, the
relation between different nodes, etc.
(more information: Evolution:Google vs.GRIS.
http://arxiv.org/abs/cs.DL/0312024)

5 DRIS and IPV6. The cooperation with IPV6 WG will be proposed. IPV6 will be
the most distinct feather of next generation
Internet.IPV6 is still in improving and any technology that can benefit the
Internet all can be added to the IPV6 system.
Since the searching is the main service of most user of Internet and this
service is not so satisfied to us in current
Internet, why not take this request into account when build the new
Internet. For example, in IPV6, all kinds of data flows
are assigned a priority, and then Internet can guarantee a high priority to
the data flow of DRIS. So there may need some
considerations for the relation between DRIS and IPV6.

The detailed information about DRIS could be found in
http://www.lib.hust.edu.cn/dl-lib/English/main.htm

Ask for more advices. Thanks





From owner-ietf@ietf.org  Thu Jan  8 11:19:26 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00729
	for <ietf-web-archive@odin.ietf.org>; Thu, 8 Jan 2004 11:19:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AecjS-0006zz-9o
	for ietf-list@asgard.ietf.org; Thu, 08 Jan 2004 11:10:02 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AeciA-0006Nt-Sk
	for ietf@asgard.ietf.org; Thu, 08 Jan 2004 11:08:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29955
	for <ietf@ietf.org>; Thu, 8 Jan 2004 11:08:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aeci7-0004Lu-00
	for ietf@ietf.org; Thu, 08 Jan 2004 11:08:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AecgA-0004F5-00
	for ietf@ietf.org; Thu, 08 Jan 2004 11:06:40 -0500
Received: from jay.songbird.com ([208.184.79.253])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AecfC-00049R-00
	for ietf@ietf.org; Thu, 08 Jan 2004 11:05:38 -0500
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 i08G58005014;
	Thu, 8 Jan 2004 08:05:11 -0800
Message-Id: <5.1.0.14.2.20040108091726.00b82008@127.0.0.1>
X-Sender: gk-bulk@127.0.0.1 (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 08 Jan 2004 09:33:13 +0000
To: "wang liang" <wangliang_f@163.com>, <ietf@ietf.org>
From: Graham Klyne <GK@ninebynine.org>
Subject: Re: Building a new work group for public information retrieval
  protocol, ask for advices.
In-Reply-To: <004d01c3d5b7$f2dda7d0$a81843d3@wl302>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=DATE_IN_PAST_06_12 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 15:20 08/01/04 +0800, wang liang wrote:
>After publishing the message "propose some information retrieval protocols
>for Internet", we received many advices. Now we
>want to build a new work group for this issue, asking for more advices.

I think it's not clear that this is an appropriate IETF working group that 
is being proposed:

(a) it seems to be primarily a Web service to find information about Web 
resources, rather than a more general Internet issue, and there's a debate 
to be had about whether the IETF is the right forum for this.

(b) the proposal seems to be about defining and retrieving metadata about 
Web resources, and as such seems to have significant overlap with existing 
and planned work in W3C [1].  Specifically, the W3C have recently advanced 
the revised metadata format standard (RDF) and the companion ontology 
language (OWL) to Proposed Recommendation [2] [3].  They are also in the 
process of forming a group to define a metadata access service/protocol 
[4], whose likely function would considerably overlap what I understand 
your proposal to be doing.

You mention use of Dublin Core as part of your metadata set:  I note that 
there are already RDF specifications for the Dublin Core metadata set [5], 
and that much existing work with Dublin Core uses RDF.

If you have strong reasons for not following the RDF route, there is also a 
body of XML Query work that you seem to have overlooked [6].

I also note that I have been unable to access the web page you mention 
(http://www.lib.hust.edu.cn/dl-lib/English/main.htm).

#g
--

[1] http://www.w3.org/

[2] http://www.w3.org/RDF/

[3] http://www.w3.org/2001/sw/WebOnt/

[4] http://www.w3.org/2003/10/RDF-Query-Charter

[5] http://dublincore.org/documents/2002/07/31/dcmes-xml/
     http://dublincore.org/documents/2002/04/14/dcq-rdf-xml/

[6] http://www.w3.org/XML/Query


At 15:20 08/01/04 +0800, wang liang wrote:
>After publishing the message "propose some information retrieval protocols
>for Internet", we received many advices. Now we
>want to build a new work group for this issue, asking for more advices.
>Information retrieval service may exceed E-mail
>service and become the most import service of Internet, so we can't neglect
>it.
>
>The reason to build a work group for public information retrieval protocols
>lies in the disadvantage of current commercial
>search engines and the improvement in future public search system.
>
>The faults in commercial search engines.
>
>1 In technology. Now no search engine can cover 60% of all the pages on
>Internet. The average update interval of their web
>pages database is almost one month. This is mainly because no of them can
>close keep up with the explosive web pages on
>Internet. But the web page is only one kind of information resources. There
>are still many other resources such as video,
>special databases, BBS, etc. Could you image single search engine company
>can efficiently administer all these information
>resources?
>
>2 In business model. Now many search engine companies are concerned with how
>to make profit from company users by
>advertisement and ranking prominence, but never consider what its real
>customers will feel. Search engine originally is tools
>for the convenience of Internet customers, but search engine companies have
>to apply advertisement or selling ranking
>prominence, somewhat inconvenient to information retrieval, to maintain
>their subsistence. In other words, search engines
>make money at the cost of inconvenience of most Internet users, but not its
>high quality of search service.
>
>3 Except search engine, all the services of Internet such as E-mail, BBS,
>and FTP are all based on public protocol. There is
>no secret technology in these services. But the information retrieval
>service, may be the most important service on Internet,
>is still dominated by few search engine companies. Many experts know the
>basic "Pages Ranking" algorithm, but no one know its
>detail, which is commercial secret. No public surveillance, no real candid
>ranking algorithm. but We all know another world
>famous algorithm very well, "money can elevate ranking score". This may not
>comply with the basic rules of Internet, a public
>and free world.
>
>4 In any free market, customers should be the God forever, but not few
>companies.
>
>
>The improvement in new public search system, DRIS (Domain resources
>integrated system)
>
>1 In technology. DRIS will build the information retrieval infrastructure of
>Internet. DRIS applies a hierarchical
>distributed architecture to manage all the information on Internet, just
>like DNS. Its main principle is (organization level
>-conventional database system)-(main sub country Internet level-metadata
>harvest system)-(country level-distributed search
>system).In easy words, like web pages system, every DRIS server in bottom
>level like a university will download and index all
>the web pages in its local network and then send the metadata to higher
>layer. All the other resources are also integrated in
>this method. So DRIS will improve the performance of Internet search engine
>in recency, coverage and so on.
>
>2 Management. Who will control the DRIS? It's administrated by none of us
>but every of us. DRIS is managed by its users and
>coordinated by a public organization, just like management method of DNS.
>Every organization is its customer and also its
>builder. It's just the real truth of Internet. DRIS is an opening system,
>which needn't any profits from its users and of
>course need not any advertisements.
>
>3 The basic idea of DRIS : "search should be the internal function of
>Internet and every one should have his own search
>engine". DRIS just provide the rude search results (like the results in
>current search engine). Many intelligent search
>systems can apply DRIS as their data source and provide high quality of
>personal or commercial search service. So commercial
>search engine can still survive in the way it should be.
>
>4 Although DRIS gives us an excellent and promising solution for the new
>public Internet search system, this can't ensure the
>establishment of DRIS. One important principle in technology, the best
>technology is the technology that can meet the urgent
>demand in society. This is just the secret of DRIS. In our testbed, in
>organization level, only few universities have the web
>search engine for the school network. Say nothing of union search system
>that can efficiently integrate all its information
>resources such as ftp, BBS and special databases in library. It's the demand
>in third layer. Sharing the information
>resources between different organizations is also an attraction, which is
>the demand to build the second layer's DRIS. In the
>top layer, integrating all the information resources on Internet may be the
>dream of everyone.
>
>5 Practice is the only principle to judge a theory. Now we have built some
>experimental third layer's DRIS servers in HuBei
>Province. I can only say that things just should like this.
>
>
>
>                                                     Protocol Series of
>DRIS(for work group)
>Description of Working Group:
>
>With the rapid increase of the web pages, the coverage of search engines
>will become poorer and the update interval will be much longer. If the
>current architecture of search engines is still in use, it will be an
>impossible mission to find the precise and comprehensive information in the
>future. This problem will be more serious when IPV6 technology is widely
>implemented in communication networks. The problem of "Too much information
>means no information" may become a disaster with information explosion. To
>solve this problem, there should be an efficient information management
>system for Internet.
>
>In this group, Domain Resource Integrated System--DRIS will be proposed.
>DRIS is a distributed information retrieval system, which will build the
>information retrieval infrastructure for the Internet and also can be
>regarded as a kind of Internet information management system.
>
>DRIS is a hierarchical distributed search system and comprise three kinds of
>information retrieval system, conventional
>database system, distributed search system and metadata harvest system. We
>will first define the basic search system and then
>define the entire DRIS.
>
>Specific work items are:
>
>1 Standard distributed search system. It defines the platform-independent
>search interface and a collection description
>standard for heterogeneous information resources. An I-D "information
>retrieval protocol for digital resources" has been
>proposed.  (http://www.ietf.org/internet-drafts/draft-liang-irpdl-03.txt)
>
>2 Standard metadata harvest system. A protocol based some available opening
>standard like OAI will be proposed. It will
>define a standard metadata that can be compatible with most database system.
>
>3 Standard public web pages search system. There are many kinds of database
>system. As long as they can provide the standard
>distributed search interface or comply with the metadata harvest format,
>they can be brought into DRIS in appropriate layer.
>But web pages are special for its distributed character and astronomical
>amount. To efficiently integrate web pages on
>Internet, DRIS will build a public opening web pages database, which will
>strictly comply with the principle of (organization
>level-conventional database system)-(sub country Internet level-metadata
>harvest system)-(country level-distributed system).
>(More information: Make search become the internal function of Internet.
>http://arxiv.org/abs/cs.IR/0311015)
>
>4 DRIS. It will define entire DRIS. It includes its whole architecture, the
>relation between different nodes, etc.
>(more information: Evolution:Google vs.GRIS.
>http://arxiv.org/abs/cs.DL/0312024)
>
>5 DRIS and IPV6. The cooperation with IPV6 WG will be proposed. IPV6 will be
>the most distinct feather of next generation
>Internet.IPV6 is still in improving and any technology that can benefit the
>Internet all can be added to the IPV6 system.
>Since the searching is the main service of most user of Internet and this
>service is not so satisfied to us in current
>Internet, why not take this request into account when build the new
>Internet. For example, in IPV6, all kinds of data flows
>are assigned a priority, and then Internet can guarantee a high priority to
>the data flow of DRIS. So there may need some
>considerations for the relation between DRIS and IPV6.
>
>The detailed information about DRIS could be found in
>http://www.lib.hust.edu.cn/dl-lib/English/main.htm
>
>Ask for more advices. Thanks
>
>
>
>_______________________________________________
>This message was passed through ietf_censored@carmen.ipv6.cselt.it, which 
>is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on 
>what to pass are made solely by IETF_CENSORED ML Administrator 
>(ietf_admin@ngnet.it).

------------
Graham Klyne
For email:
http://www.ninebynine.org/#Contact




From owner-ietf@ietf.org  Thu Jan  8 15:12:32 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09400
	for <ietf-web-archive@odin.ietf.org>; Thu, 8 Jan 2004 15:12:32 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aeg6u-0005Vp-QL
	for ietf-list@asgard.ietf.org; Thu, 08 Jan 2004 14:46:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AefPF-0003n4-9I
	for ietf@asgard.ietf.org; Thu, 08 Jan 2004 14:01:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06140
	for <ietf@ietf.org>; Thu, 8 Jan 2004 14:00:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AefOo-0006tM-00
	for ietf@ietf.org; Thu, 08 Jan 2004 14:00:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AefJD-0006dg-00
	for ietf@ietf.org; Thu, 08 Jan 2004 13:55:08 -0500
Received: from [206.196.68.254] (helo=confucius.gnacademy.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AefFR-0006QM-00
	for ietf@ietf.org; Thu, 08 Jan 2004 13:51:13 -0500
Received: from confucius.gnacademy.org (confucius.gnacademy.org [206.196.68.254])
	by confucius.gnacademy.org (Postfix) with ESMTP id 8043E228083;
	Thu,  8 Jan 2004 12:50:50 -0600 (CST)
Date: Thu, 8 Jan 2004 12:50:50 -0600 (CST)
From: Wawa Ngenge <ngenge@confucius.gnacademy.org>
To: Mark Smith <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
Cc: mose@mose.fr, ietf@ietf.org, isdf@isoc.org
Subject: Re: [isdf] Re: www.internetforce.org
In-Reply-To: <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
Message-ID: <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
 <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 5 Jan 2004, Mark Smith wrote:

> On Sat, 03 Jan 2004 07:53:04 -0500
> Because that is not how they are updated.
> The RFC faq would a place to seek your ansers.

The original question is : "Why do they not operate that way", if they are 
indeed REQUESTS?
w
 
> http://www.rfc-editor.org/rfcfaq.html
> 
> Regards,
> Mark.
> _______________________________________________
> Isdf mailing list
> Isdf@isoc.org
> http://www.isoc.org/mailman/listinfo/isdf
> 

-- 
Wawa Ngenge (Ph.D.)
Internet Society Trustee Emeritus
WorldComputerExchange.org  Director
www.worldcomputerexchange.org/board_staff/ngenge-resume.htm
ngenge@confucius.gnacademy.org





From owner-ietf@ietf.org  Thu Jan  8 15:58:10 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11761
	for <ietf-web-archive@odin.ietf.org>; Thu, 8 Jan 2004 15:58:10 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aeh5k-0002Ck-LA
	for ietf-list@asgard.ietf.org; Thu, 08 Jan 2004 15:49:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aeh5H-0002Af-S7
	for ietf@asgard.ietf.org; Thu, 08 Jan 2004 15:48:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11521
	for <ietf@ietf.org>; Thu, 8 Jan 2004 15:48:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aeh5E-0005LU-00
	for ietf@ietf.org; Thu, 08 Jan 2004 15:48:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aeh3I-0005EK-00
	for ietf@ietf.org; Thu, 08 Jan 2004 15:46:49 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aeh22-00057o-00
	for ietf@ietf.org; Thu, 08 Jan 2004 15:45:30 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1Aeh1p-000ADx-00; Thu, 08 Jan 2004 15:45:17 -0500
Date: Thu, 08 Jan 2004 15:45:17 -0500
From: John C Klensin <john-ietf@jck.com>
To: Wawa Ngenge <ngenge@confucius.gnacademy.org>
cc: ietf@ietf.org, isdf@isoc.org
Subject: Re: [isdf] Re: www.internetforce.org
Message-ID: <240387438.1073576717@scan.jck.com>
In-Reply-To: <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
 <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nos
 ense.org>
 <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Thursday, 08 January, 2004 12:50 -0600 Wawa Ngenge 
<ngenge@confucius.gnacademy.org> wrote:

> On Mon, 5 Jan 2004, Mark Smith wrote:
>
>> On Sat, 03 Jan 2004 07:53:04 -0500
>> Because that is not how they are updated.
>> The RFC faq would a place to seek your ansers.
>
> The original question is : "Why do they not operate that way",
> if they are  indeed REQUESTS?
> w

Hi.

A better answer would have been "the term 'request for comment' 
is historical, dating from a time when the preferred way to make 
a formal comment on a document involved writing another 
document, which then was numbered into the series".  That 
mechanism is still available, although usually very slow.  But 
documents that become RFCs are now first posted as Internet 
Drafts (see http://www.ietf.org/ID); comments on those are both 
solicited and, usually, handled very quickly.

Today, the RFC Series, despite retention of the original name 
and numbering series, acts as a permanent, archival, repository 
of information, decisions taken, and standards published.  As 
such, documents in the series are subjected to review and 
editing processes (which differ somewhat depending on the type 
of document and are appropriate for conventional references from 
conventional documents.  Running conversations, logs of 
comments, etc., are not well suited for that archival and 
reference role, regardless of their other advantages and 
disadvantages.

regards,
    john




From owner-ietf@ietf.org  Thu Jan  8 17:03:42 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13677
	for <ietf-web-archive@odin.ietf.org>; Thu, 8 Jan 2004 17:03:42 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AeiAW-0005R1-IA
	for ietf-list@asgard.ietf.org; Thu, 08 Jan 2004 16:58:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AeiAC-0005Oi-KE
	for ietf@asgard.ietf.org; Thu, 08 Jan 2004 16:58:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13534
	for <ietf@ietf.org>; Thu, 8 Jan 2004 16:57:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeiA2-0001EU-00
	for ietf@ietf.org; Thu, 08 Jan 2004 16:57:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aei57-000145-00
	for ietf@ietf.org; Thu, 08 Jan 2004 16:52:45 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aei3y-0000y5-00
	for ietf@ietf.org; Thu, 08 Jan 2004 16:51:34 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-2.cisco.com with ESMTP; 08 Jan 2004 13:58:37 +0000
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i08LotVM006110;
	Thu, 8 Jan 2004 13:50:55 -0800 (PST)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id APB88806;
	Thu, 8 Jan 2004 13:50:53 -0800 (PST)
Message-Id: <6.0.1.1.2.20040108125245.043441e8@mira-sjc5-b.cisco.com >
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 08 Jan 2004 13:47:36 -0800
To: Wawa Ngenge <ngenge@confucius.gnacademy.org>
From: Fred Baker <fred@cisco.com>
Subject: Re: [isdf] Re: www.internetforce.org
Cc: Mark Smith <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>,
        mose@mose.fr, ietf@ietf.org, isdf@isoc.org
In-Reply-To: <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
 <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
 <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.7 required=5.0 tests=FORGED_MUA_EUDORA,
	INVALID_MSGID autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Wawa:

Is this a relay of a question from the ISDF list to the IETF list? I don't 
seem to have the context of the conversation.

I gather that the question has something to do with the management of RFCs. 
It would be good to read the discussion at http://www.rfc-editor.org/ for 
what the RFC Editor thinks the RFC Series is.

As to the name, you need to understand both the origins and the history of 
the series: the series was originally an archive of notes among friends, 
and (per Steve Crocker, the guy who named them) was called "Request for 
Comments" as much as anything to downplay the concept of "we are now 
publishing Something Immutable and Really Important". That was in 1969. By 
the time I became associated with the IETF in 1989, there was a running 
joke that the letters really stood for "Requirements for Compliance", and 
today we often have a hard time convincing the ignorant that a published 
RFC - even when it opens with the words "this is not a standard" or "this 
is a bad idea that we are archiving so we don't forget why it is a bad 
idea" - is in fact not a standard. http://www.ietf.org/rfc/rfc2026.txt 
describes the current use of the RFC series, in terms of standards track 
specifications (about 1/3 of the RFCs), history, experiments, white papers 
on networking, poetry, and April Fool's jokes.

Fred


At 10:50 AM 1/8/2004, Wawa Ngenge wrote:
>On Mon, 5 Jan 2004, Mark Smith wrote:
>
> > On Sat, 03 Jan 2004 07:53:04 -0500
> > Because that is not how they are updated.
> > The RFC faq would a place to seek your ansers.
>
>The original question is : "Why do they not operate that way", if they are
>indeed REQUESTS?
>w
>
> > http://www.rfc-editor.org/rfcfaq.html
> >
> > Regards,
> > Mark.
> > _______________________________________________
> > Isdf mailing list
> > Isdf@isoc.org
> > http://www.isoc.org/mailman/listinfo/isdf
> >
>
>--
>Wawa Ngenge (Ph.D.)
>Internet Society Trustee Emeritus
>WorldComputerExchange.org  Director
>www.worldcomputerexchange.org/board_staff/ngenge-resume.htm
>ngenge@confucius.gnacademy.org
>
>
>
>_______________________________________________
>This message was passed through ietf_censored@carmen.ipv6.cselt.it, which 
>is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on 
>what to pass are made solely by IETF_CENSORED ML Administrator 
>(ietf_admin@ngnet.it).




From owner-ietf@ietf.org  Thu Jan  8 17:56:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16051
	for <ietf-web-archive@odin.ietf.org>; Thu, 8 Jan 2004 17:56:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AeiyX-0000ik-1e
	for ietf-list@asgard.ietf.org; Thu, 08 Jan 2004 17:50:01 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AeixP-0000bY-67
	for ietf@asgard.ietf.org; Thu, 08 Jan 2004 17:48:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15944
	for <ietf@ietf.org>; Thu, 8 Jan 2004 17:48:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeixN-0004rF-00
	for ietf@ietf.org; Thu, 08 Jan 2004 17:48:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aeive-0004lY-00
	for ietf@ietf.org; Thu, 08 Jan 2004 17:47:03 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeiuJ-0004cW-00
	for ietf@ietf.org; Thu, 08 Jan 2004 17:45:40 -0500
Received: by franck-lxnb.sopac.org.fj (Postfix, from userid 501)
	id 2C75D4B6A1; Thu,  8 Jan 2004 17:45:08 -0500 (EST)
Subject: Re: [isdf] Re: www.internetforce.org
From: Franck Martin <franck@sopac.org>
To: Fred Baker <fred@cisco.com>
Cc: ietf@ietf.org, isdf@isoc.org
In-Reply-To: <6.0.1.1.2.20040108125245.043441e8@mira-sjc5-b.cisco.com >
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
	 <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
	 <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
	 <6.0.1.1.2.20040108125245.043441e8@mira-sjc5-b.cisco.com >
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-go3fXeiwfjkbycLqGbPo"
Organization: SOPAC
Message-Id: <1073601907.2729.9.camel@franck-lxnb.sopac.org.fj>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4-1.1mdk 
Date: 09 Jan 2004 10:45:08 +1200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


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

http://www.internetforce.org/tiki/tiki-index.php?page=3DTechnology

I put some of your comments there....

Hope you don't mind...

Cheers

On Fri, 2004-01-09 at 09:47, Fred Baker wrote:
> Wawa:
>=20
> Is this a relay of a question from the ISDF list to the IETF list? I don'=
t=20
> seem to have the context of the conversation.
>=20
The archive is only open to ISDF members, unfortunately.... Which is
still better than no ISTF archives.... ;)
----
Franck Martin
franck@sopac.org
SOPAC, Fiji
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9  D9C6 BE79 9E60 81D9 1320
"Toute connaissance est une reponse a une question" G.Bachelard

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

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

iD8DBQA//d1zvnmeYIHZEyARAsffAJ9lnmIsHKqUhU88LBGXL1Uh+t4ZqQCglO3S
qLPMoylI3k4+0MjiV1tPWfQ=
=U1Fd
-----END PGP SIGNATURE-----

--=-go3fXeiwfjkbycLqGbPo--



From owner-ietf@ietf.org  Thu Jan  8 18:29:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18129
	for <ietf-web-archive@odin.ietf.org>; Thu, 8 Jan 2004 18:29:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AejSq-0000Yy-K8
	for ietf-list@asgard.ietf.org; Thu, 08 Jan 2004 18:21:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AejSK-0000WO-55
	for ietf@asgard.ietf.org; Thu, 08 Jan 2004 18:20:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17771
	for <ietf@ietf.org>; Thu, 8 Jan 2004 18:20:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AejSH-0006Wr-00
	for ietf@ietf.org; Thu, 08 Jan 2004 18:20:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AejQk-0006N6-00
	for ietf@ietf.org; Thu, 08 Jan 2004 18:19:11 -0500
Received: from [63.247.76.239] (helo=montage.altserver.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AejLW-00065S-00
	for ietf@ietf.org; Thu, 08 Jan 2004 18:13:46 -0500
Received: from f02v-18-105.d0.club-internet.fr ([212.195.233.105] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1AejL6-0008BB-PF; Thu, 08 Jan 2004 15:13:21 -0800
Message-Id: <6.0.1.1.2.20040108232213.03f8beb0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 08 Jan 2004 23:32:43 +0100
To: John C Klensin <john-ietf@jck.com>,
        Wawa Ngenge <ngenge@confucius.gnacademy.org>
From: jfcm <info@utel.net>
Subject: Re: [isdf] Re: www.internetforce.org
Cc: ietf@ietf.org, isdf@isoc.org
In-Reply-To: <240387438.1073576717@scan.jck.com>
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
 <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nos ense.org>
 <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
 <240387438.1073576717@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 21:45 08/01/04, John C Klensin wrote:
>A better answer would have been "the term 'request for comment' is 
>historical, dating from a time when the preferred way to make a formal 
>comment on a document involved writing another document, which then was 
>numbered into the series".  That mechanism is still available, although 
>usually very slow.  But documents that become RFCs are now first posted as 
>Internet Drafts (see http://www.ietf.org/ID); comments on those are both 
>solicited and, usually, handled very quickly.
>
>Today, the RFC Series, despite retention of the original name and 
>numbering series, acts as a permanent, archival, repository of 
>information, decisions taken, and standards published.  As such, documents 
>in the series are subjected to review and editing processes (which differ 
>somewhat depending on the type of document and are appropriate for 
>conventional references from conventional documents.  Running 
>conversations, logs of comments, etc., are not well suited for that 
>archival and reference role, regardless of their other advantages and 
>disadvantages.


Could it not be useful to have a "List of Comments" (LOC) for each RFC? 
Where experience about the RFC reading, testing and implementation could be 
listed by the authors (or a successor) from experience and questions 
received. It would avoid the same questions to be debated again and again 
and it would help further thinking. These comments could start with a 
summary of the WG debated issues, explaining the whys of some options. I 
suppose the implementation would be easy enough since it would follow the 
same numbering scheme and titles. Such a LOC being an updated appendix 
could be reviewed and help preparing replacements.
jfc




From owner-ietf@ietf.org  Thu Jan  8 18:47:38 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18987
	for <ietf-web-archive@odin.ietf.org>; Thu, 8 Jan 2004 18:47:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aejo8-0001p6-Gm
	for ietf-list@asgard.ietf.org; Thu, 08 Jan 2004 18:43:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AejnW-0001mW-Tg
	for ietf@asgard.ietf.org; Thu, 08 Jan 2004 18:42:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18859
	for <ietf@ietf.org>; Thu, 8 Jan 2004 18:42:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AejnQ-0000R2-00
	for ietf@ietf.org; Thu, 08 Jan 2004 18:42:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aejlb-0000Ka-00
	for ietf@ietf.org; Thu, 08 Jan 2004 18:40:43 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aejjt-00009Q-00
	for ietf@ietf.org; Thu, 08 Jan 2004 18:38:57 -0500
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id i08NcOQu006407;
	Thu, 8 Jan 2004 15:38:24 -0800 (PST)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id APC01595;
	Thu, 8 Jan 2004 15:38:23 -0800 (PST)
Message-Id: <6.0.1.1.2.20040108153525.041ccb90@mira-sjc5-b.cisco.com >
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 08 Jan 2004 15:37:18 -0800
To: jfcm <info@utel.net>
From: Fred Baker <fred@cisco.com>
Subject: Re: [isdf] Re: www.internetforce.org
Cc: John C Klensin <john-ietf@jck.com>,
        Wawa Ngenge <ngenge@confucius.gnacademy.org>, ietf@ietf.org,
        isdf@isoc.org
In-Reply-To: <6.0.1.1.2.20040108232213.03f8beb0@mail.utel.net>
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
 <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nos ense.org>
 <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
 <240387438.1073576717@scan.jck.com>
 <6.0.1.1.2.20040108232213.03f8beb0@mail.utel.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.7 required=5.0 tests=AWL,FORGED_MUA_EUDORA,
	INVALID_MSGID autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 02:32 PM 1/8/2004, jfcm wrote:
>Could it not be useful to have a "List of Comments" (LOC) for each RFC? 
>Where experience about the RFC reading, testing and implementation could 
>be listed by the authors (or a successor) from experience and questions 
>received.

These are usually found in the form of working group archives and 
subsequent RFCs that update or obsolete the older ones, especially in the 
case of standards track documents. The RFC Editor also keeps a log of notes 
on RFCs when asked to.

It's not obvious, at least to me, why a second mechanism is required if th 
one that is there works...  




From owner-ietf@ietf.org  Thu Jan  8 22:25:24 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26407
	for <ietf-web-archive@odin.ietf.org>; Thu, 8 Jan 2004 22:25:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aen6J-000324-JK
	for ietf-list@asgard.ietf.org; Thu, 08 Jan 2004 22:14:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aen4s-0002xz-Bc
	for ietf@asgard.ietf.org; Thu, 08 Jan 2004 22:12:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25769
	for <ietf@ietf.org>; Thu, 8 Jan 2004 22:12:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aen4g-0005pW-00
	for ietf@ietf.org; Thu, 08 Jan 2004 22:12:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AemyF-0005bB-00
	for ietf@ietf.org; Thu, 08 Jan 2004 22:06:00 -0500
Received: from [202.108.44.205] (helo=163.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1Aemv3-0005P4-00
	for ietf@ietf.org; Thu, 08 Jan 2004 22:02:41 -0500
Received: from wl302 (unknown [211.67.24.168])
	by 192.168.1.205 (Coremail) with SMTP id pZ8IAK8Z_j8hABio.1
	for <gk@ninebynine.org>; Fri, 09 Jan 2004 11:02:14 +0800 (CST)
X-Originating-IP: [211.67.24.168]
Message-ID: <001401c3d65d$3ef71a70$a81843d3@wl302>
From: "wang liang" <wangliang_f@163.com>
To: "Graham Klyne" <GK@ninebynine.org>
Cc: <ietf@ietf.org>
References: <5.1.0.14.2.20040108091726.00b82008@127.0.0.1>
Subject: Re: Building a new work group for public information retrieval  protocol, ask for advices.
Date: Fri, 9 Jan 2004 11:04:00 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The main aim of DRIS is to build the information retrieval infrastructure
for Internet. XML/RDF/Webservice is just tools.
In fact, in IRTF,http://www.irtf.org,an organization for the "evolution of
the future Internet"(supported by IETF)
There has been a work group "Information Infrastructure Architecture".

This proposed group can be regarded as its continued work.


> I think it's not clear that this is an appropriate IETF working group that
> is being proposed:
>





From owner-ietf@ietf.org  Thu Jan  8 22:34:56 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26998
	for <ietf-web-archive@odin.ietf.org>; Thu, 8 Jan 2004 22:34:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AenMl-0003un-En
	for ietf-list@asgard.ietf.org; Thu, 08 Jan 2004 22:31:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AenKT-0003ji-1L
	for ietf@asgard.ietf.org; Thu, 08 Jan 2004 22:28:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26563
	for <ietf@ietf.org>; Thu, 8 Jan 2004 22:28:54 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AenKR-0006wC-00
	for ietf@ietf.org; Thu, 08 Jan 2004 22:28:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AenIX-0006n4-00
	for ietf@ietf.org; Thu, 08 Jan 2004 22:26:58 -0500
Received: from h80ad25d9.async.vt.edu ([128.173.37.217] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AenGz-0006fe-00
	for ietf@ietf.org; Thu, 08 Jan 2004 22:25:21 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i093P7Ga003975;
	Thu, 8 Jan 2004 22:25:07 -0500
Message-Id: <200401090325.i093P7Ga003975@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Fred Baker <fred@cisco.com>
Cc: ietf@ietf.org, isdf@isoc.org
Subject: Re: [isdf] Re: www.internetforce.org 
In-Reply-To: Your message of "Thu, 08 Jan 2004 15:37:18 PST."
             <6.0.1.1.2.20040108153525.041ccb90@mira-sjc5-b.cisco.com> 
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org> <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org> <240387438.1073576717@scan.jck.com> <6.0.1.1.2.20040108232213.03f8beb0@mail.utel.net>
            <6.0.1.1.2.20040108153525.041ccb90@mira-sjc5-b.cisco.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_2077242210P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 08 Jan 2004 22:25:07 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Thu, 08 Jan 2004 15:37:18 PST, Fred Baker said:
> At 02:32 PM 1/8/2004, jfcm wrote:
> >Could it not be useful to have a "List of Comments" (LOC) for each RFC? 
> >Where experience about the RFC reading, testing and implementation could 
> >be listed by the authors (or a successor) from experience and questions 
> >received.
> 
> These are usually found in the form of working group archives and 
> subsequent RFCs that update or obsolete the older ones, especially in the 
> case of standards track documents. The RFC Editor also keeps a log of notes 
> on RFCs when asked to.

Actually *finding* something in the working group archive can be.. interesting.

There is much that happens during the editing of a reply to an e-mail message
that is totally different than the sort of expository writing that a LOC would
need in order to be useful. They're different skill sets, they're different
mindsets, and vastly different assumptions.

For instance, this note probably won't stand well by itself 5 years from now,
because I'm writing to an audience that has Fred Baker's and jfcm's comments
fresh in their minds, and presumably have an interest in both the thread and
what I have to say in reply to Fred Baker (hopefully, those that aren't have
some combination of threading, killfiles, and delete keys ;)

I remember a few times going back to the big-internet and MIME/ESMTP mailing
lists, and even with the assist of actually having been a participant the first
time around, was unable to track down specific things I remember having been
written. Approaching it with nothing more than "Somebody mentioned something
about that issue way back when", if that much - now that would be downright
scary.

The recent discussion about RFCs, 'Updates', and similar topics would probably
be equally difficult to track down several years down the road.

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

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

iD8DBQE//h8TcC3lWbTT17ARAlptAJ4hPXpGVKWUAR9hO51ieEB0EG3g6gCfRrYD
T+zR1+I7ktgJbg3ufO5nkI8=
=a2dl
-----END PGP SIGNATURE-----

--==_Exmh_2077242210P--



From owner-ietf@ietf.org  Fri Jan  9 01:33:01 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01543
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 01:33:01 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aeq3D-0006Ax-2D
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 01:23:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aeq2k-00068e-Qc
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 01:22:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01214
	for <ietf@ietf.org>; Fri, 9 Jan 2004 01:22:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aeq2i-00073l-00
	for ietf@ietf.org; Fri, 09 Jan 2004 01:22:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aeq1K-0006xA-00
	for ietf@ietf.org; Fri, 09 Jan 2004 01:21:23 -0500
Received: from [63.247.76.239] (helo=montage.altserver.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aepzn-0006l2-00
	for ietf@ietf.org; Fri, 09 Jan 2004 01:19:47 -0500
Received: from f02m-17-233.d0.club-internet.fr ([212.195.212.233] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1Aepzd-00031c-Fv; Thu, 08 Jan 2004 22:19:44 -0800
Message-Id: <6.0.1.1.2.20040109065754.046c8b70@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 09 Jan 2004 07:03:19 +0100
To: ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: [isdf] Re: www.internetforce.org
Cc: isdf@isoc.org
In-Reply-To: <6.0.1.1.2.20040108153525.041ccb90@mira-sjc5-b.cisco.com >
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
 <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nos ense.org>
 <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
 <240387438.1073576717@scan.jck.com>
 <6.0.1.1.2.20040108232213.03f8beb0@mail.utel.net>
 <6.0.1.1.2.20040108153525.041ccb90@mira-sjc5-b.cisco.com >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 00:37 09/01/04, Fred Baker wrote:

>At 02:32 PM 1/8/2004, jfcm wrote:
>>Could it not be useful to have a "List of Comments" (LOC) for each RFC? 
>>Where experience about the RFC reading, testing and implementation could 
>>be listed by the authors (or a successor) from experience and questions 
>>received.
>
>These are usually found in the form of working group archives and 
>subsequent RFCs that update or obsolete the older ones, especially in the 
>case of standards track documents. The RFC Editor also keeps a log of 
>notes on RFCs when asked to.
>
>It's not obvious, at least to me, why a second mechanism is required if th 
>one that is there works... .

Let say that an RFC is an IETF deliverable. After-delivery 
support/maintenance is not a requirment for the delivery to exist but an 
usual user expectation. An RFC is a project imposed to the world before it 
is validated. A market standard is the desciption of what works and is 
adopted. We might find this way a fortunate compromise? 




From owner-ietf@ietf.org  Fri Jan  9 03:30:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17358
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 03:30:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AerrS-00015k-OY
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 03:19:18 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aerqx-00013e-3a
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 03:18:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17088
	for <ietf@ietf.org>; Fri, 9 Jan 2004 03:18:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aerqu-0004Sf-00
	for ietf@ietf.org; Fri, 09 Jan 2004 03:18:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aerp4-0004PL-00
	for ietf@ietf.org; Fri, 09 Jan 2004 03:16:51 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AernZ-0004Li-00
	for ietf@ietf.org; Fri, 09 Jan 2004 03:15:17 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AernY-000GG4-00; Fri, 09 Jan 2004 03:15:16 -0500
Date: Fri, 09 Jan 2004 03:15:16 -0500
From: John C Klensin <john-ietf@jck.com>
To: jfcm <info@utel.net>, Wawa Ngenge <ngenge@confucius.gnacademy.org>
cc: ietf@ietf.org, isdf@isoc.org
Subject: Re: [isdf] Re: www.internetforce.org
Message-ID: <281785696.1073618116@scan.jck.com>
In-Reply-To: <6.0.1.1.2.20040108232213.03f8beb0@mail.utel.net>
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
 <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nos
  ense.org>
 <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
 <240387438.1073576717@scan.jck.com>
 <6.0.1.1.2.20040108232213.03f8beb0@mail.utel.net>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Thursday, 08 January, 2004 23:32 +0100 jfcm <info@utel.net> 
wrote:

> At 21:45 08/01/04, John C Klensin wrote:
>> A better answer would have been "the term 'request for
>> comment' is  historical, dating from a time when the
>> preferred way to make a formal  comment on a document
>> involved writing another document, which then was  numbered
>> into the series".  That mechanism is still available,
>> although  usually very slow.  But documents that become RFCs
>> are now first posted as  Internet Drafts (see
>> http://www.ietf.org/ID); comments on those are both
>> solicited and, usually, handled very quickly.
>>
>> Today, the RFC Series, despite retention of the original name
>> and  numbering series, acts as a permanent, archival,
>> repository of  information, decisions taken, and standards
>> published.  As such, documents  in the series are subjected
>> to review and editing processes (which differ  somewhat
>> depending on the type of document and are appropriate for
>> conventional references from conventional documents.  Running
>> conversations, logs of comments, etc., are not well suited
>> for that  archival and reference role, regardless of their
>> other advantages and  disadvantages.
>
>
> Could it not be useful to have a "List of Comments" (LOC) for
> each RFC? Where experience about the RFC reading, testing and
> implementation could be listed by the authors (or a successor)
> from experience and questions received. It would avoid the
> same questions to be debated again and again and it would help
> further thinking. These comments could start with a summary of
> the WG debated issues, explaining the whys of some options. I
> suppose the implementation would be easy enough since it would
> follow the same numbering scheme and titles. Such a LOC being
> an updated appendix could be reviewed and help preparing
> replacements.

Jefsey,

There are many ways by which almost any system could be, or 
could have been, designed or evolved.  Typically each has its 
advantages and disadvantages, even if, overall, the difference 
in effect is slight.  Certainly the Internet standards and 
definitions process could have evolved with RFCs and LOCs or 
some other pieces.  Certainly the idea of "standards" could have 
been put in place early in the process, and we could have called 
what are now "Internet-Drafts" "RFCs" instead, could have had 
standards in a separate series, and had an additional separate 
series for experimental and informational documents (we might 
even have followed the lead of some other bodies and called the 
latter series "technical reports", which they are definitely 
not).    And certainly we could have adopted a distinct 
numbering system and document series for standards along with a 
regular review model, standing WGs to which each standard is 
applied, and revisions that share the number but have different 
dates or revision numbers.

In some cases, the fact that we didn't go down those paths is an 
historical accident.  In others, it was a very deliberate 
decision.  And, in some cases, the path that was chosen was very 
important in shaping how the IETF operates or reflects the 
nature of those operations (e.g., the fact that we generally 
close WGs that have finished their work, rather than encouraging 
them to find new things to keep them busy has, I believe, been 
very important in keeping us from developing many standards that 
no one wants and that are out of touch with reality).

But we do things in a particular way that mostly works (although 
it should probably be more effectively and accessibly 
documented), and, while we might tune things differently or use 
different terminology if we were starting over today, what 
purpose would it serve to develop redundant mechanisms that 
would require extra volunteer or staff effort to make work and 
keep working and that would leave people uncertain as to where 
to go for information?  And what purpose is served by proposing 
such an action?

Regards,
    john






From owner-ietf@ietf.org  Fri Jan  9 09:58:56 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02544
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 09:58:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aexsz-0007kl-O4
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 09:45:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aexsb-0007iv-77
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 09:44:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02318
	for <ietf@ietf.org>; Fri, 9 Jan 2004 09:44:50 -0500 (EST)
From: john.loughney@kolumbus.fi
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AexsZ-0005Sz-00
	for ietf@ietf.org; Fri, 09 Jan 2004 09:44:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aexqs-0005PP-00
	for ietf@ietf.org; Fri, 09 Jan 2004 09:43:06 -0500
Received: from cust-smtp1.radiolinja.fi ([213.161.33.208])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AexpD-0005G7-00
	for ietf@ietf.org; Fri, 09 Jan 2004 09:41:23 -0500
Received: from [10.64.9.86] (rl045112.radiolinja.net [213.161.45.112])
	by cust-smtp1.radiolinja.fi (Postfix) with ESMTP
	id 5666F40006; Fri,  9 Jan 2004 16:40:41 +0200 (EET)
Reply-To: john.loughney@kolumbus.fi
To: "jfcm" <info@utel.net>
Cc: "John C Klensin" <john-ietf@jck.com>,
        "Wawa Ngenge" <ngenge@confucius.gnacademy.org>, ietf@ietf.org,
        isdf@isoc.org
Subject: Re: [isdf] Re: www.internetforce.org
Date: Fri,  9 Jan 2004 16:40:34 +0200
Message-ID: <ZKBxf5krLWzT.BznZyrbh@smtp.mobiili.net>
X-Mailer: Symbian OS Email Version 7.0
MIME-Version: 1.0
Content-Language: i-default
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Folks,

I wrote up a draft, =
http://www.ietf.org/internet-drafts/draft-loughney-what-standards-00.txt =
which discusses similar issues. I'd appreciate comments, as I intend on =
updating the document soon.

Thanks,
John
-- original message --
Subject:	Re: [isdf] Re: www.internetforce.org
From:	"jfcm" <info@utel.net>
Date:		8th January 2004 11:32:43 pm

At 21:45 08/01/04, John C Klensin wrote:
>A better answer would have been "the term 'request for comment' is =

>historical, dating from a time when the preferred way to make a formal =

>comment on a document involved writing another document, which then was =

>numbered into the series".  That mechanism is still available, although =

>usually very slow.  But documents that become RFCs are now first posted as =

>Internet Drafts (see http://www.ietf.org/ID); comments on those are both =

>solicited and, usually, handled very quickly.
>
>Today, the RFC Series, despite retention of the original name and=20
>numbering series, acts as a permanent, archival, repository of=20
>information, decisions taken, and standards published.  As such, documents =

>in the series are subjected to review and editing processes (which differ =

>somewhat depending on the type of document and are appropriate for =

>conventional references from conventional documents.  Running=20
>conversations, logs of comments, etc., are not well suited for that =

>archival and reference role, regardless of their other advantages and =

>disadvantages.


Could it not be useful to have a "List of Comments" (LOC) for each RFC? =

Where experience about the RFC reading, testing and implementation could be =

listed by the authors (or a successor) from experience and questions =

received. It would avoid the same questions to be debated again and again =

and it would help further thinking. These comments could start with a =

summary of the WG debated issues, explaining the whys of some options. I =

suppose the implementation would be easy enough since it would follow the =

same numbering scheme and titles. Such a LOC being an updated appendix =

could be reviewed and help preparing replacements.
jfc






From owner-ietf@ietf.org  Fri Jan  9 10:41:22 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06922
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 10:41:22 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AeygM-00088J-4n
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 10:36:18 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AeyfT-000808-OP
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 10:35:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05636
	for <ietf@ietf.org>; Fri, 9 Jan 2004 10:35:21 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aeycz-0007fq-01
	for ietf@ietf.org; Fri, 09 Jan 2004 10:32:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeyPT-0006vF-00
	for ietf@ietf.org; Fri, 09 Jan 2004 10:18:52 -0500
Received: from h80ad25ea.async.vt.edu ([128.173.37.234] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeyL9-0006eg-00
	for ietf@ietf.org; Fri, 09 Jan 2004 10:14:24 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i09FDsCq030865;
	Fri, 9 Jan 2004 10:13:54 -0500
Message-Id: <200401091513.i09FDsCq030865@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: jfcm <info@utel.net>
Cc: ietf@ietf.org, isdf@isoc.org
Subject: Re: [isdf] Re: www.internetforce.org 
In-Reply-To: Your message of "Fri, 09 Jan 2004 07:03:19 +0100."
             <6.0.1.1.2.20040109065754.046c8b70@mail.utel.net> 
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org> <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org> <240387438.1073576717@scan.jck.com> <6.0.1.1.2.20040108232213.03f8beb0@mail.utel.net> <6.0.1.1.2.20040108153525.041ccb90@mira-sjc5-b.cisco.com>
            <6.0.1.1.2.20040109065754.046c8b70@mail.utel.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-159465412P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 09 Jan 2004 10:13:54 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Fri, 09 Jan 2004 07:03:19 +0100, jfcm said:

> is validated. A market standard is the desciption of what works and is 
> adopted. We might find this way a fortunate compromise? 

Unfortunately, "market standards" often include borken things that are adopted
via forced-feeding.  More than one vendor has done this, and some research
would probably find at least one example at each of the 7 OSI layers.

Current pet peeve - 100BaseT auto-negotiation on older gear, especially when
"the other end" is nailed to something other than auto. (Co-worker's comment on
that one - "Didn't we go through that whole subnet and clean that up twice
already?" :)  So much for market "standards". (Yes, I know it's better now.
The hardware involved is many moons old).


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

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

iD8DBQE//sUycC3lWbTT17ARArf/AKDOOPkom/+02WmgIr/NVAFvnW7sSgCgq3HZ
AQv2ev4p1AWdBevZlc/MSOk=
=BILp
-----END PGP SIGNATURE-----

--==_Exmh_-159465412P--



From owner-ietf@ietf.org  Fri Jan  9 11:48:19 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13101
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 11:48:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aezfy-0004Di-MO
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 11:39:58 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aeze3-00048P-QX
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 11:37:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12433
	for <ietf@ietf.org>; Fri, 9 Jan 2004 11:37:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aeze2-0004xz-00
	for ietf@ietf.org; Fri, 09 Jan 2004 11:37:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aezc9-0004gE-00
	for ietf@ietf.org; Fri, 09 Jan 2004 11:36:03 -0500
Received: from 82-35-77-212.cable.ubr02.dals.blueyonder.co.uk ([82.35.77.212] helo=DarkLord.Sabahattin-Gucukoglu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AezZq-0004HF-00
	for ietf@ietf.org; Fri, 09 Jan 2004 11:33:38 -0500
Received: from Spooler by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v3.32) ID MO00010D;
    9 Jan 04 16:31:54 -0000
Received: from spooler by sabahattin-gucukoglu.com (Mercury/32 v3.32); 9 Jan 04 16:31:51 -0000
Received: from aurora (192.168.1.3) by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v3.32) with ESMTP ID MG00010B;
   9 Jan 04 16:31:49 -0000
From: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
Organization: I need more of this!
To: ietf@ietf.org
Date: Fri, 09 Jan 2004 16:28:13 -0000
MIME-Version: 1.0
Subject: SMTP Minimum Retry Period - Proposal To Modify Mx
Message-ID: <3FFED69D.16780.9223C3@localhost>
X-PM-Encryptor: QDPGP, 4
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi people,

I have a friend whose on ADSL and who wants to run his own email service, 
but is periodically disconnected.  He likes his mail delivered straight to 
his primary host, but his mate is there across the other side of the 
country if ever he's out as a backup MX.  Now, every time he uses the 
connection, which is at least once every few hours and at most once a day, 
his connection automagically reestablishes itself.  While he's been down, 
though, any mail destined for him has gone to his mate, who only delivers 
mail once every four hours or so.  By misfortune, my friend has gone down 
just as a mail was being queued for sending, in a place far away.  Being 
down, he can't take the mail, so his mate takes it for him.  He must wait 
four whole hours, assuming he has come up after the delivery of that 
message to his mate, even if the originating client was willing to deliver 
it sooner - say, thirty minutes, if his mate hadn't been around.  There's 
just one more condition - his mate, though great as mates go, is an anti-
RBL purist.  He refuses to use RBLs.  His mate is picking up spam which he 
would have rejected, had he been responsible, and it isn't reasonable to 
parse the mail after the mail is accepted, in particular because he's 
serving other people and doesn't justify this kind of intrusive filtering.

Now, all that was mostly hypothetical - based on a true story.  If my 
friend is some poor soul on ADSL, and his mate (that is, friend, just in 
case - buddy for the Americans) is a dynamic service provider with backup 
MX facilities or some organisation who can't reasonably be expected to 
alter their mail service policies to be in line with that of my friends 
who are of my anti-spam, direct-to-destination kind with no wish to be at 
the mercy of our ISPs, we need some mechanism to tell the SMTP client to 
keep trying to deliver to a particular MX(es), for a particular time(s).

My proposal: an extension to the MX record in the DNS, which must be 
backward compatible with existing MX records - that is, non-conformant 
mailers must not be confused by the new form of the record.  The creation 
of a new record type must only be necessary if that record type may 
facilitate many such extensions, not just this one.  This use of the MX 
might look like:
example.org: mx 10 example.org 86400
(Or, if the record - new or existing - is used extensibly, something like 
"mx 10 example.org MRP86400")
Where 86400 is the minimum number of seconds (1 day) for which the MX must 
be tried before those of lower priority must be tried.  If other MX 
records exist with same preference, then the same rule applies to those 
hosts, except that the delivery timeouts occur in parallel, and no MXs of 
lower preferences are to be tried until all MXs at this preference have 
been tried - that is, if:
mx 10 mx1.example.org 60
mx 10 mx2.example.org 30
mx 20 mx3.example.org
Then mx1.example.org and mx2.example.org will be tried simultaneously 
(that is, one after another but immediately following as in normal MX 
selection and delivery attempt behaviour), with the client giving delivery 
attempts whenever it usually does at whatever intervals it normally uses 
until the timeout occurs on mx2, at which point only mx1 is continually 
assaulted with the same algorithms as before, until it to is deemed 
unusable - 30 seconds later (hypothetical numbers, we'd normally be 
talking many hours!).  Only at this point is mx3 tried, which may or may 
not have such a minimum time given, and the same algorithm procedure is 
used at this preference.  As you see here the mx3 is listed without the 
MRP, which may be away of avoiding compatibility issues.

Where local policy dictates differing delivery times and intervals, the 
time given in the DNS must always be respected - so, if you deliver first 
at 30 minutes, then at 60 following, then 2 hours, then 4 etc. in a 
typical backoff style, then the sum of these times preceding must be 
waited against the value in DNS (in seconds).  If the total time spent 
attempting delivery to this host is now exceeded, then - at discretion of 
administrator - the unreachable host may be tried once more.  In any 
event, it is now permissible to proceed to lower-priority MXs.

Since this is meant to be backwards-compatible, there's a possible 
argument that mandating the attempts for the MRP for compliant systems is 
a bit counter-intuitive; I'm hoping that enough systems could do this to 
make it worthwhile, and there's no other way of achieving the same thing 
without an MX knowing when another MX of higher preference was both 
available and not available (the latter obviously being very hard to 
advertise, because it aint available!) with which knowledge the MX could 
either accept the mail or refuse to accept mail on the grounds that the 
higher MX was already available.

Of course, this little flash of brilliance ( :-P ) is only going to work 
if we can bend the DNS without anyone noticing.  Which, chances are, they 
will.  RFC 2821 which replaced RFC 974 before it on this matter makes no 
reference to the exact way in which MX records should be parsed, so that 
it could be chancy.

Still, what do you all think?

Cheers,
Sabahattin
- -- 
Thought for the day:
    Bagpipes (n): an octopus wearing a kilt.

Latest PGP Public key blocks?  Send any mail to:
<PGPPublicKey@sabahattin-gucukoglu.com>

Sabahattin Gucukoglu
Phone: +44 (0)20 7,502-1615
Mobile: +44 (0)7986 053399
http://www.sabahattin-gucukoglu.com/
Email/MSN: <mail@Sabahattin-Gucukoglu.com>


-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0 -- QDPGP 2.70 
Comment: Previous key for <Sabahattin_Gucukoglu@mailandnews.co.uk> revoked due to invalidated primary address.

iQA/AwUBP/7WniNEOmEWtR2TEQInAACgqw1sV1eESQ1bGri/5vRYH1oGaVsAoMpI
eBN1NlE0QJBAhldfPkQpDnFW
=VytL
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Fri Jan  9 11:48:20 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13119
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 11:48:20 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aezk9-0004Oe-FD
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 11:44:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aezi3-0004Hf-VD
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 11:42:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12636
	for <ietf@ietf.org>; Fri, 9 Jan 2004 11:42:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aezi2-0005Hm-00
	for ietf@ietf.org; Fri, 09 Jan 2004 11:42:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AezgB-0005Ae-00
	for ietf@ietf.org; Fri, 09 Jan 2004 11:40:12 -0500
Received: from 82-35-77-212.cable.ubr02.dals.blueyonder.co.uk ([82.35.77.212] helo=DarkLord.Sabahattin-Gucukoglu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aezem-00053W-00
	for ietf@ietf.org; Fri, 09 Jan 2004 11:38:44 -0500
Received: from Spooler by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v3.32) ID MO000110;
    9 Jan 04 16:37:00 -0000
Received: from spooler by sabahattin-gucukoglu.com (Mercury/32 v3.32); 9 Jan 04 16:36:56 -0000
Received: from aurora (192.168.1.3) by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v3.32) with ESMTP ID MG00010E;
   9 Jan 04 16:36:55 -0000
From: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
Organization: I need more of this!
To: ietf@ietf.org
Date: Fri, 09 Jan 2004 16:33:20 -0000
MIME-Version: 1.0
Subject: SMTP Minimum Retry Period - Proposal To Modify Mx
Message-ID: <3FFED7D0.30933.96D04A@localhost>
X-PM-Encryptor: QDPGP, 4
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi people,

I have a friend whose on ADSL and who wants to run his own email service, 
but is periodically disconnected.  He likes his mail delivered straight to 
his primary host, but his mate is there across the other side of the 
country if ever he's out as a backup MX.  Now, every time he uses the 
connection, which is at least once every few hours and at most once a day, 
his connection automagically reestablishes itself.  While he's been down, 
though, any mail destined for him has gone to his mate, who only delivers 
mail once every four hours or so.  By misfortune, my friend has gone down 
just as a mail was being queued for sending, in a place far away.  Being 
down, he can't take the mail, so his mate takes it for him.  He must wait 
four whole hours, assuming he has come up after the delivery of that 
message to his mate, even if the originating client was willing to deliver 
it sooner - say, thirty minutes, if his mate hadn't been around.  There's 
just one more condition - his mate, though great as mates go, is an anti-
RBL purist.  He refuses to use RBLs.  His mate is picking up spam which he 
would have rejected, had he been responsible, and it isn't reasonable to 
parse the mail after the mail is accepted, in particular because he's 
serving other people and doesn't justify this kind of intrusive filtering.

Now, all that was mostly hypothetical - based on a true story.  If my 
friend is some poor soul on ADSL, and his mate (that is, friend, just in 
case - buddy for the Americans) is a dynamic service provider with backup 
MX facilities or some organisation who can't reasonably be expected to 
alter their mail service policies to be in line with that of my friends 
who are of my anti-spam, direct-to-destination kind with no wish to be at 
the mercy of our ISPs, we need some mechanism to tell the SMTP client to 
keep trying to deliver to a particular MX(es), for a particular time(s).

My proposal: an extension to the MX record in the DNS, which must be 
backward compatible with existing MX records - that is, non-conformant 
mailers must not be confused by the new form of the record.  The creation 
of a new record type must only be necessary if that record type may 
facilitate many such extensions, not just this one.  This use of the MX 
might look like:
example.org: mx 10 example.org 86400
(Or, if the record - new or existing - is used extensibly, something like 
"mx 10 example.org MRP86400")
Where 86400 is the minimum number of seconds (1 day) for which the MX must 
be tried before those of lower priority must be tried.  If other MX 
records exist with same preference, then the same rule applies to those 
hosts, except that the delivery timeouts occur in parallel, and no MXs of 
lower preferences are to be tried until all MXs at this preference have 
been tried - that is, if:
mx 10 mx1.example.org 60
mx 10 mx2.example.org 30
mx 20 mx3.example.org
Then mx1.example.org and mx2.example.org will be tried simultaneously 
(that is, one after another but immediately following as in normal MX 
selection and delivery attempt behaviour), with the client giving delivery 
attempts whenever it usually does at whatever intervals it normally uses 
until the timeout occurs on mx2, at which point only mx1 is continually 
assaulted with the same algorithms as before, until it to is deemed 
unusable - 30 seconds later (hypothetical numbers, we'd normally be 
talking many hours!).  Only at this point is mx3 tried, which may or may 
not have such a minimum time given, and the same algorithm procedure is 
used at this preference.  As you see here the mx3 is listed without the 
MRP, which may be away of avoiding compatibility issues.

Where local policy dictates differing delivery times and intervals, the 
time given in the DNS must always be respected - so, if you deliver first 
at 30 minutes, then at 60 following, then 2 hours, then 4 etc. in a 
typical backoff style, then the sum of these times preceding must be 
waited against the value in DNS (in seconds).  If the total time spent 
attempting delivery to this host is now exceeded, then - at discretion of 
administrator - the unreachable host may be tried once more.  In any 
event, it is now permissible to proceed to lower-priority MXs.

Since this is meant to be backwards-compatible, there's a possible 
argument that mandating the attempts for the MRP for compliant systems is 
a bit counter-intuitive; I'm hoping that enough systems could do this to 
make it worthwhile, and there's no other way of achieving the same thing 
without an MX knowing when another MX of higher preference was both 
available and not available (the latter obviously being very hard to 
advertise, because it aint available!) with which knowledge the MX could 
either accept the mail or refuse to accept mail on the grounds that the 
higher MX was already available.

Of course, this little flash of brilliance ( :-P ) is only going to work 
if we can bend the DNS without anyone noticing.  Which, chances are, they 
will.  RFC 2821 which replaced RFC 974 before it on this matter makes no 
reference to the exact way in which MX records should be parsed, so that 
it could be chancy.

Still, what do you all think?

Cheers,
Sabahattin
- -- 
Thought for the day:
    The only thing that hurts more than paying income tax
    is not having to pay income tax.

Latest PGP Public key blocks?  Send any mail to:
<PGPPublicKey@sabahattin-gucukoglu.com>

Sabahattin Gucukoglu
Phone: +44 (0)20 7,502-1615
Mobile: +44 (0)7986 053399
http://www.sabahattin-gucukoglu.com/
Email/MSN: <mail@Sabahattin-Gucukoglu.com>


-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0 -- QDPGP 2.70 
Comment: Previous key for <Sabahattin_Gucukoglu@mailandnews.co.uk> revoked due to invalidated primary address.

iQA/AwUBP/7X0CNEOmEWtR2TEQLbSQCfdgl36Ng3pnane8nV3Jbd+OMxuV4AoJC7
e7RPQCrDZHvLgNwqRC++nncs
=ed5n
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Fri Jan  9 12:30:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15407
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 12:30:16 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af0On-0006pn-R6
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 12:26:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af0OW-0006nQ-Lm
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 12:26:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15169
	for <ietf@ietf.org>; Fri, 9 Jan 2004 12:25:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af0OV-0000iL-00
	for ietf@ietf.org; Fri, 09 Jan 2004 12:25:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af0MP-0000Tq-00
	for ietf@ietf.org; Fri, 09 Jan 2004 12:23:50 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af0Hn-0007i8-00
	for ietf@ietf.org; Fri, 09 Jan 2004 12:19:03 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 3367961B9B; Fri,  9 Jan 2004 18:18:22 +0100 (CET)
Date: Fri, 09 Jan 2004 09:18:20 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>, ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Message-ID: <2067122895.1073639900@halvestr-w2k1>
In-Reply-To: <3FFED7D0.30933.96D04A@localhost>
References: <3FFED7D0.30933.96D04A@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Why doesn't your friend use ETRN to trigger delivery of his queued mail 
from his mate whenever he gets online?

That way, the 4-hour delay is avoided without requiring global changes to 
the Internet infrastructure....




From owner-ietf@ietf.org  Fri Jan  9 12:30:17 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15425
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 12:30:17 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af0Mr-0006l9-Gm
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 12:24:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af0LJ-0006gS-D8
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 12:22:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14771
	for <ietf@ietf.org>; Fri, 9 Jan 2004 12:22:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af0LH-0000Ex-00
	for ietf@ietf.org; Fri, 09 Jan 2004 12:22:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af09J-0007JW-00
	for ietf@ietf.org; Fri, 09 Jan 2004 12:10:17 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50] helo=smtp.cs.utk.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af02z-0006jm-00
	for ietf@ietf.org; Fri, 09 Jan 2004 12:03:45 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 2EE8DAFF2C; Fri,  9 Jan 2004 12:03:09 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 30097-04; Fri,  9 Jan 2004 12:03:08 -0500 (EST)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id DB6CBAFF29; Fri,  9 Jan 2004 12:03:07 -0500 (EST)
Date: Fri, 9 Jan 2004 12:03:07 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Message-Id: <20040109120307.2a39485e.moore@cs.utk.edu>
In-Reply-To: <3FFED69D.16780.9223C3@localhost>
References: <3FFED69D.16780.9223C3@localhost>
X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> There's 
> just one more condition - his mate, though great as mates go, is an anti-
> RBL purist.  He refuses to use RBLs.

His mate is a wise man.  RBLs are a really terrible idea, and they've
caused a lot of valid mail to be rejected.  There's really no way to
reliably determine that a message is spam based on the IP address or
sender's domain name.  The most you should do with RBLs is delay or
rate-limit mail from the blacklisted sites, you should never reject
such mail.

> My proposal: an extension to the MX record in the DNS, which must be 
> backward compatible with existing MX records - that is, non-conformant 
> mailers must not be confused by the new form of the record.

Doesn't seem like a good idea in general, nor does it seem necessary. 
It's perfectly reasonable for the secondary MX to be explicitly 
configured to flush its mail queue for the primary MX at pre-determined
times (as in a cron job).  It's also perfectly reasonable for the
primary MX to contact the secondary MX at regular intervals and
(using any of a variety of mechanisms) say "please give me my mail".

So it doesn't seem like we need a new DNS RR to solve this problem.

Keith



From owner-ietf@ietf.org  Fri Jan  9 12:30:21 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15444
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 12:30:21 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af0Iz-0006cd-Be
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 12:20:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af0Iv-0006aZ-Ta
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 12:20:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14650
	for <ietf@ietf.org>; Fri, 9 Jan 2004 12:20:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af0Ik-0007m4-00
	for ietf@ietf.org; Fri, 09 Jan 2004 12:20:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af05B-00074K-00
	for ietf@ietf.org; Fri, 09 Jan 2004 12:06:03 -0500
Received: from 82-35-77-212.cable.ubr02.dals.blueyonder.co.uk ([82.35.77.212] helo=DarkLord.Sabahattin-Gucukoglu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AezyY-0006Tn-00
	for ietf@ietf.org; Fri, 09 Jan 2004 11:59:10 -0500
Received: from Spooler by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v3.32) ID MO00011B;
    9 Jan 04 16:57:26 -0000
Received: from spooler by sabahattin-gucukoglu.com (Mercury/32 v3.32); 9 Jan 04 16:57:08 -0000
From: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
Organization: I need more of this!
To: ietf@ietf.org
Date: Fri, 09 Jan 2004 16:48:28 -0000
MIME-Version: 1.0
Subject: SMTP Minimum Retry Period - Proposal To Modify Mx
Message-ID: <3FFEDB5C.12870.A4AAFD@localhost>
X-PM-Encryptor: QDPGP, 4
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi people,

I have a friend whose on ADSL and who wants to run his own email service, 
but is periodically disconnected.  He likes his mail delivered straight to 
his primary host, but his mate is there across the other side of the 
country if ever he's out as a backup MX.  Now, every time he uses the 
connection, which is at least once every few hours and at most once a day, 
his connection automagically reestablishes itself.  While he's been down, 
though, any mail destined for him has gone to his mate, who only delivers 
mail once every four hours or so.  By misfortune, my friend has gone down 
just as a mail was being queued for sending, in a place far away.  Being 
down, he can't take the mail, so his mate takes it for him.  He must wait 
four whole hours, assuming he has come up after the delivery of that 
message to his mate, even if the originating client was willing to deliver 
it sooner - say, thirty minutes, if his mate hadn't been around.  There's 
just one more condition - his mate, though great as mates go, is an anti-
RBL purist.  He refuses to use RBLs.  His mate is picking up spam which he 
would have rejected, had he been responsible, and it isn't reasonable to 
parse the mail after the mail is accepted, in particular because he's 
serving other people and doesn't justify this kind of intrusive filtering.

Now, all that was mostly hypothetical - based on a true story.  If my 
friend is some poor soul on ADSL, and his mate (that is, friend, just in 
case - buddy for the Americans) is a dynamic service provider with backup 
MX facilities or some organisation who can't reasonably be expected to 
alter their mail service policies to be in line with that of my friends 
who are of my anti-spam, direct-to-destination kind with no wish to be at 
the mercy of our ISPs, we need some mechanism to tell the SMTP client to 
keep trying to deliver to a particular MX(es), for a particular time(s).

My proposal: an extension to the MX record in the DNS, which must be 
backward compatible with existing MX records - that is, non-conformant 
mailers must not be confused by the new form of the record.  The creation 
of a new record type must only be necessary if that record type may 
facilitate many such extensions, not just this one.  This use of the MX 
might look like:
example.org: mx 10 example.org 86400
(Or, if the record - new or existing - is used extensibly, something like 
"mx 10 example.org MRP86400")
Where 86400 is the minimum number of seconds (1 day) for which the MX must 
be tried before those of lower priority must be tried.  If other MX 
records exist with same preference, then the same rule applies to those 
hosts, except that the delivery timeouts occur in parallel, and no MXs of 
lower preferences are to be tried until all MXs at this preference have 
been tried - that is, if:
mx 10 mx1.example.org 60
mx 10 mx2.example.org 30
mx 20 mx3.example.org
Then mx1.example.org and mx2.example.org will be tried simultaneously 
(that is, one after another but immediately following as in normal MX 
selection and delivery attempt behaviour), with the client giving delivery 
attempts whenever it usually does at whatever intervals it normally uses 
until the timeout occurs on mx2, at which point only mx1 is continually 
assaulted with the same algorithms as before, until it to is deemed 
unusable - 30 seconds later (hypothetical numbers, we'd normally be 
talking many hours!).  Only at this point is mx3 tried, which may or may 
not have such a minimum time given, and the same algorithm procedure is 
used at this preference.  As you see here the mx3 is listed without the 
MRP, which may be away of avoiding compatibility issues.

Where local policy dictates differing delivery times and intervals, the 
time given in the DNS must always be respected - so, if you deliver first 
at 30 minutes, then at 60 following, then 2 hours, then 4 etc. in a 
typical backoff style, then the sum of these times preceding must be 
waited against the value in DNS (in seconds).  If the total time spent 
attempting delivery to this host is now exceeded, then - at discretion of 
administrator - the unreachable host may be tried once more.  In any 
event, it is now permissible to proceed to lower-priority MXs.

Since this is meant to be backwards-compatible, there's a possible 
argument that mandating the attempts for the MRP for compliant systems is 
a bit counter-intuitive; I'm hoping that enough systems could do this to 
make it worthwhile, and there's no other way of achieving the same thing 
without an MX knowing when another MX of higher preference was both 
available and not available (the latter obviously being very hard to 
advertise, because it aint available!) with which knowledge the MX could 
either accept the mail or refuse to accept mail on the grounds that the 
higher MX was already available.

Of course, this little flash of brilliance ( :-P ) is only going to work 
if we can bend the DNS without anyone noticing.  Which, chances are, they 
will.  RFC 2821 which replaced RFC 974 before it on this matter makes no 
reference to the exact way in which MX records should be parsed, so that 
it could be chancy.

Still, what do you all think?

Cheers,
Sabahattin
- -- 
Thought for the day:
    Book (n): a utensil used to pass time while waiting
    for the TV repairman.

Latest PGP Public key blocks?  Send any mail to:
<PGPPublicKey@sabahattin-gucukoglu.com>

Sabahattin Gucukoglu
Phone: +44 (0)20 7,502-1615
Mobile: +44 (0)7986 053399
http://www.sabahattin-gucukoglu.com/
Email/MSN: <mail@Sabahattin-Gucukoglu.com>


-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0 -- QDPGP 2.70 
Comment: Previous key for <Sabahattin_Gucukoglu@mailandnews.co.uk> revoked due to invalidated primary address.

iQA/AwUBP/7bXCNEOmEWtR2TEQJyuwCeIbafW2tUrQFEXF9UfJcU2yXmo8YAnj1G
Ym/1XpLknxQbZeEclG8gzoiR
=VDSt
-----END PGP SIGNATURE-----
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Fri Jan  9 13:14:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20279
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 13:14:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af11V-0001mI-FG
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 13:06:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af0zp-0001RW-6d
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 13:04:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19301
	for <ietf@ietf.org>; Fri, 9 Jan 2004 13:04:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af0zj-00062Q-00
	for ietf@ietf.org; Fri, 09 Jan 2004 13:04:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af0lT-00043D-00
	for ietf@ietf.org; Fri, 09 Jan 2004 12:49:43 -0500
Received: from apollo.ext.eurgw.xerox.com ([13.16.138.21] helo=apollo.eurgw.xerox.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af0hf-0003Eb-00
	for ietf@ietf.org; Fri, 09 Jan 2004 12:45:47 -0500
Received: from eurodns2.eur.xerox.com (eurodns2.eur.xerox.com [13.202.66.10])
	by apollo.eurgw.xerox.com (8.12.9-20030917/8.12.9) with ESMTP id i09HjGrt009028
	for <ietf@ietf.org>; Fri, 9 Jan 2004 17:45:16 GMT
Received: from eurdubmg03.eur.xerox.com (eurdubmg03.eur.xerox.com [13.202.66.60])
	by eurodns2.eur.xerox.com (8.12.9/8.12.9) with ESMTP id i09HjFF6017502
	for <ietf@ietf.org>; Fri, 9 Jan 2004 17:45:15 GMT
Received: from eurgbrbh03.emeacinops.xerox.com (unverified) by eurdubmg03.eur.xerox.com
 (Content Technologies SMTPRS 4.2.10) with ESMTP id <T6708259c130dca423c3dc@eurdubmg03.eur.xerox.com> for <ietf@ietf.org>;
 Fri, 9 Jan 2004 17:45:14 +0000
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.2657.72)
	id YJJZVSHV; Fri, 9 Jan 2004 17:45:14 -0000
Received: by gbrwgcbh01.wgc.gbr.xerox.com with Internet Mail Service (5.5.2657.72)
	id <V8CZPXDN>; Fri, 9 Jan 2004 17:46:10 -0000
Message-ID: <59697CCC6CE3D411B4CD00805FBB776704F7E200@gbrwgcms03.wgc.gbr.xerox.com>
From: "Brookes, Stuart P" <StuartP.Brookes@gbr.xerox.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: prtMarkerTable - Clarification required
Date: Fri, 9 Jan 2004 17:46:01 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3D6D7.FD2726A0"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_40_50,HTML_MESSAGE 
	autolearn=no version=2.60
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_01C3D6D7.FD2726A0
Content-Type: text/plain

All,
 
I require clarification on an object within the prtMarkerTable (Printer MIB,
RFC 1759).
 
The MIB objects in question are 'prtMarkerAddressabilityFeedDir' and
'prtMarkerAddressabilityFeedXDir'.
 
Are these objects referring to the dpi at the 'input stage of the
Interpreter', the 'output stage interpreter' or the actual space available
for marking after the 'interpreter output'?
 
Obviously, the dpi is different at all three stages.  So which stage do
these objects refer to?  I have looked at the RFC and not found a specific
answer to this.

I hope somebody can be of help.
 
Thanks
Stuart

------_=_NextPart_001_01C3D6D7.FD2726A0
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.2800.1276" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=587504017-09012004><FONT face=Arial 
size=2>All,</FONT></SPAN></DIV>
<DIV><SPAN class=587504017-09012004><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=587504017-09012004><FONT face=Arial size=2>I require 
clarification on an object within the prtMarkerTable (Printer MIB, RFC 
1759).</FONT></SPAN></DIV>
<DIV><SPAN class=587504017-09012004><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=587504017-09012004><FONT face=Arial size=2>The MIB objects in 
question are 'prtMarkerAddressabilityFeedDir' and 
'prtMarkerAddressabilityFeedXDir'.</FONT></SPAN></DIV>
<DIV><SPAN class=587504017-09012004><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=587504017-09012004><FONT face=Arial size=2>Are these objects 
referring to the dpi at the 'input stage of the Interpreter', the 'output stage 
interpreter' or the actual space available for marking after the 'interpreter 
output'?</FONT></SPAN></DIV>
<DIV><SPAN class=587504017-09012004><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=587504017-09012004><FONT face=Arial size=2>Obviously, the dpi 
is different at all three stages.&nbsp; So which stage do these objects refer 
to?&nbsp; </FONT></SPAN><SPAN class=587504017-09012004><FONT face=Arial size=2>I 
have looked at the RFC and not found a specific answer to this.</FONT></DIV>
<DIV><BR><SPAN class=587504017-09012004><FONT face=Arial size=2>I hope somebody 
can be of help.</FONT></SPAN></DIV>
<DIV><SPAN class=587504017-09012004><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=587504017-09012004><FONT face=Arial 
size=2>Thanks</FONT></SPAN></DIV>
<DIV><SPAN class=587504017-09012004><FONT face=Arial 
size=2>Stuart</FONT></SPAN></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C3D6D7.FD2726A0--



From owner-ietf@ietf.org  Fri Jan  9 14:39:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28225
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 14:39:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af2Ez-0004dQ-I7
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 14:24:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af2Eu-0004YM-Io
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 14:24:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26251
	for <ietf@ietf.org>; Fri, 9 Jan 2004 14:24:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af2Es-0001yX-00
	for ietf@ietf.org; Fri, 09 Jan 2004 14:24:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af1Pd-00022E-00
	for ietf@ietf.org; Fri, 09 Jan 2004 13:31:16 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af1Df-000701-00
	for ietf@ietf.org; Fri, 09 Jan 2004 13:18:51 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Af1DL-00084M-4M
	for ietf@ietf.org; Fri, 09 Jan 2004 13:18:31 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i09Hu4NM074582
	for ietf@ietf.org env-from <vjs>;
	Fri, 9 Jan 2004 10:56:04 -0700 (MST)
Date: Fri, 9 Jan 2004 10:56:04 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401091756.i09Hu4NM074582@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <20040109120307.2a39485e.moore@cs.utk.edu>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> ...
> His mate is a wise man.  RBLs are a really terrible idea, and they've
> caused a lot of valid mail to be rejected.  There's really no way to
> reliably determine that a message is spam based on the IP address or
> sender's domain name.  The most you should do with RBLs is delay or
> rate-limit mail from the blacklisted sites, you should never reject
> such mail.
> ..

It's never clear to me what Keith Moore means by "RBL" when he repeats
that claim.  Those three letters are a registered service mark for a
product that historically has been run so conservatively that claims
that should not be used to reject mail sound silly.  You would certainly
want to do more than just rate limit Cyberpromo's spam.

He might be referring to other DNS (or BGP) distributed, more or less
real time blacklists.  Depending on which of the zillions of lists he
is talking about, his claim is either entirely accurate or even worse
than it would be if it refers to MAPS's RBL(sm).  Some DNS blacklists
are at best used for scoring and only by those who don't mind affecting
legitimate email.  Other DNS blacklists have false positive rates
(legitimate rejected/total legitimate) below 0.01% that allow them to
be used by corporations that would rather receive 1000 spam than reject
one legitimate message.

If his claim refers to private blacklists, then it is obvious nonsense.
There are many IP addresses (e.g. WholesaleBandwidth's /18) that will
never send mail that anyone but a spammer wants delivered for the
foreseeable future.  Then there are private blacklists of domain names
that are undeniably valid targets of complete blacklisting, starting
with Cyberpromo.com.

The clear and undesputed (except by spammers and some others with
special interests) consensus is that blacklists are undesirable but
entirely legitimate, useful, and often necessary mechanisms for dealing
with network abuse by rejecting, not just delaying mail.  The buyer
(or user) must beware, but Keith Moore blanket condemnation of "RBLs"
is simply wrong.  His apparent claim that SMTP servers must accept
mail from everywhere as much sense as claims R. Stallman's complaints
20 years ago closed telnet ports.

Note none of the SMTP servers I run use any DNS (or BGP) SMTP
blacklists.  He's not trying to gore any of my oxen.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri Jan  9 15:13:17 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06607
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 15:13:17 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af2mr-0005uX-K8
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 14:59:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af2mW-0005s5-65
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 14:58:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00414
	for <ietf@ietf.org>; Fri, 9 Jan 2004 14:58:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af2fe-0003UH-00
	for ietf@ietf.org; Fri, 09 Jan 2004 14:51:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af2IH-0003Fs-00
	for ietf@ietf.org; Fri, 09 Jan 2004 14:27:47 -0500
Received: from 212-59.84.64.master-link.com ([64.84.59.212] helo=NSNOVPS00411.nacio.xythos.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af1X3-0003YK-00
	for ietf@ietf.org; Fri, 09 Jan 2004 13:38:53 -0500
Received: from lisalap ([64.202.9.194]) by NSNOVPS00411.nacio.xythos.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Fri, 9 Jan 2004 10:38:18 -0800
From: "Lisa Dusseault" <lisa@xythos.com>
To: "'wang liang'" <wangliang_f@163.com>, <ietf@ietf.org>
Cc: "'Julian Reschke'" <julian.reschke@gmx.de>,
        "'Jim Whitehead'" <ejw@cs.ucsc.edu>
Subject: RE: Building a new work group for public information retrieval protocol, ask for advices.
Date: Fri, 9 Jan 2004 10:39:37 -0800
Message-ID: <002f01c3d6df$ef4d0880$75c990c6@lisalap>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <004d01c3d5b7$f2dda7d0$a81843d3@wl302>
Importance: Normal
X-OriginalArrivalTime: 09 Jan 2004 18:38:18.0622 (UTC) FILETIME=[C02531E0:01C3D6DF]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

There used to exist a DASL WG and its main proposal included a framework
for sending Search requests to Web servers (including WebDAV servers).
The framework was complemented by one proposed syntax for searching
the resources stored directly on that server according to their
metadata values.  Another syntax for the same framework could 
easily allow some Web servers to act as search aggregators or
proxies for other repositories -- including not just a larger
group of Web servers but also non-HTTP URLs could be returned. 

Now the DASL WG doesn't exist, but the work still continues on 
the WebDAV WG mailing list.

http://www.webdav.org/dasl/

Lisa

> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On 
> Behalf Of wang liang
> Sent: Wednesday, January 07, 2004 11:21 PM
> To: ietf@ietf.org
> Subject: Building a new work group for public information 
> retrieval protocol, ask for advices.
> 
> 
> After publishing the message "propose some information 
> retrieval protocols
> for Internet", we received many advices. Now we
> want to build a new work group for this issue, asking for 
> more advices.
> Information retrieval service may exceed E-mail
> service and become the most import service of Internet, so we 
> can't neglect
> it.
> 
> The reason to build a work group for public information 
> retrieval protocols
> lies in the disadvantage of current commercial
> search engines and the improvement in future public search system.
> 
> The faults in commercial search engines.
> 
> 1 In technology. Now no search engine can cover 60% of all 
> the pages on
> Internet. The average update interval of their web
> pages database is almost one month. This is mainly because no 
> of them can
> close keep up with the explosive web pages on
> Internet. But the web page is only one kind of information 
> resources. There
> are still many other resources such as video,
> special databases, BBS, etc. Could you image single search 
> engine company
> can efficiently administer all these information
> resources?
> 
> 2 In business model. Now many search engine companies are 
> concerned with how
> to make profit from company users by
> advertisement and ranking prominence, but never consider what its real
> customers will feel. Search engine originally is tools
> for the convenience of Internet customers, but search engine 
> companies have
> to apply advertisement or selling ranking
> prominence, somewhat inconvenient to information retrieval, 
> to maintain
> their subsistence. In other words, search engines
> make money at the cost of inconvenience of most Internet 
> users, but not its
> high quality of search service.
> 
> 3 Except search engine, all the services of Internet such as 
> E-mail, BBS,
> and FTP are all based on public protocol. There is
> no secret technology in these services. But the information retrieval
> service, may be the most important service on Internet,
> is still dominated by few search engine companies. Many 
> experts know the
> basic "Pages Ranking" algorithm, but no one know its
> detail, which is commercial secret. No public surveillance, 
> no real candid
> ranking algorithm. but We all know another world
> famous algorithm very well, "money can elevate ranking 
> score". This may not
> comply with the basic rules of Internet, a public
> and free world.
> 
> 4 In any free market, customers should be the God forever, but not few
> companies.
> 
> 
> The improvement in new public search system, DRIS (Domain resources
> integrated system)
> 
> 1 In technology. DRIS will build the information retrieval 
> infrastructure of
> Internet. DRIS applies a hierarchical
> distributed architecture to manage all the information on 
> Internet, just
> like DNS. Its main principle is (organization level
> -conventional database system)-(main sub country Internet 
> level-metadata
> harvest system)-(country level-distributed search
> system).In easy words, like web pages system, every DRIS 
> server in bottom
> level like a university will download and index all
> the web pages in its local network and then send the metadata 
> to higher
> layer. All the other resources are also integrated in
> this method. So DRIS will improve the performance of Internet 
> search engine
> in recency, coverage and so on.
> 
> 2 Management. Who will control the DRIS? It's administrated 
> by none of us
> but every of us. DRIS is managed by its users and
> coordinated by a public organization, just like management 
> method of DNS.
> Every organization is its customer and also its
> builder. It's just the real truth of Internet. DRIS is an 
> opening system,
> which needn't any profits from its users and of
> course need not any advertisements.
> 
> 3 The basic idea of DRIS : "search should be the internal function of
> Internet and every one should have his own search
> engine". DRIS just provide the rude search results (like the 
> results in
> current search engine). Many intelligent search
> systems can apply DRIS as their data source and provide high 
> quality of
> personal or commercial search service. So commercial
> search engine can still survive in the way it should be.
> 
> 4 Although DRIS gives us an excellent and promising solution 
> for the new
> public Internet search system, this can't ensure the
> establishment of DRIS. One important principle in technology, the best
> technology is the technology that can meet the urgent
> demand in society. This is just the secret of DRIS. In our testbed, in
> organization level, only few universities have the web
> search engine for the school network. Say nothing of union 
> search system
> that can efficiently integrate all its information
> resources such as ftp, BBS and special databases in library. 
> It's the demand
> in third layer. Sharing the information
> resources between different organizations is also an 
> attraction, which is
> the demand to build the second layer's DRIS. In the
> top layer, integrating all the information resources on 
> Internet may be the
> dream of everyone.
> 
> 5 Practice is the only principle to judge a theory. Now we 
> have built some
> experimental third layer's DRIS servers in HuBei
> Province. I can only say that things just should like this.
> 
> 
> 
>                                                     Protocol Series of
> DRIS(for work group)
> Description of Working Group:
> 
> With the rapid increase of the web pages, the coverage of 
> search engines
> will become poorer and the update interval will be much longer. If the
> current architecture of search engines is still in use, it will be an
> impossible mission to find the precise and comprehensive 
> information in the
> future. This problem will be more serious when IPV6 
> technology is widely
> implemented in communication networks. The problem of "Too 
> much information
> means no information" may become a disaster with information 
> explosion. To
> solve this problem, there should be an efficient information 
> management
> system for Internet.
> 
> In this group, Domain Resource Integrated System--DRIS will 
> be proposed.
> DRIS is a distributed information retrieval system, which 
> will build the
> information retrieval infrastructure for the Internet and also can be
> regarded as a kind of Internet information management system.
> 
> DRIS is a hierarchical distributed search system and comprise 
> three kinds of
> information retrieval system, conventional
> database system, distributed search system and metadata 
> harvest system. We
> will first define the basic search system and then
> define the entire DRIS.
> 
> Specific work items are:
> 
> 1 Standard distributed search system. It defines the 
> platform-independent
> search interface and a collection description
> standard for heterogeneous information resources. An I-D "information
> retrieval protocol for digital resources" has been
> proposed.  
> (http://www.ietf.org/internet-drafts/draft-liang-irpdl-03.txt)
> 
> 2 Standard metadata harvest system. A protocol based some 
> available opening
> standard like OAI will be proposed. It will
> define a standard metadata that can be compatible with most 
> database system.
> 
> 3 Standard public web pages search system. There are many 
> kinds of database
> system. As long as they can provide the standard
> distributed search interface or comply with the metadata 
> harvest format,
> they can be brought into DRIS in appropriate layer.
> But web pages are special for its distributed character and 
> astronomical
> amount. To efficiently integrate web pages on
> Internet, DRIS will build a public opening web pages 
> database, which will
> strictly comply with the principle of (organization
> level-conventional database system)-(sub country Internet 
> level-metadata
> harvest system)-(country level-distributed system).
> (More information: Make search become the internal function 
> of Internet.
> http://arxiv.org/abs/cs.IR/0311015)
> 
> 4 DRIS. It will define entire DRIS. It includes its whole 
> architecture, the
> relation between different nodes, etc.
> (more information: Evolution:Google vs.GRIS.
> http://arxiv.org/abs/cs.DL/0312024)
> 
> 5 DRIS and IPV6. The cooperation with IPV6 WG will be 
> proposed. IPV6 will be
> the most distinct feather of next generation
> Internet.IPV6 is still in improving and any technology that 
> can benefit the
> Internet all can be added to the IPV6 system.
> Since the searching is the main service of most user of 
> Internet and this
> service is not so satisfied to us in current
> Internet, why not take this request into account when build the new
> Internet. For example, in IPV6, all kinds of data flows
> are assigned a priority, and then Internet can guarantee a 
> high priority to
> the data flow of DRIS. So there may need some
> considerations for the relation between DRIS and IPV6.
> 
> The detailed information about DRIS could be found in
> http://www.lib.hust.edu.cn/dl-lib/English/main.htm
> 
> Ask for more advices. Thanks
> 
> 
> 
> 




From owner-ietf@ietf.org  Fri Jan  9 15:34:01 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11173
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 15:34:01 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af3C0-00076P-Kq
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 15:25:16 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af3Ac-0006sP-T7
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 15:23:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08320
	for <ietf@ietf.org>; Fri, 9 Jan 2004 15:23:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af3AZ-0007YF-00
	for ietf@ietf.org; Fri, 09 Jan 2004 15:23:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af2XZ-0000Br-00
	for ietf@ietf.org; Fri, 09 Jan 2004 14:43:32 -0500
Received: from 82-35-77-212.cable.ubr02.dals.blueyonder.co.uk ([82.35.77.212] helo=DarkLord.Sabahattin-Gucukoglu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af1j3-0006F4-00
	for ietf@ietf.org; Fri, 09 Jan 2004 13:51:17 -0500
Received: from Spooler by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v3.32) ID MO000130;
    9 Jan 04 18:49:33 -0000
Received: from spooler by sabahattin-gucukoglu.com (Mercury/32 v3.32); 9 Jan 04 18:49:28 -0000
Received: from aurora (192.168.1.3) by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v3.32) with ESMTP ID MG00012F;
   9 Jan 04 18:49:28 -0000
From: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
Organization: I need more of this!
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Date: Fri, 09 Jan 2004 18:45:57 -0000
MIME-Version: 1.0
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
CC: ietf@ietf.org
Message-ID: <3FFEF6E5.30848.1103D7E@localhost>
In-reply-to: <2067122895.1073639900@halvestr-w2k1>
References: <3FFED7D0.30933.96D04A@localhost>
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

On 9 Jan 2004 at 9:18, Harald Tveit Alvestrand <harald@alvestrand.no> spoke, thus:

> Why doesn't your friend use ETRN to trigger delivery of his queued mail
> from his mate whenever he gets online?

He doesn't want his mate getting his mail while he's not available if he 
will be available shortly after.  The idea is to restrain clients from 
passing onto the next MX, and thereby let his mail fall into his own 
responsibility when the unavailability of his host is either known to be 
temporary or is simply not long enough to justify any resulting policy 
differences between hosts.  His mate could, if this were a dynamic DNS 
provider, be half-way across the world when the client only needed to wait 
a few minutes before it could deliver to the final destination.  This is 
just an example.  Also, etrn/similar don't solve the RBL problem.

> That way, the 4-hour delay is avoided without requiring global changes to
> the Internet infrastructure....

The unilateral thought of all of us, no doubt. :-)  It is quite outrageous 
as far as requirements go for such a simple feature, but I honestly can't 
see a simple way otherwise that doesn't involve inter-host communication 
which, obviously, can't happen if the backed-up host is out, or other 
scheduled checking.  If his mate could somehow know that he (my friend) 
were down, his mate could serve him, and when he returned his mate could, 
upon instruction by him, give an appropriate number and message to the 
effect that the primary was up, go and deliver to him, when all clients 
tried sending to my friend through his mate.  Would implementation of such 
a system be worthwhile, even if it meant periodic checks by his mate that 
my friend was down?  The MX concept is very good, but very heavy-handed 
and served a time long ago when it really was necessary.  Also, the demand 
on the speed of mail delivery has gone up with the number of email users 
on the net and their expectations of it.  In terms of saved bandwidth, 
there's a slight argument for the cost of a DNS query.  I would be willing 
to implement it either way, though preferably the least destructive one.

Cheers,
Sabahattin
-- 
Thought for the day:
    Dictatorship (n): a form of government under which everything 
    which is not prohibited is compulsory.

Latest PGP Public key blocks?  Send any mail to:
<PGPPublicKey@sabahattin-gucukoglu.com>

Sabahattin Gucukoglu
Phone: +44 (0)20 7,502-1615
Mobile: +44 (0)7986 053399
http://www.sabahattin-gucukoglu.com/
Email/MSN: <mail@Sabahattin-Gucukoglu.com>




From owner-ietf@ietf.org  Fri Jan  9 15:41:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13416
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 15:41:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af3Li-0000lC-OC
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 15:35:18 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af3LX-0000e0-8p
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 15:35:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11699
	for <ietf@ietf.org>; Fri, 9 Jan 2004 15:35:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af3LU-0002WG-00
	for ietf@ietf.org; Fri, 09 Jan 2004 15:35:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af3GA-00018n-00
	for ietf@ietf.org; Fri, 09 Jan 2004 15:29:35 -0500
Received: from proxy2baymi.bay.mi.charter.com ([24.247.24.55] helo=proxy2-baycity.chartermi.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af32e-0006vZ-00
	for ietf@ietf.org; Fri, 09 Jan 2004 15:15:36 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by proxy2-baycity.chartermi.net (8.11.7p1+Sun/8.11.6) with SMTP id i09KESO21924
	for <ietf@ietf.org>; Fri, 9 Jan 2004 15:14:28 -0500 (EST)
Received: (qmail 22900 invoked by uid 0); 9 Jan 2004 20:14:25 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.069517 secs); 09 Jan 2004 20:14:25 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 9 Jan 2004 20:14:24 -0000
Message-Id: <6.0.0.22.0.20040109150813.03b83f18@mjs.alientech.net>
X-Mailer: Eudora
Date: Fri, 09 Jan 2004 15:13:50 -0500
To: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
From: ietf@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
In-Reply-To: <20040109120307.2a39485e.moore@cs.utk.edu>
References: <3FFED69D.16780.9223C3@localhost>
 <20040109120307.2a39485e.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:03 PM 1/9/2004, Keith Moore wrote...
>> There's 
>> just one more condition - his mate, though great as mates go, is an anti-
>> RBL purist.  He refuses to use RBLs.
>
>His mate is a wise man.  RBLs are a really terrible idea, and they've
>caused a lot of valid mail to be rejected. 

Not only that, but at least in the U.S., they are illegal per 18 U.S.C. 1030 -Fraud and Related Activity in Connection with Computers. That law reads in part:

"Whoever... knowingly causes the transmission of a program, information, code, or command, and as a result of such conduct, intentionally causes damage without authorization, to a protected computer...shall be punished..."

MAPS RBL and DUL and those who participate in it knowingly transmit information (zone lookups) and commands (SMTP configurations) which causes unauthorized damage to protected systems. 

"[T]he term "protected computer" means a computer... which is used in interstate or foreign commerce or communications, including a computer located outside the United States that is used in a manner that affects interstate or foreign commerce or communication of the United States"

This clearly covers any computer with which the user may send email for Internet commerce, including eBay and web purchases.

"The term 'damage' means any impairment to the integrity or availability of data, a program, a system, or information"

Use of the MAPS RBL and DUL clearly impairs the availability and integrity of the Internet email system and the information transferred using that system. MAPS RBL and DUL participants are actively participating in illegal denial of service





From owner-ietf@ietf.org  Fri Jan  9 15:41:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13423
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 15:41:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af3Nc-0000wn-P7
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 15:37:16 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af3Lp-0000mK-Mr
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 15:35:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11789
	for <ietf@ietf.org>; Fri, 9 Jan 2004 15:35:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af3Ll-0002cV-00
	for ietf@ietf.org; Fri, 09 Jan 2004 15:35:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af3H6-0001LE-00
	for ietf@ietf.org; Fri, 09 Jan 2004 15:30:33 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af39S-0007Ik-00
	for ietf@ietf.org; Fri, 09 Jan 2004 15:22:38 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 09 Jan 2004 12:23:45 +0000
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i09KLuGN006509;
	Fri, 9 Jan 2004 12:21:56 -0800 (PST)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id APC83051;
	Fri, 9 Jan 2004 12:21:55 -0800 (PST)
Message-Id: <6.0.1.1.2.20040109120030.044e7cc8@mira-sjc5-b.cisco.com >
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 09 Jan 2004 12:02:46 -0800
To: jfcm <info@utel.net>
From: Fred Baker <fred@cisco.com>
Subject: Re: [isdf] Re: www.internetforce.org
Cc: ietf@ietf.org, isdf@isoc.org
In-Reply-To: <6.0.1.1.2.20040109065754.046c8b70@mail.utel.net>
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
 <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nos ense.org>
 <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
 <240387438.1073576717@scan.jck.com>
 <6.0.1.1.2.20040108232213.03f8beb0@mail.utel.net>
 <6.0.1.1.2.20040108153525.041ccb90@mira-sjc5-b.cisco.com >
 <6.0.1.1.2.20040109065754.046c8b70@mail.utel.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.7 required=5.0 tests=AWL,FORGED_MUA_EUDORA,
	INVALID_MSGID autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

May I suggest you become familiar with the IETF process before commenting 
on it? The RFCs on the standards track are generally field tested before 
deployment at Proposed Standard, and the various standardization levels 
specifically address the issue you raise.

Read RFC 2026.

At 10:03 PM 1/8/2004, jfcm wrote:
>At 00:37 09/01/04, Fred Baker wrote:
>
>>At 02:32 PM 1/8/2004, jfcm wrote:
>>>Could it not be useful to have a "List of Comments" (LOC) for each RFC? 
>>>Where experience about the RFC reading, testing and implementation could 
>>>be listed by the authors (or a successor) from experience and questions 
>>>received.
>>
>>These are usually found in the form of working group archives and 
>>subsequent RFCs that update or obsolete the older ones, especially in the 
>>case of standards track documents. The RFC Editor also keeps a log of 
>>notes on RFCs when asked to.
>>
>>It's not obvious, at least to me, why a second mechanism is required if 
>>th one that is there works... .
>
>Let say that an RFC is an IETF deliverable. After-delivery 
>support/maintenance is not a requirment for the delivery to exist but an 
>usual user expectation. An RFC is a project imposed to the world before it 
>is validated. A market standard is the desciption of what works and is 
>adopted. We might find this way a fortunate compromise?
>
>_______________________________________________
>This message was passed through ietf_censored@carmen.ipv6.cselt.it, which 
>is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on 
>what to pass are made solely by IETF_CENSORED ML Administrator 
>(ietf_admin@ngnet.it).




From owner-ietf@ietf.org  Fri Jan  9 16:21:58 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15897
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 16:21:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af3xS-0002uv-MK
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 16:14:18 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AeqkS-0003WX-OC
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 02:08:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10327
	for <ietf@ietf.org>; Fri, 9 Jan 2004 02:07:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aeqk9-0001ey-00
	for ietf@ietf.org; Fri, 09 Jan 2004 02:07:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aeqin-0001YU-00
	for ietf@ietf.org; Fri, 09 Jan 2004 02:06:17 -0500
Received: from smtp.sprintpcs.com ([63.167.114.16] helo=dedicated60-bos.wh.sprintip.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aeqds-0001MC-00
	for ietf@ietf.org; Fri, 09 Jan 2004 02:01:12 -0500
Received: from solidmatrix.com (000-389-380.area3.spcsdns.net [68.29.235.26])
 by dedicated60-bos.wh.sprintip.net
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTPA id <0HR700CW2NDK38@dedicated60-bos.wh.sprintip.net> for
 ietf@ietf.org; Fri, 09 Jan 2004 06:58:37 +0000 (GMT)
Date: Fri, 09 Jan 2004 01:58:32 -0500
From: Yakov Shafranovich <research@solidmatrix.com>
Subject: Verisign to make changes to .com and .net SOA values in 30 days
To: ietf@ietf.org
Message-id: <3FFE5118.3080603@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en, he, ru
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5)
 Gecko/20031007
X-Enigmail-Version: 0.82.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

According to a post on NANOG list, Verisign will change the serial
number format and "minimum" value in the .com and .net zones' SOA
records on or shortly after 9 February 2004. According to the post "this
serial number format change is in preparation for potentially more
frequent updates to these zones."

The relevant NANOG thread seems to have already covered all issues 
involved including "possible" RFC problems. I am posting this here so 
people should be aware of the change.

Relevant NANOG post is here:
http://www.merit.edu/mail.archives/nanog/msg00794.html

Related InfoWorld story here:
http://www.infoworld.com/article/04/01/08/HNverisigncom_1.html


-------
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"I ate your Web page. / Forgive me. It was juicy / And tart on my 
tongue." (MIT's 404 Message)
-------






From owner-ietf@ietf.org  Fri Jan  9 17:25:33 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23412
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 17:25:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af4Et-0003oQ-22
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 16:32:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af4Ce-0003dK-Of
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 16:30:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17425
	for <ietf@ietf.org>; Fri, 9 Jan 2004 16:29:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af4Cc-0000Ah-00
	for ietf@ietf.org; Fri, 09 Jan 2004 16:29:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af4Aj-0007fP-00
	for ietf@ietf.org; Fri, 09 Jan 2004 16:28:02 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50] helo=smtp.cs.utk.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af48b-0007Dh-00
	for ietf@ietf.org; Fri, 09 Jan 2004 16:25:50 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 55286AFDA1; Fri,  9 Jan 2004 16:25:48 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 01454-08; Fri,  9 Jan 2004 16:25:47 -0500 (EST)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 28F52AFB2D; Fri,  9 Jan 2004 16:25:47 -0500 (EST)
Date: Fri, 9 Jan 2004 16:25:46 -0500
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Message-Id: <20040109162546.6a47bf1e.moore@cs.utk.edu>
In-Reply-To: <200401091756.i09Hu4NM074582@calcite.rhyolite.com>
References: <20040109120307.2a39485e.moore@cs.utk.edu>
	<200401091756.i09Hu4NM074582@calcite.rhyolite.com>
X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > His mate is a wise man.  RBLs are a really terrible idea, and
> > they've caused a lot of valid mail to be rejected.  There's really
> > no way to reliably determine that a message is spam based on the IP
> > address or sender's domain name.  The most you should do with RBLs
> > is delay or rate-limit mail from the blacklisted sites, you should
> > never reject such mail.
> > ..
> 
> It's never clear to me what Keith Moore means by "RBL" when he repeats
> that claim.  Those three letters are a registered service mark for a
> product that historically has been run so conservatively that claims
> that should not be used to reject mail sound silly. 

Yes, "RBL" did indeed reject valid mail, because it misled site
administrators into thinking that mailers that failed its test were
inherently able to be exploited into relaying significant amounts of
spam.  So sites that trusted RBL's misrepresentation blocked valid mail
from sites that rate-limited relayed mail (including the site I ran at
one time) even when that rate-limiting was an effective spam block. 

I really have no sympathy for net vigilanties who insist on trying to
enforce their own narrow-minded definitions for how the net should work,
and who disrupt others' service in the process.  






From owner-ietf@ietf.org  Fri Jan  9 17:26:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23591
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 17:26:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af50H-0006YK-GD
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 17:21:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af4GN-0003qX-Qy
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 16:33:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17893
	for <ietf@ietf.org>; Fri, 9 Jan 2004 16:33:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af4GM-0000bR-00
	for ietf@ietf.org; Fri, 09 Jan 2004 16:33:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af4EQ-0000PL-00
	for ietf@ietf.org; Fri, 09 Jan 2004 16:31:50 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50] helo=smtp.cs.utk.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af4CX-00009g-00
	for ietf@ietf.org; Fri, 09 Jan 2004 16:29:53 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 88F7EAFEDD; Fri,  9 Jan 2004 16:29:53 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 02144-09; Fri,  9 Jan 2004 16:29:52 -0500 (EST)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 6624DAFDA1; Fri,  9 Jan 2004 16:29:52 -0500 (EST)
Date: Fri, 9 Jan 2004 16:29:52 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
Cc: moore@cs.utk.edu, harald@alvestrand.no, ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Message-Id: <20040109162952.05d4896b.moore@cs.utk.edu>
In-Reply-To: <3FFEF6E5.30848.1103D7E@localhost>
References: <3FFED7D0.30933.96D04A@localhost>
	<3FFEF6E5.30848.1103D7E@localhost>
X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> On 9 Jan 2004 at 9:18, Harald Tveit Alvestrand <harald@alvestrand.no>
> spoke, thus:
> 
> > Why doesn't your friend use ETRN to trigger delivery of his queued
> > mail from his mate whenever he gets online?
> 
> He doesn't want his mate getting his mail while he's not available if
> he will be available shortly after.  

So configure the secondary MX return to 4xx in response to RCPT whenever
the primary MX should be available "shortly after".  

> Also, etrn/similar don't solve the RBL problem.

For that matter, RBL doesn't solve any problem either.  But if you
really want to do RBL filtering on mail relayed to the secondary MX, you
should be able to filter on addresses in Received fields.  Sure, it's 
dodgy, but if you're trusting RBL you're already demonstrating you don't
care about reliable mail delivery.




From owner-ietf@ietf.org  Fri Jan  9 18:05:11 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26566
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 18:05:11 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af5VZ-0002MV-UD
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 17:53:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af5OH-00021h-3o
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 17:46:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25143
	for <ietf@ietf.org>; Fri, 9 Jan 2004 17:46:02 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af5OF-0000zk-00
	for ietf@ietf.org; Fri, 09 Jan 2004 17:46:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af5MT-0000oq-00
	for ietf@ietf.org; Fri, 09 Jan 2004 17:44:13 -0500
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af5Kl-0000cX-00
	for ietf@ietf.org; Fri, 09 Jan 2004 17:42:27 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i09Mg4H1014285;
	Fri, 9 Jan 2004 17:42:04 -0500
Message-Id: <200401092242.i09Mg4H1014285@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: ietf@flatsurface.com (Mike S)
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
In-Reply-To: Your message of "Fri, 09 Jan 2004 15:13:50 EST."
             <6.0.0.22.0.20040109150813.03b83f18@mjs.alientech.net> 
References: <3FFED69D.16780.9223C3@localhost> <20040109120307.2a39485e.moore@cs.utk.edu>
            <6.0.0.22.0.20040109150813.03b83f18@mjs.alientech.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_287815232P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 09 Jan 2004 17:42:04 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Fri, 09 Jan 2004 15:13:50 EST, ietf@flatsurface.com (Mike S)  said:

> Use of the MAPS RBL and DUL clearly impairs the availability and integrity of
> the Internet email system and the information transferred using that system.
> MAPS RBL and DUL participants are actively participating in illegal denial of
> service

Erm.  No.

Note that MAPS is *NOT* blocking a single piece of e-mail itself.  None. Zip. Zero.

All they are doing is publishing information regarding their opinion of a given host's
mail policies.  As such, they're not interfering with anything, but merely answering
queries.

Meanwhile, the site that's actually rejecting your mail has made that decision *itself*,
that it doesn't want to receive mail from you, possibly with MAPS as one component
of the information used to make said decision.

To have a chance of winning this argument, you'll have to prove that the receiving
system is legally *obligated* to accept every piece of mail that you might happen to
want to send.


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

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

iD8DBQE//y48cC3lWbTT17ARApsAAJ4w+uN2ZdbSvsUWRXYRv9RXpeHT6ACgyVlR
piC9+A5tvbKozJkiPmPkE54=
=XCxn
-----END PGP SIGNATURE-----

--==_Exmh_287815232P--



From owner-ietf@ietf.org  Fri Jan  9 18:16:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28169
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 18:16:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af5jr-0007uW-K7
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 18:08:23 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af5fg-0005sl-CK
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 18:04:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26400
	for <ietf@ietf.org>; Fri, 9 Jan 2004 18:04:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af5ff-0002Wq-00
	for ietf@ietf.org; Fri, 09 Jan 2004 18:04:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af5dt-0002SF-00
	for ietf@ietf.org; Fri, 09 Jan 2004 18:02:14 -0500
Received: from nr2baymi.bay.mi.charter.com ([24.247.24.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af5d2-0002MR-00
	for ietf@ietf.org; Fri, 09 Jan 2004 18:01:20 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by nr2baymi.bay.mi.charter.com (8.11.7p1+Sun/8.11.6) with SMTP id i09N1Ev27781
	for <ietf@ietf.org>; Fri, 9 Jan 2004 18:01:14 -0500 (EST)
Received: (qmail 24176 invoked by uid 0); 9 Jan 2004 23:01:10 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.074454 secs); 09 Jan 2004 23:01:10 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 9 Jan 2004 23:01:09 -0000
Message-Id: <6.0.0.22.0.20040109174825.03bd7340@mjs.alientech.net>
X-Mailer: Eudora
Date: Fri, 09 Jan 2004 18:00:54 -0500
To: Valdis.Kletnieks@vt.edu, ietf@ietf.org
From: ietf@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
In-Reply-To: <200401092242.i09Mg4H1014285@turing-police.cc.vt.edu>
References: <3FFED69D.16780.9223C3@localhost>
 <20040109120307.2a39485e.moore@cs.utk.edu>
 <6.0.0.22.0.20040109150813.03b83f18@mjs.alientech.net>
 <200401092242.i09Mg4H1014285@turing-police.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 05:42 PM 1/9/2004, Valdis.Kletnieks@vt.edu wrote...
>On Fri, 09 Jan 2004 15:13:50 EST, ietf@flatsurface.com (Mike S)  said:
>
>> Use of the MAPS RBL and DUL clearly impairs the availability and integrity of
>> the Internet email system and the information transferred using that system.
>> MAPS RBL and DUL participants are actively participating in illegal denial of
>> service
>
>Erm. 

Sounds like you're choking on something.

> No.

You are.

>Note that MAPS is *NOT* blocking a single piece of e-mail itself.  None. Zip. Zero.

Of course not. MAPS is simply a database. As I quite clearly said, *USE* of MAPS impairs email.

>Meanwhile, the site that's actually rejecting your mail has made that decision *itself*,
>that it doesn't want to receive mail from you, possibly with MAPS as one component
>of the information used to make said decision.
>
>To have a chance of winning this argument, you'll have to prove that the receiving
>system is legally *obligated* to accept every piece of mail that you might happen to
>want to send.

MX <> recipient. If I send email foobar@aol.com to the published MX for aol.com and aol.com blocks the ultimate recipient from receiving that email, they are in violation of the law, having interfered with the availability of email for both the sending and receiving systems. By publishing an MX, they have agreed to accept email for any valid address within their domain. That's what an MX is. They are likely in breach of their civil contract with the recipient, also.

Of course, anyone who publishes an MX record but refuses mail is simply an idiot incapable of understanding why the Internet exists in the first place. The Balkanization has begun. The Internet is dead. 




From owner-ietf@ietf.org  Fri Jan  9 18:50:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29662
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 18:50:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af6IZ-0004ng-Ti
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 18:44:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af6IU-0004jB-37
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 18:44:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29395
	for <ietf@ietf.org>; Fri, 9 Jan 2004 18:44:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af6IS-0004tQ-00
	for ietf@ietf.org; Fri, 09 Jan 2004 18:44:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af6Gc-0004nT-00
	for ietf@ietf.org; Fri, 09 Jan 2004 18:42:15 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af6Fb-0004hY-00
	for ietf@ietf.org; Fri, 09 Jan 2004 18:41:12 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i09NfAvg056863
	for ietf@ietf.org env-from <vjs>;
	Fri, 9 Jan 2004 16:41:10 -0700 (MST)
Date: Fri, 9 Jan 2004 16:41:10 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401092341.i09NfAvg056863@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <20040109162546.6a47bf1e.moore@cs.utk.edu>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> ...
> > It's never clear to me what Keith Moore means by "RBL" when he repeats
> > that claim.  Those three letters are a registered service mark for a
> > product that historically has been run so conservatively that claims
> > that should not be used to reject mail sound silly. 
>
> Yes, "RBL" did indeed reject valid mail,

I never heard of any examples of mail considered valid by its targets
that was rejected as the result of RBL listings.  There was plenty of
screaming and whining by advertisers would be about their supposed
free speech rights.

Could you point to significant amounts of real mail, as opposed to
theoretical examples, that might reasonably have consider legitimate
by its targets but that was rejected as the result of a MAPS RBL
listing?  Note that the validity of mail is determined not its senders
but by its targets.

>                                          because it misled site
> administrators into thinking that mailers that failed its test were
> inherently able to be exploited into relaying significant amounts of
> spam.  So sites that trusted RBL's misrepresentation blocked valid mail
> from sites that rate-limited relayed mail (including the site I ran at
> one time) even when that rate-limiting was an effective spam block. 

That makes no sense to me.  It sounds like a confounding of other
blacklists with MAPS's RBL.  The RBL is (was?) based on spam received
instead of open relays inferred by probing.  Or perhaps it is a statement
that you were "misled ... into thinking" that some "mailer" failed
some test.  Or is it at statement that bulk mail you sent was rejected
by its targets?

In any case, what standing do you have to comment on what mail is
rejected by other peoples SMTP servers?  I think that as long as
those using blacklists get what they ask for, no outsiders have any
business commenting, and particularly not would be senders of
unsolicited bulk mail.


> I really have no sympathy for net vigilanties who insist on trying to
> enforce their own narrow-minded definitions for how the net should work,
> and who disrupt others' service in the process.  

Do you have any idea how ironic that statement is?  Can you imagine
that the saying "their network; their rules" might apply to all of us?
I happen to agree with some of your statements about NAT, but I hope
I'm sane enough to not act on them, because "trying to enforce [that]
narrow-minded [definition] for how the net should work [would] disrupt
others' service in the process."

By the way, do you also agree with the other individual who repeated
the familiar (in spammy circles) kooky wishful thinking that running
a DNS blacklist somehow violates U.S. Federal law?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri Jan  9 18:54:34 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26563
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 18:05:11 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af5Pg-0002B0-Mc
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 17:47:32 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af5EQ-0001ht-Sy
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 17:35:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24614
	for <ietf@ietf.org>; Fri, 9 Jan 2004 17:35:50 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af5EN-0000Gz-00
	for ietf@ietf.org; Fri, 09 Jan 2004 17:35:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af5CU-0000CN-00
	for ietf@ietf.org; Fri, 09 Jan 2004 17:33:55 -0500
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af5Al-00005T-00
	for ietf@ietf.org; Fri, 09 Jan 2004 17:32:07 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i09MVjTG013817;
	Fri, 9 Jan 2004 17:31:45 -0500
Message-Id: <200401092231.i09MVjTG013817@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
In-Reply-To: Your message of "Fri, 09 Jan 2004 10:56:04 MST."
             <200401091756.i09Hu4NM074582@calcite.rhyolite.com> 
References: <20040109120307.2a39485e.moore@cs.utk.edu>
            <200401091756.i09Hu4NM074582@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_285796992P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 09 Jan 2004 17:31:45 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Fri, 09 Jan 2004 10:56:04 MST, Vernon Schryver <vjs@calcite.rhyolite.com>  said:

> It's never clear to me what Keith Moore means by "RBL" when he repeats
> that claim.  Those three letters are a registered service mark for a
> product that historically has been run so conservatively that claims

Unfortunately, this has probably gone the same way as Linoleum.

> If his claim refers to private blacklists, then it is obvious nonsense.
> There are many IP addresses (e.g. WholesaleBandwidth's /18) that will
> never send mail that anyone but a spammer wants delivered for the
> foreseeable future.

Yeah, and 69/8 wouldn't be sending packets for the forseeable future either.

Look where it got the people who got the early allocations out of that range.


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

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

iD8DBQE//yvQcC3lWbTT17ARApxfAKCqDWYav3Q/v5Yn1FslA08lNDsFBwCg1RW8
WAAUkfOqb6743uC+VkRlgkA=
=eznW
-----END PGP SIGNATURE-----

--==_Exmh_285796992P--



From owner-ietf@ietf.org  Fri Jan  9 18:56:38 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00031
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 18:56:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af6QJ-0005aT-LS
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 18:52:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af6M4-0004yQ-EF
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 18:47:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29522
	for <ietf@ietf.org>; Fri, 9 Jan 2004 18:47:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af6M2-00054r-00
	for ietf@ietf.org; Fri, 09 Jan 2004 18:47:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af6K9-0004z4-00
	for ietf@ietf.org; Fri, 09 Jan 2004 18:45:54 -0500
Received: from biscayne-one-station.mit.edu ([18.7.7.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af6II-0004re-00
	for ietf@ietf.org; Fri, 09 Jan 2004 18:43:58 -0500
Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])
	by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id i09NhwMH010649;
	Fri, 9 Jan 2004 18:43:58 -0500 (EST)
Received: from mit.edu (KEN-WIRELESS.MIT.EDU [18.18.1.76])
	(authenticated bits=56)
        (User authenticated as raeburn@ATHENA.MIT.EDU)
	by melbourne-city-street.mit.edu (8.12.4/8.12.4) with ESMTP id i09NhuRw010327
	(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT);
	Fri, 9 Jan 2004 18:43:57 -0500 (EST)
Date: Fri, 9 Jan 2004 18:43:55 -0500
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: ietf@ietf.org
To: ietf@flatsurface.com (Mike S)
From: Ken Raeburn <raeburn@MIT.EDU>
In-Reply-To: <6.0.0.22.0.20040109174825.03bd7340@mjs.alientech.net>
Message-Id: <B038F6DA-42FD-11D8-A84D-000A95909EE2@mit.edu>
X-Mailer: Apple Mail (2.553)
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Friday, Jan 9, 2004, at 18:00 US/Eastern, Mike S wrote:
>> Meanwhile, the site that's actually rejecting your mail has made that 
>> decision *itself*,
>> that it doesn't want to receive mail from you, possibly with MAPS as 
>> one component
>> of the information used to make said decision.
>>
>> To have a chance of winning this argument, you'll have to prove that 
>> the receiving
>> system is legally *obligated* to accept every piece of mail that you 
>> might happen to
>> want to send.
>
> MX <> recipient. If I send email foobar@aol.com to the published MX 
> for aol.com and aol.com blocks the ultimate recipient from receiving 
> that email, they are in violation of the law, having interfered with 
> the availability of email for both the sending and receiving systems. 
> By publishing an MX, they have agreed to accept email for any valid 
> address within their domain. That's what an MX is. They are likely in 
> breach of their civil contract with the recipient, also.

So, by that argument, an MX site for FooISP (which presumably would be 
run by FooISP, or at least under contract with FooISP) can't use 
Spamassassin or Greylisting to avoid spam either, nor any other 
criteria.  The spammers must love you.

An ISP using such tools may be in breach of contract with the 
recipient; it depends on the contract, of course.  More likely, I 
suspect, the contract gives them the latitude to prevent abusive 
behavior, or rejects any guarantees of availability of services at any 
given time or when dealing with non-local resources.  Which is probably 
enough to cover Spamassassin and RBL.

If you think there's some violation of law going on here, please be 
more specific.  What law, and in what country?  As Valdis said, you 
need to show why they're obligated to accept absolutely every message, 
regardless of contracts.


> Of course, anyone who publishes an MX record but refuses mail is 
> simply an idiot incapable of understanding why the Internet exists in 
> the first place. The Balkanization has begun. The Internet is dead.

Um, right.  Maybe my troll filter is on the blink today?

Ken




From owner-ietf@ietf.org  Fri Jan  9 19:25:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01281
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 19:25:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af6pT-0007bT-Ih
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 19:18:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af6pL-0007Xo-4L
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 19:18:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00963
	for <ietf@ietf.org>; Fri, 9 Jan 2004 19:18:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af6pJ-000707-00
	for ietf@ietf.org; Fri, 09 Jan 2004 19:18:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af6nO-0006tu-00
	for ietf@ietf.org; Fri, 09 Jan 2004 19:16:06 -0500
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af6ma-0006ol-00
	for ietf@ietf.org; Fri, 09 Jan 2004 19:15:16 -0500
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id LAA667303;
	Sat, 10 Jan 2004 11:14:36 +1100 (EST)
Message-ID: <3FFF43EC.F3E185@swin.edu.au>
Date: Sat, 10 Jan 2004 11:14:36 +1100
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <3FFED69D.16780.9223C3@localhost>
	 <20040109120307.2a39485e.moore@cs.utk.edu> <6.0.0.22.0.20040109150813.03b83f18@mjs.alientech.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Mike S wrote:
	[..]
> "Whoever... knowingly causes the transmission of a program, information, code, or
> command, and as a result of such conduct, intentionally causes damage without
> authorization, to a protected computer...shall be punished..."

Your email is not authorized to enter and reside on a recipient's mail server until and
unless the recipient's mail server says it is. Mail servers are entitled to refuse reception
of your email using whatever decision process they choose. This includes the method of
assigning a "this source is likely a spammer" semantic to responses received from lookups
on certain externally maintained lists.

cheers,
gja
-- 
Grenville Armitage
http://caia.swin.edu.au
I come from a LAN downunder.



From owner-ietf@ietf.org  Fri Jan  9 20:14:33 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03651
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 20:14:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af7dY-0002bu-6u
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 20:10:00 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af7Zd-0002NL-S6
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 20:05:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02697
	for <ietf@ietf.org>; Fri, 9 Jan 2004 20:05:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af7Zc-0001mp-00
	for ietf@ietf.org; Fri, 09 Jan 2004 20:05:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af7Xo-0001iJ-00
	for ietf@ietf.org; Fri, 09 Jan 2004 20:04:05 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af7WH-0001dt-00
	for ietf@ietf.org; Fri, 09 Jan 2004 20:02:29 -0500
Received: by franck-lxnb.sopac.org.fj (Postfix, from userid 501)
	id 736A84B6A1; Fri,  9 Jan 2004 20:02:32 -0500 (EST)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
From: Franck Martin <franck@sopac.org>
To: ietf@ietf.org
In-Reply-To: <6.0.0.22.0.20040109174825.03bd7340@mjs.alientech.net>
References: <3FFED69D.16780.9223C3@localhost>
	 <20040109120307.2a39485e.moore@cs.utk.edu>
	 <6.0.0.22.0.20040109150813.03b83f18@mjs.alientech.net>
	 <200401092242.i09Mg4H1014285@turing-police.cc.vt.edu>
	 <6.0.0.22.0.20040109174825.03bd7340@mjs.alientech.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-wR6sPNqnQWAfA0+BflBU"
Organization: SOPAC
Message-Id: <1073696552.2719.24.camel@franck-lxnb.sopac.org.fj>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4-1.1mdk 
Date: 10 Jan 2004 13:02:32 +1200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_FONTCOLOR_UNSAFE,
	HTML_MESSAGE autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-wR6sPNqnQWAfA0+BflBU
Content-Type: multipart/alternative; boundary="=-vjDpzgkwPZSxgu4CEAna"


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

On Sat, 2004-01-10 at 11:00, Mike S wrote:

> At 05:42 PM 1/9/2004, Valdis.Kletnieks@vt.edu wrote...
> >On Fri, 09 Jan 2004 15:13:50 EST, ietf@flatsurface.com (Mike S)  said:
> >Note that MAPS is *NOT* blocking a single piece of e-mail itself.  None.=
 Zip. Zero.
>=20
> Of course not. MAPS is simply a database. As I quite clearly said, *USE* =
of MAPS impairs email.
>=20
> >Meanwhile, the site that's actually rejecting your mail has made that de=
cision *itself*,
> >that it doesn't want to receive mail from you, possibly with MAPS as one=
 component
> >of the information used to make said decision.
> >
> >To have a chance of winning this argument, you'll have to prove that the=
 receiving
> >system is legally *obligated* to accept every piece of mail that you mig=
ht happen to
> >want to send.
>=20
> MX <> recipient. If I send email foobar@aol.com to the published MX for a=
ol.com and aol.com blocks the ultimate recipient from receiving that email,=
 they are in violation of the law, having interfered with the availability =
of email for both the sending and receiving systems. By publishing an MX, t=
hey have agreed to accept email for any valid address within their domain. =
That's what an MX is. They are likely in breach of their civil contract wit=
h the recipient, also.
>=20
> Of course, anyone who publishes an MX record but refuses mail is simply a=
n idiot incapable of understanding why the Internet exists in the first pla=
ce. The Balkanization has begun. The Internet is dead.=20


Any user of such services agree to a user agreement of use of the
service, which includes the right for the service to filter e-mail,
monitor content, and terminate the user account.

It is interesting to see that with the new US law, some people are
trying to find justification within the IETF on why SPAM should be
authorised. I would not be surprised if a few IETF members here be
summoned to one of these new multi-million dollar case base on their
comments...

Cheers


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

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
  <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/1.1.10">
</HEAD>
<BODY>
On Sat, 2004-01-10 at 11:00, Mike S wrote:
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>At 05:42 PM 1/9/2004, Valdis.Kle=
tnieks@vt.edu wrote...
&gt;On Fri, 09 Jan 2004 15:13:50 EST, ietf@flatsurface.com (Mike S)  said:
&gt;Note that MAPS is *NOT* blocking a single piece of e-mail itself.  None=
. Zip. Zero.

Of course not. MAPS is simply a database. As I quite clearly said, *USE* of=
 MAPS impairs email.

&gt;Meanwhile, the site that's actually rejecting your mail has made that d=
ecision *itself*,
&gt;that it doesn't want to receive mail from you, possibly with MAPS as on=
e component
&gt;of the information used to make said decision.
&gt;
&gt;To have a chance of winning this argument, you'll have to prove that th=
e receiving
&gt;system is legally *obligated* to accept every piece of mail that you mi=
ght happen to
&gt;want to send.

MX &lt;&gt; recipient. If I send email foobar@aol.com to the published MX f=
or aol.com and aol.com blocks the ultimate recipient from receiving that em=
ail, they are in violation of the law, having interfered with the availabil=
ity of email for both the sending and receiving systems. By publishing an M=
X, they have agreed to accept email for any valid address within their doma=
in. That's what an MX is. They are likely in breach of their civil contract=
 with the recipient, also.

Of course, anyone who publishes an MX record but refuses mail is simply an =
idiot incapable of understanding why the Internet exists in the first place=
. The Balkanization has begun. The Internet is dead. </I></FONT></PRE>
</BLOCKQUOTE>
<FONT SIZE=3D"3"><BR>
Any user of such services agree to a user agreement of use of the service, =
which includes the right for the service to filter e-mail, monitor content,=
 and terminate the user account.<BR>
<BR>
It is interesting to see that with the new US law, some people are trying t=
o find justification within the IETF on why SPAM should be authorised. I wo=
uld not be surprised if a few IETF members here be summoned to one of these=
 new multi-million dollar case base on their comments...<BR>
<BR>
Cheers<BR>
</FONT><BR>
<PRE><TABLE CELLSPACING=3D"0" CELLPADDING=3D"0" WIDTH=3D"100%">
<TR>
<TD>
----<BR>
Franck Martin<BR>
<A HREF=3D"mailto:franck@sopac.org">franck@sopac.org</A><BR>
SOPAC, Fiji<BR>
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9&nbsp; D9C6 BE79 9E60 81D9 =
1320<BR>
&quot;Toute connaissance est une reponse a une question&quot; G.Bachelard
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-vjDpzgkwPZSxgu4CEAna--

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

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

iD4DBQA//08ovnmeYIHZEyARAk26AKCUjFr8tAnz9XknUlNNkiwNJsUrXACWLZ1A
BErTkOipFeKJXWpTBMAcOg==
=Qfka
-----END PGP SIGNATURE-----

--=-wR6sPNqnQWAfA0+BflBU--



From owner-ietf@ietf.org  Fri Jan  9 20:43:35 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04553
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 20:43:35 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af84t-0004uA-8w
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 20:38:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af84l-0004qH-Bm
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 20:38:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04421
	for <ietf@ietf.org>; Fri, 9 Jan 2004 20:38:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af84j-0003bL-00
	for ietf@ietf.org; Fri, 09 Jan 2004 20:38:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af82m-0003Wa-00
	for ietf@ietf.org; Fri, 09 Jan 2004 20:36:05 -0500
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af81f-0003SQ-00
	for ietf@ietf.org; Fri, 09 Jan 2004 20:34:55 -0500
Received: from unknown.hamachi.org (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id B5E1C17921; Fri,  9 Jan 2004 20:34:43 -0500 (EST)
Received: from unknown.hamachi.org (sommerfeld@localhost)
	by unknown.hamachi.org (8.12.5+Sun/8.8.8) with ESMTP id i0A1XeVu023454;
	Fri, 9 Jan 2004 20:33:40 -0500 (EST)
Message-Id: <200401100133.i0A1XeVu023454@unknown.hamachi.org>
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: ietf@flatsurface.com
Cc: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify MX 
In-Reply-To: Message from ietf@flatsurface.com (Mike S) 
   of "Fri, 09 Jan 2004 15:13:50 EST." <6.0.0.22.0.20040109150813.03b83f18@mjs.alientech.net> 
Reply-To: sommerfeld@orchard.arlington.ma.us
Date: Fri, 09 Jan 2004 20:33:40 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> That law reads in part:
> 
> "Whoever... knowingly causes the transmission of a program,
> information, code, or command, and as a result of such conduct,
> intentionally causes damage without authorization, to a protected
> computer...shall be punished..."

Except that use of DNSBL's is generally authorized by the entity
administering the mail servers; moreover, it is increasingly clear
that the vast majority of email users do not regard the blocking of
spam as "damage".

See also 47 USC 230(c)(2):

   No provider or user of an interactive computer service shall be held
   liable on account of -

   (A) any action voluntarily taken in good faith to restrict access to
   or availability of material that the provider or user considers to be
   obscene, lewd, lascivious, filthy, excessively violent, harassing, or
   otherwise objectionable, whether or not such material is
   constitutionally protected; or

   (B) any action taken to enable or make available to information content
   providers or others the technical means to restrict access to
   material ...

---
As far as I'm concerned, spam is "otherwise objectionable".

And I believe that there is at least one congressional resolution
encouraging the private sector to work on spam control technologies..

						- Bill



From owner-ietf@ietf.org  Fri Jan  9 22:18:06 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06557
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 22:18:06 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af9Vu-0002U7-8K
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 22:10:14 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af9Vf-0002Qi-4h
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 22:09:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06410
	for <ietf@ietf.org>; Fri, 9 Jan 2004 22:09:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af9Vc-0007F4-00
	for ietf@ietf.org; Fri, 09 Jan 2004 22:09:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af9To-0007BV-00
	for ietf@ietf.org; Fri, 09 Jan 2004 22:08:04 -0500
Received: from [202.108.44.204] (helo=163.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1Af9SM-00077g-00
	for ietf@ietf.org; Fri, 09 Jan 2004 22:06:34 -0500
Received: from wl302 (unknown [211.67.24.168])
	by 192.168.1.204 (Coremail) with SMTP id 3_UJAChs_z8nABio.1
	for <lisa@xythos.com>; Sat, 10 Jan 2004 11:06:21 +0800 (CST)
X-Originating-IP: [211.67.24.168]
Message-ID: <002001c3d726$fe552d70$a81843d3@wl302>
From: "wang liang" <wangliang_f@163.com>
To: "Lisa Dusseault" <lisa@xythos.com>, <ietf@ietf.org>
Cc: "'Julian Reschke'" <julian.reschke@gmx.de>,
        "'Jim Whitehead'" <ejw@cs.ucsc.edu>
References: <002f01c3d6df$ef4d0880$75c990c6@lisalap>
Subject: Re: Building a new work group for public information retrieval protocol, ask for advices.
Date: Sat, 10 Jan 2004 11:08:12 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


DRIS will build a frame to integrate all kinds of information on
Internet.It's a information retrieval infrastructure.
But there still no a work group for information retrieval service in
IETF,but it may be the most important service on Internet.

There are some pre-discussions in http://www.irtf.org ,just for information
retrieval infrastructure.

So building a work group may make all related work (including DASL) more
efficient.

What's your opinions?




> There used to exist a DASL WG and its main proposal included a framework
> for sending Search requests to Web servers (including WebDAV servers).
> The framework was complemented by one proposed syntax for searching
> the resources stored directly on that server according to their
> metadata values.  Another syntax for the same framework could
> easily allow some Web servers to act as search aggregators or
> proxies for other repositories -- including not just a larger
> group of Web servers but also non-HTTP URLs could be returned.
>
> Now the DASL WG doesn't exist, but the work still continues on
> the WebDAV WG mailing list.





From owner-ietf@ietf.org  Fri Jan  9 22:21:30 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06640
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 22:21:30 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af9de-0002wB-RZ
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 22:18:14 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af9dN-0002oa-P7
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 22:17:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06535
	for <ietf@ietf.org>; Fri, 9 Jan 2004 22:17:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af9dL-0007XD-00
	for ietf@ietf.org; Fri, 09 Jan 2004 22:17:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af9bW-0007UI-00
	for ietf@ietf.org; Fri, 09 Jan 2004 22:16:02 -0500
Received: from proxy2baymi.bay.mi.charter.com ([24.247.24.55] helo=proxy2-baycity.chartermi.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af9Zz-0007QZ-00
	for ietf@ietf.org; Fri, 09 Jan 2004 22:14:27 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by proxy2-baycity.chartermi.net (8.11.7p1+Sun/8.11.6) with SMTP id i0A3ELO28011
	for <ietf@ietf.org>; Fri, 9 Jan 2004 22:14:21 -0500 (EST)
Received: (qmail 26276 invoked by uid 0); 10 Jan 2004 03:14:18 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.077458 secs); 10 Jan 2004 03:14:18 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 10 Jan 2004 03:14:17 -0000
Message-Id: <6.0.0.22.0.20040109220540.04348810@mjs.alientech.net>
X-Mailer: Eudora
Date: Fri, 09 Jan 2004 22:06:56 -0500
To: Ken Raeburn <raeburn@MIT.EDU>, ietf@ietf.org
From: ietf@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
In-Reply-To: <B038F6DA-42FD-11D8-A84D-000A95909EE2@mit.edu>
References: <6.0.0.22.0.20040109174825.03bd7340@mjs.alientech.net>
 <B038F6DA-42FD-11D8-A84D-000A95909EE2@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 06:43 PM 1/9/2004, Ken Raeburn wrote...
> If you think there's some violation of law going on here, please be more 
> specific.  What law, and in what country? 

Try to keep up. A specific citation has already been made.




From owner-ietf@ietf.org  Fri Jan  9 22:44:48 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07630
	for <ietf-web-archive@odin.ietf.org>; Fri, 9 Jan 2004 22:44:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Af9xy-0004xn-0u
	for ietf-list@asgard.ietf.org; Fri, 09 Jan 2004 22:39:14 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af9uo-0004mM-7E
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 22:35:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07412
	for <ietf@ietf.org>; Fri, 9 Jan 2004 22:35:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af9um-0000r8-00
	for ietf@ietf.org; Fri, 09 Jan 2004 22:35:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af9su-0000mY-00
	for ietf@ietf.org; Fri, 09 Jan 2004 22:34:00 -0500
Received: from biscayne-one-station.mit.edu ([18.7.7.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af9r9-0000j6-00
	for ietf@ietf.org; Fri, 09 Jan 2004 22:32:11 -0500
Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])
	by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id i0A3WCsZ006185;
	Fri, 9 Jan 2004 22:32:12 -0500 (EST)
Received: from mit.edu (KEN-WIRELESS.MIT.EDU [18.18.1.76])
	(authenticated bits=56)
        (User authenticated as raeburn@ATHENA.MIT.EDU)
	by melbourne-city-street.mit.edu (8.12.4/8.12.4) with ESMTP id i0A3WBRw025297
	(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT);
	Fri, 9 Jan 2004 22:32:11 -0500 (EST)
Date: Fri, 9 Jan 2004 22:32:10 -0500
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: ietf@ietf.org
To: ietf@flatsurface.com (Mike S)
From: Ken Raeburn <raeburn@MIT.EDU>
In-Reply-To: <6.0.0.22.0.20040109220540.04348810@mjs.alientech.net>
Message-Id: <932E2B3A-431D-11D8-A84D-000A95909EE2@mit.edu>
X-Mailer: Apple Mail (2.553)
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Friday, Jan 9, 2004, at 22:06 US/Eastern, Mike S wrote:
> At 06:43 PM 1/9/2004, Ken Raeburn wrote...
>> If you think there's some violation of law going on here, please be 
>> more
>> specific.  What law, and in what country?
> Try to keep up. A specific citation has already been made.

Not in any mail I've seen so far, but the other traffic since implies 
I've missed something.  Investigating that... my apologies.

In any case, the quotations I've seen suggest you believe that the 
blocking is done without authorization.  As I said in my previous mail, 
I suspect the service agreement is likely to provide for it; it would 
be something for the customer to take up with the ISP if they believe 
otherwise.  And I suspect the receiving computer to which "damage" 
would be done would be the ISP's mail server; presumably none of this 
is interfering with the transmission between the ISP's mail server and 
the customer's machine.

Ken




From owner-ietf@ietf.org  Sat Jan 10 00:26:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10197
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 00:26:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfBWj-000281-62
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 00:19:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfBPq-0001sf-7U
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 00:12:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09844
	for <ietf@ietf.org>; Sat, 10 Jan 2004 00:12:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfBPn-0005DV-00
	for ietf@ietf.org; Sat, 10 Jan 2004 00:12:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfBO0-00059Y-00
	for ietf@ietf.org; Sat, 10 Jan 2004 00:10:13 -0500
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfBN7-00054w-00
	for ietf@ietf.org; Sat, 10 Jan 2004 00:09:17 -0500
Received: from dsl092-109-027.nyc2.dsl.speakeasy.net ([66.92.109.27] helo=thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:RC4-SHA:128)  (Exim 3.35 #1 (Debian))
	id 1AfBMw-00039I-00; Sat, 10 Jan 2004 00:09:06 -0500
Received: from tytso by thunk.org with local (Exim 4.30)
	id 1Af69M-0002ut-7V; Fri, 09 Jan 2004 18:34:44 -0500
Date: Fri, 9 Jan 2004 18:34:44 -0500
From: "Theodore Ts'o" <tytso@mit.edu>
To: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Message-ID: <20040109233444.GA11157@thunk.org>
References: <3FFED7D0.30933.96D04A@localhost> <3FFEF6E5.30848.1103D7E@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3FFEF6E5.30848.1103D7E@localhost>
User-Agent: Mutt/1.5.4i
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/>.
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-7.4 required=5.0 tests=AWL,DATE_IN_PAST_03_06,
	HABEAS_SWE autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, Jan 09, 2004 at 06:45:57PM -0000, Sabahattin Gucukoglu wrote:
> On 9 Jan 2004 at 9:18, Harald Tveit Alvestrand <harald@alvestrand.no> spoke, thus:
> 
> > Why doesn't your friend use ETRN to trigger delivery of his queued mail
> > from his mate whenever he gets online?
> 
> He doesn't want his mate getting his mail while he's not available if he 
> will be available shortly after.  The idea is to restrain clients from 
> passing onto the next MX, and thereby let his mail fall into his own 
> responsibility when the unavailability of his host is either known to be 
> temporary or is simply not long enough to justify any resulting policy 
> differences between hosts.  

But the problem is that until vast quanties of people understand your
extended MX proposal, the mail will be received by the backup server
anyway.  And given past experience, it takes a long, long time for
support for new features to get propagated to enough of the global
internet infrastructure that it will really solve your friend's
problem.

Let me propose another possible solution, which doesn't require making
global infrastructural changes.  It will require changes to the SMTP
server on the backup MX machine, but that is something which is much
more likely to be doable.

First of all, on the backup MX server, you create a little daemon that
periodically checks to see if the primary mail server is up.  If it is
down for more than a predefined time perioud (a day in your example),
then it sets a flag "this host is down hard".

Secondly, you change the the SMTP server on the backup MX server that
by default, attempts to send mail to your friends domain return a 4xx
soft error, UNLESS the "this host is down hard" flag is set.  If that
flag is set, then the mail is accepted, and queued for transmission to
your friend's mail server.

As a side benefit, current spamming software will see the soft
failure, and not bother to retry the mail transmission while your
friend's host mail server is temporarily down.

						- Ted



From owner-ietf@ietf.org  Sat Jan 10 08:53:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05267
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 08:53:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfJUD-0006Yo-IF
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 08:49:09 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfJRV-0006SJ-2c
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 08:46:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05086
	for <ietf@ietf.org>; Sat, 10 Jan 2004 08:46:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfJRU-00009a-00
	for ietf@ietf.org; Sat, 10 Jan 2004 08:46:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfJPh-00004z-00
	for ietf@ietf.org; Sat, 10 Jan 2004 08:44:29 -0500
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfJP1-0007n3-00
	for ietf@ietf.org; Sat, 10 Jan 2004 08:43:47 -0500
Received: from unknown.hamachi.org (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id C0A3517921; Sat, 10 Jan 2004 08:43:45 -0500 (EST)
Received: from unknown.hamachi.org (sommerfeld@localhost)
	by unknown.hamachi.org (8.12.5+Sun/8.8.8) with ESMTP id i0ADghvF023743;
	Sat, 10 Jan 2004 08:42:43 -0500 (EST)
Message-Id: <200401101342.i0ADghvF023743@unknown.hamachi.org>
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: ietf@flatsurface.com (Mike S)
Cc: Ken Raeburn <raeburn@MIT.EDU>, ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
In-Reply-To: Message from ietf@flatsurface.com (Mike S) 
   of "Fri, 09 Jan 2004 22:06:56 EST." <6.0.0.22.0.20040109220540.04348810@mjs.alientech.net> 
Reply-To: sommerfeld@orchard.arlington.ma.us
Date: Sat, 10 Jan 2004 08:42:43 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> > If you think there's some violation of law going on here, please be more 
> > specific.  What law, and in what country? 
> 
> Try to keep up. A specific citation has already been made.

and already been debunked.  

							- Bill




From owner-ietf@ietf.org  Sat Jan 10 08:53:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05285
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 08:53:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfJMT-0006H0-Hv
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 08:41:09 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfJLv-0006EZ-LO
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 08:40:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04964
	for <ietf@ietf.org>; Sat, 10 Jan 2004 08:40:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfJLs-0007gW-00
	for ietf@ietf.org; Sat, 10 Jan 2004 08:40:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfJJy-0007b2-00
	for ietf@ietf.org; Sat, 10 Jan 2004 08:38:34 -0500
Received: from [63.247.76.239] (helo=montage.altserver.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfJJM-0007Vc-00
	for ietf@ietf.org; Sat, 10 Jan 2004 08:37:56 -0500
Received: from f01v-39-82.d0.club-internet.fr ([212.195.250.82] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1AfJIx-000262-0U; Sat, 10 Jan 2004 05:37:31 -0800
Message-Id: <6.0.1.1.2.20040110134736.04511030@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sat, 10 Jan 2004 14:18:04 +0100
To: Wawa Ngenge <ngenge@confucius.gnacademy.org>
From: jfcm <info@utel.net>
Subject: URS and LOC (was Re: [isdf] Re: www.internetforce.org)
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org, isdf@isoc.org
In-Reply-To: <Pine.LNX.4.58.0401091922130.29579@confucius.gnacademy.org>
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
 <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nos ense.org>
 <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
 <240387438.1073576717@scan.jck.com>
 <6.0.1.1.2.20040108232213.03f8beb0@mail.utel.net>
 <Pine.LNX.4.58.0401091922130.29579@confucius.gnacademy.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 02:30 10/01/04, Wawa Ngenge wrote:
>I suspect that any approach that was chosen was the result of negotiations
>and discussions among those who took part in the discussion at that time.
>Any solution would raise questions in a societal setting, since unanimity
>is not the norm in a democratic process.  The RFC process has extended so
>deep and so far that change may be difficult, though not impossible.

You are right and Fred's and John's comments below show it. The RFC system 
is part of the legacy technology, is defined by an RFC and will die with 
TCP/IP, or kill it.

Is this a reason to come back and stay in 1983 (I would then chose another 
technology :-). The same reasons are given here as to keep the DNS as it 
is: 800.000 nameservers out there - yet IDNA came. The same reason as about 
LHS, yet John wants to go ahead.  Experience does not mean fossilization.

At 21:02 09/01/04, Fred Baker wrote:
>May I suggest you become familiar with the IETF process before commenting 
>on it? The RFCs on the standards track are generally field tested before 
>deployment at Proposed Standard, and the various standardization levels 
>specifically address the issue you raise.
>Read RFC 2026.

Unnecessary comment. "generally field tested" is not a QA definition of 
what I call serious experimentation and not of what I call global user 
approbation. Even a braod user acceptance is not the proof of valid 
proposition. The current e-mail is universally accepted but it is not a 
good solution as spam shows it every day.

I spent time enough on a DNS experimentation test bed project these past 
two tyears to know that real life technical, societal and governantal 
experimentation is a concept foreign to the internet community.

>>At 21:45 08/01/04, John C Klensin wrote:
>But we do things in a particular way that mostly works (although it should 
>probably be more effectively and accessibly documented), and, while we 
>might tune things differently or use different terminology if we were 
>starting over today, what purpose would it serve to develop redundant 
>mechanisms that would require extra volunteer or staff effort to make work 
>and keep working and that would leave people uncertain as to where to go 
>for information?  And what purpose is served by proposing such an action?

Let just consider the standard path, not the reducing exceptions. The RFC 
system suffers from being mainly a mental exercise between two realities it 
does not relate very well with (the demand and the operational supply). 
When I rise the question "what to do to restore a situation where RFC are 
not respested" the only response I get is "stick to the RFC". When someone 
says "I have two hours to work I want to know the IETF state of art/mind on 
a matter", the response is "spend months reading every elucubration in a 
old WG mailing list".

Up to now users are absent in the IAB/IETF process.
Operations, R&D, deployement etc. calls for more. I did not say a change.

On 16:13 09/01/04, Valdis.Kletnieks@vt.edu said:
>On Fri, 09 Jan 2004 07:03:19 +0100, jfcm said:
> > is validated. A market standard is the desciption of what works and is
> > adopted. We might find this way a fortunate compromise?
>
>Unfortunately, "market standards" often include borken things that are 
>adopted via forced-feeding.  More than one vendor has done this, and some 
>research would probably find at least one example at each of the 7 OSI layers.

True. This is why I talk of compromise. To take the beast from both.


What I see is that WGs lack serious market/user demand studies. They 
replace that with their own evaluation of their reasonable proposition. 
This permits evolution, not innovation, no break through.

IMHO, there should be two documents/prcess added to an RFC (not replacing it):

1. Up stream: a Users Needs Summary. Including what WG may propose, market 
studies, visionnaries suggestions, etc.
2. down he stream: a List of Comments by authors, implementers,users; etc. 
The LOC will comment how the RFC addresses the UNS.

The authors/mainteners of such documents should be professionals. There are 
tools to help.
Closing a WG maens that the RFC porcess is closed. This is whan RFC support 
is to take over.
jfc














From owner-ietf@ietf.org  Sat Jan 10 09:32:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06364
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 09:32:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfK4z-0000bs-Nm
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 09:27:09 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfK4S-0000Z4-Ou
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 09:26:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06279
	for <ietf@ietf.org>; Sat, 10 Jan 2004 09:26:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfK4N-0002Ne-00
	for ietf@ietf.org; Sat, 10 Jan 2004 09:26:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfK0C-0002G7-00
	for ietf@ietf.org; Sat, 10 Jan 2004 09:22:13 -0500
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfJzx-0002DA-00
	for ietf@ietf.org; Sat, 10 Jan 2004 09:21:57 -0500
Received: from unknown.hamachi.org (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id A2D8E17922; Sat, 10 Jan 2004 09:21:56 -0500 (EST)
Received: from unknown.hamachi.org (sommerfeld@localhost)
	by unknown.hamachi.org (8.12.5+Sun/8.8.8) with ESMTP id i0AEKuUZ023781;
	Sat, 10 Jan 2004 09:20:56 -0500 (EST)
Message-Id: <200401101420.i0AEKuUZ023781@unknown.hamachi.org>
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: mikes@flatsurface.com (Mike S)
Cc: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify MX 
In-Reply-To: Message from mikes@flatsurface.com (Mike S) 
   of "Fri, 09 Jan 2004 22:13:22 EST." <6.0.0.22.0.20040109221106.03d07530@mjs.alientech.net> 
Reply-To: sommerfeld@orchard.arlington.ma.us
Date: Sat, 10 Jan 2004 09:20:56 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> The RBL, and particularly the DUL, are not "good faith," as it is
> well known that both block significant amounts of legitimate,
> non-spam, non-uce, recipient-desired email.

I guess it depends on your definition of "significant".  I haven't
noticed a problem, but the amount of spam I get is large enough that,
in good faith, I'm willing to tolerate a modest number of false
positives.

					- Bill








From owner-ietf@ietf.org  Sat Jan 10 11:47:43 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10235
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 11:47:43 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfM7k-0004pI-9n
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 11:38:08 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfM7d-0004mM-Av
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 11:38:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10107
	for <ietf@ietf.org>; Sat, 10 Jan 2004 11:37:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfM7X-0000M7-00
	for ietf@ietf.org; Sat, 10 Jan 2004 11:37:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfM1C-00008T-00
	for ietf@ietf.org; Sat, 10 Jan 2004 11:31:22 -0500
Received: from nr2baymi.bay.mi.charter.com ([24.247.24.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfLyb-0007jt-00
	for ietf@ietf.org; Sat, 10 Jan 2004 11:28:41 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by nr2baymi.bay.mi.charter.com (8.11.7p1+Sun/8.11.6) with SMTP id i0AGRvv12670
	for <ietf@ietf.org>; Sat, 10 Jan 2004 11:28:00 -0500 (EST)
Received: (qmail 31489 invoked by uid 0); 10 Jan 2004 16:27:55 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.081575 secs); 10 Jan 2004 16:27:55 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 10 Jan 2004 16:27:54 -0000
Message-Id: <6.0.0.22.0.20040110112413.042f2528@mjs.alientech.net>
X-Mailer: Eudora
Date: Sat, 10 Jan 2004 11:27:53 -0500
To: ietf@ietf.org
From: ietf@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
In-Reply-To: <200401101342.i0ADghvF023743@unknown.hamachi.org>
References: <Message from ietf@flatsurface.com (Mike S)  of "Fri, 09 Jan 2004 22:06:56 EST." <6.0.0.22.0.20040109220540.04348810@mjs.alientech.net>
 <200401101342.i0ADghvF023743@unknown.hamachi.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 08:42 AM 1/10/2004, Bill Sommerfeld wrote...
>> > If you think there's some violation of law going on here, please be more 
>> > specific.  What law, and in what country? 
>> 
>> Try to keep up. A specific citation has already been made.
>
>and already been debunked.  

If one considers spraying bullets and so shooting and killing innocent bystanders while defending against an assailant as legal, then yes, it's been debunked.





From owner-ietf@ietf.org  Sat Jan 10 11:56:10 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10369
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 11:56:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfMLI-0005nf-5m
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 11:52:08 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfMKw-0005kl-G5
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 11:51:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10304
	for <ietf@ietf.org>; Sat, 10 Jan 2004 11:51:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfMKq-0000lZ-00
	for ietf@ietf.org; Sat, 10 Jan 2004 11:51:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfMHE-0000ew-00
	for ietf@ietf.org; Sat, 10 Jan 2004 11:47:56 -0500
Received: from proxy5baymi.bay.mi.charter.com ([24.247.24.54] helo=proxy5-baycity.chartermi.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfMF3-0000ZB-00
	for ietf@ietf.org; Sat, 10 Jan 2004 11:45:41 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by proxy5-baycity.chartermi.net (8.11.7p1+Sun/8.11.6) with SMTP id i0AGiao18014
	for <ietf@ietf.org>; Sat, 10 Jan 2004 11:44:36 -0500 (EST)
Received: (qmail 31613 invoked by uid 0); 10 Jan 2004 16:44:33 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.066799 secs); 10 Jan 2004 16:44:33 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 10 Jan 2004 16:44:33 -0000
Message-Id: <6.0.0.22.0.20040110112835.040dd3e0@mjs.alientech.net>
X-Mailer: Eudora
Date: Sat, 10 Jan 2004 11:28:52 -0500
To: ietf@ietf.org
From: ietf@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 06:41 PM 1/9/2004, Vernon Schryver wrote...

>Could you point to significant amounts of real mail, as opposed to
>theoretical examples, that might reasonably have consider legitimate
>by its targets but that was rejected as the result of a MAPS RBL
>listing?  Note that the validity of mail is determined not its senders
>but by its targets.

Yes. For a lengthy period, all mail.com SMTP servers were included in the RBL, blocking significant numbers of legitimate, private, non-spam emails from reaching willing recipients.  




From owner-ietf@ietf.org  Sat Jan 10 11:56:11 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10387
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 11:56:11 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfMLI-0005nl-Fz
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 11:52:08 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfML2-0005kn-57
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 11:51:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10308
	for <ietf@ietf.org>; Sat, 10 Jan 2004 11:51:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfMKw-0000ld-00
	for ietf@ietf.org; Sat, 10 Jan 2004 11:51:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfMHF-0000f5-00
	for ietf@ietf.org; Sat, 10 Jan 2004 11:47:57 -0500
Received: from proxy5baymi.bay.mi.charter.com ([24.247.24.54] helo=proxy5-baycity.chartermi.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfMF3-0000ZH-00
	for ietf@ietf.org; Sat, 10 Jan 2004 11:45:41 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by proxy5-baycity.chartermi.net (8.11.7p1+Sun/8.11.6) with SMTP id i0AGido18033
	for <ietf@ietf.org>; Sat, 10 Jan 2004 11:44:39 -0500 (EST)
Received: (qmail 31621 invoked by uid 0); 10 Jan 2004 16:44:34 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.096526 secs); 10 Jan 2004 16:44:34 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 10 Jan 2004 16:44:34 -0000
Message-Id: <6.0.0.22.0.20040110113155.042f2900@mjs.alientech.net>
X-Mailer: Eudora
Date: Sat, 10 Jan 2004 11:44:30 -0500
To: ietf@ietf.org
From: ietf@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
In-Reply-To: <932E2B3A-431D-11D8-A84D-000A95909EE2@mit.edu>
References: <6.0.0.22.0.20040109220540.04348810@mjs.alientech.net>
 <932E2B3A-431D-11D8-A84D-000A95909EE2@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:32 PM 1/9/2004, Ken Raeburn wrote...

>Not in any mail I've seen so far, but the other traffic since implies I've missed something.  Investigating that... my apologies.

18 U.S.C. 1030


>In any case, the quotations I've seen suggest you believe that the blocking is done without authorization. 

That is correct. Understand that I am NOT referring to UCE/spam. In the case of UCE/Spam, I will stipulate that the intended recipient may indeed have authorized upstream blocking/filtering. It is, however, irrational and incorrect to argue that the recipient has authorized blocking/filtering of email replies sent in direct response to queries they have sent. RBL/DUL makes no distinction between these types of email, and indiscriminately causes both types to be blocked. One cannot argue that general "best effort" or "no guarantees" terms of service cover this situation, since the blocking is known and deliberate.

> As I said in my previous mail, I suspect the service agreement is likely to provide for it;

I can only speak for the ISP agreements I've been a party to, and they do NOT authorize any upstream filtering or blocking.

>And I suspect the receiving computer to which "damage" would be done would be the ISP's mail server; presumably none of this is interfering with the transmission between the ISP's mail server and the customer's machine.

It is interfering with communications between sender and recipient, which is exactly what the cited law prohibits. The maintainer of the MX has publicly agreed to accept mail destined for the domain (by publishing an MX record). Blocking/refusing/filtering email bound for a protected system is a violation of U.S. law, unless specific authorization has been granted to do so, which has not occurred (see above).  




From owner-ietf@ietf.org  Sat Jan 10 12:19:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11651
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 12:19:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfMhX-0007th-Od
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 12:15:07 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfMgd-0007rH-4U
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 12:14:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11554
	for <ietf@ietf.org>; Sat, 10 Jan 2004 12:14:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfMgc-0002Pu-00
	for ietf@ietf.org; Sat, 10 Jan 2004 12:14:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfMej-0002NR-00
	for ietf@ietf.org; Sat, 10 Jan 2004 12:12:14 -0500
Received: from krusty-motorsports.com ([192.94.170.8] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfMd0-0002LI-00
	for ietf@ietf.org; Sat, 10 Jan 2004 12:10:26 -0500
Received: from [24.194.112.77] (helo=skipper.averillpark.net)
	by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.22)
	id 1AfNZ0-0005Of-Ck
	for ietf@ietf.org; Sat, 10 Jan 2004 18:10:22 +0000
Received: from [127.0.0.1] (helo=localhost)
	by skipper.averillpark.net with esmtp (Exim 4.22)
	id 1AfMb1-0000AM-Tt
	for ietf@ietf.org; Sat, 10 Jan 2004 12:08:23 -0500
Date: Sat, 10 Jan 2004 12:08:20 -0500 (EST)
From: Richard Welty <rwelty@averillpark.net>
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
To: ietf@ietf.org
Message-ID: <Mahogany-0.66.0-30279-20040110-120820.00@averillpark.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE
References: <Message from ietf@flatsurface.com (Mike S)  of "Fri, 09 Jan 2004 22:06:56 EST." <6.0.0.22.0.20040109220540.04348810@mjs.alientech.net><200401101342.i0ADghvF023743@unknown.hamachi.org>
 <6.0.0.22.0.20040110112413.042f2528@mjs.alientech.net>
In-Reply-To: <6.0.0.22.0.20040110112413.042f2528@mjs.alientech.net>
Organization: Averill Park Networking
X-Mailer: Mahogany 0.66.0 'Clio', compiled for Linux 2.4.18-14 i686
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 10 Jan 2004 11:27:53 -0500 Mike S <ietf@flatsurface.com> wrote:

> At 08:42 AM 1/10/2004, Bill Sommerfeld wrote...
> >> > If you think there's some violation of law going on here, please be more 
> >> > specific.  What law, and in what country? 
> >> 
> >> Try to keep up. A specific citation has already been made.
> >
> >and already been debunked.  

> If one considers spraying bullets and so shooting and killing
> innocent bystanders while defending against an assailant as
> legal, then yes, it's been debunked.

might i suggest citing some case law demonstrating the relevance
of the statute you cited?[1]  the rhetoric of your response is
largely content free. w/o supporting case law, your "legal
opinion" is of rather limited value. 

richard

[1] i, for one, will be extremely impressed if you actually dredge
some up. i don't think that statute has any relevance to dns based
BLs, whether a MAPS product or otherwise. the question is one
for the courts to decide, and i'm not at all aware of anyone
actually attempting to use that statute in the manner you suggest.
-- 
Richard Welty                                         rwelty@averillpark.net
Averill Park Networking                                         518-573-7592
    Java, PHP, PostgreSQL, Unix, Linux, IP Network Engineering, Security




From owner-ietf@ietf.org  Sat Jan 10 13:07:52 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12781
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 13:07:52 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfNQ3-00028S-RQ
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 13:01:07 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfNPD-00025A-S8
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 13:00:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12510
	for <ietf@ietf.org>; Sat, 10 Jan 2004 13:00:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfNPC-0004iq-00
	for ietf@ietf.org; Sat, 10 Jan 2004 13:00:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfNNz-0004Zp-00
	for ietf@ietf.org; Sat, 10 Jan 2004 12:59:00 -0500
Received: from proxy1baymi.bay.mi.charter.com ([24.247.24.39] helo=proxy1-baycity.chartermi.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfNEp-0004C7-00
	for ietf@ietf.org; Sat, 10 Jan 2004 12:49:31 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by proxy1-baycity.chartermi.net (8.11.7p1+Sun/8.11.6) with SMTP id i0AHn2b09768
	for <ietf@ietf.org>; Sat, 10 Jan 2004 12:49:02 -0500 (EST)
Received: (qmail 32301 invoked by uid 0); 10 Jan 2004 17:48:58 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.068057 secs); 10 Jan 2004 17:48:58 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 10 Jan 2004 17:48:57 -0000
Message-Id: <6.0.0.22.0.20040110124641.047fe200@mjs.alientech.net>
X-Mailer: Eudora
Date: Sat, 10 Jan 2004 12:48:39 -0500
To: ietf@ietf.org
From: ietf@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
In-Reply-To: <Mahogany-0.66.0-30279-20040110-120820.00@averillpark.net>
References: <Message from ietf@flatsurface.com (Mike S)  of "Fri, 09 Jan 2004 22:06:56 EST." <6.0.0.22.0.20040109220540.04348810@mjs.alientech.net>
 <200401101342.i0ADghvF023743@unknown.hamachi.org>
 <6.0.0.22.0.20040110112413.042f2528@mjs.alientech.net>
 <Mahogany-0.66.0-30279-20040110-120820.00@averillpark.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:08 PM 1/10/2004, Richard Welty wrote...
>might i suggest citing some case law demonstrating the relevance
>of the statute you cited?

Non sequitor. By your implied logic, no new laws could be effectively created or enforced, since all would lack precedent. The relevant code is relatively new, so only limited, if any, case law can be expected to be extant in any case.




From owner-ietf@ietf.org  Sat Jan 10 14:06:32 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14161
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 14:06:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfOMr-0005XG-CV
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 14:01:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfOLa-0005U0-UE
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 14:00:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13934
	for <ietf@ietf.org>; Sat, 10 Jan 2004 14:00:33 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfOLZ-0007kj-00
	for ietf@ietf.org; Sat, 10 Jan 2004 14:00:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfOJv-0007em-00
	for ietf@ietf.org; Sat, 10 Jan 2004 13:58:52 -0500
Received: from h80ad254f.async.vt.edu ([128.173.37.79] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfOHj-0007Ut-00
	for ietf@ietf.org; Sat, 10 Jan 2004 13:56:35 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i0AItnEj004331;
	Sat, 10 Jan 2004 13:55:49 -0500
Message-Id: <200401101855.i0AItnEj004331@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: ietf@flatsurface.com (Mike S)
Cc: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
In-Reply-To: Your message of "Sat, 10 Jan 2004 12:48:39 EST."
             <6.0.0.22.0.20040110124641.047fe200@mjs.alientech.net> 
References: "of Fri, 09 Jan 2004 22:06:56 EST." <6.0.0.22.0.20040109220540.04348810@mjs.alientech.net> <200401101342.i0ADghvF023743@unknown.hamachi.org> <6.0.0.22.0.20040110112413.042f2528@mjs.alientech.net> <Mahogany-0.66.0-30279-20040110-120820.00@averillpark.net>
            <6.0.0.22.0.20040110124641.047fe200@mjs.alientech.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_2087695836P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sat, 10 Jan 2004 13:55:49 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sat, 10 Jan 2004 12:48:39 EST, ietf@flatsurface.com (Mike S)  said:

> The relevant code is relatively new, so only limited, if any, case law can be expected to be extant in any case.> 

http://www.usdoj.gov/criminal/cybercrime/1030_new.html

Title of the page is "18 USC 1030, as amended Oct 11, 1996".  And the language you
cite from 18 USC 1030 (5)(A)(i) was in there back then.  In 1996. Plenty of time to
build up case law.

Interesting that no spammer seems to have actually brought suit under 18 USC 1030 (g):

http://www4.law.cornell.edu/uscode/18/1030.html

"Any person who suffers damage or loss by reason of a violation of this section
may maintain a civil action against the violator to obtain compensatory damages
and injunctive relief or other equitable relief. A civil action for a violation
of this section may be brought only if the conduct involves 1 of the factors
set forth in clause (i), (ii), (iii), (iv), or (v) of subsection (a)(5)(B).
Damages for a violation involving only conduct described in subsection
(a)(5)(B)(i) are limited to economic damages. No action may be brought under
this subsection unless such action is begun within 2 years of the date of the
act complained of or the date of the discovery of the damage. No action may be
brought under this subsection for the negligent design or manufacture of
computer hardware, computer software, or firmware.

I'm sure if that legal theory were sustainable, MAPS would have been served notice
of a lawsuit by now....  And I know there's people from MAPS lurking here, so
if they want to chime up that such a lawsuit has made it past the preliminary
stages (i.e. didn't get thrown out by a judge immediately), they can...

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

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

iD8DBQFAAEq1cC3lWbTT17ARAuncAKC3FGQwKRcKM5st8T1Ik9dzW5TtIQCgxzGi
jPJubJuFNmXGfNEcjS9gz4U=
=3UcE
-----END PGP SIGNATURE-----

--==_Exmh_2087695836P--



From owner-ietf@ietf.org  Sat Jan 10 15:15:53 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17361
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 15:15:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfPJ9-0003jP-RM
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 15:02:07 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfPHN-0001uU-QA
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 15:00:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15738
	for <ietf@ietf.org>; Sat, 10 Jan 2004 15:00:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfPHM-0003Cj-00
	for ietf@ietf.org; Sat, 10 Jan 2004 15:00:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfPFW-0002zl-00
	for ietf@ietf.org; Sat, 10 Jan 2004 14:58:23 -0500
Received: from krusty-motorsports.com ([192.94.170.8] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfPDD-0002ee-00
	for ietf@ietf.org; Sat, 10 Jan 2004 14:55:59 -0500
Received: from [24.194.112.77] (helo=skipper.averillpark.net)
	by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.22)
	id 1AfQ8g-0007Sl-Vh
	for ietf@ietf.org; Sat, 10 Jan 2004 20:55:23 +0000
Received: from [127.0.0.1] (helo=localhost)
	by skipper.averillpark.net with esmtp (Exim 4.22)
	id 1AfPBg-0000L1-Mo
	for ietf@ietf.org; Sat, 10 Jan 2004 14:54:24 -0500
Date: Sat, 10 Jan 2004 14:54:20 -0500 (EST)
From: Richard Welty <rwelty@averillpark.net>
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
To: ietf@ietf.org
Message-ID: <Mahogany-0.66.0-30279-20040110-145420.00@averillpark.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE
References: <Message from ietf@flatsurface.com (Mike S)  of "Fri, 09 Jan 2004 22:06:56 EST." <6.0.0.22.0.20040109220540.04348810@mjs.alientech.net><200401101342.i0ADghvF023743@unknown.hamachi.org><6.0.0.22.0.20040110112413.042f2528@mjs.alientech.net><Mahogany-0.66.0-30279-20040110-120820.00@averillpark.net>
 <6.0.0.22.0.20040110124641.047fe200@mjs.alientech.net>
In-Reply-To: <6.0.0.22.0.20040110124641.047fe200@mjs.alientech.net>
Organization: Averill Park Networking
X-Mailer: Mahogany 0.66.0 'Clio', compiled for Linux 2.4.18-14 i686
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 10 Jan 2004 12:48:39 -0500 Mike S <ietf@flatsurface.com> wrote:

> At 12:08 PM 1/10/2004, Richard Welty wrote...
> >might i suggest citing some case law demonstrating the relevance
> >of the statute you cited?

> Non sequitor. By your implied logic, no new laws could be
> effectively created or enforced, since all would lack precedent.
> The relevant code is relatively new, so only limited, if any,
> case law can be expected to be extant in any case.

so, you have a statute dated 1996 which you claim prohibits
certain activities. you are apparently unable to cite any case
law (i don't know if you actually have tried to find any or not,
you simply responded by dismissing the suggestion.)

i suspect you're not a lawyer. i also seriously doubt you've
actually asked a lawyer specializing in this type of law for
an informed opinion.

i think that i don't care to take "legal advice" from you.

have a nice day,
   richard
-- 
Richard Welty                                         rwelty@averillpark.net
Averill Park Networking                                         518-573-7592
    Java, PHP, PostgreSQL, Unix, Linux, IP Network Engineering, Security




From owner-ietf@ietf.org  Sat Jan 10 16:04:42 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17371
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 15:15:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfPJ9-0003j5-J3
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 15:02:07 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfPGP-0000Y0-OK
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 14:59:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15680
	for <ietf@ietf.org>; Sat, 10 Jan 2004 14:59:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfPGO-00037M-00
	for ietf@ietf.org; Sat, 10 Jan 2004 14:59:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfPF1-0002ts-00
	for ietf@ietf.org; Sat, 10 Jan 2004 14:57:52 -0500
Received: from proxy1baymi.bay.mi.charter.com ([24.247.24.39] helo=proxy1-baycity.chartermi.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfPAw-0002ZA-00
	for ietf@ietf.org; Sat, 10 Jan 2004 14:53:38 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by proxy1-baycity.chartermi.net (8.11.7p1+Sun/8.11.6) with SMTP id i0AJqub19465
	for <ietf@ietf.org>; Sat, 10 Jan 2004 14:52:56 -0500 (EST)
Received: (qmail 1051 invoked by uid 0); 10 Jan 2004 19:52:53 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.079814 secs); 10 Jan 2004 19:52:53 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 10 Jan 2004 19:52:52 -0000
Message-Id: <6.0.0.22.0.20040110145128.04ae3ec8@mjs.alientech.net>
X-Mailer: Eudora
Date: Sat, 10 Jan 2004 14:52:51 -0500
To: ietf@ietf.org
From: ietf@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
In-Reply-To: <200401101855.i0AItnEj004331@turing-police.cc.vt.edu>
References: <"of Fri, 09 Jan 2004 22:06:56 EST." <6.0.0.22.0.20040109220540.04348810@mjs.alientech.net>
 <200401101342.i0ADghvF023743@unknown.hamachi.org>
 <6.0.0.22.0.20040110112413.042f2528@mjs.alientech.net>
 <Mahogany-0.66.0-30279-20040110-120820.00@averillpark.net>
 <6.0.0.22.0.20040110124641.047fe200@mjs.alientech.net>
 <200401101855.i0AItnEj004331@turing-police.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 01:55 PM 1/10/2004, Valdis.Kletnieks@vt.edu wrote...
>I'm sure if that legal theory were sustainable, MAPS would have been served notice
>of a lawsuit by now....

So, your argument amounts to the equivalent of "If life is possible on Mars, then life must exist on Mars." You'd better let NASA know, it may save them a bundle of money.




From owner-ietf@ietf.org  Sat Jan 10 18:25:01 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23440
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 18:25:01 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfSJt-0002je-JS
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 18:15:05 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfSJB-0002UT-DZ
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 18:14:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23112
	for <ietf@ietf.org>; Sat, 10 Jan 2004 18:14:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfSJ9-0004BV-00
	for ietf@ietf.org; Sat, 10 Jan 2004 18:14:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfSHJ-00049Q-00
	for ietf@ietf.org; Sat, 10 Jan 2004 18:12:26 -0500
Received: from smtp3.fuse.net ([216.68.8.173])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfSGv-00046Y-00
	for ietf@ietf.org; Sat, 10 Jan 2004 18:12:01 -0500
Received: from culsu.net ([216.196.137.59]) by smtp2.fuse.net
          (InterMail vM.6.00.05.02 201-2115-109-103-20031105) with SMTP
          id <20040110231045.DTD13061.smtp2.fuse.net@culsu.net>
          for <ietf@ietf.org>; Sat, 10 Jan 2004 18:10:45 -0500
Received: FROM culsu.net BY culsu.net ; Sat, 10 Jan 2004 18:07:16 -5:00 
From: "Daniel Pelstring" <culsu@culsu.net>
To: "'Mike S'" <ietf@flatsurface.com>, <ietf@ietf.org>
Subject: RE: SMTP Minimum Retry Period - Proposal To Modify Mx 
Date: Sat, 10 Jan 2004 18:07:16 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <6.0.0.22.0.20040110113155.042f2900@mjs.alientech.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Thread-Index: AcPXmsxbCgCIAGy9RZqB6X7r/8yKwwALFi+g
Message-Id: <20040110231045.DTD13061.smtp2.fuse.net@culsu.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

	

	The law you cited refers only to civil damages resulting from
criminal activity.  In order to press a civil suit under this law, the
defendant would first need to be convicted of criminal activity falling
under (i), (ii), (iii), (iv), or (v) of subsection (a)(5)(B), which in turn
requires a violation of (a)(5)(A) which requires unauthorized access to a
protected computer. 

	The administrator doing the blocking would be in the clear, since
they are authorized to access this computer (and are in fact authorized to
change this information, even if you disagree with the change.)  The
provider of a blocking list would not have accessed this computer at all,
since they did not make the change.  The desires of the intended recipient
do not matter at all under this law, as they do not own the computer on
which the change was made.

	If something has been done which violates a service agreement, you
can press a civil suit based on that agreement, which falls under contract
law and has nothing at all to do with 18 U.S.C. 1030.

	I am not a lawyer, although I did spend much time doing legal
research for one.  This is actually an extremely simple law, and I can say
with a fair degree of certainty that it does not cover what you think it
does.

	If you need legal advice, talk to a lawyer, you may have a civil
suit if this filtering violates a contract you have with the party in
question.  18 U.S.C. 1030 however, does not apply here.

I hope this was helpful.

-Daniel Pelstring




-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Mike S
Sent: Saturday, January 10, 2004 11:45 AM
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 

At 10:32 PM 1/9/2004, Ken Raeburn wrote...

>Not in any mail I've seen so far, but the other traffic since implies I've
missed something.  Investigating that... my apologies.

18 U.S.C. 1030


>In any case, the quotations I've seen suggest you believe that the blocking
is done without authorization. 

That is correct. Understand that I am NOT referring to UCE/spam. In the case
of UCE/Spam, I will stipulate that the intended recipient may indeed have
authorized upstream blocking/filtering. It is, however, irrational and
incorrect to argue that the recipient has authorized blocking/filtering of
email replies sent in direct response to queries they have sent. RBL/DUL
makes no distinction between these types of email, and indiscriminately
causes both types to be blocked. One cannot argue that general "best effort"
or "no guarantees" terms of service cover this situation, since the blocking
is known and deliberate.

> As I said in my previous mail, I suspect the service agreement is likely
to provide for it;

I can only speak for the ISP agreements I've been a party to, and they do
NOT authorize any upstream filtering or blocking.

>And I suspect the receiving computer to which "damage" would be done would
be the ISP's mail server; presumably none of this is interfering with the
transmission between the ISP's mail server and the customer's machine.

It is interfering with communications between sender and recipient, which is
exactly what the cited law prohibits. The maintainer of the MX has publicly
agreed to accept mail destined for the domain (by publishing an MX record).
Blocking/refusing/filtering email bound for a protected system is a
violation of U.S. law, unless specific authorization has been granted to do
so, which has not occurred (see above).  





From owner-ietf@ietf.org  Sat Jan 10 19:30:06 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26553
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 19:30:06 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfTNh-0007s3-2l
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 19:23:05 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfTN2-0007oP-SR
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 19:22:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26477
	for <ietf@ietf.org>; Sat, 10 Jan 2004 19:22:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfTN1-0000NM-00
	for ietf@ietf.org; Sat, 10 Jan 2004 19:22:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfTLB-0000K5-00
	for ietf@ietf.org; Sat, 10 Jan 2004 19:20:30 -0500
Received: from proxy2baymi.bay.mi.charter.com ([24.247.24.55] helo=proxy2-baycity.chartermi.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfTJu-0000Gg-00
	for ietf@ietf.org; Sat, 10 Jan 2004 19:19:10 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by proxy2-baycity.chartermi.net (8.11.7p1+Sun/8.11.6) with SMTP id i0B0J2T13488
	for <ietf@ietf.org>; Sat, 10 Jan 2004 19:19:02 -0500 (EST)
Received: (qmail 3432 invoked by uid 0); 11 Jan 2004 00:18:59 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.130746 secs); 11 Jan 2004 00:18:59 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 11 Jan 2004 00:18:57 -0000
Message-Id: <6.0.0.22.0.20040110182459.092b18b0@mjs.alientech.net>
X-Mailer: Eudora
Date: Sat, 10 Jan 2004 19:18:56 -0500
To: "Daniel Pelstring" <culsu@culsu.net>, <ietf@ietf.org>
From: ietf@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
In-Reply-To: <20040110231050.DTZ13061.smtp2.fuse.net@culsu.net>
References: <6.0.0.22.0.20040110113155.042f2900@mjs.alientech.net>
 <20040110231050.DTZ13061.smtp2.fuse.net@culsu.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 06:07 PM 1/10/2004, Daniel Pelstring wrote...
>        The administrator doing the blocking would be in the clear, since
>they are authorized to access this computer (and are in fact authorized to
>change this information, even if you disagree with the change.)

The law prohibits "intentionally cause[ing] damage without authorization, to a protected computer." The MX is not the "protected computer" in the discussion at hand. The "protected computer" is the computer of the email addressee. The MX is merely an intermediary.

By the logic you present, one could argue that no violation (of this law) would be present for hacking a backbone router and inserting a filter which dropped all incoming packets bound for any next hop, since that router would not be "damaged" under the definition given by 18 U.S.C. 1030, the "damage" only occurring external to that router. 

>  The
>provider of a blocking list would not have accessed this computer at all,
>since they did not make the change.  The desires of the intended recipient
>do not matter at all under this law, as they do not own the computer on
>which the change was made.

The change interferes with the delivery of email to a "protected computer," i.e. the computer of the person to whom the email is sent. The ISP's mail exchanger is simply an intermediary. 

The RBL and DUL are quite clearly (and openly) designed and intended to be used to implement denial of service. Doing so with the explicit authorization of the email recipient would be legal. 

Using MAPS RBL and/or DUL is an act which "knowingly causes the transmission of a program, information, code, or command, and as a result of such conduct, intentionally causes damage ['impairment to the integrity or availability of data, a program, a system, or information'] without authorization, to a protected computer," a violation of 18 U.S.C. 1030. The "protected system" is the email addressee's, not the ISP's. If a recipient is not receiving desired email due to ISP use of the MAPS system, the ISP is guilty of unlawful denial of service. Not only the ISP, but also MAPS, is guilty of knowingly and intentionally damaging a protected computer.

A person may authorize, indeed ask, that spam be blocked upstream. With such authorization, an ISP is clearly free to block spam email. As I have already pointed out, it is irrational to claim that a addressee has authorized that _desired_ email be dropped. I have encountered exactly that situation due to use of the MAPS DUL. 

The MAPS system does not, and cannot, distinguish between spam email and legitimate, addressee desired email. It is a brute force system which throws the baby out with the bathwater.




From owner-ietf@ietf.org  Sat Jan 10 20:02:43 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27489
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 20:02:43 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfTpk-0001YW-LX
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 19:52:04 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfTns-0001RI-VW
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 19:50:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26966
	for <ietf@ietf.org>; Sat, 10 Jan 2004 19:50:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfTnm-0001B9-00
	for ietf@ietf.org; Sat, 10 Jan 2004 19:50:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfTia-00014I-00
	for ietf@ietf.org; Sat, 10 Jan 2004 19:44:41 -0500
Received: from proxy5baymi.bay.mi.charter.com ([24.247.24.54] helo=proxy5-baycity.chartermi.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfThI-0000yQ-00
	for ietf@ietf.org; Sat, 10 Jan 2004 19:43:20 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by proxy5-baycity.chartermi.net (8.11.7p1+Sun/8.11.6) with SMTP id i0B0gOo19289
	for <ietf@ietf.org>; Sat, 10 Jan 2004 19:42:26 -0500 (EST)
Received: (qmail 3651 invoked by uid 0); 11 Jan 2004 00:42:21 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.139177 secs); 11 Jan 2004 00:42:21 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 11 Jan 2004 00:42:20 -0000
Message-Id: <6.0.0.22.0.20040110193938.092668d8@mjs.alientech.net>
X-Mailer: Eudora
Date: Sat, 10 Jan 2004 19:42:18 -0500
To: ietf@ietf.org
From: ietf@flatsurface.com (Mike S)
Subject: Apology
In-Reply-To: <20040110231045.DTD13061.smtp2.fuse.net@culsu.net>
References: <6.0.0.22.0.20040110113155.042f2900@mjs.alientech.net>
 <20040110231045.DTD13061.smtp2.fuse.net@culsu.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

The recent thread which I've been contributing to has extended too far from both the original subject and the purpose of this list. I will make no further responses via this list. Those interested and willing to argue their points of view are free to use direct email, which is what I will do should I respond further.




From owner-ietf@ietf.org  Sat Jan 10 20:05:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27555
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 20:05:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfU0O-0002Hb-Ks
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 20:03:04 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfTzl-00025Q-38
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 20:02:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27472
	for <ietf@ietf.org>; Sat, 10 Jan 2004 20:02:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfTzh-0001x5-00
	for ietf@ietf.org; Sat, 10 Jan 2004 20:02:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfTy6-0001uN-00
	for ietf@ietf.org; Sat, 10 Jan 2004 20:00:43 -0500
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfTwZ-0001ks-00
	for ietf@ietf.org; Sat, 10 Jan 2004 19:59:07 -0500
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id LAA745615;
	Sun, 11 Jan 2004 11:58:29 +1100 (EST)
Message-ID: <40009FB4.BC3D2DFC@swin.edu.au>
Date: Sun, 11 Jan 2004 11:58:28 +1100
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <6.0.0.22.0.20040110113155.042f2900@mjs.alientech.net>
	 <20040110231050.DTZ13061.smtp2.fuse.net@culsu.net> <6.0.0.22.0.20040110182459.092b18b0@mjs.alientech.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Mike S wrote:
	[..]
> The change interferes with the delivery of email to a "protected
> computer," i.e. the computer of the person to whom the email is sent.
> The ISP's mail exchanger is simply an intermediary.

You have no right, without a contract, to *demand* transit service from
any ISP's mail exchanger. If you *have* a contract then read the fineprint carefully.
You probably delegated to your ISP the right to accept/reject SMTP connections carrying
emails nominally heading to your address/mailbox.

	[..]
> The MAPS system does not, and cannot, distinguish between spam email
> and legitimate, addressee desired email.

True, but irrelevant to the question of who is authorized to protect what machines.

cheers,
gja
--
Grenville Armitage
http://caia.swin.edu.au
I come from a LAN downunder.



From owner-ietf@ietf.org  Sat Jan 10 20:14:28 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28109
	for <ietf-web-archive@odin.ietf.org>; Sat, 10 Jan 2004 20:14:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfU89-0003TL-2T
	for ietf-list@asgard.ietf.org; Sat, 10 Jan 2004 20:11:05 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfU7q-0003Mt-Ed
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 20:10:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28035
	for <ietf@ietf.org>; Sat, 10 Jan 2004 20:10:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfU7o-0002bM-00
	for ietf@ietf.org; Sat, 10 Jan 2004 20:10:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfU6F-0002Va-00
	for ietf@ietf.org; Sat, 10 Jan 2004 20:09:08 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfU4Y-0002Mc-00
	for ietf@ietf.org; Sat, 10 Jan 2004 20:07:23 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i0B17Lov032817
	for ietf@ietf.org env-from <vjs>;
	Sat, 10 Jan 2004 18:07:21 -0700 (MST)
Date: Sat, 10 Jan 2004 18:07:21 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401110107.i0B17Lov032817@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <6.0.0.22.0.20040110182459.092b18b0@mjs.alientech.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: ietf@flatsurface.com (Mike S)

> ...
> The RBL and DUL are quite clearly (and openly) designed and
> intended to be used to implement denial of service. Doing so with
> the explicit authorization of the email recipient would be legal.

> ...
> The MAPS system does not, and cannot, distinguish between spam
> email and legitimate, addressee desired email. It is a brute force
> system which throws the baby out with the bathwater.

Who but someone incapable of understanding the concept of one person
never wanting to receive any mail or other communications from another
could say something like that?  For the rest of us, it makes perfect
sense to say "I never want to receive any mail from any IP address
owned by Stanford Wallace.  I also never want to receive mail from any
SMTP client using an IP address that has been declared 'dynamic' by
its owner, because that declaration says that its owner cannot figure
out who is using the address at any given time."

I suspect that Mike Sauve (msauve at alientech.net) is upset with the
RBL and DUL because some of his mail was rejected.  I cannot find any
evidence that he has sent unsolicited bulk commecial email, although
some of his public statements about the definition of "spam" have been
a little unusual.  Perhaps he tried to run a commercial site on
"residential" IP addresses and blames MAPS instead of the ISP that
labelled those addresses.


Note:
  - The DUL was largely populated with declarations by the owners of
   the IP addresses in question.

  - The IP address owners are ISPs, not the end users renting them,
   at least if they're not SWIPed.

  - I've always considered "dynamic" declarations by ISPs as implying
   that the ISP is a slumlord uninterested in tracking abuse by its
   users.  Contrary to years of knowingly false statements from such
   as UUNET, anyone with standing to contribute to this list knows
   that figuring out which modem, DSL port, or cable modem port was
   using a block of "dynamic" IP addresses at any given instant requires
   only the will to maintain and consult RADIUS or other logs.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sun Jan 11 06:24:26 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23162
	for <ietf-web-archive@odin.ietf.org>; Sun, 11 Jan 2004 06:24:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfdUk-0007U2-1V
	for ietf-list@asgard.ietf.org; Sun, 11 Jan 2004 06:11:02 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfdUI-0007QE-Nt
	for ietf@asgard.ietf.org; Sun, 11 Jan 2004 06:10:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22983
	for <ietf@ietf.org>; Sun, 11 Jan 2004 06:10:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfdUF-0003jL-00
	for ietf@ietf.org; Sun, 11 Jan 2004 06:10:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfdSP-0003gO-00
	for ietf@ietf.org; Sun, 11 Jan 2004 06:08:38 -0500
Received: from [202.62.1.33] (helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfdRf-0003dK-00
	for ietf@ietf.org; Sun, 11 Jan 2004 06:07:52 -0500
Received: by franck-lxnb.sopac.org.fj (Postfix, from userid 501)
	id E76044B6A1; Sun, 11 Jan 2004 06:07:42 -0500 (EST)
Subject: Internet Force Stats
From: Franck Martin <franck@sopac.org>
To: isdf@isoc.org
Cc: ietf@ietf.org, pignet@lyris.spc.int
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-BV05ciq+8dYiiobQLRgR"
Organization: SOPAC
Message-Id: <1073819262.2814.35.camel@franck-lxnb.sopac.org.fj>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4-1.1mdk 
Date: 11 Jan 2004 23:07:42 +1200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-BV05ciq+8dYiiobQLRgR
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

from:
http://www.internetforce.org/tiki/tiki-stats.php

24 days online
43 pages
200 pages view per day
32 Users including 13 User Profiles

New Wiki Pages:
Privacy
Technology
Niue
Nauru

www.internetforce.org

Is a site where any can contribute and write about any Internet Issue,
informing the general public about the challenges the Internet is
facing, while directing the public to more in depth information on other
sites.

The Internet Force supports the work of the Internet Society:
www.isoc.org

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

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

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

iD8DBQBAAS5+vnmeYIHZEyARAldSAJ4+UCOo+2H+zxz/KT4vliX7kjScuwCfSOpy
x+mcS0659/MlHOy6exdIJWw=
=mUhi
-----END PGP SIGNATURE-----

--=-BV05ciq+8dYiiobQLRgR--



From owner-ietf@ietf.org  Sun Jan 11 10:26:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02171
	for <ietf-web-archive@odin.ietf.org>; Sun, 11 Jan 2004 10:26:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfhKn-0003Yh-6p
	for ietf-list@asgard.ietf.org; Sun, 11 Jan 2004 10:17:01 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfhKL-0003S4-8O
	for ietf@asgard.ietf.org; Sun, 11 Jan 2004 10:16:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01892
	for <ietf@ietf.org>; Sun, 11 Jan 2004 10:16:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfhKK-00011y-00
	for ietf@ietf.org; Sun, 11 Jan 2004 10:16:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfhIQ-0000xB-00
	for ietf@ietf.org; Sun, 11 Jan 2004 10:14:35 -0500
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfhGa-0000rm-00
	for ietf@ietf.org; Sun, 11 Jan 2004 10:12:40 -0500
Received: from limbo (limbo.unfix.org [3ffe:8114:2000:240:200:39ff:fe77:1f3f])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP id 1444A84A1;
	Sun, 11 Jan 2004 16:12:36 +0100 (CET)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Franck Martin'" <franck@sopac.org>, <isdf@isoc.org>
Cc: <ietf@ietf.org>, <pignet@lyris.spc.int>
Subject: Since when is ietf@ietf.org a website stats list? (RE: Internet Force Stats)
Date: Sun, 11 Jan 2004 16:09:32 +0100
Organization: Unfix
Message-ID: <009f01c3d854$eae82240$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <1073819262.2814.35.camel@franck-lxnb.sopac.org.fj>
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,LINES_OF_YELLING,
	UPPERCASE_25_50 autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

Franck Martin wrote:
> from:
> http://www.internetforce.org/tiki/tiki-stats.php
> 
> 24 days online
> 43 pages
> 200 pages view per day
> 32 Users including 13 User Profiles

Is everybody going to show their webstats on the ietf@ietf.org list ?

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / http://unfix.org/~jeroen

iQA/AwUBQAFnIimqKFIzPnwjEQKNwwCgqt/Oi4zxdiuYjpTWlM4MDWZHst0Ani34
UKU+VCUqjdtfHQd2Ai3RpZpZ
=CHnT
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Sun Jan 11 12:11:26 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06368
	for <ietf-web-archive@odin.ietf.org>; Sun, 11 Jan 2004 12:11:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Afj0K-000259-VQ
	for ietf-list@asgard.ietf.org; Sun, 11 Jan 2004 12:04:00 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Afizk-00021m-9B
	for ietf@asgard.ietf.org; Sun, 11 Jan 2004 12:03:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06184
	for <ietf@ietf.org>; Sun, 11 Jan 2004 12:03:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Afizj-0000JM-00
	for ietf@ietf.org; Sun, 11 Jan 2004 12:03:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Afiye-00006u-00
	for ietf@ietf.org; Sun, 11 Jan 2004 12:02:17 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50] helo=smtp.cs.utk.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfivF-0007Cz-00
	for ietf@ietf.org; Sun, 11 Jan 2004 11:58:45 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id CCA68AFDF2; Sun, 11 Jan 2004 11:58:41 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 24690-06; Sun, 11 Jan 2004 11:58:40 -0500 (EST)
Received: from [192.168.0.4] (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 4E40AAFC0C; Sun, 11 Jan 2004 11:58:40 -0500 (EST)
In-Reply-To: <200401092341.i09NfAvg056863@calcite.rhyolite.com>
References: <20040109162546.6a47bf1e.moore@cs.utk.edu> <200401092341.i09NfAvg056863@calcite.rhyolite.com>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <789E445C-4457-11D8-BE61-000393DB5366@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
From: Keith Moore <moore@cs.utk.edu>
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Date: Sun, 11 Jan 2004 11:59:08 -0500
To: Vernon Schryver <vjs@calcite.rhyolite.com>
X-Mailer: Apple Mail (2.609)
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>> ...
>>> It's never clear to me what Keith Moore means by "RBL" when he 
>>> repeats
>>> that claim.  Those three letters are a registered service mark for a
>>> product that historically has been run so conservatively that claims
>>> that should not be used to reject mail sound silly.
>>
>> Yes, "RBL" did indeed reject valid mail,
>
> I never heard of any examples of mail considered valid by its targets
> that was rejected as the result of RBL listings.

Maybe you ought to get out more.

> Could you point to significant amounts of real mail, as opposed to
> theoretical examples, that might reasonably have consider legitimate
> by its targets but that was rejected as the result of a MAPS RBL
> listing?

Yes, but I'm not going to dig back through backup tapes looking from 
complaints from users who didn't get their na-digests just because 
you're in denial.

> In any case, what standing do you have to comment on what mail is
> rejected by other peoples SMTP servers?

Sites can reject mail to their own servers if they want to.  the issue 
is whether they're being misled about the criteria used by a blacklist.

>  I think that as long as
> those using blacklists get what they ask for, no outsiders have any
> business commenting, and particularly not would be senders of
> unsolicited bulk mail.

Apparently you also think that it's acceptable to forward mail from 
people you don't like to DCC, misrepresenting it as spam.  The only 
reasonable response to people with this kind of attitude ends with "and 
the horse you rode in on".  Actually, that's being far too polite.




From owner-ietf@ietf.org  Sun Jan 11 13:02:28 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08649
	for <ietf-web-archive@odin.ietf.org>; Sun, 11 Jan 2004 13:02:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Afjpf-0005Z3-Vr
	for ietf-list@asgard.ietf.org; Sun, 11 Jan 2004 12:57:03 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfjoI-0005RR-RQ
	for ietf@asgard.ietf.org; Sun, 11 Jan 2004 12:55:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08193
	for <ietf@ietf.org>; Sun, 11 Jan 2004 12:55:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfjoH-0003P9-00
	for ietf@ietf.org; Sun, 11 Jan 2004 12:55:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Afjmt-0003DE-00
	for ietf@ietf.org; Sun, 11 Jan 2004 12:54:12 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Afjhd-0002vH-00
	for ietf@ietf.org; Sun, 11 Jan 2004 12:48:45 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i0BHm1gV067168
	for ietf@ietf.org env-from <vjs>;
	Sun, 11 Jan 2004 10:48:01 -0700 (MST)
Date: Sun, 11 Jan 2004 10:48:01 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401111748.i0BHm1gV067168@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <789E445C-4457-11D8-BE61-000393DB5366@cs.utk.edu>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> ...
> > In any case, what standing do you have to comment on what mail is
> > rejected by other peoples SMTP servers?
>
> Sites can reject mail to their own servers if they want to.  the issue 
> is whether they're being misled about the criteria used by a blacklist.

If that is an issue, it ought to be raised by those who are being
misled, the targets of mail, instead of senders and other third parties.


> >  I think that as long as
> > those using blacklists get what they ask for, no outsiders have any
> > business commenting, and particularly not would be senders of
> > unsolicited bulk mail.
>
> Apparently you also think that it's acceptable to forward mail from 
> people you don't like to DCC, misrepresenting it as spam.  The only 
> reasonable response to people with this kind of attitude ends with "and 
> the horse you rode in on".  Actually, that's being far too polite.

First, contrary to Keith Moore's the baloney, DCC clients detect bulk
mail.  It is impossible to (mis)represent mail as unsolicited bulk
mail or spam by forwarding it to a DCC server.  Doing so only reports
it as "bulk."  Are the "courtesy" copies mailing list contributions
that Keith Moore insists on sending "bulk"?  If they are private, then
forwarding them to the DCC instead of my mailbox can have no effect
because no one else will see them.  If they are bulk, then some extra
reporting also has no effect; if DCC clients haven't marked them solicited
bulk by whitelisting the IETF list, they should be rejected as unsolicited
bulk mail.  That's how the DCC works.  So why is Keith Moore so exercised?

Consider "courtesy" copies of mailing list messages and the people who
send them.  Many courtesy copies are sent unthinkingly by using a
"reply all" function, but others are intentional.  The intentional
copies amount to "microphone queue jumping."  Their senders they feel
their targets should see and respond to their words first.  When the
IETF reflector took literally days to finish sending copies to people
at the end of alphabet like me, there might have been other reasons,
but today it finishes within several dozen minutes.

I didn't realize that "courtesy" copies are often intentional queue
jumping until I noticed that senders of "courtesy copies" tend to foam
at the mouth about the evils of MAPS, the RBL, blacklists, and spam
filtering in general.  I did not notice that common thread until I
tired of "courtesy" copies of foaming flaming nonsense and started
dropping senders into my personal, non-published blacklist.

If you want to see apoplectic fits, use a sendmail access_DB instead
of procmail to for your filtering.  That will spare your system a few
cycles, but it also lets senders know they're not being heard.  People
who hate the RBL and DUL for impersonally filtering their earthshaking
words really hate being being personally shunned.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sun Jan 11 14:41:48 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12656
	for <ietf-web-archive@odin.ietf.org>; Sun, 11 Jan 2004 14:41:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AflKW-00036L-63
	for ietf-list@asgard.ietf.org; Sun, 11 Jan 2004 14:33:00 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AflHv-0002vN-7M
	for ietf@asgard.ietf.org; Sun, 11 Jan 2004 14:30:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12236
	for <ietf@ietf.org>; Sun, 11 Jan 2004 14:30:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AflHg-0000Mk-00
	for ietf@ietf.org; Sun, 11 Jan 2004 14:30:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AflEe-0000JT-00
	for ietf@ietf.org; Sun, 11 Jan 2004 14:26:57 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50] helo=smtp.cs.utk.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AflCb-0000GC-00
	for ietf@ietf.org; Sun, 11 Jan 2004 14:24:49 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 0C32FAFC5F; Sun, 11 Jan 2004 14:24:22 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 04746-08; Sun, 11 Jan 2004 14:24:20 -0500 (EST)
Received: from [192.168.0.4] (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 6D8BEAFBE5; Sun, 11 Jan 2004 14:24:20 -0500 (EST)
In-Reply-To: <200401111748.i0BHm1gV067168@calcite.rhyolite.com>
References: <789E445C-4457-11D8-BE61-000393DB5366@cs.utk.edu> <200401111748.i0BHm1gV067168@calcite.rhyolite.com>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <D2EBCE4E-446B-11D8-BE61-000393DB5366@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
From: Keith Moore <moore@cs.utk.edu>
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Date: Sun, 11 Jan 2004 14:24:49 -0500
To: Vernon Schryver <vjs@calcite.rhyolite.com>
X-Mailer: Apple Mail (2.609)
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>>> In any case, what standing do you have to comment on what mail is
>>> rejected by other peoples SMTP servers?
>>
>> Sites can reject mail to their own servers if they want to.  the issue
>> is whether they're being misled about the criteria used by a 
>> blacklist.
>
> If that is an issue, it ought to be raised by those who are being
> misled, the targets of mail, instead of senders and other third 
> parties.

it IS being raised by them, for those who are actually able to figure 
out what's going on.  of course, when the recipient doesn't receive the 
mail he's expecting, he has no idea where to look - so he tends to 
blame the sender.

>> Apparently you also think that it's acceptable to forward mail from
>> people you don't like to DCC, misrepresenting it as spam.  The only
>> reasonable response to people with this kind of attitude ends with 
>> "and
>> the horse you rode in on".  Actually, that's being far too polite.
>
> First, contrary to Keith Moore's the baloney, DCC clients detect bulk
> mail.

whatever.  your mail server claims it's forwarding my mail to DCC, and 
it's not bulk mail.

> Consider "courtesy" copies of mailing list messages and the people who
> send them.  Many courtesy copies are sent unthinkingly by using a
> "reply all" function, but others are intentional.  The intentional
> copies amount to "microphone queue jumping."

"and the horse you rode in on."

you are misleading people, and you know it. 
  




From owner-ietf@ietf.org  Sun Jan 11 15:56:20 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16429
	for <ietf-web-archive@odin.ietf.org>; Sun, 11 Jan 2004 15:56:20 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfmMN-0007Jy-S2
	for ietf-list@asgard.ietf.org; Sun, 11 Jan 2004 15:38:59 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfmLp-0007Hh-EK
	for ietf@asgard.ietf.org; Sun, 11 Jan 2004 15:38:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16081
	for <ietf@ietf.org>; Sun, 11 Jan 2004 15:38:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfmLe-00040n-00
	for ietf@ietf.org; Sun, 11 Jan 2004 15:38:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfmHp-0003uU-00
	for ietf@ietf.org; Sun, 11 Jan 2004 15:34:18 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfmFD-0003qd-00
	for ietf@ietf.org; Sun, 11 Jan 2004 15:31:35 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i0BKV9AX008076
	for ietf@ietf.org env-from <vjs>;
	Sun, 11 Jan 2004 13:31:09 -0700 (MST)
Date: Sun, 11 Jan 2004 13:31:09 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401112031.i0BKV9AX008076@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <D2EBCE4E-446B-11D8-BE61-000393DB5366@cs.utk.edu>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
> From: Keith Moore <moore@cs.utk.edu>
> To: Vernon Schryver <vjs@calcite.rhyolite.com>

> ...
> > If that is an issue, it ought to be raised by those who are being
> > misled, the targets of mail, instead of senders and other third 
> > parties.
>
> it IS being raised by them, for those who are actually able to figure 
> out what's going on.  of course, when the recipient doesn't receive the 
> mail he's expecting, he has no idea where to look - so he tends to 
> blame the sender.

Keith Moore is not complaining about mail he has not received because
of the dasterdly misinformation from the RBL.  He is either a third
party sender of reject mail that he is certain was wanted by its targets
despite being rejected or he is a fourth party presuming to speak for
the first parties (spam targets) against the second parties (blacklist
providers).

An odd thing about users of DNS blacklists and other filters is that
many users avoid confronting senders of rejected mail.  Many users are
happy to let senders assume what the senders want to believe, that the
evil nasty rbl consipracy used lies, bribery, and extortion to force
an ISPs to use a blacklist.  Never mind that after being informed of
that evil nexus by senders, most users do nothing but demand even more
filtering.  Ignore the fact that blacklists are free or cost money and
are now generally selling points.

Of course popularity in the market is not proof of virtue, but it does
poke holes in the claims of senders of rejected mail about blacklists.


> ...
> whatever.  your mail server claims it's forwarding my mail to DCC, and 
> it's not bulk mail.

The first phrase is true but only of mail sent directly from Keith
Moore to my SMTP server.  His second statement is false.  Bulk mail
includes any message which has a "a bunch" of copies sent to one or
more mailboxes.  All mail sent through non-trivial mailing list
reflectors is bulk.  Spam is bulk mail that is unsolicited.  "A bunch"
varies depending on whom you ask and when.

Keith Moore has long known that his "courtesy copies" to my mailbox
are unsolicited and unwelcome.  They are identical except in headers
to hundreds of copies of the same messages, and so are "bulk."  I
tolerate (and sometimes find interesting) the copies of his messages
that arrive through the IETF reflector, but I object to duplicate
copies of flames and insults.  If your "a bunch" threshold for "bulk"
is 2, then Keith Moore's attempts to put 2 copies of his messages in
my mailbox are "spam" regardless of the hundreds of copies sent
elsewhere.  (Some people say 2 is the right threshold for "bulk", but
I run my DCC client with a threshold of 5.  5 is a common choice for
vanity domains.  Choices for real domains range from 20 to 200 as well
as the overflow value of "many.")


> > Consider "courtesy" copies of mailing list messages and the people who
> > send them.  Many courtesy copies are sent unthinkingly by using a
> > "reply all" function, but others are intentional.  The intentional
> > copies amount to "microphone queue jumping."
>
> "and the horse you rode in on."
>
> you are misleading people, and you know it. 

Notice that he does not specify whom is being misled or the falsehood.

Sheesh!--what would a reasonable person do who knows that one of his
targets doesn't want his "courtesy" copies?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sun Jan 11 18:17:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21785
	for <ietf-web-archive@odin.ietf.org>; Sun, 11 Jan 2004 18:17:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfogZ-0008Us-Fk
	for ietf-list@asgard.ietf.org; Sun, 11 Jan 2004 18:07:59 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Afofd-0008Ei-Ac
	for ietf@asgard.ietf.org; Sun, 11 Jan 2004 18:07:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20669
	for <ietf@ietf.org>; Sun, 11 Jan 2004 18:06:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Afofb-00029M-00
	for ietf@ietf.org; Sun, 11 Jan 2004 18:06:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Afodr-000227-00
	for ietf@ietf.org; Sun, 11 Jan 2004 18:05:11 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50] helo=smtp.cs.utk.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfocD-0001u8-00
	for ietf@ietf.org; Sun, 11 Jan 2004 18:03:30 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 5681DAFE62; Sun, 11 Jan 2004 18:03:30 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 25058-04; Sun, 11 Jan 2004 18:03:29 -0500 (EST)
Received: from [192.168.0.4] (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id E837AAFE5E; Sun, 11 Jan 2004 18:03:28 -0500 (EST)
In-Reply-To: <200401112031.i0BKV9AX008076@calcite.rhyolite.com>
References: <D2EBCE4E-446B-11D8-BE61-000393DB5366@cs.utk.edu> <200401112031.i0BKV9AX008076@calcite.rhyolite.com>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <708BF3BC-448A-11D8-BE61-000393DB5366@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
From: Keith Moore <moore@cs.utk.edu>
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Date: Sun, 11 Jan 2004 18:03:59 -0500
To: Vernon Schryver <vjs@calcite.rhyolite.com>
X-Mailer: Apple Mail (2.609)
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>>> If that is an issue, it ought to be raised by those who are being
>>> misled, the targets of mail, instead of senders and other third
>>> parties.
>>
>> it IS being raised by them, for those who are actually able to figure
>> out what's going on.  of course, when the recipient doesn't receive 
>> the
>> mail he's expecting, he has no idea where to look - so he tends to
>> blame the sender.
>
> Keith Moore is not complaining about mail he has not received because
> of the dasterdly misinformation from the RBL.  He is either a third
> party sender of reject mail that he is certain was wanted by its 
> targets
> despite being rejected or he is a fourth party presuming to speak for
> the first parties (spam targets) against the second parties (blacklist
> providers).

You are a barefaced liar.




From owner-ietf@ietf.org  Sun Jan 11 19:11:43 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23608
	for <ietf-web-archive@odin.ietf.org>; Sun, 11 Jan 2004 19:11:43 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfpYl-00056n-5M
	for ietf-list@asgard.ietf.org; Sun, 11 Jan 2004 19:03:59 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfpXx-00054c-NB
	for ietf@asgard.ietf.org; Sun, 11 Jan 2004 19:03:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23179
	for <ietf@ietf.org>; Sun, 11 Jan 2004 19:03:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfpXw-0004Kt-00
	for ietf@ietf.org; Sun, 11 Jan 2004 19:03:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfpVz-0004CS-00
	for ietf@ietf.org; Sun, 11 Jan 2004 19:01:08 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfpUn-00042Y-00
	for ietf@ietf.org; Sun, 11 Jan 2004 18:59:53 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i0BNxrvM056375
	for ietf@ietf.org env-from <vjs>;
	Sun, 11 Jan 2004 16:59:53 -0700 (MST)
Date: Sun, 11 Jan 2004 16:59:53 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401112359.i0BNxrvM056375@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <708BF3BC-448A-11D8-BE61-000393DB5366@cs.utk.edu>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
> From: Keith Moore <moore@cs.utk.edu>
> To: Vernon Schryver <vjs@calcite.rhyolite.com>

> >>> If that is an issue, it ought to be raised by those who are being
> >>> misled, the targets of mail, instead of senders and other third
> >>> parties.
> >>
> >> it IS being raised by them, for those who are actually able to figure
> >> out what's going on.  of course, when the recipient doesn't receive 
> >> the
> >> mail he's expecting, he has no idea where to look - so he tends to
> >> blame the sender.
> >
> > Keith Moore is not complaining about mail he has not received because
> > of the dasterdly misinformation from the RBL.  He is either a third
> > party sender of reject mail that he is certain was wanted by its 
> > targets
> > despite being rejected or he is a fourth party presuming to speak for
> > the first parties (spam targets) against the second parties (blacklist
> > providers).
>
> You are a barefaced liar.

How so in that assertion of mine?  Unless I missed something that seems
unlikely, Keith Moore is not complaining about mail he has failed to
receive.  He surely would not have been misled by blacklist operators
into configuring his SMTP servers to use one of their evil nasty
cheating lying dishonest fraudulent unhealthy fattening cancer-causing
end-to-end principle breaking RBLs.  The remaining possibilities are
that he writing is on behalf of himself as a sender of rejected mail
or he is a fourth party presuming to speak for the people actually
involved, senders, receivers, and blacklist operators.

I admit that I would not be surprised if his opinion of anti-spam
blacklists was informed long ago when some of his more or less innocent
mail was rejected with a reference to MAPS's RBL.  I've no evidence
of that except his use of archaic jargon and what his "courtesy copies"
and statements about how I've configured my SMTP server show of his
views of those who would be happier with fewer of his words.

Concerning how I've configured my SMTP server--Juging from the headers
of the IETF list messages, today it has rejected 2 copies of "and the
horse you rode in on" and one copy of "You are a barefaced liar."  That
seems like a Good Thing(tm), but perhaps not enough.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sun Jan 11 20:05:13 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24938
	for <ietf-web-archive@odin.ietf.org>; Sun, 11 Jan 2004 20:05:13 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfqN5-0007Nl-1N
	for ietf-list@asgard.ietf.org; Sun, 11 Jan 2004 19:55:59 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfqMZ-0007M1-Cd
	for ietf@asgard.ietf.org; Sun, 11 Jan 2004 19:55:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24605
	for <ietf@ietf.org>; Sun, 11 Jan 2004 19:55:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfqMX-0006K8-00
	for ietf@ietf.org; Sun, 11 Jan 2004 19:55:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfqKJ-0006F0-00
	for ietf@ietf.org; Sun, 11 Jan 2004 19:53:07 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50] helo=smtp.cs.utk.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfqGF-000667-00
	for ietf@ietf.org; Sun, 11 Jan 2004 19:48:55 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 0DE93AFE1F; Sun, 11 Jan 2004 19:48:31 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 00655-14; Sun, 11 Jan 2004 19:48:30 -0500 (EST)
Received: from [192.168.0.4] (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id AE7E2AFC6B; Sun, 11 Jan 2004 19:48:29 -0500 (EST)
In-Reply-To: <200401112359.i0BNxrvM056375@calcite.rhyolite.com>
References: <708BF3BC-448A-11D8-BE61-000393DB5366@cs.utk.edu> <200401112359.i0BNxrvM056375@calcite.rhyolite.com>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1C032158-4499-11D8-BE61-000393DB5366@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
From: Keith Moore <moore@cs.utk.edu>
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Date: Sun, 11 Jan 2004 19:48:59 -0500
To: Vernon Schryver <vjs@calcite.rhyolite.com>
X-Mailer: Apple Mail (2.609)
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>> You are a barefaced liar.
>
> How so in that assertion of mine?

Folks who can't see the hole in your analysis for themselves can ask me 
in private mail.  Somehow I doubt the IETF list cares enough to want to 
keep reading this exchange, and you've already demonstrated that you 
don't care what I say.




From owner-ietf@ietf.org  Sun Jan 11 22:35:04 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28019
	for <ietf-web-archive@odin.ietf.org>; Sun, 11 Jan 2004 22:35:04 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AfsiE-0003Vt-CH
	for ietf-list@asgard.ietf.org; Sun, 11 Jan 2004 22:25:58 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Afsft-0003Sp-31
	for ietf@asgard.ietf.org; Sun, 11 Jan 2004 22:23:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27911
	for <ietf@ietf.org>; Sun, 11 Jan 2004 22:23:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Afsfi-0003Mo-00
	for ietf@ietf.org; Sun, 11 Jan 2004 22:23:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfsdV-0003J9-00
	for ietf@ietf.org; Sun, 11 Jan 2004 22:21:06 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Afsd5-0003EO-00
	for ietf@ietf.org; Sun, 11 Jan 2004 22:20:39 -0500
Content-class: urn:content-classes:message
Subject: RE: SMTP Minimum Retry Period - Proposal To Modify Mx
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 11 Jan 2004 19:20:18 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C832@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: SMTP Minimum Retry Period - Proposal To Modify Mx
Thread-Index: AcPYqHj2idN8VMScRGmOOWOBMunpQQAElGIg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Keith Moore" <moore@cs.utk.edu>,
        "Vernon Schryver" <vjs@calcite.rhyolite.com>
Cc: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Keith Moore
> Somehow I doubt the IETF list cares enough to
> want to keep reading this exchange,

There's definitely some of the readers that are tired of reading you.

Michel.




From owner-ietf@ietf.org  Mon Jan 12 07:42:19 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24335
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 07:42:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag1EW-0006nq-Mv
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 07:31:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag1Da-0006l1-2F
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 07:30:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24056
	for <ietf@ietf.org>; Mon, 12 Jan 2004 07:30:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag1DO-0006Pp-00
	for ietf@ietf.org; Mon, 12 Jan 2004 07:30:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag1BR-0006KX-00
	for ietf@ietf.org; Mon, 12 Jan 2004 07:28:42 -0500
Received: from sccrmhc13.comcast.net ([204.127.202.64])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag17l-0006F3-00
	for ietf@ietf.org; Mon, 12 Jan 2004 07:24:53 -0500
Received: from guppylake.com (pcp05307270pcs.wanarb01.mi.comcast.net[68.42.70.186])
          by comcast.net (sccrmhc13) with SMTP
          id <2004011212235701600pv3oge>; Mon, 12 Jan 2004 12:23:57 +0000
Date: Mon, 12 Jan 2004 07:25:46 -0500
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: "Keith Moore" <moore@cs.utk.edu>,
        "Vernon Schryver" <vjs@calcite.rhyolite.com>, <ietf@ietf.org>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C832@server2003.arneill-py.sacramento.ca.us>
Message-Id: <72FD3708-44FA-11D8-A0E4-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

FWIW, I believe Keith is probably right.  Blacklisting has been a major 
impediment to my own email usage.  I don't know about any *particular* 
blacklisting service because when your ISP gets blacklisted by mistake 
and you're simply collateral damage, it's very hard for you to get an 
explanation of what's going on, because your email has been blocked -- 
this has happened to me several times.  My own theory is that 
blacklists are fundamentally flawed because they are inevitably NOT 
accompanied by sufficient administrative staff to deal with the 
inevitable mistakes and exceptions in the blacklist.  Moreover they 
aren't necessary, given the number of other ways to block spam.  -- 
Nathaniel

On Sunday, January 11, 2004, at 10:20  PM, Michel Py wrote:

>> Keith Moore
>> Somehow I doubt the IETF list cares enough to
>> want to keep reading this exchange,
>
> There's definitely some of the readers that are tired of reading you.
>
> Michel.
>
>
>
>




From owner-ietf@ietf.org  Mon Jan 12 12:27:31 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06775
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 12:27:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag5fQ-00043C-6M
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 12:15:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag5eW-00041Y-DG
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 12:15:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06502
	for <ietf@ietf.org>; Mon, 12 Jan 2004 12:14:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag5eV-0004Q1-00
	for ietf@ietf.org; Mon, 12 Jan 2004 12:14:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag5cb-0004PA-00
	for ietf@ietf.org; Mon, 12 Jan 2004 12:13:02 -0500
Received: from ginger.cmf.nrl.navy.mil ([134.207.10.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag5cC-0004OH-00
	for ietf@ietf.org; Mon, 12 Jan 2004 12:12:36 -0500
Received: from cmf.nrl.navy.mil (elvis.cmf.nrl.navy.mil [134.207.10.38])
	(authenticated bits=0)
	by ginger.cmf.nrl.navy.mil (8.12.7/8.12.7) with ESMTP id i0CHCRRr007502
	for <ietf@ietf.org>; Mon, 12 Jan 2004 12:12:28 -0500 (EST)
Message-Id: <200401121712.i0CHCRRr007502@ginger.cmf.nrl.navy.mil>
To: ietf@ietf.org
Subject: Re: Visa for South Korea 
In-Reply-To: Message from Sam Hartman <hartmans@mit.edu> 
   of "Sun, 11 Jan 2004 17:42:24 EST." <tslsmimksz3.fsf@konishi-polis.mit.edu> 
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4
	WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d
	gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;Mv(aiO2z~9n.w?@\>kEpSD@*e`
Date: Mon, 12 Jan 2004 12:12:27 -0500
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
X-Spam-Score: () hits=0 User Authenticated
X-Virus-Scanned: NAI Completed
X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>I'd be interested in answers people get from other consulate/embassy
>staff both from locations other than Boston and with different
>phrasings of the question.

Well, I finally was able to talk to someone at the Washington, DC, embassy.

Their answer?  "We're not sure, but you might need one".

I basically took the same tactic that Sam took; I described the IETF as
a professional organization, and explained I was attending a meeting
of this organization.  At first he said that a visa was not required,
because this counts as a "visit", but then he said he wasn't sure, and
maybe I would need a visa.

I then started asking a few more questions.  I asked what exactly
"business" travel was defined as, and after going around a few times
about it, he basically settled on the definition that if you were
travelling to Korea to a meeting for a "business purpose", then you
need a visa.

The whole thing was as clear as mud, and he clearly wasn't that familiar
with the regulations.  I might try calling a few more consulates to
see if I can find someone more knowledgeable.

BTW, has anyone been able to contact the host web site?  (The one
linked off of the IETF Seoul meeting web page)

http://www.tta.or.kr/ietf59/index.htm

I've been trying for a few days now and no go.  It doesn't seem like
a local network problem from where I'm sitting, but sometimes it's hard
to be sure.

--Ken



From owner-ietf@ietf.org  Mon Jan 12 13:00:04 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08379
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 13:00:04 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag6GY-0005LG-Bj
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 12:54:18 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag6G7-0005K3-2L
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 12:53:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07999
	for <ietf@ietf.org>; Mon, 12 Jan 2004 12:53:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag6G5-0005wW-00
	for ietf@ietf.org; Mon, 12 Jan 2004 12:53:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag6EG-0005sK-00
	for ietf@ietf.org; Mon, 12 Jan 2004 12:51:57 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag6CN-0005oH-00
	for ietf@ietf.org; Mon, 12 Jan 2004 12:50:00 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i0CHnwvW010342
	for ietf@ietf.org env-from <vjs>;
	Mon, 12 Jan 2004 10:49:58 -0700 (MST)
Date: Mon, 12 Jan 2004 10:49:58 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401121749.i0CHnwvW010342@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <72FD3708-44FA-11D8-A0E4-000A9571873E@guppylake.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Nathaniel Borenstein <nsb@guppylake.com>

> FWIW, I believe Keith is probably right.  Blacklisting has been a major 
> impediment to my own email usage.  I don't know about any *particular* 
> blacklisting service because when your ISP gets blacklisted by mistake 
> and you're simply collateral damage, it's very hard for you to get an 
> explanation of what's going on, because your email has been blocked -- 
> this has happened to me several times. 

Several times?  As far as I know, most people I know have never been
collateral or other kinds of blacklist damage.  Do you use what might
be called marginal ISPs?  Some large outfits such as UUNet have long
refused to care enough about spam.  (See the current Spamhaus listings
for UUNet at http://www.spamhaus.org/sbl/listings.lasso?isp=uu.net and
particularly the orange boxes.)


>                                         My own theory is that 
> blacklists are fundamentally flawed because they are inevitably NOT 
> accompanied by sufficient administrative staff to deal with the 
> inevitable mistakes and exceptions in the blacklist.  Moreover they 
> aren't necessary, given the number of other ways to block spam.  -- 
> Nathaniel

I have interests in other ways to block spam, but I don't like that
reasoning.  Many bad implementations don't prove the idea is hopeless.
The design and implementation flaws in practically all installations
of desktop software do not show that desk top computers are bad ideas.
All of us, including those who have never used a Microsoft product,
have been collateral damage of Microsoft's design philosophies,
implementation processes, and business plans, but that implies nothing
about personal computers in general or software from the Seattle area.

Before mail-abuse.org existed and I think before the RBL was called
the "RBL," it was pointed out to me.  I said that I couldn't imagine
a Fortune 500 company having an outsider decide which IP addresses
could send mail.  No matter how forcefully I would have said "Paul's
a good guy," if I'd been one of my bosses, I would have been unmoved.

But maybe that's just me.  All other (usable) ways to block spam
are being purchased as out-sourced services.  If you can trust
outsiders to have "sufficient administrative staff to deal with the
inevitable mistakes and exceptions" in a spam blocking mechanism
that is not blacklist, then why can't a blacklist be run properly?

The only thing that distinguishes blacklists from other third party
spam filters is that setting up a DNS blacklist is easiest.  Any fool
can set up a blacklist.  That many fools have and other fools have
used them does not show that blacklists are bad any more than the ease
of setting up an IP network shows TCP is the spawn of the devil.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Mon Jan 12 13:33:12 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09890
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 13:33:12 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag6kC-0006X7-1L
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 13:24:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag6jT-0006Vj-Q4
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 13:24:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09560
	for <ietf@ietf.org>; Mon, 12 Jan 2004 13:24:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag6jS-0007OA-00
	for ietf@ietf.org; Mon, 12 Jan 2004 13:24:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag6hd-0007Kd-00
	for ietf@ietf.org; Mon, 12 Jan 2004 13:22:17 -0500
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag6gf-0007G6-00
	for ietf@ietf.org; Mon, 12 Jan 2004 13:21:17 -0500
Received: from h-68-164-159-253.snvacaid.dynamic.covad.net ([68.164.159.253] helo=oemcomputer)
	by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1Ag6gf-000522-00
	for ietf@ietf.org; Mon, 12 Jan 2004 10:21:17 -0800
Message-ID: <000401c3d938$e21db6e0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <72FD3708-44FA-11D8-A0E4-000A9571873E@guppylake.com> <200401121749.i0CHnwvW010342@calcite.rhyolite.com>
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Date: Mon, 12 Jan 2004 10:21:22 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi -

> From: "Vernon Schryver" <vjs@calcite.rhyolite.com>
> To: <ietf@ietf.org>
> Sent: Monday, January 12, 2004 9:49 AM
> Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
...
> Several times?  As far as I know, most people I know have never been
> collateral or other kinds of blacklist damage.
...

In the past, both the IETF disman and agentx mailing lists were adversely
affected because the domain in which they were then hosted was blacklisted.
It would not surprise me if other IETF mailing lists have had similar problems.
Outside the IETF, I've seen similar problems for mailing lists for INCITS
and ISO groups.  Depending on the list software in use and how the hosts
using the blacklists are configured, the working group members, and even
the mailing list administrator, may be completely unaware that some group
members are not getting all (or any) posts unless they compare what
they've received with the mailing list archive.

A particularly nasty kind of damage occurs when web forms use email
confirmation.  Last year I had some grief because a national railway
company in Europe was using a service that blacklisted mindspring.com.
I couldn't complete the transaction until I confirmed my email address,
but I couldn't confirm my email address because they had blocked the
domain.

Randy





From owner-ietf@ietf.org  Mon Jan 12 13:51:50 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10721
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 13:51:50 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag75T-0007c3-UD
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 13:46:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag74m-0007aX-6Q
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 13:46:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10581
	for <ietf@ietf.org>; Mon, 12 Jan 2004 13:46:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag74l-0000aE-00
	for ietf@ietf.org; Mon, 12 Jan 2004 13:46:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag72v-0000Vk-00
	for ietf@ietf.org; Mon, 12 Jan 2004 13:44:18 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag71T-0000Qz-00
	for ietf@ietf.org; Mon, 12 Jan 2004 13:42:47 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 12 Jan 2004 10:44:38 +0000
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0CIgFGN016244
	for <ietf@ietf.org>; Mon, 12 Jan 2004 10:42:16 -0800 (PST)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id APE30968;
	Mon, 12 Jan 2004 10:42:14 -0800 (PST)
Message-Id: <6.0.1.1.2.20040112102632.04644718@mira-sjc5-b.cisco.com >
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Mon, 12 Jan 2004 10:29:02 -0800
To: ietf@ietf.org
From: Fred Baker <fred@cisco.com>
Subject: dire outlook on internet and NAT
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.7 required=5.0 tests=FORGED_MUA_EUDORA,
	INVALID_MSGID autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Interesting reading: some have been asking what the cost of moving from a 
peer-to-peer to a service/consumer model are, in terms of applications 
deployed and the ability to build more robust business models. Many ISPs 
are thinking in terms of VoIP as a next generation business, the one after 
"selling bandwidth". But there are issues with that as well...

	http://www.fourmilab.ch/speakfree/eol/




From owner-ietf@ietf.org  Mon Jan 12 14:14:24 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11886
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 14:14:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag7Qm-00006G-1W
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 14:08:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag7O4-0008U9-IF
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 14:06:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11541
	for <ietf@ietf.org>; Mon, 12 Jan 2004 14:06:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag7O3-0001WJ-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:06:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag7M8-0001Qx-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:04:08 -0500
Received: from evrtwa1-ar8-4-65-026-048.evrtwa1.dsl-verizon.net ([4.65.26.48] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag7Kx-0001Nu-00
	for IETF@ietf.org; Mon, 12 Jan 2004 14:02:56 -0500
Received: from eaglet (127.0.0.1:4087)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S41CEE> for <IETF@ietf.org> from <alh-ietf@tndh.net>;
	Mon, 12 Jan 2004 11:02:52 -0800
From: "Tony Hain" <alh-ietf@tndh.net>
To: <IETF@ietf.org>
Subject: Death of the Internet - details at 11
Date: Mon, 12 Jan 2004 11:02:48 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Thread-Index: AcPZPqt4G/ivMnNqTdOx1dR4FcH/hA==
Message-Id: <E1Ag7Kx-0001Nu-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

While one aging application does not constitute 'the Internet', this should
be taken as an early indicator of things that are happing, with more to
come. 
http://www.fourmilab.ch/speakfree/eol/

Like it or not, the IETF must stop wasting time and effort building new
structures on a crumbling framework. A quick scan of the IESG document queue
shows that the vast majority of the workload is still not seriously focused
on making IPv6 the default protocol. 

Happy new year,
Tony 





From owner-ietf@ietf.org  Mon Jan 12 14:44:03 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13079
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 14:44:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag7rs-0001QL-1C
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 14:36:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag7r5-0001P4-OG
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 14:36:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12835
	for <ietf@ietf.org>; Mon, 12 Jan 2004 14:36:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag7r4-0002mc-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:36:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag7pE-0002jG-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:34:12 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag7oA-0002er-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:33:06 -0500
Subject: RE: dire outlook on internet and NAT
Date: Mon, 12 Jan 2004 11:32:47 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C836@server2003.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
Thread-Topic: dire outlook on internet and NAT
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
thread-index: AcPZPUggrX9PVEu/Q3WkwR+Ce4/0egAAgv8g
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Fred Baker" <fred@cisco.com>, <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,LONG_DISTANCE autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Fred Baker wrote:
> Many ISPs are thinking in terms of VoIP as a next generation
> business, the one after "selling bandwidth". But there are
> issues with that as well...

You must be talking about ISPs that are not in bed with a phone company;
at this point in time I don't see how they can compete.

Last month, I dug out the home phone bill to see how many long minutes
we were actually using. It turned out to be 200, which I bought for $5 a
month on my regular phone line; $10 would have bought me 600 minutes and
$20 unlimited long distance.

I do have VOIP (H-323) over my home aDSL line. It works great, because I
control the QOS at the source. I still have to see any ISP giving me
unlimited long distance not only to other VOIP phones but to the entire
PSTN, guaranteeing toll quality even when I'm FTPing a 600MB file out,
for 20 bucks a month.

Michel.




From owner-ietf@ietf.org  Mon Jan 12 14:56:02 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13716
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 14:56:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag86O-000273-UE
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 14:51:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag86M-00022k-KQ
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 14:51:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13492
	for <ietf@ietf.org>; Mon, 12 Jan 2004 14:51:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag86L-0003YG-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:51:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag84S-0003S5-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:49:56 -0500
Received: from 99.231.33.65.cfl.rr.com ([65.33.231.99] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag82i-0003H4-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:48:11 -0500
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1Ag82f-0004dg-00; Mon, 12 Jan 2004 14:48:05 -0500
Date: Mon, 12 Jan 2004 14:47:36 -0500 (EST)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Fred Baker <fred@cisco.com>
cc: ietf@ietf.org
Subject: Re: dire outlook on internet and NAT
In-Reply-To: <6.0.1.1.2.20040112102632.04644718@mira-sjc5-b.cisco.com >
Message-ID: <Pine.LNX.4.44.0401121444350.17798-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=2.3 required=5.0 tests=AWL,WEIRD_PORT autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 12 Jan 2004, Fred Baker wrote:

> Interesting reading: some have been asking what the cost of moving from a
> peer-to-peer to a service/consumer model are, in terms of applications
> deployed and the ability to build more robust business models. Many ISPs
> are thinking in terms of VoIP as a next generation business, the one after
> "selling bandwidth". But there are issues with that as well...
>
> 	http://www.fourmilab.ch/speakfree/eol/
>

IPv6 and NAT cooperate quite well though.  Which would maintain the peer
to peer model on top of NAT.

Scott


>
>

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




From owner-ietf@ietf.org  Mon Jan 12 14:57:50 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13807
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 14:57:50 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag89H-0002B3-OP
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 14:54:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag88Q-00029t-Hm
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 14:54:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13603
	for <ietf@ietf.org>; Mon, 12 Jan 2004 14:54:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag88P-0003g0-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:54:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag86e-0003b5-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:52:13 -0500
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag851-0003Rt-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:50:31 -0500
Received: from guppylake.com (pcp05307270pcs.wanarb01.mi.comcast.net[68.42.70.186])
          by comcast.net (rwcrmhc12) with SMTP
          id <2004011219495501400ru2hde>; Mon, 12 Jan 2004 19:49:55 +0000
Date: Mon, 12 Jan 2004 14:51:43 -0500
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: ietf@ietf.org
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <200401121749.i0CHnwvW010342@calcite.rhyolite.com>
Message-Id: <BF05885C-4538-11D8-9AFA-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Monday, January 12, 2004, at 12:49  PM, Vernon Schryver wrote:

> Several times?  As far as I know, most people I know have never been
> collateral or other kinds of blacklist damage.  Do you use what might
> be called marginal ISPs?  Some large outfits such as UUNet have long
> refused to care enough about spam.

The ISP in question was XO -- marginal by some standards, perhaps.  But 
as I tried to mediate the dispute, I found XO acting much more 
responsibly than Road Runner, which was blocking them.

I also have to say that I fear your approach would help the larger ISPs 
use spam as an excuse to kill off smaller ISP's...  and I question the 
fundamental legitimacy of blocking all of an ISP's customers before 
there's a fair due process to establish the ISP's culpability.  "Caring 
enough about spam" is an awfully slippery concept on which to base a 
blacklist.

> If you can trust
> outsiders to have "sufficient administrative staff to deal with the
> inevitable mistakes and exceptions" in a spam blocking mechanism
> that is not blacklist, then why can't a blacklist be run properly?

Good point.  That's why I favor giving users access to their spam pool 
when they suspect problems, and using challenge/response in certain 
(carefully defined) situations.  A good filtering mechanism is not 
nearly as black and white as a blacklist.

> Any fool
> can set up a blacklist.  That many fools have and other fools have
> used them does not show that blacklists are bad any more than the ease
> of setting up an IP network shows TCP is the spawn of the devil.

I will confess that my personal experience makes it very hard for me to 
be rational on the subject of blacklists, as I fear that any concession 
to them will only encourage the creation of destructive blacklists by 
"fools".  In general I prefer a solution that any fool can implement, 
because one surely will.  -- Nathaniel




From owner-ietf@ietf.org  Mon Jan 12 15:07:05 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14956
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 15:07:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag8G4-0005q7-Is
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 15:01:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag8FS-00059d-Ju
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 15:01:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14155
	for <ietf@ietf.org>; Mon, 12 Jan 2004 15:01:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8FR-0004Fm-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:01:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag8DC-00042X-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:58:59 -0500
Received: from nr2baymi.bay.mi.charter.com ([24.247.24.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8Bv-0003qp-00
	for IETF@ietf.org; Mon, 12 Jan 2004 14:57:39 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by nr2baymi.bay.mi.charter.com (8.11.7p1+Sun/8.11.6) with SMTP id i0CJpGv07040
	for <IETF@ietf.org>; Mon, 12 Jan 2004 14:51:17 -0500 (EST)
Received: (qmail 30061 invoked by uid 0); 12 Jan 2004 19:51:12 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.066529 secs); 12 Jan 2004 19:51:12 -0000
Received: from h81s34a184n47.user.nortelnetworks.com (HELO MSAUVE-2.flatsurface.com) (47.184.34.81)
  by linux.alientech.net with SMTP; 12 Jan 2004 19:51:11 -0000
Message-Id: <6.0.0.22.0.20040112143059.02adaa28@mjs.alientech.net>
X-Mailer: Eudora
Date: Mon, 12 Jan 2004 14:49:15 -0500
To: "Tony Hain" <alh-ietf@tndh.net>
From: ietf@flatsurface.com (Mike S)
Subject: Re: Death of the Internet - details at 11
Cc: <IETF@ietf.org>
In-Reply-To: <E1Ag7Kx-0001Nu-00@ietf-mx>
References: <E1Ag7Kx-0001Nu-00@ietf-mx>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 02:02 PM 1/12/2004, Tony Hain wrote...
>While one aging application does not constitute 'the Internet', this should
>be taken as an early indicator of things that are happing, with more to
>come. 

The true threat is administrative, not technical. It won't do any good to have an IPv6 address space when ISPs won't allow personal servers (and block ports to enforce that ban), blackhole lists block communications from anyone not considered to be "in the club," and ISPs allow TOS/AUP contracts to be violated in proportion to the customer's monthly bill.

It won't be long before ISPs only allow SYNs to flow one-way for "non-business" customers.

Welcome to the new, improved Interweb. 




From owner-ietf@ietf.org  Mon Jan 12 15:08:51 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15156
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 15:08:51 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag8Ix-00009M-Qj
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 15:04:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag8GE-00060Y-6H
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 15:02:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14212
	for <ietf@ietf.org>; Mon, 12 Jan 2004 15:02:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8GC-0004MP-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:02:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag8EP-00046j-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:00:14 -0500
Received: from postal.netaxs.com ([207.8.186.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8CK-0003tG-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:58:04 -0500
Received: (from cook@localhost)
	by postal.netaxs.com (8.12.8p1/8.12.0.Beta7) id i0CJw3rQ000343;
	Mon, 12 Jan 2004 14:58:03 -0500 (EST)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com
Message-Id: <p0601021cbc28ab0ef9f1@[10.0.1.3]>
In-Reply-To: <E1Ag7Kx-0001Nu-00@ietf-mx>
References: <E1Ag7Kx-0001Nu-00@ietf-mx>
Date: Mon, 12 Jan 2004 14:55:28 -0500
To: "Tony Hain" <alh-ietf@tndh.net>
From: Gordon Cook <cook@cookreport.com>
Subject: Re: Death of the Internet - details at 11
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>While one aging application does not constitute 'the Internet', this should
>be taken as an early indicator of things that are happing, with more to
>come.
>http://www.fourmilab.ch/speakfree/eol/
>
>Like it or not, the IETF must stop wasting time and effort building new
>structures on a crumbling framework. A quick scan of the IESG document queue
>shows that the vast majority of the workload is still not seriously focused
>on making IPv6 the default protocol.

Agreed.

http://www.fourmilab.ch/documents/digital-imprimatur/  is the really 
spooky essay.  Excerpted in my December issue.

Read the Digital Imprimatur if you haven't already.

I will take another look at IPv6 before long and would welcome any 
**private** suggestions on how best to do that.



>
>Happy new year,
>Tony


-- 
=============================================================
The COOK Report on Internet Protocol,  609 882-2572 (PSTN) 703 738-6031
(Vonage) Subscription info & prices at 
http://cookreport.com/subscriptions.shtml 
Googin on real time global corp. http://cookreport.com/12.11.shtml  Purchase 10
years of back issues at http://www.cafeshops.com/cookreportinter.6936314 
E-mail cook@cookreport.com or use cook@oldcolo.com Free World Dial up 17318
=============================================================




From owner-ietf@ietf.org  Mon Jan 12 15:11:42 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15508
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 15:11:42 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag8Lr-0001qs-Iu
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 15:07:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag8Jq-0000jv-5b
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 15:05:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14817
	for <ietf@ietf.org>; Mon, 12 Jan 2004 15:05:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8Jo-0004f1-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:05:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag8Jh-0004e2-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:05:42 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8JS-0004ZO-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:05:26 -0500
Subject: RE: dire outlook on internet and NAT
Date: Mon, 12 Jan 2004 12:05:09 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C837@server2003.arneill-py.sacramento.ca.us>
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Thread-Topic: dire outlook on internet and NAT
thread-index: AcPZRiFd7IdAtjUbR022rFzYEyTKBQAAA4Eg
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Nathaniel Borenstein" <nsb@guppylake.com>
Cc: "Fred Baker" <fred@cisco.com>, <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Nathaniel Borenstein wrote:
> Pardon me if I'm missing something obvious here, but
> couldn't one just use either XMPP or Simple for presence,
> associate your "server name" with a Jabber/Simple ID, and
> automatically have your "server" findable via these
> general presence protocols? =20

One not only could, but does.
http://www.pulver.com/fwd/index.html
Nice IP phones are quite inexpensive these days too.
https://secure.pulver.com/pulverinnovations/order_grandstream.html


> Why isn't that a reasonable approach to peer to
> peer in a NAT world?

It is, although it could use some polishing. That's not the issue; you
still don't have a free bridge to the PSTN, there is no way to regulate
telemarketers, does not work when the power fails, if your kids have
kazaa open voice quality stinks because kazaa gobbles it all.

I pay 5 bucks for long distance a month, explain me why I should bother?

Michel.




From owner-ietf@ietf.org  Mon Jan 12 15:23:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16959
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 15:23:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag8VY-0005uY-OA
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 15:17:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag8UK-0005Sv-5Q
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 15:16:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16576
	for <ietf@ietf.org>; Mon, 12 Jan 2004 15:16:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8UI-0005Vq-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:16:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag8Sm-0005My-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:15:04 -0500
Received: from hannibal.servitor.co.uk ([195.188.15.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8R2-00058u-00
	for IETF@ietf.org; Mon, 12 Jan 2004 15:13:16 -0500
Received: from hannibal.servitor.co.uk ([195.188.15.48] helo=iconoplex.co.uk)
	by hannibal.servitor.co.uk with esmtp (Exim 4.14)
	id 1Ag8Qt-000B0G-VS; Mon, 12 Jan 2004 20:13:08 +0000
Message-ID: <4002FFCE.4020407@iconoplex.co.uk>
Date: Mon, 12 Jan 2004 20:13:02 +0000
From: Paul Robinson <paul@iconoplex.co.uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tony Hain <alh-ietf@tndh.net>
CC: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
References: <E1Ag7Kx-0001Nu-00@ietf-mx>
In-Reply-To: <E1Ag7Kx-0001Nu-00@ietf-mx>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony Hain wrote:

>While one aging application does not constitute 'the Internet', this should
>be taken as an early indicator of things that are happing, with more to
>come. 
>http://www.fourmilab.ch/speakfree/eol/
>
>Like it or not, the IETF must stop wasting time and effort building new
>structures on a crumbling framework. A quick scan of the IESG document queue
>shows that the vast majority of the workload is still not seriously focused
>on making IPv6 the default protocol. 
>

Methinks you doth protest too much.

The Internet is not dying. It's growing every day. However, both end-users and yes, even service providers, are becoming exponentially stupid with time. They neither understand the issues we believe to be important at a technical level, nor do they care about understanding them anytime soon. The modern Internet is run by marketing, not technical, requirements.

IPv6 will not take off any time soon because neither the end-user nor the service provider sees the need. The moment AOL, Wanadoo, Tiscali, World Online et al shout out "we *need* IPv6" it will happen. Quickly.

So, is it time for some serious lobbying, or do we wait until half the applications out there suddenly stop working?

And out of curiosity, how many people here have migrated their entire network to IPv6 already to set a good example and show how it's done? Yes, thought so.

-- 
Paul Robinson





From owner-ietf@ietf.org  Mon Jan 12 15:40:24 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17790
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 15:40:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag8i8-0007Bc-Jv
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 15:30:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag8hP-00075U-QM
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 15:30:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17414
	for <ietf@ietf.org>; Mon, 12 Jan 2004 15:30:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8hO-00065e-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:30:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag8g6-00062k-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:28:51 -0500
Received: from firecrest.mail.pas.earthlink.net ([207.217.121.247])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8es-0005wc-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:27:34 -0500
Received: from [38.119.96.105] (helo=[192.168.0.2])
	by firecrest.mail.pas.earthlink.net with asmtp (Exim 3.33 #1)
	id 1Ag8eh-0002fR-00; Mon, 12 Jan 2004 12:27:23 -0800
Date: Mon, 12 Jan 2004 15:18:21 -0500
From: Gene Gaines <gene.gaines@gainesgroup.com>
Organization: Gaines Group
X-Priority: 3 (Normal)
Message-ID: <16079252054.20040112151821@gainesgroup.com>
To: Ken Hornstein <kenh@cmf.nrl.navy.mil>
CC: ietf@ietf.org
Subject: Re: Visa for South Korea
In-Reply-To: <200401121712.i0CHCRRr007502@ginger.cmf.nrl.navy.mil>
References: Message from Sam Hartman <hartmans@mit.edu>    of "Sun, 11 Jan 2004
 17:42:24 EST." <tslsmimksz3.fsf@konishi-polis.mit.edu>
 <200401121712.i0CHCRRr007502@ginger.cmf.nrl.navy.mil>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: e892362a6fa8b5d372cc1e1b0924a179239a348a220c2609e00ca84ec6fa1101237031a119a798e1548b785378294e88350badd9bab72f9c350badd9bab72f9c
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=PRIORITY_NO_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ken,

As it happens, I attended a dinner Saturday that was addressed
by Ambassador Han, the Korean Ambassador to the U.S.

Taking up the Korean visa issue today, I spoke with an official
in the Washington DC visa section.

I believe I can state the visa regulation as it applies to U.S.
citizens.

  - Individuals traveling to Korean to attend the IETF meeting
    do not need a visa, as they are traveling to attend a
    non-profit conference.  They can stay in Korea up to 30
    day for such purpose and for tourism.

  - If you travel to Korea for business purposes, such as
    meeting customers or other business purposes, then a
    visa is needed.

  - This applies only to private U.S. citizens.  Government
    employees and citizens of other countries need to contact
    their local Korean embassy for a determination in their
    case. Ken, in your case, if you are a government employee,
    you will need a visa.

  - Another consideration concerning visa.  People attend
    IETF meetings as individuals, not directly representing
    their company -- and clearly a private individual traveling
    to attend a nonprofit technical meeting clearly does not
    need a visa.

Warning.  I am only relaying what was told to me today by a
responsible embassy official.  I am not attending the Seoul meeting,
but if I was, I would want to have an official statement from an
Korean official regarding the visa request.  One official who can
handle such a request at the visa section in Washington DC is
Mr. Sang Yoo.  I am copying this email to him.  A member of the
meeting committee might want to put a formal query to him, and
email his answer to the list.

For Mr. Yoo, details of the meeting:
59th IETF Meeting, Seoul, South Korea, 29 February - 5 March 2004.
For information about the IETF (Internet Engineering Task Force)
see: http://www.ietf.org/overview.html



    

Gene Gaines
gene.gaines@gainesgroup.com

On Monday, January 12, 2004, 12:12:27 PM, Ken wrote:

>>I'd be interested in answers people get from other consulate/embassy
>>staff both from locations other than Boston and with different
>>phrasings of the question.

> Well, I finally was able to talk to someone at the Washington, DC, embassy.

> Their answer?  "We're not sure, but you might need one".

> I basically took the same tactic that Sam took; I described the IETF as
> a professional organization, and explained I was attending a meeting
> of this organization.  At first he said that a visa was not required,
> because this counts as a "visit", but then he said he wasn't sure, and
> maybe I would need a visa.

> I then started asking a few more questions.  I asked what exactly
> "business" travel was defined as, and after going around a few times
> about it, he basically settled on the definition that if you were
> travelling to Korea to a meeting for a "business purpose", then you
> need a visa.

> The whole thing was as clear as mud, and he clearly wasn't that familiar
> with the regulations.  I might try calling a few more consulates to
> see if I can find someone more knowledgeable.

> BTW, has anyone been able to contact the host web site?  (The one
> linked off of the IETF Seoul meeting web page)

> http://www.tta.or.kr/ietf59/index.htm

> I've been trying for a few days now and no go.  It doesn't seem like
> a local network problem from where I'm sitting, but sometimes it's hard
> to be sure.

> --Ken


-- 




From owner-ietf@ietf.org  Mon Jan 12 16:05:40 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19129
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 16:05:40 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag92m-00087i-7h
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 15:52:16 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag8wb-0007vi-VM
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 15:45:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18374
	for <ietf@ietf.org>; Mon, 12 Jan 2004 15:45:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8wa-00074A-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:45:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag8wU-000738-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:45:46 -0500
Received: from ginger.cmf.nrl.navy.mil ([134.207.10.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8w9-000718-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:45:25 -0500
Received: from cmf.nrl.navy.mil (elvis.cmf.nrl.navy.mil [134.207.10.38])
	(authenticated bits=0)
	by ginger.cmf.nrl.navy.mil (8.12.7/8.12.7) with ESMTP id i0CKjLRr012553
	for <ietf@ietf.org>; Mon, 12 Jan 2004 15:45:22 -0500 (EST)
Message-Id: <200401122045.i0CKjLRr012553@ginger.cmf.nrl.navy.mil>
To: ietf@ietf.org
Subject: Re: Visa for South Korea 
In-Reply-To: Message from Gene Gaines <gene.gaines@gainesgroup.com> 
   of "Mon, 12 Jan 2004 15:18:21 EST." <16079252054.20040112151821@gainesgroup.com> 
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4
	WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d
	gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;Mv(aiO2z~9n.w?@\>kEpSD@*e`
Date: Mon, 12 Jan 2004 15:45:22 -0500
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
X-Spam-Score: () hits=0 User Authenticated
X-Virus-Scanned: NAI Completed
X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>  - Individuals traveling to Korean to attend the IETF meeting
>    do not need a visa, as they are traveling to attend a
>    non-profit conference.  They can stay in Korea up to 30
>    day for such purpose and for tourism.

Ah, okay, this makes sense now, because there was a slight language
issue with the person I spoke with (I hesitate to mention it since I am
a typical American and am only monolingual, but it's relevant here).
The individual I spoke with said several times that if you "paid them
money" (referring to the organization) you needed a visa, but I think
based on the context he really meant "non-profit".  So this agrees
with Sam's information and what you found out.

>  - If you travel to Korea for business purposes, such as
>    meeting customers or other business purposes, then a
>    visa is needed.

Right, there was no confusion on this issue, but this one clearly
doesn't apply.

>  - This applies only to private U.S. citizens.  Government
>    employees and citizens of other countries need to contact
>    their local Korean embassy for a determination in their
>    case. Ken, in your case, if you are a government employee,
>    you will need a visa.

Luckily, I'm not, so that doesn't apply here.

>  - Another consideration concerning visa.  People attend
>    IETF meetings as individuals, not directly representing
>    their company -- and clearly a private individual traveling
>    to attend a nonprofit technical meeting clearly does not
>    need a visa.

Well ... this really depends on what you mean by "representing", I think.
Certainly the _theory_ at the IETF is that people are supposed to be
attending the meetings as individuals.  I've certainly seen a number of
cases where an individual was clearly representing a company rather
than theirself.  But I think it's a fuzzy line if your employer pays
for your trip and your salary while you're at IETF.  Sure, in the IETF
context, they may be just their as theirself.  But it sure would look
like they were representing their company to a third party (say, the
South Korean government).

--Ken



From owner-ietf@ietf.org  Mon Jan 12 16:05:40 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19139
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 16:05:40 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ag98U-0008HR-7X
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 15:58:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag94T-0008DC-Kt
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 15:54:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18559
	for <ietf@ietf.org>; Mon, 12 Jan 2004 15:54:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag94S-0007Gi-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:54:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag92a-0007EU-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:52:05 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag91g-0007CM-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:51:08 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i0CKp8dd055037
	for ietf@ietf.org env-from <vjs>;
	Mon, 12 Jan 2004 13:51:08 -0700 (MST)
Date: Mon, 12 Jan 2004 13:51:08 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401122051.i0CKp8dd055037@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <BF05885C-4538-11D8-9AFA-000A9571873E@guppylake.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Nathaniel Borenstein <nsb@guppylake.com>

> ...
> I also have to say that I fear your approach would help the larger ISPs 
> use spam as an excuse to kill off smaller ISP's...  

How so?  Exactly what is my approach?  Please note what I've said too
many times:
  - I don't currently use a public blacklist and have never used one
      for non-trivial mail.
  - I'm flogging spam defenses that compete with blacklists.

>                                                  and I question the 
> fundamental legitimacy of blocking all of an ISP's customers before 
> there's a fair due process to establish the ISP's culpability. 

"Fair due process" and "free speech" and even "legitimacy" are none
of your concern unless you own the mailbox that would *RECEIVE* the
blocked mail.  No one has any right to send anyone any mail.  We have
only privileges granted by targets of our mail.  If our targets are
foolish and hire ISPs with long histories of both permitting a lot of
outgoing spam and blocking a lot of incoming legitimate mail (see
recent complaints about RR's false positives), then that's just tough
and perhaps we should convince our correspondents to switch ISPs or
find new correspondents.

Good or bad spam filtering is merely a part of the rest of good or bad
SMTP or any other ISP service.  It makes no more sense to condemn the
HTTP protocol because many web pages are junk than it does to condemn
blacklists because some blacklists are junk or used badly.

If you think blacklists are bad because they can be run by fools, then
you also must hate any network authentication and authorization
mechanism.  What's the difference between Kerberos and a mail blacklist?
Both are responsible for summary denial of services.

I fear there are bad reasons for the disdain for blacklists:
 - they are effective against spam from spam friendly ISPs.
 - some of us work for spam friendly ISPs and let the interests of
    our employers color our thinking.
 - some of us are lazy and hire ISPs have been spam friendly.
 - some of us feel we have a devine right to send any mail to anyone
    and are deeply offended by any contrary suggestion, not to mention
    an effective mechanism.


>                                                             "Caring 
> enough about spam" is an awfully slippery concept on which to base a 
> blacklist.

I am offended by your implication that I suggested any such thing. 
I only pointed out that using spam-friendly ISPs has consequences.
(You evidently know about XO's reputation, which I think has improved
lately.)  The only major blacklist that does anything remotely like
your implication is SPEWS, which "escalates" in order to get the
attention of ISPs.  If I did use a blacklist, it wouldn't be SPEWS but
that would be only one reason among serveral.


> ...
> > that is not blacklist, then why can't a blacklist be run properly?
>
> Good point.  That's why I favor giving users access to their spam pool 
> when they suspect problems, and using challenge/response in certain 
> (carefully defined) situations.  A good filtering mechanism is not 
> nearly as black and white as a blacklist.

The last part of that is simply wrong.  Every filtering mechanism is
exactly as black and white as a blacklist.  Whether or not an SMTP
server keeps good logs has nothing to do with whether it decides to
reject messages using blacklists of IP addresses or domain names or
anything else.  If your correspondents use software that consults any
blacklist but doesn't keep good logs, then the fault lies first with
your correspondents for using bad software, second with you for having
foolish correspondents, and not at all with the blacklist.

Yes, I realize that I'm implying that to keep good logs you need to
act on a blacklist (if you use one) at the end of the DATA command
instead of before the HELO.


> > Any fool
> > can set up a blacklist.  That many fools have and other fools have
> > used them does not show that blacklists are bad any more than the ease
> > of setting up an IP network shows TCP is the spawn of the devil.
>
> I will confess that my personal experience makes it very hard for me to 
> be rational on the subject of blacklists, as I fear that any concession 
> to them will only encourage the creation of destructive blacklists by 
> "fools".  In general I prefer a solution that any fool can implement, 
> because one surely will.  

Then you'd better give up on the Internet.  As with much of the net,
the information in and functioning of any spam system is at least
somewhat "administrative" and subject to the whims of any fools
administrating it.  The buyer must beware, not only of hiring a spam
friendly ISP, but contracting with a foolish spam filter.  The greater
fool is often the buyer of services offered by lesser fools.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Mon Jan 12 17:01:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24284
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 17:01:16 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgA0w-0003Hk-7k
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 16:54:26 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag9Y0-00036C-9j
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 16:24:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20711
	for <ietf@ietf.org>; Mon, 12 Jan 2004 16:24:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag9Xx-00016t-00
	for ietf@ietf.org; Mon, 12 Jan 2004 16:24:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag9W0-0000vO-00
	for ietf@ietf.org; Mon, 12 Jan 2004 16:22:28 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag9Uo-0000p1-00
	for IETF@ietf.org; Mon, 12 Jan 2004 16:21:14 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0CLKlZN087389;
	Mon, 12 Jan 2004 22:20:49 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <4002FFCE.4020407@iconoplex.co.uk>
References: <E1Ag7Kx-0001Nu-00@ietf-mx> <4002FFCE.4020407@iconoplex.co.uk>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <3648DE95-4545-11D8-815B-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <IETF@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Death of the Internet - details at 11
Date: Mon, 12 Jan 2004 22:20:57 +0100
To: Paul Robinson <paul@iconoplex.co.uk>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 12-jan-04, at 21:13, Paul Robinson wrote:

> The modern Internet is run by marketing, not technical, requirements.

> IPv6 will not take off any time soon because neither the end-user nor 
> the service provider sees the need. The moment AOL, Wanadoo, Tiscali, 
> World Online et al shout out "we *need* IPv6" it will happen. Quickly.

In other words, you can lead a horse to water, but you can't make it 
drink.

(I wonder what AOL & friends are going to do when they find out that 
the apps won't use the IP version they made happen so quickly, though.)

> So, is it time for some serious lobbying, or do we wait until half the 
> applications out there suddenly stop working?

Wouldn't it be better to focus on providing the water and let the horse 
get thirsty in its own good time?

> And out of curiosity, how many people here have migrated their entire 
> network to IPv6 already to set a good example and show how it's done? 
> Yes, thought so.

Sorry, but that one won't work on me.  :-)




From owner-ietf@ietf.org  Mon Jan 12 17:01:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24288
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 17:01:16 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgA0x-0003M7-VQ
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 16:54:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag9dG-0005i5-6j
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 16:29:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21297
	for <ietf@ietf.org>; Mon, 12 Jan 2004 16:29:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag9d2-0001uY-00
	for ietf@ietf.org; Mon, 12 Jan 2004 16:29:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag9aV-0001Vh-00
	for ietf@ietf.org; Mon, 12 Jan 2004 16:27:07 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag9YN-0001A9-00
	for ietf@ietf.org; Mon, 12 Jan 2004 16:24:55 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0CLOdZN087455;
	Mon, 12 Jan 2004 22:24:40 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <p0601021cbc28ab0ef9f1@[10.0.1.3]>
References: <E1Ag7Kx-0001Nu-00@ietf-mx> <p0601021cbc28ab0ef9f1@[10.0.1.3]>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C0F447C2-4545-11D8-815B-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Death of the Internet - details at 11
Date: Mon, 12 Jan 2004 22:24:49 +0100
To: Gordon Cook <cook@cookreport.com>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 12-jan-04, at 20:55, Gordon Cook wrote:

> http://www.fourmilab.ch/documents/digital-imprimatur/  is the really 
> spooky essay.  Excerpted in my December issue.

> Read the Digital Imprimatur if you haven't already.

I find it a tad on the wordy side... (27731 words, to be precise, more 
than an hour worth of reading.)

> I will take another look at IPv6 before long and would welcome any 
> **private** suggestions on how best to do that.

I would (or rather, did), but oh irony:

    ----- The following addresses had permanent fatal errors -----
<cook@cookreport.com>
     (reason: 550 5.7.1 <cook@cookreport.com>... 213.156.1.123 is 
unwelcome here)




From owner-ietf@ietf.org  Mon Jan 12 17:11:03 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25043
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 17:11:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgACF-00050x-JU
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 17:06:07 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgA6F-00047U-4O
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 16:59:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24203
	for <ietf@ietf.org>; Mon, 12 Jan 2004 16:59:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgA6D-0004UN-00
	for ietf@ietf.org; Mon, 12 Jan 2004 16:59:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgA4H-0004Rt-00
	for ietf@ietf.org; Mon, 12 Jan 2004 16:57:54 -0500
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgA2R-0004Nt-00
	for ietf@ietf.org; Mon, 12 Jan 2004 16:55:59 -0500
Received: from guppylake.com (pcp05307270pcs.wanarb01.mi.comcast.net[68.42.70.186])
          by comcast.net (rwcrmhc12) with SMTP
          id <2004011221552801400ehi4he>; Mon, 12 Jan 2004 21:55:29 +0000
Date: Mon, 12 Jan 2004 16:57:16 -0500
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: IETF Discussion <ietf@ietf.org>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <200401122051.i0CKp8dd055037@calcite.rhyolite.com>
Message-Id: <4954C9CA-454A-11D8-9AFA-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

[my final message to the list on this thread]

On Monday, January 12, 2004, at 03:51  PM, Vernon Schryver wrote:

>> I also have to say that I fear your approach would help the larger 
>> ISPs
>> use spam as an excuse to kill off smaller ISP's...
>
> How so?  Exactly what is my approach?

I'm sorry, you're right, that was totally unfair.  I meant blacklists, 
because you were arguing for them, but that doesn't make "your 
approach" synonymous with blacklists.  My apologies for trivializing 
your position.  s/"your approach"/blacklisting/

> "Fair due process" and "free speech" and even "legitimacy" are none
> of your concern....

I don't want to burden the ietf list with an argument over the nature 
of liberty, but I'd be happy to have that discussion privately if you 
like.

> If you think blacklists are bad because they can be run by fools, then
> you also must hate any network authentication and authorization
> mechanism.

That's only a slight overstatement, actually.

> I am offended by your implication that I suggested any such thing.

I am sorry if I misinterpreted.

> Then you'd better give up on the Internet.

That's a tad oversimplified, isn't it?  Was Yosemite doomed when the 
first candy wrapper was dropped in the valley?  -- Nathaniel




From owner-ietf@ietf.org  Mon Jan 12 17:38:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26162
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 17:38:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgAcB-00076y-NO
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 17:32:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgAbW-00071w-61
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 17:32:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26027
	for <ietf@ietf.org>; Mon, 12 Jan 2004 17:32:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgAbU-0006Hi-00
	for ietf@ietf.org; Mon, 12 Jan 2004 17:32:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgAZh-0006F0-00
	for ietf@ietf.org; Mon, 12 Jan 2004 17:30:22 -0500
Received: from evrtwa1-ar8-4-65-026-048.evrtwa1.dsl-verizon.net ([4.65.26.48] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgAYp-0006Au-00
	for IETF@ietf.org; Mon, 12 Jan 2004 17:29:27 -0500
Received: from eaglet (127.0.0.1:4650)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S41D68> for <IETF@ietf.org> from <alh-ietf@tndh.net>;
	Mon, 12 Jan 2004 14:29:29 -0800
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Paul Robinson'" <paul@iconoplex.co.uk>
Cc: <IETF@ietf.org>
Subject: RE: Death of the Internet - details at 11
Date: Mon, 12 Jan 2004 14:29:24 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <4002FFCE.4020407@iconoplex.co.uk>
Thread-Index: AcPZSIBOyFHR1UehQ0uzV2jeOLFgAgAD9CjQ
Message-Id: <E1AgAYp-0006Au-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

You seem to have missed the point. Not only are we loosing existing
applications, there are untold new things that are not making it to market.
These new applications are unable to generate the critical mass they need to
make any marketing noise because the NAT rich environment is too difficult
for Joe-sixpack to deal with. 

You will never hear a consumer demanding IPv6; that is technology plumbing.
The most they will demand is an app that only works because IPv6 provides
direct access between endpoint peers. You won't hear ISP's demanding IPv6
unless their customers are demanding apps that run over IPv6 (even then the
consumer is more likely to use an automated tunnel and make the clueless ISP
irrelevant). You won't get new apps unless the development community sees a
viable path to personal riches. You won't get the development community to
pay attention to the simplicity afforded by IPv6 until the IETF stops
wasting time trying to extend a dead protocol. Continuing work on IPv4 only
creates the illusion that it is a viable protocol for application developers
to rely on for future income. 

Tony


> -----Original Message-----
> From: Paul Robinson [mailto:paul@iconoplex.co.uk]
> Sent: Monday, January 12, 2004 12:13 PM
> To: Tony Hain
> Cc: IETF@ietf.org
> Subject: Re: Death of the Internet - details at 11
> 
> Tony Hain wrote:
> 
> >While one aging application does not constitute 'the Internet', this
> should
> >be taken as an early indicator of things that are happing, with more to
> >come.
> >http://www.fourmilab.ch/speakfree/eol/
> >
> >Like it or not, the IETF must stop wasting time and effort building new
> >structures on a crumbling framework. A quick scan of the IESG document
> queue
> >shows that the vast majority of the workload is still not seriously
> focused
> >on making IPv6 the default protocol.
> >
> 
> Methinks you doth protest too much.
> 
> The Internet is not dying. It's growing every day. However, both end-users
> and yes, even service providers, are becoming exponentially stupid with
> time. They neither understand the issues we believe to be important at a
> technical level, nor do they care about understanding them anytime soon.
> The modern Internet is run by marketing, not technical, requirements.
> 
> IPv6 will not take off any time soon because neither the end-user nor the
> service provider sees the need. The moment AOL, Wanadoo, Tiscali, World
> Online et al shout out "we *need* IPv6" it will happen. Quickly.
> 
> So, is it time for some serious lobbying, or do we wait until half the
> applications out there suddenly stop working?
> 
> And out of curiosity, how many people here have migrated their entire
> network to IPv6 already to set a good example and show how it's done? Yes,
> thought so.
> 
> --
> Paul Robinson





From owner-ietf@ietf.org  Mon Jan 12 17:58:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27256
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 17:58:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgAwZ-0008Rp-F2
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 17:53:59 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgAsy-0008De-Qr
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 17:50:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26736
	for <ietf@ietf.org>; Mon, 12 Jan 2004 17:50:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgAsu-00076N-00
	for ietf@ietf.org; Mon, 12 Jan 2004 17:50:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgArC-00072g-00
	for ietf@ietf.org; Mon, 12 Jan 2004 17:48:26 -0500
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgAqN-0006xn-00
	for ietf@ietf.org; Mon, 12 Jan 2004 17:47:35 -0500
Received: from unknown.hamachi.org (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id DD7C317921; Mon, 12 Jan 2004 17:47:34 -0500 (EST)
Received: from unknown.hamachi.org (sommerfeld@localhost)
	by unknown.hamachi.org (8.12.5+Sun/8.8.8) with ESMTP id i0CMVr8f001694;
	Mon, 12 Jan 2004 17:31:53 -0500 (EST)
Message-Id: <200401122231.i0CMVr8f001694@unknown.hamachi.org>
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: Nathaniel Borenstein <nsb@guppylake.com>
Cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
In-Reply-To: Message from Nathaniel Borenstein <nsb@guppylake.com> 
   of "Mon, 12 Jan 2004 14:51:43 EST." <BF05885C-4538-11D8-9AFA-000A9571873E@guppylake.com> 
Reply-To: sommerfeld@orchard.arlington.ma.us
Date: Mon, 12 Jan 2004 17:31:53 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> Good point.  That's why I favor giving users access to their spam pool 
> when they suspect problems, and using challenge/response in certain 
> (carefully defined) situations.  

> A good filtering mechanism is not nearly as black and white as a blacklist.

so, you're conflating two things here:
 1) the access control criteria (message source address in blacklist
 vs. "bad" message content as determined by various heuristics).

 2) what happens to the message once the access control decision is
made (rejected at SMTP layer; accepted but bitbucketed; accepted but
quarantined; accepted and placed in regular mailbox; etc.).

you can (and spamassassin does) uses DNSBL's as part of a "not black
and white" decision process, and you can implement both strategies.

One problem with dropping suspected spam into a spam cesspool as
opposed to rejecting it outright in the SMTP session is that many
people (myself included) have neither the time nor the inclination to
wade through our spam cesspools on a regular basis looking for
misclassified messages.

An SMTP-level reject at least gives the sender a real-time indication
that the recipient will not be seeing the message any time soon..

						- Bill



From owner-ietf@ietf.org  Mon Jan 12 18:59:26 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00429
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 18:59:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgBit-000110-9a
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 18:43:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgBhF-0000vK-9K
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 18:42:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29801
	for <ietf@ietf.org>; Mon, 12 Jan 2004 18:42:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgBhD-0001kR-00
	for ietf@ietf.org; Mon, 12 Jan 2004 18:42:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgBfK-0001fK-00
	for ietf@ietf.org; Mon, 12 Jan 2004 18:40:15 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgBe9-0001an-00
	for IETF@ietf.org; Mon, 12 Jan 2004 18:39:02 -0500
Subject: RE: Death of the Internet - details at 11
Date: Mon, 12 Jan 2004 15:38:43 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C83C@server2003.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
Thread-Topic: Death of the Internet - details at 11
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
thread-index: AcPZSIBOyFHR1UehQ0uzV2jeOLFgAgAD9CjQAAMN27A=
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Tony Hain" <alh-ietf@tndh.net>
Cc: <IETF@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Tony Hain wrote:
> You won't get the development community to pay attention
> to the simplicity afforded by IPv6 until the IETF stops
> wasting time trying to extend a dead protocol.

If one in {IPv4,IPv6} could be qualified as dead, it's IPv6. If it was
not for IPv4, the majority of this list would not even be able to read
this.

Michel.




From owner-ietf@ietf.org  Mon Jan 12 18:59:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00456
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 18:59:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgBvT-0001vl-4k
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 18:56:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgBsq-0001SJ-KQ
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 18:54:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00168
	for <ietf@ietf.org>; Mon, 12 Jan 2004 18:54:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgBsp-0002GK-00
	for ietf@ietf.org; Mon, 12 Jan 2004 18:54:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgBqy-0002Ag-00
	for ietf@ietf.org; Mon, 12 Jan 2004 18:52:17 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgBpD-00025m-00
	for ietf@ietf.org; Mon, 12 Jan 2004 18:50:28 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i0CNoRrY096681
	for ietf@ietf.org env-from <vjs>;
	Mon, 12 Jan 2004 16:50:27 -0700 (MST)
Date: Mon, 12 Jan 2004 16:50:27 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401122350.i0CNoRrY096681@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <200401122231.i0CMVr8f001694@unknown.hamachi.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>

> ...
> One problem with dropping suspected spam into a spam cesspool as
> opposed to rejecting it outright in the SMTP session is that many
> people (myself included) have neither the time nor the inclination to
> wade through our spam cesspools on a regular basis looking for
> misclassified messages.

That's too true.  Since the spam collected/rejected by my real mailbox
and personal spam traps exceeded 1000 spam/day, I can only skim envelopes.
If I count duplicates, my average for the last 40 days is 3516/day.

> An SMTP-level reject at least gives the sender a real-time indication
> that the recipient will not be seeing the message any time soon..

There may be a false dichotomy there.  You can reject a message during
the SMTP transaction and so give the sender a real-time indication while
also capturing the entire message in a spam cesspool.  All 787 MBytes
now in my 40-day rolling cesspoll were rejected with a 5yz or 4yz SMTP
response.  That many systems don't capture what they reject implies
nothing about anything except those SMTP servers.

I'm flummoxed by criticism of external DNS blacklists based on the
lack logging by SMTP servers.  That's predictable among the general
public, but not here.

This thread is related to the nearby thread about the end of life
announcement for SpeakFreely.  The problem in both cases is less with
evil media conglomerates converting the Internet into TV than with people
who won't feed themselves.  Instead of getting their code and networks
running IPv6, they install NAT boxes and complain about the RIAA.
Contrary to the whines from ISPs with major spam problem, those that
have real (including enforced) anti-spam policies don't have spamming
customers.  Instead of paying the extra cost to hire an ISP that cares
enough to not have spamming customers, people complain about the evils
of blacklists.  Instead of taking the extra trouble to use an operating
system or at least an MTA that is not a worm delivery and spam
facilitation system, they send mail to random, spam-obsessed strangers
like me asking how to add spam filtering to Outlook.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Mon Jan 12 19:36:36 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02088
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 19:36:36 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgCRY-0004JX-OY
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 19:30:04 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgCLq-00043S-VT
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 19:24:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01654
	for <ietf@ietf.org>; Mon, 12 Jan 2004 19:24:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgCLp-000416-00
	for ietf@ietf.org; Mon, 12 Jan 2004 19:24:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgCJz-0003v4-00
	for ietf@ietf.org; Mon, 12 Jan 2004 19:22:16 -0500
Received: from 170.cust8.nsw.dsl.ozemail.com.au ([203.102.235.170] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgCI7-0003jl-00
	for ietf@ietf.org; Mon, 12 Jan 2004 19:20:19 -0500
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP id 984303F02A
	for <ietf@ietf.org>; Tue, 13 Jan 2004 10:49:21 +1030 (CST)
Date: Tue, 13 Jan 2004 10:49:21 +1030
From: Mark Smith <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
To: ietf@ietf.org
Subject: Re: dire outlook on internet and NAT
Message-Id: <20040113104921.6258ef2a.ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
In-Reply-To: <6.0.1.1.2.20040112102632.04644718@mira-sjc5-b.cisco.com>
References: <6.0.1.1.2.20040112102632.04644718@mira-sjc5-b.cisco.com>
Organization: The No Sense Organisation (http://www.nosense.org)
X-Mailer: Sylpheed version 0.9.8a (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Mon, 12 Jan 2004 10:29:02 -0800
Fred Baker <fred@cisco.com> wrote:

> Interesting reading: some have been asking what the cost of
> moving from a peer-to-peer to a service/consumer model are, in
> terms of applications deployed and the ability to build more
> robust business models. Many ISPs are thinking in terms of VoIP
> as a next generation business, the one after "selling
> bandwidth". But there are issues with that as well...
> 
> 	http://www.fourmilab.ch/speakfree/eol/
> 

John's articles were part of the motivation for my question as to
whether IPv4 (and IPv4 NAT) would be formally deprecated when
IPv6 was"ready", which I asked a few months ago on the IPv6 ML.

For those interested in reading or reviewing the ensuing
discussion, here is a URL.

http://marc.theaimsgroup.com/?l=ipng&m=106614091529296&w=2

Admittedly I can't remember where I read it, but I've come across
a suggestion that enterprise networks adopting IPv6 is likely to
happen before ISPs provide it in any big way, as enterprise
networks have more to gain from the technology (well, possibly,
assuming they can be convinced that "proper" address space is
better than NAT). Once enterprises have it, they will then ask
for it from their ISP. I'd agree that expecting the drive for it
to come from ISPs is probably incorrect.

Maybe the focus needs to be to work on IPv6 protocols that
enterprises need. Anybody want to work on NetBIOS over IPv6 ?
After all, File and Print would have to be the "killer"
application for enterprise networks - it's the application that
 got networks into most enterprises in the first place in
the last 10 years.

Regards,
Mark.



From owner-ietf@ietf.org  Mon Jan 12 20:26:05 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04309
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 20:26:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgD8x-0002WF-My
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 20:14:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgD8O-0002TM-5K
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 20:14:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03279
	for <ietf@ietf.org>; Mon, 12 Jan 2004 20:14:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgD8M-0006Xl-00
	for ietf@ietf.org; Mon, 12 Jan 2004 20:14:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgD6W-0006Rr-00
	for ietf@ietf.org; Mon, 12 Jan 2004 20:12:25 -0500
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgD5b-0006MW-00
	for ietf@ietf.org; Mon, 12 Jan 2004 20:11:27 -0500
Received: from unknown.hamachi.org (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id DDCF717922; Mon, 12 Jan 2004 20:11:26 -0500 (EST)
Received: from unknown.hamachi.org (sommerfeld@localhost)
	by unknown.hamachi.org (8.12.5+Sun/8.8.8) with ESMTP id i0CN4FBj005289;
	Mon, 12 Jan 2004 18:04:15 -0500 (EST)
Message-Id: <200401122304.i0CN4FBj005289@unknown.hamachi.org>
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: Gene Gaines <gene.gaines@gainesgroup.com>
Cc: Ken Hornstein <kenh@cmf.nrl.navy.mil>, ietf@ietf.org
Subject: Re: Visa for South Korea 
In-Reply-To: Message from Gene Gaines <gene.gaines@gainesgroup.com> 
   of "Mon, 12 Jan 2004 15:18:21 EST." <16079252054.20040112151821@gainesgroup.com> 
Reply-To: sommerfeld@orchard.arlington.ma.us
Date: Mon, 12 Jan 2004 18:04:15 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>   - Individuals traveling to Korean to attend the IETF meeting
>     do not need a visa, as they are traveling to attend a
>     non-profit conference.  They can stay in Korea up to 30
>     day for such purpose and for tourism.
> 
>   - If you travel to Korea for business purposes, such as
>     meeting customers or other business purposes, then a
>     visa is needed.

It's typical for my activity at IETF to fall somewhere between these
two cases.

I run into employees of my employer's customers and suppliers at IETF
all the time.  Small amounts of "business"-related discussions
invariably occur..

						- Bill










From owner-ietf@ietf.org  Mon Jan 12 20:58:51 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06075
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 20:58:51 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgDkh-0004Wc-3y
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 20:53:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgDhO-0004Mn-Rh
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 20:50:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05829
	for <ietf@ietf.org>; Mon, 12 Jan 2004 20:50:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgDhN-0001R5-00
	for ietf@ietf.org; Mon, 12 Jan 2004 20:50:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgDfR-0001Js-00
	for ietf@ietf.org; Mon, 12 Jan 2004 20:48:29 -0500
Received: from nr2baymi.bay.mi.charter.com ([24.247.24.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgDeg-0001Di-00
	for ietf@ietf.org; Mon, 12 Jan 2004 20:47:42 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by nr2baymi.bay.mi.charter.com (8.11.7p1+Sun/8.11.6) with SMTP id i0D1lbv09362
	for <ietf@ietf.org>; Mon, 12 Jan 2004 20:47:37 -0500 (EST)
Received: (qmail 1313 invoked by uid 0); 13 Jan 2004 01:47:34 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.088972 secs); 13 Jan 2004 01:47:34 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 13 Jan 2004 01:47:34 -0000
Message-Id: <6.0.0.22.0.20040112204043.02b83af0@mjs.alientech.net>
X-Mailer: Eudora
Date: Mon, 12 Jan 2004 20:47:32 -0500
To: ietf@ietf.org
From: ietf@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 06:50 PM 1/12/2004, Vernon Schryver wrote...
>Instead of paying the extra cost to hire an ISP that cares
>enough to not have spamming customers, people complain about the evils
>of blacklists. 

Feh. Once again with an argument based on incorrect assumptions. 

I don't spam. I would preferentially route email direct for two main reasons: 1) privacy - routing via my ISP's outbound SMTP gives them the right to intercept and read my email, according the ECPA; 2) control - sending from my own system allows me to control retry attempts and times, instead of being forced to wait 4 days for my ISP to bounce an undelivered back to me, assuming they don't just silently lose it.

I can't do so because my IP address is on a blacklist. I have cable modem, but the world thinks I'm a dial-up. For that reason alone, having nothing whatsoever to do with spam, I'm forced to give up privacy and control of my communications.

"Anti-spam" initiatives that are based on such blacklists are quite simply the failed results of irrational, fascist thought. Regardless of your exact definition of spam, all reasonable ones I've heard have one thing in common - it's based on CONTENT, not IP address. Blacklists couldn't care less about content - legitimate email or spam, out it goes, to the detriment of communications, which is the Internet's raison d'etre. I take that back, it used to be that way. Now the Internet is meant to make big corporations lots of money.

Blacklists also, quite clearly, don't work to eliminate spam. 





From owner-ietf@ietf.org  Mon Jan 12 22:16:53 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09656
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 22:16:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgEvG-0001VX-Td
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 22:08:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgEuQ-0001Sz-GK
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 22:08:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09195
	for <ietf@ietf.org>; Mon, 12 Jan 2004 22:08:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgEuO-00067P-00
	for ietf@ietf.org; Mon, 12 Jan 2004 22:08:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgEsU-00063R-00
	for ietf@ietf.org; Mon, 12 Jan 2004 22:06:02 -0500
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgEqe-0005xq-00
	for ietf@ietf.org; Mon, 12 Jan 2004 22:04:08 -0500
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 XAA07732;
	Mon, 12 Jan 2004 23:06:38 -0500
Date: Mon, 12 Jan 2004 21:58:24 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: <dean@vista.av8.net>
To: Mike S <ietf@flatsurface.com>
cc: <ietf@ietf.org>
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
In-Reply-To: <6.0.0.22.0.20040112204043.02b83af0@mjs.alientech.net>
Message-ID: <Pine.LNX.4.33.0401122124380.16714-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 12 Jan 2004, Mike S wrote:

> At 06:50 PM 1/12/2004, Vernon Schryver wrote...
> >Instead of paying the extra cost to hire an ISP that cares
> >enough to not have spamming customers, people complain about the evils
> >of blacklists.
>
> Feh. Once again with an argument based on incorrect assumptions.
>
> I don't spam. I would preferentially route email direct for two main
> reasons:

1) privacy - routing via my ISP's outbound SMTP gives them
> the right to intercept and read my email, according the ECPA;

Err, Just the opposite is more freqently the case. Most ISP's usually only
have the right to block spam. Some don't even have that right, if you
don't purchase their spam filter service.  The ECPA specifically prohibits
the ISP from exceeding its limited authority.  There was recently a very
good ECPA case of a company (not an ISP) that exceeded its authority:
Konop V Hawaiian Airlines.

But privacy is still an issue, because you don't know that the ISP's
admins aren't breaking the law.  Reading mail in a mail queue is far
easier than using a sniffer, and much more tempting.  Some ISPs are very
lax on administrator discipline, and some very well-known people such as
Steven Bellovin still claim the ECPA doesn't apply to the internet at all.
[FYI, I will be posting the House and Senate reports (scans of copies, but
mostly readable) on the web with a lot of other information about the ECPA
and the Computer Fraud and Abuse Act, including cases and other
information, as well as cases involving blacklists and Anti-Trust. The
ECPA house and senate reports are very illuminating.  I'll post a URL if
people are interested.]

2) control - sending from my own system allows me to control retry
> attempts and times, instead of being forced to wait 4 days for my ISP
> to bounce an undelivered back to me, assuming they don't just silently
> lose it.

If your contract allows you to run your own system, then the ISP would not
be allowed to prevent you from doing that.  This could be made into an
ECPA issue---some people think it is merely and only a contract
non-performance issue and said contract excludes liability for failure to
perform.  Like the Sherman Anti-Trust Act, the ECPA is a criminal statute
with civil actions permitted, and carries its own civil and criminal
penalties.

Of course, if your contract does not allow you to run your own system,
then you don't have a complaint about blacklists blocking it.

Assuming you have permission to operate your system, then there are many
good reasons besides the ones you've listed to do that.

> I can't do so because my IP address is on a blacklist. I have cable
> modem, but the world thinks I'm a dial-up. For that reason alone,
> having nothing whatsoever to do with spam, I'm forced to give up
> privacy and control of my communications.

This is what anti-trust law is for. A blacklist is group boycott. If it
significantly harms your business, then it is illegal.  The blacklist and
the blacklist subscribers can be (and have been) enjoined from
blacklisting genuine business.

> "Anti-spam" initiatives that are based on such blacklists are quite
> simply the failed results of irrational, fascist thought. Regardless
> of your exact definition of spam, all reasonable ones I've heard have
> one thing in common - it's based on CONTENT, not IP address.
> Blacklists couldn't care less about content - legitimate email or
> spam, out it goes, to the detriment of communications, which is the
> Internet's raison d'etre. I take that back, it used to be that way.
> Now the Internet is meant to make big corporations lots of money.
>
> Blacklists also, quite clearly, don't work to eliminate spam.

True.  But rational argument isn't enough to overcome irrational facist,
thought. For that we have courts and laws.

		--Dean




From owner-ietf@ietf.org  Mon Jan 12 22:50:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11226
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 22:50:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgFQF-0003Hq-5a
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 22:40:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgFPz-0003FJ-QT
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 22:40:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10827
	for <ietf@ietf.org>; Mon, 12 Jan 2004 22:40:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgFPx-0000F5-00
	for ietf@ietf.org; Mon, 12 Jan 2004 22:40:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgFO8-00007b-00
	for ietf@ietf.org; Mon, 12 Jan 2004 22:38:44 -0500
Received: from nr2baymi.bay.mi.charter.com ([24.247.24.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgFMh-0007mt-00
	for ietf@ietf.org; Mon, 12 Jan 2004 22:37:15 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by nr2baymi.bay.mi.charter.com (8.11.7p1+Sun/8.11.6) with SMTP id i0D3avv27878
	for <ietf@ietf.org>; Mon, 12 Jan 2004 22:36:57 -0500 (EST)
Received: (qmail 2309 invoked by uid 0); 13 Jan 2004 03:36:54 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.132637 secs); 13 Jan 2004 03:36:54 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 13 Jan 2004 03:36:53 -0000
Message-Id: <6.0.0.22.0.20040112222640.03fc76b0@mjs.alientech.net>
X-Mailer: Eudora
Date: Mon, 12 Jan 2004 22:35:30 -0500
To: Dean Anderson <dean@av8.com>
From: ietf@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Cc: <ietf@ietf.org>
In-Reply-To: <Pine.LNX.4.33.0401122124380.16714-100000@vista.av8.net>
References: <6.0.0.22.0.20040112204043.02b83af0@mjs.alientech.net>
 <Pine.LNX.4.33.0401122124380.16714-100000@vista.av8.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 09:58 PM 1/12/2004, Dean Anderson wrote...
>On Mon, 12 Jan 2004, Mike S wrote:
>1) privacy - routing via my ISP's outbound SMTP gives them
>> the right to intercept and read my email, according the ECPA;
>
>Err, Just the opposite is more freqently the case.The ECPA specifically prohibits the ISP from exceeding its limited authority.

Cite, please. I've got one:

"(2)(a)(i) It shall not be unlawful under this chapter for an ... agent of a provider  of  wire  or  electronic communication  service,  whose facilities  are used in the transmission of a wire or  electronic communication, to intercept, disclose, or use that  communication in the normal  course of his employment..."

>2) control - sending from my own system allows me to control retry
>> attempts and times, instead of being forced to wait 4 days for my ISP
>> to bounce an undelivered back to me, assuming they don't just silently
>> lose it.
>
>If your contract allows you to run your own system, then the ISP would not
>be allowed to prevent you from doing that.  This could be made into an
>ECPA issue---some people think it is merely and only a contract
>non-performance issue and said contract excludes liability for failure to
>perform.  Like the Sherman Anti-Trust Act, the ECPA is a criminal statute
>with civil actions permitted, and carries its own civil and criminal
>penalties.

My ISP's support of the MAPS DUL, and the use of the MAPS system by others, is a violation of 18 U.S.C. 1030. Email me for details, but I've covered this on this list recently.

>Of course, if your contract does not allow you to run your own system,
>then you don't have a complaint about blacklists blocking it.

There is nothing to prohibit direct routing of email.





From owner-ietf@ietf.org  Mon Jan 12 22:52:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11270
	for <ietf-web-archive@odin.ietf.org>; Mon, 12 Jan 2004 22:52:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgFXy-0003WI-Te
	for ietf-list@asgard.ietf.org; Mon, 12 Jan 2004 22:48:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgFXS-0003Te-LT
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 22:48:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11149
	for <ietf@ietf.org>; Mon, 12 Jan 2004 22:48:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgFXQ-0000ap-00
	for ietf@ietf.org; Mon, 12 Jan 2004 22:48:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgFVg-0000X1-00
	for ietf@ietf.org; Mon, 12 Jan 2004 22:46:33 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgFV2-0000SD-00
	for ietf@ietf.org; Mon, 12 Jan 2004 22:45:53 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i0D3jnpS058424
	for ietf@ietf.org env-from <vjs>;
	Mon, 12 Jan 2004 20:45:49 -0700 (MST)
Date: Mon, 12 Jan 2004 20:45:49 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401130345.i0D3jnpS058424@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <6.0.0.22.0.20040112204043.02b83af0@mjs.alientech.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: ietf@flatsurface.com (Mike S)

> ...
> >Instead of paying the extra cost to hire an ISP that cares
> >enough to not have spamming customers, people complain about the evils
> >of blacklists. 

> ...
> I can't do so because my IP address is on a blacklist. I have
> cable modem, but the world thinks I'm a dial-up. For that reason
> alone, having nothing whatsoever to do with spam, I'm forced to
> give up privacy and control of my communications.

Mr. Sauve could rent an IP address that is not on dial-up or dynamic
blacklists and run his systems there.  A remote co-lo or hosting service
would cost more than the $30/month or whatever slum rate he is paying
for cable modem service.  Or he could convince his correspondents to
whitelist his IP address or stop using the relevant blacklists.  Either
he has not tried that, his correspondents also pay slum rates for slum
service, or they don't want enough to hear from him to increase their
spam loads.

Perhaps I should ask if Mr. Sauve is violating the terms of service
of his ISP.  What does Charter say about "servers"?  Did Charter
give Mr. Sauve's IP address to the blacklists that bother him?

Or perhaps he has already rented an IP address that is not dynamic.
But if he has done that, where is his complaint?  Is it just
Interveloce/GO International's rates?


> "Anti-spam" initiatives that are based on such blacklists are
> quite simply the failed results of irrational, fascist thought.

In that he is calling his correspondents irrational fascists, because
it is they who have chosen to reject his mail.

Never mind that facism has something to do with "centralized autocratic
government headed by a dictatorial leader, severe economic and social
regimentation, and forcible suppression of opposition" and that seems
like the opposite of the anarchy of blacklists.
Also ignore the fact that a taxi or pizza delivery service refusing
to go to dangerous parts of town is no more irrational than refusing
mail from the IP address neighborhoods that are major sources of spam.
Any individual is unlikely to be a spammer or mugger, but the statistical
risk/reward ratio is too high.  By all accounts, the odds that the the
next SYN to your port 25 from a "dynamic" IP address involve spam are
very high.


> Regardless of your exact definition of spam, all reasonable ones
> I've heard have one thing in common - it's based on CONTENT, not
> IP address. Blacklists couldn't care less about content 

That's nonsense.  Blacklists do care about content in a statistical
sense.  If blacklists don't care about content, then neither do so
called Bayseian filters.  I've often said that lists like the DUL bug
me, but not because they are useless.  Lists like the DUL catch a
lot of spam and little legitimate mail.


>                                                      - legitimate
> email or spam, out it goes, to the detriment of communications,
> which is the Internet's raison d'etre. I take that back, it used
> to be that way. Now the Internet is meant to make big corporations
> lots of money.

I've been around for a few years (TIP-25 (DOCB) in 1972), but I don't
recall that Communication in the sense Mr. Sauve means was ever the
Internet's raison d'etre.  15 years ago, would be communalists were
bemoaning the commercialization of the net and interference with
capital-C-Communication, by which they meant they deserved free
bandwidth.  Their successors complain about the free ride they never
got.  Back in Mr. Sauve's golden era, his perfect unfiltered IP bandwdith
was either not available to small or commercial outfits like Alientech
LLC or it would have cost 2000% more (>$5000/year) for 10% as many
bits/sec (56K).


> Blacklists also, quite clearly, don't work to eliminate spam. 

No honest person who actually looks at spam agrees with that.
Good blacklists (e.g. CRL) are better than 70% effective with 
false negative rates that large, very conservative corportations
can tolerate.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Tue Jan 13 01:44:01 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15816
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 01:44:01 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgI8t-0003U0-U5
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 01:35:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgI27-0003Gm-D3
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 01:28:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15501
	for <ietf@ietf.org>; Tue, 13 Jan 2004 01:28:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgI25-0005B7-00
	for ietf@ietf.org; Tue, 13 Jan 2004 01:28:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgI0H-000578-00
	for ietf@ietf.org; Tue, 13 Jan 2004 01:26:18 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgHye-00054H-00
	for ietf@ietf.org; Tue, 13 Jan 2004 01:24:36 -0500
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i0D6ONf15585;
	Mon, 12 Jan 2004 22:24:24 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200401130624.i0D6ONf15585@boreas.isi.edu>
Subject: Re: Visa for South Korea
In-Reply-To: <200401122304.i0CN4FBj005289@unknown.hamachi.org> from Bill Sommerfeld at "Jan 12, 4 06:04:15 pm"
To: sommerfeld@orchard.arlington.ma.us
Date: Mon, 12 Jan 2004 22:24:23 -0800 (PST)
Cc: gene.gaines@gainesgroup.com, kenh@cmf.nrl.navy.mil, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

% >   - Individuals traveling to Korean to attend the IETF meeting
% >     do not need a visa, as they are traveling to attend a
% >     non-profit conference.  They can stay in Korea up to 30
% >     day for such purpose and for tourism.
% > 
% >   - If you travel to Korea for business purposes, such as
% >     meeting customers or other business purposes, then a
% >     visa is needed.
% 
% It's typical for my activity at IETF to fall somewhere between these
% two cases.
% 
% I run into employees of my employer's customers and suppliers at IETF
% all the time.  Small amounts of "business"-related discussions
% invariably occur..
% 
% 						- Bill

	get a visa.

--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 Jan 13 01:44:02 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15834
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 01:44:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgIER-0003ju-3c
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 01:40:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgIDi-0003hc-6a
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 01:40:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15758
	for <ietf@ietf.org>; Tue, 13 Jan 2004 01:40:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgIDg-0005VG-00
	for ietf@ietf.org; Tue, 13 Jan 2004 01:40:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgIBn-0005Ti-00
	for ietf@ietf.org; Tue, 13 Jan 2004 01:38:12 -0500
Received: from rc-dmz.felix.nlri.ca ([192.5.4.54] helo=felix.automagic.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgIB3-0005Rm-00
	for IETF@ietf.org; Tue, 13 Jan 2004 01:37:25 -0500
Received: from [199.212.90.24] (helo=[199.212.90.24])
	by felix.automagic.org with asmtp (TLSv1:RC4-SHA:128)
	(Exim 4.20)
	id 1AgIB0-000KZb-Hw; Tue, 13 Jan 2004 06:37:22 +0000
In-Reply-To: <4002FFCE.4020407@iconoplex.co.uk>
References: <E1Ag7Kx-0001Nu-00@ietf-mx> <4002FFCE.4020407@iconoplex.co.uk>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F9421262-4592-11D8-AB12-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
Cc: Tony Hain <alh-ietf@tndh.net>, IETF@ietf.org
From: Joe Abley <jabley@isc.org>
Subject: Re: Death of the Internet - details at 11
Date: Tue, 13 Jan 2004 01:37:35 -0500
To: Paul Robinson <paul@iconoplex.co.uk>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On 12 Jan 2004, at 15:13, Paul Robinson wrote:

> IPv6 will not take off any time soon because neither the end-user nor 
> the service provider sees the need. The moment AOL, Wanadoo, Tiscali, 
> World Online et al shout out "we *need* IPv6" it will happen. Quickly.

Interestingly, whenever we deploy an F root nameserver, the one 
operator we can absolutely rely on to do IPv6 peering with us is 
Tiscali.

> And out of curiosity, how many people here have migrated their entire 
> network to IPv6 already to set a good example and show how it's done? 
> Yes, thought so.

AS 3557 been routing both native v6 and v4 for some time now, and most 
of the content we host is served over both. AS3557 operates over three 
sites in California with cisco and Juniper routers; we're not big, but 
we're maybe a microcosm of a larger backbone/transit provider network.

The operational cost of supporting both v4 and v6 from the network 
perspective not great, based on our experience (although the support 
load for v6 clients to content hosted in our network is currently much 
lower than for v4 clients, as you'd expect).

I'd be very happy to share more details about what we're running with 
people who have interest.


Joe




From owner-ietf@ietf.org  Tue Jan 13 04:49:48 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03040
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 04:49:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgL2b-0000My-Je
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 04:40:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgL1q-0000LP-Ob
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 04:40:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02675
	for <ietf@ietf.org>; Tue, 13 Jan 2004 04:40:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgL1o-0002bH-00
	for ietf@ietf.org; Tue, 13 Jan 2004 04:40:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgKzr-0002Xr-00
	for ietf@ietf.org; Tue, 13 Jan 2004 04:38:04 -0500
Received: from hannibal.servitor.co.uk ([195.188.15.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgKxw-0002VG-00
	for IETF@ietf.org; Tue, 13 Jan 2004 04:36:05 -0500
Received: from paul by hannibal.servitor.co.uk with local (Exim 4.14)
	id 1AgKxz-000Dap-4o; Tue, 13 Jan 2004 09:36:07 +0000
Date: Tue, 13 Jan 2004 09:36:07 +0000
From: Paul Robinson <paul@iconoplex.co.uk>
To: Tony Hain <alh-ietf@tndh.net>
Cc: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <20040113093607.GM27903@iconoplex.co.uk>
References: <4002FFCE.4020407@iconoplex.co.uk> <E1AgAYp-0006Au-00@ietf-mx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1AgAYp-0006Au-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Jan 12, 2004 at 02:29:24PM -0800, Tony Hain wrote:

> You will never hear a consumer demanding IPv6; that is technology plumbing.
> The most they will demand is an app that only works because IPv6 provides
> direct access between endpoint peers. You won't hear ISP's demanding IPv6

But that app has to be something particularly splendid. And in Europe at 
least, NAT is not as prevalent as some think it is.

> unless their customers are demanding apps that run over IPv6 (even then the
> consumer is more likely to use an automated tunnel and make the clueless ISP
> irrelevant). You won't get new apps unless the development community sees a
> viable path to personal riches. You won't get the development community to
> pay attention to the simplicity afforded by IPv6 until the IETF stops
> wasting time trying to extend a dead protocol. Continuing work on IPv4 only
> creates the illusion that it is a viable protocol for application developers
> to rely on for future income. 

Are you suggesting then, that all RFCs based on IPv6 should be... stopped? 
By the sounds of it, what you're looking for is for us as a community to 
refuse to deal with IPv4 any more, that we wash our hands of it, and make 
vendors realise that they are going to be unable to support IPv4 for more 
than a few years?

It's brutal, but I can see the point. Thinking about a cut-off date for IPv4 
would indeed provoke some interesting discussion, but I think a lot of 
people still want to hang onto IPv4. Even so, how does July 31st 2005 sound 
to everybody?
 
-- 
Paul Robinson



From owner-ietf@ietf.org  Tue Jan 13 05:39:51 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04833
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 05:39:51 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgLsr-00021d-92
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 05:34:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgLs7-00020K-Jx
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 05:34:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04695
	for <ietf@ietf.org>; Tue, 13 Jan 2004 05:34:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgLs5-0004mi-00
	for ietf@ietf.org; Tue, 13 Jan 2004 05:34:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgLq8-0004jL-00
	for ietf@ietf.org; Tue, 13 Jan 2004 05:32:05 -0500
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgLoI-0004h0-00
	for IETF@ietf.org; Tue, 13 Jan 2004 05:30:10 -0500
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 KAA00829
	for <IETF@ietf.org>; Tue, 13 Jan 2004 10:30:10 GMT
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id KAA05638
	for <IETF@ietf.org>; Tue, 13 Jan 2004 10:30:00 GMT
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i0DAU5516278
	for IETF@ietf.org; Tue, 13 Jan 2004 10:30:05 GMT
Date: Tue, 13 Jan 2004 10:30:05 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <20040113103005.GE14378@login.ecs.soton.ac.uk>
References: <4002FFCE.4020407@iconoplex.co.uk> <E1AgAYp-0006Au-00@ietf-mx> <20040113093607.GM27903@iconoplex.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040113093607.GM27903@iconoplex.co.uk>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, Jan 13, 2004 at 09:36:07AM +0000, Paul Robinson wrote:
> 
> But that app has to be something particularly splendid. And in Europe at 
> least, NAT is not as prevalent as some think it is.

It is prevalent wherever there is broadband.  And that is where (with the
extra bandwidth and always-on) connectivity into the network is desirable.
 
> Are you suggesting then, that all RFCs based on IPv6 should be... stopped? 
> By the sounds of it, what you're looking for is for us as a community to 
> refuse to deal with IPv4 any more, that we wash our hands of it, and make 
> vendors realise that they are going to be unable to support IPv4 for more 
> than a few years?

IPv4+NAT will coexist with IPv6 for many years.   A home router can easily
offer v4/NAT and v6 together.   This allows v6 apps to be used opportunisticly
between homes or other networks that would otherwise have NAT and need some
3rd party broker.
 
> It's brutal, but I can see the point. Thinking about a cut-off date for IPv4 
> would indeed provoke some interesting discussion, but I think a lot of 
> people still want to hang onto IPv4. Even so, how does July 31st 2005 sound 
> to everybody?

That's rather insane :)   More like July 31st 2025 before we remove IPv4,
and even then it'll hang around... remember no-one *has* to install IPv6,
it's just an option if you want the functionality.   Users want features not
protocols.

Tim



From owner-ietf@ietf.org  Tue Jan 13 05:41:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04950
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 05:41:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgLwj-000271-8O
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 05:38:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgLwE-00025h-PA
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 05:38:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04807
	for <ietf@ietf.org>; Tue, 13 Jan 2004 05:38:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgLwC-0004xy-00
	for ietf@ietf.org; Tue, 13 Jan 2004 05:38:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgLuK-0004tx-00
	for ietf@ietf.org; Tue, 13 Jan 2004 05:36:25 -0500
Received: from hannibal.servitor.co.uk ([195.188.15.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgLt1-0004qC-00
	for IETF@ietf.org; Tue, 13 Jan 2004 05:35:04 -0500
Received: from paul by hannibal.servitor.co.uk with local (Exim 4.14)
	id 1AgLt3-000DlQ-Gh; Tue, 13 Jan 2004 10:35:05 +0000
Date: Tue, 13 Jan 2004 10:35:05 +0000
From: Paul Robinson <paul@iconoplex.co.uk>
To: Tony Hain <alh-ietf@tndh.net>
Cc: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <20040113103505.GN27903@iconoplex.co.uk>
References: <4002FFCE.4020407@iconoplex.co.uk> <E1AgAYp-0006Au-00@ietf-mx> <20040113093607.GM27903@iconoplex.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040113093607.GM27903@iconoplex.co.uk>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, Jan 13, 2004 at 09:36:07AM +0000, Paul Robinson wrote:

> Are you suggesting then, that all RFCs based on IPv6 should be... stopped? 

That's what happens when you write e-mails and then don't check them before 
sending them...

s/IPv6/IPv4 - obviously. :-)

-- 
Paul Robinson



From owner-ietf@ietf.org  Tue Jan 13 05:43:57 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05031
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 05:43:57 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgLyf-0002NT-B4
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 05:40:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgLyM-0002IX-Je
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 05:40:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04912
	for <ietf@ietf.org>; Tue, 13 Jan 2004 05:40:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgLyK-00055T-00
	for ietf@ietf.org; Tue, 13 Jan 2004 05:40:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgLwQ-00050O-00
	for ietf@ietf.org; Tue, 13 Jan 2004 05:38:34 -0500
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgLva-0004vE-00
	for IETF@ietf.org; Tue, 13 Jan 2004 05:37:43 -0500
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 KAA01029
	for <IETF@ietf.org>; Tue, 13 Jan 2004 10:37:43 GMT
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id KAA06251
	for <IETF@ietf.org>; Tue, 13 Jan 2004 10:37:37 GMT
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i0DAbge16407
	for IETF@ietf.org; Tue, 13 Jan 2004 10:37:42 GMT
Date: Tue, 13 Jan 2004 10:37:42 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <20040113103742.GG14378@login.ecs.soton.ac.uk>
References: <E1Ag7Kx-0001Nu-00@ietf-mx> <4002FFCE.4020407@iconoplex.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4002FFCE.4020407@iconoplex.co.uk>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Jan 12, 2004 at 08:13:02PM +0000, Paul Robinson wrote:
> 
> IPv6 will not take off any time soon because neither the end-user nor the 
> service provider sees the need. The moment AOL, Wanadoo, Tiscali, World 
> Online et al shout out "we *need* IPv6" it will happen. Quickly.

IPv6 is taking off now because of specific high-profile demands like those
of the US DoD.  There have been many significant advances in the past 12
months in terms of stability of standards and hardening of implementations
(including h/w support from key vendors such as Juniper and Cisco).

Most users will use IPv6 without knowing it, which is part of the beauty but
also a little sad for those who have worked hard to make IPv6 happen.
 
> And out of curiosity, how many people here have migrated their entire 
> network to IPv6 already to set a good example and show how it's done? Yes, 
> thought so.

Many networks have, almost all via dual-stack.    Those who have done so have
found the extra cost minimal where the v6 capability is introduced as part of 
a normal procurement cycle.   The UK academic backbone JANET is one example
in your context.  Remember it's not about migrating in most circumstances,
it's about parallel capability to enable v6 to operate now as the first phase
of a (very long) transition.   But some networks are emerging ipv6-only, 
particularly in Asia.
 
Tim



From owner-ietf@ietf.org  Tue Jan 13 06:00:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05880
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 06:00:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgMCE-0003mU-5s
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 05:54:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgMBl-0003jZ-4u
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 05:54:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05722
	for <ietf@ietf.org>; Tue, 13 Jan 2004 05:54:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgMBi-00065R-00
	for ietf@ietf.org; Tue, 13 Jan 2004 05:54:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgMAK-0005vf-00
	for ietf@ietf.org; Tue, 13 Jan 2004 05:52:58 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgM5W-0005V6-00
	for IETF@ietf.org; Tue, 13 Jan 2004 05:47:58 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0DAlGZN098158;
	Tue, 13 Jan 2004 11:47:16 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20040113093607.GM27903@iconoplex.co.uk>
References: <4002FFCE.4020407@iconoplex.co.uk> <E1AgAYp-0006Au-00@ietf-mx> <20040113093607.GM27903@iconoplex.co.uk>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <E0A896BE-45B5-11D8-815B-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <IETF@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Death of the Internet - details at 11
Date: Tue, 13 Jan 2004 11:47:26 +0100
To: Paul Robinson <paul@iconoplex.co.uk>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 13-jan-04, at 10:36, Paul Robinson wrote:

>> Continuing work on IPv4 only creates the illusion that it is a viable 
>> protocol for application developers to rely on for future income.

> Are you suggesting then, that all RFCs based on IPv6 should be... 
> stopped?

I think that one should read IPv4...

> By the sounds of it, what you're looking for is for us as a community 
> to
> refuse to deal with IPv4 any more, that we wash our hands of it, and 
> make
> vendors realise that they are going to be unable to support IPv4 for 
> more
> than a few years?

Hm, didn't they try something along those general lines at Coca Cola a 
while ago?

> It's brutal, but I can see the point. Thinking about a cut-off date 
> for IPv4
> would indeed provoke some interesting discussion, but I think a lot of
> people still want to hang onto IPv4. Even so, how does July 31st 2005 
> sound
> to everybody?

Why don't we start by making *.ietf.org only reachable over IPv6 
starting 04-04-04?




From owner-ietf@ietf.org  Tue Jan 13 06:31:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07131
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 06:31:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgMhD-0005XW-94
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 06:26:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgMep-0005ST-Jd
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 06:24:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06850
	for <ietf@ietf.org>; Tue, 13 Jan 2004 06:24:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgMem-0007Sh-00
	for ietf@ietf.org; Tue, 13 Jan 2004 06:24:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgMcq-0007ON-00
	for ietf@ietf.org; Tue, 13 Jan 2004 06:22:24 -0500
Received: from hannibal.servitor.co.uk ([195.188.15.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgMc3-0007Kc-00
	for IETF@ietf.org; Tue, 13 Jan 2004 06:21:35 -0500
Received: from paul by hannibal.servitor.co.uk with local (Exim 4.14)
	id 1AgMc1-000Dsq-W5; Tue, 13 Jan 2004 11:21:33 +0000
Date: Tue, 13 Jan 2004 11:21:33 +0000
From: Paul Robinson <paul@iconoplex.co.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <20040113112133.GO27903@iconoplex.co.uk>
References: <4002FFCE.4020407@iconoplex.co.uk> <E1AgAYp-0006Au-00@ietf-mx> <20040113093607.GM27903@iconoplex.co.uk> <20040113103005.GE14378@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040113103005.GE14378@login.ecs.soton.ac.uk>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.4 required=5.0 tests=AWL,SERIOUS_CASH autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, Jan 13, 2004 at 10:30:05AM +0000, Tim Chown wrote:

> It is prevalent wherever there is broadband.  And that is where (with the
> extra bandwidth and always-on) connectivity into the network is desirable.

Not around me it isn't. In the UK, even with cable modem providers, I have 
non-NAT - as they are known in the European ISP industry "RIPE addresses" - 
and although I've installed NAT myself to enable quick and easy WiFi access 
using the one IP address, there is nothing stopping me taking that box out 
and having proper IPv4 direct to my NIC.

In addition, many, many broadband ISPs in the UK will not only provide IP 
addresses, but will happily route subnets providing you fill in the form 
explaing why you want the addresses, so they can give the justification to 
RIPE if they need to apply for more address space.

There are a few big players who do NAT - BT OpenWorld is the biggest I know 
- and yes, they are aiming for a consumer market that as yet does not see 
the advantage of non-NAT network access. There are two ways people will 
address the issue when the time comes:

1. Demand non-NAT network access
2. Use protocols that work around NAT restrictions
  
> IPv4+NAT will coexist with IPv6 for many years.   A home router can easily
> offer v4/NAT and v6 together.   This allows v6 apps to be used opportunisticly
> between homes or other networks that would otherwise have NAT and need some
> 3rd party broker.

I am not advocating a policy of insisting that IPv4+NAT gets withdrawn from
the Internet. What I am suggesting is that there is an official withdrawal
of support for continuing the development of IPv4 protocols - that we should
be saying to the world "Look, very nice, but we're about 3 years ahead of
you on the technology curve, and we're not providing life support for
something we know you won't want in 3 years time when we can be using 
that time dreaming up the support for the apps we know you will want"...
  
> That's rather insane :)   More like July 31st 2025 before we remove IPv4,
> and even then it'll hang around... remember no-one *has* to install IPv6,
> it's just an option if you want the functionality.   Users want features not
> protocols.

I'm not saying we remove IPv4. Just we push market demands by removing
continued RFC support for protocols replying on it. This is exactly the
technique the author of Speak Freely used to bring this issue to our
attention. It's what MS, Sun, Cisco, everybody does. If you're happy with
IPv4, fine, keep it, but we're not going to carry on pumping resources into
something that quite frankly, is not a suitable use of our time. This to me 
seems a reasonable approach.

I think if we say "From the middle of next year, no more IPv4 RFCs or drafts 
please", then vendors and application developers will have to sit up and 
take notice. Remember, the protocols take between 6-36 months to be deployed 
for real, so what we'd actually be saying is "we don't think IPv4 is worth 
deploying from scratch after the middle of 2007". We'd be saying to 
application developers "Look, IPv4 isn't where you're going to make serious 
cash with innovative applications in the future, come play with IPv6".

And of course, if after a couple of years it isn't working, there is nothing 
stopping the IETF rescinding, and supporting IPv4 once more due to "customer 
pressures". :-)

-- 
Paul Robinson



From owner-ietf@ietf.org  Tue Jan 13 07:09:53 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08388
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 07:09:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgNE6-00070Q-VL
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 07:00:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgNDM-0006yj-D5
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 07:00:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08215
	for <ietf@ietf.org>; Tue, 13 Jan 2004 07:00:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgNDE-0001G2-00
	for ietf@ietf.org; Tue, 13 Jan 2004 07:00:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgN7d-00018Y-00
	for ietf@ietf.org; Tue, 13 Jan 2004 06:54:13 -0500
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgN4G-0000zE-00
	for IETF@ietf.org; Tue, 13 Jan 2004 06:50:44 -0500
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 LAA03491
	for <IETF@ietf.org>; Tue, 13 Jan 2004 11:50:19 GMT
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id LAA14173
	for <IETF@ietf.org>; Tue, 13 Jan 2004 11:50:09 GMT
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i0DBoFh18038
	for IETF@ietf.org; Tue, 13 Jan 2004 11:50:15 GMT
Date: Tue, 13 Jan 2004 11:50:15 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <20040113115014.GL14378@login.ecs.soton.ac.uk>
References: <4002FFCE.4020407@iconoplex.co.uk> <E1AgAYp-0006Au-00@ietf-mx> <20040113093607.GM27903@iconoplex.co.uk> <20040113103005.GE14378@login.ecs.soton.ac.uk> <20040113112133.GO27903@iconoplex.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040113112133.GO27903@iconoplex.co.uk>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, Jan 13, 2004 at 11:21:33AM +0000, Paul Robinson wrote:
> 
> Not around me it isn't. In the UK, even with cable modem providers, I have 
> non-NAT - as they are known in the European ISP industry "RIPE addresses" - 
> and although I've installed NAT myself to enable quick and easy WiFi access 
> using the one IP address, there is nothing stopping me taking that box out 
> and having proper IPv4 direct to my NIC.

Which is one of the drivers.  Most ISPs still only give 1, often dynamic,
IPv4 address.   As soon as you have multiple home devices (I now have 11
different MAC addresses observed on my home router since last summer) you
hit the problem.
 
> In addition, many, many broadband ISPs in the UK will not only provide IP 
> addresses, but will happily route subnets providing you fill in the form 
> explaing why you want the addresses, so they can give the justification to 
> RIPE if they need to apply for more address space.

I don't think it's that many.  And as you say, the big ISPs like BT who will
only give 1 IP (and indeed who will flat out refuse to support you if you
replace your USB DSL modem with a "real" DSL router) are the ones that make
up the vast majority of UK broadband.

Yes some people can go to smaller ISPs and find those that give subnets (I
found one that gives a /29 for free), but these are the minority.  

One beauty of IPv6 is not having to go back to RIPE to ask for more addresses;
you get enough to start with to avoid the paperwork cycles; that's some saving
in its own right.

I think protocols should continue to be developed that are as far as possible
IP independent.  This will help transition; stopping work on IPv4 seems
inapprpriate given IPv4 will be here for 20+ years still.   But there are
specific IPv6-only properties that are very interesting, like CGA, or
resilience to port scanning, that should be taken advantage of asap.

Tim



From owner-ietf@ietf.org  Tue Jan 13 07:59:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09981
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 07:59:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgO3N-0001F5-3n
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 07:53:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgO2P-0001Bk-MV
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 07:52:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09843
	for <ietf@ietf.org>; Tue, 13 Jan 2004 07:52:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgO2F-0003uU-00
	for ietf@ietf.org; Tue, 13 Jan 2004 07:52:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgNxX-0003lm-00
	for ietf@ietf.org; Tue, 13 Jan 2004 07:47:52 -0500
Received: from [67.38.193.238] (helo=stewart.chicago.il.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgNu1-0003eG-00
	for IETF@ietf.org; Tue, 13 Jan 2004 07:44:13 -0500
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1])
	by stewart.chicago.il.us (8.12.8p1/8.12.8) with ESMTP id i0DChhO6039282;
	Tue, 13 Jan 2004 06:43:44 -0600 (CST)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <4003E7FF.8030403@stewart.chicago.il.us>
Date: Tue, 13 Jan 2004 06:43:43 -0600
From: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Robinson <paul@iconoplex.co.uk>
CC: Tim Chown <tjc@ecs.soton.ac.uk>, IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
References: <4002FFCE.4020407@iconoplex.co.uk> <E1AgAYp-0006Au-00@ietf-mx> <20040113093607.GM27903@iconoplex.co.uk> <20040113103005.GE14378@login.ecs.soton.ac.uk> <20040113112133.GO27903@iconoplex.co.uk>
In-Reply-To: <20040113112133.GO27903@iconoplex.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul Robinson wrote:

>
>I think if we say "From the middle of next year, no more IPv4 RFCs or drafts 
>please", then vendors and application developers will have to sit up and 
>take notice. Remember, the protocols take between 6-36 months to be deployed 
>for real, so what we'd actually be saying is "we don't think IPv4 is worth 
>deploying from scratch after the middle of 2007". We'd be saying to 
>application developers "Look, IPv4 isn't where you're going to make serious 
>cash with innovative applications in the future, come play with IPv6".
>  
>
Paul:

Something about this thread confuses me :-0  Now maybe it
is just me having my head down in the sand.. I work in the
transport area mainly and last I checked:

1) TCP/SCTP and UDP all run over IPv6, in fact SCTP
     (which I most work with :->) will setup an association
    with BOTH IPv4 and IPv6 addresses in the association,
    I don't even have to choose, I get them both as long as
    I open an AF_INET6 socket. :->

2)  I can't remember any transport area document in recent
     history (course I don't read them all) that is just IPv4... Most
     of the things popping around are the congestion control work
     for high speed and things for false fast retransmit... and other
     fun transport area stuff :-> No IPv4 specifis there ....

3) I cannot, in writting an RFC, make the user of the socket interface
    do "s = socket(AF_INET6, SOCK_STREAM, IPPROTO_SCTP);" At least
    I don't know how to specify that in a draft..

What I am saying is that a large part of the work in the IETF is rather
ambivilant to what the IP infrastructure is that is beneth it... is this 
not a
good thing?

Maybe y'all are refering to another area that I don't keep up on (which
is most since I can barely keep up in transport) :->

R

-- 
Randall R. Stewart
815-477-2127 (office)
815-342-5222 (cell phone)





From owner-ietf@ietf.org  Tue Jan 13 08:15:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10610
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 08:15:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgOHt-0002Dc-1H
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 08:08:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgOH7-0002BB-LM
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 08:08:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10157
	for <ietf@ietf.org>; Tue, 13 Jan 2004 08:07:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgOGq-0004X1-00
	for ietf@ietf.org; Tue, 13 Jan 2004 08:07:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgOBz-0004Dt-00
	for ietf@ietf.org; Tue, 13 Jan 2004 08:02:48 -0500
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgO5J-0003zA-00
	for ietf@ietf.org; Tue, 13 Jan 2004 07:55:53 -0500
Received: from guppylake.com (pcp05307270pcs.wanarb01.mi.comcast.net[68.42.70.186])
          by comcast.net (rwcrmhc11) with SMTP
          id <20040113125457013008h159e>; Tue, 13 Jan 2004 12:54:57 +0000
Date: Tue, 13 Jan 2004 07:56:46 -0500
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: ietf@ietf.org
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <200401130345.i0D3jnpS058424@calcite.rhyolite.com>
Message-Id: <F1AD801E-45C7-11D8-9AFA-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I'm sorry, I know I said I wasn't going to be lured into another 
exchange in this thread, but I can't help it...

On Monday, January 12, 2004, at 10:45  PM, Vernon Schryver wrote:

> Mr. Sauve could rent an IP address that is not on dial-up or dynamic
> blacklists and run his systems there.

In other words, because some ISP with whom he has NO relationship has 
deemed his own ISP spam-friendly, he should abandon his ISP, whether 
*he* thinks they are spam-friendly or not. The words that come to mind 
to describe this sort of arrangement are "cartel," "blackmail," and 
"extortion."  It is also a perfect example of an assertion I made 
before, which is that blacklists are being used by the large ISP's as a 
tool for consolidation in the ISP market.  When RoadRunner blocked my 
ISP, the *only* thing they were helpful about was offering to help me 
get "better" Internet service by changing ISPs.

>> Blacklists also, quite clearly, don't work to eliminate spam.
>
> No honest person who actually looks at spam agrees with that.

As I've made clear, *I* agree with that.  Given the exchanges that 
preceded this, it sounds like you are asserting that I -- and all the 
other people who have argued against you in good faith on this list -- 
are dishonest.  Is everyone who disagrees with your conclusions 
necessarily dishonest?  If so, why are you wasting time talking with 
us?  -- Nathaniel




From owner-ietf@ietf.org  Tue Jan 13 08:26:49 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11512
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 08:26:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgOUT-0003Do-Cn
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 08:21:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgOU9-0003AJ-IE
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 08:21:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11240
	for <ietf@ietf.org>; Tue, 13 Jan 2004 08:21:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgOU8-0005nW-00
	for ietf@ietf.org; Tue, 13 Jan 2004 08:21:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgOSj-0005bQ-00
	for ietf@ietf.org; Tue, 13 Jan 2004 08:20:06 -0500
Received: from hannibal.servitor.co.uk ([195.188.15.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgOQj-0005J2-00
	for IETF@ietf.org; Tue, 13 Jan 2004 08:18:01 -0500
Received: from paul by hannibal.servitor.co.uk with local (Exim 4.14)
	id 1AgOQe-000EHY-GY; Tue, 13 Jan 2004 13:17:56 +0000
Date: Tue, 13 Jan 2004 13:17:56 +0000
From: Paul Robinson <paul@iconoplex.co.uk>
To: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <20040113131756.GR27903@iconoplex.co.uk>
References: <4002FFCE.4020407@iconoplex.co.uk> <E1AgAYp-0006Au-00@ietf-mx> <20040113093607.GM27903@iconoplex.co.uk> <20040113103005.GE14378@login.ecs.soton.ac.uk> <20040113112133.GO27903@iconoplex.co.uk> <4003E7FF.8030403@stewart.chicago.il.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4003E7FF.8030403@stewart.chicago.il.us>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, Jan 13, 2004 at 06:43:43AM -0600, Randall R. Stewart (home) wrote:

> Something about this thread confuses me :-0  Now maybe it
> is just me having my head down in the sand.. I work in the
> transport area mainly and last I checked:
> 
> 1) TCP/SCTP and UDP all run over IPv6, in fact SCTP
>     (which I most work with :->) will setup an association
>    with BOTH IPv4 and IPv6 addresses in the association,
>    I don't even have to choose, I get them both as long as
>    I open an AF_INET6 socket. :->

Yes, I see what you're saying. I think the point was, we should be actively
dissuading any further work around IPv4 protocols (where they occur), NOT
actively encouraging IPv6. By saying IPv4 is "officially" dead, we might
push forward the replacement for it (IPv6) and the takeup with both vendors
and service providers, particularly when it comes to consumer end-points.

Several people have been citing their providers as offering dual-stack
services, and how IPv6 peering with Tiscali happens, etc. but they are
completely missing the point. What we're discussing is the need for IPv6 to
be pushed out to the edge of the network to broadband users as the DEFAULT,
and not an option for those hosting servers near the core of the network,
who get it when they ask for it, which is what we mostly have now.

I'm not advocating re-drafts where we stick IPv6 Requirements into 
everything in sight, however. :-)
 
-- 
Paul Robinson



From owner-ietf@ietf.org  Tue Jan 13 08:34:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11830
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 08:34:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgOcD-0003qP-2S
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 08:29:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgOag-0003ha-Ue
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 08:28:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11565
	for <ietf@ietf.org>; Tue, 13 Jan 2004 08:28:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgOag-00065Q-00
	for ietf@ietf.org; Tue, 13 Jan 2004 08:28:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgOYw-00062H-00
	for ietf@ietf.org; Tue, 13 Jan 2004 08:26:30 -0500
Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgOYF-0005yp-00
	for ietf@ietf.org; Tue, 13 Jan 2004 08:25:47 -0500
Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2657.72)
	id <CN07D3SW>; Tue, 13 Jan 2004 08:25:16 -0500
Message-ID: <9E3BA3946476AD4EB94672712B12A85F042082@ftmail.lab.flarion.com>
From: Soliman Hesham <H.Soliman@flarion.com>
To: "'Mark Smith'" <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>,
        ietf@ietf.org
Subject: RE: dire outlook on internet and NAT
Date: Tue, 13 Jan 2004 08:25:05 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk



 > Admittedly I can't remember where I read it, but I've come across
 > a suggestion that enterprise networks adopting IPv6 is likely to
 > happen before ISPs provide it in any big way, as enterprise
 > networks have more to gain from the technology (well, possibly,
 > assuming they can be convinced that "proper" address space is
 > better than NAT). 

=> I'm a bit confused as to why enterprises would be interested
in v6. There are even prorietry solutions that allow for VPN
access behind a NAT. And enterprises are not known for encouraging 
p2p apps for their employees. So this business case doesn't
seem like a winner to me. 

My hope has been that p2p apps will one day be "needed now" and 
force people to turn v6 on in their networks.

   Once enterprises have it, they will then ask
 > for it from their ISP. 

=> Sure, but it's not clear that they'd be early adopters. 
Autoconfig of addresses will not be enough, if they ever use it. 

Hesham


I'd agree that expecting the drive for it
 > to come from ISPs is probably incorrect.
 > 
 > Maybe the focus needs to be to work on IPv6 protocols that
 > enterprises need. Anybody want to work on NetBIOS over IPv6 ?
 > After all, File and Print would have to be the "killer"
 > application for enterprise networks - it's the application that
 >  got networks into most enterprises in the first place in
 > the last 10 years.
 > 
 > Regards,
 > Mark.
 > 



From owner-ietf@ietf.org  Tue Jan 13 08:56:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12570
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 08:56:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgOvY-0004ym-Sq
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 08:49:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgOvF-0004wy-6T
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 08:49:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12437
	for <ietf@ietf.org>; Tue, 13 Jan 2004 08:49:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgOv4-0007NG-00
	for ietf@ietf.org; Tue, 13 Jan 2004 08:49:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgOoP-0007Bw-00
	for ietf@ietf.org; Tue, 13 Jan 2004 08:42:30 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgOma-000746-00
	for ietf@ietf.org; Tue, 13 Jan 2004 08:40:36 -0500
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com for <ietf@ietf.org>;
          Tue, 13 Jan 2004 08:40:34 -0500
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: Your all complaining about NAT mostly
Date: Tue, 13 Jan 2004 08:40:34 -0500
Message-ID: <20040113134034384.AAA409@hq.lindsayelec.com@rflooker1>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I'm making a product from scratch shortly and think the tide has turned to
support IPv6 as much as possible. I haven't looked. Are Docsis Cable modems
2.0 IPv6 aware? How about MS operating systems?

If ISP's and cable ops didn't ration fixed IP's NAT wouldn't be so popular.
Its a way to evade an cost which is arguably illegitimate in the first
place. The operators caused this, and not it reduces there income. They did
it to make money; (and also were too busy to notice what they were doing).
Can be fixed in a number of ways.
-Dan K


>Almost all via dual-stack.    Those who have done so have
>found the extra cost minimal where the v6 capability is introduced as part of 
>a normal procurement cycle.   The UK academic backbone JANET is one example
>in your context.  Remember it's not about migrating in most circumstances,
>it's about parallel capability to enable v6 to operate now as the first phase
>of a (very long) transition.   But some networks are emerging ipv6-only, 
>particularly in Asia.
>Tim




From owner-ietf@ietf.org  Tue Jan 13 09:40:40 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14328
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 09:40:40 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgPYG-0006p8-QB
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 09:29:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgPWk-0006lL-5Y
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 09:28:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13899
	for <ietf@ietf.org>; Tue, 13 Jan 2004 09:28:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgPWj-0001fB-00
	for ietf@ietf.org; Tue, 13 Jan 2004 09:28:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgPUt-0001dH-00
	for ietf@ietf.org; Tue, 13 Jan 2004 09:26:23 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgPTM-0001al-00
	for ietf@ietf.org; Tue, 13 Jan 2004 09:24:48 -0500
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com; Tue, 13 Jan 2004 09:24:47 -0500
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: Re: Your all complaining about NAT mostly
Cc: ietf@ietf.org
Date: Tue, 13 Jan 2004 09:24:47 -0500
Message-ID: <20040113142447324.AAA403@hq.lindsayelec.com@rflooker1>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>Actually, I'm told by ISP people that they don't make money off their address
>charges, that they basically just cover their own costs.
>Noel

Bell Canada here charges $10 or so for a few fixed IP's per month. They are
bought for $0.60 US as a one time cost.

A pretty "good cover".

Regs,
Dan


Dan Kolis - Lindsay Electronics Ltd dank@hq.lindsayelec.com
50 Mary Street West, Lindsay Ontario Canada K9V 2S7
(705) 324-2196  X272             (705) 324-5474 Fax
An ISO 9001 Company; 
/Document end




From owner-ietf@ietf.org  Tue Jan 13 09:44:48 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14540
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 09:44:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgPiu-0007Ef-Pq
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 09:40:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgPiV-00078p-5B
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 09:40:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14312
	for <ietf@ietf.org>; Tue, 13 Jan 2004 09:40:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgPiU-000290-00
	for ietf@ietf.org; Tue, 13 Jan 2004 09:40:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgPgl-00025z-00
	for ietf@ietf.org; Tue, 13 Jan 2004 09:38:39 -0500
Received: from lakemtao04.cox.net ([68.1.17.241])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgPfr-000222-00
	for IETF@ietf.org; Tue, 13 Jan 2004 09:37:43 -0500
Received: from dowding.lcs.mit.edu ([68.10.113.154]) by lakemtao04.cox.net
          (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP
          id <20040113143712.JJWV19895.lakemtao04.cox.net@dowding.lcs.mit.edu>;
          Tue, 13 Jan 2004 09:37:12 -0500
Message-Id: <5.0.2.1.0.20040113093724.009e5450@mailhub.exis.net>
X-Sender: jnc@mailhub.exis.net (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 13 Jan 2004 09:39:55 -0500
To: IETF@ietf.org
From: "J. Noel Chiappa" <jnc@lcs.mit.edu>
Subject: Re: Death of the Internet - details at 11
Cc: jnc@lcs.mit.edu
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

     > From: Paul Robinson <paul@iconoplex.co.uk>

     > of course, if after a couple of years it isn't working, there is nothing
     > stopping the IETF rescinding, and supporting IPv4 once more due to
     > "customer pressures". :-)

Hello? That's where we are *now*.

May I remind you that IPv6 has been available December 1995, when the first
set of IPv6 specification RFC's came out, and now, almost 10 years later,
deployment is still minimal. The customers have "voted with their feet" for
IPv4.

(Yes, I know, "the support situation has improved and we expect wide-scale
deployment in the next year" - I think I've heard that same mantra every year
for the last N years. I really ought to go back through my email folders and
create a web page of IPv6 predictions. In fact, I think that's a good idea -
it will help make plain how hollow such claims are. My task for today! :-)

Anyway, the point is that successful networking technologies don't take 10
years to succeed. They either catch on, or they don't, and after 10 years
this one has not caught on.

The upgrade path (replace the entire internet layer in one fell swoop) IPv6
adopted clearly isn't working. Time to try something rather different.

	Noel




From owner-ietf@ietf.org  Tue Jan 13 10:30:57 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18747
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 10:30:57 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgQNZ-0007Wz-UW
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 10:22:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgQNU-0007Uh-Tg
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 10:22:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18342
	for <ietf@ietf.org>; Tue, 13 Jan 2004 10:22:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgQNT-0005ry-00
	for ietf@ietf.org; Tue, 13 Jan 2004 10:22:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgQLh-0005lY-00
	for ietf@ietf.org; Tue, 13 Jan 2004 10:20:58 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgQK8-0005eA-00
	for IETF@ietf.org; Tue, 13 Jan 2004 10:19:20 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0DFIxZN001876;
	Tue, 13 Jan 2004 16:19:01 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <5.0.2.1.0.20040113093724.009e5450@mailhub.exis.net>
References: <5.0.2.1.0.20040113093724.009e5450@mailhub.exis.net>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <D59FD8D8-45DB-11D8-815B-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Death of the Internet - details at 11
Date: Tue, 13 Jan 2004 16:19:09 +0100
To: "J. Noel Chiappa" <jnc@lcs.mit.edu>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 13-jan-04, at 15:39, J. Noel Chiappa wrote:

>     > of course, if after a couple of years it isn't working, there is
>     > nothing stopping the IETF rescinding, and supporting IPv4 once
>     >  more due to "customer pressures". :-)

> Hello? That's where we are *now*.

> May I remind you that IPv6 has been available December 1995, when the 
> first
> set of IPv6 specification RFC's came out,

That's ridiculous. Any IPv6 implementation from before around 2000 is 
really too immature to be usable (just look at those early specs), and 
there are still problem areas that must be solved before IPv6 can be 
considered a decent alternative to IPv4.

> and now, almost 10 years later, deployment is still minimal. The 
> customers have "voted with their feet" for IPv4.

Not yet.

> (Yes, I know, "the support situation has improved and we expect 
> wide-scale
> deployment in the next year" - I think I've heard that same mantra 
> every year for the last N years. I really ought to go back through my 
> email folders and create a web page of IPv6 predictions. In fact, I 
> think that's a good idea - it will help make plain how hollow such 
> claims are. My task for today! :-)

But you are doing the exact same thing by claiming premature defeat. If 
IPv6 were really as dead as you say, how is it possible that so many 
vendors have been implementing so many new IPv6 features the past year 
alone?

> Anyway, the point is that successful networking technologies don't 
> take 10
> years to succeed. They either catch on, or they don't, and after 10 
> years
> this one has not caught on.

It would be interesting to compare the first 5 years of ARPANET with 
the first 5 years of IPv6 availability. I wouldn't be surprised if 
there are more systems running IPv6 today than systems connected to the 
ARPANET in 1974.

> The upgrade path (replace the entire internet layer in one fell swoop) 
> IPv6
> adopted clearly isn't working. Time to try something rather different.

If this is what you really want I think you should make your case based 
on technical merit of the new approach over IPv6 rather than a 
perceived marketing failure.




From owner-ietf@ietf.org  Tue Jan 13 10:31:02 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18768
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 10:31:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgQNZ-0007Wt-K6
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 10:22:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgQNO-0007Uf-82
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 10:22:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18323
	for <ietf@ietf.org>; Tue, 13 Jan 2004 10:22:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgQNN-0005rW-00
	for ietf@ietf.org; Tue, 13 Jan 2004 10:22:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgQLd-0005ku-00
	for ietf@ietf.org; Tue, 13 Jan 2004 10:20:54 -0500
Received: from [63.247.76.241] (helo=montage.altserver.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgQJi-0005ds-00
	for IETF@ietf.org; Tue, 13 Jan 2004 10:18:54 -0500
Received: from f01m-38-11.d0.club-internet.fr ([212.195.229.11] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1AgQJY-0001If-4d
	for IETF@ietf.org; Tue, 13 Jan 2004 07:18:44 -0800
Message-Id: <6.0.1.1.2.20040113144214.03ab0390@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 13 Jan 2004 15:41:27 +0100
To: IETF@ietf.org
From: jfcm <info@utel.net>
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <F9421262-4592-11D8-AB12-00039312C852@isc.org>
References: <E1Ag7Kx-0001Nu-00@ietf-mx>
 <4002FFCE.4020407@iconoplex.co.uk>
 <F9421262-4592-11D8-AB12-00039312C852@isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 07:37 13/01/04, Joe Abley wrote:
>The operational cost of supporting both v4 and v6 from the network 
>perspective not great, based on our experience (although the support load 
>for v6 clients to content hosted in our network is currently much lower 
>than for v4 clients, as you'd expect).
>
>I'd be very happy to share more details about what we're running with 
>people who have interest.

Gentlemen,
let agree IETF is lacking formal interfaces with the real world of users 
and the real world of operators.  John Klensin's official participation to 
the ICANN BoD is a first good step towards formal links with operators. 
However, the lack of relation of ICANN with users (@large) and the US 
oriented nature of ICANN (the problem is not the USA but a single country), 
leads world towards ITU. I support the principle of this move as a 
multilateralism American structures have some difficulties with, but not a 
move towards ITU-T.  We need an ITU-I where IETF may very well fit through 
a good and fruitful MoU or more.

Each "sector" (ICANN/NICs, @large, IETF/IAB, ITU/GAC) in this chain suffers 
from its imperfections and its lack of cooperation. For too long each said 
"the fault is with the other". IMHO the fault is with every of us and we 
all are to cooperate. When ICANN started the ERC process, I made sure in 
calling on everyone (Vin may recall that he contributed) that there was a 
consensus about the need to reform  ICANN (read Governance) and that the 
solution had to be consensual to succeed. The solution is not consensual 
and we saw Geneva WSIS positions as a result. We now have 2 years to 
correct that, before UN says "I take over".

White House identified the weaknesses of the system too. One of their 
answers is IPv6. http://whitehouse.gov/pcipb asks all the US 
administrations to move to IPv6. And DoD is obeying the Chief. In France, 
the Research Ministry switched to IPv6 and the research network for France 
(Renater) is the IPv6 leader (the same for Europe (Geant) as far as I 
understand). We all know what Asia is doing for IPv6. So, IPv6 could be a 
uniting factor to reorganize the Governance, the "Technicance" and the 
Brainware (the ways users use the system) in a concerted way, instead of 
bickering each other.

As a user/brainware person for a long, I see several issues where I need 
the Technicance and the Governance to help. Not to commit anyone I will say 
a popous "I", but it is actually several "we"s I currently see(share in) 
structuring


1. I am not technical enough on this to comment about IPv6 as an 
architecture and as a system. But I do not trust a system the architecture 
of which is to be dig into hundredth of RFCs and confused closed discussion 
lists. I need first an Internet architecture document (equivalent to what 
the W3C published) to understand what is the Internet network system 
application and how it relates with other network system applications such 
as telephone, television, OSI, etc. so I am sure everyone understands what 
we want to do together.


2. I am not a government but I have a IQ high enough to understand that 
Govs will not buy IPv6 the way it is proposed today for two main reasons.

- IPv6.001 (001 numbering plan) is unique and IPv6 is to support up to 6 
numbering plans. If IPv6 is to be deployed (real life tested) with only one 
numbering plan, we will face a Y2K potential threat since no one will be 
able to warranty the world a new numbering plan will be compatible with the 
then existing equipment base or even if IPv6 can support it. Nor that it 
will not endanger existing world operations. We have that exact example 
with the DNS. To introduce a new TLD is considered as a potential technical 
threat (while it should be able to support millions of it).

- IPv6.001 is flat. Both in routing and in addressing (and confuses both - 
some wanting to add identification/authetification). As such it offers no 
control nor surety to countries. Also, it creates many identification, 
bandwidth, recovery and economical problems.

I need a second numbering plan (IPv6.010)  to be accepted in the RFCs and 
discussed. And I do propose this plan to be defined and maintained by ITU. 
For several reasons. (1) to enforce the ITU-I concept and protect us from 
the Telcos [to aggregate the Telephone and X.121 numbering plan the ITU-I 
will have to talk with ITU-T] (2) to get the support of the Govs and show 
them what is possible and what is not in term of international Technicance. 
(3) to get a good PR for IPv6. The TF IPv6 submitted a document to the 
French Research Minister to promote IPv6: I tried to make them understand 
that technical arguments were low interest, what was of interest was to 
propose tax cuts for corporations switching to IPv6 to compensate for the 
equipment upgrade/change. If Govs are involved, they will understand better 
why to advertise IPv6 and to support to the change.

Also, I miss words like dynamic routing, anonymous network presence, 
domotic/teleurbanism support, service/addressing  continuity support, 
mobile identification, intelligent ubiquity support and I know the societal 
demand is for them. If they are not addressed, I able also able to 
understand there will be no funding for R&D programs by Europe or others. I 
am therefore not excited as this will not take off quick and I suppose that 
in the meanwhile someone may comes with an NGN universal addressing plan 
(COULD have been IPv6.010).


3. as user I find IPv6 totally unfriendly. The main reason why IPv4 will 
stay around IMHO is that I can manually use any ASCII editor and manage a 
DNS db file. The semantic of an IPv6 address is user unfriendly and its 
support obscure to me as a user. I want a 0-Z numbering plan first, to be 
able to quote an IPv6 address on the phone and an explanation manual in 
three pages that everyone will understand. If it is needed it must be 
simply understood and accepted.

Please give me a one page explaining why Music Lovers can universally take 
advantage from an IPv6 oriented TLD in a way where stakeholders may share 
in the control (through the naming used?) and I will tell you how we can 
quick make IPv6 ... universal.

We are in a real life world. Lobbying is of use towards Govs. and we (all 
of us together) need some. Only adhesion, interest, personal advantage can 
influence the users brainware. An IPv6 mandatory Napster is what we need.

Short of that IPv6 may never take off (what for? tell your kid why they 
need IPv6 and copy us. Here is what people may wantto listen to).
jfc















From owner-ietf@ietf.org  Tue Jan 13 10:32:30 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18961
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 10:32:30 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgQTM-0007k7-NW
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 10:28:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgQSy-0007i9-32
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 10:28:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18556
	for <ietf@ietf.org>; Tue, 13 Jan 2004 10:28:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgQSx-0006AS-00
	for ietf@ietf.org; Tue, 13 Jan 2004 10:28:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgQRJ-00065o-00
	for ietf@ietf.org; Tue, 13 Jan 2004 10:26:46 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgQPj-00060l-00
	for ietf@ietf.org; Tue, 13 Jan 2004 10:25:07 -0500
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com; Tue, 13 Jan 2004 10:25:04 -0500
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: "J. Noel Chiappa" <jnc@lcs.mit.edu>
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: 10 Years
Cc: ietf@ietf.org
Date: Tue, 13 Jan 2004 10:25:04 -0500
Message-ID: <20040113152504508.AAA399@hq.lindsayelec.com@rflooker1>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>Anyway, the point is that successful networking technologies don't take 10
>years to succeed. They either catch on, or they don't, and after 10 years
>this one has not caught on.

Ho boy. Good point there. Its like "boy oh boy! POP3 is dead use IMAP".
blablabla

IPv6 oddly though is sort of a hmmm behind the scenes thing a little.
slightly different. 

But I think your right if 10 years of waiting doesn't get an internet
innovation adopted much its at least sick and maybe dead.

regs
Dan

Dan Kolis - Lindsay Electronics Ltd dank@hq.lindsayelec.com
50 Mary Street West, Lindsay Ontario Canada K9V 2S7
(705) 324-2196  X272             (705) 324-5474 Fax
An ISO 9001 Company; 
/Document end




From owner-ietf@ietf.org  Tue Jan 13 10:50:52 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20106
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 10:50:52 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgQe2-0000tJ-9D
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 10:39:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgQc3-0000gs-Gf
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 10:37:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19484
	for <ietf@ietf.org>; Tue, 13 Jan 2004 10:37:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgQc2-00071d-00
	for ietf@ietf.org; Tue, 13 Jan 2004 10:37:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgQaJ-0006oG-00
	for ietf@ietf.org; Tue, 13 Jan 2004 10:36:03 -0500
Received: from hellmouth5.gatech.edu ([130.207.165.165] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgQYS-0006Xz-00
	for IETF@ietf.org; Tue, 13 Jan 2004 10:34:08 -0500
Received: from hellmouth5.gatech.edu (localhost [127.0.0.1])
	by hellmouth5.gatech.edu (Postfix) with SMTP
	id 5AE051D1A70; Tue, 13 Jan 2004 10:34:01 -0500 (EST)
	(envelope-from gt0165c@mail.gatech.edu)
Received: from mailprx5.gatech.edu (mailprx5.prism.gatech.edu [130.207.171.19])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(Client CN "smtp.mail.gatech.edu", Issuer "RSA Data Security? Inc." (verified OK))
	by hellmouth5.gatech.edu (Postfix) with ESMTP
	id 3D9C81D1A46; Tue, 13 Jan 2004 10:34:01 -0500 (EST)
	(envelope-from gt0165c@mail.gatech.edu)
Received: from atmnt1.gatech.edu (atmnt1.eecom.gatech.edu [130.207.231.125])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	(sasl: method=LOGIN, username=gt0165c, sender=n/a)
	by mailprx5.gatech.edu (Postfix) with ESMTP
	id F1F5D3A60F; Tue, 13 Jan 2004 10:33:59 -0500 (EST)
	(envelope-from gt0165c@mail.gatech.edu)
Message-Id: <5.2.1.1.2.20040113103028.00baacf8@pop.mail.gatech.edu>
X-Sender: gt0165c@pop.mail.gatech.edu
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Tue, 13 Jan 2004 10:34:16 -0500
To: IETF@ietf.org
From: Hayriye Altunbasak <gt0165c@mail.gatech.edu>
Subject: Re: Death of the Internet - details at 11
Cc: jnc@lcs.mit.edu
In-Reply-To: <5.0.2.1.0.20040113093724.009e5450@mailhub.exis.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Just a small comment:
Should not you first investigate the reason why IPv6 is not successful in 
terms of  deployment (yet)? So that, we won't make the same mistakes if the 
world decides to sth else....


At 09:39 AM 1/13/2004 -0500, J. Noel Chiappa wrote:
>     > From: Paul Robinson <paul@iconoplex.co.uk>
>
>     > of course, if after a couple of years it isn't working, there is 
> nothing
>     > stopping the IETF rescinding, and supporting IPv4 once more due to
>     > "customer pressures". :-)
>
>Hello? That's where we are *now*.
>
>May I remind you that IPv6 has been available December 1995, when the first
>set of IPv6 specification RFC's came out, and now, almost 10 years later,
>deployment is still minimal. The customers have "voted with their feet" for
>IPv4.
>
>(Yes, I know, "the support situation has improved and we expect wide-scale
>deployment in the next year" - I think I've heard that same mantra every year
>for the last N years. I really ought to go back through my email folders and
>create a web page of IPv6 predictions. In fact, I think that's a good idea -
>it will help make plain how hollow such claims are. My task for today! :-)
>
>Anyway, the point is that successful networking technologies don't take 10
>years to succeed. They either catch on, or they don't, and after 10 years
>this one has not caught on.
>
>The upgrade path (replace the entire internet layer in one fell swoop) IPv6
>adopted clearly isn't working. Time to try something rather different.
>
>         Noel
>





From owner-ietf@ietf.org  Tue Jan 13 10:52:28 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20262
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 10:52:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgQiq-00017t-Rj
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 10:44:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgQiO-00015k-Va
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 10:44:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19920
	for <ietf@ietf.org>; Tue, 13 Jan 2004 10:44:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgQiN-0007H4-00
	for ietf@ietf.org; Tue, 13 Jan 2004 10:44:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgQgX-0007Ep-00
	for ietf@ietf.org; Tue, 13 Jan 2004 10:42:30 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgQgA-0007C3-00
	for ietf@ietf.org; Tue, 13 Jan 2004 10:42:06 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i0DFg168023155
	for ietf@ietf.org env-from <vjs>;
	Tue, 13 Jan 2004 08:42:01 -0700 (MST)
Date: Tue, 13 Jan 2004 08:42:01 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401131542.i0DFg168023155@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <F1AD801E-45C7-11D8-9AFA-000A9571873E@guppylake.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Nathaniel Borenstein <nsb@guppylake.com>

> ...
> > Mr. Sauve could rent an IP address that is not on dial-up or dynamic
> > blacklists and run his systems there.
>
> In other words, because some ISP with whom he has NO relationship has 
> deemed his own ISP spam-friendly, he should abandon his ISP, whether 
> *he* thinks they are spam-friendly or not. The words that come to mind 
> to describe this sort of arrangement are "cartel," "blackmail," and 
> "extortion."  It is also a perfect example of an assertion I made 
> before, which is that blacklists are being used by the large ISP's as a 
> tool for consolidation in the ISP market.  When RoadRunner blocked my 
> ISP, the *only* thing they were helpful about was offering to help me 
> get "better" Internet service by changing ISPs.

Exactly the same charges can be made about taxis, pizza delivery
services, and so forth that refuse to deliver to "bad" parts of the
real world.  Perhaps in some cases you are right, but in the vast
majority you are wrong.  Is a simple, undeniable fact that the sources
of spam are concentrated in a small fraction of the IPv4 address space.
For example, the last numbers I saw about SPEWS had it listing a tiny
fraction of 1% of the IPv4 address space.

There are other problems with your theory.  The biggest is the link
between the big ISPs and the blacklisters.  Besides the undeniable
spammers (e.g. the ROKSO members), it is the big ISPs that are most
likely to be blacklisted, particularly in "dialup" or "dynamic"
blacklists.  According to your theory, Charter Communications is part
of a conspiracy of big outfits to drive away their own customers by
blacklisting their own IP addresses.  How sane and honest is that?

If you are saying that blacklists and boycotts are dangerous weapons,
then you're certainly right.  That's why contrary to my naive reading
of the U.S. Constitution, there are federal laws that limit or outlaw
boycotts in some circumstances that I don't understand.  
See http://www.google.com/search?q=%22secondary+boycott%22

Exactly what do you want? 
  - a U.S. Federal law against IP address blacklists?
  - a test for social responsibility and good sense given prospective
      IP address blacklist opererators administrated by the IESG?
  - a U.N. regulation prohibiting stupidity and foolishness by users
      and ISPs while choosing blacklists?

Pardon me, but it seems you want the IETF to declare that all blacklisting
and spam rejecting by IP address wrong and nasty.  As far as I can
tell, you would require me to accept mail from 69.6.0.0/18 because you
fear I might refuse mail from you.  Or perhaps you would allow me to
reject Wholesalebandwidth spam provided I not tell anyone.


> >> Blacklists also, quite clearly, don't work to eliminate spam.
> >
> > No honest person who actually looks at spam agrees with that.
>
> As I've made clear, *I* agree with that.  Given the exchanges that 
> preceded this, it sounds like you are asserting that I -- and all the 
> other people who have argued against you in good faith on this list -- 
> are dishonest.  Is everyone who disagrees with your conclusions 
> necessarily dishonest?  If so, why are you wasting time talking with 
> us?

You might be ignorant instead of dishonest.  If you have not looked
any blacklists except those that have affected your mail, then you
have not, in my words, really looked at spam.

Are you calling me and those who point out that some blacklists 
detect 70-90% of spam with false positive rates below 1% liers?
It your words could be read that way.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Tue Jan 13 11:24:18 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21869
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 11:24:18 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRFs-0004DQ-QZ
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:19:00 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af7fi-0002mM-8s
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 20:12:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03474
	for <ietf@ietf.org>; Fri, 9 Jan 2004 20:12:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af7fc-0002I7-00
	for ietf@ietf.org; Fri, 09 Jan 2004 20:12:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af7eS-0002Cc-00
	for ietf@ietf.org; Fri, 09 Jan 2004 20:10:56 -0500
Received: from [206.196.68.254] (helo=confucius.gnacademy.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af7dI-00021P-00
	for ietf@ietf.org; Fri, 09 Jan 2004 20:09:44 -0500
Received: from confucius.gnacademy.org (confucius.gnacademy.org [206.196.68.254])
	by confucius.gnacademy.org (Postfix) with ESMTP id 4468C228083;
	Fri,  9 Jan 2004 19:09:35 -0600 (CST)
Date: Fri, 9 Jan 2004 19:09:35 -0600 (CST)
From: Wawa Ngenge <ngenge@confucius.gnacademy.org>
To: John C Klensin <john-ietf@jck.com>
Cc: ietf@ietf.org, isdf@isoc.org
Subject: Re: [isdf] Re: www.internetforce.org
In-Reply-To: <240387438.1073576717@scan.jck.com>
Message-ID: <Pine.LNX.4.58.0401091907020.29579@confucius.gnacademy.org>
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
 <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nos ense.org>
 <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
 <240387438.1073576717@scan.jck.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


Thank you. This does answer the question, and is a good example of how to 
approach questions in a societal forum like ISDF where even rhetorical 
questions may hide a cry for information.  Once again, thank you.
w

 On Thu, 8 Jan 2004, John C 
Klensin wrote: > --On Thursday, 08 January, 2004 12:50 -0600 Wawa Ngenge 
> <ngenge@confucius.gnacademy.org> wrote:
> > On Mon, 5 Jan 2004, Mark Smith wrote:
> >> On Sat, 03 Jan 2004 07:53:04 -0500
> >> Because that is not how they are updated.
> >> The RFC faq would a place to seek your ansers.
> > The original question is : "Why do they not operate that way",
> > if they are  indeed REQUESTS?
> Hi.
> A better answer would have been "the term 'request for comment' 
> is historical, dating from a time when the preferred way to make 
> a formal comment on a document involved writing another 
> document, which then was numbered into the series".  That 
> mechanism is still available, although usually very slow.  But 
> documents that become RFCs are now first posted as Internet 
> Drafts (see http://www.ietf.org/ID); comments on those are both 
> solicited and, usually, handled very quickly.
> 
> Today, the RFC Series, despite retention of the original name 
> and numbering series, acts as a permanent, archival, repository 
> of information, decisions taken, and standards published.  As 
> such, documents in the series are subjected to review and 
> editing processes (which differ somewhat depending on the type 
> of document and are appropriate for conventional references from 
> conventional documents.  Running conversations, logs of 
> comments, etc., are not well suited for that archival and 
> reference role, regardless of their other advantages and 
> disadvantages.
> 
> regards,





From owner-ietf@ietf.org  Tue Jan 13 11:24:18 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21874
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 11:24:18 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRDp-00048L-7O
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:16:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgRDC-000460-7w
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 11:16:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21530
	for <ietf@ietf.org>; Tue, 13 Jan 2004 11:16:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgRDB-00013D-00
	for ietf@ietf.org; Tue, 13 Jan 2004 11:16:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgRBE-0000xt-00
	for ietf@ietf.org; Tue, 13 Jan 2004 11:14:13 -0500
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgR9K-0000rN-00
	for ietf@ietf.org; Tue, 13 Jan 2004 11:12:14 -0500
Received: from guppylake.com (pcp05307270pcs.wanarb01.mi.comcast.net[68.42.70.186])
          by comcast.net (rwcrmhc13) with SMTP
          id <2004011316113701500c5vi4e>; Tue, 13 Jan 2004 16:11:38 +0000
Date: Tue, 13 Jan 2004 11:13:26 -0500
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Content-Type: multipart/alternative; boundary=Apple-Mail-23--933557645
Mime-Version: 1.0 (Apple Message framework v553)
Cc: ietf@ietf.org
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <200401131542.i0DFg168023155@calcite.rhyolite.com>
Message-Id: <6B21B4FC-45E3-11D8-9AFA-000A9571873E@guppylake.com>
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


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

On Tuesday, January 13, 2004, at 10:42  AM, Vernon Schryver wrote:

> You might be ignorant instead of dishonest.

How very kind of you to consider two possibilities, thank  you.

> Are you calling me and those who point out that some blacklists
> detect 70-90% of spam with false positive rates below 1% liers?

Calling someone a liar is simply not my style, nor did I use any words 
that were remotely close to doing so.  If I could see anything in my 
words that could possibly be construed that way I would apologize for 
it.  (And, by the way, I consider *any* false positives unacceptable if 
there's no suitable mechanism for detecting and correcting them.)

This discussion is going nowhere, so I'm going back to more serious 
work on comprehensive spam control.  -- Nathaniel

--Apple-Mail-23--933557645
Content-Type: text/enriched;
	charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Tuesday, January 13, 2004, at 10:42  AM, Vernon Schryver wrote:


<excerpt>You might be ignorant instead of dishonest.

</excerpt>

How very kind of you to consider two possibilities, thank  you.


<excerpt><fixed>Are you calling me and those who point out that some
blacklists 

detect 70-90% of spam with false positive rates below 1% liers?

</fixed></excerpt>

Calling someone a liar is simply not my style, nor did I use any words
that were remotely close to doing so.  If I could see anything in my
words that could possibly be construed that way I would apologize for
it.  (And, by the way, I consider *any* false positives unacceptable
if there's no suitable mechanism for detecting and correcting them.)


This discussion is going nowhere, so I'm going back to more serious
work on comprehensive spam control.  -- Nathaniel


--Apple-Mail-23--933557645--




From owner-ietf@ietf.org  Tue Jan 13 11:30:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22215
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 11:30:29 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRNU-0004wF-PM
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:26:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgRN7-0004sT-Gp
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 11:26:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22000
	for <ietf@ietf.org>; Tue, 13 Jan 2004 11:26:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgRN6-0001YF-00
	for ietf@ietf.org; Tue, 13 Jan 2004 11:26:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgRLJ-0001Tw-00
	for ietf@ietf.org; Tue, 13 Jan 2004 11:24:37 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgRKC-0001Pv-00
	for IETF@ietf.org; Tue, 13 Jan 2004 11:23:28 -0500
Subject: RE: Death of the Internet - details at 11
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 13 Jan 2004 08:23:10 -0800
Content-class: urn:content-classes:message
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C840@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Death of the Internet - details at 11
thread-index: AcPZ4/LR8d+VaE8JRq6rOyxoa4+LTAADSWYA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "J. Noel Chiappa" <jnc@lcs.mit.edu>, <IETF@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> J. Noel Chiappa wrote:
> Anyway, the point is that successful networking
> technologies don't take 10 years to succeed. They
> either catch on, or they don't, and after 10
> years this one has not caught on.

And as of the DoD requirements, those of us that are old enough will
remember the ADA language.....

> The upgrade path (replace the entire internet layer
> in one fell swoop) IPv6 adopted clearly isn't
> working. Time to try something rather different.

Ack

Michel.




From owner-ietf@ietf.org  Tue Jan 13 11:42:51 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23248
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 11:42:51 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRY8-0006Hu-Ef
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:37:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af9dN-0002oY-BF
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 22:17:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06531
	for <ietf@ietf.org>; Fri, 9 Jan 2004 22:17:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af9dL-0007X8-00
	for ietf@ietf.org; Fri, 09 Jan 2004 22:17:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af9bV-0007UA-00
	for ietf@ietf.org; Fri, 09 Jan 2004 22:16:02 -0500
Received: from nr2baymi.bay.mi.charter.com ([24.247.24.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af9Zy-0007QY-00
	for ietf@ietf.org; Fri, 09 Jan 2004 22:14:27 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by nr2baymi.bay.mi.charter.com (8.11.7p1+Sun/8.11.6) with SMTP id i0A3ELv23683
	for <ietf@ietf.org>; Fri, 9 Jan 2004 22:14:22 -0500 (EST)
Received: (qmail 26285 invoked by uid 0); 10 Jan 2004 03:14:19 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.079135 secs); 10 Jan 2004 03:14:19 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 10 Jan 2004 03:14:18 -0000
Message-Id: <6.0.0.22.0.20040109220724.0432fcc0@mjs.alientech.net>
X-Mailer: Eudora
Date: Fri, 09 Jan 2004 22:09:22 -0500
To: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
From: mikes@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
In-Reply-To: <200401092341.i09NfAvg056863@calcite.rhyolite.com>
References: <20040109162546.6a47bf1e.moore@cs.utk.edu>
 <200401092341.i09NfAvg056863@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 06:41 PM 1/9/2004, Vernon Schryver wrote...

>Could you point to significant amounts of real mail, as opposed to
>theoretical examples, that might reasonably have consider legitimate
>by its targets but that was rejected as the result of a MAPS RBL
>listing?  Note that the validity of mail is determined not its senders
>but by its targets.

Yes. For a lengthy period, all mail.com SMTP servers were included in the RBL, blocking significant numbers of legitimate, private, non-spam emails from reaching willing recipients. 






From owner-ietf@ietf.org  Tue Jan 13 11:42:52 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23254
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 11:42:52 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRXA-0006E7-G5
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:36:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Af80h-0004Wm-Fq
	for ietf@asgard.ietf.org; Fri, 09 Jan 2004 20:33:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04334
	for <ietf@ietf.org>; Fri, 9 Jan 2004 20:33:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af80f-0003QB-00
	for ietf@ietf.org; Fri, 09 Jan 2004 20:33:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af7yo-0003Md-00
	for ietf@ietf.org; Fri, 09 Jan 2004 20:31:59 -0500
Received: from [206.196.68.254] (helo=confucius.gnacademy.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af7xS-0003JD-00
	for ietf@ietf.org; Fri, 09 Jan 2004 20:30:34 -0500
Received: from confucius.gnacademy.org (confucius.gnacademy.org [206.196.68.254])
	by confucius.gnacademy.org (Postfix) with ESMTP id 40F05228083;
	Fri,  9 Jan 2004 19:30:35 -0600 (CST)
Date: Fri, 9 Jan 2004 19:30:35 -0600 (CST)
From: Wawa Ngenge <ngenge@confucius.gnacademy.org>
To: jfcm <info@utel.net>
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org, isdf@isoc.org
Subject: Re: [isdf] Re: www.internetforce.org
In-Reply-To: <6.0.1.1.2.20040108232213.03f8beb0@mail.utel.net>
Message-ID: <Pine.LNX.4.58.0401091922130.29579@confucius.gnacademy.org>
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
 <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nos ense.org>
 <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
 <240387438.1073576717@scan.jck.com> <6.0.1.1.2.20040108232213.03f8beb0@mail.utel.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I suspect that any approach that was chosen was the result of negotiations 
and discussions among those who took part in the discussion at that time.  
Any solution would raise questions in a societal setting, since unanimity 
is not the norm in a democratic process.  The RFC process has extended so 
deep and so far that change may be difficult, though not impossible.
wawa

On Thu, 8 Jan 2004, jfcm wrote:
> Could it not be useful to have a "List of Comments" (LOC) for each RFC? 
> Where experience about the RFC reading, testing and implementation could be 
> listed by the authors (or a successor) from experience and questions 
> received. It would avoid the same questions to be debated again and again 
> and it would help further thinking. These comments could start with a 
> summary of the WG debated issues, explaining the whys of some options. I 
> suppose the implementation would be easy enough since it would follow the 
> same numbering scheme and titles. Such a LOC being an updated appendix 
> could be reviewed and help preparing replacements.
> jfc
> 

-- 
Wawa Ngenge (Ph.D.)
Internet Society Trustee Emeritus
WorldComputerExchange.org  Director
www.worldcomputerexchange.org/board_staff/ngenge-resume.htm
ngenge@confucius.gnacademy.org





From owner-ietf@ietf.org  Tue Jan 13 11:51:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23990
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 11:51:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRfs-0007Hs-Ln
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:45:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag92Y-00084Y-Cw
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 15:52:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18534
	for <ietf@ietf.org>; Mon, 12 Jan 2004 15:51:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag92V-0007Da-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:51:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag90k-0007Bt-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:50:11 -0500
Received: from mercury.lcs.mit.edu ([18.26.0.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag90D-00078G-00
	for IETF@ietf.org; Mon, 12 Jan 2004 15:49:37 -0500
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id DB760872F5; Mon, 12 Jan 2004 15:49:07 -0500 (EST)
To: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Cc: jnc@mercury.lcs.mit.edu
Message-Id: <20040112204907.DB760872F5@mercury.lcs.mit.edu>
Date: Mon, 12 Jan 2004 15:49:07 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

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

I agree completely.

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

	Noel





From owner-ietf@ietf.org  Tue Jan 13 11:51:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24004
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 11:51:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRfs-0007Hm-HO
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:45:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ag8Eh-0004XS-4M
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 15:00:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13989
	for <ietf@ietf.org>; Mon, 12 Jan 2004 15:00:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8Ef-00048s-00
	for ietf@ietf.org; Mon, 12 Jan 2004 15:00:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag8CX-0003vX-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:58:18 -0500
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag8Am-0003m1-00
	for ietf@ietf.org; Mon, 12 Jan 2004 14:56:28 -0500
Received: from guppylake.com (pcp05307270pcs.wanarb01.mi.comcast.net[68.42.70.186])
          by comcast.net (rwcrmhc13) with SMTP
          id <2004011219555701500b3np0e>; Mon, 12 Jan 2004 19:55:58 +0000
Date: Mon, 12 Jan 2004 14:57:45 -0500
Subject: Re: dire outlook on internet and NAT
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: "Fred Baker" <fred@cisco.com>, <ietf@ietf.org>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C836@server2003.arneill-py.sacramento.ca.us>
Message-Id: <971D0CB4-4539-11D8-9AFA-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pardon me if I'm missing something obvious here, but couldn't one just 
use either XMPP or Simple for presence, associate your "server name" 
with a Jabber/Simple ID, and automatically have your "server" findable 
via these general presence protocols?  Why isn't that a reasonable 
approach to peer to peer in a NAT world?  I would contend that it's 
even better in a mobile world -- your laptop might change IP address a 
dozen times per day, but if it keeps reconnecting with your presence 
server you could base a stable "host" identity on the IM ID to enable 
peer to peer applications, couldn't you?






From owner-ietf@ietf.org  Tue Jan 13 11:51:48 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24026
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 11:51:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRb2-0006Qe-Qk
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:40:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfoSM-00049e-AG
	for ietf@asgard.ietf.org; Sun, 11 Jan 2004 17:53:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19644
	for <ietf@ietf.org>; Sun, 11 Jan 2004 17:53:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfoS5-0001JA-00
	for ietf@ietf.org; Sun, 11 Jan 2004 17:53:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfoPN-00018p-00
	for ietf@ietf.org; Sun, 11 Jan 2004 17:50:13 -0500
Received: from stratton-four-sixty-four.mit.edu ([18.187.6.209] helo=konishi-polis.mit.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfoIF-0000vt-00
	for ietf@ietf.org; Sun, 11 Jan 2004 17:42:51 -0500
Received: by konishi-polis.mit.edu (Postfix, from userid 8042)
	id 1C79915159C; Sun, 11 Jan 2004 17:42:24 -0500 (EST)
To: Ken Hornstein <kenh@cmf.nrl.navy.mil>
Cc: ietf@ietf.org
Subject: Re: Visa for South Korea
References: <200312301903.hBUJ3aRr002561@ginger.cmf.nrl.navy.mil>
From: Sam Hartman <hartmans@mit.edu>
Date: Sun, 11 Jan 2004 17:42:24 -0500
In-Reply-To: <200312301903.hBUJ3aRr002561@ginger.cmf.nrl.navy.mil> (Ken
 Hornstein's message of "Tue, 30 Dec 2003 14:03:36 -0500")
Message-ID: <tslsmimksz3.fsf@konishi-polis.mit.edu>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>>>>> "Ken" == Ken Hornstein <kenh@cmf.nrl.navy.mil> writes:

    >>> What I'm really looking for is some form of official
    >>> government communication on the subject (unless of course the
    >>> hosts are the ones who are manning the passport control desks
    >>> at the airport).
    >>> 
    >> So call the nearest Korean consulate/embassy.  Answering this
    >> kind of question is part of their job.

    Ken> I actually already had put a call in to them; the relevant
    Ken> person was out of the office, but I left a message.  We'll
    Ken> see what they say.

I did as well and here is what I got.

The phone was answered.  I asked to speak to someone about Visa
information.  I was transferred to someone who answered in Korean; I
did not understand the greeting.

"Hi.  I'm an American citizen traveling to Seoul in late February to
attend a meeting of a professional society.  Do I need a visa?"

She asked again for my citizenship and then said that I did not need a
visa.


I chose to describe IETF as a professional society because saying
standards development organization when referring to something
non-ISO-based might confuse a government official.  Similarly, I was
concerned that conference might map to academic conference.


I'd be interested in answers people get from other consulate/embassy
staff both from locations other than Boston and with different
phrasings of the question.







From owner-ietf@ietf.org  Tue Jan 13 11:51:48 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24029
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 11:51:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRb2-0006Pa-Fe
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:40:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AfBLv-0001gr-Jq
	for ietf@asgard.ietf.org; Sat, 10 Jan 2004 00:08:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09686
	for <ietf@ietf.org>; Sat, 10 Jan 2004 00:08:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfBLt-00052Z-00
	for ietf@ietf.org; Sat, 10 Jan 2004 00:08:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AfBK4-0004z2-00
	for ietf@ietf.org; Sat, 10 Jan 2004 00:06:09 -0500
Received: from mx.bol.bg ([193.200.15.129] helo=mail.bol.bg)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AfBIy-0004v4-00
	for ietf@ietf.org; Sat, 10 Jan 2004 00:05:00 -0500
Received: from bol-zf77hkaqs39.veni.com (lozenec-center.users.bol.bg [192.168.36.30])
	by mail.bol.bg (8.12.9/8.11.2) with ESMTP id i0A54YHQ026115;
	Sat, 10 Jan 2004 07:04:39 +0200
Message-Id: <6.0.1.1.2.20040110065834.02f0dd48@198.111.183.129>
X-Sender: veni-h@198.111.183.129 (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sat, 10 Jan 2004 07:00:19 +0100
To: Wawa Ngenge <ngenge@confucius.gnacademy.org>,
        John C Klensin <john-ietf@jck.com>
From: veni markovski <veni@veni.com>
Subject: Re: [isdf] Re: www.internetforce.org
Cc: ietf@ietf.org, isdf@isoc.org
In-Reply-To: <Pine.LNX.4.58.0401091907020.29579@confucius.gnacademy.org>
References: <E1AdT4L-0005Y9-Iw@asgard.ietf.org>
 <20040105224543.534b421a.ietf@2c9d1f3141b658e37c53395b25a04078.nos ense.org>
 <Pine.LNX.4.58.0401081245210.26656@confucius.gnacademy.org>
 <240387438.1073576717@scan.jck.com>
 <Pine.LNX.4.58.0401091907020.29579@confucius.gnacademy.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="windows-1251"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-KOI8-Plugin-Info: v2.0.43
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Dear Wawa, John, and colleagues,
Talking about approaching questions in a societal forum like the ISDF...
I am following your discussion but don't feel certain I should write to the=
=20
IETF mailing list, so I will only respond in the list where I am subscribed=
=20
- the ISDF.

veni

At 19:09 09.1.2004 '=E3.' Conve -0600, Wawa Ngenge wrote:

>Thank you. This does answer the question, and is a good example of how to
>approach questions in a societal forum like ISDF where even rhetorical
>questions may hide a cry for information.  Once again, thank you.
>w






From owner-ietf@ietf.org  Tue Jan 13 11:53:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24112
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 11:53:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRfs-0007IX-T9
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:45:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgDbB-00048s-KG
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 20:44:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05367
	for <ietf@ietf.org>; Mon, 12 Jan 2004 20:44:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgDb9-0000qW-00
	for ietf@ietf.org; Mon, 12 Jan 2004 20:44:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgDZA-0000mg-00
	for ietf@ietf.org; Mon, 12 Jan 2004 20:42:02 -0500
Received: from proxy1baymi.bay.mi.charter.com ([24.247.24.39] helo=proxy1-baycity.chartermi.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgDYF-0000kt-00
	for ietf@ietf.org; Mon, 12 Jan 2004 20:41:03 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by proxy1-baycity.chartermi.net (8.11.7p1+Sun/8.11.6) with SMTP id i0D1eQ107168
	for <ietf@ietf.org>; Mon, 12 Jan 2004 20:40:26 -0500 (EST)
Received: (qmail 1237 invoked by uid 0); 13 Jan 2004 01:40:23 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.088429 secs); 13 Jan 2004 01:40:23 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 13 Jan 2004 01:40:22 -0000
Message-Id: <6.0.0.22.0.20040112201122.02b83af0@mjs.alientech.net>
X-Mailer: Eudora
Date: Mon, 12 Jan 2004 20:31:19 -0500
To: ietf@ietf.org
From: mikes@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
In-Reply-To: <200401122350.i0CNoRrY096681@calcite.rhyolite.com>
References: <200401122231.i0CMVr8f001694@unknown.hamachi.org>
 <200401122350.i0CNoRrY096681@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 06:50 PM 1/12/2004, Vernon Schryver wrote...
>Instead of paying the extra cost to hire an ISP that cares
>enough to not have spamming customers, people complain about the evils
>of blacklists. 

Feh. Once again with the incorrect assumptions. I don't spam. I would preferentially route email direct for two main reasons: 1) privacy - routing via my ISP's outbound SMTP gives them the right to intercept and read my email, according the ECPA; 2) control - sending from my own system allows me to control retry attempts and times, instead of being forced to wait 4 days for my ISP to bounce an undelivered back to me, assuming they don't just silently lose it.

I can't do so because my IP address is on a blacklist. I have cable modem, but the world thinks I'm a dial-up. For that reason alone, having nothing whatsoever to do with spam, I'm forced to give up privacy and control of my communications.

"Anti-spam" initiatives that are based on such blacklists are quite simply the failed results of irrational, fascist thought. Regardless of your exact definition of spam, all reasonable ones I've heard have one thing in common - it's based on CONTENT, not IP address. Blacklists couldn't care less about content - legitimate email or spam, out it goes, to the detriment of communications.

They also, quite clearly, don't work to eliminate spam. 







From owner-ietf@ietf.org  Tue Jan 13 11:54:18 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24153
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 11:54:18 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRft-0007J6-80
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:45:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgNaq-0008Kl-4p
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 07:24:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09296
	for <ietf@ietf.org>; Tue, 13 Jan 2004 07:24:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgNap-0002rJ-00
	for ietf@ietf.org; Tue, 13 Jan 2004 07:24:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgNZ5-0002n8-00
	for ietf@ietf.org; Tue, 13 Jan 2004 07:22:35 -0500
Received: from proxy5baymi.bay.mi.charter.com ([24.247.24.54] helo=proxy5-baycity.chartermi.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgNYb-0002iX-00
	for ietf@ietf.org; Tue, 13 Jan 2004 07:22:05 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by proxy5-baycity.chartermi.net (8.11.7p1+Sun/8.11.6) with SMTP id i0DCM0o21113
	for <ietf@ietf.org>; Tue, 13 Jan 2004 07:22:00 -0500 (EST)
Received: (qmail 6326 invoked by uid 0); 13 Jan 2004 12:21:56 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.066257 secs); 13 Jan 2004 12:21:56 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 13 Jan 2004 12:21:56 -0000
Message-Id: <6.0.0.22.0.20040113071900.041d7188@mjs.alientech.net>
X-Mailer: Eudora
Date: Tue, 13 Jan 2004 07:21:53 -0500
To: ietf@ietf.org
From: mikes@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
In-Reply-To: <200401130345.i0D3jnpS058424@calcite.rhyolite.com>
References: <6.0.0.22.0.20040112204043.02b83af0@mjs.alientech.net>
 <200401130345.i0D3jnpS058424@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:45 PM 1/12/2004, Vernon Schryver wrote...
>Mr. Sauve could rent an IP address that is not on dial-up or dynamic
>blacklists and run his systems there.

Proven wrong, you now change your argument to one of trying to rationalize interference with legitimate email, and attempting to place the burden on those who wish to use the Internet as designed, not as damaged by your beloved blacklists.

As I said, fascist.






From owner-ietf@ietf.org  Tue Jan 13 11:54:20 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24171
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 11:54:20 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRft-0007Ip-2N
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:45:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgEuR-0001T1-3g
	for ietf@asgard.ietf.org; Mon, 12 Jan 2004 22:08:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09199
	for <ietf@ietf.org>; Mon, 12 Jan 2004 22:08:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgEuP-00067U-00
	for ietf@ietf.org; Mon, 12 Jan 2004 22:08:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgEsW-00063q-00
	for ietf@ietf.org; Mon, 12 Jan 2004 22:06:05 -0500
Received: from mercury.lcs.mit.edu ([18.26.0.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgEqi-0005xp-00
	for IETF@ietf.org; Mon, 12 Jan 2004 22:04:12 -0500
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id B617D872FB; Mon, 12 Jan 2004 22:03:37 -0500 (EST)
To: IETF@ietf.org
Subject: RE: Death of the Internet - details at 11
Cc: jnc@mercury.lcs.mit.edu
Message-Id: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
Date: Mon, 12 Jan 2004 22:03:37 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

    > You seem to have missed the point. ... You will never hear a consumer
    > demanding IPv6 .. You won't hear ISP's demanding IPv6 unless their
    > customers are demanding apps that run over IPv6 (even then the consumer
    > is more likely to use an automated tunnel and make the clueless ISP
    > irrelevant). You won't get new apps unless the development community
    > sees a viable path to personal riches.

Tony, I think you're the one missing the point - although you're half-way
there in your later comments above.

IPv6 simply isn't going to get deployed "as a replacement for IPv4". It's just
not enough better to make it worth switching - and you can flame all day about
how NAT's are preventing deployment of new applications, but I can't run an
SMTP or HTTP server in my house because my provider blocks incoming SMTP
connections unless I pay for business service, and I personally find that a
lot more problematic than the limitations of NAT.

IPv6's only hope of some modest level of deployment is, as the latter part of
your message points out, as the substrate for some hot application(s). Somehow
I doubt anything the IETF does or does not do is going to have any affect on
whether or not that happens.

Of course, that still doesn't get you to the "general replacement for IPv4"
stage. I don't think that goal is reachable - IPv6 just isn't enough better
(i.e. more functionality) than IPv4. It's ironic that one of IPv6's big
concept points ("the IPv4 architecture is fine, we just need to fix a few
details") turns out to be IPv6's Achilles' heel. (Although some of us
predicted that at the time IPv6 was adopted....)


Now if basic IPv6 (and basic IPv6 applications) were reworked so that it's
IMPOSSIBLE to tell, from looking at the packet, what kind of service it's
going to - e.g. by using random TCP ports for applications servers, and having
the ICP include a service name (the field for which is encrypted so
middle-boxes can't read it) to do the rendezvous - that would be the kind of
thing that might interest a few more people.

And while we're at it, you probably want to make it impossible for the ISP to
even tell if it's a TCP SYN, otherwise they'll probably just filter them *all*
out incoming...


    > Continuing work on IPv4 only creates the illusion that it is a viable
    > protocol for application developers to rely on for future income.

Continuing work on IPv6 only creates the illusion that it is a viable protocol
for the network as a whole to rely on for the provision of ubiquitous datagram
substrate service.

In anything even vaguely like its current form, that goal is completely
unreachable for IPv6, and the continued chanting of "IPv6 is the future" only
prevents work on *feasible* upgrades that will allow the continued provision
of ubiquitous datagram substrate service.

	Noel





From owner-ietf@ietf.org  Tue Jan 13 11:55:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24329
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 11:55:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRft-0007JC-CT
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:45:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgOJ6-0002GU-JZ
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 08:10:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10203
	for <ietf@ietf.org>; Tue, 13 Jan 2004 08:10:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgOJ1-0004Zz-00
	for ietf@ietf.org; Tue, 13 Jan 2004 08:10:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgOD5-0004Go-00
	for ietf@ietf.org; Tue, 13 Jan 2004 08:03:56 -0500
Received: from proxy1baymi.bay.mi.charter.com ([24.247.24.39] helo=proxy1-baycity.chartermi.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgO6N-000438-00
	for ietf@ietf.org; Tue, 13 Jan 2004 07:57:00 -0500
Received: from linux.alientech.net (24.247.81.108.bay.mi.chartermi.net [24.247.81.108])
	by proxy1-baycity.chartermi.net (8.11.7p1+Sun/8.11.6) with SMTP id i0DCuIr22024
	for <ietf@ietf.org>; Tue, 13 Jan 2004 07:56:19 -0500 (EST)
Received: (qmail 6586 invoked by uid 0); 13 Jan 2004 12:56:16 -0000
Received: from mikes@flatsurface.com by linux by uid 506 with qmail-scanner-1.20rc1 
 (clamscan: 0.60. spamassassin: 2.20.  Clear:RC:1:. 
 Processed in 0.102442 secs); 13 Jan 2004 12:56:16 -0000
Received: from ii.alientech.net (HELO MSAUVE-2.flatsurface.com) (192.168.168.1)
  by linux.alientech.net with SMTP; 13 Jan 2004 12:56:15 -0000
Message-Id: <6.0.0.22.0.20040113074147.043115c0@mjs.alientech.net>
X-Mailer: Eudora
Date: Tue, 13 Jan 2004 07:56:12 -0500
To: ietf@ietf.org
From: mikes@flatsurface.com (Mike S)
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:45 PM 1/12/2004, Vernon Schryver wrote...
>Mr. Sauve could rent an IP address that is not on dial-up or dynamic
>blacklists and run his systems there.

Proven wrong, Vernon now changes his tack to one of trying to rationalize interference with legitimate email and attempting to place the burden on those who wish to use the Internet as designed, not as damaged by his beloved blacklists.

As I said, fascist. He has learned to use whois and Google, though, and seems very self-impressed at his ability to learn such simple things. He has apparently not, however, discovered dictionary.com. "In the design of ... software tools, 'the fascist alternative' is the most restrictive and structured way of capturing a particular function;"








From owner-ietf@ietf.org  Tue Jan 13 12:37:03 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27637
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 12:37:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgSCa-0001CQ-CZ
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 12:19:40 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgS8j-0000tf-T0
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 12:15:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26545
	for <ietf@ietf.org>; Tue, 13 Jan 2004 12:15:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgS8e-000609-00
	for ietf@ietf.org; Tue, 13 Jan 2004 12:15:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgS6H-0005fX-00
	for ietf@ietf.org; Tue, 13 Jan 2004 12:13:11 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgS2y-0005DZ-00
	for IETF@ietf.org; Tue, 13 Jan 2004 12:09:44 -0500
Subject: RE: Death of the Internet - details at 11
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 13 Jan 2004 09:09:27 -0800
Content-class: urn:content-classes:message
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C845@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Death of the Internet - details at 11
thread-index: AcPZ7TYmm6Eh/09MRbqFfoz+xFK9OgACf/7Q
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Hayriye Altunbasak" <gt0165c@mail.gatech.edu>, <IETF@ietf.org>
Cc: <jnc@lcs.mit.edu>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Hayriye Altunbasak wrote:
> Should not you first investigate the reason why
> IPv6 is not successful in terms of deployment
> (yet)? So that, we won't make the same mistakes
> if the world decides to sth else....

These reasons are well-known and two-fold:

1. It's an investment without any foreseeable ROI:
- Scarcity of IPv4 addresses? Not any time soon and certainly not soon
enough to justify any investment within the next n years.
- Ease of renumbering? A myth.
- Auto-configuration? Not fundamentally a breakthrough over DHCP.
In other words: what is IPv6 going to buy me or my business in the next
n years? Nothing I don't already have with IPv4; why should I invest in
it (especially given the tight finances these days) ?

2. It does not even provide what IPv4 does:
- No multihoming.
- No PA addresses.
- Ni private addresses.

Michel.




From owner-ietf@ietf.org  Tue Jan 13 12:37:04 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27643
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 12:37:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgSBj-00010V-Fu
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 12:18:47 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgS0x-0000RL-Vm
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 12:07:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25671
	for <ietf@ietf.org>; Tue, 13 Jan 2004 12:06:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgRzZ-00054C-00
	for ietf@ietf.org; Tue, 13 Jan 2004 12:06:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgRxd-0004yu-00
	for ietf@ietf.org; Tue, 13 Jan 2004 12:04:13 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgRvj-0004nH-00
	for ietf@ietf.org; Tue, 13 Jan 2004 12:02:15 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 13 Jan 2004 09:04:13 +0000
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 i0DH1cGN029488;
	Tue, 13 Jan 2004 09:01:39 -0800 (PST)
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.6-GR)
	with ESMTP id ALJ82445;
	Tue, 13 Jan 2004 09:01:37 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id JAA28850; Tue, 13 Jan 2004 09:01:37 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16388.9329.240329.343472@thomasm-u1.cisco.com>
Date: Tue, 13 Jan 2004 09:01:37 -0800 (PST)
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <20040112204907.DB760872F5@mercury.lcs.mit.edu>
References: <20040112204907.DB760872F5@mercury.lcs.mit.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!
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

What leads you to believe that an alternate
solution set isn't the empty set? Isn't entropy
the easiest and most likely outcome?

	    Mike



From owner-ietf@ietf.org  Tue Jan 13 12:49:33 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28792
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 12:49:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgSZn-0003D0-6D
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 12:43:39 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgSZV-00037E-Io
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 12:43:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28288
	for <ietf@ietf.org>; Tue, 13 Jan 2004 12:43:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgSZU-000064-00
	for ietf@ietf.org; Tue, 13 Jan 2004 12:43:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgSXi-0007dB-00
	for ietf@ietf.org; Tue, 13 Jan 2004 12:41:31 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgSVI-0007N7-00
	for IETF@ietf.org; Tue, 13 Jan 2004 12:39:00 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AgSVI-000B7R-00; Tue, 13 Jan 2004 12:39:00 -0500
Date: Tue, 13 Jan 2004 12:39:00 -0500
From: John C Klensin <john-ietf@jck.com>
To: jfcm <info@utel.net>, IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <100401419.1073997540@scan.jck.com>
In-Reply-To: <6.0.1.1.2.20040113144214.03ab0390@mail.utel.net>
References: <E1Ag7Kx-0001Nu-00@ietf-mx>
 <4002FFCE.4020407@iconoplex.co.uk>
 <F9421262-4592-11D8-AB12-00039312C852@isc.org>
 <6.0.1.1.2.20040113144214.03ab0390@mail.utel.net>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Tuesday, 13 January, 2004 15:41 +0100 jfcm <info@utel.net> 
wrote:

> Gentlemen,
> let agree IETF is lacking formal interfaces with the real
> world of users and the real world of operators.  John
> Klensin's official participation to the ICANN BoD is a first
> good step towards formal links with operators.

Sigh.  Whatever that relationship constitutes, "formal links 
with operators" isn't one of them -- there are even fewer actual 
operators represented and actively participating in ICANN than 
there are in IETF.

Please, at least, get your facts right.

    john





From owner-ietf@ietf.org  Tue Jan 13 13:01:49 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29580
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 13:01:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgSmW-00047R-N5
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 12:56:48 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgSiF-0003vU-9Y
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 12:52:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28894
	for <ietf@ietf.org>; Tue, 13 Jan 2004 12:52:20 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgSiE-0000cd-00
	for ietf@ietf.org; Tue, 13 Jan 2004 12:52:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgSgN-0000Tu-00
	for ietf@ietf.org; Tue, 13 Jan 2004 12:50:27 -0500
Received: from h80ad37a4.dhcp.vt.edu ([128.173.55.164] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgSes-0000Q2-00
	for ietf@ietf.org; Tue, 13 Jan 2004 12:48:54 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i0DHmvN3010068;
	Tue, 13 Jan 2004 12:48:57 -0500
Message-Id: <200401131748.i0DHmvN3010068@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: mikes@flatsurface.com (Mike S)
Cc: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
In-Reply-To: Your message of "Tue, 13 Jan 2004 07:21:53 EST."
             <6.0.0.22.0.20040113071900.041d7188@mjs.alientech.net> 
References: <6.0.0.22.0.20040112204043.02b83af0@mjs.alientech.net> <200401130345.i0D3jnpS058424@calcite.rhyolite.com>
            <6.0.0.22.0.20040113071900.041d7188@mjs.alientech.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-2082007319P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 13 Jan 2004 12:48:57 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Tue, 13 Jan 2004 07:21:53 EST, mikes@flatsurface.com (Mike S)  said:

> As I said, fascist.

Godwin.

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

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

iD8DBQFABC+JcC3lWbTT17ARAtYCAKD0ZJWI+GeIwSbkhNb94T6aQ7hwRACfSifY
zbUCH0Ha29s0umAoKvm7Ejs=
=vtw8
-----END PGP SIGNATURE-----

--==_Exmh_-2082007319P--



From owner-ietf@ietf.org  Tue Jan 13 13:01:49 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29583
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 13:01:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgSmW-00046Y-7p
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 12:56:48 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgSem-0003XS-BM
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 12:48:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28773
	for <ietf@ietf.org>; Tue, 13 Jan 2004 12:48:43 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgSei-0000P2-00
	for ietf@ietf.org; Tue, 13 Jan 2004 12:48:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgScn-0000LG-00
	for ietf@ietf.org; Tue, 13 Jan 2004 12:46:46 -0500
Received: from h80ad37a4.dhcp.vt.edu ([128.173.55.164] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgScD-0000G7-00
	for IETF@ietf.org; Tue, 13 Jan 2004 12:46:09 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i0DHkBMG010010;
	Tue, 13 Jan 2004 12:46:11 -0500
Message-Id: <200401131746.i0DHkBMG010010@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: "J. Noel Chiappa" <jnc@lcs.mit.edu>, IETF@ietf.org
Subject: Re: Death of the Internet - details at 11 
In-Reply-To: Your message of "Tue, 13 Jan 2004 08:23:10 PST."
             <DD7FE473A8C3C245ADA2A2FE1709D90B06C840@server2003.arneill-py.sacramento.ca.us> 
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C840@server2003.arneill-py.sacramento.ca.us>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-2082853805P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 13 Jan 2004 12:46:11 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Tue, 13 Jan 2004 08:23:10 PST, Michel Py <michel@arneill-py.sacramento.ca.us>  said:

> And as of the DoD requirements, those of us that are old enough will
> remember the ADA language.....

GOSIP.

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

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

iD8DBQFABC7icC3lWbTT17ARAhNIAKDhGWSrtEMjMXEidtaoXR6qtCLDFACgppSq
/JzgssJ2LW59oYdArR+EtXA=
=rByF
-----END PGP SIGNATURE-----

--==_Exmh_-2082853805P--



From owner-ietf@ietf.org  Tue Jan 13 13:12:05 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00694
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 13:12:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgSx0-0005Tt-Cg
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 13:07:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgSwE-0005NG-7R
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 13:06:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00089
	for <ietf@ietf.org>; Tue, 13 Jan 2004 13:06:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgSwD-0001xI-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:06:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgSuK-0001g6-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:04:52 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgSsF-0001Qw-00
	for IETF@ietf.org; Tue, 13 Jan 2004 13:02:43 -0500
Received: from netcore.fi ([193.94.160.1])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AgSsG-0002rT-7t
	for IETF@ietf.org; Tue, 13 Jan 2004 13:02:44 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i0DI2SH17882;
	Tue, 13 Jan 2004 20:02:28 +0200
Date: Tue, 13 Jan 2004 20:02:28 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: "J. Noel Chiappa" <jnc@lcs.mit.edu>
cc: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <5.0.2.1.0.20040113093724.009e5450@mailhub.exis.net>
Message-ID: <Pine.LNX.4.44.0401132000520.17809-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 13 Jan 2004, J. Noel Chiappa wrote:
> The upgrade path (replace the entire internet layer in one fell swoop) IPv6
> adopted clearly isn't working. Time to try something rather different.

Exactly.  As we have been saying for years not, we must aim for
co-existence of IPv4 and IPv6, not replacing IPv4 with IPv6.

-- 
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  Tue Jan 13 13:25:12 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27639
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 12:37:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgRtS-0002rH-1v
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 11:59:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgRt2-0002mL-6w
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 11:59:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24854
	for <ietf@ietf.org>; Tue, 13 Jan 2004 11:59:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgRt1-0004Sn-00
	for ietf@ietf.org; Tue, 13 Jan 2004 11:59:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgRqW-000449-00
	for ietf@ietf.org; Tue, 13 Jan 2004 11:56:52 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgRoP-0003hy-00
	for ietf@ietf.org; Tue, 13 Jan 2004 11:54:42 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i0DGsbHs045700
	for ietf@ietf.org env-from <vjs>;
	Tue, 13 Jan 2004 09:54:37 -0700 (MST)
Date: Tue, 13 Jan 2004 09:54:37 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401131654.i0DGsbHs045700@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
References: <6B21B4FC-45E3-11D8-9AFA-000A9571873E@guppylake.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Nathaniel Borenstein <nsb@guppylake.com>

> > You might be ignorant instead of dishonest.
>
> How very kind of you to consider two possibilities, thank  you.

My original words that you felt labelled you dishonest explicitly
included that possibility.  Most people have strong opinions about
spam, but have not really looked at it, and are quite wrong about it.


> ...
>      (And, by the way, I consider *any* false positives unacceptable if 
> there's no suitable mechanism for detecting and correcting them.)

That wisdom applies to a lot more than spam defenses.

However, it is worth noting that many and perhaps most email users
value avoiding false negatives more than avoiding false positives in
their spam defenses.  That is one reason why the blunt, high false
positive blacklists are popular.  One also must not try to reduce false
positives from spam filters much below the error rate of SMTP in the
real world (e.g. not just bounces but blackholes).


> This discussion is going nowhere, so I'm going back to more serious 
> work on comprehensive spam control.  

That's fine, but it would be wise to recognize the overall situation
while developing those comprehensive controls.  Railing against the
evil conspiracy of big monopolistic ISPs using blacklists against
themselves isn't productive.  Except for organizations that run their
own private blacklists, public anti-spam blacklists will remain quite
popular.  MAPS used to claim 45% of the Internet used the RBL.  I
suspect that at least that much uses the RBL+, CRL, XBL, SBL, and/or
SPEWS.  Public blacklists are here to stay, because they work.

The only likely tactic for reducing the use of blunt blacklists such
as those listing dynamic IP addresses is to convince ISPs to take network
abuse seriously.  As long as big ISPs make listing their own IP adddresses
"dynamic" lists their main response to their own bad customers, those
blunt, high false positive blacklists will remain popular.

Talk about transition plans to IPv6, comprehensive spam controls,
the evils of NAT, the evils of blacklists, media conglomerate ISPs
distributing NAT boxes to break VoIP, and monopolisitic ISPs using
blacklists is one thing.  Actually doing something is something else.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Tue Jan 13 13:42:48 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02487
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 13:42:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgTMA-000714-Bj
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 13:33:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgTKz-0006vH-Ai
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 13:32:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01904
	for <ietf@ietf.org>; Tue, 13 Jan 2004 13:32:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTKy-0003YC-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:32:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgTIz-0003Tv-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:30:22 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTHP-0003NJ-00
	for IETF@ietf.org; Tue, 13 Jan 2004 13:28:43 -0500
Subject: RE: Death of the Internet - details at 11
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 13 Jan 2004 10:28:25 -0800
Content-class: urn:content-classes:message
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C846@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Death of the Internet - details at 11
thread-index: AcPaAOOqzEtfKg59TmO/EgzoVqscSAAAN2mg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Pekka Savola" <pekkas@netcore.fi>, "J. Noel Chiappa" <jnc@lcs.mit.edu>
Cc: <IETF@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Pekka Savola
> Exactly.  As we have been saying for years not,
> we must aim for co-existence of IPv4 and IPv6,
> not replacing IPv4 with IPv6.

IPv6 is currently not worth the price of dual-stack, which is the very
reason it is not being deployed. As of transition mechanisms, they're
not good enough to run an IPv6-only network, which in turns makes
dual-stack mandatory.
=20
Michel.




From owner-ietf@ietf.org  Tue Jan 13 13:55:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03467
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 13:55:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgTdV-0007xk-QX
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 13:51:33 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgTUa-0007O7-QW
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 13:42:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02431
	for <ietf@ietf.org>; Tue, 13 Jan 2004 13:42:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTUZ-00048a-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:42:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgTSj-00041D-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:40:25 -0500
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTR1-0003o7-00
	for IETF@ietf.org; Tue, 13 Jan 2004 13:38:40 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i0DIc7K18439;
	Tue, 13 Jan 2004 20:38:07 +0200
Date: Tue, 13 Jan 2004 20:38:07 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: "J. Noel Chiappa" <jnc@lcs.mit.edu>
cc: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <Pine.LNX.4.44.0401132000520.17809-100000@netcore.fi>
Message-ID: <Pine.LNX.4.44.0401132037180.17809-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 13 Jan 2004, Pekka Savola wrote:

> On Tue, 13 Jan 2004, J. Noel Chiappa wrote:
> > The upgrade path (replace the entire internet layer in one fell swoop) IPv6
> > adopted clearly isn't working. Time to try something rather different.
> 
> Exactly.  As we have been saying for years not, we must aim for
                                             ^^^
Oops:                                      s/not/now/

> co-existence of IPv4 and IPv6, not replacing IPv4 with IPv6.

.. but this was probably understandable. :-)

-- 
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  Tue Jan 13 13:55:15 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03486
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 13:55:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgTb7-0007oq-3X
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 13:49:05 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgTT0-0007Ln-Hj
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 13:40:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02327
	for <ietf@ietf.org>; Tue, 13 Jan 2004 13:40:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTSz-00043e-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:40:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgTRV-0003w6-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:39:09 -0500
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTPm-0003nv-00
	for IETF@ietf.org; Tue, 13 Jan 2004 13:37:22 -0500
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1.3)
  with ESMTP-TLS id 650082 for IETF@ietf.org; Tue, 13 Jan 2004 16:23:05 -0600
Message-ID: <40043ADE.7050703@ehsco.com>
Date: Tue, 13 Jan 2004 12:37:18 -0600
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
In-Reply-To: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On 1/12/2004 9:03 PM, Noel Chiappa wrote:

> IPv6's only hope of some modest level of deployment is, as the latter
> part of your message points out, as the substrate for some hot
> application(s). Somehow I doubt anything the IETF does or does not do
> is going to have any affect on whether or not that happens.

Yup, it needs a killer app or feature. Bigger address space was that
feature, but one made moot by NATs.

There are other features (security, etc), but they are end-user oriented
and don't really hold promise to ISPs or the equipment manufacturers (the
simple cost-of-goods factor means that the vendor community has negative
motivation to offer IPv6 in low-end gear). There has to be some kind of
effort to get past these hurdles -- development of a routing service that
makes multi-homing simpler for everybody at a magnitude higher scale, or
convincing vendors that IPv6 in the cheapest gear is in their best
interests, and so forth.

Since the engineers in the IETF tend to hold these kind of marketing
efforts in relatively low regard, the likelihood of any of this changing
is close to nil.

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




From owner-ietf@ietf.org  Tue Jan 13 13:55:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03528
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 13:55:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgTda-00084M-PG
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 13:51:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgTZJ-0007lX-P1
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 13:47:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02886
	for <ietf@ietf.org>; Tue, 13 Jan 2004 13:47:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTZI-0004fA-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:47:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgTXa-0004UE-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:45:26 -0500
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTW6-0004Hy-00
	for IETF@ietf.org; Tue, 13 Jan 2004 13:43:54 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i0DIhGq18567;
	Tue, 13 Jan 2004 20:43:16 +0200
Date: Tue, 13 Jan 2004 20:43:16 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
cc: "J. Noel Chiappa" <jnc@lcs.mit.edu>, <IETF@ietf.org>
Subject: RE: Death of the Internet - details at 11
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C846@server2003.arneill-py.sacramento.ca.us>
Message-ID: <Pine.LNX.4.44.0401132038210.17809-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 13 Jan 2004, Michel Py wrote:
> IPv6 is currently not worth the price of dual-stack, which is the very
> reason it is not being deployed. 

Some think it's worth the price.  In many cases, the price (in terms
of money, at least) is zero.

In any case, the users are given the opportunity to run applications
which leverage IPv6, with or without support from their ISPs or sites.
If they don't want to, that's another issue..

> As of transition mechanisms, they're not good enough to run an
> IPv6-only network, which in turns makes dual-stack mandatory.

No problem, because IPv6-only networks don't make sense anyway.

However, the transition mechanisms that have been deployed seem to be
good enough to enable dual-stack deployments.

-- 
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  Tue Jan 13 13:56:31 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03588
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 13:56:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgTdc-000871-CU
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 13:51:40 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgTau-0007o8-Cs
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 13:48:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03121
	for <ietf@ietf.org>; Tue, 13 Jan 2004 13:48:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTat-0004oA-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:48:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgTZT-0004ge-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:47:23 -0500
Received: from evrtwa1-ar8-4-65-026-048.evrtwa1.dsl-verizon.net ([4.65.26.48] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTXq-0004VW-00
	for IETF@ietf.org; Tue, 13 Jan 2004 13:45:42 -0500
Received: from eaglet (127.0.0.1:3080)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S41F59> for <IETF@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 13 Jan 2004 10:45:36 -0800
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Noel Chiappa'" <jnc@mercury.lcs.mit.edu>, <IETF@ietf.org>
Subject: RE: Death of the Internet - details at 11
Date: Tue, 13 Jan 2004 10:45:30 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
Thread-Index: AcPZ9mEOI+yfGlI0Rz2HO3wsOmx7HgABRdMQ
Message-Id: <E1AgTXq-0004VW-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Noel Chiappa wrote:
> ...
> IPv6 simply isn't going to get deployed "as a replacement for IPv4". It's
> just
> not enough better to make it worth switching - and you can flame all day
> about
> how NAT's are preventing deployment of new applications, but I can't run
> an
> SMTP or HTTP server in my house because my provider blocks incoming SMTP
> connections unless I pay for business service, and I personally find that
> a
> lot more problematic than the limitations of NAT.

This sounds more like a point to raise with a regulatory agency than a
technical discussion. Your ISP would make you a prime candidate for a
tunnel-broker that will get you past the blockage:
http://www.freenet6.net/

> 
> IPv6's only hope of some modest level of deployment is, as the latter part
> of
> your message points out, as the substrate for some hot application(s).
> Somehow
> I doubt anything the IETF does or does not do is going to have any affect
> on
> whether or not that happens.

You may be right, but that only argues that the IETF is irrelevant to the
development of applications. If that is true, why do we have an applications
area full of working groups? My question was really why they are not
recognizing that at this point IPv4 is a dead end, and stopping any work
that assumes an IPv4 substrate? Yes apps are supposed to be agnostic, but we
all know that apps insist on hooks down the stack, because the app developer
believes he can do a better job of managing the network than the OS.
 
> 
> Of course, that still doesn't get you to the "general replacement for
> IPv4"
> stage. I don't think that goal is reachable - IPv6 just isn't enough
> better
> (i.e. more functionality) than IPv4. It's ironic that one of IPv6's big
> concept points ("the IPv4 architecture is fine, we just need to fix a few
> details") turns out to be IPv6's Achilles' heel. (Although some of us
> predicted that at the time IPv6 was adopted....)

As you may recall, I really don't care about the bit pattern in the header,
as long as it has enough bits. I have been the pragmatist focused on getting
whatever is implemented actually deployed (we could have had TUBA deployed
long ago, as some of us had the routing infrastructure up before the IPv6
decision). IETF internal conflict has had more to do with any delays than
the market could have. 

> 
> 
> Now if basic IPv6 (and basic IPv6 applications) were reworked so that it's
> IMPOSSIBLE to tell, from looking at the packet, what kind of service it's
> going to - e.g. by using random TCP ports for applications servers, and
> having
> the ICP include a service name (the field for which is encrypted so
> middle-boxes can't read it) to do the rendezvous - that would be the kind
> of
> thing that might interest a few more people.

As I recall, several people including Peter Ford were arguing that the
transport layer should be reworked at the same time, because making the
stack and application changes would be a big enough job that people would
only want to do it once. There was a vast outcry in the IETF to make the
minimum number of changes and keep the architecture exactly the same. Now we
find continuing efforts to rework the architecture because various groups
didn't get the 'minor' tweak they wanted. 

> 
> And while we're at it, you probably want to make it impossible for the ISP
> to
> even tell if it's a TCP SYN, otherwise they'll probably just filter them
> *all*
> out incoming...

See tunneling comment above.

> 
> 
>     > Continuing work on IPv4 only creates the illusion that it is a
> viable
>     > protocol for application developers to rely on for future income.
> 
> Continuing work on IPv6 only creates the illusion that it is a viable
> protocol
> for the network as a whole to rely on for the provision of ubiquitous
> datagram
> substrate service.
> 
> In anything even vaguely like its current form, that goal is completely
> unreachable for IPv6, and the continued chanting of "IPv6 is the future"
> only
> prevents work on *feasible* upgrades that will allow the continued
> provision
> of ubiquitous datagram substrate service.

Clearly work on IPv6 is not preventing work on changing the fundamental
Internet architecture (see multi6). Turning your earlier argument around,
there is nothing the IETF does or does not do that precludes the IETF from
doing something else. What the IETF can influence is public perception (read
that average developer on the street) by where it places a clear focus. From
the outside, the IETF is continuing to work on IPv4, therefore the IETF
doesn't believe it is a dead end. The average developer is not going to take
the time to learn something different unless it is clear the market is going
away from what he already knows. We can debate all day about how much
influence the IETF has on the market, but given the current abundance of
vendor participants, there is a clear path from standards focus to products
available to the marketplace. 

Like it or not, we are at the end of the IPV4 road, and IPv6 is the only
viable alternative. Anything that comes out of rearchitecting the Internet
will be at least another 10 year process. I realize you would like things to
occur much faster than that, but even IPv4 took over 10 years to make it out
of the lab and into mainstream use (this is easy to overlook if you were so
close to the action that you missed the forest for all those pesky trees).
The market will adopt any technology that seems to solve the perceived
problem cheaper than the alternatives. In a world of apps where consumer
clients connect to publicly operated servers, IPv4 w/NAT is the cheapest
approach. In a world with arbitrary app interactions, the cost of managing
code development and NAT configurations/updates will easily exceed the cost
of changing protocols. At the same time, anyone trying to make a sweeping
one-shot change is just asking for pain. There are tools to make the change
reasonably straight forward for the average network manager. Can the same be
said for a completely new architecture?

Tony 





From owner-ietf@ietf.org  Tue Jan 13 13:59:09 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03679
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 13:59:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgTeZ-0008GK-6D
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 13:52:39 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgTcG-0007rV-Iz
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 13:50:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03250
	for <ietf@ietf.org>; Tue, 13 Jan 2004 13:50:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTcF-0004r8-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:50:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgTaM-0004jg-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:48:19 -0500
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTYT-0004XT-00
	for ietf@ietf.org; Tue, 13 Jan 2004 13:46:21 -0500
Received: from [10.0.2.2] (adsl-63-202-92-157.dsl.snfc21.pacbell.net [63.202.92.157])
	(authenticated bits=0)
	by above.proper.com (8.12.10/8.12.8) with ESMTP id i0DIkHic057768
	for <ietf@ietf.org>; Tue, 13 Jan 2004 10:46:17 -0800 (PST)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0602049ebc29ecc7b879@[10.0.2.2]>
In-Reply-To: <200401131748.i0DHmvN3010068@turing-police.cc.vt.edu>
References: <6.0.0.22.0.20040112204043.02b83af0@mjs.alientech.net>
 <200401130345.i0D3jnpS058424@calcite.rhyolite.com>           
 <6.0.0.22.0.20040113071900.041d7188@mjs.alientech.net>
 <200401131748.i0DHmvN3010068@turing-police.cc.vt.edu>
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: Tue, 13 Jan 2004 10:46:17 -0800
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-8.0 required=5.0 tests=HABEAS_SWE autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:48 PM -0500 1/13/04, Valdis.Kletnieks@vt.edu wrote:
>On Tue, 13 Jan 2004 07:21:53 EST, mikes@flatsurface.com (Mike S)  said:
>
>  > As I said, fascist.
>
>Godwin.

Valdis, you have confused two protocols that produced similar results 
but used different underlying transports and different signalling.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Tue Jan 13 14:14:10 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04829
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 14:14:10 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgTu2-0003GY-Sx
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 14:08:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgTtq-0003CQ-RU
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 14:08:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04732
	for <ietf@ietf.org>; Tue, 13 Jan 2004 14:08:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTtp-0006KN-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:08:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgTsB-0006Ia-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:06:43 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgTrZ-0006EU-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:06:05 -0500
Received: from dank ([191.1.2.3]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com; Tue, 13 Jan 2004 14:06:04 -0500
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: "Eric A. Hall" <ehall@ehsco.com>
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: Re: Death of the Internet - details at 11
Cc: ietf@ietf.org
Date: Tue, 13 Jan 2004 14:06:04 -0500
Message-ID: <20040113190604148.AAA148@hq.lindsayelec.com@dank>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>Yup, it needs a killer app or feature. Bigger address space was that
>feature, but one made moot by NATs.

VoIP and multimedia via SIP without having a resident network engineer in
your attic. 
Enough said?


Dan




From owner-ietf@ietf.org  Tue Jan 13 14:35:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06354
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 14:35:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgUFK-0004Yk-3I
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 14:30:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgUD5-0004Nb-Uf
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 14:28:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05957
	for <ietf@ietf.org>; Tue, 13 Jan 2004 14:28:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgUD4-0007aJ-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:28:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgUBJ-0007XR-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:26:29 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgU9U-0007Uh-00
	for IETF@ietf.org; Tue, 13 Jan 2004 14:24:36 -0500
Received: from isi.edu (upn.isi.edu [128.9.168.55])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i0DJOZD19033;
	Tue, 13 Jan 2004 11:24:35 -0800 (PST)
Message-ID: <400445F4.5030300@isi.edu>
Date: Tue, 13 Jan 2004 11:24:36 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <40043ADE.7050703@ehsco.com>
In-Reply-To: <40043ADE.7050703@ehsco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Eric A. Hall wrote:

> On 1/12/2004 9:03 PM, Noel Chiappa wrote:
> 
> 
>>IPv6's only hope of some modest level of deployment is, as the latter
>>part of your message points out, as the substrate for some hot
>>application(s). Somehow I doubt anything the IETF does or does not do
>>is going to have any affect on whether or not that happens.
> 
> Yup, it needs a killer app or feature. Bigger address space was that
> feature, but one made moot by NATs.
> 
> There are other features (security, etc),

One man's bread (security by defeating outside 'calls' to your address) 
is another man's poison (failed apps. because you defeated outside 
'calls' to your address).

Other than conserving addresses, NAT "features" are basically poison 
resold as bread.

Joe





From owner-ietf@ietf.org  Tue Jan 13 14:45:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07090
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 14:45:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgUN4-0005dj-3G
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 14:38:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgUMl-0005bD-BB
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 14:38:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06455
	for <ietf@ietf.org>; Tue, 13 Jan 2004 14:38:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgUMj-00009X-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:38:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgUKp-00001h-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:36:19 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgUIz-0007lE-00
	for IETF@ietf.org; Tue, 13 Jan 2004 14:34:25 -0500
Subject: RE: Death of the Internet - details at 11
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 13 Jan 2004 11:34:08 -0800
Content-class: urn:content-classes:message
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C84B@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Death of the Internet - details at 11
thread-index: AcPZ9mEOI+yfGlI0Rz2HO3wsOmx7HgABRdMQAAOoe1A=
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Tony Hain" <alh-ietf@tndh.net>, "Noel Chiappa" <jnc@mercury.lcs.mit.edu>,
        <IETF@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Tony,

> Tony Hain wrote
> Like it or not, we are at the end of the IPV4 road

I think that's where you missed it. We are not. The truth is that the
end of the IPv4 road is in sight; how far away we don't really know, as
looking through the NAT binoculars does not seem to make it closer. How
fast we will be there we don't know either, as the Ferrari we were
driving 3 years ago has run out of gas and we're now traveling in a much
slower bus.

> Anything that comes out of rearchitecting the
> Internet will be at least another 10 year process.

If it's designed as a protocol, likely. If it's designed as a product
with a migration roadmap, not necessarily so. The very flaw in IPv6 is
that it's never been designed as a product that needs to be adopted.

Michel.




From owner-ietf@ietf.org  Tue Jan 13 14:46:24 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07183
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 14:46:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgUQw-00060F-4A
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 14:42:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgUQe-0005xj-Gz
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 14:42:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06926
	for <ietf@ietf.org>; Tue, 13 Jan 2004 14:42:18 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgUQd-0000Zj-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:42:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgUOo-0000Pj-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:40:27 -0500
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgUMz-0000Bb-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:38:33 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i0DJcVhW003715;
	Tue, 13 Jan 2004 14:38:31 -0500
Message-Id: <200401131938.i0DJcVhW003715@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Paul Hoffman / IMC <phoffman@imc.org>
Cc: ietf@ietf.org
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx 
In-Reply-To: Your message of "Tue, 13 Jan 2004 10:46:17 PST."
             <p0602049ebc29ecc7b879@[10.0.2.2]> 
References: <6.0.0.22.0.20040112204043.02b83af0@mjs.alientech.net> <200401130345.i0D3jnpS058424@calcite.rhyolite.com> <6.0.0.22.0.20040113071900.041d7188@mjs.alientech.net> <200401131748.i0DHmvN3010068@turing-police.cc.vt.edu>
            <p0602049ebc29ecc7b879@[10.0.2.2]>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1293344253P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 13 Jan 2004 14:38:31 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Tue, 13 Jan 2004 10:46:17 PST, Paul Hoffman / IMC <phoffman@imc.org>  said:
> At 12:48 PM -0500 1/13/04, Valdis.Kletnieks@vt.edu wrote:
> >On Tue, 13 Jan 2004 07:21:53 EST, mikes@flatsurface.com (Mike S)  said:
> >
> >  > As I said, fascist.
> >
> >Godwin.
> 
> Valdis, you have confused two protocols that produced similar results 
> but used different underlying transports and different signalling.

Call it a pre-emptive first strike.  Rate we're going here, it'll be Godwin time soon enough ;)

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

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

iD8DBQFABEk3cC3lWbTT17ARAmYsAJ9kPr8QspkSovlt8apamM0kTaxP9QCdGETb
cCHLkOpPx+4va6G0B8ZPBiA=
=gmJV
-----END PGP SIGNATURE-----

--==_Exmh_1293344253P--



From owner-ietf@ietf.org  Tue Jan 13 15:00:40 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08095
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 15:00:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgUeV-0007jS-DF
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 14:56:39 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgUe9-0007gh-Mr
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 14:56:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07966
	for <ietf@ietf.org>; Tue, 13 Jan 2004 14:56:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgUe8-0001cL-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:56:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgUcG-0001Xz-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:54:21 -0500
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgUaS-0001Tl-00
	for IETF@ietf.org; Tue, 13 Jan 2004 14:52:28 -0500
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1.3)
  with ESMTP-TLS id 650102; Tue, 13 Jan 2004 17:38:12 -0600
Message-ID: <40044C79.907@ehsco.com>
Date: Tue, 13 Jan 2004 13:52:25 -0600
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Joe Touch <touch@ISI.EDU>
CC: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <40043ADE.7050703@ehsco.com> <400445F4.5030300@isi.edu>
In-Reply-To: <400445F4.5030300@isi.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On 1/13/2004 1:24 PM, Joe Touch wrote:

> Eric A. Hall wrote:

> Other than conserving addresses, NAT "features" are basically poison 
> resold as bread.

Heck, I don't even like the conservation feature.

Misguided allocation policies created a false demand. We would have been
better off to run out of addresses than to let gateways 'rescue' us from
our false shortage.

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




From owner-ietf@ietf.org  Tue Jan 13 15:25:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06351
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 14:35:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgUES-0004Vr-85
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 14:29:44 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgU7H-00049q-42
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 14:22:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05747
	for <ietf@ietf.org>; Tue, 13 Jan 2004 14:22:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgU7F-0007O0-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:22:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgU5O-0007KN-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:20:23 -0500
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgU3Z-0007Aj-00
	for ietf@ietf.org; Tue, 13 Jan 2004 14:18:29 -0500
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1.3)
  with ESMTP-TLS id 650093; Tue, 13 Jan 2004 17:04:13 -0600
Message-ID: <40044482.8030909@ehsco.com>
Date: Tue, 13 Jan 2004 13:18:26 -0600
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dan Kolis <dank@hq.lindsayelec.com>
CC: ietf@ietf.org
Subject: Re: Death of the Internet - details at 11
References: <20040113190604148.AAA148@hq.lindsayelec.com@dank>
In-Reply-To: <20040113190604148.AAA148@hq.lindsayelec.com@dank>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On 1/13/2004 1:06 PM, Dan Kolis wrote:

>>Yup, it needs a killer app or feature. Bigger address space was that
>>feature, but one made moot by NATs.
> 
> VoIP and multimedia via SIP without having a resident network engineer in
> your attic. 
> Enough said?

"in your attic" implies end-user benefit. As I said, I think the hurdles
are in the carrier and equipment space, not the end-user benefits.

Keep in mind that "larger address space" was beneficial towards ISPs, and
not just end-users.

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




From owner-ietf@ietf.org  Tue Jan 13 17:21:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18095
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 17:21:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgWlG-0000m5-So
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 17:11:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgWk1-0000dV-G1
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 17:10:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17737
	for <ietf@ietf.org>; Tue, 13 Jan 2004 17:10:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgWju-000206-00
	for ietf@ietf.org; Tue, 13 Jan 2004 17:10:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgWi1-0001yS-00
	for ietf@ietf.org; Tue, 13 Jan 2004 17:08:25 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgWhA-0001x5-00
	for IETF@ietf.org; Tue, 13 Jan 2004 17:07:32 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AgWh9-000DU5-00; Tue, 13 Jan 2004 17:07:31 -0500
Date: Tue, 13 Jan 2004 17:07:31 -0500
From: John C Klensin <john-ietf@jck.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF@ietf.org
Subject: RE: Death of the Internet - details at 11
Message-ID: <116512686.1074013651@scan.jck.com>
In-Reply-To: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Monday, 12 January, 2004 22:03 -0500 Noel Chiappa 
<jnc@mercury.lcs.mit.edu> wrote:

>...
> IPv6 simply isn't going to get deployed "as a replacement for
> IPv4". It's just not enough better to make it worth switching
> - and you can flame all day about how NAT's are preventing
> deployment of new applications, but I can't run an SMTP or
> HTTP server in my house because my provider blocks incoming
> SMTP connections unless I pay for business service, and I
> personally find that a lot more problematic than the
> limitations of NAT.
>
> IPv6's only hope of some modest level of deployment is, as the
> latter part of your message points out, as the substrate for
> some hot application(s). Somehow I doubt anything the IETF
> does or does not do is going to have any affect on whether or
> not that happens.

Noel, I'm slightly more optimistic along at least two other 
dimensions...

(1) As others have pointed out, the knowledge/skill level of a 
typical ISP seems to be on a rapid downslope with no end in 
sight.  There are lots of ways in which that is not surprising, 
but the only realistic solution for someone who needs high 
reliability in that environment is multihoming, and there seems 
to be no hope for multihoming of small-scale networks with IPv4. 
The bad news, of course, is that the IPv6 multihoming ideas that 
don't cause immediate routing catastrophes seem to be about as 
ready/ mature/ deployed today as they were a decade ago, which 
is to say... Not. And that _is_ an IETF problem.

(2) The "no servers unless you pay business rates", and its 
close relative, "you don't get to run VPNs, or use your own 
email address rather than ours" nonsense you and many others are 
experiencing is sort of an old story.  In a competitive market, 
it is also a pretty simple matter of economics:

	* You don't "want" the server and address capability
	enough to pay for it, because you consider it
	excessively more expensive than the cheap "client"
	service.  I go ahead and pay for it, both because I have
	a higher perception of need and because it is still lots
	cheaper, and offers better performance most days, than a
	dedicated DS0 from any plausible ISP I've been able to
	find.
	
	* The difference between those "business rates" and
	whatever you are paying are mostly determined by a "what
	they can get away with" mentality -- we know what the
	marginal operational costs are.   If those prices stay
	high, it is either because there is no alternate
	provider, or because there is (illegal) price-fixing
	going on, or because no one sees a business opportunity
	by operating a business service at a lower margin.  Many
	of us can remember when the solution to "no viable
	Internet dialup service" was "go form a consortium with
	a few friends"... perhaps it is time to do something
	similar with DSL.  Or maybe we would rather whine than
	do something, perhaps because what we have been fed is "good 
	enough".

And, of course, if enough of those sorts of  things happen, it 
starts to put pressure on the address space, and that means IPv6 
unless someone comes up with another viable alternative _really_ 
soon.

No, that doesn't make me a lot more optimistic.  But some...

      john




From owner-ietf@ietf.org  Tue Jan 13 18:14:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21246
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 18:14:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgXeP-00037n-DH
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 18:08:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgXe4-0002zy-UL
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 18:08:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20500
	for <ietf@ietf.org>; Tue, 13 Jan 2004 18:08:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgXe3-0004aI-00
	for ietf@ietf.org; Tue, 13 Jan 2004 18:08:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgXcA-0004X3-00
	for ietf@ietf.org; Tue, 13 Jan 2004 18:06:27 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgXaP-0004UV-00
	for IETF@ietf.org; Tue, 13 Jan 2004 18:04:37 -0500
Received: from isi.edu (upn.isi.edu [128.9.168.55])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i0DN4aD25461;
	Tue, 13 Jan 2004 15:04:36 -0800 (PST)
Message-ID: <40047985.4010008@isi.edu>
Date: Tue, 13 Jan 2004 15:04:37 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com>
In-Reply-To: <116512686.1074013651@scan.jck.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



John C Klensin wrote:
> 
> Noel, I'm slightly more optimistic along at least two other dimensions...
> 
...
> 
> (2) The "no servers unless you pay business rates", and its close 
> relative, "you don't get to run VPNs, or use your own email address 
> rather than ours" nonsense you and many others are experiencing is sort 
> of an old story.  In a competitive market, it is also a pretty simple 
> matter of economics:
> 
>     * You don't "want" the server and address capability
>     enough to pay for it,  because you consider it
>     excessively more expensive than the cheap "client"
>     service.  I go ahead and pay for it, both because I have
>     a higher perception of need and because it is still lots
>     cheaper, and offers better performance most days, than a
>     dedicated DS0 from any plausible ISP I've been able to
>     find.

That's a specious argument; you declare it nonsense that ISPs charge 
business rates, but you admit that's what they do, and in fact endorse 
it by paying those rates.

>     * The difference between those "business rates" and
>     whatever you are paying are mostly determined by a "what
>     they can get away with" mentality -- we know what the
>     marginal operational costs are.   If those prices stay
>     high, it is either because there is no alternate
>     provider, or because there is (illegal) price-fixing
>     going on, or because no one sees a business opportunity
>     by operating a business service at a lower margin. 

Or because it will cut into their "business" business, which is more to 
the point. The telcos are maximizing a pair of profits - business and 
consumer, not just consumer. The difference in rates is their attempt to 
create two markets, with the simplest amount of effort on their end.

These arguments could be used to justify any status-quo. Some economics 
environments evolve because of a shared perception, whether that 
perception is complicit or not.

Joe




From owner-ietf@ietf.org  Tue Jan 13 18:15:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21345
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 18:15:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgXhB-0004HP-1M
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 18:11:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgXgo-00048f-Qv
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 18:11:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20801
	for <ietf@ietf.org>; Tue, 13 Jan 2004 18:11:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgXgn-0004hB-00
	for ietf@ietf.org; Tue, 13 Jan 2004 18:11:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgXeX-0004dy-00
	for ietf@ietf.org; Tue, 13 Jan 2004 18:08:54 -0500
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgXdv-0004ZS-00
	for IETF@ietf.org; Tue, 13 Jan 2004 18:08:15 -0500
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id KAA558734;
	Wed, 14 Jan 2004 10:07:39 +1100 (EST)
Message-ID: <40047A3A.EAF30D79@swin.edu.au>
Date: Wed, 14 Jan 2004 10:07:38 +1100
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
References: <5.0.2.1.0.20040113093724.009e5450@mailhub.exis.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"J. Noel Chiappa" wrote:
	[..]
> (Yes, I know, "the support situation has improved and we expect wide-scale
> deployment in the next year" - I think I've heard that same mantra every year
> for the last N years. I really ought to go back through my email folders and
> create a web page of IPv6 predictions. In fact, I think that's a good idea -
> it will help make plain how hollow such claims are. My task for today! :-)

Not trying to be facetious, but it would be useful to supplement this with
a list other technologies that didn't taken off and reach world-dominating
acceptance within 10 years of being partially spec'd out. Then note their
ultimate market penetration/impact.

cheers,
gja



From owner-ietf@ietf.org  Tue Jan 13 18:25:34 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22205
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 18:25:34 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgXmi-0006Eh-Cl
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 18:17:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgXiD-0004az-9l
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 18:12:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20934
	for <ietf@ietf.org>; Tue, 13 Jan 2004 18:12:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgXiB-0004mM-00
	for ietf@ietf.org; Tue, 13 Jan 2004 18:12:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgXgo-0004hf-00
	for ietf@ietf.org; Tue, 13 Jan 2004 18:11:15 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgXec-0004e5-00
	for IETF@ietf.org; Tue, 13 Jan 2004 18:08:58 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i0DN8sno038176
	for IETF@ietf.org env-from <vjs>;
	Tue, 13 Jan 2004 16:08:54 -0700 (MST)
Date: Tue, 13 Jan 2004 16:08:54 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401132308.i0DN8sno038176@calcite.rhyolite.com>
To: IETF@ietf.org
Subject: RE: Death of the Internet - details at 11
References: <116512686.1074013651@scan.jck.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: John C Klensin <john-ietf@jck.com>

> ...
> (1) As others have pointed out, the knowledge/skill level of a 
> typical ISP seems to be on a rapid downslope with no end in 
> sight. ...

> ...
> 	* The difference between those "business rates" and
> 	whatever you are paying are mostly determined by a "what
> 	they can get away with" mentality -- we know what the
> 	marginal operational costs are.   If those prices stay
> 	high, it is either because there is no alternate
> 	provider, or because there is (illegal) price-fixing
> 	going on, or because no one sees a business opportunity
> 	by operating a business service at a lower margin.  

The second segment seems to ignore the implications of the first segment.
The marginal cost difference between "business" and "residental" is
zilch only if you have the same people running things and interacting
with customers.  Front line tech-support droids that are dumber than
the Windows boxes of residential customer cost a lot less than humans.
If your front line support people know have a clue about the LSRR IP
option, then either your rates are higher than $30/month or you have
customers like us who do most of our own support (and cost our employers
or ourselves a lot more than $30/month for that support).

> 	                                                    Many
> 	of us can remember when the solution to "no viable
> 	Internet dialup service" was "go form a consortium with
> 	a few friends"... 

There are some surviving ISPs that were started and still run that way
least in geographical areas I know about.  Their prices seem to be
higher than the organizations in that race to maximum stupidity.

It is not a coincidence that they have very few internal spam problems.
They are never blacklisted, not even by the second tier spam blacklists,
even when they rent straight modem dial-up ports.  (Third tier DNS
blacklists are kooky 32-bit random number generators.)


> 	                  perhaps it is time to do something
> 	similar with DSL.  

I know people who have done that sort of thing with DSL and 802.11.
However, I fear that idea is generally killed for now by the fact
that IP bandwidth pricing is set by those outfits racing for ultimate
stupidity.  They see IP bandwidth as a loss-leader.

> 	                   Or maybe we would rather whine than
> 	do something, perhaps because what we have been fed is "good 
> 	enough".

Until people like the individual complaining here that his cable-modem
is listed as a dynamic address are willing to pay for the costs of
real IP service, including the costs of doing more against your spamming
customers than asking blacklists to list your own addresses, there's
not much hope.

We could accept the fact that people who are not willing pay more than
$10-30/month are not interested in the Internet and stop listen to
their whining.  Detroit laughs as people who expect to get Mercedes
for Chevrolet prices.  Why can't we laugh at people who expect to get
real IP service for $10-30/month, or least stop taking their demands
literally?

If cable-modem IP is good enough for you, then you're not interested
in multihoming or even running your own VoIP system.  You might be
happy to have your phones connected to the email and web browser
demark/appliance maintained by your telco/cableco, but you're not really
interested in the Internet.  You lack the interest to be allowed to
run your own servers for anything.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Tue Jan 13 18:39:43 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23011
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 18:39:43 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgY3y-00006V-Lr
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 18:35:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgY3K-0008UR-Aj
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 18:34:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22745
	for <ietf@ietf.org>; Tue, 13 Jan 2004 18:34:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgY3I-0006BM-00
	for ietf@ietf.org; Tue, 13 Jan 2004 18:34:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgY1i-00068l-00
	for ietf@ietf.org; Tue, 13 Jan 2004 18:32:51 -0500
Received: from [63.247.76.241] (helo=montage.altserver.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgY0Y-00064Q-00
	for IETF@ietf.org; Tue, 13 Jan 2004 18:31:38 -0500
Received: from f02m-18-97.d0.club-internet.fr ([212.195.213.97] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1AgY0S-0002or-MU; Tue, 13 Jan 2004 15:31:33 -0800
Message-Id: <6.0.1.1.2.20040113221848.03b263e0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 13 Jan 2004 22:23:17 +0100
To: John C Klensin <john-ietf@jck.com>, IETF@ietf.org
From: jfcm <info@utel.net>
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <100401419.1073997540@scan.jck.com>
References: <E1Ag7Kx-0001Nu-00@ietf-mx>
 <4002FFCE.4020407@iconoplex.co.uk>
 <F9421262-4592-11D8-AB12-00039312C852@isc.org>
 <6.0.1.1.2.20040113144214.03ab0390@mail.utel.net>
 <100401419.1073997540@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 18:39 13/01/04, John C Klensin wrote:
>--On Tuesday, 13 January, 2004 15:41 +0100 jfcm <info@utel.net> wrote:
>>Gentlemen,
>>let agree IETF is lacking formal interfaces with the real world of users 
>>and the real world of operators.  John Klensin's official participation 
>>to the ICANN BoD is a first good step towards formal links with operators.
>
>Sigh.  Whatever that relationship constitutes, "formal links with 
>operators" isn't one of them -- there are even fewer actual operators 
>represented and actively participating in ICANN than there are in IETF.
>
>Please, at least, get your facts right.

Sigh. When will you think in network users terms?
In the operator - designer - user scheme I discuss, the operator (whatever 
the layer) is someone who operates something the user uses. These people 
ICANN claims to gather (and is partly doing).

If this is the way you think, oh, Boy! we better off to subscribe directly 
to ITU.
Thomas, I understand your martyrdom with ICANN.
jfc






From owner-ietf@ietf.org  Tue Jan 13 21:49:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28875
	for <ietf-web-archive@odin.ietf.org>; Tue, 13 Jan 2004 21:49:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgavT-0008Te-UP
	for ietf-list@asgard.ietf.org; Tue, 13 Jan 2004 21:38:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgavQ-0008QK-KE
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 21:38:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28172
	for <ietf@ietf.org>; Tue, 13 Jan 2004 21:38:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgavO-0004kU-00
	for ietf@ietf.org; Tue, 13 Jan 2004 21:38:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgatV-0004Um-00
	for ietf@ietf.org; Tue, 13 Jan 2004 21:36:37 -0500
Received: from razorbill.mail.pas.earthlink.net ([207.217.121.248])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agaon-0004Dk-00
	for ietf@ietf.org; Tue, 13 Jan 2004 21:31:41 -0500
Received: from [38.119.96.105] (helo=CHERYL)
	by razorbill.mail.pas.earthlink.net with asmtp (Exim 3.33 #1)
	id 1AgaoE-0005H1-00
	for ietf@ietf.org; Tue, 13 Jan 2004 18:31:06 -0800
Date: Tue, 13 Jan 2004 21:17:35 -0500
From: Gene Gaines <gene.gaines@gainesgroup.com>
Organization: Gaines Group
X-Priority: 3 (Normal)
Message-ID: <3637111772.20040113211735@gainesgroup.com>
To: ietf@ietf.org
Subject: Fwd: Re: Visa for IETF meeting
In-Reply-To: <1074030940319.consular_usa@mofat.go.kr>
References: <1074030940319.consular_usa@mofat.go.kr>
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="----------D61E10621BB94C3"
X-ELNK-Trace: e892362a6fa8b5d372cc1e1b0924a179239a348a220c26097eaf3c35d0fafb807c55f85125362efd667c3043c0873f7e350badd9bab72f9c350badd9bab72f9c
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,HTML_MESSAGE,HTML_WEB_BUGS,
	LINES_OF_YELLING,PRIORITY_NO_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

------------D61E10621BB94C3
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

Email below is from Mr. Sang Yoo, in the visa office of the
Korean consulate in Washington DC. It should put to rest the
question of visas for the upcoming IETF meeting in Seoul.

Gene Gaines
gene.gaines@gainesgroup.com

This is a forwarded message
From:  =B9=CC=B1=B9 <consular_usa@mofat.go.kr>
To:    gene.gaines@gainesgroup.com
Date:  Tuesday, January 13, 2004, 4:55:40 PM
Subject: Visa for IETF meeting for MR. YOO
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DOriginal message text=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Hi,

Mr.Yoo said that you don't need visas for the conference and can stay up to=
 30days in Korea.

But he pointed out one wrong thing=A0in your email. That is the following.

=A0

You wrote;

=A0 - This applies only to private U.S. citizens.=A0 Government
=A0=A0=A0 employees and citizens of other countries need to contact
=A0=A0=A0 their local Korean embassy for a determination in their
=A0=A0=A0 case. Ken, in your case, if you are a government employee,
=A0=A0=A0 you will need a visa.

=A0

But the right=A0information is that it applies to all U.S.citizens.=20

And even though when government employees go to Korean for official purpose=
, then they need official visas. But when they go to Korea just for tour or=
 non-profit conference, they don't need visas.

If you have more questions, then please write us back.

=A0

Thank you.




=A0

------ [ =BF=F8=BA=BB =B8=DE=BC=BC=C1=F6 ] ------=20

=BA=B8=B3=BD =BB=E7=B6=F7 : "Gene Gaines"=20

=B3=AF=C2=A5 : 2004-01-13 06:15:07=20

=C1=A6=B8=F1 : Visa for IETF meeting for MR. YOO=20

Sang Yoo,

Thank you for speaking with me today.

I described what you told me in the email below, sent to the
email list used by the people that will be attending the
Internet engineering meeting in Seoul 29 February - 5 March 2004.

Gene Gaines
President
Gaines Group
Sterling, Virginia
gene.gaines@gainesgroup.com
703-433-2081



COPY OF MESSAGE SENT BELOW

From:=A0 Gene Gaines <gene.gaines@gainesgroup.com>
To:=A0=A0=A0 Ken Hornstein
CC:=A0=A0=A0 ietf@ietf.org
Date:=A0 Monday, January 12, 2004, 3:18:21 PM
Subject: Visa for South Korea
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DOriginal message text=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Ken,

As it happens, I attended a dinner Saturday that was addressed
by Ambassador Han, the Korean Ambassador to the U.S.

Taking up the Korean visa issue today, I spoke with an official
in the Washington DC visa section.

I believe I can state the visa regulation as it applies to U.S.
citizens.

=A0 - Individuals traveling to Korean to attend the IETF meeting
=A0=A0=A0 do not need a visa, as they are traveling to attend a
=A0=A0=A0 non-profit conference.=A0 They can stay in Korea up to 30
=A0=A0=A0 day for such purpose and for tourism.

=A0 - If you travel to Korea for business purposes, such as
=A0=A0=A0 meeting customers or other business purposes, then a
=A0=A0=A0 visa is needed.

=A0 - This applies only to private U.S. citizens.=A0 Government
=A0=A0=A0 employees and citizens of other countries need to contact
=A0=A0=A0 their local Korean embassy for a determination in their
=A0=A0=A0 case. Ken, in your case, if you are a government employee,
=A0=A0=A0 you will need a visa.

=A0 - Another consideration concerning visa.=A0 People attend
=A0=A0=A0 IETF meetings as individuals, not directly representing
=A0=A0=A0 their company -- and clearly a private individual traveling
=A0=A0=A0 to attend a nonprofit technical meeting clearly does not
=A0=A0=A0 need a visa.

Warning.=A0 I am only relaying what was told to me today by a
responsible embassy official.=A0 I am not attending the Seoul meeting,
but if I was, I would want to have an official statement from an
Korean official regarding the visa request.=A0 One official who can
handle such a request at the visa section in Washington DC is
Mr. Sang Yoo.=A0 I am copying this email to him.=A0 A member of the
meeting committee might want to put a formal query to him, and
email his answer to the list.

For Mr. Yoo, details of the meeting:
59th IETF Meeting, Seoul, South Korea, 29 February - 5 March 2004.
For information about the IETF (Internet Engineering Task Force)
see: http://www.ietf.org/overview.html



=A0=A0=A0=20

Gene Gaines
gene.gaines@gainesgroup.com

On Monday, January 12, 2004, 12:12:27 PM, Ken wrote:

>>I d be interested in answers people get from other consulate/embassy
>>staff both from locations other than Boston and with different
>>phrasings of the question.

> Well, I finally was able to talk to someone at the Washington, DC, embass=
y.

> Their answer?=A0 "We re not sure, but you might need one".

 -- snip --

> --Ken


--=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DEnd of original message text=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


--=20
Gene=20
gene.gaines@gainesgroup.com


Embassy of the Republic of Korea

http://www.koreaembassy.org

=A0

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DEnd of original message text=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

------------D61E10621BB94C3
Content-Type: TEXT/HTML; name="Message.html"
Content-Disposition: attachment; filename="Message.html"
Content-Transfer-Encoding: base64

PFA+SGksPC9QPg0KPFA+TXIuWW9vIHNhaWQgdGhhdCB5b3UgZG9uJ3QgbmVlZCB2aXNhcyBm
b3IgdGhlIGNvbmZlcmVuY2UgYW5kIGNhbiBzdGF5IHVwIHRvIDMwZGF5cyBpbiBLb3JlYS48
L1A+DQo8UD5CdXQgaGUgcG9pbnRlZCBvdXQgb25lIHdyb25nIHRoaW5nJm5ic3A7aW4geW91
ciBlbWFpbC4gVGhhdCBpcyB0aGUgZm9sbG93aW5nLjwvUD4NCjxQPiZuYnNwOzwvUD4NCjxQ
PllvdSB3cm90ZTs8L1A+DQo8UD4mbmJzcDsgLSBUaGlzIGFwcGxpZXMgb25seSB0byBwcml2
YXRlIFUuUy4gY2l0aXplbnMuJm5ic3A7IEdvdmVybm1lbnQ8QlI+Jm5ic3A7Jm5ic3A7Jm5i
c3A7IGVtcGxveWVlcyBhbmQgY2l0aXplbnMgb2Ygb3RoZXIgY291bnRyaWVzIG5lZWQgdG8g
Y29udGFjdDxCUj4mbmJzcDsmbmJzcDsmbmJzcDsgdGhlaXIgbG9jYWwgS29yZWFuIGVtYmFz
c3kgZm9yIGEgZGV0ZXJtaW5hdGlvbiBpbiB0aGVpcjxCUj4mbmJzcDsmbmJzcDsmbmJzcDsg
Y2FzZS4gS2VuLCBpbiB5b3VyIGNhc2UsIGlmIHlvdSBhcmUgYSBnb3Zlcm5tZW50IGVtcGxv
eWVlLDxCUj4mbmJzcDsmbmJzcDsmbmJzcDsgeW91IHdpbGwgbmVlZCBhIHZpc2EuPC9QPg0K
PFA+Jm5ic3A7PC9QPg0KPFA+QnV0IHRoZSByaWdodCZuYnNwO2luZm9ybWF0aW9uIGlzIHRo
YXQgaXQgYXBwbGllcyB0byBhbGwgVS5TLmNpdGl6ZW5zLiA8L1A+DQo8UD5BbmQgZXZlbiB0
aG91Z2ggd2hlbiBnb3Zlcm5tZW50IGVtcGxveWVlcyBnbyB0byBLb3JlYW4gZm9yIG9mZmlj
aWFsIHB1cnBvc2UsIHRoZW4gdGhleSBuZWVkIG9mZmljaWFsIHZpc2FzLiBCdXQgd2hlbiB0
aGV5IGdvIHRvIEtvcmVhIGp1c3QgZm9yIHRvdXIgb3Igbm9uLXByb2ZpdCBjb25mZXJlbmNl
LCB0aGV5IGRvbid0IG5lZWQgdmlzYXMuPC9QPg0KPFA+SWYgeW91IGhhdmUgbW9yZSBxdWVz
dGlvbnMsIHRoZW4gcGxlYXNlIHdyaXRlIHVzIGJhY2suPC9QPg0KPFA+Jm5ic3A7PC9QPg0K
PFA+VGhhbmsgeW91LjwvUD4NCjxQPjxCUj48QlI+PEJSPiZuYnNwOzwvUD4NCjxCTE9DS1FV
T1RFIGRpcj1sdHIgc3R5bGU9IlBBRERJTkctUklHSFQ6IDBweDsgUEFERElORy1MRUZUOiA1
cHg7IE1BUkdJTi1MRUZUOiA1cHg7IEJPUkRFUi1MRUZUOiAjMDAwMDAwIDJweCBzb2xpZDsg
TUFSR0lOLVJJR0hUOiAwcHgiPg0KPERJVj4tLS0tLS0gWyC/+Lq7ILjevLzB9iBdIC0tLS0t
LSA8L0RJVj4NCjxESVY+urizvSC757b3IDogIkdlbmUgR2FpbmVzIiA8R0VORS5HQUlORVNA
R0FJTkVTR1JPVVAuQ09NPjwvRElWPg0KPERJVj6zr8KlIDogMjAwNC0wMS0xMyAwNjoxNTow
NyA8L0RJVj4NCjxESVY+waa48SA6IFZpc2EgZm9yIElFVEYgbWVldGluZyBmb3IgTVIuIFlP
TyA8L0RJVj5TYW5nIFlvbyw8QlI+PEJSPlRoYW5rIHlvdSBmb3Igc3BlYWtpbmcgd2l0aCBt
ZSB0b2RheS48QlI+PEJSPkkgZGVzY3JpYmVkIHdoYXQgeW91IHRvbGQgbWUgaW4gdGhlIGVt
YWlsIGJlbG93LCBzZW50IHRvIHRoZTxCUj5lbWFpbCBsaXN0IHVzZWQgYnkgdGhlIHBlb3Bs
ZSB0aGF0IHdpbGwgYmUgYXR0ZW5kaW5nIHRoZTxCUj5JbnRlcm5ldCBlbmdpbmVlcmluZyBt
ZWV0aW5nIGluIFNlb3VsIDI5IEZlYnJ1YXJ5IC0gNSBNYXJjaCAyMDA0LjxCUj48QlI+R2Vu
ZSBHYWluZXM8QlI+UHJlc2lkZW50PEJSPkdhaW5lcyBHcm91cDxCUj5TdGVybGluZywgVmly
Z2luaWE8QlI+Z2VuZS5nYWluZXNAZ2FpbmVzZ3JvdXAuY29tPEJSPjcwMy00MzMtMjA4MTxC
Uj48QlI+PEJSPjxCUj5DT1BZIE9GIE1FU1NBR0UgU0VOVCBCRUxPVzxCUj48QlI+RnJvbTom
bmJzcDsgR2VuZSBHYWluZXMgJmx0O2dlbmUuZ2FpbmVzQGdhaW5lc2dyb3VwLmNvbSZndDs8
QlI+VG86Jm5ic3A7Jm5ic3A7Jm5ic3A7IEtlbiBIb3Juc3RlaW48QlI+Q0M6Jm5ic3A7Jm5i
c3A7Jm5ic3A7IGlldGZAaWV0Zi5vcmc8QlI+RGF0ZTombmJzcDsgTW9uZGF5LCBKYW51YXJ5
IDEyLCAyMDA0LCAzOjE4OjIxIFBNPEJSPlN1YmplY3Q6IFZpc2EgZm9yIFNvdXRoIEtvcmVh
PEJSPj09PT09PT09PT09PT09PT09T3JpZ2luYWwgbWVzc2FnZSB0ZXh0PT09PT09PT09PT09
PT09PEJSPjxCUj5LZW4sPEJSPjxCUj5BcyBpdCBoYXBwZW5zLCBJIGF0dGVuZGVkIGEgZGlu
bmVyIFNhdHVyZGF5IHRoYXQgd2FzIGFkZHJlc3NlZDxCUj5ieSBBbWJhc3NhZG9yIEhhbiwg
dGhlIEtvcmVhbiBBbWJhc3NhZG9yIHRvIHRoZSBVLlMuPEJSPjxCUj5UYWtpbmcgdXAgdGhl
IEtvcmVhbiB2aXNhIGlzc3VlIHRvZGF5LCBJIHNwb2tlIHdpdGggYW4gb2ZmaWNpYWw8QlI+
aW4gdGhlIFdhc2hpbmd0b24gREMgdmlzYSBzZWN0aW9uLjxCUj48QlI+SSBiZWxpZXZlIEkg
Y2FuIHN0YXRlIHRoZSB2aXNhIHJlZ3VsYXRpb24gYXMgaXQgYXBwbGllcyB0byBVLlMuPEJS
PmNpdGl6ZW5zLjxCUj48QlI+Jm5ic3A7IC0gSW5kaXZpZHVhbHMgdHJhdmVsaW5nIHRvIEtv
cmVhbiB0byBhdHRlbmQgdGhlIElFVEYgbWVldGluZzxCUj4mbmJzcDsmbmJzcDsmbmJzcDsg
ZG8gbm90IG5lZWQgYSB2aXNhLCBhcyB0aGV5IGFyZSB0cmF2ZWxpbmcgdG8gYXR0ZW5kIGE8
QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IG5vbi1wcm9maXQgY29uZmVyZW5jZS4mbmJzcDsgVGhl
eSBjYW4gc3RheSBpbiBLb3JlYSB1cCB0byAzMDxCUj4mbmJzcDsmbmJzcDsmbmJzcDsgZGF5
IGZvciBzdWNoIHB1cnBvc2UgYW5kIGZvciB0b3VyaXNtLjxCUj48QlI+Jm5ic3A7IC0gSWYg
eW91IHRyYXZlbCB0byBLb3JlYSBmb3IgYnVzaW5lc3MgcHVycG9zZXMsIHN1Y2ggYXM8QlI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7IG1lZXRpbmcgY3VzdG9tZXJzIG9yIG90aGVyIGJ1c2luZXNz
IHB1cnBvc2VzLCB0aGVuIGE8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IHZpc2EgaXMgbmVlZGVk
LjxCUj48QlI+Jm5ic3A7IC0gVGhpcyBhcHBsaWVzIG9ubHkgdG8gcHJpdmF0ZSBVLlMuIGNp
dGl6ZW5zLiZuYnNwOyBHb3Zlcm5tZW50PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyBlbXBsb3ll
ZXMgYW5kIGNpdGl6ZW5zIG9mIG90aGVyIGNvdW50cmllcyBuZWVkIHRvIGNvbnRhY3Q8QlI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7IHRoZWlyIGxvY2FsIEtvcmVhbiBlbWJhc3N5IGZvciBhIGRl
dGVybWluYXRpb24gaW4gdGhlaXI8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IGNhc2UuIEtlbiwg
aW4geW91ciBjYXNlLCBpZiB5b3UgYXJlIGEgZ292ZXJubWVudCBlbXBsb3llZSw8QlI+Jm5i
c3A7Jm5ic3A7Jm5ic3A7IHlvdSB3aWxsIG5lZWQgYSB2aXNhLjxCUj48QlI+Jm5ic3A7IC0g
QW5vdGhlciBjb25zaWRlcmF0aW9uIGNvbmNlcm5pbmcgdmlzYS4mbmJzcDsgUGVvcGxlIGF0
dGVuZDxCUj4mbmJzcDsmbmJzcDsmbmJzcDsgSUVURiBtZWV0aW5ncyBhcyBpbmRpdmlkdWFs
cywgbm90IGRpcmVjdGx5IHJlcHJlc2VudGluZzxCUj4mbmJzcDsmbmJzcDsmbmJzcDsgdGhl
aXIgY29tcGFueSAtLSBhbmQgY2xlYXJseSBhIHByaXZhdGUgaW5kaXZpZHVhbCB0cmF2ZWxp
bmc8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IHRvIGF0dGVuZCBhIG5vbnByb2ZpdCB0ZWNobmlj
YWwgbWVldGluZyBjbGVhcmx5IGRvZXMgbm90PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyBuZWVk
IGEgdmlzYS48QlI+PEJSPldhcm5pbmcuJm5ic3A7IEkgYW0gb25seSByZWxheWluZyB3aGF0
IHdhcyB0b2xkIHRvIG1lIHRvZGF5IGJ5IGE8QlI+cmVzcG9uc2libGUgZW1iYXNzeSBvZmZp
Y2lhbC4mbmJzcDsgSSBhbSBub3QgYXR0ZW5kaW5nIHRoZSBTZW91bCBtZWV0aW5nLDxCUj5i
dXQgaWYgSSB3YXMsIEkgd291bGQgd2FudCB0byBoYXZlIGFuIG9mZmljaWFsIHN0YXRlbWVu
dCBmcm9tIGFuPEJSPktvcmVhbiBvZmZpY2lhbCByZWdhcmRpbmcgdGhlIHZpc2EgcmVxdWVz
dC4mbmJzcDsgT25lIG9mZmljaWFsIHdobyBjYW48QlI+aGFuZGxlIHN1Y2ggYSByZXF1ZXN0
IGF0IHRoZSB2aXNhIHNlY3Rpb24gaW4gV2FzaGluZ3RvbiBEQyBpczxCUj5Nci4gU2FuZyBZ
b28uJm5ic3A7IEkgYW0gY29weWluZyB0aGlzIGVtYWlsIHRvIGhpbS4mbmJzcDsgQSBtZW1i
ZXIgb2YgdGhlPEJSPm1lZXRpbmcgY29tbWl0dGVlIG1pZ2h0IHdhbnQgdG8gcHV0IGEgZm9y
bWFsIHF1ZXJ5IHRvIGhpbSwgYW5kPEJSPmVtYWlsIGhpcyBhbnN3ZXIgdG8gdGhlIGxpc3Qu
PEJSPjxCUj5Gb3IgTXIuIFlvbywgZGV0YWlscyBvZiB0aGUgbWVldGluZzo8QlI+NTl0aCBJ
RVRGIE1lZXRpbmcsIFNlb3VsLCBTb3V0aCBLb3JlYSwgMjkgRmVicnVhcnkgLSA1IE1hcmNo
IDIwMDQuPEJSPkZvciBpbmZvcm1hdGlvbiBhYm91dCB0aGUgSUVURiAoSW50ZXJuZXQgRW5n
aW5lZXJpbmcgVGFzayBGb3JjZSk8QlI+c2VlOiBodHRwOi8vd3d3LmlldGYub3JnL292ZXJ2
aWV3Lmh0bWw8QlI+PEJSPjxCUj48QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxCUj48QlI+R2Vu
ZSBHYWluZXM8QlI+Z2VuZS5nYWluZXNAZ2FpbmVzZ3JvdXAuY29tPEJSPjxCUj5PbiBNb25k
YXksIEphbnVhcnkgMTIsIDIwMDQsIDEyOjEyOjI3IFBNLCBLZW4gd3JvdGU6PEJSPjxCUj4m
Z3Q7Jmd0O0kgZCBiZSBpbnRlcmVzdGVkIGluIGFuc3dlcnMgcGVvcGxlIGdldCBmcm9tIG90
aGVyIGNvbnN1bGF0ZS9lbWJhc3N5PEJSPiZndDsmZ3Q7c3RhZmYgYm90aCBmcm9tIGxvY2F0
aW9ucyBvdGhlciB0aGFuIEJvc3RvbiBhbmQgd2l0aCBkaWZmZXJlbnQ8QlI+Jmd0OyZndDtw
aHJhc2luZ3Mgb2YgdGhlIHF1ZXN0aW9uLjxCUj48QlI+Jmd0OyBXZWxsLCBJIGZpbmFsbHkg
d2FzIGFibGUgdG8gdGFsayB0byBzb21lb25lIGF0IHRoZSBXYXNoaW5ndG9uLCBEQywgZW1i
YXNzeS48QlI+PEJSPiZndDsgVGhlaXIgYW5zd2VyPyZuYnNwOyAiV2UgcmUgbm90IHN1cmUs
IGJ1dCB5b3UgbWlnaHQgbmVlZCBvbmUiLjxCUj48QlI+Jmd0OyBJIGJhc2ljYWxseSB0b29r
IHRoZSBzYW1lIHRhY3RpYyB0aGF0IFNhbSB0b29rOyBJIGRlc2NyaWJlZCB0aGUgSUVURiBh
czxCUj4mZ3Q7IGEgcHJvZmVzc2lvbmFsIG9yZ2FuaXphdGlvbiwgYW5kIGV4cGxhaW5lZCBJ
IHdhcyBhdHRlbmRpbmcgYSBtZWV0aW5nPEJSPiZndDsgb2YgdGhpcyBvcmdhbml6YXRpb24u
Jm5ic3A7IEF0IGZpcnN0IGhlIHNhaWQgdGhhdCBhIHZpc2Egd2FzIG5vdCByZXF1aXJlZCw8
QlI+Jmd0OyBiZWNhdXNlIHRoaXMgY291bnRzIGFzIGEgInZpc2l0IiwgYnV0IHRoZW4gaGUg
c2FpZCBoZSB3YXNuIHQgc3VyZSwgYW5kPEJSPiZndDsgbWF5YmUgSSB3b3VsZCBuZWVkIGEg
dmlzYS48QlI+PEJSPiZndDsgSSB0aGVuIHN0YXJ0ZWQgYXNraW5nIGEgZmV3IG1vcmUgcXVl
c3Rpb25zLiZuYnNwOyBJIGFza2VkIHdoYXQgZXhhY3RseTxCUj4mZ3Q7ICJidXNpbmVzcyIg
dHJhdmVsIHdhcyBkZWZpbmVkIGFzLCBhbmQgYWZ0ZXIgZ29pbmcgYXJvdW5kIGEgZmV3IHRp
bWVzPEJSPiZndDsgYWJvdXQgaXQsIGhlIGJhc2ljYWxseSBzZXR0bGVkIG9uIHRoZSBkZWZp
bml0aW9uIHRoYXQgaWYgeW91IHdlcmU8QlI+Jmd0OyB0cmF2ZWxsaW5nIHRvIEtvcmVhIHRv
IGEgbWVldGluZyBmb3IgYSAiYnVzaW5lc3MgcHVycG9zZSIsIHRoZW4geW91PEJSPiZndDsg
bmVlZCBhIHZpc2EuPEJSPjxCUj4mZ3Q7IFRoZSB3aG9sZSB0aGluZyB3YXMgYXMgY2xlYXIg
YXMgbXVkLCBhbmQgaGUgY2xlYXJseSB3YXNuIHQgdGhhdCBmYW1pbGlhcjxCUj4mZ3Q7IHdp
dGggdGhlIHJlZ3VsYXRpb25zLiZuYnNwOyBJIG1pZ2h0IHRyeSBjYWxsaW5nIGEgZmV3IG1v
cmUgY29uc3VsYXRlcyB0bzxCUj4mZ3Q7IHNlZSBpZiBJIGNhbiBmaW5kIHNvbWVvbmUgbW9y
ZSBrbm93bGVkZ2VhYmxlLjxCUj48QlI+Jmd0OyBCVFcsIGhhcyBhbnlvbmUgYmVlbiBhYmxl
IHRvIGNvbnRhY3QgdGhlIGhvc3Qgd2ViIHNpdGU/Jm5ic3A7IChUaGUgb25lPEJSPiZndDsg
bGlua2VkIG9mZiBvZiB0aGUgSUVURiBTZW91bCBtZWV0aW5nIHdlYiBwYWdlKTxCUj48QlI+
Jmd0OyBodHRwOi8vd3d3LnR0YS5vci5rci9pZXRmNTkvaW5kZXguaHRtPEJSPjxCUj4mZ3Q7
IEkgdmUgYmVlbiB0cnlpbmcgZm9yIGEgZmV3IGRheXMgbm93IGFuZCBubyBnby4mbmJzcDsg
SXQgZG9lc24gdCBzZWVtIGxpa2U8QlI+Jmd0OyBhIGxvY2FsIG5ldHdvcmsgcHJvYmxlbSBm
cm9tIHdoZXJlIEkgbSBzaXR0aW5nLCBidXQgc29tZXRpbWVzIGl0IHMgaGFyZDxCUj4mZ3Q7
IHRvIGJlIHN1cmUuPEJSPjxCUj4mZ3Q7IC0tS2VuPEJSPjxCUj48QlI+LS0gPEJSPjxCUj49
PT09PT09PT09PT09PUVuZCBvZiBvcmlnaW5hbCBtZXNzYWdlIHRleHQ9PT09PT09PT09PTxC
Uj48QlI+PEJSPi0tIDxCUj5HZW5lIDxCUj5nZW5lLmdhaW5lc0BnYWluZXNncm91cC5jb208
QlI+PEJSPjxCUj48L0JMT0NLUVVPVEU+PGJyPjxwPjxzdHlsZT5QIHttYXJnaW4tdG9wOjJw
eDttYXJnaW4tYm90dG9tOjJweDt9PC9zdHlsZT4NCjxQPkVtYmFzc3kgb2YgdGhlIFJlcHVi
bGljIG9mIEtvcmVhPC9QPg0KPFA+PEEgaHJlZj0iaHR0cDovL3d3dy5rb3JlYWVtYmFzc3ku
b3JnLyI+aHR0cDovL3d3dy5rb3JlYWVtYmFzc3kub3JnPC9BPjwvUD4NCjxQPiZuYnNwOzwv
UD48YnI+PHA+PGltZyBzcmM9aHR0cDovL21haWwubW9mYXQuZ28ua3I6ODAva28vanNwL21h
aWwvcmVhZENoZWNrLmpzcD9yZWFkPWNvbnN1bGFyX3VzYS4xMDc0MDMwOTQwMzIxIGJvcmRl
cj0wIGhlaWdodD0xIHdpZHRoPTE+DQoNCg0K

------------D61E10621BB94C3--




From owner-ietf@ietf.org  Wed Jan 14 08:25:31 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16439
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 08:25:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Agkpu-0005dz-JF
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 08:13:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgWWK-0008Cu-Gq
	for ietf@asgard.ietf.org; Tue, 13 Jan 2004 16:56:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17180
	for <ietf@ietf.org>; Tue, 13 Jan 2004 16:56:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgWWI-0001PG-00
	for ietf@ietf.org; Tue, 13 Jan 2004 16:56:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgWUM-0001LC-00
	for ietf@ietf.org; Tue, 13 Jan 2004 16:54:19 -0500
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgWSa-0001HW-00
	for ietf@ietf.org; Tue, 13 Jan 2004 16:52:28 -0500
Received: from dsl092-109-027.nyc2.dsl.speakeasy.net ([66.92.109.27] helo=thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:RC4-SHA:128)  (Exim 3.35 #1 (Debian))
	id 1AgWQo-0004hT-00; Tue, 13 Jan 2004 16:50:38 -0500
Received: from tytso by thunk.org with local (Exim 4.30)
	id 1AgWQn-0007mI-LL; Tue, 13 Jan 2004 16:50:37 -0500
Date: Tue, 13 Jan 2004 16:50:37 -0500
From: "Theodore Ts'o" <tytso@mit.edu>
To: Nathaniel Borenstein <nsb@guppylake.com>
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>,
        Fred Baker <fred@cisco.com>, ietf@ietf.org
Subject: Re: dire outlook on internet and NAT
Message-ID: <20040113215037.GB29820@thunk.org>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C836@server2003.arneill-py.sacramento.ca.us> <971D0CB4-4539-11D8-9AFA-000A9571873E@guppylake.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <971D0CB4-4539-11D8-9AFA-000A9571873E@guppylake.com>
User-Agent: Mutt/1.5.5.1+cvs20040105i
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/>.
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-7.8 required=5.0 tests=AWL,HABEAS_SWE autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Jan 12, 2004 at 02:57:45PM -0500, Nathaniel Borenstein wrote:
> Pardon me if I'm missing something obvious here, but couldn't one just 
> use either XMPP or Simple for presence, associate your "server name" 
> with a Jabber/Simple ID, and automatically have your "server" findable 
> via these general presence protocols?  Why isn't that a reasonable 
> approach to peer to peer in a NAT world?  I would contend that it's 
> even better in a mobile world -- your laptop might change IP address a 
> dozen times per day, but if it keeps reconnecting with your presence 
> server you could base a stable "host" identity on the IM ID to enable 
> peer to peer applications, couldn't you?

XMPP or Simple solve the problem of dynamic IP addresses.  NAT's
however go beyond dynamic IP addresses, as they multiplex multiple
hosts behind a single IP address.  Many of these systems do not have
an easy way to allow users to accept an incoming TCP connection (and
unexpected UDP packets are often harder) to be happed to a particular
host behind a NAT box.  Doing so often requires administrative access
to the NAT, and if you're lucky there is a manual web interface you
can use to configure such access.  If you're not so lucky there is a
text config file you have to edit.  In either case, this makes peer to
peer much more difficult for the average user behind a NAT.  Some
might say that it is impossible.

One could imagine developing a protocols for discovering NAT boxes,
and making requests that they listen on certain ports and when they
receive an incoming TCP connection, that it be remapped to a
particular address behind the NAT box.  This is not too bad for one
NAT box, but if you start having multiple NAT boxes between the
communicating partners, it starts becoming bad in a hurry.  

Of course, this isn't necessary so as long as one of the parties is
not behind a NAT, but the moment both the sides are behind one or more
levels of NAT, trying to do a peer-to-peer TCP connection between the
two entities is non-trivial.

						- Ted






From owner-ietf@ietf.org  Wed Jan 14 08:36:15 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16862
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 08:36:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Agl7L-0006cA-0B
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 08:31:31 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Agl7F-0006Z0-Ne
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 08:31:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16611
	for <ietf@ietf.org>; Wed, 14 Jan 2004 08:31:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agl7E-0002V3-00
	for ietf@ietf.org; Wed, 14 Jan 2004 08:31:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agl5B-0002M5-00
	for ietf@ietf.org; Wed, 14 Jan 2004 08:29:18 -0500
Received: from smtp.inet.fi ([192.89.123.192])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agl3K-0002Di-00
	for ietf@ietf.org; Wed, 14 Jan 2004 08:27:22 -0500
Received: from EMCL (gprs-internet.mobile.sonera.net [212.213.204.99])
	by smtp.inet.fi (Postfix) with SMTP
	id 6084E617C; Wed, 14 Jan 2004 15:26:51 +0200 (EET)
From: "=?UTF-8?Q?John?=" <john.loughney@kolumbus.fi>
To: <H.Soliman@flarion.com>,
        <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>, <ietf@ietf.org>
Subject: =?UTF-8?Q?RE:_dire_outlook_on_internet_and_NAT?=
Date: Wed, 14 Jan 2004 15:25:19 +0000
Message-Id: <1074093919046@john.loughney_kolumbus.fi>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: EMCL v4.10
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hesham,=20

VOIP with SIP seems like a good app for enterprises.  I think I=
Pv6 helps.

John

 > Admittedly I can't remember where I read it, but I've come a=
cross
 > a suggestion that enterprise networks adopting IPv6 is likel=
y to
 > happen before ISPs provide it in any big way, as enterprise
 > networks have more to gain from the technology (well, possib=
ly,
 > assuming they can be convinced that "proper" address space i=
s
 > better than NAT).=20

=3D> I'm a bit confused as to why enterprises would be interest=
ed
in v6. There are even prorietry solutions that allow for VPN
access behind a NAT. And enterprises are not known for encourag=
ing=20
p2p apps for their employees. So this business case doesn't
seem like a winner to me.=20

My hope has been that p2p apps will one day be "needed now" and=
=20
force people to turn v6 on in their networks.

   Once enterprises have it, they will then ask
 > for it from their ISP.=20

=3D> Sure, but it's not clear that they'd be early adopters.=20
Autoconfig of addresses will not be enough, if they ever use it=
.=20

Hesham





From owner-ietf@ietf.org  Wed Jan 14 08:44:53 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17415
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 08:44:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AglH0-0007K6-MJ
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 08:41:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AglEp-00076u-IH
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 08:39:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16980
	for <ietf@ietf.org>; Wed, 14 Jan 2004 08:39:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AglEo-0002tS-00
	for ietf@ietf.org; Wed, 14 Jan 2004 08:39:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AglCZ-0002mV-00
	for ietf@ietf.org; Wed, 14 Jan 2004 08:36:56 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AglCA-0002iU-00
	for IETF@ietf.org; Wed, 14 Jan 2004 08:36:30 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AglC9-000LOm-00; Wed, 14 Jan 2004 08:36:29 -0500
Date: Wed, 14 Jan 2004 08:36:28 -0500
From: John C Klensin <john-ietf@jck.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>, IETF@ietf.org
Subject: RE: Death of the Internet - details at 11
Message-ID: <172249221.1074069388@scan.jck.com>
In-Reply-To: <200401132308.i0DN8sno038176@calcite.rhyolite.com>
References: <116512686.1074013651@scan.jck.com>
 <200401132308.i0DN8sno038176@calcite.rhyolite.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Tuesday, 13 January, 2004 16:08 -0700 Vernon Schryver 
<vjs@calcite.rhyolite.com> wrote:

>> From: John C Klensin <john-ietf@jck.com>
>
>> ...
>> (1) As others have pointed out, the knowledge/skill level of
>> a  typical ISP seems to be on a rapid downslope with no end
>> in  sight. ...
>
>> ...
>> 	* The difference between those "business rates" and
>> 	whatever you are paying are mostly determined by a "what
>> 	they can get away with" mentality -- we know what the
>> 	marginal operational costs are.   If those prices stay
>> 	high, it is either because there is no alternate
>> 	provider, or because there is (illegal) price-fixing
>> 	going on, or because no one sees a business opportunity
>> 	by operating a business service at a lower margin.
>
> The second segment seems to ignore the implications of the
> first segment. The marginal cost difference between "business"
> and "residental" is zilch only if you have the same people
> running things and interacting with customers.  Front line
> tech-support droids that are dumber than the Windows boxes of
> residential customer cost a lot less than humans. If your
> front line support people know have a clue about the LSRR IP
> option, then either your rates are higher than $30/month or
> you have customers like us who do most of our own support (and
> cost our employers or ourselves a lot more than $30/month for
> that support).

A little hyperbole aside, this is, of course, correct.   My 
observation was based on the observation --however anecdotal-- 
that many or most vendors of "business" DSL or cable modem 
services, at least in the US, provide almost exactly the same 
level of service/ support as they do for their "residential" 
customers.  The only things one gets are more than one address 
(and relatively static ones if the ISP's normal practice is 
dynamic) and unblocking of a number of functions/activities. 
That level of support does not include "a clue about the LSRR IP 
option"; it often barely includes understanding that, if one can 
log into a CPE router and ping the local network but not the 
ISP's first-hop router, it might suggest a problem with the link 
or that remote router.  The level of support you are 
hypothesizing --either from the vendor or so that internal 
experts can get to non-droids quickly-- seems to come, with some 
ISPs, with yet another increment in price to a "business 
premium" or "managed" service; with others, one has to give up 
DSL or Cable and go to, e.g., fractional T1s.

While, despite some other comments, I still consider this 
nonsense -- the marginal prices for the "business service" are 
all out of proportion to marginal costs and my biases are such 
that I don't like the idea of incurring even small extra costs 
to cripple one service to force people to another, more 
expensive one-- they certainly constitute sound business 
practices for the ISPs, at least for as long as they can get 
away with it.

> There are some surviving ISPs that were started and still run
> that way least in geographical areas I know about.  Their
> prices seem to be higher than the organizations in that race
> to maximum stupidity.
>
> It is not a coincidence that they have very few internal spam
> problems. They are never blacklisted, not even by the second
> tier spam blacklists, even when they rent straight modem
> dial-up ports.  (Third tier DNS blacklists are kooky 32-bit
> random number generators.)

None of this, including the higher prices, are surprising. 
Racing to maximum stupidity and, e.g., eliminating all but the 
pretense of technical support, does lower costs and may improve 
volume.

> I know people who have done that sort of thing with DSL and
> 802.11. However, I fear that idea is generally killed for now
> by the fact that IP bandwidth pricing is set by those outfits
> racing for ultimate stupidity.  They see IP bandwidth as a
> loss-leader.

yes.  But then several of them turn around and incur extra costs 
(however small) to filter outgoing and incoming protocols 
sufficiently to force users into "pure client" mode, prevent 
their mail servers from being used as outbound relays unless the 
addresses are theirs or one buys an extra-cost "service", and so 
on.  Those things are not the mark of stupidity, they are the 
mark of a deliberate and considered business practice, however 
ugly we might find it.

>> 	                   Or maybe we would rather whine than
>> 	do something, perhaps because what we have been fed is "good
>> 	enough".
>
> Until people like the individual complaining here that his
> cable-modem is listed as a dynamic address are willing to pay
> for the costs of real IP service, including the costs of doing
> more against your spamming customers than asking blacklists to
> list your own addresses, there's not much hope.

I think we agree... and that was part of my point.

> We could accept the fact that people who are not willing pay
> more than $10-30/month are not interested in the Internet and
> stop listen to their whining.  Detroit laughs as people who
> expect to get Mercedes for Chevrolet prices.  Why can't we
> laugh at people who expect to get real IP service for
> $10-30/month, or least stop taking their demands literally?
>
> If cable-modem IP is good enough for you, then you're not
> interested in multihoming or even running your own VoIP
> system.  You might be happy to have your phones connected to
> the email and web browser demark/appliance maintained by your
> telco/cableco, but you're not really interested in the
> Internet.  You lack the interest to be allowed to run your own
> servers for anything.

Exactly.  Sadly, but...

     john




From owner-ietf@ietf.org  Wed Jan 14 11:41:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26505
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 11:41:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgnzO-0006Zw-Az
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 11:35:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Agnyj-0006Vq-RX
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 11:34:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26296
	for <ietf@ietf.org>; Wed, 14 Jan 2004 11:34:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agnyi-0003Dq-00
	for ietf@ietf.org; Wed, 14 Jan 2004 11:34:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agnxn-0003CQ-00
	for ietf@ietf.org; Wed, 14 Jan 2004 11:33:52 -0500
Received: from [203.199.83.28] (helo=rediffmail.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1Agnx7-0003B1-00
	for IETF@ietf.org; Wed, 14 Jan 2004 11:33:10 -0500
Received: (qmail 17666 invoked by uid 510); 14 Jan 2004 16:31:24 -0000
Date: 14 Jan 2004 16:31:24 -0000
Message-ID: <20040114163124.17665.qmail@webmail18.rediffmail.com>
Received: from unknown (61.11.88.146) by rediffmail.com via HTTP; 14 jan 2004 16:31:24 -0000
MIME-Version: 1.0
From: "thiru moorthi k" <thiru_moorthi@rediffmail.com>
Reply-To: "thiru moorthi k" <thiru_moorthi@rediffmail.com>
To: IETF@ietf.org
Subject: Un subscribe
Content-type: multipart/alternative;
	boundary="Next_1074097884---0-203.199.83.28-17662"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.7 required=5.0 tests=AWL,HTML_70_80,
	HTML_IMAGE_ONLY_02,HTML_MESSAGE,MSGID_FROM_MTA_HEADER autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

 This is a multipart mime message


--Next_1074097884---0-203.199.83.28-17662
Content-type: text/html;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

<P>=0AUn subscribe=0A</P>=0A<br><br>=0A<A target=3D"_blank" HREF=3D"http://=
clients.rediff.com/signature/track_sig.asp"><IMG SRC=3D"http://ads.rediff.c=
om/RealMedia/ads/adstream_nx.cgi/www.rediffmail.com/inbox.htm@Bottom" BORDE=
R=3D0 VSPACE=3D0 HSPACE=3D0 HEIGHT=3D74 WIDTH=3D496></a>=0A
--Next_1074097884---0-203.199.83.28-17662
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Un subscribe
--Next_1074097884---0-203.199.83.28-17662--




From owner-ietf@ietf.org  Wed Jan 14 11:41:43 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26527
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 11:41:43 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ago1K-0006fX-Bb
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 11:37:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Agnzg-0006a2-6f
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 11:35:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26323
	for <ietf@ietf.org>; Wed, 14 Jan 2004 11:35:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agnzc-0003F4-00
	for ietf@ietf.org; Wed, 14 Jan 2004 11:35:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agnyf-0003DU-00
	for ietf@ietf.org; Wed, 14 Jan 2004 11:34:46 -0500
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agnxl-0003B4-00
	for ietf@ietf.org; Wed, 14 Jan 2004 11:33:49 -0500
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 MAA01206;
	Wed, 14 Jan 2004 12:36:48 -0500
Date: Wed, 14 Jan 2004 11:28:36 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: <dean@vista.av8.net>
To: Mike S <ietf@flatsurface.com>
cc: <ietf@ietf.org>
Subject: Re: SMTP Minimum Retry Period - Proposal To Modify Mx
In-Reply-To: <6.0.0.22.0.20040112222640.03fc76b0@mjs.alientech.net>
Message-ID: <Pine.LNX.4.33.0401141106100.18879-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 12 Jan 2004, Mike S wrote:

> At 09:58 PM 1/12/2004, Dean Anderson wrote...
> >On Mon, 12 Jan 2004, Mike S wrote:
> >1) privacy - routing via my ISP's outbound SMTP gives them
> >> the right to intercept and read my email, according the ECPA;
> >

> >Err, Just the opposite is more freqently the case.The ECPA
> >specifically prohibits the ISP from exceeding its limited authority.
>
> Cite, please. I've got one:
>
> "(2)(a)(i) It shall not be unlawful under this chapter for an ...
> agent of a provider of wire or electronic communication service, whose
> facilities are used in the transmission of a wire or electronic
> communication, to intercept, disclose, or use that communication in
> the normal course of his employment..."

"Normal course of employment" is the operative phrase. Exceeding
authorization is not part of the normal course of employment.  The section
you quote also goes on to prohibit service monitoring except for random
quality control checks. Reading email in excess of the limited
authorization to block spam isn't a quality control check, either.

Also, the section you quote is the wiretap act, which covers
communications on the wire. The ECPA extends this and provides coverage of
stored and temporarilly stored communications, ie, when they are on a mail
server or in the memory of a router or server.

> >2) control - sending from my own system allows me to control retry
> >> attempts and times, instead of being forced to wait 4 days for my ISP
> >> to bounce an undelivered back to me, assuming they don't just silently
> >> lose it.
> >
> >If your contract allows you to run your own system, then the ISP would not
> >be allowed to prevent you from doing that.  This could be made into an
> >ECPA issue---some people think it is merely and only a contract
> >non-performance issue and said contract excludes liability for failure to
> >perform.  Like the Sherman Anti-Trust Act, the ECPA is a criminal statute
> >with civil actions permitted, and carries its own civil and criminal
> >penalties.
>
> My ISP's support of the MAPS DUL, and the use of the MAPS system by
> others, is a violation of 18 U.S.C. 1030. Email me for details, but
> I've covered this on this list recently.

I missed your statements on this, but I'll look back in the archives.
MAPS has been successfully sued for anti-trust violations in Exactis V
MAPS.  That case was settled after the MAPS defense (First Amendment) was
rejected, and its attorney's chastised. Reportedly, MAPS agreed never to
block Exactis, and agreed to specific monetary damages if it did.  Exactis
continued to do what it was doing, single opt-out advertising.

> >Of course, if your contract does not allow you to run your own system,
> >then you don't have a complaint about blacklists blocking it.
>
> There is nothing to prohibit direct routing of email.

Point taken.  Some mail clients route directly. But they probably
shouldn't do that for other reasons having to do with lack of information
about mail routing.  But, I suppose one can say they are allowed to
anyway.

		--Dean





From owner-ietf@ietf.org  Wed Jan 14 11:58:24 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27815
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 11:58:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgoHm-00007h-AP
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 11:54:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgoH3-0008SI-VJ
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 11:53:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27509
	for <ietf@ietf.org>; Wed, 14 Jan 2004 11:53:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgoH3-0004YM-00
	for ietf@ietf.org; Wed, 14 Jan 2004 11:53:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgoG4-0004VX-00
	for ietf@ietf.org; Wed, 14 Jan 2004 11:52:45 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgoF8-0004P5-00
	for ietf@ietf.org; Wed, 14 Jan 2004 11:51:46 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 14 Jan 2004 08:54:00 +0000
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i0EGp9VQ020986
	for <ietf@ietf.org>; Wed, 14 Jan 2004 08:51:14 -0800 (PST)
Received: from CSCOAMERA19540.cisco.com (dhcp-171-71-214-50.cisco.com [171.71.214.50])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id APG39253;
	Wed, 14 Jan 2004 08:51:08 -0800 (PST)
Message-Id: <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com >
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 14 Jan 2004 08:43:58 -0800
To: ietf@ietf.org
From: Fred Baker <fred@cisco.com>
Subject: Processing of Expired Internet-Drafts
In-Reply-To: <200401141552.KAA24589@ietf.org>
References: <200401141552.KAA24589@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.7 required=5.0 tests=FORGED_MUA_EUDORA,
	INVALID_MSGID autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

The secretariat sent a note to ietf-announce this morning, which I mostly 
consider a step forward - internet drafts will be aged out 185 days after 
their original posting barring certain procedural caveats such as being on 
a list waiting to be published.

I wonder what thoughts people have about this paragraph, though:

At 07:52 AM 1/14/2004, The IETF Secretariat wrote:
>When an Internet-Draft expires, a "tombstone" file will be created that 
>includes the filename and version number of the Internet-Draft that has 
>expired.  The filename of the tombstone file will be the same as that of 
>the expired Internet-Draft with the version number increased by one.  If a 
>revised version of an expired Internet-Draft is submitted for posting, 
>then the revised version will replace the tombstone file and will receive 
>the same version number as that previously assigned to the tombstone 
>file.  Tombstone files will never expire and will always be available for 
>reference unless they are replaced by updated versions of the subject 
>Internet-Drafts.

This affects me in two ways.

First, I maintain Cisco's internet draft and RFC mirrors. My procedure is 
pretty simple. Every night, I run a process which

  - obtains a list of the drafts/rfcs on the IETF server, via FTP
  - creates a list of the drafts/rfcs on my mirror
  - takes a diff between the 'ls' outputs
  - downloads the new files via FTP
  - deletes the ones that are no longer there

This has an interesting side-effect in our present (I suppose I should say 
past) system: since an expired draft gets a tombstone file that lasts for 
six months but does not change the name, the name remains on the IETF 
server. Hence, in *my* mirror, an expired draft is still available until 
the tombstone is removed six months later. For my purposes, that can be a 
nice side-effect, although it is one I'm not stuck on.

If I can have two separate files (a tombstone and a subsequent new file 
version) that have the same name, as described in the recent announcement, 
I am going to have to figure out a trigger that will tell me that I need to 
re-download the file.

Second, every 4 months we post ~700 IDs. Many of these are -00, meaning 
"new name". Every ID that is posted eventually expires, which means that 
according to the above procedure we are going to accumulate empty tombstone 
files at a rate of perhaps 1000-2000 per year ad infinitum.

It seems to me that there is a better approach to the above, at least in 
the context of the above. If the "tombstone" is literally as described, it 
would be far more space/search/etc efficient for us to have the tombstone 
consist of an added text line in a file indicating that the named draft 
expired on a certain date, and keep separate files for the active internet 
drafts. It seems to me that this makes it simpler to maintain a mirror and 
to find temporary documents.

Thoughts? 




From owner-ietf@ietf.org  Wed Jan 14 12:26:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28873
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 12:26:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Agoag-0001fB-40
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 12:14:02 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgoZb-0001cK-Ae
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 12:12:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28481
	for <ietf@ietf.org>; Wed, 14 Jan 2004 12:12:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgoZa-0005ar-00
	for ietf@ietf.org; Wed, 14 Jan 2004 12:12:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgoYb-0005Zj-00
	for ietf@ietf.org; Wed, 14 Jan 2004 12:11:53 -0500
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgoYG-0005YP-00
	for ietf@ietf.org; Wed, 14 Jan 2004 12:11:32 -0500
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 1AgoYF-00048n-00
	for <ietf@ietf.org>; Wed, 14 Jan 2004 17:11:31 +0000
Date: Wed, 14 Jan 2004 17:11:31 +0000
To: ietf@ietf.org
Subject: Re: Processing of Expired Internet-Drafts
Message-ID: <20040114171130.GB25888@fysh.org>
References: <200401141552.KAA24589@ietf.org> <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com >
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com >
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Definitions:

	"draft name" = filename stem, excluding version number (e.g.,
			"draft-iab-dos")
	"version number" = two-digit I-D version number
	"filename" = full filename, composed of draft name, version
		number, and a format suffix (e.g., "draft-iab-dos-00.ps")

(I've seen the term "filename" in this context used variously to refer
to (a) the full filename, (b) what I call the draft name, and (c) the
combination of draft name and version number.)

Fred Baker wrote:
>If I can have two separate files (a tombstone and a subsequent new file 
>version) that have the same name, as described in the recent announcement, 
>I am going to have to figure out a trigger that will tell me that I need to 
>re-download the file.

I, too, dislike the idea of these filenames being ambiguous.  I'd prefer
that the tombstone file is the only file that ever gets that combination
of draft name and version number.  Any subsequent version of the draft
should get a new version number, higher than that used by the tombstone.

>according to the above procedure we are going to accumulate empty tombstone 
>files at a rate of perhaps 1000-2000 per year ad infinitum.

They're not empty.  I see no need for them to remain indefinitely --
six months seems fine to me -- though if we're going to maintain strong
uniqueness of draft names then at least the names need to be recorded
indefinitely.

-zefram



From owner-ietf@ietf.org  Wed Jan 14 12:39:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29394
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 12:39:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Agora-0002z1-Ay
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 12:31:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Agor2-0002vS-I6
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 12:30:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29112
	for <ietf@ietf.org>; Wed, 14 Jan 2004 12:30:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agor1-0006L1-00
	for ietf@ietf.org; Wed, 14 Jan 2004 12:30:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agoq7-0006I9-00
	for ietf@ietf.org; Wed, 14 Jan 2004 12:29:59 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50] helo=smtp.cs.utk.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgopK-0006DY-00
	for ietf@ietf.org; Wed, 14 Jan 2004 12:29:10 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP id 53E88AFEC4
	for <ietf@ietf.org>; Wed, 14 Jan 2004 12:29:07 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 22770-03; Wed, 14 Jan 2004 12:29:06 -0500 (EST)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id E9759AFEBD; Wed, 14 Jan 2004 12:29:05 -0500 (EST)
Date: Wed, 14 Jan 2004 12:29:05 -0500
From: Keith Moore <moore@cs.utk.edu>
To: ietf@ietf.org
Cc: moore@cs.utk.edu
Subject: dubious assumptions about IPv6 (was death of the Internet)
Message-Id: <20040114122905.4b2c7ff5.moore@cs.utk.edu>
X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Since the topic of IPv6 transition seems to have surfaced in this
discussion, I thought I'd send a pointer to my argument as to why a lot
of the common assumptions about IPv6 transitions are dubious.  

I put these things in a web page to avoid needing to re-type the same
arguments over and over, and because I think I express things more
effectively in this form than when trying to finish an email message on
a difficult topic before going to X  (where X is one of
{work,lunch,dinner,bed}).  One downside is that the web page isn't
directly tailored to a specific list discussion - so some of the 
assumptions listed on the web page are apropos to the recent discussion
on this list while others are not.

http://www.cs.utk.edu/~moore/opinions/ipv6/dubious-assumptions.html

Responses should go to my private email address if you want me to see
them - I've disabled my subscription to the ietf list and am currently
only scanning the archives once every few days.  (In general, it's a bad
idea to assume that you know whether someone will receive a reply sent
to the entire list.)




From owner-ietf@ietf.org  Wed Jan 14 12:47:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29839
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 12:47:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Agp2E-0003lQ-6f
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 12:42:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Agp1l-0003iJ-Fh
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 12:42:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29528
	for <ietf@ietf.org>; Wed, 14 Jan 2004 12:41:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agp1k-0006rp-00
	for ietf@ietf.org; Wed, 14 Jan 2004 12:42:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agp0q-0006ml-00
	for ietf@ietf.org; Wed, 14 Jan 2004 12:41:05 -0500
Received: from bulk.resource.org ([192.101.98.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agozu-0006g6-00
	for ietf@ietf.org; Wed, 14 Jan 2004 12:40:06 -0500
Received: from bulk.resource.org (localhost.resource.org [127.0.0.1])
	by bulk.resource.org (8.12.2/8.12.2) with ESMTP id i0EHdB1o029237;
	Wed, 14 Jan 2004 09:39:11 -0800 (PST)
Received: (from carl@localhost)
	by bulk.resource.org (8.12.2/8.12.2/Submit) id i0EHdB5B029236;
	Wed, 14 Jan 2004 09:39:11 -0800 (PST)
From: Carl Malamud <carl@media.org>
Message-Id: <200401141739.i0EHdB5B029236@bulk.resource.org>
Subject: Re: Processing of Expired Internet-Drafts
In-Reply-To: <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com >
To: Fred Baker <fred@cisco.com>
Date: Wed, 14 Jan 2004 09:39:11 -0800 (PST)
CC: ietf@ietf.org
Organization: Memory Palace Press
X-Winch: Warn 9.5i
X-Mailer: ELM [version 2.4ME+ PL94 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Fred -

> 
> If I can have two separate files (a tombstone and a subsequent new file 
> version) that have the same name, as described in the recent announcement, 
> I am going to have to figure out a trigger that will tell me that I need to 
> re-download the file.

Incrementing the number also screws up a common operation for authors: is
the internet-draft that I'm citing the current one?  With the new algorithm,
a search for a +1 version will yield a hit and I have to go look in that
file.

> the context of the above. If the "tombstone" is literally as described, it 
> would be far more space/search/etc efficient for us to have the tombstone 
> consist of an added text line in a file indicating that the named draft 
> expired on a certain date, and keep separate files for the active internet 
> drafts. It seems to me that this makes it simpler to maintain a mirror and 
> to find temporary documents.
> 

A tombstone jail containing that information would be preferable in my
view to mixing them all together.  

Regards,

Carl



From owner-ietf@ietf.org  Wed Jan 14 13:04:03 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00697
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 13:04:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgpHi-00055q-4h
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 12:58:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgpH3-00053S-ES
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 12:57:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00533
	for <ietf@ietf.org>; Wed, 14 Jan 2004 12:57:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgpH2-00000D-00
	for ietf@ietf.org; Wed, 14 Jan 2004 12:57:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgpGB-0007nU-00
	for ietf@ietf.org; Wed, 14 Jan 2004 12:56:56 -0500
Received: from one.elistx.com ([209.116.252.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgpFx-0007m6-00
	for ietf@ietf.org; Wed, 14 Jan 2004 12:56:41 -0500
Received: from localhost (one.elistx.com [209.116.252.130])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HRH00J6CR6XG2@eListX.com>
 for ietf@ietf.org; Wed, 14 Jan 2004 12:56:58 -0500 (EST)
Date: Wed, 14 Jan 2004 12:56:25 -0500 (EST)
From: James M Galvin <galvin+ietf@elistx.com>
Subject: Re: Processing of Expired Internet-Drafts
In-reply-to: <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com>
X-X-Sender: galvin@three.elistx.com
To: Fred Baker <fred@cisco.com>
Cc: ietf@ietf.org
Message-id: <Pine.BSF.4.43.0401141244120.96041-100000@three.elistx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


On Wed, 14 Jan 2004, Fred Baker wrote:

    I wonder what thoughts people have about this paragraph, though:

    At 07:52 AM 1/14/2004, The IETF Secretariat wrote:

    >When an Internet-Draft expires, a "tombstone" file will be created
    >that includes the filename and version number of the Internet-Draft
    >that has expired.  The filename of the tombstone file will be the
    >same as that of the expired Internet-Draft with the version number
    >increased by one.  If a revised version of an expired
    >Internet-Draft is submitted for posting, then the revised version
    >will replace the tombstone file and will receive the same version
    >number as that previously assigned to the tombstone file.

This surprises me.  I would expect them to increment the version number
for the revised version.  At a minimum it is logically the right thing
to do because the information in the file is changing, i.e., it is not
the same file.

I am particularly surpised because it was more than 10 years that
incrementing the version number for the tombstone file started.  The
Secretariat didn't do that originally.

This was back before mirroring of the I-D directory was as popular as it
is today.  I was creating a mirror at my then employer and really wanted
to track the tombstone file, for consistency.  It is the same problem
you're having now although perhaps the content this time is more
valuable.

I had several conversations with Steve Coya about it back then and
pushed very hard to get that version number incremented for the
tombstone file.  It would be silly (if not shameful) to take a step
backwards now.

Jim




From owner-ietf@ietf.org  Wed Jan 14 13:52:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02851
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 13:52:29 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgpyH-00046M-TS
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 13:42:29 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Agpxi-00045O-T3
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 13:41:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02373
	for <ietf@ietf.org>; Wed, 14 Jan 2004 13:41:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agpxh-0001u5-00
	for ietf@ietf.org; Wed, 14 Jan 2004 13:41:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agpwm-0001sA-00
	for ietf@ietf.org; Wed, 14 Jan 2004 13:40:57 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agpw0-0001ok-00
	for ietf@ietf.org; Wed, 14 Jan 2004 13:40:08 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 14 Jan 2004 10:41:45 +0000
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0EIdUGT014702;
	Wed, 14 Jan 2004 10:39:36 -0800 (PST)
Received: from CSCOAMERA19540.cisco.com (dhcp-171-71-214-50.cisco.com [171.71.214.50])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id APG52408;
	Wed, 14 Jan 2004 10:39:29 -0800 (PST)
Message-Id: <6.0.1.1.2.20040114103520.045671a8@mira-sjc5-b.cisco.com >
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 14 Jan 2004 10:39:08 -0800
To: James M Galvin <galvin+ietf@elistx.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: Processing of Expired Internet-Drafts
Cc: ietf@ietf.org
In-Reply-To: <Pine.BSF.4.43.0401141244120.96041-100000@three.elistx.com>
References: <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com>
 <Pine.BSF.4.43.0401141244120.96041-100000@three.elistx.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.7 required=5.0 tests=FORGED_MUA_EUDORA,
	INVALID_MSGID autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 09:56 AM 1/14/2004, James M Galvin wrote:
>I had several conversations with Steve Coya about it back then and
>pushed very hard to get that version number incremented for the
>tombstone file.  It would be silly (if not shameful) to take a step
>backwards now.

I'm not sure it is backwards. If it is deemed to solve a problem (not 
obvious to me), it creates another.

I'd be happier bumping the number any time the file is changed, so that the 
tombstone supercedes the removed file and a subsequent posting supercedes 
the tombstone.

I am very concerned about the accumulation of tombstones forever, though. 
If we don't want to accumulate draft versions forever, what makes 
tombstones different? I would far rather age them out after some interval, 
such as six months. 




From owner-ietf@ietf.org  Wed Jan 14 14:06:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03555
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 14:06:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgqGf-00050q-Dw
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 14:01:29 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgqG2-0004zi-MJ
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 14:00:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03397
	for <ietf@ietf.org>; Wed, 14 Jan 2004 14:00:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgqG1-0002lt-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:00:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgqF2-0002lK-00
	for ietf@ietf.org; Wed, 14 Jan 2004 13:59:49 -0500
Received: from one.elistx.com ([209.116.252.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgqEO-0002l0-00
	for ietf@ietf.org; Wed, 14 Jan 2004 13:59:08 -0500
Received: from localhost (one.elistx.com [209.116.252.130])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HRH00125U30EI@eListX.com>
 for ietf@ietf.org; Wed, 14 Jan 2004 13:59:25 -0500 (EST)
Date: Wed, 14 Jan 2004 13:58:51 -0500 (EST)
From: James M Galvin <galvin+ietf@elistx.com>
Subject: Re: Processing of Expired Internet-Drafts
In-reply-to: <6.0.1.1.2.20040114103520.045671a8@mira-sjc5-b.cisco.com>
X-X-Sender: galvin@three.elistx.com
To: Fred Baker <fred@cisco.com>
Cc: ietf@ietf.org
Message-id: <Pine.BSF.4.43.0401141351290.96041-100000@three.elistx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


On Wed, 14 Jan 2004, Fred Baker wrote:

    I am very concerned about the accumulation of tombstones forever,
    though.  If we don't want to accumulate draft versions forever, what
    makes tombstones different? I would far rather age them out after
    some interval, such as six months.

I don't feel strong about this issue either way.

I will observe that from the point of view of the Secretariat, if they
don't keep I-Ds around forever they probably should not keep tombstones
around forever either, which really only means I don't see the problem
they are solving by keeping them.

Keeping them around forever is a role filled nicely by the archiving
mirrors (although this presupposes incrementing the version number if a
revision is submitted).

Certainly, a tombstone should be removed if a revision is submitted,
which would be a change to the new rules as documented.

Jim




From owner-ietf@ietf.org  Wed Jan 14 14:33:17 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04862
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 14:33:17 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Agqer-0006IS-N2
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 14:26:29 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgqeI-0006HE-B2
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 14:25:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04402
	for <ietf@ietf.org>; Wed, 14 Jan 2004 14:25:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgqeH-0003iO-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:25:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgqdN-0003g4-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:24:57 -0500
Received: from e5.ny.us.ibm.com ([32.97.182.105])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgqcT-0003cG-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:24:01 -0500
Received: from northrelay04.pok.ibm.com (northrelay04.pok.ibm.com [9.56.224.206])
	by e5.ny.us.ibm.com (8.12.10/8.12.2) with ESMTP id i0EJNU9n752092
	for <ietf@ietf.org>; Wed, 14 Jan 2004 14:23:30 -0500
Received: from rotala.raleigh.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay04.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i0EJNUqK123664
	for <ietf@ietf.org>; Wed, 14 Jan 2004 14:23:30 -0500
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by rotala.raleigh.ibm.com (8.12.8/8.12.5) with ESMTP id i0EJKs8L032262
	for <ietf@ietf.org>; Wed, 14 Jan 2004 14:20:54 -0500
Received: from rotala.raleigh.ibm.com (narten@localhost)
	by rotala.raleigh.ibm.com (8.12.8/8.12.8/Submit) with ESMTP id i0EJKsbQ032258
	for <ietf@ietf.org>; Wed, 14 Jan 2004 14:20:54 -0500
Message-Id: <200401141920.i0EJKsbQ032258@rotala.raleigh.ibm.com>
To: ietf@ietf.org
Subject: Re: Processing of Expired Internet-Drafts 
In-Reply-To: Message from fred@cisco.com
   of "Wed, 14 Jan 2004 08:43:58 PST." <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com > 
Date: Wed, 14 Jan 2004 14:20:54 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

One reminder for those who may not know...

For those mirroring IDs and/or RFCs, both the Secretariat and RFC
Editor support rsync. If you are still using ftp for the mirroring,
rsync has a lot to offer.

http://www.ietf.org/rsync-help.html
 
http://www.rfc-editor.org/rsync-help.html

Thomas



From owner-ietf@ietf.org  Wed Jan 14 14:37:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05392
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 14:37:16 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Agqkf-0006Qs-IZ
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 14:32:29 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Agqj8-0006PH-0U
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 14:30:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04692
	for <ietf@ietf.org>; Wed, 14 Jan 2004 14:30:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agqj6-0003vi-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:30:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agqi9-0003rn-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:29:54 -0500
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgqhV-0003oH-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:29:14 -0500
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id i0EJP5a18160
	for <ietf@ietf.org>; Wed, 14 Jan 2004 11:25:05 -0800
Date: Wed, 14 Jan 2004 11:25:05 -0800 (PST)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
Subject: Re: Processing of Expired Internet-Drafts
In-Reply-To: <6.0.1.1.2.20040114103520.045671a8@mira-sjc5-b.cisco.com >
Message-ID: <Pine.LNX.4.33.0401141109210.14383-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk



On Wed, 14 Jan 2004, Fred Baker wrote:

> I'd be happier bumping the number any time the file is changed, so that the
> tombstone supercedes the removed file and a subsequent posting supercedes
> the tombstone.

Absolutely. Principals of version control are broken otherwise.

In the preferences space, I'd rather see the file extension change as well
so it would be possible to determine w/o parsing the file content that it
is a tombstone.

> I am very concerned about the accumulation of tombstones forever, though.
> If we don't want to accumulate draft versions forever, what makes
> tombstones different? I would far rather age them out after some interval,
> such as six months.

As was noted, a mechanism must be maintained to track names and such a
mechanism SHOULD be visible to the ietf community. Doesn't have to be the
drafts directory.

If they are aged, it should be based on natural IETF cycles and not the
current arbitrary 6 months ... for example, a draft associated with a
working group should have the tombstone remain until some time after the
WG closes ... 1 year? That should include drafts submitted to but not
owned by a WG. Individual drafts should retain the tombstone for
substantially longer than 6 months. Perhaps 2 years.

Regarding the clarification about expiration occuring the moment the
processing reopens after a meeting... a better approach would be 15 days
AFTER ALL drafts submitted while processing was suspended and processed.

I wonder how many WG drafts are resubmitted these days to reset the clock
rather than because there were substantive changes? Needless churn. It
seems quite reasonable that a WG would have reference materials written
early in the cycle for discussion which don't change but are still
important 2 years later as the WG is perhaps finishing the official RFC
track documents. Perhaps even later as RFCs progress thru the standards
track. WG chairs should have a mechanism which allows them to extend the
expiration of WG drafts w/o churn of version, etc.

Dave Morris




From owner-ietf@ietf.org  Wed Jan 14 14:45:38 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06054
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 14:45:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgqsV-0007RU-Gl
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 14:40:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Agqpw-00074E-TV
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 14:37:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05464
	for <ietf@ietf.org>; Wed, 14 Jan 2004 14:37:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agqpv-0004SW-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:37:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agqp6-0004PI-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:37:05 -0500
Received: from rufus.isode.com ([62.3.217.251])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgqoD-0004GF-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:36:09 -0500
Received: from isode.com (shiny.isode.com [62.3.217.250]) by rufus.isode.com
          via TCP (with SMTP (internal)) with ESMTPA;
          Wed, 14 Jan 2004 19:35:34 +0000
Message-ID: <40059A03.40609@isode.com>
Date: Wed, 14 Jan 2004 19:35:31 +0000
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
CC: ietf@ietf.org
Subject: Re: Processing of Expired Internet-Drafts
References: <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com> <Pine.BSF.4.43.0401141244120.96041-100000@three.elistx.com> <6.0.1.1.2.20040114103520.045671a8@mira-sjc5-b.cisco.com >
In-Reply-To: <6.0.1.1.2.20040114103520.045671a8@mira-sjc5-b.cisco.com >
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Fred Baker wrote:

> At 09:56 AM 1/14/2004, James M Galvin wrote:
>
>> I had several conversations with Steve Coya about it back then and
>> pushed very hard to get that version number incremented for the
>> tombstone file.  It would be silly (if not shameful) to take a step
>> backwards now.
>
>
> I'm not sure it is backwards. If it is deemed to solve a problem (not 
> obvious to me), it creates another.
>
> I'd be happier bumping the number any time the file is changed, so 
> that the tombstone supercedes the removed file and a subsequent 
> posting supercedes the tombstone.
>
> I am very concerned about the accumulation of tombstones forever, 
> though. If we don't want to accumulate draft versions forever, what 
> makes tombstones different? I would far rather age them out after some 
> interval, such as six months. 

IMHO, if tombstones get removed after 6 months, the search interface on 
ietf.org should still be able to report that the document with a given 
name existed but expired.
I've been several times in a position when I had to search for a draft 
that has expired more than 6 months ago.

Alexey
__________________________________________
Isode Limited, http://www.isode.com

IETF standard related pages:
http://www.melnikov.ca/mel/devel/Links.html

Personal Home Page: http://www.melnikov.ca
__________________________________________





From owner-ietf@ietf.org  Wed Jan 14 14:53:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06584
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 14:53:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgqyF-0007rt-Mb
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 14:46:31 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Agqwh-0007he-5b
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 14:44:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06022
	for <ietf@ietf.org>; Wed, 14 Jan 2004 14:44:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agqwf-0004vG-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:44:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agqvj-0004tH-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:43:56 -0500
Received: from biscayne-one-station.mit.edu ([18.7.7.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agquq-0004rn-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:43:01 -0500
Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])
	by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id i0EJh0cX000170
	for <ietf@ietf.org>; Wed, 14 Jan 2004 14:43:00 -0500 (EST)
Received: from mit.edu ([18.101.0.226])
	(authenticated bits=56)
        (User authenticated as raeburn@ATHENA.MIT.EDU)
	by melbourne-city-street.mit.edu (8.12.4/8.12.4) with ESMTP id i0EJgvRw021021
	(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT)
	for <ietf@ietf.org>; Wed, 14 Jan 2004 14:42:57 -0500 (EST)
Date: Wed, 14 Jan 2004 14:42:56 -0500
Subject: Re: Processing of Expired Internet-Drafts
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
From: Ken Raeburn <raeburn@MIT.EDU>
To: ietf@ietf.org
In-Reply-To: <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com >
Message-Id: <D9FD86D8-46C9-11D8-A84D-000A95909EE2@mit.edu>
X-Mailer: Apple Mail (2.553)
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wednesday, Jan 14, 2004, at 11:43 US/Eastern, Fred Baker wrote:
> At 07:52 AM 1/14/2004, The IETF Secretariat wrote:
>> When an Internet-Draft expires, a "tombstone" file will be created 
>> that includes the filename and version number of the Internet-Draft 
>> that has expired.  The filename of the tombstone file will be the 
>> same as that of the expired Internet-Draft with the version number 
>> increased by one.  If a revised version of an expired Internet-Draft 
>> is submitted for posting, then the revised version will replace the 
>> tombstone file and will receive the same version number as that 
>> previously assigned to the tombstone file.  Tombstone files will 
>> never expire and will always be available for reference unless they 
>> are replaced by updated versions of the subject Internet-Drafts.

Does this also apply in the "published as RFC" and "replaced by 
draft-foo" cases, not just expiration without publication?

>
> If I can have two separate files (a tombstone and a subsequent new 
> file version) that have the same name, as described in the recent 
> announcement, I am going to have to figure out a trigger that will 
> tell me that I need to re-download the file.
>

Kind of like how 1id-*.txt changes almost daily?  If you can't use the 
timestamp as a trigger, the file size would probably be fairly 
reliable.  For my personal mirror, I use rsync, and I've noticed no 
problems.

 From what I've been told, the handling of numbers described above has 
been the procedure for a while.  I asked about it a year or so ago and 
was told that the number of the tombstone file should be reused for the 
next submission "reviving" the draft.  So, you may have been missing 
updates for a while.

> It seems to me that there is a better approach to the above, at least 
> in the context of the above. If the "tombstone" is literally as 
> described, it would be far more space/search/etc efficient for us to 
> have the tombstone consist of an added text line in a file indicating 
> that the named draft expired on a certain date, and keep separate 
> files for the active internet drafts. It seems to me that this makes 
> it simpler to maintain a mirror and to find temporary documents.

Keeping the tombstone files around forever does sound messy.  I like 
your suggestion of using a file to collect the data, at least for the 
long term.  We'd want the author contact (and disposition, if not just 
for expiration) info around for at least a while, though maybe not 
permanently.  So maybe still keeping tombstone files for six months or 
so would be wise.  And it's the established way of finding out what's 
happening with recent enough drafts.

This file with the "used" names might grow to be pretty large after a 
lot of years, but we're probably not talking about more than a megabyte 
or two a year, are we, even if we keep all the author info around?  By 
the time it's big enough to be a problem, we'll probably have better 
solutions....

Ken




From owner-ietf@ietf.org  Wed Jan 14 14:55:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06724
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 14:55:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Agr3W-0008FN-4S
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 14:51:58 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Agr2S-0008Bo-CI
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 14:50:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06465
	for <ietf@ietf.org>; Wed, 14 Jan 2004 14:50:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agr2R-0005Ff-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:50:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agr1T-0005BN-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:49:52 -0500
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agr0W-00056p-00
	for ietf@ietf.org; Wed, 14 Jan 2004 14:48:52 -0500
Received: from dsl092-109-027.nyc2.dsl.speakeasy.net ([66.92.109.27] helo=thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:RC4-SHA:128)  (Exim 3.35 #1 (Debian))
	id 1Agr0S-0002zC-00; Wed, 14 Jan 2004 14:48:48 -0500
Received: from tytso by thunk.org with local (Exim 4.30)
	id 1Agr0P-0000d0-CN; Wed, 14 Jan 2004 14:48:45 -0500
Date: Wed, 14 Jan 2004 14:48:45 -0500
From: "Theodore Ts'o" <tytso@mit.edu>
To: Fred Baker <fred@cisco.com>
Cc: ietf@ietf.org
Subject: Re: Processing of Expired Internet-Drafts
Message-ID: <20040114194845.GA2387@thunk.org>
References: <200401141552.KAA24589@ietf.org> <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com >
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com>
User-Agent: Mutt/1.5.5.1+cvs20040105i
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/>.
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-7.8 required=5.0 tests=AWL,HABEAS_SWE autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Jan 14, 2004 at 08:43:58AM -0800, Fred Baker wrote:
> 
> It seems to me that there is a better approach to the above, at least in 
> the context of the above. If the "tombstone" is literally as described, it 
> would be far more space/search/etc efficient for us to have the tombstone 
> consist of an added text line in a file indicating that the named draft 
> expired on a certain date, and keep separate files for the active internet 
> drafts. It seems to me that this makes it simpler to maintain a mirror and 
> to find temporary documents.

I would prefer this as well.

						- Ted



From owner-ietf@ietf.org  Wed Jan 14 16:47:03 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15634
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 16:47:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgskW-0007zY-Dm
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 16:40:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgpOp-0002XD-WC
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 13:05:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00791
	for <ietf@ietf.org>; Wed, 14 Jan 2004 13:05:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgpOo-0000E8-00
	for ietf@ietf.org; Wed, 14 Jan 2004 13:05:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgpNr-0000B6-00
	for ietf@ietf.org; Wed, 14 Jan 2004 13:04:51 -0500
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgpN0-00007u-00
	for ietf@ietf.org; Wed, 14 Jan 2004 13:03:58 -0500
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 3CB74CDD3D; Wed, 14 Jan 2004 13:03:27 -0500 (EST)
To: ietf@ietf.org
Subject: draft newtrk charter posted
Message-Id: <20040114180327.3CB74CDD3D@newdev.harvard.edu>
Date: Wed, 14 Jan 2004 13:03:27 -0500 (EST)
From: sob@harvard.edu (Scott Bradner)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


fyi - I've posted a draft charter for a newtrk WG to the newtrk list

archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html
subscribe to list:  mail to majordomo@lists.uoregon.edu
			"subscribe newtrk" in body
list address: newtrk@lists.uoregon.edu

Scott





From owner-ietf@ietf.org  Wed Jan 14 16:47:04 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15652
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 16:47:04 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgskW-0007ze-IB
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 16:40:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgrLx-0004Zw-NP
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 15:11:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08056
	for <ietf@ietf.org>; Wed, 14 Jan 2004 15:10:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgrLw-0006Th-00
	for ietf@ietf.org; Wed, 14 Jan 2004 15:11:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgrLB-0006S1-00
	for ietf@ietf.org; Wed, 14 Jan 2004 15:10:14 -0500
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgrKX-0006OO-00
	for ietf@ietf.org; Wed, 14 Jan 2004 15:09:34 -0500
Received: from slb-av-02.boeing.com ([129.172.13.7])
	by slb-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id MAA18279;
	Wed, 14 Jan 2004 12:09:17 -0800 (PST)
Received: from slb-hub-01.boeing.com (localhost [127.0.0.1])
	by slb-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id MAA15574;
	Wed, 14 Jan 2004 12:09:27 -0800 (PST)
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 i0EK7MQ18674;
	Wed, 14 Jan 2004 12:07:22 -0800 (PST)
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, 14 Jan 2004 12:06:42 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Processing of Expired Internet-Drafts
Date: Wed, 14 Jan 2004 12:06:42 -0800
Message-ID: <5B58696DB20B9140AD20E0685C573A6402992F09@xch-nw-09.nw.nos.boeing.com>
Thread-Topic: Processing of Expired Internet-Drafts
Thread-Index: AcPa2Mc/ftj5O2CWT5K44FZHOjfcAgAACy5g
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: "Theodore Ts'o" <tytso@mit.edu>, "Fred Baker" <fred@cisco.com>
Cc: <ietf@ietf.org>
X-OriginalArrivalTime: 14 Jan 2004 20:06:42.0739 (UTC) FILETIME=[EDB5F830:01C3DAD9]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

I also concur with this suggestion.=20

This modification would also assist us to find expired drafts containing =
good ideas but that were either introduced before the community became =
interested in the topic or else were not renewed due to procedural =
issues (i.e., not due to their lack of technical merit). I am sure that =
others in our community are interested in many drafts which we are =
unable to read due to more pressing local work-related pressures and =
then are disappointed that we can't find the draft once the work =
pressures permit us time to read the previously deferred drafts. There =
are many reasons why some drafts fail to receive resonance and this =
approach would increase the probability of technically viable ideas not =
timing out and becoming lost.

-----Original Message-----
From: Theodore Ts'o [mailto:tytso@mit.edu]
Sent: Wednesday, January 14, 2004 11:49 AM
To: Fred Baker
Cc: ietf@ietf.org
Subject: Re: Processing of Expired Internet-Drafts


On Wed, Jan 14, 2004 at 08:43:58AM -0800, Fred Baker wrote:
>=20
> It seems to me that there is a better approach to the above, at least =
in=20
> the context of the above. If the "tombstone" is literally as =
described, it=20
> would be far more space/search/etc efficient for us to have the =
tombstone=20
> consist of an added text line in a file indicating that the named =
draft=20
> expired on a certain date, and keep separate files for the active =
internet=20
> drafts. It seems to me that this makes it simpler to maintain a mirror =
and=20
> to find temporary documents.

I would prefer this as well.

						- Ted






From owner-ietf@ietf.org  Wed Jan 14 16:54:11 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16216
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 16:54:11 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgsuL-0000fi-V2
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 16:50:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Agsrk-0000CV-IU
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 16:47:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15681
	for <ietf@ietf.org>; Wed, 14 Jan 2004 16:47:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agsrj-0004Gj-00
	for ietf@ietf.org; Wed, 14 Jan 2004 16:47:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Agsqn-0004EL-00
	for ietf@ietf.org; Wed, 14 Jan 2004 16:46:57 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgsqH-0004Db-00
	for ietf@ietf.org; Wed, 14 Jan 2004 16:46:25 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0ELk2kw026522;
	Wed, 14 Jan 2004 22:46:02 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com >
References: <200401141552.KAA24589@ietf.org> <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com >
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <12D3726D-46DB-11D8-815B-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Processing of Expired Internet-Drafts
Date: Wed, 14 Jan 2004 22:46:13 +0100
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 14-jan-04, at 17:43, Fred Baker wrote:

> It seems to me that there is a better approach to the above, at least 
> in the context of the above. If the "tombstone" is literally as 
> described, it would be far more space/search/etc efficient for us to 
> have the tombstone consist of an added text line in a file indicating 
> that the named draft expired on a certain date, and keep separate 
> files for the active internet drafts. It seems to me that this makes 
> it simpler to maintain a mirror and to find temporary documents.

> Thoughts?

This is probably orthogonal to mirroring issues, but it sometimes 
drives me mad when I have a draft filename but I can't find the draft 
itself and/or its status. Two things could help in this area:

- for all drafts, make it possible to determine the latest version
- for inactive drafts, supply some reference to the author(s)

A good and simple way to do this would be to create a file that matches 
the draft filename without the version number (would this be that 
tombstone thingy you guys keep talking about?) and say something like 
"version 34 was submitted 2003-04-05" or "version 00 was deleted 
1970-01-01" and copy the author's address section of the most recent 
version. Authors can then supply a link to the intended permanent 
resting place of the draft, if any, in this section.

If keeping all those files around is problematic, copying the author's 
address section into the I-D ACTION email message would also help a lot 
as the announcements mailinglist is well-archived.




From owner-ietf@ietf.org  Wed Jan 14 17:19:59 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17481
	for <ietf-web-archive@odin.ietf.org>; Wed, 14 Jan 2004 17:19:59 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AgtDY-0002Lu-Ln
	for ietf-list@asgard.ietf.org; Wed, 14 Jan 2004 17:10:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AgtC3-0002Ef-WE
	for ietf@asgard.ietf.org; Wed, 14 Jan 2004 17:08:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17096
	for <ietf@ietf.org>; Wed, 14 Jan 2004 17:08:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgtC2-0005XW-00
	for ietf@ietf.org; Wed, 14 Jan 2004 17:08:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgtB5-0005X3-00
	for ietf@ietf.org; Wed, 14 Jan 2004 17:07:56 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgtAH-0005Vp-00
	for ietf@ietf.org; Wed, 14 Jan 2004 17:07:05 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
  by sj-iport-5.cisco.com with ESMTP; 14 Jan 2004 14:06:42 -0800
Received: from cisco.com (sjc-vpn4-8.cisco.com [10.21.80.8])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with SMTP id i0EM6WjQ024069
	for <ietf@ietf.org>; Wed, 14 Jan 2004 14:06:32 -0800 (PST)
Received: by cisco.com (sSMTP sendmail emulation); Wed, 14 Jan 2004 17:06:25 -0500
Date: Wed, 14 Jan 2004 17:06:25 -0500
From: Scott W Brim <swb@employees.org>
To: ietf@ietf.org
Subject: Re: Processing of Expired Internet-Drafts
Message-ID: <20040114220625.GD2064@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <swb@employees.org>, ietf@ietf.org
References: <200401141552.KAA24589@ietf.org> <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com> <12D3726D-46DB-11D8-815B-000A95CD987A@muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <12D3726D-46DB-11D8-815B-000A95CD987A@muada.com>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Jan 14, 2004 10:46:13PM +0100, Iljitsch van Beijnum allegedly wrote:
> A good and simple way to do this would be to create a file that matches 
> the draft filename without the version number 

I use a script that does: wget -k -nd -nH -r -np --glob=on -nc
--passive-ftp ftp://www.ietf.org/internet-drafts/$1\*




From owner-ietf@ietf.org  Thu Jan 15 06:07:50 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27265
	for <ietf-web-archive@odin.ietf.org>; Thu, 15 Jan 2004 06:07:50 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ah58o-0000Tk-Qu
	for ietf-list@asgard.ietf.org; Thu, 15 Jan 2004 05:54:22 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ah57w-0000RJ-8B
	for ietf@asgard.ietf.org; Thu, 15 Jan 2004 05:53:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26604
	for <ietf@ietf.org>; Thu, 15 Jan 2004 05:53:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah57t-0005Hj-00
	for ietf@ietf.org; Thu, 15 Jan 2004 05:53:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah56x-0005F8-00
	for ietf@ietf.org; Thu, 15 Jan 2004 05:52:27 -0500
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah56V-0005DJ-00
	for ietf@ietf.org; Thu, 15 Jan 2004 05:51:59 -0500
Received: from pigeon.ecs.soton.ac.uk (pigeon [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id i0FApjOr020178;
	Thu, 15 Jan 2004 10:51:45 GMT
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id KAA20301;
	Thu, 15 Jan 2004 10:51:32 GMT
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i0FApdb19733;
	Thu, 15 Jan 2004 10:51:39 GMT
Date: Thu, 15 Jan 2004 10:51:39 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: Fred Baker <fred@cisco.com>, ietf@ietf.org
Subject: Re: Processing of Expired Internet-Drafts
Message-ID: <20040115105139.GA19591@login.ecs.soton.ac.uk>
References: <200401141552.KAA24589@ietf.org> <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com> <12D3726D-46DB-11D8-815B-000A95CD987A@muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <12D3726D-46DB-11D8-815B-000A95CD987A@muada.com>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

www.watersprings.org is helpful, if you know the draft name.

On Wed, Jan 14, 2004 at 10:46:13PM +0100, Iljitsch van Beijnum wrote:
> On 14-jan-04, at 17:43, Fred Baker wrote:
> 
> >It seems to me that there is a better approach to the above, at least 
> >in the context of the above. If the "tombstone" is literally as 
> >described, it would be far more space/search/etc efficient for us to 
> >have the tombstone consist of an added text line in a file indicating 
> >that the named draft expired on a certain date, and keep separate 
> >files for the active internet drafts. It seems to me that this makes 
> >it simpler to maintain a mirror and to find temporary documents.
> 
> >Thoughts?
> 
> This is probably orthogonal to mirroring issues, but it sometimes 
> drives me mad when I have a draft filename but I can't find the draft 
> itself and/or its status. Two things could help in this area:
> 
> - for all drafts, make it possible to determine the latest version
> - for inactive drafts, supply some reference to the author(s)
> 
> A good and simple way to do this would be to create a file that matches 
> the draft filename without the version number (would this be that 
> tombstone thingy you guys keep talking about?) and say something like 
> "version 34 was submitted 2003-04-05" or "version 00 was deleted 
> 1970-01-01" and copy the author's address section of the most recent 
> version. Authors can then supply a link to the intended permanent 
> resting place of the draft, if any, in this section.
> 
> If keeping all those files around is problematic, copying the author's 
> address section into the I-D ACTION email message would also help a lot 
> as the announcements mailinglist is well-archived.
> 



From owner-ietf@ietf.org  Thu Jan 15 07:05:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00062
	for <ietf-web-archive@odin.ietf.org>; Thu, 15 Jan 2004 07:05:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ah68k-0003DV-9g
	for ietf-list@asgard.ietf.org; Thu, 15 Jan 2004 06:58:22 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ah671-00039U-Lh
	for ietf@asgard.ietf.org; Thu, 15 Jan 2004 06:56:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29541
	for <ietf@ietf.org>; Thu, 15 Jan 2004 06:56:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah66y-0001TI-00
	for ietf@ietf.org; Thu, 15 Jan 2004 06:56:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah65l-0001Fg-00
	for ietf@ietf.org; Thu, 15 Jan 2004 06:55:18 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah64F-0000zD-00
	for ietf@ietf.org; Thu, 15 Jan 2004 06:53:43 -0500
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i0FBrbAh025304;
	Thu, 15 Jan 2004 12:53:37 +0100
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <ZJBSQGD8>; Thu, 15 Jan 2004 12:55:10 +0100
Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D03F52C77@Esealnt877.al.sw.ericsson.se>
From: "Yuri Ismailov (KI/EAB)" <yuri.ismailov@ericsson.com>
To: "'Keith Moore'" <moore@cs.utk.edu>, ietf@ietf.org
Subject: RE: dubious assumptions about IPv6 (was death of the Internet)
Date: Thu, 15 Jan 2004 12:48:21 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I share pretty much the views expressed on the page.
Small addition to that would be the fact that current "transition" proposals are killing the possibility of transition as such. IPv6 is strongly dependent on IPv4 through various "ipv4 compatible" addresses, which are essentially private IPv6 addresses, i.e. not globally routable. BTW, not the only private v6 addresses in this sense. This basically means that it will be nearly impossible or at least extremely hard to wash out IPv4 from the implementation. Personally I think that removing IPv4 can not be justified.
Instead of introducing two networks internetworked in a proper way, there are two networks tightly coupled to each other. Besides all, such approach nearly exclude the design of yet another network, which can be naturally internetworked with existing networks. Are there many believers that IPv6 is the last one and forever?
The power of layering was heavily underestimated if not ignored. Isn't it clear enough that we would be nowhere if bridging of link layers would take over internetworking of networks. Is this imaginable situation? 
The ambitions driving the new network design certainly deserve respect because it is natural to improve things but hardly the way it is being done.


-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org]On Behalf Of Keith
Moore
Sent: den 14 januari 2004 18:29
To: ietf@ietf.org
Cc: moore@cs.utk.edu
Subject: dubious assumptions about IPv6 (was death of the Internet)


Since the topic of IPv6 transition seems to have surfaced in this
discussion, I thought I'd send a pointer to my argument as to why a lot
of the common assumptions about IPv6 transitions are dubious.  

I put these things in a web page to avoid needing to re-type the same
arguments over and over, and because I think I express things more
effectively in this form than when trying to finish an email message on
a difficult topic before going to X  (where X is one of
{work,lunch,dinner,bed}).  One downside is that the web page isn't
directly tailored to a specific list discussion - so some of the 
assumptions listed on the web page are apropos to the recent discussion
on this list while others are not.

http://www.cs.utk.edu/~moore/opinions/ipv6/dubious-assumptions.html

Responses should go to my private email address if you want me to see
them - I've disabled my subscription to the ietf list and am currently
only scanning the archives once every few days.  (In general, it's a bad
idea to assume that you know whether someone will receive a reply sent
to the entire list.)




From owner-ietf@ietf.org  Thu Jan 15 09:15:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06553
	for <ietf-web-archive@odin.ietf.org>; Thu, 15 Jan 2004 09:15:29 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ah87d-0008SB-BP
	for ietf-list@asgard.ietf.org; Thu, 15 Jan 2004 09:05:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ah87C-0008Og-Lz
	for ietf@asgard.ietf.org; Thu, 15 Jan 2004 09:04:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06100
	for <ietf@ietf.org>; Thu, 15 Jan 2004 09:04:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah87B-0002HI-00
	for ietf@ietf.org; Thu, 15 Jan 2004 09:04:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah86I-0002CO-00
	for ietf@ietf.org; Thu, 15 Jan 2004 09:03:59 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah85f-00026Z-00
	for ietf@ietf.org; Thu, 15 Jan 2004 09:03:20 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0FE2okw039527;
	Thu, 15 Jan 2004 15:02:53 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <4E85E49D1F0CBF4F96EA08E335750D7D03F52C77@Esealnt877.al.sw.ericsson.se>
References: <4E85E49D1F0CBF4F96EA08E335750D7D03F52C77@Esealnt877.al.sw.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <87F8530D-4763-11D8-815B-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Keith Moore'" <moore@cs.utk.edu>, IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: dubious assumptions about IPv6 (was death of the Internet)
Date: Thu, 15 Jan 2004 15:03:01 +0100
To: "Yuri Ismailov (KI/EAB)" <yuri.ismailov@ericsson.com>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 15-jan-04, at 12:48, Yuri Ismailov (KI/EAB) wrote:

> I share pretty much the views expressed on the page.

I don't share all of them (9 billion people in 2050, 3.7 billion usable 
IPv4 addresses, show me some math that makes this work) but where on 
this page is there a point being made? It seems more like a fairly 
random collection of statements.

> Small addition to that would be the fact that current "transition" 
> proposals are killing the possibility of transition as such. IPv6 is 
> strongly dependent on IPv4 through various "ipv4 compatible" 
> addresses, which are essentially private IPv6 addresses, i.e. not 
> globally routable.

??? Which kind of IPv4-related addresses would a host with native IPv6 
connectivity and IPv6-enabled applications need?

> BTW, not the only private v6 addresses in this sense. This basically 
> means that it will be nearly impossible or at least extremely hard to 
> wash out IPv4 from the implementation. Personally I think that 
> removing IPv4 can not be justified.

Removing IPv4 from the code would be a peculiar idea to say the least. 
But running IPv6-only works for the most part. I tried this on the most 
recent version of MacOS and it's very easy to disable IPv4 for all 
interfaces except loopback. If you manually configure a nameserver 
that's reachable over IPv6 and use IPv6-capable applications, no 
problems whatsoever. People do give me weird looks when I say that I 
want to test running IPv6-only, though.

> Instead of introducing two networks internetworked in a proper way, 
> there are two networks tightly coupled to each other. Besides all, 
> such approach nearly exclude the design of yet another network, which 
> can be naturally internetworked with existing networks. Are there many 
> believers that IPv6 is the last one and forever?

Forever is a very long time. IPv6 is far from perfect, but none of the 
issues are such that replacing the protocol because of them makes 
sense. If we're going to see something new it will probably be a 
niche-only thing for a very long time. But since a simple lack of 
address space won't be an issue in IPv6 (of course this leaves the 
complex lack of address space) it is almost certain that it will be 
possible to translate back and forth between the new protocol and IPv6 
in a way that's compatible with existing IPv6 implementations, so 
deployment won't be an issue.

> The power of layering was heavily underestimated if not ignored. Isn't 
> it clear enough that we would be nowhere if bridging of link layers 
> would take over internetworking of networks.

Talking about power, where are you going to find the power to run those 
16 million+ entry CAMs at 10 Gbps+ without a network layer?




From owner-ietf@ietf.org  Thu Jan 15 10:47:20 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12233
	for <ietf-web-archive@odin.ietf.org>; Thu, 15 Jan 2004 10:47:20 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ah9Zc-000212-OI
	for ietf-list@asgard.ietf.org; Thu, 15 Jan 2004 10:38:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ah9Yu-0001yh-6b
	for ietf@asgard.ietf.org; Thu, 15 Jan 2004 10:37:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11804
	for <ietf@ietf.org>; Thu, 15 Jan 2004 10:37:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah9Yt-0007l9-00
	for ietf@ietf.org; Thu, 15 Jan 2004 10:37:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah9Xx-0007ja-00
	for ietf@ietf.org; Thu, 15 Jan 2004 10:36:38 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah9Xf-0007hj-00
	for ietf@ietf.org; Thu, 15 Jan 2004 10:36:19 -0500
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i0FFaGqY012814;
	Thu, 15 Jan 2004 16:36:17 +0100 (MET)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <ZJBSSJNJ>; Thu, 15 Jan 2004 16:37:50 +0100
Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D03F52C78@Esealnt877.al.sw.ericsson.se>
From: "Yuri Ismailov (KI/EAB)" <yuri.ismailov@ericsson.com>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>
Cc: "'Keith Moore'" <moore@cs.utk.edu>, IETF Discussion <ietf@ietf.org>
Subject: RE: dubious assumptions about IPv6 (was death of the Internet)
Date: Thu, 15 Jan 2004 16:30:59 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

If the number of addresses would be the only concern it would be much easier to expand IPv4 adddresses to 16 bytes and use the rest of IPv4. There are many more things in IPv6 besides address size. IPv6 or whatever besides IPv4 is needed.
My point is not what is better, it is about how to internetwork both of them and this where layering comes into place. The logic is simple: IP was designed to internetwork networks. Once there is more than one IP network, let's internetwork them in a proper way as well. Not more simple than that. Given that, pure IPv6 hosts do not need to use v4 and the other way round.

I'm running IPv6 network with IPv6 DNS since two years ago. It works fine for me, however I want to see both v6 and v4 in action. Do not mind to add private v4 here but internetworked with public v4 and v6 in the same way as v4 to v6 - internetworked but not hacked with the NATs. This is my "math".

-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
Sent: den 15 januari 2004 15:03
To: Yuri Ismailov (KI/EAB)
Cc: 'Keith Moore'; IETF Discussion
Subject: Re: dubious assumptions about IPv6 (was death of the Internet)


On 15-jan-04, at 12:48, Yuri Ismailov (KI/EAB) wrote:

> I share pretty much the views expressed on the page.

I don't share all of them (9 billion people in 2050, 3.7 billion usable 
IPv4 addresses, show me some math that makes this work) but where on 
this page is there a point being made? It seems more like a fairly 
random collection of statements.

> Small addition to that would be the fact that current "transition" 
> proposals are killing the possibility of transition as such. IPv6 is 
> strongly dependent on IPv4 through various "ipv4 compatible" 
> addresses, which are essentially private IPv6 addresses, i.e. not 
> globally routable.

??? Which kind of IPv4-related addresses would a host with native IPv6 
connectivity and IPv6-enabled applications need?

> BTW, not the only private v6 addresses in this sense. This basically 
> means that it will be nearly impossible or at least extremely hard to 
> wash out IPv4 from the implementation. Personally I think that 
> removing IPv4 can not be justified.

Removing IPv4 from the code would be a peculiar idea to say the least. 
But running IPv6-only works for the most part. I tried this on the most 
recent version of MacOS and it's very easy to disable IPv4 for all 
interfaces except loopback. If you manually configure a nameserver 
that's reachable over IPv6 and use IPv6-capable applications, no 
problems whatsoever. People do give me weird looks when I say that I 
want to test running IPv6-only, though.

> Instead of introducing two networks internetworked in a proper way, 
> there are two networks tightly coupled to each other. Besides all, 
> such approach nearly exclude the design of yet another network, which 
> can be naturally internetworked with existing networks. Are there many 
> believers that IPv6 is the last one and forever?

Forever is a very long time. IPv6 is far from perfect, but none of the 
issues are such that replacing the protocol because of them makes 
sense. If we're going to see something new it will probably be a 
niche-only thing for a very long time. But since a simple lack of 
address space won't be an issue in IPv6 (of course this leaves the 
complex lack of address space) it is almost certain that it will be 
possible to translate back and forth between the new protocol and IPv6 
in a way that's compatible with existing IPv6 implementations, so 
deployment won't be an issue.

> The power of layering was heavily underestimated if not ignored. Isn't 
> it clear enough that we would be nowhere if bridging of link layers 
> would take over internetworking of networks.

Talking about power, where are you going to find the power to run those 
16 million+ entry CAMs at 10 Gbps+ without a network layer?



From owner-ietf@ietf.org  Thu Jan 15 12:31:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16177
	for <ietf-web-archive@odin.ietf.org>; Thu, 15 Jan 2004 12:31:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AhBBI-0000Mo-24
	for ietf-list@asgard.ietf.org; Thu, 15 Jan 2004 12:21:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AhBAn-0000Iw-Ba
	for ietf@asgard.ietf.org; Thu, 15 Jan 2004 12:20:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15711
	for <ietf@ietf.org>; Thu, 15 Jan 2004 12:20:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhBAl-0004bL-00
	for ietf@ietf.org; Thu, 15 Jan 2004 12:20:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhB9o-0004YH-00
	for ietf@ietf.org; Thu, 15 Jan 2004 12:19:49 -0500
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhB9X-0004Ur-00
	for ietf@ietf.org; Thu, 15 Jan 2004 12:19:31 -0500
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 NAA30263;
	Thu, 15 Jan 2004 13:20:20 -0500
Date: Thu, 15 Jan 2004 12:12:09 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: <dean@vista.av8.net>
To: "Yuri Ismailov (KI/EAB)" <yuri.ismailov@ericsson.com>
cc: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'Keith Moore'" <moore@cs.utk.edu>, IETF Discussion <ietf@ietf.org>
Subject: RE: dubious assumptions about IPv6 (was death of the Internet)
In-Reply-To: <4E85E49D1F0CBF4F96EA08E335750D7D03F52C78@Esealnt877.al.sw.ericsson.se>
Message-ID: <Pine.LNX.4.33.0401151137260.20023-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

The way people have been thinking about internetworking them is via NATs
and tunnels. and this has prompted the discussion about the evilness of
NATs.

But whether you internetwork with IPv6 and NAT, or just keep IPv4, NAT
will not go likely go away. The "math" below works out because 9 billion
people don't each need a unique IP address.  The vast majority of those
people will be serviced via NAT, as cable and dsl providers are starting
to do now.  Whether this is replaced by IPv6 inter-networks sooner or
later is probably irrelevant to the kinds of services offered to the
people behind the NATs.  The problem of course, is that once you go the
NAT route, you don't really need IPv6 as much. Then it becomes a cost
issue and a support issue, and it becomes something of a luxury rather
than a necessity.

The other problem is that the entire world can't be converted at once, so
there is significant business in the IPv4 side, that the IPv6 side can't
abandon or lose connectivity to.  Those cable and DSL customers presently
using NATs might not be able to handle IPv6 addresses, so the Cable and
DSL companies can't utilize IPv6 addresses.

It would be like losing the ability to contact your bank and make deposits
if you upgrade to the new version of the accounting software.  You can't
do that.  And the bank can't upgrade because then it would lose the people
who haven't upgraded.  Thus, legacy software is frozen in place, until it
is no longer useful.  This is why most of the software written, is still
written in Cobol.  It is likely that Cobol, and IPv4 will still be in use
in 2050.

I think IPv6 would get faster deployment if the cost structure of IPv6
address space were different (free, or $35/yr registration fee), and one
tried to get a specific new industry to adopt it like a proprietary
protocol that just isn't propietary.  My company, Av8 Internet, doesn't
have IPv6 address space because it costs too much money for a plaything,
and for many years to come, it is just for play.  The vast bulk of the
30,000+ isp's are in the same boat.  Making the address space free, and
getting a lot of it assigned, could lead to more use, even if that use
isn't really anything other than horseplay by ISP admins.  But let's say
that NOC's are interconnected by IPv6, with an IPv6 instant messaging
application or IRC--noncritical, but we're just playing around.  It then
becomes much easier for those ISPs to delegate v6 space to customers, who
just want to play.  Then it becomes easier for those customers to create
some initially insignificant v6 application, that grows in importance, and
in turn, provides a pathway for migrating legacy applications.  Someday,
then, those dsl customers can be migrated to IPv6.

You observation that IPv6 is more than just expanded address space is
good, but when given the chance to create a new protocol, people put all
kinds of improvements in. These improvements increase the complexity
somewhat, but I'm not sure they change the overall problem very much.
Given the cost of the change, one would kind of want some significant
improvement besides address space.

		--Dean

On Thu, 15 Jan 2004, Yuri Ismailov (KI/EAB) wrote:

> If the number of addresses would be the only concern it would be much
> easier to expand IPv4 adddresses to 16 bytes and use the rest of IPv4.
> There are many more things in IPv6 besides address size. IPv6 or
> whatever besides IPv4 is needed. My point is not what is better, it is
> about how to internetwork both of them and this where layering comes
> into place. The logic is simple: IP was designed to internetwork
> networks. Once there is more than one IP network, let's internetwork
> them in a proper way as well. Not more simple than that. Given that,
> pure IPv6 hosts do not need to use v4 and the other way round.
>
> I'm running IPv6 network with IPv6 DNS since two years ago. It works
> fine for me, however I want to see both v6 and v4 in action. Do not
> mind to add private v4 here but internetworked with public v4 and v6
> in the same way as v4 to v6 - internetworked but not hacked with the
> NATs. This is my "math".
>
> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> Sent: den 15 januari 2004 15:03
> To: Yuri Ismailov (KI/EAB)
> Cc: 'Keith Moore'; IETF Discussion
> Subject: Re: dubious assumptions about IPv6 (was death of the Internet)
>
>
> On 15-jan-04, at 12:48, Yuri Ismailov (KI/EAB) wrote:
>
> > I share pretty much the views expressed on the page.
>
> I don't share all of them (9 billion people in 2050, 3.7 billion usable
> IPv4 addresses, show me some math that makes this work) but where on
> this page is there a point being made? It seems more like a fairly
> random collection of statements.
>
> > Small addition to that would be the fact that current "transition"
> > proposals are killing the possibility of transition as such. IPv6 is
> > strongly dependent on IPv4 through various "ipv4 compatible"
> > addresses, which are essentially private IPv6 addresses, i.e. not
> > globally routable.
>
> ??? Which kind of IPv4-related addresses would a host with native IPv6
> connectivity and IPv6-enabled applications need?
>
> > BTW, not the only private v6 addresses in this sense. This basically
> > means that it will be nearly impossible or at least extremely hard to
> > wash out IPv4 from the implementation. Personally I think that
> > removing IPv4 can not be justified.
>
> Removing IPv4 from the code would be a peculiar idea to say the least.
> But running IPv6-only works for the most part. I tried this on the most
> recent version of MacOS and it's very easy to disable IPv4 for all
> interfaces except loopback. If you manually configure a nameserver
> that's reachable over IPv6 and use IPv6-capable applications, no
> problems whatsoever. People do give me weird looks when I say that I
> want to test running IPv6-only, though.
>
> > Instead of introducing two networks internetworked in a proper way,
> > there are two networks tightly coupled to each other. Besides all,
> > such approach nearly exclude the design of yet another network, which
> > can be naturally internetworked with existing networks. Are there many
> > believers that IPv6 is the last one and forever?
>
> Forever is a very long time. IPv6 is far from perfect, but none of the
> issues are such that replacing the protocol because of them makes
> sense. If we're going to see something new it will probably be a
> niche-only thing for a very long time. But since a simple lack of
> address space won't be an issue in IPv6 (of course this leaves the
> complex lack of address space) it is almost certain that it will be
> possible to translate back and forth between the new protocol and IPv6
> in a way that's compatible with existing IPv6 implementations, so
> deployment won't be an issue.
>
> > The power of layering was heavily underestimated if not ignored. Isn't
> > it clear enough that we would be nowhere if bridging of link layers
> > would take over internetworking of networks.
>
> Talking about power, where are you going to find the power to run those
> 16 million+ entry CAMs at 10 Gbps+ without a network layer?
>
>




From owner-ietf@ietf.org  Thu Jan 15 13:59:09 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19875
	for <ietf-web-archive@odin.ietf.org>; Thu, 15 Jan 2004 13:59:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AhCSo-0003qE-MA
	for ietf-list@asgard.ietf.org; Thu, 15 Jan 2004 13:43:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AhCRy-0003oX-Mh
	for ietf@asgard.ietf.org; Thu, 15 Jan 2004 13:42:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19119
	for <ietf@ietf.org>; Thu, 15 Jan 2004 13:42:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhCRw-0000ib-00
	for ietf@ietf.org; Thu, 15 Jan 2004 13:42:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhCQx-0000fW-00
	for ietf@ietf.org; Thu, 15 Jan 2004 13:41:36 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhCQ5-0000dN-00
	for ietf@ietf.org; Thu, 15 Jan 2004 13:40:41 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0FIeKkw043287;
	Thu, 15 Jan 2004 19:40:21 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.33.0401151137260.20023-100000@vista.av8.net>
References: <Pine.LNX.4.33.0401151137260.20023-100000@vista.av8.net>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <4C07C315-478A-11D8-815B-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Keith Moore'" <moore@cs.utk.edu>, IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: dubious assumptions about IPv6 (was death of the Internet)
Date: Thu, 15 Jan 2004 19:40:31 +0100
To: Dean Anderson <dean@av8.com>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 15-jan-04, at 18:12, Dean Anderson wrote:

> But whether you internetwork with IPv6 and NAT, or just keep IPv4, NAT
> will not go likely go away.

Directly internetworking IPv4 and IPv6 (where an IPv4-only host talks 
to an IPv6-only host) is only possible for IPv6 hosts that use an 
IPv4-compatible address. This is an interesting experiment, but it's 
not very useful as this imports all the IPv4 address-related issues 
into IPv6.

> The "math" below works out because 9 billion
> people don't each need a unique IP address.  The vast majority of those
> people will be serviced via NAT,

What is your basis for this argument? The current host count is around 
250 million but there are 2 billion addresses in (some form of) use. 
This is obviously going to get better and in the long run not every 
individual needs a public address 24/7, but I don't see how we can get 
from 5 - 10 addresses per person to 0.3 without significant problems.

> as cable and dsl providers are starting to do now.

I don't know which part of the world you hang out, but I've never seen 
any ISP NAT on behalf of its customers. I've heard some talk of GPRS 
service providers doing this (but not seen it) but certainly not 
broadband or regular dial-up. If there is NAT somewhere, it's done by 
the end-users themselves.

> The other problem is that the entire world can't be converted at once, 
> so
> there is significant business in the IPv4 side, that the IPv6 side 
> can't
> abandon or lose connectivity to.

So? One way to accomplish this is to install IPv6 everywhere and only 
keep a few gateways around for access to "legacy" IPv4 web, email and 
the like.

> It would be like losing the ability to contact your bank and make 
> deposits
> if you upgrade to the new version of the accounting software.  You 
> can't
> do that.  And the bank can't upgrade because then it would lose the 
> people
> who haven't upgraded.

Way back when I had to use special software to interact with my bank, I 
used to get a disk with new software in the mail several times each 
year. I guess switching to a web based system was worth it for them 
because of the savings on postage alone.

> Thus, legacy software is frozen in place, until it
> is no longer useful.  This is why most of the software written, is 
> still
> written in Cobol.  It is likely that Cobol, and IPv4 will still be in 
> use
> in 2050.

That's ridiculous. None of us used IPv4 46 years ago, there is no 
telling what we'll be doing in another 46 years.

> I think IPv6 would get faster deployment if the cost structure of IPv6
> address space were different (free, or $35/yr registration fee), and 
> one
> tried to get a specific new industry to adopt it like a proprietary
> protocol that just isn't propietary.  My company, Av8 Internet, doesn't
> have IPv6 address space because it costs too much money

Talk to ARIN. Here in Europe there is no additional cost for ISPs to 
get IPv6 address space.

> for a plaything, and for many years to come, it is just for play.

Unless you are a hardware or software vendor and your customers want 
IPv6.

> You observation that IPv6 is more than just expanded address space is
> good, but when given the chance to create a new protocol, people put 
> all
> kinds of improvements in. These improvements increase the complexity
> somewhat, but I'm not sure they change the overall problem very much.
> Given the cost of the change, one would kind of want some significant
> improvement besides address space.

What would this cost be? Are Windows XP and MacOS Panther more 
expensive with IPv6 support than without? (You don't need IPv6-capable 
routers or switches in order to run IPv6.) And IPv6 is still IP, it's 
not hard to learn.

Now if people prefer to stay with IPv4. that's fine. But the people who 
made IPv6 happen deserve some credit because if and when the time comes 
that we really need IPv6, it will be there, which is a very comforting 
thought.




From owner-ietf@ietf.org  Thu Jan 15 16:16:04 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28700
	for <ietf-web-archive@odin.ietf.org>; Thu, 15 Jan 2004 16:16:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AhEfi-0004wY-8f
	for ietf-list@asgard.ietf.org; Thu, 15 Jan 2004 16:04:58 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AhEej-0004un-Vd
	for ietf@asgard.ietf.org; Thu, 15 Jan 2004 16:03:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28174
	for <ietf@ietf.org>; Thu, 15 Jan 2004 16:03:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhEei-0001y1-00
	for ietf@ietf.org; Thu, 15 Jan 2004 16:03:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhEdf-0001uZ-00
	for ietf@ietf.org; Thu, 15 Jan 2004 16:02:52 -0500
Received: from kahuna.telstra.net ([203.50.0.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhEcz-0001qN-00
	for ietf@ietf.org; Thu, 15 Jan 2004 16:02:09 -0500
Received: from gih505.telstra.net (dhcp24.potaroo.net [203.10.60.24])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id i0FL1FuX047426;
	Fri, 16 Jan 2004 08:01:27 +1100 (EST)
	(envelope-from gih@telstra.net)
Message-Id: <6.0.1.1.2.20040116075855.01c78ec0@kahuna.telstra.net>
X-Sender: gih@kahuna.telstra.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 16 Jan 2004 08:01:06 +1100
To: Iljitsch van Beijnum <iljitsch@muada.com>, Fred Baker <fred@cisco.com>
From: Geoff Huston <gih@telstra.net>
Subject: Re: Processing of Expired Internet-Drafts
Cc: ietf@ietf.org
In-Reply-To: <12D3726D-46DB-11D8-815B-000A95CD987A@muada.com>
References: <200401141552.KAA24589@ietf.org>
 <6.0.1.1.2.20040114082816.0476d6b0@mira-sjc5-b.cisco.com >
 <12D3726D-46DB-11D8-815B-000A95CD987A@muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


>A good and simple way to do this would be to create a file that matches 
>the draft filename without the version number (would this be that 
>tombstone thingy you guys keep talking about?) and say something like 
>"version 34 was submitted 2003-04-05" or "version 00 was deleted 1970-01-01"


You can find an implementation of that form of indexing I-Ds at 
http://www.potaroo.net/ietf/xids-ietf.html

   Geoff





From owner-ietf@ietf.org  Fri Jan 16 05:08:59 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07492
	for <ietf-web-archive@odin.ietf.org>; Fri, 16 Jan 2004 05:08:59 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AhQi7-0003J3-9W
	for ietf-list@asgard.ietf.org; Fri, 16 Jan 2004 04:56:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AhQhF-0003I8-3S
	for ietf@asgard.ietf.org; Fri, 16 Jan 2004 04:55:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07134
	for <ietf@ietf.org>; Fri, 16 Jan 2004 04:55:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhQh3-0006lJ-00
	for ietf@ietf.org; Fri, 16 Jan 2004 04:55:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhQg9-0006jC-00
	for ietf@ietf.org; Fri, 16 Jan 2004 04:54:13 -0500
Received: from [63.247.75.146] (helo=montage.altserver.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhQfc-0006gm-00
	for ietf@ietf.org; Fri, 16 Jan 2004 04:53:40 -0500
Received: from f01v-39-167.d0.club-internet.fr ([212.195.250.167] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1AhQfK-0003LJ-Ok; Fri, 16 Jan 2004 01:53:23 -0800
Message-Id: <6.0.1.1.2.20040116110327.04729250@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 16 Jan 2004 11:06:38 +0100
To: Dean Anderson <dean@av8.com>,
        "Yuri Ismailov (KI/EAB)" <yuri.ismailov@ericsson.com>
From: jfcm <info@utel.net>
Subject: RE: dubious assumptions about IPv6 (was death of the Internet)
Cc: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'Keith Moore'" <moore@cs.utk.edu>, IETF Discussion <ietf@ietf.org>
In-Reply-To: <Pine.LNX.4.33.0401151137260.20023-100000@vista.av8.net>
References: <4E85E49D1F0CBF4F96EA08E335750D7D03F52C78@Esealnt877.al.sw.ericsson.se>
 <Pine.LNX.4.33.0401151137260.20023-100000@vista.av8.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 18:12 15/01/04, Dean Anderson wrote:
>But whether you internetwork with IPv6 and NAT, or just keep IPv4, NAT
>will not go likely go away. The "math" below works out because 9 billion
>people don't each need a unique IP address.  The vast majority of those
>people will be serviced via NAT, as cable and dsl providers are starting
>to do now.  Whether this is replaced by IPv6 inter-networks sooner or
>later is probably irrelevant to the kinds of services offered to the
>people behind the NATs.  The problem of course, is that once you go the
>NAT route, you don't really need IPv6 as much. Then it becomes a cost
>issue and a support issue, and it becomes something of a luxury rather
>than a necessity.

Is there somewhere an upto date analysis of the costs per country/areas of 
IPv6 vs IPv4? This is the "ultima ratio" of a move and of the selection of 
an application to promote IPv6. Without an architectural and economical 
network model could people take decisions. Lobbying will make them 
interested, money will make them decide.
jfc







From owner-ietf@ietf.org  Fri Jan 16 08:54:13 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14014
	for <ietf-web-archive@odin.ietf.org>; Fri, 16 Jan 2004 08:54:13 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AhUHi-0007XF-E7
	for ietf-list@asgard.ietf.org; Fri, 16 Jan 2004 08:45:14 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AhOXS-0008Ug-OA
	for ietf@asgard.ietf.org; Fri, 16 Jan 2004 02:37:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04322
	for <ietf@ietf.org>; Fri, 16 Jan 2004 02:37:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhOXQ-0001eT-00
	for ietf@ietf.org; Fri, 16 Jan 2004 02:37:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhOWa-0001cT-00
	for ietf@ietf.org; Fri, 16 Jan 2004 02:36:13 -0500
Received: from smtp.sprintpcs.com ([63.167.114.16] helo=dedicated59-bos.wh.sprintip.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhOVu-0001WE-00
	for ietf@ietf.org; Fri, 16 Jan 2004 02:35:30 -0500
Received: from solidmatrix.com (000-362-286.area3.spcsdns.net [68.29.129.174])
 by dedicated59-bos.wh.sprintip.net
 (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
 with ESMTPA id <0HRK00DRUNQ9E5@dedicated59-bos.wh.sprintip.net> for
 ietf@ietf.org; Fri, 16 Jan 2004 07:35:01 +0000 (GMT)
Date: Fri, 16 Jan 2004 02:34:58 -0500
From: Yakov Shafranovich <research@solidmatrix.com>
Subject: ASRG/IRTF Soliciting Volunteers and Feedback
To: ietf@ietf.org
Message-id: <40079422.1030001@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en, he, ru
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5)
 Gecko/20031007
X-Enigmail-Version: 0.82.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

The Anti-Spam Research Group (ASRG) of the IRTF is seeking feedback and 
volunteers from the wider IETF community. We have recently changed our 
charter to focus on approaches that can be defined, deployed and used in 
the near term, likely to lead to usable results, and to avoid those that 
duplicate other efforts or that have proven unproductive in the past. 
Majority of our research will seek to provide input into the IETF 
standardization activities. We are refocusing our efforts on the 
following areas:

o Problem areas in the current email architecture that facilitate junk 
email and network abuse, and the impact of each area on the overall problem
o Analysis of persistent patterns in spam and spammer behavior that can 
be used to improve existing and propose new solutions.
o Best Current Practices for Spam Control - including email admins, end 
users, MTA developers, blacklist operators, etc..
o Filtering Standards - dynamic updates, standard headers for MTAs, etc.
o Abuse Reporting Standards - research into common standards for 
exchanging information about network and email abuse.
o. SMTP Session Verification - verification of the SMTP transaction 
(e.g. LMAP, etc.).
o Message Verification - verification of both the message headers and 
content (e.g. DK, Lumos, TEOS, etc.)

More information can be found on our webpage at:
http://asrg.sp.am. Feedback is welcome on our mailing list, 
asrg@ietf.org or to the chairs directly.

Sincerely,
Yakov Shafranovich
Co-Chair, ASRG/IRTF

-------
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"Some lies are easier to believe than the truth" (Dune)
-------






From owner-ietf@ietf.org  Fri Jan 16 19:04:12 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06122
	for <ietf-web-archive@odin.ietf.org>; Fri, 16 Jan 2004 19:04:12 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ahdj9-0007fA-BZ
	for ietf-list@asgard.ietf.org; Fri, 16 Jan 2004 18:50:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ahdil-0007eY-C6
	for ietf@asgard.ietf.org; Fri, 16 Jan 2004 18:49:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05808
	for <ietf@ietf.org>; Fri, 16 Jan 2004 18:49:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ahdij-00059Z-00
	for ietf@ietf.org; Fri, 16 Jan 2004 18:49:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ahdho-00055P-00
	for ietf@ietf.org; Fri, 16 Jan 2004 18:48:49 -0500
Received: from thing.verisignlabs.com ([65.201.175.62] helo=cliffie.verisignlabs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ahdh0-0004xA-00
	for ietf@ietf.org; Fri, 16 Jan 2004 18:47:58 -0500
Received: from thinkingcat.com ([::ffff:216.168.239.87])
  (AUTH: PLAIN leslie, TLS: TLSv1/SSLv3,128bits,RC4-MD5)
  by cliffie.verisignlabs.com with esmtp; Fri, 16 Jan 2004 18:47:28 -0500
Message-ID: <400877D0.7040603@thinkingcat.com>
Date: Fri, 16 Jan 2004 18:46:24 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Jan04:  Update on administration restructuring
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Consistent with my December update, there have not been many further
comments on the IAB Advisory Committee report.  The IAB has requested 
that the RFC-Editor publish the document
(draft-iab-advcomm-01.txt).

One substantive point of discussion that has come up more than
once is:  why does changing the administration structure of the
IETF help deal with the budgetary issues that have been outlined?

Changing structure doesn't make those problems go away, of course.
The entire thrust of the proposed restructuring, we believe, is
that more coordination of the different IETF activities (in terms
of their administration and budgeting) is a necessary first step
to giving us, the contributing community, the tools necessary
to address the pressing financial questions.

We expect to have an Internet-Draft outlining more concrete proposals
(and addressing that question in more detail) published by
the -00 cutoff deadline for IETF59 (February 9).

Leslie.

-- 

-------------------------------------------------------------------
"Reality:
     Yours to discover."
                                -- ThinkingCat
Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------





From owner-ietf@ietf.org  Fri Jan 16 19:12:33 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06327
	for <ietf-web-archive@odin.ietf.org>; Fri, 16 Jan 2004 19:12:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ahdyd-0007wH-CT
	for ietf-list@asgard.ietf.org; Fri, 16 Jan 2004 19:06:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AhdyU-0007vL-Ok
	for ietf@asgard.ietf.org; Fri, 16 Jan 2004 19:06:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06165
	for <ietf@ietf.org>; Fri, 16 Jan 2004 19:05:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ahdy3-0005r9-00
	for ietf@ietf.org; Fri, 16 Jan 2004 19:05:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhdvA-0005iZ-00
	for ietf@ietf.org; Fri, 16 Jan 2004 19:02:37 -0500
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ahdsl-0005Y2-00
	for ietf@ietf.org; Fri, 16 Jan 2004 19:00:07 -0500
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 UAA01058;
	Fri, 16 Jan 2004 20:04:57 -0500
Date: Fri, 16 Jan 2004 18:56:47 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: "'Keith Moore'" <moore@cs.utk.edu>, IETF Discussion <ietf@ietf.org>
Subject: Re: dubious assumptions about IPv6 (was death of the Internet)
In-Reply-To: <4C07C315-478A-11D8-815B-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0401161805130.21552-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 15 Jan 2004, Iljitsch van Beijnum wrote:

> On 15-jan-04, at 18:12, Dean Anderson wrote:
>
> > But whether you internetwork with IPv6 and NAT, or just keep IPv4, NAT
> > will not go likely go away.
>
> Directly internetworking IPv4 and IPv6 (where an IPv4-only host talks
> to an IPv6-only host) is only possible for IPv6 hosts that use an
> IPv4-compatible address. This is an interesting experiment, but it's
> not very useful as this imports all the IPv4 address-related issues
> into IPv6.

I was thinking more of a dual homed host, with an IPv6 interface, and an
IPv4 interface, and an IPv6-IPv4 NAT. Essentially your IPv6 HTTP request
is NATTed or proxied through to an IPv4 server.

> > The "math" below works out because 9 billion
> > people don't each need a unique IP address.  The vast majority of those
> > people will be serviced via NAT,
>
> What is your basis for this argument? The current host count is around
> 250 million but there are 2 billion addresses in (some form of) use.
> This is obviously going to get better and in the long run not every
> individual needs a public address 24/7, but I don't see how we can get
> from 5 - 10 addresses per person to 0.3 without significant problems.

Just the observation that most cable and DSL providers can give customers
RFC1918 address space, and use NAT. Some providers are doing this now. The
residential users don't need to have a globaly unique IP address.  The
vast majority of the 9 billion people in the world will be residential
users.  It could very well be possible for a long time to come that only a
few billion unique addressses are needed.

> > as cable and dsl providers are starting to do now.
>
> I don't know which part of the world you hang out, but I've never seen
> any ISP NAT on behalf of its customers. I've heard some talk of GPRS
> service providers doing this (but not seen it) but certainly not
> broadband or regular dial-up. If there is NAT somewhere, it's done by
> the end-users themselves.

I've heard of residential service companies doing this.

> > The other problem is that the entire world can't be converted at once,
> > so there is significant business in the IPv4 side, that the IPv6 side
> > can't abandon or lose connectivity to.
>
> So? One way to accomplish this is to install IPv6 everywhere and only
> keep a few gateways around for access to "legacy" IPv4 web, email and
> the like.

Right, but everyone operating a server will want to keep their IPv4 legacy
stuff, and what motivation do they have for going to IPv6?  Why, for
example, would Fleet Bank move to IPv6?

This is a serious rhetorical question. You have to put yourself in the
position of CIO of Fleet Bank, and consider the options.  Internal cost,
ISP cost, to what benefit?

> > It would be like losing the ability to contact your bank and make
> > deposits if you upgrade to the new version of the accounting software.
> > You can't do that.  And the bank can't upgrade because then it would
> > lose the people who haven't upgraded.
>
> Way back when I had to use special software to interact with my bank, I
> used to get a disk with new software in the mail several times each
> year. I guess switching to a web based system was worth it for them
> because of the savings on postage alone.

Yep. Those programs cost the bank quite a lot. Most banks didn't do them.
Some that did them, canceled them.  My bank had a dialup program that they
canceled after a pilot.

> > Thus, legacy software is frozen in place, until it is no longer
> > useful.  This is why most of the software written, is still written in
> > Cobol.  It is likely that Cobol, and IPv4 will still be in use in
> > 2050.
>
> That's ridiculous. None of us used IPv4 46 years ago, there is no
> telling what we'll be doing in another 46 years.

46 years ago was 1958.  In 1954, the first B52 bomber flew.  The last one
made was delivered in 1962.  I note that we are still flying the B52. It
was only a few years ago that the Pentagon shut down the last Multics
machine. I think somewhere around that then the IBM 360 series was
introduced.  That same architecture still runs in the latest IBM Z series.
You are right that we can't forsee the future. But we can make some
guesses.  Mine is that people will still be using Cobol and IPv4.  I would
also hope that people aren't using Microsoft, but I think that is probably
unlikely.

> > I think IPv6 would get faster deployment if the cost structure of IPv6
> > address space were different (free, or $35/yr registration fee), and
> > one tried to get a specific new industry to adopt it like a
> > proprietary protocol that just isn't propietary.  My company, Av8
> > Internet, doesn't have IPv6 address space because it costs too much
> > money
>
> Talk to ARIN. Here in Europe there is no additional cost for ISPs to
> get IPv6 address space.

Good point.

> > for a plaything, and for many years to come, it is just for play.
>
> Unless you are a hardware or software vendor and your customers want
> IPv6.

I have yet to have an Internet customer ask for IPv6 address space. But I
am certain I have customers that have done IPv6 testing.

I think if you make operating systems and network software, the questions
are different.  But the developers of operating systems don't need to talk
to Fleet Bank over IPv6 to test their software, and they don't need IPv6
space from their ISP.

> > You observation that IPv6 is more than just expanded address space is
> > good, but when given the chance to create a new protocol, people put
> > all kinds of improvements in. These improvements increase the
> > complexity somewhat, but I'm not sure they change the overall problem
> > very much. Given the cost of the change, one would kind of want some
> > significant improvement besides address space.
>
> What would this cost be? Are Windows XP and MacOS Panther more
> expensive with IPv6 support than without? (You don't need IPv6-capable
> routers or switches in order to run IPv6.) And IPv6 is still IP, it's
> not hard to learn.

Here's a 30 second list:

Administrative--you have to create systems to track and manage two pools
of space.
Help Desk--you have to train people to support IPv6
Help Desk--you spend more time spelling out IPv6 addresses over the phone.
Operations--you have to support routing 2 essentially separate protocols
Operations--you have to manage and debug IPv6 problems.

If you are servicing residential users that pay $35/mo, you can't spend
too much time on the phone. You can't spend too much time on network
operations. And you can't spend very much on resource administration.
These are low margin operations. They can't spend very much per user and
stay in business. They have to limit what their customers can do, just to
limit those costs.  IPv4 isn't hard to learn either, but the "unforeseen"
support costs of IPv4 have driven a number of residential providers out of
business.

We don't offer residential services. The story is quite different again in
the commercial services world.  I think the commercial companies like high
tech companies are more likely to want to simply play with IPv6.  But that
isn't something they can pay for, and it would still cost me money to
provide the service. So what's my interest?

But of course, when I talk to Cisco, I still ask them about IPv6 support.
Of course, I'm not willing to pay for it either. Luckily, they are doing
it "for free".  Most everyone wants stuff that _can_ do IPv6, but actually
using that support is another issue altogether.

> Now if people prefer to stay with IPv4. that's fine. But the people who
> made IPv6 happen deserve some credit because if and when the time comes
> that we really need IPv6, it will be there, which is a very comforting
> thought.

I'm not saying that they don't deserve credit. I'm just saying that there
are many other practicalities to consider.




From owner-ietf@ietf.org  Sat Jan 17 02:15:35 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28101
	for <ietf-web-archive@odin.ietf.org>; Sat, 17 Jan 2004 02:15:35 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AhkV6-0005MZ-WE
	for ietf-list@asgard.ietf.org; Sat, 17 Jan 2004 02:04:09 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AhkUD-0005Lm-45
	for ietf@asgard.ietf.org; Sat, 17 Jan 2004 02:03:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18900
	for <ietf@ietf.org>; Sat, 17 Jan 2004 02:03:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhkTx-0000Yc-00
	for ietf@ietf.org; Sat, 17 Jan 2004 02:02:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhkQs-0000Nz-00
	for ietf@ietf.org; Sat, 17 Jan 2004 01:59:47 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50] helo=smtp.cs.utk.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhkOy-0000Gy-00
	for ietf@ietf.org; Sat, 17 Jan 2004 01:57:48 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 2A794AFF13; Sat, 17 Jan 2004 01:57:20 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 05062-08; Sat, 17 Jan 2004 01:57:18 -0500 (EST)
Received: from [192.168.0.4] (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 1AAA4AFF16; Sat, 17 Jan 2004 01:57:18 -0500 (EST)
In-Reply-To: <Pine.LNX.4.44.0401161805130.21552-100000@vista.av8.net>
References: <Pine.LNX.4.44.0401161805130.21552-100000@vista.av8.net>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <784F1990-48BA-11D8-BE61-000393DB5366@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@cs.utk.edu>, Iljitsch van Beijnum <iljitsch@muada.com>,
        IETF Discussion <ietf@ietf.org>
From: Keith Moore <moore@cs.utk.edu>
Subject: Re: dubious assumptions about IPv6 (was death of the Internet)
Date: Sat, 17 Jan 2004 01:57:52 -0500
To: Dean Anderson <dean@av8.com>
X-Mailer: Apple Mail (2.609)
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> The residential users don't need to have a globaly unique IP address.

That's like saying residential telephone users don't need to have a 
phone number at which they can be reached.  (after all, the purpose of 
their residential phones is to call businesses for the purpose of 
obtaining services, right?)

There are lots of apps that would be valuable to residential users if 
residential users had reachable IP addresses.  check the status of your 
alarm system, or your roast in the oven, or your freezer's inventory.  
Grab a picture from your baby-cam while you're out for dinner and have 
left the kid with the baby sitter.  Reset the thermostat if you're 
going to be out of town longer than you thought.  Do all of these from 
your portable phone/PDA which is running guess what? -- IPv6.

Also, don't assume that IPv6 addresses will be used by people or their 
personal computers.  IPv6 enables lots and lots of individually 
addressable devices which don't have to be associated with individuals. 
  Every km of highway can have an addressable traffic sensor so that 
police and emergency crews know exactly when and where a traffic 
accident happened.  Every streetlight can be monitored to see if it is 
functioning properly or if it needs service.  Every traffic signal can 
be made individually controllable so that they can dynamically adapt to 
changes in traffic patterns.  For reasons like this, the demand for 
IPv6 addresses won't be determined by some linear multiple of the 
number of humans on the planet.

Finally, don't assume that IPv6 devices will require the support 
burdens we associate with PCs.  PCs as we currently know them are 
dinosaurs. Appliances that talk to the network aren't going to need the 
same kind of technical hand-holding that PCs do (because they'd never 
succeed if they did), and neither will the devices that replace what we 
now think of as personal computers.

IPv6 will eventually replace IPv4, but it's misleading to think of IPv6 
as just a replacement for IPv4.  By the time IPv6 replaces IPv4, we 
won't recognize the IPv6 network as something that resembles what the 
IPv4 network is used for today.  Even though the underlying technology 
is very similar, IPv6 is really a new kind of network, one that enables 
things that were really never possible with IPv4 on a large scale.




From owner-ietf@ietf.org  Sat Jan 17 03:04:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00900
	for <ietf-web-archive@odin.ietf.org>; Sat, 17 Jan 2004 03:04:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AhlMK-0006Xx-GI
	for ietf-list@asgard.ietf.org; Sat, 17 Jan 2004 02:59:08 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AhlIX-0006Vb-6i
	for ietf@asgard.ietf.org; Sat, 17 Jan 2004 02:55:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00757
	for <ietf@ietf.org>; Sat, 17 Jan 2004 02:55:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhlIQ-0003gp-00
	for ietf@ietf.org; Sat, 17 Jan 2004 02:55:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhlH6-0003dv-00
	for ietf@ietf.org; Sat, 17 Jan 2004 02:53:45 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhlFu-0003aP-00
	for ietf@ietf.org; Sat, 17 Jan 2004 02:52:30 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id AA85461B8D
	for <ietf@ietf.org>; Sat, 17 Jan 2004 08:51:42 +0100 (CET)
Date: Fri, 16 Jan 2004 22:53:47 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Summary status of change efforts - Updated Web page
Message-ID: <405441934.1074293627@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I've attempted to update my summary of "where everything is" and placed it 
on http://www.ietf.org/u/ietfchair/change-status.html

Because a cron job has to run before it's visible, it may be late in 
arriving - if the date at the top says "January 13", it's the new version.

A pre-production copy is on 
http://www.alvestrand.no/ietf/chair/change-status.html if anyone's in a 
hurry.

Comments welcome - but don't expect a quick response from me; I'll be 
(mostly) off the net next week....

                 Harald






From owner-ietf@ietf.org  Sat Jan 17 07:39:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06349
	for <ietf-web-archive@odin.ietf.org>; Sat, 17 Jan 2004 07:39:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AhpZa-000232-JW
	for ietf-list@asgard.ietf.org; Sat, 17 Jan 2004 07:29:06 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AhpZR-00022N-0W
	for ietf@asgard.ietf.org; Sat, 17 Jan 2004 07:28:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06191
	for <ietf@ietf.org>; Sat, 17 Jan 2004 07:28:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhpZQ-0006qf-00
	for ietf@ietf.org; Sat, 17 Jan 2004 07:28:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhpYS-0006nG-00
	for ietf@ietf.org; Sat, 17 Jan 2004 07:27:57 -0500
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhpXV-0006iI-00
	for ietf@ietf.org; Sat, 17 Jan 2004 07:26:57 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i0HCQPQ12276
	for <ietf@ietf.org>; Sat, 17 Jan 2004 14:26:25 +0200
Date: Sat, 17 Jan 2004 14:26:25 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: The IETF Mission [Re: Summary status of change efforts - Updated
 Web page]
In-Reply-To: <405441934.1074293627@localhost>
Message-ID: <Pine.LNX.4.44.0401171150270.11109-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Hello all,

Sorry for opening this obvious can of worms (well, I think it has been
opened a number of times, so the worms are probably already gone
now..), but when considering how the IETF needs to change, it's
obvious that we'll first (unless we just stick to the relatively
"safe" changes, like improving review, enhancing the tools,
streamlining the process, etc.) have get consensus on what the IETF
should be doing in the first place.

From the URL (and the material it references):

http://www.alvestrand.no/ietf/chair/change-status.html

.. I'll quote some important pieces (hopefully) not too much out of 
context:

===
The common purpose that brings the IETF together is that "The Internet 
must work". 
===
 - I believe that's a shared purpose; of course, different people have 
different things in mind when they think about what constitutes
"Internet" and "work" though.

===
A large part of making the Internet work is the job of others, and NOT 
IETF business - because others do it better. 
This includes: 

 - Deploying networks. ISPs do that. 
 - Building products. Vendors do that. 
 - Regulating the ways in which the Internet can be used. Governments 
do that (and ICANN tries to). 
===
 - These are so overly broad statements that they're close to unusable
UNLESS you believe IETF is just a rubber-stamping standards
organization.  For example, what constitutes "deploying networks"?  
IETF certainly shouldn't be go digging fibers, or give advice on how
to dig fibers.

But as the vast evidence makes it clear, most ISPs do a very lousy job
of deploying networks *properly*, causing harm to the Internet as a
whole.  Wouldn't it be somewhat in the IETF's business to try to give
advice (using BCP and Info documents) how to do it better?  

I guess one could argue against this, with "well, then why don't the
users pick their competitors?" -- but the point is that many networks
aren't really that bad on the user of *that* network, but for the
Internet as a whole.  It seems pretty clear that "darwinism" doesn't
help, and the stakes ("the commons") are too high to ignore these
issues.

Similarly, "building products" is vague, and may become problematic
especially if one believes the IETF (however that decision could be
reached is another can of worms entirely) has the power to say "No, we
don't want to standardize FOO" or "No, we don't want to standardize
the means to do BAR using the approach FOO".  Then the vendor could
argue it's not the IETF's business to tell how it should build it's
products.  Similarly, this "gray area" is often invaded when the
specifications state which knobs, toggles or features MUST/SHOULD be
implemented -- isn't this also telling the vendors how to build
products? (Of course, there is a fine line with actually "building
products" and "documenting how one could build a product (if it was to
be standards-compliant)".)

"Regulating the Internet" is also not problem-free.  If the IETF
decides not to standarize or publish something which is considered to
be a Bad Thing (e.g., NAT for IPv6, Wiretapping mechanisms, VOIP
Backdoors, etc.etc.) -- couldn't one argue that the IETF is basically
regulating the Internet by some means?  Naturally, the IETF has no
power outside it's own "jurisdiction" (i.e., publishing documents, and
to an extent, overseeing the administration of number spaces), so the
IETF can't (and shouldn't) disallow someone from doing something which
may be a bad idea anyway -- just it won't give its "blessing"  for
doing so.  But still, it seems the IETF is trying to (gently)  guide
the Internet around the things that seem like really bad ideas.
 
===
"The purpose of the IETF is to create high quality, relevant, and 
timely standards for the Internet."

Note that this clearly positions the IETF primarily as a standards 
development organization. There are other activities in the IETF; but 
if the IETF does not do its core mission, all else will quickly fade.

[...]

Supporting missions
[...]

The IETF has also had a strong operational component, with a tight 
bond, and hence coordination, between protocol developers and network 
operators, and has had many participants who did both. This has 
provided valuable feedback to allow correction of misguided 
standardization efforts, and has provided feedback to sort out which 
standards were actually needed. As the field has grown explosively, 
specialization has set in, and market pressures have risen, there has 
been less and less operator participation in the IETF.
===

I'm not sure if I agree that the main purpose of the IETF is to
produce standards for the Internet.  I guess this boils down to the
fact whether the processes should be vendor-driven or
consumer/customer-driven.

Naturally, from the vendor perspective, creating interoperable
standards is the most important thing. (Of course, some vendors could
use the lack of standards as a business driver as well, so this is
probably an animous opinion..)  E.g., giving advice on how to deploy
technologies (e.g., ingress filtering) is probably not seen
interesting or necessary.

From the customer/operator/consumer perspective, however, this may be
slightly different.  In a multi-vendor networks, interoperability is
of course important.  But even more, the standards which exist must be
relevant -- anything else is waste of time and energy, or even
damaging ("misleading the users to think they need X, or to achieve
the effect of X, they should do it with mechanism X").  Second, what's
more important than the standards themselves is some guidance or
advise on where/whether they are needed or useful in the first place
and if there are significant problems in deploying something, some
advice on how to go about doing that.  Of course, one could ask
whether the IETF is the right place to do that?  Well, at least some
part of that has to (and should) be done by someone else, but putting
it everything on e.g. vendors would be extremely counter-productive,
as discussed above. Third, general documents in general are also very
useful (e.g., documenting how the implementations are _not_
standards-compliant and what practical problems that causes, or what
are the issues/considerations in FOO (e.g., DNSSEC, DDNS, etc. -- or a
subset thereof)).

Therefore, I'd be quite hesitant to lower the other functions the IETF
is doing to be just supporting missions.  Producing the standards
should probably be listed in the mission, but not as the only item.

Sorry for the long note.

On Fri, 16 Jan 2004, Harald Tveit Alvestrand wrote:
> I've attempted to update my summary of "where everything is" and placed it 
> on http://www.ietf.org/u/ietfchair/change-status.html
> 
> Because a cron job has to run before it's visible, it may be late in 
> arriving - if the date at the top says "January 13", it's the new version.
> 
> A pre-production copy is on 
> http://www.alvestrand.no/ietf/chair/change-status.html if anyone's in a 
> hurry.
> 
> Comments welcome - but don't expect a quick response from me; I'll be 
> (mostly) off the net next week....
> 
>                  Harald
> 
> 
> 
> 

-- 
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  Sat Jan 17 11:32:30 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11546
	for <ietf-web-archive@odin.ietf.org>; Sat, 17 Jan 2004 11:32:30 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AhtC4-0004uE-TL
	for ietf-list@asgard.ietf.org; Sat, 17 Jan 2004 11:21:04 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AhtBL-0004tX-6K
	for ietf@asgard.ietf.org; Sat, 17 Jan 2004 11:20:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11277
	for <ietf@ietf.org>; Sat, 17 Jan 2004 11:20:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhtBA-0007JR-00
	for ietf@ietf.org; Sat, 17 Jan 2004 11:20:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aht9n-0007Fw-00
	for ietf@ietf.org; Sat, 17 Jan 2004 11:18:44 -0500
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aht7R-0007AM-00
	for ietf@ietf.org; Sat, 17 Jan 2004 11:16:17 -0500
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id 94CE5E063B; Sat, 17 Jan 2004 11:15:48 -0500 (EST)
Date: Sat, 17 Jan 2004 11:15:48 -0500
From: John Leslie <john@jlc.net>
To: Pekka Savola <pekkas@netcore.fi>
Cc: ietf@ietf.org
Subject: The IETF Mission
Message-ID: <20040117161548.GB98499@verdi>
References: <405441934.1074293627@localhost> <Pine.LNX.4.44.0401171150270.11109-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0401171150270.11109-100000@netcore.fi>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Pekka Savola <pekkas@netcore.fi> wrote:
> 
> But as the vast evidence makes it clear, most ISPs do a very lousy job
> of deploying networks *properly*, causing harm to the Internet as a
> whole.  Wouldn't it be somewhat in the IETF's business to try to give
> advice (using BCP and Info documents) how to do it better?  

   This started out as a response to Pekka. And a response to Pekka is
still very important. But that will have to wait for another message,
because there's too much background which must be covered first.

>> http://www.alvestrand.no/ietf/chair/change-status.html

    In that document, Harald refers to:

http://www.alvestrand.no/ietf/chair/ietf-mission.html

which seems to state a "mission" for IETF:

" The purpose of the IETF is to create high quality, relevant, and timely
" standards for the Internet.

   This is one of those "motherhood and apple pie" statements we've been
conditioned to ignore. Much though I like Harald, I don't think it's a
good statement of our purpose, least of all mission.

   But first, let Harald explain:

" Note that this clearly positions the IETF primarily as a standards
" development organization.

   I doubt the wisdom of "positioning" the IETF "primarily" as a
"standards development organization". Clearly we do develop standards;
I'll even agree that there seems to be consensus to learn to do so better.

   But I don't believe that has ever before been our "primary" purpose.
(Surely, if it were, we'd have put more effort into doing it well.)

   And, most of all, I don't believe it wise to try to "position" the
IETF as anything other than a pretty chaotic group of people. No,
strike that -- I should have said, many pretty chaotic groups of people.

   "Positioning" the IETF makes "herding cats" look easy!

" There are other activities in the IETF; but if the IETF does not do its
" core mission, all else will quickly fade. 

   I contend that the IETF hasn't been doing a good job of "creating
high quality, relevant, and timely standards", but the Internet still
works. (So I must disagree with Harald here.)

" This is intended to be an ordered list of characteristics. Timely
" standards of low quality or that are irrelevant will not serve the
" Internet's or the IETF's needs.

   Here we get to the crux of the matter. "Timely" standards are crucial
to the operation of the Internet. Witness Microsoft. They have a wildly
successful business plan based upon "timely" standards, of whatever
quality and relevance.

   Thankfully, Microsoft has competitors. These competitors realize that
"high quality" will avail them nothing if they don't have a "timely"
alternative to the Microsoft standard. (This may be why so much gets
implemented off of "Internet drafts".)

   "Relevance" is obvious only in hindsight. Even in hindsight, it's
obvious that relevance -- in the eye of the beholder -- is a slippery
thing. The _perception_ of relevance must be built up -- usually after
a "standard" is fully described" -- in the eyes of potential users.
"Relevance" simply cannot precede "timeliness".

" This leaves open the very interesting and difficult questions of how to
" measure quality, relevance, and timeliness. The IETF has identified
" interoperability, security, and scalability as essential, but without
" attaching measurements to those characteristics.

   "Interoperability" is a long-standing tradition. "Security" is a
relatively recent buzzword -- suffering from all the problems which come
with buzzwords. "Scalability" deserves a place next to "interoperability"
as a long-standing tradition; but I'm fearful that -- as individuals --
we're attaching too many different definitions to it.

" It is important that this is "For the Internet," and does not include
" everything that happens to use IP. IP is being used in a myriad of
" real-world applications, such as controlling street lights, but the
" IETF does not standardize those applications.

   That concludes Harald's section on "The IETF Mission".

   Though it's pointless to try to substitute my wisdom for that of the
IESG, I will suggest some food for thought:

1) The IETF has always chartered Working Groups. Doesn't that belong
   fairly high in our priorities?

2) There is a long tradition of waiting for grassroots interest and
   gathering interested persons to hammer out an approach which may
   reach "rough consensus and working code". Is this no longer a good
   approach?

3) The IETF has always had a mechanism for appropriately publishing
   individual viewpoints. Is this no longer important?

4) "Timeliness" is a difficult nut to crack. Wouldn't we be better off
   creating several new paths to improve timeliness instead of placing
   blind faith in an ability to "charter in" timeliness to a standards
   process designed around a slow consensus process?

--
John Leslie <john@jlc.net>



From owner-ietf@ietf.org  Sat Jan 17 19:05:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21382
	for <ietf-web-archive@odin.ietf.org>; Sat, 17 Jan 2004 19:05:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ai08f-0000eD-T7
	for ietf-list@asgard.ietf.org; Sat, 17 Jan 2004 18:46:01 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ai080-0000dY-Jn
	for ietf@asgard.ietf.org; Sat, 17 Jan 2004 18:45:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21110
	for <ietf@ietf.org>; Sat, 17 Jan 2004 18:45:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ai07y-0003st-00
	for ietf@ietf.org; Sat, 17 Jan 2004 18:45:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ai076-0003r9-00
	for ietf@ietf.org; Sat, 17 Jan 2004 18:44:24 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ai064-0003nu-00
	for ietf@ietf.org; Sat, 17 Jan 2004 18:43:20 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 17 Jan 2004 15:46:12 +0000
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i0HNglVM023489;
	Sat, 17 Jan 2004 15:42:48 -0800 (PST)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id APJ48760;
	Sat, 17 Jan 2004 15:42:46 -0800 (PST)
Message-Id: <6.0.1.1.2.20040117103457.0466fc00@mira-sjc5-b.cisco.com >
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sat, 17 Jan 2004 15:24:54 -0800
To: Pekka Savola <pekkas@netcore.fi>
From: Fred Baker <fred@cisco.com>
Subject: Re: The IETF Mission [Re: Summary status of change efforts -
  Updated Web page]
Cc: ietf@ietf.org
In-Reply-To: <Pine.LNX.4.44.0401171150270.11109-100000@netcore.fi>
References: <405441934.1074293627@localhost>
 <Pine.LNX.4.44.0401171150270.11109-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.7 required=5.0 tests=AWL,FORGED_MUA_EUDORA,
	INVALID_MSGID autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At 04:26 AM 1/17/2004, Pekka Savola wrote:
>"The purpose of the IETF is to create high quality, relevant, and
>timely standards for the Internet."

I think I would state it in these words:

    "The Internet Engineering Task Force provides a forum for the
    discussion and development of white papers and specifications
    for the engineering issues of the Internet."

NANOG her sisters might argue that they are also engineering fora, and I 
will agree; they deal with operational engineering, where the IETF deals 
with more of the protocol issues. I don't think that particularly 
denigrates either organization.

 From my perspective, it is less about "standards" than it is about 
"specifications" and various contributions improving our understanding. For 
the same reason, this needs to not be a discussion of whether it is the 
vendors or the users of their products; the real value of the IETF is that 
both are present and the opinions of both are treated as having value.

Lets take an example. I have been involved in QoS work, and there have been 
a number of specifications written on the subject; much of that started 
with white papers, including especially

0896 Congestion control in IP/TCP internetworks. J. Nagle.
      Jan-06-1984. (Format: TXT=26782 bytes) (Status: UNKNOWN)

0970 On packet switches with infinite storage. J. Nagle. Dec-01-1985.
      (Format: TXT=35316 bytes) (Status: UNKNOWN)

The first of these is very operational in nature, and is posed by a user of 
the technology. The second, by the same author, is far more academic in 
nature, and was seminal in the development of a variety of ideas relating 
to QoS in the succeeding decade. But it originates with a very real and 
very damaging operational problem, that of BSD 4.1's predilection to TCP 
Silly Window Syndrome and an operator's desire to minimize the impact of 
that on competing data traffic.

To leave white papers and internet drafts, many of which are never 
published as RFCs and a relatively small portion ever become standards, 
out, and to leave the discussion part out is, I think, to leave out much of 
the real value of the IETF. Yes, both of those predate the IETF as we now 
know it, but had the IETF existed then, they would have been very 
appropriate in it. Today's counterparts include papers like some I 
currently have posted (not intending to self-aggrandize, but they're the 
one's I know most quickly). The posting of questions, problems, and ideas 
is perhaps *the* key part; standards are from my perspective only one of 
the products, and perhaps a byproduct. 
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBQAnERm4xHWxyLJtDEQJOBACg6gngigXoA5jexovqdRHLbe1ELCYAnAgS
AYYF5UNWFVRChpzlkjUY1gXa
=Qa0x
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Sat Jan 17 20:29:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22994
	for <ietf-web-archive@odin.ietf.org>; Sat, 17 Jan 2004 20:29:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ai1Wn-00020Z-5W
	for ietf-list@asgard.ietf.org; Sat, 17 Jan 2004 20:15:01 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ai1Vy-0001zp-V9
	for ietf@asgard.ietf.org; Sat, 17 Jan 2004 20:14:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22611
	for <ietf@ietf.org>; Sat, 17 Jan 2004 20:14:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ai1Vn-0007Ec-00
	for ietf@ietf.org; Sat, 17 Jan 2004 20:13:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ai1TD-00078L-00
	for ietf@ietf.org; Sat, 17 Jan 2004 20:11:19 -0500
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ai1SD-00072E-00
	for ietf@ietf.org; Sat, 17 Jan 2004 20:10:17 -0500
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id MAA602591;
	Sun, 18 Jan 2004 12:09:15 +1100 (EST)
Message-ID: <4009DCBA.24380065@swin.edu.au>
Date: Sun, 18 Jan 2004 12:09:15 +1100
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The IETF Mission [Re: Summary status of change efforts - UpdatedWeb 
 page]
References: <Pine.LNX.4.44.0401171150270.11109-100000@netcore.fi>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I'm not sure I see the ambiguities you assert.

Pekka Savola wrote:
	[..]
>  - These are so overly broad statements that they're close to unusable
> UNLESS you believe IETF is just a rubber-stamping standards
> organization.  For example, what constitutes "deploying networks"?
> IETF certainly shouldn't be go digging fibers, or give advice on how
> to dig fibers.
> 
> But as the vast evidence makes it clear, most ISPs do a very lousy job
> of deploying networks *properly*, causing harm to the Internet as a
> whole.  Wouldn't it be somewhat in the IETF's business to try to give
> advice (using BCP and Info documents) how to do it better?

I can't see your problem here. Clearly we know what it means to
actually deploy a network. Saying that the IETF does not deploy
networks in no way inhibits the IETF from giving guidance to good
(or purported to be good) engineering practise and trade-offs.

So Harald's observation about IETF not deploying networks is spot on.

	[..]
> Similarly, "building products" is vague, and may become problematic
> especially if one believes the IETF (however that decision could be
> reached is another can of worms entirely) has the power to say "No, we
> don't want to standardize FOO" or "No, we don't want to standardize
> the means to do BAR using the approach FOO".  Then the vendor could
> argue it's not the IETF's business to tell how it should build it's
> products.

"Building products" isn't vague at all. By your own example the IETF
isn't building any product, although it might be a nuisance to the marketing
arm of any vendor who wished to build a product that incorporated "non approved"
protocols, techniques or technologies. No problem, vendors do that all
the time. The IETF still does not build products.

	[..]
> "Regulating the Internet" is also not problem-free.  If the IETF
> decides not to standarize or publish something which is considered to
> be a Bad Thing (e.g., NAT for IPv6, Wiretapping mechanisms, VOIP
> Backdoors, etc.etc.) -- couldn't one argue that the IETF is basically
> regulating the Internet by some means?

"Regulation" has a specific conotation here of government legislation,
rules or guidelines with operational/legal implications. Having influence
is not the same as regulating, and so Harald's characterisation here
is quite right too. There's no ambiguity. The IETF cannot prevent
things from happening even if does go to great lengths to state
considered, expert, technical opinions.

cheers,
gja
-- 
Grenville Armitage
http://caia.swin.edu.au
I come from a LAN downunder.



From owner-ietf@ietf.org  Sun Jan 18 02:03:12 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02566
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 02:03:12 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ai6ms-0006Ml-Iq
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 01:51:58 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ai6m6-0006Ly-D3
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 01:51:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28703
	for <ietf@ietf.org>; Sun, 18 Jan 2004 01:50:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ai6lp-0003Js-00
	for ietf@ietf.org; Sun, 18 Jan 2004 01:50:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ai6jA-0003FV-00
	for ietf@ietf.org; Sun, 18 Jan 2004 01:48:08 -0500
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ai6hv-0003BO-00
	for ietf@ietf.org; Sun, 18 Jan 2004 01:46:52 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i0I6jbH28033;
	Sun, 18 Jan 2004 08:45:37 +0200
Date: Sun, 18 Jan 2004 08:45:37 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Fred Baker <fred@cisco.com>
cc: ietf@ietf.org
Subject: Re: The IETF Mission [Re: Summary status of change efforts -  Updated
 Web page]
In-Reply-To: <6.0.1.1.2.20040117103457.0466fc00@mira-sjc5-b.cisco.com >
Message-ID: <Pine.LNX.4.44.0401180842440.27982-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

On Sat, 17 Jan 2004, Fred Baker wrote:
> At 04:26 AM 1/17/2004, Pekka Savola wrote:
> >"The purpose of the IETF is to create high quality, relevant, and
> >timely standards for the Internet."
> 
> I think I would state it in these words:
> 
>     "The Internet Engineering Task Force provides a forum for the
>     discussion and development of white papers and specifications
>     for the engineering issues of the Internet."
[...]

I pretty much agree with all you're stating -- thanks for spelling it 
out.

> The posting of questions, problems, and ideas 
> is perhaps *the* key part; standards are from my perspective only one of 
> the products, and perhaps a byproduct.

Right on.  This is the core of relevant, high-quality work I think.  
You could capture of some of those issues in the standards themselves,
if you really wanted, but a longer and more in-depth discussion seems
to belong in some other form of documents.

-- 
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  Sun Jan 18 02:08:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08909
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 02:08:29 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ai6yU-0006jX-H4
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 02:03:58 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ai6y1-0006g6-UE
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 02:03:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02906
	for <ietf@ietf.org>; Sun, 18 Jan 2004 02:03:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ai6xz-0003i6-00
	for ietf@ietf.org; Sun, 18 Jan 2004 02:03:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ai6wY-0003gf-00
	for ietf@ietf.org; Sun, 18 Jan 2004 02:01:58 -0500
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ai6vq-0003da-00
	for ietf@ietf.org; Sun, 18 Jan 2004 02:01:14 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i0I6xiN28109;
	Sun, 18 Jan 2004 08:59:44 +0200
Date: Sun, 18 Jan 2004 08:59:44 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: grenville armitage <garmitage@swin.edu.au>
cc: ietf@ietf.org
Subject: Re: The IETF Mission [Re: Summary status of change efforts - UpdatedWeb
  page]
In-Reply-To: <4009DCBA.24380065@swin.edu.au>
Message-ID: <Pine.LNX.4.44.0401180845480.27982-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sun, 18 Jan 2004, grenville armitage wrote:
> I'm not sure I see the ambiguities you assert.

I think this is because you use the "narrow interpretation" (e.g., the
actual network deployment) of the terms -- which is fine.  My problem
with that, though, is that people can have a "broad interpretation"  
(e.g., anything regarding network deployment, including giving advice)
as well -- and the terms used are chosen such that the reader does not
know which one is correct.  This creates confusion.

> Pekka Savola wrote:
> 	[..]
> >  - These are so overly broad statements that they're close to unusable
> > UNLESS you believe IETF is just a rubber-stamping standards
> > organization.  For example, what constitutes "deploying networks"?
> > IETF certainly shouldn't be go digging fibers, or give advice on how
> > to dig fibers.
> > 
> > But as the vast evidence makes it clear, most ISPs do a very lousy job
> > of deploying networks *properly*, causing harm to the Internet as a
> > whole.  Wouldn't it be somewhat in the IETF's business to try to give
> > advice (using BCP and Info documents) how to do it better?
> 
> I can't see your problem here. Clearly we know what it means to
> actually deploy a network. Saying that the IETF does not deploy
> networks in no way inhibits the IETF from giving guidance to good
> (or purported to be good) engineering practise and trade-offs.

Right, actual deployment (digging fibers, purchasing links, installing
routers, configuring the network equipment, making network plans,
etc.) doesn't seem to be in IETF's purview.  But it is not clear with
the above "broad" vs "strict" interpretation, whether "deploying
networks" includes advice on some aspects of deploying networks as
well.

A statement like "we don't deploy networks because others do it 
better" implies that the others know how to deploy networks better, 
and do deploy them better, and the IETF does not have expertise for 
that.  And if the others know how to deploy the network better, is the 
IETF the right body, with expertise, to give advice on how to do it?  

Knowing how to do something, and actually doing it, are closely tied
into each other.

With a broad interpretation, both could be excluded.  With a narrow
interpretation, maybe only actually doing it could be excluded (which
would be natural as the IETF participants are not volunteers to go
deploying networks... :-).

[[ the similar arguments apply to building products and regulating the 
Internet, so I don't repeat them again. ]]

-- 
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  Sun Jan 18 13:56:58 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27818
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 13:56:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiHss-0000DM-Ii
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 13:42:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiHry-0000D0-BA
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 13:41:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27561
	for <ietf@ietf.org>; Sun, 18 Jan 2004 13:41:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiHrx-0002Bb-00
	for ietf@ietf.org; Sun, 18 Jan 2004 13:41:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiHr0-00029l-00
	for ietf@ietf.org; Sun, 18 Jan 2004 13:40:59 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiHq8-00027i-00
	for ietf@ietf.org; Sun, 18 Jan 2004 13:40:04 -0500
Received: (from braden@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i0IIdpS14922;
	Sun, 18 Jan 2004 10:39:51 -0800 (PST)
Date: Sun, 18 Jan 2004 10:39:51 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Message-Id: <200401181839.i0IIdpS14922@boreas.isi.edu>
To: fred@cisco.com
Subject: Re: The IETF Mission
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

  *> 
  *> Lets take an example. I have been involved in QoS work, and there have been
  *> a number of specifications written on the subject; much of that started 
  *> with white papers, including especially
  *> 
  *> 0896 Congestion control in IP/TCP internetworks. J. Nagle.
  *>       Jan-06-1984. (Format: TXT=26782 bytes) (Status: UNKNOWN)
  *> 
  *> 0970 On packet switches with infinite storage. J. Nagle. Dec-01-1985.
  *>       (Format: TXT=35316 bytes) (Status: UNKNOWN)
  *> 

Fred,

Please note that these references are to published RFCs, which are
available in perpetuity in the official document archive of the
Internet community, the RFC series.  It is an illustration that
publishing significant white papers and discussion papers as RFCs has
real value, which is being lost lost in what you correctly characterize
as an over-emphasis on "standards".  We are letting the marketing types
rule.

  *> 
  *> To leave white papers and internet drafts, many of which are never 
  *> published as RFCs and a relatively small portion ever become standards, 
  *> out, and to leave the discussion part out is, I think, to leave out much of
  *> the real value of the IETF. Yes, both of those predate the IETF as we now 
  *> know it, but had the IETF existed then, they would have been very 
  *> appropriate in it. Today's counterparts include papers like some I 
  *> currently have posted (not intending to self-aggrandize, but they're the 
  *> one's I know most quickly). The posting of questions, problems, and ideas 
  *> is perhaps *the* key part; standards are from my perspective only one of 
  *> the products, and perhaps a byproduct. 


Yes. So let's consciously endeavor to ensure that sigificant
non-standards documents -- responsible position papers, white papers,
new ideas, etc.  -- become RFCs.  (Making Internet Drafts into an
archival series seems like a terrible idea to me, but that is a
different topic.)

Bob Braden



From owner-ietf@ietf.org  Sun Jan 18 15:01:43 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29139
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 15:01:43 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiIza-00016m-Lk
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 14:53:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiIyf-00016D-0d
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 14:52:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28954
	for <ietf@ietf.org>; Sun, 18 Jan 2004 14:52:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiIyd-0005N3-00
	for ietf@ietf.org; Sun, 18 Jan 2004 14:52:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiIxf-0005Li-00
	for ietf@ietf.org; Sun, 18 Jan 2004 14:51:56 -0500
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiIwm-0005K5-00
	for ietf@ietf.org; Sun, 18 Jan 2004 14:51:00 -0500
Received: from inet-vrs-04.redmond.corp.microsoft.com ([157.54.8.149]) by mail4.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sun, 18 Jan 2004 11:50:28 -0800
Received: from 157.54.6.150 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Sun, 18 Jan 2004 11:50:31 -0800
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);
	 Sun, 18 Jan 2004 11:50:30 -0800
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by RED-IMC-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sun, 18 Jan 2004 11:50:47 -0800
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Sun, 18 Jan 2004 11:50:16 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7150.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: The IETF Mission
Date: Sun, 18 Jan 2004 11:50:32 -0800
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA06F38BCE@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: The IETF Mission
Thread-Index: AcPd9WkTmSvFCyGzRMWlo9Agq0FslAABq0tg
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Bob Braden" <braden@ISI.EDU>, <fred@cisco.com>
Cc: <ietf@ietf.org>
X-OriginalArrivalTime: 18 Jan 2004 19:50:16.0922 (UTC) FILETIME=[4BC53BA0:01C3DDFC]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


> Yes. So let's consciously endeavor to ensure that sigificant
> non-standards documents -- responsible position papers, white papers,
> new ideas, etc.  -- become RFCs.  (Making Internet Drafts into an
> archival series seems like a terrible idea to me, but that is a
> different topic.)

I could not agree more!
Obviously, we need some amount of peer review before a "white paper
draft" becomes a "white paper RFC", but I guess we know how to do that.

-- Christian Huitema



From owner-ietf@ietf.org  Sun Jan 18 15:34:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01523
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 15:34:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiJWU-0001wt-A5
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 15:27:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiJVo-0001wC-NZ
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 15:27:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01203
	for <ietf@ietf.org>; Sun, 18 Jan 2004 15:27:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiJVn-0006yR-00
	for ietf@ietf.org; Sun, 18 Jan 2004 15:27:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiJUu-0006uC-00
	for ietf@ietf.org; Sun, 18 Jan 2004 15:26:17 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiJTx-0006mn-00
	for ietf@ietf.org; Sun, 18 Jan 2004 15:25:17 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0IKOXr04171;
	Sun, 18 Jan 2004 12:24:33 -0800
X-mProtect: <200401182024> Nokia Silicon Valley Messaging Protection
Received: from pc-b165.wlan.inet.fi (194.89.117.165, claiming to be "spruce.nokia.com")
	by darkstar.iprg.nokia.com smtpdLGrEkb; Sun, 18 Jan 2004 12:24:31 PST
Message-Id: <4.3.2.7.2.20040118121849.00b97ae8@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 18 Jan 2004 12:21:49 -0800
To: Christian Huitema <huitema@windows.microsoft.com>
From: Bob Hinden <bob.hinden@nokia.com>
Subject: RE: The IETF Mission
Cc: Bob Braden <braden@ISI.EDU>, <fred@cisco.com>, ietf@ietf.org
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA06F38BCE@WIN-MSG-10.wingro
 up.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 11:50 AM 1/18/2004, Christian Huitema wrote:

> > Yes. So let's consciously endeavor to ensure that sigificant
> > non-standards documents -- responsible position papers, white papers,
> > new ideas, etc.  -- become RFCs.  (Making Internet Drafts into an
> > archival series seems like a terrible idea to me, but that is a
> > different topic.)
>
>I could not agree more!
>Obviously, we need some amount of peer review before a "white paper
>draft" becomes a "white paper RFC", but I guess we know how to do that.

I agree with this as well.  I think it is important to keep the RFC series 
available for significant non-standards documents and IETF standards.

Bob




From owner-ietf@ietf.org  Sun Jan 18 16:14:09 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02792
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 16:14:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiK7G-0002iY-6b
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 16:05:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiK6M-0002hp-Sh
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 16:04:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02652
	for <ietf@ietf.org>; Sun, 18 Jan 2004 16:04:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiK6L-0001f2-00
	for ietf@ietf.org; Sun, 18 Jan 2004 16:04:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiK5O-0001dn-00
	for ietf@ietf.org; Sun, 18 Jan 2004 16:03:59 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiK4s-0001d2-00
	for ietf@ietf.org; Sun, 18 Jan 2004 16:03:27 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0IL35kw002584;
	Sun, 18 Jan 2004 22:03:05 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <200401181839.i0IIdpS14922@boreas.isi.edu>
References: <200401181839.i0IIdpS14922@boreas.isi.edu>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <BE754971-49F9-11D8-BA88-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: The IETF Mission
Date: Sun, 18 Jan 2004 22:03:19 +0100
To: Bob Braden <braden@ISI.EDU>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 18-jan-04, at 19:39, Bob Braden wrote:

> So let's consciously endeavor to ensure that sigificant
> non-standards documents -- responsible position papers, white papers,
> new ideas, etc.  -- become RFCs.

Sigh. Even more RFCs. Pretty soon we're going to need a 32-bit RFC 
number space.

> (Making Internet Drafts into an archival series seems like a terrible 
> idea to me, but that is a different topic.)

Actually it's pretty much the same topic, as there needs to be a way to 
preserve drafts that are important in some way or another. One way to 
do this would be to make all drafts that are worth preserving an RFC. 
This means drastically lowering the standards for what can be published 
as an RFC. (Note that this brings us closer to what RFCs used to be 15 
years or so ago.) Another way to do it would be to simply archive all 
drafts. I agree this has the unpleasant side effect that all those 
drafts that become obsolete (or are so from inception) stay around 
forever. But it's still better than the current situation, where making 
something an RFC means an incredible amount of work for many people, 
but not doing it means that ideas that may have taken days or weeks to 
write down are pretty much lost forever. Even the emails announcing the 
availability of new drafts are archived longer.

I think there is some middle ground where expired drafts that are 
referred to in non-expired drafts are kept, as well as any drafts that 
are implemented and possibly drafts that a certain n number of people 
feel are interesting in some way.




From owner-ietf@ietf.org  Sun Jan 18 17:08:31 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04080
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 17:08:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiL0P-0003gr-T8
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 17:02:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiKzY-0003fw-KB
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 17:02:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03792
	for <ietf@ietf.org>; Sun, 18 Jan 2004 17:01:58 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiKzW-0003io-00
	for ietf@ietf.org; Sun, 18 Jan 2004 17:01:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiKxv-0003dH-00
	for ietf@ietf.org; Sun, 18 Jan 2004 17:00:19 -0500
Received: from h80ad25ab.async.vt.edu ([128.173.37.171] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiKxK-0003ZM-00
	for ietf@ietf.org; Sun, 18 Jan 2004 16:59:42 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i0ILxV3E013698;
	Sun, 18 Jan 2004 16:59:31 -0500
Message-Id: <200401182159.i0ILxV3E013698@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Bob Braden <braden@ISI.EDU>
Cc: fred@cisco.com, ietf@ietf.org
Subject: Re: The IETF Mission 
In-Reply-To: Your message of "Sun, 18 Jan 2004 10:39:51 PST."
             <200401181839.i0IIdpS14922@boreas.isi.edu> 
References: <200401181839.i0IIdpS14922@boreas.isi.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-740012163P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sun, 18 Jan 2004 16:59:31 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sun, 18 Jan 2004 10:39:51 PST, Bob Braden said:

> Yes. So let's consciously endeavor to ensure that sigificant
> non-standards documents -- responsible position papers, white papers,
> new ideas, etc.  -- become RFCs.  (Making Internet Drafts into an
> archival series seems like a terrible idea to me, but that is a
> different topic.)

Out of curiosity, where would the I-D that described Mail-Followup-To: fall in
this spectrum?  This is an example of something that's widely deployed(*), and
definitely not a "non-standard", but we (for whatever reason) never got an RFC
out the door.

There's been other good ideas, or reasonable starts at same, that have expired
out of the I-D directory and never been published.  And unfortunately for the
person doing the literature review, this is a big problem, because the drafts
that *aren't* published are an important resource for ideas, both good and bad.
Yes, you still get to dig for which of the two it was, but in either case, finding
that the same (or similar idea) has been proposed before can be important... 

(*) So far this year, I've received 598 pieces of mail with one, out of 9,017
mails I saved the headers for (which included all the spam I've seen so far).
So in at least some communities, it's being used by a significant percentage of
users.  Compare to 559 for multipart/signed, for which (a) there *is* an RFC
and (b) 150 of which were my own postings to mailing lists...


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

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

iD8DBQFACwHDcC3lWbTT17ARAr8aAJ9z13DU8qZmC99mYGgXIfkfGNmeSACeJCjh
sr3Gm04OAHBjPgQFgCa6Xzw=
=e1Qt
-----END PGP SIGNATURE-----

--==_Exmh_-740012163P--



From owner-ietf@ietf.org  Sun Jan 18 17:27:11 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04862
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 17:27:11 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiLHp-0004Io-Pt
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 17:20:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiLGz-0004IB-Rs
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 17:20:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04515
	for <ietf@ietf.org>; Sun, 18 Jan 2004 17:19:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiLGy-0004r7-00
	for ietf@ietf.org; Sun, 18 Jan 2004 17:20:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiLG0-0004ia-00
	for ietf@ietf.org; Sun, 18 Jan 2004 17:19:00 -0500
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiLF5-0004ek-00
	for ietf@ietf.org; Sun, 18 Jan 2004 17:18:04 -0500
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id JAA671061;
	Mon, 19 Jan 2004 09:17:31 +1100 (EST)
Message-ID: <400B05FB.B4D55C8D@swin.edu.au>
Date: Mon, 19 Jan 2004 09:17:31 +1100
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: The IETF Mission
References: <200401181839.i0IIdpS14922@boreas.isi.edu> <BE754971-49F9-11D8-BA88-000A95CD987A@muada.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum wrote:
> 
	[..]
> Actually it's pretty much the same topic, as there needs to be a way to
> preserve drafts that are important in some way or another.

If it is important, it'll progress the work of some group in the
IETF and be archived as an RFC. If it (the I-D) doesn't capture work
well enough to be archived as an RFC then it ought to fade from IETF
I-D storage. If the authors (or someone else) feels strongly that there's
still material in their I-D of value, 'archiving' it on a personal website
for google to find.

Or put differently, it is important for the IETF's collective clarity of
focus that IETF-hosted I-Ds decay and disappear if not actively maintained.
Whether or not an interested 3rd party (or I-D authors) maintain their I-Ds
beyond the expiration date is a separate issue.

> One way to
> do this would be to make all drafts that are worth preserving an RFC.
> This means drastically lowering the standards for what can be published
> as an RFC.

Is the standard for Informational currently that onerous?

> Another way to do it would be to simply archive all
> drafts. I agree this has the unpleasant side effect that all those
> drafts that become obsolete (or are so from inception) stay around
> forever.

Yes, that's a major problem. Organizations need to clean out their
clutter on a regular basis just like individuals do.

> But it's still better than the current situation, where making
> something an RFC means an incredible amount of work for many people,
> but not doing it means that ideas that may have taken days or weeks to
> write down are pretty much lost forever. Even the emails announcing the
> availability of new drafts are archived longer.

Then perhaps we encourage WG members to post a summary of their non-RFC
ideas to the WG mailing list around the time when work is wrapping up.
The ideas will thus survive (to be found through Google) as long as the mailing
list archive is around. If the author wants something longer lived, there's always
personal websites.

cheers,
gja
-- 
Grenville Armitage
http://caia.swin.edu.au
I come from a LAN downunder.



From owner-ietf@ietf.org  Sun Jan 18 18:43:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08075
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 18:43:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiMRR-0005WL-7M
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 18:34:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiMLx-0005Ty-W1
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 18:29:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07697
	for <ietf@ietf.org>; Sun, 18 Jan 2004 18:29:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiMLw-0007WB-00
	for ietf@ietf.org; Sun, 18 Jan 2004 18:29:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiML2-0007T0-00
	for ietf@ietf.org; Sun, 18 Jan 2004 18:28:16 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiMKJ-0007Q3-00
	for ietf@ietf.org; Sun, 18 Jan 2004 18:27:32 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0INR9kw004475;
	Mon, 19 Jan 2004 00:27:10 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <400B05FB.B4D55C8D@swin.edu.au>
References: <200401181839.i0IIdpS14922@boreas.isi.edu> <BE754971-49F9-11D8-BA88-000A95CD987A@muada.com> <400B05FB.B4D55C8D@swin.edu.au>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DED4F359-4A0D-11D8-BA88-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: The IETF Mission
Date: Mon, 19 Jan 2004 00:27:24 +0100
To: grenville armitage <garmitage@swin.edu.au>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 18-jan-04, at 23:17, grenville armitage wrote:

>> Actually it's pretty much the same topic, as there needs to be a way 
>> to
>> preserve drafts that are important in some way or another.

> If it is important, it'll progress the work of some group in the
> IETF and be archived as an RFC.

Really. What's the number for the GSE RFC again? Even current work such 
as draft-ietf-idr-as4bytes-07.txt stays in draft limbo for years.

> If it (the I-D) doesn't capture work
> well enough to be archived as an RFC then it ought to fade from IETF
> I-D storage.

I agree it would be nice if things worked this way but they don't.

> If the authors (or someone else) feels strongly that there's
> still material in their I-D of value, 'archiving' it on a personal 
> website
> for google to find.

Again, this simply doesn't work well enough in practice. Very little 
web content stays in the same place for many years, and for a variety 
of reasons, some things can be incredibly hard to search for in search 
engines.

>> One way to
>> do this would be to make all drafts that are worth preserving an RFC.
>> This means drastically lowering the standards for what can be 
>> published
>> as an RFC.

> Is the standard for Informational currently that onerous?

I guess I'll have to find out...

>> Another way to do it would be to simply archive all
>> drafts. I agree this has the unpleasant side effect that all those
>> drafts that become obsolete (or are so from inception) stay around
>> forever.

> Yes, that's a major problem. Organizations need to clean out their
> clutter on a regular basis just like individuals do.

This argument is bogus as long as mailing list archives for stuff like 
draft announcements are kept.

> Then perhaps we encourage WG members to post a summary of their non-RFC
> ideas to the WG mailing list around the time when work is wrapping up.
> The ideas will thus survive (to be found through Google) as long as 
> the mailing list archive is around.

Searching in such an archive is only possible if you know the search 
terms in advance. For instance, the draft I mentioned earlier isn't 
easily found when searching for "32 bit as number".




From owner-ietf@ietf.org  Sun Jan 18 19:24:53 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09122
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 19:24:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiN48-0006J9-UG
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 19:14:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiN3T-0006IF-Eq
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 19:14:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08875
	for <ietf@ietf.org>; Sun, 18 Jan 2004 19:14:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiN3R-0001nW-00
	for ietf@ietf.org; Sun, 18 Jan 2004 19:14:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiN2W-0001lq-00
	for ietf@ietf.org; Sun, 18 Jan 2004 19:13:13 -0500
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiN2L-0001jk-00
	for ietf@ietf.org; Sun, 18 Jan 2004 19:13:01 -0500
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id LAA684973;
	Mon, 19 Jan 2004 11:12:29 +1100 (EST)
Message-ID: <400B20ED.F6DDB02F@swin.edu.au>
Date: Mon, 19 Jan 2004 11:12:29 +1100
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: The IETF Mission
References: <200401181839.i0IIdpS14922@boreas.isi.edu> <BE754971-49F9-11D8-BA88-000A95CD987A@muada.com> <400B05FB.B4D55C8D@swin.edu.au> <DED4F359-4A0D-11D8-BA88-000A95CD987A@muada.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum wrote:
> 
> On 18-jan-04, at 23:17, grenville armitage wrote:
	[.]
> > If it is important, it'll progress the work of some group in the
> > IETF and be archived as an RFC.
> 
> Really. What's the number for the GSE RFC again? Even current work such
> as draft-ietf-idr-as4bytes-07.txt stays in draft limbo for years.

I suspect this speaks more to the focus of the authors of those documents
than any particular lack in the I-D development process. IMO, of course :)

	[..]
> > Yes, that's a major problem. Organizations need to clean out their
> > clutter on a regular basis just like individuals do.
> 
> This argument is bogus as long as mailing list archives for stuff like
> draft announcements are kept.

I don't quite see it that way. A mail list archive quite clearly conveys
the sense of "this is a snapshot in time of things in the past" whereas our
I-D repository has/had the semantics of "this is current thinking of someone,
somewhere in the IETF" (for current <= 6 months). So I believe in mail
archives far more than I believe in permanent I-D archives.

	[..]
> Searching in such an archive is only possible if you know the search
> terms in advance. For instance, the draft I mentioned earlier isn't
> easily found when searching for "32 bit as number".

I can't see how this would be improved by storing I-Ds in a well know,
permanent location. You'd still have trouble searching inside the archive
on ambiguous search terms.

cheers,
gja
-- 
Grenville Armitage
http://caia.swin.edu.au
I come from a LAN downunder.



From owner-ietf@ietf.org  Sun Jan 18 22:09:37 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13628
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 22:09:37 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiPYx-0008OV-Ou
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 21:54:51 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiPYK-0008Np-DX
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 21:54:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13381
	for <ietf@ietf.org>; Sun, 18 Jan 2004 21:54:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiPYI-0001MD-00
	for ietf@ietf.org; Sun, 18 Jan 2004 21:54:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiPXQ-0001Jb-00
	for ietf@ietf.org; Sun, 18 Jan 2004 21:53:16 -0500
Received: from [63.247.76.254] (helo=montage.altserver.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiPWZ-0001En-00
	for ietf@ietf.org; Sun, 18 Jan 2004 21:52:23 -0500
Received: from f01m-34-229.d0.club-internet.fr ([212.195.225.229] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1AiPWR-0001Wo-OZ; Sun, 18 Jan 2004 18:52:16 -0800
Message-Id: <6.0.1.1.2.20040118065950.04691b10@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sun, 18 Jan 2004 07:09:20 +0100
To: Fred Baker <fred@cisco.com>, Pekka Savola <pekkas@netcore.fi>
From: jfcm <info@utel.net>
Subject: Re: The IETF Mission [Re: Summary status of change efforts -
  Updated Web page]
Cc: ietf@ietf.org
In-Reply-To: <6.0.1.1.2.20040117103457.0466fc00@mira-sjc5-b.cisco.com >
References: <405441934.1074293627@localhost>
 <Pine.LNX.4.44.0401171150270.11109-100000@netcore.fi>
 <6.0.1.1.2.20040117103457.0466fc00@mira-sjc5-b.cisco.com >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,DATE_IN_PAST_12_24 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 00:24 18/01/04, Fred Baker wrote:
>But it originates with a very real and very damaging operational problem, 
>that of BSD 4.1's predilection to TCP Silly Window Syndrome and an 
>operator's desire to minimize the impact of that on competing data traffic.

Dear Fred,
thank you for your inputs. You point out the IETF problems I see. You say 
developers and users may meet. And the example you take is an "operator" 
(your word) predating IETF/IAB because you know it better.  This exactly 
documents the four problems I point out.

1. you describe IETF as only a forum, like "Nature" for the Science 
community. I would say it is more. It certainly is a place of dialog 
between techies and operators (I agree with your meaning of the word, John 
Klensin rebuked, of someone who operates something in using an IETF 
deliverable).

2. but it is not the polylog (the very nature of the internet) we need, 
with all the users (name them @large?) content providers, politics, 
business etc. So there is a split we often observe in here between reality 
and assumptions. You answered me that there was indeed some experimentation 
in the Standard track. I responded there is no global societal acceptance 
(including economic model, general policy etc.) nor governantal (will the 
governance accept the proposed solutions and will it be able to manage them?).

3. as such IETF it is not a place for major innovations. This calls for 
architects. The main problem of IETF is IAB and the lack of an Internet 
global model and of global development targets. You use an example from a 
time when major changes could be made, just  because they were correct. 
Today the size of the network prevents to do that easily. This is to go be 
correct direction and momentum.

4. you use examples you know. You document this way a major problem. You 
should be able to use any subject as an example. A person like you is 
trained to understand a technical state of the art summary easily in a few 
hours. But there are none of them. Read all the RFCs and the archive of 
their closed WGs.


- IETF for geeks and internuts only.
- awkward with users (demands, acceptances and usages  brainware)
- no IAB vision based upon a commonly accepted global model
- no state of the art summaries and organized RFC comments and 
experimentation reports


Experience is the mistakes of someone with memory. Why not to analyze the 
IDNA (now confirmed failure) and to try to understand how not to repeat it? 
(I opposed IDNA all the way long, but I am the first to say it was a 
complex work achieved by a hard working WG). It was useful in uncovering 
problems to be solved and some solution elements.

jfc





From owner-ietf@ietf.org  Sun Jan 18 22:40:35 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14512
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 22:40:35 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiQ9k-0000nc-Ul
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 22:32:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiQ95-0000mm-OU
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 22:32:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14324
	for <ietf@ietf.org>; Sun, 18 Jan 2004 22:32:09 -0500 (EST)
From: jstracke@INCENTIVESYSTEMS.COM
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiQ94-0003Av-00
	for ietf@ietf.org; Sun, 18 Jan 2004 22:32:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiQ86-00037h-00
	for ietf@ietf.org; Sun, 18 Jan 2004 22:31:10 -0500
Received: from pc1243.law.usyd.edu.au ([129.78.136.142] helo=patrick)
	by ietf-mx with smtp (Exim 4.12)
	id 1AiQ78-00032n-00
	for ietf@IETF.ORG; Sun, 18 Jan 2004 22:30:11 -0500
Date: Mon, 19 Jan 2004 14:26:46 +1000
To: ietf@ietf.org
Subject: Hi
Message-ID: <jprlhmmlitaarkxkqds@INCENTIVESYSTEMS.COM>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------117307011682843"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=MICROSOFT_EXECUTABLE,
	NO_REAL_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

----------117307011682843
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

 Test =)
qxbavnirg
--
Test, yep.

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

[Filename: wgjpkhbavno.exe, Content-Type: application/x-msdownload]
The attachment file in the message has been removed by eManager.

----------117307011682843--




From owner-ietf@ietf.org  Sun Jan 18 22:54:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14980
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 22:54:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiQQB-0001Nb-Ch
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 22:49:51 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiQPa-0001Mn-5K
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 22:49:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14794
	for <ietf@ietf.org>; Sun, 18 Jan 2004 22:49:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiQPY-0004EH-00
	for ietf@ietf.org; Sun, 18 Jan 2004 22:49:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiQOg-0004Cd-00
	for ietf@ietf.org; Sun, 18 Jan 2004 22:48:18 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiQOG-0004Ah-00
	for ietf@ietf.org; Sun, 18 Jan 2004 22:47:52 -0500
Received: from edison.cisco.com (edison.cisco.com [171.71.180.109])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0J3lLGN006351;
	Sun, 18 Jan 2004 19:47:21 -0800 (PST)
Received: from cisco.com (sjc-vpn3-1186.cisco.com [10.21.68.162]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id TAA15689; Sun, 18 Jan 2004 19:47:20 -0800 (PST)
Message-ID: <400B5348.1000509@cisco.com>
Date: Sun, 18 Jan 2004 19:47:20 -0800
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040115
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bob Braden <braden@ISI.EDU>
CC: fred@cisco.com, ietf@ietf.org
Subject: Re: The IETF Mission
References: <200401181839.i0IIdpS14922@boreas.isi.edu>
In-Reply-To: <200401181839.i0IIdpS14922@boreas.isi.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bob,

I agree that many works of great value can be found in early RFCs.  But 
here's my question to you: if the focus is too much on standards, how do 
  we scale the process so that we can have great works that are NOT 
standards?  Clearly neither the IESG nor the IETF need be involved in 
that process, so long as the work does not misrepresent itself as a 
standard or other IETF-type work.

Now, you may say that the RFC Editor should take that job.  Okay.  Then 
I presume we need to scale the RFC Editor to this sort of task.  Another 
way of looking at this would be to create some sort of refereed track. 
That would be fine, but then it seems to me that the day of ASCII has to 
really come to an end (IMHO). (and with the mention of ASCII, why do I 
feel as though I've just violated Godwin's Law?)

By the way, I think we should also ask where our role ends and where the 
role of SIGCOMM and the like pick up (he says trying to pay his dues ;-).

Eliot

>   *> 
>   *> Lets take an example. I have been involved in QoS work, and there have been
>   *> a number of specifications written on the subject; much of that started 
>   *> with white papers, including especially
>   *> 
>   *> 0896 Congestion control in IP/TCP internetworks. J. Nagle.
>   *>       Jan-06-1984. (Format: TXT=26782 bytes) (Status: UNKNOWN)
>   *> 
>   *> 0970 On packet switches with infinite storage. J. Nagle. Dec-01-1985.
>   *>       (Format: TXT=35316 bytes) (Status: UNKNOWN)
>   *> 
> 
> Fred,
> 
> Please note that these references are to published RFCs, which are
> available in perpetuity in the official document archive of the
> Internet community, the RFC series.  It is an illustration that
> publishing significant white papers and discussion papers as RFCs has
> real value, which is being lost lost in what you correctly characterize
> as an over-emphasis on "standards".  We are letting the marketing types
> rule.
> 
>   *> 
>   *> To leave white papers and internet drafts, many of which are never 
>   *> published as RFCs and a relatively small portion ever become standards, 
>   *> out, and to leave the discussion part out is, I think, to leave out much of
>   *> the real value of the IETF. Yes, both of those predate the IETF as we now 
>   *> know it, but had the IETF existed then, they would have been very 
>   *> appropriate in it. Today's counterparts include papers like some I 
>   *> currently have posted (not intending to self-aggrandize, but they're the 
>   *> one's I know most quickly). The posting of questions, problems, and ideas 
>   *> is perhaps *the* key part; standards are from my perspective only one of 
>   *> the products, and perhaps a byproduct. 
> 
> 
> Yes. So let's consciously endeavor to ensure that sigificant
> non-standards documents -- responsible position papers, white papers,
> new ideas, etc.  -- become RFCs.  (Making Internet Drafts into an
> archival series seems like a terrible idea to me, but that is a
> different topic.)
> 
> Bob Braden
> 
> 
> 



From owner-ietf@ietf.org  Sun Jan 18 23:25:28 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15937
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 23:25:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiQqJ-0002D6-7h
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 23:16:51 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiQpn-0002CN-B2
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 23:16:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15723
	for <ietf@ietf.org>; Sun, 18 Jan 2004 23:16:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiQpl-0005bp-00
	for ietf@ietf.org; Sun, 18 Jan 2004 23:16:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiQop-0005Yn-00
	for ietf@ietf.org; Sun, 18 Jan 2004 23:15:19 -0500
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiQnw-0005UP-00
	for ietf@ietf.org; Sun, 18 Jan 2004 23:14:25 -0500
Received: by sa.vix.com (Postfix, from userid 716)
	id 49D0218DE1; Mon, 19 Jan 2004 04:13:48 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: The IETF Mission
References: <200401181839.i0IIdpS14922@boreas.isi.edu>
	<400B5348.1000509@cisco.com>
From: Paul Vixie <vixie@vix.com>
Date: 19 Jan 2004 04:13:48 +0000
In-Reply-To: <400B5348.1000509@cisco.com>
Message-ID: <g3u12s60eb.fsf@sa.vix.com>
Lines: 23
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> ... Another way of looking at this would be to create some sort of
> refereed track.

Quis custodiet ipsos custodes?  (who shall govern the referees?)  note that
for a long time, peter salus begged the Computing Systems readership for
articles, and usenix ultimately closed it down due to lack of submissions.
i'm really not sure another refereed document series could find traction in
a world that already has an rfc editor, usenix, sigcomm, and so on.

> By the way, I think we should also ask where our role ends and where the 
> role of SIGCOMM and the like pick up (he says trying to pay his dues ;-).

while we at isc are hardly referees, i note with interest that one of the
publications at www.isc.org/tn was written by someone whose day job is
elsewhere, but he thought that "isc technote" was the logical place to put
this work, and we agreed.  with that remark i do not imply a solicitation,
but if isc and icann-secsac can each do their own document series, and if
the root name servers can publish c.root-servers.org/october21.txt as an
independent (non-series) document, then havn't we achieved gutenberg's goal,
doesn't everybody have their own printing press, and can't we either choose
an existing refereed forum for non-standards work, or just self-publish it?
-- 
Paul Vixie



From owner-ietf@ietf.org  Sun Jan 18 23:47:26 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16616
	for <ietf-web-archive@odin.ietf.org>; Sun, 18 Jan 2004 23:47:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiRFT-0002ze-4k
	for ietf-list@asgard.ietf.org; Sun, 18 Jan 2004 23:42:51 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiRCw-0002xM-Iu
	for ietf@asgard.ietf.org; Sun, 18 Jan 2004 23:40:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16398
	for <ietf@ietf.org>; Sun, 18 Jan 2004 23:40:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiRCu-0006j2-00
	for ietf@ietf.org; Sun, 18 Jan 2004 23:40:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiRBw-0006hP-00
	for ietf@ietf.org; Sun, 18 Jan 2004 23:39:13 -0500
Received: from sccrmhc11.comcast.net ([204.127.202.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiRBH-0006f5-00
	for ietf@ietf.org; Sun, 18 Jan 2004 23:38:31 -0500
Received: from dfnjgl21 (c-24-1-97-129.client.comcast.net[24.1.97.129])
          by comcast.net (sccrmhc11) with SMTP
          id <2004011904380101100j9qg6e>
          (Authid: sdawkins@comcast.net);
          Mon, 19 Jan 2004 04:38:01 +0000
Message-ID: <017901c3de46$0646b500$0400a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: "IETF Discussion" <ietf@ietf.org>
References: <200401181839.i0IIdpS14922@boreas.isi.edu> <BE754971-49F9-11D8-BA88-000A95CD987A@muada.com> <400B05FB.B4D55C8D@swin.edu.au>
Subject: Re: The IETF Mission
Date: Sun, 18 Jan 2004 22:38:02 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: "grenville armitage" <garmitage@swin.edu.au>
To: "IETF Discussion" <ietf@ietf.org>
Sent: Sunday, January 18, 2004 4:17 PM
Subject: Re: The IETF Mission


> Is the standard for Informational currently that onerous?

I'm curious what the average time-to-publish from first draft to RFC
for Informational RFCs is. And that would be a very interesting
statistic for this discussion.

Spencer




From owner-ietf@ietf.org  Mon Jan 19 00:32:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17591
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 00:32:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiRu6-00047M-Kk
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 00:24:50 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiRtX-00046V-QD
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 00:24:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17397
	for <ietf@ietf.org>; Mon, 19 Jan 2004 00:24:12 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiRtV-0000Vq-00
	for ietf@ietf.org; Mon, 19 Jan 2004 00:24:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiRsb-0000UW-00
	for ietf@ietf.org; Mon, 19 Jan 2004 00:23:17 -0500
Received: from h80ad2508.async.vt.edu ([128.173.37.8] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiRrz-0000T9-00
	for ietf@ietf.org; Mon, 19 Jan 2004 00:22:40 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i0J5MMJc026781;
	Mon, 19 Jan 2004 00:22:22 -0500
Message-Id: <200401190522.i0J5MMJc026781@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Paul Vixie <vixie@vix.com>
Cc: ietf@ietf.org
Subject: Re: The IETF Mission 
In-Reply-To: Your message of "Mon, 19 Jan 2004 04:13:48 GMT."
             <g3u12s60eb.fsf@sa.vix.com> 
References: <200401181839.i0IIdpS14922@boreas.isi.edu> <400B5348.1000509@cisco.com>
            <g3u12s60eb.fsf@sa.vix.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1510012894P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 19 Jan 2004 00:22:22 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Mon, 19 Jan 2004 04:13:48 GMT, Paul Vixie <vixie@vix.com>  said:

> independent (non-series) document, then havn't we achieved gutenberg's goal,
> doesn't everybody have their own printing press, and can't we either choose
> an existing refereed forum for non-standards work, or just self-publish it?

Having your idea published isn't equivalent to having your idea heard.

At least for well-known refereed forums, one can make the guess that "maybe
an ACM or IEEE or whatever has relevant publications".  Self-publication is
dependent on getting a good Google ranking (more or less).


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

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

iD8DBQFAC2mOcC3lWbTT17ARAhUkAJ49gcp5SAigaBmehd254al4V1lPyQCeOd7H
+T0feuncf3p1xAs1Vx4snY4=
=Be1i
-----END PGP SIGNATURE-----

--==_Exmh_-1510012894P--



From owner-ietf@ietf.org  Mon Jan 19 02:54:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04643
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 02:54:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiU4b-0006sd-TJ
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 02:43:49 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiU47-0006rb-UF
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 02:43:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04304
	for <ietf@ietf.org>; Mon, 19 Jan 2004 02:43:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiU45-000051-00
	for ietf@ietf.org; Mon, 19 Jan 2004 02:43:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiU39-00002l-00
	for ietf@ietf.org; Mon, 19 Jan 2004 02:42:20 -0500
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiU2L-0007ku-00
	for ietf@ietf.org; Mon, 19 Jan 2004 02:41:29 -0500
Received: by sa.vix.com (Postfix, from userid 716)
	id 4CE1C18DE5; Mon, 19 Jan 2004 07:40:56 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: The IETF Mission
References: <200401190522.i0J5MMJc026781@turing-police.cc.vt.edu>
From: Paul Vixie <vixie@vix.com>
Date: 19 Jan 2004 07:40:56 +0000
In-Reply-To: <200401190522.i0J5MMJc026781@turing-police.cc.vt.edu>
Message-ID: <g3ptdg5qt3.fsf@sa.vix.com>
Lines: 29
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> Having your idea published isn't equivalent to having your idea heard.

of course not.  most new documents in any series are ignored.  very few
people other than professional propeller-heads in ivory tower actually
read every article in acm-sigcomm or every rfc that comes out or whatever.
(computing systems, and the usenix proceedings, are notable exceptions,
with many hundreds of interested readers who at least skim everything
since it's likely that they know most of the program committee personally.)

> At least for well-known refereed forums, one can make the guess that
> "maybe an ACM or IEEE or whatever has relevant publications".
> Self-publication is dependent on getting a good Google ranking (more or
> less).

two things.  (1) people who want a reference will use google first, and
will search it thouroughly, before checking to see if acm or usenix or
ieee knows something that google hasn't heard yet.  (2) all publication
is dependent on promotion, whether the journal is refereed or whether
it's just up on the company web server.

so if you want to know that your pubs are available to interested parties,
put them where google can find them and you're done.  and if you want to
know that your pubs are skimmed by not-yet-interested parties, talk about
them in public and hope you motivate some lurkers.  (it's sort of like spam
in that way, though i wouldn't recommend trying to get a credit card number
before you show someone your content if you're using a list like ietf@ to
generate interest.)
-- 
Paul Vixie



From owner-ietf@ietf.org  Mon Jan 19 02:54:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04646
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 02:54:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiU6h-0006ub-GN
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 02:45:59 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiU64-0006ta-Lb
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 02:45:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04386
	for <ietf@ietf.org>; Mon, 19 Jan 2004 02:45:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiU62-0000A6-00
	for ietf@ietf.org; Mon, 19 Jan 2004 02:45:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiU54-00007t-00
	for ietf@ietf.org; Mon, 19 Jan 2004 02:44:19 -0500
Received: from kc-msxproto2.kc.umkc.edu ([134.193.143.155])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiU48-00005J-00
	for ietf@ietf.org; Mon, 19 Jan 2004 02:43:20 -0500
Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211]) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 19 Jan 2004 01:43:19 -0600
x-mimeole: Produced By Microsoft Exchange V6.5.6944.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: The IETF Mission
Date: Mon, 19 Jan 2004 01:42:09 -0600
Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B01108236@KC-MAIL4.kc.umkc.edu>
Thread-Topic: The IETF Mission
Thread-Index: AcPd9OgMeIeIJZSZTbS8q6MD/KaSoQAatasm
From: "Ayyasamy, Senthilkumar  \(UMKC-Student\)" <saq66@umkc.edu>
To: "Bob Braden" <braden@ISI.EDU>, <fred@cisco.com>
Cc: <ietf@ietf.org>
X-OriginalArrivalTime: 19 Jan 2004 07:43:19.0632 (UTC) FILETIME=[E840B500:01C3DE5F]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=FROM_ENDS_IN_NUMS autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> let's consciously endeavor to ensure that sigificant non-standards=20
> documents -- responsible position papers, white papers, new ideas,=20
> etc.  -- become RFCs.=20
=20
i.e. something like IPng white paper series?=20
=20
On considering the feasibility ground, it is hard to standardize all
possible pet ideas into RFC series - due to scalability and hard-to-
reach-consensus reasons. For example, multi6 is discussing indirection
related proposals. The solutions ranges from minor configuration=20
change to new layer. So, the task is really hard. At times, it will
make the WG task difficult (lack of focus etc.) OTOH, IRTF and new=20
area related ideas should be made into RFC (as many have restricted=20
mailing lists.)
=20
Let's now consider usability grounds. The "pet" idea RFC series doesn't
serve the purpose:
=20
  o If one is revisiting the old ideas, they will most likely prefer=20
    mailing list archives (due to its descriptive nature) than RFC.=20
=20
  o As for citation purpose, position/opinion papers can be in any=20
    form(RFC/mailing list post/expired ID/unpublished piece/even
    personal communication.) OTOH, vendors/operators value IETF=20
    rubber stamp in the form of RFC for implementation/operational
    practice. =20



From owner-ietf@ietf.org  Mon Jan 19 07:40:59 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14752
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 07:40:59 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiYWN-0003Uj-Ip
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 07:28:47 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiYW8-0003Tr-NR
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 07:28:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14235
	for <ietf@ietf.org>; Mon, 19 Jan 2004 07:28:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiYW3-00010k-00
	for ietf@ietf.org; Mon, 19 Jan 2004 07:28:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiYSD-0000pr-00
	for ietf@ietf.org; Mon, 19 Jan 2004 07:24:30 -0500
Received: from sccrmhc13.comcast.net ([204.127.202.64])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiYQ3-0000eU-00
	for ietf@ietf.org; Mon, 19 Jan 2004 07:22:15 -0500
Received: from dfnjgl21 (c-24-1-97-129.client.comcast.net[24.1.97.129])
          by comcast.net (sccrmhc13) with SMTP
          id <2004011912210901600gc31he>
          (Authid: sdawkins@comcast.net);
          Mon, 19 Jan 2004 12:21:09 +0000
Message-ID: <019101c3de86$b8d4e5d0$0400a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf@ietf.org>
References: <5EF7D95E17BDAD4A968C812E5ABC390B01108236@KC-MAIL4.kc.umkc.edu>
Subject: Re: The IETF Mission
Date: Mon, 19 Jan 2004 06:21:09 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: "Ayyasamy, Senthilkumar (UMKC-Student)" <saq66@umkc.edu>
To: "Bob Braden" <braden@ISI.EDU>; <fred@cisco.com>
Cc: <ietf@ietf.org>
Sent: Monday, January 19, 2004 1:42 AM
Subject: RE: The IETF Mission

> Let's now consider usability grounds. The "pet" idea RFC series
doesn't
> serve the purpose:
>
>   o If one is revisiting the old ideas, they will most likely prefer
>     mailing list archives (due to its descriptive nature) than RFC.

Ummm, no. Most IETF mailing lists are pretty inaccessible to non-WG
participants because no one ever summarizes ideas before WG last call.
Some are more inaccessible because of posting volume levels. Some are
becoming more inaccessible because they don't restrict posting to
members and are filling their archives with spam. Professional
networking researchers might have time, but might not, and people
doing prior art searches for ideas that they've just been sued over
might make time, but if our mailing list archives continue to be our
institutional memory, we'll continue to suffer from Alzheimers (except
that we lose our minds first-in-first-out, while Alzheimers takes your
mind last-in-first-out).

It's not like people who weren't there can find things easily in the
RFC series (note the recent discussion on end-to-end as the TCP
research community realized that they weren't sure what was, and was
not, TCP). I-D draft respositories are an order of magnitude more
difficult to search, because ideas come, go, and come again in the
lifetime of discussion of a draft (and because, sadly, we rename
drafts for almost no reason when they are adopted as WG items, and
gratuitously challenge people to associate individual draft history
with WG draft history). Mailing list archives are an order of
magnitude more difficult than that (for the reasons previously
stated).

Spencer




From owner-ietf@ietf.org  Mon Jan 19 08:34:52 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16190
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 08:34:52 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiZSR-0004lO-3V
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 08:28:47 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiZRw-0004kO-3Y
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 08:28:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15831
	for <ietf@ietf.org>; Mon, 19 Jan 2004 08:28:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiZRl-0003zs-00
	for ietf@ietf.org; Mon, 19 Jan 2004 08:28:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiZPZ-0003oB-00
	for ietf@ietf.org; Mon, 19 Jan 2004 08:25:50 -0500
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1AiZNa-0003fN-00
	for ietf@ietf.org; Mon, 19 Jan 2004 08:23:46 -0500
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (NAVGW 2.5.2.11) with SMTP id M2004011908403715408
 for <ietf@ietf.org>; Mon, 19 Jan 2004 08:40:37 -0500
Received: from centive.com ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 19 Jan 2004 08:19:33 -0500
Message-ID: <400BD965.1070404@centive.com>
Date: Mon, 19 Jan 2004 08:19:33 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Hi
References: <jprlhmmlitaarkxkqds@INCENTIVESYSTEMS.COM>
In-Reply-To: <jprlhmmlitaarkxkqds@INCENTIVESYSTEMS.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jan 2004 13:19:33.0759 (UTC) FILETIME=[E0F830F0:01C3DE8E]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

jstracke@INCENTIVESYSTEMS.COM wrote:

> Test =)
>qxbavnirg
>--
>Test, yep.
>
I didn't write that; the return address was faked.  The Received: lines 
show it was from an IP address assigned to the University of Sydney.

-- 
/==========================================\
|John Stracke      |jstracke@centive.com   |
|Principal Engineer|http://www.centive.com |
|Centive           |My opinions are my own.|
|==========================================|
|Solipsists have all the fun.              |
\==========================================/




From owner-ietf@ietf.org  Mon Jan 19 09:42:24 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18121
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 09:42:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiaQQ-0006C1-Lh
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 09:30:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiaPV-0006Ah-1T
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 09:29:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17825
	for <ietf@ietf.org>; Mon, 19 Jan 2004 09:29:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiaPK-0007Px-00
	for ietf@ietf.org; Mon, 19 Jan 2004 09:29:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiaLX-0007Dy-00
	for ietf@ietf.org; Mon, 19 Jan 2004 09:25:44 -0500
Received: from kc-msxproto3.kc.umkc.edu ([134.193.143.160])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiaJF-00072K-00
	for ietf@ietf.org; Mon, 19 Jan 2004 09:23:21 -0500
Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211] RDNS failed) by kc-msxproto3.kc.umkc.edu with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 19 Jan 2004 08:22:24 -0600
x-mimeole: Produced By Microsoft Exchange V6.5.6944.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: The IETF Mission
Date: Mon, 19 Jan 2004 08:22:24 -0600
Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B01108239@KC-MAIL4.kc.umkc.edu>
Thread-Topic: The IETF Mission
Thread-Index: AcPeiY/gWde74WfdTU2pPf9Pa5jXrwADMwNe
From: "Ayyasamy, Senthilkumar  \(UMKC-Student\)" <saq66@umkc.edu>
To: "Spencer Dawkins" <spencer@mcsr-labs.org>, <ietf@ietf.org>
X-OriginalArrivalTime: 19 Jan 2004 14:22:24.0924 (UTC) FILETIME=[A8C24DC0:01C3DE97]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS 
	autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

>>   o If one is revisiting the old ideas, they will most likely prefer
>>     mailing list archives (due to its descriptive nature) than RFC.
>
> Ummm, no. Most IETF mailing lists are pretty inaccessible to non-WG
> participants because no one ever summarizes ideas before WG last call.
 ...
> (note the recent discussion on end-to-end as the TCP
> research community realized that they weren't sure what was, and was
> not, TCP).
...
> Mailing list archives are an order of magnitude more difficult than=20
> that (for the reasons previously stated).
=20
so, RFCs too share the same problem (as per your reference to TCP=20
related RFC issue.) we should be specific about what can be made=20
into RFC; it should not also share the long process time associated=20
with informational RFCs (e.g., area report series after every IETF=20
meeting which summarize BOF results.)



From owner-ietf@ietf.org  Mon Jan 19 11:04:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23416
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 11:04:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aibkg-00080R-2o
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 10:55:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aibkb-0007z3-6R
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 10:55:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23016
	for <ietf@ietf.org>; Mon, 19 Jan 2004 10:55:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aibka-0005i2-00
	for ietf@ietf.org; Mon, 19 Jan 2004 10:55:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aibjg-0005cN-00
	for ietf@ietf.org; Mon, 19 Jan 2004 10:54:45 -0500
Received: from mercury.lcs.mit.edu ([18.26.0.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aibir-0005TZ-00
	for ietf@ietf.org; Mon, 19 Jan 2004 10:53:54 -0500
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id 9A57C872FC; Mon, 19 Jan 2004 10:53:18 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Hi
Cc: jnc@mercury.lcs.mit.edu
Message-Id: <20040119155318.9A57C872FC@mercury.lcs.mit.edu>
Date: Mon, 19 Jan 2004 10:53:18 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: John Stracke <jstracke@centive.com>

    > I didn't write that; the return address was faked.

So much for mailing list "security" by only allowing posts from subscribers.

This virus/worm is actually mildly interested in the way it operates. I'm
seeing lots of email from people with whom I would have corresponded long ago.
So it's probably mining web pages for old email, and using the addresses it
finds in the headers as source/dest pairs.

I wonder how long it will take before the spammers catch onto this trick.

	Noel



From owner-ietf@ietf.org  Mon Jan 19 11:49:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26672
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 11:49:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AicRQ-0008B8-3R
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 11:39:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AicP6-0007tw-Oh
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 11:37:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25137
	for <ietf@ietf.org>; Mon, 19 Jan 2004 11:37:14 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AicOl-00013A-00
	for ietf@ietf.org; Mon, 19 Jan 2004 11:37:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AicFS-0000Gx-00
	for ietf@ietf.org; Mon, 19 Jan 2004 11:27:34 -0500
Received: from h80ad2484.async.vt.edu ([128.173.36.132] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aic9M-0007QP-00
	for ietf@ietf.org; Mon, 19 Jan 2004 11:21:16 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i0JGKjsu012269;
	Mon, 19 Jan 2004 11:20:45 -0500
Message-Id: <200401191620.i0JGKjsu012269@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: ietf@ietf.org
Subject: Re: Hi 
In-Reply-To: Your message of "Mon, 19 Jan 2004 10:53:18 EST."
             <20040119155318.9A57C872FC@mercury.lcs.mit.edu> 
References: <20040119155318.9A57C872FC@mercury.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1047108949P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 19 Jan 2004 11:20:45 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Mon, 19 Jan 2004 10:53:18 EST, Noel Chiappa said:

> This virus/worm is actually mildly interested in the way it operates. I'm
> seeing lots of email from people with whom I would have corresponded long ago

From http://www.viruslist.com/eng/alert.html?id=783050:

The worm searches disk drives for files with the following extensions:

wab, txt, htm, html, r1

and scans them for email-like text strings, then sends infected messages to the
email addresses found. The worm uses its own SMTP engine to send infected
messages.

> So it's probably mining web pages for old email, and using the addresses it
> finds in the headers as source/dest pairs.

Old notebooks, but you're on the right track.

> I wonder how long it will take before the spammers catch onto this trick.

They already have.  Somebody on the NANOG list is infected with something that
takes the RFC822 headers of incoming mail and glues them onto a spam.  I found
this when I got a "sensitive content" warning 8 minutes after I posted to NANOG.
The victim site's filter coughed up the from/to/subject - but by the time it had
gotten there, the body had mutated into an ad for a male enhancement pill.

The clever part here is that since it's using near-in-real-time headers from
actual discussions, there's a very good chance that the spam recipient will
open it, thinking it's the ongoing discussion....


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

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

iD8DBQFADAPccC3lWbTT17ARArLeAJ93sFfEuVQ6DlfBZcbSMqsHUkL4/QCgw5X1
LUY+aX3HetIV9b0tOV5udt0=
=tVx/
-----END PGP SIGNATURE-----

--==_Exmh_-1047108949P--



From owner-ietf@ietf.org  Mon Jan 19 12:09:20 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28091
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 12:09:20 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aicgv-0000uI-2w
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 11:55:57 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aicfi-0000nL-7I
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 11:54:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27502
	for <ietf@ietf.org>; Mon, 19 Jan 2004 11:54:39 -0500 (EST)
From: kent@songbird.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aicfh-0004Jk-00
	for ietf@ietf.org; Mon, 19 Jan 2004 11:54:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aiceq-0004Cc-00
	for ietf@ietf.org; Mon, 19 Jan 2004 11:53:49 -0500
Received: from adsl-67-116-36-254.dsl.sntc01.pacbell.net ([67.116.36.254] helo=localhost.localdomain)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aicdk-0003zR-00
	for ietf@ietf.org; Mon, 19 Jan 2004 11:52:40 -0500
Received: (from kent@localhost)
	by localhost.localdomain (8.11.6/8.11.6) id i0JGqas12342
	for ietf@ietf.org; Mon, 19 Jan 2004 08:52:36 -0800
Date: Mon, 19 Jan 2004 08:52:36 -0800
To: ietf@ietf.org
Subject: Re: Hi
Message-ID: <20040119165236.GF4306@owl.songbird.com>
Mail-Followup-To: ietf@ietf.org
References: <20040119155318.9A57C872FC@mercury.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040119155318.9A57C872FC@mercury.lcs.mit.edu>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NORMAL_HTTP_TO_IP,
	NO_REAL_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Jan 19, 2004 at 10:53:18AM -0500, Noel Chiappa wrote:
>     > From: John Stracke <jstracke@centive.com>
> 
>     > I didn't write that; the return address was faked.
> 
> So much for mailing list "security" by only allowing posts from subscribers.

Security is not a binary condition.  

> This virus/worm is actually mildly interested in the way it operates. I'm
> seeing lots of email from people with whom I would have corresponded long ago.
> So it's probably mining web pages for old email, and using the addresses it
> finds in the headers as source/dest pairs.

Perhaps, but that would be pretty impressive for a 16K executable --
maybe it downloads a second stage  -- there are a bunch of builtin urls,
eg:

http://www.elrasshop.de/1.php
http://www.it-msc.de/1.php
http://www.getyourfree.net/1.php
http://www.dmdesign.de/1.php
http://64.176.228.13/1.php
http://www.leonzernitsky.com/1.php
http://216.98.136.248/1.php
http://216.98.134.247/1.php
http://www.cdromca.com/1.php
http://www.kunst-in-templin.de/1.php
http://vipweb.ru/1.php
http://antol-co.ru/1.php
http://www.bags-dostavka.mags.ru/1.php
http://www.5x12.ru/1.php
http://bose-audio.net/1.php
http://www.sttngdata.de/1.php
http://wh9.tu-dresden.de/1.php
http://www.micronuke.net/1.php
http://www.stadthagen.org/1.php
etc


-- 
Kent Crispin 
kent@icann.org    p: +1 310 823 9358  f: +1 310 823 8649
kent@songbird.com SIP: 81202@fwd.pulver.com




From owner-ietf@ietf.org  Mon Jan 19 14:02:49 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02480
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 14:02:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AieYq-0005SP-MO
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 13:55:44 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AieWw-0005P1-MQ
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 13:53:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01919
	for <ietf@ietf.org>; Mon, 19 Jan 2004 13:53:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AieWv-0003fa-00
	for ietf@ietf.org; Mon, 19 Jan 2004 13:53:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AieW1-0003Zn-00
	for ietf@ietf.org; Mon, 19 Jan 2004 13:52:50 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AieV5-0003SU-00
	for ietf@ietf.org; Mon, 19 Jan 2004 13:51:51 -0500
Received: (from braden@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i0JIpeb18626;
	Mon, 19 Jan 2004 10:51:40 -0800 (PST)
Date: Mon, 19 Jan 2004 10:51:40 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Message-Id: <200401191851.i0JIpeb18626@boreas.isi.edu>
To: braden@ISI.EDU, iljitsch@muada.com
Subject: Re: The IETF Mission
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


  *> This means drastically lowering the standards for what can be published 
  *> as an RFC. (Note that this brings us closer to what RFCs used to be 15 
  *> years or so ago.) Another way to do it would be to simply archive all 

I do not believe that it means lowering the standards at all, in
general.  In general, the documents we should be publishing as RFCs,
but are allowing to disappear into long-dead Internet Drafts, are every
bit as good quality as the RFCs we are publishing today (if not
better!).

Example: The RFC Editor has been pushing to get the current plateau of
the technical specification of HIP published as an RFC.  It's like
pulling teeth, for some reason, but hopefully we will make it.  The
current HIP architecture document is an important contribution that will
be a valuable reference to future Internet techies, regardless of the
future trajectory of the HIP protocol.

BTW, when you said 15 years you really meant 25, back to the late
ARPAnet and early Internet days.  15 years ago is relatively recent,
really part of "modern times" for the Internet community.  For example,
the Host Requirements RFCs (1122, 1123) were published 15 years ago.  I
don't think you would be lowering current standards to reach that
level.

  *> drafts. I agree this has the unpleasant side effect that all those 
  *> drafts that become obsolete (or are so from inception) stay around 
  *> forever. But it's still better than the current situation, where making 
  *> something an RFC means an incredible amount of work for many people, 

It is true that writing quality documents, no matter what
you call them, is always an "incredible amount of work."  Work well
spent, I believe.

Bob Braden




From owner-ietf@ietf.org  Mon Jan 19 14:13:34 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02874
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 14:13:34 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AielR-0007Ho-Go
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 14:08:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aieji-0007A5-Tg
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 14:06:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02607
	for <ietf@ietf.org>; Mon, 19 Jan 2004 14:06:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiejX-0004YH-00
	for ietf@ietf.org; Mon, 19 Jan 2004 14:06:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aiegb-0004O7-00
	for ietf@ietf.org; Mon, 19 Jan 2004 14:03:46 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AieeU-0004Gr-00
	for ietf@ietf.org; Mon, 19 Jan 2004 14:01:34 -0500
Received: (from braden@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i0JJ1OU26110;
	Mon, 19 Jan 2004 11:01:24 -0800 (PST)
Date: Mon, 19 Jan 2004 11:01:24 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Message-Id: <200401191901.i0JJ1OU26110@boreas.isi.edu>
To: ietf@ietf.org, garmitage@swin.edu.au
Subject: Re: The IETF Mission
X-Sun-Charset: US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

  *> 
  *> If it is important, it'll progress the work of some group in the
  *> IETF and be archived as an RFC. If it (the I-D) doesn't capture work
  *> well enough to be archived as an RFC then it ought to fade from IETF
  *> I-D storage.

Grenville,

Not all important ideas enter the working group process and emerge
as standards, and the fact that some working group chooses not to
"capture" an document does not make it necessarily unworthy of
preservation.  After all, the technical problems evolve, and our
solutions need to evolve too; ideas that did not make it at one
stage may turn out to be important in the future.  And, I believe
you are surrendering too easily the over-emphasis on standards
that Fred decried in his message.

  *> 
  *> Is the standard for Informational currently that onerous?

Certainly not.  But the community (and especially its chosen
leadership) need to believe in the importance of using Informational
to capture important documents and ideas as RFCs.

Bob Braden




From owner-ietf@ietf.org  Mon Jan 19 15:03:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05202
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 15:03:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AifSy-0000lf-Cg
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 14:53:44 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AifSC-0000hs-Dp
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 14:52:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04680
	for <ietf@ietf.org>; Mon, 19 Jan 2004 14:52:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AifSA-0000JC-00
	for ietf@ietf.org; Mon, 19 Jan 2004 14:52:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AifRJ-0000Fa-00
	for ietf@ietf.org; Mon, 19 Jan 2004 14:52:02 -0500
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AifQw-0000B9-00
	for ietf@ietf.org; Mon, 19 Jan 2004 14:51:38 -0500
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1.3)
  with ESMTP-TLS id 660121; Mon, 19 Jan 2004 13:51:37 -0600
Message-ID: <400C3547.5010908@ehsco.com>
Date: Mon, 19 Jan 2004 13:51:35 -0600
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bob Braden <braden@ISI.EDU>
CC: ietf@ietf.org, garmitage@swin.edu.au
Subject: Re: The IETF Mission
References: <200401191901.i0JJ1OU26110@boreas.isi.edu>
In-Reply-To: <200401191901.i0JJ1OU26110@boreas.isi.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On 1/19/2004 1:01 PM, Bob Braden wrote:

> Not all important ideas enter the working group process and emerge
> as standards, and the fact that some working group chooses not to
> "capture" an document does not make it necessarily unworthy of
> preservation.  After all, the technical problems evolve, and our
> solutions need to evolve too; ideas that did not make it at one
> stage may turn out to be important in the future.

Another approach here is to allow for the creation of ad-hoc WGs. That
would provide a cleaner path for tangential documents that don't fit
within existing charters, and would facilitate broader group review of
independent submissions. Speaking for myself, I've written some drafts
that I would have liked to seen progressl, but didn't fit in existing WGs,
and the requirements for new WGs were too stringent to pursue. This latter
 issue is also one of the reasons behind the relatively low involvement
from the developing-world community, and exacerbates the feelings of
powerlessness and resentment that end up costing us recovery time fighting
off the well-meaning fools who would make this problem worse by handing
control to organizations with even higher barriers of entry.

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



From owner-ietf@ietf.org  Mon Jan 19 16:50:03 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10118
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 16:50:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AihAL-0004Ko-77
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 16:42:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aih8l-0004Iq-1p
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 16:40:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09670
	for <ietf@ietf.org>; Mon, 19 Jan 2004 16:40:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aih8g-0007Fc-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:40:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aih7r-0007Aj-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:40:04 -0500
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aih74-0006yW-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:39:14 -0500
Received: from cirrus ([130.105.36.66])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA01942;
	Mon, 19 Jan 2004 17:44:17 -0500
Date: Mon, 19 Jan 2004 16:36:08 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus
To: Keith Moore <moore@cs.utk.edu>
cc: Iljitsch van Beijnum <iljitsch@muada.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: dubious assumptions about IPv6 (was death of the Internet)
In-Reply-To: <784F1990-48BA-11D8-BE61-000393DB5366@cs.utk.edu>
Message-ID: <Pine.LNX.4.44.0401191606230.8290-100000@cirrus>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 17 Jan 2004, Keith Moore wrote:

> > The residential users don't need to have a globaly unique IP address.
> 
> That's like saying residential telephone users don't need to have a 
> phone number at which they can be reached.  (after all, the purpose of 
> their residential phones is to call businesses for the purpose of 
> obtaining services, right?)

No, its not at all like saying that.  Its like saying that residential
phone users don't need a globally unique circuit facilities assignment
(CFA)  number. Indeed, most residential telephone users aren't aware of
that number, even though they have one.  The globably unique telephone
number is more comparable to the email address, or the instant message id.  
I contact you at moore@cs.utk.edu, not your IP address.  And when I call
your phone number, computers (telephone switches) figure out the physical
switch port number to route the call to.  I don't need to know that
number; That number doesn't need to be unique.  

Indeed, its quite possible that your phone number might even replace your
email address as your globally unique identifier.  And thus it might not
matter whether IP is even used at all. One could connect to that phone
number via TDM switched circuits, via Voice over IP, via Voice over Frame
Relay, or via some other yet-to-be-invented method. That connection could
be voice, email, instant messaging, web, etc. I don't want to go into the
merits of this, but only to use this as an example that IP addresses don't
necessarilly need to be globally unique, so long as there exists other
globably unique identifiers and gateways between different kinds of
networks.

> There are lots of apps that would be valuable to residential users if 
> residential users had reachable IP addresses.  check the status of your 
> alarm system, or your roast in the oven, or your freezer's inventory.  
> Grab a picture from your baby-cam while you're out for dinner and have 
> left the kid with the baby sitter.  Reset the thermostat if you're 
> going to be out of town longer than you thought.  Do all of these from 
> your portable phone/PDA which is running guess what? -- IPv6.

Sure, but these are servers; servers that many residential use contracts
prohibit except at additional cost. And like email, such services can be
implemented without static ip addresses by 'pushing' data up to a web or
application server.

Certainly, IPv6 could enable some things that aren't possible without it,
and could provide more implementation and design choices to the
application developers. I don't dispute that. But this is not free. There
are practical costs associated with this.

> IPv6 will eventually replace IPv4, but it's misleading to think of IPv6 
> as just a replacement for IPv4.  By the time IPv6 replaces IPv4, we 
> won't recognize the IPv6 network as something that resembles what the 
> IPv4 network is used for today.  Even though the underlying technology 
> is very similar, IPv6 is really a new kind of network, one that enables 
> things that were really never possible with IPv4 on a large scale.

I agree. But like Cobol, technically better solutions aren't always
adopted, and even when they are adopted, the inferior solutions often
don't go away for a long time.

		--Dean




From owner-ietf@ietf.org  Mon Jan 19 16:52:02 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10180
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 16:52:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AihFH-0004VX-GF
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 16:47:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AihDX-0004Rt-64
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 16:45:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09873
	for <ietf@ietf.org>; Mon, 19 Jan 2004 16:45:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AihDV-0007XJ-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:45:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AihCb-0007Tv-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:44:58 -0500
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AihCH-0007Qt-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:44:37 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i0JLi1v23259;
	Mon, 19 Jan 2004 23:44:01 +0200
Date: Mon, 19 Jan 2004 23:44:00 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: ietf@ietf.org
Subject: Re: The IETF Mission
In-Reply-To: <400C3547.5010908@ehsco.com>
Message-ID: <Pine.LNX.4.44.0401192339100.22021-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 19 Jan 2004, Eric A. Hall wrote:
> Another approach here is to allow for the creation of ad-hoc WGs. That
> would provide a cleaner path for tangential documents that don't fit
> within existing charters, and would facilitate broader group review of
> independent submissions. Speaking for myself, I've written some drafts
> that I would have liked to seen progressl, but didn't fit in existing WGs,
> and the requirements for new WGs were too stringent to pursue. This latter
>  issue is also one of the reasons behind the relatively low involvement
> from the developing-world community, and exacerbates the feelings of
> powerlessness and resentment that end up costing us recovery time fighting
> off the well-meaning fools who would make this problem worse by handing
> control to organizations with even higher barriers of entry.

Maybe you have a common(?) fallacy that once a WG is established, you 
start to magically a better and broader review of the drafts.

Often this is not the case.

But the core point is, I think, how can one attract the reviewers or 
people in general to read and send feedback on an idea which has been 
documented in an Internet-draft.  This is obviously a difficult 
problem, as everybody probably thinks their work is special.

One thing which *might* make it easier, for the drafts which relate to
existing technologies, is if there were "maintenance teams" for the
core protocols, with mailing-lists one could spam one's ideas to,
hoping for feedback from the people interested in a subject.  Not sure
if that would help significantly though..
 
-- 
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 Jan 19 16:53:03 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10204
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 16:53:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AihFH-0004Vj-V8
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 16:47:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AihET-0004Tc-Nt
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 16:46:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09902
	for <ietf@ietf.org>; Mon, 19 Jan 2004 16:46:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AihES-0007aj-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:46:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AihDb-0007YA-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:45:59 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50] helo=smtp.cs.utk.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AihDB-0007Uc-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:45:33 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 62054AFD66; Mon, 19 Jan 2004 16:45:26 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 15303-06; Mon, 19 Jan 2004 16:45:25 -0500 (EST)
Received: from [192.168.0.4] (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id EE67BAFD5D; Mon, 19 Jan 2004 16:45:24 -0500 (EST)
In-Reply-To: <Pine.LNX.4.44.0401191606230.8290-100000@cirrus>
References: <Pine.LNX.4.44.0401191606230.8290-100000@cirrus>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <D92BA335-4AC8-11D8-AF40-000393DB5366@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@cs.utk.edu>, Iljitsch van Beijnum <iljitsch@muada.com>,
        IETF Discussion <ietf@ietf.org>
From: Keith Moore <moore@cs.utk.edu>
Subject: Re: dubious assumptions about IPv6 (was death of the Internet)
Date: Mon, 19 Jan 2004 16:45:50 -0500
To: Dean Anderson <dean@av8.com>
X-Mailer: Apple Mail (2.609)
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>>> The residential users don't need to have a globaly unique IP address.
>>
>> That's like saying residential telephone users don't need to have a
>> phone number at which they can be reached.  (after all, the purpose of
>> their residential phones is to call businesses for the purpose of
>> obtaining services, right?)
>
> No, its not at all like saying that.  Its like saying that residential
> phone users don't need a globally unique circuit facilities assignment
> (CFA)  number. Indeed, most residential telephone users aren't aware of
> that number, even though they have one.  The globably unique telephone
> number is more comparable to the email address, or the instant message 
> id.

only if you want to insist that every application that someone might 
want to run at home should require an expensive external 
infrastructure.  (there are no polite words to describe people with 
that attitude)




From owner-ietf@ietf.org  Mon Jan 19 16:54:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10260
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 16:54:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AihIB-0004pm-Ly
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 16:50:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AihHJ-0004Ze-CP
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 16:49:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10064
	for <ietf@ietf.org>; Mon, 19 Jan 2004 16:49:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AihHI-0007mG-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:49:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AihGJ-0007hl-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:48:47 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AihFQ-0007e8-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:47:52 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i0JLlpJX022631
	for ietf@ietf.org env-from <vjs>;
	Mon, 19 Jan 2004 14:47:51 -0700 (MST)
Date: Mon, 19 Jan 2004 14:47:51 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401192147.i0JLlpJX022631@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: The IETF Mission
References: <400C3547.5010908@ehsco.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> > Not all important ideas enter the working group process and emerge
> > as standards, and the fact that some working group chooses not to
> > "capture" an document does not make it necessarily unworthy of
> > preservation.  ...

> Another approach here is to allow for the creation of ad-hoc WGs. That
> would provide a cleaner path for tangential documents that don't fit
> ... 

Let's see if I've got all of this straight:

 - The IETF is working on a Dilbert Standard compliant Mission Statement.
  The Dilbert Mission Statement Standard requires foursquare support
  of all virtues and opposition to all vices, without unnecessary
  (read "any") limitations.

 - There are many wonderful ideas that are so awesome that if they were
  self-published, their publishers cannot be slashdotted and would
  never be indexed by Google.  To remedy this unfair lack of publishers
  and de facto censorship, the IETF will go into competition with the
  ACM, IEEE, etc. in both the refereed academic publish-or-perish
  business (e.g. CACM or *Transactions) and the random research notes
  business (SIGCOMM).

 - Salescritters, marketoons, and trade rag espurts find it inconvenient
  to utilize the IETF imprimatur by submitting I-Ds (possibly pushed
  to Informational) and then advertising compliance.  To fix this
  terrible shortcoming of the IETF Standards Process that hinders
  innovatation by Microsoft and other leading edge organizations, the
  new IETF Mission Statement will require that anyone who wants a WG
  can have one.

I think those are excellent proposals, although perhaps not for the
same reasons as other adovcates.  I've been complaining about nonsense
I-Ds and write-only RFCs for many years.  The most effective way to
relive the pressure for junk RFCs and nonsense IDs is to make IETF's
stamp of approval meaningless by giving it to anything and everything
that comes along.  Within a matter of at most a year or two, RFCs might
go back to what they were 20 years ago.

To solve any funding problems or overwork of the IESG,
http://www.ietf.org/html.charters/wg-dir.html will become an automated
index of links much like http://reshmeat.net/ and we'll do away with
Last Calls. 

Let's hurry up and advance or at least archive these IDs before they expire:

  draft-terrell-internet-protocol-t1-t2-ad-sp-06.pdf
  draft-terrell-iptx-dhcp-req-iptx-ip-add-spec-00.pdf
  draft-terrell-iptx-dns-req-iptx-ip-add-spec-03.pdf
  draft-terrell-iptx-spec-def-cidr-ach-net-descrip-01.pdf


Vernon  Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Mon Jan 19 17:32:02 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12448
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 17:32:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aihrl-0007sV-3Y
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 17:27:29 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aihpi-0007lY-0C
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 17:25:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11709
	for <ietf@ietf.org>; Mon, 19 Jan 2004 17:24:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AihpB-0002Zu-00
	for ietf@ietf.org; Mon, 19 Jan 2004 17:24:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aihid-00024Q-00
	for ietf@ietf.org; Mon, 19 Jan 2004 17:18:04 -0500
Received: from bartok.sidn.nl ([193.176.144.164])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AihdS-0001eh-00
	for ietf@ietf.org; Mon, 19 Jan 2004 17:12:42 -0500
Received: from bartok.sidn.nl (localhost.sidn.nl [127.0.0.1])
	by bartok.sidn.nl (8.12.10/8.12.10) with ESMTP id i0JMBfrP091010;
	Mon, 19 Jan 2004 23:11:41 +0100 (CET)
	(envelope-from jaap@bartok.sidn.nl)
Message-Id: <200401192211.i0JMBfrP091010@bartok.sidn.nl>
To: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
cc: ietf@ietf.org
Subject: Re: ESMTP Services Advertisement Requirements? RFC 821 Esoteric Commands Exclusion Permitted? 
In-reply-to: Your message of Mon, 19 Jan 2004 21:39:31 +0000.
             <400C4E93.489.14CB7AFC@localhost> 
Date: Mon, 19 Jan 2004 23:11:41 +0100
From: Jaap Akkerhuis <jaap@sidn.nl>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


    
    What are your thoughts?  
    
RFC 2821 obsoletes 821, 974, 1869 and updates 1123. Maybe you find some
answers there?

	jaap




From owner-ietf@ietf.org  Mon Jan 19 17:36:11 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10119
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 16:50:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AihAR-0004Mc-KK
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 16:42:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aih9l-0004Ka-UJ
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 16:42:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09712
	for <ietf@ietf.org>; Mon, 19 Jan 2004 16:41:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aih9k-0007Jn-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:42:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aih8o-0007Gm-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:41:02 -0500
Received: from 82-35-77-212.cable.ubr02.dals.blueyonder.co.uk ([82.35.77.212] helo=DarkLord.Sabahattin-Gucukoglu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aih8A-0007Cn-00
	for ietf@ietf.org; Mon, 19 Jan 2004 16:40:22 -0500
Received: from Spooler by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v4.01a) ID MO0000B6;
    19 Jan 2004 21:39:56 -0000
Received: from spooler by sabahattin-gucukoglu.com (Mercury/32 v4.01a); 19 Jan 2004 21:39:52 -0000
Received: from amethyst (192.168.1.5) by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v4.01a) with ESMTP ID MG0000B5;
   19 Jan 2004 21:39:51 -0000
From: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
Organization: I need more of this!
To: ietf@ietf.org
Date: Mon, 19 Jan 2004 21:39:31 -0000
MIME-Version: 1.0
Subject: ESMTP Services Advertisement Requirements? RFC 821 Esoteric Commands Exclusion Permitted?
Message-ID: <400C4E93.489.14CB7AFC@localhost>
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.0 required=5.0 tests=AWL,NEW_DOMAIN_EXTENSIONS 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

Hi people,

For STD 10, RFC 1869, SMTP Service Extensions, it is not made clear, 
except possibly in a pair of examples provided by that memo, exactly 
whether or not the commands defined as optional and not required for a 
minimum implementation of SMTP (RFC 821), should or should not be 
advertised as described by the Service Extensions listings maintained by 
IANA in the manner described by RFC 1869.  In fact, no mandates are set 
upon the specific advertisement of any service, be it supported or not, of 
RFC 821 origin or otherwise.  Specifically, since the standard 
implementation of SMTP in RFC 821 makes no requirement for advertising 
optional commands that may be implemented (HELP, EXPN, SAML, SOML, etc), 
is it a violation of RFC 1869 that the server, despite supporting those 
features of RFC 821, does not advertise any or some of those supported 
commands in the ESMTP ehlo response, even if they are available for 
service in normal use of SMTP?  Since they were defined as extensions only 
when the extensions framework was built, it seems unreasonable to expect 
implementations which may support the ESMTP framework to necessarily 
advertise those commands, rather than the few new ESMTP extensions such as 
Auth and StartTLS that the framework support was probably designed to 
cater for and for which developers have incorporated support into their 
mail transports.  Not advertising features of SMTP will slightly decrease 
the transaction overhead without impact, in all probability, since the 
assumption can safely be made that those esoteric features of SMTP that 
are of any use to a specific client are called usually with prior 
knowledge of the features provided by the server, as in the use of turn or 
help in normal RFC 821 usage.  Finally, many SMTP services out there 
exhibit this exact behaviour, not advertising supported features of SMTP 
in their ESMTP synopsis, so it is of interest to me to know whether, as 
part of the configurability of a mail transport, the option to advertise 
any, all, or all except RFC821 specific optional commands should be made 
available, or even whether or not the advertising of any service, of 
whatever origin, is required at all in any case.  The help verb may then 
list all verbs which are supported, inclusive of those defined by RFC 821 
or otherwise excluded for administrative reasons.  

What are your thoughts?  

Cheers,
Sabahattin
-- 
Thought for the day:
    A penny saved is ridiculous.

Latest PGP Public key blocks?  Send any mail to:
<PGPPublicKey@sabahattin-gucukoglu.com>

Sabahattin Gucukoglu
Phone: +44 (0)20 7,502-1615
Mobile: +44 (0)7986 053399
http://www.sabahattin-gucukoglu.com/
Email/MSN: <mail@Sabahattin-Gucukoglu.com>




From owner-ietf@ietf.org  Mon Jan 19 18:14:24 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14576
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 18:14:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiiV9-0001Lo-UU
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 18:08:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiiSj-0001Fe-M5
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 18:05:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13732
	for <ietf@ietf.org>; Mon, 19 Jan 2004 18:05:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiiST-0005Jl-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:05:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiiOR-00059F-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:01:16 -0500
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiiMS-000504-00
	for ietf@ietf.org; Mon, 19 Jan 2004 17:59:12 -0500
Received: from cirrus ([130.105.36.66])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA21208;
	Mon, 19 Jan 2004 19:03:35 -0500
Date: Mon, 19 Jan 2004 17:55:28 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus
To: Keith Moore <moore@cs.utk.edu>
cc: Iljitsch van Beijnum <iljitsch@muada.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: dubious assumptions about IPv6 (was death of the Internet)
In-Reply-To: <D92BA335-4AC8-11D8-AF40-000393DB5366@cs.utk.edu>
Message-ID: <Pine.LNX.4.44.0401191751460.8290-100000@cirrus>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 19 Jan 2004, Keith Moore wrote:

> >>> The residential users don't need to have a globaly unique IP address.
> >>
> >> That's like saying residential telephone users don't need to have a
> >> phone number at which they can be reached.  (after all, the purpose of
> >> their residential phones is to call businesses for the purpose of
> >> obtaining services, right?)
> >
> > No, its not at all like saying that.  Its like saying that residential
> > phone users don't need a globally unique circuit facilities assignment
> > (CFA)  number. Indeed, most residential telephone users aren't aware of
> > that number, even though they have one.  The globably unique telephone
> > number is more comparable to the email address, or the instant message 
> > id.
> 
> only if you want to insist that every application that someone might 
> want to run at home should require an expensive external 
> infrastructure.  (there are no polite words to describe people with 
> that attitude)

As Kazaa, Napster, Groove, and other protocols have demonstrated, its
quite easy to create peer-to-peer applications without either expensive
external infrastructure or fixed, unique IP addresses.  The scalability of
these protocols has threatened the Music and Movie Industries--and thats
really something.  I wouldn't have thought such a thing possible ten years 
ago.

		--Dean




From owner-ietf@ietf.org  Mon Jan 19 18:18:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14942
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 18:18:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiibT-0001fE-31
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 18:14:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiibE-0001b2-Qc
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 18:14:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14570
	for <ietf@ietf.org>; Mon, 19 Jan 2004 18:14:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aiib3-0005oS-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:14:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiiY4-0005d4-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:11:13 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiiUg-0005PQ-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:07:42 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 19 Jan 2004 15:10:33 +0000
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id i0JN6jgP013366;
	Mon, 19 Jan 2004 15:06:45 -0800 (PST)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id APK59199;
	Mon, 19 Jan 2004 15:06:44 -0800 (PST)
Message-Id: <6.0.1.1.2.20040119141750.0420ecd0@mira-sjc5-b.cisco.com >
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Mon, 19 Jan 2004 15:06:22 -0800
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: The IETF Mission
Cc: ietf@ietf.org
In-Reply-To: <200401192147.i0JLlpJX022631@calcite.rhyolite.com>
References: <400C3547.5010908@ehsco.com>
 <200401192147.i0JLlpJX022631@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.7 required=5.0 tests=AWL,FORGED_MUA_EUDORA,
	INVALID_MSGID autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Good grief.

I don't know that we're changing anything in what the IETF does. What is 
happening is that the IETF is growing up and taking control of its own 
destiny in a variety of ways, and trying to clean up its own processes. In 
all the *other* problems it tries to solve, the IETF tries to say what 
problem it is solving sometime before finishing solving it, if for no other 
reason so that it can decide whether it did in fact solve it. Same here.

I can't speak for the others who took a crack at a mission statement, but 
I'll bet that each would articulate what he was trying to do about the same 
way that I do: I was trying to state in a few pithy words what I thought 
was important about the IETF. The purpose of the mission statement is to 
say what is core - what it is that is so important that if we screw it up 
we screwed up. If we tried to describe "what Vernon does all day" and wound 
up saying something about wearing a dress, my guess is that we could be 
accused of screwing up. If we described "what Vernon does all day" in terms 
of having ideas and articulating them, perhaps we hit closer. If we were 
trying to figure out processes to ensure that Vernon succeeded in doing 
what was important, processes that helped the latter might be more 
valuable. Am I close? The same is true of the IETF; hence the question.

I proposed the wording that I did because to me, the most important things 
the IETF does include
  - discussion of engineering issues in the Internet,
  - improvement of understanding of engineering issues in the Internet,
  - creating white papers that embody that understanding of engineering
    issues in the Internet, and
  - creating specifications for protocols that improve the engineered
    behavior of the Internet.

Some of the outcomes of the fourth bullet get labeled "standards", because 
we agree to call them that and because we agree to implement them, but by 
no means do all, and certainly the items on the third bullet don't. The 
observation that of all documents that have RFC numbers about 2/7 (1014 out 
of 3681) are Proposed Standards, Draft Standards, Full Standards, or Best 
Current Practice documents is not a call for more documents. It is also not 
a call to archive documents that are not felt to contribute valuable 
insights to our community memory. It is an observation of fact. 2/3 of the 
documents in the RFC series are *not* specifications. They are discussion 
of problems, of architecture, of requirements, and so on. They are the 
documents that a purely standards-oriented organization would never pursue, 
but which improve our understanding of the subject at hand.

Once we have decided that we did in fact solve the problem before us, I 
don't know that the bumper sticker gets us all that much further. But the 
bumper sticker can be helpful when we are asking the questions "what are we 
trying to accomplish?" and "are we accomplishing it?".

Dilbert may have something to say about it, but I personally am not a 
management consultant...
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBQAxi7m4xHWxyLJtDEQK5kQCgkV7NOuJq0UOMu1k4AelJZe0x9bEAn3vD
dsQj42jIjZ4KbZgLRQKQyUGX
=ZcIY
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Mon Jan 19 18:38:28 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16419
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 18:38:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aiitq-00031J-QM
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 18:33:42 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiitK-0002zL-Sb
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 18:33:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16146
	for <ietf@ietf.org>; Mon, 19 Jan 2004 18:33:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiitJ-0007FO-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:33:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aiis6-0007BA-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:31:55 -0500
Received: from 134.cust17.nsw.dsl.ozemail.com.au ([203.103.104.134] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiirU-00077p-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:31:16 -0500
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 079D93F02A; Tue, 20 Jan 2004 10:00:31 +1030 (CST)
Date: Tue, 20 Jan 2004 10:00:31 +1030
From: Mark Smith <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
To: Dean Anderson <dean@av8.com>
Cc: moore@cs.utk.edu, iljitsch@muada.com, ietf@ietf.org
Subject: Re: dubious assumptions about IPv6 (was death of the Internet)
Message-Id: <20040120100031.39296a50.ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
In-Reply-To: <Pine.LNX.4.44.0401191751460.8290-100000@cirrus>
References: <D92BA335-4AC8-11D8-AF40-000393DB5366@cs.utk.edu>
	<Pine.LNX.4.44.0401191751460.8290-100000@cirrus>
Organization: The No Sense Organisation (http://www.nosense.org)
X-Mailer: Sylpheed version 0.9.8a (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Mon, 19 Jan 2004 17:55:28 -0500 (EST)
Dean Anderson <dean@av8.com> wrote:

> On Mon, 19 Jan 2004, Keith Moore wrote:
> 
> > >>> The residential users don't need to have a globaly unique
> > >IP address.>
> > >> That's like saying residential telephone users don't need
> > >to have a> phone number at which they can be reached. 
> > >(after all, the purpose of> their residential phones is to
> > >call businesses for the purpose of> obtaining services,
> > >right?)
> > >
> > > No, its not at all like saying that.  Its like saying that
> > > residential phone users don't need a globally unique
> > > circuit facilities assignment(CFA)  number. Indeed, most
> > > residential telephone users aren't aware of that number,
> > > even though they have one.  The globably unique telephone
> > > number is more comparable to the email address, or the
> > > instant message id.
> > 
> > only if you want to insist that every application that
> > someone might want to run at home should require an expensive
> > external infrastructure.  (there are no polite words to
> > describe people with that attitude)
> 
> As Kazaa, Napster, Groove, and other protocols have
> demonstrated, its quite easy to create peer-to-peer
> applications without either expensive external infrastructure
> or fixed, unique IP addresses. 

I'm afraid it isn't quite that easy. I contribute to a few
discussion / help forums where people use these types
applications, including IM with file transfer or VoIP, and the
question as to how to re-configure the NAT/Firewall box to make
the application work comes up quite often.

However, people are willing to wear the inconvenience, as the
benefits, legal or otherwise, are greater.

Everything has a cost. For these types of applications, and the
applications that Keith mentioned, IPv6 will be both cheaper
and far more flexible than the IPv4+NAT combination.


 The scalability of
> these protocols has threatened the Music and Movie
> Industries--and thats really something.  I wouldn't have
> thought such a thing possible ten years ago.
>

This really doesn't say much about the scalability of the
solution. What it indicates is how much effort people are
willing to go to to commit what is perceived as victimless crime.

If these applications work "out of the box" it means effort has
be put into developing NAT traversal solutions. While this effort
is necessary, it is sad that effort had to be expended. The
developers could have been adding extra features, rather than
working around a common network infrastructure limitation.

 
Regards,
Mark.




From owner-ietf@ietf.org  Mon Jan 19 18:49:18 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17082
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 18:49:18 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aij2Z-0003ja-71
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 18:42:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aij1S-0003cY-6A
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 18:41:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16703
	for <ietf@ietf.org>; Mon, 19 Jan 2004 18:41:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aij1Q-0000E7-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:41:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aij0V-00005o-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:40:35 -0500
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aiizb-0007lK-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:39:39 -0500
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1.3)
  with ESMTP-TLS id 660147 for ietf@ietf.org; Mon, 19 Jan 2004 17:39:39 -0600
Message-ID: <400C6AB6.5030807@ehsco.com>
Date: Mon, 19 Jan 2004 17:39:34 -0600
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The IETF Mission
References: <400C3547.5010908@ehsco.com> <200401192147.i0JLlpJX022631@calcite.rhyolite.com>
In-Reply-To: <200401192147.i0JLlpJX022631@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On 1/19/2004 3:47 PM, Vernon Schryver wrote:

>>> Not all important ideas enter the working group process and emerge 
>>> as standards, and the fact that some working group chooses not to 
>>> "capture" an document does not make it necessarily unworthy of 
>>> preservation.  ...
> 
>> Another approach here is to allow for the creation of ad-hoc WGs.
>> That would provide a cleaner path for tangential documents that don't
>> fit ...
> 
> Let's see if I've got all of this straight:

No (although I'm not really sure you tried). "Ad-hoc" isn't supposed to
mean 'anything goes', but about providing an alternative channel to BOFs.

I'm sure there was a time where discouraging potentially frivolous efforts
by imposing a high cost of entry was considered a positive benefit of the
design. It still might be. If the objective is to broaden the scope and
quantity of documents to be published, however, lowering that bar would be
useful. Speaking for myself and others, getting volunteer part-timers from
multiple different continents to the same meeting is a pain, and the
payoff is so far into the future and marginal that it usually isn't worth
the cost involved.

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



From owner-ietf@ietf.org  Mon Jan 19 18:49:19 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17100
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 18:49:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aij2Z-0003l8-Qi
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 18:42:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aij20-0003ee-KW
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 18:42:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16780
	for <ietf@ietf.org>; Mon, 19 Jan 2004 18:42:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aij1y-0000Ib-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:42:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aij1E-0000Cc-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:41:21 -0500
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aij0I-0007mW-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:40:22 -0500
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id KAA830357;
	Tue, 20 Jan 2004 10:39:49 +1100 (EST)
Message-ID: <400C6AC5.CAC5A830@swin.edu.au>
Date: Tue, 20 Jan 2004 10:39:49 +1100
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The IETF Mission
References: <200401191901.i0JJ1OU26110@boreas.isi.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Bob Braden wrote:
> 
>   *>
>   *> If it is important, it'll progress the work of some group in the
>   *> IETF and be archived as an RFC. If it (the I-D) doesn't capture work
>   *> well enough to be archived as an RFC then it ought to fade from IETF
>   *> I-D storage.
> 
> Grenville,
> 
> Not all important ideas enter the working group process and emerge
> as standards,

True, but to be fair, I actually said "...to be archived as an RFC." Although
I might appear to have succumbed to "RFC == standard" mentality, I haven't
really :)

> and the fact that some working group chooses not to
> "capture" an document does not make it necessarily unworthy of
> preservation.

Yes, that's true. I simply believe that we already have a mechanism in
our posession for WGs (who are the best judges) to archive their developed
wisdom and insights - the Informational RFC. If WGs aren't using this method
then that's a problem we can fix without creating an indestructable I-Ds.
I'd hope. (I've used Informational status for this very purpose myself a
few times, so I'm biased.)

>  After all, the technical problems evolve, and our
> solutions need to evolve too; ideas that did not make it at one
> stage may turn out to be important in the future.  And, I believe
> you are surrendering too easily the over-emphasis on standards
> that Fred decried in his message.

Hopefully you were thinking of someone else ;)

> 
>   *>
>   *> Is the standard for Informational currently that onerous?
> 
> Certainly not.  But the community (and especially its chosen
> leadership) need to believe in the importance of using Informational
> to capture important documents and ideas as RFCs.

Absolutely agree.

cheers,
gja
-- 
Grenville Armitage
http://caia.swin.edu.au
I come from a LAN downunder.



From owner-ietf@ietf.org  Mon Jan 19 18:51:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17224
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 18:51:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aij6Z-0003tg-Nb
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 18:46:51 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aij2i-0003lP-8c
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 18:42:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16805
	for <ietf@ietf.org>; Mon, 19 Jan 2004 18:42:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aij2g-0000KU-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:42:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aij1m-0000Gj-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:41:54 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aij0s-00009A-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:40:58 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0JNfMLS005768;
	Tue, 20 Jan 2004 00:41:22 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0401191751460.8290-100000@cirrus>
References: <Pine.LNX.4.44.0401191751460.8290-100000@cirrus>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <EC665140-4AD8-11D8-9871-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: dubious assumptions about IPv6 (was death of the Internet)
Date: Tue, 20 Jan 2004 00:40:54 +0100
To: Dean Anderson <dean@av8.com>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 19-jan-04, at 23:55, Dean Anderson wrote:

> As Kazaa, Napster, Groove, and other protocols have demonstrated, its
> quite easy to create peer-to-peer applications without either expensive
> external infrastructure or fixed, unique IP addresses.

These protocols require that at least one side in each transfer is 
capable of receiving inbound sessions. This can work if the user has a 
NAT and configures it such that inbound sessions are forwarded 
appropriately, but it can NOT work if the NATting is done by a service 
provider of some kind without any way for the user to configure this 
NAT box.

> The scalability of
> these protocols has threatened the Music and Movie Industries--and 
> thats
> really something.  I wouldn't have thought such a thing possible ten 
> years
> ago.

So what else is new. In Shakespeare's time there were people that went 
to plays, memorizing them for later copying and performing the play 
without paying the author. And remember these are the same people that 
thought the VCR would kill their business.




From owner-ietf@ietf.org  Mon Jan 19 19:04:13 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17838
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 19:04:13 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AijI2-0005wX-Ka
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 18:58:42 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AijHC-0005td-UP
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 18:57:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17413
	for <ietf@ietf.org>; Mon, 19 Jan 2004 18:57:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AijGw-0001UR-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:57:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AijDJ-00017s-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:53:50 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AijA7-0000tw-00
	for ietf@ietf.org; Mon, 19 Jan 2004 18:50:31 -0500
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com; Mon, 19 Jan 2004 18:50:30 -0500
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Mark Smith <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: P2P - Crime / NAT
Cc: ietf@ietf.org
Date: Mon, 19 Jan 2004 18:50:30 -0500
Message-ID: <20040119235030168.AAA71@hq.lindsayelec.com@rflooker1>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>This really doesn't say much about the scalability of the
>solution. What it indicates is how much effort people are
>willing to go to to commit what is perceived as victimless crime.

Two things.
First, here in Canada there is a new tax on "media" like writable CD's;
(extendable to Memory cards, or anything that likely holds licenced media).
And this ostensibly is redistributed to the artists via some sort of audit
like Arbitron, etc. So, at least here downloading movies, etc is part of a
transaction. Apparently, oddly its legal to download music specifically...
but MAYBE isn't legal; to offer it on a permenently available server ...
with what constitutes a "server" intentionally vague. 

Law is a work around by its very nature. It only pretends precision.

Second: If/When I start a residential gateway I think I will do everything
possible to make it IpNG capable. Thanks everyone for talking me into it.
I'm trying to study it in detail a little every evening to get ready. I hope
cable TV (my industry) get with the program and do this right. These little
boxes glued all over the networks with there http interfaces... are not
specifically too good. If anything will force the issue its going to be SIP
I think.

Does anyone know when/if Microsoft is bring out a consumer operating system
with IpV6 in it? That would be useful for market acceptance...???

regs
Dan




From owner-ietf@ietf.org  Mon Jan 19 19:34:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19418
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 19:34:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AijdT-0007Ry-6I
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 19:20:51 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AijcL-0007LK-GD
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 19:19:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18492
	for <ietf@ietf.org>; Mon, 19 Jan 2004 19:19:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aijbz-00030E-00
	for ietf@ietf.org; Mon, 19 Jan 2004 19:19:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AijU7-0002U0-00
	for ietf@ietf.org; Mon, 19 Jan 2004 19:11:12 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AijQA-00020c-00
	for ietf@ietf.org; Mon, 19 Jan 2004 19:07:06 -0500
Received: from rc-dmz.felix.nlri.ca ([192.5.4.54] helo=felix.automagic.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AijCR-0008AA-1z
	for ietf@ietf.org; Mon, 19 Jan 2004 18:52:55 -0500
Received: from [199.212.90.24] (helo=[199.212.90.24])
	by felix.automagic.org with asmtp (TLSv1:RC4-SHA:128)
	(Exim 4.20)
	id 1AijBx-0007CE-WD; Mon, 19 Jan 2004 23:52:26 +0000
In-Reply-To: <Pine.LNX.4.44.0401191606230.8290-100000@cirrus>
References: <Pine.LNX.4.44.0401191606230.8290-100000@cirrus>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <86898BEE-4ADA-11D8-A539-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@cs.utk.edu>, Iljitsch van Beijnum <iljitsch@muada.com>,
        IETF Discussion <ietf@ietf.org>
From: Joe Abley <jabley@isc.org>
Subject: Re: dubious assumptions about IPv6 (was death of the Internet)
Date: Mon, 19 Jan 2004 18:52:22 -0500
To: Dean Anderson <dean@av8.com>
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On 19 Jan 2004, at 16:36, Dean Anderson wrote:

> No, its not at all like saying that.  Its like saying that residential
> phone users don't need a globally unique circuit facilities assignment
> (CFA)  number.

They do if you want them to be able to receive phone calls from anybody 
else in the world without requiring the call to be switched through 
intermediaries with overlapping address scope.

Decentralising the business of call switching to the edge is surely the 
attractive aspect of voip. If you require calls to be switched through 
third parties, you're just reinventing the PSTN and all its attendant 
baggage using a different transport, and there's nothing particularly 
innovative or disruptive in that.


Joe




From owner-ietf@ietf.org  Mon Jan 19 19:39:35 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19822
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 19:39:35 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aijrt-0008DN-Nz
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 19:35:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aijkc-0007iU-L4
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 19:28:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18796
	for <ietf@ietf.org>; Mon, 19 Jan 2004 19:28:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AijkR-0003ae-00
	for ietf@ietf.org; Mon, 19 Jan 2004 19:28:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aijfi-0003Ey-00
	for ietf@ietf.org; Mon, 19 Jan 2004 19:23:11 -0500
Received: from 134.cust17.nsw.dsl.ozemail.com.au ([203.103.104.134] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AijYQ-0002n5-00
	for ietf@ietf.org; Mon, 19 Jan 2004 19:15:38 -0500
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 172F03F02A; Tue, 20 Jan 2004 10:44:47 +1030 (CST)
Date: Tue, 20 Jan 2004 10:44:46 +1030
From: Mark Smith <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
To: dank@hq.lindsayelec.com (Dan Kolis)
Cc: ietf@ietf.org
Subject: Re: P2P - Crime / NAT
Message-Id: <20040120104446.21ffe282.ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
In-Reply-To: <20040119235030168.AAA71@hq.lindsayelec.com@rflooker1>
References: <20040119235030168.AAA71@hq.lindsayelec.com@rflooker1>
Organization: The No Sense Organisation (http://www.nosense.org)
X-Mailer: Sylpheed version 0.9.8a (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Mon, 19 Jan 2004 18:50:30 -0500
dank@hq.lindsayelec.com (Dan Kolis) wrote:

> >This really doesn't say much about the scalability of the
> >solution. What it indicates is how much effort people are
> >willing to go to to commit what is perceived as victimless
> >crime.
> 
> Two things.
> First, here in Canada there is a new tax on "media" like
> writable CD's;(extendable to Memory cards, or anything that
> likely holds licenced media). And this ostensibly is
> redistributed to the artists via some sort of audit like
> Arbitron, etc. So, at least here downloading movies, etc is
> part of a transaction. Apparently, oddly its legal to download
> music specifically... but MAYBE isn't legal; to offer it on a
> permenently available server ... with what constitutes a
> "server" intentionally vague. 
>

Fortunately I don't live in Canada. Other wise, I would have now
started downloading music (as I never have before), because I now
wouldn't have a choice as to whether I pay for it or not.

 
> Law is a work around by its very nature. It only pretends
> precision.
> 
> Second: If/When I start a residential gateway I think I will do
> everything possible to make it IpNG capable. Thanks everyone
> for talking me into it. I'm trying to study it in detail a
> little every evening to get ready. I hope cable TV (my
> industry) get with the program and do this right. These little
> boxes glued all over the networks with there http interfaces...
> are not specifically too good. If anything will force the issue
> its going to be SIP I think.
> 
> Does anyone know when/if Microsoft is bring out a consumer
> operating system with IpV6 in it? That would be useful for
> market acceptance...???
> 

I'm no expert (don't use MS OS anymore), but I understand that
IPv6 already comes with XP. Apparently, it is a simple one-line
command to install it.

From what I've heard, the major thing missing would be NetBIOS
over IPv6 a.k.a. Microsoft File and Print sharing over IPv6.

Regards,
Mark.




From owner-ietf@ietf.org  Mon Jan 19 19:41:04 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19888
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 19:41:04 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aijrz-0008FF-TK
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 19:35:51 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AijmP-0007k1-Qk
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 19:30:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18892
	for <ietf@ietf.org>; Mon, 19 Jan 2004 19:30:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AijmN-0003hG-00
	for ietf@ietf.org; Mon, 19 Jan 2004 19:30:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aijgv-0003Kx-00
	for ietf@ietf.org; Mon, 19 Jan 2004 19:24:26 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AijbG-0002uw-00
	for ietf@ietf.org; Mon, 19 Jan 2004 19:18:34 -0500
Content-class: urn:content-classes:message
Subject: RE: dubious assumptions about IPv6 (was death of the Internet)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Jan 2004 16:17:55 -0800
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DAE0C@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: dubious assumptions about IPv6 (was death of the Internet)
thread-index: AcPe51atSu9x5oA1RqS+Ldri8txeBgAAzT+w
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
Cc: "IETF Discussion" <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Iljitsch van Beijnum wrote:
> These protocols require that at least one
> side in each transfer is capable of
> receiving inbound sessions.

This is not true. Kaaza does not require to open any ports nor configure
anything in the NAT box. The latest versions of SIP using STUN don't
either.

Michel.




From owner-ietf@ietf.org  Mon Jan 19 20:55:13 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22408
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 20:55:13 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aikwb-0004Cb-TB
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 20:44:41 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aikvy-0004A8-6I
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 20:44:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22053
	for <ietf@ietf.org>; Mon, 19 Jan 2004 20:44:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aikvw-0000hh-00
	for ietf@ietf.org; Mon, 19 Jan 2004 20:44:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aikv1-0000f7-00
	for ietf@ietf.org; Mon, 19 Jan 2004 20:43:03 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aikun-0000cb-00
	for ietf@ietf.org; Mon, 19 Jan 2004 20:42:49 -0500
Received: from dank ([191.1.2.3]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com for <ietf@ietf.org>;
          Mon, 19 Jan 2004 20:42:48 -0500
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: Effectiveness of STUN protocol
Date: Mon, 19 Jan 2004 20:42:48 -0500
Message-ID: <20040120014248368.AAA71@hq.lindsayelec.com@dank>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Michel said:
>This is not true. Kaaza does not require to open any ports nor configure
>anything in the NAT box. The latest versions of SIP using STUN don't
>either.

Dan asks:

Yes indeed. Probably the #1 biggest use for STUN short term is going to be
SIP. It seems like not too much information has to go thru the known
reachable machine. Maybe just about the same loading as a DNS server?

So, although its kind of a work around, its probably going to do the job.

Does that seem right?

Dan





From owner-ietf@ietf.org  Mon Jan 19 20:55:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22426
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 20:55:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ail0U-0004Nn-0a
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 20:48:42 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aikzx-0004Kb-AV
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 20:48:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22212
	for <ietf@ietf.org>; Mon, 19 Jan 2004 20:48:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aikzv-0000zw-00
	for ietf@ietf.org; Mon, 19 Jan 2004 20:48:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aikyz-0000vd-00
	for ietf@ietf.org; Mon, 19 Jan 2004 20:47:09 -0500
Received: from 59.cust18.nsw.dsl.ozemail.com.au ([203.103.105.59] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AikyM-0000ph-00
	for ietf@ietf.org; Mon, 19 Jan 2004 20:46:30 -0500
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 377043F02A; Tue, 20 Jan 2004 12:15:42 +1030 (CST)
Date: Tue, 20 Jan 2004 12:15:42 +1030
From: Mark Smith <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: iljitsch@muada.com, ietf@ietf.org
Subject: Re: dubious assumptions about IPv6 (was death of the Internet)
Message-Id: <20040120121542.6a39f5ac.ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B0DAE0C@server2003.arneill-py.sacramento.ca.us>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B0DAE0C@server2003.arneill-py.sacramento.ca.us>
Organization: The No Sense Organisation (http://www.nosense.org)
X-Mailer: Sylpheed version 0.9.8a (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Mon, 19 Jan 2004 16:17:55 -0800
"Michel Py" <michel@arneill-py.sacramento.ca.us> wrote:

> > Iljitsch van Beijnum wrote:
> > These protocols require that at least one
> > side in each transfer is capable of
> > receiving inbound sessions.
> 
> This is not true. Kaaza does not require to open any ports nor
> configure anything in the NAT box. 

Here is how the Kaaza Skype proprietory VoIP network gets around
NAT (from http://www.skype.com/skype_p2pexplained.html) :

"Firewall and NAT (Network Address Translation) traversal:

Non-firewalled clients and clients on publicly routable IP
addresses are able to help NAT?ed nodes to communicate by routing
calls. This allows two clients who otherwise would not be able to
communicate to speak with each other. Because the calls are
encrypted end-to-end, proxies present no security or privacy
risk.

Likewise, only proxies with available spare resources are chosen
so that the performance for these users is not affected.

Several new techniques were also developed in order to avoid
end-user configuration of gateways and firewalls, whose
non-intuitive configuration settings typically prohibit the
majority of users from communicating successfully. In short,
Skype works behind the majority of firewalls and gateways with no
special configuration."

Of course, if the non-NATted peer goes off line, the phone call
dies.

Also, at least here in Australia, were ADSL/broadband plans are
typically download capped (eg. I have 4000MB per month download),
the non-NATted peer ends up paying for Skype VoIP traffic for
phone calls they are not even part of. Nice (said with typical
Australian sarcasm).

What makes it worse is that most people who would use Skype are
likely to be technology or networking neophytes, and those who
are the non-NATted peers are unlikely to be able to easily
workout where their additional traffic is coming from. They will
call up their ISP, complaining about wrong billing, the ISP will
spend time investigating. The ISPs support costs will increase,
which will be passed onto all customers, increasing the cost of
the Internet service. This is one example of a hidden cost of
NAT.

Further more, the effectiveness of the Skype NAT solution becomes
less and less as NAT becomes more prevalent, which is probable
with the perceived "security" of NAT, and the use of IPv4 address
"scarcity" by ISPs to differentiate between residential and
business products. This Skype solution, in the longer term, is
a dead end street solution. That's assuming the big
telcos don't set up "public" NAT exchange points for the Skype
network, which I'm sure they (as they can then bill calls), and
the various government intelligence agencies would love (as they
may be able then tap phone calls, or at least perform traffic
anaylsis.).

Of course, it also breaks the end-to-end model, but that is
inherent in NAT anyway.

(As Skype apparently does encrypt the phone calls, so
man-in-the-middle attacks from the non-NATted peer are not a
problem, unless the implementation has bugs.)

The latest versions of SIP using STUN don't
> either.
>

Does SIP with STUN use similar techniques to Skype to get around
two NATted VoIP peers ?

Regards,
Mark. 



From owner-ietf@ietf.org  Mon Jan 19 21:27:51 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23852
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 21:27:51 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AilXN-0006au-Mi
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 21:22:41 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AilUn-0006VH-Bo
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 21:20:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23576
	for <ietf@ietf.org>; Mon, 19 Jan 2004 21:19:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AilUl-00034W-00
	for ietf@ietf.org; Mon, 19 Jan 2004 21:19:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AilTo-00032E-00
	for ietf@ietf.org; Mon, 19 Jan 2004 21:19:01 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AilT9-000302-00
	for ietf@ietf.org; Mon, 19 Jan 2004 21:18:20 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id i0K2IIbt089629
	for ietf@ietf.org env-from <vjs>;
	Mon, 19 Jan 2004 19:18:18 -0700 (MST)
Date: Mon, 19 Jan 2004 19:18:18 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200401200218.i0K2IIbt089629@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: The IETF Mission
References: <400C6AC5.CAC5A830@swin.edu.au>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: grenville armitage <garmitage@swin.edu.au>

> ...
> then that's a problem we can fix without creating an indestructable I-Ds.
> ...

IETF rules to the contrary, I-Ds are indestructable for anyone who
cares to look for them.  Every several months I'm moved to point to
classic I-Ds that should have been destroyed as proof that almost
anyone can submit an I-D that says almost anything, no matter
how...ah...controversial.  I have never failed to find copies somewhere
on the net.  Today the only aspect of an I-D that expires after 6 months 
is the endorsement implicit in a copy at venera.isi.edu or www.ietf.org.

Today an endorsement of some sort is the only difference between having
your ideas heard by self-publishing and having them officially published.
The web is taking us a major step forward to 400 or 500 years ago when
good ideas were self-published and readers didn't need the moderation
of a Rupert Murdoch or the IETF.  I don't know what the academic
publish-or-perish, RIAA, and other commercial and mass media worlds
will do to replace their citation indecies, royalties, and advertising
revenues, and I don't much care.

I'm not saying anything against WGs producing Informational RFCs. 
I'm only pointing out that calls to have the IETF Mission Statement
"broaden the scope and quantity of documents to be published" suggest
ignorance of search engines or needs to have things endorsed by the IETF.


] From: Fred Baker <fred@cisco.com>

] I don't know that we're changing anything in what the IETF does. What is 
] happening is that the IETF is growing up and taking control of its own 
] destiny in a variety of ways, and trying to clean up its own processes. In 
] all the *other* problems it tries to solve, the IETF tries to say what 
] problem it is solving sometime before finishing solving it, if for no other 
] reason so that it can decide whether it did in fact solve it. Same here.

The facilitators hired by H-R departments to run mission statement
"off-sites" always say all of that.  They are always perfectly sincere
and well meaning.  Those good intentions do not change the fact that
trying to write a mission statement changes the organization.  If an
organization lacks an unstated consensus purpose, then writing a mission
statement is unlikely to create one.  On the other hand, trying to
write one exposes any lack of consensus and turns into a race to the
Dilbert Standard of advocating all virtues, condemning all vices, and
creating new mandates such as "ad hoc WGs" and "archived I-Ds."

You could be right and I might be wrong if much this thread were not
filled with talk about turning the IETF an unfunded Reed Elsevier.

] ...
] Once we have decided that we did in fact solve the problem before us, I 
] don't know that the bumper sticker gets us all that much further. But the 
] bumper sticker can be helpful when we are asking the questions "what are we 
] trying to accomplish?" and "are we accomplishing it?".

It's one thing to consider those questions and something else to write
a "mission statement."  Mission statement facilitators always say the
only purpose is to consider those to questions, but the results are
what they always are.  Those results are related to the fact that they're
officiously titled "Mission Statements" instead of "ad hoc comments
about what we're trying to do and how well we're doing it."

I know many of you must have been through Mission Statement charades.
Have you ever seen one that with 12 months hindsight was not a waste
of time or worse?  My personal experience suggests that "write a mission
statement" means the same as "jump the shark."  See
http://www.google.com/search?q=%22jump+the+shark%22


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Mon Jan 19 21:31:06 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23958
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 21:31:06 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AilcH-0006up-Rs
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 21:27:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AilbX-0006rm-8O
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 21:26:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23836
	for <ietf@ietf.org>; Mon, 19 Jan 2004 21:26:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AilbV-0003RS-00
	for ietf@ietf.org; Mon, 19 Jan 2004 21:26:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ailaj-0003PY-00
	for ietf@ietf.org; Mon, 19 Jan 2004 21:26:09 -0500
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1AilZj-0003M3-00
	for ietf@ietf.org; Mon, 19 Jan 2004 21:25:07 -0500
Received: (qmail 71850 invoked from network); 20 Jan 2004 02:33:57 -0000
Received: from h219-110-033-058.catv01.itscom.jp (HELO necom830.hpcl.titech.ac.jp) (219.110.33.58)
  by necom830.hpcl.titech.ac.jp with SMTP; 20 Jan 2004 02:33:57 -0000
Message-ID: <400C91BA.4070105@necom830.hpcl.titech.ac.jp>
Date: Tue, 20 Jan 2004 11:26:02 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Dan Kolis <dank@hq.lindsayelec.com>
CC: ietf@ietf.org
Subject: Re: Effectiveness of STUN protocol
References: <20040120014248368.AAA71@hq.lindsayelec.com@dank>
In-Reply-To: <20040120014248368.AAA71@hq.lindsayelec.com@dank>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dan Kolis;

> Yes indeed. Probably the #1 biggest use for STUN short term is going to be
> SIP. It seems like not too much information has to go thru the known
> reachable machine. Maybe just about the same loading as a DNS server?

Wrong. For a host to receive external calls, the binding on a
NAT box must be active all the time that periodic refresh is
required.

OTOH, DNS query is necessary only on demands when a host want to
initiate external calls.

						Masataka Ohta





From owner-ietf@ietf.org  Mon Jan 19 22:08:31 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25450
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 22:08:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aim4R-0000kO-Jc
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 21:56:51 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aim3x-0000hD-ND
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 21:56:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24986
	for <ietf@ietf.org>; Mon, 19 Jan 2004 21:56:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aim3v-0005PX-00
	for ietf@ietf.org; Mon, 19 Jan 2004 21:56:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aim2q-0005Fg-00
	for ietf@ietf.org; Mon, 19 Jan 2004 21:55:13 -0500
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aim0Q-0004zm-00
	for ietf@ietf.org; Mon, 19 Jan 2004 21:52:43 -0500
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id NAA857907;
	Tue, 20 Jan 2004 13:51:41 +1100 (EST)
Message-ID: <400C97BC.1982739B@swin.edu.au>
Date: Tue, 20 Jan 2004 13:51:40 +1100
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The IETF Mission
References: <400C6AC5.CAC5A830@swin.edu.au> <200401200218.i0K2IIbt089629@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Vernon Schryver wrote:
> 
> > From: grenville armitage <garmitage@swin.edu.au>
> 
> > ...
> > then that's a problem we can fix without creating an indestructable I-Ds.
> > ...
	[..]
> I have never failed to find copies somewhere
> on the net.  Today the only aspect of an I-D that expires after 6 months
> is the endorsement implicit in a copy at venera.isi.edu or www.ietf.org.

That's the extent of my observation. The implicit endorsement of
storing an I-D at www.ietf.org should be temporary. If people want to
store/publish/whatever a document elsewhere, well, that's fine and dandy.
This thread was (I thought) about an IETF-endorsed archivive of I-Ds,
which I object to as unnecessary. I suspect we may agree.

cheers,
gja



From owner-ietf@ietf.org  Mon Jan 19 22:12:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25716
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 22:12:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AimFt-0001Dq-9f
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 22:08:41 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aim7a-0000th-2B
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 22:00:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25242
	for <ietf@ietf.org>; Mon, 19 Jan 2004 22:00:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aim7Y-0005iV-00
	for ietf@ietf.org; Mon, 19 Jan 2004 22:00:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aim6g-0005g9-00
	for ietf@ietf.org; Mon, 19 Jan 2004 21:59:11 -0500
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aim6L-0005ck-00
	for ietf@ietf.org; Mon, 19 Jan 2004 21:58:49 -0500
Received: from cirrus ([130.105.36.66])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id WAA26525;
	Mon, 19 Jan 2004 22:57:45 -0500
Date: Mon, 19 Jan 2004 21:49:38 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: dubious assumptions about IPv6 (was death of the Internet)
In-Reply-To: <EC665140-4AD8-11D8-9871-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0401192127020.31881-100000@cirrus>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 20 Jan 2004, Iljitsch van Beijnum wrote:

> On 19-jan-04, at 23:55, Dean Anderson wrote:
> 
> > As Kazaa, Napster, Groove, and other protocols have demonstrated, its
> > quite easy to create peer-to-peer applications without either expensive
> > external infrastructure or fixed, unique IP addresses.
> 
> These protocols require that at least one side in each transfer is 
> capable of receiving inbound sessions. This can work if the user has a 
> NAT and configures it such that inbound sessions are forwarded 
> appropriately, but it can NOT work if the NATting is done by a service 
> provider of some kind without any way for the user to configure this 
> NAT box.

It can't work only if Both users have NATs with no inbound access.  

A simple connection broker can probably make this work even with both
sides having no inbound access.  While external, this wouldn't quite be
'expensive external infrastructure'.

> So what else is new. In Shakespeare's time there were people that went 
> to plays, memorizing them for later copying and performing the play 
> without paying the author. And remember these are the same people that 
> thought the VCR would kill their business.

Duplicating VCR tapes, DVDs, and CDrom's is still relatively
expensive--more so than sharing files over Kazaa.  I'm against the DMCA,
but the old situation is qualitatively and quantitatively different from
today's filesharing.  You used to pay perhaps half the price for an
inferior product.  That's an easy proposition to resist.  Now you get the
same quality for free.  That is much harder to resist.  When there is no
expensive infrastructure necessary to support the activity, it is much
harder to stop.  I can see why that is alarming.

		--Dean




From owner-ietf@ietf.org  Mon Jan 19 23:23:19 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28539
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 23:23:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AinLd-0005Fa-L3
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 23:18:41 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AinL5-0005CW-2G
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 23:18:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28300
	for <ietf@ietf.org>; Mon, 19 Jan 2004 23:18:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AinL3-0002e4-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:18:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AinK5-0002ax-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:17:06 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AinJW-0002X1-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:16:30 -0500
Content-class: urn:content-classes:message
Subject: RE: Effectiveness of STUN protocol
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Jan 2004 20:16:20 -0800
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DAE0D@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Effectiveness of STUN protocol
thread-index: AcPe/Zekux0sB5gMQFa/zwCYWlczgAAB8S+g
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>,
        "Dan Kolis" <dank@hq.lindsayelec.com>
Cc: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

>> Dan Kolis wrote:
>> Yes indeed. Probably the #1 biggest use for STUN short
>> term is going to be SIP. It seems like not too much
>> information has to go thru the known reachable machine.
>> Maybe just about the same loading as a DNS server?

> Masataka Ohta wrote:
> Wrong.

No. _you_ are wrong, Dan is right, it's a glorified DNS server that
instead of resolving names to addresses resolves names to addresses +
ports. In case of P2P, there is also the load associated with searches.

So, two hosts behind NAT can't talk if they don't have a port open can
they?
Here's how it works:

- Dan and Michel are two hosts behind NAT. They both use the same P2P
app. Both their NAT boxes are default config, no ingress open.
- Dan wants to download the file "unforgiven.mp3" that Michel has.

- Michel opens a connection to the P2P server.
- Michel to P2p server: I have "unforgiven.mp3"
- Dan opens a connection to the P2P server.
- Dan to P2P server: search "unforgiven.mp3"
- P2P server to Dan: Michel has it, his IP
  address is M.I.P.A
  (P2P server knows Michel's public address as
  being the src address on Michel's open session)
- Dan to Michel: UDP packet, src port randomA,
  dst port randomB, "hello".
  (this packet is discarded at Michel's NAT but
  opens the NAT hole on Dan's NAT).
- Dan to P2P server: tell Michel that I need to
  talk on randomA, randomB.
- P2P server to Michel: BTW, Dan at IP D.I.P.A
  needs to talk to you on randomA, randomB.
- Michel to Dan: UDP packet, src port randomB,
  dst port randomA, "hi there, what is the name
  of the pirated mp3 you want?".
  (this opens the NAT hole on Michel's NAT _and_
  does reach Dan's host, as the hole was opened
  before).
- Dan to Michel (direct, now goes through):
  "unforgiven.mp3"

Voila.

If you don't understand/can't code what's above, don't worry: I know
plenty of 16-years-old that can code it for me in exchange for the
latest 60GB mp3 player.

Michel.

P.S. I never had "unforgiven.mp3". Metallica is not the kind of stuff I
listen to.




From owner-ietf@ietf.org  Mon Jan 19 23:30:34 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29076
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 23:30:34 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AinTN-0006Gx-8g
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 23:26:41 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AinRj-00063d-DW
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 23:24:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28574
	for <ietf@ietf.org>; Mon, 19 Jan 2004 23:24:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AinRh-00039o-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:24:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AinQi-00030U-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:23:57 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AinPo-0002vm-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:23:01 -0500
Content-class: urn:content-classes:message
Subject: RE: dubious assumptions about IPv6 (was death of the Internet)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Jan 2004 20:22:51 -0800
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DAE0E@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: dubious assumptions about IPv6 (was death of the Internet)
thread-index: AcPe9zFyZO5+X6DgQGmMWFqqjehwtQAFVMlg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Mark Smith" <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
Cc: "Iljitsch van Beijnum" <iljitsch@muada.com>, <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Mark Smith wrote:
> Does SIP with STUN use similar techniques to Skype
> to get around two NATted VoIP peers ?

I have to confess that I have not read STUN in much detail, but I
understand that one of the "novelties" is that the STUN server replies
to the originating SIP client what its public address is, enabling the
SIP client to embed the valid public address in the packet instead of
the only one it knows which is RFC1918. Combine with what I just
posted...

I encourage my competitors to keep wasting their energy whining about
how NAT breaks their apps: as long as I have an ample supply of
16-years-old that can code how to traverse it I don't have a problem
with it.

Michel.




From owner-ietf@ietf.org  Mon Jan 19 23:43:09 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29376
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 23:43:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ainez-0007OK-GF
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 23:38:41 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aine6-0007JV-7u
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 23:37:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29203
	for <ietf@ietf.org>; Mon, 19 Jan 2004 23:37:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aindu-0003vZ-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:37:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AinZv-0003lc-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:33:27 -0500
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AinYY-0003eO-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:32:02 -0500
Received: from inet-vrs-04.redmond.corp.microsoft.com ([157.54.8.149]) by mail4.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 19 Jan 2004 20:31:03 -0800
Received: from 157.54.8.23 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 19 Jan 2004 20:31:08 -0800
Received: from RED-IMC-04.redmond.corp.microsoft.com ([157.54.2.168]) by inet-hub-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 19 Jan 2004 20:31:03 -0800
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, 19 Jan 2004 20:31:26 -0800
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Mon, 19 Jan 2004 20:31:06 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7150.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Effectiveness of STUN protocol
Date: Mon, 19 Jan 2004 20:31:09 -0800
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA06FB62FF@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Effectiveness of STUN protocol
Thread-Index: AcPe+QTHj1qyTmtsSPqZPYnxgvdpmAAExo2g
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Dan Kolis" <dank@hq.lindsayelec.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 20 Jan 2004 04:31:06.0842 (UTC) FILETIME=[38965BA0:01C3DF0E]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Yes indeed. Probably the #1 biggest use for STUN short term is going
to be
> SIP. It seems like not too much information has to go thru the known
> reachable machine. Maybe just about the same loading as a DNS server?
>=20
> So, although its kind of a work around, its probably going to do the
job.
>=20
> Does that seem right?

Well, sort off.=20

STUN is indeed a great protocol, with all the right authors, but it
makes a couple of assumptions about the type of NATs and about the
structure of the network.=20

The assumption about NAT boxes tend to be correct, mostly because
vendors know about STUN and about similar workaround used by various
video-games manufacturers as well as by some IPv6 services (Teredo).
Most new NATs adopt the "cone" or "protected cone" model that work for
STUN, rather than the so call "symmetric" model. But there are still
some old fashioned designs that try hard to break things, so YMMV.

The assumption about topology is more likely to be wrong. STUN works
well in a "core and leaves" model in which privates networks are
directly to a globally addressed IPv4 core, with a single NAT. In this
model, two STUN hosts are either on the same private network, or
connected through the core. Things get much harder when there are
multiple layers of NAT, or when there are backdoor connections between
private networks.

STUN is an OK solution now, but it will stop working when the topology
becomes more complex -- communications will randomly fail. It is just as
easy to deploy IPv6 using Teredo now. As we go on deploying IPv6, we
have a chance to support these more complex topologies.

-- Christian Huitema



From owner-ietf@ietf.org  Tue Jan 20 00:02:37 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00469
	for <ietf-web-archive@odin.ietf.org>; Tue, 20 Jan 2004 00:02:37 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AinwP-0000Q7-BK
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 23:56:41 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ainvn-0000N1-ME
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 23:56:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00306
	for <ietf@ietf.org>; Mon, 19 Jan 2004 23:56:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ainvl-0005T9-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:56:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ainux-0005QX-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:55:11 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AinuD-0005IR-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:54:25 -0500
Content-class: urn:content-classes:message
Subject: RE: Effectiveness of STUN protocol
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Jan 2004 20:54:15 -0800
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DAE10@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Effectiveness of STUN protocol
thread-index: AcPe+QTHj1qyTmtsSPqZPYnxgvdpmAAExo2gAAEJO+A=
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Christian Huitema" <huitema@windows.microsoft.com>,
        "Dan Kolis" <dank@hq.lindsayelec.com>, <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Christian Huitema wrote:
> STUN is indeed a great protocol, with all the right
> authors, but it makes a couple of assumptions about the
> type of NATs and about the structure of the network.

Indeed, but its assumptions are well in line with the predicted
clientele: home/soho.

We were talking about SIP; enterprises do not have too much of a problem
with SIP and NAT, because a) they have a somehow knowledgeable staff b)
they can deploy gateways/proxies/whatever at the edge of their network,
where NAT occurs. If SIPPhone and FWD can deploy SIP proxies, so can
Microsoft, Cisco, and a bunch of others. SIPPhone, FWD and consorts do
already connect together and there are beta tests to connect private
Call Manager domains to them.

Michel.




From owner-ietf@ietf.org  Tue Jan 20 00:05:43 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00677
	for <ietf-web-archive@odin.ietf.org>; Tue, 20 Jan 2004 00:05:43 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aio1F-0000gn-RQ
	for ietf-list@asgard.ietf.org; Tue, 20 Jan 2004 00:01:41 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aio0e-0000da-Du
	for ietf@asgard.ietf.org; Tue, 20 Jan 2004 00:01:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00428
	for <ietf@ietf.org>; Tue, 20 Jan 2004 00:01:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aio0c-0005hh-00
	for ietf@ietf.org; Tue, 20 Jan 2004 00:01:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ainzk-0005fQ-00
	for ietf@ietf.org; Tue, 20 Jan 2004 00:00:08 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AinzA-0005b2-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:59:32 -0500
Content-class: urn:content-classes:message
Subject: RE: Effectiveness of STUN protocol
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Jan 2004 20:59:22 -0800
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DAE11@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Effectiveness of STUN protocol
thread-index: AcPe+QTHj1qyTmtsSPqZPYnxgvdpmAAExo2gAAFcpfA=
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Christian Huitema" <huitema@windows.microsoft.com>,
        "Dan Kolis" <dank@hq.lindsayelec.com>, <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Christian Huitema wrote:
> It is just as easy to deploy IPv6 using Teredo now.

Yeah right. Find me a Teredo client (not to mention any IPv6 in the
first place) for

Grandstream:
http://www.grandstream.com/y-product.htm

Or Sipura:
http://www.sipura.com/products/spa2000.htm

The internet is _not_ limited to Microsoft and Cisco, BTW.

Michel.




From owner-ietf@ietf.org  Tue Jan 20 00:11:13 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28541
	for <ietf-web-archive@odin.ietf.org>; Mon, 19 Jan 2004 23:23:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AinI7-0004yF-Fl
	for ietf-list@asgard.ietf.org; Mon, 19 Jan 2004 23:15:03 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AinEJ-0004u4-97
	for ietf@asgard.ietf.org; Mon, 19 Jan 2004 23:11:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27986
	for <ietf@ietf.org>; Mon, 19 Jan 2004 23:11:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AinEG-0002Be-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:11:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AinDN-00028I-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:10:09 -0500
Received: from sccrmhc12.comcast.net ([204.127.202.56])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AinCZ-00021h-00
	for ietf@ietf.org; Mon, 19 Jan 2004 23:09:19 -0500
Received: from dfnjgl21 (c-24-1-97-129.client.comcast.net[24.1.97.129])
          by comcast.net (sccrmhc12) with SMTP
          id <20040120040849012002da45e>
          (Authid: sdawkins@comcast.net);
          Tue, 20 Jan 2004 04:08:49 +0000
Message-ID: <01f701c3df0b$1cf071e0$0400a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf@ietf.org>
References: <200401191901.i0JJ1OU26110@boreas.isi.edu>
Subject: Re: The IETF Mission
Date: Mon, 19 Jan 2004 22:08:50 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: "Bob Braden" <braden@ISI.EDU>
To: <ietf@ietf.org>; <garmitage@swin.edu.au>
Sent: Monday, January 19, 2004 1:01 PM
Subject: Re: The IETF Mission

>   *> Is the standard for Informational currently that onerous?
>
> Certainly not.  But the community (and especially its chosen
> leadership) need to believe in the importance of using Informational
> to capture important documents and ideas as RFCs.
>
> Bob Braden

Just to be clear - in
http://www1.ietf.org/mail-archive/ietf/Current/msg23935.html I made a
snotty remark wondering what the average time-to-publish from first
draft to RFC for Informational RFCs is.

I was trying to say what Bob said more clearly (first time that's
happened today, of course). If you look up "Informational RFC" in
2026, it's not that bad. If we lived in the world of 2026, we would
publish more of them, especially individual drafts. HIP Architecture
is a wonderful example of an Informational RFC-to-be.

Spencer




From owner-ietf@ietf.org  Tue Jan 20 02:55:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17927
	for <ietf-web-archive@odin.ietf.org>; Tue, 20 Jan 2004 02:55:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aiqau-0001FI-V9
	for ietf-list@asgard.ietf.org; Tue, 20 Jan 2004 02:46:40 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiqYy-0001B9-T8
	for ietf@asgard.ietf.org; Tue, 20 Jan 2004 02:44:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17477
	for <ietf@ietf.org>; Tue, 20 Jan 2004 02:44:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiqYm-0004iW-00
	for ietf@ietf.org; Tue, 20 Jan 2004 02:44:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiqWi-0004b6-00
	for ietf@ietf.org; Tue, 20 Jan 2004 02:42:20 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiqTz-0004Tl-00
	for ietf@ietf.org; Tue, 20 Jan 2004 02:39:31 -0500
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i0K7d0qY014497;
	Tue, 20 Jan 2004 08:39:00 +0100 (MET)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <ZJBTXXTH>; Tue, 20 Jan 2004 08:40:50 +0100
Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D03F52C7C@Esealnt877.al.sw.ericsson.se>
From: "Yuri Ismailov (KI/EAB)" <yuri.ismailov@ericsson.com>
To: "'dank@hq.lindsayelec.com'" <dank@hq.lindsayelec.com>,
        Mark Smith
	 <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
Cc: ietf@ietf.org
Subject: RE: P2P - Crime / NAT
Date: Tue, 20 Jan 2004 08:33:36 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Ipv6 works in WinXP. Latest developer SDK support socket programing over v6.
No NetBIOS.
Disabling of pseudo interfaces can be done by stopping 6to4 service.
This may be useful if there is a global IPv6 configured. Otherwise OS returns the whole bunch of IPv6 addresses and in some cases, when needed, the code should take care of which one to choose. This is the case with latest java_1.5.0 to my knowledge.
Programming aplications, which are both v6 and v4 aware is quite a pain but may be achieved as well.
Win2000 can use IPv6 as well. I got working MS Research prerelease under Win2000 and it is not different from what you get in XP. However, requires separate download and some SP number. If remember correctly should be at least 2.

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org]On Behalf Of
dank@hq.lindsayelec.com
Sent: den 20 januari 2004 00:51
To: Mark Smith
Cc: ietf@ietf.org
Subject: P2P - Crime / NAT


>This really doesn't say much about the scalability of the
>solution. What it indicates is how much effort people are
>willing to go to to commit what is perceived as victimless crime.

Two things.
First, here in Canada there is a new tax on "media" like writable CD's;
(extendable to Memory cards, or anything that likely holds licenced media).
And this ostensibly is redistributed to the artists via some sort of audit
like Arbitron, etc. So, at least here downloading movies, etc is part of a
transaction. Apparently, oddly its legal to download music specifically...
but MAYBE isn't legal; to offer it on a permenently available server ...
with what constitutes a "server" intentionally vague. 

Law is a work around by its very nature. It only pretends precision.

Second: If/When I start a residential gateway I think I will do everything
possible to make it IpNG capable. Thanks everyone for talking me into it.
I'm trying to study it in detail a little every evening to get ready. I hope
cable TV (my industry) get with the program and do this right. These little
boxes glued all over the networks with there http interfaces... are not
specifically too good. If anything will force the issue its going to be SIP
I think.

Does anyone know when/if Microsoft is bring out a consumer operating system
with IpV6 in it? That would be useful for market acceptance...???

regs
Dan




From owner-ietf@ietf.org  Tue Jan 20 06:45:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25241
	for <ietf-web-archive@odin.ietf.org>; Tue, 20 Jan 2004 06:45:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiuAV-0002GS-Uw
	for ietf-list@asgard.ietf.org; Tue, 20 Jan 2004 06:35:39 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiuA9-0002ER-6j
	for ietf@asgard.ietf.org; Tue, 20 Jan 2004 06:35:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25056
	for <ietf@ietf.org>; Tue, 20 Jan 2004 06:35:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiuA1-0001Ci-00
	for ietf@ietf.org; Tue, 20 Jan 2004 06:35:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aiu8S-0001AQ-00
	for ietf@ietf.org; Tue, 20 Jan 2004 06:33:33 -0500
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1Aiu76-000175-00
	for ietf@ietf.org; Tue, 20 Jan 2004 06:32:08 -0500
Received: (qmail 73523 invoked from network); 20 Jan 2004 11:40:47 -0000
Received: from h219-110-033-058.catv01.itscom.jp (HELO necom830.hpcl.titech.ac.jp) (219.110.33.58)
  by necom830.hpcl.titech.ac.jp with SMTP; 20 Jan 2004 11:40:47 -0000
Message-ID: <400D11DE.8080205@necom830.hpcl.titech.ac.jp>
Date: Tue, 20 Jan 2004 20:32:46 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Michel Py <michel@arneill-py.sacramento.ca.us>
CC: Dan Kolis <dank@hq.lindsayelec.com>, ietf@ietf.org
Subject: Re: Effectiveness of STUN protocol
References: <DD7FE473A8C3C245ADA2A2FE1709D90B0DAE0D@server2003.arneill-py.sacramento.ca.us>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B0DAE0D@server2003.arneill-py.sacramento.ca.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Michel;

>>>Dan Kolis wrote:
>>>Yes indeed. Probably the #1 biggest use for STUN short
>>>term is going to be SIP. It seems like not too much
>>>information has to go thru the known reachable machine.
>>>Maybe just about the same loading as a DNS server?

>>Wrong.

> No. _you_ are wrong, Dan is right, 

and you say:

> I have to confess that I have not read STUN in much detail,

What a convincing argument.

However, you have to confess that you know nothing about P2P.

> - Michel opens a connection to the P2P server.

> - Dan opens a connection to the P2P server.

You are saying that there are a P2P server and two P2P clients.

Is it a client server app or a P2P app?

> If you don't understand/can't code what's above, don't worry: I know
> plenty of 16-years-old that can code it for me in exchange for the
> latest 60GB mp3 player.

I'm afraid you also confess that you can't code it yourself.

							Masataka Ohta





From owner-ietf@ietf.org  Tue Jan 20 09:12:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00385
	for <ietf-web-archive@odin.ietf.org>; Tue, 20 Jan 2004 09:12:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiwOt-0007TJ-Nb
	for ietf-list@asgard.ietf.org; Tue, 20 Jan 2004 08:58:39 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiwOg-0007R4-AO
	for ietf@asgard.ietf.org; Tue, 20 Jan 2004 08:58:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29442
	for <ietf@ietf.org>; Tue, 20 Jan 2004 08:58:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiwOf-0000ja-00
	for ietf@ietf.org; Tue, 20 Jan 2004 08:58:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiwNM-0000TS-00
	for ietf@ietf.org; Tue, 20 Jan 2004 08:57:07 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiwJ9-000046-00
	for ietf@ietf.org; Tue, 20 Jan 2004 08:52:43 -0500
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AiwIs-0004nR-Mh
	for ietf@ietf.org; Tue, 20 Jan 2004 08:52:26 -0500
Received: from limbo (limbo.unfix.org [3ffe:8114:2000:240:200:39ff:fe77:1f3f])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP id B7AFC8548;
	Tue, 20 Jan 2004 14:51:54 +0100 (CET)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Yuri Ismailov (KI/EAB)'" <yuri.ismailov@ericsson.com>,
        <dank@hq.lindsayelec.com>,
        "'Mark Smith'" <ietf@2c9d1f3141b658e37c53395b25a04078.nosense.org>
Cc: <ietf@ietf.org>
Subject: RE: P2P - Crime / NAT
Date: Tue, 20 Jan 2004 14:50:40 +0100
Organization: Unfix
Message-ID: <005601c3df5c$6548c900$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <4E85E49D1F0CBF4F96EA08E335750D7D03F52C7C@Esealnt877.al.sw.ericsson.se>
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,LINES_OF_YELLING 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

[This might be getting ietf-offtopic...]

Yuri Ismailov (KI/EAB) wrote:

> Ipv6 works in WinXP. Latest developer SDK support socket 
> programing over v6.
> No NetBIOS.
> Disabling of pseudo interfaces can be done by stopping 6to4 service.

But when you disable the 6to4 service you disable a lot of
other services as it was wrongly named. It is actually the
6to4 *helper* service taking care of a number of things
amongst others the portproxy helper.

If one wants to disable 6to4 and teredo, then use:
netsh int ipv6 6to4 set state disabled disabled
netsh int ipv6 set teredo disable

> This may be useful if there is a global IPv6 configured. 
> Otherwise OS returns the whole bunch of IPv6 addresses and in 
> some cases, when needed, the code should take care of which 
> one to choose. This is the case with latest java_1.5.0 to my 
> knowledge.

Set correct routes, use metrics etc. This should not be a
problem and your program should take care of that.
There is work for a new IPv6 Java API which will support
all the special nifty IPv6 features too.

> Programming aplications, which are both v6 and v4 aware is 
> quite a pain but may be achieved as well.

Use getaddrinfo() and relieve yourself of 'the pain'
See the following great document by Eva Castro:
http://jungla.dit.upm.es/~ecastro/IPv6-web/ipv6.html
Or Itojun's article from way back in 1998:
http://www.kame.net/newsletter/19980604/

> Win2000 can use IPv6 as well. I got working MS Research 
> prerelease under Win2000 and it is not different from what 
> you get in XP.

It is *very* different from the version in XP, it doesn't
do a lot of things which did get fixed in the XP version.

> However, requires separate download and some 
> SP number. If remember correctly should be at least 2.

See the FAQ on the MS site or simply download the prepped
version from eg http://hs247.com which has the fixed hotfix.ini
with updated version numbering.

"dank@hq.lindsayelec.com" wrote:

> Two things.
> First, here in Canada there is a new tax on "media" like writable CD's;
> (extendable to Memory cards, or anything that likely holds licenced media).

They have that 'tax' also in the Netherlands, but still, even though
you are 'paying' money for 'copyrighted' material to some vague organisation
one is not allowed to copy copyrighted material onto it.

I still also wonder why one can buy a pallet of burnable cd's at the
supermarket or every computer corner around the shop and nobody really
cares about that ;) Or even cooler: Copy your cd's from Polygram
(read: Philips) onto cd recordable's which are manufactured by Philips
using your double-decked Philips CD-Copy-Home-Station ;)
They really are doing it themselves.

> Does anyone know when/if Microsoft is bring out a consumer 
> operating system
> with IpV6 in it? That would be useful for market acceptance...???

XP SP1 and 2003 support it from the default install and are supported.
NT4/2000 have stacks available from MS Research which work but have
quirks and are not supported...

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / http://unfix.org/~jeroen

iQA/AwUBQA0yMCmqKFIzPnwjEQJYBACeOMFVgECBvzNgyD4I68nCxB15TxkAn1xm
a/ho0w8Pyu/dhjDA2k5r1pk0
=cagr
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Tue Jan 20 10:45:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06874
	for <ietf-web-archive@odin.ietf.org>; Tue, 20 Jan 2004 10:45:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aixul-0007Gh-G0
	for ietf-list@asgard.ietf.org; Tue, 20 Jan 2004 10:35:39 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aixud-0007CE-Mo
	for ietf@asgard.ietf.org; Tue, 20 Jan 2004 10:35:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05428
	for <ietf@ietf.org>; Tue, 20 Jan 2004 10:35:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aixub-0006oI-00
	for ietf@ietf.org; Tue, 20 Jan 2004 10:35:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aixtv-0006lA-00
	for ietf@ietf.org; Tue, 20 Jan 2004 10:34:47 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aixt7-0006bG-00
	for ietf@ietf.org; Tue, 20 Jan 2004 10:33:57 -0500
Content-class: urn:content-classes:message
Subject: RE: Effectiveness of STUN protocol
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 20 Jan 2004 07:33:37 -0800
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DAE14@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Effectiveness of STUN protocol
thread-index: AcPfSQeAdVFGB6CuT9y1hVHBVQsFsAAHOqkw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>
Cc: "Dan Kolis" <dank@hq.lindsayelec.com>, <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Masataka Ohta wrote:
> Is it a client server app or a P2P app?

What a total ignorance of the P2P world.
It appears that some education is needed for our candid friend here.

First, a little history. "THE" P2P app, the original Napster, was
shutdown because of its reliance on centralized servers.
=20
Besides, many other P2P apps use servers as well:

- Threedegrees uses MSN messenger's servers.

- Napster offspring such as opennap and edonkey have decentralized the
servers; however the motive behind this was to make them moving targets
operated by different entities in different countries, making the whole
server mesh virtually impossible to be shut down by legal action. At
this very moment the top 6 servers in the edonkey network have between
100,000 and 220,000 simultaneous connections each and account for more
than half of the 1.5M total users on the system.

- On-line games have centralized lobbies where players meet before they
play; there are Quake servers.

- SIP outfits all have centralized registering servers; the first things
to configure on a SIP phone are its own SIP number and the address of
the SIP server.

So yes, P2P usually means server, too.

Michel.




From owner-ietf@ietf.org  Tue Jan 20 11:00:51 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07653
	for <ietf-web-archive@odin.ietf.org>; Tue, 20 Jan 2004 11:00:51 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiyE8-0002yn-Gg
	for ietf-list@asgard.ietf.org; Tue, 20 Jan 2004 10:55:40 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiyDz-0002uR-7q
	for ietf@asgard.ietf.org; Tue, 20 Jan 2004 10:55:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07324
	for <ietf@ietf.org>; Tue, 20 Jan 2004 10:55:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiyDy-0000ca-00
	for ietf@ietf.org; Tue, 20 Jan 2004 10:55:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiyCt-0000X2-00
	for ietf@ietf.org; Tue, 20 Jan 2004 10:54:23 -0500
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiyC8-0000V7-00
	for ietf@ietf.org; Tue, 20 Jan 2004 10:53:37 -0500
Received: from limbo (limbo.unfix.org [3ffe:8114:2000:240:200:39ff:fe77:1f3f])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP id AA5E28548;
	Tue, 20 Jan 2004 16:53:31 +0100 (CET)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Michel Py'" <michel@arneill-py.sacramento.ca.us>,
        "'Masataka Ohta'" <mohta@necom830.hpcl.titech.ac.jp>
Cc: "'Dan Kolis'" <dank@hq.lindsayelec.com>, <ietf@ietf.org>
Subject: RE: Effectiveness of STUN protocol
Date: Tue, 20 Jan 2004 16:52:49 +0100
Organization: Unfix
Message-ID: <009f01c3df6d$74dc9bb0$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B0DAE14@server2003.arneill-py.sacramento.ca.us>
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,LINES_OF_YELLING 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

Michel Py wrote:

> > Masataka Ohta wrote:
> > Is it a client server app or a P2P app?
> 
> What a total ignorance of the P2P world.
> It appears that some education is needed for our candid friend here.
> 
> First, a little history. "THE" P2P app, the original Napster, was
> shutdown because of its reliance on centralized servers.

<SNIP>

> So yes, P2P usually means server, too.

And otherwise apps would still fall back to using 
DNS or anycast-IP as the locator service.
DCC on IRC uses the IRC server to communicate the ports used
for the transfer of data between the peers, the data is never
seen though.

Thus P2P has 2 aspects in this part:
 - location service
   (where is that user and where is that IP/port
    the app has to push it's traffic too/from)
 - the actual peers using the location service
   to find out where everything is.

The second part is really Peer-2-Peer, but before
that there has to be a communication with the (decentralized)
location service to actually find out where someone is.

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / http://unfix.org/~jeroen

iQA/AwUBQA1O0CmqKFIzPnwjEQLOUQCfXdiLYQtr079BK15ciTToaqzFDBwAn12M
8CJe/mS+rsOonTqsUm3uCOgx
=1POr
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Tue Jan 20 11:05:15 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08083
	for <ietf-web-archive@odin.ietf.org>; Tue, 20 Jan 2004 11:05:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiyIx-0003Vd-P4
	for ietf-list@asgard.ietf.org; Tue, 20 Jan 2004 11:00:39 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiyIn-0003Sr-FD
	for ietf@asgard.ietf.org; Tue, 20 Jan 2004 11:00:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07638
	for <ietf@ietf.org>; Tue, 20 Jan 2004 11:00:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiyIm-00012K-00
	for ietf@ietf.org; Tue, 20 Jan 2004 11:00:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiyHs-0000zi-00
	for ietf@ietf.org; Tue, 20 Jan 2004 10:59:33 -0500
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1AiyH5-0000wi-00
	for ietf@ietf.org; Tue, 20 Jan 2004 10:58:44 -0500
Received: (qmail 74648 invoked from network); 20 Jan 2004 16:07:48 -0000
Received: from h219-110-033-058.catv01.itscom.jp (HELO necom830.hpcl.titech.ac.jp) (219.110.33.58)
  by necom830.hpcl.titech.ac.jp with SMTP; 20 Jan 2004 16:07:48 -0000
Message-ID: <400D5070.5040103@necom830.hpcl.titech.ac.jp>
Date: Wed, 21 Jan 2004 00:59:44 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Michel Py <michel@arneill-py.sacramento.ca.us>
CC: Dan Kolis <dank@hq.lindsayelec.com>, ietf@ietf.org
Subject: Re: Effectiveness of STUN protocol
References: <DD7FE473A8C3C245ADA2A2FE1709D90B0DAE14@server2003.arneill-py.sacramento.ca.us>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B0DAE14@server2003.arneill-py.sacramento.ca.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Michel;
 
> What a total ignorance of the P2P world.
> It appears that some education is needed for our candid friend here.
> 
> First, a little history. "THE" P2P app, the original Napster, was

If you are not joking, you have to distinguish file
exchanges and P2P and to distinguish marketing hype and
technical reality.

It should be noted that

> At
> this very moment the top 6 servers in the edonkey network have between
> 100,000 and 220,000 simultaneous connections each

you support my point that (UDP or TCP) connection to STUN (or
whatever) server must be kept alive, which means more load
than DNS.

							Masataka Ohta





From owner-ietf@ietf.org  Tue Jan 20 11:14:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08786
	for <ietf-web-archive@odin.ietf.org>; Tue, 20 Jan 2004 11:14:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiyNw-0004Ec-IS
	for ietf-list@asgard.ietf.org; Tue, 20 Jan 2004 11:05:48 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiyKe-0003nf-Ru
	for ietf@asgard.ietf.org; Tue, 20 Jan 2004 11:02:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07737
	for <ietf@ietf.org>; Tue, 20 Jan 2004 11:02:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiyKd-00019O-00
	for ietf@ietf.org; Tue, 20 Jan 2004 11:02:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiyJh-00015K-00
	for ietf@ietf.org; Tue, 20 Jan 2004 11:01:25 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiyIu-000134-00
	for ietf@ietf.org; Tue, 20 Jan 2004 11:00:36 -0500
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com; Tue, 20 Jan 2004 11:00:33 -0500
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: mohta@necom830.hpcl.titech.ac.jp
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: RE: Effectiveness of STUN protocol
Cc: ietf@ietf.org
Date: Tue, 20 Jan 2004 11:00:33 -0500
Message-ID: <20040120160033980.AAA180@hq.lindsayelec.com@rflooker1>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>> Masataka Ohta wrote about STUN
>> Is it a client server app or a P2P app?


Hi.

Well, I read the RFC in some detail, and it is an application which should
be on the public internet side on a stable server. Its "clients" could be
all kinds of processes/apps, from P2P programs mostly, but its a general
resource to decode what a NAT is doing.
          
The RFC reminds the reader there could be lots of transactions sometimes, so
it should be scaled for the purpose.

Regs,
Dan




From owner-ietf@ietf.org  Tue Jan 20 11:21:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09356
	for <ietf-web-archive@odin.ietf.org>; Tue, 20 Jan 2004 11:21:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AiyWl-00057Z-1U
	for ietf-list@asgard.ietf.org; Tue, 20 Jan 2004 11:14:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AiyUQ-0004rB-6W
	for ietf@asgard.ietf.org; Tue, 20 Jan 2004 11:12:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08624
	for <ietf@ietf.org>; Tue, 20 Jan 2004 11:12:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiyUP-0001yZ-00
	for ietf@ietf.org; Tue, 20 Jan 2004 11:12:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiyTW-0001wL-00
	for ietf@ietf.org; Tue, 20 Jan 2004 11:11:35 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiySk-0001tA-00
	for ietf@ietf.org; Tue, 20 Jan 2004 11:10:46 -0500
Received: from dank ([191.1.2.3]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com; Tue, 20 Jan 2004 11:10:42 -0500
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: "Jeroen Massar" <jeroen@unfix.org>
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: STUN protocol implementations
Cc: ietf@ietf.org
Date: Tue, 20 Jan 2004 11:10:42 -0500
Message-ID: <20040120161042608.AAA392@hq.lindsayelec.com@dank>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

About STUN:

Reading it, it would seem like the app could ask about itself and then
forward the "real" IP(s) and ports, avoiding having the STUN server get a
lot of hits. But this is a REAL workaround no matter what. That doesn't make
it a bad thing. The documents really clear that it is a way to deal with
undocumented NAT processes.

It would seem like this might help... but really its probably not useful.
The programmer(s), I think, should be attentive to the idea some
configuration thingus could change the the session using whatever protocol
suddenly can't continue. If so, maybe reinitializing the transactions after
consulting STUN can be done without having the session itself fail.

I guess if the process/program is doing a one to many by any methods...
(multicast, lots of streams, etc), it could keep asking the STUN server
about itself, they try to advise the other end so the STUN server doesn't
get flooded. But its probably a race condition without formal timeouts anyway.

messy.

regs
Dan




From owner-ietf@ietf.org  Tue Jan 20 19:50:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04064
	for <ietf-web-archive@odin.ietf.org>; Tue, 20 Jan 2004 19:50:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aj6HS-0000dG-Ik
	for ietf-list@asgard.ietf.org; Tue, 20 Jan 2004 19:31:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aj6Ga-0000ZB-Op
	for ietf@asgard.ietf.org; Tue, 20 Jan 2004 19:30:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03502
	for <ietf@ietf.org>; Tue, 20 Jan 2004 19:30:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aj6GZ-0001YX-00
	for ietf@ietf.org; Tue, 20 Jan 2004 19:30:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aj6Fu-0001WD-00
	for ietf@ietf.org; Tue, 20 Jan 2004 19:30:03 -0500
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aj6FJ-0001Lf-00
	for ietf@ietf.org; Tue, 20 Jan 2004 19:29:25 -0500
Received: from consulintel02 ([217.126.187.160])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v6.8.5.R)
	with ESMTP id 63-md50000000037.tmp
	for <ietf@ietf.org>; Wed, 21 Jan 2004 01:32:09 +0100
Message-ID: <040201c3dfb6$00f8e7a0$650a0a0a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Subject: IETF registration and privacy ...
Date: Wed, 21 Jan 2004 01:32:07 +0100
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Wed, 21 Jan 2004 01:32:09 +0100
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hi,

Despite that it has been commented in this list some time ago, I still =
see that the list of attendees is open, and there is no option, when =
registering to indicate if you want to be there or not ?

I don't really mind myself, but we should have this option, at least =
this is my understanding from data protection laws all around the world.

Specially when we consider the lack of "legal" constituency and the =
possible responsibilities.

May be the secretariat is already working on this ?

Regards,
Jordi

**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.





From owner-ietf@ietf.org  Tue Jan 20 20:36:24 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04062
	for <ietf-web-archive@odin.ietf.org>; Tue, 20 Jan 2004 19:50:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aj6V0-0001ZB-D4
	for ietf-list@asgard.ietf.org; Tue, 20 Jan 2004 19:45:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aj6U3-0001VA-2h
	for ietf@asgard.ietf.org; Tue, 20 Jan 2004 19:44:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03919
	for <ietf@ietf.org>; Tue, 20 Jan 2004 19:44:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aj6U1-0002Av-00
	for ietf@ietf.org; Tue, 20 Jan 2004 19:44:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aj6T5-00028y-00
	for ietf@ietf.org; Tue, 20 Jan 2004 19:43:40 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aj6SR-00024h-00
	for ietf@ietf.org; Tue, 20 Jan 2004 19:42:59 -0500
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0L0gSGN027701;
	Tue, 20 Jan 2004 16:42:28 -0800 (PST)
Received: from localhost (ole@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id QAA29720; Tue, 20 Jan 2004 16:42:27 -0800 (PST)
Date: Tue, 20 Jan 2004 16:42:27 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
Reply-To: Ole Jacobsen <ole@cisco.com>
To: The IETF <ietf@ietf.org>
Subject: The Korean power plug
Message-ID: <Pine.HPX.4.58.0401201626490.11620@wells.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


At first glance, the power plug used in Korea looks just like the one
used in most of Western Europe, known as the "Euro-plug". But the Korean
plug is actually subtly different. The pins are 4.8 mm in diameter vs
4.0 mm for the Euro plug.

Does it matter, and should you care if you are going to the Seoul IETF?

Probably not, a Euro plug will fit, but if you want a more mechanically
stable solution, plan to use either:

- A *grounded* European plug (these have 4.8 mm pins also)

or

- A native Korean plug

[The Apple World-Wide adapter kit contains both a Euro and a Korean plug]

For the gory details, look at:

http://www.sony.jp/ServiceArea/Voltage_map/bigmap/ao.html

... and click on the "A" and "B" plugs.

Yes, the Sascom will work. Yes, you can buy Korean plugs in Seoul and add
them to your own power cable. And you can probably buy a Korean power
cable too if you search around.

So, who's planning a day or half-day trip to the DMZ? There are lots of
tour operators who offer trips. Google is your friend :-)

Ole


***** www.organdemo.info  OUR NEXT EVENT IS NEXT WEEK AT RIPE 47  *****

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj





From owner-ietf@ietf.org  Wed Jan 21 07:37:09 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18184
	for <ietf-web-archive@odin.ietf.org>; Wed, 21 Jan 2004 07:37:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AjHKa-0006yJ-7H
	for ietf-list@asgard.ietf.org; Wed, 21 Jan 2004 07:19:36 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AjHJr-0006vp-CF
	for ietf@asgard.ietf.org; Wed, 21 Jan 2004 07:18:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17592
	for <ietf@ietf.org>; Wed, 21 Jan 2004 07:18:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjHJg-0000AN-00
	for ietf@ietf.org; Wed, 21 Jan 2004 07:18:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjHHT-00005v-00
	for ietf@ietf.org; Wed, 21 Jan 2004 07:16:23 -0500
Received: from eu242.st117-net74.ip.superonlinecorporate.com ([213.74.117.242] helo=smtp.kvk.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjHFk-0007nZ-00
	for ietf@ietf.org; Wed, 21 Jan 2004 07:14:37 -0500
Message-ID: <cee709789a52223b82fc3572b67aee21400e7b6b@kvk.com>
From: Firat ARAS <firat@sayot.com>
To: ietf@ietf.org
Date: Wed, 21 Jan 2004 14:12:31 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_d4d28a3ca5de846ec7bce0dca30dd9d0"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.2 required=5.0 tests=AWL,HTML_90_100,HTML_MESSAGE,
	MIME_HTML_MOSTLY autolearn=no version=2.60
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.

--=_d4d28a3ca5de846ec7bce0dca30dd9d0
Content-Type: text/plain

 

--=_d4d28a3ca5de846ec7bce0dca30dd9d0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C3DFD4.7395BE00">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:windowtext;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:36.0pt'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--=_d4d28a3ca5de846ec7bce0dca30dd9d0--



From owner-ietf@ietf.org  Wed Jan 21 10:21:48 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25350
	for <ietf-web-archive@odin.ietf.org>; Wed, 21 Jan 2004 10:21:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AjK03-000695-N5
	for ietf-list@asgard.ietf.org; Wed, 21 Jan 2004 10:10:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AjJzc-00066W-B6
	for ietf@asgard.ietf.org; Wed, 21 Jan 2004 10:10:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24592
	for <ietf@ietf.org>; Wed, 21 Jan 2004 10:10:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjJzb-0002gM-00
	for ietf@ietf.org; Wed, 21 Jan 2004 10:10:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjJyf-0002fH-00
	for ietf@ietf.org; Wed, 21 Jan 2004 10:09:10 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjJxw-0002dq-00
	for ietf@ietf.org; Wed, 21 Jan 2004 10:08:24 -0500
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com; Wed, 21 Jan 2004 10:08:22 -0500
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Priority: 2 (High)
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: My first hand routed SIP call - Good example for new users
Cc: hgs@cs.columbia.edu
Date: Wed, 21 Jan 2004 10:08:22 -0500
Message-ID: <20040121150822720.AAA144@hq.lindsayelec.com@rflooker1>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


Hello... Regarding making SIP hop for you in your first session!

As any programmer knows, getting the first "Hello world" back from a new
computer language is the hardest hurdle. After that, you look back after a
few thousand pages of code and say... "easy". Doing this all a little at a
time will teach you it in a deep sense. If you just want to make a call and
not know how it works: Bum a quarter and find a payphone instead!

Anyway, here is a canned example of a TCP hand coded SIP session that works
as of this morning. SIP tends to just hangup without an response code unless
the session is reasonably well formed. The below works.

Thanks Henning S. for inventing SIP! and making the client exist on
columbia.edu as below.


This is via TCP using a telnet client under linux. I telneted to the linux
box from home using a telnet client under Windows. Anyway, it couldn't make
the UDP open, but that is "hello world plus" so once you have the response
code to parse... the low level is working, obviously.


The below is a "telephone call" to Columbia university via internet
hand routed without software. This is a good way to learn it in depth.
The best actually. The top block is what I hand entered, and the bottom
is the (HA!) "phone switch". Stimus and response, hand entered. Somewhere 
I read some Telnet clients inserts extra [CR LF[ sequences which goofs up
the [CR LF] detection. SO enter it carefully by hand once and you will be far
ahead. If you get a "200 Bad thing" etc you know your firewalls and what
have you is not in the way.

Regards,
Dan K


  TELNET
  telnet> open sip.columbia.edu 5060
  Trying 128.59.39.127...
  Connected to ren.cc.columbia.edu.
  Escape character is '^]'.
  INVITE sip:a@qwerty.com SIP/2.0
  Via: SIP/2.0/UDP 169.130.4.4
  FROM: <sip:test@qwerty.com>
  TO: <sip:test2@qwerty.com>
  call-id: 123456@Dbk@test.com
  content-length: 0


  SIP/2.0 400 Transaction tupel incomplete (9/SL)
  Via: SIP/2.0/UDP 169.130.4.4;received=204.101.26.60
  FROM: <sip:test@qwerty.com>
  TO: <sip:test2@qwerty.com>;tag=b27e1a1d33761e85846fc98f5f3a7e58.16fb
  call-id: 123456@Dbk@test.com
  Server: Sip EXpress router (0.8.12 (i386/linux))
  Content-Length: 0
  Warning: 392 128.59.39.127:5060 "Noisy feedback tells:  pid=13647
  req_src_ip=204.101.26.60 req_src_port=4829 in_uri=sip:a@qwerty.com 
  out_uri=sip:a@qwerty.com vi
  a_cnt==1"

Example: 4769498 "First SIP call"

Regards,
Dan Kolis




From owner-ietf@ietf.org  Wed Jan 21 11:30:15 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28505
	for <ietf-web-archive@odin.ietf.org>; Wed, 21 Jan 2004 11:30:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AjL5o-0001b4-1j
	for ietf-list@asgard.ietf.org; Wed, 21 Jan 2004 11:20:36 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AjL5R-0001Yd-A7
	for ietf@asgard.ietf.org; Wed, 21 Jan 2004 11:20:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27829
	for <ietf@ietf.org>; Wed, 21 Jan 2004 11:20:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjL5Q-0005Xu-00
	for ietf@ietf.org; Wed, 21 Jan 2004 11:20:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjL4T-0005Vj-00
	for ietf@ietf.org; Wed, 21 Jan 2004 11:19:14 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjL3i-0005RY-00
	for ietf@ietf.org; Wed, 21 Jan 2004 11:18:26 -0500
Received: from ibm-eyjgx9r6nqt.shockey.us (APh-Aug-104-2-1-192.w217-128.abo.wanadoo.fr [217.128.104.192])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i0LGPlE00989
	for <ietf@ietf.org>; Wed, 21 Jan 2004 08:25:48 -0800
Message-Id: <6.0.1.1.2.20040121111654.026abec0@popd.ix.netcom.com>
X-Sender: richard@joy.songbird.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 21 Jan 2004 11:17:49 -0500
To: ietf@ietf.org
From: Richard Shockey <richard@shockey.us>
Subject: US Government NTIA requests comments on IPv6
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,BIZ_TLD,LINES_OF_YELLING 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk



For Immediate Release
January 15, 2004        Contact: Clyde Ensslin or
Ranjit de Silva, 202-482-7002
http://www.ntia.doc.gov/ntiahome/press/2004/IPv6_01152004.htm

COMMERCE DEPARTMENT TASK FORCE REQUESTS COMMENTS ON
BENEFITS AND COSTS OF TRANSITION TO NEW INTERNET
PROTOCOL

  Appropriate Role of Government in IPv6 Deployment To
Be Addressed

The Commerce Department's task force studying issues
related to Internet Protocol version 6 (IPv6) today
invited interested parties to file comments on the
costs and benefits of a transition from I.P. version 4
to I.P. version 6 in a detailed notice signed by Dr.
Arden L. Bement, Jr., Director of the National
Institute of Standards and Technology, and Michael D.
Gallagher, Acting Assistant Secretary of Commerce for
Communications and Information. Comments are due 45
days after publication in the Federal Register.

"Before we make any policy decisions, we must fully
understand the degree to which the new standard will
enable direct connectivity among wireless devices,
boost the productivity of the American worker and
enrich the experience of the American consumer," said
Acting Assistant Secretary Gallagher. "We also must
fully explore the costs and technical impacts of
large-scale deployment."

"The interoperability among technologies is a critical
element both for national competitiveness and for
national security," NIST Director Bement said. "Our
task force can play a valuable role in developing an
understanding of the merits of, and obstacles to,
moving to IPv6. One of the objectives of our task
force is to measure the current status of deployment
and assess alternative future deployment scenarios,
which is vitally important for policy makers."

Commenters are invited to provide information on a
variety of topics, including IPv6 characteristics that
will either enhance or possibly degrade network
security, and affect network access and
"traceability." Comments are also sought on the
expected costs of upgrading and replacing hardware and
software, and of maintaining security during
transition to the new standard.

The task force, called for by President Bush's
National Strategy to Secure Cyberspace, is co-chaired
by the Commerce Department's National
Telecommunications and Information Administration
(NTIA) and the National Institute of Standards and
Technology (NIST) and will operate in consultation
with the Department of Homeland Security and other
federal offices and agencies. The task force will
issue a report of its findings and recommendations to
the President later this year. The next-generation
Internet Protocol provides a vastly expanded number of
addresses for Internet-connected devices, and may
enable new market applications, facilitate improved
security and reduce operational expenses for Internet
users.

The text of the notice is available at NTIA's Web site
at www.ntia.doc.gov.




 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
<http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<




From owner-ietf@ietf.org  Wed Jan 21 11:44:51 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29221
	for <ietf-web-archive@odin.ietf.org>; Wed, 21 Jan 2004 11:44:51 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AjLOB-0002nE-ND
	for ietf-list@asgard.ietf.org; Wed, 21 Jan 2004 11:39:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AjLNt-0002kV-OF
	for ietf@asgard.ietf.org; Wed, 21 Jan 2004 11:39:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29015
	for <ietf@ietf.org>; Wed, 21 Jan 2004 11:39:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjLNs-0006Z1-00
	for ietf@ietf.org; Wed, 21 Jan 2004 11:39:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjLN0-0006Wq-00
	for ietf@ietf.org; Wed, 21 Jan 2004 11:38:22 -0500
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjLMX-0006Su-00
	for ietf@ietf.org; Wed, 21 Jan 2004 11:37:53 -0500
Received: from consulintel02 ([217.126.187.160])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v6.8.5.R)
	with ESMTP id 18-md50000000061.tmp
	for <ietf@ietf.org>; Wed, 21 Jan 2004 17:40:29 +0100
Message-ID: <06b401c3e03c$c94a86b0$650a0a0a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <6.0.1.1.2.20040121111654.026abec0@popd.ix.netcom.com>
Subject: Re: US Government NTIA requests comments on IPv6
Date: Wed, 21 Jan 2004 17:36:54 +0100
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Wed, 21 Jan 2004 17:40:29 +0100
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,BIZ_TLD autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hi,

There is one more recent info about this at:
http://www.ist-ipv6.org/modules.php?op=3Dmodload&name=3DNews&file=3Dartic=
le&sid=3D324

If you want news about IPv6, almost daily updated, you should take a =
look at:
http://www.ist-ipv6.org

Regards,
Jordi

----- Original Message -----=20
From: "Richard Shockey" <richard@shockey.us>
To: <ietf@ietf.org>
Sent: Wednesday, January 21, 2004 5:17 PM
Subject: US Government NTIA requests comments on IPv6


>=20
>=20
> For Immediate Release
> January 15, 2004        Contact: Clyde Ensslin or
> Ranjit de Silva, 202-482-7002
> http://www.ntia.doc.gov/ntiahome/press/2004/IPv6_01152004.htm
>=20
> COMMERCE DEPARTMENT TASK FORCE REQUESTS COMMENTS ON
> BENEFITS AND COSTS OF TRANSITION TO NEW INTERNET
> PROTOCOL
>=20
>   Appropriate Role of Government in IPv6 Deployment To
> Be Addressed
>=20
> The Commerce Department's task force studying issues
> related to Internet Protocol version 6 (IPv6) today
> invited interested parties to file comments on the
> costs and benefits of a transition from I.P. version 4
> to I.P. version 6 in a detailed notice signed by Dr.
> Arden L. Bement, Jr., Director of the National
> Institute of Standards and Technology, and Michael D.
> Gallagher, Acting Assistant Secretary of Commerce for
> Communications and Information. Comments are due 45
> days after publication in the Federal Register.
>=20
> "Before we make any policy decisions, we must fully
> understand the degree to which the new standard will
> enable direct connectivity among wireless devices,
> boost the productivity of the American worker and
> enrich the experience of the American consumer," said
> Acting Assistant Secretary Gallagher. "We also must
> fully explore the costs and technical impacts of
> large-scale deployment."
>=20
> "The interoperability among technologies is a critical
> element both for national competitiveness and for
> national security," NIST Director Bement said. "Our
> task force can play a valuable role in developing an
> understanding of the merits of, and obstacles to,
> moving to IPv6. One of the objectives of our task
> force is to measure the current status of deployment
> and assess alternative future deployment scenarios,
> which is vitally important for policy makers."
>=20
> Commenters are invited to provide information on a
> variety of topics, including IPv6 characteristics that
> will either enhance or possibly degrade network
> security, and affect network access and
> "traceability." Comments are also sought on the
> expected costs of upgrading and replacing hardware and
> software, and of maintaining security during
> transition to the new standard.
>=20
> The task force, called for by President Bush's
> National Strategy to Secure Cyberspace, is co-chaired
> by the Commerce Department's National
> Telecommunications and Information Administration
> (NTIA) and the National Institute of Standards and
> Technology (NIST) and will operate in consultation
> with the Department of Homeland Security and other
> federal offices and agencies. The task force will
> issue a report of its findings and recommendations to
> the President later this year. The next-generation
> Internet Protocol provides a vastly expanded number of
> addresses for Internet-connected devices, and may
> enable new market applications, facilitate improved
> security and reduce operational expenses for Internet
> users.
>=20
> The text of the notice is available at NTIA's Web site
> at www.ntia.doc.gov.
>=20
>=20
>=20
>=20
>  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Richard Shockey, Senior Manager, Strategic Technology Initiatives
> NeuStar Inc.
> 46000 Center Oak Plaza  -   Sterling, VA  20166
> sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  Fax: +1 =
815.333.1237
> <mailto:richard(at)shockey.us> or =
<mailto:richard.shockey(at)neustar.biz>
> <http://www.neustar.biz> ; <http://www.enum.org>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> 

**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.





From owner-ietf@ietf.org  Thu Jan 22 17:10:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15283
	for <ietf-web-archive@odin.ietf.org>; Thu, 22 Jan 2004 17:10:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ajmga-0006DD-3l
	for ietf-list@asgard.ietf.org; Thu, 22 Jan 2004 16:48:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ajmfc-0006Cx-VE
	for ietf@asgard.ietf.org; Thu, 22 Jan 2004 16:47:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13785
	for <ietf@ietf.org>; Thu, 22 Jan 2004 16:47:22 -0500 (EST)
From: Tomson_Eric@Yahoo.fr
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajmfb-0005m3-00
	for ietf@ietf.org; Thu, 22 Jan 2004 16:47:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ajmch-000559-00
	for ietf@ietf.org; Thu, 22 Jan 2004 16:44:24 -0500
Received: from dyn-195-242-73-4.ppp.tiscali.fr ([195.242.73.4] helo=nathalie)
	by ietf-mx with smtp (Exim 4.12)
	id 1AjmXe-00042G-00
	for ietf@ietf.org; Thu, 22 Jan 2004 16:39:11 -0500
Date: Thu, 22 Jan 2004 22:59:34 +0100
To: ietf@ietf.org
Subject: Hi
Message-ID: <nwlsjmuynofyonniivh@Yahoo.fr>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------330131188876784"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=MICROSOFT_EXECUTABLE,
	NO_REAL_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

----------330131188876784
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

 Test =)
wlmulvqufnjmbykv
--
Test, yep.

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

[Filename: flhiudm.exe, Content-Type: application/x-msdownload]
The attachment file in the message has been removed by eManager.

----------330131188876784--




From owner-ietf@ietf.org  Sat Jan 24 16:52:28 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25313
	for <ietf-web-archive@odin.ietf.org>; Sat, 24 Jan 2004 16:52:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AkVSh-0007VR-Fq
	for ietf-list@asgard.ietf.org; Sat, 24 Jan 2004 16:37:03 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AkVSM-0007UP-8d
	for ietf@asgard.ietf.org; Sat, 24 Jan 2004 16:36:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24956
	for <ietf@ietf.org>; Sat, 24 Jan 2004 16:36:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkVSK-0005DZ-00
	for ietf@ietf.org; Sat, 24 Jan 2004 16:36:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AkVRM-0005BF-00
	for ietf@ietf.org; Sat, 24 Jan 2004 16:35:41 -0500
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkVR8-00059o-00; Sat, 24 Jan 2004 16:35:26 -0500
Received: from [63.202.92.156] (adsl-63-202-92-156.dsl.snfc21.pacbell.net [63.202.92.156])
	(authenticated bits=0)
	by above.proper.com (8.12.10/8.12.8) with ESMTP id i0OLZMic066706;
	Sat, 24 Jan 2004 13:35:22 -0800 (PST)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0602041fbc388eadfa5f@[63.202.92.156]>
Date: Sat, 24 Jan 2004 13:35:24 -0800
To: (various IETF lists)
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: New mail-ng mailing list open for sign-ups
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-4.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Greetings again. There seems to be more discussion these days about 
replacing SMTP and/or RFC 2822 and/or POP/IMAP for a variety of 
reasons. The discussion seems to pop up on a few different lists and 
in a few different hallways, and it might be good to have a single 
list where folks can congregate. Thus, I have set up a mail-ng 
mailing list.

The first task probably is to determine what the next generation of 
mail should do, and how that is different than what 
SMTP/2822/POP-or-IMAP or instant messaging does. It is safe to say 
that we can ignore actual protocol proposals for many months (if not 
years) until we figure out what is needed. Once we do that, there are 
plenty of protocol people who can attack the decided-on requirements.

There is no expectation that there will be significant agreement on 
the list. It is likely that over time the discussion will split into 
camps of like-minded design goals. The list might then spawn 
different lists for the folks of the different camps (mail-ng-shoe, 
mail-ng-sandal, ...). The list is explicitly not yet meant to be an 
IETF working group yet (if at all), and is probably more akin to the 
IRTF. But at the beginning, it will most likely be talking, not 
research.

See <http://www.imc.org/mail-ng/> for information on how to 
subscribe. The list is taking subscriptions now, and will probably go 
live for discussions within a week. Having some discussion on a 
mailing list now should make the dinners and bar gatherings at Seoul 
more interesting.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Sun Jan 25 09:04:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04063
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 Jan 2004 09:04:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AkkZM-0008Ps-Nu
	for ietf-list@asgard.ietf.org; Sun, 25 Jan 2004 08:44:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AkkYa-0008Ol-Mg
	for ietf@asgard.ietf.org; Sun, 25 Jan 2004 08:44:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03619
	for <ietf@ietf.org>; Sun, 25 Jan 2004 08:44:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkkYa-0006Hi-00
	for ietf@ietf.org; Sun, 25 Jan 2004 08:44:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AkkXg-0006Fd-00
	for ietf@ietf.org; Sun, 25 Jan 2004 08:43:12 -0500
Received: from [194.90.70.20] (helo=ilmx1.p-cube.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkkWo-00069m-00
	for ietf@ietf.org; Sun, 25 Jan 2004 08:42:18 -0500
Received: by ilmx1.p-cube.com with Internet Mail Service (5.5.2653.19)
	id <DTTZTPCK>; Sun, 25 Jan 2004 15:42:29 +0200
Message-ID: <BB7797D6BF684A4B91ABB19AB6A579C567C3AF@ilmx1.p-cube.com>
From: Haim Rochberger <haimro@p-cube.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: packets of multiple users sent over the same TCP/IP session
Date: Sun, 25 Jan 2004 15:42:28 +0200
Importance: high
X-Priority: 1
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3E349.12F80DF0"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE,
	X_PRIORITY_HIGH autolearn=no version=2.60
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_01C3E349.12F80DF0
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

I am looking for any protocol or type of protocol/application that runs over
TCP/IP, and that packets of that same session "belong" (i.e. either destined
or sourced) to/by 
more then one subscribers (meaning that each packet belongs to one
subscriber, but there are a some packets that belong to subscriber A, some
to B, etc.).
 
I am not talking about tunneling protocol, as in their case the internal IP
is the identity of the subscriber, but I am talking about protocols that the
identity of the subscriber 
resides at the higher level, like the application layer, and the muxing
between the packets to subscribers can be done only if you understand the
protocol at that high level.
 
 
An example for such a protocol is SMPP that is used for sending SMS messages
of different subscribers on the same TCP/IP session
between the SMSC and the application server. There, the subscriber identity
is embedded in the SPMM protocol (above the TCP/IP).

I will appreciate your help as it will help in making a better design
decisions.

Yours,

Haim. 
 

------_=_NextPart_001_01C3E349.12F80DF0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 5.50.4134.600" name=GENERATOR></HEAD>
<BODY>
<DIV>Hi,<BR><BR><SPAN class=356332813-25012004><FONT face=Arial size=2>I am 
looking for any protocol or type of protocol/application that runs over TCP/IP, 
and that packets of that <STRONG>same</STRONG> session "belong" (i.e. either 
destined or sourced) to/by </FONT></SPAN></DIV>
<DIV><SPAN class=356332813-25012004><FONT face=Arial size=2>more then one 
subscribers (meaning that each packet belongs to <STRONG>one</STRONG> 
subscriber, but there are a some packets that belong to subscriber A, some to B, 
etc.).</FONT></SPAN></DIV>
<DIV><SPAN class=356332813-25012004><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=356332813-25012004><FONT face=Arial size=2>I am not talking 
about tunneling protocol, as in their case the internal IP is the identity of 
the subscriber, but I am talking about protocols that the identity of the 
subscriber </FONT></SPAN></DIV>
<DIV><SPAN class=356332813-25012004><FONT face=Arial size=2>resides at the 
higher level, like the application layer, and the muxing between the packets to 
subscribers can be done only if you understand the protocol at that high 
level.</FONT></SPAN></DIV>
<DIV><SPAN class=356332813-25012004><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=356332813-25012004><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><SPAN class=356332813-25012004>An example for such 
a protocol is SMPP that is used for sending SMS messages of different 
subscribers on the same TCP/IP session</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=356332813-25012004>between the SMSC and 
the application server. There, the subscriber identity is embedded in the SPMM 
protocol (above the TCP/IP).</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT><BR>I will appreciate your help as it will 
help in making a better design decisions.<BR><BR>Yours,<BR><BR>Haim. </DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C3E349.12F80DF0--



From owner-ietf@ietf.org  Sun Jan 25 11:52:50 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10510
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 Jan 2004 11:52:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AknNY-0003TT-36
	for ietf-list@asgard.ietf.org; Sun, 25 Jan 2004 11:44:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AknMz-0003SL-DG
	for ietf@asgard.ietf.org; Sun, 25 Jan 2004 11:44:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10353
	for <ietf@ietf.org>; Sun, 25 Jan 2004 11:44:18 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AknMy-00071b-00
	for ietf@ietf.org; Sun, 25 Jan 2004 11:44:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AknM3-0006zG-00
	for ietf@ietf.org; Sun, 25 Jan 2004 11:43:24 -0500
Received: from h80ad2489.async.vt.edu ([128.173.36.137] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AknLH-0006wZ-00
	for ietf@ietf.org; Sun, 25 Jan 2004 11:42:36 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i0PGgVLA031190;
	Sun, 25 Jan 2004 11:42:31 -0500
Message-Id: <200401251642.i0PGgVLA031190@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Haim Rochberger <haimro@p-cube.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: packets of multiple users sent over the same TCP/IP session 
In-Reply-To: Your message of "Sun, 25 Jan 2004 15:42:28 +0200."
             <BB7797D6BF684A4B91ABB19AB6A579C567C3AF@ilmx1.p-cube.com> 
References: <BB7797D6BF684A4B91ABB19AB6A579C567C3AF@ilmx1.p-cube.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1262652270P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sun, 25 Jan 2004 11:42:31 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sun, 25 Jan 2004 15:42:28 +0200, Haim Rochberger <haimro@p-cube.com>  said:

> I will appreciate your help as it will help in making a better design
> decisions.

Hmm.. been a while since I've had to post this. ;)

The first thing you want to do is take a step *back* from the problem, and ask
yourself what problem you're trying to solve via this multiplexing.  You
already said you didn't want to use tunneling, but at the same time you gave us
insufficient information to know if SMPP or anything similar is applicable to
your problem. With the information you gave, it's likely many will fear to give
you any really useful answers for fear of sending you in a totally useless
direction.

For all I know, HTTP pipelining may be a solution to your problem - in that
scenario, you have in-flight packets for multiple HTTP requests (read
"subscribers") active at the same time.  On the other hand, although it meets
the requirements you stated, it's almost certainly not the right answer.  But
not knowing what problem you're trying to solve, it's hard to say.

Basically, you need to make sure that what you have in your hand is a nail
rather than a screw *before* you start selecting hammers....


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

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

iD8DBQFAE/H3cC3lWbTT17ARAuH5AKD46Pla+W9tuK3ui22HA8Pts6AbPQCgp/k8
mXvGeMOTcBWVrzVLyHm7emg=
=LZsn
-----END PGP SIGNATURE-----

--==_Exmh_-1262652270P--



From owner-ietf@ietf.org  Sun Jan 25 12:29:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11693
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 Jan 2004 12:29:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ako0G-0004cr-3Q
	for ietf-list@asgard.ietf.org; Sun, 25 Jan 2004 12:24:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ako00-0004bg-O2
	for ietf@asgard.ietf.org; Sun, 25 Jan 2004 12:24:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11514
	for <ietf@ietf.org>; Sun, 25 Jan 2004 12:24:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aknzu-00016P-00
	for ietf@ietf.org; Sun, 25 Jan 2004 12:24:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aknw4-0000y1-00
	for ietf@ietf.org; Sun, 25 Jan 2004 12:20:36 -0500
Received: from [194.90.70.20] (helo=ilmx1.p-cube.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aknvc-0000tL-00
	for ietf@ietf.org; Sun, 25 Jan 2004 12:20:08 -0500
Received: by ilmx1.p-cube.com with Internet Mail Service (5.5.2653.19)
	id <DTTZTPK6>; Sun, 25 Jan 2004 19:20:02 +0200
Message-ID: <BB7797D6BF684A4B91ABB19AB6A579C567C3B3@ilmx1.p-cube.com>
From: Haim Rochberger <haimro@p-cube.com>
To: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>,
        Haim Rochberger
	 <haimro@p-cube.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: packets of multiple users sent over the same TCP/IP session 
Date: Sun, 25 Jan 2004 19:20:02 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Valdis,

Thanks for the reply.

SMPP is a good example to what I am looking for, and I am trying to see if
other 
protocol foreseen in the future (or past) have the same characteristics:

The special thing about SMPP is that in the same TCP/IP session packet that
are really SMS embedded in IP 
are sent from one network element (called SMSC) to another (called ESME) -
so that the packets (i.e. SMS) belong to different mobile users.

In this case I cannot map the IP address of the TCP session to one specific
mobile subscriber - and the only way I can 
identify the subscriber is by "looking" on the SMPP layer (above the TCP)
and extract the subscriber mobile number.

Another example may be SMTP (not sure).

Anyway the thing I am trying to solve is whether I should consider this kind
of protocol characteristic as "special" and "rare", and so build a dedicated
solution for SMPP, or maybe I can expect to see many more such protocol and
so I should build a more generic solution.

It is obvious to me that a generic solution is better technically, but since
my resources (i.e. time) is limited, 
I need to see how rare this kind of protocol (same TCP/IP with packets of
multiple users) is common/expected.

Another characteristic of SMPP that I am looking for its "commonness" is the
fact that there could be many 
TCP/IP session from many SCSCs to ESMEs at the same time - and packets of
the SAME subscriber may appear 
on them at the same time...

Complicated :-)   that's my life (-:





yours,

Haim Rochberger




> -----Original Message-----
> From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
> Sent: Sun, January 25, 2004 6:43 PM
> To: Haim Rochberger
> Cc: 'ietf@ietf.org'
> Subject: Re: packets of multiple users sent over the same 
> TCP/IP session
> 
> 
> 
> On Sun, 25 Jan 2004 15:42:28 +0200, Haim Rochberger 
> <haimro@p-cube.com>  said:
> 
> > I will appreciate your help as it will help in making a 
> better design
> > decisions.
> 
> Hmm.. been a while since I've had to post this. ;)
> 
> The first thing you want to do is take a step *back* from the 
> problem, and ask
> yourself what problem you're trying to solve via this 
> multiplexing.  You
> already said you didn't want to use tunneling, but at the 
> same time you gave us
> insufficient information to know if SMPP or anything similar 
> is applicable to
> your problem. With the information you gave, it's likely many 
> will fear to give
> you any really useful answers for fear of sending you in a 
> totally useless
> direction.
> 
> For all I know, HTTP pipelining may be a solution to your 
> problem - in that
> scenario, you have in-flight packets for multiple HTTP requests (read
> "subscribers") active at the same time.  On the other hand, 
> although it meets
> the requirements you stated, it's almost certainly not the 
> right answer.  But
> not knowing what problem you're trying to solve, it's hard to say.
> 
> Basically, you need to make sure that what you have in your 
> hand is a nail
> rather than a screw *before* you start selecting hammers....
> 
> 



From owner-ietf@ietf.org  Sun Jan 25 13:04:32 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12623
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 Jan 2004 13:04:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AkoWB-0005fX-U3
	for ietf-list@asgard.ietf.org; Sun, 25 Jan 2004 12:57:55 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AkoUc-0005dG-2V
	for ietf@asgard.ietf.org; Sun, 25 Jan 2004 12:56:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12404
	for <ietf@ietf.org>; Sun, 25 Jan 2004 12:56:15 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkoUa-0002TA-00
	for ietf@ietf.org; Sun, 25 Jan 2004 12:56:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AkoTg-0002Ro-00
	for ietf@ietf.org; Sun, 25 Jan 2004 12:55:21 -0500
Received: from h80ad2489.async.vt.edu ([128.173.36.137] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkoTB-0002Q7-00
	for ietf@ietf.org; Sun, 25 Jan 2004 12:54:50 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i0PHsjcJ001121;
	Sun, 25 Jan 2004 12:54:45 -0500
Message-Id: <200401251754.i0PHsjcJ001121@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Haim Rochberger <haimro@p-cube.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: packets of multiple users sent over the same TCP/IP session 
In-Reply-To: Your message of "Sun, 25 Jan 2004 19:20:02 +0200."
             <BB7797D6BF684A4B91ABB19AB6A579C567C3B3@ilmx1.p-cube.com> 
References: <BB7797D6BF684A4B91ABB19AB6A579C567C3B3@ilmx1.p-cube.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1232531466P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sun, 25 Jan 2004 12:54:45 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sun, 25 Jan 2004 19:20:02 +0200, Haim Rochberger said:

> In this case I cannot map the IP address of the TCP session to one specific
> mobile subscriber - and the only way I can 
> identify the subscriber is by "looking" on the SMPP layer (above the TCP)
> and extract the subscriber mobile number.

It's tempting to suggest using IPv6 tunelling, and sorting out whos packets
are whose by inserting the subscriber info in the low-order 64 bits.

For that matter, aren't many mobile solutions IPv6 ready (at least in Japan,
which seems to have more of a clue about this than the US)?

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

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

iD8DBQFAFALlcC3lWbTT17ARAvh9AKD6NxKj5ntyMao1GQepjlq+4WF7QQCg1iNL
pNx8Vayti7T8tR6rWL2XQY8=
=PY84
-----END PGP SIGNATURE-----

--==_Exmh_-1232531466P--



From owner-ietf@ietf.org  Sun Jan 25 13:45:38 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13600
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 Jan 2004 13:45:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AkpAy-0006ye-Pn
	for ietf-list@asgard.ietf.org; Sun, 25 Jan 2004 13:40:04 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Akp7T-0006u7-Or
	for ietf@asgard.ietf.org; Sun, 25 Jan 2004 13:36:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13366
	for <ietf@ietf.org>; Sun, 25 Jan 2004 13:36:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Akp7Q-000435-00
	for ietf@ietf.org; Sun, 25 Jan 2004 13:36:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Akp6R-0003zc-00
	for ietf@ietf.org; Sun, 25 Jan 2004 13:35:24 -0500
Received: from burp.tkv.asdf.org ([212.16.99.49] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Akp5T-0003uE-00
	for ietf@ietf.org; Sun, 25 Jan 2004 13:34:24 -0500
Received: from burp.tkv.asdf.org (msa@localhost [127.0.0.1])
	by burp.tkv.asdf.org (8.12.9/8.12.9/Debian-5) with ESMTP id i0PIXj8u032657;
	Sun, 25 Jan 2004 20:33:45 +0200
Received: (from msa@localhost)
	by burp.tkv.asdf.org (8.12.9/8.12.9/Debian-5) id i0PIXjCZ032654;
	Sun, 25 Jan 2004 20:33:45 +0200
Date: Sun, 25 Jan 2004 20:33:45 +0200
Message-Id: <200401251833.i0PIXjCZ032654@burp.tkv.asdf.org>
From: Markku Savela <msa@burp.tkv.asdf.org>
To: haimro@p-cube.com
CC: ietf@ietf.org
In-reply-to: <BB7797D6BF684A4B91ABB19AB6A579C567C3AF@ilmx1.p-cube.com>
	(message from Haim Rochberger on Sun, 25 Jan 2004 15:42:28 +0200)
Subject: Re: packets of multiple users sent over the same TCP/IP session
References: <BB7797D6BF684A4B91ABB19AB6A579C567C3AF@ilmx1.p-cube.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Haim Rochberger <haimro@p-cube.com>

> I am looking for any protocol or type of protocol/application that
> runs over TCP/IP, and that packets of that same session "belong"
> (i.e. either destined or sourced) to/by more then one subscribers
> (meaning that each packet belongs to one subscriber, but there are a
> some packets that belong to subscriber A, some to B, etc.).

Sort of like TCP connections between IRC servers, messages of
different clients over the same connection?




From owner-ietf@ietf.org  Sun Jan 25 18:11:24 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21754
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 Jan 2004 18:11:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AktCU-000393-GJ
	for ietf-list@asgard.ietf.org; Sun, 25 Jan 2004 17:57:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AktC6-00038J-Ir
	for ietf@asgard.ietf.org; Sun, 25 Jan 2004 17:57:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20839
	for <ietf@ietf.org>; Sun, 25 Jan 2004 17:57:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AktC4-0006N5-00
	for ietf@ietf.org; Sun, 25 Jan 2004 17:57:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AktBA-0006Kt-00
	for ietf@ietf.org; Sun, 25 Jan 2004 17:56:33 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AktAf-0006Ii-00
	for ietf@ietf.org; Sun, 25 Jan 2004 17:56:01 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0PMuO2g046484;
	Sun, 25 Jan 2004 23:56:25 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <200401251754.i0PHsjcJ001121@turing-police.cc.vt.edu>
References: <BB7797D6BF684A4B91ABB19AB6A579C567C3B3@ilmx1.p-cube.com> <200401251754.i0PHsjcJ001121@turing-police.cc.vt.edu>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <A490925C-4F89-11D8-9871-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: packets of multiple users sent over the same TCP/IP session 
Date: Sun, 25 Jan 2004 23:55:59 +0100
To: Valdis.Kletnieks@vt.edu
X-Mailer: Apple Mail (2.609)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 25-jan-04, at 18:54, Valdis.Kletnieks@vt.edu wrote:

>> In this case I cannot map the IP address of the TCP session to one 
>> specific
>> mobile subscriber - and the only way I can
>> identify the subscriber is by "looking" on the SMPP layer (above the 
>> TCP)
>> and extract the subscriber mobile number.

> It's tempting to suggest using IPv6 tunelling, and sorting out whos 
> packets
> are whose by inserting the subscriber info in the low-order 64 bits.

I would love to see the neighbor discovery (~= ARP for the 
v6-challenged) for such a solution. Not to mention that you can't run 
TCP that way.

But why use TCP in the first place? If this stuff is small enough to 
fit in a single IP packet, it makes much more sense to use UDP: no 
multiplexing problems. If reliability is needed it gets more complex, 
but some kind of RTP-like protocol makes more sense here than TCP.




From owner-ietf@ietf.org  Sun Jan 25 18:28:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22872
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 Jan 2004 18:28:16 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aktbe-0003r1-0P
	for ietf-list@asgard.ietf.org; Sun, 25 Jan 2004 18:23:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AktZK-0003oy-J7
	for ietf@asgard.ietf.org; Sun, 25 Jan 2004 18:21:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22691
	for <ietf@ietf.org>; Sun, 25 Jan 2004 18:21:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AktZJ-0007Uk-00
	for ietf@ietf.org; Sun, 25 Jan 2004 18:21:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AktYT-0007T1-00
	for ietf@ietf.org; Sun, 25 Jan 2004 18:20:37 -0500
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AktXz-0007QU-00
	for ietf@ietf.org; Sun, 25 Jan 2004 18:20:07 -0500
Received: from [63.202.92.156] (adsl-63-202-92-156.dsl.snfc21.pacbell.net [63.202.92.156])
	(authenticated bits=0)
	by above.proper.com (8.12.11/8.12.8) with ESMTP id i0PNJx2S022298
	for <ietf@ietf.org>; Sun, 25 Jan 2004 15:19:59 -0800 (PST)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p06020439bc39ff920402@[63.202.92.156]>
Date: Sun, 25 Jan 2004 15:20:02 -0800
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: New mail-ng mailing list open for sign-ups
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-3.4 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Greetings again. There seems to be more discussion these days about 
replacing SMTP and/or RFC 2822 and/or POP/IMAP for a variety of 
reasons. The discussion seems to pop up on a few different lists and 
in a few different hallways, and it might be good to have a single 
list where folks can congregate. Thus, I have set up a mail-ng 
mailing list.

The first task probably is to determine what the next generation of 
mail should do, and how that is different than what 
SMTP/2822/POP-or-IMAP or instant messaging does. It is safe to say 
that we can ignore actual protocol proposals for many months (if not 
years) until we figure out what is needed. Once we do that, there are 
plenty of protocol people who can attack the decided-on requirements.

There is no expectation that there will be significant agreement on 
the list. It is likely that over time the discussion will split into 
camps of like-minded design goals. The list might then spawn 
different lists for the folks of the different camps (mail-ng-shoe, 
mail-ng-sandal, ...). The list is explicitly not yet meant to be an 
IETF working group yet (if at all), and is probably more akin to the 
IRTF. But at the beginning, it will most likely be talking, not 
research.

See <http://www.imc.org/mail-ng/> for information on how to 
subscribe. The list is taking subscriptions now, and will probably go 
live for discussions within a week. Having some discussion on a 
mailing list now should make the dinners and bar gatherings at Seoul 
more interesting.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Sun Jan 25 20:38:49 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29239
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 Jan 2004 20:38:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AkvWf-00063a-8I
	for ietf-list@asgard.ietf.org; Sun, 25 Jan 2004 20:26:53 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AkvWM-00062f-FM
	for ietf@asgard.ietf.org; Sun, 25 Jan 2004 20:26:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28862
	for <ietf@ietf.org>; Sun, 25 Jan 2004 20:26:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkvWK-0001PQ-00
	for ietf@ietf.org; Sun, 25 Jan 2004 20:26:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AkvVN-0001Nl-00
	for ietf@ietf.org; Sun, 25 Jan 2004 20:25:34 -0500
Received: from [63.247.76.254] (helo=montage.altserver.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkvUh-0001M2-00
	for ietf@ietf.org; Sun, 25 Jan 2004 20:24:51 -0500
Received: from f02v-17-100.d0.club-internet.fr ([212.195.232.100] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1AkvUR-0001Gj-Ci; Sun, 25 Jan 2004 17:24:35 -0800
Message-Id: <6.0.1.1.2.20040125212813.04421d80@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sun, 25 Jan 2004 21:29:02 +0100
To: Valdis.Kletnieks@vt.edu, Haim Rochberger <haimro@p-cube.com>
From: jfcm <info@utel.net>
Subject: Re: packets of multiple users sent over the same TCP/IP
  session 
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
In-Reply-To: <200401251754.i0PHsjcJ001121@turing-police.cc.vt.edu>
References: <BB7797D6BF684A4B91ABB19AB6A579C567C3B3@ilmx1.p-cube.com>
 <200401251754.i0PHsjcJ001121@turing-police.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,DATE_IN_PAST_03_06 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 18:54 25/01/04, Valdis.Kletnieks@vt.edu wrote:
>It's tempting to suggest using IPv6 tunelling, and sorting out whos packets
>are whose by inserting the subscriber info in the low-order 64 bits.

That would make the solution dependent from the IPv6.001 numbering plan only.
jfc






From owner-ietf@ietf.org  Sun Jan 25 23:08:05 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03126
	for <ietf-web-archive@odin.ietf.org>; Sun, 25 Jan 2004 23:08:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Akxro-0000MH-Dh
	for ietf-list@asgard.ietf.org; Sun, 25 Jan 2004 22:56:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Akxra-0000LB-Oi
	for ietf@asgard.ietf.org; Sun, 25 Jan 2004 22:56:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02801
	for <ietf@ietf.org>; Sun, 25 Jan 2004 22:56:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkxrZ-0000SC-00
	for ietf@ietf.org; Sun, 25 Jan 2004 22:56:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Akxqb-0000Qk-00
	for ietf@ietf.org; Sun, 25 Jan 2004 22:55:38 -0500
Received: from sccrmhc13.comcast.net ([204.127.202.64])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkxqL-0000PA-00
	for ietf@ietf.org; Sun, 25 Jan 2004 22:55:21 -0500
Received: from dfnjgl21 (c-24-1-97-129.client.comcast.net[24.1.97.129])
          by comcast.net (sccrmhc13) with SMTP
          id <2004012603544601600hf2t5e>
          (Authid: sdawkins@comcast.net);
          Mon, 26 Jan 2004 03:54:46 +0000
Message-ID: <005101c3e3c0$2478d330$0400a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf@ietf.org>
References: <BB7797D6BF684A4B91ABB19AB6A579C567C3B3@ilmx1.p-cube.com>
Subject: Re: packets of multiple users sent over the same TCP/IP session 
Date: Sun, 25 Jan 2004 21:54:47 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The SMPP protocol really is a tunnelling protocol - one set of
endpoints is subscriber-to-subscriber, the other is server-to-server,
in this case, SMSC-to-ESME.

Since the subscriber-to-subscriber endpoints can use IP endpoint
addressing, ISDN endpoint addressing, or a mixture of IP and ISDN
addressing, it sounds like you really want to tunnel, but your inner
addressing is just strange.

Can you tell us any more about what you're trying to do?

Spencer

----- Original Message ----- 
From: "Haim Rochberger" <haimro@p-cube.com>
To: <Valdis.Kletnieks@vt.edu>; "Haim Rochberger" <haimro@p-cube.com>
Cc: <ietf@ietf.org>
Sent: Sunday, January 25, 2004 11:20 AM
Subject: RE: packets of multiple users sent over the same TCP/IP
session


> Hi Valdis,
>
> Thanks for the reply.
>
> SMPP is a good example to what I am looking for, and I am trying to
see if
> other
> protocol foreseen in the future (or past) have the same
characteristics:
>
> The special thing about SMPP is that in the same TCP/IP session
packet that
> are really SMS embedded in IP
> are sent from one network element (called SMSC) to another (called
ESME) -
> so that the packets (i.e. SMS) belong to different mobile users.
>
> In this case I cannot map the IP address of the TCP session to one
specific
> mobile subscriber - and the only way I can
> identify the subscriber is by "looking" on the SMPP layer (above the
TCP)
> and extract the subscriber mobile number.
>
> Another example may be SMTP (not sure).
>
> Anyway the thing I am trying to solve is whether I should consider
this kind
> of protocol characteristic as "special" and "rare", and so build a
dedicated
> solution for SMPP, or maybe I can expect to see many more such
protocol and
> so I should build a more generic solution.
>
> It is obvious to me that a generic solution is better technically,
but since
> my resources (i.e. time) is limited,
> I need to see how rare this kind of protocol (same TCP/IP with
packets of
> multiple users) is common/expected.
>
> Another characteristic of SMPP that I am looking for its
"commonness" is the
> fact that there could be many
> TCP/IP session from many SCSCs to ESMEs at the same time - and
packets of
> the SAME subscriber may appear
> on them at the same time...
>
> Complicated :-)   that's my life (-:
>
>
>
>
>
> yours,
>
> Haim Rochberger
>
>
>
>
> > -----Original Message-----
> > From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
> > Sent: Sun, January 25, 2004 6:43 PM
> > To: Haim Rochberger
> > Cc: 'ietf@ietf.org'
> > Subject: Re: packets of multiple users sent over the same
> > TCP/IP session
> >
> >
> >
> > On Sun, 25 Jan 2004 15:42:28 +0200, Haim Rochberger
> > <haimro@p-cube.com>  said:
> >
> > > I will appreciate your help as it will help in making a
> > better design
> > > decisions.
> >
> > Hmm.. been a while since I've had to post this. ;)
> >
> > The first thing you want to do is take a step *back* from the
> > problem, and ask
> > yourself what problem you're trying to solve via this
> > multiplexing.  You
> > already said you didn't want to use tunneling, but at the
> > same time you gave us
> > insufficient information to know if SMPP or anything similar
> > is applicable to
> > your problem. With the information you gave, it's likely many
> > will fear to give
> > you any really useful answers for fear of sending you in a
> > totally useless
> > direction.
> >
> > For all I know, HTTP pipelining may be a solution to your
> > problem - in that
> > scenario, you have in-flight packets for multiple HTTP requests
(read
> > "subscribers") active at the same time.  On the other hand,
> > although it meets
> > the requirements you stated, it's almost certainly not the
> > right answer.  But
> > not knowing what problem you're trying to solve, it's hard to say.
> >
> > Basically, you need to make sure that what you have in your
> > hand is a nail
> > rather than a screw *before* you start selecting hammers....
> >
> >
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it,
which is a sublist of ietf@ietf.org. Not all messages are passed.
Decisions on what to pass are made solely by IETF_CENSORED ML
Administrator (ietf_admin@ngnet.it).




From owner-ietf@ietf.org  Mon Jan 26 11:22:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11018
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 Jan 2004 11:22:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Al9My-00052x-IJ
	for ietf-list@asgard.ietf.org; Mon, 26 Jan 2004 11:13:48 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Al9MD-00052J-Kf
	for ietf@asgard.ietf.org; Mon, 26 Jan 2004 11:13:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10862
	for <ietf@ietf.org>; Mon, 26 Jan 2004 11:12:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Al9MC-00058X-00
	for ietf@ietf.org; Mon, 26 Jan 2004 11:13:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Al9LF-00056G-00
	for ietf@ietf.org; Mon, 26 Jan 2004 11:12:01 -0500
Received: from bws10.bridgewatersystems.com ([216.113.7.10] helo=exch01.bridgewatersys.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Al9L6-000544-00
	for ietf@ietf.org; Mon, 26 Jan 2004 11:11:52 -0500
Received: by exch01.bridgewatersys.com with Internet Mail Service (5.5.2657.72)
	id <Y0N7B85R>; Mon, 26 Jan 2004 11:11:22 -0500
Message-ID: <F17FB067A86B2D488382C923C532EAA793F6D5@exch01.bridgewatersys.com>
From: Avi Lior <avi@bridgewatersystems.com>
To: "'sommerfeld@orchard.arlington.ma.us'"
	 <sommerfeld@orchard.arlington.ma.us>,
        Gene Gaines
	 <gene.gaines@gainesgroup.com>
Cc: Ken Hornstein <kenh@cmf.nrl.navy.mil>, ietf@ietf.org
Subject: FYI  Visa for South Korea for Canadians
Date: Mon, 26 Jan 2004 11:11:16 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I just found this for Canadian Citizens: (Source:
http://www.emb-korea.ottawa.on.ca/html/html1/e_menu.htm)

Canadian citizens are exempt from obtaining a visa for tourism, visiting or
business(without any employment activities) for a stay of 90 days or less.
The permission to stay for 90 days or less will be given at the time of your
entry. Those who wish to stay longer can get an extension for an additional
90 days, for a total of 6 months.

Surprisingly these are much better (and clearer) terms then those for the
US.

Hope this helps (fellow Canadians),
Avi 




From owner-ietf@ietf.org  Mon Jan 26 16:05:03 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20262
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 Jan 2004 16:05:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlDlr-00035K-1A
	for ietf-list@asgard.ietf.org; Mon, 26 Jan 2004 15:55:47 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlDlI-000334-DJ
	for ietf@asgard.ietf.org; Mon, 26 Jan 2004 15:55:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19992
	for <ietf@ietf.org>; Mon, 26 Jan 2004 15:55:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlDlG-0003eW-00
	for ietf@ietf.org; Mon, 26 Jan 2004 15:55:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlDkH-0003bC-00
	for ietf@ietf.org; Mon, 26 Jan 2004 15:54:10 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlDjK-0003XB-00
	for ietf@ietf.org; Mon, 26 Jan 2004 15:53:11 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 6305B61B9A; Mon, 26 Jan 2004 21:52:39 +0100 (CET)
Date: Mon, 26 Jan 2004 12:52:38 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, ietf@ietf.org
Subject: Re: IETF registration and privacy ...
Message-ID: <1233372035.1075121558@halvestr-w2k1>
In-Reply-To: <040201c3dfb6$00f8e7a0$650a0a0a@consulintel.es>
References: <040201c3dfb6$00f8e7a0$650a0a0a@consulintel.es>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 21. januar 2004 01:32 +0100 JORDI PALET MARTINEZ 
<jordi.palet@consulintel.es> wrote:

> Hi,
>
> Despite that it has been commented in this list some time ago, I still
> see that the list of attendees is open, and there is no option, when
> registering to indicate if you want to be there or not ?
>
> I don't really mind myself, but we should have this option, at least this
> is my understanding from data protection laws all around the world.

There's a reverse consideration here - the availability of the public 
record of who attended meetings is an important part of the openness of the 
standards process.

Would *you* believe that a standard had been arrived at through a fair and 
open process in an indiviual-participation process where you're told that 
you can't see who the participants were?

We did remove the email addresses from the list....

                     Harald




From owner-ietf@ietf.org  Mon Jan 26 18:04:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23078
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 Jan 2004 18:04:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlFc2-0004wG-0K
	for ietf-list@asgard.ietf.org; Mon, 26 Jan 2004 17:53:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlFbe-0004vY-4Z
	for ietf@asgard.ietf.org; Mon, 26 Jan 2004 17:53:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22703
	for <ietf@ietf.org>; Mon, 26 Jan 2004 17:53:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlFbc-0001FU-00
	for ietf@ietf.org; Mon, 26 Jan 2004 17:53:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlFag-0001By-00
	for ietf@ietf.org; Mon, 26 Jan 2004 17:52:23 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlFZw-000155-00
	for ietf@ietf.org; Mon, 26 Jan 2004 17:51:36 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0QMouk15131;
	Mon, 26 Jan 2004 14:50:56 -0800
X-mProtect: <200401262250> Nokia Silicon Valley Messaging Protection
Received: from walnut2.iprg.nokia.com (205.226.9.199, claiming to be "spruce.nokia.com")
	by darkstar.iprg.nokia.com smtpdEatXqa; Mon, 26 Jan 2004 14:50:53 PST
Message-Id: <4.3.2.7.2.20040126144232.03296590@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 26 Jan 2004 14:47:38 -0800
To: Harald Tveit Alvestrand <harald@alvestrand.no>
From: Bob Hinden <bob.hinden@nokia.com>
Subject: Re: IETF registration and privacy ...
Cc: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, ietf@ietf.org
In-Reply-To: <1233372035.1075121558@halvestr-w2k1>
References: <040201c3dfb6$00f8e7a0$650a0a0a@consulintel.es>
 <040201c3dfb6$00f8e7a0$650a0a0a@consulintel.es>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Harald,

>>Despite that it has been commented in this list some time ago, I still
>>see that the list of attendees is open, and there is no option, when
>>registering to indicate if you want to be there or not ?
>>
>>I don't really mind myself, but we should have this option, at least this
>>is my understanding from data protection laws all around the world.
>
>There's a reverse consideration here - the availability of the public 
>record of who attended meetings is an important part of the openness of 
>the standards process.

I agree and think that there should continue to be a public record of who 
attended IETF meetings.  It is an important part of our open standards process.

It might be a good thing to disclose this to people when they register for 
the IETF meetings (if it isn't done already).

Bob




From owner-ietf@ietf.org  Mon Jan 26 19:02:12 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25341
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 Jan 2004 19:02:12 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlGY5-000691-FQ
	for ietf-list@asgard.ietf.org; Mon, 26 Jan 2004 18:53:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlGXe-00068F-PE
	for ietf@asgard.ietf.org; Mon, 26 Jan 2004 18:53:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25165
	for <ietf@ietf.org>; Mon, 26 Jan 2004 18:53:16 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlGXd-0004Cm-00
	for ietf@ietf.org; Mon, 26 Jan 2004 18:53:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlGWg-0004A0-00
	for ietf@ietf.org; Mon, 26 Jan 2004 18:52:18 -0500
Received: from [128.173.54.129] (helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlGVy-00046z-00
	for ietf@ietf.org; Mon, 26 Jan 2004 18:51:34 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id i0QNpVr5019099;
	Mon, 26 Jan 2004 18:51:31 -0500
Message-Id: <200401262351.i0QNpVr5019099@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Bob Hinden <bob.hinden@nokia.com>
Cc: ietf@ietf.org
Subject: Re: IETF registration and privacy ... 
In-Reply-To: Your message of "Mon, 26 Jan 2004 14:47:38 PST."
             <4.3.2.7.2.20040126144232.03296590@mailhost.iprg.nokia.com> 
References: <040201c3dfb6$00f8e7a0$650a0a0a@consulintel.es> <040201c3dfb6$00f8e7a0$650a0a0a@consulintel.es>
            <4.3.2.7.2.20040126144232.03296590@mailhost.iprg.nokia.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-38301371P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 Jan 2004 18:51:31 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Mon, 26 Jan 2004 14:47:38 PST, Bob Hinden said:
> I agree and think that there should continue to be a public record of who 
> attended IETF meetings.  It is an important part of our open standards process.
> 
> It might be a good thing to disclose this to people when they register for 
> the IETF meetings (if it isn't done already).

Indeed.  I'd be surprised if failing to do so doesn't fall astray of some EU privacy
laws - I've seen tell of the EU laws even being an issue for public mailing lists...




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

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

iD8DBQFAFagDcC3lWbTT17ARAnr2AKCd3c/wNpVtgmV5cnsNgXZz4ZkzLwCfU7BV
tYSzmjKHjUJMsTuCpVVx1+Q=
=WWdy
-----END PGP SIGNATURE-----

--==_Exmh_-38301371P--



From owner-ietf@ietf.org  Mon Jan 26 19:47:15 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25339
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 Jan 2004 19:02:12 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlGW9-00067N-JY
	for ietf-list@asgard.ietf.org; Mon, 26 Jan 2004 18:51:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlGVh-00066V-Nu
	for ietf@asgard.ietf.org; Mon, 26 Jan 2004 18:51:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25144
	for <ietf@ietf.org>; Mon, 26 Jan 2004 18:51:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlGVf-000463-00
	for ietf@ietf.org; Mon, 26 Jan 2004 18:51:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlGUg-00043a-00
	for ietf@ietf.org; Mon, 26 Jan 2004 18:50:15 -0500
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlGUA-00040V-00
	for ietf@ietf.org; Mon, 26 Jan 2004 18:49:43 -0500
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HS40060RFHLPZ@mailout2.samsung.com> for ietf@ietf.org; Tue,
 27 Jan 2004 08:48:57 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HS4002H8FHHF9@mailout2.samsung.com> for ietf@ietf.org; Tue,
 27 Jan 2004 08:48:53 +0900 (KST)
Received: from LocalHost ([168.219.203.183])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HS400IQHFHG77@mmp1.samsung.com> for ietf@ietf.org;
 Tue, 27 Jan 2004 08:48:52 +0900 (KST)
Date: Tue, 27 Jan 2004 08:48:43 +0900
From: "S. Daniel Park" <soohong.park@samsung.com>
Subject: RE: IETF registration and privacy ...
In-reply-to: <4.3.2.7.2.20040126144232.03296590@mailhost.iprg.nokia.com>
To: "'Bob Hinden'" <bob.hinden@nokia.com>,
        "'Harald Tveit Alvestrand'" <harald@alvestrand.no>
Cc: "'JORDI PALET MARTINEZ'" <jordi.palet@consulintel.es>, ietf@ietf.org
Message-id: <004601c3e466$ee925370$b7cbdba8@LocalHost>
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT


> It might be a good thing to disclose this to people when they 
> register for 
> the IETF meetings (if it isn't done already).

I'd second this utility. 
I also glance at the attendee list before do my registration.




Daniel (Soohong Daniel Park)
Mobile Platform Laboratory, Samsung Electronics.




From owner-ietf@ietf.org  Mon Jan 26 20:59:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01940
	for <ietf-web-archive@odin.ietf.org>; Mon, 26 Jan 2004 20:59:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlINJ-0000Ak-1o
	for ietf-list@asgard.ietf.org; Mon, 26 Jan 2004 20:50:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlIKz-00009k-3w
	for ietf@asgard.ietf.org; Mon, 26 Jan 2004 20:48:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01395
	for <ietf@ietf.org>; Mon, 26 Jan 2004 20:48:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlIKx-0005HX-00
	for ietf@ietf.org; Mon, 26 Jan 2004 20:48:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlIK0-0005GC-00
	for ietf@ietf.org; Mon, 26 Jan 2004 20:47:20 -0500
Received: from [213.172.48.142] (helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlIJh-0005Dt-00
	for ietf@ietf.org; Mon, 26 Jan 2004 20:47:01 -0500
Received: from consulintel02 ([219.122.122.82])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v6.8.5.R)
	with ESMTP id 62-md50000000083.tmp
	for <ietf@ietf.org>; Tue, 27 Jan 2004 02:49:49 +0100
Message-ID: <0d7201c3e477$c61b87c0$1d000a0a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <040201c3dfb6$00f8e7a0$650a0a0a@consulintel.es> <1233372035.1075121558@halvestr-w2k1>
Subject: Re: IETF registration and privacy ...
Date: Tue, 27 Jan 2004 10:49:12 +0900
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Tue, 27 Jan 2004 02:49:49 +0100
	(not processed: message from valid local sender)
X-MDRemoteIP: 219.122.122.82
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Well, the openness process can't go over the law ;-)

As said the solution is probably to tell the people that their details =
will be disclosed, before they register.

Regards,
Jordi

----- Original Message -----=20
From: "Harald Tveit Alvestrand" <harald@alvestrand.no>
To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>; <ietf@ietf.org>
Sent: Tuesday, January 27, 2004 5:52 AM
Subject: Re: IETF registration and privacy ...


>=20
>=20
> --On 21. januar 2004 01:32 +0100 JORDI PALET MARTINEZ=20
> <jordi.palet@consulintel.es> wrote:
>=20
> > Hi,
> >
> > Despite that it has been commented in this list some time ago, I =
still
> > see that the list of attendees is open, and there is no option, when
> > registering to indicate if you want to be there or not ?
> >
> > I don't really mind myself, but we should have this option, at least =
this
> > is my understanding from data protection laws all around the world.
>=20
> There's a reverse consideration here - the availability of the public=20
> record of who attended meetings is an important part of the openness =
of the=20
> standards process.
>=20
> Would *you* believe that a standard had been arrived at through a fair =
and=20
> open process in an indiviual-participation process where you're told =
that=20
> you can't see who the participants were?
>=20
> We did remove the email addresses from the list....
>=20
>                      Harald
> 

**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.





From owner-ietf@ietf.org  Tue Jan 27 02:36:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23149
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 Jan 2004 02:36:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlNbS-0005Oy-96
	for ietf-list@asgard.ietf.org; Tue, 27 Jan 2004 02:25:42 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlNbF-0005O7-N2
	for ietf@asgard.ietf.org; Tue, 27 Jan 2004 02:25:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22640
	for <ietf@ietf.org>; Tue, 27 Jan 2004 02:25:28 -0500 (EST)
From: pbaker@verisign.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlNbD-0004ZZ-00
	for ietf@ietf.org; Tue, 27 Jan 2004 02:25:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlNaE-0004WR-00
	for ietf@ietf.org; Tue, 27 Jan 2004 02:24:27 -0500
Received: from [203.122.20.167] (helo=sachin)
	by ietf-mx with smtp (Exim 4.12)
	id 1AlNZH-0004T4-00
	for ietf@ietf.org; Tue, 27 Jan 2004 02:23:27 -0500
Date: Tue, 27 Jan 2004 12:55:56 +0530
To: ietf@ietf.org
Subject: Hi
Message-ID: <botqxqsjyacflhrwqik@verisign.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------428017307478852"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=MICROSOFT_EXECUTABLE,
	NO_REAL_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

----------428017307478852
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

 Test =)
kgfatssnnyyebixjw
--
Test, yep.

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

[Filename: wwgyq.exe, Content-Type: application/x-msdownload]
The attachment file in the message has been removed by eManager.

----------428017307478852--




From owner-ietf@ietf.org  Tue Jan 27 14:39:50 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19714
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 Jan 2004 14:39:50 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlYlJ-0007FA-T4
	for ietf-list@asgard.ietf.org; Tue, 27 Jan 2004 14:20:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlYlF-0007EV-0X
	for ietf@asgard.ietf.org; Tue, 27 Jan 2004 14:20:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18960
	for <ietf@ietf.org>; Tue, 27 Jan 2004 14:20:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlYkt-0000Ve-00
	for ietf@ietf.org; Tue, 27 Jan 2004 14:20:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlYie-0000QS-00
	for ietf@ietf.org; Tue, 27 Jan 2004 14:17:53 -0500
Received: from stewart.chicago.il.us ([66.93.186.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlYhC-0000It-00
	for ietf@ietf.org; Tue, 27 Jan 2004 14:16:22 -0500
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1])
	by stewart.chicago.il.us (8.12.8p1/8.12.8) with ESMTP id i0RJFMO6054016;
	Tue, 27 Jan 2004 13:15:23 -0600 (CST)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <4016B8C9.5060504@stewart.chicago.il.us>
Date: Tue, 27 Jan 2004 13:15:21 -0600
From: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Haim Rochberger <haimro@p-cube.com>
CC: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: packets of multiple users sent over the same TCP/IP session
References: <BB7797D6BF684A4B91ABB19AB6A579C567C3AF@ilmx1.p-cube.com>
In-Reply-To: <BB7797D6BF684A4B91ABB19AB6A579C567C3AF@ilmx1.p-cube.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Haim:

If I understand your problem correctly I would think
the closest thing to this is what sigtran has done with
SS7 over IP..

They use SCTP and use its stream feature to avoid
head of line blocking for the various calls.. I am not
sure if they put each call in its own stream or each SLS
in its on stream.. either way would work.

In there case they have

xUA
------
SCTP
------
IP

Where xUA is their User Adaption layer.. and the X
being one of MTP2/MTP3 or S

Depending on what levels of the SS7 stack they are adapting

R

Haim Rochberger wrote:

> Hi,
>
> I am looking for any protocol or type of protocol/application that 
> runs over TCP/IP, and that packets of that *same* session "belong" 
> (i.e. either destined or sourced) to/by
> more then one subscribers (meaning that each packet belongs to *one* 
> subscriber, but there are a some packets that belong to subscriber A, 
> some to B, etc.).
>  
> I am not talking about tunneling protocol, as in their case the 
> internal IP is the identity of the subscriber, but I am talking about 
> protocols that the identity of the subscriber
> resides at the higher level, like the application layer, and the 
> muxing between the packets to subscribers can be done only if you 
> understand the protocol at that high level.
>  
>  
> An example for such a protocol is SMPP that is used for sending SMS 
> messages of different subscribers on the same TCP/IP session
> between the SMSC and the application server. There, the subscriber 
> identity is embedded in the SPMM protocol (above the TCP/IP).
>
> I will appreciate your help as it will help in making a better design 
> decisions.
>
> Yours,
>
> Haim.
>  



-- 
Randall R. Stewart
815-477-2127 (office)
815-342-5222 (cell phone)





From owner-ietf@ietf.org  Tue Jan 27 14:41:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19778
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 Jan 2004 14:41:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlZ0o-0007Rw-Ca
	for ietf-list@asgard.ietf.org; Tue, 27 Jan 2004 14:36:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlZ0b-0007Qt-3u
	for ietf@asgard.ietf.org; Tue, 27 Jan 2004 14:36:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19510
	for <ietf@ietf.org>; Tue, 27 Jan 2004 14:36:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlZ0Z-0001XB-00
	for ietf@ietf.org; Tue, 27 Jan 2004 14:36:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlYyw-0001N9-00
	for ietf@ietf.org; Tue, 27 Jan 2004 14:34:43 -0500
Received: from mail-dark.research.att.com ([192.20.225.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlYx3-00019c-00
	for ietf@ietf.org; Tue, 27 Jan 2004 14:32:45 -0500
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by mail-dark.research.att.com (Postfix) with ESMTP id 27190E81D3
	for <ietf@ietf.org>; Tue, 27 Jan 2004 14:32:56 -0500 (EST)
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-green.research.att.com (Postfix) with ESMTP id 21CA8F38D4
	for <ietf@ietf.org>; Tue, 27 Jan 2004 14:29:23 -0500 (EST)
Received: from berkshire.research.att.com (raptor.research.att.com [135.207.23.32])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id i0RJVoZ03721
	for <ietf@ietf.org>; Tue, 27 Jan 2004 14:31:50 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP id 3F1377B43
	for <ietf@ietf.org>; Tue, 27 Jan 2004 14:31:50 -0500 (EST)
From: Steve Bellovin <smb@research.att.com>
To: ietf@ietf.org
Subject: visa requirements (US citizens)
Date: Tue, 27 Jan 2004 14:31:50 -0500
Message-Id: <20040127193150.3F1377B43@berkshire.research.att.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I was advised by our corporate travel consultants that I should get a
visa.  Given the current international climate -- there was an article
in last Thursday's Wall Street Journal about how other countries
are retaliating for the current U.S. fingerprinting and visa application
requirements -- this may be a prudent course of action.



From owner-ietf@ietf.org  Tue Jan 27 16:18:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24861
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 Jan 2004 16:18:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlaSn-0001Fh-04
	for ietf-list@asgard.ietf.org; Tue, 27 Jan 2004 16:09:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlaS8-0001Em-Pb
	for ietf@asgard.ietf.org; Tue, 27 Jan 2004 16:08:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24442
	for <ietf@ietf.org>; Tue, 27 Jan 2004 16:08:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlaS7-0000dk-00
	for ietf@ietf.org; Tue, 27 Jan 2004 16:08:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlaRF-0000bS-00
	for ietf@ietf.org; Tue, 27 Jan 2004 16:08:01 -0500
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlaQi-0000Yj-00
	for ietf@ietf.org; Tue, 27 Jan 2004 16:07:28 -0500
Received: from [63.202.92.146] (adsl-66-125-125-65.dsl.pltn13.pacbell.net [66.125.125.65])
	(authenticated bits=0)
	by above.proper.com (8.12.11/8.12.8) with ESMTP id i0RL7Ps3058956;
	Tue, 27 Jan 2004 13:07:26 -0800 (PST)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p06020442bc3c82a5ebc6@[63.202.92.146]>
In-Reply-To: <20040127193150.3F1377B43@berkshire.research.att.com>
References: <20040127193150.3F1377B43@berkshire.research.att.com>
Date: Tue, 27 Jan 2004 13:07:27 -0800
To: Steve Bellovin <smb@research.att.com>, ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: visa requirements (US citizens)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-4.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 2:31 PM -0500 1/27/04, Steve Bellovin wrote:
>I was advised by our corporate travel consultants that I should get a
>visa.  Given the current international climate -- there was an article
>in last Thursday's Wall Street Journal about how other countries
>are retaliating for the current U.S. fingerprinting and visa application
>requirements -- this may be a prudent course of action.

The Korean embassy page that is linked to from the IETF meetings page 
(<http://www.koreaembassy.org/visiting/eng_visas.cfm>) makes it 
pretty darn clear that US folks should get a visa. They do have a 
link from that page saying how wonderful US-Korea relations are, of 
course.

Showing up in the airport without a visa and saying "but someone at 
one of your consulates told me I didn't need one" may go over as well 
in other countries as it does in the US...

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Tue Jan 27 20:05:10 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07312
	for <ietf-web-archive@odin.ietf.org>; Tue, 27 Jan 2004 20:05:10 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AldwZ-0004kX-A5
	for ietf-list@asgard.ietf.org; Tue, 27 Jan 2004 19:52:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AldwE-0004jY-Ci
	for ietf@asgard.ietf.org; Tue, 27 Jan 2004 19:52:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06759
	for <ietf@ietf.org>; Tue, 27 Jan 2004 19:52:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AldwC-0003sS-00
	for ietf@ietf.org; Tue, 27 Jan 2004 19:52:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AldvC-0003ns-00
	for ietf@ietf.org; Tue, 27 Jan 2004 19:51:10 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlduK-0003gk-00
	for ietf@ietf.org; Tue, 27 Jan 2004 19:50:18 -0500
Received: by franck-lxnb.sopac.org.fj (Postfix, from userid 501)
	id BB96E4B6A2; Tue, 27 Jan 2004 19:49:38 -0500 (EST)
Subject: Wiki RFC
From: Franck Martin <franck@sopac.org>
To: ietf@ietf.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-5mF822M1GpxtFNeNCtRY"
Organization: SOPAC
Message-Id: <1075250978.2820.55.camel@franck-lxnb.sopac.org.fj>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4-1.1mdk 
Date: 28 Jan 2004 12:49:38 +1200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


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

I was just wondering if there has been any work to standardise the Wiki
syntax/system into an RFC?

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

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

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

iD8DBQBAFwcivnmeYIHZEyARAmppAJkBtYTPmq9CsKnhu94hhXcsMJc1hgCeK2ot
/+lX+Cw1ARWqO2zIGlbLHxY=
=i8p3
-----END PGP SIGNATURE-----

--=-5mF822M1GpxtFNeNCtRY--



From owner-ietf@ietf.org  Wed Jan 28 11:04:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06099
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 11:04:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Alrse-0006Ta-EY
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 10:45:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AleVt-0005ZS-PX
	for ietf@asgard.ietf.org; Tue, 27 Jan 2004 20:29:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08894
	for <ietf@ietf.org>; Tue, 27 Jan 2004 20:29:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AleVs-00076R-00
	for ietf@ietf.org; Tue, 27 Jan 2004 20:29:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AleV4-00073x-00
	for ietf@ietf.org; Tue, 27 Jan 2004 20:28:15 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AleU7-0006xD-00
	for IETF@ietf.org; Tue, 27 Jan 2004 20:27:15 -0500
Received: from BBFUJIP.brandenburg.com (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i0S1Ygd08313
	for <IETF@ietf.org>; Tue, 27 Jan 2004 17:34:42 -0800
Date: Wed, 28 Jan 2004 07:36:46 +0900
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <19410259999.20040128073646@brandenburg.com>
To: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <116512686.1074013651@scan.jck.com>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

JCK> but the only realistic solution for someone who needs high
JCK> reliability in that environment is multihoming, and there seems 
JCK> to be no hope for multihoming of small-scale networks with IPv4.

There is not much of a solution, today, for either IPv4 _or_ IPv6.

However there are nearly 10 different proposals under consideration in
the IETF, to deal with multihoming.  Few are restricted to IPv4.

In other words, when there is a serious solution to multihoming -- ie,
being able to preserve a connection when using more than one IP
Address -- it will likely work for IPv4.

Most of these proposals are quite new.  No more than a year old and
many less than 6 months.

This does not speak well for anything happening immediately, of
course.  However quite a number of the proposals do not require any
significant infrastructure change.  This bodes well for rapid
deployment, once they make it through the standards process.

On the other hand, getting the IETF to produce standards track
specifications out of this large pack of candidates could take another
10 years...

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






From owner-ietf@ietf.org  Wed Jan 28 13:05:01 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17366
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 13:05:01 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Althz-0000Yu-K0
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 12:42:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Alth3-0000UR-BX
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 12:41:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16250
	for <ietf@ietf.org>; Wed, 28 Jan 2004 12:41:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alth2-0004i5-00
	for ietf@ietf.org; Wed, 28 Jan 2004 12:41:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Altg8-0004cd-00
	for ietf@ietf.org; Wed, 28 Jan 2004 12:40:41 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AltfH-0004Xx-00
	for IETF@ietf.org; Wed, 28 Jan 2004 12:39:47 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1Altf9-0008Vs-00; Wed, 28 Jan 2004 12:39:39 -0500
Date: Wed, 28 Jan 2004 12:39:39 -0500
From: John C Klensin <john-ietf@jck.com>
To: Dave Crocker <dhc@dcrocker.net>, IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <224923613.1075293579@scan.jck.com>
In-Reply-To: <19410259999.20040128073646@brandenburg.com>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com>
 <19410259999.20040128073646@brandenburg.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave,

Just to pick a small nit or three...

--On Wednesday, 28 January, 2004 07:36 +0900 Dave Crocker 
<dhc@dcrocker.net> wrote:

> John,
>
> JCK> but the only realistic solution for someone who needs high
> JCK> reliability in that environment is multihoming, and there
> seems  JCK> to be no hope for multihoming of small-scale
> networks with IPv4.
>
> There is not much of a solution, today, for either IPv4 _or_
> IPv6.
>
> However there are nearly 10 different proposals under
> consideration in the IETF, to deal with multihoming.  Few are
> restricted to IPv4.

or to IPv6, which I assume is what you intended.

> In other words, when there is a serious solution to
> multihoming -- ie, being able to preserve a connection when
> using more than one IP Address -- it will likely work for IPv4.

Actually, that definition changes the problem into a much harder 
one, and one that I think is unnecessary for the problem I was 
discussing --unnecessary 99% of the time, if not always.  The 
reality is that there is very little that we do on the Internet 
today that require connection persistence when a link goes bad 
(or when "using more than one IP address").  If a connection 
goes down, email retries, file transfer connections are 
reconnected and the file (or the balance of the file if 
checkpointing is in use) is transferred again, URLs are 
refreshed, telnet and tunnel connections are recreated over 
other paths, and so on.  It might be claimed that our 
applications, and our human work habits, are designed to work at 
least moderately well when running over a TCP that is vunerable 
to dropped physical connections.

Would it be good to have a TCP, or TCP-equivalent, that did not 
have that vunerability, i.e., "could preserve a connection when 
using more than one address"?  Sure, if the cost was not too 
high on normal operations and we could actually get it.  But the 
goal has proven elusive for the last 30-odd years -- at least in 
the absence of running with full IP Mobility machinery all of 
the time, which involves its own issues -- and, frankly, I'm not 
holding my breath.

By contrast, the problem that I find of greatest concern is the 
one in which, if I'm communicating with you, and one or the 
other of us has multiple connections available, and the 
connection path between us (using one address each) disappears 
or goes bad, we can efficiently switch to a different 
combination... even if all open TCP connections drop and have to 
be reestablished in the interim. For _that_ problem, we had a 
reasonably effective IPv4 solution (at least for those who could 
afford it) for many years -- all one needed was multiple 
interfaces on the relevant equipment (the hosts early on and the 
router later) with, of course, a different connection and 
address on each interface.  But, when we imposed CIDR, and the 
address-allocation restrictions that went with it, it became 
impossible for someone to get the PI space that is required to 
operate a LAN behind such an arrangement (at least without 
having a NAT associated with the relevant router) unless one was 
running a _very_ large network.

Now, I'll stipulate this is a routing problem as much, or more, 
than it is an address-availability problem.  And I'll also agree 
that there appears to be little evidence that IPv6 is 
significantly more routing-friendly than IPv4 and hence, that 
any real routing-based solutions that help the one will help the 
other.  But,

	(i) if any of the options turn out to require an
	approach similar to the one that continue to work for
	big enterprises with PI space in IPv4, then we are going
	to need (lots) more address space.  And
	
	(ii) If any of the "multiple addresses per host" or
	"tricks with prefixes" approaches are actually workable
	and can be adequately defined and implemented at scale
	--and there is some evidence that variations of them can
	be, at least for leaf networks-- then they really do
	depend on structure and facilities that appear to me to
	are available in IPv6 and not in IPv4.

So, for the problem I was referring to (but perhaps not for your 
much more general formulation), I stand by my comment and 
analysis.

> Most of these proposals are quite new.  No more than a year
> old and many less than 6 months.
>
> This does not speak well for anything happening immediately, of
> course.  However quite a number of the proposals do not
> require any significant infrastructure change.  This bodes
> well for rapid deployment, once they make it through the
> standards process.
>
> On the other hand, getting the IETF to produce standards track
> specifications out of this large pack of candidates could take
> another 10 years...

Yes.  And it may speak to the IETF's sense of priorities that 
the efforts to which you refer are predominantly going into the 
much more complex and long-term problem, rather than the one 
that is presumably easier to solve and higher leverage.

     john





From owner-ietf@ietf.org  Wed Jan 28 13:56:00 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19887
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 13:56:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Alum2-00046m-9E
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 13:50:50 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aluj2-0003vF-1t
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 13:47:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19547
	for <ietf@ietf.org>; Wed, 28 Jan 2004 13:47:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aluj1-0003Qu-00
	for ietf@ietf.org; Wed, 28 Jan 2004 13:47:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Alui8-0003M8-00
	for ietf@ietf.org; Wed, 28 Jan 2004 13:46:48 -0500
Received: from letters.cs.ucsb.edu ([128.111.41.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aluhd-0003Gv-00
	for ietf@ietf.org; Wed, 28 Jan 2004 13:46:17 -0500
Received: from jackson.cs.ucsb.edu (jackson [128.111.52.10])
	by letters.cs.ucsb.edu (8.11.7+Sun/8.11.7) with ESMTP id i0SIkDc18003
	for <ietf@ietf.org>; Wed, 28 Jan 2004 10:46:14 -0800 (PST)
Received: from jackson.cs.ucsb.edu (localhost [127.0.0.1])
	by jackson.cs.ucsb.edu (8.12.8/8.11.6) with ESMTP id i0SIkDti005033
	for <ietf@ietf.org>; Wed, 28 Jan 2004 10:46:13 -0800
Received: (from almeroth@localhost)
	by jackson.cs.ucsb.edu (8.12.8/8.12.8/Submit) id i0SIkCqK005031
	for ietf@ietf.org; Wed, 28 Jan 2004 10:46:12 -0800
Date: Wed, 28 Jan 2004 10:46:12 -0800
From: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
Message-Id: <200401281846.i0SIkCqK005031@jackson.cs.ucsb.edu>
To: ietf@ietf.org
Subject: Re: visa requirements (US citizens)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>>The Korean embassy page that is linked to from the IETF meetings page 
>>(<http://www.koreaembassy.org/visiting/eng_visas.cfm>) makes it 
>>pretty darn clear that US folks should get a visa. They do have a 
>>link from that page saying how wonderful US-Korea relations are, of 
>>course.

What part are you reading that says this?

"# You may enter Korea without a visa for a stay up to 30 days 
or less for tourism, visiting, or transit to another country when 
carrying a valid US passport."

Seems to me to pretty clear that a visa is not needed.

-Kevin



From owner-ietf@ietf.org  Wed Jan 28 14:21:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21426
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 14:21:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Alv93-0006pf-Pe
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 14:14:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Alv5J-0006YS-QV
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 14:10:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20943
	for <ietf@ietf.org>; Wed, 28 Jan 2004 14:10:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alv5I-00063j-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:10:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Alv4O-0005xF-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:09:48 -0500
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alv3U-0005qd-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:08:53 -0500
Received: from [63.202.92.156] (adsl-66-125-125-65.dsl.pltn13.pacbell.net [66.125.125.65])
	(authenticated bits=0)
	by above.proper.com (8.12.11/8.12.8) with ESMTP id i0SJ8lDl052204;
	Wed, 28 Jan 2004 11:08:47 -0800 (PST)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p06020419bc3db8d12d73@[63.202.92.156]>
In-Reply-To: <200401281846.i0SIkCqK005031@jackson.cs.ucsb.edu>
References: <200401281846.i0SIkCqK005031@jackson.cs.ucsb.edu>
Date: Wed, 28 Jan 2004 11:08:49 -0800
To: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>, ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: visa requirements (US citizens)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:46 AM -0800 1/28/04, Kevin C. Almeroth wrote:
>  >>The Korean embassy page that is linked to from the IETF meetings page
>>>(<http://www.koreaembassy.org/visiting/eng_visas.cfm>) makes it
>>>pretty darn clear that US folks should get a visa. They do have a
>>>link from that page saying how wonderful US-Korea relations are, of
>>>course.
>
>What part are you reading that says this?
>
>"# You may enter Korea without a visa for a stay up to 30 days
>or less for tourism, visiting, or transit to another country when
>carrying a valid US passport."
>
>Seems to me to pretty clear that a visa is not needed.

I am not a lawyer, but I don't think attending a professional meeting 
is either "tourism", "visiting", or "transit to another country". 
YMMV.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Wed Jan 28 14:21:58 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21486
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 14:21:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlvA4-0006vB-JY
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 14:15:40 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Alv6Y-0006cb-H9
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 14:12:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21033
	for <ietf@ietf.org>; Wed, 28 Jan 2004 14:12:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alv6X-0006EY-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:12:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Alv5b-00066n-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:11:04 -0500
Received: from 216-43-25-66.ip.mcleodusa.net ([216.43.25.66] helo=episteme-software.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alv4e-0005sL-00
	for IETF@ietf.org; Wed, 28 Jan 2004 14:10:05 -0500
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server X 3.2.3b4);
 Wed, 28 Jan 2004 13:09:34 -0600
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p06100901bc3db58a1619@[216.43.25.67]>
In-Reply-To: <224923613.1075293579@scan.jck.com>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com>
 <19410259999.20040128073646@brandenburg.com>
 <224923613.1075293579@scan.jck.com>
X-Mailer: Eudora [Macintosh version 6.1a9]
Date: Wed, 28 Jan 2004 13:09:35 -0600
To: John C Klensin <john-ietf@jck.com>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Death of the Internet - details at 11
Cc: Dave Crocker <dhc@dcrocker.net>, IETF@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.9 required=5.0 tests=AWL,FORGED_MUA_EUDORA 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On 1/28/04 at 12:39 PM -0500, John C Klensin wrote:

>The reality is that there is very little that we do on the Internet 
>today that require connection persistence when a link goes bad (or 
>when "using more than one IP address").  If a connection goes down, 
>email retries, file transfer connections are reconnected and the 
>file (or the balance of the file if checkpointing is in use) is 
>transferred again, URLs are refreshed, telnet and tunnel connections 
>are recreated over other paths, and so on.  It might be claimed that 
>our applications, and our human work habits, are designed to work at 
>least moderately well when running over a TCP that is vunerable to 
>dropped physical connections.
>
>Would it be good to have a TCP, or TCP-equivalent, that did not have 
>that vunerability, i.e., "could preserve a connection when using 
>more than one address"?  Sure, if the cost was not too high on 
>normal operations and we could actually get it.  But the goal has 
>proven elusive for the last 30-odd years -- at least in the absence 
>of running with full IP Mobility machinery all of the time, which 
>involves its own issues -- and, frankly, I'm not holding my breath.

I am rather ambivalent about this issue (it seems like the obvious 
thing to do, but also seems quite painful to accomplish), but I do 
think there is something missing in this response: "The cost" to 
which you refer needs to be weighed against the cost of *not* doing 
so, and that cost seems to have been mounting all along and shows no 
sign of slowing down. The fact is that we have had to engineer all 
sorts of application-layer solutions to this single problem and will 
continue to do so for new application-layer protocols into the 
future. Worse yet, some of those solutions continue to include 
ridiculously high-cost solutions such as having to retransmit entire 
files, and my guess is such costs (bandwidth and otherwise) will 
continue in the future. I also think that the argument ignores the 
possibility that if we do address the "connection persistence" 
problem, we will be able to do many things at the application layer 
that we have always avoided doing because of the cost of having to 
engineer around it. From the view up here in the nosebleed section, 
it seems like it is worth at least the attempt to get a solution.
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
QUALCOMM Incorporated



From owner-ietf@ietf.org  Wed Jan 28 14:49:59 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23266
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 14:49:59 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlvUC-0001H8-K7
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 14:36:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlvSW-00015J-Ez
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 14:34:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22433
	for <ietf@ietf.org>; Wed, 28 Jan 2004 14:34:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlvSV-00014p-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:34:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlvRX-0000zy-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:33:43 -0500
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlvQn-0000rC-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:32:58 -0500
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49])
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id i0SJSLa19454
	for <ietf@ietf.org>; Wed, 28 Jan 2004 11:28:22 -0800
Date: Wed, 28 Jan 2004 11:28:17 -0800 (PST)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
Subject: Re: visa requirements (US citizens)
In-Reply-To: <p06020419bc3db8d12d73@[63.202.92.156]>
Message-ID: <Pine.LNX.4.33.0401281125260.19436-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Furthermore, how often have you found that web content hasn't been kept
current ???

And exactly who will you appeal to if you arrive in Korea without a Visa
and you discover it is recovered.

If I were investing my funds in travel to Korea, I'd make sure that I had
the proper documents by dealing DIRECTLY with the authorized
representatives of the government in question.

On Wed, 28 Jan 2004, Paul Hoffman / IMC wrote:

> At 10:46 AM -0800 1/28/04, Kevin C. Almeroth wrote:
> >  >>The Korean embassy page that is linked to from the IETF meetings page
> >>>(<http://www.koreaembassy.org/visiting/eng_visas.cfm>) makes it
> >>>pretty darn clear that US folks should get a visa. They do have a
> >>>link from that page saying how wonderful US-Korea relations are, of
> >>>course.
> >
> >What part are you reading that says this?
> >
> >"# You may enter Korea without a visa for a stay up to 30 days
> >or less for tourism, visiting, or transit to another country when
> >carrying a valid US passport."
> >
> >Seems to me to pretty clear that a visa is not needed.
>
> I am not a lawyer, but I don't think attending a professional meeting
> is either "tourism", "visiting", or "transit to another country".
> YMMV.
>
> --Paul Hoffman, Director
> --Internet Mail Consortium
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on what to pass are made solely by IETF_CENSORED ML Administrator (ietf_admin@ngnet.it).
>




From owner-ietf@ietf.org  Wed Jan 28 14:49:59 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23274
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 14:49:59 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlvUC-0001Gx-8V
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 14:36:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlvRX-0000vu-37
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 14:33:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22419
	for <ietf@ietf.org>; Wed, 28 Jan 2004 14:33:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlvRV-0000zc-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:33:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlvQZ-0000vQ-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:32:44 -0500
Received: from oetest.freeswan.org ([205.150.200.166] helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlvPx-0000r0-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:32:05 -0500
Received: from sandelman.ottawa.on.ca (unionstation.halfspot.bellnexxia.net. [67.69.0.130])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id i0SJVLS00390
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK);
	Wed, 28 Jan 2004 14:31:30 -0500 (EST)
Received: from marajade.sandelman.ottawa.on.ca (marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id i0RMRBsM032002
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 27 Jan 2004 17:27:12 -0500
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by marajade.sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id i0RMR9xk031998;
	Tue, 27 Jan 2004 17:27:10 -0500
To: Haim Rochberger <haimro@p-cube.com>
cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: packets of multiple users sent over the same TCP/IP session 
In-reply-to: Your message of "Sun, 25 Jan 2004 15:42:28 +0200."
             <BB7797D6BF684A4B91ABB19AB6A579C567C3AF@ilmx1.p-cube.com> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 27 Jan 2004 17:27:08 -0500
Message-ID: <31997.1075242428@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=LINES_OF_YELLING autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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


>>>>> "Haim" == Haim Rochberger <haimro@p-cube.com> writes:
    Haim> I am looking for any protocol or type of protocol/application that
    Haim> runs over 
    Haim> TCP/IP, and that packets of that same session "belong" (i.e. either
    Haim> destined or sourced) to/by more then one subscribers (meaning that
    Haim> each packet belongs to one subscriber, but there are a some packets
    Haim> that belong to subscriber A, some to B, etc.).

  Examples that come to mind:
	   1) NFSv3 over TCP	(one TCP connection per mount)

	   2) SMTP		(multiple users' transactions per session)

	   3) persistent HTTP from a www proxy.
	      (I'm not really sure if this is really done)

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

iQCVAwUBQBbluoqHRg3pndX9AQGt8AQApnjdup1s9FchlNqgvnnMIYNw/N8nHEOT
yck+H0et3JMGUK+pNhd+1j4MRQmizNyP2+4Q4+Od/DT/lJ9B42jaxy4aC6sgx9MI
BJH1ye53bQS8li9n8nwj2nw0Eg+c2UgqyfbheDAHSu33WbWS5eKYdnXlyGKo+NN/
uE8ccpJImKY=
=MUk9
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Wed Jan 28 14:58:33 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23826
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 14:58:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Alvke-0003WI-Ns
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 14:53:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Alvix-00031b-Q7
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 14:51:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23338
	for <ietf@ietf.org>; Wed, 28 Jan 2004 14:51:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alviw-0002yz-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:51:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Alvhw-0002oU-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:50:40 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alvgy-0002gr-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:49:40 -0500
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i0SJnanp013658
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 28 Jan 2004 11:49:37 -0800 (PST)
Received: from [129.46.227.161] (carbuncle.qualcomm.com [129.46.227.161])
	by crowley.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i0SJnYRY002998;
	Wed, 28 Jan 2004 11:49:35 -0800 (PST)
Mime-Version: 1.0
X-Sender: hardie@mage.qualcomm.com
Message-Id: <p06020404bc3dc193a137@[129.46.227.161]>
In-Reply-To: <p06020419bc3db8d12d73@[63.202.92.156]>
References: <200401281846.i0SIkCqK005031@jackson.cs.ucsb.edu>
 <p06020419bc3db8d12d73@[63.202.92.156]>
Date: Wed, 28 Jan 2004 11:49:33 -0800
To: Paul Hoffman / IMC <phoffman@imc.org>,
        "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>, ietf@ietf.org
From: Ted Hardie <hardie@qualcomm.com>
Subject: Re: visa requirements (US citizens)
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 11:08 AM -0800 01/28/2004, Paul Hoffman / IMC wrote:
>At 10:46 AM -0800 1/28/04, Kevin C. Almeroth wrote:
>> >>The Korean embassy page that is linked to from the IETF meetings page
>>>>(<http://www.koreaembassy.org/visiting/eng_visas.cfm>) makes it
>>>>pretty darn clear that US folks should get a visa. They do have a
>>>>link from that page saying how wonderful US-Korea relations are, of
>>>>course.
>>
>>What part are you reading that says this?
>>
>>"# You may enter Korea without a visa for a stay up to 30 days
>>or less for tourism, visiting, or transit to another country when
>>carrying a valid US passport."
>>
>>Seems to me to pretty clear that a visa is not needed.
>
>I am not a lawyer, but I don't think attending a professional meeting is either "tourism", "visiting", or "transit to another country". YMMV.

Nor am I a lawyer.  I have heard several times, though, that "visiting" includes meetings of
this type, since attendees are not being paid by a Korean company for work and are
not expected to sell goods or services to Korean companies while there.  I took away
from that the idea that "if your economic interaction with Korea while there is
only that of 'consumer', you are visiting".

Again, I am not a lawyer, and I suggest only that there may be a different view.
				regards,
					Ted Hardie



From owner-ietf@ietf.org  Wed Jan 28 15:13:53 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25187
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 15:13:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Alvz9-0005L2-Re
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 15:08:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlvxT-00057U-HX
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 15:06:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24446
	for <ietf@ietf.org>; Wed, 28 Jan 2004 15:06:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlvxS-0004bj-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:06:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlvwV-0004XZ-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:05:43 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alvvy-0004Qk-00
	for IETF@ietf.org; Wed, 28 Jan 2004 15:05:10 -0500
Received: from [130.105.19.131] ([130.105.19.131])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i0SK4aRQ027408
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 28 Jan 2004 15:04:36 -0500
Date: Wed, 28 Jan 2004 15:04:36 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@localhost.localdomain
To: Dave Crocker <dhc@dcrocker.net>
cc: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <19410259999.20040128073646@brandenburg.com>
Message-ID: <Pine.LNX.4.44.0401281444220.13261-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 28 Jan 2004, Dave Crocker wrote:

> John,
> 
> JCK> but the only realistic solution for someone who needs high
> JCK> reliability in that environment is multihoming, and there seems 
> JCK> to be no hope for multihoming of small-scale networks with IPv4.
> 
> There is not much of a solution, today, for either IPv4 _or_ IPv6.

There is a good solution, and it works for IPv4. But I can't tell you what
it is, since I am making money with that knowledge, and I don't want to 
tell my competitors my business.

But I will give you a hint:  Over-consolidation doesn't scale well.  It
just creates exhorbitant executive salaries, crazy-stupid business plans
funded by VC, and opportunities for undercooked books.  The dinosaurs are
dying, and they don't know why.  To continue the metaphor, I'm small and
furry, and I don't really know why they are dying either. But I know I'm
not in the same boat.

		--Dean





From owner-ietf@ietf.org  Wed Jan 28 15:13:54 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25203
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 15:13:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlvzA-0005L8-5j
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 15:08:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlvxU-00057W-4E
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 15:06:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24452
	for <ietf@ietf.org>; Wed, 28 Jan 2004 15:06:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlvxS-0004bo-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:06:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlvwV-0004Xh-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:05:44 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alvw6-0004TP-00
	for IETF@ietf.org; Wed, 28 Jan 2004 15:05:18 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1Alvw5-000AbA-00; Wed, 28 Jan 2004 15:05:17 -0500
Date: Wed, 28 Jan 2004 15:05:17 -0500
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qualcomm.com>
cc: Dave Crocker <dhc@dcrocker.net>, IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <2230797.1075302317@scan.jck.com>
In-Reply-To: <p06100901bc3db58a1619@[216.43.25.67]>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com>
 <19410259999.20040128073646@brandenburg.com>
 <224923613.1075293579@scan.jck.com>
 <p06100901bc3db58a1619@[216.43.25.67]>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pete,

I think the _attempt_ and _effort_ to get a solution to the 
persistent connection problem is entirely worthwhile and did not 
mean to suggest otherwise.  I think that ignoring or delaying an 
easier, and still important, problem while we work the 
persistent connection one borders on irresponsible.  And that 
distinction is the only one I was attempting to make.

We may still disagree, of course.

    john


--On Wednesday, 28 January, 2004 13:09 -0600 Pete Resnick 
<presnick@qualcomm.com> wrote:

> On 1/28/04 at 12:39 PM -0500, John C Klensin wrote:
>
>> The reality is that there is very little that we do on the
>> Internet  today that require connection persistence when a
>> link goes bad (or  when "using more than one IP address").
>> If a connection goes down,  email retries, file transfer
>> connections are reconnected and the  file (or the balance of
>> the file if checkpointing is in use) is  transferred again,
>> URLs are refreshed, telnet and tunnel connections  are
>> recreated over other paths, and so on.  It might be claimed
>> that  our applications, and our human work habits, are
>> designed to work at  least moderately well when running over
>> a TCP that is vunerable to  dropped physical connections.
>>
>> Would it be good to have a TCP, or TCP-equivalent, that did
>> not have  that vunerability, i.e., "could preserve a
>> connection when using  more than one address"?  Sure, if the
>> cost was not too high on  normal operations and we could
>> actually get it.  But the goal has  proven elusive for the
>> last 30-odd years -- at least in the absence  of running with
>> full IP Mobility machinery all of the time, which  involves
>> its own issues -- and, frankly, I'm not holding my breath.
>
> I am rather ambivalent about this issue (it seems like the
> obvious thing to do, but also seems quite painful to
> accomplish), but I do think there is something missing in this
> response: "The cost" to which you refer needs to be weighed
> against the cost of *not* doing so, and that cost seems to
> have been mounting all along and shows no sign of slowing
> down. The fact is that we have had to engineer all sorts of
> application-layer solutions to this single problem and will
> continue to do so for new application-layer protocols into the
> future. Worse yet, some of those solutions continue to include
> ridiculously high-cost solutions such as having to retransmit
> entire files, and my guess is such costs (bandwidth and
> otherwise) will continue in the future. I also think that the
> argument ignores the possibility that if we do address the
> "connection persistence" problem, we will be able to do many
> things at the application layer that we have always avoided
> doing because of the cost of having to engineer around it.
> From the view up here in the nosebleed section, it seems like
> it is worth at least the attempt to get a solution.







From owner-ietf@ietf.org  Wed Jan 28 15:31:11 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26597
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 15:31:11 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlwDf-0007WS-RT
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 15:23:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlwD1-0007M2-Q7
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 15:22:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26328
	for <ietf@ietf.org>; Wed, 28 Jan 2004 15:22:45 -0500 (EST)
From: USPhoenix@aol.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlwD0-0006XM-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:22:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlwC6-0006Rn-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:21:50 -0500
Received: from imo-r01.mx.aol.com ([152.163.225.97])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlwBF-0006HB-00
	for IETF@ietf.org; Wed, 28 Jan 2004 15:20:57 -0500
Received: from USPhoenix@aol.com
	by imo-r01.mx.aol.com (mail_out_v36_r4.12.) id l.89.2253494 (4468)
	 for <IETF@ietf.org>; Wed, 28 Jan 2004 15:20:22 -0500 (EST)
Message-ID: <89.2253494.2d497386@aol.com>
Date: Wed, 28 Jan 2004 15:20:22 EST
Subject: Re: Death of the Internet - details at 11
To: IETF@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1075321221"
X-Mailer: 9.0 for Windows sub 5006
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=HTML_70_80,HTML_MESSAGE,
	NO_REAL_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


-------------------------------1075321221
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Amen to those words

Wayne

-------------------------------1075321221
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD>
<META charset=3DUTF-8 http-equiv=3DContent-Type content=3D"text/html; charse=
t=3Dutf-8">
<META content=3D"MSHTML 6.00.2734.1600" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; BACKGROUND-COLOR: #fffff=
f">
<DIV>Amen to those words</DIV>
<DIV>&nbsp;</DIV>
<DIV>Wayne</DIV></BODY></HTML>

-------------------------------1075321221--



From owner-ietf@ietf.org  Wed Jan 28 16:01:58 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28284
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 16:01:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Alwit-0003oS-O8
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 15:55:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlwgG-0002w1-II
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 15:53:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27606
	for <ietf@ietf.org>; Wed, 28 Jan 2004 15:52:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlwgF-0001l0-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:52:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlwfH-0001aT-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:52:00 -0500
Received: from ginger.cmf.nrl.navy.mil ([134.207.10.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alweh-0001TC-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:51:23 -0500
Received: from cmf.nrl.navy.mil (fermi.cmf.nrl.navy.mil [134.207.10.73])
	(authenticated bits=0)
	by ginger.cmf.nrl.navy.mil (8.12.7/8.12.7) with ESMTP id i0SKpKRr007608
	for <ietf@ietf.org>; Wed, 28 Jan 2004 15:51:20 -0500 (EST)
Message-Id: <200401282051.i0SKpKRr007608@ginger.cmf.nrl.navy.mil>
To: ietf@ietf.org
Subject: Re: visa requirements (US citizens) 
In-reply-to: Your message of "Wed, 28 Jan 2004 11:08:49 PST."
             <p06020419bc3db8d12d73@[63.202.92.156]> 
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4
	WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d
	gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;Mv(aiO2z~9n.w?@\>kEpSD@*e`
Date: Wed, 28 Jan 2004 15:51:19 -0500
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
X-Spam-Score: () hits=0 User Authenticated
X-Virus-Scanned: NAI Completed
X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>>"# You may enter Korea without a visa for a stay up to 30 days
>>or less for tourism, visiting, or transit to another country when
>>carrying a valid US passport."
>>
>>Seems to me to pretty clear that a visa is not needed.
>
>I am not a lawyer, but I don't think attending a professional meeting 
>is either "tourism", "visiting", or "transit to another country". 
>YMMV.

Man, where were you guys the first time this was discussed here? :-)

So, my initial reading of the embassy web page was in line with Paul's;
it certainly seemed to me that IETF attendees would need a visa.  When
I mentioned this to the list, a bunch of people chimed up and said, "What
are you talking about, I've been there a bazillion times for meetings
and never needed a visa".

Sam Hartman and I called our respective consulates (Boston and Washington, DC,
respectively).  Sam was told unambiguously that a visa was not required.
I spoke to a seemingly less knowledgeable person, who was not completely
sure, but seemed to indicate that since IETF was non-profit, a visa was not
required.  Someone else on this list (forgive me, I don't remember your
name), had contact with the Korean Ambassador to the US, and forwarded an
email from either him or a representative who indicated that a visa is
not required.

However, Steve Bellovin has an excellent point; these reprisals by
other countries in response to our new immigration policies are
documented, and while I haven't seen any specific examples of ones from
Korea, it's certainly a possibility.  I'd hate to be the one who gets
the "rubber glove" treatment from a immigration official who has a beef
with the US.

My feeling regarding the whole thing is:

- Without a visa, you're probably okay.
- With a visa, you're almost certainly okay.

On a side note ... has anyone else had problems getting to the web site
of the host?  http://www.tta.or.kr/ietf59/index.htm has failed every time
I've tried to connect to it in the past few weeks.

--Ken



From owner-ietf@ietf.org  Wed Jan 28 16:02:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28326
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 16:02:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Alwiu-0003ot-7J
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 15:55:44 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlwhT-0003Kt-04
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 15:54:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27763
	for <ietf@ietf.org>; Wed, 28 Jan 2004 15:54:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlwhR-0001xs-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:54:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Alwga-0001o6-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:53:21 -0500
Received: from stewart.chicago.il.us ([66.93.186.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alwfb-0001Yo-00
	for IETF@ietf.org; Wed, 28 Jan 2004 15:52:19 -0500
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1])
	by stewart.chicago.il.us (8.12.8p1/8.12.8) with ESMTP id i0SKpfO6062431;
	Wed, 28 Jan 2004 14:51:42 -0600 (CST)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <401820DD.1000302@stewart.chicago.il.us>
Date: Wed, 28 Jan 2004 14:51:41 -0600
From: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dave Crocker <dhc@dcrocker.net>
CC: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com>
In-Reply-To: <19410259999.20040128073646@brandenburg.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave:

Comments in-line below..

Dave Crocker wrote:

>John,
>
>JCK> but the only realistic solution for someone who needs high
>JCK> reliability in that environment is multihoming, and there seems 
>JCK> to be no hope for multihoming of small-scale networks with IPv4.
>
>There is not much of a solution, today, for either IPv4 _or_ IPv6.
>

This is just plain silly .. there is a perfectly good solution for
multi-homing.. its called SCTP.. been around since Oct 2000 as
an RFC and the SS7 over IP folks are using it now. Yes it works for
both IPv4 and IPv6 and it will even setup an association (connection
for you TCPites) that includes BOTH IPv4 and IPv6.

It fails over and keeps on working when an interface goes down...

>
>However there are nearly 10 different proposals under consideration in
>the IETF, to deal with multihoming.  Few are restricted to IPv4.
>

I have always wondered why we are spinning our wheels in
this multi-homing group when the solution already exists.
Lode Coene has brought this up in the Multi-6 working
group but he seems to be ignored.

You don't need to do anything.. its already there.. just use it.

R

>
>In other words, when there is a serious solution to multihoming -- ie,
>being able to preserve a connection when using more than one IP
>Address -- it will likely work for IPv4.
>
>Most of these proposals are quite new.  No more than a year old and
>many less than 6 months.
>
>This does not speak well for anything happening immediately, of
>course.  However quite a number of the proposals do not require any
>significant infrastructure change.  This bodes well for rapid
>deployment, once they make it through the standards process.
>
>On the other hand, getting the IETF to produce standards track
>specifications out of this large pack of candidates could take another
>10 years...
>
>d/
>--
> Dave Crocker <dcrocker-at-brandenburg-dot-com>
> Brandenburg InternetWorking <www.brandenburg.com>
> Sunnyvale, CA  USA <tel:+1.408.246.8253>
>
>
>
>
>
>
>  
>


-- 
Randall R. Stewart
815-477-2127 (office)
815-342-5222 (cell phone)





From owner-ietf@ietf.org  Wed Jan 28 16:04:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28494
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 16:04:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlwoR-0004zb-Sh
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 16:01:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Alwj6-0003rV-W2
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 15:55:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27901
	for <ietf@ietf.org>; Wed, 28 Jan 2004 15:55:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alwj5-0002Ci-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:55:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlwiE-00025y-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:55:03 -0500
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlwhR-0001xt-00
	for ietf@ietf.org; Wed, 28 Jan 2004 15:54:13 -0500
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1.3)
  with ESMTP-TLS id 670529 for ietf@ietf.org; Wed, 28 Jan 2004 14:54:13 -0600
Message-ID: <40182174.8070707@ehsco.com>
Date: Wed, 28 Jan 2004 14:54:12 -0600
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: visa requirements (US citizens)
References: <200401281846.i0SIkCqK005031@jackson.cs.ucsb.edu>
In-Reply-To: <200401281846.i0SIkCqK005031@jackson.cs.ucsb.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On 1/28/2004 12:46 PM, Kevin C. Almeroth wrote:

> Seems to me to pretty clear that a visa is not needed.

These are the future possibilities:

 1) You got the visa, the guard on duty that day deems it unnecessary,
    and you curse the effort you spent to get it.

 2) You don't get the visa, the trainee on duty that day deems it is
    necessary, and you curse the ~30 hour round-trip flight, the
    money, and the effort you spent avoiding the visa fetch.

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



From owner-ietf@ietf.org  Wed Jan 28 16:12:24 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29222
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 16:12:24 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlwqN-0005hj-RT
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 16:03:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Alwps-0005Tf-55
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 16:02:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28375
	for <ietf@ietf.org>; Wed, 28 Jan 2004 16:02:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alwpq-00030q-00
	for ietf@ietf.org; Wed, 28 Jan 2004 16:02:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Alwoy-0002uP-00
	for ietf@ietf.org; Wed, 28 Jan 2004 16:02:01 -0500
Received: from stewart.chicago.il.us ([66.93.186.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlwoT-0002nV-00
	for IETF@ietf.org; Wed, 28 Jan 2004 16:01:29 -0500
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1])
	by stewart.chicago.il.us (8.12.8p1/8.12.8) with ESMTP id i0SL0pO6062519;
	Wed, 28 Jan 2004 15:00:51 -0600 (CST)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <40182303.7000300@stewart.chicago.il.us>
Date: Wed, 28 Jan 2004 15:00:51 -0600
From: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
CC: Dave Crocker <dhc@dcrocker.net>, IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com>
In-Reply-To: <224923613.1075293579@scan.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John C Klensin wrote:

> Dave,
>
> Just to pick a small nit or three...
>
> --On Wednesday, 28 January, 2004 07:36 +0900 Dave Crocker 
> <dhc@dcrocker.net> wrote:
>
>> John,
>>
>> JCK> but the only realistic solution for someone who needs high
>> JCK> reliability in that environment is multihoming, and there
>> seems  JCK> to be no hope for multihoming of small-scale
>> networks with IPv4.
>>
>> There is not much of a solution, today, for either IPv4 _or_
>> IPv6.
>>
>> However there are nearly 10 different proposals under
>> consideration in the IETF, to deal with multihoming.  Few are
>> restricted to IPv4.
>
>
> or to IPv6, which I assume is what you intended.
>
>> In other words, when there is a serious solution to
>> multihoming -- ie, being able to preserve a connection when
>> using more than one IP Address -- it will likely work for IPv4. 
>

Yes.. SCTP solves the problem for V4 and V6 (missed that bit last time).

>>
>
> Actually, that definition changes the problem into a much harder one, 
> and one that I think is unnecessary for the problem I was discussing 
> --unnecessary 99% of the time, if not always.  The reality is that 
> there is very little that we do on the Internet today that require 
> connection persistence when a link goes bad (or when "using more than 
> one IP address").  If a connection goes down, email retries, file 
> transfer connections are reconnected and the file (or the balance of 
> the file if checkpointing is in use) is transferred again, URLs are 
> refreshed, telnet and tunnel connections are recreated over other 
> paths, and so on.  It might be claimed that our applications, and our 
> human work habits, are designed to work at least moderately well when 
> running over a TCP that is vunerable to dropped physical connections. 

Yes.. it is true we have trained folks to hit the reload button... there 
is no
doubt about that :->

>
>
> Would it be good to have a TCP, or TCP-equivalent, that did not have 
> that vunerability, i.e., "could preserve a connection when using more 
> than one address"?  Sure, if the cost was not too high on normal 
> operations and we could actually get it.  But the goal has proven 
> elusive for the last 30-odd years 

John, please go look at RFC2960... it does this.. it is TCP equivalent.. 
and yes the
cost is not to high.

It is available in Linux 2.6, all of the BSD via KAME, Solaris (via 
package I am told), HP
and you can purchase it for many other platforms...

You can find information on this at:

http://www.sctp.org/implementations.html

It always seems to me like typical engineers... we solve the problem
one place and then rush out and try to solve it in yet another place... when
all we have to do is use what is already defined... I guess it is the 
ole NIH syndrom... :-<

> -- at least in the absence of running with full IP Mobility machinery 
> all of the time, which involves its own issues -- and, frankly, I'm 
> not holding my breath.
>
> By contrast, the problem that I find of greatest concern is the one in 
> which, if I'm communicating with you, and one or the other of us has 
> multiple connections available, and the connection path between us 
> (using one address each) disappears or goes bad, we can efficiently 
> switch to a different combination... even if all open TCP connections 
> drop and have to be reestablished in the interim. For _that_ problem, 
> we had a reasonably effective IPv4 solution (at least for those who 
> could afford it) for many years -- all one needed was multiple 
> interfaces on the relevant equipment (the hosts early on and the 
> router later) with, of course, a different connection and address on 
> each interface.  But, when we imposed CIDR, and the address-allocation 
> restrictions that went with it, it became impossible for someone to 
> get the PI space that is required to operate a LAN behind such an 
> arrangement (at least without having a NAT associated with the 
> relevant router) unless one was running a _very_ large network. 

The web server that I mention above has two addresses that are on the 
Big-I. And if
you connect via SCTP to the apache engine .. guess what.. you will use 
both of them..
and no I don't need a large block of lan allocation.. SCTP takes care of 
all of
this for me...

Will it work (multi-homed) behind a nat.. nope.. you reduce down to
singly homed .. but that is the price you pay for NAT..

I suppose one could define a inter-nat protocol so one could support 
multi-homing but
that is a swamp I would not care to walk down...

R

>
>
> Now, I'll stipulate this is a routing problem as much, or more, than 
> it is an address-availability problem.  And I'll also agree that there 
> appears to be little evidence that IPv6 is significantly more 
> routing-friendly than IPv4 and hence, that any real routing-based 
> solutions that help the one will help the other.  But,
>
>     (i) if any of the options turn out to require an
>     approach similar to the one that continue to work for
>     big enterprises with PI space in IPv4, then we are going
>     to need (lots) more address space.  And
>     
>     (ii) If any of the "multiple addresses per host" or
>     "tricks with prefixes" approaches are actually workable
>     and can be adequately defined and implemented at scale
>     --and there is some evidence that variations of them can
>     be, at least for leaf networks-- then they really do
>     depend on structure and facilities that appear to me to
>     are available in IPv6 and not in IPv4.
>
> So, for the problem I was referring to (but perhaps not for your much 
> more general formulation), I stand by my comment and analysis.
>
>> Most of these proposals are quite new.  No more than a year
>> old and many less than 6 months.
>>
>> This does not speak well for anything happening immediately, of
>> course.  However quite a number of the proposals do not
>> require any significant infrastructure change.  This bodes
>> well for rapid deployment, once they make it through the
>> standards process.
>>
>> On the other hand, getting the IETF to produce standards track
>> specifications out of this large pack of candidates could take
>> another 10 years...
>
>
> Yes.  And it may speak to the IETF's sense of priorities that the 
> efforts to which you refer are predominantly going into the much more 
> complex and long-term problem, rather than the one that is presumably 
> easier to solve and higher leverage.
>
>     john
>
>
>
>
>


-- 
Randall R. Stewart
815-477-2127 (office)
815-342-5222 (cell phone)





From owner-ietf@ietf.org  Wed Jan 28 16:13:56 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29351
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 16:13:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Alwx9-00075L-CF
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 16:10:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlwsN-0006Fj-GL
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 16:05:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28629
	for <ietf@ietf.org>; Wed, 28 Jan 2004 16:05:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlwsM-0003Rx-00
	for ietf@ietf.org; Wed, 28 Jan 2004 16:05:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlwrM-0003GB-00
	for ietf@ietf.org; Wed, 28 Jan 2004 16:04:28 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlwqT-000352-00
	for IETF@ietf.org; Wed, 28 Jan 2004 16:03:33 -0500
Received: from rw-18.mit.edu ([18.18.18.19] helo=jis.tzo.com)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AlwqT-0001ZN-9n
	for IETF@ietf.org; Wed, 28 Jan 2004 16:03:33 -0500
Received: (from jis@localhost)
	by jis.tzo.com (8.12.8p2/8.12.8) id i0SL36em002609;
	Wed, 28 Jan 2004 16:03:06 -0500
X-Authentication-Warning: jis.tzo.com: jis set sender to jis@mit.edu using -f
Date: Wed, 28 Jan 2004 16:03:06 -0500
From: "Jeffrey I. Schiller" <jis@mit.edu>
To: Pete Resnick <presnick@qualcomm.com>
Cc: John C Klensin <john-ietf@jck.com>, Dave Crocker <dhc@dcrocker.net>,
        IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <20040128160306.C1735@mit.edu>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <p06100901bc3db58a1619@[216.43.25.67]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <p06100901bc3db58a1619@[216.43.25.67]>; from presnick@qualcomm.com on Wed, Jan 28, 2004 at 01:09:35PM -0600
Spam-Alum-Prob: 0.000001
Spam-Alum-Time: 1.110531
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Applications have to deal with more then just losing a
connection. They have to deal with the loss of state that occurs when
you lose a connection. In general you really don't know which
transactions finished and which ones didn't, so you have to re-sync
your state in some way. 

I believe that no matter what we do to provide connection persistence,
connections will still break. Whether they break because of a total
loss of path for a long period of time, or more likely path is lost
for longer then the human timeout (i.e, the human starts typing ^C
[unix] or clicking CANCEL [gui] or whatever).

As long as connections break, applications will have to deal with
getting back to work when a connection can be made again. Given I
don't believe you will ever get "perfect" connection persistence (even
if you can do better then TCP does today) so therefore applications
will always have to have that re-syncing baggage.

		 -Jeff



From owner-ietf@ietf.org  Wed Jan 28 16:32:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00938
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 16:32:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Alx8l-00019m-Ge
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 16:22:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Alx8N-00014b-Qu
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 16:22:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00004
	for <ietf@ietf.org>; Wed, 28 Jan 2004 16:22:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alx8M-0005jK-00
	for ietf@ietf.org; Wed, 28 Jan 2004 16:22:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Alx7L-0005cI-00
	for ietf@ietf.org; Wed, 28 Jan 2004 16:21:00 -0500
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alx6o-0005Vz-00
	for IETF@ietf.org; Wed, 28 Jan 2004 16:20:26 -0500
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id 53398E0EAE; Wed, 28 Jan 2004 16:20:23 -0500 (EST)
Date: Wed, 28 Jan 2004 16:20:23 -0500
From: John Leslie <john@jlc.net>
To: John C Klensin <john-ietf@jck.com>
Cc: Dave Crocker <dhc@dcrocker.net>, IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <20040128212023.GB88924@verdi>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <224923613.1075293579@scan.jck.com>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

John C Klensin <john-ietf@jck.com> wrote:
> --On Wednesday, 28 January, 2004 07:36 +0900 Dave Crocker 
> <dhc@dcrocker.net> wrote:
> 
>> In other words, when there is a serious solution to
>> multihoming -- ie, being able to preserve a connection when
>> using more than one IP Address -- it will likely work for IPv4.
> 
> Actually, that definition changes the problem into a much harder 
> one,

   Preserving a connection when using more that one IP address is
not _necessarily_ a much harder problem -- especially if we
stipulate that tunneling is a legitimate middleware operation.

> The reality is that there is very little that we do on the Internet 
> today that require connection persistence when a link goes bad... 

   But we certainly _should_ be doing things that would greatly
benefit from connection persistence when a link goes bad.

> It might be claimed that our applications, and our human work
> habits, are designed to work at least moderately well when running
> over a TCP that is vunerable to dropped physical connections.

   Alternatively, one might claim our work habits have "evolved"
to work moderately well...

> Would it be good to have a TCP, or TCP-equivalent, that did not 
> have that vunerability, i.e., "could preserve a connection when 
> using more than one address"?  Sure, if the cost was not too 
> high on normal operations and we could actually get it.  But the 
> goal has proven elusive for the last 30-odd years...

   Might we do well to consider _why_ this is so?

> By contrast, the problem that I find of greatest concern is the 
> one in which, if I'm communicating with you, and one or the 
> other of us has multiple connections available, and the 
> connection path between us (using one address each) disappears 
> or goes bad, we can efficiently switch to a different 
> combination... even if all open TCP connections drop and have to 
> be reestablished in the interim.

   If I understand, John is looking for applications-level link
redundancy, which strikes me as unlikely to be easy to deploy.

> For _that_ problem, we had a reasonably effective IPv4 solution
> (at least for those who could afford it) for many years -- all
> one needed was multiple interfaces on the relevant equipment
> (the hosts early on and the router later) with, of course, a
> different connection and address on each interface. 

   Aren't we now talking what John said "changes the problem into
a much harder one" -- namely preserving connection when using
more than one IP address?

> But, when we imposed CIDR, and the address-allocation restrictions
> that went with it, it became impossible for someone to get the
> PI space that is required to operate a LAN behind such an
> arrangement (at least without having a NAT associated with the
> relevant router) unless one was running a _very_ large network.

   A /20 is _not_ "very large" -- just impractical to justify for
small-scale projects. (Thus, the allocation policies prevented
much of the small-scale experimentation which normally comes in
the early stages of design.)

> Now, I'll stipulate this is a routing problem as much, or more, 
> than it is an address-availability problem. 

   I'm not sure I agree. It's true that address-availability
policies were driven by routing problems. One _could_ consider
the route-filtering policies to be "a routing problem", but this
doesn't strike me as useful.

> And I'll also agree that there appears to be little evidence
> that IPv6 is significantly more routing-friendly than IPv4

   Agreed.

> and hence, that any real routing-based solutions that help the
> one will help the other.  But,
>   (i) if any of the options turn out to require an
> 	approach similar to the one that continue to work for
> 	big enterprises with PI space in IPv4, then we are going
> 	to need (lots) more address space.  And
>  (ii) If any of the "multiple addresses per host" or
> 	"tricks with prefixes" approaches are actually workable
> 	and can be adequately defined and implemented at scale
> 	--and there is some evidence that variations of them can
> 	be, at least for leaf networks-- then they really do
> 	depend on structure and facilities that appear to me to
> 	are available in IPv6 and not in IPv4.

   This gives the impression of overstating your case. Indeed, there
_will_ be solutions which require lots more IPv4 space; and there
will be solutions which depend on structure of IPv6. But these will
have to compete with other solutions which need neither.

> So, for the problem I was referring to (but perhaps not for your 
> much more general formulation), I stand by my comment and 
> analysis.

   I won't attempt to restate your analysis. But I think your
analysis is too narrow. You quite ignore the tricks which many
smaller ISPs can perform -- especially when they cooperate.

   We have a genuine problem in that we'd like something immediately
scalable -- and only larger ISPs can immediately reach large numbers
of users -- and larger ISPs impose arbitrary and capricious limits
on what their customers can do.

   Nonetheless, larger ISPs will have so many problems deploying
IPv6 that I have no confidence they _can_ make it native to their
operations within five years. OTOH, if we need to tunnel it over
IPv4, the situation really isn't different from any other tunneling
over IPv4...

>> Most of these proposals are quite new.  No more than a year
>> old and many less than 6 months.

   I'd love to investigate them...

>> This does not speak well for anything happening immediately, of
>> course.  However quite a number of the proposals do not
>> require any significant infrastructure change.  This bodes
>> well for rapid deployment, once they make it through the
>> standards process.

   I rather suspect many of them could be deployed _before_ they
make it through the standards process. ;^)
 
>> On the other hand, getting the IETF to produce standards track
>> specifications out of this large pack of candidates could take
>> another 10 years...

   Exactly!

> Yes.  And it may speak to the IETF's sense of priorities that 
> the efforts to which you refer are predominantly going into the 
> much more complex and long-term problem, rather than the one 
> that is presumably easier to solve and higher leverage.

   There is a great tendency to broaden the scope of a project as
you add more people to it; and a very rational tendency to extend
the time-frame being considered as the time-to-approach-consensus
appears to grow. Lamenting this won't change it.

   Where we go seriously wrong is requiring short-timeframe efforts
to coordinate their work with long-timeframe efforts.

--
John Leslie <john@jlc.net>



From owner-ietf@ietf.org  Wed Jan 28 17:27:32 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03341
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 17:27:32 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aly23-0006HB-R4
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 17:19:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Alxta-0005ik-CQ
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 17:10:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02623
	for <ietf@ietf.org>; Wed, 28 Jan 2004 17:10:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlxtY-0003DC-00
	for ietf@ietf.org; Wed, 28 Jan 2004 17:10:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Alxsb-00037q-00
	for ietf@ietf.org; Wed, 28 Jan 2004 17:09:50 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Alxri-00031p-00
	for IETF@ietf.org; Wed, 28 Jan 2004 17:08:54 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0SM9CKG003755;
	Wed, 28 Jan 2004 23:09:12 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <40182303.7000300@stewart.chicago.il.us>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Death of the Internet - details at 11
Date: Wed, 28 Jan 2004 23:08:43 +0100
To: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 28-jan-04, at 22:00, Randall R. Stewart (home) wrote:

>>> In other words, when there is a serious solution to
>>> multihoming -- ie, being able to preserve a connection when
>>> using more than one IP Address -- it will likely work for IPv4.

> Yes.. SCTP solves the problem for V4 and V6 (missed that bit last 
> time).

That remains to be seen. The list of issues that SCTP has or at least 
seems to have is long. To name a few:

- increased overhead compared to TCP
- requires significant changes from applications
- no backward compatibility of any kind
- source address selection problem isn't addressed fully, if at all

I can't be sure right now, but I also suspect SCTP could very well be 
vulnerable to some of the threats identified lately in the multi6 wg.




From owner-ietf@ietf.org  Wed Jan 28 17:27:32 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03356
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 17:27:32 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aly24-0006HM-69
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 17:19:36 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Alxva-0005tX-MK
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 17:12:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02674
	for <ietf@ietf.org>; Wed, 28 Jan 2004 17:12:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlxvZ-0003QP-00
	for ietf@ietf.org; Wed, 28 Jan 2004 17:12:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Alxuh-0003LF-00
	for ietf@ietf.org; Wed, 28 Jan 2004 17:12:00 -0500
Received: from mercury.lcs.mit.edu ([18.26.0.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlxuM-0003FN-00
	for IETF@ietf.org; Wed, 28 Jan 2004 17:11:38 -0500
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id 3E5A786AEC; Wed, 28 Jan 2004 17:11:07 -0500 (EST)
To: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Cc: jnc@mercury.lcs.mit.edu
Message-Id: <20040128221107.3E5A786AEC@mercury.lcs.mit.edu>
Date: Wed, 28 Jan 2004 17:11:07 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: John C Klensin <john-ietf@jck.com>

    > For _that_ problem, we had a reasonably effective IPv4 solution .. for
    > many years

We only has a "solution" as long as we had a small network. It was not a
solution which would scale. If that was a "solution", then IPv4 is a
"solution" to the need for address space.

    > when we imposed CIDR, and the address-allocation restrictions that went
    > with it, it became impossible for someone to get the PI space that is
    > required ...
    > I'll stipulate this is a routing problem as much, or more, than it is
    > an address-availability problem.

CIDR was always a single set of mechanisms (ubiquitous use of address masks)
which solved two completely separate problems: i) allocation of address space
in finer-grained chunks, to slow the rate of use, and ii) address table
bloat, leading to routing instability. The routing aspect was not an
afterthought or a later discovery, but an integral aspect from the very
beginning. Thinking of CIDR as a address space allocation mechanism is broken.


    > I'll also agree that there appears to be little evidence that IPv6 is
    > significantly more routing-friendly than IPv4

"little" -> "none".

    > any real routing-based solutions that help the one will help the other.

One of the painful pills the WG members have had to swallow is that there *is
no* "routing-based solution" to providing support for wide-spread
multi-homing (at least in anything like the current routing architecture,
i.e. packets which include only source and destintion addresses, as opposed
to a source route).

If you (or anyone else) doesn't understand why, please review the WG mailing
list archives before claiming otherwise.


    >   (i) if any of the options turn out to require an
    >   approach similar to the one that continue to work for
    >   big enterprises with PI space in IPv4, then we are going
    >   to need (lots) more address space.

Since the precursor is not going to happen, we don't need to worry about
the hypothetical consequence.


    > there is very little that we do on the Internet today that require
    > connection persistence when a link goes bad

I made this exact point some time back, and asked if this was therefore
really a requirement, and was told that it was. I remained extremely dubious,
but had no interest (for obvious reasons) in correcting it if wrong.

I will note in passing that if this capability were not really needed, one
might ask why SCTP added it.

    > it may speak to the IETF's sense of priorities that the efforts to
    > which you refer are predominantly going into the much more complex and
    > long-term problem, rather than the one that is presumably easier to
    > solve and higher leverage.

The general approach (of multiple addresses) is the only realistic one. Any
analysis of whether the additional requirement (for connection survivability)
has a reasonable cost/benefit ratio needs to start with this ground truth.

It may be that the differential complexity to go from i) multiple addresses,
and established connections cannot switch, to ii) multiple addresses, and
established connections can switch, is minimal. I can't say; I haven't
bothered to look at the (to me, boring) engineering details.

	Noel



From owner-ietf@ietf.org  Wed Jan 28 17:28:19 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03407
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 17:28:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Aly6t-00074H-Fe
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 17:24:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Aly6B-0006wH-7d
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 17:23:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03169
	for <ietf@ietf.org>; Wed, 28 Jan 2004 17:23:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aly69-0004Xx-00
	for ietf@ietf.org; Wed, 28 Jan 2004 17:23:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aly5I-0004Sw-00
	for ietf@ietf.org; Wed, 28 Jan 2004 17:22:57 -0500
Received: from stork.mail.pas.earthlink.net ([207.217.120.188])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aly4O-0004NL-00
	for ietf@ietf.org; Wed, 28 Jan 2004 17:22:01 -0500
Received: from [38.119.96.105] (helo=[192.168.0.2])
	by stork.mail.pas.earthlink.net with asmtp (Exim 3.33 #1)
	id 1Aly4N-0000rX-00
	for ietf@ietf.org; Wed, 28 Jan 2004 14:21:59 -0800
Date: Wed, 28 Jan 2004 17:20:24 -0500
From: Gene Gaines <gene.gaines@gainesgroup.com>
Organization: Gaines Group
X-Priority: 3 (Normal)
Message-ID: <1266011254.20040128172024@gainesgroup.com>
To: ietf@ietf.org
Subject: Re: visa requirements (US citizens)
In-Reply-To: <40182174.8070707@ehsco.com>
References: <200401281846.i0SIkCqK005031@jackson.cs.ucsb.edu>
 <40182174.8070707@ehsco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
X-ELNK-Trace: e892362a6fa8b5d372cc1e1b0924a179239a348a220c2609e14407e0b0f37df63f7993d9264c2711350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Visas for travel to Seoul, Korea IETF meeting.

Perhaps I can settle this.

A U.S. citizen does NOT need a visa to visit Korea for a meeting
by a non-profit group such as the Internet Engineering Task Force.
I just confirmed this with the head of the visa section in the
Korean Consulate in Washington DC.

But don't take my word for it. If anyone requests, I will be glad
to get an official letter faxed from the Korean Consulate-General.
I would carry that letter with your current U.S. passport.

More precise statement:

=A0 - U.S. citizens traveling to Korean to attend the IETF meeting
=A0=A0=A0 do not need a visa, as they are traveling to attend a
=A0=A0=A0 non-profit conference.=A0 They can stay in Korea up to 30 days
=A0=A0=A0 for such purposes and for tourism.

  - If you travel to Korea for business purposes, such as meeting
    customers or other business purposes, then a visa is required.

  - There also is confusion about government employees.  U.S.
    government employees going to Korea just for tourism or a non-
    profit conference such as IETF do not need a visa because they
    are going a private citizens.  However, government employees
    going to Korea for official purposes do need an official visa.

I won't request an official letter unless someone asks me to do
so. I could post on a neutral web site or email to you.

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

On Wednesday, January 28, 2004, 3:54:12 PM, Eric wrote:


> On 1/28/2004 12:46 PM, Kevin C. Almeroth wrote:

>> Seems to me to pretty clear that a visa is not needed.

> These are the future possibilities:

>  1) You got the visa, the guard on duty that day deems it unnecessary,
>     and you curse the effort you spent to get it.

>  2) You don't get the visa, the trainee on duty that day deems it is
>     necessary, and you curse the ~30 hour round-trip flight, the
>     money, and the effort you spent avoiding the visa fetch.



--=20




From owner-ietf@ietf.org  Wed Jan 28 17:51:50 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04859
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 17:51:50 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlyIP-0001Gb-ES
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 17:36:29 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlyCZ-0000AG-SD
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 17:30:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03599
	for <ietf@ietf.org>; Wed, 28 Jan 2004 17:30:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlyCY-0005LA-00
	for ietf@ietf.org; Wed, 28 Jan 2004 17:30:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlyBO-000577-00
	for ietf@ietf.org; Wed, 28 Jan 2004 17:29:15 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlyAM-0004xV-00
	for IETF@ietf.org; Wed, 28 Jan 2004 17:28:10 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0SMScKG003984;
	Wed, 28 Jan 2004 23:28:38 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <224923613.1075293579@scan.jck.com>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <404A5260-51E1-11D8-98F9-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Death of the Internet - details at 11
Date: Wed, 28 Jan 2004 23:28:09 +0100
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 28-jan-04, at 18:39, John C Klensin wrote:

> The reality is that there is very little that we do on the Internet 
> today that require connection persistence when a link goes bad (or 
> when "using more than one IP address").  If a connection goes down, 
> email retries, file transfer connections are reconnected and the file 
> (or the balance of the file if checkpointing is in use) is transferred 
> again, URLs are refreshed, telnet and tunnel connections are recreated 
> over other paths, and so on.  It might be claimed that our 
> applications, and our human work habits, are designed to work at least 
> moderately well when running over a TCP that is vunerable to dropped 
> physical connections.

This assumes that when address A fails, address B keeps working. This 
is only true when routing is symmetric or the multiaddressed endpoint 
is able to detect the failure. And applications need to retry with 
other addresses. They typically don't do this very well if at all in 
IPv4, and only moderately well in IPv6.

> Would it be good to have a TCP, or TCP-equivalent, that did not have 
> that vunerability, i.e., "could preserve a connection when using more 
> than one address"?  Sure, if the cost was not too high on normal 
> operations and we could actually get it.

There are several proof of concept multiaddress TCPs.

[sorry for the long quote:]

> By contrast, the problem that I find of greatest concern is the one in 
> which, if I'm communicating with you, and one or the other of us has 
> multiple connections available, and the connection path between us 
> (using one address each) disappears or goes bad, we can efficiently 
> switch to a different combination... even if all open TCP connections 
> drop and have to be reestablished in the interim. For _that_ problem, 
> we had a reasonably effective IPv4 solution (at least for those who 
> could afford it) for many years -- all one needed was multiple 
> interfaces on the relevant equipment (the hosts early on and the 
> router later) with, of course, a different connection and address on 
> each interface.  But, when we imposed CIDR, and the address-allocation 
> restrictions that went with it, it became impossible for someone to 
> get the PI space that is required to operate a LAN behind such an 
> arrangement (at least without having a NAT associated with the 
> relevant router) unless one was running a _very_ large network.

??? Why would you need PI space to be able to give hosts more than one 
address and use those successfully?

And if you had the PI space, why would you bother? Contrary to some 
reports multihoming using independent address space and links to more 
than one ISP works fairly well: failover times are almost always 
shorter than TCP or user timeouts.

> 	(i) if any of the options turn out to require an
> 	approach similar to the one that continue to work for
> 	big enterprises with PI space in IPv4, then we are going
> 	to need (lots) more address space.  And

More than what?

>> However quite a number of the proposals do not
>> require any significant infrastructure change.  This bodes
>> well for rapid deployment, once they make it through the
>> standards process.

>> On the other hand, getting the IETF to produce standards track
>> specifications out of this large pack of candidates could take
>> another 10 years...

Looking at the rate at which the IETF is coming up with ways to 
automatically determine IPv6 DNS resolver addresses I can hardly 
disagree.

But most of the multi6 proposals have large parts in common with other 
proposals. It seems to me that all we have to do is combine the best 
parts. How hard can that be. (Famous last words.)

> Yes.  And it may speak to the IETF's sense of priorities that the 
> efforts to which you refer are predominantly going into the much more 
> complex and long-term problem, rather than the one that is presumably 
> easier to solve and higher leverage.

Which would be?




From owner-ietf@ietf.org  Wed Jan 28 17:54:15 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04969
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 17:54:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AlyWU-0002WG-O5
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 17:51:02 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AlyVM-0002Og-S4
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 17:49:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04803
	for <ietf@ietf.org>; Wed, 28 Jan 2004 17:49:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlyVK-0007Y9-00
	for ietf@ietf.org; Wed, 28 Jan 2004 17:49:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlyUV-0007TL-00
	for ietf@ietf.org; Wed, 28 Jan 2004 17:49:00 -0500
Received: from stewart.chicago.il.us ([66.93.186.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlyTq-0007Ks-00
	for IETF@ietf.org; Wed, 28 Jan 2004 17:48:18 -0500
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1])
	by stewart.chicago.il.us (8.12.8p1/8.12.8) with ESMTP id i0SMliO6063232;
	Wed, 28 Jan 2004 16:47:46 -0600 (CST)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <40183C10.10401@stewart.chicago.il.us>
Date: Wed, 28 Jan 2004 16:47:44 -0600
From: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
CC: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
Subject: Re: Death of the Internet - details at 11
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us> <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com>
In-Reply-To: <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,BE_AMAZED autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum wrote:

> On 28-jan-04, at 22:00, Randall R. Stewart (home) wrote:
>
>>>> In other words, when there is a serious solution to
>>>> multihoming -- ie, being able to preserve a connection when
>>>> using more than one IP Address -- it will likely work for IPv4.
>>>
>
>> Yes.. SCTP solves the problem for V4 and V6 (missed that bit last time). 
>
Let me go through these one by one...

>
> That remains to be seen. The list of issues that SCTP has or at least 
> seems to have is long. To name a few:
>
> - increased overhead compared to TCP 

Ok lets see. SCTP takes on average 4 more bytes per data packet then
TCP. However, if the TCP implementation enables timestamps then
that is not true and TCP takes more overhead by about 4 bytes...

Unless you are discussing another type of overhead...

>
> - requires significant changes from applications 


Ok let see.. for Mozilla we converted two lines of code

sd = socket(AF_INET6, SOCK_STREAM, IPPROTO_TCP);
became --------------> sd = socket(AF_INET, SOCK_STREAM, IPPROTO_SCTP);

and

setsockopt(sd, IPPROTO_TCP, TCP_NODELAY, &on_off, sizeof(on_off));
became ---------------> setsockopt(sd, IPPROTO_SCTP, SCTP_NODELAY, 
&on_off, sizeof(on_off));

Now to take advantage of the stream feature you would need to do
more.. but for pure multi-homing one or two lines of change does
not seem that big of deal to me ...

>
> - no backward compatibility of any kind 

I am not sure what you mean by backward compatable? You definetly
can't have TCP and SCTP talk.. they are after all different protocols...
But if an application needs the redundancy move to it.. its there today
with about 2 lines of coding change...

>
> - source address selection problem isn't addressed fully, if at all 

I don't think I understand this issue either.. We have fully
addressed source address selection in the KAME implementation. It
is not a difficult problem.. it does require some code.. but any good
implementation must address this issue... And since the site scope
went away in IPv6 (at least for now) its easier to do then it was).

>
>
> I can't be sure right now, but I also suspect SCTP could very well be 
> vulnerable to some of the threats identified lately in the multi6 wg. 

I would have to look at your threats... if you add the dynamic address 
feature.. sure
thats why the document has not progressed.. but that will change when the
Purpose Built Keys instantation in SCTP happens.. hopefully soon.. just 
another
draft to write :-D

I think you may want to have a little closer look at SCTP.. you might
want to get the KAME BSD implementation and play with it for
a bit.. I think you would be amazed at how simple it is to
convert an application and you end up with multi-homing for
free with those 2 lines of code :->

R

>
>
>
>


-- 
Randall R. Stewart
815-477-2127 (office)
815-342-5222 (cell phone)





From owner-ietf@ietf.org  Wed Jan 28 21:30:30 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12468
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 21:30:30 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Am1lA-0001CQ-VE
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 21:18:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Am1kq-00018H-JZ
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 21:18:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12075
	for <ietf@ietf.org>; Wed, 28 Jan 2004 21:17:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am1ki-0003ja-00
	for ietf@ietf.org; Wed, 28 Jan 2004 21:17:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Am1jo-0003eG-00
	for ietf@ietf.org; Wed, 28 Jan 2004 21:17:00 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am1jV-0003Ys-00
	for ietf@ietf.org; Wed, 28 Jan 2004 21:16:41 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 1ACAE61C11; Thu, 29 Jan 2004 03:16:10 +0100 (CET)
Date: Wed, 28 Jan 2004 17:25:15 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Franck Martin <franck@sopac.org>, ietf@ietf.org
Subject: Re: Wiki RFC
Message-ID: <1422526635.1075310715@localhost>
In-Reply-To: <1075250978.2820.55.camel@franck-lxnb.sopac.org.fj>
References: <1075250978.2820.55.camel@franck-lxnb.sopac.org.fj>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 28. januar 2004 12:49 +1200 Franck Martin <franck@sopac.org> wrote:

> I was just wondering if there has been any work to standardise the Wiki
> syntax/system into an RFC?

AFAIK, no.
Do you know of any effort to make stable documentation for the WIKI syntax 
& functionality, or is it just "use the Source, Luke"?






From owner-ietf@ietf.org  Wed Jan 28 21:30:30 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12479
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 21:30:30 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Am1lB-0001CW-AM
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 21:18:25 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Am1kq-00018J-MP
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 21:18:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12089
	for <ietf@ietf.org>; Wed, 28 Jan 2004 21:17:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am1kk-0003jr-00
	for ietf@ietf.org; Wed, 28 Jan 2004 21:17:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Am1jq-0003ef-00
	for ietf@ietf.org; Wed, 28 Jan 2004 21:17:03 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am1jZ-0003Yu-00
	for ietf@ietf.org; Wed, 28 Jan 2004 21:16:45 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 9407D61C23
	for <ietf@ietf.org>; Thu, 29 Jan 2004 03:16:14 +0100 (CET)
Date: Wed, 28 Jan 2004 18:15:48 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: SUMMARY: Processing of expired Internet-Drafts
Message-ID: <1425560006.1075313748@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Just to make one thing clear....

The published processing of expired Internet-Drafts was intended to be a 
reasonably small change to existing procedures.

That's not to say that the procedures are going to live forever. But we 
don't want to make bigger changes than we have to until we're ready to 
overhaul the whole system (and know why).

Anyway, back to the summary..... I've tried to represent what people said, 
and group them into a few topics. Conclusions (mine) at the end.

* Use of tombstone files.
Current procedure is to create tombstone files whenever an I-D is no longer 
valid (withdrawn, expired, published as RFC).
Arguments raised are that a file of "old names" is better (Fred, Ted, Eric 
F) or a separate directory (Carl) or a search system (Alexey).

* Tombstones and expiry.
Current procedure is to make them live forever.
Arguments raised are that 700 IDs per year produce a lot of tombstones 
(Fred, Ken), and that we could expire them after 6 months (Zefram, Fred) or 
2 years (David Morris).
My argument is that we've lived with the present system since 2001, and 
produced only around 2500 tombstones; it's not worth bothering to change 
that until we change the system more dramatically.

* Tombstones and version numbers:
Current procedure is to expire name-nn, create tombstone name-nn+1, and if 
it is resurrected, to resurrect as name-nn+1.
(Until some time ago, the tombstone was name-nn)
Arguments raised are that 2 files with the same name and different content 
is a Bad Thing, and that we should increment the number once again for a 
new version (Fred, Zefram, Jim Galvin), or use another extension for 
tombstones (David Morris).
One problem seen is searching for name+1 will now give a hit (Carl), and 
that maintaining mirrors is harder (Fred).
The problem of mirroring can be cleanly solved with rsync (Thomas), or 
comparing file sizes (someone else).

* Status of drafts:
Current procedure is to let the version-numbered files, including 
tombstones, serve as status information, as well as 1id-index listing the 
current drafts.
Argument is that a name without the version number would be more easy to 
find (Iljitch); this is easy to make when you need it (Scott Brim), and 
exists at www.watersprings.org (among other places (Tim Chown) and 
www.potaroo.net (Geoff)

Conclusions, all mine:

- Documenting current procedures is good.
- We won't expire tombstones. They're not a big enough problem yet.
- We'll think about naming tombstones something else than the exact draft 
name (for instance draft-whatever-version-nn-expired.txt???)
- We'll note the issue of referencing names without the version number as 
input for thinking about overhauling the whole I-D system. But that won't 
happen very quickly - it "mostly works".

Seems to make sense?

                        Harald





From owner-ietf@ietf.org  Wed Jan 28 22:22:33 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14898
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 22:22:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Am2dM-0005SF-PB
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 22:14:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Am2bH-0005Iu-1V
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 22:12:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14027
	for <ietf@ietf.org>; Wed, 28 Jan 2004 22:12:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am2bF-0001GH-00
	for ietf@ietf.org; Wed, 28 Jan 2004 22:12:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Am2aJ-000193-00
	for ietf@ietf.org; Wed, 28 Jan 2004 22:11:16 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am2Zf-000125-00
	for ietf@ietf.org; Wed, 28 Jan 2004 22:10:38 -0500
Received: by franck-lxnb.sopac.org.fj (Postfix, from userid 501)
	id 0FF0E4B6A2; Wed, 28 Jan 2004 22:10:03 -0500 (EST)
Subject: Re: Wiki RFC
From: Franck Martin <franck@sopac.org>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org, mose@mose.fr
In-Reply-To: <1422526635.1075310715@localhost>
References: <1075250978.2820.55.camel@franck-lxnb.sopac.org.fj>
	 <1422526635.1075310715@localhost>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-LFIefH8HKfmxWNpK/JfR"
Organization: SOPAC
Message-Id: <1075345802.3095.24.camel@franck-lxnb.sopac.org.fj>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4-1.1mdk 
Date: 29 Jan 2004 15:10:02 +1200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_FONTCOLOR_UNSAFE,
	HTML_MESSAGE autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-LFIefH8HKfmxWNpK/JfR
Content-Type: multipart/alternative; boundary="=-iKVo/dWyshafSPmyCohe"


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

Well,

As part of the www.tikiwiki.org project, I have been talking about
writing the wiki syntax into an RFC like documentation. I think the wiki
syntax in this project is in documentation format but not looking like
an RFC.=20

I think we could quickly whack an RFC on wiki, and ask people to
contribute to it... When it is stabilised we could submit to IETF.

The advantage, is that there is already an implementation, the other
advantage would be to bring some standardisation in all the wiki.

I think since the creation of the Web, there has not been such a
revolution as wiki. Imagine an e-mail message wiki formated. No need to
use HTML anymore in a multi part message. The text can be read as is, or
wiki interpreted for better display...

Cheers

On Thu, 2004-01-29 at 13:25, Harald Tveit Alvestrand wrote:

> --On 28. januar 2004 12:49 +1200 Franck Martin <franck@sopac.org> wrote:
>=20
> > I was just wondering if there has been any work to standardise the Wiki
> > syntax/system into an RFC?
>=20
> AFAIK, no.
> Do you know of any effort to make stable documentation for the WIKI synta=
x=20
> & functionality, or is it just "use the Source, Luke"?

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

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
  <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/1.1.10">
</HEAD>
<BODY>
Well,<BR>
<BR>
As part of the <A HREF=3D"http://www.tikiwiki.org">www.tikiwiki.org</A> pro=
ject, I have been talking about writing the wiki syntax into an RFC like do=
cumentation. I think the wiki syntax in this project is in documentation fo=
rmat but not looking like an RFC. <BR>
<BR>
I think we could quickly whack an RFC on wiki, and ask people to contribute=
 to it... When it is stabilised we could submit to IETF.<BR>
<BR>
The advantage, is that there is already an implementation, the other advant=
age would be to bring some standardisation in all the wiki.<BR>
<BR>
I think since the creation of the Web, there has not been such a revolution=
 as wiki. Imagine an e-mail message wiki formated. No need to use HTML anym=
ore in a multi part message. The text can be read as is, or wiki interprete=
d for better display...<BR>
<BR>
Cheers<BR>
<BR>
On Thu, 2004-01-29 at 13:25, Harald Tveit Alvestrand wrote:
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>--On 28. januar 2004 12:49 +1200=
 Franck Martin &lt;franck@sopac.org&gt; wrote:

&gt; I was just wondering if there has been any work to standardise the Wik=
i
&gt; syntax/system into an RFC?

AFAIK, no.
Do you know of any effort to make stable documentation for the WIKI syntax=20
&amp; functionality, or is it just &quot;use the Source, Luke&quot;?</I></F=
ONT></PRE>
</BLOCKQUOTE>
<PRE><TABLE CELLSPACING=3D"0" CELLPADDING=3D"0" WIDTH=3D"100%">
<TR>
<TD>
----<BR>
Franck Martin<BR>
<A HREF=3D"mailto:franck@sopac.org">franck@sopac.org</A><BR>
SOPAC, Fiji<BR>
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9&nbsp; D9C6 BE79 9E60 81D9 =
1320<BR>
&quot;Toute connaissance est une reponse a une question&quot; G.Bachelard
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-iKVo/dWyshafSPmyCohe--

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

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

iD8DBQBAGHmKvnmeYIHZEyARAs0SAJsG1sovsFFzO3SRFH4R/sYwE1NgqACfXaVi
cFEzXmEnCBUsl4xMcHdzNjo=
=79qM
-----END PGP SIGNATURE-----

--=-LFIefH8HKfmxWNpK/JfR--



From owner-ietf@ietf.org  Wed Jan 28 22:54:20 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15770
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 22:54:20 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Am38K-0008EI-AC
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 22:46:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Am37t-0008AI-SF
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 22:45:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15605
	for <ietf@ietf.org>; Wed, 28 Jan 2004 22:45:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am37r-0005CB-00
	for ietf@ietf.org; Wed, 28 Jan 2004 22:45:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Am36u-00056A-00
	for ietf@ietf.org; Wed, 28 Jan 2004 22:44:56 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am35z-0004wB-00
	for ietf@ietf.org; Wed, 28 Jan 2004 22:43:59 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 6831761A93; Thu, 29 Jan 2004 04:43:28 +0100 (CET)
Date: Wed, 28 Jan 2004 19:40:03 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Franck Martin <franck@sopac.org>
Cc: ietf@ietf.org, mose@mose.fr
Subject: Re: Wiki RFC
Message-ID: <1430614775.1075318803@localhost>
In-Reply-To: <1075345802.3095.24.camel@franck-lxnb.sopac.org.fj>
References: <1075250978.2820.55.camel@franck-lxnb.sopac.org.fj>	
 <1422526635.1075310715@localhost>
 <1075345802.3095.24.camel@franck-lxnb.sopac.org.fj>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

please do - it would follow in the glorious tradition of publishing RFCs 
for such useful things as the OGG file format, the Vorbis codec and the 
zlib compression formats.....

--On 29. januar 2004 15:10 +1200 Franck Martin <franck@sopac.org> wrote:

> Well,
>
> As part of the www.tikiwiki.org project, I have been talking about
> writing the wiki syntax into an RFC like documentation. I think the wiki
> syntax in this project is in documentation format but not looking like an
> RFC.
>
> I think we could quickly whack an RFC on wiki, and ask people to
> contribute to it... When it is stabilised we could submit to IETF.
>
> The advantage, is that there is already an implementation, the other
> advantage would be to bring some standardisation in all the wiki.
>
> I think since the creation of the Web, there has not been such a
> revolution as wiki. Imagine an e-mail message wiki formated. No need to
> use HTML anymore in a multi part message. The text can be read as is, or
> wiki interpreted for better display...







From owner-ietf@ietf.org  Wed Jan 28 23:56:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18351
	for <ietf-web-archive@odin.ietf.org>; Wed, 28 Jan 2004 23:56:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Am46K-000465-2k
	for ietf-list@asgard.ietf.org; Wed, 28 Jan 2004 23:48:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Am462-00042G-R1
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 23:48:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18177
	for <ietf@ietf.org>; Wed, 28 Jan 2004 23:48:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am460-00046V-00
	for ietf@ietf.org; Wed, 28 Jan 2004 23:48:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Am452-00040S-00
	for ietf@ietf.org; Wed, 28 Jan 2004 23:47:05 -0500
Received: from cobalt.sopac.org.fj ([202.62.0.150] helo=franck-lxnb.sopac.org.fj)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am449-0003up-00
	for ietf@ietf.org; Wed, 28 Jan 2004 23:46:10 -0500
Received: by franck-lxnb.sopac.org.fj (Postfix, from userid 501)
	id 469AC4B6A2; Wed, 28 Jan 2004 23:46:08 -0500 (EST)
Subject: Re: Wiki RFC
From: Franck Martin <franck@sopac.org>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org, mose@mose.fr
In-Reply-To: <1430614775.1075318803@localhost>
References: <1075250978.2820.55.camel@franck-lxnb.sopac.org.fj>
	 <1422526635.1075310715@localhost>
	 <1075345802.3095.24.camel@franck-lxnb.sopac.org.fj>
	 <1430614775.1075318803@localhost>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-9vlIoptU/WyIY9sYc88v"
Organization: SOPAC
Message-Id: <1075351567.2780.22.camel@franck-lxnb.sopac.org.fj>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4-1.1mdk 
Date: 29 Jan 2004 16:46:08 +1200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_20_30,
	HTML_FONTCOLOR_UNSAFE,HTML_MESSAGE autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-9vlIoptU/WyIY9sYc88v
Content-Type: multipart/alternative; boundary="=-EaMPvurLVgX1LT+f6HC4"


--=-EaMPvurLVgX1LT+f6HC4
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

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

Also some background
http://tikiwiki.org/tiki-index.php?page=3DTextWiki

and the syntax to be put in RFC format:
http://doc.tikiwiki.org/tiki-index.php?page=3DWiki+Text+Formatting

Anybody wanting to help is most welcome...

On Thu, 2004-01-29 at 15:40, Harald Tveit Alvestrand wrote:

> please do - it would follow in the glorious tradition of publishing RFCs=20
> for such useful things as the OGG file format, the Vorbis codec and the=20
> zlib compression formats.....
>=20
> --On 29. januar 2004 15:10 +1200 Franck Martin <franck@sopac.org> wrote:
>=20
> > Well,
> >
> > As part of the www.tikiwiki.org project, I have been talking about
> > writing the wiki syntax into an RFC like documentation. I think the wik=
i
> > syntax in this project is in documentation format but not looking like =
an
> > RFC.
> >
> > I think we could quickly whack an RFC on wiki, and ask people to
> > contribute to it... When it is stabilised we could submit to IETF.
> >
> > The advantage, is that there is already an implementation, the other
> > advantage would be to bring some standardisation in all the wiki.
> >
> > I think since the creation of the Web, there has not been such a
> > revolution as wiki. Imagine an e-mail message wiki formated. No need to
> > use HTML anymore in a multi part message. The text can be read as is, o=
r
> > wiki interpreted for better display...
>=20

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

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
  <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/1.1.10">
</HEAD>
<BODY>
The page is on:<BR>
<A HREF=3D"http://tikiwiki.org/tiki-index.php?page=3DRFCWiki">http://tikiwi=
ki.org/tiki-index.php?page=3DRFCWiki</A><BR>
<BR>
Also some background<BR>
<A HREF=3D"http://tikiwiki.org/tiki-index.php?page=3DRFCWiki">http://tikiwi=
ki.org/tiki-index.php?page=3DTextWiki</A><BR>
<BR>
and the syntax to be put in RFC format:<BR>
<A HREF=3D"http://doc.tikiwiki.org/tiki-index.php?page=3DWiki+Text+Formatti=
ng">http://doc.tikiwiki.org/tiki-index.php?page=3DWiki+Text+Formatting</A><=
BR>
<BR>
Anybody wanting to help is most welcome...<BR>
<BR>
On Thu, 2004-01-29 at 15:40, Harald Tveit Alvestrand wrote:
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>please do - it would follow in t=
he glorious tradition of publishing RFCs=20
for such useful things as the OGG file format, the Vorbis codec and the=20
zlib compression formats.....

--On 29. januar 2004 15:10 +1200 Franck Martin &lt;franck@sopac.org&gt; wro=
te:

&gt; Well,
&gt;
&gt; As part of the </FONT><A HREF=3D"http://www.tikiwiki.org"><FONT SIZE=
=3D"3">www.tikiwiki.org</FONT></A><FONT COLOR=3D"#737373" SIZE=3D"3"> proje=
ct, I have been talking about
&gt; writing the wiki syntax into an RFC like documentation. I think the wi=
ki
&gt; syntax in this project is in documentation format but not looking like=
 an
&gt; RFC.
&gt;
&gt; I think we could quickly whack an RFC on wiki, and ask people to
&gt; contribute to it... When it is stabilised we could submit to IETF.
&gt;
&gt; The advantage, is that there is already an implementation, the other
&gt; advantage would be to bring some standardisation in all the wiki.
&gt;
&gt; I think since the creation of the Web, there has not been such a
&gt; revolution as wiki. Imagine an e-mail message wiki formated. No need t=
o
&gt; use HTML anymore in a multi part message. The text can be read as is, =
or
&gt; wiki interpreted for better display...
</I></FONT></PRE>
</BLOCKQUOTE>
<PRE><TABLE CELLSPACING=3D"0" CELLPADDING=3D"0" WIDTH=3D"100%">
<TR>
<TD>
----<BR>
Franck Martin<BR>
<A HREF=3D"mailto:franck@sopac.org">franck@sopac.org</A><BR>
SOPAC, Fiji<BR>
GPG Key fingerprint =3D 44A4 8AE4 392A 3B92 FDF9&nbsp; D9C6 BE79 9E60 81D9 =
1320<BR>
&quot;Toute connaissance est une reponse a une question&quot; G.Bachelard
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-EaMPvurLVgX1LT+f6HC4--

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

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

iD8DBQBAGJAPvnmeYIHZEyARAuCKAJ0SBcsKtttSpMBcKUiXEJdi7B2Y1QCcD7gA
PtmoqRcWdI+upnHflYKsxqg=
=O7JP
-----END PGP SIGNATURE-----

--=-9vlIoptU/WyIY9sYc88v--



From owner-ietf@ietf.org  Thu Jan 29 07:15:31 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14485
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 07:15:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmAvA-000652-Fy
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 07:05:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmAv4-00061G-BU
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 07:05:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14247
	for <ietf@ietf.org>; Thu, 29 Jan 2004 07:05:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmAv1-0002TP-00
	for ietf@ietf.org; Thu, 29 Jan 2004 07:05:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmAu6-0002OT-00
	for ietf@ietf.org; Thu, 29 Jan 2004 07:04:15 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmAtH-0002JM-00
	for IETF@ietf.org; Thu, 29 Jan 2004 07:03:23 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0TC3fKH014866;
	Thu, 29 Jan 2004 13:03:46 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <40183C10.10401@stewart.chicago.il.us>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us> <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <654669B6-524E-11D8-98F9-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Death of the Internet - details at 11
Date: Thu, 29 Jan 2004 12:29:26 +0100
To: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 28-jan-04, at 23:47, Randall R. Stewart (home) wrote:

>> - increased overhead compared to TCP

> Ok lets see. SCTP takes on average 4 more bytes per data packet then
> TCP. However, if the TCP implementation enables timestamps then
> that is not true and TCP takes more overhead by about 4 bytes...

Hm... timestamp option takes 12 bytes, what gives?

> Unless you are discussing another type of overhead...

Apart from the extra bytes (which isn't the main issue) there are the 
CRC32 checksum, which is considerably more expensive to compute than 
the TCP/UDP/IP checksum and the fact that SCTP has much more 
complexity. I would be surprised if the "fast path" for SCTP wouldn't 
turn out to be more expensive than that of TCP, especially without 
disabling all the features that make SCTP more interesting than TCP in 
the first place. And of course those heartbeats I love to hate. (Which 
don't provide any benefits when there are only two paths anyway.)

>> - requires significant changes from applications

> Ok let see.. for Mozilla we converted two lines of code

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

> sd = socket(AF_INET6, SOCK_STREAM, IPPROTO_TCP);
> became --------------> sd = socket(AF_INET, SOCK_STREAM, IPPROTO_SCTP);

> and

> setsockopt(sd, IPPROTO_TCP, TCP_NODELAY, &on_off, sizeof(on_off));
> became ---------------> setsockopt(sd, IPPROTO_SCTP, SCTP_NODELAY, 
> &on_off, sizeof(on_off));

So is this enough to gain all multihoming benefits? Even if all other 
magic is hidden inside the protocol, the application must at least try 
all possible destination addresses. (But this is true for several other 
multi6 proposals as well.)

> Now to take advantage of the stream feature you would need to do
> more.. but for pure multi-homing one or two lines of change does
> not seem that big of deal to me ...

Doing WWW-style HTTP (lots of concurrent sessions) with SCTP would be 
nonsense, this is where the feature where multiple streams are 
multiplexed over a single session would be extremely useful.

>> - no backward compatibility of any kind

> I am not sure what you mean by backward compatable? You definetly
> can't have TCP and SCTP talk.. they are after all different 
> protocols...
> But if an application needs the redundancy move to it.. its there today
> with about 2 lines of coding change...

But then you'll have to run services on both TCP and SCTP pretty much 
forever. Not a good thing.

>> - source address selection problem isn't addressed fully, if at all

> I don't think I understand this issue either..

Host has addresses a and b from ISPs A and B. Host sends a packet to 
address x which is routed over ISP A. However, the host selects source 
address b which is filtered by A, so no connectivity. For extra credit: 
solve same when this happens in the middle of a session, and in cases 
where connectivity consists of two one way paths. (a -> x and y -> b 
work, but not x -> a or b -> y)

> We have fully
> addressed source address selection in the KAME implementation.

In what way?




From owner-ietf@ietf.org  Thu Jan 29 07:51:31 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15256
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 07:51:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmBYq-0000cc-9m
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 07:46:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmBYl-0000YZ-4M
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 07:46:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15140
	for <ietf@ietf.org>; Thu, 29 Jan 2004 07:46:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmBYk-0006WG-00
	for ietf@ietf.org; Thu, 29 Jan 2004 07:46:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmBXm-0006Ql-00
	for ietf@ietf.org; Thu, 29 Jan 2004 07:45:14 -0500
Received: from stewart.chicago.il.us ([66.93.186.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmBWm-0006G2-00
	for IETF@ietf.org; Thu, 29 Jan 2004 07:44:12 -0500
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1])
	by stewart.chicago.il.us (8.12.8p1/8.12.8) with ESMTP id i0TCheO6067633;
	Thu, 29 Jan 2004 06:43:41 -0600 (CST)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <4018FFFB.2010201@stewart.chicago.il.us>
Date: Thu, 29 Jan 2004 06:43:39 -0600
From: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
CC: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
Subject: Re: Death of the Internet - details at 11
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us> <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us> <654669B6-524E-11D8-98F9-000A95CD987A@muada.com>
In-Reply-To: <654669B6-524E-11D8-98F9-000A95CD987A@muada.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum wrote:

> On 28-jan-04, at 23:47, Randall R. Stewart (home) wrote:
>
>>> - increased overhead compared to TCP
>>
>
>> Ok lets see. SCTP takes on average 4 more bytes per data packet then
>> TCP. However, if the TCP implementation enables timestamps then
>> that is not true and TCP takes more overhead by about 4 bytes...
>
>
> Hm... timestamp option takes 12 bytes, what gives? 


Ahh.. I never did the direct comparison at the RFCs... just what
I saw in ethereal..

My hosts are BSD based and always send MSS of 1448 bytes. SCTP
uses 1452.

Looking at the RFC's SCTP is 8 bytes more...

Don't think 8 bytes is really a killer.. especially when 4 of those
bytes can be used for the application (PPId)....

And especially since:

1) SCTP is not as subject to the wrap issue so Timestamps are not needed
2) SCTP is not as subject to data and control injection by blind attackers

and these come for free as well..

>
>
>> Unless you are discussing another type of overhead...
>
>
> Apart from the extra bytes (which isn't the main issue) there are the 
> CRC32 checksum, which is considerably more expensive to compute than 
> the TCP/UDP/IP checksum and the fact that SCTP has much more 
> complexity. I would be surprised if the "fast path" for SCTP wouldn't 
> turn out to be more expensive than that of TCP, especially without 
> disabling all the features that make SCTP more interesting than TCP in 
> the first place. And of course those heartbeats I love to hate. (Which 
> don't provide any benefits when there are only two paths anyway.)

As to CRC32c .. yes it is more expensive.. but it affords a lot more
protection then the TCP checksum.  And just like the TCP checksum
there are already chipsets out there that do this in hardware... I
know intel has such a chipset and I am sure you will see it evolve
to other hardware makers as well.

As to the other features... if the application is going to
have to perform them then you have not removed the
cost.. you have just pushed it to a higher layer...

>
>>> - requires significant changes from applications
>>
>
>> Ok let see.. for Mozilla we converted two lines of code
>
>
> Ok, we can discuss whether the changes are significant but the fact 
> that changes are required at all is the main problem. 


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

>
>
>> sd = socket(AF_INET6, SOCK_STREAM, IPPROTO_TCP);
>> became --------------> sd = socket(AF_INET, SOCK_STREAM, IPPROTO_SCTP);
>
>
>> and
>
>
>> setsockopt(sd, IPPROTO_TCP, TCP_NODELAY, &on_off, sizeof(on_off));
>> became ---------------> setsockopt(sd, IPPROTO_SCTP, SCTP_NODELAY, 
>> &on_off, sizeof(on_off));
>
>
> So is this enough to gain all multihoming benefits? Even if all other 
> magic is hidden inside the protocol, the application must at least try 
> all possible destination addresses. (But this is true for several 
> other multi6 proposals as well.) 


Yes you get a retransmissions to alternate addresses with this small 
change. And
you don't have to try all the addresses.. just an alternate until you
find one that works...

>
>
>> Now to take advantage of the stream feature you would need to do
>> more.. but for pure multi-homing one or two lines of change does
>> not seem that big of deal to me ...
>
>
> Doing WWW-style HTTP (lots of concurrent sessions) with SCTP would be 
> nonsense, this is where the feature where multiple streams are 
> multiplexed over a single session would be extremely useful. 


Yes.. if you wanted to do HTTP over SCTP and use features such
as streams you WOULD WANT to extend HTML so that you could
have the client "get pages" on particular streams... Then you could
have parrallel transfers over one association and not have to require
multiple TCP connections... this is optimal...

Jana was doing some investagtion into this at the University of 
Deleware's Protocol
Engineering Lab.. don't know if he will be writting a paper on it.. I 
imagine so...

>
>
>>> - no backward compatibility of any kind
>>
>
>> I am not sure what you mean by backward compatable? You definetly
>> can't have TCP and SCTP talk.. they are after all different protocols...
>> But if an application needs the redundancy move to it.. its there today
>> with about 2 lines of coding change...
>
>
> But then you'll have to run services on both TCP and SCTP pretty much 
> forever. Not a good thing.

Just like we are stuck with IPv4 "forever" as well...  Its pretty much
a given.. once a new technology comes along it is a slow gradual 
transition not
a mass move. IPv6 as been out since 1993 and we are not only 11 years into
the migration.. it will all happen eventually.. but I see many years 
left for
IPv4... and only a slow migration to V6...

The same, I think, can be said for SCTP.. and it is very early in this 
process if
you use IPv6 as a gage :-D

>
>>> - source address selection problem isn't addressed fully, if at all
>>
>
>> I don't think I understand this issue either..
>
>
> Host has addresses a and b from ISPs A and B. Host sends a packet to 
> address x which is routed over ISP A. However, the host selects source 
> address b which is filtered by A, so no connectivity. For extra 
> credit: solve same when this happens in the middle of a session, and 
> in cases where connectivity consists of two one way paths. (a -> x and 
> y -> b work, but not x -> a or b -> y) 


We have solved this in kame with our alternate routing code. Each time
an address fails more than a threshold (default of 2 rtx's if I remember 
right) we
ask the routing system for an alternate route... This makes it so that after
any two failed transmissions to x routed through B we would then ask for
a new route and get one over A... And yes it works in the the middle
of a session when the ISP makes a change during the conversation.. the
thresholds are not picky about when it happens ...

I might add that TCP could also take advantage of this code and gain
some reliability as well.

Oh, and note, in your scenario above.. if it happens in the middle of
a TCP connection the connection will fail.. or just plain not start
up if it is being filtered and that is the way the routes point.

For our KAME stack with the patch it will NOT fail in the middle...

>
>
>> We have fully
>> addressed source address selection in the KAME implementation.
>
>
> In what way? 


See above, you would be best to get the KAME stack, and the patch from
www.sctp.org
(further details are in the alternate routing discussion on the sctp.org 
web site)
and then play with it..

R

>
>
>
>


-- 
Randall R. Stewart
815-477-2127 (office)
815-342-5222 (cell phone)





From owner-ietf@ietf.org  Thu Jan 29 08:43:56 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17082
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 08:43:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmCHo-0003vv-8F
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 08:32:48 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Am2KV-0004Nb-Az
	for ietf@asgard.ietf.org; Wed, 28 Jan 2004 21:54:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13541
	for <ietf@ietf.org>; Wed, 28 Jan 2004 21:54:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am2KT-0007Tf-00
	for ietf@ietf.org; Wed, 28 Jan 2004 21:54:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Am2JV-0007NT-00
	for ietf@ietf.org; Wed, 28 Jan 2004 21:53:53 -0500
Received: from cooprev.independence.net ([206.168.112.32] helo=sirius.theinternetco.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am2IZ-0007Dw-00
	for ietf@ietf.org; Wed, 28 Jan 2004 21:52:55 -0500
Received: from [3ffe:bc0:641:1:208:c7ff:fed9:fa6a] (helo=betelgeuse.theinternetco.net)
	by sirius.theinternetco.net with asmtp (Exim 4.30)
	id 1Am2IT-0003pZ-St
	for ietf@ietf.org; Wed, 28 Jan 2004 19:52:50 -0700
Received: from aredridel by betelgeuse.theinternetco.net with local (Exim 4.30)
	id 1Am2IP-00022A-3T
	for ietf@ietf.org; Wed, 28 Jan 2004 19:52:45 -0700
Date: Wed, 28 Jan 2004 19:52:44 -0700
From: Rick Stewart <rick.stewart@theinternetco.net>
Cc: ietf@ietf.org
Subject: Re: Wiki RFC
Message-ID: <20040129025244.GA7814@mail.theinternetco.net>
References: <1075250978.2820.55.camel@franck-lxnb.sopac.org.fj> <1422526635.1075310715@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1422526635.1075310715@localhost>
User-Agent: Mutt/1.4.1i
X-Arbitrary-Number-Of-The-Day: 42
X-Scan-Signature: d4f800c6dfb852e833af5c577c06e812
X-Spam-Score: 0.0 (/)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Jan 28, 2004 at 05:25:15PM -0800, Harald Tveit Alvestrand wrote:
> 
> 
> --On 28. januar 2004 12:49 +1200 Franck Martin <franck@sopac.org> wrote:
> 
> >I was just wondering if there has been any work to standardise the Wiki
> >syntax/system into an RFC?
> 
> AFAIK, no.
> Do you know of any effort to make stable documentation for the WIKI syntax 
> & functionality, or is it just "use the Source, Luke"?

And beware those peddling "The" wiki syntax.

Most engines invent their own.

I know the one I've written leans far more to the natural-language side
of things at the moment.

> 
> 
> 
> 





From owner-ietf@ietf.org  Thu Jan 29 08:52:49 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17448
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 08:52:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmCXG-0005Qa-Pp
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 08:48:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmCWn-0005Km-Cu
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 08:48:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17338
	for <ietf@ietf.org>; Thu, 29 Jan 2004 08:48:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmCWm-0005pt-00
	for ietf@ietf.org; Thu, 29 Jan 2004 08:48:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmCVn-0005gy-00
	for ietf@ietf.org; Thu, 29 Jan 2004 08:47:16 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmCUo-0005TX-00
	for IETF@ietf.org; Thu, 29 Jan 2004 08:46:14 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AmCUn-0001CC-00; Thu, 29 Jan 2004 08:46:13 -0500
Date: Thu, 29 Jan 2004 08:46:13 -0500
From: John C Klensin <john-ietf@jck.com>
To: Dave Crocker <dhc@dcrocker.net>
cc: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <65886049.1075365973@scan.jck.com>
In-Reply-To: <1419514349.20040129143445@brandenburg.com>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com>
 <19410259999.20040128073646@brandenburg.com>
 <224923613.1075293579@scan.jck.com>
 <1419514349.20040129143445@brandenburg.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Thursday, 29 January, 2004 14:34 +0900 Dave Crocker 
<dhc@dcrocker.net> wrote:

>...
> JCK> Yes.  And it may speak to the IETF's sense of priorities
> that JCK> the efforts to which you refer are predominantly
> going into the  JCK> much more complex and long-term problem,
> rather than the one  JCK> that is presumably easier to solve
> and higher leverage.
>
> I think a simple version of what you want is already available
> and has been for many years, namely multiple A records in the
> DNS.
>
> (OK.  Let's see you respond to _that_ and claim that the
> response only has picks at nits... Hah!)

Of course, multiple A records works, is out there, and have 
worked for years.  But they worked better before we introduced 
routers (i.e., when the hosts with multiple A records really had 
interfaces on different networks).  Today, it effectively 
implies having multiple addresses on an interface and multiple 
"local" address prefixes running around on the same physical LAN 
segment.  IPv4 was not designed to work well in that environment 
and, with at least some implementations that are arguably still 
conforming, it has some unfortunate side effects, such as not 
really knowing which addresses are local to you and which 
aren't, at least without setting up local routing tables that 
are well beyond the capabilities of the typical user.  The claim 
has been made that IPv6 _is_ designed to work in that 
environment, for whatever that claim may be worth.

Perhaps more important, as Noel points out, it doesn't scale 
very well, at least in terms of the routing fabric.   And, as I 
tried to point out, address preservation policies have had 
trickle-down effects that make it impractical for small 
enterprises.

Nits?  Probably not.

   best,
    john




From owner-ietf@ietf.org  Thu Jan 29 10:02:10 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20299
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 10:02:10 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmDXj-0001u1-7J
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 09:53:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmDWo-0001pr-9N
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 09:52:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19990
	for <ietf@ietf.org>; Thu, 29 Jan 2004 09:52:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmDWn-0005Ho-00
	for ietf@ietf.org; Thu, 29 Jan 2004 09:52:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmDVr-00059e-00
	for ietf@ietf.org; Thu, 29 Jan 2004 09:51:24 -0500
Received: from parsley.amaranth.net ([208.254.46.23])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmDVD-00052z-00
	for IETF@ietf.org; Thu, 29 Jan 2004 09:50:43 -0500
Received: from Willow.senie.com (h0006b1049b35.ne.client2.attbi.com [24.91.86.165])
	(authenticated bits=0)
	by parsley.amaranth.net (8.12.8/8.12.8) with ESMTP id i0TEoe5V013764
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <IETF@ietf.org>; Thu, 29 Jan 2004 09:50:40 -0500
Message-Id: <6.0.1.1.2.20040129094026.0308c540@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 29 Jan 2004 09:50:32 -0500
To: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
From: Daniel Senie <dts@senie.com>
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <4018FFFB.2010201@stewart.chicago.il.us>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com>
 <19410259999.20040128073646@brandenburg.com>
 <224923613.1075293579@scan.jck.com>
 <40182303.7000300@stewart.chicago.il.us>
 <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com>
 <40183C10.10401@stewart.chicago.il.us>
 <654669B6-524E-11D8-98F9-000A95CD987A@muada.com>
 <4018FFFB.2010201@stewart.chicago.il.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 07:43 AM 1/29/2004, Randall R. Stewart (home) wrote:
>Iljitsch van Beijnum wrote:
>
>>On 28-jan-04, at 23:47, Randall R. Stewart (home) wrote:
>>
>>>>- increased overhead compared to TCP
>>
>>>Ok lets see. SCTP takes on average 4 more bytes per data packet then
>>>TCP. However, if the TCP implementation enables timestamps then
>>>that is not true and TCP takes more overhead by about 4 bytes...
>>
>>
>>Hm... timestamp option takes 12 bytes, what gives?
>
>
>Ahh.. I never did the direct comparison at the RFCs... just what
>I saw in ethereal..
>
>My hosts are BSD based and always send MSS of 1448 bytes. SCTP
>uses 1452.
>
>Looking at the RFC's SCTP is 8 bytes more...
>
>Don't think 8 bytes is really a killer.. especially when 4 of those
>bytes can be used for the application (PPId)....
>
>And especially since:
>
>1) SCTP is not as subject to the wrap issue so Timestamps are not needed
>2) SCTP is not as subject to data and control injection by blind attackers
>
>and these come for free as well..
>
>>
>>
>>>Unless you are discussing another type of overhead...
>>
>>
>>Apart from the extra bytes (which isn't the main issue) there are the 
>>CRC32 checksum, which is considerably more expensive to compute than the 
>>TCP/UDP/IP checksum and the fact that SCTP has much more complexity. I 
>>would be surprised if the "fast path" for SCTP wouldn't turn out to be 
>>more expensive than that of TCP, especially without disabling all the 
>>features that make SCTP more interesting than TCP in the first place. And 
>>of course those heartbeats I love to hate. (Which don't provide any 
>>benefits when there are only two paths anyway.)
>
>As to CRC32c .. yes it is more expensive.. but it affords a lot more
>protection then the TCP checksum.  And just like the TCP checksum
>there are already chipsets out there that do this in hardware... I
>know intel has such a chipset and I am sure you will see it evolve
>to other hardware makers as well.
>
>As to the other features... if the application is going to
>have to perform them then you have not removed the
>cost.. you have just pushed it to a higher layer...
>
>>
>>>>- requires significant changes from applications
>>
>>>Ok let see.. for Mozilla we converted two lines of code
>>
>>
>>Ok, we can discuss whether the changes are significant but the fact that 
>>changes are required at all is the main problem.
>
>
>You don't get new features without change of some sort...
>
>>
>>
>>>sd = socket(AF_INET6, SOCK_STREAM, IPPROTO_TCP);
>>>became --------------> sd = socket(AF_INET, SOCK_STREAM, IPPROTO_SCTP);
>>
>>
>>>and
>>
>>
>>>setsockopt(sd, IPPROTO_TCP, TCP_NODELAY, &on_off, sizeof(on_off));
>>>became ---------------> setsockopt(sd, IPPROTO_SCTP, SCTP_NODELAY, 
>>>&on_off, sizeof(on_off));
>>
>>
>>So is this enough to gain all multihoming benefits? Even if all other 
>>magic is hidden inside the protocol, the application must at least try 
>>all possible destination addresses. (But this is true for several other 
>>multi6 proposals as well.)
>
>
>Yes you get a retransmissions to alternate addresses with this small 
>change. And
>you don't have to try all the addresses.. just an alternate until you
>find one that works...

I really don't see how this fits with routing policy. You appear to make 
the assumption that a multi-homed site wants to use the multiple paths as 
equals.




>>>Now to take advantage of the stream feature you would need to do
>>>more.. but for pure multi-homing one or two lines of change does
>>>not seem that big of deal to me ...
>>
>>
>>Doing WWW-style HTTP (lots of concurrent sessions) with SCTP would be 
>>nonsense, this is where the feature where multiple streams are 
>>multiplexed over a single session would be extremely useful.
>
>
>Yes.. if you wanted to do HTTP over SCTP and use features such
>as streams you WOULD WANT to extend HTML so that you could
>have the client "get pages" on particular streams... Then you could
>have parrallel transfers over one association and not have to require
>multiple TCP connections... this is optimal...
>
>Jana was doing some investagtion into this at the University of Deleware's 
>Protocol
>Engineering Lab.. don't know if he will be writting a paper on it.. I 
>imagine so...
>
>>
>>
>>>>- no backward compatibility of any kind
>>
>>>I am not sure what you mean by backward compatable? You definetly
>>>can't have TCP and SCTP talk.. they are after all different protocols...
>>>But if an application needs the redundancy move to it.. its there today
>>>with about 2 lines of coding change...
>>
>>
>>But then you'll have to run services on both TCP and SCTP pretty much 
>>forever. Not a good thing.
>
>Just like we are stuck with IPv4 "forever" as well...  Its pretty much
>a given.. once a new technology comes along it is a slow gradual 
>transition not
>a mass move. IPv6 as been out since 1993 and we are not only 11 years into
>the migration.. it will all happen eventually.. but I see many years left for
>IPv4... and only a slow migration to V6...
>
>The same, I think, can be said for SCTP.. and it is very early in this 
>process if
>you use IPv6 as a gage :-D
>
>>
>>>>- source address selection problem isn't addressed fully, if at all
>>
>>>I don't think I understand this issue either..
>>
>>
>>Host has addresses a and b from ISPs A and B. Host sends a packet to 
>>address x which is routed over ISP A. However, the host selects source 
>>address b which is filtered by A, so no connectivity. For extra credit: 
>>solve same when this happens in the middle of a session, and in cases 
>>where connectivity consists of two one way paths. (a -> x and y -> b 
>>work, but not x -> a or b -> y)
>
>
>We have solved this in kame with our alternate routing code. Each time
>an address fails more than a threshold (default of 2 rtx's if I remember 
>right) we
>ask the routing system for an alternate route... This makes it so that after
>any two failed transmissions to x routed through B we would then ask for
>a new route and get one over A... And yes it works in the the middle
>of a session when the ISP makes a change during the conversation.. the
>thresholds are not picky about when it happens ...

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

I'm afraid the multihoming solution you are promoting does not match up 
entirely with the full scope of the multihoming problem. Though I'm sure 
some folks will be relieved to not need to formulate routing policies, it 
does seem a lot of folks really want to be able to control their routing. 
Today, there can be cost differences among circuits (think about circuits 
that are priced based on usage), preferred circuits, and so forth.


>I might add that TCP could also take advantage of this code and gain
>some reliability as well.
>
>Oh, and note, in your scenario above.. if it happens in the middle of
>a TCP connection the connection will fail.. or just plain not start
>up if it is being filtered and that is the way the routes point.
>
>For our KAME stack with the patch it will NOT fail in the middle...
>
>>
>>
>>>We have fully
>>>addressed source address selection in the KAME implementation.
>>
>>
>>In what way?
>
>
>See above, you would be best to get the KAME stack, and the patch from
>www.sctp.org
>(further details are in the alternate routing discussion on the sctp.org 
>web site)
>and then play with it..

The other failing of the dual-address problem is the need for dual 
addresses. I guess we'll have to ask ARIN and the other RIRs to adjust 
their rules to allow justification of parallel allocations from multiple 
upstreams to a single company, where they'd only have needed a single block 
of a given size before. There's no free lunch, at least if there's any 
interest in using SCTP as a multihoming solution atop IPv4. 




From owner-ietf@ietf.org  Thu Jan 29 11:36:52 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00296
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 11:36:52 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmEyq-000183-KW
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 11:25:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmEt0-0000dE-CC
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 11:19:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29425
	for <ietf@ietf.org>; Thu, 29 Jan 2004 11:19:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmEsz-0003rC-00
	for ietf@ietf.org; Thu, 29 Jan 2004 11:19:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmEs2-0003kP-00
	for ietf@ietf.org; Thu, 29 Jan 2004 11:18:22 -0500
Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AmEr7-0003Y4-00
	for ietf@ietf.org; Thu, 29 Jan 2004 11:17:26 -0500
Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap 
	 id 20403; Thu, 29 Jan 2004 11:18:54 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: visa requirements (US citizens)
Date: Thu, 29 Jan 2004 11:16:54 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209DB1A0CD@zoe.office.snowshore.com>
Thread-Topic: visa requirements (US citizens)
Thread-Index: AcPlG2bdQwJIaPNvRta0mBg9ZU7ycwBZZhMA
From: "Eric Burger" <eburger@snowshore.com>
To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR 
	autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

How about this for a twist:  if you ask for an invitation (required for =
a visa), you are told you really, really don't need it.  When I =
requested a visa from TTA, this is the response I got.  Has anyone =
succeeded in getting a letter?



-----Original Message-----
From: KeeMoon Roh [mailto:ietf59@tta.or.kr]
Sent: Monday, January 26, 2004 1:32 AM
To: Eric Burger
Subject: RE: [Fwd: Korean Visa invitation letter request for C-2 visa]


  Dear. Mr. Burger=20

This mail is from 59th Local IETF Secretariats in Korea.
Currently we are issuing invitation letters.

There is one thing we like to tell you about Korean Entry Visa.
USA Nationals who want to visit Korea just for a short-term tour or =
transit are permitted to enter Korea with no visa according to the =
principles of reciprocity or priority of national interests with a =
tourist/transit visa status(B-2, 30days).

Event though, it is written that No-Visa Entry is for a short-term tour =
or transit, participating in short term conventions or meetings(less =
than 30 days) is allowed as well.

I checked this out several times with Korean Embassy.

Please refer to http://www.mofat.go.kr/en/visa/e_visa.mof
=20
USA citizens, who hold US passport, do not need VISA to attend the 59th =
IETF Meeting in Seoul Korea,=20

Invitation letter is only for VISA issuing.
If you need for some other reason,
I can issue you an invitation letter without notarial certificate (not =
for submitting to Korean embassy).


If you still need an invitation letter. please reply to this mail =
(ietf59@tta.or.kr).

best regards,
-------------------------------------------------------------------------=
-------------
Kee-Moon Roh
???
???
TTA (Telecommunications Technology Association)
* Mobile : +82-11-1735-1161
* TEL     : +82-31-724-0075
* FAX     : +82-31-724-0059
* E-mail : kees@tta.or.kr ( TTA Secretariat )
* E-mail : ietf59@tta.or.kr ( 59th IETF Local Secretariat )
-------------------------------------------------------------------------=
---------------



> -----Original Message-----
> From: Paul Hoffman / IMC [mailto:phoffman@imc.org]
> Sent: Tuesday, January 27, 2004 4:07 PM
> To: Steve Bellovin; ietf@ietf.org
> Subject: Re: visa requirements (US citizens)
>=20
>=20
> At 2:31 PM -0500 1/27/04, Steve Bellovin wrote:
> >I was advised by our corporate travel consultants that I should get a
> >visa.  Given the current international climate -- there was=20
> an article
> >in last Thursday's Wall Street Journal about how other countries
> >are retaliating for the current U.S. fingerprinting and visa=20
> application
> >requirements -- this may be a prudent course of action.
>=20
> The Korean embassy page that is linked to from the IETF meetings page=20
> (<http://www.koreaembassy.org/visiting/eng_visas.cfm>) makes it=20
> pretty darn clear that US folks should get a visa. They do have a=20
> link from that page saying how wonderful US-Korea relations are, of=20
> course.
>=20
> Showing up in the airport without a visa and saying "but someone at=20
> one of your consulates told me I didn't need one" may go over as well=20
> in other countries as it does in the US...
>=20
> --Paul Hoffman, Director
> --Internet Mail Consortium
>=20
>=20
>=20




From owner-ietf@ietf.org  Thu Jan 29 11:37:59 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00338
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 11:37:59 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmF72-0002MF-Jd
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 11:33:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmF5b-00028W-2s
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 11:32:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00032
	for <ietf@ietf.org>; Thu, 29 Jan 2004 11:32:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmF5a-0005Ok-00
	for ietf@ietf.org; Thu, 29 Jan 2004 11:32:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmF4c-0005Fh-00
	for ietf@ietf.org; Thu, 29 Jan 2004 11:31:22 -0500
Received: from mercury.lcs.mit.edu ([18.26.0.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmF3f-00050z-00
	for IETF@ietf.org; Thu, 29 Jan 2004 11:30:23 -0500
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id 6110386AEA; Thu, 29 Jan 2004 11:29:52 -0500 (EST)
To: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Cc: jnc@mercury.lcs.mit.edu
Message-Id: <20040129162952.6110386AEA@mercury.lcs.mit.edu>
Date: Thu, 29 Jan 2004 11:29:52 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: John C Klensin <john-ietf@jck.com>

    > Of course, multiple A records works, is out there, and have worked for
    > years. But they worked better before we introduced routers (i.e., when
    > the hosts with multiple A records really had interfaces on different
    > networks). Today, it effectively implies having multiple addresses on
    > an interface and multiple "local" address prefixes running around on
    > the same physical LAN segment.
    > ...
    > Perhaps more important, as Noel points out, it doesn't scale very well,
    > at least in terms of the routing fabric.

Sorry? What I said doesn't work for the routing, in terms of scaling to many
small sites, is for a multi-homed site to have a single address prefix, which
is then globally advertised. (That's the most common tack for multi-homing
support in IPv4 to date, which is what you were talking about.)

Having multiple addresses for a host (which has only a single physical
interface, but which is in a site which is multi-homed) is in fact the only
approach whose effects on the routing does scale (within anything like the
current routing architecture, i.e. packets which include only source and
destination addresses, as opposed to a source route).


    > as I tried to point out, address preservation policies have had
    > trickle-down effects that make it impractical for small enterprises.

It is an interesting point (as Daniel Senie also just pointed out) that
multiple addresses -> faster consumption of the address space.

However, since to avoid a size explosion in the routing tables, those
multiple addresses do have to be connectivity-dependent (political
translation - "provider-dependent"), I don't see how address preservation
policies have made this approach "impractical for small enterprises". My
understanding of current allocation policies is that ISP's can get enough
addresses to cover their customers. If company X is a customer of both ISP P
and ISP Q, I would assume that both P and Q don't have a problem getting
enough space to cover their customers - including X.

(Or were you speaking of the "one address block, globally advertized"?)

	Noel



From owner-ietf@ietf.org  Thu Jan 29 11:56:08 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01311
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 11:56:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmFCJ-0003XP-26
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 11:39:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmFBW-0003IK-HI
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 11:38:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00365
	for <ietf@ietf.org>; Thu, 29 Jan 2004 11:38:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmFBV-00066F-00
	for ietf@ietf.org; Thu, 29 Jan 2004 11:38:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmFAU-0005xm-00
	for ietf@ietf.org; Thu, 29 Jan 2004 11:37:27 -0500
Received: from ginger.cmf.nrl.navy.mil ([134.207.10.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmF9z-0005sA-00
	for ietf@ietf.org; Thu, 29 Jan 2004 11:36:55 -0500
Received: from cmf.nrl.navy.mil (elvis.cmf.nrl.navy.mil [134.207.10.38])
	(authenticated bits=0)
	by ginger.cmf.nrl.navy.mil (8.12.7/8.12.7) with ESMTP id i0TGafRr019321
	for <ietf@ietf.org>; Thu, 29 Jan 2004 11:36:41 -0500 (EST)
Message-Id: <200401291636.i0TGafRr019321@ginger.cmf.nrl.navy.mil>
To: ietf@ietf.org
Subject: Re: visa requirements (US citizens) 
In-Reply-To: Message from Gene Gaines <gene.gaines@gainesgroup.com> 
   of "Wed, 28 Jan 2004 17:20:24 EST." <1266011254.20040128172024@gainesgroup.com> 
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4
	WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d
	gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;Mv(aiO2z~9n.w?@\>kEpSD@*e`
Date: Thu, 29 Jan 2004 11:36:41 -0500
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
X-Spam-Score: () hits=0 User Authenticated
X-Virus-Scanned: NAI Completed
X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>A U.S. citizen does NOT need a visa to visit Korea for a meeting
>by a non-profit group such as the Internet Engineering Task Force.
>I just confirmed this with the head of the visa section in the
>Korean Consulate in Washington DC.

Gene,

Could you please post the contact information for the head of the visa
section of the Korean Consulate?  My call to the to the same consolate
where I navigated the menus to the visa department resulted in me
talking to a person who was ... well, I suppose the kindest thing to
say was that he was less than completely confident in his answer.  It
makes me nervous when two different people talk to the same
organization and get two completely different answers.

--Ken



From owner-ietf@ietf.org  Thu Jan 29 12:10:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01923
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 12:10:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmFY2-00052Q-7r
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 12:01:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmFM6-0004Dy-Mz
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 11:49:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00995
	for <ietf@ietf.org>; Thu, 29 Jan 2004 11:49:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmFM5-0007V4-00
	for ietf@ietf.org; Thu, 29 Jan 2004 11:49:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmFL8-0007Pv-00
	for ietf@ietf.org; Thu, 29 Jan 2004 11:48:27 -0500
Received: from ginger.cmf.nrl.navy.mil ([134.207.10.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmFKv-0007Kb-00
	for ietf@ietf.org; Thu, 29 Jan 2004 11:48:13 -0500
Received: from cmf.nrl.navy.mil (elvis.cmf.nrl.navy.mil [134.207.10.38])
	(authenticated bits=0)
	by ginger.cmf.nrl.navy.mil (8.12.7/8.12.7) with ESMTP id i0TGm9Rr019515;
	Thu, 29 Jan 2004 11:48:10 -0500 (EST)
Message-Id: <200401291648.i0TGm9Rr019515@ginger.cmf.nrl.navy.mil>
To: "Eric Burger" <eburger@snowshore.com>
cc: ietf@ietf.org
Subject: Re: visa requirements (US citizens) 
In-Reply-To: Message from "Eric Burger" <eburger@snowshore.com> 
   of "Thu, 29 Jan 2004 11:16:54 EST." <4A3384433CE2AB46A63468CB207E209DB1A0CD@zoe.office.snowshore.com> 
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4
	WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d
	gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;Mv(aiO2z~9n.w?@\>kEpSD@*e`
Date: Thu, 29 Jan 2004 11:48:09 -0500
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
X-Spam-Score: () hits=0 User Authenticated
X-Virus-Scanned: NAI Completed
X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>How about this for a twist:  if you ask for an invitation (required for a
>visa), you are told you really, really don't need it.  When I requested a
>visa from TTA, this is the response I got.  Has anyone succeeded in getting
>a letter?

When I downloaded the visa application form (and checked the Korean Embassy
web page), it did not indicate that an invitation letter was required from
anyone in Korea.  What it did indicate was required (and you can check
the web page yourself at http://www.koreaembassy.org/visiting/eng_visas.cfm),
is the following (assuming you're a US citizen and you get a "business" visa):

- Visa application form
- One passport-sized photo
- US Passport
- Original copy of company letter on company letterhead _signed by your
  employer_ (emphasis mine), stating the purpose, name and duration
- $ 45.00 USD application fee.
- And a prepaid postage return envelope (if applying by mail)

While the question of whether or not a visa is required has not in my mind
been completely answered, it appears definite to me that you don't need
an invitation letter from TTA to get one.

--Ken



From owner-ietf@ietf.org  Thu Jan 29 12:46:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04504
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 12:46:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmG8V-00082p-Cd
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 12:39:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmG5e-0007kZ-2j
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 12:36:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03596
	for <ietf@ietf.org>; Thu, 29 Jan 2004 12:36:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmG5d-0005it-00
	for ietf@ietf.org; Thu, 29 Jan 2004 12:36:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmG4m-0005cz-00
	for ietf@ietf.org; Thu, 29 Jan 2004 12:35:37 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmG4F-0005WP-00; Thu, 29 Jan 2004 12:35:03 -0500
Received: from [192.168.1.5] (dsl081-036-151.lax1.dsl.speakeasy.net [64.81.36.151])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i0THZ2v10744;
	Thu, 29 Jan 2004 09:35:02 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <73DC462E-5281-11D8-B733-000A95DBDB84@isi.edu>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, iesg@ietf.org
From: Aaron Falk <falk@ISI.EDU>
Subject: Do we or don't we need a visa for the Korean IETF?
Date: Thu, 29 Jan 2004 09:34:55 -0800
To: Support Online <iesg-secretary@ietf.org>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

This is insane.  Can the Secretariat please give unambiguous advice  
(preferably backed up by a letter from the Korean embassy) to  
attendees?

--aaron

Begin forwarded message:

> From: "Eric Burger" <eburger@snowshore.com>
> Date: January 29, 2004 8:16:54 AM PST
> To: <ietf@ietf.org>
> Subject: RE: visa requirements (US citizens)
>
> How about this for a twist:  if you ask for an invitation (required  
> for a visa), you are told you really, really don't need it.  When I  
> requested a visa from TTA, this is the response I got.  Has anyone  
> succeeded in getting a letter?
>
>
>
> -----Original Message-----
> From: KeeMoon Roh [mailto:ietf59@tta.or.kr]
> Sent: Monday, January 26, 2004 1:32 AM
> To: Eric Burger
> Subject: RE: [Fwd: Korean Visa invitation letter request for C-2 visa]
>
>
>   Dear. Mr. Burger
>
> This mail is from 59th Local IETF Secretariats in Korea.
> Currently we are issuing invitation letters.
>
> There is one thing we like to tell you about Korean Entry Visa.
> USA Nationals who want to visit Korea just for a short-term tour or  
> transit are permitted to enter Korea with no visa according to the  
> principles of reciprocity or priority of national interests with a  
> tourist/transit visa status(B-2, 30days).
>
> Event though, it is written that No-Visa Entry is for a short-term  
> tour or transit, participating in short term conventions or  
> meetings(less than 30 days) is allowed as well.
>
> I checked this out several times with Korean Embassy.
>
> Please refer to http://www.mofat.go.kr/en/visa/e_visa.mof
>
> USA citizens, who hold US passport, do not need VISA to attend the  
> 59th IETF Meeting in Seoul Korea,
>
> Invitation letter is only for VISA issuing.
> If you need for some other reason,
> I can issue you an invitation letter without notarial certificate (not  
> for submitting to Korean embassy).
>
>
> If you still need an invitation letter. please reply to this mail  
> (ietf59@tta.or.kr).
>
> best regards,
> ----------------------------------------------------------------------- 
> ---------------
> Kee-Moon Roh
> ???
> ???
> TTA (Telecommunications Technology Association)
> * Mobile : +82-11-1735-1161
> * TEL     : +82-31-724-0075
> * FAX     : +82-31-724-0059
> * E-mail : kees@tta.or.kr ( TTA Secretariat )
> * E-mail : ietf59@tta.or.kr ( 59th IETF Local Secretariat )
> ----------------------------------------------------------------------- 
> -----------------
>
>
>
>> -----Original Message-----
>> From: Paul Hoffman / IMC [mailto:phoffman@imc.org]
>> Sent: Tuesday, January 27, 2004 4:07 PM
>> To: Steve Bellovin; ietf@ietf.org
>> Subject: Re: visa requirements (US citizens)
>>
>>
>> At 2:31 PM -0500 1/27/04, Steve Bellovin wrote:
>>> I was advised by our corporate travel consultants that I should get a
>>> visa.  Given the current international climate -- there was
>> an article
>>> in last Thursday's Wall Street Journal about how other countries
>>> are retaliating for the current U.S. fingerprinting and visa
>> application
>>> requirements -- this may be a prudent course of action.
>>
>> The Korean embassy page that is linked to from the IETF meetings page
>> (<http://www.koreaembassy.org/visiting/eng_visas.cfm>) makes it
>> pretty darn clear that US folks should get a visa. They do have a
>> link from that page saying how wonderful US-Korea relations are, of
>> course.
>>
>> Showing up in the airport without a visa and saying "but someone at
>> one of your consulates told me I didn't need one" may go over as well
>> in other countries as it does in the US...
>>
>> --Paul Hoffman, Director
>> --Internet Mail Consortium
>>
>>
>>
>
>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it,  
> which is a sublist of ietf@ietf.org. Not all messages are passed.  
> Decisions on what to pass are made solely by IETF_CENSORED ML  
> Administrator (ietf_admin@ngnet.it).




From owner-ietf@ietf.org  Thu Jan 29 12:59:56 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05295
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 12:59:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmGNE-0001bk-Hc
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 12:54:40 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmGGW-0000lW-3T
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 12:47:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04751
	for <ietf@ietf.org>; Thu, 29 Jan 2004 12:47:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmGGV-0007b2-00
	for ietf@ietf.org; Thu, 29 Jan 2004 12:47:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmGFk-0007RK-00
	for ietf@ietf.org; Thu, 29 Jan 2004 12:46:56 -0500
Received: from thing.verisignlabs.com ([65.201.175.62] helo=cliffie.verisignlabs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmGEq-0007A3-00
	for ietf@ietf.org; Thu, 29 Jan 2004 12:46:00 -0500
Received: from thinkingcat.com ([::ffff:208.251.43.51])
  (AUTH: PLAIN leslie, TLS: TLSv1/SSLv3,128bits,RC4-MD5)
  by cliffie.verisignlabs.com with esmtp; Thu, 29 Jan 2004 12:45:27 -0500
Message-ID: <401946E8.9030207@thinkingcat.com>
Date: Thu, 29 Jan 2004 12:46:16 -0500
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: Fred Baker <fred@cisco.com>
CC: Pekka Savola <pekkas@netcore.fi>, ietf@ietf.org
Subject: Re: The IETF Mission [Re: Summary status of change efforts - Updated
 Web page]
References: <405441934.1074293627@localhost> <Pine.LNX.4.44.0401171150270.11109-100000@netcore.fi> <6.0.1.1.2.20040117103457.0466fc00@mira-sjc5-b.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



I'd like to come back to this point, and try a slightly different
direction:

Fred Baker wrote:
>>"The purpose of the IETF is to create high quality, relevant, and
>>timely standards for the Internet."
> 
> 
> I think I would state it in these words:
> 
>     "The Internet Engineering Task Force provides a forum for the
>     discussion and development of white papers and specifications
>     for the engineering issues of the Internet."
>

This seems like a reasonable characterization of the output of
the IETF.  

However, it doesn't seem to capture some of the scoping/delimiting 
that the original text did -- does the IETF discuss any and all
such issues?  Is it trying to achieve anything in particular
by documenting things?  (How) can we detect that there are issues
we should be discussing and can't?

(How) would you add to your text to provide some boundaries/
guiding lines?


Leslie.

-- 

-------------------------------------------------------------------
"Reality:
      Yours to discover."
                                 -- ThinkingCat 

Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------





From owner-ietf@ietf.org  Thu Jan 29 12:59:58 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05315
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 12:59:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmGOp-0001sv-Do
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 12:56:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmGL4-0001Lt-UW
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 12:52:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05049
	for <ietf@ietf.org>; Thu, 29 Jan 2004 12:52:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmGL3-0000RG-00
	for ietf@ietf.org; Thu, 29 Jan 2004 12:52:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmGK9-0000M2-00
	for ietf@ietf.org; Thu, 29 Jan 2004 12:51:30 -0500
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1AmGJe-0000Ev-00
	for ietf@ietf.org; Thu, 29 Jan 2004 12:50:58 -0500
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (NAVGW 2.5.2.11) with SMTP id M2004012913092331917
 for <ietf@ietf.org>; Thu, 29 Jan 2004 13:09:25 -0500
Received: from centive.com ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 29 Jan 2004 12:47:15 -0500
Message-ID: <40194720.8040708@centive.com>
Date: Thu, 29 Jan 2004 12:47:12 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Do we or don't we need a visa for the Korean IETF?
References: <73DC462E-5281-11D8-B733-000A95DBDB84@isi.edu>
In-Reply-To: <73DC462E-5281-11D8-B733-000A95DBDB84@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Jan 2004 17:47:15.0518 (UTC) FILETIME=[EEA79DE0:01C3E68F]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Aaron Falk wrote:

> This is insane.  Can the Secretariat please give unambiguous advice  
> (preferably backed up by a letter from the Korean embassy) to  attendees?

It sounds like you might be safest contacting the Korean embassy 
yourself and asking for a visa.  If they say you don't need one, you're 
on firmer ground than if the IETF says you don't need one.

-- 
/================================================================\
|John Stracke      |jstracke@centive.com                         |
|Principal Engineer|http://www.centive.com                       |
|Centive           |My opinions are my own.                      |
|================================================================|
|That is correct. I'm out of fuel. My landing gear is jammed. And|
|there's an unhappy bald eagle loose in the cockpit.             |
\================================================================/




From owner-ietf@ietf.org  Thu Jan 29 13:30:13 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06469
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 13:30:13 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmGow-0005vM-IN
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 13:23:18 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmGlE-0005Oc-NB
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 13:19:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06197
	for <ietf@ietf.org>; Thu, 29 Jan 2004 13:19:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmGlD-0003Sk-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:19:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmGkK-0003NH-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:18:32 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmGjh-0003Hi-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:17:53 -0500
Received: from [128.9.168.79] (nak.isi.edu [128.9.168.79])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i0TIHqv04231;
	Thu, 29 Jan 2004 10:17:52 -0800 (PST)
In-Reply-To: <40194720.8040708@centive.com>
References: <73DC462E-5281-11D8-B733-000A95DBDB84@isi.edu> <40194720.8040708@centive.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <730F0A9C-5287-11D8-B733-000A95DBDB84@isi.edu>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Aaron Falk <falk@ISI.EDU>
Subject: Re: Do we or don't we need a visa for the Korean IETF?
Date: Thu, 29 Jan 2004 10:17:51 -0800
To: John Stracke <jstracke@centive.com>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Jan 29, 2004, at 9:47 AM, John Stracke wrote:

> It sounds like you might be safest contacting the Korean embassy 
> yourself and asking for a visa.  If they say you don't need one, 
> you're on firmer ground than if the IETF says you don't need one.

I believe the risk is in how one characterizes what an IETF meeting is 
and why one is attending.  I would prefer that we had all had the same 
instructions on what to say, vetted by the embassy.

--aaron




From owner-ietf@ietf.org  Thu Jan 29 13:30:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06487
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 13:30:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmGow-0005vS-Sl
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 13:23:18 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmGlG-0005Oe-2c
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 13:19:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06205
	for <ietf@ietf.org>; Thu, 29 Jan 2004 13:19:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmGlE-0003Su-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:19:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmGkM-0003NX-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:18:34 -0500
Received: from ginger.cmf.nrl.navy.mil ([134.207.10.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmGk0-0003Hn-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:18:12 -0500
Received: from cmf.nrl.navy.mil (elvis.cmf.nrl.navy.mil [134.207.10.38])
	(authenticated bits=0)
	by ginger.cmf.nrl.navy.mil (8.12.7/8.12.7) with ESMTP id i0TII6Rr021016
	for <ietf@ietf.org>; Thu, 29 Jan 2004 13:18:06 -0500 (EST)
Message-Id: <200401291818.i0TII6Rr021016@ginger.cmf.nrl.navy.mil>
To: ietf@ietf.org
Subject: Re: Do we or don't we need a visa for the Korean IETF? 
In-Reply-To: Message from John Stracke <jstracke@centive.com> 
   of "Thu, 29 Jan 2004 12:47:12 EST." <40194720.8040708@centive.com> 
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4
	WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d
	gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;Mv(aiO2z~9n.w?@\>kEpSD@*e`
Date: Thu, 29 Jan 2004 13:18:06 -0500
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
X-Spam-Score: () hits=0 User Authenticated
X-Virus-Scanned: NAI Completed
X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>> This is insane.  Can the Secretariat please give unambiguous advice  
>> (preferably backed up by a letter from the Korean embassy) to  attendees?
>
>It sounds like you might be safest contacting the Korean embassy 
>yourself and asking for a visa.  If they say you don't need one, you're 
>on firmer ground than if the IETF says you don't need one.

I would guess that the amount of "firmness" you get is probably the
same if you get an answer from the Secretariat, the Korean Consulate,
or your uncle Bob.  Since it seems to be a grey area, the determining
factor will likely be the whim of the immigration official (who I
imagine will likely be unmoved by your claims that you talked to
the Consulate (how would they be able to verify that?)

--Ken



From owner-ietf@ietf.org  Thu Jan 29 13:56:49 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07851
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 13:56:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmHG4-00005J-EB
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 13:51:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmH5Z-000832-Ic
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 13:40:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07194
	for <ietf@ietf.org>; Thu, 29 Jan 2004 13:40:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmH5Y-0005wr-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:40:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmH4a-0005re-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:39:29 -0500
Received: from ginger.cmf.nrl.navy.mil ([134.207.10.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmH3u-0005mW-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:38:46 -0500
Received: from cmf.nrl.navy.mil (elvis.cmf.nrl.navy.mil [134.207.10.38])
	(authenticated bits=0)
	by ginger.cmf.nrl.navy.mil (8.12.7/8.12.7) with ESMTP id i0TIcgRr021303
	for <ietf@ietf.org>; Thu, 29 Jan 2004 13:38:43 -0500 (EST)
Message-Id: <200401291838.i0TIcgRr021303@ginger.cmf.nrl.navy.mil>
To: ietf@ietf.org
Subject: Re: visa requirements (US citizens) 
In-Reply-To: Message from Vijay Devarapalli <vijayd@iprg.nokia.com> 
   of "Thu, 29 Jan 2004 10:33:40 PST." <40195204.5060004@iprg.nokia.com> 
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4
	WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d
	gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;Mv(aiO2z~9n.w?@\>kEpSD@*e`
Date: Thu, 29 Jan 2004 13:38:42 -0500
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
X-Spam-Score: () hits=0 User Authenticated
X-Virus-Scanned: NAI Completed
X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

>I am an Indian national (which means I need a visa). I know for a fact 
>that I need a produce an invitation letter to get a visa.

Please note that I did qualify my note by saying "US citizens".  Of
course entry requirements differ between countries.  My point was that
US citizens do not need an invitation letter to obtain a visa (from my
reading of the visa application form and the on-line documentation).

--Ken



From owner-ietf@ietf.org  Thu Jan 29 13:56:50 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07868
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 13:56:50 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmHG3-0008WJ-Vu
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 13:51:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmH1h-0007vu-U0
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 13:36:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07061
	for <ietf@ietf.org>; Thu, 29 Jan 2004 13:36:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmH1g-0005Zg-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:36:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmH0v-0005T4-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:35:42 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmH04-0005DG-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:34:48 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0TIXrG08713;
	Thu, 29 Jan 2004 10:33:53 -0800
X-mProtect: <200401291833> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp141200.americas.nokia.com (172.18.141.200, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdD8GJaB; Thu, 29 Jan 2004 10:33:51 PST
Message-ID: <40195204.5060004@iprg.nokia.com>
Date: Thu, 29 Jan 2004 10:33:40 -0800
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ken Hornstein <kenh@cmf.nrl.navy.mil>
CC: Eric Burger <eburger@snowshore.com>, ietf@ietf.org
Subject: Re: visa requirements (US citizens)
References: <200401291648.i0TGm9Rr019515@ginger.cmf.nrl.navy.mil>
In-Reply-To: <200401291648.i0TGm9Rr019515@ginger.cmf.nrl.navy.mil>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I am an Indian national (which means I need a visa). I know for a fact 
that I need a produce an invitation letter to get a visa.

Vijay

Ken Hornstein wrote:
>>How about this for a twist:  if you ask for an invitation (required for a
>>visa), you are told you really, really don't need it.  When I requested a
>>visa from TTA, this is the response I got.  Has anyone succeeded in getting
>>a letter?
> 
> 
> When I downloaded the visa application form (and checked the Korean Embassy
> web page), it did not indicate that an invitation letter was required from
> anyone in Korea.  What it did indicate was required (and you can check
> the web page yourself at http://www.koreaembassy.org/visiting/eng_visas.cfm),
> is the following (assuming you're a US citizen and you get a "business" visa):
> 
> - Visa application form
> - One passport-sized photo
> - US Passport
> - Original copy of company letter on company letterhead _signed by your
>   employer_ (emphasis mine), stating the purpose, name and duration
> - $ 45.00 USD application fee.
> - And a prepaid postage return envelope (if applying by mail)
> 
> While the question of whether or not a visa is required has not in my mind
> been completely answered, it appears definite to me that you don't need
> an invitation letter from TTA to get one.
> 
> --Ken
> 




From owner-ietf@ietf.org  Thu Jan 29 14:03:57 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08628
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 14:03:57 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmHG4-00006E-Ti
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 13:51:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmH8V-0008A9-JX
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 13:43:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07308
	for <ietf@ietf.org>; Thu, 29 Jan 2004 13:43:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmH8U-0006G4-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:43:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmH7X-00069Y-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:42:31 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmH7N-000644-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:42:21 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AmH7M-0005pV-00; Thu, 29 Jan 2004 13:42:20 -0500
Date: Thu, 29 Jan 2004 13:42:20 -0500
From: John C Klensin <john-ietf@jck.com>
To: John Stracke <jstracke@centive.com>, ietf@ietf.org
Subject: Re: Do we or don't we need a visa for the Korean IETF?
Message-ID: <83652145.1075383740@scan.jck.com>
In-Reply-To: <40194720.8040708@centive.com>
References: <73DC462E-5281-11D8-B733-000A95DBDB84@isi.edu>
 <40194720.8040708@centive.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Thursday, 29 January, 2004 12:47 -0500 John Stracke 
<jstracke@centive.com> wrote:

> Aaron Falk wrote:
>
>> This is insane.  Can the Secretariat please give unambiguous
>> advice   (preferably backed up by a letter from the Korean
>> embassy) to  attendees?
>
> It sounds like you might be safest contacting the Korean
> embassy yourself and asking for a visa.  If they say you don't
> need one, you're on firmer ground than if the IETF says you
> don't need one.

John,

As I understand it, different embassies and consulates are 
giving different advice, or advice that is as ambiguous as what 
is on the web pages (which, for example, do not mention the 
"non-profit" categories that have been discussed on this list), 
with further ambiguities as to what the IETF is.  I have now had 
one consular official tell me that they _will not_ issue a visa 
if one appears to be unnecessary, even if one shows up with the 
form, the picture, and the $45 (in my experience, a fairly high 
fee as visas go).   So even the "to be safe, get a visa" advice 
that has appeared on the list may not be useful.

My own experience is that the Korean immigration folks have been 
pretty relaxed when one says one is arriving for a 
"professional" meeting and a short (under a week or two) stay -- 
I've never been asked about a visa and I've never been 
questioned in any detail about, e.g., whether "business" might 
be discussed at such a meeting.   But, as others have pointed 
out, there may be some risk of addition scrutiny in reaction to 
increase border nonsense by the US.

To make things even more exciting, those "business" category 
visas apparently require a notarized letter of invitation -- 
apparently hard copy, wet signatures, raised seal -- which can't 
usefully be posted on the web.

So I have to agree with Aaron's analysis.  This has reached the 
point of being insane.  Can the secretariat --or whomever is 
responsible for agreeing to this meeting-- get a definitive 
statement from an authoritative entity, mentioning the IETF 
meeting by name, and get it up on the web site in image form, so 
that we can all print it out and bring it with us (either to the 
embassy/ consulate if a visa is needed or to show to the 
immigration official if not).  I think, given this level of 
confusion, that statement needs to be from the Korean Foreign 
Ministry or equivalent, not whomever answers the phone at a 
random time in some embassy or consulate.

And, if that is not possible, is it time that we hear about the 
contingency plan for holding this meeting somewhere else?

thanks,
   john




From owner-ietf@ietf.org  Thu Jan 29 14:04:40 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08659
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 14:04:40 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmHPj-0001C7-1i
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 14:01:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmHN4-0000i1-DZ
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 13:58:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08020
	for <ietf@ietf.org>; Thu, 29 Jan 2004 13:58:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmHN3-0000Ke-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:58:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmHM1-00006Z-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:57:30 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmHKz-0007gN-00
	for IETF@ietf.org; Thu, 29 Jan 2004 13:56:26 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AmHKz-00067e-00; Thu, 29 Jan 2004 13:56:25 -0500
Date: Thu, 29 Jan 2004 13:56:25 -0500
From: John C Klensin <john-ietf@jck.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-ID: <84497390.1075384585@scan.jck.com>
In-Reply-To: <20040129162952.6110386AEA@mercury.lcs.mit.edu>
References: <20040129162952.6110386AEA@mercury.lcs.mit.edu>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Noel,

(1) Sorry to have misconstrued your comments.

(2) Yes, I was trying to refer to situations in which each of 
the hosts on a multihomed LAN has exactly one address, largely 
because of bad experiences with client machines running 
widely-used junk software trying to handle multiple addresses 
(in IPv4) on the same interface.  I know of only two ways to 
accomplish that "exactly one address on local host" criterion: 
(i) use of NATs (even if only on a one-one basis) to make 
different external addresses appear as a single set of addresses 
on the LAN and (ii) use of globally-routed, 
provider-independent, addresses for the LAN.

I am now going to drop out of this discussion since I don't seem 
to be in sufficiently good shape this week to make comments 
sufficiently precise that I don't just create more confusion.

     john


--On Thursday, 29 January, 2004 11:29 -0500 Noel Chiappa 
<jnc@mercury.lcs.mit.edu> wrote:

>     > From: John C Klensin <john-ietf@jck.com>
>
>     > Of course, multiple A records works, is out there, and
> have worked for     > years. But they worked better before we
> introduced routers (i.e., when     > the hosts with multiple A
> records really had interfaces on different     > networks).
> Today, it effectively implies having multiple addresses on
> > an interface and multiple "local" address prefixes running
> around on     > the same physical LAN segment.
>     > ...
>     > Perhaps more important, as Noel points out, it doesn't
> scale very well,     > at least in terms of the routing fabric.
>
> Sorry? What I said doesn't work for the routing, in terms of
> scaling to many small sites, is for a multi-homed site to have
> a single address prefix, which is then globally advertised.
> (That's the most common tack for multi-homing support in IPv4
> to date, which is what you were talking about.)
>
> Having multiple addresses for a host (which has only a single
> physical interface, but which is in a site which is
> multi-homed) is in fact the only approach whose effects on the
> routing does scale (within anything like the current routing
> architecture, i.e. packets which include only source and
> destination addresses, as opposed to a source route).
>
>
>     > as I tried to point out, address preservation policies
> have had     > trickle-down effects that make it impractical
> for small enterprises.
>
> It is an interesting point (as Daniel Senie also just pointed
> out) that multiple addresses -> faster consumption of the
> address space.
>
> However, since to avoid a size explosion in the routing
> tables, those multiple addresses do have to be
> connectivity-dependent (political translation -
> "provider-dependent"), I don't see how address preservation
> policies have made this approach "impractical for small
> enterprises". My understanding of current allocation policies
> is that ISP's can get enough addresses to cover their
> customers. If company X is a customer of both ISP P and ISP Q,
> I would assume that both P and Q don't have a problem getting
> enough space to cover their customers - including X.
>
> (Or were you speaking of the "one address block, globally
> advertized"?)
>
> 	Noel
>







From owner-ietf@ietf.org  Thu Jan 29 14:07:17 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08784
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 14:07:17 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmHRe-0001mb-8o
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 14:03:18 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmHPt-0001H8-VD
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 14:01:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08349
	for <ietf@ietf.org>; Thu, 29 Jan 2004 14:01:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmHPs-0000qk-00
	for ietf@ietf.org; Thu, 29 Jan 2004 14:01:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmHOu-0000gW-00
	for ietf@ietf.org; Thu, 29 Jan 2004 14:00:29 -0500
Received: from letters.cs.ucsb.edu ([128.111.41.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmHNw-0000UG-00
	for ietf@ietf.org; Thu, 29 Jan 2004 13:59:28 -0500
Received: from jackson.cs.ucsb.edu (jackson [128.111.52.10])
	by letters.cs.ucsb.edu (8.11.7+Sun/8.11.7) with ESMTP id i0TIxPc06125
	for <ietf@ietf.org>; Thu, 29 Jan 2004 10:59:26 -0800 (PST)
Received: from jackson.cs.ucsb.edu (localhost [127.0.0.1])
	by jackson.cs.ucsb.edu (8.12.8/8.11.6) with ESMTP id i0TIxOti008977
	for <ietf@ietf.org>; Thu, 29 Jan 2004 10:59:24 -0800
Received: from localhost (almeroth@localhost)
	by jackson.cs.ucsb.edu (8.12.8/8.12.8/Submit) with ESMTP id i0TIxO71008973
	for <ietf@ietf.org>; Thu, 29 Jan 2004 10:59:24 -0800
X-Authentication-Warning: jackson.cs.ucsb.edu: almeroth owned process doing -bs
Date: Thu, 29 Jan 2004 10:59:24 -0800 (PST)
From: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
To: ietf@ietf.org
Subject: Visa for Korea (same as Vienna)
Message-ID: <Pine.LNX.4.44.0401291058450.8971-100000@jackson.cs.ucsb.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0401291058452.8971@jackson.cs.ucsb.edu>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


My suggestion:  do what you did for Vienna.  Vienna has the same rules:

U.S. citizens in possession of a valid U.S.-passport do not need a visa if traveling
to Austria as a tourist for a period not to exceed 90 days (visa waiver program).

-Kevin





From owner-ietf@ietf.org  Thu Jan 29 15:02:21 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13231
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 15:02:20 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmI7H-00089A-Qw
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 14:46:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmFyO-000706-1c
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 12:29:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03248
	for <ietf@ietf.org>; Thu, 29 Jan 2004 12:28:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmFyN-0004nx-00
	for ietf@ietf.org; Thu, 29 Jan 2004 12:28:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmFxC-0004YZ-00
	for ietf@ietf.org; Thu, 29 Jan 2004 12:27:47 -0500
Received: from shield.kudpc.kyoto-u.ac.jp ([130.54.9.41])
	by ietf-mx with smtp (Exim 4.12)
	id 1AmFvl-00047F-00
	for ietf@ietf.org; Thu, 29 Jan 2004 12:26:17 -0500
Received: by shield.kudpc.kyoto-u.ac.jp; id CAA01471; Fri, 30 Jan 2004 02:26:10 +0900
Received: from localhost(127.0.0.1) by shield.kudpc.kyoto-u.ac.jp via csmap (V4.1)
	id srcAAANday2c; Fri, 30 Jan 04 02:26:09 +0900
Received: from mbox.kudpc.kyoto-u.ac.jp (mbox.kudpc.kyoto-u.ac.jp [130.54.9.32])
	by shield.kudpc.kyoto-u.ac.jp (8.11.3/8.11.3) with ESMTP id i0THQ8b01448;
	Fri, 30 Jan 2004 02:26:09 +0900 (JST)
Received: from blackpearl.arifumi.net (p29ded5.kyotac00.ap.so-net.ne.jp [218.41.222.213])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by mbox.kudpc.kyoto-u.ac.jp (Postfix) with ESMTP
	id 587AD48C097; Fri, 30 Jan 2004 02:26:08 +0900 (JST)
Date: Fri, 30 Jan 2004 02:25:37 +0900
From: arifumi <a@arifumi.net>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: Franck Martin <franck@sopac.org>, ietf@ietf.org
Subject: Re: Wiki RFC
Message-Id: <20040130022537.5a384b22@blackpearl.arifumi.net>
In-Reply-To: <1422526635.1075310715@localhost>
References: <1075250978.2820.55.camel@franck-lxnb.sopac.org.fj>
	<1422526635.1075310715@localhost>
X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

hi,

> AFAIK, no.
> Do you know of any effort to make stable documentation for the WIKI syntax 
> & functionality, or is it just "use the Source, Luke"?

FYI,
there are some efforts,
http://www.usemod.com/cgi-bin/mb.pl?WikiMarkupStandard

and Japanese Wiki syntax standardization,
http://lab.lolipop.jp/fswiki/wiki.cgi/wikistandard
(Japanese only)
-- 
/arifumi





From owner-ietf@ietf.org  Thu Jan 29 15:11:57 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14552
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 15:11:57 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmIAd-0008VT-R4
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 14:49:47 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmI7b-0008FQ-9C
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 14:46:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11908
	for <ietf@ietf.org>; Thu, 29 Jan 2004 14:46:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmI7a-0006z2-00
	for ietf@ietf.org; Thu, 29 Jan 2004 14:46:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmI6Z-0006rD-00
	for ietf@ietf.org; Thu, 29 Jan 2004 14:45:36 -0500
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmI5m-0006cs-00
	for ietf@ietf.org; Thu, 29 Jan 2004 14:44:46 -0500
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 29 Jan 2004 20:44:57 +0100
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by ams-msg-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i0TJhWCX002533;
	Thu, 29 Jan 2004 20:43:53 +0100 (MET)
Received: from cisco.com ([10.25.65.182])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AQK13842;
	Thu, 29 Jan 2004 11:40:06 -0800 (PST)
Date: Thu, 29 Jan 2004 14:40:02 -0500
Subject: Re: Visa for Korea (same as Vienna)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: ietf@ietf.org
To: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <Pine.LNX.4.44.0401291058450.8971-100000@jackson.cs.ucsb.edu>
Message-Id: <EE59A9E8-5292-11D8-B46B-000A95E35274@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Thursday, January 29, 2004, at 01:59 PM, Kevin C. Almeroth wrote:
> U.S. citizens in possession of a valid U.S.-passport do not need a 
> visa if traveling
> to Austria as a tourist for a period not to exceed 90 days (visa 
> waiver program).

We're not traveling as tourists, strictly speaking.

The same situation exists with Americans entering Canada, believe it
or not.  If you're American and enter Canada to do commercial business
(i.e. you're selling stuff, or you're being paid by a Canadian firm,
etc.) you need a Canadian work permit.  I used to cross the border for
work quite often (American employee of Canadian firm) and usually said
that I was attending an academic conference, which did the trick.

Melinda




From owner-ietf@ietf.org  Thu Jan 29 15:23:01 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15959
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 15:23:01 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmITO-000169-Bu
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 15:09:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmIQw-0000qS-Ai
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 15:06:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13784
	for <ietf@ietf.org>; Thu, 29 Jan 2004 15:06:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmIQu-00024a-00
	for ietf@ietf.org; Thu, 29 Jan 2004 15:06:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmIPz-0001vh-00
	for ietf@ietf.org; Thu, 29 Jan 2004 15:05:40 -0500
Received: from firecrest.mail.pas.earthlink.net ([207.217.121.247])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmIP8-0001lc-00
	for ietf@ietf.org; Thu, 29 Jan 2004 15:04:46 -0500
Received: from [38.119.96.105] (helo=[192.168.0.2])
	by firecrest.mail.pas.earthlink.net with asmtp (Exim 3.33 #1)
	id 1AmIP7-0005Wy-00
	for ietf@ietf.org; Thu, 29 Jan 2004 12:04:46 -0800
Date: Thu, 29 Jan 2004 15:01:37 -0500
From: Gene Gaines <gene.gaines@gainesgroup.com>
Organization: Gaines Group
X-Priority: 3 (Normal)
Message-ID: <2226201457.20040129150137@gainesgroup.com>
To: ietf@ietf.org
Subject: Re: Visa for Korea
In-Reply-To: <Pine.LNX.4.44.0401291058450.8971-100000@jackson.cs.ucsb.edu>
References: <Pine.LNX.4.44.0401291058450.8971-100000@jackson.cs.ucsb.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: e892362a6fa8b5d372cc1e1b0924a179239a348a220c2609a8f447e190b56b1cae50c48a90e14ec3a7ce0e8f8d31aa3f350badd9bab72f9c350badd9bab72f9c
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

An attempt to attenuate the visa discussion.

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

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

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

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

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






From owner-ietf@ietf.org  Thu Jan 29 15:25:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16172
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 15:25:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmIf7-0002Zx-Pn
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 15:21:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmIeA-0002Re-KN
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 15:20:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15781
	for <ietf@ietf.org>; Thu, 29 Jan 2004 15:20:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmIe9-00048T-00
	for ietf@ietf.org; Thu, 29 Jan 2004 15:20:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmIdH-0003wU-00
	for ietf@ietf.org; Thu, 29 Jan 2004 15:19:23 -0500
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmIc4-0003ig-00
	for ietf@ietf.org; Thu, 29 Jan 2004 15:18:08 -0500
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.1.3)
  with ESMTP-TLS id 670763; Thu, 29 Jan 2004 14:18:08 -0600
Message-ID: <40196A7E.6080102@ehsco.com>
Date: Thu, 29 Jan 2004 14:18:06 -0600
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: ietf@ietf.org
Subject: Re: SUMMARY: Processing of expired Internet-Drafts
References: <1425560006.1075313748@localhost>
In-Reply-To: <1425560006.1075313748@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On 1/28/2004 8:15 PM, Harald Tveit Alvestrand wrote:

> Conclusions, all mine:
> 
> - Documenting current procedures is good. - We won't expire tombstones.
> They're not a big enough problem yet. - We'll think about naming
> tombstones something else than the exact draft name (for instance
> draft-whatever-version-nn-expired.txt???) - We'll note the issue of
> referencing names without the version number as input for thinking
> about overhauling the whole I-D system. But that won't happen very
> quickly - it "mostly works".
> 
> Seems to make sense?

How about using the draft name without a version number as placeholder?
That placeholder file can either reference the current version, or it can
contain the tombstone text. For example, draft-whatever.txt can either
contain a pointer to draft-whatever-nn.txt or can contain text that the
last version of that I-D was -nn but has since expired.

That eliminates naming collisions, allows for mirroring based on the
filedate alone, and provides a running reference to the latest version
which can either be fetched directly (if active) or can be retrieved from
an archival system (if expired). Other useful information could also be
provided in the placeholder, such as referencing the I-D's current
progress through the channels, referencing any RFC which may have been
published, and so forth.

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



From owner-ietf@ietf.org  Thu Jan 29 16:56:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21890
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 16:56:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmJzN-0007Qf-KG
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 16:46:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmJyq-0007HJ-G4
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 16:45:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21233
	for <ietf@ietf.org>; Thu, 29 Jan 2004 16:45:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmJyo-0007nS-00
	for ietf@ietf.org; Thu, 29 Jan 2004 16:45:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmJxj-0007Ts-00
	for ietf@ietf.org; Thu, 29 Jan 2004 16:44:37 -0500
Received: from trout.cpsr.org ([66.180.229.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmJve-0006ra-00
	for ietf@ietf.org; Thu, 29 Jan 2004 16:42:26 -0500
Received: from guppylake.com (trout [66.180.229.5])
	by trout.cpsr.org (8.12.8p2/8.12.8) with ESMTP id i0TLg03i063820;
	Thu, 29 Jan 2004 13:42:15 -0800 (PST)
	(envelope-from nsb@guppylake.com)
Date: Thu, 29 Jan 2004 16:41:59 -0500
Subject: Re: visa requirements (US citizens) 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: "Eric Burger" <eburger@snowshore.com>, ietf@ietf.org
To: Ken Hornstein <kenh@cmf.nrl.navy.mil>
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <200401291648.i0TGm9Rr019515@ginger.cmf.nrl.navy.mil>
Message-Id: <F78F9E6D-52A3-11D8-85D8-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

One more thing:  They won't take a check.  Cash and money order are the 
only things you can send 'em.  -- nathaniel

On Thursday, January 29, 2004, at 11:48  AM, Ken Hornstein wrote:

>> How about this for a twist:  if you ask for an invitation (required 
>> for a
>> visa), you are told you really, really don't need it.  When I 
>> requested a
>> visa from TTA, this is the response I got.  Has anyone succeeded in 
>> getting
>> a letter?
>
> When I downloaded the visa application form (and checked the Korean 
> Embassy
> web page), it did not indicate that an invitation letter was required 
> from
> anyone in Korea.  What it did indicate was required (and you can check
> the web page yourself at 
> http://www.koreaembassy.org/visiting/eng_visas.cfm),
> is the following (assuming you're a US citizen and you get a 
> "business" visa):
>
> - Visa application form
> - One passport-sized photo
> - US Passport
> - Original copy of company letter on company letterhead _signed by your
>   employer_ (emphasis mine), stating the purpose, name and duration
> - $ 45.00 USD application fee.
> - And a prepaid postage return envelope (if applying by mail)
>
> While the question of whether or not a visa is required has not in my 
> mind
> been completely answered, it appears definite to me that you don't need
> an invitation letter from TTA to get one.
>
> --Ken
>
>
>




From owner-ietf@ietf.org  Thu Jan 29 17:41:11 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24897
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 17:41:11 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmKkM-0005yu-30
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 17:34:50 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmKjD-0005qO-V0
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 17:33:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24139
	for <ietf@ietf.org>; Thu, 29 Jan 2004 17:33:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmKjC-0006ip-00
	for ietf@ietf.org; Thu, 29 Jan 2004 17:33:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmKiG-0006c9-00
	for ietf@ietf.org; Thu, 29 Jan 2004 17:32:40 -0500
Received: from mail-dark.research.att.com ([192.20.225.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmKhW-0006QX-00; Thu, 29 Jan 2004 17:31:54 -0500
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by mail-dark.research.att.com (Postfix) with ESMTP id 81A09E812C;
	Thu, 29 Jan 2004 17:32:27 -0500 (EST)
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-green.research.att.com (Postfix) with ESMTP id 2EB07F3A91;
	Thu, 29 Jan 2004 17:28:47 -0500 (EST)
Received: from berkshire.research.att.com (raptor.research.att.com [135.207.23.32])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id i0TMVMZ18391;
	Thu, 29 Jan 2004 17:31:22 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id 651107B43; Thu, 29 Jan 2004 17:31:22 -0500 (EST)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: Aaron Falk <falk@ISI.EDU>
Cc: Support Online <iesg-secretary@ietf.org>, ietf@ietf.org, iesg@ietf.org
Subject: Re: Do we or don't we need a visa for the Korean IETF? 
In-Reply-To: Your message of "Thu, 29 Jan 2004 09:34:55 PST."
             <73DC462E-5281-11D8-B733-000A95DBDB84@isi.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 29 Jan 2004 17:31:22 -0500
Message-Id: <20040129223122.651107B43@berkshire.research.att.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <73DC462E-5281-11D8-B733-000A95DBDB84@isi.edu>, Aaron Falk writes:
>This is insane.  Can the Secretariat please give unambiguous advice  
>(preferably backed up by a letter from the Korean embassy) to  
>attendees?
>

As I posted to the IETF list a couple of days ago, the company that 
AT&T uses for advice on such things suggested that I get a visa.  (Not 
that they sounded too sure about it...)  I've gotten a few responses 
that suggest that they're being prudent.

I've sent in my forms to get a Visa -- we'll see what happens.

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





From owner-ietf@ietf.org  Thu Jan 29 20:10:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03934
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 20:10:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmN31-0008N2-LP
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 20:02:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmMzg-0007uT-Se
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 19:58:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03602
	for <ietf@ietf.org>; Thu, 29 Jan 2004 19:58:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmMzf-0004qL-00
	for ietf@ietf.org; Thu, 29 Jan 2004 19:58:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmMyh-0004jx-00
	for ietf@ietf.org; Thu, 29 Jan 2004 19:57:48 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmMyF-0004cI-00
	for ietf@ietf.org; Thu, 29 Jan 2004 19:57:19 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 04A2361BEC
	for <ietf@ietf.org>; Fri, 30 Jan 2004 01:56:49 +0100 (CET)
Date: Thu, 29 Jan 2004 16:24:37 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Very summarized version of the "mission statement" discussion
Message-ID: <1505287168.1075393477@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========85BD278A577F9FE11067=========="
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

Hitting some very high points....

- Talking is important. It's what the IETF does.

- Standards are one, but not the only, output of that talking.

- Publishing good ideas is important. It's what the RFC Editor does.

- Mission statements are dangerous. Discussing them makes you have to admit =

that you disagree. Hiding the disagreement requires making the mission=20
statements say nothing.

- Anything is possible to misunderstand. Especially if it's short.

We'll see where we can get from there.

                 Harald


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

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

iD8DBQFAGaRKOMj+2+WY0F4RAvhyAJ0ejJzFg5ptdwyBphyX9E5K5m2NRQCfaR50
I10vbQhvLmqv1Vsubb9ydKY=
=KMqj
-----END PGP SIGNATURE-----

--==========85BD278A577F9FE11067==========--




From owner-ietf@ietf.org  Thu Jan 29 23:48:26 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11678
	for <ietf-web-archive@odin.ietf.org>; Thu, 29 Jan 2004 23:48:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmQLT-0000dA-T8
	for ietf-list@asgard.ietf.org; Thu, 29 Jan 2004 23:33:31 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmQL2-0000Pq-JR
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 23:33:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10927
	for <ietf@ietf.org>; Thu, 29 Jan 2004 23:33:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmQL0-0006f6-00
	for ietf@ietf.org; Thu, 29 Jan 2004 23:33:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmQJz-0006XA-00
	for ietf@ietf.org; Thu, 29 Jan 2004 23:32:00 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmQJW-0006Pg-00
	for ietf@ietf.org; Thu, 29 Jan 2004 23:31:30 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
  by sj-iport-5.cisco.com with ESMTP; 29 Jan 2004 20:31:17 -0800
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i0U4UxGK019950;
	Thu, 29 Jan 2004 20:30:59 -0800 (PST)
Received: from CSCOAMERA19540.cisco.com (sjc-vpn4-1023.cisco.com [10.21.83.254])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id APU22449;
	Thu, 29 Jan 2004 20:30:57 -0800 (PST)
Message-Id: <6.0.1.1.2.20040129213127.047b0a08@mira-sjc5-b.cisco.com >
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 29 Jan 2004 19:36:39 -0500
To: Leslie Daigle <leslie@thinkingcat.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: The IETF Mission
Cc: ietf@ietf.org
In-Reply-To: <401946E8.9030207@thinkingcat.com>
References: <405441934.1074293627@localhost>
 <Pine.LNX.4.44.0401171150270.11109-100000@netcore.fi>
 <6.0.1.1.2.20040117103457.0466fc00@mira-sjc5-b.cisco.com>
 <401946E8.9030207@thinkingcat.com>
Mime-Version: 1.0
Content-Type: multipart/signed;
 boundary="==----==--=--===-=----=----=-==---==--=--===-===";
 protocol="application/pgp-signature"; micalg=pgp-sha1
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=4.1 required=5.0 tests=AWL,DATE_IN_PAST_03_06,
	FORGED_MUA_EUDORA,INVALID_MSGID autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

--==----==--=--===-=----=----=-==---==--=--===-===
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 12:46 PM 1/29/2004, Leslie Daigle wrote:
>I'd like to come back to this point, and try a slightly different direction:
>
>Fred Baker wrote:
>>>"The purpose of the IETF is to create high quality, relevant, and timely 
>>>standards for the Internet."
>>
>>I think I would state it in these words:
>>   "The Internet Engineering Task Force provides a forum for the
>>   discussion and development of white papers and specifications
>>   for the engineering issues of the Internet."
>
>This seems like a reasonable characterization of the output of the IETF.
>
>However, it doesn't seem to capture some of the scoping/delimiting that 
>the original text did - does the IETF discuss any and all such issues?  Is 
>it trying to achieve anything in particular by documenting things?  (How) 
>can we detect that there are issues we should be discussing and can't?
>
>(How) would you add to your text to provide some boundaries/guiding lines?

Thinking out loud here, plenty of room for all to chime in. The key 
differences, if there are any, between IETF and NANOG and her sisters, and 
between IETF and IRTF, are:

Operationally, IETF discussions address advice to operators (service 
provider and enterprise, the latter being a group that our operational 
friends sometimes seem to forget) from the individuals who participated in 
the discussion, as opposed to discussions among operators. The latter are 
perfectly welcome and do happen (ptomaine, v6ops), but I would characterize 
them as often more uniquely the domain of NANOG and her sisters.

 From a research/innovation perspective, I would characterize the IETF as 
creating solutions that we in some sense know how to build, as opposed to 
playing with and learning about possible solutions that we are unsure how 
to properly build. When we built OSPF, to name one example, it was not from 
whole cloth; the algorithms were already well defined - we were simply 
figuring out how to use them. You can say quite accurately that we make our 
share of mistakes even in what we supposedly know how to do, but at least 
we can recognize when we do so. In research, 90% of ideas are truly bad 
ideas, and the other 10% are testing grounds for bits and pieces that will 
some day contribute to the solution. That is *normal*; research is 
*supposed* to be risky, to be "out of the box". When the researchers have 
done their job and the engineers come to build a solution for the Internet, 
the engineers rarely if ever simply adopt research proposals. But they are 
guided by the wisdom learned in that community, and if they lack that 
compass, they quickly are lost.

I am reminded of an academic researcher who once complained to me that "you 
write too many RFCs. You write the RFC, and we start our research on that 
RFC. We get part way into it, and you publish a new RFC." I replied to him 
that the idea is that he is supposed to do the research *before* I write 
the RFC, so that when I write the RFC I write it once and it is right. If 
he think he is doing the research afterwards, then in reality I am doing 
the research and the engineering together, in my customer's networks, and 
he is doing Quality Assurance.

We need the researchers, desperately, but not to do the engineering. We 
need them to tell us how, to be the pathfinders. We need the operational 
folks equally desperately. If nothing else, they are the canaries in the 
mine shaft, and they often can tell us what the mother lode looks like when 
we see it in the rough. And yes, we need the engineers that are paid by the 
vendors. Their marketing people are IMHO unwelcome, because they set one 
person against another for their company's gain, and a house divided 
against itself cannot stand. But if you think for a minute that the 
operators and the researchers can do this Internet thing without the 
products the vendors build, and the engineers that build them, you are 
sadly mistaken.

I am reminded of comments that I have heard in various parts of each of 
those organizations. Dave Clark, speaking to the Internet II Joint Techs 
last Tuesday, said that the IETF had forsaken innovation, and had been 
overtaken by the [evil] vendors. I submit that we - the academics, 
students, and researchers, the edge network operators that deliver 
applications running in a network, the transit network operators that 
deliver bandwidth to interconnect edges, and the vendors, whose products 
inhabit all of those networks - may not all meet together at the same time 
or with the same purpose, and we certainly all see things from different 
perspectives and in different ways. To that extent, perhaps he has a point. 
But we each play a part in the play.

Our strength and our value is not, however, that those of our particular 
stripe are somehow better than others, or more needed, or have a better 
level of understanding - that rock breaks scissors, that scissors cut 
paper, or that paper covers the rock. Our strength, rather, is that we 
bring our various perspectives together, as a builder brings together brick 
and mortar, the flexible strength of the board, the mass of the hammer, and 
the steel of the nail, and build something that will withstand the test of 
operational experience.

Let me try to say all that succinctly:

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

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

Is that on target? Is it too many words? 
--==----==--=--===-=----=----=-==---==--=--===-===
Content-Type: application/pgp-signature

-----BEGIN PGP MESSAGE-----
Version: PGP 7.0.1

iQA/AwUBQBnRRm4xHWxyLJtDEQKfmwCfRmkX+jCmJhpBkJNFyXGOrmXagbEAn1vX
Y7sa/hUZoAIQsfr6mw7c6bcs
=gS+b
-----END PGP MESSAGE-----

--==----==--=--===-=----=----=-==---==--=--===-===--




From owner-ietf@ietf.org  Fri Jan 30 03:44:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02629
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 03:44:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmU7M-0004J1-5O
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 03:35:12 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmU6B-00046q-Rg
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 03:33:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02145
	for <ietf@ietf.org>; Fri, 30 Jan 2004 03:33:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmU69-0003kN-00
	for ietf@ietf.org; Fri, 30 Jan 2004 03:33:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmU5D-0003e9-00
	for ietf@ietf.org; Fri, 30 Jan 2004 03:33:00 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmU4Q-0003Ww-00
	for IETF@ietf.org; Fri, 30 Jan 2004 03:32:10 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0U8WNKH031537;
	Fri, 30 Jan 2004 09:32:33 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <4018FFFB.2010201@stewart.chicago.il.us>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us> <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us> <654669B6-524E-11D8-98F9-000A95CD987A@muada.com> <4018FFFB.2010201@stewart.chicago.il.us>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F2D4652B-52F9-11D8-98F9-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Death of the Internet - details at 11
Date: Fri, 30 Jan 2004 08:57:28 +0100
To: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

[I'm not going to get into _all_ the details as this probably isn't the 
right place for it.]

On 29-jan-04, at 13:43, Randall R. Stewart (home) wrote:

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

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

Sure. But wouldn't it be better to keep the number of places where 
changes are necessary to an absolute minimum? I still have to use IPv4 
for 90% of my applications despite the fact that all the boxes I 
regularly use run IPv6 because each and everyone application that uses 
the socket API must be changed to support IPv6. Sure, it's only a few 
lines, but progress in this area is extremely slow.

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

As far as I can tell, most of the multi6 wg participants are thinking 
along similar lines.

>> Doing WWW-style HTTP (lots of concurrent sessions) with SCTP would be 
>> nonsense, this is where the feature where multiple streams are 
>> multiplexed over a single session would be extremely useful.

> Yes.. if you wanted to do HTTP over SCTP and use features such
> as streams you WOULD WANT to extend HTML so that you could
> have the client "get pages" on particular streams...

Why extend the markup language?

HTTP has supported sessions that stay alive so they can be used for 
more than just one operation for many years now. The trouble is that 
you get head of line blockage if you fetch all the elements that make 
up a WWW page in serial fashion. Being able to multiplex different 
streams (within an SCTP session) that all fetch elements simultenously 
would fix this. This of course requires changes to both HTTP clients 
and servers, but it should otherwise be transparent to the user.

>> But then you'll have to run services on both TCP and SCTP pretty much 
>> forever. Not a good thing.

> Just like we are stuck with IPv4 "forever" as well...  Its pretty much
> a given.. once a new technology comes along it is a slow gradual 
> transition not
> a mass move. IPv6 as been out since 1993 and we are not only 11 years 
> into
> the migration.. it will all happen eventually..

Actually the oldest RFC with IPv6 specs that I know of is from december 
1995, so it's "only" 8 years. And IPv6 implementations from before this 
century (give or take) are too immature to be usable. Even today there 
are some significant hurdles that must be cleared up before any serious 
migration can start.

Anyway, with IPv6 the address format is fundamentally incompatible with 
that of IPv4 so there is no choice but running them concurrently during 
the transition period. A new multihoming-capable transport protocol 
doesn't have to be incompatible with existing TCP so this situation is 
avoidable here.




From owner-ietf@ietf.org  Fri Jan 30 05:49:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07230
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 05:49:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmW5H-0002Et-GF
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 05:41:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmW59-00027s-I9
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 05:41:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07013
	for <ietf@ietf.org>; Fri, 30 Jan 2004 05:41:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmW57-0003kL-00
	for ietf@ietf.org; Fri, 30 Jan 2004 05:41:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmW48-0003d7-00
	for ietf@ietf.org; Fri, 30 Jan 2004 05:40:01 -0500
Received: from kc-msxproto2.kc.umkc.edu ([134.193.143.155])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmW3A-0003Vi-00
	for IETF@ietf.org; Fri, 30 Jan 2004 05:39:00 -0500
Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211]) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(6.0.3790.0);
	 Fri, 30 Jan 2004 04:39:01 -0600
x-mimeole: Produced By Microsoft Exchange V6.5.6944.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: Death of the Internet - details at 11
Date: Fri, 30 Jan 2004 04:34:09 -0600
Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B0110826D@KC-MAIL4.kc.umkc.edu>
Thread-Topic: Death of the Internet - details at 11
Thread-Index: AcPnDUnKmcj+C/E5SpelKAeszfR7FgADYp0A
From: "Ayyasamy, Senthilkumar  \(UMKC-Student\)" <saq66@umkc.edu>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>,
        "Randall R. Stewart \(home\)" <randall@stewart.chicago.il.us>
Cc: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
X-OriginalArrivalTime: 30 Jan 2004 10:39:01.0610 (UTC) FILETIME=[464E24A0:01C3E71D]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS 
	autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> That's why I think it makes more sense to backport the SCTP =
multihoming
> features to TCP so all TCP apps can use them without having to be
> changed, or even better: contain the changes in a separate shim layer
> so that all transport protocols can become address agile without =
having
> to be changed.
>
> As far as I can tell, most of the multi6 wg participants are thinking
> along similar lines.
=20
 1. multi6 has not done with architectural analysis. It is still unknown
    whether a multi-addressing or a id/loc split proposal(which includes
    shim layer) or something else is going to be accepted.=20
=20
 2. If you look at the ML archive, all possible proposals are discussed=20
    (which includes SCTP, SLAP or whatever..) So, your statement about=20
    *most* WG participants thinking along similar lines is wrong.
=20
 3. you should speak for yourself, not for others.
=20
=20

=20




From owner-ietf@ietf.org  Fri Jan 30 06:09:38 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09025
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 06:09:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmWSV-0005S3-Mu
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 06:05:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmWRd-0005Kf-4A
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 06:04:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08721
	for <ietf@ietf.org>; Fri, 30 Jan 2004 06:04:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmWRa-0007fu-00
	for ietf@ietf.org; Fri, 30 Jan 2004 06:04:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmWQU-0007Uf-00
	for ietf@ietf.org; Fri, 30 Jan 2004 06:03:06 -0500
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmWPR-0007CS-00
	for IETF@ietf.org; Fri, 30 Jan 2004 06:02:01 -0500
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i0UB2SKG033555;
	Fri, 30 Jan 2004 12:02:29 +0100 (CET)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <5EF7D95E17BDAD4A968C812E5ABC390B0110826D@KC-MAIL4.kc.umkc.edu>
References: <5EF7D95E17BDAD4A968C812E5ABC390B0110826D@KC-MAIL4.kc.umkc.edu>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <BA7AC46E-5313-11D8-98F9-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Death of the Internet - details at 11
Date: Fri, 30 Jan 2004 12:02:00 +0100
To: "Ayyasamy, Senthilkumar  \(UMKC-Student\)" <saq66@umkc.edu>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 30-jan-04, at 11:34, Ayyasamy, Senthilkumar ((UMKC-Student)) wrote:

>> As far as I can tell, most of the multi6 wg participants are thinking
>> along similar lines.

>  3. you should speak for yourself, not for others.

I think I used enough qualifiers to be able to make this statement. 
Obviously reality is more complex, so anyone interested should check 
out the drafts submitted to multi6 and/or the mailing list archive.




From owner-ietf@ietf.org  Fri Jan 30 07:22:27 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11754
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 07:22:27 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmXYF-0005cb-0R
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 07:15:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmXXC-0005OT-8O
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 07:14:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11470
	for <ietf@ietf.org>; Fri, 30 Jan 2004 07:14:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmXXB-0000dP-00
	for ietf@ietf.org; Fri, 30 Jan 2004 07:14:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmXWI-0000XT-00
	for ietf@ietf.org; Fri, 30 Jan 2004 07:13:11 -0500
Received: from stewart.chicago.il.us ([66.93.186.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmXVe-0000JN-00
	for IETF@ietf.org; Fri, 30 Jan 2004 07:12:30 -0500
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1])
	by stewart.chicago.il.us (8.12.8p1/8.12.8) with ESMTP id i0UCBvO6075193;
	Fri, 30 Jan 2004 06:11:57 -0600 (CST)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <401A4A0C.4010007@stewart.chicago.il.us>
Date: Fri, 30 Jan 2004 06:11:56 -0600
From: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Daniel Senie <dts@senie.com>
CC: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
Subject: Re: Death of the Internet - details at 11
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us> <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us> <654669B6-524E-11D8-98F9-000A95CD987A@muada.com> <4018FFFB.2010201@stewart.chicago.il.us> <6.0.1.1.2.20040129094026.0308c540@mail.amaranth.net>
In-Reply-To: <6.0.1.1.2.20040129094026.0308c540@mail.amaranth.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Daniel Senie wrote:

>
> I really don't see how this fits with routing policy. You appear to 
> make the assumption that a multi-homed site wants to use the multiple 
> paths as equals.
>

>
>
>
>>>> Now to take advantage of the stream feature you would need to do
>>>> more.. but for pure multi-homing one or two lines of change does
>>>> not seem that big of deal to me ...
>>>
>>>
>>>
>>> Doing WWW-style HTTP (lots of concurrent sessions) with SCTP would 
>>> be nonsense, this is where the feature where multiple streams are 
>>> multiplexed over a single session would be extremely useful.
>>
>>
>>
>> Yes.. if you wanted to do HTTP over SCTP and use features such
>> as streams you WOULD WANT to extend HTML so that you could
>> have the client "get pages" on particular streams... Then you could
>> have parrallel transfers over one association and not have to require
>> multiple TCP connections... this is optimal...
>>
>> Jana was doing some investagtion into this at the University of 
>> Deleware's Protocol
>> Engineering Lab.. don't know if he will be writting a paper on it.. I 
>> imagine so...
>>
>>>
>>>
>>>>> - no backward compatibility of any kind
>>>>
>>>
>>>> I am not sure what you mean by backward compatable? You definetly
>>>> can't have TCP and SCTP talk.. they are after all different 
>>>> protocols...
>>>> But if an application needs the redundancy move to it.. its there 
>>>> today
>>>> with about 2 lines of coding change...
>>>
>>>
>>>
>>> But then you'll have to run services on both TCP and SCTP pretty 
>>> much forever. Not a good thing.
>>
>>
>> Just like we are stuck with IPv4 "forever" as well...  Its pretty much
>> a given.. once a new technology comes along it is a slow gradual 
>> transition not
>> a mass move. IPv6 as been out since 1993 and we are not only 11 years 
>> into
>> the migration.. it will all happen eventually.. but I see many years 
>> left for
>> IPv4... and only a slow migration to V6...
>>
>> The same, I think, can be said for SCTP.. and it is very early in 
>> this process if
>> you use IPv6 as a gage :-D
>>
>>>
>>>>> - source address selection problem isn't addressed fully, if at all
>>>>
>>>
>>>> I don't think I understand this issue either..
>>>
>>>
>>>
>>> Host has addresses a and b from ISPs A and B. Host sends a packet to 
>>> address x which is routed over ISP A. However, the host selects 
>>> source address b which is filtered by A, so no connectivity. For 
>>> extra credit: solve same when this happens in the middle of a 
>>> session, and in cases where connectivity consists of two one way 
>>> paths. (a -> x and y -> b work, but not x -> a or b -> y)
>>
>>
>>
>> We have solved this in kame with our alternate routing code. Each time
>> an address fails more than a threshold (default of 2 rtx's if I 
>> remember right) we
>> ask the routing system for an alternate route... This makes it so 
>> that after
>> any two failed transmissions to x routed through B we would then ask for
>> a new route and get one over A... And yes it works in the the middle
>> of a session when the ISP makes a change during the conversation.. the
>> thresholds are not picky about when it happens ...
>
>
> Ah, so you have indeed made routing policy decisions and placed them 
> into the end systems of the originator of the session. This is most 
> interesting. A site which has multiple connections with varying cost 
> has to either live with the routing policy you've encoded into the 
> stack or force dropped packets in some fashion to try to fool your stack. 

No.. it is not the stack that makes the policy.. it is what is in the
routing tables...

Note that all SCTP (or TCP for that matter) does is ask for an alternate.
If the administrator does not have an alternate available.. or deems it
costs to much then it would not be at that level of the table. Also the
admin controls which is priority by order.. .i.e. if I add

route add default 10.1.1.1
and then
route add default 10.2.1.1

Then you will get the 10.1.1.1 first... the signifigance of this is
that you use the alternate route ONLY when you are having
difficulty getting to through to the peer... i.e. T3-rtx's...

So if you were really concerned about cost.. the admin would
need to put the cheapest route in first... in reality my two
routes in my multi-homed box do not cost any more.. they
are equal cost.. I have them since I want to stay connected and
I want it simple.. i.e. I add two default routes and SCTP just
works...



>
>
> I'm afraid the multihoming solution you are promoting does not match 
> up entirely with the full scope of the multihoming problem. Though I'm 
> sure some folks will be relieved to not need to formulate routing 
> policies, it does seem a lot of folks really want to be able to 
> control their routing. Today, there can be cost differences among 
> circuits (think about circuits that are priced based on usage), 
> preferred circuits, and so forth.


I think you need to look at how most of us purchase broadband.. I buy
two DSL's into my house... I don't really care which one is used.. they cost
no more if I let one sit idle then if I send/recv ton's of data. This is the
reality of the DSL for 49.95 a month... there is not cost difference.. only
when I start running T1's and such to my house does cost become an
issue... and I just don't see the masses doing this.. they will wait
for the DSL and cable modem to be in the neighborhood...



>
>
>> I might add that TCP could also take advantage of this code and gain
>> some reliability as well.
>>
>> Oh, and note, in your scenario above.. if it happens in the middle of
>> a TCP connection the connection will fail.. or just plain not start
>> up if it is being filtered and that is the way the routes point.
>>
>> For our KAME stack with the patch it will NOT fail in the middle...
>>
>>>
>>>
>>>> We have fully
>>>> addressed source address selection in the KAME implementation.
>>>
>>>
>>>
>>> In what way?
>>
>>
>>
>> See above, you would be best to get the KAME stack, and the patch from
>> www.sctp.org
>> (further details are in the alternate routing discussion on the 
>> sctp.org web site)
>> and then play with it..
>
>
> The other failing of the dual-address problem is the need for dual 
> addresses. I guess we'll have to ask ARIN and the other RIRs to adjust 
> their rules to allow justification of parallel allocations from 
> multiple upstreams to a single company, where they'd only have needed 
> a single block of a given size before. There's no free lunch, at least 
> if there's any interest in using SCTP as a multihoming solution atop 
> IPv4. 

I don't see why I would want two addresses to the same companies.. I buy
two DSL's in my location because I know that any single ISP tends to 
fail.. thus
I get two seperate non-related IP addresses... like I have now.. go do
a dig on
stewart.chicago.il.us

The two V4 addresses you see are NOT related... one is SBC/Ameritech the
other is speakeasy..

This requires no changes in any ARIN or RIRs rules...

R

>
>
>
>


-- 
Randall R. Stewart
815-477-2127 (office)
815-342-5222 (cell phone)





From owner-ietf@ietf.org  Fri Jan 30 07:26:58 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12076
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 07:26:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmXd5-0006Di-OP
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 07:20:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmXc3-0005zK-Ha
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 07:19:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11634
	for <ietf@ietf.org>; Fri, 30 Jan 2004 07:19:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmXc2-0001DT-00
	for ietf@ietf.org; Fri, 30 Jan 2004 07:19:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmXbA-00017R-00
	for ietf@ietf.org; Fri, 30 Jan 2004 07:18:13 -0500
Received: from stewart.chicago.il.us ([66.93.186.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmXaW-0000sW-00
	for IETF@ietf.org; Fri, 30 Jan 2004 07:17:32 -0500
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1])
	by stewart.chicago.il.us (8.12.8p1/8.12.8) with ESMTP id i0UCGxO6075217;
	Fri, 30 Jan 2004 06:16:59 -0600 (CST)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <401A4B3B.6050607@stewart.chicago.il.us>
Date: Fri, 30 Jan 2004 06:16:59 -0600
From: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
CC: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
References: <20040129162952.6110386AEA@mercury.lcs.mit.edu>
In-Reply-To: <20040129162952.6110386AEA@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Noel:

Comments in line :->

Noel Chiappa wrote:

>    > From: John C Klensin <john-ietf@jck.com>
>
>    > Of course, multiple A records works, is out there, and have worked for
>    > years. But they worked better before we introduced routers (i.e., when
>    > the hosts with multiple A records really had interfaces on different
>    > networks). Today, it effectively implies having multiple addresses on
>    > an interface and multiple "local" address prefixes running around on
>    > the same physical LAN segment.
>    > ...
>    > Perhaps more important, as Noel points out, it doesn't scale very well,
>    > at least in terms of the routing fabric.
>
>Sorry? What I said doesn't work for the routing, in terms of scaling to many
>small sites, is for a multi-homed site to have a single address prefix, which
>is then globally advertised. (That's the most common tack for multi-homing
>support in IPv4 to date, which is what you were talking about.)
>
>Having multiple addresses for a host (which has only a single physical
>interface, but which is in a site which is multi-homed) is in fact the only
>approach whose effects on the routing does scale (within anything like the
>current routing architecture, i.e. packets which include only source and
>destination addresses, as opposed to a source route).
>

Or you can use SCTP and have seperate interfaces going to
seperate ISP's and have the transport use them both....

That is how we designed SCTP.....

>
>
>    > as I tried to point out, address preservation policies have had
>    > trickle-down effects that make it impractical for small enterprises.
>
>It is an interesting point (as Daniel Senie also just pointed out) that
>multiple addresses -> faster consumption of the address space.
>
>However, since to avoid a size explosion in the routing tables, those
>multiple addresses do have to be connectivity-dependent (political
>translation - "provider-dependent"), I don't see how address preservation
>policies have made this approach "impractical for small enterprises". My
>understanding of current allocation policies is that ISP's can get enough
>addresses to cover their customers. If company X is a customer of both ISP P
>and ISP Q, I would assume that both P and Q don't have a problem getting
>enough space to cover their customers - including X.
>

Exactly... When I buy two seperate DSL's from two seperate
ISP's the two ISP's hand me an IP address .. they are seperate and
don't break or violate any current address allocation policy.
I don't ask SBC to advertise my speakeasy address... or vice-versa..
instead I let SCTP handle it all...

R

>
>(Or were you speaking of the "one address block, globally advertized"?)
>
>	Noel
>
>
>
>  
>


-- 
Randall R. Stewart
815-477-2127 (office)
815-342-5222 (cell phone)





From owner-ietf@ietf.org  Fri Jan 30 08:10:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13601
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 08:10:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmYJe-0003nS-AQ
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 08:04:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmJts-0006VR-NW
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 16:40:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20392
	for <ietf@ietf.org>; Thu, 29 Jan 2004 16:40:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmJtr-0006TT-00
	for ietf@ietf.org; Thu, 29 Jan 2004 16:40:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmJsz-0006ND-00
	for ietf@ietf.org; Thu, 29 Jan 2004 16:39:42 -0500
Received: from trout.cpsr.org ([66.180.229.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmJsW-0006Gs-00
	for ietf@ietf.org; Thu, 29 Jan 2004 16:39:12 -0500
Received: from us.ibm.com (trout [66.180.229.5])
	by trout.cpsr.org (8.12.8p2/8.12.8) with ESMTP id i0TLcx3i063711;
	Thu, 29 Jan 2004 13:38:59 -0800 (PST)
	(envelope-from nborenst@us.ibm.com)
Date: Thu, 29 Jan 2004 16:38:58 -0500
Subject: Korean visa problems
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: John Stracke <jstracke@centive.com>, ietf@ietf.org
To: John C Klensin <john-ietf@jck.com>
From: Nathaniel Borenstein <nborenst@us.ibm.com>
In-Reply-To: <83652145.1075383740@scan.jck.com>
Message-Id: <8BB2DCBD-52A3-11D8-85D8-000A9571873E@us.ibm.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

OK, after reading this list for long enough I decided to play it safe 
and send away for a Korean visa.  However, they are telling me that 
they require a NOTARIZED letter from the IETF confirming my attendance. 
  I went to the IETF page and ordered a "letter of invitation" but I'm 
not really expecting it to be notarized.  Now, not only do I not have a 
visa, but my US passport is currently on a desk in the Korean consulate 
in Chicago.  (Yes, you have to send the original passport away to get 
the visa.)  Anybody else have a problem like this?  Any suggestions on 
how to get a notarized letter from the IETF?  -- Nathaniel
---
Nathaniel S. Borenstein, Ph.D.  <nborenst@us.ibm.com>
Distinguished Engineer, IBM, Lotus CTO Office
Phone:  +1 (734) 395-9828 or +1 (989) 739-8243






From owner-ietf@ietf.org  Fri Jan 30 08:10:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13621
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 08:10:29 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmYJe-0003nY-Ex
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 08:04:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmK6Y-0008AH-Go
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 16:53:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21729
	for <ietf@ietf.org>; Thu, 29 Jan 2004 16:53:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmK6X-0001CP-00
	for ietf@ietf.org; Thu, 29 Jan 2004 16:53:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmK5k-00015x-00
	for ietf@ietf.org; Thu, 29 Jan 2004 16:52:53 -0500
Received: from trout.cpsr.org ([66.180.229.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmK5B-0000xq-00
	for ietf@ietf.org; Thu, 29 Jan 2004 16:52:17 -0500
Received: from us.ibm.com (trout [66.180.229.5])
	by trout.cpsr.org (8.12.8p2/8.12.8) with ESMTP id i0TLqD3i064010;
	Thu, 29 Jan 2004 13:52:13 -0800 (PST)
	(envelope-from nborenst@us.ibm.com)
Date: Thu, 29 Jan 2004 16:52:12 -0500
Subject: Re: Korean visa problems
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
From: Nathaniel Borenstein <nborenst@us.ibm.com>
To: John C Klensin <john-ietf@jck.com>, John Stracke <jstracke@centive.com>,
        IETF Discussion <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <8BB2DCBD-52A3-11D8-85D8-000A9571873E@us.ibm.com>
Message-Id: <65300B3E-52A5-11D8-85D8-000A9571873E@us.ibm.com>
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

One more thing:  I called back again, armed with the information Gene 
Gaines posted from the Korean Consulate in DC.  The woman at the 
consulate in Chicago got very angry at me, and told her that it doesn't 
matter what the other consulates say, I have to follow the rules of the 
Chicago consulate because I live in Michigan.  (If I went to another 
consulate, she says, they'd tell me I had to go to the Chicago one.)  
And she did her very best to make it absolutely clear to me that:

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

2.  I need a *notarized* letter from the IETF for them to give me a 
visa.

This is absurd, but I'm beginning to wonder if I'll actually be able to 
attend....  -- Nathaniel

On Thursday, January 29, 2004, at 04:38  PM, Nathaniel Borenstein wrote:

> OK, after reading this list for long enough I decided to play it safe 
> and send away for a Korean visa.  However, they are telling me that 
> they require a NOTARIZED letter from the IETF confirming my 
> attendance.  I went to the IETF page and ordered a "letter of 
> invitation" but I'm not really expecting it to be notarized.  Now, not 
> only do I not have a visa, but my US passport is currently on a desk 
> in the Korean consulate in Chicago.  (Yes, you have to send the 
> original passport away to get the visa.)  Anybody else have a problem 
> like this?  Any suggestions on how to get a notarized letter from the 
> IETF?  -- Nathaniel
> ---
> Nathaniel S. Borenstein, Ph.D.  <nborenst@us.ibm.com>
> Distinguished Engineer, IBM, Lotus CTO Office
> Phone:  +1 (734) 395-9828 or +1 (989) 739-8243
>






From owner-ietf@ietf.org  Fri Jan 30 08:11:22 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13694
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 08:11:22 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmYMY-00049B-Oy
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 08:07:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmYKY-0003ne-Hl
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 08:05:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13319
	for <ietf@ietf.org>; Fri, 30 Jan 2004 08:05:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmYKX-0006oa-00
	for ietf@ietf.org; Fri, 30 Jan 2004 08:05:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmYJY-0006g7-00
	for ietf@ietf.org; Fri, 30 Jan 2004 08:04:05 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmYIb-0006Z5-00
	for IETF@ietf.org; Fri, 30 Jan 2004 08:03:05 -0500
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i0UD30YG007169;
	Fri, 30 Jan 2004 14:03:04 +0100 (MET)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <DZ591MJL>; Fri, 30 Jan 2004 14:03:12 +0100
Message-ID: <4E85E49D1F0CBF4F96EA08E335750D7D03F52C95@Esealnt877.al.sw.ericsson.se>
From: "Yuri Ismailov (KI/EAB)" <yuri.ismailov@ericsson.com>
To: "'Randall R. Stewart (home)'" <randall@stewart.chicago.il.us>,
        Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: IETF@ietf.org
Subject: RE: Death of the Internet - details at 11
Date: Fri, 30 Jan 2004 13:57:16 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

However this is only about using multiple addresses.
Is there any concern about mobility between them?
In such case things look much differently, especially if interfaces configured with v6 and v4.
/yuri

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org]On Behalf Of
Randall R. Stewart (home)
Sent: den 30 januari 2004 13:17
To: Noel Chiappa
Cc: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11


Noel:

Comments in line :->

Noel Chiappa wrote:

>    > From: John C Klensin <john-ietf@jck.com>
>
>    > Of course, multiple A records works, is out there, and have worked for
>    > years. But they worked better before we introduced routers (i.e., when
>    > the hosts with multiple A records really had interfaces on different
>    > networks). Today, it effectively implies having multiple addresses on
>    > an interface and multiple "local" address prefixes running around on
>    > the same physical LAN segment.
>    > ...
>    > Perhaps more important, as Noel points out, it doesn't scale very well,
>    > at least in terms of the routing fabric.
>
>Sorry? What I said doesn't work for the routing, in terms of scaling to many
>small sites, is for a multi-homed site to have a single address prefix, which
>is then globally advertised. (That's the most common tack for multi-homing
>support in IPv4 to date, which is what you were talking about.)
>
>Having multiple addresses for a host (which has only a single physical
>interface, but which is in a site which is multi-homed) is in fact the only
>approach whose effects on the routing does scale (within anything like the
>current routing architecture, i.e. packets which include only source and
>destination addresses, as opposed to a source route).
>

Or you can use SCTP and have seperate interfaces going to
seperate ISP's and have the transport use them both....

That is how we designed SCTP.....

>
>
>    > as I tried to point out, address preservation policies have had
>    > trickle-down effects that make it impractical for small enterprises.
>
>It is an interesting point (as Daniel Senie also just pointed out) that
>multiple addresses -> faster consumption of the address space.
>
>However, since to avoid a size explosion in the routing tables, those
>multiple addresses do have to be connectivity-dependent (political
>translation - "provider-dependent"), I don't see how address preservation
>policies have made this approach "impractical for small enterprises". My
>understanding of current allocation policies is that ISP's can get enough
>addresses to cover their customers. If company X is a customer of both ISP P
>and ISP Q, I would assume that both P and Q don't have a problem getting
>enough space to cover their customers - including X.
>

Exactly... When I buy two seperate DSL's from two seperate
ISP's the two ISP's hand me an IP address .. they are seperate and
don't break or violate any current address allocation policy.
I don't ask SBC to advertise my speakeasy address... or vice-versa..
instead I let SCTP handle it all...

R

>
>(Or were you speaking of the "one address block, globally advertized"?)
>
>	Noel
>
>
>
>  
>


-- 
Randall R. Stewart
815-477-2127 (office)
815-342-5222 (cell phone)





From owner-ietf@ietf.org  Fri Jan 30 08:13:39 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13884
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 08:13:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmYPV-0004WJ-J3
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 08:10:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmNZS-0004n5-5E
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 20:35:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04885
	for <ietf@ietf.org>; Thu, 29 Jan 2004 20:35:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmNZQ-0001LN-00
	for ietf@ietf.org; Thu, 29 Jan 2004 20:35:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmNYW-0001FY-00
	for ietf@ietf.org; Thu, 29 Jan 2004 20:34:48 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmNXz-00017e-00
	for IETF@ietf.org; Thu, 29 Jan 2004 20:34:15 -0500
Received: from BBFUJIP.brandenburg.com (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i0U1fYd13958;
	Thu, 29 Jan 2004 17:41:34 -0800
Date: Fri, 30 Jan 2004 10:33:11 +0900
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <312347488.20040130103311@brandenburg.com>
To: John C Klensin <john-ietf@jck.com>
CC: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <65886049.1075365973@scan.jck.com>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com>
 <19410259999.20040128073646@brandenburg.com>
 <224923613.1075293579@scan.jck.com> <1419514349.20040129143445@brandenburg.com>
 <65886049.1075365973@scan.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

JJCK> Of course, multiple A records works, is out there, and have
JCK> worked for years.  But they worked better before we introduced 
JCK> routers (i.e., when the hosts with multiple A records really had 
JCK> interfaces on different networks).  Today, it effectively 
JCK> implies having multiple addresses on an interface and multiple 
JCK> "local" address prefixes running around on the same physical LAN 
JCK> segment.

Multiple addresses is multiple addresses. (I quite the fact that that
is grammatical, in this particular case...) Reliability is affected by
whether they are through different interfaces and through different
network paths, but the degree of host mechanism is really the same.

The fact that the indirection of routed sub-networks is involved is of
course significant, but it is merely the cost of scaling.  Better, it
really is only (did I say "only"?) an administrative cost.  Still, the
fact that a little more administration gives a lot more reliability
strikes me as a fair trade.


JCK> IPv4 was not designed to work well in that environment 
JCK> and, with at least some implementations that are arguably still 
JCK> conforming, ...  The claim
JCK> has been made that IPv6 _is_ designed to work in that 
JCK> environment, for whatever that claim may be worth.

I've heard that claim too and have yet to hear it substantiated,
although I've asked.



JCK> Perhaps more important, as Noel points out, it doesn't scale 
JCK> very well, at least in terms of the routing fabric.

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


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






From owner-ietf@ietf.org  Fri Jan 30 08:56:50 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16675
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 08:56:50 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmZ2B-0003ED-81
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 08:50:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmYwa-0002Ux-1c
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 08:44:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16039
	for <ietf@ietf.org>; Fri, 30 Jan 2004 08:44:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmYwZ-00050t-00
	for ietf@ietf.org; Fri, 30 Jan 2004 08:44:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmYvo-0004sM-00
	for ietf@ietf.org; Fri, 30 Jan 2004 08:43:37 -0500
Received: from rufus.isode.com ([62.3.217.251])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmYvE-0004gZ-00
	for ietf@ietf.org; Fri, 30 Jan 2004 08:43:01 -0500
Received: from isode.com (shiny.isode.com [62.3.217.250]) by rufus.isode.com
          via TCP (with SMTP (internal)) with ESMTPA;
          Fri, 30 Jan 2004 13:42:13 +0000
Message-ID: <401A5F35.70309@isode.com>
Date: Fri, 30 Jan 2004 13:42:13 +0000
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Nathaniel Borenstein <nborenst@us.ibm.com>
CC: John C Klensin <john-ietf@jck.com>, John Stracke <jstracke@centive.com>,
        ietf@ietf.org
Subject: Re: Korean visa problems
References: <8BB2DCBD-52A3-11D8-85D8-000A9571873E@us.ibm.com>
In-Reply-To: <8BB2DCBD-52A3-11D8-85D8-000A9571873E@us.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Nathaniel Borenstein wrote:

> OK, after reading this list for long enough I decided to play it safe 
> and send away for a Korean visa.  However, they are telling me that 
> they require a NOTARIZED letter from the IETF confirming my 
> attendance.  I went to the IETF page and ordered a "letter of 
> invitation" but I'm not really expecting it to be notarized.  Now, not 
> only do I not have a visa, but my US passport is currently on a desk 
> in the Korean consulate in Chicago.  (Yes, you have to send the 
> original passport away to get the visa.)  Anybody else have a problem 
> like this?  Any suggestions on how to get a notarized letter from the 
> IETF?  -- Nathaniel 

Organized (TTA) will send you a notorized letter. I've just received 
recently one in my mail.

Alexey





From owner-ietf@ietf.org  Fri Jan 30 08:57:56 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13619
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 08:10:29 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmYMY-000494-DJ
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 08:07:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmNZS-0004n5-5E
	for ietf@asgard.ietf.org; Thu, 29 Jan 2004 20:35:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04885
	for <ietf@ietf.org>; Thu, 29 Jan 2004 20:35:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmNZQ-0001LN-00
	for ietf@ietf.org; Thu, 29 Jan 2004 20:35:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmNYW-0001FY-00
	for ietf@ietf.org; Thu, 29 Jan 2004 20:34:48 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmNXz-00017e-00
	for IETF@ietf.org; Thu, 29 Jan 2004 20:34:15 -0500
Received: from BBFUJIP.brandenburg.com (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i0U1fYd13958;
	Thu, 29 Jan 2004 17:41:34 -0800
Date: Fri, 30 Jan 2004 10:33:11 +0900
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <312347488.20040130103311@brandenburg.com>
To: John C Klensin <john-ietf@jck.com>
CC: IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <65886049.1075365973@scan.jck.com>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com>
 <19410259999.20040128073646@brandenburg.com>
 <224923613.1075293579@scan.jck.com> <1419514349.20040129143445@brandenburg.com>
 <65886049.1075365973@scan.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

JJCK> Of course, multiple A records works, is out there, and have
JCK> worked for years.  But they worked better before we introduced 
JCK> routers (i.e., when the hosts with multiple A records really had 
JCK> interfaces on different networks).  Today, it effectively 
JCK> implies having multiple addresses on an interface and multiple 
JCK> "local" address prefixes running around on the same physical LAN 
JCK> segment.

Multiple addresses is multiple addresses. (I quite the fact that that
is grammatical, in this particular case...) Reliability is affected by
whether they are through different interfaces and through different
network paths, but the degree of host mechanism is really the same.

The fact that the indirection of routed sub-networks is involved is of
course significant, but it is merely the cost of scaling.  Better, it
really is only (did I say "only"?) an administrative cost.  Still, the
fact that a little more administration gives a lot more reliability
strikes me as a fair trade.


JCK> IPv4 was not designed to work well in that environment 
JCK> and, with at least some implementations that are arguably still 
JCK> conforming, ...  The claim
JCK> has been made that IPv6 _is_ designed to work in that 
JCK> environment, for whatever that claim may be worth.

I've heard that claim too and have yet to hear it substantiated,
although I've asked.



JCK> Perhaps more important, as Noel points out, it doesn't scale 
JCK> very well, at least in terms of the routing fabric.

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


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






From owner-ietf@ietf.org  Fri Jan 30 11:30:10 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24867
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 11:30:10 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmbNb-0004jR-O8
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 11:20:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmbCr-0004Nu-2P
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 11:09:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23513
	for <ietf@ietf.org>; Fri, 30 Jan 2004 11:09:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmbCq-0007jH-00
	for ietf@ietf.org; Fri, 30 Jan 2004 11:09:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmbBv-0007by-00
	for ietf@ietf.org; Fri, 30 Jan 2004 11:08:23 -0500
Received: from [63.247.76.254] (helo=montage.altserver.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmbBJ-0007Tf-00
	for IETF@ietf.org; Fri, 30 Jan 2004 11:07:45 -0500
Received: from f02m-17-100.d0.club-internet.fr ([212.195.212.100] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1AmbBG-0002JD-UY; Fri, 30 Jan 2004 08:07:43 -0800
Message-Id: <6.0.1.1.2.20040130170947.059bf8f0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 30 Jan 2004 17:10:50 +0100
To: Iljitsch van Beijnum <iljitsch@muada.com>,
        "Ayyasamy, Senthilkumar  \(UMKC-Student\)" <saq66@umkc.edu>
From: jfcm <info@utel.net>
Subject: Re: Death of the Internet - details at 11
Cc: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
In-Reply-To: <BA7AC46E-5313-11D8-98F9-000A95CD987A@muada.com>
References: <5EF7D95E17BDAD4A968C812E5ABC390B0110826D@KC-MAIL4.kc.umkc.edu>
 <BA7AC46E-5313-11D8-98F9-000A95CD987A@muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:02 30/01/04, Iljitsch van Beijnum wrote:
>I think I used enough qualifiers to be able to make this statement. 
>Obviously reality is more complex, so anyone interested should check out 
>the drafts submitted to multi6 and/or the mailing list archive.

Anyone concerned would like to be kept informed by an executive summary of 
this archive.  




From owner-ietf@ietf.org  Fri Jan 30 11:35:09 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25677
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 11:35:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmbY5-0007VY-E0
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 11:31:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmbX7-0007BZ-Sn
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 11:30:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24904
	for <ietf@ietf.org>; Fri, 30 Jan 2004 11:30:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmbX6-0002rK-00
	for ietf@ietf.org; Fri, 30 Jan 2004 11:30:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmbW6-0002hN-00
	for ietf@ietf.org; Fri, 30 Jan 2004 11:29:15 -0500
Received: from parsley.amaranth.net ([208.254.46.23])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmbV7-0002Y2-00
	for ietf@ietf.org; Fri, 30 Jan 2004 11:28:13 -0500
Received: from Willow.senie.com (h0006b1049b35.ne.client2.attbi.com [24.91.86.165])
	(authenticated bits=0)
	by parsley.amaranth.net (8.12.8/8.12.8) with ESMTP id i0UGSB5V019019
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <ietf@ietf.org>; Fri, 30 Jan 2004 11:28:11 -0500
Message-Id: <6.0.1.1.2.20040130110425.033b1dc8@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 30 Jan 2004 11:22:37 -0500
To: ietf@ietf.org
From: Daniel Senie <dts@senie.com>
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <401A4A0C.4010007@stewart.chicago.il.us>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com>
 <19410259999.20040128073646@brandenburg.com>
 <224923613.1075293579@scan.jck.com>
 <40182303.7000300@stewart.chicago.il.us>
 <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com>
 <40183C10.10401@stewart.chicago.il.us>
 <654669B6-524E-11D8-98F9-000A95CD987A@muada.com>
 <4018FFFB.2010201@stewart.chicago.il.us>
 <6.0.1.1.2.20040129094026.0308c540@mail.amaranth.net>
 <401A4A0C.4010007@stewart.chicago.il.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

We're clearly looking at this issue from VERY different viewpoints. See 
comments inline.

At 07:11 AM 1/30/2004, Randall R. Stewart (home) wrote:
>Daniel Senie wrote:
>
>>
>>I really don't see how this fits with routing policy. You appear to make 
>>the assumption that a multi-homed site wants to use the multiple paths as 
>>equals.
>
>>
>>
>>
>>>>>Now to take advantage of the stream feature you would need to do
>>>>>more.. but for pure multi-homing one or two lines of change does
>>>>>not seem that big of deal to me ...
>>>>
>>>>
>>>>
>>>>Doing WWW-style HTTP (lots of concurrent sessions) with SCTP would be 
>>>>nonsense, this is where the feature where multiple streams are 
>>>>multiplexed over a single session would be extremely useful.
>>>
>>>
>>>
>>>Yes.. if you wanted to do HTTP over SCTP and use features such
>>>as streams you WOULD WANT to extend HTML so that you could
>>>have the client "get pages" on particular streams... Then you could
>>>have parrallel transfers over one association and not have to require
>>>multiple TCP connections... this is optimal...
>>>
>>>Jana was doing some investagtion into this at the University of 
>>>Deleware's Protocol
>>>Engineering Lab.. don't know if he will be writting a paper on it.. I 
>>>imagine so...
>>>
>>>>
>>>>
>>>>>>- no backward compatibility of any kind
>>>>
>>>>>I am not sure what you mean by backward compatable? You definetly
>>>>>can't have TCP and SCTP talk.. they are after all different protocols...
>>>>>But if an application needs the redundancy move to it.. its there today
>>>>>with about 2 lines of coding change...
>>>>
>>>>
>>>>
>>>>But then you'll have to run services on both TCP and SCTP pretty much 
>>>>forever. Not a good thing.
>>>
>>>
>>>Just like we are stuck with IPv4 "forever" as well...  Its pretty much
>>>a given.. once a new technology comes along it is a slow gradual 
>>>transition not
>>>a mass move. IPv6 as been out since 1993 and we are not only 11 years into
>>>the migration.. it will all happen eventually.. but I see many years 
>>>left for
>>>IPv4... and only a slow migration to V6...
>>>
>>>The same, I think, can be said for SCTP.. and it is very early in this 
>>>process if
>>>you use IPv6 as a gage :-D
>>>
>>>>
>>>>>>- source address selection problem isn't addressed fully, if at all
>>>>
>>>>>I don't think I understand this issue either..
>>>>
>>>>
>>>>
>>>>Host has addresses a and b from ISPs A and B. Host sends a packet to 
>>>>address x which is routed over ISP A. However, the host selects source 
>>>>address b which is filtered by A, so no connectivity. For extra credit: 
>>>>solve same when this happens in the middle of a session, and in cases 
>>>>where connectivity consists of two one way paths. (a -> x and y -> b 
>>>>work, but not x -> a or b -> y)
>>>
>>>
>>>
>>>We have solved this in kame with our alternate routing code. Each time
>>>an address fails more than a threshold (default of 2 rtx's if I remember 
>>>right) we
>>>ask the routing system for an alternate route... This makes it so that after
>>>any two failed transmissions to x routed through B we would then ask for
>>>a new route and get one over A... And yes it works in the the middle
>>>of a session when the ISP makes a change during the conversation.. the
>>>thresholds are not picky about when it happens ...
>>
>>
>>Ah, so you have indeed made routing policy decisions and placed them into 
>>the end systems of the originator of the session. This is most 
>>interesting. A site which has multiple connections with varying cost has 
>>to either live with the routing policy you've encoded into the stack or 
>>force dropped packets in some fashion to try to fool your stack.
>
>No.. it is not the stack that makes the policy.. it is what is in the
>routing tables...

Wrong origination of routing information. I see from comments below you're 
looking at the "I'm an end user and want to have multiple paths to the 
Internet to get more bandwidth or redundancy" aspect. I run a web hosting 
company. We want to be able to have multiple upstream providers and 
multihome to guard against outages at any one provider. We pay for 
bandwidth based on usage, and so may well have several connections, but 
designate one or more to be used only if other connectivity as a last resort.

As the content provider who's spending lots of money on which of MY 
circuits I want traffic to arrive on, I don't want you deciding on your two 
DSL lines to choose one of my sets of addresses or the other. If you stream 
video over a link I don't want used normally, my bills would skyrocket.

This is why I said the decisions in YOUR stack are deciding routing policy 
for MY circuits. In the IPv4/BGP world configuration of this stuff isn't 
clean or simple, but it is possible to encourage the use of some links over 
others. I don't see how I would be able to implement that type of control 
with your simplistic SCTP stack tests, other than to play games with 
discarding or delaying probe packets from your computer on some paths.


>Note that all SCTP (or TCP for that matter) does is ask for an alternate.
>If the administrator does not have an alternate available.. or deems it
>costs to much then it would not be at that level of the table. Also the
>admin controls which is priority by order.. .i.e. if I add

Wrong table. You can control which interfaces YOU use to reach the world. I 
don't see how I can control the weightings and preferences your computer 
will use to reach MY multihomed systems.


>route add default 10.1.1.1
>and then
>route add default 10.2.1.1
>
>Then you will get the 10.1.1.1 first... the signifigance of this is
>that you use the alternate route ONLY when you are having
>difficulty getting to through to the peer... i.e. T3-rtx's...
>
>So if you were really concerned about cost.. the admin would
>need to put the cheapest route in first... in reality my two
>routes in my multi-homed box do not cost any more.. they
>are equal cost.. I have them since I want to stay connected and
>I want it simple.. i.e. I add two default routes and SCTP just
>works...

I'm concerned about traffic inbound to my site, and the cost of the various 
pipes I use for that.






>>I'm afraid the multihoming solution you are promoting does not match up 
>>entirely with the full scope of the multihoming problem. Though I'm sure 
>>some folks will be relieved to not need to formulate routing policies, it 
>>does seem a lot of folks really want to be able to control their routing. 
>>Today, there can be cost differences among circuits (think about circuits 
>>that are priced based on usage), preferred circuits, and so forth.
>
>
>I think you need to look at how most of us purchase broadband..

This is where I got clued in to the fact that we're not talking about the 
same problem.

>  I buy
>two DSL's into my house... I don't really care which one is used.. they cost
>no more if I let one sit idle then if I send/recv ton's of data. This is the
>reality of the DSL for 49.95 a month... there is not cost difference.. only
>when I start running T1's and such to my house does cost become an
>issue... and I just don't see the masses doing this.. they will wait
>for the DSL and cable modem to be in the neighborhood...

I don't expect the masses to multihome at all. I do expect most content 
providers to be multihomed, and to want to manage that multihoming. Today, 
it's possible to multhome if you have PI space, or if you get a couple of 
cooperating network providers to punch sufficient holes in their aggregates 
and toss routes to one another (to deal with folks who filter the more 
specifics). A great deal of effort has been expended by many folk to 
provide ways to specify routing policy and path preferences.

If I can't make these types of policy decisions, there's no reason for me 
to implement the type of multihoming you're promoting.






>>>I might add that TCP could also take advantage of this code and gain
>>>some reliability as well.
>>>
>>>Oh, and note, in your scenario above.. if it happens in the middle of
>>>a TCP connection the connection will fail.. or just plain not start
>>>up if it is being filtered and that is the way the routes point.
>>>
>>>For our KAME stack with the patch it will NOT fail in the middle...
>>>
>>>>
>>>>
>>>>>We have fully
>>>>>addressed source address selection in the KAME implementation.
>>>>
>>>>
>>>>
>>>>In what way?
>>>
>>>
>>>
>>>See above, you would be best to get the KAME stack, and the patch from
>>>www.sctp.org
>>>(further details are in the alternate routing discussion on the sctp.org 
>>>web site)
>>>and then play with it..
>>
>>
>>The other failing of the dual-address problem is the need for dual 
>>addresses. I guess we'll have to ask ARIN and the other RIRs to adjust 
>>their rules to allow justification of parallel allocations from multiple 
>>upstreams to a single company, where they'd only have needed a single 
>>block of a given size before. There's no free lunch, at least if there's 
>>any interest in using SCTP as a multihoming solution atop IPv4.
>
>I don't see why I would want two addresses to the same companies.. I buy
>two DSL's in my location because I know that any single ISP tends to 
>fail.. thus
>I get two seperate non-related IP addresses... like I have now.. go do
>a dig on
>stewart.chicago.il.us

If I've got a farm of 100 servers, I would need each of them to have an 
address on each provider. Will those providers allow me to obtain more 
address space? Under present rules, I have to justify the space I ask for 
from each upstream. Each of them wants to know how I'm utilizing space from 
the other.


>The two V4 addresses you see are NOT related... one is SBC/Ameritech the
>other is speakeasy..
>
>This requires no changes in any ARIN or RIRs rules...

It sure seems like it would if you're asking for a bigger chunk of space 
from each provider. Will I be able to get a /23 from each of 3 providers 
without running afoul of ARIN rules? I don't know for sure, but suspect it 
would be an issue.

Since you're talking about residential circuits, and I'm talking about fat 
pipes in data centers, it seems the examples each of us had in mind don't 
make sense for the others' arguments.

Dan




From owner-ietf@ietf.org  Fri Jan 30 12:04:42 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28299
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 12:04:42 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ambx7-00037Y-I7
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 11:57:09 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Ambpc-0002AB-2f
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 11:49:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26722
	for <ietf@ietf.org>; Fri, 30 Jan 2004 11:49:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ambpb-0005tc-00
	for ietf@ietf.org; Fri, 30 Jan 2004 11:49:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Amboi-0005mS-00
	for ietf@ietf.org; Fri, 30 Jan 2004 11:48:29 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ambnr-0005QP-00
	for ietf@ietf.org; Fri, 30 Jan 2004 11:47:35 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i0UGk0DB012716
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 30 Jan 2004 11:46:01 -0500
Date: Fri, 30 Jan 2004 11:46:00 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Fred Baker <fred@cisco.com>
cc: Leslie Daigle <leslie@thinkingcat.com>, <ietf@ietf.org>
Subject: Re: The IETF Mission
In-Reply-To: <6.0.1.1.2.20040129213127.047b0a08@mira-sjc5-b.cisco.com >
Message-ID: <Pine.LNX.4.44.0401301011520.10127-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

> 
> Thinking out loud here, plenty of room for all to chime in. The key 
> differences, if there are any, between IETF and NANOG and her sisters, and 
> between IETF and IRTF, are:

Nanog should not be compared to the IETF.  Nanog is a forum that has
promoted ignorance of the law or perhaps even tolerance of illegal
activity, and specifically promotes misinformation of network operators
with respect to the Electronic Communications and Privacy Act (ECPA) and
Computer Fraud and Abuse Act (CFAA). Nanog does this by selective
suppression of discussion on the subject and the suppression of
participation of anyone who would refute the notion that the ECPA only
applies to "common carriers".  Merit and Nanog describe themselves as
"educational".  The failure to educate Network Operators on the legal
aspects of their profession is, in my opinion, nothing less than
reprehensible.  Quite obviously, there are legal aspects to internet
service operation just as there are legal aspects to business. No
reputable business school would fail to provide adequate courses in
business law, or fail to discuss the legal aspects of business with
students. Nanog claims to be an educational organization, yet it fails to
live up to any reasonable standard of education, and goes further with its
selective suppression.  The selective suppression reveals an agenda of
misinformation that goes beyond simply not educating.

Over the years, I have done extensive research on the ECPA, and the CFAA.
I have employed lawyers on the subject, and have supporting documents such
as legal, uptodate copies of the statutes, the House and Senate reports on
the ECPA and the CFAA, and the Model Criminal Code, as well as an
extensive library of case law. While the House and Senate reports on the
ECPA speak extensivly about Email and Remote Computing Services, many
people on Nanog have posted that the ECPA does not apply to ISPs. Yet
despite having all this information, Susan Harris has asked me not to
refute those people who claim that the ECPA does not apply to ISPs or
Email.

In January of 2000, Susan Harris asked me (only me) to stop posting on the
subject, in reference to a specific incident.  She didn't want me to
refute people on the topic. She did not make any requests of anyone else
to stop, and the "bashing" continued for two or three days, until news
reported that law enforcement acted in a way that vindicated what I was
saying. After I posted this vindication, which came after several days of
bashing in which I did not participate, she removed my posting privileges.  
Actually being right on concrete issues is not something that is respected
on Nanog. My posts were also informative, respectful, and well supported
with citations.  Supposing this were off-topic, it would be appropriate to
ask everyone to stop. But of course, it isn't any more off-topic for
Network operators to learn about the ECPA than it is for business school
candidates to learn about business law.

While Nanog did have a DOJ person speak in October, 2000, that
presentation has been wildly misquoted, and it barely addressed the civil
aspect of the ECPA.  The CFAA was not discussed.  False information is
still posted on Nanog on the topic, which has been brought up by others.
And the topic is clearly of interest to network operators, because it
keeps coming up.  

For example, I was not allowed to correct claims made in June 2002 by
Steve Bellovin that "what you say is correct for *telephone* companies,
but not ISPs.".  Bellovin attributes this statement to the DOJ
presentation. But the DOJ presentation does not in fact say that. Though I
concede that it is easy to take the slides out of context, this goes well
beyond that.  Bellovin makes other mistakes to give the impression that
only common carriers need be concerned with the ECPA.  Bellovin also uses
claims of "discussions with prosecutors" to substantiate his claims. But
his claims are refuted by the statute text, the Congressional Reports, and
the case law.  Unfortunately, few are familar with that material allowed
to post.  Some of the material is obscure and costs money to obtain. So I
am limited to privately emailing information to the people who posted the
original questions.  Others, perhaps interested in the topic, but who
didn't post, are misled.

So Nanog is quite a bit different from the IETF, and, in my opinion,
should not be associated with or compared to the IETF.  Actually being 
right on concrete issues is something that carries no weight with Nanog, 
but it does carry weight with the IETF.

Dean Anderson
CEO
Av8 Internet, Inc








From owner-ietf@ietf.org  Fri Jan 30 12:17:56 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24866
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 11:30:10 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmbNc-0004jX-1h
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 11:20:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmbCr-0004Nw-Mx
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 11:09:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23517
	for <ietf@ietf.org>; Fri, 30 Jan 2004 11:09:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmbCq-0007jM-00
	for ietf@ietf.org; Fri, 30 Jan 2004 11:09:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmbBv-0007c6-00
	for ietf@ietf.org; Fri, 30 Jan 2004 11:08:24 -0500
Received: from [63.247.76.254] (helo=montage.altserver.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmbBL-0007Te-00
	for ietf@ietf.org; Fri, 30 Jan 2004 11:07:47 -0500
Received: from f02m-17-100.d0.club-internet.fr ([212.195.212.100] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1AmbBE-0002JD-3s; Fri, 30 Jan 2004 08:07:40 -0800
Message-Id: <6.0.1.1.2.20040130074241.04faca50@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 30 Jan 2004 08:07:19 +0100
To: Fred Baker <fred@cisco.com>, Leslie Daigle <leslie@thinkingcat.com>
From: jfcm <info@utel.net>
Subject: Re: The IETF Mission
Cc: ietf@ietf.org
In-Reply-To: <6.0.1.1.2.20040129213127.047b0a08@mira-sjc5-b.cisco.com >
References: <405441934.1074293627@localhost>
 <Pine.LNX.4.44.0401171150270.11109-100000@netcore.fi>
 <6.0.1.1.2.20040117103457.0466fc00@mira-sjc5-b.cisco.com>
 <401946E8.9030207@thinkingcat.com>
 <6.0.1.1.2.20040129213127.047b0a08@mira-sjc5-b.cisco.com >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,DATE_IN_PAST_06_12 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Dear Fred,
you formulated this with real majesty. Good. IETF is a wise
men pow wow where users are represented by vendors and
its favorite matter is datagram internet scalability.

This puts free softwares and new generation networks out of
its scope. They are Research from what I understand. Why not?

Would then the question not be to define the IAB Mission?
Should not someone take care of modelization and innovation?
jfc

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




From owner-ietf@ietf.org  Fri Jan 30 13:05:46 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04924
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 13:05:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Amci1-0008CG-Qp
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 12:45:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmcBt-000548-6w
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 12:12:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28854
	for <ietf@ietf.org>; Fri, 30 Jan 2004 12:12:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmcBs-0001WA-00
	for ietf@ietf.org; Fri, 30 Jan 2004 12:12:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmcAv-0001O0-00
	for ietf@ietf.org; Fri, 30 Jan 2004 12:11:26 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmcA4-00019w-00
	for ietf@ietf.org; Fri, 30 Jan 2004 12:10:32 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 30 Jan 2004 09:15:55 +0000
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 i0UH9x7U014031;
	Fri, 30 Jan 2004 09:10:00 -0800 (PST)
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.6-GR)
	with ESMTP id ALX54775;
	Fri, 30 Jan 2004 09:09:58 -0800 (PST)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id JAA03950; Fri, 30 Jan 2004 09:09:58 -0800 (PST)
From: Michael Thomas <mat@cisco.com>
X-IMAIL-SIG: v:1; h:"thomasm-u1"; t: 1075482598; x: 1075914598; a:rsa-hmacmd5;
	e:Iw==; n:quBFGQY/VhsJDGuN5vP3v9sHBDn6GYUp31ShJkqhPzzD+5fMz0jvtZpcXOO2A+en/B75A0PEtsgKSNWKC3pyaIsPWI1D4XyBQzkyC6Hys0yD5/8GYKWiupLLfjf+OBKMwvRxBd9U6p6+QkNu3JsycHOzmYuhy615pUe/J1cdOi0=;
	s:Fr+JZ5SghF9FxS/J/r5VPMw4tgO3RC2SXmCelyUl5ESXCCJGf6L4Z4mY32wrLMLxgDUkTpymw4ei/7cavwldBmBktE9CxaOQqoaOzZCahi7pzikv90+yGk9q//tLoO9N+0UfUSk4g7JxPEbbRodMhLXq9UyWPuDoQ/SLoUDBUlU=;
	c: "Subject: Re: Death of the Internet - details at 11"
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16410.36837.865239.515682@thomasm-u1.cisco.com>
Date: Fri, 30 Jan 2004 09:09:57 -0800 (PST)
To: Daniel Senie <dts@senie.com>
Cc: ietf@ietf.org
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <6.0.1.1.2.20040130110425.033b1dc8@mail.amaranth.net>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
	<116512686.1074013651@scan.jck.com>
	<19410259999.20040128073646@brandenburg.com>
	<224923613.1075293579@scan.jck.com>
	<40182303.7000300@stewart.chicago.il.us>
	<89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com>
	<40183C10.10401@stewart.chicago.il.us>
	<654669B6-524E-11D8-98F9-000A95CD987A@muada.com>
	<4018FFFB.2010201@stewart.chicago.il.us>
	<6.0.1.1.2.20040129094026.0308c540@mail.amaranth.net>
	<401A4A0C.4010007@stewart.chicago.il.us>
	<6.0.1.1.2.20040130110425.033b1dc8@mail.amaranth.net>
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!
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Daniel Senie writes:
 > Wrong origination of routing information. I see from comments below you're 
 > looking at the "I'm an end user and want to have multiple paths to the 
 > Internet to get more bandwidth or redundancy" aspect. I run a web hosting 
 > company. We want to be able to have multiple upstream providers and 
 > multihome to guard against outages at any one provider. We pay for 
 > bandwidth based on usage, and so may well have several connections, but 
 > designate one or more to be used only if other connectivity as a last resort.
 > 
 > As the content provider who's spending lots of money on which of MY 
 > circuits I want traffic to arrive on, I don't want you deciding on your two 
 > DSL lines to choose one of my sets of addresses or the other. If you stream 
 > video over a link I don't want used normally, my bills would skyrocket.
 > 
 > This is why I said the decisions in YOUR stack are deciding routing policy 
 > for MY circuits. In the IPv4/BGP world configuration of this stuff isn't 
 > clean or simple, but it is possible to encourage the use of some links over 
 > others. I don't see how I would be able to implement that type of control 
 > with your simplistic SCTP stack tests, other than to play games with 
 > discarding or delaying probe packets from your computer on some paths.

   Now wait a minute. It's your bandwidth... shouldn't 
   you be _shaping_ his traffic if there's some reason
   he shouldn't be using one path or another? And thus
   provide negative feedback so that he has incentive
   to use the path that you want him to use? After all,
   the end consumer is likely clueless about your
   network and is going to do whatever they can to
   get what they're after -- bandwidth. Sounds to
   me that if he's able to cause your bills go
   through the ceiling _you're_ doing something
   wrong.

		Mike



From owner-ietf@ietf.org  Fri Jan 30 13:53:17 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08285
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 13:53:17 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Amdeb-0006i8-4t
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 13:46:09 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Amdc3-0006Oj-Ca
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 13:43:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07724
	for <ietf@ietf.org>; Fri, 30 Jan 2004 13:43:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Amdc2-0002Hu-00
	for ietf@ietf.org; Fri, 30 Jan 2004 13:43:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Amdb9-00028G-00
	for ietf@ietf.org; Fri, 30 Jan 2004 13:42:36 -0500
Received: from stewart.chicago.il.us ([66.93.186.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Amdaa-0001xh-00
	for IETF@ietf.org; Fri, 30 Jan 2004 13:42:01 -0500
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1])
	by stewart.chicago.il.us (8.12.8p1/8.12.8) with ESMTP id i0UIfLO6077258;
	Fri, 30 Jan 2004 12:41:22 -0600 (CST)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <401AA551.3000104@stewart.chicago.il.us>
Date: Fri, 30 Jan 2004 12:41:21 -0600
From: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dave Crocker <dhc@dcrocker.net>
CC: John C Klensin <john-ietf@jck.com>, IETF@ietf.org
Subject: Re: Death of the Internet - details at 11
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <1419514349.20040129143445@brandenburg.com> <65886049.1075365973@scan.jck.com> <312347488.20040130103311@brandenburg.com>
In-Reply-To: <312347488.20040130103311@brandenburg.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave Crocker wrote:

>John,
>
>JJCK> Of course, multiple A records works, is out there, and have
>JCK> worked for years.  But they worked better before we introduced 
>JCK> routers (i.e., when the hosts with multiple A records really had 
>JCK> interfaces on different networks).  Today, it effectively 
>JCK> implies having multiple addresses on an interface and multiple 
>JCK> "local" address prefixes running around on the same physical LAN 
>JCK> segment.
>
>Multiple addresses is multiple addresses. (I quite the fact that that
>is grammatical, in this particular case...) Reliability is affected by
>whether they are through different interfaces and through different
>network paths, but the degree of host mechanism is really the same.
>
>The fact that the indirection of routed sub-networks is involved is of
>course significant, but it is merely the cost of scaling.  Better, it
>really is only (did I say "only"?) an administrative cost.  Still, the
>fact that a little more administration gives a lot more reliability
>strikes me as a fair trade.
>
>
>JCK> IPv4 was not designed to work well in that environment 
>JCK> and, with at least some implementations that are arguably still 
>JCK> conforming, ...  The claim
>JCK> has been made that IPv6 _is_ designed to work in that 
>JCK> environment, for whatever that claim may be worth.
>
>I've heard that claim too and have yet to hear it substantiated,
>although I've asked.
>
>
>
>JCK> Perhaps more important, as Noel points out, it doesn't scale 
>JCK> very well, at least in terms of the routing fabric.
>
>Let's see.  I get a CIDR network address from one provider.  I get
>another from another.  I can have my BGP announce both of them all the
>time or one of them at a time.  I guess I do not see the horrible
>scaling problem.
>

Dave:

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

But of course the whole point is that we don't need this.. at least
not with SCTP...and even your proposal which is cloned from add-ip
should not require these "host routes"

R

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


-- 
Randall R. Stewart
815-477-2127 (office)
815-342-5222 (cell phone)





From owner-ietf@ietf.org  Fri Jan 30 15:16:51 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14051
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 15:16:51 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Ames4-0007CX-Ir
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 15:04:08 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmepY-0006u1-7X
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 15:01:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12406
	for <ietf@ietf.org>; Fri, 30 Jan 2004 15:01:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmepW-00068l-00
	for ietf@ietf.org; Fri, 30 Jan 2004 15:01:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ameoa-00062T-00
	for ietf@ietf.org; Fri, 30 Jan 2004 15:00:32 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmeoE-0005vA-00
	for ietf@ietf.org; Fri, 30 Jan 2004 15:00:10 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 9710C61B8B; Fri, 30 Jan 2004 20:59:39 +0100 (CET)
Date: Fri, 30 Jan 2004 11:59:33 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Behaviour on IETF lists (Re: The IETF Mission)
Message-ID: <1575782615.1075463973@[192.168.1.52]>
In-Reply-To: <Pine.LNX.4.44.0401301011520.10127-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0401301011520.10127-100000@cirrus.av8.net>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========862D711A5B15345661A1=========="
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

Dean,

the subject of the IETF mission is not particularly relevant to bashing=20
NANOG policies, or personal attacks on persons for their activities within=20
NANOG.
Nor are personal attacks appropriate on the IETF list.
If you want to quarrel about NANOG topics, at least change the subject.
Or better yet, take it to NANOG.

--On 30. januar 2004 11:46 -0500 Dean Anderson <dean@av8.com> wrote:

> So Nanog is quite a bit different from the IETF, and, in my opinion,
> should not be associated with or compared to the IETF.  Actually being
> right on concrete issues is something that carries no weight with Nanog,
> but it does carry weight with the IETF.




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

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

iD8DBQFAGreqOMj+2+WY0F4RAtirAJ0WNNXfjZxkZJs6aCoMZKTt0q2iVQCg5mjz
99PkakyxsgQgP290znUJ5+0=
=IaAZ
-----END PGP SIGNATURE-----

--==========862D711A5B15345661A1==========--




From owner-ietf@ietf.org  Fri Jan 30 16:20:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17367
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 16:20:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Amfw1-0005Gm-Ho
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 16:12:17 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmfrX-00059B-47
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 16:07:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16605
	for <ietf@ietf.org>; Fri, 30 Jan 2004 16:07:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmfrV-00074j-00
	for ietf@ietf.org; Fri, 30 Jan 2004 16:07:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmfqY-0006wQ-00
	for ietf@ietf.org; Fri, 30 Jan 2004 16:06:39 -0500
Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1Amfpk-0006gm-01
	for ietf@ietf.org; Fri, 30 Jan 2004 16:05:49 -0500
Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap 
	 id 17335; Fri, 30 Jan 2004 16:07:13 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: While leaving Korea
Date: Fri, 30 Jan 2004 16:05:16 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209DB1A0F6@zoe.office.snowshore.com>
Thread-Topic: While leaving Korea
Thread-Index: AcPm/Cmo6ceDOv6ORh+dX9PYPo/Pog==
From: "Eric Burger" <eburger@snowshore.com>
To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

I just left Incheon airport (Seoul).

Amongst the various items that you would expect to be banned, like =
propane tanks, razor blades, and knives, there is a prohibition on =
taking batteries in your carry-on baggage.

I don't know if it is only Alkaline batteries -- my bags were searched, =
but they did not pull (or find) my NiMH batteries.

The humorous thing is while my stuff was being searched, the person =
behind me put his batteries and butane lighter in a tray to go through =
X-Ray.  Of course, the "dangerous" batteries were confiscated, but he =
got to take the lighter.

True to the open source movement, they also had a detailed description =
of how to build a shoe bomb.  I'm actually not being facetious here -- =
it actually explains what they are looking for.




From owner-ietf@ietf.org  Fri Jan 30 16:20:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17369
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 16:20:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Amfym-0005uz-50
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 16:15:08 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Amfx6-0005WB-UE
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 16:13:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17044
	for <ietf@ietf.org>; Fri, 30 Jan 2004 16:13:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Amfx5-00003w-00
	for ietf@ietf.org; Fri, 30 Jan 2004 16:13:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmfwA-0007js-00
	for ietf@ietf.org; Fri, 30 Jan 2004 16:12:26 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmfvD-0007XP-00
	for ietf@ietf.org; Fri, 30 Jan 2004 16:11:27 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 30 Jan 2004 13:16:52 +0000
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0ULAkp0027156;
	Fri, 30 Jan 2004 13:10:54 -0800 (PST)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id APU91833;
	Fri, 30 Jan 2004 12:33:09 -0800 (PST)
Message-Id: <6.0.1.1.2.20040130120457.056dc5b0@mira-sjc5-b.cisco.com >
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 30 Jan 2004 12:14:13 -0800
To: jfcm <info@utel.net>
From: Fred Baker <fred@cisco.com>
Subject: Re: The IETF Mission
Cc: Leslie Daigle <leslie@thinkingcat.com>, ietf@ietf.org
In-Reply-To: <6.0.1.1.2.20040130074241.04faca50@mail.utel.net>
References: <405441934.1074293627@localhost>
 <Pine.LNX.4.44.0401171150270.11109-100000@netcore.fi>
 <6.0.1.1.2.20040117103457.0466fc00@mira-sjc5-b.cisco.com>
 <401946E8.9030207@thinkingcat.com>
 <6.0.1.1.2.20040129213127.047b0a08@mira-sjc5-b.cisco.com >
 <6.0.1.1.2.20040130074241.04faca50@mail.utel.net>
Mime-Version: 1.0
Content-Type: multipart/signed;
 boundary="====---========------=-====-----=======--=-=--==";
 protocol="application/pgp-signature"; micalg=pgp-sha1
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.8 required=5.0 tests=AWL,FORGED_MUA_EUDORA,
	INVALID_MSGID autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

--====---========------=-====-----=======--=-=--==
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 11:07 PM 1/29/2004, jfcm wrote:
>This puts free softwares and new generation networks out of its scope. 
>They are Research from what I understand. Why not?

I don't think the IETF tells people how to charge; the software can be free 
or not. I don't think the IETF cares, and I don't know that being free 
makes it research.

As to next generation networks, I have a little rant on the topic. There 
are two terms that go around that drive me nuts:
    "Next Generation Network"
       Marketing term: it means "the network or networking technology I
       would like to sell you"
    "Legacy technology"
       Marketing term: it means "the technology you already have that I
       would like to replace with my Next Generation Network"

An example of this usage showed up recently on the manet list: I was 
proposing adding manet capabilities to OSPF, so that manet networks could 
easily be part of a larger network that contained more traditional regions 
as well. The respondent asked whether I had considered building a 
manet-only protocol, since the wired networks were legacy networks destined 
for the dustbin and wireless is the only thing that will be present in the 
future. My word... If you believe that, I have a bridge to sell you...

Market-babble doesn't belong in the IETF. But the solid engineering that 
the market-droids babble about most certainly does. 
--====---========------=-====-----=======--=-=--==
Content-Type: application/pgp-signature

-----BEGIN PGP MESSAGE-----
Version: PGP 7.0.1

iQA/AwUBQBq7FW4xHWxyLJtDEQJE4gCgje++jqms/fwgMgETPt+e9fCE99IAn2X+
B+lvJPu+Xx3EBPiVXG077DPT
=v7a3
-----END PGP MESSAGE-----

--====---========------=-====-----=======--=-=--==--




From owner-ietf@ietf.org  Fri Jan 30 18:12:21 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01116
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 18:12:21 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmhhD-00078W-1A
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 18:05:07 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmhgZ-000756-Ew
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 18:04:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23676
	for <ietf@ietf.org>; Fri, 30 Jan 2004 18:04:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmhgX-0007nK-00
	for ietf@ietf.org; Fri, 30 Jan 2004 18:04:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmhfY-0007gf-00
	for ietf@ietf.org; Fri, 30 Jan 2004 18:03:25 -0500
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Amheb-0007T9-00
	for ietf@ietf.org; Fri, 30 Jan 2004 18:02:25 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i0UN1sLC019626
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 30 Jan 2004 18:01:54 -0500
Date: Fri, 30 Jan 2004 18:01:54 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: Behaviour on IETF lists (Re: The IETF Mission)
In-Reply-To: <1575782615.1075463973@[192.168.1.52]>
Message-ID: <Pine.LNX.4.44.0401301543370.10127-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Harald,

It seems that you haven't quite followed the thread, or read the messages.

This issue was brought up in a comparison between Nanog and the IETF by
Fred Baker, who apparently found little difference between the IETF and
Nanog.  It is quite valid to make comparisions to the missions of other
organizations, so he brings up a valid point, which deserves equally valid
disagreement.

The events involving Susan Harris occurred, and I am reporting them to
distinguish the IETF from Nanog in response to a post comparing the IETF
to NANOG. Many people no doubt think her conduct was improper.  Reporting
improper conduct is not a personal attack.  The act I am criticizing was
made in her official role at Nanog, and reflects on Nanog as an
organization. This was not a private or personal act.  It has nothing to
do with her personally except that she is a person responsible for Nanog,
and has authority at Nanog, and she made the decsisions which are being
criticized.  Her official decisions reflect on Nanog just as your official
decisions reflect on the IETF.  If you make bad decisions, they will
reflect badly on the IETF, and you and the IETF will deserve criticism.  
Such criticism is not a personal attack. You are misusing the term.

Susan Harris may be an nice person. I've never met her in person. I don't
know anything personal about her to attack.  But sometimes nice people
behave in ways that are quite obviously improper. Documenting, reporting,
criticizing, and complaining about such behavior is not a personal attack.
For your information and reference, a 'personal attack' is where one
attacks a personal trait of the person, rather than their position.  I've
attacked her position as represented by her official decisions regarding
Nanog, not her personally.

Sometimes people try to deflect criticism by trying to call it a personal
attack. This in not the first time that people have misused the term
'personal attack' when their friends were being criticized.  Perhaps you
are letting your friendship get in the way?

Quite obviously, I can't take it to Nanog--apparently you didn't read my
message.  Certainly you wouldn't make such a frivolous statement if you
had read it.  But your suggestion clarifies and obvious difference between
Nanog and the IETF: there is no one in authority other than Susan
Harris--there is no one to appeal her decisions to.  IETF decisions, as
you know, can be appealed.

But she also did some things that are relevant to the IETF.  Besides
halting my participation in Nanog, she also halted my participation in the
RADB. At the time, Av8 was participating in the RADB and had RADB objects.  
It seems to me that denying my participation in the RADB may be a
violation of IETF/ISOC/ICANN rules.  And this should be redressed.


Thanks,

Dean Anderson
CEO
Av8 Internet, Inc


On Fri, 30 Jan 2004, Harald Tveit Alvestrand wrote:

> Dean,
> 
> the subject of the IETF mission is not particularly relevant to bashing 
> NANOG policies, or personal attacks on persons for their activities within 
> NANOG.
> Nor are personal attacks appropriate on the IETF list.
> If you want to quarrel about NANOG topics, at least change the subject.
> Or better yet, take it to NANOG.
> 
> --On 30. januar 2004 11:46 -0500 Dean Anderson <dean@av8.com> wrote:
> 
> > So Nanog is quite a bit different from the IETF, and, in my opinion,
> > should not be associated with or compared to the IETF.  Actually being
> > right on concrete issues is something that carries no weight with Nanog,
> > but it does carry weight with the IETF.
> 
> 
> 
> 






From owner-ietf@ietf.org  Fri Jan 30 19:37:59 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28851
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 19:37:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Amj1T-0002wO-3l
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 19:30:07 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Amiy0-0002jD-ML
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 19:26:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16781
	for <ietf@ietf.org>; Fri, 30 Jan 2004 19:26:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Amixz-0001rz-00
	for ietf@ietf.org; Fri, 30 Jan 2004 19:26:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Amix4-0001lx-00
	for ietf@ietf.org; Fri, 30 Jan 2004 19:25:35 -0500
Received: from pec.etri.re.kr ([129.254.114.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmiwY-0001en-00
	for IETF@ietf.org; Fri, 30 Jan 2004 19:25:03 -0500
Received: from LocalHost (sjkoh.etri.re.kr [129.254.112.15])
	by pec.etri.re.kr (8.12.10/8.12.10) with SMTP id i0V0eafM016769;
	Sat, 31 Jan 2004 09:40:36 +0900 (KST)
Message-ID: <002a01c3e790$96f52160$0f70fe81@LocalHost>
From: "Seok J. Koh" <sjkoh@pec.etri.re.kr>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>,
        "Randall R. Stewart \(home\)" <randall@stewart.chicago.il.us>
Cc: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us> <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us> <654669B6-524E-11D8-98F9-000A95CD987A@muada.com> <4018FFFB.2010201@stewart.chicago.il.us> <F2D4652B-52F9-11D8-98F9-000A95CD987A@muada.com>
Subject: Re: Death of the Internet - details at 11
Date: Sat, 31 Jan 2004 09:24:28 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> Anyway, with IPv6 the address format is fundamentally incompatible with 
> that of IPv4 so there is no choice but running them concurrently during 
> the transition period. A new multihoming-capable transport protocol 
> doesn't have to be incompatible with existing TCP so this situation is 
> avoidable here.

It does not seem reasonable to compare the IPv6/IPv4 deployment and 
SCTP/TCP deployment. SCTP and TCP are basically the end-to-end protocols 
so that hosts/terminals have only to have them, whereas IPv4 and IPv6 are 
subject to network support or change.

IMHO, we don't need to worry about inter-operablity or compatibilty between
SCTP and TCP. I mean SCTP will be used by the new emerging applications and
services including mobile internet stuffs, for example, between mobile clients
and contents servers of the M-ISP.

Seok J. Koh



From owner-ietf@ietf.org  Fri Jan 30 19:44:58 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06956
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 19:44:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmjC6-0003nA-BQ
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 19:41:06 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmjBX-0003id-8z
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 19:40:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01873
	for <ietf@ietf.org>; Fri, 30 Jan 2004 19:40:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmjBV-0003Z7-00
	for ietf@ietf.org; Fri, 30 Jan 2004 19:40:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmjAW-0003PS-00
	for ietf@ietf.org; Fri, 30 Jan 2004 19:39:28 -0500
Received: from rc-dmz.felix.nlri.ca ([192.5.4.54] helo=felix.automagic.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Amj9Y-0003H5-00
	for ietf@ietf.org; Fri, 30 Jan 2004 19:38:28 -0500
Received: from [199.212.90.19] (helo=[199.212.90.19])
	by felix.automagic.org with asmtp (TLSv1:RC4-SHA:128)
	(Exim 4.20)
	id 1Amj9X-000Jwf-S7; Sat, 31 Jan 2004 00:38:28 +0000
In-Reply-To: <Pine.LNX.4.44.0401301543370.10127-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0401301543370.10127-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <BB36AAA4-5385-11D8-B11C-003065CD52E4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
From: Joe Abley <jabley@isc.org>
Subject: Alternatives to RADB
Date: Fri, 30 Jan 2004 19:38:04 -0500
To: Dean Anderson <dean@av8.com>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On a purely operational note, and ignoring (having not read) the other 
aspects of this thread:

On 30 Jan 2004, at 18:01, Dean Anderson wrote:

> It seems to me that denying my participation in the RADB may be a
> violation of IETF/ISOC/ICANN rules.

Merit operates the RADB, which is one of many loosely-associated public 
databases known as the Internet Routing Registry (IRR), each modelled 
(sometimes slightly loosely, with respect to local extensions) on 
RFC2622, "Routing Policy Specification Language (RPSL)". The RADB is a 
for-fee service run by Merit of their own volition.

An example list of alternative, independently-operated databases within 
this vague "IRR" umbrella can be found by looking through the mirrored 
databases at:

   ftp://ftp.merit.edu/radb/dbase/

Each of those comes from a different database. All the databases are, 
in general, run independently.

There is nothing magical and special about the RADB in the context of 
the operation of the IRR, and if Merit does not want you as a customer 
there are plenty of other suppliers you can talk to. Perhaps start 
here: <http://www.altdb.net/>.


Joe




From owner-ietf@ietf.org  Fri Jan 30 19:46:30 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08525
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 19:46:30 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmjE2-000442-Sm
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 19:43:06 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmjDk-0003yl-2w
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 19:42:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04385
	for <ietf@ietf.org>; Fri, 30 Jan 2004 19:42:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmjDg-0003v0-00
	for ietf@ietf.org; Fri, 30 Jan 2004 19:42:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmjCt-0003n8-00
	for ietf@ietf.org; Fri, 30 Jan 2004 19:41:55 -0500
Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmjCL-0003de-00
	for ietf@ietf.org; Fri, 30 Jan 2004 19:41:21 -0500
Received: by mail.eecis.udel.edu (Postfix, from userid 62)
	id E869932B02; Fri, 30 Jan 2004 19:41:16 -0500 (EST)
Received: from stimpy.eecis.udel.edu (stimpy.eecis.udel.edu [128.4.40.17])
	by mail.eecis.udel.edu (Postfix) with ESMTP
	id 042CE32ACA; Fri, 30 Jan 2004 19:41:16 -0500 (EST)
Date: Fri, 30 Jan 2004 19:41:16 -0500 (EST)
From: "Armando L. Caro Jr." <me@armandocaro.net>
X-X-Sender: acaro@stimpy.eecis.udel.edu
To: Michael Thomas <mat@cisco.com>
Cc: Daniel Senie <dts@senie.com>, ietf@ietf.org
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <16410.36837.865239.515682@thomasm-u1.cisco.com>
Message-ID: <Pine.GSO.4.58.0401301935200.6101@stimpy.eecis.udel.edu>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com>
 <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us>
 <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us>
 <654669B6-524E-11D8-98F9-000A95CD987A@muada.com> <4018FFFB.2010201@stewart.chicago.il.us>
 <6.0.1.1.2.20040129094026.0308c540@mail.amaranth.net> <401A4A0C.4010007@stewart.chicago.il.us>
 <6.0.1.1.2.20040130110425.033b1dc8@mail.amaranth.net>
 <16410.36837.865239.515682@thomasm-u1.cisco.com>
X-Sanitizer: This message has been sanitized!
X-Sanitizer-URL: http://mailtools.anomy.net/
X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm,v 1.64 2002/10/22 MIME-Version: 1.0
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 30 Jan 2004, Michael Thomas wrote:

> Daniel Senie writes:
>  > Wrong origination of routing information. I see from comments below you're
>  > looking at the "I'm an end user and want to have multiple paths to the
>  > Internet to get more bandwidth or redundancy" aspect. I run a web hosting
>  > company. We want to be able to have multiple upstream providers and
>  > multihome to guard against outages at any one provider. We pay for
>  > bandwidth based on usage, and so may well have several connections, but
>  > designate one or more to be used only if other connectivity as a last resort.
>  >
>  > As the content provider who's spending lots of money on which of MY
>  > circuits I want traffic to arrive on, I don't want you deciding on your two
>  > DSL lines to choose one of my sets of addresses or the other. If you stream
>  > video over a link I don't want used normally, my bills would skyrocket.
>  >
>  > This is why I said the decisions in YOUR stack are deciding routing policy
>  > for MY circuits. In the IPv4/BGP world configuration of this stuff isn't
>  > clean or simple, but it is possible to encourage the use of some links over
>  > others. I don't see how I would be able to implement that type of control
>  > with your simplistic SCTP stack tests, other than to play games with
>  > discarding or delaying probe packets from your computer on some paths.
>
>    Now wait a minute. It's your bandwidth... shouldn't
>    you be _shaping_ his traffic if there's some reason
>    he shouldn't be using one path or another? And thus
>    provide negative feedback so that he has incentive
>    to use the path that you want him to use? After all,
>    the end consumer is likely clueless about your
>    network and is going to do whatever they can to
>    get what they're after -- bandwidth. Sounds to
>    me that if he's able to cause your bills go
>    through the ceiling _you're_ doing something
>    wrong.

Yes, I agree. Afterall, the purpose for a content provider to be
multihomed is so that they can provide more redundancy to their customers.
The content provider only knows about the parameters (capacity, etc) of
its incoming links, but has NO clue about the dynamics/quality of the
customer's path to those links. Any given user may have a different
experience to each of the content provider's incoming links. Thus, the
customer is in the best position to decide which destination is best at
any point in time. So, as Mike said, if the content provider has a
preference, it must encourage/discourage using traffic shapers, etc.

~armando

0--                                              --0
| Armando L. Caro Jr.  |  Protocol Engineering Lab |
| www.armandocaro.net  |    University of Delaware |
0--                                              --0



From owner-ietf@ietf.org  Fri Jan 30 20:02:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24909
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 20:02:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmjSY-0005et-74
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 19:58:06 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmjS7-0005bo-8I
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 19:57:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20346
	for <ietf@ietf.org>; Fri, 30 Jan 2004 19:57:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmjS5-00067J-00
	for ietf@ietf.org; Fri, 30 Jan 2004 19:57:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmjR8-00060g-00
	for ietf@ietf.org; Fri, 30 Jan 2004 19:56:39 -0500
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmjQi-0005tn-00
	for IETF@ietf.org; Fri, 30 Jan 2004 19:56:12 -0500
Received: from limbo (limbo.unfix.org [3ffe:8114:2000:240:200:39ff:fe77:1f3f])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP id 40C0185FB;
	Sat, 31 Jan 2004 01:56:07 +0100 (CET)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Seok J. Koh'" <sjkoh@pec.etri.re.kr>,
        "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'Randall R. Stewart (home)'" <randall@stewart.chicago.il.us>
Cc: "''ietf@ietf.org' Discussion'" <IETF@ietf.org>
Subject: RE: Death of the Internet - details at 11
Date: Sat, 31 Jan 2004 01:55:55 +0100
Organization: Unfix
Message-ID: <000401c3e794$fc9c8cc0$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <002a01c3e790$96f52160$0f70fe81@LocalHost>
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,LINES_OF_YELLING 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

Seok J. Koh wrote:

> > Anyway, with IPv6 the address format is fundamentally incompatible with 
> > that of IPv4 so there is no choice but running them concurrently during 
> > the transition period. A new multihoming-capable transport protocol 
> > doesn't have to be incompatible with existing TCP so this situation is 
> > avoidable here.
> 
> It does not seem reasonable to compare the IPv6/IPv4 deployment and 
> SCTP/TCP deployment. SCTP and TCP are basically the 
> end-to-end protocols so that hosts/terminals have only to have them, whereas IPv4 
> and IPv6 are subject to network support or change.

I see a possibility of speeding up SCTP deployment by using semi-NAT,
what about PT, Protocol-Translation, this could be accomplished using
a BIA (Bump In the API) approach.

Scenario: Clients connects to server.
Client's TCP/SCTP stack sees a connect() using TCP, it changes the
protocol field to SCTP and just tries to connect(), if it fails it
uses the normal TCP protocol.

Server starts to listen on TCP. It checks to see if the same port
for SCTP is already in use, if not, it also binds to SCTP.

Thus any client will also try to use sctp and any servercode will
automatically bind to SCTP, voila free multihoming code.
Putting this in the defacto Linux kernel will instantaniously have
a major deployment as generally people who keep up with new kernels
also enable the new toys in those kernels.

Or did someone already draft or even implement this? :)

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / http://unfix.org/~jeroen

iQA/AwUBQBr9GimqKFIzPnwjEQIhvgCfQn3SZ30zZRPz2C4DDmajFYpNjzoAnRVW
fTxLNkJcHK3nK+B1XNr3gPvB
=q2g+
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Fri Jan 30 20:25:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15920
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 20:25:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Amjnq-0000ZH-GM
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 20:20:06 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmjnJ-0000Tp-Iv
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 20:19:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12911
	for <ietf@ietf.org>; Fri, 30 Jan 2004 20:19:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmjnH-00029h-00
	for ietf@ietf.org; Fri, 30 Jan 2004 20:19:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmjmP-00023v-00
	for ietf@ietf.org; Fri, 30 Jan 2004 20:18:37 -0500
Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Amjlp-0001xi-00
	for IETF@ietf.org; Fri, 30 Jan 2004 20:18:01 -0500
Received: by mail.eecis.udel.edu (Postfix, from userid 62)
	id 9A9D232979; Fri, 30 Jan 2004 20:18:02 -0500 (EST)
Received: from stimpy.eecis.udel.edu (stimpy.eecis.udel.edu [128.4.40.17])
	by mail.eecis.udel.edu (Postfix) with ESMTP
	id D887F32971; Fri, 30 Jan 2004 20:18:01 -0500 (EST)
Date: Fri, 30 Jan 2004 20:18:01 -0500 (EST)
From: "Armando L. Caro Jr." <me@armandocaro.net>
X-X-Sender: acaro@stimpy.eecis.udel.edu
To: Jeroen Massar <jeroen@unfix.org>
Cc: "'Randall R. Stewart (home)'" <randall@stewart.chicago.il.us>,
        "''ietf@ietf.org' Discussion'" <IETF@ietf.org>
Subject: RE: Death of the Internet - details at 11
In-Reply-To: <000401c3e794$fc9c8cc0$210d640a@unfix.org>
Message-ID: <Pine.GSO.4.58.0401302017020.6101@stimpy.eecis.udel.edu>
References: <000401c3e794$fc9c8cc0$210d640a@unfix.org>
X-Sanitizer: This message has been sanitized!
X-Sanitizer-URL: http://mailtools.anomy.net/
X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm,v 1.64 2002/10/22 MIME-Version: 1.0
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 31 Jan 2004, Jeroen Massar wrote:

> I see a possibility of speeding up SCTP deployment by using semi-NAT,
> what about PT, Protocol-Translation, this could be accomplished using
> a BIA (Bump In the API) approach.
>
> Scenario: Clients connects to server.
> Client's TCP/SCTP stack sees a connect() using TCP, it changes the
> protocol field to SCTP and just tries to connect(), if it fails it
> uses the normal TCP protocol.
>
> Server starts to listen on TCP. It checks to see if the same port
> for SCTP is already in use, if not, it also binds to SCTP.
>
> Thus any client will also try to use sctp and any servercode will
> automatically bind to SCTP, voila free multihoming code.
> Putting this in the defacto Linux kernel will instantaniously have
> a major deployment as generally people who keep up with new kernels
> also enable the new toys in those kernels.
>
> Or did someone already draft or even implement this? :)

I have thought about this idea many times, but didn't really have feel of
feasible it is.

~armando

0--                                              --0
| Armando L. Caro Jr.  |  Protocol Engineering Lab |
| www.armandocaro.net  |    University of Delaware |
0--                                              --0



From owner-ietf@ietf.org  Fri Jan 30 20:25:56 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15945
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 20:25:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Amjnq-0000Z6-4c
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 20:20:06 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmjlL-0000MB-PN
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 20:17:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10627
	for <ietf@ietf.org>; Fri, 30 Jan 2004 20:17:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmjlK-0001vA-00
	for ietf@ietf.org; Fri, 30 Jan 2004 20:17:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmjkM-0001pT-00
	for ietf@ietf.org; Fri, 30 Jan 2004 20:16:31 -0500
Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmjjR-0001jg-00
	for IETF@ietf.org; Fri, 30 Jan 2004 20:15:33 -0500
Received: by mail.eecis.udel.edu (Postfix, from userid 62)
	id D8FCD32A8F; Fri, 30 Jan 2004 20:14:48 -0500 (EST)
Received: from stimpy.eecis.udel.edu (stimpy.eecis.udel.edu [128.4.40.17])
	by mail.eecis.udel.edu (Postfix) with ESMTP
	id E018832A6D; Fri, 30 Jan 2004 20:14:47 -0500 (EST)
Date: Fri, 30 Jan 2004 20:14:47 -0500 (EST)
From: "Armando L. Caro Jr." <me@armandocaro.net>
X-X-Sender: acaro@stimpy.eecis.udel.edu
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>,
        "'ietf@ietf.org' Discussion" <IETF@ietf.org>
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <F2D4652B-52F9-11D8-98F9-000A95CD987A@muada.com>
Message-ID: <Pine.GSO.4.58.0401301944040.6101@stimpy.eecis.udel.edu>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com>
 <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us>
 <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us>
 <654669B6-524E-11D8-98F9-000A95CD987A@muada.com> <4018FFFB.2010201@stewart.chicago.il.us>
 <F2D4652B-52F9-11D8-98F9-000A95CD987A@muada.com>
X-Sanitizer: This message has been sanitized!
X-Sanitizer-URL: http://mailtools.anomy.net/
X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm,v 1.64 2002/10/22 MIME-Version: 1.0
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 30 Jan 2004, Iljitsch van Beijnum wrote:

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

This _kind_ of a solution has already been proposed by Joe Touch and Ted
Faber in their ICNP 97 paper, "Dynamic Host Routing for Production Use of
Developmental Networks". It works, but on of the problems is that you hide
path information from the transport. TCP maintains congestion control
information about a single destination, with the assumption that the path
will not change during the connection. If it does occasionally, then it's
fine. However, with multihoming, the change may be a common occurance
throughtout the lifetime of a connection depending on the application and
the use of the multiple paths (failover, concurrent multipath transfer,
etc). So TCP (or whatever transport) should not be blind to the fact that
data is potentially going over a different path. Otherwise, the congestion
control parameters/algorithms will not work properly.

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

> As far as I can tell, most of the multi6 wg participants are thinking
> along similar lines.

I must admit that I haven't following the multi6 too closely yet, but I
plan to catch up and follow. But from what I have seen, it seems that SCTP
is ignored on the sidelines. _Maybe_ SCTP doesn't solve _all_ the
problems, but I think SCTP should be evaluated more closely before
developing yet another protocol. ...because I believe that no matter how
much we don't want to touch TCP or IP, something has to be changed to get
all this functionality. In my opinion, the transport is the easiest to
change, since they live on the endpoints and operating systems do
eventually get upgraded.

> > Yes.. if you wanted to do HTTP over SCTP and use features such
> > as streams you WOULD WANT to extend HTML so that you could
> > have the client "get pages" on particular streams...
>
> Why extend the markup language?

I think that was a typo...

> HTTP has supported sessions that stay alive so they can be used for
> more than just one operation for many years now. The trouble is that
> you get head of line blockage if you fetch all the elements that make
> up a WWW page in serial fashion. Being able to multiplex different
> streams (within an SCTP session) that all fetch elements simultenously
> would fix this. This of course requires changes to both HTTP clients
> and servers, but it should otherwise be transparent to the user.

This is essentially what Jana did. I don't really know the details of his
changes, but he exploited SCTP's multistreaming to avoid head of line
blocking. Sourabh Ladha did similar work with FTP.

Sourabh Ladha, Paul D. Amer,   Improving Multiple File Transfers Using
SCTP Multistreaming , IPCCC 2004, Phoenix AZ.
http://www.eecis.udel.edu/~ladha/2003.MultistreamedFTP.pdf

> Anyway, with IPv6 the address format is fundamentally incompatible with
> that of IPv4 so there is no choice but running them concurrently during
> the transition period. A new multihoming-capable transport protocol
> doesn't have to be incompatible with existing TCP so this situation is
> avoidable here.

No, it doesn't have to, but as I said above... something has to
change. Without change, you're limited to the improvements you can make.

~armando

0--                                              --0
| Armando L. Caro Jr.  |  Protocol Engineering Lab |
| www.armandocaro.net  |    University of Delaware |
0--                                              --0



From owner-ietf@ietf.org  Fri Jan 30 20:27:26 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17269
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 20:27:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Amjri-0000kw-Gv
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 20:24:06 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmjqC-0000eq-FK
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 20:22:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15745
	for <ietf@ietf.org>; Fri, 30 Jan 2004 20:22:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmjqA-0002Rg-00
	for ietf@ietf.org; Fri, 30 Jan 2004 20:22:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmjpF-0002M0-00
	for ietf@ietf.org; Fri, 30 Jan 2004 20:21:34 -0500
Received: from mail4.dynamicsoft.com ([63.110.3.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Amjof-0002AF-00; Fri, 30 Jan 2004 20:20:58 -0500
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id i0V1KNr0000611;
	Fri, 30 Jan 2004 19:20:27 -0600 (CST)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <DFXLR92P>; Fri, 30 Jan 2004 19:20:22 -0600
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3E86841@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Alexey Melnikov'" <Alexey.Melnikov@isode.com>
Cc: ietf@ietf.org, "'dthomas@foretec.com'" <dthomas@foretec.com>
Subject: RE: Korean visa problems
Date: Fri, 30 Jan 2004 19:20:21 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR 
	autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Alexey Melnikov [mailto:Alexey.Melnikov@isode.com] writes:

> Organized (TTA) will send you a notorized letter. I've just received 
> recently one in my mail.

How? As far as I can tell, TTA is refusing to send
letters of invitation to US citizens. I tried to get
one, and received the following response.

/a



-----Original Message-----
From: KeeMoon Roh [mailto:ietf59@tta.or.kr]
Sent: Friday, January 30, 2004 18:56
To: adam@dynamicsoft.com
Subject: RE: [Fwd: Letter of Invitation]


Dear. Adam Roach
 
This mail is from 59th Local IETF Secretariats in Korea.
Currently we are issuing invitation letters.
 
There is one thing we like to tell you about Korean Entry Visa.
----------------------------------------------------------------------------
-----------------------
USA citizens who want to visit Korea just for a short-term tour or transit
are permitted to enter Korea with no visa according to the principles of
reciprocity or priority of national interests with a tourist/transit visa
status (B-2, 30 days).
 
Event though, it is written that No-Visa Entry is for a short-term tour or
transit, participating in short term conventions or meetings (less than 30
days) is allowed as well.

U.S. citizens traveling to Korea to attend the IETF meeting in Seoul do not
need a visa, as they are traveling to attend a technical, non-profit 
conference. They can stay in Korea up to 30 days for such purposes and for
tourism.
---------------------------------------------------------------------
I checked this out several times with Ministry of Foreign Affairs and
Trades.

Please refer to http://www.mofat.go.kr/en/visa/e_visa.mof
IETF Meeting is non-profit conference not a business.
Invitation letter is only for VISA issuing.

best regards,
----------------------------------------------------------------------------
----------
Kee-Moon Roh
TTA (Telecommunications Technology Association)
* Mobile : +82-11-1735-1161
* TEL     : +82-31-724-0075
* FAX     : +82-31-724-0059
* E-mail : kees@tta.or.kr ( TTA Secretariat )
* E-mail : ietf59@tta.or.kr ( 59th IETF Local Secretariat )
----------------------------------------------------------------------------
------------





-----Original Message-----
From: Dawn Thomas [mailto:dthomas@foretec.com]
Sent: Saturday, January 31, 2004 6:36 AM
To: KeeMoon Roh
Cc: adam@dynamicsoft.com; ietf-registrar@ietf.org
Subject: [Fwd: Letter of Invitation]


Kee Moon,

Mr. Roach has registered and paid - please issue a letter of invitation

Thanks
Dawn

-------- Original Message -------- 
Subject: Letter of Invitation
Date: Wed, 28 Jan 2004 15:05:42 -0600
From: Adam Roach <adam@dynamicsoft.com>
To: "'ietf-registrar@ietf.org'" <ietf-registrar@ietf.org>



At the advice of the Korean Embassy in Houston, I will
be getting a visa for the upcoming IETF meeting. To
do so, I require a letter of invitation.

...



From owner-ietf@ietf.org  Fri Jan 30 20:41:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18148
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 20:41:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Amk1P-0002Uq-3W
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 20:34:07 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1Amjyw-0002IN-O4
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 20:31:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17869
	for <ietf@ietf.org>; Fri, 30 Jan 2004 20:31:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Amjyu-0003qa-00
	for ietf@ietf.org; Fri, 30 Jan 2004 20:31:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Amjxz-0003ha-00
	for ietf@ietf.org; Fri, 30 Jan 2004 20:30:36 -0500
Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Amjx4-0003V1-00
	for IETF@ietf.org; Fri, 30 Jan 2004 20:29:38 -0500
Received: by mail.eecis.udel.edu (Postfix, from userid 62)
	id 7482A32A6D; Fri, 30 Jan 2004 20:29:21 -0500 (EST)
Received: from stimpy.eecis.udel.edu (stimpy.eecis.udel.edu [128.4.40.17])
	by mail.eecis.udel.edu (Postfix) with ESMTP
	id B4FFE32971; Fri, 30 Jan 2004 20:29:20 -0500 (EST)
Date: Fri, 30 Jan 2004 20:29:20 -0500 (EST)
From: "Armando L. Caro Jr." <me@armandocaro.net>
X-X-Sender: acaro@stimpy.eecis.udel.edu
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: John C Klensin <john-ietf@jck.com>,
        "'ietf@ietf.org' Discussion" <IETF@ietf.org>
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <404A5260-51E1-11D8-98F9-000A95CD987A@muada.com>
Message-ID: <Pine.GSO.4.58.0401302027340.6101@stimpy.eecis.udel.edu>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com>
 <224923613.1075293579@scan.jck.com> <404A5260-51E1-11D8-98F9-000A95CD987A@muada.com>
X-Sanitizer: This message has been sanitized!
X-Sanitizer-URL: http://mailtools.anomy.net/
X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm,v 1.64 2002/10/22 MIME-Version: 1.0
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 28 Jan 2004, Iljitsch van Beijnum wrote:

> And if you had the PI space, why would you bother? Contrary to some
> reports multihoming using independent address space and links to more
> than one ISP works fairly well: failover times are almost always
> shorter than TCP or user timeouts.

I assume you mean failovers from first hop links failing, because
end-to-end failures cannot be detected faster than a timeout.

~armando

0--                                              --0
| Armando L. Caro Jr.  |  Protocol Engineering Lab |
| www.armandocaro.net  |    University of Delaware |
0--                                              --0



From owner-ietf@ietf.org  Fri Jan 30 23:19:21 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22957
	for <ietf-web-archive@odin.ietf.org>; Fri, 30 Jan 2004 23:19:21 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmmRy-0001eb-TI
	for ietf-list@asgard.ietf.org; Fri, 30 Jan 2004 23:09:42 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmmQz-0001bl-3C
	for ietf@asgard.ietf.org; Fri, 30 Jan 2004 23:08:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22718
	for <ietf@ietf.org>; Fri, 30 Jan 2004 23:08:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmmQw-0006kP-00
	for ietf@ietf.org; Fri, 30 Jan 2004 23:08:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmmPy-0006bt-00
	for ietf@ietf.org; Fri, 30 Jan 2004 23:07:39 -0500
Received: from sccrmhc11.comcast.net ([204.127.202.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmmPA-0006OV-00
	for IETF@ietf.org; Fri, 30 Jan 2004 23:06:48 -0500
Received: from dfnjgl21 (c-24-1-97-129.client.comcast.net[24.1.97.129])
          by comcast.net (sccrmhc11) with SMTP
          id <2004013104061801100ds17je>
          (Authid: sdawkins@comcast.net);
          Sat, 31 Jan 2004 04:06:18 +0000
Message-ID: <049e01c3e7af$9809fbb0$0400a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us> <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us> <654669B6-524E-11D8-98F9-000A95CD987A@muada.com> <4018FFFB.2010201@stewart.chicago.il.us> <F2D4652B-52F9-11D8-98F9-000A95CD987A@muada.com> <Pine.GSO.4.58.0401301944040.6101@stimpy.eecis.udel.edu>
Subject: Re: Death of the Internet - details at 11
Date: Fri, 30 Jan 2004 22:06:24 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Armondo - nice discussion.

Just a couple of notes on one of my favorite topics...

Spencer

----- Original Message ----- 
From: "Armando L. Caro Jr." <me@armandocaro.net>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
Cc: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>;
"'ietf@ietf.org' Discussion" <IETF@ietf.org>
Sent: Friday, January 30, 2004 7:14 PM
Subject: Re: Death of the Internet - details at 11

>
> This _kind_ of a solution has already been proposed by Joe Touch and
Ted
> Faber in their ICNP 97 paper, "Dynamic Host Routing for Production
Use of
> Developmental Networks". It works, but on of the problems is that
you hide
> path information from the transport. TCP maintains congestion
control
> information about a single destination, with the assumption that the
path
> will not change during the connection. If it does occasionally, then
it's
> fine. However, with multihoming, the change may be a common
occurance
> throughtout the lifetime of a connection depending on the
application and
> the use of the multiple paths (failover, concurrent multipath
transfer,
> etc). So TCP (or whatever transport) should not be blind to the fact
that
> data is potentially going over a different path. Otherwise, the
congestion
> control parameters/algorithms will not work properly.

Yeah, you might think that. I did, when we proposed TRIGTRAN (how
could finding out that a link failed be WRONG?).

The problem was that when we were discussing notifications like
PATH_CHANGE (or whatever we ended up calling it), the TCP has a
decision to make when it sees PATH_CHANGE - "do I

- slow start, recognizing that I now haven't got the remotest clue
what the path capacity is, or

- maintain my congestion window and try to actually LOSE something
before I decide that I need to adjust?"

TCPs have been ignoring things like ICMP Unreachable for decades, so
the second idea isn't totally bogus - they respond to actual loss, not
to the potential for loss.

Once you decide that your path change is no different than cross
traffic starting and stopping, which we adjust to after losing
something, transports ignoring path changes makes a lot of sense. If
you are changing paths frequently (and round-robin would be the
limiting case), slow-starting every time you change paths is
excessive - and, if you're going to respond to PATH_CHANGE, what else
would you do? You could do congestion avoidance during the first round
trip, or actually lose something and do congestion avoidance on the
second round trip - not a big difference, conceptually.

[deleted down to]

>
> > > Yes.. if you wanted to do HTTP over SCTP and use features such
> > > as streams you WOULD WANT to extend HTML so that you could
> > > have the client "get pages" on particular streams...
> >
> > Why extend the markup language?
>
> I think that was a typo...

Commonly-deployed browsers don't pipeline HTTP requests because they
don't get any advice on (1) size of objects or (2) recommended
retrieval order. Extending HTML to provide one or the other would make
at least as much sense as extending HTTP.

>
> > HTTP has supported sessions that stay alive so they can be used
for
> > more than just one operation for many years now. The trouble is
that
> > you get head of line blockage if you fetch all the elements that
make
> > up a WWW page in serial fashion. Being able to multiplex different
> > streams (within an SCTP session) that all fetch elements
simultenously
> > would fix this. This of course requires changes to both HTTP
clients
> > and servers, but it should otherwise be transparent to the user.

As above - fetching all elements simultaneously makes perfect sense to
transport guys, but can give pretty flaky-looking pages during
retrieval. If you think HTTP/1.1 with two connections makes sense, you
might start retrieving the smallest elements on one connection and the
largest on the other, and meet in the middle, but since the browser
has no idea how to do this, it's pretty difficult to resist the
temptation to wait for a connection to become idle before sending
another request.

And this is why HTTP over cellular links has horrible throughput - if
you stop-and-wait request 300-byte objects with one-second RTTs, your
throughputp looks a LOT like 300 bytes per second...




From owner-ietf@ietf.org  Sat Jan 31 00:33:55 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25280
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 Jan 2004 00:33:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1Amna0-00051L-81
	for ietf-list@asgard.ietf.org; Sat, 31 Jan 2004 00:22:04 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmnZg-0004yp-LH
	for ietf@asgard.ietf.org; Sat, 31 Jan 2004 00:21:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24832
	for <ietf@ietf.org>; Sat, 31 Jan 2004 00:21:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmnZe-0007d3-00
	for ietf@ietf.org; Sat, 31 Jan 2004 00:21:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmnYi-0007Wd-00
	for ietf@ietf.org; Sat, 31 Jan 2004 00:20:45 -0500
Received: from sentosa.post1.com ([202.27.17.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1AmnYA-0007P0-00
	for IETF@ietf.org; Sat, 31 Jan 2004 00:20:10 -0500
Received: (qmail 78777 invoked from network); 31 Jan 2004 05:40:03 -0000
Received: from bb220-255-187-71.singnet.com.sg (HELO pobox.org.sg) (220.255.187.71)
  by sentosa.post1.com with SMTP; 31 Jan 2004 05:40:03 -0000
Message-ID: <401B3ADC.7000803@pobox.org.sg>
Date: Sat, 31 Jan 2004 13:19:24 +0800
From: James Seng <jseng@pobox.org.sg>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, zh-cn, zh-tw, ja, ko
MIME-Version: 1.0
To: Spencer Dawkins <spencer@mcsr-labs.org>
CC: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
Subject: Re: Death of the Internet - details at 11
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu> <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com> <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us> <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us> <654669B6-524E-11D8-98F9-000A95CD987A@muada.com> <4018FFFB.2010201@stewart.chicago.il.us> <F2D4652B-52F9-11D8-98F9-000A95CD987A@muada.com> <Pine.GSO.4.58.0401301944040.6101@stimpy.eecis.udel.edu> <049e01c3e7af$9809fbb0$0400a8c0@DFNJGL21>
In-Reply-To: <049e01c3e7af$9809fbb0$0400a8c0@DFNJGL21>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pricing and architecture of the Internet: Historical perspectives from 
telecommunications and transportation, Andrew Odlyzko

http://www.dtc.umn.edu/~odlyzko/doc/pricing.architecture.pdf

would give you very new perspective to all these so-called "threats".

-James Seng

Spencer Dawkins wrote:

> Armondo - nice discussion.
> 
> Just a couple of notes on one of my favorite topics...
> 
> Spencer
> 
> ----- Original Message ----- 
> From: "Armando L. Caro Jr." <me@armandocaro.net>
> To: "Iljitsch van Beijnum" <iljitsch@muada.com>
> Cc: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>;
> "'ietf@ietf.org' Discussion" <IETF@ietf.org>
> Sent: Friday, January 30, 2004 7:14 PM
> Subject: Re: Death of the Internet - details at 11
> 
> 
>>This _kind_ of a solution has already been proposed by Joe Touch and
> 
> Ted
> 
>>Faber in their ICNP 97 paper, "Dynamic Host Routing for Production
> 
> Use of
> 
>>Developmental Networks". It works, but on of the problems is that
> 
> you hide
> 
>>path information from the transport. TCP maintains congestion
> 
> control
> 
>>information about a single destination, with the assumption that the
> 
> path
> 
>>will not change during the connection. If it does occasionally, then
> 
> it's
> 
>>fine. However, with multihoming, the change may be a common
> 
> occurance
> 
>>throughtout the lifetime of a connection depending on the
> 
> application and
> 
>>the use of the multiple paths (failover, concurrent multipath
> 
> transfer,
> 
>>etc). So TCP (or whatever transport) should not be blind to the fact
> 
> that
> 
>>data is potentially going over a different path. Otherwise, the
> 
> congestion
> 
>>control parameters/algorithms will not work properly.
> 
> 
> Yeah, you might think that. I did, when we proposed TRIGTRAN (how
> could finding out that a link failed be WRONG?).
> 
> The problem was that when we were discussing notifications like
> PATH_CHANGE (or whatever we ended up calling it), the TCP has a
> decision to make when it sees PATH_CHANGE - "do I
> 
> - slow start, recognizing that I now haven't got the remotest clue
> what the path capacity is, or
> 
> - maintain my congestion window and try to actually LOSE something
> before I decide that I need to adjust?"
> 
> TCPs have been ignoring things like ICMP Unreachable for decades, so
> the second idea isn't totally bogus - they respond to actual loss, not
> to the potential for loss.
> 
> Once you decide that your path change is no different than cross
> traffic starting and stopping, which we adjust to after losing
> something, transports ignoring path changes makes a lot of sense. If
> you are changing paths frequently (and round-robin would be the
> limiting case), slow-starting every time you change paths is
> excessive - and, if you're going to respond to PATH_CHANGE, what else
> would you do? You could do congestion avoidance during the first round
> trip, or actually lose something and do congestion avoidance on the
> second round trip - not a big difference, conceptually.
> 
> [deleted down to]
> 
> 
>>>>Yes.. if you wanted to do HTTP over SCTP and use features such
>>>>as streams you WOULD WANT to extend HTML so that you could
>>>>have the client "get pages" on particular streams...
>>>
>>>Why extend the markup language?
>>
>>I think that was a typo...
> 
> 
> Commonly-deployed browsers don't pipeline HTTP requests because they
> don't get any advice on (1) size of objects or (2) recommended
> retrieval order. Extending HTML to provide one or the other would make
> at least as much sense as extending HTTP.
> 
> 
>>>HTTP has supported sessions that stay alive so they can be used
> 
> for
> 
>>>more than just one operation for many years now. The trouble is
> 
> that
> 
>>>you get head of line blockage if you fetch all the elements that
> 
> make
> 
>>>up a WWW page in serial fashion. Being able to multiplex different
>>>streams (within an SCTP session) that all fetch elements
> 
> simultenously
> 
>>>would fix this. This of course requires changes to both HTTP
> 
> clients
> 
>>>and servers, but it should otherwise be transparent to the user.
> 
> 
> As above - fetching all elements simultaneously makes perfect sense to
> transport guys, but can give pretty flaky-looking pages during
> retrieval. If you think HTTP/1.1 with two connections makes sense, you
> might start retrieving the smallest elements on one connection and the
> largest on the other, and meet in the middle, but since the browser
> has no idea how to do this, it's pretty difficult to resist the
> temptation to wait for a connection to become idle before sending
> another request.
> 
> And this is why HTTP over cellular links has horrible throughput - if
> you stop-and-wait request 300-byte objects with one-second RTTs, your
> throughputp looks a LOT like 300 bytes per second...
> 
> 
> 
> 



From owner-ietf@ietf.org  Sat Jan 31 13:24:49 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29698
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 Jan 2004 13:24:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AmzcB-00038K-TQ
	for ietf-list@asgard.ietf.org; Sat, 31 Jan 2004 13:13:07 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmzbF-00037k-9a
	for ietf@asgard.ietf.org; Sat, 31 Jan 2004 13:12:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29443
	for <ietf@ietf.org>; Sat, 31 Jan 2004 13:12:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmzbE-0002BY-00
	for ietf@ietf.org; Sat, 31 Jan 2004 13:12:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmzaF-00024U-00
	for ietf@ietf.org; Sat, 31 Jan 2004 13:11:08 -0500
Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmzZH-0001rz-00
	for IETF@ietf.org; Sat, 31 Jan 2004 13:10:07 -0500
Received: by mail.eecis.udel.edu (Postfix, from userid 62)
	id 52C9532EB0; Sat, 31 Jan 2004 13:06:48 -0500 (EST)
Received: from stimpy.eecis.udel.edu (stimpy.eecis.udel.edu [128.4.40.17])
	by mail.eecis.udel.edu (Postfix) with ESMTP
	id 60B7D32E62; Sat, 31 Jan 2004 13:06:47 -0500 (EST)
Date: Sat, 31 Jan 2004 13:06:47 -0500 (EST)
From: "Armando L. Caro Jr." <me@armandocaro.net>
X-X-Sender: acaro@stimpy.eecis.udel.edu
To: Spencer Dawkins <spencer@mcsr-labs.org>
Cc: Janardhan Iyengar <iyengar@cis.udel.edu>,
        "'ietf@ietf.org' Discussion" <IETF@ietf.org>
Subject: Re: Death of the Internet - details at 11
In-Reply-To: <049e01c3e7af$9809fbb0$0400a8c0@DFNJGL21>
Message-ID: <Pine.GSO.4.58.0401311250190.17658@stimpy.eecis.udel.edu>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
 <116512686.1074013651@scan.jck.com> <19410259999.20040128073646@brandenburg.com>
 <224923613.1075293579@scan.jck.com> <40182303.7000300@stewart.chicago.il.us>
 <89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com> <40183C10.10401@stewart.chicago.il.us>
 <654669B6-524E-11D8-98F9-000A95CD987A@muada.com> <4018FFFB.2010201@stewart.chicago.il.us>
 <F2D4652B-52F9-11D8-98F9-000A95CD987A@muada.com>
 <Pine.GSO.4.58.0401301944040.6101@stimpy.eecis.udel.edu>
 <049e01c3e7af$9809fbb0$0400a8c0@DFNJGL21>
X-Sanitizer: This message has been sanitized!
X-Sanitizer-URL: http://mailtools.anomy.net/
X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm,v 1.64 2002/10/22 MIME-Version: 1.0
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 30 Jan 2004, Spencer Dawkins wrote:

> Yeah, you might think that. I did, when we proposed TRIGTRAN (how
> could finding out that a link failed be WRONG?).
>
> The problem was that when we were discussing notifications like
> PATH_CHANGE (or whatever we ended up calling it), the TCP has a
> decision to make when it sees PATH_CHANGE - "do I
>
> - slow start, recognizing that I now haven't got the remotest clue
> what the path capacity is, or
>
> - maintain my congestion window and try to actually LOSE something
> before I decide that I need to adjust?"
>
> TCPs have been ignoring things like ICMP Unreachable for decades, so
> the second idea isn't totally bogus - they respond to actual loss, not
> to the potential for loss.
>
> Once you decide that your path change is no different than cross
> traffic starting and stopping, which we adjust to after losing
> something, transports ignoring path changes makes a lot of sense. If
> you are changing paths frequently (and round-robin would be the
> limiting case), slow-starting every time you change paths is
> excessive - and, if you're going to respond to PATH_CHANGE, what else
> would you do? You could do congestion avoidance during the first round
> trip, or actually lose something and do congestion avoidance on the
> second round trip - not a big difference, conceptually.

I understand your point, and I have heard this argument before when I
brought up the same issue in various Mobile IP meetings/talks. But I don't
agree. How is this behavior different from simply beginning a new TCP
connection with a large cwnd?

Also, if multihoming is supported at the transport so that the transport
is aware of the different paths (cwnd, ssthresh, etc), then there is a
potential of doing concurrent multipath transfer (aka load balancing, load
sharing, etc) at the transport layer.  Otherwise, CMT cannot be done
well... at least not any better than an application load balancing across
multiple connections. Jana Iyengar is doing work in this area. I cc'd him
in case he wants to jump in here.

~armando

0--                                              --0
| Armando L. Caro Jr.  |  Protocol Engineering Lab |
| www.armandocaro.net  |    University of Delaware |
0--                                              --0



From owner-ietf@ietf.org  Sat Jan 31 14:20:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01536
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 Jan 2004 14:20:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1An0Z5-00044s-62
	for ietf-list@asgard.ietf.org; Sat, 31 Jan 2004 14:13:59 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1An0YO-00044G-AH
	for ietf@asgard.ietf.org; Sat, 31 Jan 2004 14:13:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01314
	for <ietf@ietf.org>; Sat, 31 Jan 2004 14:13:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1An0YN-0001H9-00
	for ietf@ietf.org; Sat, 31 Jan 2004 14:13:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1An0XO-00019f-00
	for ietf@ietf.org; Sat, 31 Jan 2004 14:12:15 -0500
Received: from shield.kudpc.kyoto-u.ac.jp ([130.54.9.41])
	by ietf-mx with smtp (Exim 4.12)
	id 1An0WY-00013e-00
	for ietf@ietf.org; Sat, 31 Jan 2004 14:11:22 -0500
Received: by shield.kudpc.kyoto-u.ac.jp; id EAA21774; Sun, 1 Feb 2004 04:11:20 +0900
Received: from localhost(127.0.0.1) by shield.kudpc.kyoto-u.ac.jp via csmap (V4.1)
	id srcAAAloaOHQ; Sun, 1 Feb 04 04:11:19 +0900
Received: from mbox.kudpc.kyoto-u.ac.jp (mbox.kudpc.kyoto-u.ac.jp [130.54.9.32])
	by shield.kudpc.kyoto-u.ac.jp (8.11.3/8.11.3) with ESMTP id i0VJBJ021770
	for <ietf@ietf.org>; Sun, 1 Feb 2004 04:11:19 +0900 (JST)
Received: from blackpearl.arifumi.net (p622171.kyotac00.ap.so-net.ne.jp [219.98.33.113])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by mbox.kudpc.kyoto-u.ac.jp (Postfix) with ESMTP id CCE1048C097
	for <ietf@ietf.org>; Sun,  1 Feb 2004 04:11:19 +0900 (JST)
Date: Sun, 1 Feb 2004 04:10:31 +0900
From: arifumi <a@arifumi.net>
To: ietf@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-Id: <20040201041031.6a02c0a8@blackpearl.arifumi.net>
In-Reply-To: <16410.36837.865239.515682@thomasm-u1.cisco.com>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>	<116512686.1074013651@scan.jck.com>
	<19410259999.20040128073646@brandenburg.com>
	<224923613.1075293579@scan.jck.com>
	<40182303.7000300@stewart.chicago.il.us>
	<89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com>
	<40183C10.10401@stewart.chicago.il.us>
	<654669B6-524E-11D8-98F9-000A95CD987A@muada.com>
	<4018FFFB.2010201@stewart.chicago.il.us>
	<6.0.1.1.2.20040129094026.0308c540@mail.amaranth.net>
	<401A4A0C.4010007@stewart.chicago.il.us>
	<6.0.1.1.2.20040130110425.033b1dc8@mail.amaranth.net>
	<16410.36837.865239.515682@thomasm-u1.cisco.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

(Resend)
Hi Mike,

On Fri, 30 Jan 2004 09:09:57 -0800 (PST)
Michael Thomas <mat@cisco.com> wrote:

>    Now wait a minute. It's your bandwidth... shouldn't 
>    you be _shaping_ his traffic if there's some reason
>    he shouldn't be using one path or another? And thus
>    provide negative feedback so that he has incentive
>    to use the path that you want him to use? After all,
>    the end consumer is likely clueless about your
>    network and is going to do whatever they can to
>    get what they're after -- bandwidth. Sounds to
>    me that if he's able to cause your bills go
>    through the ceiling _you're_ doing something
>    wrong.

I guess Daniel's problem is not that simply solved.
Just the shaping isn't enough, because the backup path should
be fully used only when the main path has some "trouble".
Moreover, "trouble" isn't also such a simple thing like
a direct link failure, such as fibre cut, but it includes
yet upper link(ISP)'s failure.
This is not even a problem of "OK" or "Not OK".
I mean, those cases are very likely to happen that you can
communicate with only a few of ASes through the main path.

So, though you may say "we can stop the shaping if we have
troubles in the main path," it is not such easy.
You have to change the bandwidth of backup path's shaping
depending on the number of routes passed from main path's
upstream ISP.

I'm not familiar with BGP routing techniques that much,
but I guess these policies can be implemented, right ?

Though I believe end-to-end multihoming is the way to go,
I don't have a good answer for this problem.

-- 
/arifumi
a@arifumi.net



From owner-ietf@ietf.org  Sat Jan 31 16:42:38 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06607
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 Jan 2004 16:42:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1An2fi-0005v3-5R
	for ietf-list@asgard.ietf.org; Sat, 31 Jan 2004 16:28:58 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1An2f1-0005uQ-5X
	for ietf@asgard.ietf.org; Sat, 31 Jan 2004 16:28:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05951
	for <ietf@ietf.org>; Sat, 31 Jan 2004 16:28:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1An2ez-00007r-00
	for ietf@ietf.org; Sat, 31 Jan 2004 16:28:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1An2e5-000018-00
	for ietf@ietf.org; Sat, 31 Jan 2004 16:27:17 -0500
Received: from kc-msxproto3.kc.umkc.edu ([134.193.143.160])
	by ietf-mx with esmtp (Exim 4.12)
	id 1An2dj-0007jL-00
	for IETF@ietf.org; Sat, 31 Jan 2004 16:26:55 -0500
Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211] RDNS failed) by kc-msxproto3.kc.umkc.edu with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 31 Jan 2004 15:26:54 -0600
x-mimeole: Produced By Microsoft Exchange V6.5.6944.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: Death of the Internet - details at 11
Date: Sat, 31 Jan 2004 15:26:54 -0600
Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B01108275@KC-MAIL4.kc.umkc.edu>
Thread-Topic: Death of the Internet - details at 11
Thread-Index: AcPnmTbMFFVtXs/zRBGARVktEBYGLAAnJ/3Z
From: "Ayyasamy, Senthilkumar  \(UMKC-Student\)" <saq66@umkc.edu>
To: "Armando L. Caro Jr." <me@armandocaro.net>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>
Cc: "Randall R. Stewart \(home\)" <randall@stewart.chicago.il.us>,
        "'ietf@ietf.org' Discussion" <IETF@ietf.org>
X-OriginalArrivalTime: 31 Jan 2004 21:26:54.0933 (UTC) FILETIME=[F3064050:01C3E840]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=FROM_ENDS_IN_NUMS autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> However, with multihoming, the change may be a common occurance
> throughtout the lifetime of a connection depending on the application =
and
> the use of the multiple paths (failover, concurrent multipath =
transfer,
> etc). So TCP (or whatever transport) should not be blind to the fact =
that
> data is potentially going over a different path. Otherwise, the =
congestion
> control parameters/algorithms will not work properly.
=20
I agree. But, as you mention in an other mail, TCP/SCTP/DCCP has a limit =
to=20
do simultaneous tranfer. It is impossible to provide concurrent =
multipath
transfer without changing the cc algorithms. But, given current options,
transport is the better judge to do zero click fail-over.=20

> Also, since the transport is maintaining per path information, it is =
in
> the best decision to decide which path to use.=20
=20
*nod*. It is the main reason why multi addressing is the only=20
architectural possibility to do a scalable MH. The problem with
the remaining solutions (at shim/new identity/network layer) is=20
that they hide the redundancy factor (multiple address -MA) from
the users. Given the current state (failures, misconfigurations
and rate limitations,) e2e check (by measurements) is the only=20
option to check path availability. The MA feature gives user a=20
chance to make a choice based on e2e reachability checks.=20
=20
I dont know why people get suprised by explicit announcement of=20
MA. we have been doing this kind of explicit announcement both=20
in DNS ( multiple NX records) and SMTP ( multiple MX records.)=20
So, in a way SMTP reliability is due to explicit announcement of=20
multiple MX records.=20
=20
id/loc split proposals are cool. But, without modifying the routing
architecture, they can never provide a e2e reliability or explicit=20
user control feature. OTOH, I don't forsee any routing change at=20
*architectural* level in the near future. It is time to think=20
on why id/loc split proposals without routing architecture change=20
kill the e2e control/reliability options and are architecturally=20
incomplete.
=20
So, it is clear that a combination/subset of host-centric MH,=20
transport MA and BGP MH (if there exists a solution which=20
doesn't bloat routing table) is the ONLY possibility to do a=20
scalable MHv6.



From owner-ietf@ietf.org  Sat Jan 31 20:20:12 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14855
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 Jan 2004 20:20:12 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1An69U-0000FI-FN
	for ietf-list@asgard.ietf.org; Sat, 31 Jan 2004 20:11:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1An690-0000Ed-6Q
	for ietf@asgard.ietf.org; Sat, 31 Jan 2004 20:11:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14658
	for <ietf@ietf.org>; Sat, 31 Jan 2004 20:11:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1An68w-0001uz-00
	for ietf@ietf.org; Sat, 31 Jan 2004 20:11:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1An681-0001p3-00
	for ietf@ietf.org; Sat, 31 Jan 2004 20:10:26 -0500
Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1An67B-0001j4-00
	for IETF@ietf.org; Sat, 31 Jan 2004 20:09:33 -0500
Received: by mail.eecis.udel.edu (Postfix, from userid 62)
	id 664E232C31; Sat, 31 Jan 2004 20:03:27 -0500 (EST)
Received: from stimpy.eecis.udel.edu (stimpy.eecis.udel.edu [128.4.40.17])
	by mail.eecis.udel.edu (Postfix) with ESMTP
	id 9BFE732C02; Sat, 31 Jan 2004 20:03:26 -0500 (EST)
Date: Sat, 31 Jan 2004 20:03:26 -0500 (EST)
From: "Armando L. Caro Jr." <me@armandocaro.net>
X-X-Sender: acaro@stimpy.eecis.udel.edu
To: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
Cc: "'ietf@ietf.org' Discussion" <IETF@ietf.org>
Subject: RE: Death of the Internet - details at 11
In-Reply-To: <5EF7D95E17BDAD4A968C812E5ABC390B01108275@KC-MAIL4.kc.umkc.edu>
Message-ID: <Pine.GSO.4.58.0401311954170.23518@stimpy.eecis.udel.edu>
References: <5EF7D95E17BDAD4A968C812E5ABC390B01108275@KC-MAIL4.kc.umkc.edu>
X-Sanitizer: This message has been sanitized!
X-Sanitizer-URL: http://mailtools.anomy.net/
X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm,v 1.64 2002/10/22 MIME-Version: 1.0
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 31 Jan 2004, Ayyasamy, Senthilkumar  (UMKC-Student) wrote:

> > However, with multihoming, the change may be a common occurance
> > throughtout the lifetime of a connection depending on the application and
> > the use of the multiple paths (failover, concurrent multipath transfer,
> > etc). So TCP (or whatever transport) should not be blind to the fact that
> > data is potentially going over a different path. Otherwise, the congestion
> > control parameters/algorithms will not work properly.
>
> I agree. But, as you mention in an other mail, TCP/SCTP/DCCP has a limit to
> do simultaneous tranfer. It is impossible to provide concurrent multipath
> transfer without changing the cc algorithms.

Yes, I never meant to imply that the cc algorithms could remain the same.
I just wanted to point out that concurrent multipath transfer (CMT) can
not be done well without multihoming support at the transport. At UD, we
(in particular, Jana Iyengar) are investigating CMT in multihomed
transports (ie, SCTP) so that only the sender has to modify it's cc
algorithms to remain Internet-friendly.

> But, given current options, transport is the better judge to do zero
> click fail-over.

Yes, I think so.

~armando

0--                                              --0
| Armando L. Caro Jr.  |  Protocol Engineering Lab |
| www.armandocaro.net  |    University of Delaware |
0--                                              --0



From owner-ietf@ietf.org  Sat Jan 31 21:32:01 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17930
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 Jan 2004 21:32:01 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1An7I8-0001WT-30
	for ietf-list@asgard.ietf.org; Sat, 31 Jan 2004 21:24:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1An7HO-0001Vf-0r
	for ietf@asgard.ietf.org; Sat, 31 Jan 2004 21:24:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17616
	for <ietf@ietf.org>; Sat, 31 Jan 2004 21:24:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1An7HL-0002nF-00
	for ietf@ietf.org; Sat, 31 Jan 2004 21:24:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1An7G3-0002V8-00
	for ietf@ietf.org; Sat, 31 Jan 2004 21:22:47 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1An7E5-0001xF-00
	for ietf@ietf.org; Sat, 31 Jan 2004 21:20:45 -0500
Received: from BBFUJIP (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with SMTP id i112Rod17527;
	Sat, 31 Jan 2004 18:27:50 -0800
From: Dave Crocker <dhc@dcrocker.net>
To: Haim Rochberger <haimro@p-cube.com>
CC: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>,
        "'ietf@ietf.org'" <ietf@ietf.org>
X-Mailer: PocoMail 3.01 (1661) - EVALUATION VERSION
X-URL: http://www.pocomail.com/
Reply-To: dcrocker@brandenburg.com
Date: Sun, 1 Feb 2004 09:47:09 +0900
Message-ID: <2004219479.241869@BBFUJIP>
In-Reply-To: <BB7797D6BF684A4B91ABB19AB6A579C567C3B3@ilmx1.p-cube.com>
Subject: Re: packets of multiple users sent over the same TCP/IP session
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Haim,

HR> SMPP is a good example to what I am looking for, and I am trying to see if
HR> other
HR> protocol foreseen in the future (or past) have the same characteristics:

RFC1692, Transport Multiplexing Protocol, was designed for the
operation you appear to be describing.

As long as you have access to the necessary bits of protocol software
in the stack, it's a simple, flexible and efficient mechanism.

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







From owner-ietf@ietf.org  Sat Jan 31 23:18:47 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22142
	for <ietf-web-archive@odin.ietf.org>; Sat, 31 Jan 2004 23:18:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1An8wg-0003Gn-V3
	for ietf-list@asgard.ietf.org; Sat, 31 Jan 2004 23:10:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AmsgN-0000kr-V7
	for ietf@asgard.ietf.org; Sat, 31 Jan 2004 05:48:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17225
	for <ietf@ietf.org>; Sat, 31 Jan 2004 05:48:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmsgL-00078Y-00
	for ietf@ietf.org; Sat, 31 Jan 2004 05:48:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmsfO-00071h-00
	for ietf@ietf.org; Sat, 31 Jan 2004 05:47:59 -0500
Received: from shield.kudpc.kyoto-u.ac.jp ([130.54.9.41])
	by ietf-mx with smtp (Exim 4.12)
	id 1Amsew-0006uW-00
	for ietf@ietf.org; Sat, 31 Jan 2004 05:47:30 -0500
Received: by shield.kudpc.kyoto-u.ac.jp; id TAA14338; Sat, 31 Jan 2004 19:47:28 +0900
Received: from localhost(127.0.0.1) by shield.kudpc.kyoto-u.ac.jp via csmap (V4.1)
	id srcAAAtva4_B; Sat, 31 Jan 04 19:47:27 +0900
Received: from mbox.kudpc.kyoto-u.ac.jp (mbox.kudpc.kyoto-u.ac.jp [130.54.9.32])
	by shield.kudpc.kyoto-u.ac.jp (8.11.3/8.11.3) with ESMTP id i0VAlRK14332
	for <ietf@ietf.org>; Sat, 31 Jan 2004 19:47:27 +0900 (JST)
Received: from blackpearl.arifumi.net (pddc1fe.kyotac00.ap.so-net.ne.jp [218.221.193.254])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by mbox.kudpc.kyoto-u.ac.jp (Postfix) with ESMTP id 8C82748C097
	for <ietf@ietf.org>; Sat, 31 Jan 2004 19:47:27 +0900 (JST)
Date: Sat, 31 Jan 2004 19:46:41 +0900
From: arifumi <a@arifumi.net>
To: ietf@ietf.org
Subject: Re: Death of the Internet - details at 11
Message-Id: <20040131194641.2d0d7e92@blackpearl.arifumi.net>
In-Reply-To: <16410.36837.865239.515682@thomasm-u1.cisco.com>
References: <20040113030337.B617D872FB@mercury.lcs.mit.edu>
	<116512686.1074013651@scan.jck.com>
	<19410259999.20040128073646@brandenburg.com>
	<224923613.1075293579@scan.jck.com>
	<40182303.7000300@stewart.chicago.il.us>
	<89289E9F-51DE-11D8-98F9-000A95CD987A@muada.com>
	<40183C10.10401@stewart.chicago.il.us>
	<654669B6-524E-11D8-98F9-000A95CD987A@muada.com>
	<4018FFFB.2010201@stewart.chicago.il.us>
	<6.0.1.1.2.20040129094026.0308c540@mail.amaranth.net>
	<401A4A0C.4010007@stewart.chicago.il.us>
	<6.0.1.1.2.20040130110425.033b1dc8@mail.amaranth.net>
	<16410.36837.865239.515682@thomasm-u1.cisco.com>
X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Mike,

On Fri, 30 Jan 2004 09:09:57 -0800 (PST)
Michael Thomas <mat@cisco.com> wrote:

>    Now wait a minute. It's your bandwidth... shouldn't 
>    you be _shaping_ his traffic if there's some reason
>    he shouldn't be using one path or another? And thus
>    provide negative feedback so that he has incentive
>    to use the path that you want him to use? After all,
>    the end consumer is likely clueless about your
>    network and is going to do whatever they can to
>    get what they're after -- bandwidth. Sounds to
>    me that if he's able to cause your bills go
>    through the ceiling _you're_ doing something
>    wrong.

I guess Daniel's problem is not that simply solved.
Just the shaping isn't enough, because the backup path should
be fully used only when the main path has some "trouble".
Moreover, "trouble" isn't also such a simple thing like
a direct link failure, such as fibre cut, but it includes
yet upper link(ISP)'s failure.
This is not even a problem of "OK" or "Not OK".
I mean, those cases are very likely to happen that you can
communicate with only a few of ASes through the main path.

So, though you may say "we can stop the shaping if we have
troubles in the main path," it is not such easy.
You have to change the bandwidth of backup path's shaping
depending on the number of routes passed from main path's
upstream ISP.

I'm not familiar with BGP routing techniques that much,
but I guess these policies can be implemented, right ?

Though I believe end-to-end multihoming is the way to go,
I don't have a good answer for this problem.

-- 
/arifumi
a@arifumi.net





