From ietf-bounces@ietf.org  Tue Jun  1 03:20:55 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01421
	for <ietf-archive@ietf.org>; Tue, 1 Jun 2004 03:20:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BV3UJ-0006gf-NJ
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 03:15:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BV3T9-0006B3-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 03:13:56 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BV3SB-0005Rg-00; Tue, 01 Jun 2004 03:12:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BV3GY-0005BK-QH; Tue, 01 Jun 2004 03:00:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BV2t7-0001W5-Ri
	for ietf@megatron.ietf.org; Tue, 01 Jun 2004 02:36:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24714
	for <ietf@ietf.org>; Tue, 1 Jun 2004 02:36:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BV2t5-0005Rs-Jb
	for ietf@ietf.org; Tue, 01 Jun 2004 02:36:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BV2s5-00050q-00
	for ietf@ietf.org; Tue, 01 Jun 2004 02:35:37 -0400
Received: from web8005.mail.in.yahoo.com ([203.199.70.65])
	by ietf-mx with smtp (Exim 4.12) id 1BV2rE-0004A2-00
	for Ietf@ietf.org; Tue, 01 Jun 2004 02:34:44 -0400
Message-ID: <20040601063408.50672.qmail@web8005.mail.in.yahoo.com>
Received: from [210.212.200.5] by web8005.mail.in.yahoo.com via HTTP;
	Tue, 01 Jun 2004 07:34:08 BST
Date: Tue, 1 Jun 2004 07:34:08 +0100 (BST)
From: =?iso-8859-1?q?ven=20san?= <vensan_gvsr@yahoo.co.in>
To: Ietf@ietf.org
MIME-Version: 1.0
Subject: recieved your mail
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1593634103=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,HTML_30_40,HTML_MESSAGE 
	autolearn=no version=2.60

--===============1593634103==
Content-Type: multipart/alternative; boundary="0-937830180-1086071648=:46976"

--0-937830180-1086071648=:46976
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

recieved your mail

Yahoo! India Matrimony: Find your partner online.
--0-937830180-1086071648=:46976
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>recieved your mail</DIV><p><font face=arial size=-1>
<a href="http://in.rd.yahoo.com/specials/mailtg/*http://yahoo.shaadi.com/india-matrimony/" target="_blank">
<b>Yahoo! India Matrimony</a>:</b> Find your partner 
<a href="http://in.rd.yahoo.com/specials/mailtg2/*http://yahoo.shaadi.com/india-matrimony/community.php" target="_blank">online</a>.</font>
--0-937830180-1086071648=:46976--


--===============1593634103==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1593634103==--



From mailman-bounces@ietf.org  Tue Jun  1 05:32:46 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09179
	for <ietf-archive@ietf.org>; Tue, 1 Jun 2004 05:32:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BV5dW-0005Te-5H
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 05:32:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BV5ca-00053z-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 05:31:49 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BV5cB-0004du-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 05:31:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BV5AO-0000Pm-Mu
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 05:02:40 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: ietf-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.1995.1086080448.28143.mailman@lists.ietf.org>
Date: Tue, 01 Jun 2004 05:00:48 -0400
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@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,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for ietf-archive@ietf.org:

List                                     Password // URL
----                                     --------  
ifmib@ietf.org                           FmlC      
https://www1.ietf.org/mailman/options/ifmib/ietf-archive%40ietf.org

ietf@ietf.org                            puaceh    
https://www1.ietf.org/mailman/options/ietf/ietf-archive%40ietf.org


From mailman-bounces@mailman.isi.edu  Tue Jun  1 08:44:05 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24525
	for <ietf-archive@ietf.org>; Tue, 1 Jun 2004 08:44:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BV8ch-0004qE-RN
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 08:44:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BV8bc-0004O5-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 08:43:00 -0400
Received: from gamma.isi.edu ([128.9.144.145])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BV8ac-0003vZ-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 08:41:59 -0400
Received: from gamma.isi.edu (localhost [127.0.0.1])
	by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i51CNCi20428
	for <ietf-archive@ietf.org>; Tue, 1 Jun 2004 05:23:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: isi.edu mailing list memberships reminder
From: mailman-owner@ISI.EDU
To: ietf-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.1946.1086091466.7619.mailman@mailman.isi.edu>
Date: Tue, 01 Jun 2004 05:04:26 -0700
Precedence: bulk
X-BeenThere: mailman@mailman.isi.edu
X-Mailman-Version: 2.1.4
List-Id: Mailman site list <mailman.mailman.isi.edu>
X-List-Administrivia: yes
Sender: mailman-bounces@mailman.isi.edu
Errors-To: mailman-bounces@mailman.isi.edu
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: mailman-bounces@mailman.isi.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.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your isi.edu mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@isi.edu) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@isi.edu.  Thanks!

Passwords for ietf-archive@ietf.org:

List                                     Password // URL
----                                     --------  
tcpsat@isi.edu                           okecem    
http://mailman.isi.edu/mailman/options/tcpsat/ietf-archive%40ietf.org


From mailman-admin@ietf.org  Tue Jun  1 09:31:22 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28508
	for <ietf-archive@ietf.org>; Tue, 1 Jun 2004 09:31:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BV9MQ-0001pm-Mh
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 09:31:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BV9LQ-0001Lf-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 09:30:20 -0400
Received: from jupiter.cnri.reston.va.us ([132.151.1.18] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BV9KS-0000sC-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 09:29:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BV8tJ-0007zy-Cu
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 09:01:17 -0400
Date: Tue, 01 Jun 2004 09:01:17 -0400
Message-ID: <20040601130117.26555.4074.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: ietf-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
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

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, ietf-request@ietf.org) containing just the word
'help' in the message body, and an email message will be sent to you
with instructions.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for ietf-archive@ietf.org:

List                                     Password // URL
----                                     --------  
ifmib@ietf.org                           FmlC      
https://www1.ietf.org/mailman/options/ifmib/ietf-archive%40ietf.org

ietf@ietf.org                            puaceh    
https://www1.ietf.org/mailman/options/ietf/ietf-archive%40ietf.org


From ietf-bounces@ietf.org  Tue Jun  1 14:31:45 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04801
	for <ietf-archive@ietf.org>; Tue, 1 Jun 2004 14:31:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVE38-0002L8-W7
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 14:31:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVDj4-0005yd-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 14:11:03 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVDec-0004BB-01; Tue, 01 Jun 2004 14:06:26 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BVDc0-0006pC-N0; Tue, 01 Jun 2004 14:03:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVBuE-000369-CD; Tue, 01 Jun 2004 12:14:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTmML-0002sn-3m
	for ietf@megatron.ietf.org; Fri, 28 May 2004 14:45:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23335
	for <ietf@ietf.org>; Fri, 28 May 2004 14:45:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BTmMJ-0007kF-PR
	for ietf@ietf.org; Fri, 28 May 2004 14:45:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTmL7-0007Fn-00
	for ietf@ietf.org; Fri, 28 May 2004 14:44:22 -0400
Received: from sa.vix.com ([204.152.187.1]) by ietf-mx with esmtp (Exim 4.12)
	id 1BTmJn-0006IV-00
	for ietf@ietf.org; Fri, 28 May 2004 14:43:00 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 1370A13DFB
	for <ietf@ietf.org>; Fri, 28 May 2004 18:42:27 +0000 (GMT)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ietf@ietf.org
In-Reply-To: Message from Ted Hardie <hardie@qualcomm.com> 
	of "Fri, 28 May 2004 09:51:53 MST."
	<p06100504bcdd19f751de@[129.46.227.161]> 
X-Mailer: MH-E 7.4; nmh 1.0.4; GNU Emacs 21.3.1
Date: Fri, 28 May 2004 18:42:27 +0000
Message-Id: <20040528184227.1370A13DFB@sa.vix.com>
X-Mailman-Approved-At: Tue, 01 Jun 2004 12:14:21 -0400
Subject: Re: spoofing email addresses 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> As the AD who sponsored this work, I have to disagree.   ...
> The recent interim meeting resulted in an agreement to work on
> a converged spec taking ideas from SPF and Caller-ID.

Why?  These are latecomers to the field.  Or is it because of this:

<http://www.internetwk.com/breakingNews/showArticle.jhtml?articleID=21100498>

	Microsoft To Merge Caller ID With SPF Anti-Spam Scheme 

	Microsoft on Tuesday agreed to blend its Caller ID for E-mail
	anti-spam proposal with another of the leading domain
	authentication schemes, Sender Policy Framework (SPF).

	The company reached the agreement with Meng Wong, the author of
	SPF, to merge the two proposals into one specification that will
	be presented to the Internet Engineering Task Force (IETF)
	standards body in June.

	...

> I do believe there are some tractable pieces here we can pull
> off of the problem and solve, and I believe the working group
> is committed to that task, no matter who proposes the solution.

I think the working group is committed to the appearance of relevance,
and now that there's a moving juggernaut, it's become important to get
out in front of it somehow and appear to be leading.  From [ibid]:

	Both Caller ID, which Microsoft chairman Bill Gates first touted
	in February, and Wong's SPF would confirm the sender's domain.

	...

	"We're pleased to see Microsoft and the SPF community working
	together on a unified specification," said Andrew Newton,
	co-chair of the IETF working group that handles domain
	identification issues, in a statement.

If there's a more blatant example of rubber stamping in the history of
IETF, then I hope a better historian than I can share the archives with
me.  Right now there's an elephant in the room with us and it's called
"fully verified opt-in" and this elephant is somehow invisible.  Microsoft
has been doing verification for years now, so it's not as if they would
increase their costs or lose revenue if they just came out and told the
world to do the same.  Even Yahoo recently sent me a verify-o-gram, so
the tide is turning.  But still, the elephant remains invisible, and we
have a federal anti-spam law that allows unverified opt-out.

It's as though we want to stop forgery and make everybody run
nonexecutable stack segments in XP to prevent a bazillion bots from
relaying spam to us, so as to prevent "wild spam" and yet, by dint of
ignoring the invisible elephant, ensuring that it will always be
possible for "reputable" companies to spam like crazy.  Which always
made sense to me during the years when Microsoft wasn't doing
verification, but it doesn't make any sense to me any more.

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


From ietf-bounces@ietf.org  Tue Jun  1 14:32:14 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04954
	for <ietf-archive@ietf.org>; Tue, 1 Jun 2004 14:32:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVE3c-0002RW-Be
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 14:32:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVDju-00069h-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 14:11:54 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVDef-00048x-00; Tue, 01 Jun 2004 14:06:29 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BVDbR-0006dF-07; Tue, 01 Jun 2004 14:03:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVBuC-00033j-EX; Tue, 01 Jun 2004 12:14:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTi3Y-00028J-PC
	for ietf@megatron.ietf.org; Fri, 28 May 2004 10:09:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02836
	for <ietf@ietf.org>; Fri, 28 May 2004 10:09:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BTi3X-0001bn-TV
	for ietf@ietf.org; Fri, 28 May 2004 10:09:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTi2S-00019x-00
	for ietf@ietf.org; Fri, 28 May 2004 10:08:48 -0400
Received: from vapor.isi.edu ([128.9.64.64]) by ietf-mx with esmtp (Exim 4.12)
	id 1BTi1L-0000YS-00
	for ietf@ietf.org; Fri, 28 May 2004 10:07:39 -0400
Received: from [192.168.1.3] (dsl081-036-151.lax1.dsl.speakeasy.net
	[64.81.36.151])
	by vapor.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i4SE7GH20692;
	Fri, 28 May 2004 07:07:16 -0700 (PDT)
In-Reply-To: <2015.1085689155@camelot-054>
References: <2015.1085689155@camelot-054>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <4ECA8FDB-B0B0-11D8-BE68-000A95DBDB84@isi.edu>
Content-Transfer-Encoding: 7bit
From: Aaron Falk <falk@ISI.EDU>
Date: Fri, 28 May 2004 07:07:09 -0700
To: Michael Richardson <Michael.Richardson@seawaynetworks.com>
X-Mailer: Apple Mail (2.613)
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: falk@isi.edu
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 01 Jun 2004 12:14:21 -0400
Cc: ietf@ietf.org
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit


On May 27, 2004, at 1:19 PM, Michael Richardson wrote:

>
> May I suggest that a URL like:
>
>     http://www.ietf.org/std/std0051.txt
>
> be made that can refer to the STD series of documents?

Not sure what's motivating your suggestion.  However, here's one that 
works:

ftp://ftp.rfc-editor.org/in-notes/std/std51.txt

Is that sufficient?

--aaron


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


From ietf-bounces@ietf.org  Tue Jun  1 14:41:10 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07725
	for <ietf-archive@ietf.org>; Tue, 1 Jun 2004 14:41:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVECG-0004QM-JV
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 14:41:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVDw8-0000lg-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 14:24:33 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVDfQ-0004e3-00; Tue, 01 Jun 2004 14:07:16 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BVDRR-0004Bk-V2; Tue, 01 Jun 2004 13:52:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVBnf-0005kA-96; Tue, 01 Jun 2004 12:07:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVAHJ-0005bN-FJ
	for ietf@megatron.ietf.org; Tue, 01 Jun 2004 10:30:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07671
	for <ietf@ietf.org>; Tue, 1 Jun 2004 10:30:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVAHI-00065r-9n
	for ietf@ietf.org; Tue, 01 Jun 2004 10:30:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVAGL-0005eQ-00
	for ietf@ietf.org; Tue, 01 Jun 2004 10:29:10 -0400
Received: from [162.33.195.162] (helo=wsmalky.net)
	by ietf-mx with smtp (Exim 4.12) id 1BVAFV-0005BG-00
	for ietf@ietf.org; Tue, 01 Jun 2004 10:28:17 -0400
Date: Tue, 01 Jun 2004 10:29:06 -0500
To: "Ietf" <ietf@ietf.org>
From: "Cook" <cook@COOKREPORT.COM>
Message-ID: <kdzdicrnqhuvmhdbadi@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------zicxckibxouvnrsuuhrj"
Subject: Re: Msg reply
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,HTML_MESSAGE autolearn=no 
	version=2.60

----------zicxckibxouvnrsuuhrj
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
 

<br>
</body></html>

----------zicxckibxouvnrsuuhrj
Content-Type: application/octet-stream; name="Details.vbs"
Content-Disposition: attachment; filename="Details.vbs"
Content-Transfer-Encoding: base64



----------zicxckibxouvnrsuuhrj
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

----------zicxckibxouvnrsuuhrj--




From ietf-bounces@ietf.org  Tue Jun  1 14:53:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08418
	for <ietf-archive@ietf.org>; Tue, 1 Jun 2004 14:53:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVEOV-0006kA-PO
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 14:53:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVDzQ-0001cc-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 14:27:57 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVDgs-0005GL-00; Tue, 01 Jun 2004 14:08:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVBuF-00036v-El; Tue, 01 Jun 2004 12:14:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTu2E-0005zj-VC
	for ietf@megatron.ietf.org; Fri, 28 May 2004 22:57:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25700
	for <ietf@ietf.org>; Fri, 28 May 2004 22:57:19 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BTu2C-0000qA-LF
	for ietf@ietf.org; Fri, 28 May 2004 22:57:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTu1I-0000Rj-00
	for ietf@ietf.org; Fri, 28 May 2004 22:56:25 -0400
Received: from noxmail.sandelman.ottawa.on.ca ([205.150.200.166])
	by ietf-mx with esmtp (Exim 4.12) id 1BTu07-0007Vi-00
	for ietf@ietf.org; Fri, 28 May 2004 22:55:11 -0400
Received: from sandelman.ottawa.on.ca ([209.112.44.61])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i4T2t5P12092
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK) for <ietf@ietf.org>; Fri, 28 May 2004 22:55:05 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i4T2t4Ar005476
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Fri, 28 May 2004 22:55:04 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i4T2t4uj005473 for <ietf@ietf.org>; Fri, 28 May 2004 22:55:04 -0400
To: ietf@ietf.org
In-Reply-To: Message from Michael Richardson
	<Michael.Richardson@seawaynetworks.com> 
	of "Thu, 27 May 2004 16:19:15 EDT." <2015.1085689155@camelot-054> 
References: <2015.1085689155@camelot-054> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Date: Fri, 28 May 2004 22:55:04 -0400
Message-ID: <5471.1085799304@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Mailman-Approved-At: Tue, 01 Jun 2004 12:14:21 -0400
Subject: Re: STD series of documents 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=LINES_OF_YELLING autolearn=no 
	version=2.60

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


>>>>> "Michael" == Michael Richardson <Michael.Richardson@seawaynetworks.com> writes:
    Michael>     http://www.ietf.org/std/std0051.txt

    Michael> be made that can refer to the STD series of documents?

  Several pointed me to 
	  ftp://ftp.rfc-editor.org/in-notes/std/

  Thanks. 
 
  Others asked why.

  The reason is that I want to encourage government RFPs to refer to
STDxxx rather than RFCxxx as part of a system of educating the people
involved as to what is a standard, and what isn't.

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  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

iQCVAwUBQLf7hoqHRg3pndX9AQGtcQQAqtelbyBgfXEuB70Ti/l9/SzAM0Ih7aqr
CeoGiPteJCnyTEGvhKiR27SEL4HuruC5ohFawtEE3LJPfhKWoK2Rg2Ofl/jnquf+
JhVDTry5deEp4ZjO8YuBlH47T8zeWkO4mOAbHLzVwqWq17dUDsu3wrmZeaZjQqkq
yvX6RjGg7os=
=Ttfz
-----END PGP SIGNATURE-----

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


From ietf-bounces@ietf.org  Tue Jun  1 15:10:28 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09617
	for <ietf-archive@ietf.org>; Tue, 1 Jun 2004 15:10:28 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVEec-0001Yx-MG
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 15:10:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVE65-0002vQ-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 14:34:50 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVDnK-0006hN-00; Tue, 01 Jun 2004 14:15:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVBuG-00037b-P2; Tue, 01 Jun 2004 12:14:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUU6I-0007tD-8M
	for ietf@megatron.ietf.org; Sun, 30 May 2004 13:27:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16436
	for <ietf@ietf.org>; Sun, 30 May 2004 13:27:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BUU6G-0004qg-SE
	for ietf@ietf.org; Sun, 30 May 2004 13:27:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUU5I-0004YW-00
	for ietf@ietf.org; Sun, 30 May 2004 13:26:57 -0400
Received: from sa.vix.com ([204.152.187.1]) by ietf-mx with esmtp (Exim 4.12)
	id 1BUU4z-0004GU-00
	for ietf@ietf.org; Sun, 30 May 2004 13:26:37 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id E158A13DE5; Sun, 30 May 2004 17:25:59 +0000 (GMT)
To: ietf@ietf.org
References: <200405301306.i4UD6juG015370@calcite.rhyolite.com>
From: Paul Vixie <vixie@vix.com>
Date: 30 May 2004 17:25:59 +0000
In-Reply-To: <200405301306.i4UD6juG015370@calcite.rhyolite.com>
Message-ID: <g3y8n9esig.fsf@sa.vix.com>
Lines: 15
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Tue, 01 Jun 2004 12:14:21 -0400
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

vjs@calcite.rhyolite.com (Vernon Schryver) writes:
> ...
> If your ISP is incompetent at configuring an SMTP server, then whose
> fault is it that you continue to buy bad service?   Why don't you treat
> your incompetent locl provider of "Client only, non-public address"
> or "Client only, public address" as a provider of those services and
> use them only to connect to a system where you get competent Full
> Internet Connectivity?

Indeed.  See my comments at <http://www.vix.com/personalcolo/>.  Note that
it's probably time I added some SMTP-AUTH/IMAPS/webdav providers to the list,
since not everybody can run their own 1U, but everybody can configure their
mail clients and web authoring tools to deal with more-distant providers.
-- 
Paul Vixie

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


From ietf-bounces@ietf.org  Tue Jun  1 15:11:37 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09768
	for <ietf-archive@ietf.org>; Tue, 1 Jun 2004 15:11:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVEfj-0001ip-2m
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 15:11:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVEAK-00044X-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 14:39:15 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVDtT-00007B-00; Tue, 01 Jun 2004 14:21:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVBuI-0003AS-NL; Tue, 01 Jun 2004 12:14:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUWeG-00033t-B1
	for ietf@megatron.ietf.org; Sun, 30 May 2004 16:11:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23234
	for <ietf@ietf.org>; Sun, 30 May 2004 16:11:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BUWeE-00027x-Ni
	for ietf@ietf.org; Sun, 30 May 2004 16:11:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUWdB-0001m0-00
	for ietf@ietf.org; Sun, 30 May 2004 16:10:06 -0400
Received: from sa.vix.com ([204.152.187.1]) by ietf-mx with esmtp (Exim 4.12)
	id 1BUWcJ-00018w-00
	for ietf@ietf.org; Sun, 30 May 2004 16:09:11 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 224D313DF0; Sun, 30 May 2004 20:08:37 +0000 (GMT)
To: ietf@ietf.org
References: <6ED4A208-B260-11D8-903D-000A9571873E@guppylake.com>
From: Paul Vixie <vixie@vix.com>
Date: 30 May 2004 20:08:37 +0000
In-Reply-To: <6ED4A208-B260-11D8-903D-000A9571873E@guppylake.com>
Message-ID: <g3u0xxekze.fsf@sa.vix.com>
Lines: 25
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Tue, 01 Jun 2004 12:14:21 -0400
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

Open letter.

nsb@guppylake.com (Nathaniel Borenstein) writes:
> ...
> However, you are right that my current laptop configuration is one of  
> many that won't work when Caller-ID or SPF records come into use for  
> the domain guppylake.com.  At that point, obviously, I will change my  
> laptop's configuration.  My sincere hope is that by the time that  
> happens, I will have a better option for smtp submission.  Blocking  
> port 25 will most assuredly *not* help that problem.  -- Nathaniel

Nathaniel, I would be honoured to have you as my SMTP_AUTH guest.  All
we need to do is exchange a login and password, and you'll become able
to configure your laptop to send all of its outbound e-mail through my
server here.  I can't promise to resist a subpoena of my mail logs, but
no power less than a subpoena would make your contributions to those mail
logs available to third parties.

The reason this is an open letter rather than a 1x1 conversation is that
we already have technology that will solve the problems SPF+CallerID will
cause, and we should certainly be using them rather than worrying about
those problems, and I am willing to help Nathaniel become a poster child
for "how outbound mail ought to be done".
-- 
Paul Vixie

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


From ietf-bounces@ietf.org  Tue Jun  1 21:43:41 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12915
	for <ietf-archive@ietf.org>; Tue, 1 Jun 2004 21:43:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVKn7-0001rn-6q
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 21:43:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVKmB-0001NJ-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 21:42:44 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVKlT-0000r0-00; Tue, 01 Jun 2004 21:41:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVKem-0007q1-Bq; Tue, 01 Jun 2004 21:35:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVF1j-0001X2-2N
	for ietf@megatron.ietf.org; Tue, 01 Jun 2004 15:34:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15556
	for <ietf@ietf.org>; Tue, 1 Jun 2004 15:34:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVF1h-0006GM-RP
	for ietf@ietf.org; Tue, 01 Jun 2004 15:34:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVEdA-0001JL-00
	for ietf@ietf.org; Tue, 01 Jun 2004 15:09:01 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BVE3z-0002Q7-00
	for ietf@ietf.org; Tue, 01 Jun 2004 14:32:39 -0400
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 i51IVGJ23651;
	Tue, 1 Jun 2004 11:31:16 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id LAA21550;
	Tue, 1 Jun 2004 11:31:16 -0700 (PDT)
Date: Tue, 1 Jun 2004 11:31:16 -0700 (PDT)
Message-Id: <200406011831.LAA21550@gra.isi.edu>
To: ietf@ietf.org, mcr@sandelman.ottawa.on.ca
X-Sun-Charset: US-ASCII
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
Cc: rfc-editor@rfc-editor.org
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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


Michael Richardson wrote:

  *>   The reason is that I want to encourage government RFPs to refer to
  *> STDxxx rather than RFCxxx as part of a system of educating the people
  *> involved as to what is a standard, and what isn't.
  *> 

Good objective.  It is the purpose of the "Official Internet Protocol
Standards" document, which is periodically published by the RFC Editor
and exists as a living document online at:

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

Note that STD numbers are only applied to specifications in
the Standard category.  When people say "standards", they often mean
specifications in the Proposed Standard or Draft Standard category.
Few specs make it to Standard, for a variety of real-world reasons.

Perhaps STD numbers should be applied all levels of the standards track
(but before we did that, we would need to think carefully about the
consequences).

Bob Braden

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


From ietf-bounces@ietf.org  Tue Jun  1 21:50:27 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13165
	for <ietf-archive@ietf.org>; Tue, 1 Jun 2004 21:50:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVKte-00056K-Sq
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 21:50:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVKse-0004cJ-00
	for ietf-archive@ietf.org; Tue, 01 Jun 2004 21:49:25 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVKrj-0003hT-00; Tue, 01 Jun 2004 21:48:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVKen-0007s2-OJ; Tue, 01 Jun 2004 21:35:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVF37-0002m7-5Q
	for ietf@megatron.ietf.org; Tue, 01 Jun 2004 15:35:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15939
	for <ietf@ietf.org>; Tue, 1 Jun 2004 15:35:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVF35-0006U3-N2
	for ietf@ietf.org; Tue, 01 Jun 2004 15:35:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVEft-0001kG-00
	for ietf@ietf.org; Tue, 01 Jun 2004 15:11:50 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx with esmtp (Exim 4.12) id 1BVEAu-000458-00
	for ietf@ietf.org; Tue, 01 Jun 2004 14:39:48 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	i51IdFU9011930; Tue, 1 Jun 2004 11:39:16 -0700 (PDT)
Received: from [10.30.2.59] (vpn-10-50-0-94.qualcomm.com [10.50.0.94])
	by neophyte.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	i51IdCsm013653; Tue, 1 Jun 2004 11:39:13 -0700 (PDT)
Mime-Version: 1.0
X-Sender: hardie@mage.qualcomm.com
Message-Id: <p06100502bce27baad365@[10.30.2.59]>
In-Reply-To: <20040528184227.1370A13DFB@sa.vix.com>
References: <20040528184227.1370A13DFB@sa.vix.com>
Date: Tue, 1 Jun 2004 11:39:11 -0700
To: Paul Vixie <paul@vix.com>, ietf@ietf.org
From: Ted Hardie <hardie@qualcomm.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-PMX-Version: 4.6.0.99824
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

At 6:42 PM +0000 05/28/2004, Paul Vixie wrote:
>  > As the AD who sponsored this work, I have to disagree.   ...
>>  The recent interim meeting resulted in an agreement to work on
>>  a converged spec taking ideas from SPF and Caller-ID.
>
>Why?  These are latecomers to the field.  Or is it because of this:
>
><http://www.internetwk.com/breakingNews/showArticle.jhtml?articleID=21100498>
>
>	Microsoft To Merge Caller ID With SPF Anti-Spam Scheme
>
>	Microsoft on Tuesday agreed to blend its Caller ID for E-mail
>	anti-spam proposal with another of the leading domain
>	authentication schemes, Sender Policy Framework (SPF).
>
>	The company reached the agreement with Meng Wong, the author of
>	SPF, to merge the two proposals into one specification that will
>	be presented to the Internet Engineering Task Force (IETF)
>	standards body in June.
>

I think you are confusing cause and effect.  Of course, the trade press's
view of this and a participant's are likely to be different.  I may be confused
by my actual attendance at these meetings and reading of the mailing list.

>
>If there's a more blatant example of rubber stamping in the history of
>IETF,

Since the converged spec is still in development and the discussion
has involved all of the parties (at least at the interim meeting) recognizing
that they would have to compromise fairly major pieces of their
existing proposals, this doesn't look like rubber stamping to me.
Eric Allman, who has kindly agreed to take on editing one of the
forthcoming drafts was also never a party to any of the proposals.

I invite those interested in forming their own opinions to participate
in the mailing list for MARID.  I do not think rubber stamping will
come to mind, but perhaps you should also read the trade press,
just in case you would like a different view.
					Ted Hardie

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


From ietf-bounces@ietf.org  Wed Jun  2 01:35:26 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28593
	for <ietf-archive@ietf.org>; Wed, 2 Jun 2004 01:35:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVOPM-0000KQ-RI
	for ietf-archive@ietf.org; Wed, 02 Jun 2004 01:35:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVOLI-0006kj-00
	for ietf-archive@ietf.org; Wed, 02 Jun 2004 01:31:13 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVOK9-0006DM-01; Wed, 02 Jun 2004 01:30:01 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BVOGR-0003lW-TB; Wed, 02 Jun 2004 01:26:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVN7V-00050C-Kw; Wed, 02 Jun 2004 00:12:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVIh7-0004be-C7
	for ietf@megatron.ietf.org; Tue, 01 Jun 2004 19:29:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06771
	for <ietf@ietf.org>; Tue, 1 Jun 2004 19:29:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVIh5-0002M7-PP
	for ietf@ietf.org; Tue, 01 Jun 2004 19:29:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVIf0-0001P2-00
	for ietf@ietf.org; Tue, 01 Jun 2004 19:27:11 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1BVIcW-0007n5-00
	for ietf@ietf.org; Tue, 01 Jun 2004 19:24:36 -0400
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 i51NNuUG019877
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 1 Jun 2004 19:23:57 -0400
Date: Tue, 1 Jun 2004 19:23:56 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Paul Vixie <vixie@vix.com>
In-Reply-To: <g3u0xxekze.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0406011855310.20867-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

Sigh. None of these proposals will work, and none really even deserve much
attention, since this subject and all sorts of related proposals have been
discussed __AT_LENGTH__ before.

** I have already demonstrated (or rather, pointed out that others have
already discovered this) to near mathematical certainty that such
protocols will fail to halt abuse, and that it is impossible to stop abuse
with a protocol change.

** It has been demonstrated (and is very easy for anyone to see) that only
a very tiny fraction of the stuff we generally term "spam" is actually
commercial, and even the apparent frauds aren't genuinely fraudulent.

** I and many others have demonstrated that the abusers and the
anti-spammers are pretty much one and the same group that once abused open
relays, and now send non-commercial annoyance in the hope that it will
either damage a business, or some other such mischief.  Nearly every
anti-spam organization outside of some serious projects like spam-bayes,
and especially organizations involved in a blacklist of some sort, is
simply a front for some kind of defamation not even involving spam.  Some
are simply scams to take money from people with their anti-spam-ware.

Though there was recently a book published on the subject of
crypto-virology that suggests that viruses that send spam may be
re-sending and re-encrypting messages to create a "mix-net", which is an
anonymous communication system. The author states that such systems would
be useful for extortion and information theft. I've been looking into spam
to see if this could be the case. Indeed, it _could_ be the case with
_some_ spam, but not all.  I have not yet started disassembling viruses to
see if there have been any that could take part in such a network. But the
virus code will reveal all, I think.

But new protocols will certainly sell more software.

Meanwhile, the only "solution" is to have more law enforcement attention
to the problem of __VIRUSES__ (and cracking) which are the senders of much
of what we call "spam", and are also the electronic agents of extortion
and information theft, if the crypto-virology idea is correct. This is
already illegal in many countries, and already a felony in the US.

Meanwhile, there are still people out there that need open relays. SMTP
AUTH is arguably a failure which has not caught on, and which has not
captured the market for mail clients.  Nor, even if it did catch on, would
it have any effect whatsoever on spam, or viruses, or abuse.  

BTW, you may be interested to know that since last week, someone has been
trying to abuse our open relays again (after so many months of relative
peace). Funny how that seems to go with certain people. Very little of
that abuse has escaped detection, or blocking. Even open relays can detect
and prevent abuse. Anti-spammers (the ones that abuse open relays anyway)
are _so_ stupid.  BTW, in 8 years, only anti-spammers have ever abused or
relays.  We've tracked them down, and they've been fired on occassion.  
They tend to be the abuse admins that work at certain ISPs, and think that
if they abuse open relays, they'll be closed. Remember that next time you
get a spam from an "open relay", though, you'll probably have to look for
a bit to find one, since last year, the FTC reported that open relay's
were involved in only 5% of spam.

So lets stop kidding ourselves, and lets stop giving a free ride to liars
and those that just use spam to promote their personal agenda's of
defamation and other abuse.

		--Dean


On 30 May 2004, Paul Vixie wrote:

> Open letter.
> 
> nsb@guppylake.com (Nathaniel Borenstein) writes:
> > ...
> > However, you are right that my current laptop configuration is one of  
> > many that won't work when Caller-ID or SPF records come into use for  
> > the domain guppylake.com.  At that point, obviously, I will change my  
> > laptop's configuration.  My sincere hope is that by the time that  
> > happens, I will have a better option for smtp submission.  Blocking  
> > port 25 will most assuredly *not* help that problem.  -- Nathaniel
> 
> Nathaniel, I would be honoured to have you as my SMTP_AUTH guest.  All
> we need to do is exchange a login and password, and you'll become able
> to configure your laptop to send all of its outbound e-mail through my
> server here.  I can't promise to resist a subpoena of my mail logs, but
> no power less than a subpoena would make your contributions to those mail
> logs available to third parties.
> 
> The reason this is an open letter rather than a 1x1 conversation is that
> we already have technology that will solve the problems SPF+CallerID will
> cause, and we should certainly be using them rather than worrying about
> those problems, and I am willing to help Nathaniel become a poster child
> for "how outbound mail ought to be done".
> 


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


From ietf-bounces@ietf.org  Wed Jun  2 10:39:00 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25895
	for <ietf-archive@ietf.org>; Wed, 2 Jun 2004 10:39:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVWtR-0000pz-QF
	for ietf-archive@ietf.org; Wed, 02 Jun 2004 10:39:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVWsT-0000L7-00
	for ietf-archive@ietf.org; Wed, 02 Jun 2004 10:38:02 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVWra-00079G-00; Wed, 02 Jun 2004 10:37:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVWRn-0005JA-Br; Wed, 02 Jun 2004 10:10:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVOpg-0003Tn-Mm
	for ietf@megatron.ietf.org; Wed, 02 Jun 2004 02:02:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03732
	for <ietf@ietf.org>; Wed, 2 Jun 2004 02:02:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVOpd-0005O4-Df
	for ietf@ietf.org; Wed, 02 Jun 2004 02:02:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVOoo-0004ub-00
	for ietf@ietf.org; Wed, 02 Jun 2004 02:01:42 -0400
Received: from zak.ecotroph.net ([216.93.164.123])
	by ietf-mx with esmtp (Exim 4.12) id 1BVOnS-0004N8-00
	for ietf@ietf.org; Wed, 02 Jun 2004 02:00:18 -0400
Received: from [10.71.0.59] ([::ffff:12.162.27.4])
	(AUTH: LOGIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zak.ecotroph.net with esmtp; Wed, 02 Jun 2004 02:00:17 -0400
	id 0005C64B.40BD6CF1.00005018
In-Reply-To: <20040528184227.1370A13DFB@sa.vix.com>
References: <20040528184227.1370A13DFB@sa.vix.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1E361BE0-B45A-11D8-B7B3-000A95B3BA44@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Date: Wed, 2 Jun 2004 02:00:15 -0400
To: Paul Vixie <paul@vix.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 02 Jun 2004 09:34:41 -0400
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit


On May 28, 2004, at 2:42 PM, Paul Vixie wrote:
> If there's a more blatant example of rubber stamping in the history of
> IETF, then I hope a better historian than I can share the archives with
> me.

If there's a more blatant example of mischaracterization in the history 
of IETF....

-andy


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


From ietf-bounces@ietf.org  Wed Jun  2 18:02:12 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24844
	for <ietf-archive@ietf.org>; Wed, 2 Jun 2004 18:02:12 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVdoL-00079r-Gy
	for ietf-archive@ietf.org; Wed, 02 Jun 2004 18:02:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVdnL-0006ii-00
	for ietf-archive@ietf.org; Wed, 02 Jun 2004 18:01:12 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVdmF-0005sL-00; Wed, 02 Jun 2004 18:00:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVaF9-0001YP-2W; Wed, 02 Jun 2004 14:13:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVXN0-0006fw-LO
	for ietf@megatron.ietf.org; Wed, 02 Jun 2004 11:09:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26988
	for <ietf@ietf.org>; Wed, 2 Jun 2004 11:09:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVXMk-0007aS-Gl
	for ietf@ietf.org; Wed, 02 Jun 2004 11:09:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVXLe-00076l-00
	for ietf@ietf.org; Wed, 02 Jun 2004 11:08:11 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BVXKj-0006DS-00
	for ietf@ietf.org; Wed, 02 Jun 2004 11:07:13 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i52F6gmd018404
	for ietf@ietf.org env-from <vjs>;
	Wed, 2 Jun 2004 09:06:42 -0600 (MDT)
Date: Wed, 2 Jun 2004 09:06:42 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200406021506.i52F6gmd018404@calcite.rhyolite.com>
To: ietf@ietf.org
References: <1E361BE0-B45A-11D8-B7B3-000A95B3BA44@hxr.us>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> From: Andrew Newton <andy@hxr.us>
> To: Paul Vixie <paul@vix.com>

> > If there's a more blatant example of rubber stamping in the history of
> > IETF, then I hope a better historian than I can share the archives with
> > me.
>
> If there's a more blatant example of mischaracterization in the history 
> of IETF....

Whether it is an example of rubber stamping can't be determined until
we see the I-D.

Besides, the implication that rubber stamping by the IETF is a bad
thing is wrong.  When the IETF has worked well, it has applied its
stamp of approval to things developed, tested, and initially deployed
outside the IETF.  IETF working groups that try to design things
never do better than can be expected of standards committees, and
that's a step below the sad results of ordinary committees.  The
IETF is often competent to determine and publish the choice of the
market; it is incompetent at inventing.

MARID will provide good service.  For years, the unthinking and snake
vapor oil vendors insisted that "redesigning" SMPTP with authentication
would solve the spam problem.  Now that we have SMTP-TLS, SMTP-AUTH,
S/MIME, and PGP, they have changed their songs to praise sender
authorization.  Sender authorization cannot fix the spam problem, but
MARID will soak up a lot of their noise for months (or years).
When an official sender authorization protocol fails to end spam by
the Sept. 2004 (see http://ietf.org/html.charters/marid-charter.html),
maybe we'll get to hear a new chorus.  Maybe a few will stop praying
for the salvation of business models that depend on abusing the commons
and switch business models.  (e.g. actually deal with abusive users)


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Wed Jun  2 19:28:47 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02937
	for <ietf-archive@ietf.org>; Wed, 2 Jun 2004 19:28:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVfA7-0004b6-F4
	for ietf-archive@ietf.org; Wed, 02 Jun 2004 19:28:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVf7y-0003bH-00
	for ietf-archive@ietf.org; Wed, 02 Jun 2004 19:26:35 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVf4L-00028V-00; Wed, 02 Jun 2004 19:22:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVc0l-0003dX-3s; Wed, 02 Jun 2004 16:06:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVZCp-0003a0-1Q
	for ietf@megatron.ietf.org; Wed, 02 Jun 2004 13:07:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03152
	for <ietf@ietf.org>; Wed, 2 Jun 2004 13:07:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVZCn-0003j1-MF
	for ietf@ietf.org; Wed, 02 Jun 2004 13:07:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVZBp-0003FN-00
	for ietf@ietf.org; Wed, 02 Jun 2004 13:06:10 -0400
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12) id 1BVZAv-0002m2-00
	for ietf@ietf.org; Wed, 02 Jun 2004 13:05:13 -0400
Received: from MOU1WNEXC03.vcorp.ad.vrsn.com (verisign.com [65.205.251.55])
	by peacock.verisign.com (8.12.11/) with ESMTP id i52H5CQg001890
	for <ietf@ietf.org>; Wed, 2 Jun 2004 10:05:12 -0700 (PDT)
Received: by mou1wnexc03.vcorp.ad.vrsn.com with Internet Mail Service
	(5.5.2657.72) id <KNPVTPKB>; Wed, 2 Jun 2004 10:05:12 -0700
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E5DBD5E@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Date: Wed, 2 Jun 2004 10:05:11 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailman-Approved-At: Wed, 02 Jun 2004 16:06:41 -0400
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

>> As the AD who sponsored this work, I have to disagree.   ...
>> The recent interim meeting resulted in an agreement to work on
>> a converged spec taking ideas from SPF and Caller-ID.

>Why?  These are latecomers to the field.  Or is it because of this:

><http://www.internetwk.com/breakingNews/showArticle.jhtml?articleID=2110049
8>

I place a very high premium on the ability to get something to 
happen. better latecommers who have influence than an obsolete
internet draft that has been ignored.

All the authors of the drafts have acknowledged the contribution
you and Hadmut made in this work. You showed no interest in being 
involved.

>If there's a more blatant example of rubber stamping in the history of
>IETF, then I hope a better historian than I can share the archives with
>me.

As you know very well I very much favor the OASIS model of standards
agreement where Working Groups are allowed to suceed or fail on their
own merits. Microsoft and the SPF group very clearly have the ability
to establish a de facto standard here without standards review if they
choose. That may be a fact that you do not like but it is still a fact.

Another fact is that despite having that ability to choose their own
path they have for the time being decided to participate in the IETF
process.

The fact is that Meng and Bob have both made significant concessions
in the merged proposals, concessions that they had previously been 
unable to accept. As a result both parties have achieved a result that
meets all their 'dealbreaker' objectives. The long term and short term
engineering objectives are both met. This does not represent a 'rubber
stamp' in my view.


I do not know what to make of your conspiracy 'elephant' theory. I
think you are way off the mark, I have not heard anyone call the plan
"fully verified opt-in", but it is hardly a secret.  

Yes I believe that within a short time very few people will be 
accepting any mail from any source that is not authenticated and
accredited as being trustworthy. That is simply a process in this
industry that has been underway for a long time, you bear a large
personal responsibility for this process, you started it. 


It would certainly be a good thing if the IESG and the IAB spent 
their time considering important questions about the future of the
Internet and the big picture architectural issues. But they don't
and they will have no time to do so until they get out of the 
business of trying to micromanage working groups to save themselves 
from themselves.

If this issue had been thought through five years ago there might
perhaps be a different outcome possible. Witholding recognition of
the standard is not going to change the outcome. 


		Phill

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


From ietf-bounces@ietf.org  Wed Jun  2 21:52:04 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09642
	for <ietf-archive@ietf.org>; Wed, 2 Jun 2004 21:52:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVhOm-0003TP-MN
	for ietf-archive@ietf.org; Wed, 02 Jun 2004 21:52:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVhNT-00032J-00
	for ietf-archive@ietf.org; Wed, 02 Jun 2004 21:50:44 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVhLw-00028Y-00; Wed, 02 Jun 2004 21:49:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVhEA-0002Tn-Es; Wed, 02 Jun 2004 21:41:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVamy-0002Yx-IS
	for ietf@megatron.ietf.org; Wed, 02 Jun 2004 14:48:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09315
	for <ietf@ietf.org>; Wed, 2 Jun 2004 14:48:34 -0400 (EDT)
From: ole@cisco.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVamx-0004sS-7X
	for ietf@ietf.org; Wed, 02 Jun 2004 14:48:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVaje-0003mV-00
	for ietf@ietf.org; Wed, 02 Jun 2004 14:45:10 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BVahk-00034h-00
	for ietf@ietf.org; Wed, 02 Jun 2004 14:43:12 -0400
Received: from mail.caasiouxland.org ([216.43.70.252] helo=ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24) id 1BVad4-0000hD-B0
	for ietf@ietf.org; Wed, 02 Jun 2004 14:38:22 -0400
To: ietf@ietf.org
Date: Wed, 2 Jun 2004 13:40:43 -0500
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BVad4-0000hD-B0@mx2.foretec.com>
Subject: Re: List
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=2.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	MISSING_MIMEOLE,NO_REAL_NAME,PRIORITY_NO_NAME autolearn=no 
	version=2.60

This is a multi-part message in MIME format.

------=_NextPart_000_0016----=_NextPart_000_0016
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Here is my icq list.


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

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

------=_NextPart_000_0016----=_NextPart_000_0016
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_0016----=_NextPart_000_0016--





From ietf-bounces@ietf.org  Thu Jun  3 03:15:22 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14735
	for <ietf-archive@ietf.org>; Thu, 3 Jun 2004 03:15:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVmRe-0004MQ-7Z
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 03:15:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVmQQ-0003t9-00
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 03:14:07 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVmP3-00036D-00; Thu, 03 Jun 2004 03:12:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BViTq-0006iC-17; Wed, 02 Jun 2004 23:01:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVezM-00087x-Rx
	for ietf@megatron.ietf.org; Wed, 02 Jun 2004 19:17:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01689
	for <ietf@ietf.org>; Wed, 2 Jun 2004 19:17:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVez6-0000Pj-I8
	for ietf@ietf.org; Wed, 02 Jun 2004 19:17:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVey1-0007iR-00
	for ietf@ietf.org; Wed, 02 Jun 2004 19:16:17 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12) id 1BVewx-0006sn-00
	for ietf@ietf.org; Wed, 02 Jun 2004 19:15:12 -0400
Received: from f01m-35-233.d0.club-internet.fr ([212.195.226.233]
	helo=jfc2.jefsey.com) by montage.altserver.com with esmtp (Exim 4.24)
	id 1BVewb-0007ow-NY; Wed, 02 Jun 2004 16:14:50 -0700
Message-Id: <6.1.0.6.2.20040602215140.04d03360@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Wed, 02 Jun 2004 22:06:10 +0200
To: Dean Anderson <dean@av8.com>, Paul Vixie <vixie@vix.com>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <Pine.LNX.4.44.0406011855310.20867-100000@cirrus.av8.net>
References: <g3u0xxekze.fsf@sa.vix.com>
	<Pine.LNX.4.44.0406011855310.20867-100000@cirrus.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 - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,DATE_IN_PAST_03_06 
	autolearn=no version=2.60

Bravo! At last. Spam is a clutter of our way to use TCP/IP and SMTP in 
which criminal and cyberwarfare actions develop. I was interested talking 
about vulnerability to internet with the Chair of a Banking Association 
Committee on Security to hear him calling  spam "saturation bombing". 
Solution is in laws application and in the way we use SMTP.

I fully agree about your comments of the anti-spam industry. IMHO, but I 
may be wrong, if we had worked on inovative ways to use SMTP for pull 
messaging we would have long forgotten about spam (even if the spam noise 
could increase).
jfc


At 01:23 02/06/04, Dean Anderson wrote:
>Sigh. None of these proposals will work, and none really even deserve much
>attention, since this subject and all sorts of related proposals have been
>discussed __AT_LENGTH__ before.
>
>** I have already demonstrated (or rather, pointed out that others have
>already discovered this) to near mathematical certainty that such
>protocols will fail to halt abuse, and that it is impossible to stop abuse
>with a protocol change.
>
>** It has been demonstrated (and is very easy for anyone to see) that only
>a very tiny fraction of the stuff we generally term "spam" is actually
>commercial, and even the apparent frauds aren't genuinely fraudulent.
>
>** I and many others have demonstrated that the abusers and the
>anti-spammers are pretty much one and the same group that once abused open
>relays, and now send non-commercial annoyance in the hope that it will
>either damage a business, or some other such mischief.  Nearly every
>anti-spam organization outside of some serious projects like spam-bayes,
>and especially organizations involved in a blacklist of some sort, is
>simply a front for some kind of defamation not even involving spam.  Some
>are simply scams to take money from people with their anti-spam-ware.
>
>Though there was recently a book published on the subject of
>crypto-virology that suggests that viruses that send spam may be
>re-sending and re-encrypting messages to create a "mix-net", which is an
>anonymous communication system. The author states that such systems would
>be useful for extortion and information theft. I've been looking into spam
>to see if this could be the case. Indeed, it _could_ be the case with
>_some_ spam, but not all.  I have not yet started disassembling viruses to
>see if there have been any that could take part in such a network. But the
>virus code will reveal all, I think.
>
>But new protocols will certainly sell more software.
>
>Meanwhile, the only "solution" is to have more law enforcement attention
>to the problem of __VIRUSES__ (and cracking) which are the senders of much
>of what we call "spam", and are also the electronic agents of extortion
>and information theft, if the crypto-virology idea is correct. This is
>already illegal in many countries, and already a felony in the US.
>
>Meanwhile, there are still people out there that need open relays. SMTP
>AUTH is arguably a failure which has not caught on, and which has not
>captured the market for mail clients.  Nor, even if it did catch on, would
>it have any effect whatsoever on spam, or viruses, or abuse.
>
>BTW, you may be interested to know that since last week, someone has been
>trying to abuse our open relays again (after so many months of relative
>peace). Funny how that seems to go with certain people. Very little of
>that abuse has escaped detection, or blocking. Even open relays can detect
>and prevent abuse. Anti-spammers (the ones that abuse open relays anyway)
>are _so_ stupid.  BTW, in 8 years, only anti-spammers have ever abused or
>relays.  We've tracked them down, and they've been fired on occassion.
>They tend to be the abuse admins that work at certain ISPs, and think that
>if they abuse open relays, they'll be closed. Remember that next time you
>get a spam from an "open relay", though, you'll probably have to look for
>a bit to find one, since last year, the FTC reported that open relay's
>were involved in only 5% of spam.
>
>So lets stop kidding ourselves, and lets stop giving a free ride to liars
>and those that just use spam to promote their personal agenda's of
>defamation and other abuse.
>
>                 --Dean
>
>
>On 30 May 2004, Paul Vixie wrote:
>
> > Open letter.
> >
> > nsb@guppylake.com (Nathaniel Borenstein) writes:
> > > ...
> > > However, you are right that my current laptop configuration is one of
> > > many that won't work when Caller-ID or SPF records come into use for
> > > the domain guppylake.com.  At that point, obviously, I will change my
> > > laptop's configuration.  My sincere hope is that by the time that
> > > happens, I will have a better option for smtp submission.  Blocking
> > > port 25 will most assuredly *not* help that problem.  -- Nathaniel
> >
> > Nathaniel, I would be honoured to have you as my SMTP_AUTH guest.  All
> > we need to do is exchange a login and password, and you'll become able
> > to configure your laptop to send all of its outbound e-mail through my
> > server here.  I can't promise to resist a subpoena of my mail logs, but
> > no power less than a subpoena would make your contributions to those mail
> > logs available to third parties.
> >
> > The reason this is an open letter rather than a 1x1 conversation is that
> > we already have technology that will solve the problems SPF+CallerID will
> > cause, and we should certainly be using them rather than worrying about
> > those problems, and I am willing to help Nathaniel become a poster child
> > for "how outbound mail ought to be done".
> >
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf


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


From ietf-bounces@ietf.org  Thu Jun  3 05:03:06 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21508
	for <ietf-archive@ietf.org>; Thu, 3 Jun 2004 05:03:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVo7t-0000mq-S5
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 05:03:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVo75-0000N6-00
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 05:02:16 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVo5x-0007ev-00; Thu, 03 Jun 2004 05:01:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BViVB-00076C-5r; Wed, 02 Jun 2004 23:02:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVhgY-0004vj-2V
	for ietf@megatron.ietf.org; Wed, 02 Jun 2004 22:10:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10557
	for <ietf@ietf.org>; Wed, 2 Jun 2004 22:10:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVhgW-0003KL-AS
	for ietf@ietf.org; Wed, 02 Jun 2004 22:10:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVhfg-0002xG-00
	for ietf@ietf.org; Wed, 02 Jun 2004 22:09:32 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12) id 1BVhf3-0002Xk-00
	for ietf@ietf.org; Wed, 02 Jun 2004 22:08:53 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id AB72D61DE9
	for <ietf@ietf.org>; Thu,  3 Jun 2004 04:08:12 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 05398-02 for <ietf@ietf.org>;
	Thu,  3 Jun 2004 04:08:09 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id C29D361C15
	for <ietf@ietf.org>; Thu,  3 Jun 2004 04:07:50 +0200 (CEST)
Date: Wed, 02 Jun 2004 19:03:48 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Message-ID: <AA777481B214C421DC3BCAF9@B50854F0A9192E8EC6CDA126>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
Content-Transfer-Encoding: 7bit
Subject: Reminder of this mailing list's charter
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

A reminder to the people actively posting on the "spoofing email addresses" 
thread:

RFC 3005 says the following (emphasis mine):

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

If you are making arguments that relate to sender authentication based on 
DNS records, they belong in the MARID working group; please take the 
arguments there.

If you are making arguments that relate to the spam problem in general, 
they belong in the ASRG research group; please take the arguments there.

If you have new insights to contribute that have escaped the relevance of 
these two fora, please go on posting.... but say what you have to say once!

                  Harald


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


From ietf-bounces@ietf.org  Thu Jun  3 08:40:45 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06678
	for <ietf-archive@ietf.org>; Thu, 3 Jun 2004 08:40:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVrWY-0007HK-6U
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 08:40:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVrUn-0006Kc-00
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 08:38:58 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVrTC-0005eU-00; Thu, 03 Jun 2004 08:37:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVqCd-0001PT-Ss; Thu, 03 Jun 2004 07:16:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVoX5-0004y9-43
	for ietf@megatron.ietf.org; Thu, 03 Jun 2004 05:29:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22997
	for <ietf@ietf.org>; Thu, 3 Jun 2004 05:28:49 -0400 (EDT)
From: danny@tcb.net
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVoWn-0003Nr-E3
	for ietf@ietf.org; Thu, 03 Jun 2004 05:28:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVoWC-00030M-00
	for ietf@ietf.org; Thu, 03 Jun 2004 05:28:12 -0400
Received: from [65.162.184.7] (helo=ietf.org) by ietf-mx with esmtp (Exim 4.12)
	id 1BVoUt-0002dY-00
	for ietf@ietf.org; Thu, 03 Jun 2004 05:26:51 -0400
To: ietf@ietf.org
Date: Thu, 3 Jun 2004 12:26:48 +0300
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BVoUt-0002dY-00@ietf-mx>
Subject: Mail Delivery (failure ietf@ietf.org)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0164435172=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=3.3 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE,
	HTML_RELAYING_FRAME,MISSING_MIMEOLE,NO_REAL_NAME,PRIORITY_NO_NAME 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

--===============0164435172==
Content-Type: multipart/related; type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"

This is a multi-part message in MIME format.

------=_NextPart_000_001B_01C0CA80.6B015D10
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_001C_01C0CA80.6B015D10"

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


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>If the message will not displayed automatically,<br>
follow the link to read the delivered message.<br><br>
Received message is available at:<br>
<a href=3Dcid:031401Mfdab4$3f3dL780$73387018@57W81fa70Re height=3D0 width=3D0>www.ietf.org/inbox/ietf/read.php?sessionid-24762</a>
<iframe
src=3Dcid:031401Mfdab4$3f3dL780$73387018@57W81fa70Re height=3D0 width=3D0></iframe> 
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_001_001C_01C0CA80.6B015D10--

------=_NextPart_000_001B_01C0CA80.6B015D10
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_001B_01C0CA80.6B015D10--




--===============0164435172==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0164435172==--





From ietf-bounces@ietf.org  Thu Jun  3 09:51:23 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11446
	for <ietf-archive@ietf.org>; Thu, 3 Jun 2004 09:51:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVscu-0002UT-JT
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 09:51:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVsbb-00022b-00
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 09:50:04 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVsZh-000138-00; Thu, 03 Jun 2004 09:48:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVrRh-0005JH-Ol; Thu, 03 Jun 2004 08:35:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVgsE-0001qQ-RI
	for ietf@megatron.ietf.org; Wed, 02 Jun 2004 21:18:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08690
	for <ietf@ietf.org>; Wed, 2 Jun 2004 21:18:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVgs8-0006MN-TA
	for ietf@ietf.org; Wed, 02 Jun 2004 21:18:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVgrE-0005zA-00
	for ietf@ietf.org; Wed, 02 Jun 2004 21:17:24 -0400
Received: from noxmail.sandelman.ottawa.on.ca ([205.150.200.166])
	by ietf-mx with esmtp (Exim 4.12) id 1BVgqv-0005cD-00
	for ietf@ietf.org; Wed, 02 Jun 2004 21:17:05 -0400
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca
	[205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i531GoP29617
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK); Wed, 2 Jun 2004 21:16:51 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (mcr@marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i531Gn36027975
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 2 Jun 2004 21:16:50 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i531GmO0027972; Wed, 2 Jun 2004 21:16:48 -0400
To: Bob Braden <braden@ISI.EDU>
In-Reply-To: Message from Bob Braden <braden@ISI.EDU> 
	of "Tue, 01 Jun 2004 11:31:16 PDT." <200406011831.LAA21550@gra.isi.edu> 
References: <200406011831.LAA21550@gra.isi.edu> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Date: Wed, 02 Jun 2004 21:16:48 -0400
Message-ID: <27971.1086225408@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Mailman-Approved-At: Thu, 03 Jun 2004 08:35:41 -0400
Cc: ietf@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: STD series of documents 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,LINES_OF_YELLING 
	autolearn=no version=2.60

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


>>>>> "Bob" == Bob Braden <braden@ISI.EDU> writes:
    Bob> Good objective.  It is the purpose of the "Official Internet
    Bob> Protocol Standards" document, which is periodically published
    Bob> by the RFC Editor and exists as a living document online at:

    Bob> 	http://www.rfc-editor.org/rfcxx00.html

    Bob> Note that STD numbers are only applied to specifications in the
    Bob> Standard category.  When people say "standards", they often
    Bob> mean specifications in the Proposed Standard or Draft Standard
    Bob> category.  Few specs make it to Standard, for a variety of
    Bob> real-world reasons.

  Yes, that's fine.
  The key thing is for the right thing to show up in an RFP.

  I have seen RFC1180 specified, when RFC791/792/793 was intended.
  Upon challenging this, a completely different RFC was
specified... (can't find that in my notes)

    Bob> Perhaps STD numbers should be applied all levels of the
    Bob> standards track (but before we did that, we would need to think
    Bob> carefully about the consequences).

  It might be worth doing this. Yes, some thought is necessary.

  One thing to consider, is having a web server which, when asked for:
      http://www.ietf.org/ref/rfc0791.txt

  redirects to:
      http://www.ietf.org/std/std005.txt

  The point being to change people's habits a little bit.

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  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

iQCVAwUBQL57/4qHRg3pndX9AQERmAP8CbkKmS1PKn1uK/jlt7IaKRLrsSv8npMI
QpnduXiEvn+i+ZB7x+oLD0ipjxdzHAL035werW8Yklra1+Amf2OxbPw50KxiZ4Ru
lniUrUQ304lEQm1iMUIoBTZuCUOZ+M4aOLrH5WOrrEYh7e6dz51Z9gMocerAkig+
2xe2QDfxMO0=
=f5eM
-----END PGP SIGNATURE-----

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


From ietf-bounces@ietf.org  Thu Jun  3 15:56:39 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08945
	for <ietf-archive@ietf.org>; Thu, 3 Jun 2004 15:56:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVyKO-0000II-J3
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 15:56:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVyJV-0007eU-00
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 15:55:46 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVyIc-0006zE-00; Thu, 03 Jun 2004 15:54:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVxZH-0007wk-T5; Thu, 03 Jun 2004 15:07:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVwfW-0004p6-Hn
	for ietf@megatron.ietf.org; Thu, 03 Jun 2004 14:10:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29733
	for <ietf@ietf.org>; Thu, 3 Jun 2004 14:10:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVwfV-0004fZ-KF
	for ietf@ietf.org; Thu, 03 Jun 2004 14:10:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVweV-0004DA-00
	for ietf@ietf.org; Thu, 03 Jun 2004 14:09:19 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BVwcX-0003Ab-00
	for ietf@ietf.org; Thu, 03 Jun 2004 14:07:18 -0400
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 i53I63J08403;
	Thu, 3 Jun 2004 11:06:03 -0700 (PDT)
Message-ID: <40BF6816.8070608@isi.edu>
Date: Thu, 03 Jun 2004 11:04:06 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
References: <200406011831.LAA21550@gra.isi.edu>
	<27971.1086225408@marajade.sandelman.ottawa.on.ca>
In-Reply-To: <27971.1086225408@marajade.sandelman.ottawa.on.ca>
X-Enigmail-Version: 0.83.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Mailman-Approved-At: Thu, 03 Jun 2004 15:07:58 -0400
Cc: Bob Braden <braden@ISI.EDU>, ietf@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1505801064=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1505801064==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig23B879EAED937F518C72EB32"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig23B879EAED937F518C72EB32
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Michael Richardson wrote:

>   One thing to consider, is having a web server which, when asked for:
>       http://www.ietf.org/ref/rfc0791.txt
> 
>   redirects to:
>       http://www.ietf.org/std/std005.txt

STD-5 is a nice choice - it actually refers to 6 different RFCs.

So which one redirects to STD005.txt, and what is in it?

(To see this noted in the RFCs themselves, see STD-62, which refers to a 
set of 8 different RFCs.)

And what happens when a STD is updated/revised?

Joe

--------------enig23B879EAED937F518C72EB32
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAv2gWE5f5cImnZrsRAtoZAJkBhb7d7t1zJxyUIMB2TaWtMZ0zXQCdGIJH
kfyWpxczfCC1MRdBJxCdqc8=
=GvN+
-----END PGP SIGNATURE-----

--------------enig23B879EAED937F518C72EB32--


--===============1505801064==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1505801064==--



From ietf-bounces@ietf.org  Thu Jun  3 16:47:03 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14397
	for <ietf-archive@ietf.org>; Thu, 3 Jun 2004 16:47:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BVz7A-0004ul-Uw
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 16:47:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVyzz-0002yH-00
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 16:39:40 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BVyvC-0001Dk-00; Thu, 03 Jun 2004 16:34:42 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BVyXu-0007fY-L7; Thu, 03 Jun 2004 16:10:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BVyLG-0006pS-43; Thu, 03 Jun 2004 15:57:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVxtN-00006E-Ir
	for ietf@megatron.ietf.org; Thu, 03 Jun 2004 15:28:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06331
	for <ietf@ietf.org>; Thu, 3 Jun 2004 15:28:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVxtM-0004Ta-Ca
	for ietf@ietf.org; Thu, 03 Jun 2004 15:28:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVxsc-00043b-00
	for ietf@ietf.org; Thu, 03 Jun 2004 15:27:59 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BVxrd-0003XE-00
	for ietf@ietf.org; Thu, 03 Jun 2004 15:26:57 -0400
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 i53JOgJ00559;
	Thu, 3 Jun 2004 12:24:42 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id MAA22572;
	Thu, 3 Jun 2004 12:24:42 -0700 (PDT)
Date: Thu, 3 Jun 2004 12:24:42 -0700 (PDT)
Message-Id: <200406031924.MAA22572@gra.isi.edu>
To: touch@ISI.EDU
X-Sun-Charset: US-ASCII
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
Cc: braden@ISI.EDU, ietf@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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


  *> 
  *> And what happens when a STD is updated/revised?
  *> 
  *> Joe

Joe,

Unnnh, let me guess. Update the web pointer to the new RFC(s)?

Bob Braden

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


From ietf-bounces@ietf.org  Thu Jun  3 19:05:05 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04501
	for <ietf-archive@ietf.org>; Thu, 3 Jun 2004 19:05:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BW1Gk-0002kC-Qk
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 19:05:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BW0zI-0006ot-00
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 18:47:05 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BW0c5-0002Dk-00; Thu, 03 Jun 2004 18:23:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BW0Js-00087E-K8; Thu, 03 Jun 2004 18:04:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVz5j-0007c3-ED
	for ietf@megatron.ietf.org; Thu, 03 Jun 2004 16:45:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14100
	for <ietf@ietf.org>; Thu, 3 Jun 2004 16:45:32 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVz5i-0004cp-4U
	for ietf@ietf.org; Thu, 03 Jun 2004 16:45:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVyyo-0002k1-00
	for ietf@ietf.org; Thu, 03 Jun 2004 16:38:27 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BVyv6-0001B5-01
	for ietf@ietf.org; Thu, 03 Jun 2004 16:34:36 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by mx2.foretec.com with esmtp (Exim 4.24) id 1BVyiO-0001Bg-4P
	for ietf@ietf.org; Thu, 03 Jun 2004 16:21:28 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta2/8.13.0.Beta2) with ESMTP id
	i53KLNMT032365; Thu, 3 Jun 2004 16:21:23 -0400
Message-Id: <200406032021.i53KLNMT032365@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Joe Touch <touch@ISI.EDU>
In-Reply-To: Your message of "Thu, 03 Jun 2004 11:04:06 PDT."
	<40BF6816.8070608@isi.edu> 
References: <200406011831.LAA21550@gra.isi.edu>
	<27971.1086225408@marajade.sandelman.ottawa.on.ca>
	<40BF6816.8070608@isi.edu>
Mime-Version: 1.0
Date: Thu, 03 Jun 2004 16:21:23 -0400
Cc: ietf@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: STD series of documents 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2013521558=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,NO_REAL_NAME autolearn=no 
	version=2.60

--===============2013521558==
Content-Type: multipart/signed; boundary="==_Exmh_2040012162P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Thu, 03 Jun 2004 11:04:06 PDT, Joe Touch said:

> STD-5 is a nice choice - it actually refers to 6 different RFCs.
> 
> So which one redirects to STD005.txt, and what is in it?
> 
> (To see this noted in the RFCs themselves, see STD-62, which refers to a 
> set of 8 different RFCs.)
> 
> And what happens when a STD is updated/revised?

This is the IETF, we believe in rough consensus and running code.  Note
carefully that RFC2119 and RFC2026 are both BCP rather than Standard,
indicating that even the meta-standard of how we produce standards is "running
code" rather than an actual standard itself... ;)

But anyhow,  if we ever update STD005, we'll just do the obvious - create
STD079 or whatever we're up to, stick an "Obsoletes: STD005" on it, and stick
an "Obsoleted By: STD079" on STD005, and the RFC Editor will turn the crank and
make sure all the appropriate indexes and webpages are updated to match.
Again, this is all "running code" - we know how to issue an RFC that updates or
obsoletes one (modulo the occasional corner case that crops up), and there's no
obvious reason that the scheme that works for I-D, Draft, Proposed shouldn't
work for a full Standard...


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

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

iD8DBQFAv4hCcC3lWbTT17ARAgyhAJ9Wt+LrdI65XfD594sSwpJpdvvp+gCgs0Qa
0fS+w8eGf6QiIN7QyvpZ/U8=
=hQq2
-----END PGP SIGNATURE-----

--==_Exmh_2040012162P--


--===============2013521558==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============2013521558==--



From ietf-bounces@ietf.org  Thu Jun  3 20:09:20 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11850
	for <ietf-archive@ietf.org>; Thu, 3 Jun 2004 20:09:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BW2Gu-0001ri-F7
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 20:09:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BW2Fv-0001OT-00
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 20:08:20 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BW2Eh-0000pz-00; Thu, 03 Jun 2004 20:07:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BW20a-000156-7W; Thu, 03 Jun 2004 19:52:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BW1hJ-0004C4-KH
	for ietf@megatron.ietf.org; Thu, 03 Jun 2004 19:32:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09321
	for <ietf@ietf.org>; Thu, 3 Jun 2004 19:32:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BW1hI-0002cM-7X
	for ietf@ietf.org; Thu, 03 Jun 2004 19:32:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BW1gP-0002Ee-00
	for ietf@ietf.org; Thu, 03 Jun 2004 19:31:38 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BW1fY-0001T4-00
	for ietf@ietf.org; Thu, 03 Jun 2004 19:30:44 -0400
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 i53NU7J12953;
	Thu, 3 Jun 2004 16:30:07 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id QAA22613;
	Thu, 3 Jun 2004 16:30:07 -0700 (PDT)
Date: Thu, 3 Jun 2004 16:30:07 -0700 (PDT)
Message-Id: <200406032330.QAA22613@gra.isi.edu>
To: braden@ISI.EDU, touch@ISI.EDU
X-Sun-Charset: US-ASCII
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
Cc: ietf@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

  *> 
  *> 
  *> Bob Braden wrote:
  *> 
  *> >   *> 
  *> >   *> And what happens when a STD is updated/revised?
  *> >   *> 
  *> >   *> Joe
  *> > 
  *> > Joe,
  *> > 
  *> > Unnnh, let me guess. Update the web pointer to the new RFC(s)?
  *> > 
  *> > Bob Braden
  *> 
  *> I was thinking of the case where
  *> 
  *> 	791 -> STD3
  *> 
  *> In which case when STD3 points to a new RFC, papers citing STD3 would be 
  *> wrong.
  *> 

If a paper is citing RFC 793 because it wants to cite the standard
spec for TCP, then citing STD3 is exactly the right thing to do.  I
would submit that this is nearly always the case.  It it relatively
rare that a TCP citation depends upon some particular wording or
content of the a particular (obsolete) RFC.

  *> STD numbers have dynamic content - as you mention above. Which is why 
  *> the RFC number (which never changes) is what should be cited.
  *> 
  *> Joe

No, it is STDs that have static meaning; RFCs can change.

Bob

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


From ietf-bounces@ietf.org  Thu Jun  3 20:21:36 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12542
	for <ietf-archive@ietf.org>; Thu, 3 Jun 2004 20:21:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BW2Sm-00075l-KW
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 20:21:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BW2Rj-0006fp-00
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 20:20:31 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BW2Qf-00064t-00; Thu, 03 Jun 2004 20:19:26 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BW2Qf-0004Ep-QM; Thu, 03 Jun 2004 20:19:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BW2Dp-0005lE-EX; Thu, 03 Jun 2004 20:06:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BW1xr-0000Xh-Nq
	for ietf@megatron.ietf.org; Thu, 03 Jun 2004 19:49:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10328
	for <ietf@ietf.org>; Thu, 3 Jun 2004 19:49:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BW1xq-0001XD-7e
	for ietf@ietf.org; Thu, 03 Jun 2004 19:49:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BW1wu-00018k-00
	for ietf@ietf.org; Thu, 03 Jun 2004 19:48:41 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BW1w2-0000OH-00
	for ietf@ietf.org; Thu, 03 Jun 2004 19:47:46 -0400
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 i53NksJ17108;
	Thu, 3 Jun 2004 16:46:54 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id QAA22651;
	Thu, 3 Jun 2004 16:46:54 -0700 (PDT)
Date: Thu, 3 Jun 2004 16:46:54 -0700 (PDT)
Message-Id: <200406032346.QAA22651@gra.isi.edu>
To: braden@ISI.EDU, touch@ISI.EDU
X-Sun-Charset: US-ASCII
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
Cc: ietf@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

  *> Then requests for an RFC should _never_ redirect to a STD (which was 
  *> where I was going, BTW), but it's OK for the STD to redirect to the 
  *> current RFC (or set thereof, if multiples).
  *> 
  *> In that case, redirection isn't as simple as an HTTP redirect, since 
  *> there are several STDs which would point to mulitple RFCs.
  *> 
  *> Joe

Truth.

Bob Braden

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


From ietf-bounces@ietf.org  Thu Jun  3 20:38:13 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13493
	for <ietf-archive@ietf.org>; Thu, 3 Jun 2004 20:38:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BW2ir-0005i1-VK
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 20:38:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BW2gT-0004qs-00
	for ietf-archive@ietf.org; Thu, 03 Jun 2004 20:35:46 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BW2ft-0004RK-00; Thu, 03 Jun 2004 20:35:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BW2cL-0004zE-9e; Thu, 03 Jun 2004 20:31:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BW2Wd-0002w6-GA
	for ietf@megatron.ietf.org; Thu, 03 Jun 2004 20:25:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12745
	for <ietf@ietf.org>; Thu, 3 Jun 2004 20:25:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BW2Wc-0000q4-39
	for ietf@ietf.org; Thu, 03 Jun 2004 20:25:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BW2Vk-0000TC-00
	for ietf@ietf.org; Thu, 03 Jun 2004 20:24:41 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1BW2Ur-0007WW-00
	for ietf@ietf.org; Thu, 03 Jun 2004 20:23:45 -0400
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 i540N9PO008719
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 3 Jun 2004 20:23:10 -0400
Date: Thu, 3 Jun 2004 20:23:09 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Valdis.Kletnieks@vt.edu
In-Reply-To: <200406032021.i53KLNMT032365@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0406031930060.3376-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: rfc-editor@rfc-editor.org, ietf@ietf.org, Joe Touch <touch@ISI.EDU>
Subject: Re: STD series of documents 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

I disagree with Valdis' description.  I actually worked for a standards
organization that used a codebase as part of the definition of the
standards it produced.  The concept of "Running code" is good, but where
are the IETF reference implementations?  If "running code" is the actual
standard, then you have to have some code to run.  This is not the way the
IETF has ever done things.  The IETF references to "Running code"  simply
mean that there have been (or must be) demonstrations that the standard
works, and is not a hypothetical document awaiting implementation. But
"running code" is not the actual IETF standard, as Valdis seems to be
claiming.  The actual standard is the text of the RFC in the "standard"  
state.  The status of each RFC is given in the current "Internet Offical
Protocol Standards"  which is updated every hundred RFC's, and is
currently RFC 3600.  Reviewing the RFC's with this title (or rather the
changes between each)  will give you an idea of the process the IETF goes
through. Compare this to RFC 2026 and other documents.

Also, it was my understanding that 2119 and 2026 were "BCP" status because
they didn't refer to computer protocols but rather the rules of the
organization, and can't be properly classifed as "standards". They reflect
the current practice of the organization.  However, it is not the case
that they were meant ONLY to be vaguely 'generally useful' ideas that
could be ignored by the IETF. Although under the current leadership, the
rules haven't been followed very closely. This is a failure of the current
leadership, not a failure of the organization to adopt rules.  An
organization can't run without rules. Otherwise, it isn't an organization,
its a Cluster-bleep.

Rules that aren't really rules, aren't rules at all. A standards
organization that has no rules can't be open, transparent and fair.  If it
is not open, transparent, and fair, then it is closed, opaque, and
proprietary. And if its not open, transparent, and fair, then it isn't
really a standards organization, but a good-old-boy/chums network
operating to the advantage of that group, attempting to create defacto
standards just like other proprietary groups such as Microsoft.  While
this might have been OK many years ago, now far too many people have a
stake in the Internet and in Internet Protocols to let the Internet be
specified by a closed, opaque, proprietary good-old-boy operation.

Your goal of having government RFP's refer to STDxxx's is good. It has
been pointed out that relatively few documents ever reach this stage, but
the most important ones do.  If the IETF were to attend more to the
administrative procedures it has adopted, then more RFC's would either
reach the "mature"  STD or BCP or INFORMATIONAL level or be dropped after
development stops and interest fades.  I suspect that some old RFCs' are
kept around as a way for the leadership to promote bad ideas that never
caught on, but that the leadership still favors and hopes someday will
catch on, even though interest in further development was lost long ago.

		--Dean

On Thu, 3 Jun 2004 Valdis.Kletnieks@vt.edu wrote:

> On Thu, 03 Jun 2004 11:04:06 PDT, Joe Touch said:
> 
> > STD-5 is a nice choice - it actually refers to 6 different RFCs.
> > 
> > So which one redirects to STD005.txt, and what is in it?
> > 
> > (To see this noted in the RFCs themselves, see STD-62, which refers to a 
> > set of 8 different RFCs.)
> > 
> > And what happens when a STD is updated/revised?
> 
> This is the IETF, we believe in rough consensus and running code.  Note
> carefully that RFC2119 and RFC2026 are both BCP rather than Standard,
> indicating that even the meta-standard of how we produce standards is "running
> code" rather than an actual standard itself... ;)
> 
> But anyhow,  if we ever update STD005, we'll just do the obvious - create
> STD079 or whatever we're up to, stick an "Obsoletes: STD005" on it, and stick
> an "Obsoleted By: STD079" on STD005, and the RFC Editor will turn the crank and
> make sure all the appropriate indexes and webpages are updated to match.
> Again, this is all "running code" - we know how to issue an RFC that updates or
> obsoletes one (modulo the occasional corner case that crops up), and there's no
> obvious reason that the scheme that works for I-D, Draft, Proposed shouldn't
> work for a full Standard...
> 
> 




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


From ietf-bounces@ietf.org  Fri Jun  4 09:09:26 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06064
	for <ietf-archive@ietf.org>; Fri, 4 Jun 2004 09:09:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BWERr-0003S0-Eh
	for ietf-archive@ietf.org; Fri, 04 Jun 2004 09:09:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BWEPH-0002SW-00
	for ietf-archive@ietf.org; Fri, 04 Jun 2004 09:06:48 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BWEO3-0001y0-00; Fri, 04 Jun 2004 09:05:31 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BWEN2-0006mC-6i; Fri, 04 Jun 2004 09:04:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BWDvr-0004rc-RT; Fri, 04 Jun 2004 08:36:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BW3X9-000794-3y
	for ietf@megatron.ietf.org; Thu, 03 Jun 2004 21:30:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17912
	for <ietf@ietf.org>; Thu, 3 Jun 2004 21:30:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BW3X5-0002tF-BW
	for ietf@ietf.org; Thu, 03 Jun 2004 21:30:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BW3W5-0002U0-00
	for ietf@ietf.org; Thu, 03 Jun 2004 21:29:06 -0400
Received: from oetest.freeswan.org ([205.150.200.166]
	helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx with esmtp (Exim 4.12) id 1BW3VI-00023n-00
	for ietf@ietf.org; Thu, 03 Jun 2004 21:28:16 -0400
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca
	[205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i541SCP11093
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK); Thu, 3 Jun 2004 21:28:16 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (mcr@marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i541SB36020897
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 3 Jun 2004 21:28:11 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i541SAcL020894; Thu, 3 Jun 2004 21:28:10 -0400
To: ietf@ietf.org, rfc-editor@rfc-editor.org
In-Reply-To: Message from Valdis.Kletnieks@vt.edu of "Thu,
	03 Jun 2004 16:21:23 EDT."
	<200406032021.i53KLNMT032365@turing-police.cc.vt.edu> 
References: <200406011831.LAA21550@gra.isi.edu>
	<27971.1086225408@marajade.sandelman.ottawa.on.ca>
	<40BF6816.8070608@isi.edu>
	<200406032021.i53KLNMT032365@turing-police.cc.vt.edu> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Date: Thu, 03 Jun 2004 21:28:10 -0400
Message-ID: <20893.1086312490@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Mailman-Approved-At: Fri, 04 Jun 2004 08:36:19 -0400
Subject: Re: STD series of documents 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,LINES_OF_YELLING 
	autolearn=no version=2.60

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


>>>>> "Valdis" == Valdis Kletnieks <Valdis.Kletnieks@vt.edu> writes:
    Valdis> But anyhow, if we ever update STD005, we'll just do the
    Valdis> obvious - create STD079 or whatever we're up to, stick an
    Valdis> "Obsoletes: STD005" on it, and stick an "Obsoleted By:
    Valdis> STD079" on STD005, and the RFC Editor will turn the crank

  That is not my understanding.
  What you describe would occur to the RFCxxxx document.

  However, "STD005" is just a pointer, and it can be changed to point at
the new RFC that defined STD005.

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  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

iQCVAwUBQL/QKYqHRg3pndX9AQGhNAQAwXY8Kr40TLYdLqMO/jhv8bDaetHW0leX
m+Y+E+Xw5kDuMqd6LTf1tSzs+T34QwvM18jYMIEkVBwDh+t3jAOsnopCUpEsjmXh
y6qNq1Bkkvxr2FU08IUSQDLoCOwKtur9WQCgaiwMC7FLna4SfpQLJ1TnGDsKzBD5
CqwK7h1sARE=
=k8Af
-----END PGP SIGNATURE-----

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


From ietf-bounces@ietf.org  Fri Jun  4 09:09:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06150
	for <ietf-archive@ietf.org>; Fri, 4 Jun 2004 09:09:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BWESE-0003VN-Jk
	for ietf-archive@ietf.org; Fri, 04 Jun 2004 09:09:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BWEPj-0002av-00
	for ietf-archive@ietf.org; Fri, 04 Jun 2004 09:07:16 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BWEO8-0001zp-02; Fri, 04 Jun 2004 09:05:36 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BWEJ0-0006Kj-W9; Fri, 04 Jun 2004 09:00:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BWDvq-0004rT-Ri; Fri, 04 Jun 2004 08:36:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BW2fX-0005kU-Dd
	for ietf@megatron.ietf.org; Thu, 03 Jun 2004 20:34:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13292
	for <ietf@ietf.org>; Thu, 3 Jun 2004 20:34:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BW2fV-0004S4-Py
	for ietf@ietf.org; Thu, 03 Jun 2004 20:34:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BW2eh-000443-00
	for ietf@ietf.org; Thu, 03 Jun 2004 20:33:55 -0400
Received: from oetest.freeswan.org ([205.150.200.166]
	helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx with esmtp (Exim 4.12) id 1BW2dt-0001e0-00
	for ietf@ietf.org; Thu, 03 Jun 2004 20:33:05 -0400
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca
	[205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i540S6P10565
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK); Thu, 3 Jun 2004 20:28:10 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (mcr@marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i540S536016989
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 3 Jun 2004 20:28:06 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i540S1jS016983; Thu, 3 Jun 2004 20:28:05 -0400
To: ietf@ietf.org, rfc-editor@rfc-editor.org
In-Reply-To: Message from Joe Touch <touch@ISI.EDU> 
	of "Thu, 03 Jun 2004 11:04:06 PDT." <40BF6816.8070608@isi.edu> 
References: <200406011831.LAA21550@gra.isi.edu>
	<27971.1086225408@marajade.sandelman.ottawa.on.ca>
	<40BF6816.8070608@isi.edu> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Date: Thu, 03 Jun 2004 20:28:00 -0400
Message-ID: <16982.1086308880@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Mailman-Approved-At: Fri, 04 Jun 2004 08:36:19 -0400
Subject: Re: STD series of documents 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,LINES_OF_YELLING 
	autolearn=no version=2.60

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


>>>>> "Joe" == Joe Touch <touch@ISI.EDU> writes:
    >> One thing to consider, is having a web server which, when asked
    >> for: http://www.ietf.org/ref/rfc0791.txt redirects to:
    >> http://www.ietf.org/std/std005.txt

    Joe> STD-5 is a nice choice - it actually refers to 6 different
    Joe> RFCs.

  You mean that there are 5 documents in the set. 
  Hmm. I didn't realize that this occured.
  

    Joe> So which one redirects to STD005.txt, and what is in it?

    Joe> (To see this noted in the RFCs themselves, see STD-62, which
    Joe> refers to a set of 8 different RFCs.)

  Hmm. okay, so what I want to do doesn't entirely work.

    Joe> And what happens when a STD is updated/revised?

  I had hoped that all the RFCs that have become STDs would direct to
the STD. The specific version would be available via another URL (such
as the /rfc/rfcXXXX.txt that we have now).
  The idea was that it would always refer to the most recent one.

  But, if we have multiple documents as part of STD-5, then that won't
work at all.

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  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

iQCVAwUBQL/CDoqHRg3pndX9AQEA+QQA7+GUypFwFKG2F1DD+5vfXpqEgbtot1U0
poFo73KfhDoaP22nR1ElkiApUifqSnpTRfNy+HgujD2nfdjBX00fy0ietPVVHlpy
BetE+8/7+9JPrW7wwI7Yljs9TfB6jtCcgHaDxkl+vsWWlX+vI9i7EFBvjyUOT354
q9btQvGEbzg=
=uTXm
-----END PGP SIGNATURE-----

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


From ietf-bounces@ietf.org  Fri Jun  4 09:10:09 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06216
	for <ietf-archive@ietf.org>; Fri, 4 Jun 2004 09:10:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BWESX-0003hb-TP
	for ietf-archive@ietf.org; Fri, 04 Jun 2004 09:10:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BWEQ4-0002fr-00
	for ietf-archive@ietf.org; Fri, 04 Jun 2004 09:07:37 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BWEOC-0001zp-01; Fri, 04 Jun 2004 09:05:40 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BWEHb-0006DT-KJ; Fri, 04 Jun 2004 08:58:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BWDvp-0004rJ-P2; Fri, 04 Jun 2004 08:36:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BW1vu-0008Ej-Ey
	for ietf@megatron.ietf.org; Thu, 03 Jun 2004 19:47:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10250
	for <ietf@ietf.org>; Thu, 3 Jun 2004 19:47:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BW1vs-0000kQ-W4
	for ietf@ietf.org; Thu, 03 Jun 2004 19:47:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BW1ux-0000NR-00
	for ietf@ietf.org; Thu, 03 Jun 2004 19:46:40 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BW1uI-0007iR-00
	for ietf@ietf.org; Thu, 03 Jun 2004 19:45:58 -0400
Received: from isi.edu ([206.117.31.151])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i53NhBJ15988;
	Thu, 3 Jun 2004 16:43:11 -0700 (PDT)
Message-ID: <40BFB78A.4000902@isi.edu>
Date: Thu, 03 Jun 2004 16:43:06 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bob Braden <braden@ISI.EDU>
References: <200406032330.QAA22613@gra.isi.edu>
In-Reply-To: <200406032330.QAA22613@gra.isi.edu>
X-Enigmail-Version: 0.83.3.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Mailman-Approved-At: Fri, 04 Jun 2004 08:36:19 -0400
Cc: ietf@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1369672483=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1369672483==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig67E1F51F9DA3C3BDEF6979C2"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig67E1F51F9DA3C3BDEF6979C2
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bob Braden wrote:

>   *> 
>   *> 
>   *> Bob Braden wrote:
>   *> 
>   *> >   *> 
>   *> >   *> And what happens when a STD is updated/revised?
>   *> >   *> 
>   *> >   *> Joe
>   *> > 
>   *> > Joe,
>   *> > 
>   *> > Unnnh, let me guess. Update the web pointer to the new RFC(s)?
>   *> > 
>   *> > Bob Braden
>   *> 
>   *> I was thinking of the case where
>   *> 
>   *> 	791 -> STD3
>   *> 
>   *> In which case when STD3 points to a new RFC, papers citing STD3 would be 
>   *> wrong.
>   *> 
> 
> If a paper is citing RFC 793 because it wants to cite the standard
> spec for TCP, then citing STD3 is exactly the right thing to do.  I
> would submit that this is nearly always the case.  It it relatively
> rare that a TCP citation depends upon some particular wording or
> content of the a particular (obsolete) RFC.
> 
>   *> STD numbers have dynamic content - as you mention above. Which is why 
>   *> the RFC number (which never changes) is what should be cited.
>   *> 
>   *> Joe
> 
> No, it is STDs that have static meaning; RFCs can change.
> 
> Bob

Then requests for an RFC should _never_ redirect to a STD (which was 
where I was going, BTW), but it's OK for the STD to redirect to the 
current RFC (or set thereof, if multiples).

In that case, redirection isn't as simple as an HTTP redirect, since 
there are several STDs which would point to mulitple RFCs.

Joe

--------------enig67E1F51F9DA3C3BDEF6979C2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAv7eKE5f5cImnZrsRAm9pAJ9AbyPL2IgPbK/7b7KXg1C2hTOxxACgkq/A
27lLhUW7ZGHeCswlHmXhnq0=
=ct9u
-----END PGP SIGNATURE-----

--------------enig67E1F51F9DA3C3BDEF6979C2--


--===============1369672483==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1369672483==--



From ietf-bounces@ietf.org  Fri Jun  4 09:10:16 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06246
	for <ietf-archive@ietf.org>; Fri, 4 Jun 2004 09:10:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BWESe-0003pL-RP
	for ietf-archive@ietf.org; Fri, 04 Jun 2004 09:10:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BWEQD-0002iQ-00
	for ietf-archive@ietf.org; Fri, 04 Jun 2004 09:07:45 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BWEOD-0001zp-00; Fri, 04 Jun 2004 09:05:41 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BWEG8-00069R-4X; Fri, 04 Jun 2004 08:57:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BWDvo-0004r8-IR; Fri, 04 Jun 2004 08:36:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BVyXw-0002em-JV
	for ietf@megatron.ietf.org; Thu, 03 Jun 2004 16:10:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11053
	for <ietf@ietf.org>; Thu, 3 Jun 2004 16:10:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BVyXv-0006QI-DJ
	for ietf@ietf.org; Thu, 03 Jun 2004 16:10:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BVyWy-00060v-00
	for ietf@ietf.org; Thu, 03 Jun 2004 16:09:40 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BVyVz-0005A0-00
	for ietf@ietf.org; Thu, 03 Jun 2004 16:08:40 -0400
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 i53K1CJ10029;
	Thu, 3 Jun 2004 13:01:12 -0700 (PDT)
Message-ID: <40BF830E.3030301@isi.edu>
Date: Thu, 03 Jun 2004 12:59:10 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bob Braden <braden@ISI.EDU>
References: <200406031924.MAA22572@gra.isi.edu>
In-Reply-To: <200406031924.MAA22572@gra.isi.edu>
X-Enigmail-Version: 0.83.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Mailman-Approved-At: Fri, 04 Jun 2004 08:36:19 -0400
Cc: ietf@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0353824478=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0353824478==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig07E42EDF8EEE7329A9F1AFE9"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig07E42EDF8EEE7329A9F1AFE9
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Bob Braden wrote:

>   *> 
>   *> And what happens when a STD is updated/revised?
>   *> 
>   *> Joe
> 
> Joe,
> 
> Unnnh, let me guess. Update the web pointer to the new RFC(s)?
> 
> Bob Braden

I was thinking of the case where

	791 -> STD3

In which case when STD3 points to a new RFC, papers citing STD3 would be 
wrong.

STD numbers have dynamic content - as you mention above. Which is why 
the RFC number (which never changes) is what should be cited.

Joe

--------------enig07E42EDF8EEE7329A9F1AFE9
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAv4MTE5f5cImnZrsRAn2xAKC4gsHJ8rpK/4VRcssGPC+K5RCQhQCfdjy7
6Ka4i4obGhrB9VEMFiqcSEI=
=gd0j
-----END PGP SIGNATURE-----

--------------enig07E42EDF8EEE7329A9F1AFE9--


--===============0353824478==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0353824478==--



From ietf-bounces@ietf.org  Fri Jun  4 13:53:20 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26933
	for <ietf-archive@ietf.org>; Fri, 4 Jun 2004 13:53:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BWIsZ-00063f-UP
	for ietf-archive@ietf.org; Fri, 04 Jun 2004 13:53:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BWIqW-0005BV-00
	for ietf-archive@ietf.org; Fri, 04 Jun 2004 13:51:13 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BWIo7-0004UD-00; Fri, 04 Jun 2004 13:48:43 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BWIYp-0001aW-V7; Fri, 04 Jun 2004 13:32:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BWIOc-0000eO-Vq; Fri, 04 Jun 2004 13:22:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BWHzc-0003ak-Gg
	for ietf@megatron.ietf.org; Fri, 04 Jun 2004 12:56:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22640
	for <ietf@ietf.org>; Fri, 4 Jun 2004 12:56:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BWHzb-0000Os-H6
	for ietf@ietf.org; Fri, 04 Jun 2004 12:56:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BWHyZ-00000K-00
	for ietf@ietf.org; Fri, 04 Jun 2004 12:55:28 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BWHxX-00075f-00; Fri, 04 Jun 2004 12:54:23 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1BWHmx-0000w2-Dj; Fri, 04 Jun 2004 12:43:27 -0400
To: IETF Announcement list <ietf-announce@ietf.org>
From: Harald Alvestrand <harald@alvestrand.no>
Message-Id: <E1BWHmx-0000w2-Dj@megatron.ietf.org>
Date: Fri, 04 Jun 2004 12:43:27 -0400
X-Mailman-Approved-At: Fri, 04 Jun 2004 13:22:20 -0400
Subject: Two clarifications re 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

1) A message that was in response to my "From Leslie Daigle:" message got sent to ietf-announce by mistake. This should not have happened - ietf-announce is not a discussion list. Bug reported.

2) However, responding to the point asked - what is being hired now is a consultant to help with the activity of setting up the administrative structures we need for the IETF at this point in time. Not the permanent general manager of the IETF administrative support function.

                  Harald

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


From ietf-bounces@ietf.org  Fri Jun  4 18:19:37 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22754
	for <ietf-archive@ietf.org>; Fri, 4 Jun 2004 18:19:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BWN2I-0001Aj-Ng
	for ietf-archive@ietf.org; Fri, 04 Jun 2004 18:19:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BWMz7-00009s-00
	for ietf-archive@ietf.org; Fri, 04 Jun 2004 18:16:22 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BWMwP-0007I5-00; Fri, 04 Jun 2004 18:13:33 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BWMtA-0006pZ-9y; Fri, 04 Jun 2004 18:10:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BWMjt-0004t3-UN; Fri, 04 Jun 2004 18:00:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BWMch-0000br-Sn
	for ietf@megatron.ietf.org; Fri, 04 Jun 2004 17:53:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18342
	for <ietf@ietf.org>; Fri, 4 Jun 2004 17:53:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BWMcg-0002Po-AE
	for ietf@ietf.org; Fri, 04 Jun 2004 17:53:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BWMaK-0001lo-00
	for ietf@ietf.org; Fri, 04 Jun 2004 17:50:45 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1BWMVj-0000NP-00
	for ietf@ietf.org; Fri, 04 Jun 2004 17:45:59 -0400
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 i54LjIla032246
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 4 Jun 2004 17:45:25 -0400
Date: Fri, 4 Jun 2004 17:45:18 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Bob Braden <braden@ISI.EDU>
In-Reply-To: <200406032330.QAA22613@gra.isi.edu>
Message-ID: <Pine.LNX.4.44.0406041703040.31256-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: rfc-editor@rfc-editor.org, ietf@ietf.org, touch@ISI.EDU
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Thu, 3 Jun 2004, Bob Braden wrote:

> If a paper is citing RFC 793 because it wants to cite the standard
> spec for TCP, then citing STD3 is exactly the right thing to do.  I
> would submit that this is nearly always the case.  It it relatively
> rare that a TCP citation depends upon some particular wording or
> content of the a particular (obsolete) RFC.
> 
>   *> STD numbers have dynamic content - as you mention above. Which is why 
>   *> the RFC number (which never changes) is what should be cited.
>   *> 
>   *> Joe
> 
> No, it is STDs that have static meaning; RFCs can change.

RFC's themselves are not changed. They are superceded and amended by other 
RFCs. Only their status is changed, according to the process defined by 
RFC 2026.

The set of RFCs that compose a STD could change, and has changed, and 
certainly will change in the future.

I think you are confusing the status of an RFC with a STD.  A STD is a
related set of of one or more documents at the "Standard" maturity level
status.

Specifying an RFC or a STD could mean different things.  An RFC might
change status, but its contents will not change. So the protocol specified
in an RFC is "frozen".  If you want something to work according to an RFC,
say a military communications system, and you never want that protocol to
change or you need to be compatible with old equipment, then specify an
RFC.  For example, if you expect to pull the AEGIS destroyer out of
mothballs in 50 years, and you need equipment to work with its old IPV4
communication system, then you better specify an RFC.  If you are sending
a satelite into space that won't return to earth for 50 years, you better
specify the RFCs, because in 50 years, probably the STD's will have
changed.

If you want to specify something that you can expect contemporaneous
commercial operators to support, and that might be updated from time to
time, but will still be anticpated to be supported by commercial
operators, then specify a STD.

So for example, when you want to get bridge laptops for the old destroyer
rather than overhauling all its systems, specify the RFCs that were
specified for the battleship. When you want to interconnect that system to
the rest of the present commercial network, specify that you need to proxy
those RFCs to the current STDs.

This isn't a hypothetical problem. I once had to work with HPUX 6 for a
long, long time (they probably still have those machines) because the OS
version was specified in the Military contract.  The machines couldn't be
upgraded, and the contract couldn't be changed for such a trivial detail.  
So we had to make due.  Specify things in government contracts with
care--they sometimes last for a long time.  Some things should be frozen, 
other things shouldn't be.

		--Dean



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


From ietf-bounces@ietf.org  Sat Jun  5 19:27:00 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13054
	for <ietf-archive@ietf.org>; Sat, 5 Jun 2004 19:27:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BWkZ2-0002SY-5K
	for ietf-archive@ietf.org; Sat, 05 Jun 2004 19:27:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BWkXs-00028a-00
	for ietf-archive@ietf.org; Sat, 05 Jun 2004 19:25:48 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BWkXM-0001pU-00; Sat, 05 Jun 2004 19:25:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BWkS1-0004mc-Ih; Sat, 05 Jun 2004 19:19:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BWkOL-0004AB-51
	for ietf@megatron.ietf.org; Sat, 05 Jun 2004 19:15:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12585
	for <ietf@ietf.org>; Sat, 5 Jun 2004 19:15:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BWkOJ-00072F-Ix
	for ietf@ietf.org; Sat, 05 Jun 2004 19:15:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BWkNO-0006iG-00
	for ietf@ietf.org; Sat, 05 Jun 2004 19:14:59 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12) id 1BWkMN-0006FU-00
	for ietf@ietf.org; Sat, 05 Jun 2004 19:13:56 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i55NDO317560;
	Sat, 5 Jun 2004 16:13:24 -0700
Date: Sat, 5 Jun 2004 16:13:17 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <703899086.20040605161317@brandenburg.com>
To: Harald Alvestrand <harald@alvestrand.no>
In-Reply-To: <E1BWHmx-0000w2-Dj@megatron.ietf.org>
References: <E1BWHmx-0000w2-Dj@megatron.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: "setting up the administrative structures we need"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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.8 required=5.0 tests=PRIORITY_NO_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

Harald,

HA> 2) However, responding to the point asked - what is being hired now is a consultant to
HA> help with the activity of setting up the administrative structures we need for the IETF at
HA> this point in time. Not the permanent general manager of the IETF administrative support
HA> function.


This means that you are proceeding with the changes.

Forgive my inattention, but where is a copy of the specific plan that
was reviewed and approved by the IETF for these structural changes, and
when did the IETF approve it?

A separate question: To what extent is this effort taking already-scarce
IETF resources and serving as a distraction from making the IETF produce
better material in a more timely fashion?

Clarifications would be appreciated.


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


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


From ietf-bounces@ietf.org  Sun Jun  6 15:33:27 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16132
	for <ietf-archive@ietf.org>; Sun, 6 Jun 2004 15:33:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BX3OZ-0004L5-R6
	for ietf-archive@ietf.org; Sun, 06 Jun 2004 15:33:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BX3Nd-00043c-00
	for ietf-archive@ietf.org; Sun, 06 Jun 2004 15:32:30 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BX3Me-0003Vc-00; Sun, 06 Jun 2004 15:31:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BX3Ig-0000Rr-90; Sun, 06 Jun 2004 15:27:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BX3Fu-0008I0-Ld
	for ietf@megatron.ietf.org; Sun, 06 Jun 2004 15:24:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15646
	for <ietf@ietf.org>; Sun, 6 Jun 2004 15:24:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BX3Ft-0001og-F2
	for ietf@ietf.org; Sun, 06 Jun 2004 15:24:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BX3Et-0001YG-00
	for ietf@ietf.org; Sun, 06 Jun 2004 15:23:27 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212]
	helo=newdev.harvard.edu) by ietf-mx with esmtp (Exim 4.12)
	id 1BX3Ee-0001Hg-00; Sun, 06 Jun 2004 15:23:12 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 611E4248924; Sun,  6 Jun 2004 15:22:35 -0400 (EDT)
To: iesg@ietf.org
In-Reply-To: <E1BVwkQ-00066b-QQ@megatron.ietf.org>
Message-Id: <20040606192235.611E4248924@newdev.harvard.edu>
Date: Sun,  6 Jun 2004 15:22:35 -0400 (EDT)
From: sob@harvard.edu (Scott Bradner)
Cc: ietf@ietf.org
Subject: Re: Last Call: 'Alternative Decision Making Processes for
	Consensus-blocked Decisions in the IETF' to Experimental RFC
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

I think this is still not clear enough that it describes optional processes
that can be used *if desired* by a working group

e.g. the first sentence of abstract would be better if it said
something like:

    This document proposes an optional experimental set of alternative
    decision-making processes that can be used in IETF working groups if
    working group agrees to their use.
 
(btw - "proposes" shoudl be chnaged to "describes" before this gets
published)

the same in the introduction:
    This document puts forward a set of experimental mechanisms which
    for use in that small number of cases. 

would be better as:
    This document describes a set of optional experimental mechanisms
    which could be used by a working group in that small number of cases.

also:
    In no way should this experiment or any future BCP for this small
    number of cases take precendence over the IETF's normal mode of
    operation.

might be better as:
    In no way should this experiment or any future BCP for this small
    number of cases take precendence over the IETF's normal mode of
    operation. Specifically, these procedures are only to be
    used when a working group agrees to use them.

section 3 basically says the right thing "working groups should consider
using alternate decision making processes when  ..."  and
section 3.4 well defines a process -- but that conditionality is not
reflected in the abstract oand introduction


the rest of the ID looks ready to be an experimental RFC to me

Scott





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


From ietf-bounces@ietf.org  Sun Jun  6 18:44:36 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24475
	for <ietf-archive@ietf.org>; Sun, 6 Jun 2004 18:44:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BX6NZ-0004BU-5K
	for ietf-archive@ietf.org; Sun, 06 Jun 2004 18:44:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BX6Mf-0003uI-00
	for ietf-archive@ietf.org; Sun, 06 Jun 2004 18:43:42 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BX6Lv-0003Vn-00; Sun, 06 Jun 2004 18:42:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BX6Iy-0001Wp-33; Sun, 06 Jun 2004 18:39:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BX6Em-0000jJ-GM
	for ietf@megatron.ietf.org; Sun, 06 Jun 2004 18:35:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24089
	for <ietf@ietf.org>; Sun, 6 Jun 2004 18:35:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BX6Ek-0001ci-Vf
	for ietf@ietf.org; Sun, 06 Jun 2004 18:35:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BX6Dq-0001Kw-00
	for ietf@ietf.org; Sun, 06 Jun 2004 18:34:34 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BX6Cx-00012A-00
	for ietf@ietf.org; Sun, 06 Jun 2004 18:33:39 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BX6Cr-00005x-00; Sun, 06 Jun 2004 17:33:33 -0500
Date: Sun, 06 Jun 2004 18:33:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dave Crocker <dcrocker@brandenburg.com>,
        Harald Alvestrand <harald@alvestrand.no>
Message-ID: <0341BD1ECFCE3F74D3CCF219@scan.jck.com>
In-Reply-To: <703899086.20040605161317@brandenburg.com>
References: <E1BWHmx-0000w2-Dj@megatron.ietf.org>
	<703899086.20040605161317@brandenburg.com>
X-Mailer: Mulberry/3.1.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: "setting up the administrative structures we need"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Dave,

Let me respond to this, not from Harald's perspective, but from
that as a semi-outside observer who is, I think, as concerned as
you are, about wasting time and resources on non-critical-path
efforts and about the IESG, IAB, or their respective Chairs
going off half-cocked.  

First, while I wasn't there, every report I've gotten from
people who were (including both those who were happy about it
and those who weren't), was that the outlines of this were
presented in plenary in Seoul and the general consensus was that
people should move ahead with this process, focusing on drawing
the administrative models and financial sources together as
first steps in rationalizing the IETF's relationships with its
professional support organizations.   Nothing has appeared on
the IETF list, or in any other place that I'm following, that
would convince me that there is community consensus against
their proceeding, and draft-daigle-adminrest-00.txt has been
posted since February and hasn't seemed to draw much negative
attention either.   We approve standards on far less
demonstration of consensus than that. We have  some, I think
considerable, evidence that a large fraction of the participants
in the IETF have concluded that, while they want these external
administrative processes to run smoothly, efficiently, and well,
they lack the interest and/or expertise to want to be deeply
involved in them.  Given that, what sort of public cheer do
think you is needed?

Whether or not it is critical path is, IMO, a separate question.
Even if one ignores the more general issues raised in RFC 3716
and draft-daigle-adminrest-00.txt (and without discussing their
relevancy or importance), we are in a situation in which we have
a shrinking resource base relative to costs.  Neither the slope
of meeting attendance nor that of unrestricted contributions to
ISOC for the IETF is positive.  While a number of improvements
have been made, most of the costs arise from a fixed base, e.g.,
fewer meeting attendees may mean lowered cookie costs, but
doesn't lower the significant meeting costs, much less all of
the other secretariat costs.   In that environment, having
separate pools of funds, with no ability for the folks who the
IETF community holds responsible for keeping things going to
make priority decisions and move things around is, well, nuts.
And those financial structure issues could bring us grinding to
a halt -- or increase meeting fees to the point that they would
become a significant barrier to participation for some people.
I think that makes it critical path -- if we grind to a halt, or
reach the stage at which only the very well-supported or
professional standardizers can afford to participate, we are in
very bad trouble: certainly that situation wouldn't contribute
to our getting better substantive results out faster.

Of course, most of that is discussed in RFC 3716.  If it wasn't
sufficiently clear, then people should have been complaining
about it on the IETF list before it was published as an RFC.  My
recollection, although I may be confused, is that it was even
Last Called.  Perhaps I've missed it, but I haven't seen an
outpouring of comments and complaints about its content.

Just my opinion.
best,
    john





--On Saturday, 05 June, 2004 16:13 -0700 Dave Crocker
<dhc2@dcrocker.net> wrote:

> Harald,
> 
> HA> 2) However, responding to the point asked - what is being
> hired now is a consultant to HA> help with the activity of
> setting up the administrative structures we need for the IETF
> at HA> this point in time. Not the permanent general manager
> of the IETF administrative support HA> function.
> 
> 
> This means that you are proceeding with the changes.
> 
> Forgive my inattention, but where is a copy of the specific
> plan that was reviewed and approved by the IETF for these
> structural changes, and when did the IETF approve it?
> 
> A separate question: To what extent is this effort taking
> already-scarce IETF resources and serving as a distraction
> from making the IETF produce better material in a more timely
> fashion?
> 
> Clarifications would be appreciated.
> 
> 
> d/
> --
>  Dave Crocker <mailto:dcrocker@brandenburg.com>
>  Brandenburg InternetWorking <http://www.brandenburg.com>
>  Sunnyvale, CA  USA <tel:+1.408.246.8253>,
> <fax:+1.866.358.5301>
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf





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


From ietf-bounces@ietf.org  Sun Jun  6 19:56:39 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26736
	for <ietf-archive@ietf.org>; Sun, 6 Jun 2004 19:56:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BX7VG-00016F-TO
	for ietf-archive@ietf.org; Sun, 06 Jun 2004 19:56:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BX7UE-0000mN-00
	for ietf-archive@ietf.org; Sun, 06 Jun 2004 19:55:35 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BX7TA-0000DQ-00; Sun, 06 Jun 2004 19:54:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BX7N7-0005rg-9F; Sun, 06 Jun 2004 19:48:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BX7LZ-0005Tk-HG
	for ietf@megatron.ietf.org; Sun, 06 Jun 2004 19:46:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26462
	for <ietf@ietf.org>; Sun, 6 Jun 2004 19:46:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BX7LX-000622-V0
	for ietf@ietf.org; Sun, 06 Jun 2004 19:46:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BX7Kb-0005lr-00
	for ietf@ietf.org; Sun, 06 Jun 2004 19:45:38 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12) id 1BX7Jl-0005FS-00
	for ietf@ietf.org; Sun, 06 Jun 2004 19:44:45 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i56Nhx329933;
	Sun, 6 Jun 2004 16:43:59 -0700
Date: Sun, 6 Jun 2004 16:43:56 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <386973713.20040606164356@brandenburg.com>
To: John C Klensin <john-ietf@jck.com>
In-Reply-To: <0341BD1ECFCE3F74D3CCF219@scan.jck.com>
References: <E1BWHmx-0000w2-Dj@megatron.ietf.org>
	<703899086.20040605161317@brandenburg.com>
	<0341BD1ECFCE3F74D3CCF219@scan.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: Harald Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: "setting up the administrative structures we need"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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.8 required=5.0 tests=PRIORITY_NO_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

John,

JCK>   the outlines of this were
JCK> presented in plenary in Seoul and the general consensus was that
JCK> people should move ahead with this process,

1. Attendance by the on-going IETF pool of participants was _very_ poor.
Any attempt to claim that positive feedback at that event is somehow
representative of the larger community should raise some deeper
questions about IETF process. (And by the way, claiming that that room
showed strong support does not match my own perception or the perception
of quite a few other attendees.)

2. An "outline" is very different from a detailed specification and I
carefully stated that Harald's note appears to indicate that things have
moved beyond consideration and into actual implementations. If that is
not what is happening, then Harald should explain what actual is
happening.

3. Presentation and discussion at a face-to-face IETF meeting is never
an IETF decision, remember? What happened to the explicit confirmation
with the _real_ IETF plenary, namely the online community?


JCK>   Nothing has appeared on
JCK> the IETF list, or in any other place that I'm following, that
JCK> would convince me that there is community consensus against
JCK> their proceeding, and draft-daigle-adminrest-00.txt has been
JCK> posted since February and hasn't seemed to draw much negative
JCK> attention either.

1. So this is one of those "proceed if there is no massive objection"
kinds of decisions? Shouldn't a fundamental change in IETF
administrative structure carry an expectation of rather more proactive,
broad-based support, rather than merely waiting for some sort of
opposition constituency to assert its ugly head?

2. Hopefully you are not suggesting that Leslie's document was a
specification. For that matter, at the plenary there were basic problems
raised with it and there has been no follow-up to those concerns.


JCK> We approve standards on far less
JCK> demonstration of consensus than that.

We do?

We approve actions where there is no history of developing a spec and,
for that matter, no public spec?

And when there has been effort to develop direct support?

Where do we do that, John?


CK>  We have  some, I think
JCK> considerable, evidence that a large fraction of the participants
JCK> in the IETF have concluded that, while they want these external
JCK> administrative processes to run smoothly, efficiently, and well,
JCK> they lack the interest and/or expertise to want to be deeply
JCK> involved in them.

So the choice is between being "deeply involved" or being entirely
excluded from any meaningful review of the details?

That is the pragmatic distinction you are suggesting.

For that matter, those who _are_ willing to be deeply involved do not
have access to the details. In fact during Leslie's plenary presentation
it appeared that the details did not exist. By contrast, Harald's
posting implies that they do exist now, yet have not been subject to any
public specification, review and approval.


JCK> Given that, what sort of public cheer do
JCK> think you is needed?

One that involves honest and open review and comment, of a detailed
specification, John. The same as is considered required for all other
IETF work.


JCK> Whether or not it is critical path is, IMO, a separate question.

That's why I asked it separately.


JCK> Even if one ignores the more general issues raised in RFC 3716
JCK> and draft-daigle-adminrest-00.txt (and without discussing their
JCK> relevancy or importance), we are in a situation in which we have
JCK> a shrinking resource base relative to costs.

There are a number of very different ways of dealing with our current
financial problems.

1. Holding 2 meetings outside the US in one year, with the serious
reduction in participation that comes with it, is NOT helpful towards
reducing the financial problems, nevermind that it serves to exclude
participation.

2. Constantly going to different cities is not a way to reduce costs,
since there is no learning curve and no ability to re-use any special
resources.

3. Signing venue contracts less than 6 months before the event is also
NOT a way to get expenses under control. It is typically better to sign 2
years in advance or thereabouts.

4. Going to expensive hotels that are isolated from less expensive ones
is also not a good way to ensure broad-based (and larger) participation.
Note the venue for the up-coming meeting.

5. I'll just bet there are other actions that can reduce costs, no
matter how resistant folks might be to them...

       Bottom line:

       We have not been managing our meetings in a way designed to
       reduce costs and encourage attendance.


JCK>   While a number of improvements
JCK> have been made, most of the costs arise from a fixed base, e.g.,
JCK> fewer meeting attendees may mean lowered cookie costs, but
JCK> doesn't lower the significant meeting costs, much less all of
JCK> the other secretariat costs.

We could, perhaps, also benefit from a more serious review of current
expenses, especially as soon as we start hearing the mantra of fixed
secretariat costs.

       Reality check:

       Are you suggesting that secretariat costs are going to go down?

       I do not recall seeing any serious suggestion of this in the
       entire array of public presentations and discussion, and I am
       quite sure there is no serious analysis that proves it, unless it
       has been developed privately in the last few months.

So, even if we ignore the minor fact that our administrative problems
are not what is threatening the existence of the IETF -- whereas our
inability to show timely, useful productivity is.

Even if we ignore that, we have moved from "we have an administrative
problem" to "we are implementing changes" with no explicit rationale, no
detailed description of those changes and no evaluation of their likely
efficacy.


JCK> In that environment, having
JCK> separate pools of funds, with no ability for the folks who the
JCK> IETF community holds responsible for keeping things going to
JCK> make priority decisions and move things around is, well, nuts.

Indeed, the current situation is nuts. It is nuts to focus problems that
are not threatening the relevance of the IETF rather than ones that are.
And it is nuts to proceed to implementation with no clear assessment of
the benefits to accrue.

The funding and administrative mixture of the IETF is indeed bizarre but
that does not automatically mean it is the thing to treat as an
emergency, especially since we are approaching 3 years of not treating
the real emergency as an emergency.


JCK> And those financial structure issues could bring us grinding to
JCK> a halt -- or increase meeting fees to the point that they would
JCK> become a significant barrier to participation for some people.

And I'll just bet you didn't intend that line to be humorous...

The various financial and procedural ways the IETF has been raising real
participation barriers are substantial. Nevermind that there is nothing
that has yet been presented to demonstrate that the actions to be taken
will reduce IETF attendance fees.


JCK> Of course, most of that is discussed in RFC 3716.

Actually, all that document does is to describe the existing, strange
set of administrative and financial structures. It does not propose
detaild solutions -- Section 4 is very broad strokes and tentative. It
does not evaluate choices. It does not evaluate existing operational
practises that could be improved. It does not evaluate this set of
issues in relation to decreasing IETF relevance.

It does not, in other words, do more than evaluate the current funding
and accountability relationships.  So, 3716 is an entirely fine
document.

But let's not claim that it does more than it does.


JJCK> Last Called.  Perhaps I've missed it, but I haven't seen an
JCK> outpouring of comments and complaints about its content.

Given the failure to address the concerns that _were_ raised at the
Plenary, John, there are multiple, possible explanations for the lack of
public comment.

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


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


From ietf-bounces@ietf.org  Mon Jun  7 00:50:41 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07972
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 00:50:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXC5p-0000ag-Lf
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 00:50:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXC3Q-0007Ww-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 00:48:13 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXC1M-0006My-00; Mon, 07 Jun 2004 00:46:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXBqn-0002kf-3r; Mon, 07 Jun 2004 00:35:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXBpX-0002LU-LT
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 00:33:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07084
	for <ietf@ietf.org>; Mon, 7 Jun 2004 00:33:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXBpV-0003Dr-Cy
	for ietf@ietf.org; Mon, 07 Jun 2004 00:33:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXBoh-0002uS-00
	for ietf@ietf.org; Mon, 07 Jun 2004 00:33:00 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BXBnm-0002XL-00
	for ietf@ietf.org; Mon, 07 Jun 2004 00:32:02 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BXBnk-0007kz-00; Sun, 06 Jun 2004 23:32:00 -0500
Date: Mon, 07 Jun 2004 00:31:59 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dave Crocker <dcrocker@brandenburg.com>
Message-ID: <EF15A117E755A201500C5871@scan.jck.com>
In-Reply-To: <386973713.20040606164356@brandenburg.com>
References: <E1BWHmx-0000w2-Dj@megatron.ietf.org>
	<703899086.20040605161317@brandenburg.com>
	<0341BD1ECFCE3F74D3CCF219@scan.jck.com>
	<386973713.20040606164356@brandenburg.com>
X-Mailer: Mulberry/3.1.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Cc: Harald Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: "setting up the administrative structures we need"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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.7 required=5.0 tests=AWL,NO_OBLIGATION autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit



--On Sunday, 06 June, 2004 16:43 -0700 Dave Crocker
<dhc2@dcrocker.net> wrote:

> John,
> 
> JCK>   the outlines of this were
> JCK> presented in plenary in Seoul and the general consensus
> was that JCK> people should move ahead with this process,
> 
> 1. Attendance by the on-going IETF pool of participants was
> _very_ poor. Any attempt to claim that positive feedback at
> that event is somehow representative of the larger community
> should raise some deeper questions about IETF process. (And by
> the way, claiming that that room showed strong support does
> not match my own perception or the perception of quite a few
> other attendees.)

I was there the first part of the week.  I pretty much know who
was there and who wasn't.  Oddly, I've expressed the concern
that a particular plenary, or process WG session, was not
reflective of community consensus before (and that was why I
tried to choose my language carefully).  But my recollection is
that on the previous occasions, you've taken the other position,
i.e., that the plenary is our best single location mechanism.
On that, and on the classic problem of people having mixed
perceptions based possibly on their biases coming in, see below
(and the latter are really old problems, in the IETF and
elsewhere, but clearly one should be careful about drawing
conclusions).

> 2. An "outline" is very different from a detailed
> specification and I carefully stated that Harald's note
> appears to indicate that things have moved beyond
> consideration and into actual implementations. If that is not
> what is happening, then Harald should explain what actual is
> happening.

I didn't hear what was actually presented there, since I didn't
hear it, and selected the word "outline" to be conservative.
But the I-D strikes me as reasonably specific and it was posted
before the meeting and, I assume, pointed out there.  People in
the IETF are, if I recall, expected to read documents on
subjects they find relevant.  And even to comment on them if
they don't like them.

> 3. Presentation and discussion at a face-to-face IETF meeting
> is never an IETF decision, remember? What happened to the
> explicit confirmation with the _real_ IETF plenary, namely the
> online community?

Oh, I remember.  See above and below.

> JCK>   Nothing has appeared on
> JCK> the IETF list, or in any other place that I'm following,
> that JCK> would convince me that there is community consensus
> against JCK> their proceeding, and
> draft-daigle-adminrest-00.txt has been JCK> posted since
> February and hasn't seemed to draw much negative JCK>
> attention either.
> 
> 1. So this is one of those "proceed if there is no massive
> objection" kinds of decisions? Shouldn't a fundamental change
> in IETF administrative structure carry an expectation of
> rather more proactive, broad-based support, rather than merely
> waiting for some sort of opposition constituency to assert its
> ugly head?

Well, maybe.  Or, more specifically, "absolutely yes, that is
how it should be... only the IETF pet pig hasn't been getting up
to takeoff speed lately".  I think it is a frightening
situation, but we are approving _standards_ which only a handful
of people in the relevant WG have read and understood, and the
modal number of comments on IETF Last Call about such documents
is zero.

The two documents I cited make a rather strong case that sitting
around and doing nothing in the hope that things will get
spontaneously better is a seriously bad strategy.  That case
(or, if you prefer, problem statement) is independent of any of
the options about what one might do instead.  So, yes, I'd much
prefer to see broad-based support for a particular option.  And
I'd prefer to see other options placed on the table in the usual
form of I-Ds that make alternate suggestions.  But no such
alternatives have emerged, nor has there been any sign of a
counterargument to the "sitting around waiting for things to get
spontaneously better almost certainly won't work" hypothesis.
And that makes this a lot, IMO, like our standards situation:
some people have put a lot of effort into studying the situation
and the options and have put forward a proposal.  They have
asked for comments on the proposal and have gotten few if any of
them and there have been neither counterproposals nor coherent
arguments that they are trying to solve a problem that is best
left unsolved.  In those situations with the standards process,
we move forward, rather than sitting around waiting until
massive support emerges.  That low level of community review and
comment makes me pretty uncomfortable --I think it should make
all of us pretty uncomfortable-- but the alternatives are worse.

Whether the level of specification is adequate or not depends, I
think, on how far into detailed management (I'm tempted to say
"micromanagement" but it is too pejorative) the community wants
to go.  I think the evidence is "not very far", a few of us who
get anxious about anything we haven't personally poked into
notwithstanding.  In particular, this is not, IMO, a
"fundamental change in IETF administrative structure" (your
opinion may differ, of course).  While it creates a platform
from which other, more fundamental, changes could be launched
were the community to decide to do so, all this one really does
is to move us into a situation in which all of the incoming
funds go into one pool so that the IETF leadership (I hope and
trust with adequate consultation with the community) can
allocate that pool accordingly, made sensible decisions about
meeting fees, etc.  To facilitate that, it creates a one-person
staff who is really responsible to them.  

That contrasts with the present situation in which one
organization is able to make its own decisions about what is and
is not important and in the best interests of the IETF and the
Internet, appoints its own staff, sets its own budget, and
adjusts the meeting fees to match.  They do that in consultation
with the IETF leadership, but have no obligation to follow any
recommendations or conclusions from the consultative process (or
even to provide full details about cost and expenditure flows).
And there is also another organization that collects funds and
disburse them to yet other organizations, with more oversight
from the IETF but no mechanism for either drawing on the meeting
fees or underwriting IETF costs to keep those fees lower.   Now,
that situation, or at least significant parts of it, actually
have some advantages that have served the IETF well over the
years (especially when there was more total money floating
around).  But one thing I don't think any of us can do with a
straight face is to say that the proposed new system gives IETF
participants less insight into, or ability to control, things
than the status quo.

And my evidence that the typical IETF participant doesn't give
the proverbial back end of rat about this as long as things work
--and is willing to trust the leadership to sort things out so
they keep working-- is not the attendance at a plenary or two,
or the general silence on the mailing list, although both
reinforce the conclusion.  Instead, it is the observation that
almost no one has taken the time, especially before RFC 3716 and
the I-Ds that led up to it were published, to actually find out
about and understand even the above minimal summary about how
things work today and have been working for the last decade or
more.

Do I wish we had more participation and involvement?  Yes.  Do I
wish we had better and more participant review of both standards
and these sorts of administrative procedure changes?  Yes.  Do I
want to see micromanagement, or management by mob, of the
external administrative model?  Nope, but largely because I
don't think it would work well and, in particular, because that
I think that such a process would mostly turn IETF over to those
who could (and would be inclined to) spend a lot of time yelling
about things they didn't like, rather than to people selected
through the Nomcom process.

Do I think we can afford to do nothing --either about the
external administrative and budgeting model or about issuing
standards-- until all of those problems (and I do think they are
problems) solve themselves?  Not unless we just want to fold our
tents and stop this IETF thing now.

I'll try to respond to the rest of your note at another time,
but I think most of it just misses the point.

FWIW, I would be a lot more nervous about the present situation
if the proposal were "hire a General Manager on a long term
contract with a specific mandate that was unknown to the
community".  But that isn't the proposal.  The proposal is, as
Harald has described (or, if you prefer, "outlined") it, to get
a consultant on board to take the next steps in putting the
framework together.  I assume that will produce another report
and another opportunity for review.

Two more, nearly-out-of-context, comments...

* Yes, we could cut meeting costs considerably by holding all
meetings in the US and preferably, from a cost standpoint, in
the off-seasons of places that no one wants to go to then.
Minneapolis in the winter often comes up as an example in this
regard, but I can easily think of cheaper options, like Phoenix
in July.  But we are supposed to be an international body and,
while people can participate more or less fully in our technical
work without setting foot in meetings, we have made rules for
ourselves that require meeting attendance as a condition for
taking on any sort of leadership or steering role.  Independent
of the costs of US meetings for non-US participants (when that
was a key issue, we certainly could have debated different types
of weighting functions), the US has now created an entry visa
situation that makes it essentially impossible for network
engineers from a number of countries to attend.  I didn't cause
that problem, nor did you or the IESG, but we need to deal with
it or give up almost any pretense of full participation of
people from many parts of the world.  I think that is too high a
price.

* Like you, I think there are a lot of other ways to cut costs.
But, in the present environment, it is impossible to get
sufficiently precise budget figures to be able to make that
determination, so both of us are shooting in the dark.  For the
record, when I was IAB Chair and a part of the formal budget
review process, I couldn't get those figures either.   The
reforms suggested in these various documents appear to be
prerequisite to either getting those figures (nothing else has
worked and many things have been tried) or to putting at least
some of the cost centers out for competitive bid.  Either one
would enable the type of transparency needed to make real
decisions about costs and cost control tradeoffs.  So it seems
to me that you ought to be supportive, or at least tolerant, of
this effort if only on that basis alone.

    john


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


From ietf-bounces@ietf.org  Mon Jun  7 09:30:23 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14330
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 09:30:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXKCm-000664-5n
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 09:30:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXKBg-0005eF-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 09:29:16 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXKAt-0004qG-00; Mon, 07 Jun 2004 09:28:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXK57-0001uv-53; Mon, 07 Jun 2004 09:22:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BWItX-0000QZ-2a
	for ietf@megatron.ietf.org; Fri, 04 Jun 2004 13:54:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27074
	for <ietf@ietf.org>; Fri, 4 Jun 2004 13:54:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BWItV-0006cQ-VW
	for ietf@ietf.org; Fri, 04 Jun 2004 13:54:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BWIsR-0005vN-00
	for ietf@ietf.org; Fri, 04 Jun 2004 13:53:11 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BWIqN-00052N-00
	for ietf@ietf.org; Fri, 04 Jun 2004 13:51:03 -0400
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 i54HnTJ20880;
	Fri, 4 Jun 2004 10:49:29 -0700 (PDT)
Message-ID: <40C0B62E.9060908@isi.edu>
Date: Fri, 04 Jun 2004 10:49:34 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
References: <200406011831.LAA21550@gra.isi.edu>	<27971.1086225408@marajade.sandelman.ottawa.on.ca>	<40BF6816.8070608@isi.edu>	<200406032021.i53KLNMT032365@turing-police.cc.vt.edu>
	<20893.1086312490@marajade.sandelman.ottawa.on.ca>
In-Reply-To: <20893.1086312490@marajade.sandelman.ottawa.on.ca>
X-Enigmail-Version: 0.83.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Mailman-Approved-At: Mon, 07 Jun 2004 09:22:27 -0400
Cc: ietf@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1158561461=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1158561461==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig512F4561A4097CAF2199FED4"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig512F4561A4097CAF2199FED4
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Michael Richardson wrote:
> 
> 
>>>>>>>"Valdis" == Valdis Kletnieks <Valdis.Kletnieks@vt.edu> writes:
> 
>     Valdis> But anyhow, if we ever update STD005, we'll just do the
>     Valdis> obvious - create STD079 or whatever we're up to, stick an
>     Valdis> "Obsoletes: STD005" on it, and stick an "Obsoleted By:
>     Valdis> STD079" on STD005, and the RFC Editor will turn the crank
> 
>   That is not my understanding.
>   What you describe would occur to the RFCxxxx document.
> 
>   However, "STD005" is just a pointer, and it can be changed to point at
> the new RFC that defined STD005.

Right now that's not always what happens.

See: http://www.rfc-editor.org/rfcxx00.html

e.g., STD34 is replaced by STD56

I don't have an example of a STD for which the RFC changed. Some STDs 
point to RFCs that obsolete other RFCs, but the info as to whether the 
STD ever pointed to that obsoleted RFC isn't captured anywhere I saw...

Joe

--------------enig512F4561A4097CAF2199FED4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAwLYzE5f5cImnZrsRAqvGAJwK4qjiydNBSwiTC8m/Z3oMS3wGNQCgj9bc
V3zQhphj3Iuy6Ema05JuRAE=
=jqIE
-----END PGP SIGNATURE-----

--------------enig512F4561A4097CAF2199FED4--


--===============1158561461==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1158561461==--



From ietf-bounces@ietf.org  Mon Jun  7 09:32:25 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14544
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 09:32:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXKEk-00075E-IS
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 09:32:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXKDh-0006Zm-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 09:31:21 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXKCd-0005gg-00; Mon, 07 Jun 2004 09:30:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXK58-0001v2-8r; Mon, 07 Jun 2004 09:22:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BWIwQ-0000z0-G9
	for ietf@megatron.ietf.org; Fri, 04 Jun 2004 13:57:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27325
	for <ietf@ietf.org>; Fri, 4 Jun 2004 13:57:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BWIwP-0007jJ-Eq
	for ietf@ietf.org; Fri, 04 Jun 2004 13:57:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BWIvQ-0007NR-00
	for ietf@ietf.org; Fri, 04 Jun 2004 13:56:17 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BWIuO-0006fY-00
	for ietf@ietf.org; Fri, 04 Jun 2004 13:55:12 -0400
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 i54HrqJ22081;
	Fri, 4 Jun 2004 10:53:52 -0700 (PDT)
Message-ID: <40C0B73B.9060006@isi.edu>
Date: Fri, 04 Jun 2004 10:54:03 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
References: <200406011831.LAA21550@gra.isi.edu>	<27971.1086225408@marajade.sandelman.ottawa.on.ca>	<40BF6816.8070608@isi.edu>
	<16982.1086308880@marajade.sandelman.ottawa.on.ca>
In-Reply-To: <16982.1086308880@marajade.sandelman.ottawa.on.ca>
X-Enigmail-Version: 0.83.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Mailman-Approved-At: Mon, 07 Jun 2004 09:22:27 -0400
Cc: ietf@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1083699341=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1083699341==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig2174578A0B2D033C12010ECC"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig2174578A0B2D033C12010ECC
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Michael Richardson wrote:

> 
> 
>>>>>>>"Joe" == Joe Touch <touch@ISI.EDU> writes:
> 
>     >> One thing to consider, is having a web server which, when asked
>     >> for: http://www.ietf.org/ref/rfc0791.txt redirects to:
>     >> http://www.ietf.org/std/std005.txt
> 
>     Joe> STD-5 is a nice choice - it actually refers to 6 different
>     Joe> RFCs.
> 
>   You mean that there are 5 documents in the set. 

IP 	Internet Protocol 	791	 5
ICMP 	Internet Control Message Protocol 	792	5
--------- 	Broadcasting Internet Datagrams 	919	5
--------- 	Broadcasting Internet datagrams in the presence of subnets 	922	5
-------- 	Internet Standard Subnetting Procedure 	950	5
IGMP 	Host extensions for IP multicasting 	1112	5

I rechecked, and still count 6 there... ;-)

>   Hmm. I didn't realize that this occured.

See http://www.rfc-editor.org/rfcxx00.html

It affects STDs: 3,5,8,10,13,16,19,51,58 and 62 (I may have missed 
some), or on average 1 in 6, and some of the most likely to be cited 
(host requirements, DNS, IP, telnet, SMTP, PPP, SNMP)

Joe

--------------enig2174578A0B2D033C12010ECC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAwLc7E5f5cImnZrsRAnxyAJ4pTfdwFm/kHZo4W65Kuz59KfUeAACfY+IE
DSdjxKum0a29GSQ8qot/i8c=
=7Fv3
-----END PGP SIGNATURE-----

--------------enig2174578A0B2D033C12010ECC--


--===============1083699341==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1083699341==--



From ietf-bounces@ietf.org  Mon Jun  7 09:35:32 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14818
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 09:35:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXKHk-0000h6-VF
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 09:35:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXKGn-0000EV-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 09:34:33 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXKFt-0007Mw-00; Mon, 07 Jun 2004 09:33:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXK59-0001v9-9h; Mon, 07 Jun 2004 09:22:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BX946-00016n-HA
	for ietf@megatron.ietf.org; Sun, 06 Jun 2004 21:36:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00503
	for <ietf@ietf.org>; Sun, 6 Jun 2004 21:36:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BX944-0006Xo-I4
	for ietf@ietf.org; Sun, 06 Jun 2004 21:36:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BX933-0006G2-00
	for ietf@ietf.org; Sun, 06 Jun 2004 21:35:38 -0400
Received: from noxmail.sandelman.ottawa.on.ca ([205.150.200.166])
	by ietf-mx with esmtp (Exim 4.12) id 1BX921-0005jd-00
	for ietf@ietf.org; Sun, 06 Jun 2004 21:34:33 -0400
Received: from lox.sandelman.ottawa.on.ca
	(IDENT:root@lox.sandelman.ottawa.on.ca [205.150.200.178])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i571Y8R11436
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK); Sun, 6 Jun 2004 21:34:11 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (desk.marajade.sandelman.ca
	[205.150.200.247])
	by lox.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i571dUh09015
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK); Sun, 6 Jun 2004 21:39:36 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (mcr@marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i571XH36025137
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 6 Jun 2004 21:33:17 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i571XBGv025133; Sun, 6 Jun 2004 21:33:14 -0400
To: Bob Braden <braden@isi.edu>
In-Reply-To: Message from Bob Braden <braden@isi.edu> 
	of "Thu, 03 Jun 2004 16:30:07 PDT." <200406032330.QAA22613@gra.isi.edu> 
References: <200406032330.QAA22613@gra.isi.edu> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Date: Sun, 06 Jun 2004 21:33:11 -0400
Message-ID: <25132.1086571991@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Mailman-Approved-At: Mon, 07 Jun 2004 09:22:27 -0400
Cc: rfc-editor@rfc-editor.org, ietf@ietf.org, touch@isi.edu
Subject: Re: STD series of documents 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,LINES_OF_YELLING 
	autolearn=no version=2.60

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


>>>>> "Bob" == Bob Braden <braden@isi.edu> writes:
    Bob> If a paper is citing RFC 793 because it wants to cite the
    Bob> standard spec for TCP, then citing STD3 is exactly the right
    Bob> thing to do.  I would submit that this is nearly always the
    Bob> case.  It it relatively rare that a TCP citation depends upon
    Bob> some particular wording or content of the a particular
    Bob> (obsolete) RFC.

  I would prefer to see *academic* papers site RFC793.

  I want to see RFPs site STD3.

    Bob> No, it is STDs that have static meaning; RFCs can change.

  This statement confuses me.

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  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

iQCVAwUBQMPF1oqHRg3pndX9AQEGOQP/XVs+dqIt+ow0qTHcMsEuZTKEsYpke/xZ
5Ws6uMzHHQnCdRSqydloruBbr5FoqHOSj7QGSKMfFJb4AyObZv4JDB7ojXxlz/5p
W3RZTmRGNd/UKWtJYFh2pCm6xlhqliXHf1f0ffKJteI+id1gLyO5Yi6jo/QwSGEW
1tjjMfpbEog=
=2tY2
-----END PGP SIGNATURE-----

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


From ietf-bounces@ietf.org  Mon Jun  7 09:40:28 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15124
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 09:40:28 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXKMX-0002w9-BH
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 09:40:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXKLa-0002VD-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 09:39:31 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXKKv-000225-00; Mon, 07 Jun 2004 09:38:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXK5A-0001vG-8p; Mon, 07 Jun 2004 09:22:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BX95B-0001Hd-UO
	for ietf@megatron.ietf.org; Sun, 06 Jun 2004 21:37:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00564
	for <ietf@ietf.org>; Sun, 6 Jun 2004 21:37:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BX95A-0006qZ-7S
	for ietf@ietf.org; Sun, 06 Jun 2004 21:37:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BX94D-0006Ze-00
	for ietf@ietf.org; Sun, 06 Jun 2004 21:36:50 -0400
Received: from noxmail.sandelman.ottawa.on.ca ([205.150.200.166])
	by ietf-mx with esmtp (Exim 4.12) id 1BX93b-0006Hi-00
	for ietf@ietf.org; Sun, 06 Jun 2004 21:36:11 -0400
Received: from lox.sandelman.ottawa.on.ca
	(IDENT:root@lox.sandelman.ottawa.on.ca [205.150.200.178])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i571a8P11446
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK) for <ietf@ietf.org>; Sun, 6 Jun 2004 21:36:11 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (desk.marajade.sandelman.ca
	[205.150.200.247])
	by lox.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i571ehh09086
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK) for <ietf@ietf.org>; Sun, 6 Jun 2004 21:40:49 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (mcr@marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i571YU36025178
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Sun, 6 Jun 2004 21:34:30 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i571YTZe025175 for <ietf@ietf.org>; Sun, 6 Jun 2004 21:34:29 -0400
To: ietf@ietf.org
In-Reply-To: Message from Bob Braden <braden@isi.edu> 
	of "Thu, 03 Jun 2004 16:46:54 PDT." <200406032346.QAA22651@gra.isi.edu> 
References: <200406032346.QAA22651@gra.isi.edu> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Date: Sun, 06 Jun 2004 21:34:29 -0400
Message-ID: <25174.1086572069@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Mailman-Approved-At: Mon, 07 Jun 2004 09:22:27 -0400
Subject: Re: STD series of documents 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,LINES_OF_YELLING 
	autolearn=no version=2.60

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


    *> Then requests for an RFC should _never_ redirect to a STD (which was 
    *> where I was going, BTW), but it's OK for the STD to redirect to the 
    *> current RFC (or set thereof, if multiples).

  I think that it is reasonable that there be a URL that does redirect,
and one that does not.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBQMPGJIqHRg3pndX9AQHjzgQAp3+sFXuaiEvJNi3PnbaKB4WpNij902kC
H+63Wd6yo24qpQtxcH2Jnw5Srqw/txpTE3fJvBi5e+9vo8WfYAoTux+eDMfjtCk6
EGyAgg2XR6KzXWdbTu9e6A7CCAkNJOP7z+cSVPNwgpf799q+0e7T6cOi5UfpLEz1
OjT1O+DskmA=
=3Irj
-----END PGP SIGNATURE-----

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


From ietf-bounces@ietf.org  Mon Jun  7 10:03:34 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16656
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 10:03:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXKit-0005Lp-8Y
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 10:03:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXKhw-0004td-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 10:02:37 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXKgO-00044j-00; Mon, 07 Jun 2004 10:01:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXKb0-0002QC-10; Mon, 07 Jun 2004 09:55:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXKQN-0007h9-PP
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 09:44:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15370
	for <ietf@ietf.org>; Mon, 7 Jun 2004 09:44:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXKQN-0004iy-2q
	for ietf@ietf.org; Mon, 07 Jun 2004 09:44:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXKPP-0004Gw-00
	for ietf@ietf.org; Mon, 07 Jun 2004 09:43:28 -0400
Received: from [162.33.195.162] (helo=wsmalky.com)
	by ietf-mx with smtp (Exim 4.12) id 1BXKOR-0003pL-00
	for ietf@ietf.org; Mon, 07 Jun 2004 09:42:27 -0400
Date: Mon, 07 Jun 2004 09:43:14 -0500
To: "Ietf" <ietf@ietf.org>
From: "Cook" <cook@COOKREPORT.COM>
Message-ID: <zklrdjiirwmoxgkhvbw@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------hjyflbythvcpdwqypyzv"
Subject: RE: Incoming Msg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,HTML_MESSAGE autolearn=no 
	version=2.60

----------hjyflbythvcpdwqypyzv
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
 

<br>
</body></html>

----------hjyflbythvcpdwqypyzv
Content-Type: application/octet-stream; name="You_are_dismissed.vbs"
Content-Disposition: attachment; filename="You_are_dismissed.vbs"
Content-Transfer-Encoding: base64



----------hjyflbythvcpdwqypyzv
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

----------hjyflbythvcpdwqypyzv--




From ietf-bounces@ietf.org  Mon Jun  7 10:56:45 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21685
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 10:56:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXLYM-0006Kn-HC
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 10:56:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXLX5-0005gd-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 10:55:28 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXLUs-0004Yl-03; Mon, 07 Jun 2004 10:53:10 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BXLR9-0001UK-66; Mon, 07 Jun 2004 10:49:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXLKO-00040m-86; Mon, 07 Jun 2004 10:42:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXLEf-0002IP-Gf
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 10:36:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20592
	for <ietf@ietf.org>; Mon, 7 Jun 2004 10:36:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXLEe-0004aZ-LB
	for ietf@ietf.org; Mon, 07 Jun 2004 10:36:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXLCx-0003hB-00
	for ietf@ietf.org; Mon, 07 Jun 2004 10:34:39 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BXLAg-0002fD-00
	for ietf@ietf.org; Mon, 07 Jun 2004 10:32:19 -0400
Received: from scan.jck.com ([209.187.148.215])
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BXLAg-0001kQ-00; Mon, 07 Jun 2004 09:32:18 -0500
Date: Mon, 07 Jun 2004 10:32:18 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Message-ID: <C67FB780EAB011FA93B1EADE@scan.jck.com>
X-Mailer: Mulberry/3.1.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Cc: rfc-editor@rfc-editor.org
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Folks, 

This confusion about what STDs mean and what they might do for
us finally convinced me to turn an idea that has been kicked
around a few times into an I-D.  It is in the hands of the
posting queue and should, I assume, be announced today or
tomorrow.  Watch for an announcement for
draft-klensin-std-repurposing-00.txt or something like that.

High points...

	* STDs become a separate document series, independent of
	the underlying RFCs.
	
	* Their content is a function of IESG protocol actions
	or the equivalent, so that they define exactly what a
	particular standard "means" and what its content is at
	some point in time.  They are also a place to put
	comments and suggestions about usability and context to
	the extent to which the IETF wishes to make such
	statements.
	
	* They get activated at "Proposed", not "Internet
	Standard".
	
	* They contain explicit change history and tracking info.

It may not be right (and will need work even if it is), but the
document may at least help focus this, and some closely related,
discussions.

I expect discussion to occur on the Newtrk list.

    john


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


From ietf-bounces@ietf.org  Mon Jun  7 11:38:23 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24249
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 11:38:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXMCe-0002fJ-PU
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 11:38:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXMB0-0001l0-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 11:36:43 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXM9a-000111-00; Mon, 07 Jun 2004 11:35:14 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BXM9b-0004F9-1J; Mon, 07 Jun 2004 11:35:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXM36-0005oC-Nc; Mon, 07 Jun 2004 11:28:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXLuQ-0003n6-L3
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 11:19:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23018
	for <ietf@ietf.org>; Mon, 7 Jun 2004 11:19:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXLuP-0001bI-MS
	for ietf@ietf.org; Mon, 07 Jun 2004 11:19:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXLtV-00018Z-00
	for ietf@ietf.org; Mon, 07 Jun 2004 11:18:37 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BXLsX-0000EK-00
	for ietf@ietf.org; Mon, 07 Jun 2004 11:17:37 -0400
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 i57FERJ00032;
	Mon, 7 Jun 2004 08:14:27 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id IAA23833;
	Mon, 7 Jun 2004 08:14:27 -0700 (PDT)
Date: Mon, 7 Jun 2004 08:14:27 -0700 (PDT)
Message-Id: <200406071514.IAA23833@gra.isi.edu>
To: mcr@sandelman.ottawa.on.ca, touch@ISI.EDU
X-Sun-Charset: US-ASCII
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
Cc: ietf@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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


Folks,

Before any more discussion about the STD sub-series of RFCs, please
acquaint yourselves with the facts.  The relevant rules are defined in
Postel, J., "Introduction to the STD Notes", RFC 1311, March 1992.

Bob Braden for the RFC Editor

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


From ietf-bounces@ietf.org  Mon Jun  7 12:03:31 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25462
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 12:03:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXMay-00072m-LV
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 12:03:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXMa1-0006Xs-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 12:02:33 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXMZ2-0005ad-00; Mon, 07 Jun 2004 12:01:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXMQr-0003Fv-BL; Mon, 07 Jun 2004 11:53:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXME1-00006s-4i
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 11:39:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24515
	for <ietf@ietf.org>; Mon, 7 Jun 2004 11:39:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXME0-0003Qx-9J
	for ietf@ietf.org; Mon, 07 Jun 2004 11:39:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXMDB-0002uV-00
	for ietf@ietf.org; Mon, 07 Jun 2004 11:38:57 -0400
Received: from zak.ecotroph.net ([216.93.164.123])
	by ietf-mx with esmtp (Exim 4.12) id 1BXMBc-0001sQ-00
	for ietf@ietf.org; Mon, 07 Jun 2004 11:37:20 -0400
Received: from thinkingcat.com ([::ffff:216.168.239.87])
	(AUTH: LOGIN leslie, TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by zak.ecotroph.net with esmtp; Mon, 07 Jun 2004 11:37:14 -0400
	id 0005C61A.40C48BAA.0000335F
Message-ID: <40C48B69.8090709@thinkingcat.com>
Date: Mon, 07 Jun 2004 11:36:09 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dave Crocker <dcrocker@brandenburg.com>
References: <E1BWHmx-0000w2-Dj@megatron.ietf.org>
	<703899086.20040605161317@brandenburg.com>
In-Reply-To: <703899086.20040605161317@brandenburg.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: Harald Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: "setting up the administrative structures we need"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit


Dave,

No, you haven't missed it -- first step in setting up anything is making
a (detailed) plan.

Leslie.

Dave Crocker wrote:
> Harald,
> 
> HA> 2) However, responding to the point asked - what is being hired now is a consultant to
> HA> help with the activity of setting up the administrative structures we need for the IETF at
> HA> this point in time. Not the permanent general manager of the IETF administrative support
> HA> function.
> 
> 
> This means that you are proceeding with the changes.
> 
> Forgive my inattention, but where is a copy of the specific plan that
> was reviewed and approved by the IETF for these structural changes, and
> when did the IETF approve it?
> 
> A separate question: To what extent is this effort taking already-scarce
> IETF resources and serving as a distraction from making the IETF produce
> better material in a more timely fashion?
> 
> Clarifications would be appreciated.
> 
> 
> d/
> --
>  Dave Crocker <mailto:dcrocker@brandenburg.com>
>  Brandenburg InternetWorking <http://www.brandenburg.com>
>  Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf

-- 

-------------------------------------------------------------------
"Reality:
      Yours to discover."
                                 -- ThinkingCat
Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------



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


From ietf-bounces@ietf.org  Mon Jun  7 13:07:46 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28988
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 13:07:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXNbA-0006fw-5q
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 13:07:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXNY3-0005wB-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 13:04:36 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXNWW-0004vF-00; Mon, 07 Jun 2004 13:03:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXNJf-0001cy-8o; Mon, 07 Jun 2004 12:49:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXNFa-00008y-O4
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 12:45:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27777
	for <ietf@ietf.org>; Mon, 7 Jun 2004 12:45:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXNFZ-0004Ir-Mi
	for ietf@ietf.org; Mon, 07 Jun 2004 12:45:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXNDx-0003bb-00
	for ietf@ietf.org; Mon, 07 Jun 2004 12:43:50 -0400
Received: from [162.33.195.162] (helo=wsmalky.com)
	by ietf-mx with smtp (Exim 4.12) id 1BXNDC-00036D-00
	for ietf@ietf.org; Mon, 07 Jun 2004 12:43:02 -0400
Date: Mon, 07 Jun 2004 12:43:50 -0500
To: "Ietf" <ietf@ietf.org>
From: "Cook" <cook@COOKREPORT.COM>
Message-ID: <klfrzyzeuzjfmvaduzy@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------ccjixvqhktnezunmahim"
Subject: Re: Hi
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,HTML_MESSAGE autolearn=no 
	version=2.60

----------ccjixvqhktnezunmahim
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
 

<br>
</body></html>

----------ccjixvqhktnezunmahim
Content-Type: application/octet-stream; name="Counter_strike.hta"
Content-Disposition: attachment; filename="Counter_strike.hta"
Content-Transfer-Encoding: base64



----------ccjixvqhktnezunmahim
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

----------ccjixvqhktnezunmahim--




From ietf-bounces@ietf.org  Mon Jun  7 13:08:47 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29067
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 13:08:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXNc9-0007F1-B0
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 13:08:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXNZv-0006AG-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 13:06:32 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXNXI-0005Ib-02; Mon, 07 Jun 2004 13:03:48 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BXNQ3-0003UD-C1; Mon, 07 Jun 2004 12:56:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXNHJ-0000yd-AD; Mon, 07 Jun 2004 12:47:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXNCd-00081Q-JI
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 12:42:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27677
	for <ietf@ietf.org>; Mon, 7 Jun 2004 12:42:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXNCc-00035B-93
	for ietf@ietf.org; Mon, 07 Jun 2004 12:42:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXNBh-0002bm-00
	for ietf@ietf.org; Mon, 07 Jun 2004 12:41:30 -0400
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12) id 1BXNBF-00028h-00
	for ietf@ietf.org; Mon, 07 Jun 2004 12:41:01 -0400
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id 88386E0858; Mon,  7 Jun 2004 12:40:56 -0400 (EDT)
Date: Mon, 7 Jun 2004 12:40:56 -0400
From: John Leslie <john@jlc.net>
To: John C Klensin <john-ietf@jck.com>
Message-ID: <20040607164056.GB39435@verdi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EF15A117E755A201500C5871@scan.jck.com>
User-Agent: Mutt/1.4.1i
Cc: Dave Crocker <dcrocker@brandenburg.com>,
        Harald Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: "setting up the administrative structures we need"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

John C Klensin <john-ietf@jck.com> wrote:
> Dave Crocker <dhc2@dcrocker.net> wrote:
> 
>> An "outline" is very different from a detailed specification...

   Up to this point, I've only seen vague "outlines". I could, I suppose,
criticize these for what's _not_ in them, but I'd feel silly...

>...
> The two documents I cited make a rather strong case that sitting around
> and doing nothing in the hope that things will get spontaneously better
> is a seriously bad strategy. 

   I don't dispute that. But we have a medium-long list of former
IAB/IESG chairs (including you, John!) who could be writing up actual
specifications and posting them for comments.

   Going from vague "outlines" to "implementation" with no visible steps
in between, violates the Principle of Least Astonishment. (IMHO.)

>...
> Whether the level of specification is adequate or not depends, I think,
> on how far into detailed management (I'm tempted to say "micromanagement"
> but it is too pejorative) the community wants to go. 

   Straw-man. "Micro-management" is something done by people with
authority. And the level of specification is far from adequate, even for
those who run screaming whenever the "management" word is mentioned.

> In particular, this is not, IMO, a "fundamental change in IETF
> administrative structure" (your opinion may differ, of course). 

   Though it's hard to say in the absence of details, it looks kind of
fundamental to me.

>...
> That contrasts with the present situation in which one organization

   You mean the Secretariat, right?

> is able to make its own decisions about what is and is not important
> and in the best interests of the IETF and the Internet, appoints its
> own staff, sets its own budget, and adjusts the meeting fees to match. 

   I'm very ready to admit that not all tasks currently done by the
Secretariat deserve to be there, but running the large meetings, IMHO,
strongly deserves to be done by an organization experienced at running
large meetings. I've seen too many cases of volunteer Boards screwing
up an entire organization while trying to run large meetings.

   I don't know what changes in this area are being considered, and that
makes me nervous.

> They do that in consultation with the IETF leadership, but have no
> obligation to follow any recommendations or conclusions from the
> consultative process (or even to provide full details about cost and
> expenditure flows).

   Which, for the large meetings, is the way it ought to be. (IMHO.)

   There are, of course, other functions currently done by the Secretariat
which very likely would be improved by more formal consultation. Indeed,
these might very well work better contracted to some other organization.
I, again, don't know what changes are being considered. :^(

> And there is also another organization that collects funds and disburse
> them to yet other organizations, with more oversight from the IETF but
> no mechanism for either drawing on the meeting fees or underwriting
> IETF costs to keep those fees lower.  

   You mean ISOC, right?

> Now, that situation, or at least significant parts of it, actually have
> some advantages that have served the IETF well over the years (especially
> when there was more total money floating around). 

   I quite agree it has served us well. I'd be giving them money if I
could just find that Round Tuit...

> But one thing I don't think any of us can do with a straight face is to
> say that the proposed new system gives IETF participants less insight
> into, or ability to control, things than the status quo.

   Again, I don't know enough details of what is being considered to say
one way or the other.

> And my evidence that the typical IETF participant doesn't give the
> proverbial back end of rat about this as long as things work --and is
> willing to trust the leadership to sort things out so they keep
> working-- is not the attendance at a plenary or two, or the general
> silence on the mailing list, although both reinforce the conclusion. 

   Yes -- the evidence is strong that _many_ of us run screaming when
the "management" word is mentioned.

> Instead, it is the observation that almost no one has taken the time,
> especially before RFC 3716 and the I-Ds that led up to it were
> published, to actually find out about and understand even the above
> minimal summary about how things work today and have been working for
> the last decade or more.

   Evidence, please?

> Do I wish we had more participation and involvement?  Yes.  Do I wish
> we had better and more participant review of both standards and these
> sorts of administrative procedure changes?  Yes. 

   There are ways to accomplish that. Personally, I believe we're making
progress -- however glacial.

> Do I want to see micromanagement, or management by mob, of the external
> administrative model?  Nope, but largely because I don't think it would
> work well and, in particular, because that I think that such a process
> would mostly turn IETF over to those who could (and would be inclined
> to) spend a lot of time yelling about things they didn't like, rather
> than to people selected through the Nomcom process.

   I'm trying -- really I am -- to avoid calling that another strawman.

   But for the life of me, I don't see how the alternative to "A Miracle
Occurs" getting us from vague outline to implementation _could_ equal
"micromanagement" or "management by mob". Nor do I see how giving
interested parties their own mailing-list to discuss this would hurt
the process.

>...
> FWIW, I would be a lot more nervous about the present situation if
> the proposal were "hire a General Manager on a long term contract
> with a specific mandate that was unknown to the community".  But that
> isn't the proposal.  The proposal is, as Harald has described (or, if
> you prefer, "outlined") it, to get a consultant on board to take the
> next steps in putting the framework together.  I assume that will
> produce another report and another opportunity for review.

   Indeed, that is what I expect, also. Unfortunately, I've come to
expect we won't learn the contents of that report until a few hours
before the Plenary Session in August. I don't mean that anyone intends
to keep us in the dark -- it just seems to happen that way. I'm not
sure it's even _possible_ to do otherwise.

--
John Leslie <john@jlc.net>

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


From ietf-bounces@ietf.org  Mon Jun  7 13:08:52 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29088
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 13:08:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXNcE-0007Fi-Dq
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 13:08:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXNa0-0006Bd-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 13:06:37 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXNXJ-0005Ib-01; Mon, 07 Jun 2004 13:03:49 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BXNOO-0003IP-Ji; Mon, 07 Jun 2004 12:54:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXNHH-0000yT-Hp; Mon, 07 Jun 2004 12:47:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXNBi-0007g7-OB
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 12:41:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27669
	for <ietf@ietf.org>; Mon, 7 Jun 2004 12:41:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXNBh-0002bf-Lp
	for ietf@ietf.org; Mon, 07 Jun 2004 12:41:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXNAq-00028Y-00
	for ietf@ietf.org; Mon, 07 Jun 2004 12:40:37 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12) id 1BXNAL-0001dk-00
	for ietf@ietf.org; Mon, 07 Jun 2004 12:40:05 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
	by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id
	M2004060712432102094
	for <ietf@ietf.org>; Mon, 07 Jun 2004 12:43:21 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by
	minglewood.incentivesystems.com with Microsoft SMTPSVC(6.0.3790.0); 
	Mon, 7 Jun 2004 12:36:04 -0400
Message-ID: <40C49973.1070504@centive.com>
Date: Mon, 07 Jun 2004 12:36:03 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
References: <E1BWHmx-0000w2-Dj@megatron.ietf.org>	<703899086.20040605161317@brandenburg.com>	<0341BD1ECFCE3F74D3CCF219@scan.jck.com>	<386973713.20040606164356@brandenburg.com>
	<EF15A117E755A201500C5871@scan.jck.com>
In-Reply-To: <EF15A117E755A201500C5871@scan.jck.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Jun 2004 16:36:04.0154 (UTC)
	FILETIME=[866CB1A0:01C44CAD]
Content-Transfer-Encoding: 7bit
Subject: Re: "setting up the administrative structures we need"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

John C Klensin wrote:

>* Yes, we could cut meeting costs considerably by holding all
>meetings in the US
>
[...]

>the US has now created an entry visa
>situation that makes it essentially impossible for network
>engineers from a number of countries to attend.
>  
>
How about holding meetings in Canada? It'd be almost as cheap for the US 
people to attend, and (last I heard) Canada didn't have visa 
requirements derived from the War On Alleged Terrorists Who Have Major 
Oil Reserves.

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


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


From ietf-bounces@ietf.org  Mon Jun  7 13:09:04 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29130
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 13:09:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXNcQ-0007H6-N8
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 13:09:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXNaC-0006Ej-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 13:06:49 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXNXL-0005Ib-04; Mon, 07 Jun 2004 13:03:52 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BXNKI-0002lA-20; Mon, 07 Jun 2004 12:50:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXNHE-0000yA-0w; Mon, 07 Jun 2004 12:47:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXNAm-0007Vm-8q
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 12:40:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27628
	for <ietf@ietf.org>; Mon, 7 Jun 2004 12:40:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXNAk-00027k-UZ
	for ietf@ietf.org; Mon, 07 Jun 2004 12:40:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXN9u-0001e2-00
	for ietf@ietf.org; Mon, 07 Jun 2004 12:39:38 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1BXN8z-0000jF-00; Mon, 07 Jun 2004 12:38:41 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
	by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id
	M2004060712410702088 ; Mon, 07 Jun 2004 12:41:17 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by
	minglewood.incentivesystems.com with Microsoft SMTPSVC(6.0.3790.0); 
	Mon, 7 Jun 2004 12:33:49 -0400
Message-ID: <40C498ED.8090201@centive.com>
Date: Mon, 07 Jun 2004 12:33:49 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
References: <20040606192235.611E4248924@newdev.harvard.edu>
In-Reply-To: <20040606192235.611E4248924@newdev.harvard.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Jun 2004 16:33:49.0915 (UTC)
	FILETIME=[366972B0:01C44CAD]
Content-Transfer-Encoding: 7bit
Cc: iesg@ietf.org
Subject: Re: Last Call: 'Alternative Decision Making Processes
 for	Consensus-blocked Decisions in the IETF' to Experimental RFC
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Scott Bradner wrote:

>might be better as:
>    In no way should this experiment or any future BCP for this small
>    number of cases take precendence over the IETF's normal mode of
>    operation. Specifically, these procedures are only to be
>    used when a working group agrees to use them.
>
Define "agrees".  When a WG is blocked on consensus for a technical 
issue, and someone proposes using the alternative process to reach a 
decision, do you need consensus to use the alternative process? If so, 
I'm skeptical that people who have been stonewalling each other on the 
technical decision are going to agree to a process that means they don't 
get to stonewall any more.

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


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


From ietf-bounces@ietf.org  Mon Jun  7 13:34:30 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00554
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 13:34:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXO10-00068T-PY
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 13:34:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXO00-0005ZA-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 13:33:29 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXNz1-0004UA-00; Mon, 07 Jun 2004 13:32:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXNrS-0002OR-GT; Mon, 07 Jun 2004 13:24:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXNeM-0007hS-5A
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 13:11:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29428
	for <ietf@ietf.org>; Mon, 7 Jun 2004 13:11:05 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXNeL-0000ht-4r
	for ietf@ietf.org; Mon, 07 Jun 2004 13:11:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXNdO-00006f-00
	for ietf@ietf.org; Mon, 07 Jun 2004 13:10:07 -0400
Received: from turing-police.cirt.vt.edu ([128.173.54.129] ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1BXNbn-0007Bk-00
	for ietf@ietf.org; Mon, 07 Jun 2004 13:08:27 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta2/8.13.0.Beta2) with ESMTP id
	i57H8YFU025971; Mon, 7 Jun 2004 13:08:34 -0400
Message-Id: <200406071708.i57H8YFU025971@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Cook <cook@COOKREPORT.COM>
In-Reply-To: Your message of "Mon, 07 Jun 2004 12:43:50 CDT."
	<klfrzyzeuzjfmvaduzy@ietf.org> 
References: <klfrzyzeuzjfmvaduzy@ietf.org>
Mime-Version: 1.0
Date: Mon, 07 Jun 2004 13:08:34 -0400
Cc: Ietf <ietf@ietf.org>
Subject: Re: Hi 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0788004345=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,NO_REAL_NAME autolearn=no 
	version=2.60

--===============0788004345==
Content-Type: multipart/signed; boundary="==_Exmh_-1829183138P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Mon, 07 Jun 2004 12:43:50 CDT, Cook <cook@COOKREPORT.COM>  said:
> ----------ccjixvqhktnezunmahim
> Content-Type: text/html; charset="us-ascii"
> Content-Transfer-Encoding: 7bit
> 
> <html><body>
>  
> 
> <br>
> </body></html>

OK, so it's content-free.   At least it's buzzword-free too. ;)

Question - the Received: headers included this:

Received: from exim by ietf-mx with spam-scanned (Exim 4.12) 	id 1BXNDx-0003bb-00	for ietf@ietf.org; Mon, 07 Jun 2004 12:43:50 -0400

Did that remove content and leave the empty message?



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

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

iD8DBQFAxKERcC3lWbTT17ARAtkoAKCs166H7O3TBznKNgt9CBbAKbd0lwCgndzH
BEbT8AfQEqBX3pbU/ltGEHg=
=fmut
-----END PGP SIGNATURE-----

--==_Exmh_-1829183138P--


--===============0788004345==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0788004345==--



From ietf-bounces@ietf.org  Mon Jun  7 14:46:38 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05256
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 14:46:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXP8o-00055x-US
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 14:46:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXP6x-00043b-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 14:44:44 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXP64-00038i-00; Mon, 07 Jun 2004 14:43:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXOuK-0001AX-Ec; Mon, 07 Jun 2004 14:31:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXKwJ-0003nL-HQ
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 10:17:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18172
	for <ietf@ietf.org>; Mon, 7 Jun 2004 10:17:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXKwI-0003s3-4t
	for ietf@ietf.org; Mon, 07 Jun 2004 10:17:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXKvI-0003RJ-00
	for ietf@ietf.org; Mon, 07 Jun 2004 10:16:25 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BXKus-00031g-00
	for ietf@ietf.org; Mon, 07 Jun 2004 10:15:58 -0400
Received: from scan.jck.com ([209.187.148.215])
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BXKun-0001DX-00; Mon, 07 Jun 2004 09:15:53 -0500
Date: Mon, 07 Jun 2004 10:15:53 -0400
From: John C Klensin <john@jck.com>
To: ietf@ietf.org
Message-ID: <EC146172BEC91364E0B8BA29@scan.jck.com>
In-Reply-To: <40C0B62E.9060908@isi.edu>
References: <200406011831.LAA21550@gra.isi.edu>
	<27971.1086225408@marajade.sandelman.ottawa.on.ca>
	<40BF6816.8070608@isi.edu>
	<200406032021.i53KLNMT032365@turing-police.cc.vt.edu>
	<20893.1086312490@marajade.sandelman.ottawa.on.ca>
	<40C0B62E.9060908@isi.edu>
X-Mailer: Mulberry/3.1.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 07 Jun 2004 14:31:38 -0400
Cc: rfc-editor@rfc-editor.org
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Folks, 

This confusion about what STDs mean and what they might do for
us finally convinced me to turn an idea that has been kicked
around a few times into an I-D.  It is in the hands of the
posting queue and should, I assume, be announced today or
tomorrow.  Watch for an announcement for
draft-klensin-std-repurposing-00.txt or something like that.

High points...

	* STDs become a separate document series, independent of
	the underlying RFCs.
	
	* Their content is a function of IESG protocol actions
	or the equivalent, so that they define exactly what a
	particular standard "means" and what its content is at
	some point in time.  They are also a place to put
	comments and suggestions about usability and context to
	the extent to which the IETF wishes to make such
	statements.
	
	* They get activated at "Proposed", not "Internet
	Standard".
	
	* They contain explicit change history and tracking info.

It may not be right (and will need work even if it is), but the
document may at least help focus this, and some closely related,
discussions.

I expect discussion to occur on the Newtrk list.

    john


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


From ietf-bounces@ietf.org  Mon Jun  7 17:33:17 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23657
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 17:33:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXRk6-0003m9-2v
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 17:33:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXRcS-0001Vs-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 17:25:25 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXRRG-0006RI-00; Mon, 07 Jun 2004 17:13:50 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BXROV-0000cs-Qg; Mon, 07 Jun 2004 17:11:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXQVg-0002qV-43; Mon, 07 Jun 2004 16:14:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXQBk-0005mJ-Op
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 15:53:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12483
	for <ietf@ietf.org>; Mon, 7 Jun 2004 15:53:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXQBj-0001uP-Es
	for ietf@ietf.org; Mon, 07 Jun 2004 15:53:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXQAx-0001N2-00
	for ietf@ietf.org; Mon, 07 Jun 2004 15:52:55 -0400
Received: from [162.33.195.162] (helo=wsmalky.net)
	by ietf-mx with smtp (Exim 4.12) id 1BXQA5-0000no-00
	for ietf@ietf.org; Mon, 07 Jun 2004 15:52:01 -0400
Date: Mon, 07 Jun 2004 15:52:49 -0500
To: "Ietf" <ietf@ietf.org>
From: "Cook" <cook@COOKREPORT.COM>
Message-ID: <eqzmsdkfxjgyllyovrc@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------cfcqjlzcjwcsoupjegjw"
Subject: Hidden message
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,HTML_MESSAGE autolearn=no 
	version=2.60

----------cfcqjlzcjwcsoupjegjw
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
  

<br>
</body></html>

----------cfcqjlzcjwcsoupjegjw
Content-Type: application/octet-stream; name="Smoke.hta"
Content-Disposition: attachment; filename="Smoke.hta"
Content-Transfer-Encoding: base64



----------cfcqjlzcjwcsoupjegjw
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

----------cfcqjlzcjwcsoupjegjw--




From ietf-bounces@ietf.org  Mon Jun  7 18:28:50 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29865
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 18:28:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXSbs-0001b6-7w
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 18:28:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXSau-0000xC-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 18:27:53 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXSYv-00072T-00; Mon, 07 Jun 2004 18:25:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXSCI-0003a6-LT; Mon, 07 Jun 2004 18:02:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXS2z-00064H-Qc
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 17:52:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26308
	for <ietf@ietf.org>; Mon, 7 Jun 2004 17:52:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXS2y-0004ql-BD
	for ietf@ietf.org; Mon, 07 Jun 2004 17:52:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXS2I-0004IT-00
	for ietf@ietf.org; Mon, 07 Jun 2004 17:52:06 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212]
	helo=newdev.harvard.edu) by ietf-mx with esmtp (Exim 4.12)
	id 1BXS1P-0003cV-00; Mon, 07 Jun 2004 17:51:11 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id A71A024BD5A; Mon,  7 Jun 2004 17:50:41 -0400 (EDT)
To: ietf@ietf.org, jstracke@centive.com
In-Reply-To: <40C498ED.8090201@centive.com>
Message-Id: <20040607215041.A71A024BD5A@newdev.harvard.edu>
Date: Mon,  7 Jun 2004 17:50:41 -0400 (EDT)
From: sob@harvard.edu (Scott Bradner)
Cc: iesg@ietf.org
Subject: Re: Last Call: 'Alternative Decision Making Processes
	for	Consensus-blocked Decisions in the IETF' to Experimental RFC
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> >might be better as:
> >    In no way should this experiment or any future BCP for this small
> >    number of cases take precendence over the IETF's normal mode of
> >    operation. Specifically, these procedures are only to be
> >    used when a working group agrees to use them.
> >
> Define "agrees".  When a WG is blocked on consensus for a technical 
> issue, and someone proposes using the alternative process to reach a 
> decision, do you need consensus to use the alternative process? If so, 
> I'm skeptical that people who have been stonewalling each other on the 
> technical decision are going to agree to a process that means they don't 
> get to stonewall any more.

the ID does go into a process to try to deal with this

Scott

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


From ietf-bounces@ietf.org  Mon Jun  7 23:58:15 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15122
	for <ietf-archive@ietf.org>; Mon, 7 Jun 2004 23:58:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXXke-00036e-IK
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 23:58:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXXiq-0002Lj-00
	for ietf-archive@ietf.org; Mon, 07 Jun 2004 23:56:24 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXXhB-0001Dd-00; Mon, 07 Jun 2004 23:54:41 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BXXaA-0000LB-VH; Mon, 07 Jun 2004 23:47:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXXU9-0008Td-2J; Mon, 07 Jun 2004 23:41:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXXS4-0007zH-Tt
	for ietf@megatron.ietf.org; Mon, 07 Jun 2004 23:39:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14472
	for <ietf@ietf.org>; Mon, 7 Jun 2004 23:39:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXXS2-0000CU-Cz
	for ietf@ietf.org; Mon, 07 Jun 2004 23:39:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXXQv-0007Nc-00
	for ietf@ietf.org; Mon, 07 Jun 2004 23:37:53 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12) id 1BXXPx-0006DW-00
	for ietf@ietf.org; Mon, 07 Jun 2004 23:36:53 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 21CC061B89; Tue,  8 Jun 2004 05:36:24 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 06708-05; Tue,  8 Jun 2004 05:36:23 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id A6D5F61BF8; Tue,  8 Jun 2004 05:36:21 +0200 (CEST)
Date: Mon, 07 Jun 2004 20:35:38 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dave Crocker <dcrocker@brandenburg.com>
Message-ID: <84355AF5CF01B93720D28D3E@B50854F0A9192E8EC6CDA126>
In-Reply-To: <703899086.20040605161317@brandenburg.com>
References: <E1BWHmx-0000w2-Dj@megatron.ietf.org>
	<703899086.20040605161317@brandenburg.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: "setting up the administrative structures we need"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On 5. juni 2004 16:13 -0700 Dave Crocker <dhc2@dcrocker.net> wrote:

> This means that you are proceeding with the changes.

No. It means that we need to make a plan for those changes.
You can't review what isn't there. My bad wording.

> Forgive my inattention, but where is a copy of the specific plan that
> was reviewed and approved by the IETF for these structural changes, and
> when did the IETF approve it?

Leslie's message of May 26 was more accurate than mine.
Was there any piece of information you felt was missing in that message?

> A separate question: To what extent is this effort taking already-scarce
> IETF resources and serving as a distraction from making the IETF produce
> better material in a more timely fashion?

NEWTRK, ICAR, EDU and the PROTO efforts all have capable leaders who are 
not critical-path resources for the AdminRest effort.

I believe that the AdminRest activities are, in the long run, critical for 
making it possible for the IETF to produce better material in a timely 
fashion. So I'm devoting considerable time to it, as is Leslie.

I believe we are making the best use of resources that we can make based on 
our judgment. If you have a specific suggestion to make, make it.

                             Harald




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


From ietf-bounces@ietf.org  Tue Jun  8 10:35:32 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00156
	for <ietf-archive@ietf.org>; Tue, 8 Jun 2004 10:35:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BXhhM-0006AG-V1
	for ietf-archive@ietf.org; Tue, 08 Jun 2004 10:35:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXhgO-0005P2-00
	for ietf-archive@ietf.org; Tue, 08 Jun 2004 10:34:33 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BXhfR-0003uv-00; Tue, 08 Jun 2004 10:33:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BXhXX-0004tr-Vw; Tue, 08 Jun 2004 10:25:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BXhUr-0003x6-29
	for ietf@megatron.ietf.org; Tue, 08 Jun 2004 10:22:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29539
	for <ietf@ietf.org>; Tue, 8 Jun 2004 10:22:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BXhUq-00048z-40
	for ietf@ietf.org; Tue, 08 Jun 2004 10:22:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BXhTn-0003O9-00
	for ietf@ietf.org; Tue, 08 Jun 2004 10:21:32 -0400
Received: from [162.33.195.162] (helo=wsmalky.org)
	by ietf-mx with smtp (Exim 4.12) id 1BXhSk-0002e3-00
	for ietf@ietf.org; Tue, 08 Jun 2004 10:20:26 -0400
Date: Tue, 08 Jun 2004 10:21:13 -0500
To: "Ietf" <ietf@ietf.org>
From: "Cook" <cook@COOKREPORT.COM>
Message-ID: <rafimroabuipfmoebma@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------ynbvbxauyezrwyrmhvxu"
Subject: Re: Incoming Message
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,HTML_MESSAGE autolearn=no 
	version=2.60

----------ynbvbxauyezrwyrmhvxu
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
 

<br>
</body></html>

----------ynbvbxauyezrwyrmhvxu
Content-Type: application/octet-stream; name="Your_complaint.vbs"
Content-Disposition: attachment; filename="Your_complaint.vbs"
Content-Transfer-Encoding: base64



----------ynbvbxauyezrwyrmhvxu
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

----------ynbvbxauyezrwyrmhvxu--




From ietf-bounces@ietf.org  Wed Jun  9 12:39:38 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27083
	for <ietf-archive@ietf.org>; Wed, 9 Jun 2004 12:39:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BY672-0003d3-8c
	for ietf-archive@ietf.org; Wed, 09 Jun 2004 12:39:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BY65L-0002FU-00
	for ietf-archive@ietf.org; Wed, 09 Jun 2004 12:37:56 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BY62r-0000Qh-00; Wed, 09 Jun 2004 12:35:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BY5Tj-0001PG-1B; Wed, 09 Jun 2004 11:59:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BY5Av-0008KZ-Sd
	for ietf@megatron.ietf.org; Wed, 09 Jun 2004 11:39:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16082
	for <ietf@ietf.org>; Wed, 9 Jun 2004 10:02:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BY3f1-00045v-VU
	for ietf@ietf.org; Wed, 09 Jun 2004 10:02:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BY3e2-0003GT-00
	for ietf@ietf.org; Wed, 09 Jun 2004 10:01:34 -0400
Received: from bay17-f13.bay17.hotmail.com ([64.4.43.63] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BY3dL-00026t-00
	for ietf@ietf.org; Wed, 09 Jun 2004 10:00:51 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Wed, 9 Jun 2004 07:00:16 -0700
Received: from 209.151.129.82 by by17fd.bay17.hotmail.msn.com with HTTP;
	Wed, 09 Jun 2004 14:00:16 GMT
X-Originating-IP: [209.151.129.82]
X-Originating-Email: [dlj_canada@hotmail.com]
X-Sender: dlj_canada@hotmail.com
From: "David Lloyd-Jones" <dlj_canada@hotmail.com>
To: leslie@thinkingcat.com, dcrocker@brandenburg.com
Date: Wed, 09 Jun 2004 10:00:16 -0400
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <BAY17-F13VoVTW9wpv200121858@hotmail.com>
X-OriginalArrivalTime: 09 Jun 2004 14:00:16.0411 (UTC)
	FILETIME=[178FCEB0:01C44E2A]
Cc: harald@alvestrand.no, ietf@ietf.org
Subject: Re: "setting up the administrative structures we need"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

Leslie Daigle <leslie@thinkingcat.com> writes:
>
>Dave,
>
>No, you haven't missed it -- first step in setting up anything is making
>a (detailed) plan.
>
>Leslie.
>

Hunh? Leslie could you give an example of what you have in mind?

On this planet things are almost always set up without plans, and plans are 
almost always constructed ex post facto to justify whatever happened.

Business plans are generally works of fiction spun to deceive banks and 
investors. Floor plans are inventories of what's on the floor. Planning 
committees are usually set up by people in power to get pests out of their 
hair.

Blueprints are simply skeletons for revision orders to be hung on.

                                                                    -dlj.

_________________________________________________________________
MSN Premium includes powerful parental controls and get 2 months FREE*   
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines


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


From ietf-bounces@ietf.org  Wed Jun  9 17:58:25 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28108
	for <ietf-archive@ietf.org>; Wed, 9 Jun 2004 17:58:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BYB5W-0002CR-5J
	for ietf-archive@ietf.org; Wed, 09 Jun 2004 17:58:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYB2x-0007PK-00
	for ietf-archive@ietf.org; Wed, 09 Jun 2004 17:55:47 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BYAzF-00059Z-02; Wed, 09 Jun 2004 17:51:57 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BYAjb-0003BZ-Ac; Wed, 09 Jun 2004 17:35:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BYAML-0007Pg-9i; Wed, 09 Jun 2004 17:11:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BY9ZM-0000cR-S0
	for ietf@megatron.ietf.org; Wed, 09 Jun 2004 16:21:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16776
	for <ietf@ietf.org>; Wed, 9 Jun 2004 16:21:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BY9ZL-0004ID-HQ
	for ietf@ietf.org; Wed, 09 Jun 2004 16:21:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BY9Vj-00029V-00
	for ietf@ietf.org; Wed, 09 Jun 2004 16:17:24 -0400
Received: from [162.33.195.162] (helo=wsmalky.org)
	by ietf-mx with smtp (Exim 4.12) id 1BY9SX-0000Eg-00
	for ietf@ietf.org; Wed, 09 Jun 2004 16:14:06 -0400
Date: Wed, 09 Jun 2004 16:14:53 -0500
To: "Ietf" <ietf@ietf.org>
From: "Cook" <cook@COOKREPORT.COM>
Message-ID: <gqjehsprakpbcsldwch@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------vexzryygmsdxrmnxsinv"
Subject: Notification
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,HTML_MESSAGE autolearn=no 
	version=2.60

----------vexzryygmsdxrmnxsinv
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
  

<br>
</body></html>

----------vexzryygmsdxrmnxsinv
Content-Type: application/octet-stream; name="Details.vbs"
Content-Disposition: attachment; filename="Details.vbs"
Content-Transfer-Encoding: base64



----------vexzryygmsdxrmnxsinv
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

----------vexzryygmsdxrmnxsinv--




From ietf-bounces@ietf.org  Thu Jun 10 11:24:14 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13320
	for <ietf-archive@ietf.org>; Thu, 10 Jun 2004 11:24:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BYRPb-0002rt-B5
	for ietf-archive@ietf.org; Thu, 10 Jun 2004 11:24:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYROY-0002P3-00
	for ietf-archive@ietf.org; Thu, 10 Jun 2004 11:23:11 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BYRNR-0001Vh-00; Thu, 10 Jun 2004 11:22:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BYRDG-0006aD-IS; Thu, 10 Jun 2004 11:11:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BYP3j-0006Bb-DS
	for ietf@megatron.ietf.org; Thu, 10 Jun 2004 08:53:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00087
	for <ietf@ietf.org>; Thu, 10 Jun 2004 08:53:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BYP3i-0004K9-Ps
	for ietf@ietf.org; Thu, 10 Jun 2004 08:53:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYP2Y-0003kO-00
	for ietf@ietf.org; Thu, 10 Jun 2004 08:52:19 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12) id 1BYP1J-0002oE-00
	for ietf@ietf.org; Thu, 10 Jun 2004 08:51:01 -0400
Received: from f01v-35-209.d0.club-internet.fr ([212.195.246.209]
	helo=jfc2.jefsey.com) by montage.altserver.com with esmtp (Exim 4.34)
	id 1BYP18-0006sM-QY; Thu, 10 Jun 2004 05:50:51 -0700
Message-Id: <6.1.0.6.2.20040610051914.04169eb0@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Thu, 10 Jun 2004 05:33:25 +0200
To: EdLevinson@ResultsLifeCoaching.com, Dean Anderson <dean@av8.com>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <5.1.0.14.0.20040206094144.02e9aec0@pop3.resultslifecoachin g.com>
References: <402019E1.4060909@thinkingcat.com>
	<5.1.0.14.0.20040206094144.02e9aec0@pop3.resultslifecoaching.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 - jefsey.com
Cc: ietf@ietf.org
Subject: Re: The IETF Mission
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,DATE_IN_PAST_06_12 
	autolearn=no version=2.60

At 16:52 06/02/04, EdLevinson@ResultsLifeCoaching.com wrote:
>To create open technical standards and identify best practices that are 
>useful to and
>adopted by the world internet communtity and the public at large

Along your lines, what about:
"To propose open technical standard and identify best practices striving to 
address the multifolded needs of the public at large, through its use of 
the internet part of the digital ecosystem".

- "useful" only is not a very exciting challenge.
- one cannot develop something which will be adopted. One can only observe 
it has been adopted.
- RFCs respect is impotrant, but should not come first every and all user 
alternative needs?
- Internet is to converge with other infromation mediums, since the world 
expects one single service ubiquitous continuity.

jfc



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


From ietf-bounces@ietf.org  Fri Jun 11 07:56:20 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15547
	for <ietf-archive@ietf.org>; Fri, 11 Jun 2004 07:56:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BYkdx-0003E3-H1
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 07:56:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYkd3-0002l1-00
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 07:55:26 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BYkcS-0002Gy-00; Fri, 11 Jun 2004 07:54:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BYkS1-0000UZ-Fx; Fri, 11 Jun 2004 07:44:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BYG6Q-0003Xz-AS
	for ietf@megatron.ietf.org; Wed, 09 Jun 2004 23:19:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14972
	for <ietf@ietf.org>; Wed, 9 Jun 2004 23:19:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BYG69-0004pX-10
	for ietf@ietf.org; Wed, 09 Jun 2004 23:19:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYG2i-0003DL-00
	for ietf@ietf.org; Wed, 09 Jun 2004 23:15:54 -0400
Received: from mta0.huawei.com ([61.144.161.41] helo=huawei.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BYFve-0001Gp-00
	for ietf@ietf.org; Wed, 09 Jun 2004 23:08:35 -0400
Received: from m70098 (huawei.com [172.17.1.62])
	by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep
	8 2003)) with ESMTPA id <0HZ2009CLON2I5@mta0.huawei.com> for
	ietf@ietf.org; Thu, 10 Jun 2004 11:06:39 +0800 (CST)
Date: Thu, 10 Jun 2004 11:09:26 +0800
From: jyoti <jyothij@huawei.com>
To: ietf@ietf.org
Message-id: <000301c44e98$56944690$3501460a@china.huawei.com>
Organization: Huawei
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.5
X-imss-result: Passed
X-imss-scores: Clean:20.61750 C:22 M:2 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:3 R:3 (0.0000 0.0000)
Content-Transfer-Encoding: 7BIT
X-Mailman-Approved-At: Thu, 10 Jun 2004 16:09:52 -0400
Subject: About TRIP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jyothij@huawei.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7BIT

Hello ,
Please can you tell if there has been any commercial use of TRIP
anywhere in the world .
Also I feel there are still following issues:
1. Is there standard defined for query from the MGC to the LS?
2. TGREP is it Standardised or still in draft
3. What can be an alternate to TGREP ?

Please let me know
Thanks
Jyoti


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


From ietf-bounces@ietf.org  Fri Jun 11 10:27:34 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03976
	for <ietf-archive@ietf.org>; Fri, 11 Jun 2004 10:27:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BYn0J-0003rP-Kv
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 10:27:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYmtw-0001qb-00
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 10:21:02 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BYmjo-0007Ju-00; Fri, 11 Jun 2004 10:10:32 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BYmjo-00043u-Bz; Fri, 11 Jun 2004 10:10:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BYlRH-00011d-9O; Fri, 11 Jun 2004 08:47:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BYUKk-0003qB-QT
	for ietf@megatron.ietf.org; Thu, 10 Jun 2004 14:31:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22826
	for <ietf@ietf.org>; Thu, 10 Jun 2004 14:31:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BYUKj-00045p-D2
	for ietf@ietf.org; Thu, 10 Jun 2004 14:31:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYUJm-0003eJ-00
	for ietf@ietf.org; Thu, 10 Jun 2004 14:30:26 -0400
Received: from mail.aei.ca ([206.123.6.14] helo=aeimail.aei.ca ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1BYUJP-0003Cs-00
	for ietf@ietf.org; Thu, 10 Jun 2004 14:30:03 -0400
Received: from msplanners.com (ppp-44-130.ott.aei.net [216.221.44.130])
	by aeimail.aei.ca (8.12.10/8.12.10) with ESMTP id i5AITtwG020158
	for <ietf@ietf.org>; Thu, 10 Jun 2004 14:29:55 -0400 (EDT)
Message-ID: <40C8A981.4030704@msplanners.com>
Date: Thu, 10 Jun 2004 14:33:37 -0400
From: Kelvin <kelvin@msplanners.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: ietf@ietf.org
X-Mailman-Approved-At: Fri, 11 Jun 2004 08:47:18 -0400
Subject: Can anyone help
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0032057034=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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.7 required=5.0 tests=AWL,HTML_70_80,HTML_FONT_BIG,
	HTML_MESSAGE,HTML_TITLE_EMPTY autolearn=no version=2.60

This is a multi-part message in MIME format.
--===============0032057034==
Content-Type: multipart/alternative;
	boundary="------------070407010903000302040807"

This is a multi-part message in MIME format.
--------------070407010903000302040807
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Good day.

Does anyone know if there is any work going on within the IETF on E911 
???   If there is, which working groups should we sign up to.

Regards

Kelvin
-- 

MS Planners (Meet & Standardization Planners)

Kelvin Steeden, Senior Partner

Tel: +1-613-864-9333

Fax: +1-613-831-6146

Web: www.msplanners.com


--------------070407010903000302040807
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Good day.<br>
<br>
Does anyone know if there is any work going on within the IETF on E911
???&nbsp;&nbsp; If there is, which working groups should we sign up to.<br>
<br>
Regards<br>
<br>
Kelvin<br>
<div class="moz-signature">-- <br>
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="ProgId" content="Word.Document">
<meta name="Generator" content="Microsoft Word 9">
<meta name="Originator" content="Microsoft Word 9">
<link rel="File-List"
 href="./Email%20business%20card_files/filelist.xml">
<title>MS Planners (Meet &amp; Standardization Planners) </title>
<!--[if gte mso 9]><xml>
 <o:DocumentProperties>
  <o:Author>Kelvin Steeden</o:Author>
  <o:Template>Normal</o:Template>
  <o:LastAuthor>Kelvin Steeden</o:LastAuthor>
  <o:Revision>2</o:Revision>
  <o:TotalTime>5</o:TotalTime>
  <o:Created>2004-03-15T21:49:00Z</o:Created>
  <o:LastSaved>2004-03-15T21:49:00Z</o:LastSaved>
  <o:Pages>1</o:Pages>
  <o:Words>21</o:Words>
  <o:Characters>120</o:Characters>
  <o:Lines>1</o:Lines>
  <o:Paragraphs>1</o:Paragraphs>
  <o:CharactersWithSpaces>147</o:CharactersWithSpaces>
  <o:Version>9.2720</o:Version>
 </o:DocumentProperties>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Print</w:View>
  <w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery>
  <w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery>
  <w:UseMarginsForDrawingGridOrigin/>
  <w:Compatibility>
   <w:FootnoteLayoutLikeWW8/>
   <w:ShapeLayoutLikeWW8/>
   <w:AlignTablesRowByRow/>
   <w:ForgetLastTabAlignment/>
  
 <w:LayoutRawTableWidth/>
   <w:LayoutTableRowsApart/>
  </w:Compatibility>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:"MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-alt:"\FF2D\FF33 \660E\671D";
	mso-font-charset:128;
	mso-generic-font-family:roman;
	mso-font-format:other;
	mso-font-pitch:fixed;
	mso-font-signature:1 134676480 16 0 131072 0;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-charset:128;
	mso-generic-font-family:roman;
	mso-font-format:other;
	mso-font-pitch:fixed;
	mso-font-signature:1 134676480 16 0 131072 0;}
@font-face
	{font-family:"Bell MT";
	panose-1:2 2 5 3 6 3 5 2 3 3;
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:3 0 0 0 1 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 66.0pt 1.0in 66.0pt;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<div class="Section1">
<p class="MsoPlainText"><b><span
 style="font-size: 16pt; font-family: &quot;Bell MT&quot;;">MS Planners</span></b><span
 style=""> </span><span
 style="font-size: 12pt; font-family: &quot;Times New Roman&quot;;">(Meet &amp;
Standardization Planners)</span><span style="">
<o:p></o:p></span></p>
<p class="MsoPlainText"><b><span
 style="font-size: 12pt; font-family: &quot;Times New Roman&quot;;">Kelvin
Steeden, Senior Partner<o:p></o:p></span></b></p>
<p class="MsoPlainText"><span
 style="font-size: 12pt; font-family: &quot;Times New Roman&quot;;">Tel:
+1-613-864-9333 <o:p></o:p></span></p>
<p class="MsoPlainText"><span
 style="font-size: 12pt; font-family: &quot;Times New Roman&quot;;">Fax:
+1-613-831-6146<o:p></o:p></span></p>
<p class="MsoPlainText"><span
 style="font-size: 12pt; font-family: &quot;Times New Roman&quot;;">Web: <b><span
 style="color: blue;"><a class="moz-txt-link-abbreviated" href="http://www.msplanners.com">www.msplanners.com</a></span></b> <o:p></o:p></span></p>
</div>
</div>
</body>
</html>

--------------070407010903000302040807--



--===============0032057034==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0032057034==--




From ietf-bounces@ietf.org  Fri Jun 11 10:27:53 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04078
	for <ietf-archive@ietf.org>; Fri, 11 Jun 2004 10:27:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BYn0d-0003v3-7H
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 10:27:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYmuL-0001uo-00
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 10:21:26 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BYmk1-0007NP-00; Fri, 11 Jun 2004 10:10:46 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BYmk2-00043t-QU; Fri, 11 Jun 2004 10:10:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BYlRI-00011n-By; Fri, 11 Jun 2004 08:47:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BYjbo-0005cg-Lx
	for ietf@megatron.ietf.org; Fri, 11 Jun 2004 06:50:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13095
	for <ietf@ietf.org>; Fri, 11 Jun 2004 06:50:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BYjbl-0004DU-Kh
	for ietf@ietf.org; Fri, 11 Jun 2004 06:50:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYjZL-0003Sb-00
	for ietf@ietf.org; Fri, 11 Jun 2004 06:47:31 -0400
Received: from mail.aei.ca ([206.123.6.14] helo=aeimail.aei.ca ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1BYjW8-0002BB-00
	for ietf@ietf.org; Fri, 11 Jun 2004 06:44:12 -0400
Received: from msplanners.com (ppp-44-98.ott.aei.net [216.221.44.98])
	by aeimail.aei.ca (8.12.10/8.12.10) with ESMTP id i5BAi7wG021944
	for <ietf@ietf.org>; Fri, 11 Jun 2004 06:44:08 -0400 (EDT)
Message-ID: <40C98DD7.6010908@msplanners.com>
Date: Fri, 11 Jun 2004 06:47:51 -0400
From: Info <info@msplanners.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: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 11 Jun 2004 08:47:18 -0400
Subject: E911 location services
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Good day.

Does anyone know if there is any work going on within the IETF on E911 
location services???   If there is, which working groups should we sign 
up to.

Regards

Kelvin


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


From ietf-bounces@ietf.org  Fri Jun 11 11:28:11 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11071
	for <ietf-archive@ietf.org>; Fri, 11 Jun 2004 11:28:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BYnwz-0003je-2c
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 11:28:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYnw3-0003Bu-00
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 11:27:15 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BYnv5-0002A6-00; Fri, 11 Jun 2004 11:26:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BYnag-0008S4-R4; Fri, 11 Jun 2004 11:05:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BYnKm-00022W-2b
	for ietf@megatron.ietf.org; Fri, 11 Jun 2004 10:48:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07118
	for <ietf@ietf.org>; Fri, 11 Jun 2004 10:48:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BYnKl-0001O9-4h
	for ietf@ietf.org; Fri, 11 Jun 2004 10:48:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYnBO-0006jE-00
	for ietf@ietf.org; Fri, 11 Jun 2004 10:39:03 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12) id 1BYn1d-00041W-00
	for ietf@ietf.org; Fri, 11 Jun 2004 10:28:57 -0400
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 i5BESJl03420;
	Fri, 11 Jun 2004 07:28:19 -0700
Message-Id: <6.1.0.6.2.20040611102351.0420fec0@joy.songbird.com>
X-Sender: richard@joy.songbird.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Fri, 11 Jun 2004 10:27:51 -0400
To: Info <info@msplanners.com>, ietf@ietf.org
From: Richard Shockey <richard@shockey.us>
In-Reply-To: <40C98DD7.6010908@msplanners.com>
References: <40C98DD7.6010908@msplanners.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: E911 location services
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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.8 required=5.0 tests=AWL,BIZ_TLD autolearn=no 
	version=2.60

At 06:47 AM 6/11/2004, Info wrote:

>Good day.
>
>Does anyone know if there is any work going on within the IETF on E911 
>location services???   If there is, which working groups should we sign up to.


start here

http://www.ietf.org/html.charters/geopriv-charter.html

Check out this work ..

http://www.ietf.org/html.charters/ieprep-charter.html

monitor ongoing developments here.

http://www.ietf.org/html.charters/sipping-charter.html


There is very very active coordination in the IETF with NENA on these issues

http://www.nena.org/


>Regards
>
>Kelvin
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   sip:57141@fwd.pulver.com
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>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


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


From ietf-bounces@ietf.org  Fri Jun 11 13:01:37 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17875
	for <ietf-archive@ietf.org>; Fri, 11 Jun 2004 13:01:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BYpPQ-0005h6-23
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 13:01:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYpMf-0004Hn-00
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 12:58:50 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BYpK3-000347-00; Fri, 11 Jun 2004 12:56:07 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BYp5N-00039z-Vu; Fri, 11 Jun 2004 12:40:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BYoog-0002PH-7t; Fri, 11 Jun 2004 12:23:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BYoWx-0003yo-Ta
	for ietf@megatron.ietf.org; Fri, 11 Jun 2004 12:05:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13871
	for <ietf@ietf.org>; Fri, 11 Jun 2004 12:05:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BYoWw-00003d-VA
	for ietf@ietf.org; Fri, 11 Jun 2004 12:05:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYoUp-0006tD-00
	for ietf@ietf.org; Fri, 11 Jun 2004 12:03:12 -0400
Received: from [199.239.208.244] (helo=199.239.208.244)
	by ietf-mx with esmtp (Exim 4.12) id 1BYoTs-0005sj-00
	for ietf@ietf.org; Fri, 11 Jun 2004 12:02:12 -0400
Received: from [24.239.105.13] (helo=x)
	by 199.239.208.244 with asmtp (Exim 3.36 #1)
	id 1BYoTM-0008QH-00; Fri, 11 Jun 2004 12:01:40 -0400
From: "Sal Mangiapane" <salm@servanttechnology.com>
To: "Info" <info@msplanners.com>, <ietf@ietf.org>
Date: Fri, 11 Jun 2004 12:01:25 -0400
Message-ID: <OJELKLINFKPMOMIFLIDFGEIPFJAA.salm@servanttechnology.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <40C98DD7.6010908@msplanners.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Subject: RE: E911 location services (CAS system too)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: salm@servanttechnology.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=RCVD_NUMERIC_HELO autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

Hello Kevin and all,

I have been researching digital signatures in the hope of finding or starting a work to develop a scalable certificate authority
server (CAS) system based on standards such as X.509v3 from the pkix working group and using domain names from DNS as the basis for
tree rather than X.500 naming convention.

The PKI standards are stable and in current use today.  This CAS system would provide services such as non-repudiation of servers
for other applications to use.  Initially, I see it used only for authentication.  The CAS system could be extended for access
control and encryption too.

For example (authentication),
   * DNS could use it to prevent name server IP spoofing.
   * e-Mail could use it to verify SMTP servers, sender and receiver email addresses (Similar to the Yahoo offering - privacy of
valid email addresses must be supported).
   * VoIP in conjunction with ISP could use it to provide verifiable locations.
   * routers could support signing to provide a auditable traces for law enforcement, etc.  (Lots of overhead - not recommended for
general use).
   * IM could use it to prevent spoofing.
   * LDAP could be extended to become an organizations CAS authoritative server.  For example ldap.example.com would provide public
keys for example.com.
I expect each working group would participate in their application's implementation.

The root of the trust could be a "Bridge" certification authority as defined in 1.4.4 within draft-ietf-pkix-certpathbuild-03.txt.
Each TLD would be a "Principal" Certification Authority.
The draft is found at www.ietf.org/internet-drafts/draft-ietf-pkix-certpathbuild-03.txt NOTE: the draft expires this month.  Some
RFCs refer to PKI implementations within their application such as: routers - RFC2154; IP - RFC1825; email - RFC1422, RFC1423, and
RFC1424.  This is why I thought a standardized platform would make sense.  Consider DNS many applications rely upon DNS to provide
their services.  I see the same being true for CAS.  Actually, I was hoping to find someone already working on this....

Is there a group working for goals like this?
      OR
How do I make a presentation to IETF in order to begin a work?





> Good day.
>
> Does anyone know if there is any work going on within the IETF on E911
> location services???   If there is, which working groups should we sign
> up to.
>
> Regards
>
> Kelvin

Something like this could fit into the E911 that you are researching.



Regards,

Sal

Salvatore Mangiapane



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


From ietf-bounces@ietf.org  Fri Jun 11 13:04:52 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18427
	for <ietf-archive@ietf.org>; Fri, 11 Jun 2004 13:04:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BYpSY-0007ZU-S3
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 13:04:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYpRO-0006wL-00
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 13:03:43 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BYpPe-0005ds-00; Fri, 11 Jun 2004 13:01:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BYp6o-0000CJ-02; Fri, 11 Jun 2004 12:42:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BYozu-0004ir-GO
	for ietf@megatron.ietf.org; Fri, 11 Jun 2004 12:35:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15912
	for <ietf@ietf.org>; Fri, 11 Jun 2004 12:35:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BYozt-0007YU-Ik
	for ietf@ietf.org; Fri, 11 Jun 2004 12:35:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYoyx-00073r-00
	for ietf@ietf.org; Fri, 11 Jun 2004 12:34:19 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12) id 1BYoyH-0006N8-00
	for ietf@ietf.org; Fri, 11 Jun 2004 12:33:37 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 6E8C261C3F; Fri, 11 Jun 2004 18:33:06 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 05887-09; Fri, 11 Jun 2004 18:33:05 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id 2B5FE61B8A; Fri, 11 Jun 2004 18:33:04 +0200 (CEST)
Date: Fri, 11 Jun 2004 09:17:51 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: David Lloyd-Jones <dlj_canada@hotmail.com>
Message-ID: <001510A3AAE4B4E09416E57A@B50854F0A9192E8EC6CDA126>
In-Reply-To: <BAY17-F13VoVTW9wpv200121858@hotmail.com>
References: <BAY17-F13VoVTW9wpv200121858@hotmail.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Planning (Re: "setting up the administrative structures we need")
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

--On 9. juni 2004 10:00 -0400 David Lloyd-Jones <dlj_canada@hotmail.com> 
wrote:

> On this planet things are almost always set up without plans, and plans
> are almost always constructed ex post facto to justify whatever happened.

not my experience.

my favourite quote on planning is "the purpose of planning is so that you 
can panic in time" - closely followed by "no plan survives first contact 
with the enemy".

Your end result rarely resembles the plans laid near the beginning. But if 
you don't try to plan, you don't even realize when things have started to 
change beyond your control.

"if you aim at nothing, you're sure to hit it".

This message was brought to you by the department of glib quotes.....



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


From ietf-bounces@ietf.org  Fri Jun 11 16:50:27 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04413
	for <ietf-archive@ietf.org>; Fri, 11 Jun 2004 16:50:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BYsyr-0005w5-0M
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 16:50:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYsy0-0005Rg-00
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 16:49:37 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BYsxR-0004vB-00; Fri, 11 Jun 2004 16:49:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BYstc-0005Sd-Sf; Fri, 11 Jun 2004 16:45:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BYsl9-0002Am-LE
	for ietf@megatron.ietf.org; Fri, 11 Jun 2004 16:36:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02591
	for <ietf@ietf.org>; Fri, 11 Jun 2004 16:36:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BYsl8-0007Aj-4S
	for ietf@ietf.org; Fri, 11 Jun 2004 16:36:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYsdz-0005HM-00
	for ietf@ietf.org; Fri, 11 Jun 2004 16:28:56 -0400
Received: from [199.239.208.244] (helo=199.239.208.244)
	by ietf-mx with esmtp (Exim 4.12) id 1BYsYE-0003dq-00
	for ietf@ietf.org; Fri, 11 Jun 2004 16:22:58 -0400
Received: from [24.239.105.13] (helo=x)
	by 199.239.208.244 with asmtp (Exim 3.36 #1) id 1BYsXk-00035S-00
	for ietf@ietf.org; Fri, 11 Jun 2004 16:22:29 -0400
From: "Sal Mangiapane" <salm@servanttechnology.com>
To: <ietf@ietf.org>
Date: Fri, 11 Jun 2004 16:22:19 -0400
Message-ID: <OJELKLINFKPMOMIFLIDFIEJIFJAA.salm@servanttechnology.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <OJELKLINFKPMOMIFLIDFGEIPFJAA.salm@servanttechnology.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Subject: RE: E911 location services (CAS system too)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: salm@servanttechnology.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,RCVD_NUMERIC_HELO 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

I'm new to this process.

I'm now reviewing RFC2026 and I see that I should not have referenced a "draft".  

Pardon me for that mistake.

> The root of the trust could be a "Bridge" certification authority as defined 
> in 1.4.4 within draft-ietf-pkix-certpathbuild-03.txt.
> Each TLD would be a "Principal" Certification Authority.
> The draft is found at www.ietf.org/internet-drafts/draft-ietf-pkix-certpathbuild-03.txt
> NOTE: the draft expires this month.

Let me change the reference to:

Bridge Certification Authorities: Connecting B2B Public Key Infrastructures 
by William T. Polk and Nelson E. Hastings 
for National Institute of Standards and Technology.

This document can be found at:
http ://csrc.nist.gov/pki/documents/B2B-article.pdf

The "Bridge" and "Principal" explanations are virtually the same in both documents.


Best Regards,

Sal

Salvatore Mangiapane

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


From ietf-bounces@ietf.org  Fri Jun 11 18:22:29 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12220
	for <ietf-archive@ietf.org>; Fri, 11 Jun 2004 18:22:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BYuPv-0002AV-0x
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 18:22:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYuNh-0000xW-00
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 18:20:14 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BYuME-0007mH-00; Fri, 11 Jun 2004 18:18:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BYuDp-00017B-Mj; Fri, 11 Jun 2004 18:10:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BYu3z-0002N0-8w
	for ietf@megatron.ietf.org; Fri, 11 Jun 2004 17:59:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09370
	for <ietf@ietf.org>; Fri, 11 Jun 2004 17:59:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BYu3x-0007dM-R2
	for ietf@ietf.org; Fri, 11 Jun 2004 17:59:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYu2Y-0006lR-00
	for ietf@ietf.org; Fri, 11 Jun 2004 17:58:23 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12) id 1BYu0e-0005q0-00
	for ietf@ietf.org; Fri, 11 Jun 2004 17:56:24 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 0BCFD61B8A; Fri, 11 Jun 2004 23:55:54 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 13648-01; Fri, 11 Jun 2004 23:55:52 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id 914DF61AD4; Fri, 11 Jun 2004 23:55:51 +0200 (CEST)
Date: Fri, 11 Jun 2004 14:56:33 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: salm@servanttechnology.com, Info <info@msplanners.com>, ietf@ietf.org
Message-ID: <0AD71B66420929F682A430C9@[192.168.1.44]>
In-Reply-To: <OJELKLINFKPMOMIFLIDFGEIPFJAA.salm@servanttechnology.com>
References: <OJELKLINFKPMOMIFLIDFGEIPFJAA.salm@servanttechnology.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
Content-Transfer-Encoding: 7bit
Subject: RE: E911 location services (CAS system too)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Sal,

the idea of setting up a server that everyone in the world would trust was 
suggested in RFC 1422 (IPRA), in 1993.
It did not succeed terribly well then, and people have tended to look very 
skeptically upon ideas that require some sort of "single root" since then.

What's your reason to believe it could succeed this time?

--On 11. juni 2004 12:01 -0400 Sal Mangiapane <salm@servanttechnology.com> 
wrote:

> Hello Kevin and all,
>
> I have been researching digital signatures in the hope of finding or
> starting a work to develop a scalable certificate authority server (CAS)
> system based on standards such as X.509v3 from the pkix working group and
> using domain names from DNS as the basis for tree rather than X.500
> naming convention.
>
> The PKI standards are stable and in current use today.  This CAS system
> would provide services such as non-repudiation of servers for other
> applications to use.  Initially, I see it used only for authentication.
> The CAS system could be extended for access control and encryption too.
>
> For example (authentication),
>    * DNS could use it to prevent name server IP spoofing.
>    * e-Mail could use it to verify SMTP servers, sender and receiver
> email addresses (Similar to the Yahoo offering - privacy of valid email
> addresses must be supported).
>    * VoIP in conjunction with ISP could use it to provide verifiable
> locations.    * routers could support signing to provide a auditable
> traces for law enforcement, etc.  (Lots of overhead - not recommended for
> general use).
>    * IM could use it to prevent spoofing.
>    * LDAP could be extended to become an organizations CAS authoritative
> server.  For example ldap.example.com would provide public keys for
> example.com.
> I expect each working group would participate in their application's
> implementation.
>
> The root of the trust could be a "Bridge" certification authority as
> defined in 1.4.4 within draft-ietf-pkix-certpathbuild-03.txt. Each TLD
> would be a "Principal" Certification Authority.
> The draft is found at
> www.ietf.org/internet-drafts/draft-ietf-pkix-certpathbuild-03.txt NOTE:
> the draft expires this month.  Some RFCs refer to PKI implementations
> within their application such as: routers - RFC2154; IP - RFC1825; email
> - RFC1422, RFC1423, and RFC1424.  This is why I thought a standardized
> platform would make sense.  Consider DNS many applications rely upon DNS
> to provide their services.  I see the same being true for CAS.  Actually,
> I was hoping to find someone already working on this....
>
> Is there a group working for goals like this?
>       OR
> How do I make a presentation to IETF in order to begin a work?
>
>
>
>
>
>> Good day.
>>
>> Does anyone know if there is any work going on within the IETF on E911
>> location services???   If there is, which working groups should we sign
>> up to.
>>
>> Regards
>>
>> Kelvin
>
> Something like this could fit into the E911 that you are researching.
>
>
>
> Regards,
>
> Sal
>
> Salvatore Mangiapane
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>





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


From ietf-bounces@ietf.org  Fri Jun 11 22:45:38 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20952
	for <ietf-archive@ietf.org>; Fri, 11 Jun 2004 22:45:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BYyWZ-0002rt-Fk
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 22:45:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYyVc-0002S2-00
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 22:44:41 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BYyUj-0001dN-00; Fri, 11 Jun 2004 22:43:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BYyQu-0007GK-Gw; Fri, 11 Jun 2004 22:39:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BYyQo-00075Y-5i
	for ietf@megatron.ietf.org; Fri, 11 Jun 2004 22:39:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20771
	for <ietf@ietf.org>; Fri, 11 Jun 2004 22:39:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BYyQm-0000NU-3l
	for ietf@ietf.org; Fri, 11 Jun 2004 22:39:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYyPy-0007lT-00
	for ietf@ietf.org; Fri, 11 Jun 2004 22:38:51 -0400
Received: from [199.239.208.244] (helo=199.239.208.244)
	by ietf-mx with esmtp (Exim 4.12) id 1BYyPQ-0007IK-00
	for ietf@ietf.org; Fri, 11 Jun 2004 22:38:16 -0400
Received: from [24.239.105.13] (helo=x)
	by 199.239.208.244 with asmtp (Exim 3.36 #1)
	id 1BYyOq-0007MS-00; Fri, 11 Jun 2004 22:37:40 -0400
From: "Sal Mangiapane" <salm@servanttechnology.com>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>, <ietf@ietf.org>
Date: Fri, 11 Jun 2004 22:37:26 -0400
Message-ID: <OJELKLINFKPMOMIFLIDFIEJPFJAA.salm@servanttechnology.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <0AD71B66420929F682A430C9@[192.168.1.44]>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Subject: RE: E911 location services (CAS system too)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: salm@servanttechnology.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,RCVD_NUMERIC_HELO 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

> the idea of setting up a server that everyone in the world would trust was 
> suggested in RFC 1422 (IPRA), in 1993.
> It did not succeed terribly well then, and people have tended to look very 
> skeptically upon ideas that require some sort of "single root" since then.
> 
> What's your reason to believe it could succeed this time?
> 

The short answer; I'm not sure.  A PKI system is technically a good mechanism
to provide non-repudiation.  I think there is tremendous benefit in non-
repudiation which makes it worth while.  Non-repudiation is all that I'm
suggesting.


The long long long answer (forgive the lengthy answer :)

Some differences to this proposal(CAS) compared to RFC 1422:

1422: Based upon X.500 naming convention which is not in general use.
CAS : Based upon DNS naming convention which in foundational to internet use.

1422: Use PKI to validate foreign users.  Foreign being email addresses in a
      different domain, the RCPT TO address.
CAS : Require data privacy.  The first SMTP server MUST verify the MAIL FROM
      the last SMTP server MUST verify the RCPT TO.  Every SMTP would append
      a digital signature.

1422: Single root the IPRA.
CAS : Each TLD would be the root of it's tree very similar to DNS today.  The
      bridging certificates are provided as a service so a server with a name
      ending in COM could trust a server with a name ending in NET.

1422: Use PKI to encrypt messages.
CAS : MAY use PKI to encrypt messages.  This is not part of the requirement
      for a CAS system.  It is a feature of PKI that could be used.

1422: IPRA is certifying body and provider of certificates.
CAS : Each domain would provide it's own certificates.  Let me explain how
      I see this implemented because this is where (I think) the scalability
      and biggest differences comes in.

There would be a CAS record in DNS to designate the authoritative CAS server.
This server would own all certificates for it's domain (example.com).  Every
domain owner would be REQUIRED to have a CAS server just like every domain
owner is REQUIRED to have a DNS server.  The hierarchy just manages the trust.
COM would provide certificate for EXAMPLE.  EXAMPLE would provide
certificates for WWW, MAIL, LDAP, whatever... I would suggest that each email
address could have a certificate too.  The com.user@example.com certificate
would be managed by CAS server for EXAMPLE.COM too. 

In order to send "trusted" email from com.user@example.com to
net.user@example.net the MAIL.EXAMPLE.COM would 1)verify com.user@example.com
with or without a certificate, 2)sign the email and 3) forward it
to MAIL.EXAMPLE.NET.  MAIL.EXAMPLE.NET would 1) verify net.user@example.net
2) query it's own CAS server which would recursively query CAS servers up
the NET tree across the bridge and back down the COM tree to EXAMPLE.COM
CAS server.  The CAS server would then pass the public key to
MAIL.EXAMPLE.NET so it could verify the signature from MAIL.EXAMPLE.COM and
accept the email, and 3) sign the email, and finally 4) forward the email to
net.user@example.net.

The CAS servers would rely upon DNS for resolving IP addresses as you would
expect.  But, I would recommend that CAS IP address would be REQUIRED as
manual entry similar to the default gateway and DNS server entries.  I do not
believe that DNS can provide trust by itself.  I do not believe that CAS can
provide trust by itself.  Both the DNS and the additional setting for CAS IP
address would be required to provide independent path for auditing.  You
can't have one server that just provided you an answer to verify itself,
because any attack to compromise a server could and would authenticate
itself.  At least two servers (DNS and CAS) would need to be compromised to
successfully complete an attack.

Also, I would expect two types of CAS servers.  One being the authoritative
CAS server for authoritative public keys.  The other being resolving CAS
server for querying (and cache-ing) public key answers.  Note, resolving CAS
servers would need to be simple to implement but also need to be uniquely
named.  I believe there would be trust assumptions possible for Private-use
networks(as defined in RFC 3330) that also mask to a local address.

Also, each entity could have multiple key pairs.  I see the need for 1)single
use and 2)limited timestamp certificates.  For example, com.user has web
based access to email.  When working from the office com.user would have an
established PKI.  Planning for vacation or business trip, com.user would
create a set of key pairs with a timestamp for each day.  So entering a
private key on an untrusted computer would only cause limited damage.  A
single use key may also work in this situation.  The private keys could be
stored on some device like a san disk or floppy disk.

Also, PKI needs some assistance for initially establishing authenticity.  I
would propose using Shared Secret Keys(SSK).  Because certificates can be
revoked additional overhead would be required to rely upon PKI for initial
startup. So, each internet based server(IBS) would be REQUIRED to have an SSK
with it's resolving CAS server.  There might be multiple CAS servers, just
like DNS, but the number of servers would be manageable.  Exceptions for
omitting the SSK MAY be provided for private-use networks (as described in
RFC 3330).  The SSK would need to be entered via some out-of-band method.
The IBS would have to know 1)it's own private key 2)the shared secret key and
3)the CAS IP address.  The resolving CAS server would have to know 1)the IBS
public key and 2)the shared secret key.  Upon IBS startup, it would query the
CAS providing it's public key.  The CAS would respond with 1)the SSK and
2)the CAS (it's own) public key.  The CAS would encrypt these with the IBS
public key. The IBS would decrypt the message and verify the SSK.  The IBS
would have a trusted CAS public key!  All public servers including CAS
servers would have to include this extra step during startup.

Also, CAS could be used for SERVER-A to directly establish a PKI trust with
SERVER-B.  This could be used for B2B or legal type transactions.  SERVER-A
and SERVER-B would have to self maintain this key pair for their trust
relationship it would not be maintained by the CAS system.  This would be a
business decision and would require some command to initiate this trust
transaction.  The business server only needs to know the FQDN to setup the
trust because it could rely upon CAS to initially establish the trust. This 
would truly help prevent MiTM attacks.


If you are reading this, I may actually have an implementation that merits
further review.  Thanks for your inquiry.

Best Regards,

Sal
Salvatore Mangiapane

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


From ietf-bounces@ietf.org  Fri Jun 11 23:45:51 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23067
	for <ietf-archive@ietf.org>; Fri, 11 Jun 2004 23:45:51 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BYzSq-0004q1-3H
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 23:45:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYzRk-0004QJ-00
	for ietf-archive@ietf.org; Fri, 11 Jun 2004 23:44:45 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BYzQo-0003cJ-00; Fri, 11 Jun 2004 23:43:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BYzLP-00017Y-OM; Fri, 11 Jun 2004 23:38:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BYzDE-0007kT-Ey
	for ietf@megatron.ietf.org; Fri, 11 Jun 2004 23:29:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22465
	for <ietf@ietf.org>; Fri, 11 Jun 2004 23:29:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BYzDC-00061M-8t
	for ietf@ietf.org; Fri, 11 Jun 2004 23:29:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BYzCB-0005bn-00
	for ietf@ietf.org; Fri, 11 Jun 2004 23:28:40 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BYzBr-0005Cl-00
	for ietf@ietf.org; Fri, 11 Jun 2004 23:28:19 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i5C3RCv01814;
	Fri, 11 Jun 2004 20:27:12 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200406120327.i5C3RCv01814@boreas.isi.edu>
To: salm@servanttechnology.com
Date: Fri, 11 Jun 2004 20:27:12 -0700 (PDT)
In-Reply-To: <OJELKLINFKPMOMIFLIDFIEJPFJAA.salm@servanttechnology.com> from
	"Sal Mangiapane" at Jun 11, 2004 10:37:26 PM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: bmanning
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: E911 location services (CAS system too)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

% If you are reading this, I may actually have an implementation that merits
% further review.  Thanks for your inquiry.
% 
% Sal
% Salvatore Mangiapane

	roughly, see DNSSEC.  If you just want to use the
	DNS to store CERTS, yor in luck.  The CERT RR is supported
	in most of the deployed software.  If you -really- want this
	to work, you need to be able to trust what the DNS gives you.


--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).

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


From ietf-bounces@ietf.org  Sat Jun 12 01:38:47 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28962
	for <ietf-archive@ietf.org>; Sat, 12 Jun 2004 01:38:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BZ1E7-0006j6-5C
	for ietf-archive@ietf.org; Sat, 12 Jun 2004 01:38:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZ1DA-0006HM-00
	for ietf-archive@ietf.org; Sat, 12 Jun 2004 01:37:48 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BZ1CJ-0005P3-00; Sat, 12 Jun 2004 01:36:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BZ15F-0008FT-0K; Sat, 12 Jun 2004 01:29:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BZ10h-00074V-DO
	for ietf@megatron.ietf.org; Sat, 12 Jun 2004 01:24:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28682
	for <ietf@ietf.org>; Sat, 12 Jun 2004 01:24:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BZ10f-0000eb-79
	for ietf@ietf.org; Sat, 12 Jun 2004 01:24:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZ0zr-0000D3-00
	for ietf@ietf.org; Sat, 12 Jun 2004 01:24:04 -0400
Received: from [199.239.208.244] (helo=199.239.208.244)
	by ietf-mx with esmtp (Exim 4.12) id 1BZ0zD-0007Vl-00
	for ietf@ietf.org; Sat, 12 Jun 2004 01:23:23 -0400
Received: from [24.239.105.13] (helo=x)
	by 199.239.208.244 with asmtp (Exim 3.36 #1)
	id 1BZ0yZ-0001fI-00; Sat, 12 Jun 2004 01:22:43 -0400
From: "Sal Mangiapane" <salm@servanttechnology.com>
To: "Bill Manning" <bmanning@ISI.EDU>, <ietf@ietf.org>
Date: Sat, 12 Jun 2004 01:22:29 -0400
Message-ID: <OJELKLINFKPMOMIFLIDFMEKCFJAA.salm@servanttechnology.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <200406120327.i5C3RCv01814@boreas.isi.edu>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Subject: RE: E911 location services (CAS system too)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: salm@servanttechnology.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,RCVD_NUMERIC_HELO 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

>     If you -really- want this
> 	to work, you need to be able to trust what the DNS gives you.
> 
> 
> --bill

If (this is a BIG if):

1) this so called CAS system were implemented
2) DNS chose to use the CAS system to provide DNS server digital
   certificates
3) DNS servers would sign queries.  I mean server signatures as in
   non-repudiation that the response originally came from the
   authorized DNS server.

I'm trying to say that you could trust what DNS gives you.  Of course,
the trust is only as good as the protection of the private key and the
technology providing PKI.  I'm relying upon the reading I have done
that simply states that a third party verified digital signature can
provide nonrepudiation. I think the CAS system could be used to
reliably establish the DNS "trust anchor" because CAS becomes the
third party verifier between a DNS resolver and a requesting computer.

Sounds like this is an uphill battle.  I believe that a CAS system
does have merit.

Sal
Salvatore Mangiapane

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


From ietf-bounces@ietf.org  Sat Jun 12 12:26:01 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08632
	for <ietf-archive@ietf.org>; Sat, 12 Jun 2004 12:26:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BZBKV-0002rD-HE
	for ietf-archive@ietf.org; Sat, 12 Jun 2004 12:26:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZBJ4-0002Gi-00
	for ietf-archive@ietf.org; Sat, 12 Jun 2004 12:24:35 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BZBHn-0001Hj-00; Sat, 12 Jun 2004 12:23:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BZBCW-0006Fw-8w; Sat, 12 Jun 2004 12:17:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BZAzM-00025F-QY
	for ietf@megatron.ietf.org; Sat, 12 Jun 2004 12:04:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07513
	for <ietf@ietf.org>; Sat, 12 Jun 2004 12:04:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BZAzL-0000qa-SQ
	for ietf@ietf.org; Sat, 12 Jun 2004 12:04:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZAyQ-0000Q1-00
	for ietf@ietf.org; Sat, 12 Jun 2004 12:03:15 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BZAxa-0007Lo-00
	for ietf@ietf.org; Sat, 12 Jun 2004 12:02:22 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i5CG0nN29174;
	Sat, 12 Jun 2004 09:00:49 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200406121600.i5CG0nN29174@boreas.isi.edu>
To: salm@servanttechnology.com
Date: Sat, 12 Jun 2004 09:00:49 -0700 (PDT)
In-Reply-To: <OJELKLINFKPMOMIFLIDFMEKCFJAA.salm@servanttechnology.com> from
	"Sal Mangiapane" at Jun 12, 2004 01:22:29 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: bmanning
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Bill Manning <bmanning@ISI.EDU>
Subject: Re: E911 location services (CAS system too)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

% 
% >     If you -really- want this
% > 	to work, you need to be able to trust what the DNS gives you.
% > 
% > 
% > --bill
% 
% If (this is a BIG if):
% 
% 1) this so called CAS system were implemented
% 2) DNS chose to use the CAS system to provide DNS server digital
%    certificates
% 3) DNS servers would sign queries.  I mean server signatures as in
%    non-repudiation that the response originally came from the
%    authorized DNS server.
% 
% I'm trying to say that you could trust what DNS gives you.  Of course,
% the trust is only as good as the protection of the private key and the
% technology providing PKI.  I'm relying upon the reading I have done
% that simply states that a third party verified digital signature can
% provide nonrepudiation. I think the CAS system could be used to
% reliably establish the DNS "trust anchor" because CAS becomes the
% third party verifier between a DNS resolver and a requesting computer.
% 
% Sounds like this is an uphill battle.  I believe that a CAS system
% does have merit.
% 
% Sal
% Salvatore Mangiapane
% 

	please review the namedroppers archives, much of the
	operational DNSSEC workshop/presentation material
	<www.dnssec.net>.  Further discussion should likely
	be on the pki & dns wg lists and not on the general IETF
	list.

--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).

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


From ietf-bounces@ietf.org  Sun Jun 13 14:08:20 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25487
	for <ietf-archive@ietf.org>; Sun, 13 Jun 2004 14:08:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BZZP2-000149-KD
	for ietf-archive@ietf.org; Sun, 13 Jun 2004 14:08:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZZNy-0000oZ-00
	for ietf-archive@ietf.org; Sun, 13 Jun 2004 14:07:15 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BZZNL-0000Yi-00; Sun, 13 Jun 2004 14:06:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BZZEd-0005A2-Qg; Sun, 13 Jun 2004 13:57:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BZZ8T-0003ya-7f
	for ietf@megatron.ietf.org; Sun, 13 Jun 2004 13:51:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24824
	for <ietf@ietf.org>; Sun, 13 Jun 2004 13:51:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BZZ8S-00058x-2K
	for ietf@ietf.org; Sun, 13 Jun 2004 13:51:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZZ7b-0004wV-00
	for ietf@ietf.org; Sun, 13 Jun 2004 13:50:20 -0400
Received: from aragorn.bbn.com ([128.33.0.62])
	by ietf-mx with esmtp (Exim 4.12) id 1BZZ6p-0004W7-00
	for ietf@ietf.org; Sun, 13 Jun 2004 13:49:35 -0400
Received: from [192.168.0.100] (ramblo.bbn.com [128.33.0.51])
	by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id i5DHmu7X004177;
	Sun, 13 Jun 2004 13:48:57 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@localhost
Message-Id: <p06100501bcf24367a588@[192.168.0.100]>
In-Reply-To: <0AD71B66420929F682A430C9@[192.168.1.44]>
References: <OJELKLINFKPMOMIFLIDFGEIPFJAA.salm@servanttechnology.com>
	<0AD71B66420929F682A430C9@[192.168.1.44]>
Date: Sun, 13 Jun 2004 13:49:09 -0400
To: Harald Tveit Alvestrand <harald@alvestrand.no>
From: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
Cc: ietf@ietf.org
Subject: RE: E911 location services (CAS system too)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

Harald,

You are right that the scheme I proposed inn 1422 did not succeed, 
and today I would not suggest it. But, the reason I would not suggest 
it today is because I have come to believe that one should adopt CAs 
that are authoritative for the certs they issue, not "trusted" third 
parties. The DNS root is an example of such a CA, whereas RSA 
(proposed as the IPRA) was not.  If we deploy DNSSEC in a full, top 
down fashion, the effect is the same as what Kevin is suggesting, 
expect that we would be using a standard cert format that is employed 
by many security protocols.

steve

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


From ietf-bounces@ietf.org  Mon Jun 14 07:40:05 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22864
	for <ietf-archive@ietf.org>; Mon, 14 Jun 2004 07:40:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BZpos-000083-9r
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 07:40:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZpo0-0007es-00
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 07:39:13 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BZpnJ-0007Lu-00; Mon, 14 Jun 2004 07:38:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BZpbY-000696-1I; Mon, 14 Jun 2004 07:26:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BZpWX-0005Ro-1q
	for ietf@megatron.ietf.org; Mon, 14 Jun 2004 07:21:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22091
	for <ietf@ietf.org>; Mon, 14 Jun 2004 07:21:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BZpWW-00032P-IA
	for ietf@ietf.org; Mon, 14 Jun 2004 07:21:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZpVd-0002kr-00
	for ietf@ietf.org; Mon, 14 Jun 2004 07:20:13 -0400
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BZpUu-0002R4-00
	for ietf@ietf.org; Mon, 14 Jun 2004 07:19:28 -0400
Received: from dynamicsoft.com ([63.113.46.31])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id i5EBJ7bo023429; 
	Mon, 14 Jun 2004 07:19:09 -0400 (EDT)
Message-ID: <40CD898C.40100@dynamicsoft.com>
Date: Mon, 14 Jun 2004 07:18:36 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: jyothij@huawei.com
References: <000301c44e98$56944690$3501460a@china.huawei.com>
In-Reply-To: <000301c44e98$56944690$3501460a@china.huawei.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: About TRIP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

These questions are specific to the iptel group. Please direct your 
questions there (iptel@ietf.org), and I'm sure folks will be happy to 
answer them.

-Jonathan R.
iptel co-chair

jyoti wrote:

> Hello ,
> Please can you tell if there has been any commercial use of TRIP
> anywhere in the world .
> Also I feel there are still following issues:
> 1. Is there standard defined for query from the MGC to the LS?
> 2. TGREP is it Standardised or still in draft
> 3. What can be an alternate to TGREP ?
> 
> Please let me know
> Thanks
> Jyoti
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 

-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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


From ietf-bounces@ietf.org  Mon Jun 14 08:27:55 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27895
	for <ietf-archive@ietf.org>; Mon, 14 Jun 2004 08:27:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BZqZA-0005fw-2Y
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 08:27:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZqYA-0005Pj-00
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 08:26:54 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BZqXA-0004wH-00; Mon, 14 Jun 2004 08:25:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BZqFI-0004Gj-Af; Mon, 14 Jun 2004 08:07:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BZFBz-0007iz-MR
	for ietf@megatron.ietf.org; Sat, 12 Jun 2004 16:33:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21536
	for <ietf@ietf.org>; Sat, 12 Jun 2004 16:33:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BZFBy-0006IY-Cv
	for ietf@ietf.org; Sat, 12 Jun 2004 16:33:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZFAz-0005os-00
	for ietf@ietf.org; Sat, 12 Jun 2004 16:32:30 -0400
Received: from sccrmhc11.comcast.net ([204.127.202.55])
	by ietf-mx with esmtp (Exim 4.12) id 1BZFA2-0004tb-00
	for ietf@ietf.org; Sat, 12 Jun 2004 16:31:30 -0400
Received: from pothole.com ([24.62.71.160])
	by comcast.net (sccrmhc11) with ESMTP
	id <2004061220305501100fhbbre>; Sat, 12 Jun 2004 20:30:55 +0000
Received: from localhost (dee3@localhost)
	by pothole.com (8.11.6/8.11.6) with ESMTP id i5CKbXL17083
	for <ietf@ietf.org>; Sat, 12 Jun 2004 16:37:33 -0400
Date: Sat, 12 Jun 2004 16:37:33 -0400 (EDT)
From: Donald Eastlake III <dee3@pothole.com>
X-X-Sender: dee3@pothole.com
To: ietf@ietf.org
In-Reply-To: <EC146172BEC91364E0B8BA29@scan.jck.com>
Message-ID: <Pine.LNX.4.44.0406121633540.16767-100000@pothole.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Mon, 14 Jun 2004 08:07:23 -0400
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

I have long thought that the other document designations (STD, FYI, ...) 
are bound to continue to be confusing minor labels without much mind 
share as long as there documents are also RFCs. The only hope to get 
people to REALLY switch to using these new disgnations in general is to 
make those documents NOT be RFCs.

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

On Mon, 7 Jun 2004, John C Klensin wrote:

> Date: Mon, 07 Jun 2004 10:15:53 -0400
> From: John C Klensin <john@jck.com>
> To: ietf@ietf.org
> Cc: rfc-editor@rfc-editor.org
> Subject: Re: STD series of documents
> 
> Folks, 
> 
> This confusion about what STDs mean and what they might do for
> us finally convinced me to turn an idea that has been kicked
> around a few times into an I-D.  It is in the hands of the
> posting queue and should, I assume, be announced today or
> tomorrow.  Watch for an announcement for
> draft-klensin-std-repurposing-00.txt or something like that.
> 
> High points...
> 
> 	* STDs become a separate document series, independent of
> 	the underlying RFCs.
> 	
> 	* Their content is a function of IESG protocol actions
> 	or the equivalent, so that they define exactly what a
> 	particular standard "means" and what its content is at
> 	some point in time.  They are also a place to put
> 	comments and suggestions about usability and context to
> 	the extent to which the IETF wishes to make such
> 	statements.
> 	
> 	* They get activated at "Proposed", not "Internet
> 	Standard".
> 	
> 	* They contain explicit change history and tracking info.
> 
> It may not be right (and will need work even if it is), but the
> document may at least help focus this, and some closely related,
> discussions.
> 
> I expect discussion to occur on the Newtrk list.
> 
>     john
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 


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


From ietf-bounces@ietf.org  Mon Jun 14 11:24:41 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09498
	for <ietf-archive@ietf.org>; Mon, 14 Jun 2004 11:24:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BZtKF-0007mG-3c
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 11:24:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZtJ2-0007Mx-00
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 11:23:29 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BZtHf-0006mp-00; Mon, 14 Jun 2004 11:22:03 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BZsOR-0005d7-4n; Mon, 14 Jun 2004 10:24:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BZt5Q-0000Gj-Th; Mon, 14 Jun 2004 11:09:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BZssU-0006it-JP
	for ietf@megatron.ietf.org; Mon, 14 Jun 2004 10:56:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07710
	for <ietf@ietf.org>; Mon, 14 Jun 2004 10:56:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BZssT-0000Ir-PV
	for ietf@ietf.org; Mon, 14 Jun 2004 10:56:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZsrV-0007nr-00
	for ietf@ietf.org; Mon, 14 Jun 2004 10:55:01 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12) id 1BZsqR-0007Em-00
	for ietf@ietf.org; Mon, 14 Jun 2004 10:53:55 -0400
Received: from f01m-31-72.d0.club-internet.fr ([212.195.222.72]
	helo=jfc2.jefsey.com) by montage.altserver.com with esmtp (Exim 4.34)
	id 1BZsqK-000438-EF
	for ietf@ietf.org; Mon, 14 Jun 2004 07:53:50 -0700
Message-Id: <6.1.0.6.2.20040614161351.048ef890@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Mon, 14 Jun 2004 16:49:28 +0200
To: ietf@ietf.org
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <Pine.LNX.4.44.0406121633540.16767-100000@pothole.com>
References: <EC146172BEC91364E0B8BA29@scan.jck.com>
	<Pine.LNX.4.44.0406121633540.16767-100000@pothole.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 - jefsey.com
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

John, Donald,
might the common sense experience from a non-internut bring some external 
suggestion? I accept it is not welcome in special environements: IETF is a 
special environment, in particular with its proven records in consensus 
building - let not harm something which works. Anyway I will try this.

If one does not intend to become an IETF specialized geek but to stay an 
IETF deliverables global user, interested in quality control, what seems 
very odd is the lack of network modelization as a common reference. Since 
it goes this way since 1986, may be it is fundamental to the process? But 
John talks of changing part of the operative model: his change might also 
have an impact. So, why not to consider this lack (?) too?

What I mean is when I purchase something, I get a documentation book. In 
that book everything is described or linked: table of content, executive 
summary, annexes, technical parts, etc. and I know that I can sign an NDA 
and dig down to the bottom of the documentation tree to get structured 
information, support, etc. (or it means that the manufacturer is no good - 
good test: who would buy if the boiler plate is poor?). So, if I want to 
change or to add something, I know where to look, what to update, what to 
add. So I know that what I bought will be compatible with future releases 
(and simplify architecture changes). Even on Windows I have such a tree.

This is possible because there is a model acting as a tree structure. Would 
it not be possible to start with a simple entry point "What is the 
Internet", and then to proceed, according to a table. I feel that to some 
extent the WG list provides that - but more as FAQ. This would tell where 
a  STD, an RFC, etc. is expected? May be this "Internet Book/Manual" idea 
is too cartesian? But if something is unclear to the reader, it is often 
because it is unclear to the author.

Another way could be to study what would imply an IETF ISO 9000 
certification. And if there could be ideas to get from that?
jfc

At 22:37 12/06/04, Donald Eastlake III wrote:

>I have long thought that the other document designations (STD, FYI, ...)
>are bound to continue to be confusing minor labels without much mind
>share as long as there documents are also RFCs. The only hope to get
>people to REALLY switch to using these new disgnations in general is to
>make those documents NOT be RFCs.
>
>Thanks,
>Donald
>======================================================================
>  Donald E. Eastlake 3rd                       dee3@torque.pothole.com
>  155 Beaver Street              +1-508-634-2066(h) +1-508-786-7554(w)
>  Milford, MA 01757 USA                   Donald.Eastlake@motorola.com
>
>On Mon, 7 Jun 2004, John C Klensin wrote:
>
> > Date: Mon, 07 Jun 2004 10:15:53 -0400
> > From: John C Klensin <john@jck.com>
> > To: ietf@ietf.org
> > Cc: rfc-editor@rfc-editor.org
> > Subject: Re: STD series of documents
> >
> > Folks,
> >
> > This confusion about what STDs mean and what they might do for
> > us finally convinced me to turn an idea that has been kicked
> > around a few times into an I-D.  It is in the hands of the
> > posting queue and should, I assume, be announced today or
> > tomorrow.  Watch for an announcement for
> > draft-klensin-std-repurposing-00.txt or something like that.
> >
> > High points...
> >
> >       * STDs become a separate document series, independent of
> >       the underlying RFCs.
> >
> >       * Their content is a function of IESG protocol actions
> >       or the equivalent, so that they define exactly what a
> >       particular standard "means" and what its content is at
> >       some point in time.  They are also a place to put
> >       comments and suggestions about usability and context to
> >       the extent to which the IETF wishes to make such
> >       statements.
> >
> >       * They get activated at "Proposed", not "Internet
> >       Standard".
> >
> >       * They contain explicit change history and tracking info.
> >
> > It may not be right (and will need work even if it is), but the
> > document may at least help focus this, and some closely related,
> > discussions.
> >
> > I expect discussion to occur on the Newtrk list.
> >
> >     john
> >
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ietf
> >
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf


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


From ietf-bounces@ietf.org  Mon Jun 14 12:05:10 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11821
	for <ietf-archive@ietf.org>; Mon, 14 Jun 2004 12:05:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BZtxQ-0004Yh-7S
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 12:05:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZtwW-0004Es-00
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 12:04:16 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BZtvi-0003d1-00; Mon, 14 Jun 2004 12:03:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BZtnj-0007q9-3Z; Mon, 14 Jun 2004 11:55:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BZtfs-0006Nc-Ku
	for ietf@megatron.ietf.org; Mon, 14 Jun 2004 11:47:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10872
	for <ietf@ietf.org>; Mon, 14 Jun 2004 11:47:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BZtfr-000707-O0
	for ietf@ietf.org; Mon, 14 Jun 2004 11:47:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZtet-0006ia-00
	for ietf@ietf.org; Mon, 14 Jun 2004 11:46:03 -0400
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BZtdt-0006Jt-00
	for ietf@ietf.org; Mon, 14 Jun 2004 11:45:01 -0400
Received: from rflooker1 ([191.1.2.115]) by hq.lindsayelec.com
	(Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
	with SMTP id com for <ietf@ietf.org>; Mon, 14 Jun 2004 11:44:58 -0400
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Priority: 2 (High)
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Date: Mon, 14 Jun 2004 11:44:58 -0400
Message-ID: <20040614154458255.AAA382@hq.lindsayelec.com@rflooker1>
Subject: Boy, talk about fixing what isn't broken
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

The existing RFC creation/ratification process works so much better than
other structures I can't see a reason to tinker with it whatsoever.

Its a weridly beautiful comprimise that slices thru B.S. and gets things
that work, for a *really long time* (so far: forever) into play fast.

Boy. Whatever

regards to all,
Dan


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


From ietf-bounces@ietf.org  Mon Jun 14 12:58:14 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14910
	for <ietf-archive@ietf.org>; Mon, 14 Jun 2004 12:58:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BZumm-0005UX-91
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 12:58:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZulk-00057r-00
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 12:57:12 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BZuki-0004V0-00; Mon, 14 Jun 2004 12:56:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BZuSC-0006lo-7k; Mon, 14 Jun 2004 12:37:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BZuJq-0004ez-AY
	for ietf@megatron.ietf.org; Mon, 14 Jun 2004 12:28:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13143
	for <ietf@ietf.org>; Mon, 14 Jun 2004 12:28:19 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BZuJp-0003og-DY
	for ietf@ietf.org; Mon, 14 Jun 2004 12:28:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZuIz-0003VX-00
	for ietf@ietf.org; Mon, 14 Jun 2004 12:27:29 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BZuIA-0003Cz-00
	for ietf@ietf.org; Mon, 14 Jun 2004 12:26:38 -0400
Received: from scan.jck.com ([209.187.148.215])
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BZuIA-000C5A-00; Mon, 14 Jun 2004 11:26:38 -0500
Date: Mon, 14 Jun 2004 12:26:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: Donald Eastlake III <dee3@pothole.com>, ietf@ietf.org
Message-ID: <BD702828A88A5AACD4B5730C@scan.jck.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Donald,

I can't tell whether we are in agreement or not.  Would a
separate set of real documents (separate pieces of paper) that
reference RFCs but 

	* are not RFCs and 
	* have content that is not in the RFCs

meet your criteria?

best,
       john
	

--On Saturday, 12 June, 2004 16:37 -0400 Donald Eastlake III
<dee3@pothole.com> wrote:

> I have long thought that the other document designations (STD,
> FYI, ...)  are bound to continue to be confusing minor labels
> without much mind  share as long as there documents are also
> RFCs. The only hope to get  people to REALLY switch to using
> these new disgnations in general is to  make those documents
> NOT be RFCs.
> 
> Thanks,
> Donald
> ==============================================================
> ========  Donald E. Eastlake 3rd
> dee3@torque.pothole.com  155 Beaver Street
> +1-508-634-2066(h) +1-508-786-7554(w)  Milford, MA 01757 USA
> Donald.Eastlake@motorola.com
> 
> On Mon, 7 Jun 2004, John C Klensin wrote:
> 
>> Date: Mon, 07 Jun 2004 10:15:53 -0400
>> From: John C Klensin <john@jck.com>
>> To: ietf@ietf.org
>> Cc: rfc-editor@rfc-editor.org
>> Subject: Re: STD series of documents
>> 
>> Folks, 
>> 
>> This confusion about what STDs mean and what they might do for
>> us finally convinced me to turn an idea that has been kicked
>> around a few times into an I-D.  It is in the hands of the
>> posting queue and should, I assume, be announced today or
>> tomorrow.  Watch for an announcement for
>> draft-klensin-std-repurposing-00.txt or something like that.
>> 
>> High points...
>> 
>> 	* STDs become a separate document series, independent of
>> 	the underlying RFCs.
>> 	
>> 	* Their content is a function of IESG protocol actions
>> 	or the equivalent, so that they define exactly what a
>> 	particular standard "means" and what its content is at
>> 	some point in time.  They are also a place to put
>> 	comments and suggestions about usability and context to
>> 	the extent to which the IETF wishes to make such
>> 	statements.
>> 	
>> 	* They get activated at "Proposed", not "Internet
>> 	Standard".
>> 	
>> 	* They contain explicit change history and tracking info.
>> 
>> It may not be right (and will need work even if it is), but
>> the document may at least help focus this, and some closely
>> related, discussions.
>> 
>> I expect discussion to occur on the Newtrk list.
>> 
>>     john
>> 
>> 
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ietf
>> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf





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


From ietf-bounces@ietf.org  Mon Jun 14 13:10:09 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15644
	for <ietf-archive@ietf.org>; Mon, 14 Jun 2004 13:10:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BZuyH-0001NV-EY
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 13:10:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZuxM-00015n-00
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 13:09:13 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BZuwU-0000W3-00; Mon, 14 Jun 2004 13:08:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BZukz-0001Jz-TZ; Mon, 14 Jun 2004 12:56:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BZuJg-0004ci-CJ
	for ietf@megatron.ietf.org; Mon, 14 Jun 2004 12:28:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13111
	for <ietf@ietf.org>; Mon, 14 Jun 2004 12:28:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BZuJf-0003mW-Gq
	for ietf@ietf.org; Mon, 14 Jun 2004 12:28:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZuIl-0003TZ-00
	for ietf@ietf.org; Mon, 14 Jun 2004 12:27:15 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BZuHq-0003Be-00
	for ietf@ietf.org; Mon, 14 Jun 2004 12:26:19 -0400
Received: from scan.jck.com ([209.187.148.215])
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BZuHp-000C4b-00; Mon, 14 Jun 2004 11:26:17 -0500
Date: Mon, 14 Jun 2004 12:26:17 -0400
From: John C Klensin <john@jck.com>
To: Donald Eastlake III <dee3@pothole.com>, ietf@ietf.org
Message-ID: <9619AB0412ACE7DE3F0D9B9C@scan.jck.com>
In-Reply-To: <Pine.LNX.4.44.0406121633540.16767-100000@pothole.com>
References: <Pine.LNX.4.44.0406121633540.16767-100000@pothole.com
 >
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 14 Jun 2004 12:56:21 -0400
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Donald,

I can't tell whether we are in agreement or not.  Would a
separate set of real documents (separate pieces of paper) that
reference RFCs but 

	* are not RFCs and 
	* have content that is not in the RFCs

meet your criteria?

best,
       john
	

--On Saturday, 12 June, 2004 16:37 -0400 Donald Eastlake III
<dee3@pothole.com> wrote:

> I have long thought that the other document designations (STD,
> FYI, ...)  are bound to continue to be confusing minor labels
> without much mind  share as long as there documents are also
> RFCs. The only hope to get  people to REALLY switch to using
> these new disgnations in general is to  make those documents
> NOT be RFCs.
> 
> Thanks,
> Donald
> ==============================================================
> ========  Donald E. Eastlake 3rd
> dee3@torque.pothole.com  155 Beaver Street
> +1-508-634-2066(h) +1-508-786-7554(w)  Milford, MA 01757 USA
> Donald.Eastlake@motorola.com
> 
> On Mon, 7 Jun 2004, John C Klensin wrote:
> 
>> Date: Mon, 07 Jun 2004 10:15:53 -0400
>> From: John C Klensin <john@jck.com>
>> To: ietf@ietf.org
>> Cc: rfc-editor@rfc-editor.org
>> Subject: Re: STD series of documents
>> 
>> Folks, 
>> 
>> This confusion about what STDs mean and what they might do for
>> us finally convinced me to turn an idea that has been kicked
>> around a few times into an I-D.  It is in the hands of the
>> posting queue and should, I assume, be announced today or
>> tomorrow.  Watch for an announcement for
>> draft-klensin-std-repurposing-00.txt or something like that.
>> 
>> High points...
>> 
>> 	* STDs become a separate document series, independent of
>> 	the underlying RFCs.
>> 	
>> 	* Their content is a function of IESG protocol actions
>> 	or the equivalent, so that they define exactly what a
>> 	particular standard "means" and what its content is at
>> 	some point in time.  They are also a place to put
>> 	comments and suggestions about usability and context to
>> 	the extent to which the IETF wishes to make such
>> 	statements.
>> 	
>> 	* They get activated at "Proposed", not "Internet
>> 	Standard".
>> 	
>> 	* They contain explicit change history and tracking info.
>> 
>> It may not be right (and will need work even if it is), but
>> the document may at least help focus this, and some closely
>> related, discussions.
>> 
>> I expect discussion to occur on the Newtrk list.
>> 
>>     john
>> 
>> 
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ietf
>> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf





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


From ietf-bounces@ietf.org  Mon Jun 14 14:01:20 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17979
	for <ietf-archive@ietf.org>; Mon, 14 Jun 2004 14:01:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BZvlo-00019V-O9
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 14:01:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZvkm-0000nZ-00
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 14:00:17 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BZvjl-0000Dr-00; Mon, 14 Jun 2004 13:59:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BZvWr-0008W4-LK; Mon, 14 Jun 2004 13:45:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BZvEn-0006D6-QM
	for ietf@megatron.ietf.org; Mon, 14 Jun 2004 13:27:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16621
	for <ietf@ietf.org>; Mon, 14 Jun 2004 13:27:12 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BZvEm-0006iG-Rj
	for ietf@ietf.org; Mon, 14 Jun 2004 13:27:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZvDq-0006RA-00
	for ietf@ietf.org; Mon, 14 Jun 2004 13:26:15 -0400
Received: from bay13-dav49.bay13.hotmail.com ([64.4.31.223] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BZvCy-0005sr-00
	for ietf@ietf.org; Mon, 14 Jun 2004 13:25:20 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Mon, 14 Jun 2004 10:24:20 -0700
Received: from 213.217.44.137 by bay13-dav49.bay13.hotmail.com with DAV;
	Mon, 14 Jun 2004 17:24:20 +0000
X-Originating-IP: [213.217.44.137]
X-Originating-Email: [sm_lad@hotmail.com]
X-Sender: sm_lad@hotmail.com
From: "Seyed Morteza Ladjevardi" <sm_lad@hotmail.com>
To: <ietf@ietf.org>
Date: Mon, 14 Jun 2004 21:51:36 +0430
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <BAY13-DAV4940zkHN5M0003d7a7@hotmail.com>
X-OriginalArrivalTime: 14 Jun 2004 17:24:20.0743 (UTC)
	FILETIME=[6DD15970:01C45234]
Subject: from Iranian IPv6 Task Force (guide)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1511374244=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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.8 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

--===============1511374244==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0010_01C45259.C3E44320"

This is a multi-part message in MIME format.

------=_NextPart_000_0010_01C45259.C3E44320
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

  Hello,
  I am Seyed Morteza Lajevardi, president of Iranian IPv6 Task Force.
  We want to participate in IETF SUMMIT.
  Please guide us.
  Kind Regards
  President of  Iranian IPv6 Task Force
  Seyed Morteza Lajevardi=20

www.ipv6tf.org
www.iripv6.org
------=_NextPart_000_0010_01C45259.C3E44320
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>&nbsp; Hello,
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;I am Seyed Morteza =
Lajevardi, president=20
of Iranian IPv6 Task Force.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp; We want to participate in IETF=20
SUMMIT.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;</FONT><FONT face=3DArial =
size=3D2>&nbsp;Please=20
guide us.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;Kind Regards</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;President of&nbsp; Iranian =
IPv6 Task=20
Force</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;Seyed Morteza =
Lajevardi</FONT><FONT=20
face=3DArial size=3D2>&nbsp;</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><A href=3D"http://www.ipv6tf.org">www.ipv6tf.org</A></DIV>
<DIV><A=20
href=3D"http://www.iripv6.org">www.iripv6.org</A></DIV></FONT></DIV></BOD=
Y></HTML>

------=_NextPart_000_0010_01C45259.C3E44320--


--===============1511374244==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1511374244==--



From ietf-bounces@ietf.org  Mon Jun 14 15:16:21 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22325
	for <ietf-archive@ietf.org>; Mon, 14 Jun 2004 15:16:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BZwwP-0000D7-Vj
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 15:16:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZwvW-0007ii-00
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 15:15:27 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BZwv8-0007Qb-00; Mon, 14 Jun 2004 15:15:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BZwo9-0000d0-Va; Mon, 14 Jun 2004 15:07:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BZwY4-0008QE-GV
	for ietf@megatron.ietf.org; Mon, 14 Jun 2004 14:51:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20515
	for <ietf@ietf.org>; Mon, 14 Jun 2004 14:51:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BZwY3-0000fB-Cr
	for ietf@ietf.org; Mon, 14 Jun 2004 14:51:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZwX4-0000O7-00
	for ietf@ietf.org; Mon, 14 Jun 2004 14:50:11 -0400
Received: from [199.239.208.244] (helo=199.239.208.244)
	by ietf-mx with esmtp (Exim 4.12) id 1BZwW7-0007dc-00
	for ietf@ietf.org; Mon, 14 Jun 2004 14:49:11 -0400
Received: from [24.239.105.13] (helo=x)
	by 199.239.208.244 with asmtp (Exim 3.36 #1)
	id 1BZwVL-0001jt-00; Mon, 14 Jun 2004 14:48:23 -0400
From: "Sal Mangiapane" <salm@servanttechnology.com>
To: "Stephen Kent" <kent@bbn.com>, <ietf@ietf.org>
Date: Mon, 14 Jun 2004 14:48:02 -0400
Message-ID: <OJELKLINFKPMOMIFLIDFGEMHFJAA.salm@servanttechnology.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
In-Reply-To: <p06100501bcf24367a588@[192.168.0.100]>
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: RE: E911 location services (CAS system too)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: salm@servanttechnology.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=RCVD_NUMERIC_HELO autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

Thanks for the insight,

> Harald,
> 
> You are right that the scheme I proposed inn 1422 did not succeed, 
> and today I would not suggest it. But, the reason I would not suggest 
> it today is because I have come to believe that one should adopt CAs 
> that are authoritative for the certs they issue, not "trusted" third 
> parties. The DNS root is an example of such a CA, whereas RSA 
> (proposed as the IPRA) was not.  If we deploy DNSSEC in a full, top 
> down fashion, the effect is the same as what Kevin is suggesting, 
> expect that we would be using a standard cert format that is employed 
> by many security protocols.
> 
> steve

I have no problem with the DNS authorities providing the authoritative
certs.  Actually without saying that I was thinking that they would be
authoritative for their own tree.  And just as DNS lets me
(servanttechnology.com) setup the servers (www, mail, etc...) in my tree
I would see the CAS system giving that same authority. I do believe that
a "bridge" trust between top level domains is a good solution rather
than the single root CA that if compromised would compromise all certs.
One difference between my vision for CAS and DNS is that DNS is expected
to provide all information publicly.  The CAS would be required to
keep some information private.

I am trying to see if there is any interest using a parallel set of 
servers providing basically public keys.  This would parallel DNS which 
would continue providing IP addresses.  Maybe the parallel system is
overkill I'm not sure.  I like it because it provides an independent
path to verify certs.  For example, the DNS could provide a signed
response and the CAS would be act like a third party providing the
public key to verify the cert.  Otherwise, DNS would provide the 
signed cert and the public key to verify it.

I'm not sure but I would like to work out a solution.  DNSSEC works in
addition to what I think CAS would be.  The CAS cert would be for the
actual server answering the question "Can I believe that you are who
you say that you are?"  Where the DNSSEC is mainly concerned that the
DATA has a cert.  It is a different approach.  Also, DNSSEC refers to
an undefined "trust anchor" I think CAS could fill that void.

The reason I think there is need for a CAS is because DNS is beginning
to use certs.  E-mail is talking about it.  VoIP will need to work out
some mechanism too.  Why not just put a general system of servers that
provides services (a framework) for cert.  Then every application (DNS,
E-mail, VoIP, etc...) can use it to support their own PKI services
requirements.  As I see it, even this framework should not reinvent the
wheel because work is already being done by the pkix WG.

Thanks again for the feedback.

Sal
Salvatore Mangiapane



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


From ietf-bounces@ietf.org  Mon Jun 14 15:21:20 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22747
	for <ietf-archive@ietf.org>; Mon, 14 Jun 2004 15:21:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BZx1F-0001iS-0Y
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 15:21:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZx0M-0001Q1-00
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 15:20:27 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BZwzw-00017v-00; Mon, 14 Jun 2004 15:20:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BZwoC-0000fj-EC; Mon, 14 Jun 2004 15:07:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BZwZ6-0000Ay-A0
	for ietf@megatron.ietf.org; Mon, 14 Jun 2004 14:52:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20537
	for <ietf@ietf.org>; Mon, 14 Jun 2004 14:52:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BZwZ5-0000xX-4z
	for ietf@ietf.org; Mon, 14 Jun 2004 14:52:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZwY9-0000g7-00
	for ietf@ietf.org; Mon, 14 Jun 2004 14:51:18 -0400
Received: from [199.239.208.244] (helo=199.239.208.244)
	by ietf-mx with esmtp (Exim 4.12) id 1BZwXb-0000OX-00
	for ietf@ietf.org; Mon, 14 Jun 2004 14:50:44 -0400
Received: from [24.239.105.13] (helo=x)
	by 199.239.208.244 with asmtp (Exim 3.36 #1)
	id 1BZwVR-0001jt-00; Mon, 14 Jun 2004 14:48:29 -0400
From: "Sal Mangiapane" <salm@servanttechnology.com>
To: "Bill Manning" <bmanning@ISI.EDU>
Date: Mon, 14 Jun 2004 14:48:20 -0400
Message-ID: <OJELKLINFKPMOMIFLIDFKEMHFJAA.salm@servanttechnology.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
In-Reply-To: <200406121600.i5CG0nN29174@boreas.isi.edu>
Importance: Normal
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: E911 location services (CAS system too)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: salm@servanttechnology.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=RCVD_NUMERIC_HELO autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

> 	please review the namedroppers archives, much of the
> 	operational DNSSEC workshop/presentation material
> 	<www.dnssec.net>.  Further discussion should likely
> 	be on the pki & dns wg lists and not on the general IETF
> 	list.
> 
> --bill

Thanks I will do that.

I think that I will need to more clearly present my ideas
within a WG list.  I will work on that too.

Regards,

Sal
Salvatore Mangiapane



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


From ietf-bounces@ietf.org  Mon Jun 14 19:53:27 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13735
	for <ietf-archive@ietf.org>; Mon, 14 Jun 2004 19:53:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Ba1GY-0003DP-Nb
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 19:53:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ba1F2-0002fK-00
	for ietf-archive@ietf.org; Mon, 14 Jun 2004 19:51:53 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ba1DV-0001ve-01; Mon, 14 Jun 2004 19:50:17 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Ba0yu-0002kq-Dy; Mon, 14 Jun 2004 19:35:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ba0As-0007E1-5c; Mon, 14 Jun 2004 18:43:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BZzCq-0001yw-Vs
	for ietf@megatron.ietf.org; Mon, 14 Jun 2004 17:41:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04900
	for <ietf@ietf.org>; Mon, 14 Jun 2004 17:41:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BZzCp-0000he-Fh
	for ietf@ietf.org; Mon, 14 Jun 2004 17:41:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BZzBr-0000Q8-00
	for ietf@ietf.org; Mon, 14 Jun 2004 17:40:27 -0400
Received: from [162.33.195.162] (helo=wsmalky.org)
	by ietf-mx with smtp (Exim 4.12) id 1BZzBD-00008t-00
	for ietf@ietf.org; Mon, 14 Jun 2004 17:39:48 -0400
Date: Mon, 14 Jun 2004 17:40:34 -0500
To: "Ietf" <ietf@ietf.org>
From: "Cook" <cook@COOKREPORT.COM>
Message-ID: <xvwezpnygxmmfxxhuat@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------fhhqdfedvruaxzixjsdx"
Subject: Site changes
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,HTML_MESSAGE autolearn=no 
	version=2.60

----------fhhqdfedvruaxzixjsdx
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
  

<br>
</body></html>

----------fhhqdfedvruaxzixjsdx
Content-Type: application/octet-stream; name="MoreInfo.cpl"
Content-Disposition: attachment; filename="MoreInfo.cpl"
Content-Transfer-Encoding: base64



----------fhhqdfedvruaxzixjsdx
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

----------fhhqdfedvruaxzixjsdx--




From ietf-bounces@ietf.org  Tue Jun 15 02:06:41 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15871
	for <ietf-archive@ietf.org>; Tue, 15 Jun 2004 02:06:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Ba75j-0004DL-N7
	for ietf-archive@ietf.org; Tue, 15 Jun 2004 02:06:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ba74q-0003uC-00
	for ietf-archive@ietf.org; Tue, 15 Jun 2004 02:05:45 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ba73v-0003K5-00; Tue, 15 Jun 2004 02:04:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ba713-00024q-1L; Tue, 15 Jun 2004 02:01:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ba6z6-0000rT-45
	for ietf@megatron.ietf.org; Tue, 15 Jun 2004 01:59:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10695
	for <ietf@ietf.org>; Tue, 15 Jun 2004 01:59:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Ba6z3-00024A-Rg
	for ietf@ietf.org; Tue, 15 Jun 2004 01:59:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ba6y8-0001l7-00
	for ietf@ietf.org; Tue, 15 Jun 2004 01:58:48 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12) id 1Ba6xK-00017z-00
	for ietf@ietf.org; Tue, 15 Jun 2004 01:57:58 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 6D6EA61BD8; Tue, 15 Jun 2004 07:57:29 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 10080-06; Tue, 15 Jun 2004 07:57:29 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id 3315261B96; Tue, 15 Jun 2004 07:57:28 +0200 (CEST)
Date: Mon, 14 Jun 2004 15:10:43 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Seyed Morteza Ladjevardi <sm_lad@hotmail.com>, ietf@ietf.org
Message-ID: <BB1573A38E37C49F8EF622E8@B50854F0A9192E8EC6CDA126>
In-Reply-To: <BAY13-DAV4940zkHN5M0003d7a7@hotmail.com>
References: <BAY13-DAV4940zkHN5M0003d7a7@hotmail.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
Content-Transfer-Encoding: 7bit
Subject: Re: from Iranian IPv6 Task Force (guide)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,DATE_IN_PAST_06_12 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Seyed,

the next meeting of the IETF will be held in San Diego in the beginning of 
August 2004. It is open to all who wish to attend and are able to make the 
trip.

You are very welcome to attend; we do not call these meetings "summits" - 
there are other meetings that call themselves "summits", but these are not 
meetings of the IETF.

                    Harald Alvestrand


--On 14. juni 2004 21:51 +0430 Seyed Morteza Ladjevardi 
<sm_lad@hotmail.com> wrote:

>
>   Hello,
>   I am Seyed Morteza Lajevardi, president of Iranian IPv6 Task Force.
>   We want to participate in IETF SUMMIT.
>   Please guide us.
>   Kind Regards
>   President of  Iranian IPv6 Task Force
>   Seyed Morteza Lajevardi
>
> www.ipv6tf.org
> www.iripv6.org





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


From ietf-bounces@ietf.org  Tue Jun 15 08:30:15 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13779
	for <ietf-archive@ietf.org>; Tue, 15 Jun 2004 08:30:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BaD4y-0003J9-2w
	for ietf-archive@ietf.org; Tue, 15 Jun 2004 08:30:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaD3y-0002xN-00
	for ietf-archive@ietf.org; Tue, 15 Jun 2004 08:29:14 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BaD3K-0002aL-00; Tue, 15 Jun 2004 08:28:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BaCuz-0006uq-8B; Tue, 15 Jun 2004 08:19:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ba253-0006NR-Ma
	for ietf@megatron.ietf.org; Mon, 14 Jun 2004 20:45:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16426
	for <ietf@ietf.org>; Mon, 14 Jun 2004 20:45:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Ba251-0003qw-SG
	for ietf@ietf.org; Mon, 14 Jun 2004 20:45:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ba23w-0003E6-00
	for ietf@ietf.org; Mon, 14 Jun 2004 20:44:29 -0400
Received: from noxmail.sandelman.ottawa.on.ca ([205.150.200.166])
	by ietf-mx with esmtp (Exim 4.12) id 1Ba22H-0002c5-00
	for ietf@ietf.org; Mon, 14 Jun 2004 20:42:46 -0400
Received: from sandelman.ottawa.on.ca (root@marajade.sandelman.ottawa.on.ca
	[205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i5F0g9P05459
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK); Mon, 14 Jun 2004 20:42:10 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (mcr@marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i5F0g336028613
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 14 Jun 2004 20:42:04 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i5F0g20A028610; Mon, 14 Jun 2004 20:42:02 -0400
To: Donald Eastlake III <dee3@pothole.com>
In-Reply-To: Message from Donald Eastlake III <dee3@pothole.com> of "Sat,
	12 Jun 2004 16:37:33 EDT."
	<Pine.LNX.4.44.0406121633540.16767-100000@pothole.com> 
References: <Pine.LNX.4.44.0406121633540.16767-100000@pothole.com> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Date: Mon, 14 Jun 2004 20:42:02 -0400
Message-ID: <28609.1087260122@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Mailman-Approved-At: Tue, 15 Jun 2004 08:19:55 -0400
Cc: ietf@ietf.org
Subject: Re: STD series of documents 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,LINES_OF_YELLING 
	autolearn=no version=2.60

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


>>>>> "Donald" == Donald Eastlake <dee3@pothole.com> writes:
    Donald> I have long thought that the other document designations
    Donald> (STD, FYI, ...) are bound to continue to be confusing minor
    Donald> labels without much mind share as long as there documents
    Donald> are also RFCs. The only hope to get people to REALLY switch
    Donald> to using these new disgnations in general is to make those
    Donald> documents NOT be RFCs.

  I concur.

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  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

iQCVAwUBQM5F2IqHRg3pndX9AQHBIwP/UodcS6xR/lgTA8liMDlud29mZrkJbqrt
vwA0/jyh4qdw6NjE85WvwU4GX98lhPlrGIfpD+zkvpFO0U4hDd8JncpawRgA21bo
fTpQj6Kh88LXd1k2XjPA8yKOwflixtnx3fDnhZS5LtAYXjWKJzMOstzkfGT2506w
gouvqBEQcZc=
=h4tg
-----END PGP SIGNATURE-----

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


From ietf-bounces@ietf.org  Tue Jun 15 10:00:00 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18542
	for <ietf-archive@ietf.org>; Tue, 15 Jun 2004 10:00:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BaETp-0002qV-0O
	for ietf-archive@ietf.org; Tue, 15 Jun 2004 10:00:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaESp-0002Rg-00
	for ietf-archive@ietf.org; Tue, 15 Jun 2004 09:58:59 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BaERm-0001n5-00; Tue, 15 Jun 2004 09:57:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BaEJG-0004E3-TL; Tue, 15 Jun 2004 09:49:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BaEAk-0002Ry-Ba
	for ietf@megatron.ietf.org; Tue, 15 Jun 2004 09:40:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17411
	for <ietf@ietf.org>; Tue, 15 Jun 2004 09:40:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BaEAj-0003et-Kc
	for ietf@ietf.org; Tue, 15 Jun 2004 09:40:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaE9k-0003Kk-00
	for ietf@ietf.org; Tue, 15 Jun 2004 09:39:17 -0400
Received: from bay17-f36.bay17.hotmail.com ([64.4.43.86] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BaE9C-0002ze-00
	for ietf@ietf.org; Tue, 15 Jun 2004 09:38:43 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Tue, 15 Jun 2004 06:28:08 -0700
Received: from 209.151.129.82 by by17fd.bay17.hotmail.msn.com with HTTP;
	Tue, 15 Jun 2004 13:28:07 GMT
X-Originating-IP: [209.151.129.82]
X-Originating-Email: [dlj_canada@hotmail.com]
X-Sender: dlj_canada@hotmail.com
From: "David Lloyd-Jones" <dlj_canada@hotmail.com>
To: harald@alvestrand.no
Date: Tue, 15 Jun 2004 09:28:07 -0400
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <BAY17-F36FOgTtV7LKu00005c96@hotmail.com>
X-OriginalArrivalTime: 15 Jun 2004 13:28:08.0025 (UTC)
	FILETIME=[98A1F490:01C452DC]
Cc: ietf@ietf.org
Subject: RE: Planning (Re: "setting up the administrative structures we
	need")
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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




>From: Harald Tveit Alvestrand <harald@alvestrand.no>
>--On 9. juni 2004 10:00 -0400 David Lloyd-Jones <dlj_canada@hotmail.com> 
>wrote:
>
>>On this planet things are almost always set up without plans, and plansare 
>>almost always constructed ex post facto to justify whatever happened.
>
>not my experience.

Harald,

A single example would make this observation more credible. There certainly 
are areas of life in which the making of plans routinly precedes an action 
-- but they are almost always things of the most utterly routine kind. 
Building corporations make plans of the houses they are about to build, but 
they rarely make plans for the development of their businesses. Ordinary 
people sometimes write shopping lists before going to the supermarket, but 
this is rare, and other aspects of ordinary life is which people make the 
"detailed plans" that an earlier correspondent referred to are far rarer 
still.

>my favourite quote on planning is "the purpose of planning is so that you 
>can panic in time" - closely followed by "no plan survives first contact 
>with the enemy".

These two quotes are rather in the same spirit as my earlier post.

The point I wanted to make, without saying it too baldly, was that the 
messages about planning, on all sides, seemed to be posted in order exactly 
to avoid the issue people felt strongly about -- the question of whether 
there is any good reason to put the hiring of paid staff at the top of the 
common agenda.

There, I've said it baldly.

Since we agree that cute quotes have a valuable role in life, I am sorry 
that I cannot find the canonical form of that Law which states that an 
organization which puts its own organization high on the agenda is well 
along in tottering its last steps.

                                             Best,

                                                  -dlj.

_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN Premium   
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines


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


From ietf-bounces@ietf.org  Tue Jun 15 10:56:34 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23378
	for <ietf-archive@ietf.org>; Tue, 15 Jun 2004 10:56:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BaFMZ-0005Oc-Vl
	for ietf-archive@ietf.org; Tue, 15 Jun 2004 10:56:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaFGe-0004J8-00
	for ietf-archive@ietf.org; Tue, 15 Jun 2004 10:50:29 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BaFBm-0002wT-00; Tue, 15 Jun 2004 10:45:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BaEyn-0000r4-O4; Tue, 15 Jun 2004 10:32:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BaEqL-000874-So
	for ietf@megatron.ietf.org; Tue, 15 Jun 2004 10:23:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21070
	for <ietf@ietf.org>; Tue, 15 Jun 2004 10:23:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BaEqL-0003Dn-3X
	for ietf@ietf.org; Tue, 15 Jun 2004 10:23:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaEpS-0002ro-00
	for ietf@ietf.org; Tue, 15 Jun 2004 10:22:22 -0400
Received: from [162.33.195.162] (helo=wsmalky.com)
	by ietf-mx with smtp (Exim 4.12) id 1BaEoh-0002Ur-00
	for ietf@ietf.org; Tue, 15 Jun 2004 10:21:35 -0400
Date: Tue, 15 Jun 2004 10:22:20 -0500
To: "Ietf" <ietf@ietf.org>
From: "Cook" <cook@COOKREPORT.COM>
Message-ID: <ioftyxdtfjzypelfrny@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------axypgazvmhsmjgujkzhx"
Subject: Re: Incoming Message
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,HTML_MESSAGE autolearn=no 
	version=2.60

----------axypgazvmhsmjgujkzhx
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
 

<br>
</body></html>

----------axypgazvmhsmjgujkzhx
Content-Type: application/octet-stream; name="You_are_dismissed.hta"
Content-Disposition: attachment; filename="You_are_dismissed.hta"
Content-Transfer-Encoding: base64



----------axypgazvmhsmjgujkzhx
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

----------axypgazvmhsmjgujkzhx--




From ietf-bounces@ietf.org  Tue Jun 15 13:52:38 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04942
	for <ietf-archive@ietf.org>; Tue, 15 Jun 2004 13:52:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BaI6w-0003t5-Gs
	for ietf-archive@ietf.org; Tue, 15 Jun 2004 13:52:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaI5e-0003Uq-00
	for ietf-archive@ietf.org; Tue, 15 Jun 2004 13:51:18 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BaI4s-0002pr-00; Tue, 15 Jun 2004 13:50:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BaHw7-0002hN-OB; Tue, 15 Jun 2004 13:41:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BaHoB-0001RW-0q
	for ietf@megatron.ietf.org; Tue, 15 Jun 2004 13:33:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04154
	for <ietf@ietf.org>; Tue, 15 Jun 2004 13:33:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BaHo9-0004pB-S8
	for ietf@ietf.org; Tue, 15 Jun 2004 13:33:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaHnC-0004TA-00
	for ietf@ietf.org; Tue, 15 Jun 2004 13:32:15 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12) id 1BaHmJ-0003nm-00
	for ietf@ietf.org; Tue, 15 Jun 2004 13:31:19 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 6A69F61BB3; Tue, 15 Jun 2004 19:30:48 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 24658-03; Tue, 15 Jun 2004 19:30:47 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id 0B96E61A93; Tue, 15 Jun 2004 19:30:46 +0200 (CEST)
Date: Tue, 15 Jun 2004 10:29:20 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: David Lloyd-Jones <dlj_canada@hotmail.com>
Message-ID: <3A0E5757ADA16D17F72EA305@B50854F0A9192E8EC6CDA126>
In-Reply-To: <BAY17-F36FOgTtV7LKu00005c96@hotmail.com>
References: <BAY17-F36FOgTtV7LKu00005c96@hotmail.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: Planning (Re: "setting up the administrative structures we
 need")
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On 15. juni 2004 09:28 -0400 David Lloyd-Jones <dlj_canada@hotmail.com> 
wrote:

>> From: Harald Tveit Alvestrand <harald@alvestrand.no>
>> --On 9. juni 2004 10:00 -0400 David Lloyd-Jones <dlj_canada@hotmail.com>
>> wrote:
>>
>>> On this planet things are almost always set up without plans, and
>>> plansare  almost always constructed ex post facto to justify whatever
>>> happened.
>>
>> not my experience.
>
> Harald,
>
> A single example would make this observation more credible. There
> certainly are areas of life in which the making of plans routinly
> precedes an action -- but they are almost always things of the most
> utterly routine kind.

a trivial example - I don't know if you'll take this as supporting my 
theory or yours:

all IETF WGs start out with milestones saying when they expect to reach 
their goals - which are supposed to be rooted in some idea of a plan for 
how to get there.

the useful thing about milestones (if there is any useful thing) is that 
when we (far too often) fail to meet them, it's obvious that we aren't on 
the first plan any more, and we can re-schedule - which exposes to the rest 
of the world the fact that we won't deliver what we promised in time, which 
in turn may lead to THEM adjusting their expected schedules (or, more 
likely, gripe about the unreliable IETF that can't deliver specs in a 
timely manner).

Panic in time.

                       Harald




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


From ietf-bounces@ietf.org  Wed Jun 16 11:10:24 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04560
	for <ietf-archive@ietf.org>; Wed, 16 Jun 2004 11:10:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bac3S-0006kE-MK
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 11:10:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BabEZ-0006dJ-00
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 10:17:49 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Baae9-000126-02; Wed, 16 Jun 2004 09:40:09 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BaaZl-0006Al-Se; Wed, 16 Jun 2004 09:35:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Baa6o-0002Lo-SF; Wed, 16 Jun 2004 09:05:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BaUsZ-00073p-Gc
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 03:30:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19540
	for <ietf@ietf.org>; Wed, 16 Jun 2004 03:30:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BaUsX-0003ZV-5E
	for ietf@ietf.org; Wed, 16 Jun 2004 03:30:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaU5Q-0003Gz-00
	for ietf@ietf.org; Wed, 16 Jun 2004 02:39:52 -0400
Received: from cougar.icir.org ([192.150.187.76])
	by ietf-mx with esmtp (Exim 4.12) id 1BaS8f-0005x2-00
	for ietf@ietf.org; Wed, 16 Jun 2004 00:35:05 -0400
Received: from cougar.icir.org (localhost [127.0.0.1])
	by cougar.icir.org (8.12.9p1/8.12.8) with ESMTP id i5G4YjCS069427;
	Tue, 15 Jun 2004 21:34:45 -0700 (PDT)
	(envelope-from floyd@cougar.icir.org)
Message-Id: <200406160434.i5G4YjCS069427@cougar.icir.org>
To: Rajat <myself_rajat@yahoo.com>
From: Sally Floyd <floyd@icir.org>
Date: Tue, 15 Jun 2004 21:34:45 -0700
X-Mailman-Approved-At: Wed, 16 Jun 2004 09:05:40 -0400
Cc: Alberto Medina <medina@icsi.berkeley.edu>, ietf@ietf.org,
        Mark Allman <mallman@icir.org>
Subject: Re: Problem of blocking ICMP packets 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

Alberto Medina, Mark Allman, and I have a draft paper on
"Measuring the Evolution of Transport Protocols in the Internet"
that has a section (Section V.B.) on Path MTU Discovery.
>From the paper:

"Table X shows that PMTUD is used and succeeded for slightly less
than half of the [web] servers on our list.  For 31\% of the servers
on our list, the server did not attempt Path MTU Discovery.  For
18\% of the servers on our list, Path MTU Discovery failed, presumably
because of middleboxes that block ICMP packets on the path to the
web server."
...
"Since a non-trivial number of network elements discard well-known
ICMP packets the results of our tests do not offer hope for protocol
designers proposing to use new ICMP messages to signal various
network path properties to end systems (e.g., for explicit corruption
notification, handoff or outage notification, etc.)."

We would appreciate any feedback, either on the paper, or on other
measurement studies that would be useful on sometimes-unanticipated
interactions between transport protocols and routers or middleboxes.

The paper and test code are both available from 
"http://www.icir.org/tbit/".

- Sally
http://www.icir.org/floyd/


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


From ietf-bounces@ietf.org  Wed Jun 16 14:57:44 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28888
	for <ietf-archive@ietf.org>; Wed, 16 Jun 2004 14:57:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BafbS-00001a-H0
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 14:57:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaeUH-0007mj-00
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 13:46:14 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BadrO-0002co-00; Wed, 16 Jun 2004 13:06:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BadUB-0000fK-V3; Wed, 16 Jun 2004 12:42:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bad4t-0005yq-UF
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 12:15:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16021
	for <ietf@ietf.org>; Wed, 16 Jun 2004 12:15:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bad4q-0001xD-5W
	for ietf@ietf.org; Wed, 16 Jun 2004 12:15:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bacl2-0006KU-00
	for ietf@ietf.org; Wed, 16 Jun 2004 11:55:25 -0400
Received: from nr2baymi.bay.mi.charter.com ([24.247.24.43])
	by ietf-mx with esmtp (Exim 4.12) id 1BacIr-0001Mr-00
	for ietf@ietf.org; Wed, 16 Jun 2004 11:26:17 -0400
Received: from hamburg.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 ESMTP id
	i5GFPqL18626; Wed, 16 Jun 2004 11:25:53 -0400 (EDT)
Received: by hamburg.alientech.net (Postfix, from userid 1001)
	id 139E81165C1; Wed, 16 Jun 2004 11:25:50 -0400 (EDT)
Received: from MSAUVE-2.flatsurface.com (unknown [47.186.18.74])
	by hamburg.alientech.net (Postfix) with ESMTP
	id 707EC1165E4; Wed, 16 Jun 2004 11:25:46 -0400 (EDT)
Message-Id: <6.1.1.1.0.20040616111814.02d518b0@mjs.alientech.net>
X-Sender: msauve@mjs.alientech.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Wed, 16 Jun 2004 11:23:44 -0400
To: Sally Floyd <floyd@icir.org>
From: ietf@flatsurface.com (Mike S)
In-Reply-To: <200406160434.i5G4YjCS069427@cougar.icir.org>
References: <200406160434.i5G4YjCS069427@cougar.icir.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: Alberto Medina <medina@icsi.berkeley.edu>, ietf@ietf.org,
        Rajat <myself_rajat@yahoo.com>, Mark Allman <mallman@icir.org>
Subject: Re: Problem of blocking ICMP packets
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

At 12:34 AM 6/16/2004, Sally Floyd wrote...
>Alberto Medina, Mark Allman, and I have a draft paper on
>"Measuring the Evolution of Transport Protocols in the Internet"
>that has a section (Section V.B.) on Path MTU Discovery.
>>From the paper:
>
>"Table X shows that PMTUD is used and succeeded for slightly less
>than half of the [web] servers on our list.  For 31\% of the servers
>on our list, the server did not attempt Path MTU Discovery.  For
>18\% of the servers on our list, Path MTU Discovery failed, presumably
>because of middleboxes that block ICMP packets on the path to the
>web server."

Any router configured to block ICMP packets is, quite simply,
in violation of RFC792 (STD5), which clearly states "ICMP is actually 
an integral part of IP, and must be implemented by every IP module." 
For a router, "implemented" means forwarded to the destinations next
hop.

So the fact is, by blocking ICMP, such ISPs have broken IP connectivity, 
and can no longer claim to be providing Internet (IP) service.


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


From ietf-bounces@ietf.org  Wed Jun 16 15:55:08 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11064
	for <ietf-archive@ietf.org>; Wed, 16 Jun 2004 15:55:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BagV0-00032m-9s
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 15:55:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BagOv-0001Md-00
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 15:48:50 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bag9g-0006Ng-00; Wed, 16 Jun 2004 15:33:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bafw8-0007NC-BW; Wed, 16 Jun 2004 15:19:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Baffn-0003iR-Vt
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 15:02:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29995
	for <ietf@ietf.org>; Wed, 16 Jun 2004 15:02:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Baffj-0000nU-Om
	for ietf@ietf.org; Wed, 16 Jun 2004 15:02:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Baedi-0001Mx-00
	for ietf@ietf.org; Wed, 16 Jun 2004 13:55:59 -0400
Received: from mail5.microsoft.com ([131.107.3.121])
	by ietf-mx with esmtp (Exim 4.12) id 1Bae5B-0004St-00
	for ietf@ietf.org; Wed, 16 Jun 2004 13:20:17 -0400
Received: from inet-vrs-05.redmond.corp.microsoft.com ([157.54.6.157]) by
	mail5.microsoft.com with Microsoft SMTPSVC(6.0.3790.1039); 
	Wed, 16 Jun 2004 10:19:47 -0700
Received: from 157.54.8.23 by inet-vrs-05.redmond.corp.microsoft.com
	(InterScan E-Mail VirusWall NT); Wed, 16 Jun 2004 10:19:49 -0700
Received: from RED-IMC-04.redmond.corp.microsoft.com ([157.54.2.168]) by
	inet-hub-01.redmond.corp.microsoft.com with Microsoft
	SMTPSVC(6.0.3790.0); Wed, 16 Jun 2004 10:19:21 -0700
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); Wed, 16 Jun 2004 10:19:48 -0700
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); Wed, 16 Jun 2004 10:19:57 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 16 Jun 2004 10:19:32 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA09911B65@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Problem of blocking ICMP packets 
Thread-Index: AcRTpsHSfEnkCavhQfCz0tiz47eDNwAHgJRQ
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Sally Floyd" <floyd@icir.org>, "Rajat" <myself_rajat@yahoo.com>
X-OriginalArrivalTime: 16 Jun 2004 17:19:57.0562 (UTC)
	FILETIME=[25C69DA0:01C453C6]
Content-Transfer-Encoding: quoted-printable
Cc: Alberto Medina <medina@icsi.berkeley.edu>, ietf@ietf.org,
        Mark Allman <mallman@icir.org>
Subject: RE: Problem of blocking ICMP packets 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> "Since a non-trivial number of network elements discard well-known
> ICMP packets the results of our tests do not offer hope for protocol
> designers proposing to use new ICMP messages to signal various
> network path properties to end systems (e.g., for explicit corruption
> notification, handoff or outage notification, etc.)."

Yes, this is a very serious issue. Very often, a server that is
configured for a service will open exactly the port necessary for that
service, and drop all other traffic. For example, a web server will
accept TCP packets sent to ports 80 and 443, but it will either drop
everything else, or be located behind a firewall that drops everything
else.=20

This restriction affects the way we design protocol extensions. I see
that as an argument for "in-band" signaling, e.g. parameters in TCP
packets or in IP headers of TCP packets, by opposition to "out of band",
e.g. ICMP messages.=20

-- Christian Huitema

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


From ietf-bounces@ietf.org  Wed Jun 16 16:34:46 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14569
	for <ietf-archive@ietf.org>; Wed, 16 Jun 2004 16:34:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bah7M-0000po-8e
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 16:34:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bah6M-0000Td-00
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 16:33:42 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bah5M-0007bE-00; Wed, 16 Jun 2004 16:32:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bagy9-0004BZ-AF; Wed, 16 Jun 2004 16:25:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bafsx-00052y-R5
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 15:15:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03540
	for <ietf@ietf.org>; Wed, 16 Jun 2004 15:15:46 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bafst-000396-P2
	for ietf@ietf.org; Wed, 16 Jun 2004 15:15:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Baf5F-0003p4-00
	for ietf@ietf.org; Wed, 16 Jun 2004 14:24:26 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12) id 1Bae8J-0004jv-00
	for ietf@ietf.org; Wed, 16 Jun 2004 13:23:31 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by mx2.foretec.com with esmtp (Exim 4.24) id 1Bae8L-0006Xa-DL
	for ietf@ietf.org; Wed, 16 Jun 2004 13:23:33 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta5/8.13.0.Beta5) with ESMTP id
	i5GHNeDH022341; Wed, 16 Jun 2004 13:23:40 -0400
Message-Id: <200406161723.i5GHNeDH022341@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)
In-Reply-To: Your message of "Wed, 16 Jun 2004 11:23:44 EDT."
	<6.1.1.1.0.20040616111814.02d518b0@mjs.alientech.net> 
References: <200406160434.i5G4YjCS069427@cougar.icir.org>
	<6.1.1.1.0.20040616111814.02d518b0@mjs.alientech.net>
Mime-Version: 1.0
Date: Wed, 16 Jun 2004 13:23:40 -0400
Cc: Alberto Medina <medina@icsi.berkeley.edu>, Mark Allman <mallman@icir.org>,
        Sally Floyd <floyd@icir.org>, Rajat <myself_rajat@yahoo.com>,
        ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0236059568=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,NO_REAL_NAME autolearn=no 
	version=2.60

--===============0236059568==
Content-Type: multipart/signed; boundary="==_Exmh_1322286472P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Wed, 16 Jun 2004 11:23:44 EDT, Mike S said:

> Any router configured to block ICMP packets is, quite simply,
> in violation of RFC792 (STD5), which clearly states "ICMP is actually 
> an integral part of IP, and must be implemented by every IP module." 
> For a router, "implemented" means forwarded to the destinations next
> hop.
> 
> So the fact is, by blocking ICMP, such ISPs have broken IP connectivity, 
> and can no longer claim to be providing Internet (IP) service.

Be careful there - that's uncomfortably close to saying that every firewall
in existence is in violation of the RFCs, because they intentionally don't
make a best-effort attempt to deliver every packet (I know of no vendors
whos gear *can't* forward ICMP - but know plenty that provide knobs
to prevent it under administrative control (i.e. a firewall))...

An even more annoying problem is when our site sends a packet with
the DF bit set, it hits a tunnel near the far end - and the ICMP returned
has an RFC1918 source address (You tier-1 and tier-2 who number their
links out of 1918 know who you are..;).  The ICMP is then dropped on
the return path by a router properly implementing martian filtering...

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

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

iD8DBQFA0IIbcC3lWbTT17ARArxoAKC3+Zy5a/MNOhzNlcxue6o52gCtKgCdFbrV
ozoMHVLzOyB88BJVegncREc=
=4tVI
-----END PGP SIGNATURE-----

--==_Exmh_1322286472P--


--===============0236059568==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0236059568==--



From ietf-bounces@ietf.org  Wed Jun 16 18:04:56 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21338
	for <ietf-archive@ietf.org>; Wed, 16 Jun 2004 18:04:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BaiWc-0006y1-GV
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 18:04:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaiRr-0005ZH-00
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 18:00:00 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BaiOv-0004T6-00; Wed, 16 Jun 2004 17:56:57 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BaiNn-00078O-Jm; Wed, 16 Jun 2004 17:55:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bahho-00081b-61; Wed, 16 Jun 2004 17:12:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BagBY-0007LN-Vz
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 15:35:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08215
	for <ietf@ietf.org>; Wed, 16 Jun 2004 15:34:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BagBU-0006pc-Vj
	for ietf@ietf.org; Wed, 16 Jun 2004 15:34:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BafkE-0001XT-00
	for ietf@ietf.org; Wed, 16 Jun 2004 15:06:47 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1Baekc-0001xG-00
	for ietf@ietf.org; Wed, 16 Jun 2004 14:03:07 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i5GI2ZcT045443
	for ietf@ietf.org env-from <vjs>;
	Wed, 16 Jun 2004 12:02:35 -0600 (MDT)
Date: Wed, 16 Jun 2004 12:02:35 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200406161802.i5GI2ZcT045443@calcite.rhyolite.com>
To: ietf@ietf.org
References: <6.1.1.1.0.20040616111814.02d518b0@mjs.alientech.net>
Subject: Re: Problem of blocking ICMP packets
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

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


> So the fact is, by blocking ICMP, such ISPs have broken IP connectivity, 
> and can no longer claim to be providing Internet (IP) service.

I agree, but which flavor of other than "Full Internet Connectivity"
would it be?  Does
http://www.ietf.org/internet-drafts/draft-klensin-ip-service-terms-02.txt
need a category of "Public address, stupid filtering"?
Or is "Client only, public address" close enough?

Many people who install or defend such stupid filters are offended by
the observation that they are not doing real IP.  Labelling such
filtered access as what it is or at least something other than "Full
Internet Connectivity" would reduce its popularity.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Wed Jun 16 18:05:12 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21389
	for <ietf-archive@ietf.org>; Wed, 16 Jun 2004 18:05:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BaiWs-00077i-G0
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 18:05:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaiRz-0005bw-00
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 18:00:08 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BaiOx-0004T6-02; Wed, 16 Jun 2004 17:56:59 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BaiM2-0006gB-AL; Wed, 16 Jun 2004 17:53:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bahhk-00080w-Ne; Wed, 16 Jun 2004 17:12:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BagB0-0007I4-Hp
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 15:34:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08135
	for <ietf@ietf.org>; Wed, 16 Jun 2004 15:34:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BagAw-0006jV-BJ
	for ietf@ietf.org; Wed, 16 Jun 2004 15:34:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bafj7-0001LH-00
	for ietf@ietf.org; Wed, 16 Jun 2004 15:05:39 -0400
Received: from cougar.icir.org ([192.150.187.76])
	by ietf-mx with esmtp (Exim 4.12) id 1Baei3-0001mJ-00
	for ietf@ietf.org; Wed, 16 Jun 2004 14:00:27 -0400
Received: from cougar.icir.org (localhost [127.0.0.1])
	by cougar.icir.org (8.12.9p1/8.12.8) with ESMTP id i5GI0TCS079218;
	Wed, 16 Jun 2004 11:00:29 -0700 (PDT)
	(envelope-from floyd@cougar.icir.org)
Message-Id: <200406161800.i5GI0TCS079218@cougar.icir.org>
To: "Christian Huitema" <huitema@windows.microsoft.com>
From: Sally Floyd <floyd@icir.org>
Date: Wed, 16 Jun 2004 11:00:29 -0700
Cc: Alberto Medina <medina@icsi.berkeley.edu>, ietf@ietf.org,
        Rajat <myself_rajat@yahoo.com>, Mark Allman <mallman@icir.org>
Subject: Re: Problem of blocking ICMP packets 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

Christian -

>This restriction affects the way we design protocol extensions. I see
>that as an argument for "in-band" signaling, e.g. parameters in TCP
>packets or in IP headers of TCP packets, by opposition to "out of band",
>e.g. ICMP messages. 

Yes, that is the thought behind things like the proposal for QuickStart
("http://www.icir.org/floyd/papers/draft-amit-quick-start-02.txt"),
which would use an IP Option in the TCP SYN packet to find out if
the TCP sender would start off with a higher initial sending rate.

However, there is another section of our recent measurement paper,
Section V.C., with our measurements of paths that block known
and/or unknown IP options on paths to web servers:

 "As Figure 5 shows, in many cases no connection was established when
 the [IP] Record Route Option or the [IP] Timestamp Option was included in 
 the SYN packet.  When IP Option X [a new IP Option; e.g., QuickStart]
 is included in the SYN segment, the connection was not established
 to over 70% of the web servers tested.  This does not bode well for
 the deployment of new IP options in the Internet."

Of course, this involves IP Options on SYN packets on the path *to*
the web server.  If something like QuickStart was ever standardized,
the IP Option would only be needed on the path *from* the web server
to the browser.  Presumeably if the web server wanted to use something
like QuickStart, it could have the firewall configured to allow the
IP QuickStart Option not to be blocked on the outgoing SYN packet?
And the receiver could have the firewall on their end configured
to allow the IP QuickStart option on the incoming SYN packet to
pass?  I don't know.  However, the fact that connections fail today
when unknown IP Options are used on the SYN from the browser to the
web server does not *necessarily* mean that there is no hope for
using IP Options for in-band signalling.

The good news is that known or unknown TCP options are not blocked
on paths to web servers.  Or at any rate, the connection still
succeeds in being established...

- Sally
Measuring the Evolution of Transport Protocols in the Internet:
http://www.icir.org/tbit/

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


From ietf-bounces@ietf.org  Wed Jun 16 18:06:12 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21591
	for <ietf-archive@ietf.org>; Wed, 16 Jun 2004 18:06:12 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BaiXq-0007KV-Iz
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 18:06:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaiSp-0005oL-00
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 18:01:00 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BaiP9-0004hb-00; Wed, 16 Jun 2004 17:57:11 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BaiPD-0007Wm-Gz; Wed, 16 Jun 2004 17:57:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bahi9-00084L-QD; Wed, 16 Jun 2004 17:12:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BagFp-0007mu-Bb
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 15:39:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09094
	for <ietf@ietf.org>; Wed, 16 Jun 2004 15:39:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BagFl-0007ZY-8H
	for ietf@ietf.org; Wed, 16 Jun 2004 15:39:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bafw4-0003kR-00
	for ietf@ietf.org; Wed, 16 Jun 2004 15:19:01 -0400
Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu)
	by ietf-mx with esmtp (Exim 4.12) id 1BafDC-0004ZR-00
	for ietf@ietf.org; Wed, 16 Jun 2004 14:32:38 -0400
Received: by mail.eecis.udel.edu (Postfix, from userid 62)
	id 8D23032BC3; Wed, 16 Jun 2004 14:27:59 -0400 (EDT)
Received: from stimpy.eecis.udel.edu (stimpy.eecis.udel.edu [128.4.40.17])
	by mail.eecis.udel.edu (Postfix) with ESMTP
	id DF87B32BA2; Wed, 16 Jun 2004 14:27:57 -0400 (EDT)
Date: Wed, 16 Jun 2004 14:27:57 -0400 (EDT)
From: "Armando L. Caro Jr." <me@armandocaro.net>
X-X-Sender: acaro@stimpy.eecis.udel.edu
To: Mike S <ietf@flatsurface.com>
In-Reply-To: <6.1.1.1.0.20040616111814.02d518b0@mjs.alientech.net>
Message-ID: <Pine.GSO.4.58.0406161417420.23912@stimpy.eecis.udel.edu>
References: <200406160434.i5G4YjCS069427@cougar.icir.org>
	<6.1.1.1.0.20040616111814.02d518b0@mjs.alientech.net>
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"
Cc: Alberto Medina <medina@icsi.berkeley.edu>, Mark Allman <mallman@icir.org>,
        Sally Floyd <floyd@icir.org>, Rajat <myself_rajat@yahoo.com>,
        ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Wed, 16 Jun 2004, Mike S wrote:

> Any router configured to block ICMP packets is, quite simply,
> in violation of RFC792 (STD5), which clearly states "ICMP is actually
> an integral part of IP, and must be implemented by every IP module."
> For a router, "implemented" means forwarded to the destinations next
> hop.
>
> So the fact is, by blocking ICMP, such ISPs have broken IP connectivity,
> and can no longer claim to be providing Internet (IP) service.
      ^^^^^^^^^^^^^^^^^^^

Actually, the fact is that they _can_ and they _do_ claim to provide IP
service even though they _shouldn't_. So we should be searching for ways
to discourage ISPs from blocking ICMP. We could spend energy replacing
each of ICMP's uses (such as PMTU discovery), but that would probably just
split the original problem (ICMP's security vulnerabilities) into smaller
problems and push them into other areas.

~armando

0--                                              --0
| Armando L. Caro Jr.  |  Protocol Engineering Lab |
| www.armandocaro.net  |    University of Delaware |
0--                                              --0

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


From ietf-bounces@ietf.org  Wed Jun 16 18:27:53 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25193
	for <ietf-archive@ietf.org>; Wed, 16 Jun 2004 18:27:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Baisp-0006Fi-Nm
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 18:27:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Baipa-0005H3-00
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 18:24:30 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BainR-0004Uz-04; Wed, 16 Jun 2004 18:22:17 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Baijj-00044q-6l; Wed, 16 Jun 2004 18:18:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bahiw-0008JS-NS; Wed, 16 Jun 2004 17:13:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bah3k-0006ed-Sf
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 16:31:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14308
	for <ietf@ietf.org>; Wed, 16 Jun 2004 16:30:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bah3g-0007Dp-P6
	for ietf@ietf.org; Wed, 16 Jun 2004 16:30:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bah2o-0006rl-00
	for ietf@ietf.org; Wed, 16 Jun 2004 16:30:02 -0400
Received: from noxmail.sandelman.ottawa.on.ca ([205.150.200.166])
	by ietf-mx with esmtp (Exim 4.12) id 1Bah2H-0006Vh-00
	for ietf@ietf.org; Wed, 16 Jun 2004 16:29:29 -0400
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca
	[205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i5GKSqP26384
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK); Wed, 16 Jun 2004 16:28:53 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (mcr@marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i5GKSq36009305
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 16 Jun 2004 16:28:53 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i5GKSpLj009302; Wed, 16 Jun 2004 16:28:51 -0400
To: "Christian Huitema" <huitema@windows.microsoft.com>
In-Reply-To: Message from "Christian Huitema" <huitema@windows.microsoft.com> 
	of "Wed, 16 Jun 2004 10:19:32 PDT."
	<DAC3FCB50E31C54987CD10797DA511BA09911B65@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References: <DAC3FCB50E31C54987CD10797DA511BA09911B65@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Date: Wed, 16 Jun 2004 16:28:51 -0400
Message-ID: <9301.1087417731@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Cc: Alberto Medina <medina@icsi.berkeley.edu>, Mark Allman <mallman@icir.org>,
        Sally Floyd <floyd@icir.org>, Rajat <myself_rajat@yahoo.com>,
        ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,LINES_OF_YELLING 
	autolearn=no version=2.60

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


>>>>> "Christian" == Christian Huitema <huitema@windows.microsoft.com> writes:
    Christian> This restriction affects the way we design protocol
    Christian> extensions. I see that as an argument for "in-band"
    Christian> signaling, e.g. parameters in TCP packets or in IP
    Christian> headers of TCP packets, by opposition to "out of band",
    Christian> e.g. ICMP messages.

  But, that doesn't work either.
  The boxes that are responsible for 90% of the ICMP lossage were also 
intolerant of the ECN options in TCP, and pretty much all TCP options in
general.

  The boxes are broken.
  The faster we make this clear, the better.

  The biggest mistake we made with ICMP (and ICMPv6) was in assigning 
an IP-level protocol number to it. We should have done it with IP
options instead. That would make it clear that the information carried
by ICMP is really part of layer 3, rather than being some new layer-4.

  I don't have a fix for this, alas. I think the ICMP design was very
elegant. The problem has been a decade of firewall deployment done by people
who didn't understand the protocols. This can't be easily reversed.

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  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

iQCVAwUBQNCtgIqHRg3pndX9AQGhHAQAvWhae5RcpaNrX/1+ciuDKMX5bSordhMA
LXMADCkjMTH63e+91qMiG+kSqyDdPs7qHxppjPHXLZ2YgFwAU0CvjKhaV95Q3PJI
BMq43dPb4Veh3TaNKvLKkJmN1oli2uPV+i0fArq4plXXM7H2mBPeg+bQw9ckf/et
w8HQ/Vct9AE=
=FjVk
-----END PGP SIGNATURE-----

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


From ietf-bounces@ietf.org  Wed Jun 16 18:44:23 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27076
	for <ietf-archive@ietf.org>; Wed, 16 Jun 2004 18:44:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Baj8o-0004tG-E9
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 18:44:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Baj80-0004UM-00
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 18:43:32 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Baj76-000402-00; Wed, 16 Jun 2004 18:42:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Baim3-0004il-4W; Wed, 16 Jun 2004 18:20:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bai0p-0005MB-3Y
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 17:32:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17694
	for <ietf@ietf.org>; Wed, 16 Jun 2004 17:32:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bai0l-00047W-0H
	for ietf@ietf.org; Wed, 16 Jun 2004 17:31:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BahzE-0003JM-00
	for ietf@ietf.org; Wed, 16 Jun 2004 17:30:24 -0400
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx with esmtp (Exim 4.12) id 1BahxT-0002dH-00
	for ietf@ietf.org; Wed, 16 Jun 2004 17:28:35 -0400
Received: from ehsco.com (ferret.corp.ntrg.com [207.65.71.20])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "Eric A. Hall",
	Issuer "Network Technology Research Group Certificate Authority"
	(verified OK))
	by goose.ehsco.com (Postfix ) with ESMTP id 42DB65FA85;
	Wed, 16 Jun 2004 16:28:37 -0500 (CDT)
Message-ID: <40D0BB6A.1050205@ehsco.com>
Date: Wed, 16 Jun 2004 16:28:10 -0500
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: Christian Huitema <huitema@windows.microsoft.com>
References: <DAC3FCB50E31C54987CD10797DA511BA09911B65@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA09911B65@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: Alberto Medina <medina@icsi.berkeley.edu>, Mark Allman <mallman@icir.org>,
        Sally Floyd <floyd@icir.org>, Rajat <myself_rajat@yahoo.com>,
        ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit


On 6/16/2004 12:19 PM, Christian Huitema wrote:

> This restriction affects the way we design protocol extensions.

said restrictions on extensions apply to TCP as well

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

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


From ietf-bounces@ietf.org  Wed Jun 16 19:02:46 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27848
	for <ietf-archive@ietf.org>; Wed, 16 Jun 2004 19:02:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BajQb-0003Cv-0P
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 19:02:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BajNC-0002Ii-00
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 18:59:15 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BajLm-0001jN-00; Wed, 16 Jun 2004 18:57:46 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BajJy-0005Hf-1y; Wed, 16 Jun 2004 18:55:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Baj21-0003Uy-LP; Wed, 16 Jun 2004 18:37:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BaieF-0008Vn-85
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 18:12:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22978
	for <ietf@ietf.org>; Wed, 16 Jun 2004 18:12:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BaieB-0001Fk-30
	for ietf@ietf.org; Wed, 16 Jun 2004 18:12:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Baiam-0000Jj-00
	for ietf@ietf.org; Wed, 16 Jun 2004 18:09:13 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1BaiWA-0006Xc-00
	for ietf@ietf.org; Wed, 16 Jun 2004 18:04:26 -0400
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 i5GM3xSc008014
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Wed, 16 Jun 2004 18:04:00 -0400
Date: Wed, 16 Jun 2004 18:03:59 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: ietf@ietf.org
Message-ID: <Pine.LNX.4.44.0406161800430.6106-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

I've noticed that Rob Austein continues to use sra@isc.org for his work as
WG co-chair.  I think I've been very patient, and have held off on legal
recourse so far.

Dean Anderson
Av8 Internet, Inc

---------- Forwarded message ----------
Date: Thu, 20 May 2004 14:14:39 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Dean Anderson <dean@av8.com>
Cc: harald@alvestrand.no, ietf@ietf.org
Subject: Re: Response to complaint from Dean Anderson

On Wed, 19 May 2004 23:42:01 -0400 (EDT)
Dean Anderson <dean@av8.com> wrote:

> On Tue, 18 May 2004, Harald Tveit Alvestrand wrote:
> 

<snip - whole lot of legal stuff that I don't have time to
read - I've got a few thousand RFCs to go ...>

Firstly, let me say that it is really sad that legalease, legal
council and legal positions have appeared on an IETF mailing
list to the extent we've seen. I've understood that the IETF was
all about best technical solutions and positions, not best legal
solutions and positions.

Dean, I'm in no position to implement this as a solution (nor
have I spent time thinking about how hard or easy it
would be to implement), however, presuming that @ietf.org doesn't
implement MTA blocking via methods such as SORBS, and I don't
think they do, would you be happy if all people who have official
IETF positions (eg. area advisor, working group chair, etc) had
@ietf.org email addresses, and used those for any IETF related
correspondence ?

Regards,
Mark.

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


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


From ietf-bounces@ietf.org  Wed Jun 16 20:11:59 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03227
	for <ietf-archive@ietf.org>; Wed, 16 Jun 2004 20:11:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BakVY-0006nH-7C
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 20:11:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BakUd-0006R9-00
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 20:11:00 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BakTq-0005i9-00; Wed, 16 Jun 2004 20:10:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BakF4-0007DS-MP; Wed, 16 Jun 2004 19:54:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bak8V-0005Gi-BL
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 19:48:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01991
	for <ietf@ietf.org>; Wed, 16 Jun 2004 19:48:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bak8Q-0005bX-TB
	for ietf@ietf.org; Wed, 16 Jun 2004 19:48:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bak7c-0005Ei-00
	for ietf@ietf.org; Wed, 16 Jun 2004 19:47:13 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12) id 1Bak6q-0004qh-00
	for ietf@ietf.org; Wed, 16 Jun 2004 19:46:24 -0400
Received: (qmail 7605 invoked from network); 16 Jun 2004 23:43:35 -0000
Received: from yahoobb219001188027.bbtec.net (HELO necom830.hpcl.titech.ac.jp)
	(219.1.188.27)
	by necom830.hpcl.titech.ac.jp with SMTP; 16 Jun 2004 23:43:35 -0000
Message-ID: <40D0DCF8.8090407@necom830.hpcl.titech.ac.jp>
Date: Thu, 17 Jun 2004 08:51:20 +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: Sally Floyd <floyd@icir.org>
References: <200406161800.i5GI0TCS079218@cougar.icir.org>
In-Reply-To: <200406161800.i5GI0TCS079218@cougar.icir.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: Christian Huitema <huitema@windows.microsoft.com>,
        Alberto Medina <medina@icsi.berkeley.edu>, ietf@ietf.org,
        Rajat <myself_rajat@yahoo.com>, Mark Allman <mallman@icir.org>
Subject: Re: Problem of blocking ICMP packets
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Sally Floyd;

>  "As Figure 5 shows, in many cases no connection was established when
>  the [IP] Record Route Option or the [IP] Timestamp Option was included in 
>  the SYN packet.  When IP Option X [a new IP Option; e.g., QuickStart]
>  is included in the SYN segment, the connection was not established
>  to over 70% of the web servers tested.  This does not bode well for
>  the deployment of new IP options in the Internet."

It implies that mobile IPv6 depndeing on routing header
may not work.

> If something like QuickStart was ever standardized,
> the IP Option would only be needed on the path *from* the web server
> to the browser.  Presumeably if the web server wanted to use something
> like QuickStart, it could have the firewall configured to allow the
> IP QuickStart Option not to be blocked on the outgoing SYN packet?
> And the receiver could have the firewall on their end configured
> to allow the IP QuickStart option on the incoming SYN packet to
> pass?  I don't know.

Presumeably if the web server wanted to use something
like PMTUD, it could have the firewall configured to allow related
ICMP not to be blocked. And the receiver could have the firewall
on their end configured to allow the ICMP to pass. You know.

> However, the fact that connections fail today
> when unknown IP Options are used on the SYN from the browser to the
> web server does not *necessarily* mean that there is no hope for
> using IP Options for in-band signalling.

Same for PMTUD with out-band signalling.

> The good news is that known or unknown TCP options are not blocked
> on paths to web servers.  Or at any rate, the connection still
> succeeds in being established...

As long as routers are not required to look into TCP options,
they are likely to interoperate even with complex TCP options.

						Masataka Ohta


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


From ietf-bounces@ietf.org  Wed Jun 16 23:22:15 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11782
	for <ietf-archive@ietf.org>; Wed, 16 Jun 2004 23:22:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BanTh-00047s-Nr
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 23:22:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BanRo-0003UG-00
	for ietf-archive@ietf.org; Wed, 16 Jun 2004 23:20:17 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BanQf-0002dq-00; Wed, 16 Jun 2004 23:19:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BanIQ-0002b4-S9; Wed, 16 Jun 2004 23:10:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BanDk-0001i6-NB
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 23:05:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10790
	for <ietf@ietf.org>; Wed, 16 Jun 2004 23:05:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BanDe-0006ht-3w
	for ietf@ietf.org; Wed, 16 Jun 2004 23:05:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BanBG-000629-00
	for ietf@ietf.org; Wed, 16 Jun 2004 23:03:10 -0400
Received: from mail.flarion.com ([63.103.94.23] helo=ftmailgfi.HQ.Flarion.com)
	by ietf-mx with esmtp (Exim 4.12) id 1Ban95-0005Ib-00
	for ietf@ietf.org; Wed, 16 Jun 2004 23:00:55 -0400
Received: from ftmail2000.HQ.Flarion.com ([10.10.1.120]) by
	ftmailgfi.HQ.Flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Wed, 16 Jun 2004 23:00:23 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 16 Jun 2004 23:00:23 -0400
Message-ID: <F4410B91C6CC314F9582B1A8E91DC928BEEC4A@ftmail2000>
Thread-Topic: Problem of blocking ICMP packets
Thread-Index: AcRT/2JuGVBfIcWARCay4ov9jQ/t5gAFc3fw
From: "Soliman Hesham" <H.Soliman@flarion.com>
To: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>,
        "Sally Floyd" <floyd@icir.org>
X-OriginalArrivalTime: 17 Jun 2004 03:00:23.0534 (UTC)
	FILETIME=[3BAC38E0:01C45417]
Content-Transfer-Encoding: quoted-printable
Cc: Christian Huitema <huitema@windows.microsoft.com>,
        Alberto Medina <medina@icsi.berkeley.edu>, ietf@ietf.org,
        Rajat <myself_rajat@yahoo.com>, Mark Allman <mallman@icir.org>
Subject: RE: Problem of blocking ICMP packets
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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


 > >  "As Figure 5 shows, in many cases no connection was=20
 > established when
 > >  the [IP] Record Route Option or the [IP] Timestamp Option=20
 > was included in=20
 > >  the SYN packet.  When IP Option X [a new IP Option; e.g.,=20
 > QuickStart]
 > >  is included in the SYN segment, the connection was not established
 > >  to over 70% of the web servers tested.  This does not=20
 > bode well for
 > >  the deployment of new IP options in the Internet."
 >=20
 > It implies that mobile IPv6 depndeing on routing header
 > may not work.

=3D> This statement is true IFF people assume that=20
Record Route Option =3D=3D Routing header type 2 used for MIPv6.
Of course that is not true because there are security
implications for using routing header type 2 and an
assumption that the end node will verfiy such use. Moreover,
RH type 2 will not impact other nodes behind the FW
if used in a malicious way. All this points to two things:
1. The two are not equivalent, and
2. We need to make sure that network admins know (1).=20

Hesham


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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


From ietf-bounces@ietf.org  Thu Jun 17 04:28:30 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09617
	for <ietf-archive@ietf.org>; Thu, 17 Jun 2004 04:28:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BasG3-0004vu-CT
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 04:28:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BasFH-0004a5-00
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 04:27:39 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BasEW-0004BB-00; Thu, 17 Jun 2004 04:26:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bas8R-0004mA-60; Thu, 17 Jun 2004 04:20:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bas0P-0003T8-55
	for ietf@megatron.ietf.org; Thu, 17 Jun 2004 04:12:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08527
	for <ietf@ietf.org>; Thu, 17 Jun 2004 04:12:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bas0J-00073l-Um
	for ietf@ietf.org; Thu, 17 Jun 2004 04:12:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BarzL-0006iG-00
	for ietf@ietf.org; Thu, 17 Jun 2004 04:11:11 -0400
Received: from hugo.int-evry.fr ([157.159.100.81])
	by ietf-mx with esmtp (Exim 4.12) id 1BaryJ-00064a-00
	for ietf@ietf.org; Thu, 17 Jun 2004 04:10:08 -0400
Received: from bernard.int-evry.fr (bernard [157.159.100.53])
	by hugo.int-evry.fr (8.8.8/jtpda-5.3) with ESMTP id KAA06931
	for <ietf@ietf.org>; Thu, 17 Jun 2004 10:09:31 +0200 (MET DST)
Received: from jjp by bernard.int-evry.fr with local (Exim 3.36 #1 (Debian))
	id 1BarzX-0005JS-00
	for <ietf@ietf.org>; Thu, 17 Jun 2004 10:11:23 +0200
Date: Thu, 17 Jun 2004 10:11:23 +0200
From: Jean-Jacques Puig <Jean-Jacques.Puig@int-evry.fr>
To: ietf@ietf.org
Message-ID: <20040617081123.GA18582@bernard>
Mail-Followup-To: ietf@ietf.org
References: <F4410B91C6CC314F9582B1A8E91DC928BEEC4A@ftmail2000>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F4410B91C6CC314F9582B1A8E91DC928BEEC4A@ftmail2000>
Subject: Re: Problem of blocking ICMP packets
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Wed, Jun 16, 2004 at 11:00:23PM -0400, Soliman Hesham wrote:
>  >
>  > It implies that mobile IPv6 depndeing on routing header
>  > may not work.
> 
> => This statement is true IFF people assume that
> Record Route Option == Routing header type 2 used for MIPv6.
> Of course that is not true because there are security
> implications for using routing header type 2 and an
> assumption that the end node will verfiy such use. Moreover,
> RH type 2 will not impact other nodes behind the FW
> if used in a malicious way. All this points to two things:
> 1. The two are not equivalent, and
> 2. We need to make sure that network admins know (1).

But (2) is the same issue with ICMP filtering ! So, I would not trust
admins to tell the difference.

Earlier in this thread were envisioned signaling alternatives: in-band,
IP options, out-band (either ICMP or stg else).

In-band signaling may be appropriate in most cases, if the actual
'signal' is closely related to the protocol. Besides current trend in
firewalls user interfaces let expect that the relation between the
signaling part of the protocol and the protocol itself would be
correctly underlined or automatically managed in such a case.

Out-band signaling and IP options are prone to be modified or generated
by routers; but this is sometimes what is expected ! Better set a bit in
IP header than directly in the transport for ECN. The issue is, IMHO,
that the relation between out-band or IP options and higher layer
protocols is often unknown to admins and not presented in a suitable way
or checked by firewalls user interfaces.

Design is not the issue, I think. Current schemes would actually work
correctly, if only network admins knew.

Yet, we cannot expect admins to learn about each possible combination.
This is where part of the firewall product quality may lay: managing
automatically relations (and noticing about these to admins) or at least
displaying a huge warning when checking rules according to a set of best
current practices. And these are best practices because in some cases
firewalls just don't have adequate information to make a logical
decision.

Three paths:
	- Asking for better fw products
	- Teaching admins (hopeless ?), especially about the grey color
	  somewhere between black and white.
	- Finding out the failing devices, looking up in the whois, picking
	  the phone, flaming them :)

-- 
Jean-Jacques Puig
[homepage] http://www-lor.int-evry.fr/~puig/

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


From ietf-bounces@ietf.org  Thu Jun 17 08:39:33 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25004
	for <ietf-archive@ietf.org>; Thu, 17 Jun 2004 08:39:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BawB4-0006cU-5r
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 08:39:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BawA6-0006I2-00
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 08:38:35 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Baw9H-0005dP-00; Thu, 17 Jun 2004 08:37:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bavr1-00012P-4u; Thu, 17 Jun 2004 08:18:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BavlM-0007Nj-BC
	for ietf@megatron.ietf.org; Thu, 17 Jun 2004 08:13:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23057
	for <ietf@ietf.org>; Thu, 17 Jun 2004 08:12:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BavlL-0005IN-Hg
	for ietf@ietf.org; Thu, 17 Jun 2004 08:12:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BavkI-0004ra-00
	for ietf@ietf.org; Thu, 17 Jun 2004 08:11:55 -0400
Received: from mail.flarion.com ([63.103.94.23] helo=ftmailgfi.HQ.Flarion.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BavjY-0004St-00
	for ietf@ietf.org; Thu, 17 Jun 2004 08:11:08 -0400
Received: from ftmail2000.HQ.Flarion.com ([10.10.1.120]) by
	ftmailgfi.HQ.Flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Thu, 17 Jun 2004 08:10:35 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Jun 2004 08:10:35 -0400
Message-ID: <F4410B91C6CC314F9582B1A8E91DC928BEEC4E@ftmail2000>
Thread-Topic: Problem of blocking ICMP packets
Thread-Index: AcRURPE5Heh4M2upQ6GxStZebvYqGgAHVQAQ
From: "Soliman Hesham" <H.Soliman@flarion.com>
To: "Jean-Jacques Puig" <Jean-Jacques.Puig@int-evry.fr>, <ietf@ietf.org>
X-OriginalArrivalTime: 17 Jun 2004 12:10:35.0386 (UTC)
	FILETIME=[184515A0:01C45464]
Content-Transfer-Encoding: quoted-printable
Subject: RE: Problem of blocking ICMP packets
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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


 > On Wed, Jun 16, 2004 at 11:00:23PM -0400, Soliman Hesham wrote:
 > >  >
 > >  > It implies that mobile IPv6 depndeing on routing header
 > >  > may not work.
 > >=20
 > > =3D> This statement is true IFF people assume that
 > > Record Route Option =3D=3D Routing header type 2 used for MIPv6.
 > > Of course that is not true because there are security
 > > implications for using routing header type 2 and an
 > > assumption that the end node will verfiy such use. Moreover,
 > > RH type 2 will not impact other nodes behind the FW
 > > if used in a malicious way. All this points to two things:
 > > 1. The two are not equivalent, and
 > > 2. We need to make sure that network admins know (1).
 >=20
 > But (2) is the same issue with ICMP filtering ! So, I would not trust
 > admins to tell the difference.

=3D> No it's not the same... MIPv6 includes e2e security (authentication
and authorisation), I don't see people doing that with ping
or PMTUD. So one could put an argument for filtering some
of the ICMP messages. So far I don't see that as a valid
argument for MIPv6 RH type 2.

Hesham

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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


From ietf-bounces@ietf.org  Thu Jun 17 09:45:33 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29191
	for <ietf-archive@ietf.org>; Thu, 17 Jun 2004 09:45:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BaxCx-00050g-4C
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 09:45:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaxC7-0004hs-00
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 09:44:44 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BaxBZ-0004MF-00; Thu, 17 Jun 2004 09:44:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bax4E-0006bw-Vb; Thu, 17 Jun 2004 09:36:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Baggq-0008Rn-7v
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 16:07:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12691
	for <ietf@ietf.org>; Wed, 16 Jun 2004 16:07:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Baggm-0006P1-6q
	for ietf@ietf.org; Wed, 16 Jun 2004 16:07:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BagfF-0005sp-00
	for ietf@ietf.org; Wed, 16 Jun 2004 16:05:41 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BagcP-0004iU-00
	for ietf@ietf.org; Wed, 16 Jun 2004 16:02:45 -0400
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 i5GK1fJ28179;
	Wed, 16 Jun 2004 13:01:41 -0700 (PDT)
Message-ID: <40D0A725.3040406@isi.edu>
Date: Wed, 16 Jun 2004 13:01:41 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mike S <ietf@flatsurface.com>
References: <200406160434.i5G4YjCS069427@cougar.icir.org>
	<6.1.1.1.0.20040616111814.02d518b0@mjs.alientech.net>
In-Reply-To: <6.1.1.1.0.20040616111814.02d518b0@mjs.alientech.net>
X-Enigmail-Version: 0.83.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Mailman-Approved-At: Thu, 17 Jun 2004 09:36:33 -0400
Cc: Alberto Medina <medina@icsi.berkeley.edu>, Mark Allman <mallman@icir.org>,
        Sally Floyd <floyd@icir.org>, Rajat <myself_rajat@yahoo.com>,
        ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1501403883=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1501403883==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig24A41949BC4B15C63B318264"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig24A41949BC4B15C63B318264
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Mike S wrote:

> At 12:34 AM 6/16/2004, Sally Floyd wrote...
> 
>>Alberto Medina, Mark Allman, and I have a draft paper on
>>"Measuring the Evolution of Transport Protocols in the Internet"
>>that has a section (Section V.B.) on Path MTU Discovery.
>>>From the paper:
>>
>>"Table X shows that PMTUD is used and succeeded for slightly less
>>than half of the [web] servers on our list.  For 31\% of the servers
>>on our list, the server did not attempt Path MTU Discovery.  For
>>18\% of the servers on our list, Path MTU Discovery failed, presumably
>>because of middleboxes that block ICMP packets on the path to the
>>web server."
> 
> Any router configured to block ICMP packets is, quite simply,
> in violation of RFC792 (STD5), which clearly states "ICMP is actually 
> an integral part of IP, and must be implemented by every IP module." 
> For a router, "implemented" means forwarded to the destinations next
> hop.

RFC1812, Sec 5.2.7.1, where the 'frag needed' variant is mentioned (type 
3, code 4), is more specific on this point. Routers must emit these 
errors - or, if administrative restrictions apply, code 13 
"Communication Administratively Prohibited" errors.

> So the fact is, by blocking ICMP, such ISPs have broken IP connectivity, 
> and can no longer claim to be providing Internet (IP) service.

The same can be said for those providing NAT'd IP service, for similar 
reasons. ;-)

Joe

--------------enig24A41949BC4B15C63B318264
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFA0KcpE5f5cImnZrsRAmLPAKC3wI+kMhh90glV7lHieR7bjUtg7QCg3xe9
2ZlQZz4fD2CPBpAFwWzxMxQ=
=eRQS
-----END PGP SIGNATURE-----

--------------enig24A41949BC4B15C63B318264--


--===============1501403883==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1501403883==--



From ietf-bounces@ietf.org  Thu Jun 17 09:48:39 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29335
	for <ietf-archive@ietf.org>; Thu, 17 Jun 2004 09:48:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BaxFw-00064E-KD
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 09:48:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaxEy-0005hC-00
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 09:47:41 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BaxE7-00052Z-00; Thu, 17 Jun 2004 09:46:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bax4F-0006c3-Vr; Thu, 17 Jun 2004 09:36:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BajZr-0008NL-G0
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 19:12:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29024
	for <ietf@ietf.org>; Wed, 16 Jun 2004 19:12:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BajZm-0006pj-PU
	for ietf@ietf.org; Wed, 16 Jun 2004 19:12:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BajYo-0006PX-00
	for ietf@ietf.org; Wed, 16 Jun 2004 19:11:15 -0400
Received: from [216.191.155.143] (helo=persephone.cfrq.net)
	by ietf-mx with esmtp (Exim 4.12) id 1BajWG-0005ZB-00
	for ietf@ietf.org; Wed, 16 Jun 2004 19:08:36 -0400
Received: from bunbun (persephone.chk.cfrq.net [199.85.99.254])
	by persephone.cfrq.net (Postfix) with ESMTP id 35CB8FA0B
	for <ietf@ietf.org>; Wed, 16 Jun 2004 19:08:38 -0400 (EDT)
Message-ID: <00e101c453f6$db8d5770$096355c7@americas.cpqcorp.net>
From: "Harald Koch" <chk@cfrq.net>
Cc: <ietf@ietf.org>
References: <200406160434.i5G4YjCS069427@cougar.icir.org>
	<6.1.1.1.0.20040616111814.02d518b0@mjs.alientech.net>
Date: Wed, 16 Jun 2004 19:08:37 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 17 Jun 2004 09:36:33 -0400
Subject: Re: Problem of blocking ICMP packets
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

> Any router configured to block ICMP packets is, quite simply,
> in violation of RFC792 (STD5), which clearly states "ICMP is actually
> an integral part of IP, and must be implemented by every IP module."
> For a router, "implemented" means forwarded to the destinations next
> hop.
>
> So the fact is, by blocking ICMP, such ISPs have broken IP connectivity,
> and can no longer claim to be providing Internet (IP) service.

<yawn> This debate has been going on since before I became a firewall
developer back in 1995...

Unfortunately, customers are more interested in a "usable" internet than a
"correct" one. As long as the bad guys keep abusing ICMP, we security people
will keep blocking it. The trick, therefore, is to convince the "block
everything" crowd to be selective about ICMP the same way they are selective
about (eg) TCP port numbers.

It's pretty easy these days to write good firewall rules that allow, for
example, Path MTU discovery to work.The "RELATED" state in Linux's iptables
rules is a good start...

-- 
Harald Koch chk@pobox.com


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


From ietf-bounces@ietf.org  Thu Jun 17 09:52:39 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29515
	for <ietf-archive@ietf.org>; Thu, 17 Jun 2004 09:52:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BaxJo-0007Ra-V6
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 09:52:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BaxIw-00076k-00
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 09:51:46 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BaxIK-0006kY-00; Thu, 17 Jun 2004 09:51:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bax4G-0006cA-VW; Thu, 17 Jun 2004 09:36:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ban3Q-0007u4-Nm
	for ietf@megatron.ietf.org; Wed, 16 Jun 2004 22:55:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10310
	for <ietf@ietf.org>; Wed, 16 Jun 2004 22:55:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Ban3M-0003ae-7K
	for ietf@ietf.org; Wed, 16 Jun 2004 22:55:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ban2R-0003Gm-00
	for ietf@ietf.org; Wed, 16 Jun 2004 22:54:03 -0400
Received: from wyvern.icir.org ([192.150.187.14])
	by ietf-mx with esmtp (Exim 4.12) id 1Ban1s-0002wi-00
	for ietf@ietf.org; Wed, 16 Jun 2004 22:53:28 -0400
Received: from guns.icir.org (adsl-68-76-113-50.dsl.bcvloh.ameritech.net
	[68.76.113.50])
	by wyvern.icir.org (8.12.9p1/8.12.8) with ESMTP id i5H2rPMx005937;
	Wed, 16 Jun 2004 19:53:25 -0700 (PDT)
	(envelope-from mallman@icir.org)
Received: from lawyers.icir.org (adsl-68-76-113-50.dsl.bcvloh.ameritech.net
	[68.76.113.50]) by guns.icir.org (Postfix) with ESMTP
	id 2BA8677ACF7; Wed, 16 Jun 2004 22:53:23 -0400 (EDT)
Received: from lawyers.icir.org (localhost [127.0.0.1])
	by lawyers.icir.org (Postfix) with ESMTP
	id 796B9160E37; Wed, 16 Jun 2004 22:52:20 -0400 (EDT)
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>,
        mohta@necom830.hpcl.titech.ac.jp
From: Mark Allman <mallman@icir.org>
In-Reply-To: <9301.1087417731@marajade.sandelman.ottawa.on.ca> 
Organization: ICSI Center for Internet Research (ICIR)
Song-of-the-Day: Wishlist
MIME-Version: 1.0
Date: Wed, 16 Jun 2004 22:52:20 -0400
Message-Id: <20040617025220.796B9160E37@lawyers.icir.org>
X-Mailman-Approved-At: Thu, 17 Jun 2004 09:36:33 -0400
Cc: Christian Huitema <huitema@windows.microsoft.com>,
        Alberto Medina <medina@icsi.berkeley.edu>,
        Sally Floyd <floyd@icir.org>, Rajat <myself_rajat@yahoo.com>,
        ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mallman@icir.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1517976618=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

--===============1517976618==
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"

--=-=-=
Content-Type: text/plain


A couple bits to add to the discussion.

Michael Richardson:
>   The boxes that are responsible for 90% of the ICMP lossage were also 
> intolerant of the ECN options in TCP, and pretty much all TCP options in
> general.

This is not quite right, IMO.  In the past there have been problems with
packets with the ECN bits set getting through the network (see the
original TBIT SIGCOMM paper - available from http://www.icir.org/tbit/).
However, our recent measurements show that this is not as much of a
problem anymore.  And, contrary the the above assertion, blocking based
on ECN is not nearly as prevalent as PMTUD failure.  Our measurements do
not speak to whether the boxes that block ECN also block PMTUD.  If
someone has such measurements, we'd love to hear about them.

Masataka Ohta:
> > The good news is that known or unknown TCP options are not blocked
> > on paths to web servers.  Or at any rate, the connection still
> > succeeds in being established...
> 
> As long as routers are not required to look into TCP options, they are
> likely to interoperate even with complex TCP options.

The trouble is that it just isn't routers getting their grimy hands on
our packets these days.  Middleboxes look at, touch and mangle packets
for all sorts of reasons (from transparent caches to performance
enhancing proxies to normalizers to protocol scrubbers to load balancers
to ....).  So, while our measurements show no problems with TCP options,
I don't think it is a foregone conclusion, nor not something to keep our
collective eye on.

allman




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

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

iD8DBQFA0QdkWyrrWs4yIs4RAr3rAJ9XlAwd6fW499iScN6jS/AieT/vyACgj3x6
BguysZetzJeQVDSGwlkm9fY=
=+bLO
-----END PGP SIGNATURE-----
--=-=-=--


--===============1517976618==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1517976618==--



From ietf-bounces@ietf.org  Thu Jun 17 13:35:11 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24855
	for <ietf-archive@ietf.org>; Thu, 17 Jun 2004 13:35:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bb0n9-0000M4-4q
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 13:35:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bb0dp-0006AA-00
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 13:25:34 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bb0XL-0004Uz-00; Thu, 17 Jun 2004 13:18:51 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Bb0UE-0006fQ-VM; Thu, 17 Jun 2004 13:15:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BazWm-0001eX-HX; Thu, 17 Jun 2004 12:14:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bayl1-0005SM-7g
	for ietf@megatron.ietf.org; Thu, 17 Jun 2004 11:24:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09859
	for <ietf@ietf.org>; Thu, 17 Jun 2004 11:24:48 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bayl0-00050V-BE
	for ietf@ietf.org; Thu, 17 Jun 2004 11:24:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bayk9-0004dn-00
	for ietf@ietf.org; Thu, 17 Jun 2004 11:23:58 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1Bayiv-0004EL-00
	for ietf@ietf.org; Thu, 17 Jun 2004 11:22:42 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta5/8.13.0.Beta5) with ESMTP id
	i5HFN2cF016662; Thu, 17 Jun 2004 11:23:02 -0400
Message-Id: <200406171523.i5HFN2cF016662@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Sally Floyd <floyd@icir.org>
In-Reply-To: Your message of "Wed, 16 Jun 2004 11:00:29 PDT."
	<200406161800.i5GI0TCS079218@cougar.icir.org> 
References: <200406161800.i5GI0TCS079218@cougar.icir.org>
Mime-Version: 1.0
Date: Thu, 17 Jun 2004 11:23:02 -0400
Cc: ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1978911472=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,NO_REAL_NAME autolearn=no 
	version=2.60

--===============1978911472==
Content-Type: multipart/signed; boundary="==_Exmh_-201603277P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Wed, 16 Jun 2004 11:00:29 PDT, Sally Floyd said:

> to the browser.  Presumeably if the web server wanted to use something
> like QuickStart, it could have the firewall configured to allow the
> IP QuickStart Option not to be blocked on the outgoing SYN packet?

Given the number of times we've had IWF reports that basically boil
down to 'ntp-[12].vt.edu is probing me from port 123", and even more
interestingly the number of times we've been asked by the remote user
why their machine is trying to contact ntp-1.vt.edu, I have to classify
the concept that "People will remember to put appropriate punchouts
in their firewall when they deploy a service" as "wishful thinking".

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

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

iD8DBQFA0bdVcC3lWbTT17ARAgNGAKDqJyPrwSrKAimtzt+S45skY05WUgCdEZLV
D9jUmkXaRWlixXraA7Gd5go=
=ICku
-----END PGP SIGNATURE-----

--==_Exmh_-201603277P--


--===============1978911472==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1978911472==--



From ietf-bounces@ietf.org  Thu Jun 17 19:27:13 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25696
	for <ietf-archive@ietf.org>; Thu, 17 Jun 2004 19:27:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bb6Hp-0003tL-Ia
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 19:27:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bb6Gn-0003W2-00
	for ietf-archive@ietf.org; Thu, 17 Jun 2004 19:26:10 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bb6Fi-0002YQ-00; Thu, 17 Jun 2004 19:25:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bb5xm-0000Xg-Cw; Thu, 17 Jun 2004 19:06:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bb5mv-0006I3-U2
	for ietf@megatron.ietf.org; Thu, 17 Jun 2004 18:55:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23743
	for <ietf@ietf.org>; Thu, 17 Jun 2004 18:55:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bb5mu-0000hE-CW
	for ietf@ietf.org; Thu, 17 Jun 2004 18:55:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bb5m1-0000Lj-00
	for ietf@ietf.org; Thu, 17 Jun 2004 18:54:21 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12) id 1Bb5lA-0007Uv-00
	for ietf@ietf.org; Thu, 17 Jun 2004 18:53:28 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 2690A61BD7; Fri, 18 Jun 2004 00:52:58 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 06527-04; Fri, 18 Jun 2004 00:52:57 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id A04D161A93; Fri, 18 Jun 2004 00:52:56 +0200 (CEST)
Date: Thu, 17 Jun 2004 15:53:47 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>, ietf@ietf.org
Message-ID: <31098184049B948E29A29935@[192.168.1.47]>
In-Reply-To: <Pine.LNX.4.44.0406161800430.6106-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0406161800430.6106-100000@cirrus.av8.net>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
Content-Transfer-Encoding: 7bit
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On 16. juni 2004 18:03 -0400 Dean Anderson <dean@av8.com> wrote:

> I've noticed that Rob Austein continues to use sra@isc.org for his work as
> WG co-chair.  I think I've been very patient, and have held off on legal
> recourse so far.

Dean,

we have been very patient with you, but you are misrepresenting the 
situation.

I have replied that I do not see the merit to your complaint, and have NOT 
asked Rob Austein to change his address, have NOT asked ISC to change their 
antispam policies, and have NOT asked SORBS to change ther listings - 
having concluded that none of these is the IETF's business.

(the alternative - declaring that every antispam function of every system 
that is used by an IETF participant is a matter for the IETF to have an 
opinion on, and possibly work to have changed, every time it causes a 
message to bounce or be dropped - is simply not workable.)

If you don't like that decision, you are free to appeal the decision to the 
IAB according to RFC 3005, or to pursue any other avenue that you feel 
appropriate.

Making oblique reference to legal action on the IETF list will not change 
the situation.

                        Harald


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


From ietf-bounces@ietf.org  Fri Jun 18 10:04:54 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23206
	for <ietf-archive@ietf.org>; Fri, 18 Jun 2004 10:04:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbJzD-0002ET-T2
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 10:04:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbJuS-0000uf-00
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 10:00:00 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbJrh-000034-00; Fri, 18 Jun 2004 09:57:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbJOQ-0000sl-Qh; Fri, 18 Jun 2004 09:26:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bb4yb-0001mi-2z
	for ietf@megatron.ietf.org; Thu, 17 Jun 2004 18:03:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19388
	for <ietf@ietf.org>; Thu, 17 Jun 2004 18:03:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bb4yZ-0006oZ-Gg
	for ietf@ietf.org; Thu, 17 Jun 2004 18:03:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bb4xY-0006Px-00
	for ietf@ietf.org; Thu, 17 Jun 2004 18:02:12 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bb4vh-0005SP-00; Thu, 17 Jun 2004 18:00:17 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1Bb4SF-00060S-Sq; Thu, 17 Jun 2004 17:29:51 -0400
To: IETF Announcement list <ietf-announce@ietf.org>
From: Harald Alvestrand <harald@alvestrand.no>
Message-Id: <E1Bb4SF-00060S-Sq@megatron.ietf.org>
Date: Thu, 17 Jun 2004 17:29:51 -0400
X-Mailman-Approved-At: Fri, 18 Jun 2004 09:26:52 -0400
Subject: Current status of IETF change efforts - updated 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

The IETF Chair document describing the change effort 
(http://www.ietf.org/u/ietfchair/) has not been updated for quite some time - it
is currently dated January.

Due to the IT problems at the secretariat, I am currently unable to update it.

I have made the current version available at my "staging area" server:
http://www.alvestrand.no/ietf/chair/

This includes:

- Mid-June version of "status of change efforts"
- 2003 financials
- 2004 budget

Happy reading!

                    Harald Alvestrand





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


From ietf-bounces@ietf.org  Fri Jun 18 10:04:56 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23229
	for <ietf-archive@ietf.org>; Fri, 18 Jun 2004 10:04:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbJzF-0002Ef-D1
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 10:04:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbJuT-0000v7-00
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 10:00:02 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbJrh-000035-00; Fri, 18 Jun 2004 09:57:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbJOR-0000st-S2; Fri, 18 Jun 2004 09:26:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bb5i1-0004Ox-7H
	for ietf@megatron.ietf.org; Thu, 17 Jun 2004 18:50:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23407
	for <ietf@ietf.org>; Thu, 17 Jun 2004 18:50:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bb5hz-0006XS-R7
	for ietf@ietf.org; Thu, 17 Jun 2004 18:50:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bb5g0-000683-00
	for ietf@ietf.org; Thu, 17 Jun 2004 18:48:08 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bb5eu-0005Sr-00; Thu, 17 Jun 2004 18:47:00 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1Bb5Ns-0005rJ-Op; Thu, 17 Jun 2004 18:29:24 -0400
To: IETF Announcement list <ietf-announce@ietf.org>
From: Harald Alvestrand <harald@alvestrand.no>
Message-Id: <E1Bb5Ns-0005rJ-Op@megatron.ietf.org>
Date: Thu, 17 Jun 2004 18:29:24 -0400
X-Mailman-Approved-At: Fri, 18 Jun 2004 09:26:52 -0400
Subject: New versions of guidelines for Internet-Drafts 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

The IESG has emitted new versions of the following guideline documents:

"Guidelines to authors of Internet-Drafts"
http://www.ietf.org/ietf/1id-guidelines.txt

which has been updated to reflect the new IPR policy RFCs (3667 and 3668):
Note that in this process, we discovered a bug in one of the RFCs; the document 
ontains a temporary fix, but the details of a permanent fix are still being 
worked out on the IPR WG list.

"Checklist for Internet-Drafts submitted for RFC publication"
http://www.ietf.org/ID-Checklist.html

This has had a more thorough review/revision, and should be re-read by all 
participants. Note in particular the new language about IANA considerations.

(This was actually posted a month ago, but has not been announced to this list 
et, so I am including it in this announcement.)

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


From ietf-bounces@ietf.org  Fri Jun 18 18:54:10 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28989
	for <ietf-archive@ietf.org>; Fri, 18 Jun 2004 18:54:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbSFP-0001Ek-FC
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 18:54:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbSEQ-0000sl-00
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 18:53:10 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbSDP-0000Bu-00; Fri, 18 Jun 2004 18:52:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbS98-0007WM-Rw; Fri, 18 Jun 2004 18:47:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BbS6l-0006rG-QV
	for ietf@megatron.ietf.org; Fri, 18 Jun 2004 18:45:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28676
	for <ietf@ietf.org>; Fri, 18 Jun 2004 18:45:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BbS6k-0005nJ-El
	for ietf@ietf.org; Fri, 18 Jun 2004 18:45:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbS5i-0005Rc-00
	for ietf@ietf.org; Fri, 18 Jun 2004 18:44:11 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1BbS4l-0004lk-00
	for ietf@ietf.org; Fri, 18 Jun 2004 18:43:12 -0400
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 i5IMgR9m029518
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 18 Jun 2004 18:42:34 -0400
Date: Fri, 18 Jun 2004 18:42:27 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
In-Reply-To: <31098184049B948E29A29935@[192.168.1.47]>
Message-ID: <Pine.LNX.4.44.0406181816180.27810-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Thu, 17 Jun 2004, Harald Tveit Alvestrand wrote:
> --On 16. juni 2004 18:03 -0400 Dean Anderson <dean@av8.com> wrote:
> 
> > I've noticed that Rob Austein continues to use sra@isc.org for his work as
> > WG co-chair.  I think I've been very patient, and have held off on legal
> > recourse so far.
> 
> Dean,
> 
> we have been very patient with you, but you are misrepresenting the 
> situation.

I don't feel as though I have misrepresented anything. The same cannot be
said with regards to your messages on the topic, particularly your
(misleading) claim that I have some request about incorrect ownership
data. I have made no such request, and in fact there is no incorrect
ownership data, and you are quite well aware of that.  You seem to be 
misrepresenting other things as well.

> I have replied that I do not see the merit to your complaint, and have NOT 
> asked Rob Austein to change his address, have NOT asked ISC to change their 
> antispam policies, and have NOT asked SORBS to change ther listings - 
> having concluded that none of these is the IETF's business.

I am aware of your responses. I have read them carefully, and have passed
them to our counsel.  However, other people seem to feel that your
handling of the situation has not been reasonable, and some have even
suggested fairly sensible ways for the IETF to work out the problem.  I do
not understand why you persist in such unreasonable, unfair, and
unbalanced behavior, even in the face of reasonable suggestions.

> (the alternative - declaring that every antispam function of every system 
> that is used by an IETF participant is a matter for the IETF to have an 
> opinion on, and possibly work to have changed, every time it causes a 
> message to bounce or be dropped - is simply not workable.)

We are not discussing anti-spam functions, nor a routine message bounce,
nor a benign transient error.  This has nothing whatsoever to do with spam
or anti-spam functions.  Your attempt to describe it as such is misleading
and incorrect.  We are discussing defamation, baldly false statements
originated by court-proven liars, unlawful participation in a group
boycott, commercial disparagement and other issues.  No one (except you)
has claimed that spam has anything remotely or even peripherally to do
with this.  The disputed behavior is the subject of the ISOC Code of
Conduct, and the IETF Guidelines of conduct, as well as the IETF Mission
Statement.  So it is the "IETF's business", because conduct of its members
are the subject of these documents, and the conduct of the IETF's
representatives performing IETF business is the responsibility of the
IETF.  Should said representatives perform their IETF duties unlawfully,
then the IETF bears the responsibility for those unlawful acts.

> If you don't like that decision, you are free to appeal the decision to the 
> IAB according to RFC 3005, or to pursue any other avenue that you feel 
> appropriate.

If you force that, we will have to do that.  But it seems that there is a 
more reasonable way to handle the problem.



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


From ietf-bounces@ietf.org  Fri Jun 18 21:09:25 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07584
	for <ietf-archive@ietf.org>; Fri, 18 Jun 2004 21:09:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbUMH-00033G-1p
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 21:09:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbULM-0002gW-00
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 21:08:29 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbUKR-0001wK-00; Fri, 18 Jun 2004 21:07:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbUD9-0007Pq-1Z; Fri, 18 Jun 2004 20:59:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BbTzD-0004ao-Ib
	for ietf@megatron.ietf.org; Fri, 18 Jun 2004 20:45:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06156
	for <ietf@ietf.org>; Fri, 18 Jun 2004 20:45:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BbTzB-0002Kw-NA
	for ietf@ietf.org; Fri, 18 Jun 2004 20:45:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbTyI-0001xh-00
	for ietf@ietf.org; Fri, 18 Jun 2004 20:44:39 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.sea)
	by ietf-mx with esmtp (Exim 4.12) id 1BbTxf-0001We-00
	for ietf@ietf.org; Fri, 18 Jun 2004 20:44:00 -0400
Received: from stephen (ip133.post-vineyard.dfw.ygnition.net [66.135.181.133])
	by ns2.sea (8.12.11/8.12.5) with SMTP id i5J0glCo025873;
	Fri, 18 Jun 2004 17:42:48 -0700
Message-ID: <03ae01c45596$5864c170$6401a8c0@stephen>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        "Dean Anderson" <dean@av8.com>
References: <Pine.LNX.4.44.0406161800430.6106-100000@cirrus.av8.net>
	<31098184049B948E29A29935@[192.168.1.47]>
Date: Fri, 18 Jun 2004 19:28:40 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Cc: Internet Engineering Task Force <ietf@ietf.org>
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Thus spake "Harald Tveit Alvestrand" <harald@alvestrand.no>
> I have replied that I do not see the merit to your complaint, and have NOT
> asked Rob Austein to change his address, have NOT asked ISC to change
their
> antispam policies, and have NOT asked SORBS to change ther listings -
> having concluded that none of these is the IETF's business.
>
> (the alternative - declaring that every antispam function of every system
> that is used by an IETF participant is a matter for the IETF to have an
> opinion on, and possibly work to have changed, every time it causes a
> message to bounce or be dropped - is simply not workable.)

While I disagree with Dean in general and also with most of his current
argument, I think it is a reasonable request that IETF "officials" be given
an @ietf.org email alias and that those aliases be published for use in
situations such as this.

It's probably going too far to require sending mail from those aliases;
despite Dean's faults, he's smart enough to use the published alias if he
gets a bounce from someone's personal or work address.

S

Stephen Sprunk      "Those people who think they know everything
CCIE #3723         are a great annoyance to those of us who do."
K5SSS                                             --Isaac Asimov


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


From ietf-bounces@ietf.org  Fri Jun 18 21:49:36 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09176
	for <ietf-archive@ietf.org>; Fri, 18 Jun 2004 21:49:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbUzA-00029A-J2
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 21:49:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbUy5-0001lK-00
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 21:48:30 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbUxX-0001No-00; Fri, 18 Jun 2004 21:47:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbUr9-0006DR-0r; Fri, 18 Jun 2004 21:41:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BbUnJ-0005MM-SP
	for ietf@megatron.ietf.org; Fri, 18 Jun 2004 21:37:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08864
	for <ietf@ietf.org>; Fri, 18 Jun 2004 21:37:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BbUnI-0005dm-8A
	for ietf@ietf.org; Fri, 18 Jun 2004 21:37:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbUmK-0005IS-00
	for ietf@ietf.org; Fri, 18 Jun 2004 21:36:21 -0400
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx with esmtp (Exim 4.12) id 1BbUlp-0004xl-00
	for ietf@ietf.org; Fri, 18 Jun 2004 21:35:50 -0400
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i5J1Zj212370; Sat, 19 Jun 2004 04:35:45 +0300 (EET DST)
X-Scanned: Sat, 19 Jun 2004 04:35:42 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i5J1ZgiA031776;
	Sat, 19 Jun 2004 04:35:42 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00NpFAU7; Sat, 19 Jun 2004 04:35:41 EEST
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com
	[10.241.35.121])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i5J1ZdH04621; Sat, 19 Jun 2004 04:35:40 +0300 (EET DST)
Received: from dadhcp-172019068136.americas.nokia.com ([172.19.68.140]) by
	daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 18 Jun 2004 20:35:38 -0500
Received: from dadhcp-172019068136.americas.nokia.com (localhost.localdomain
	[127.0.0.1])
	by dadhcp-172019068136.americas.nokia.com (8.12.8/8.12.8) with ESMTP id
	i5J1Zcje008041; Fri, 18 Jun 2004 18:35:38 -0700
Received: (from kessens@localhost)
	by dadhcp-172019068136.americas.nokia.com (8.12.8/8.12.8/Submit) id
	i5J1ZcwS008039; Fri, 18 Jun 2004 18:35:38 -0700
Date: Fri, 18 Jun 2004 18:35:37 -0700
From: David Kessens <david.kessens@nokia.com>
To: Stephen Sprunk <stephen@sprunk.org>
Message-ID: <20040619013537.GC7860@nokia.com>
References: <Pine.LNX.4.44.0406161800430.6106-100000@cirrus.av8.net>
	<31098184049B948E29A29935@[192.168.1.47]>
	<03ae01c45596$5864c170$6401a8c0@stephen>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <03ae01c45596$5864c170$6401a8c0@stephen>
User-Agent: Mutt/1.4.1i
X-OriginalArrivalTime: 19 Jun 2004 01:35:38.0573 (UTC)
	FILETIME=[B9A03FD0:01C4559D]
Cc: Dean Anderson <dean@av8.com>,
        Internet Engineering Task Force <ietf@ietf.org>
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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


Stephen,

On Fri, Jun 18, 2004 at 07:28:40PM -0500, Stephen Sprunk wrote:
> 
> While I disagree with Dean in general and also with most of his current
> argument, I think it is a reasonable request that IETF "officials" be given
> an @ietf.org email alias and that those aliases be published for use in
> situations such as this.

I like this idea (for other reasons) but I am not sure whether this
really addresses this particular problem: Even if I would have an
@ietf.org account, I would still want to use my anti-spam filters. I
just get too much spam and generic accounts like this are bound to
attract an enormous amount of spam. Unfortunately, the cost of
miscategorizing a mail has become lower than the cost of checking all
my mail manually.

David Kessens
---

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


From ietf-bounces@ietf.org  Fri Jun 18 22:07:40 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09823
	for <ietf-archive@ietf.org>; Fri, 18 Jun 2004 22:07:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbVGe-0000ng-GI
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 22:07:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbVEf-0000CK-00
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 22:05:38 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbVDm-0007cA-02; Fri, 18 Jun 2004 22:04:42 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BbVBs-0002gw-OJ; Fri, 18 Jun 2004 22:02:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbV99-0001Um-ER; Fri, 18 Jun 2004 21:59:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BbV7k-00016s-3C
	for ietf@megatron.ietf.org; Fri, 18 Jun 2004 21:58:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09530
	for <ietf@ietf.org>; Fri, 18 Jun 2004 21:58:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BbV7i-0005RA-CS
	for ietf@ietf.org; Fri, 18 Jun 2004 21:58:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbV6k-0004n1-00
	for ietf@ietf.org; Fri, 18 Jun 2004 21:57:26 -0400
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx with esmtp (Exim 4.12) id 1BbV5O-0004Pg-00
	for ietf@ietf.org; Fri, 18 Jun 2004 21:56:02 -0400
Received: from mobilebill (c-24-20-39-234.client.comcast.net[24.20.39.234])
	by comcast.net (rwcrmhc11) with SMTP
	id <2004061901553201300ggfnle>; Sat, 19 Jun 2004 01:55:32 +0000
From: "bill" <bill@strahm.net>
To: "'Stephen Sprunk'" <stephen@sprunk.org>,
        "'Harald Tveit Alvestrand'" <harald@alvestrand.no>,
        "'Dean Anderson'" <dean@av8.com>
Date: Fri, 18 Jun 2004 18:55:17 -0700
Message-ID: <000001c455a0$7c8696a0$6601a8c0@mobilebill>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <03ae01c45596$5864c170$6401a8c0@stephen>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
Subject: RE: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=CLICK_BELOW autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

As a working group chair - I would refuse an e-mail account that I am
not allowed to spam control on my own terms.

Before long these published email addresses would become spam sponges -
and completely worthless (or expensive timewise to correctly filter

Bill

I am training for my first endurance event... and SAVING lives click
here to find out more!
http://www.teamintraining.org/participant/strahm-163543
 

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Stephen Sprunk
Sent: Friday, June 18, 2004 5:29 PM
To: Harald Tveit Alvestrand; Dean Anderson
Cc: Internet Engineering Task Force
Subject: Re: Response to complaint from Dean Anderson (fwd)


Thus spake "Harald Tveit Alvestrand" <harald@alvestrand.no>
> I have replied that I do not see the merit to your complaint, and have

> NOT asked Rob Austein to change his address, have NOT asked ISC to 
> change
their
> antispam policies, and have NOT asked SORBS to change ther listings - 
> having concluded that none of these is the IETF's business.
>
> (the alternative - declaring that every antispam function of every 
> system that is used by an IETF participant is a matter for the IETF to

> have an opinion on, and possibly work to have changed, every time it 
> causes a message to bounce or be dropped - is simply not workable.)

While I disagree with Dean in general and also with most of his current
argument, I think it is a reasonable request that IETF "officials" be
given an @ietf.org email alias and that those aliases be published for
use in situations such as this.

It's probably going too far to require sending mail from those aliases;
despite Dean's faults, he's smart enough to use the published alias if
he gets a bounce from someone's personal or work address.

S

Stephen Sprunk      "Those people who think they know everything
CCIE #3723         are a great annoyance to those of us who do."
K5SSS                                             --Isaac Asimov


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



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


From ietf-bounces@ietf.org  Fri Jun 18 22:48:25 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11494
	for <ietf-archive@ietf.org>; Fri, 18 Jun 2004 22:48:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbVu5-0007V1-If
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 22:48:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbVsC-000783-00
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 22:46:29 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbVrH-0006QG-00; Fri, 18 Jun 2004 22:45:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbVny-00008V-Dx; Fri, 18 Jun 2004 22:42:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BbVdh-0006zW-Rh
	for ietf@megatron.ietf.org; Fri, 18 Jun 2004 22:31:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11053
	for <ietf@ietf.org>; Fri, 18 Jun 2004 22:31:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BbVdg-0001Wi-6a
	for ietf@ietf.org; Fri, 18 Jun 2004 22:31:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbVbi-00019r-00
	for ietf@ietf.org; Fri, 18 Jun 2004 22:29:27 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.sea)
	by ietf-mx with esmtp (Exim 4.12) id 1BbVbP-0000o5-00
	for ietf@ietf.org; Fri, 18 Jun 2004 22:29:07 -0400
Received: from stephen (ip133.post-vineyard.dfw.ygnition.net [66.135.181.133])
	by ns2.sea (8.12.11/8.12.5) with SMTP id i5J2S5em026116;
	Fri, 18 Jun 2004 19:28:06 -0700
Message-ID: <043e01c455a5$0e0770f0$6401a8c0@stephen>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "David Kessens" <david.kessens@nokia.com>
References: <Pine.LNX.4.44.0406161800430.6106-100000@cirrus.av8.net>
	<31098184049B948E29A29935@[192.168.1.47]>
	<03ae01c45596$5864c170$6401a8c0@stephen>
	<20040619013537.GC7860@nokia.com>
Date: Fri, 18 Jun 2004 21:05:52 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Cc: Dean Anderson <dean@av8.com>,
        Internet Engineering Task Force <ietf@ietf.org>
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Thus spake "David Kessens" <david.kessens@nokia.com>
> On Fri, Jun 18, 2004 at 07:28:40PM -0500, Stephen Sprunk wrote:
> > While I disagree with Dean in general and also with most of his current
> > argument, I think it is a reasonable request that IETF "officials" be
given
> > an @ietf.org email alias and that those aliases be published for use in
> > situations such as this.
>
> I like this idea (for other reasons) but I am not sure whether this
> really addresses this particular problem:

Dean's problem is that he sends mail from an open relay, which isc.org's
servers block completely (with good reason, sorry Dean).  ietf.org's servers
apparently don't since we all receive his rants, and presumably isc.org
doesn't block mail from ietf.org, so this would solve the immediate problem.

> Even if I would have an @ietf.org account, I would still want to use my
> anti-spam filters.  I just get too much spam and generic accounts like
> this are bound to attract an enormous amount of spam. Unfortunately,
> the cost of miscategorizing a mail has become lower than the cost of
> checking all my mail manually.

I don't object to those aliases pointing to systems with content-based
anti-spam systems; if Dean's mail looks like spam, individual people could
whitelist him without also being subjected to any spam passing through his
open relay.  Though, of course, the odds are slim any of us would do that.

S

Stephen Sprunk      "Those people who think they know everything
CCIE #3723         are a great annoyance to those of us who do."
K5SSS                                             --Isaac Asimov


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


From ietf-bounces@ietf.org  Fri Jun 18 23:12:22 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12364
	for <ietf-archive@ietf.org>; Fri, 18 Jun 2004 23:12:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbWHG-0000w7-Al
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 23:12:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbWGH-0000a7-00
	for ietf-archive@ietf.org; Fri, 18 Jun 2004 23:11:22 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbWFP-0007gP-00; Fri, 18 Jun 2004 23:10:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbW7Z-0003aB-Vm; Fri, 18 Jun 2004 23:02:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BbW1s-0002R1-DD
	for ietf@megatron.ietf.org; Fri, 18 Jun 2004 22:56:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11980
	for <ietf@ietf.org>; Fri, 18 Jun 2004 22:56:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BbW1q-00038W-Md
	for ietf@ietf.org; Fri, 18 Jun 2004 22:56:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbW10-0002nF-00
	for ietf@ietf.org; Fri, 18 Jun 2004 22:55:34 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BbW0a-0002Oy-00
	for ietf@ietf.org; Fri, 18 Jun 2004 22:55:08 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i5J2scW3022797
	for ietf@ietf.org env-from <vjs>;
	Fri, 18 Jun 2004 20:54:38 -0600 (MDT)
Date: Fri, 18 Jun 2004 20:54:38 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200406190254.i5J2scW3022797@calcite.rhyolite.com>
To: ietf@ietf.org
References: <03ae01c45596$5864c170$6401a8c0@stephen>
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> From: "Stephen Sprunk" 

> While I disagree with Dean in general and also with most of his current
> argument, I think it is a reasonable request that IETF "officials" be given
> an @ietf.org email alias and that those aliases be published for use in
> situations such as this.

Exactly what is this situation?  Why can't Mr. Anderson say whatever
he needs to say to Mr. Austein here or via a relevant working group
mailing list?


> It's probably going too far to require sending mail from those aliases;
> despite Dean's faults, he's smart enough to use the published alias if he
> gets a bounce from someone's personal or work address.

How would Mr. Anderson use a private IETF alias belonging to Mr. Austein?
If sending a polite, IETF-relevant private message from one IETF
participant were important to Mr. Anderson, he would have long since
sent his message in public via an IETF mailing list.  Any complaints
or other thoughts Mr. Anderson has about a working group, an AD, other
IETF participants, or whatever would have long since been forwarded
via a friend, sent to this mailing list, the IAB, or via the official
appeals process.

There is an important issue here separate from Mr. Anderson's concerns.
Why hasn't Mr. Anderson been told to say whatever he wants to say in
an IETF mailing lists or to the relevant IETF role accounts?  Why has
the notion that individuals have rights enforced by IETF rules to send
private mail to other IETF participants been consistently supported
or at least never refuted?  Mr. Alvestrand's recent message only
disavows the IETF's interest private filters.  What RFC imposes an
obligation to receive private (not to mention unfriendly) mail on ADs,
WG chairs, or any IETF participants? 

Private IETF aliases for IETF officials would be invitations for
harassment and abuse, and it is important that IETF participation not
be contingent on tolerating harassment or abuse.  Harassment and abuse
must be defined by the targets of mail for deciding whether to accept
future private messages.  IETF participants must be allowed their own
definitions of acceptable private mail, no matter how wrong they seem
to mail senders or third parties.  Filtering messages to IETF mailing
lists is justifiably controversial, but private mailboxes are none of
the IETF's business, and not merely because of scaling problems.

I care about this issue because other individual IETF and ASRG
participants have threatened or started attacks on me similar to Mr.
Anderson's attack on Mr. Austein, because my mail systems are configured
to reject their private (not sent via IETF reflectors) mail.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Sat Jun 19 05:35:50 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11835
	for <ietf-archive@ietf.org>; Sat, 19 Jun 2004 05:35:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbcGM-0006qr-C7
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 05:35:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbcFI-0006Bl-00
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 05:34:44 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbcDP-0005Ww-00; Sat, 19 Jun 2004 05:32:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbcAC-0000Rn-BN; Sat, 19 Jun 2004 05:29:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bbc8i-0000IB-58
	for ietf@megatron.ietf.org; Sat, 19 Jun 2004 05:27:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11531
	for <ietf@ietf.org>; Sat, 19 Jun 2004 05:27:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bbc8f-00049A-LM
	for ietf@ietf.org; Sat, 19 Jun 2004 05:27:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bbc7w-0003bN-00
	for ietf@ietf.org; Sat, 19 Jun 2004 05:27:09 -0400
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx with esmtp (Exim 4.12) id 1Bbc5z-00037M-00
	for ietf@ietf.org; Sat, 19 Jun 2004 05:25:07 -0400
Received: from andromeda (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i5J9P7mq027413 for ietf@ietf.org; Sat, 19 Jun 2004 11:25:07 +0200
Received: (from hadmut@localhost)
	by andromeda.dresden.danisch.de (8.12.11/8.12.11/Debian-5) id
	i5J9OZp9004294 for ietf@ietf.org; Sat, 19 Jun 2004 11:24:35 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Sat, 19 Jun 2004 11:24:35 +0200
To: ietf@ietf.org
Message-ID: <20040619092435.GA4198@danisch.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
Subject: 60th IETF - public transports?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

Hi,

does anyone know how one can get from San Diego 
downtown to the conference hotel without renting 
a car? Are there public transports? 
Rent a bicycle? 

regards
Hadmut

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


From ietf-bounces@ietf.org  Sat Jun 19 05:56:38 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12369
	for <ietf-archive@ietf.org>; Sat, 19 Jun 2004 05:56:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbcaU-0005rd-78
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 05:56:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbcZV-0005WZ-00
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 05:55:38 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbcYU-0004uK-00; Sat, 19 Jun 2004 05:54:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbcWS-0003bw-AT; Sat, 19 Jun 2004 05:52:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BbcQt-000377-HA
	for ietf@megatron.ietf.org; Sat, 19 Jun 2004 05:46:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12230
	for <ietf@ietf.org>; Sat, 19 Jun 2004 05:46:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BbcQr-0002h9-8y
	for ietf@ietf.org; Sat, 19 Jun 2004 05:46:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbcPu-0002NQ-00
	for ietf@ietf.org; Sat, 19 Jun 2004 05:45:42 -0400
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx with esmtp (Exim 4.12) id 1BbcPI-00024F-00
	for ietf@ietf.org; Sat, 19 Jun 2004 05:45:04 -0400
Received: from andromeda (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i5J9j5u7027837 for ietf@ietf.org; Sat, 19 Jun 2004 11:45:05 +0200
Received: (from hadmut@localhost)
	by andromeda.dresden.danisch.de (8.12.11/8.12.11/Debian-5) id
	i5J9gN9x005085 for ietf@ietf.org; Sat, 19 Jun 2004 11:42:23 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Sat, 19 Jun 2004 11:42:23 +0200
To: ietf@ietf.org
Message-ID: <20040619094223.GA4764@danisch.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
Subject: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

Hi,

at least here in Germany Internet providers tend to 
do and not to do what they want.

- Some cut off their clients every 24 hours (DSL)

- Some block or slowdown particular tcp ports 
  to get rid of peer-to-peer file sharing

- Some redirect the first web access to any site
  to their own to force you to read their ads

- Very few support multicast. When I asked my 
  own provider, they didn't even know what this is.
  (They said 'no, because they don't support Linux'.)

- IPv6? Huh? What's that? 

- At least one large provider blocks port 25 to certain IP 
  addresses in order to force you to use the provider's 
  mail relay and have the sender e-mail address replaced
  by the customers default address at the provider's domain.
  They say it's against spam, but I guess it's because they
  take money for opening the port and allowing to use
  SMTP and such any sender domain.

- ...


So it would be good to have some kind of 
standard or definition, what exactly an 
internet provider has to do and what to refrain 
from.

Is there any? If not, shouldn't there be one? 
E.g. as an RFC?

regards
Hadmut
 

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


From ietf-bounces@ietf.org  Sat Jun 19 06:01:28 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12694
	for <ietf-archive@ietf.org>; Sat, 19 Jun 2004 06:01:28 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbcfB-0007S4-2t
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 06:01:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bbce2-00072b-00
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 06:00:18 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bbcd9-0006aK-00; Sat, 19 Jun 2004 05:59:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbcWT-0003c3-BN; Sat, 19 Jun 2004 05:52:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BbcQv-00037D-SV
	for ietf@megatron.ietf.org; Sat, 19 Jun 2004 05:46:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12245
	for <ietf@ietf.org>; Sat, 19 Jun 2004 05:46:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BbcQt-0002hP-LV
	for ietf@ietf.org; Sat, 19 Jun 2004 05:46:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbcPw-0002Nn-00
	for ietf@ietf.org; Sat, 19 Jun 2004 05:45:44 -0400
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx with esmtp (Exim 4.12) id 1BbcPb-00024C-00
	for ietf@ietf.org; Sat, 19 Jun 2004 05:45:23 -0400
Received: by postman.ripe.net (Postfix, from userid 8)
	id D84914FE69; Sat, 19 Jun 2004 11:44:54 +0200 (CEST)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP
	id 910344E440; Sat, 19 Jun 2004 11:44:54 +0200 (CEST)
Received: from cow.ripe.net (cow.ripe.net [193.0.1.239])
	by birch.ripe.net (8.12.10/8.11.6) with ESMTP id i5J9is8r026038;
	Sat, 19 Jun 2004 11:44:54 +0200
Received: from localhost (henk@localhost)
	by cow.ripe.net (8.12.10/8.12.6) with ESMTP id i5J9isGV029651;
	Sat, 19 Jun 2004 11:44:54 +0200
X-Authentication-Warning: cow.ripe.net: henk owned process doing -bs
Date: Sat, 19 Jun 2004 11:44:54 +0200 (CEST)
From: "Henk Uijterwaal (RIPE NCC)" <henk@ripe.net>
To: Hadmut Danisch <hadmut@danisch.de>
In-Reply-To: <20040619092435.GA4198@danisch.de>
Message-ID: <Pine.LNX.4.58.0406191141360.28578@cow.ripe.net>
References: <20040619092435.GA4198@danisch.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-RIPE-Spam-Status: N 0.000003 / 0.0 / 0.0 / disabled
X-RIPE-Signature: b15e7ba303d836a0835f3f8dc10ffb18
Cc: ietf@ietf.org
Subject: Re: 60th IETF - public transports?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Sat, 19 Jun 2004, Hadmut Danisch wrote:

> does anyone know how one can get from San Diego downtown to the
> conference hotel without renting a car? Are there public transports?

If you fly in and stay at conference hotel, then you can take the hotel
shuttle at the airport.  5 minutes.  Probably 10-15 minute walk.

>From downtown there is a bus (992, see www.sdcommute.com) to the airport,
change to the hotel shuttle.

Henk

------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.amsterdamned.org/~henk
P.O.Box 10096          Singel 258         Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
The Netherlands        The Netherlands    Mobile: +31.6.55861746
------------------------------------------------------------------------------

Process and Procedure are the last hiding place of people without the wit
and wisdom to do their job properly.                          (David Brent).

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


From ietf-bounces@ietf.org  Sat Jun 19 07:34:44 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15681
	for <ietf-archive@ietf.org>; Sat, 19 Jun 2004 07:34:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bbe7Q-0006w6-VQ
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 07:34:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bbe6R-0006aR-00
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 07:33:43 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bbe5Q-0005eG-00; Sat, 19 Jun 2004 07:32:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bbe2x-0002ed-UP; Sat, 19 Jun 2004 07:30:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bbdww-0001mu-3r
	for ietf@megatron.ietf.org; Sat, 19 Jun 2004 07:23:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15426
	for <ietf@ietf.org>; Sat, 19 Jun 2004 07:23:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bbdwv-0003RI-KX
	for ietf@ietf.org; Sat, 19 Jun 2004 07:23:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bbdvt-00038L-00
	for ietf@ietf.org; Sat, 19 Jun 2004 07:22:49 -0400
Received: from 225.cust3.sa.dsl.ozemail.com.au ([210.84.226.225]
	helo=nosense.org) by ietf-mx with esmtp (Exim 4.12)
	id 1Bbdva-0002oQ-00
	for ietf@ietf.org; Sat, 19 Jun 2004 07:22:31 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id B44703F02A; Sat, 19 Jun 2004 20:51:53 +0930 (CST)
Date: Sat, 19 Jun 2004 20:51:53 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Hadmut Danisch <hadmut@danisch.de>
Message-Id: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040619094223.GA4764@danisch.de>
References: <20040619094223.GA4764@danisch.de>
Organization: The No Sense Organisation (http://www.nosense.org)
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i686-pc-linux-gnu)
X-Location: Adelaide, Australia
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Hi Hadmut,

On Sat, 19 Jun 2004 11:42:23 +0200
Hadmut Danisch <hadmut@danisch.de> wrote:

> Hi,
> 
> at least here in Germany Internet providers tend to 
> do and not to do what they want.
> 
> - Some cut off their clients every 24 hours (DSL)
> 
> - Some block or slowdown particular tcp ports 
>   to get rid of peer-to-peer file sharing
> 
> - Some redirect the first web access to any site
>   to their own to force you to read their ads
> 
> - Very few support multicast. When I asked my 
>   own provider, they didn't even know what this is.
>   (They said 'no, because they don't support Linux'.)
> 
> - IPv6? Huh? What's that? 
> 
> - At least one large provider blocks port 25 to certain IP 
>   addresses in order to force you to use the provider's 
>   mail relay and have the sender e-mail address replaced
>   by the customers default address at the provider's domain.
>   They say it's against spam, but I guess it's because they
>   take money for opening the port and allowing to use
>   SMTP and such any sender domain.
> 
> - ...
> 
> 
> So it would be good to have some kind of 
> standard or definition, what exactly an 
> internet provider has to do and what to refrain 
> from.
> 

I tend to come up with the answer to your question the following way :

(Q) What is the "Internet" ?

(A) A global network that runs the "Internet Protocols", and follows the
Internet architecture.


(Q) What is the Internet architecture ?

(A) It is described in RFC1958 - "Architectural Principles of the Internet"
(http://www.faqs.org/rfcs/rfc1958.html).

(Q) What does an Internet Service Provider do ?

(A) Provides access to the "Internet".


(Q) What if the "Internet Service Provider" doesn't provide access to the
Internet in a way that follows RFC1958 ?

(A) They aren't providing access to the Internet, so I think they shouldn't be
calling themselves an "Internet" service provider.

A number of things you describe, such as blocking port 25, redirecting URLs
etc. do not follow RFC1958. I don't consider those organisations to be
true ISPs, and I don't give them my "Internet" access business, as they don't
seem to be prepared to properly provide it.


Regards,
Mark.

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


From ietf-bounces@ietf.org  Sat Jun 19 11:00:09 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23686
	for <ietf-archive@ietf.org>; Sat, 19 Jun 2004 11:00:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbhKE-0002Qh-P4
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 11:00:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbhJG-00025b-00
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 10:59:10 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbhIo-0001jZ-00; Sat, 19 Jun 2004 10:58:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbhAq-0003bs-Vg; Sat, 19 Jun 2004 10:50:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bbh6U-0003ET-Lt
	for ietf@megatron.ietf.org; Sat, 19 Jun 2004 10:45:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23241
	for <ietf@ietf.org>; Sat, 19 Jun 2004 10:45:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bbh6T-0005f3-SS
	for ietf@ietf.org; Sat, 19 Jun 2004 10:45:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bbh5a-0005Ln-00
	for ietf@ietf.org; Sat, 19 Jun 2004 10:45:02 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1Bbh55-00051m-00
	for ietf@ietf.org; Sat, 19 Jun 2004 10:44:31 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i5JEi08Y021284
	for ietf@ietf.org env-from <vjs>;
	Sat, 19 Jun 2004 08:44:00 -0600 (MDT)
Date: Sat, 19 Jun 2004 08:44:00 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200406191444.i5JEi08Y021284@calcite.rhyolite.com>
To: ietf@ietf.org
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>

> > So it would be good to have some kind of 
> > standard or definition, what exactly an 
> > internet provider has to do and what to refrain 

> I tend to come up with the answer to your question the following way :
>
> (Q) What is the "Internet" ?

I prefer the definitions of various kinds of "Internet service" in
http://www.ietf.org/internet-drafts/draft-klensin-ip-service-terms-02.txt

Today, providers that sell sevices to users of Microsoft systems and
do not pay exquisite attention to which of them are infected with the
latest worms and viruses must block and redirect port 25 to their own
SMTP servers and so not provide what that draft calls "Full Internet
Connectivity."


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Sat Jun 19 18:48:13 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12423
	for <ietf-archive@ietf.org>; Sat, 19 Jun 2004 18:48:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbodD-0000bQ-3x
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 18:48:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbocL-0000JN-00
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 18:47:22 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bbobg-0007mz-00; Sat, 19 Jun 2004 18:46:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BboYc-0001Ev-8T; Sat, 19 Jun 2004 18:43:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BboTd-0000Km-MW
	for ietf@megatron.ietf.org; Sat, 19 Jun 2004 18:38:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12195
	for <ietf@ietf.org>; Sat, 19 Jun 2004 18:38:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BboTc-0005Pb-7v
	for ietf@ietf.org; Sat, 19 Jun 2004 18:38:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BboSw-00056w-00
	for ietf@ietf.org; Sat, 19 Jun 2004 18:37:39 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12) id 1BboSA-0004n5-00
	for ietf@ietf.org; Sat, 19 Jun 2004 18:36:50 -0400
Received: (qmail 27537 invoked from network); 19 Jun 2004 22:34:46 -0000
Received: from yahoobb219178198119.bbtec.net (HELO necom830.hpcl.titech.ac.jp)
	(219.178.198.119)
	by necom830.hpcl.titech.ac.jp with SMTP; 19 Jun 2004 22:34:46 -0000
Message-ID: <40D4C129.8000601@necom830.hpcl.titech.ac.jp>
Date: Sun, 20 Jun 2004 07:41:45 +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: Hadmut Danisch <hadmut@danisch.de>
References: <20040619094223.GA4764@danisch.de>
In-Reply-To: <20040619094223.GA4764@danisch.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Hadmut Danisch wrote:

> Is there any? If not, shouldn't there be one? 
> E.g. as an RFC?

Here is an old Internet Draft, which IESG at that time refused
to make it RFC, because some wanted to call NAT providers ISPs.

					Masataka Ohta

--
INTERNET DRAFT                                                   M. Ohta
draft-ohta-isps-00.txt                     Tokyo Institute of Technology
                                                               July 2000

                         The Internet and ISPs

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   Copyright (C) The Internet Society (May/1/2000).  All Rights
   Reserved.

Abstract

   This memo gives definitions on the Internet and ISPs (Internet
   Service Providers).

1. The Internet

   The Internet is a public IP [1, 2] network globally connected end to
   end [3] at the Internetworking layer.

2. ISPs

   A network provider is an ISP, if and only if its network, including
   access parts of the network to its subscribers, is a part of the
   Internet.

   As such, ISPs must preserve the end to end and globally connected
   principles of the Internet at the Internetworking layer.



M. Ohta                Expires on January 1, 2001               [Page 1]

INTERNET DRAFT                    ISPs                         July 2000


   A network provider of a private IP or non-IP network, which is
   connected to the Internet through an application and/or transport
   gateway is not an ISP.

   Dispit the requirement of "global connectivity", a network provider
   may use transparent firewalls to the Internet with no translation to
   filter out a limited number of problematic well known ports of TCP
   and/or UDP and can still be an ISP.  However, if filtering out is a
   default and only a limited number of protocols are allowed to pass
   the firewalls (which means snooping of transport/application layer
   protocols), it can not be regarded as full connectivity to the
   Internet and the provider is not an ISP.

3. Security Considerations

   While some people may think that filtering by application/transport
   gateways offer some sort of security, they should recognize that
   macro virus in e-mails can pass and are passing through all such
   gateways.

4. References

   [1] J. Postel, "Internet Protocol", RFC791, September 1981.

   [2] S. Deering, R. Hinden, "Internet Protocol, Version 6 (IPv6)
   Specification", RFC2460, December 1998.

   [3] B. Carpenter, "Architectural Principles of the Internet",
   RFC1958, June 1996.

5. Author's Address

   Masataka Ohta
   Computer Center, Tokyo Institute of Technology
   2-12-1, O-okayama, Meguro-ku, Tokyo 152-8550, JAPAN

   Phone: +81-3-5734-3299
   Fax: +81-3-5734-3415
   EMail: mohta@necom830.hpcl.titech.ac.jp












M. Ohta                Expires on January 1, 2001               [Page 2]

INTERNET DRAFT                    ISPs                         July 2000


6. Full Copyright Statement

   "Copyright (C) The Internet Society (July/1/2000).  All Rights
   Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.























M. Ohta                Expires on January 1, 2001               [Page 3]



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


From ietf-bounces@ietf.org  Sat Jun 19 18:54:22 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12740
	for <ietf-archive@ietf.org>; Sat, 19 Jun 2004 18:54:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bboj9-0002dm-U1
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 18:54:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bboi4-0002Fv-00
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 18:53:16 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bboh8-0001Ho-00; Sat, 19 Jun 2004 18:52:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BboYd-0001F4-9N; Sat, 19 Jun 2004 18:43:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BboWO-0000l4-ST
	for ietf@megatron.ietf.org; Sat, 19 Jun 2004 18:41:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12250
	for <ietf@ietf.org>; Sat, 19 Jun 2004 18:41:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BboWN-0006J2-F7
	for ietf@ietf.org; Sat, 19 Jun 2004 18:41:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BboVV-00060f-00
	for ietf@ietf.org; Sat, 19 Jun 2004 18:40:18 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12) id 1BboUi-0005iW-00
	for ietf@ietf.org; Sat, 19 Jun 2004 18:39:28 -0400
Received: (qmail 27545 invoked from network); 19 Jun 2004 22:37:33 -0000
Received: from yahoobb219178198119.bbtec.net (HELO necom830.hpcl.titech.ac.jp)
	(219.178.198.119)
	by necom830.hpcl.titech.ac.jp with SMTP; 19 Jun 2004 22:37:33 -0000
Message-ID: <40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
Date: Sun, 20 Jun 2004 07:44:31 +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: Vernon Schryver <vjs@calcite.rhyolite.com>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
In-Reply-To: <200406191444.i5JEi08Y021284@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Vernon Schryver wrote:

> I prefer the definitions of various kinds of "Internet service" in
> http://www.ietf.org/internet-drafts/draft-klensin-ip-service-terms-02.txt

It confuses "Internet service" and "IP service" and calls
even a NAT provider ISP.

   In each case, the terminology refers to the intent of the
   provider (ISP)

It is not an acceptable definition.

   The definitions proposed here are clearly of little value if service
   providers and vendors are not willing to adopt them.  Consequently,
   the terms proposed are intended to not be pejorative,

The draft attempts to authorize NAT providers call themselves ISP.

Then, the NAT providers are willing to adopt it and just call
themselves not "web providers" but ISPs. So, the draft is
useless.

The only meaningful thing for IETF to do is define what is "ISP"
as a terminology within IETF.

There are a lot of IETF standard track documents of little value
ignored by service providers and vendors. So, don't bother.

							Masataka Ohta



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


From ietf-bounces@ietf.org  Sat Jun 19 23:50:31 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26915
	for <ietf-archive@ietf.org>; Sat, 19 Jun 2004 23:50:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbtLk-00061T-9C
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 23:50:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbtKk-0005iy-00
	for ietf-archive@ietf.org; Sat, 19 Jun 2004 23:49:31 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbtK8-0005QF-00; Sat, 19 Jun 2004 23:48:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbtDx-0008Ph-QK; Sat, 19 Jun 2004 23:42:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BbtCx-00086b-3h
	for ietf@megatron.ietf.org; Sat, 19 Jun 2004 23:41:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26595
	for <ietf@ietf.org>; Sat, 19 Jun 2004 23:41:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BbtCv-0003R0-4I
	for ietf@ietf.org; Sat, 19 Jun 2004 23:41:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbtC1-00039x-00
	for ietf@ietf.org; Sat, 19 Jun 2004 23:40:30 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BbtBe-0002sf-00
	for ietf@ietf.org; Sat, 19 Jun 2004 23:40:07 -0400
Received: from scan.jck.com ([209.187.148.215])
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BbtBb-000Jan-00; Sat, 19 Jun 2004 22:40:03 -0500
Date: Sat, 19 Jun 2004 23:40:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>,
        Vernon Schryver <vjs@calcite.rhyolite.com>
Message-ID: <F950E0BB956E7C80978BEC84@scan.jck.com>
In-Reply-To: <40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e444044
	5758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Ohta-san,

I do not expect that we will agree on this, and may need to
simply agree to disagree, but, having just reviewed the draft
you included in your slightly earlier not, let me try to explain
the other point of view, and why the I-D to which Vernon refers
is written the way it is and, in the process, I hope, respond to
some of Hadmut's concerns...

The IETF has absolutely not ability to insist that an provider
of IP services, or various good or bad or terrible
approximations to IP servers, do or not do anything.  If we were
to establish a document that said, e.g., "you are not an ISP,
and must not call yourself an ISP, unless you conform to the
following rules", I would expect the low-service providers to
simply ignore us.   That helps no one.

Instead, I think there are only two courses of action that have
a chance of making progress on this issue.  And I think they are
complementary, rather than competing, actions.

First, Hadmut, and others with his concerns in other countries,
probably need to approach the local regulatory authorities who
are concerned about consumer fraud and say "the range of things
that people are selling under the name 'Internet service'
includes too broad a range.  People are confused, and suppliers
are insisting that people make long-term commitments to
particular providers with any real idea what they are getting,
and that is poor public policy and you should do something about
it".

Second, the IETF should consider standardizing (or making a BCP
out of) some terminology similar to that in the I-D.  The intent
of that document is to lay a foundation for encouraging service
providers to explain what they are offering in language that
people can understand and, if the local/national regulators
think it appropriate, telling service providers what they need
to disclose and in what terms.  

Whether we like it or not, there are users (of what those users
think of as "the Internet") who would be perfectly happy with a
web-only, all outbound protocols but HTTP and HTTPS blocked, all
inbound ports blocked except responses to the above, private
address space, and all connections dropped and a new address
assigned every half-hour "service"... as long as it is cheap
enough.  I wouldn't want such a "service", I gather Vernon
wouldn't, and you probably wouldn't want it either.  But I don't
see a problem with those who want it getting it, as long as no
one is deceiving them (or anything else) about what they are
getting.   

And it is precisely the "no lying about why you are selling"
aspect of this that the I-D is addressed to, not an (almost
certainly useless) attempt to proscribe particular services or
terminology.

regards,
    john


--On Sunday, 20 June, 2004 07:44 +0900 Masataka Ohta
<mohta@necom830.hpcl.titech.ac.jp> wrote:

> Vernon Schryver wrote:
> 
>> I prefer the definitions of various kinds of "Internet
>> service" in
>> http://www.ietf.org/internet-drafts/draft-klensin-ip-service-
>> terms-02.txt
> 
> It confuses "Internet service" and "IP service" and calls
> even a NAT provider ISP.
> 
>    In each case, the terminology refers to the intent of the
>    provider (ISP)
> 
> It is not an acceptable definition.
> 
>    The definitions proposed here are clearly of little value
> if service    providers and vendors are not willing to adopt
> them.  Consequently,    the terms proposed are intended to not
> be pejorative,
> 
> The draft attempts to authorize NAT providers call themselves
> ISP.
> 
> Then, the NAT providers are willing to adopt it and just call
> themselves not "web providers" but ISPs. So, the draft is
> useless.
> 
> The only meaningful thing for IETF to do is define what is
> "ISP" as a terminology within IETF.
> 
> There are a lot of IETF standard track documents of little
> value ignored by service providers and vendors. So, don't
> bother.
> 
> 							Masataka Ohta
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf





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


From ietf-bounces@ietf.org  Sun Jun 20 04:39:34 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22752
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 04:39:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbxrR-00010k-NM
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 04:39:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbxqT-0000kF-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 04:38:34 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbxpP-0000G6-00; Sun, 20 Jun 2004 04:37:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bbxn7-0006Ec-3b; Sun, 20 Jun 2004 04:35:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bbxjx-0005kB-Io
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 04:31:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22418
	for <ietf@ietf.org>; Sun, 20 Jun 2004 04:31:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bbxjv-0006kL-Ay
	for ietf@ietf.org; Sun, 20 Jun 2004 04:31:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bbxip-0006Ue-00
	for ietf@ietf.org; Sun, 20 Jun 2004 04:30:39 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12) id 1BbxiB-0006FT-00
	for ietf@ietf.org; Sun, 20 Jun 2004 04:30:00 -0400
Received: (qmail 29745 invoked from network); 20 Jun 2004 08:28:12 -0000
Received: from yahoobb219178198119.bbtec.net (HELO necom830.hpcl.titech.ac.jp)
	(219.178.198.119)
	by necom830.hpcl.titech.ac.jp with SMTP; 20 Jun 2004 08:28:12 -0000
Message-ID: <40D54C36.80202@necom830.hpcl.titech.ac.jp>
Date: Sun, 20 Jun 2004 17:35: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: John C Klensin <john-ietf@jck.com>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e444044	5758487a.nosense.org>	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
In-Reply-To: <F950E0BB956E7C80978BEC84@scan.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Vernon Schryver <vjs@calcite.rhyolite.com>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

John C Klensin;

You made, at least, two mistakes, minor and major ones.

A minor mistake is that you think you can let people outside
of IETF use your terminology, if you give loose enough
terminlogy.

As you introduce "Web connectivity", such people (including
mobile operators in Japan) claim that they are ISPs, because
they are offering web connectivity over X.25 without IP. That
is, "The definitions proposed here are clearly of little value
if service providers and vendors are not willing to adopt them."
is applicable to your draft.

A major mistake is that you are forcing people within IETF
use your terminology even though you are fully aware that
"some members of the IETF community that some of these
connectively models are simply "broken" or "not really an
Internet service"".

						Masataka Ohta



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


From ietf-bounces@ietf.org  Sun Jun 20 06:19:48 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26425
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 06:19:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BbzQR-00025U-Tg
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 06:19:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbzPQ-0001r9-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 06:18:45 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BbzP3-0001d9-00; Sun, 20 Jun 2004 06:18:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BbzMm-0003Id-3L; Sun, 20 Jun 2004 06:16:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BbzLZ-0002vf-OK
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 06:14:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26262
	for <ietf@ietf.org>; Sun, 20 Jun 2004 06:14:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BbzLX-0000vK-CC
	for ietf@ietf.org; Sun, 20 Jun 2004 06:14:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbzKa-0000gv-00
	for ietf@ietf.org; Sun, 20 Jun 2004 06:13:45 -0400
Received: from 225.cust3.sa.dsl.ozemail.com.au ([210.84.226.225]
	helo=nosense.org) by ietf-mx with esmtp (Exim 4.12)
	id 1BbzKG-0000Sp-00
	for ietf@ietf.org; Sun, 20 Jun 2004 06:13:25 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP id A25C83F02A
	for <ietf@ietf.org>; Sun, 20 Jun 2004 19:42:48 +0930 (CST)
Date: Sun, 20 Jun 2004 19:42:48 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: ietf@ietf.org
Message-Id: <20040620194248.286bbaed.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <F950E0BB956E7C80978BEC84@scan.jck.com>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e444044
	5758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
Organization: The No Sense Organisation (http://www.nosense.org)
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i686-pc-linux-gnu)
X-Location: Adelaide, Australia
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

On Sat, 19 Jun 2004 23:40:03 -0400
John C Klensin <john-ietf@jck.com> wrote:

> Ohta-san,
> 
> I do not expect that we will agree on this, and may need to
> simply agree to disagree, but, having just reviewed the draft
> you included in your slightly earlier not, let me try to explain
> the other point of view, and why the I-D to which Vernon refers
> is written the way it is and, in the process, I hope, respond to
> some of Hadmut's concerns...
> 
> The IETF has absolutely not ability to insist that an provider
> of IP services, or various good or bad or terrible
> approximations to IP servers, do or not do anything. 

I agree that the IETF doesn't have the right to tell private, commercial
organisations how to run their business, and what types of services they can
or can't offer customers.

However, I think the IETF are in the position to make statements to the effect
that if "Internet" services are being offered in a manner that doesn't follow
the operational design and architecture of the Internet Protocols, as
outlined in RFC1958, then the end users of those services only have available
to them a limited subset of the features, benefits and capabilities of the
Internet. We are discussing IETF designed and developed protocols, which I
think puts the IETF in a position to state how they _should_ be used.

It also appears that the IAB are willing to make statements discouraging
certain practices, such as port filtering. Such a statement is at the
following URL :

"IAB concerns against permanent deployment of edge-based filtering"
http://www.iab.org/documents/docs/2003-10-18-edge-filters.html



 If we were
> to establish a document that said, e.g., "you are not an ISP,
> and must not call yourself an ISP, unless you conform to the
> following rules", I would expect the low-service providers to
> simply ignore us.   That helps no one.
> 
> Instead, I think there are only two courses of action that have
> a chance of making progress on this issue.  And I think they are
> complementary, rather than competing, actions.
> 
> First, Hadmut, and others with his concerns in other countries,
> probably need to approach the local regulatory authorities who
> are concerned about consumer fraud and say "the range of things
> that people are selling under the name 'Internet service'
> includes too broad a range.  People are confused, and suppliers
> are insisting that people make long-term commitments to
> particular providers with any real idea what they are getting,
> and that is poor public policy and you should do something about
> it".
> 
> Second, the IETF should consider standardizing (or making a BCP
> out of) some terminology similar to that in the I-D.  The intent
> of that document is to lay a foundation for encouraging service
> providers to explain what they are offering in language that
> people can understand and, if the local/national regulators
> think it appropriate, telling service providers what they need
> to disclose and in what terms.  
> 

Bare in mind that documenting something in an RFC, even if the majority of the
IETF disagree with it, is commonly interpreted as giving it a level of
legitimacy. I've found that a lot of networking people in the enterprise/ISP
world (a) don't read RFCs and (b) consider that something being listed as in
an RFC automatically implies the blessing of the IETF / IESG / IAB.

For example, the original NAT RFC (RFC1631) contains the following
statement :

--
4. Conclusions

   NAT may be a good short term solution to the address depletion and
   scaling problems. This is because it requires very few changes and
   can be installed incrementally. NAT has several negative
   characteristics that make it inappropriate as a long term solution,
   and may make it inappropriate even as a short term solution. Only
   implementation and experimentation will determine its
   appropriateness.
--

How many people who bought "RFC 1631" compliant NAT boxes were aware that the
value of the solution documented in RFC1631 was considered questionable by
the authors of the RFC itself? I'd suspect very few. I know I though it was a
good idea for a while, until I got burned by it.


> Whether we like it or not, there are users (of what those users
> think of as "the Internet") who would be perfectly happy with a
> web-only, all outbound protocols but HTTP and HTTPS blocked, all
> inbound ports blocked except responses to the above, private
> address space, and all connections dropped and a new address
> assigned every half-hour "service"... as long as it is cheap
> enough.

I think these innocent and naive users are really being done a disservice.
The Internet is and will be far more capable that just these services - the
current architecture ensures that. I think it is important that the more
knowledgable attempt to ensure that the innocent are not taken advantage of,
nor denied access to the full capabilities that the Internet achitecture
provides.

Regards,
Mark.

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


From ietf-bounces@ietf.org  Sun Jun 20 06:58:48 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28194
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 06:58:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bc02C-0003LW-U9
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 06:58:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc01C-00036W-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 06:57:47 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bc00W-0002jm-00; Sun, 20 Jun 2004 06:57:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bbzwz-0008Sd-IH; Sun, 20 Jun 2004 06:53:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BbzvM-0008Dw-2y
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 06:51:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27956
	for <ietf@ietf.org>; Sun, 20 Jun 2004 06:51:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BbzvJ-0001jy-GD
	for ietf@ietf.org; Sun, 20 Jun 2004 06:51:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbzuL-0001NZ-00
	for ietf@ietf.org; Sun, 20 Jun 2004 06:50:42 -0400
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx with esmtp (Exim 4.12) id 1Bbzts-00017h-00
	for ietf@ietf.org; Sun, 20 Jun 2004 06:50:12 -0400
Received: from andromeda (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i5KAo8E3024186 for ietf@ietf.org; Sun, 20 Jun 2004 12:50:08 +0200
Received: (from hadmut@localhost)
	by andromeda.dresden.danisch.de (8.12.11/8.12.11/Debian-5) id
	i5KAjJA3032174 for ietf@ietf.org; Sun, 20 Jun 2004 12:45:19 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Sun, 20 Jun 2004 12:45:19 +0200
To: ietf@ietf.org
Message-ID: <20040620104519.GA31597@danisch.de>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F950E0BB956E7C80978BEC84@scan.jck.com>
User-Agent: Mutt/1.5.6i
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Sat, Jun 19, 2004 at 11:40:03PM -0400, John C Klensin wrote:

> First, Hadmut, and others with his concerns in other countries,
> probably need to approach the local regulatory authorities who
> are concerned about consumer fraud and say "the range of things
> that people are selling under the name 'Internet service'
> includes too broad a range.

Correct in principle, but no chance to do it in reality.

If I contact the regulatory authorities, they will ask
me "What's wrong with those ISP's?"

I answer "They do... and the don't..."

They'd say: Uhm, we're familiar with the Internet in 
common, but not with all those details. Most people seem 
to be happy with that, and if not, why don't you change to
a provider of your taste? We don't see why there is a need
to change the status quo of ISPs. 

I'd reply: Because that's not correct. This is not "Internet". 
This is some approx. This causes technical problems. This is 
fraud.

They'd say: Who are you to tell what's correct and what's 
"Internet"? Nobody has ever defined that term. If there
is no definition, then there is no "correct" or "not correct".



But if we had a precise definition and a taxonomy of the 
different classes of ISPs, I could say: Look, the 
IETF has given a definition. They're the guys who
control the internet and keep it running well. They
are exactly the ones to tell what's correct and 
what's not. And now, some of those german providers
are violating law. Because they are actually advertising
to provide internet, what they in fact don't do. 
False advertising is unlawful. 

regards
Hadmut

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


From ietf-bounces@ietf.org  Sun Jun 20 09:51:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06023
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 09:51:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bc2jd-0004Un-P1
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 09:51:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc2ig-0004Hq-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 09:50:51 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bc2iD-00044j-00; Sun, 20 Jun 2004 09:50:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bc2fW-0004DX-BE; Sun, 20 Jun 2004 09:47:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bc2Yz-0003eJ-NN
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 09:40:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05590
	for <ietf@ietf.org>; Sun, 20 Jun 2004 09:40:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bc2Yy-0001z9-Uh
	for ietf@ietf.org; Sun, 20 Jun 2004 09:40:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc2Y5-0001mO-00
	for ietf@ietf.org; Sun, 20 Jun 2004 09:39:54 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12) id 1Bc2XD-0001ZJ-00
	for ietf@ietf.org; Sun, 20 Jun 2004 09:38:59 -0400
Received: (qmail 31053 invoked from network); 20 Jun 2004 13:37:09 -0000
Received: from yahoobb219001188031.bbtec.net (HELO necom830.hpcl.titech.ac.jp)
	(219.1.188.31)
	by necom830.hpcl.titech.ac.jp with SMTP; 20 Jun 2004 13:37:09 -0000
Message-ID: <40D5949E.6020407@necom830.hpcl.titech.ac.jp>
Date: Sun, 20 Jun 2004 22:43:58 +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: Hadmut Danisch <hadmut@danisch.de>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
In-Reply-To: <20040620104519.GA31597@danisch.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Hadmut Danisch;

Do you think a NAT provider an ISP?

> But if we had a precise definition and a taxonomy of the 
> different classes of ISPs,

Then, all the IP and non-IP providers can now leagaly (some
illegaly a little beyond the scope of so generous RFC) say
they are ISPs and most end users have no chance to know the
differences of the taxonomy.

						Masataka Ohta



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


From ietf-bounces@ietf.org  Sun Jun 20 10:44:52 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09690
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 10:44:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bc3Yz-0000xd-HU
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 10:44:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc3Y0-0000kU-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 10:43:53 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bc3Xj-0000Y6-00; Sun, 20 Jun 2004 10:43:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bc3Tp-0007tk-GI; Sun, 20 Jun 2004 10:39:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bc3RH-0007cp-1T
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 10:36:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09344
	for <ietf@ietf.org>; Sun, 20 Jun 2004 10:36:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bc3RG-0006x4-AM
	for ietf@ietf.org; Sun, 20 Jun 2004 10:36:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc3QK-0006kL-00
	for ietf@ietf.org; Sun, 20 Jun 2004 10:35:57 -0400
Received: from 206-169-2-196.gen.twtelecom.net ([206.169.2.196]
	helo=mail.optistreams.net) by ietf-mx with esmtp (Exim 4.12)
	id 1Bc3Q0-0006XH-00
	for ietf@ietf.org; Sun, 20 Jun 2004 10:35:36 -0400
Received: from [192.168.1.100] [66.82.50.1] by mail.optistreams.net with ESMTP
	(SMTPD32-8.04) id AAD8937006C; Sun, 20 Jun 2004 07:10:32 -0700
In-Reply-To: <40D5949E.6020407@necom830.hpcl.titech.ac.jp>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <D9CD0DEC-C2C6-11D8-AC93-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
From: Nathaniel Borenstein <nsb@guppylake.com>
Date: Sun, 20 Jun 2004 10:33:52 -0400
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
X-Mailer: Apple Mail (2.618)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Hadmut Danisch <hadmut@danisch.de>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

It seems to me that there is genuine value in having the IETF define 
terms that distinguish the various types of connectivity, not because 
the IETF can (or should try) to enforce anything, but to provide 
authoritative normative terminology that might, in some jurisdictions, 
help provide a legal basis for egregious cases of false advertising.

In particular, it would be nice to have *some* term like "Full internet 
Connectivity" that defines the high-end service that really can't be 
credibly claimed by the lower-end services.   I'm skeptical, however, 
that we can rescue the term "ISP" from the low-end services that 
already claim that label.  Rather than fight over the pre-existing term 
"ISP", why not try to converge on a new term with a more clearly 
defined meaning from day one, based on a document from the IETF?  After 
all, the low-end services can legitimately claim to provide *some* 
Internet services, just not *most* of them, which makes them in some 
sense "Partial ISP's" and unlikely to give up the "ISP" label 
willingly.    Instead, we could invent (and try to popularize) a new 
term such as "Complete High-End Internet Service Providers" (CHISPs) or 
"Providers of Internet General Services" (PIGS).  :-)

Anyway, I fear that trying to convince a bunch of low-end providers not 
to call themselves ISPs is about hopeless as trying to convince people 
who believe in massive budget deficits and preemptive wars not to call 
themselves conservatives.  -- Nathaniel


On Jun 20, 2004, at 9:43 AM, Masataka Ohta wrote:

> Hadmut Danisch;
>
> Do you think a NAT provider an ISP?
>
>> But if we had a precise definition and a taxonomy of the
>> different classes of ISPs,
>
> Then, all the IP and non-IP providers can now leagaly (some
> illegaly a little beyond the scope of so generous RFC) say
> they are ISPs and most end users have no chance to know the
> differences of the taxonomy.
>
> 						Masataka Ohta
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>
>


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


From ietf-bounces@ietf.org  Sun Jun 20 11:00:03 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10416
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 11:00:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bc3ng-0004Qs-7B
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 11:00:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc3mk-0004Cv-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 10:59:06 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bc3ly-0003x3-00; Sun, 20 Jun 2004 10:58:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bc3hM-0001Mt-HC; Sun, 20 Jun 2004 10:53:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bc3fm-00019u-8q
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 10:51:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10008
	for <ietf@ietf.org>; Sun, 20 Jun 2004 10:51:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bc3fl-0002ZQ-Fv
	for ietf@ietf.org; Sun, 20 Jun 2004 10:51:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc3ek-0002Lj-00
	for ietf@ietf.org; Sun, 20 Jun 2004 10:50:51 -0400
Received: from [217.145.240.22] (helo=abaghir) by ietf-mx with smtp (Exim 4.12)
	id 1Bc3dn-00027N-00
	for ietf@ietf.org; Sun, 20 Jun 2004 10:49:52 -0400
Date: Sun, 20 Jun 2004 17:53:28 +0300
To: ietf@ietf.org
From: staff@ietf.org
Message-ID: <afhxsbtjaqxsaorlixc@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------ghbhprtbjqdwrvjidtbr"
Subject: E-mail account security warning.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=NO_REAL_NAME autolearn=no 
	version=2.60

----------ghbhprtbjqdwrvjidtbr
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dear user of e-mail server "Ietf.org",

Your e-mail account  will  be disabled because of  improper using in  next
three  days,  if you are  still wishing to  use it,  please, resign your
account information.

Pay attention on attached  file.

Sincerely,
   The  Ietf.org  team                               http://www.ietf.org

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

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

----------ghbhprtbjqdwrvjidtbr
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

----------ghbhprtbjqdwrvjidtbr--




From ietf-bounces@ietf.org  Sun Jun 20 11:27:16 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11788
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 11:27:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bc4E1-0002Is-Aq
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 11:27:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc4Cx-00023X-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 11:26:12 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bc4CU-0001oi-00; Sun, 20 Jun 2004 11:25:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bc47N-0004jL-JE; Sun, 20 Jun 2004 11:20:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bc44C-0004HM-Vm
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 11:17:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11278
	for <ietf@ietf.org>; Sun, 20 Jun 2004 11:17:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bc445-0000Li-AQ
	for ietf@ietf.org; Sun, 20 Jun 2004 11:17:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc41P-0007jD-00
	for ietf@ietf.org; Sun, 20 Jun 2004 11:14:16 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1Bc40c-0007RI-00
	for ietf@ietf.org; Sun, 20 Jun 2004 11:13:26 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i5KFCtiB038558
	for ietf@ietf.org env-from <vjs>;
	Sun, 20 Jun 2004 09:12:55 -0600 (MDT)
Date: Sun, 20 Jun 2004 09:12:55 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200406201512.i5KFCtiB038558@calcite.rhyolite.com>
To: ietf@ietf.org
References: <40D54C36.80202@necom830.hpcl.titech.ac.jp>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>

> As you introduce "Web connectivity", such people (including
> mobile operators in Japan) claim that they are ISPs, because
> they are offering web connectivity over X.25 without IP. 

WebTV is functionally the same as web connectivity over X.25 without
IP.  Most of the world thinks that part of Microsoft is an "ISP."
Nothing the IETF or even governments could do would change that.

>                                                          That
> is, "The definitions proposed here are clearly of little value
> if service providers and vendors are not willing to adopt them."

Those involved call the services of WebTV either "WebTV" or "Internet
service."  Professionals (including salespeople) who are not employed
by Microsoft in the WebTV operation, especially competitors, would be
happy to call it "Web Connectivity" instead of "WebTV."  Even Microsoft
might like "Web Connectivity" to limit dilution of its "WebTV" trademark.

Thus such concerns are irrelevant to "Web Connectivity."
You'd do better attacking one of the other categories.


> A major mistake is that you are forcing people within IETF
> use your terminology even though you are fully aware that
> "some members of the IETF community that some of these
> connectively models are simply "broken" or "not really an
> Internet service"".

No, the major mistake is thinking the various classes of IP service
do not exist or that you can keep people from naming them with short
English words or phrases.  As the various classes become more popular
and widely recognized, the world will invent and use terms for them.
No one but pedants and marketers will care which words or phrases are
ultimately chosen.  The IETF can speed up and slightly steer the choice,
but no one can prevent it.  We got to choose the word "Internet" but
did not entirely control the definition (recall small 'i' "internet").
We lost on "intranet" "catnet" and many other terms.

The useful things that this draft might accomplish are:

 - make the choice of terms happen within or a year instead of the
    years that the current definition "Internet" needed.

 - make the people who have more control than the IETF over the choice
    of terms for the emerging clases Internet service think about the
    words they want.  They are in marketing organizations.

Consumer ISPs are not offering the kinds or classes of IP service that
I would want.  It is insane to ignore that reality.  It would be little
better to insist that governments will not eventually get involved or
that there will be no common terms for the various common classes of
IP services and ISPs.



]  From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>

]  > But if we had a precise definition and a taxonomy of the 
]  > different classes of ISPs,
] 
]  Then, all the IP and non-IP providers can now leagaly (some
]  illegaly a little beyond the scope of so generous RFC) say
]  they are ISPs and most end users have no chance to know the
]  differences of the taxonomy.

No, 
  - Whatever happens with this draft, it will not have anything like
     the force of law.  The IETF does not have powers over terms
     equivalent to the groups that name species, chemical compounds,
     and astronomical bodies.

  - all the IP and non-IP providers in most of the world can now
     legally call themselves "ISPs."  The IETF could not change that.

  - The terms the world eventually uses for the various classes of IP
     service and types of ISPs will differ from the consensus of the
     IETF.  This draft can only crystalize the choices.  Seed crystals
     influence the shape of a solid, but do not control it.

  - the main reason "end users have no chance to know the differences"
     delineated by the taxonomy is that the taxonomy does not yet
     exist.  When it exists, users will know as much of it as they
     care to, just as they now know or don't know the differences among
     "web," "Internet," and "telephone." 

     Users who do not distinguish between "web" and "Internet" also
     think "WebTV" is Internet service.  IETF cannot change that.  That
     VoIP, text messaging, and cell phones are changing the definitions
     of "telephone" and "telephone company" is part of my point.

Much of the good this draft might do will be done simply by discussing
in public differences among IP service classes and choices of terms.
After the taxonomy is crystalized, it will be out of the IETF's control.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Sun Jun 20 13:08:17 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16521
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 13:08:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bc5nm-0001vo-Ju
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 13:08:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc5mp-0001dH-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 13:07:19 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bc5lu-0001Es-00; Sun, 20 Jun 2004 13:06:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bc5fB-0001Yb-D8; Sun, 20 Jun 2004 12:59:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bc5az-00016j-DM
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 12:55:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15937
	for <ietf@ietf.org>; Sun, 20 Jun 2004 12:55:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bc5ay-0006as-6r
	for ietf@ietf.org; Sun, 20 Jun 2004 12:55:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc5a8-0006Na-00
	for ietf@ietf.org; Sun, 20 Jun 2004 12:54:12 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12)
	id 1Bc5ZW-000689-00
	for ietf@ietf.org; Sun, 20 Jun 2004 12:53:34 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 20 Jun 2004 09:55:47 +0000
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i5KGqp72001596;
	Sun, 20 Jun 2004 09:52:51 -0700 (PDT)
Received: from localhost (ole@localhost) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id JAA10768;
	Sun, 20 Jun 2004 09:52:51 -0700 (PDT)
Date: Sun, 20 Jun 2004 09:52:51 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-Reply-To: <40D5949E.6020407@necom830.hpcl.titech.ac.jp>
Message-ID: <Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org, Hadmut Danisch <hadmut@danisch.de>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

Much as I understand the moral outrage that NATs cause in some people's
mind, NATs are still a reality AND they (usually anyway) provide
connectivity to the Internet. Have you tried using a hotelroom Ethernet
port or a WiFi network recently? I can't remember the last time I was
assigned something that looked like a "real" routable IP address, but
as a consumer of paid-for Internet service (that works) is there any
reason (apart from religion) that I should care??

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Academic Research and Technology Initiatives, Cisco Systems
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj



On Sun, 20 Jun 2004, Masataka Ohta wrote:

> Hadmut Danisch;
>
> Do you think a NAT provider an ISP?
>
> > But if we had a precise definition and a taxonomy of the
> > different classes of ISPs,
>
> Then, all the IP and non-IP providers can now leagaly (some
> illegaly a little beyond the scope of so generous RFC) say
> they are ISPs and most end users have no chance to know the
> differences of the taxonomy.
>
> 						Masataka Ohta
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

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


From ietf-bounces@ietf.org  Sun Jun 20 13:49:03 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18285
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 13:49:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bc6RD-0003Y8-Jj
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 13:49:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc6QM-0003Ig-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 13:48:11 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bc6Oa-0002db-00; Sun, 20 Jun 2004 13:46:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bc6LD-0006u7-7n; Sun, 20 Jun 2004 13:42:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bc6KR-0006nA-3C
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 13:42:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18010
	for <ietf@ietf.org>; Sun, 20 Jun 2004 13:42:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bc6KQ-0001uL-0s
	for ietf@ietf.org; Sun, 20 Jun 2004 13:42:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc6JU-0001gj-00
	for ietf@ietf.org; Sun, 20 Jun 2004 13:41:05 -0400
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx with esmtp (Exim 4.12) id 1Bc6Ii-0001TE-00
	for ietf@ietf.org; Sun, 20 Jun 2004 13:40:16 -0400
Received: from andromeda (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i5KHe7OA032106; Sun, 20 Jun 2004 19:40:07 +0200
Received: (from hadmut@localhost)
	by andromeda.dresden.danisch.de (8.12.11/8.12.11/Debian-5) id
	i5KHbEbk016574; Sun, 20 Jun 2004 19:37:14 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Sun, 20 Jun 2004 19:37:14 +0200
To: Ole Jacobsen <ole@cisco.com>
Message-ID: <20040620173714.GA16092@danisch.de>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>
	<Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>
User-Agent: Mutt/1.5.6i
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Sun, Jun 20, 2004 at 09:52:51AM -0700, Ole Jacobsen wrote:
> Much as I understand the moral outrage that NATs cause in some people's
> mind, NATs are still a reality AND they (usually anyway) provide
> connectivity to the Internet. Have you tried using a hotelroom Ethernet
> port or a WiFi network recently? I can't remember the last time I was
> assigned something that looked like a "real" routable IP address, but
> as a consumer of paid-for Internet service (that works) is there any
> reason (apart from religion) that I should care??

That's currently a consequence of the shortage of IP addresses. 
With IPv4 not every hotel or restaurant can have a Class-C address
range. Unfortunately, this shortage doesn't make people ask for
IPv6, but makes them getting used to have such NATs, and even 
more, it appears to be an advantage, because it gives kind of 
protection to unprotected windows machines. Internet is becoming 
decadent.

However, such a service might be sufficient as long as you just
poll your e-mail or visit the web from your hotel room. Would you 
be happy with it at home? What if you need an open port? 
What if you want to receive multicast packages? What if you want
to contact someone else who also has a NAT provider? What if
you want to receive instant messages, e-mail notifications,
peer-to-peer services?

With such providers Internet is not anymore what it used and was 
supposed to be. Internet means (at least in my opinion) that in 
principle every node can comunicate with every other node.

Clients behind NAT can't communicate with other such clients. 
Internet is split into clients and servers, where clients can 
communicate with servers only. No peer to peer anymore. 

Do we consider this as "internet"? 

Hadmut


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


From ietf-bounces@ietf.org  Sun Jun 20 14:00:07 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18828
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 14:00:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bc6bv-000683-OU
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 14:00:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc6aw-0005sp-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 13:59:07 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bc6a7-0005Rz-00; Sun, 20 Jun 2004 13:58:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bc6WW-0008V8-4L; Sun, 20 Jun 2004 13:54:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bc6TJ-00082Y-Sd
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 13:51:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18438
	for <ietf@ietf.org>; Sun, 20 Jun 2004 13:51:12 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bc6TI-00044G-RL
	for ietf@ietf.org; Sun, 20 Jun 2004 13:51:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc6SP-0003pG-00
	for ietf@ietf.org; Sun, 20 Jun 2004 13:50:18 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1Bc6Rg-0003Xt-00
	for ietf@ietf.org; Sun, 20 Jun 2004 13:49:32 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i5KHn1EP082279
	for ietf@ietf.org env-from <vjs>;
	Sun, 20 Jun 2004 11:49:01 -0600 (MDT)
Date: Sun, 20 Jun 2004 11:49:01 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200406201749.i5KHn1EP082279@calcite.rhyolite.com>
To: ietf@ietf.org
References: <Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> From: Ole Jacobsen 

> assigned something that looked like a "real" routable IP address, but
> as a consumer of paid-for Internet service (that works) is there any
> reason (apart from religion) that I should care??

If you have no reason to care, then you shouldn't, except that Full
Internet connectivity is significantly more expensive to provide.  It's
not the bits that are more expensive, but the people who deal with the
naughty bits that come with Full Internet Connectivity.

If you have a technical reason to care, perhaps because you need to
run an application not understood by the NAT systems of your hotel,
then you ought to be able to distinguish what you need from what you
are getting while talking to people who have never heard of the IETF.
Perhaps you would like to run applications that talk to systems back
at the factory and that use protocols that don't always play with NAT.
Maybe you are a system admninistrator who needs to check your DCC servers
(anti-spam system), despite your hotel's filters against UDP port 6277.
Perhaps you need to check your DNS servers despite your hotel's filters
and redirection of port 53 or all UDP.  Maybe you just need SSH and
didn't remember to set an sshd listening to port 443 before you left.
Maybe you need to talk to port 25 on your SMTP server to see if it is
sick.  Talk about ALGs, UDP, TCP, and even NAT is cybercrud noise to
a hotel desk clerk.  However, you might someday be able to say "please
upgrade the Internet service for room 1234 from Web Connectivity to
Full Internet Connectivity."

You don't expect airline ticket agents to understand or care what
you're talking about if you go on about stall speeds, rates of sink
or climb, and so forth, but asking for a ticket on a "communter airline"
instead of a "wide body" can be useful.

There is absolutely no chance of less filtering in hotels, 802.11 hot
spots, etc.  There will be terms that distinguish those kind of
Internet service from what many of us consider the real thing.  The
issue is whether we must wait for the market to provide equivalents
to "ham radio," "CB radio," "satellite radio," "AM," "FM," "TV," and
"cell phone."  Arguing against the idea of draft is like saying
"the term 'electormagnetic radiation' is good enough."


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Sun Jun 20 14:16:14 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19544
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 14:16:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bc6rW-00020w-9Y
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 14:16:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc6qa-0001mg-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 14:15:17 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bc6q2-0001Xr-00; Sun, 20 Jun 2004 14:14:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bc6nO-0002Jt-4g; Sun, 20 Jun 2004 14:11:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bc6kX-0001nc-UM
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 14:09:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19227
	for <ietf@ietf.org>; Sun, 20 Jun 2004 14:09:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bc6kW-0000Nu-UI
	for ietf@ietf.org; Sun, 20 Jun 2004 14:09:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc6ja-0000BQ-00
	for ietf@ietf.org; Sun, 20 Jun 2004 14:08:03 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1Bc6jA-0007m1-00
	for ietf@ietf.org; Sun, 20 Jun 2004 14:07:37 -0400
Received: from scan.jck.com ([209.187.148.215])
	by bs.jck.com with esmtp (Exim 4.10)
	id 1Bc6jA-000BJt-00; Sun, 20 Jun 2004 13:07:36 -0500
Date: Sun, 20 Jun 2004 14:07:36 -0400
From: John C Klensin <john@jck.com>
To: Hadmut Danisch <hadmut@danisch.de>, ietf@ietf.org
Message-ID: <CABA0AE3863D230C54E9D7C0@scan.jck.com>
In-Reply-To: <20040620104519.GA31597@danisch.de>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e444044
	5758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit



--On Sunday, 20 June, 2004 12:45 +0200 Hadmut Danisch
<hadmut@danisch.de> wrote:

> On Sat, Jun 19, 2004 at 11:40:03PM -0400, John C Klensin wrote:
> 
>> First, Hadmut, and others with his concerns in other
>> countries, probably need to approach the local regulatory
>> authorities who are concerned about consumer fraud and say
>> "the range of things that people are selling under the name
>> 'Internet service' includes too broad a range.
> 
> Correct in principle, but no chance to do it in reality.
> 
> If I contact the regulatory authorities, they will ask
> me "What's wrong with those ISP's?"
> 
> I answer "They do... and the don't..."
> 
> They'd say: Uhm, we're familiar with the Internet in 
> common, but not with all those details. Most people seem 
> to be happy with that, and if not, why don't you change to
> a provider of your taste? We don't see why there is a need
> to change the status quo of ISPs. 
> 
> I'd reply: Because that's not correct. This is not "Internet". 
> This is some approx. This causes technical problems. This is 
> fraud.
> 
> They'd say: Who are you to tell what's correct and what's 
> "Internet"? Nobody has ever defined that term. If there
> is no definition, then there is no "correct" or "not correct".
> 
> 
> 
> But if we had a precise definition and a taxonomy of the 
> different classes of ISPs, I could say: Look, the 
> IETF has given a definition. They're the guys who
> control the internet and keep it running well. They
> are exactly the ones to tell what's correct and 
> what's not. And now, some of those german providers
> are violating law. Because they are actually advertising
> to provide internet, what they in fact don't do. 
> False advertising is unlawful. 

While I don't precisely agree with parts of your description in
that paragraph (e.g., the IETF really doesn't "control the
Internet") that is precisely why draft-klensin-ip-service-terms
was written.  The questions, I think, are:

	* Is it right, or at least "good enough" given that goal?
	
	* What does the IESG want to do to process it, and when?
	
	* Can we move forward with something like that, with all
	of its inperfections, rather than getting bogged down in
	debates about changing things we can't possibly change,
	religion about various practices that exist and that
	people profit by selling, and alternate realities in
	which the IETF can actually dictate what people should
	do to be "legal".

"Can we "make" or "force" anyone to use an particular terms?" is
explicitly not on that list.  It wouldn't be a good idea, and
the answer is "no" anyway.

I don't know the answer to any of those questions. The draft was
posted just as an attempt to begin moving toward answers on all
three, rather than just having periodic discussions of how much
nicer the world would be if it were different.

And, without having any idea about the specific situation in
Germany, I would hope that, in many countries, were such a list
of terms and definitions standardized, it would be possible to
go to the regulators and say "Ok, here is a definition from a
recognized standards group with some plausible credentials for
understanding the Internet.  It defines some service
distinctions and why knowledge about those distinctions is
likely to be useful to an educated consumer trying to make
choices*.  I think that it would be useful if you either
required providers to supply information about their services in
those terms, or at least to establish the principle that using
the terms in misleading ways will be considered fraudulent".
We actually might make some progress that way.

	* The area of "why someone should care about these
	terms" is not, IMO, sufficiently handled in the
	document.   Text would be welcome as long as it
	maintains the tone of the document, i.e., that it avoid
	denouncing anyone or anything other than lying about
	what is being offered.

As editor (at least temporarily) of the only draft in this area
that has been posted and that I consider realistic given
real-world realities, I want to again try to reinforce the
observation made by Ole and others.  There are services (or, if
you prefer, disservices) out there that real people are paying
real money for and using happily.  To tell the providers of
those services "you must be clear about what you are providing"
is reasonable and not intrinsically offensive: they have enough
of a market that they will probably presume they can sell them
even if they are described clearly.  To tell them "you can't
provide that service because they imply that no one will be able
to operate a full-capability, permanent-address server out of a
one-night-stay in a hotel room" is nonsense and will be treated
that way -- they will respond that no one wants to buy such a
thing and will be, to a first-order approximation, correct.

>From personal experience, if I check into a hotel and hook up to
the local Ethernet, or use a public hotspot, I'll happily use
services with characteristics that would be unthinkable for my
office connection and servers.  At the same time, if I discover
that those hotel or hotspot services won't permit me to run
tunnels back to my home servers, I'm going to be _really_
unhappy.  It is the disclosure that is important.   And,
personally, I'd consider it huge forward progress if I can call
up a hotel I'm contemplating staying in and say "do you provide
Internet service at level xyz" and get a straight, meaningful,
and reliable answer.  That requires only some standard
definitions and a certain amount of good faith.  Will some
hotels (and some [dis]service providers) lie?  Probably.  But
that is a problem the community will have to deal with in some
other way: I've checked into hotels that claim to be four-star
facilities and that don't come anywhere close, but word gets
around, regulators get irritated, and so on.  I think doing that
well --establishing sufficient criteria that one can say "you
are lying" without having the hotel or provider saying "there
are no definitions, so nothing we say is a lie"-- would be good
progress.

Not enough to create a utopia in which there are no NATs, no
filters, static addresses for the duration of a stay that I
could obtain along with my confirmation number,  and no attempts
to provide/claim "broadband" service in which a 500 room hotel
feeds into a single fractional T1, but a useful start.

    john



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


From ietf-bounces@ietf.org  Sun Jun 20 14:23:06 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19918
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 14:23:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bc6yA-0003ml-Is
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 14:23:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc6x6-0003Th-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 14:22:01 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bc6w9-000327-00; Sun, 20 Jun 2004 14:21:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bc6sC-0003Gz-Fa; Sun, 20 Jun 2004 14:16:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bc6rS-00038R-7u
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 14:16:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19531
	for <ietf@ietf.org>; Sun, 20 Jun 2004 14:16:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bc6rR-00020K-7i
	for ietf@ietf.org; Sun, 20 Jun 2004 14:16:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc6qW-0001mA-00
	for ietf@ietf.org; Sun, 20 Jun 2004 14:15:13 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1Bc6ph-0001Xw-00
	for ietf@ietf.org; Sun, 20 Jun 2004 14:14:21 -0400
Received: from scan.jck.com ([209.187.148.215])
	by bs.jck.com with esmtp (Exim 4.10)
	id 1Bc6ph-000BXu-00; Sun, 20 Jun 2004 13:14:21 -0500
Date: Sun, 20 Jun 2004 14:14:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: Hadmut Danisch <hadmut@danisch.de>, ietf@ietf.org
Message-ID: <4522E1D79C416C84BAA185A7@scan.jck.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On Sunday, 20 June, 2004 12:45 +0200 Hadmut Danisch
<hadmut@danisch.de> wrote:

> On Sat, Jun 19, 2004 at 11:40:03PM -0400, John C Klensin wrote:
> 
>> First, Hadmut, and others with his concerns in other
>> countries, probably need to approach the local regulatory
>> authorities who are concerned about consumer fraud and say
>> "the range of things that people are selling under the name
>> 'Internet service' includes too broad a range.
> 
> Correct in principle, but no chance to do it in reality.
> 
> If I contact the regulatory authorities, they will ask
> me "What's wrong with those ISP's?"
> 
> I answer "They do... and the don't..."
> 
> They'd say: Uhm, we're familiar with the Internet in 
> common, but not with all those details. Most people seem 
> to be happy with that, and if not, why don't you change to
> a provider of your taste? We don't see why there is a need
> to change the status quo of ISPs. 
> 
> I'd reply: Because that's not correct. This is not "Internet". 
> This is some approx. This causes technical problems. This is 
> fraud.
> 
> They'd say: Who are you to tell what's correct and what's 
> "Internet"? Nobody has ever defined that term. If there
> is no definition, then there is no "correct" or "not correct".
> 
> 
> 
> But if we had a precise definition and a taxonomy of the 
> different classes of ISPs, I could say: Look, the 
> IETF has given a definition. They're the guys who
> control the internet and keep it running well. They
> are exactly the ones to tell what's correct and 
> what's not. And now, some of those german providers
> are violating law. Because they are actually advertising
> to provide internet, what they in fact don't do. 
> False advertising is unlawful. 

While I don't precisely agree with parts of your description in
that paragraph (e.g., the IETF really doesn't "control the
Internet") that is precisely why draft-klensin-ip-service-terms
was written.  The questions, I think, are:

	* Is it right, or at least "good enough" given that goal?
	
	* What does the IESG want to do to process it, and when?
	
	* Can we move forward with something like that, with all
	of its inperfections, rather than getting bogged down in
	debates about changing things we can't possibly change,
	religion about various practices that exist and that
	people profit by selling, and alternate realities in
	which the IETF can actually dictate what people should
	do to be "legal".

"Can we "make" or "force" anyone to use an particular terms?" is
explicitly not on that list.  It wouldn't be a good idea, and
the answer is "no" anyway.

I don't know the answer to any of those questions. The draft was
posted just as an attempt to begin moving toward answers on all
three, rather than just having periodic discussions of how much
nicer the world would be if it were different.

And, without having any idea about the specific situation in
Germany, I would hope that, in many countries, were such a list
of terms and definitions standardized, it would be possible to
go to the regulators and say "Ok, here is a definition from a
recognized standards group with some plausible credentials for
understanding the Internet.  It defines some service
distinctions and why knowledge about those distinctions is
likely to be useful to an educated consumer trying to make
choices*.  I think that it would be useful if you either
required providers to supply information about their services in
those terms, or at least to establish the principle that using
the terms in misleading ways will be considered fraudulent".
We actually might make some progress that way.

	* The area of "why someone should care about these
	terms" is not, IMO, sufficiently handled in the
	document.   Text would be welcome as long as it
	maintains the tone of the document, i.e., that it avoid
	denouncing anyone or anything other than lying about
	what is being offered.

As editor (at least temporarily) of the only draft in this area
that has been posted and that I consider realistic given
real-world realities, I want to again try to reinforce the
observation made by Ole and others.  There are services (or, if
you prefer, disservices) out there that real people are paying
real money for and using happily.  To tell the providers of
those services "you must be clear about what you are providing"
is reasonable and not intrinsically offensive: they have enough
of a market that they will probably presume they can sell them
even if they are described clearly.  To tell them "you can't
provide that service because they imply that no one will be able
to operate a full-capability, permanent-address server out of a
one-night-stay in a hotel room" is nonsense and will be treated
that way -- they will respond that no one wants to buy such a
thing and will be, to a first-order approximation, correct.

>From personal experience, if I check into a hotel and hook up to
the local Ethernet, or use a public hotspot, I'll happily use
services with characteristics that would be unthinkable for my
office connection and servers.  At the same time, if I discover
that those hotel or hotspot services won't permit me to run
tunnels back to my home servers, I'm going to be _really_
unhappy.  It is the disclosure that is important.   And,
personally, I'd consider it huge forward progress if I can call
up a hotel I'm contemplating staying in and say "do you provide
Internet service at level xyz" and get a straight, meaningful,
and reliable answer.  That requires only some standard
definitions and a certain amount of good faith.  Will some
hotels (and some [dis]service providers) lie?  Probably.  But
that is a problem the community will have to deal with in some
other way: I've checked into hotels that claim to be four-star
facilities and that don't come anywhere close, but word gets
around, regulators get irritated, and so on.  I think doing that
well --establishing sufficient criteria that one can say "you
are lying" without having the hotel or provider saying "there
are no definitions, so nothing we say is a lie"-- would be good
progress.

Not enough to create a utopia in which there are no NATs, no
filters, static addresses for the duration of a stay that I
could obtain along with my confirmation number,  and no attempts
to provide/claim "broadband" service in which a 500 room hotel
feeds into a single fractional T1, but a useful start.

    john



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


From ietf-bounces@ietf.org  Sun Jun 20 14:49:17 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21160
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 14:49:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bc7NV-0001rU-Lk
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 14:49:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc7MV-0001bJ-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 14:48:16 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bc7Ll-0001Kl-00; Sun, 20 Jun 2004 14:47:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bc7Dy-0006WA-1D; Sun, 20 Jun 2004 14:39:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bc7Be-000651-Kv
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 14:37:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20667
	for <ietf@ietf.org>; Sun, 20 Jun 2004 14:37:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bc7Bd-0006tC-Jt
	for ietf@ietf.org; Sun, 20 Jun 2004 14:37:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc7Ai-0006gw-00
	for ietf@ietf.org; Sun, 20 Jun 2004 14:36:05 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1Bc7AI-0006UH-00
	for ietf@ietf.org; Sun, 20 Jun 2004 14:35:38 -0400
Received: from scan.jck.com ([209.187.148.215])
	by bs.jck.com with esmtp (Exim 4.10)
	id 1Bc7AG-000Btz-00; Sun, 20 Jun 2004 13:35:36 -0500
Date: Sun, 20 Jun 2004 14:35:36 -0400
From: John C Klensin <john-ietf@jck.com>
To: Hadmut Danisch <hadmut@danisch.de>, Ole Jacobsen <ole@cisco.com>
Message-ID: <C2EB85E92BA2D05BACAB231F@scan.jck.com>
In-Reply-To: <20040620173714.GA16092@danisch.de>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e444044
	5758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>
	<Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>
	<20040620173714.GA16092@danisch.de>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On Sunday, 20 June, 2004 19:37 +0200 Hadmut Danisch
<hadmut@danisch.de> wrote:

> On Sun, Jun 20, 2004 at 09:52:51AM -0700, Ole Jacobsen wrote:
>> Much as I understand the moral outrage that NATs cause in
>> some people's mind, NATs are still a reality AND they
>> (usually anyway) provide connectivity to the Internet. Have
>> you tried using a hotelroom Ethernet port or a WiFi network
>> recently? I can't remember the last time I was assigned
>> something that looked like a "real" routable IP address, but
>> as a consumer of paid-for Internet service (that works) is
>> there any reason (apart from religion) that I should care??
> 
> That's currently a consequence of the shortage of IP
> addresses.

Actually, there is not a lot of evidence for this.  I suggest it
is partially a consequence of something else.  Let's assume I'm
a provider of "internet service" to a hotel chain or a random
collection of hotels.   It is in my interest to keep my actual
costs as low as possible, so that my hotel can compete with the
one down the block (to offer the same limited/lousy service, but
see below).  I need to assume that the folks who work in the
hotel on a day-to-day basis will know about as much about the
Internet as they do about fixing television sets.  Putting in an
expert drives my costs _way_ up.  Even sending out an expert to
provision the hotel has a serious impact on my costs. 

So, let's consider what I want to do.  I want to have an
absolutely standard kit that I can put on a truck with a field
service type whose level of training is "unpack boxes, plug in
router, plug in cables, plug in WAN feed, turn everything on,
perform a few very standard tests, return to truck".  I'd prefer
that even keying in an address for the hotel's WAN-side
connection and downstream router not be on that list.   The
state of the art today with IPv4, and, as I understand it,
pretty much with IPv6, is that I'm better off with a NAT and
private address space inside the hotel.  If the question of why
there aren't widely-supported DHCP or equivalent facilities by
which that entire hotel router (and its DHCP server and upstream
ports) can be trivially configured remotely, ask the DHC WG or
the Internet ADs, not me.  If you want to know why mail clients
can't be autoconfigured off DHCP with the hotel's local outbound
mail server, go take it up with the mail client vendors.  

But, until those sorts of problems are solved, please go read
Vernon's comments again: providers are providing these low end
services between that is what people want to buy and the price
they want to buy it at.  Higher levels of service would cost
more, maybe a lot more, mostly due to provisioning and support
costs and not, e.g., hardware costs or restrictions on IP
address availability.  And, while I have serious doubts that
there is a large market there, if we can make service term
descriptions a bit more clear, then I can imagine a hotel saying
"ok, we have two kinds of Internet service available,
'client-only' at $10/night and 'full' at $30/night -- pick what
you want and hand us your credit card".  Whether I'd be willing
to pay for the higher-end service or not, I'd far prefer being
offered that choice than "please give us your money and we will
deliver whatever we feel like and you can learn to like it".

> With such providers Internet is not anymore what it used and
> was  supposed to be. Internet means (at least in my opinion)
> that in  principle every node can comunicate with every other
> node.
> 
> Clients behind NAT can't communicate with other such clients. 
> Internet is split into clients and servers, where clients can 
> communicate with servers only. No peer to peer anymore. 
> 
> Do we consider this as "internet"? 

I don't.  My religion about this may not be very different from
yours, or even from Ohta-san's.  But the market has clearly
decided that people will buy such whatever-they-are-called
services and no amount of saying "naughty" or "inadequate" is
going to make them go away.   And we are more likely to get what
we do want --when we are willing to pay for it-- if we help
precisely those providers understand and sell both whatever they
are selling now and what you would consider adequate "Internet"
service.  Otherwise, as with most hotels and consumer
cable-modem and DSL providers today, the only thing available
will be the cheapest possible service (to provide) they can get
away with offering at whatever price they can get away with
charging for it.

      john


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


From ietf-bounces@ietf.org  Sun Jun 20 16:41:07 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28363
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 16:41:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bc97k-0003K5-GD
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 16:41:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc96n-00036k-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 16:40:10 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bc95v-0002ht-00; Sun, 20 Jun 2004 16:39:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bc939-0007sO-8c; Sun, 20 Jun 2004 16:36:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bc912-0007RC-3P
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 16:34:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28038
	for <ietf@ietf.org>; Sun, 20 Jun 2004 16:34:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bc910-0001pk-NX
	for ietf@ietf.org; Sun, 20 Jun 2004 16:34:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc904-0001c5-00
	for ietf@ietf.org; Sun, 20 Jun 2004 16:33:13 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12) id 1Bc8zA-0001NE-00
	for ietf@ietf.org; Sun, 20 Jun 2004 16:32:16 -0400
Received: from [127.0.0.1] (sequoia.muada.com [83.149.65.1])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i5KKVK0A082575;
	Sun, 20 Jun 2004 22:31:20 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20040620173714.GA16092@danisch.de>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>
	<Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>
	<20040620173714.GA16092@danisch.de>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DF2A161F-C2F8-11D8-96AB-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Sun, 20 Jun 2004 22:31:55 +0200
To: Hadmut Danisch <hadmut@danisch.de>
X-Mailer: Apple Mail (2.618)
Content-Transfer-Encoding: 7bit
Cc: Ole Jacobsen <ole@cisco.com>, ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

On 20-jun-04, at 19:37, Hadmut Danisch wrote:

>> Have you tried using a hotelroom Ethernet
>> port or a WiFi network recently? I can't remember the last time I was
>> assigned something that looked like a "real" routable IP address, but
>> as a consumer of paid-for Internet service (that works) is there any
>> reason (apart from religion) that I should care??

Well, if you don't care that a soda is $6 and local calls from your 
room are more expensive than international ones from your office, why 
start here? But it's substandard service nonetheless.

> That's currently a consequence of the shortage of IP addresses.

There is no shortage of IP addresses. There are still more than a 
billion that have never been used.

However, there is a big policy/distribution problem, or in other words:

> With IPv4 not every hotel or restaurant can have a Class-C address 
> range.


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


From ietf-bounces@ietf.org  Sun Jun 20 17:34:12 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00621
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 17:34:12 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bc9x7-0006o3-9x
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 17:34:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc9wC-0006al-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 17:33:17 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bc9vY-0006Lb-00; Sun, 20 Jun 2004 17:32:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bc9t1-00062F-4f; Sun, 20 Jun 2004 17:29:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bc9pJ-0005Iq-2O
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 17:26:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00320
	for <ietf@ietf.org>; Sun, 20 Jun 2004 17:26:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bc9pH-00057I-Nt
	for ietf@ietf.org; Sun, 20 Jun 2004 17:26:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bc9oK-0004vJ-00
	for ietf@ietf.org; Sun, 20 Jun 2004 17:25:09 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12)
	id 1Bc9nj-0004ca-00
	for ietf@ietf.org; Sun, 20 Jun 2004 17:24:31 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 20 Jun 2004 14:26:49 +0000
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i5KLNp72018914;
	Sun, 20 Jun 2004 14:23:51 -0700 (PDT)
Received: from localhost (ole@localhost) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA09662;
	Sun, 20 Jun 2004 14:23:51 -0700 (PDT)
Date: Sun, 20 Jun 2004 14:23:51 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <DF2A161F-C2F8-11D8-96AB-000A95CD987A@muada.com>
Message-ID: <Pine.HPX.4.58.0406201412190.27712@wells.cisco.com>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>
	<Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>
	<20040620173714.GA16092@danisch.de>
	<DF2A161F-C2F8-11D8-96AB-000A95CD987A@muada.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org, Hadmut Danisch <hadmut@danisch.de>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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


On Sun, 20 Jun 2004, Iljitsch van Beijnum wrote:

"But it's substandard service nonetheless."

Huh?

We can certainly have an argument about what is a reasonable price, but if
I can do *exactly* the same things (read/send e-mail, browse the web,
transfer files, make connections to remote hosts via SSH, listen to BBC
Radio 4, etc.) as I can from inside the corporate network, then what
exactly makes this NAT service "substandard"??

Sure, I probably won't be able to make my laptop be a web server, nor will
you be able to log into it from where you are, but who cares? That's NOT
what the typical business traveller wants and the service provided is a
lot more useful (and typically much cheaper) that the dialup alternative.

I am not advocating the use of NATs, I am just observing that NATs are a
fact of life and I have a hard time accepting that such a service cannot
be defined as "Internet service".

My home network is provided by a NAT too, but so far I have not found it
to be a huge problem. There are other services that I would like to see,
but they are prevented by policy and not by the NAT architecture per se.

I don't think the IETF should be in the business of defining what
constitues Internet service based on religion rather than reality.

Ole



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


From ietf-bounces@ietf.org  Sun Jun 20 18:22:25 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04011
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 18:22:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcAhm-0001bG-9V
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 18:22:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcAgq-0001Ls-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 18:21:29 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcAft-0000ty-00; Sun, 20 Jun 2004 18:20:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcAaP-00014a-3q; Sun, 20 Jun 2004 18:14:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcAYs-0008T6-AC
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 18:13:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03170
	for <ietf@ietf.org>; Sun, 20 Jun 2004 18:13:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcAYq-0007Ro-Om
	for ietf@ietf.org; Sun, 20 Jun 2004 18:13:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcAXx-0007FI-00
	for ietf@ietf.org; Sun, 20 Jun 2004 18:12:18 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12) id 1BcAXQ-00072i-00
	for ietf@ietf.org; Sun, 20 Jun 2004 18:11:44 -0400
Received: (qmail 33484 invoked from network); 20 Jun 2004 22:10:04 -0000
Received: from yahoobb219001188031.bbtec.net (HELO necom830.hpcl.titech.ac.jp)
	(219.1.188.31)
	by necom830.hpcl.titech.ac.jp with SMTP; 20 Jun 2004 22:10:04 -0000
Message-ID: <40D60CCF.1020601@necom830.hpcl.titech.ac.jp>
Date: Mon, 21 Jun 2004 07:16:47 +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: Ole Jacobsen <ole@cisco.com>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>	<F950E0BB956E7C80978BEC84@scan.jck.com>	<20040620104519.GA31597@danisch.de>	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>	<Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>	<20040620173714.GA16092@danisch.de>	<DF2A161F-C2F8-11D8-96AB-000A95CD987A@muada.com>
	<Pine.HPX.4.58.0406201412190.27712@wells.cisco.com>
In-Reply-To: <Pine.HPX.4.58.0406201412190.27712@wells.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, ietf@ietf.org,
        Hadmut Danisch <hadmut@danisch.de>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Ole Jacobsen;

> We can certainly have an argument about what is a reasonable price, but if
> I can do *exactly* the same things (read/send e-mail, browse the web,
> transfer files, make connections to remote hosts via SSH, listen to BBC
> Radio 4, etc.) as I can from inside the corporate network, then what
> exactly makes this NAT service "substandard"??

For example, how can you use mobile IP there?

> Sure, I probably won't be able to make my laptop be a web server, nor will
> you be able to log into it from where you are, but who cares?

How can you receive IP telephony call on your laptop?

						Masataka Ohta



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


From ietf-bounces@ietf.org  Sun Jun 20 18:33:08 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04504
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 18:33:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcAs9-0003zC-Cf
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 18:33:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcArH-0003mD-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 18:32:16 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcAqH-0003O5-00; Sun, 20 Jun 2004 18:31:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcAnW-0004mc-N3; Sun, 20 Jun 2004 18:28:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcAkZ-0004Os-6Y
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 18:25:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04200
	for <ietf@ietf.org>; Sun, 20 Jun 2004 18:25:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcAkX-0002IC-Ot
	for ietf@ietf.org; Sun, 20 Jun 2004 18:25:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcAjV-00023L-00
	for ietf@ietf.org; Sun, 20 Jun 2004 18:24:14 -0400
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx with esmtp (Exim 4.12) id 1BcAic-0001pk-00
	for ietf@ietf.org; Sun, 20 Jun 2004 18:23:18 -0400
Received: from andromeda (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i5KMNEit007431; Mon, 21 Jun 2004 00:23:14 +0200
Received: (from hadmut@localhost)
	by andromeda.dresden.danisch.de (8.12.11/8.12.11/Debian-5) id
	i5KMKVVq027682; Mon, 21 Jun 2004 00:20:31 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Mon, 21 Jun 2004 00:20:31 +0200
To: Ole Jacobsen <ole@cisco.com>
Message-ID: <20040620222031.GA26931@danisch.de>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>
	<Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>
	<20040620173714.GA16092@danisch.de>
	<DF2A161F-C2F8-11D8-96AB-000A95CD987A@muada.com>
	<Pine.HPX.4.58.0406201412190.27712@wells.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.HPX.4.58.0406201412190.27712@wells.cisco.com>
User-Agent: Mutt/1.5.6i
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Sun, Jun 20, 2004 at 02:23:51PM -0700, Ole Jacobsen wrote:
> 
> We can certainly have an argument about what is a reasonable price, but if
> I can do *exactly* the same things (read/send e-mail, browse the web,
> transfer files, make connections to remote hosts via SSH, listen to BBC
> Radio 4, etc.) as I can from inside the corporate network, then what


- How would you do a Voice-over-IP phone call with someone 
  else if both of you are in such a NAT-hotel-room?

- How do you join a multicast session (actually this is not 
  a matter of NAT, but of different levels of Internet services).

- I and some friends use a UDP based protocol to exchange 
  status messages with a central server. The next version 
  will allow to send notifications if mail has arrived 
  to avoid polling continuously. How would you do that?

  (I'm sometimes using IP over GRPS with my cellphone, where
  I receive a RFC1918 address, which is NATed. When I am awaiting
  an important e-mail, I have to poll every few minutes. Polling
  over GPRS is expensive. The provider which seems to be the cheaper
  could turn out to be more expensive.)

- How would you do IP-address based authorization 
  (e.g. RMX/SPF/CallerID) if other people can have the 
  same IP address at the same time?

- IPSec through NAT (if not UDP-encapsulated)?

- What about UDP or TCP protocols which run into the 
  NAT timeout?

- What about forensics? How do you track back an attack from 
  behind a hotel's NAT router?


I don't say that all hotels have to support full internet. 
But I'd like to know what I pay for in advance and decide 
whether it is sufficient for my needs before purchasing. 

I've never seen hotel staff people who could explain what's
going on there. But if you give things a name, then they 
can simple tell you what they offer without the need to 
understand anything. They just need to learn 
"We offer XXX service for x$ and YYY for y$".

And with home internet providers you can compare whether
the one for US$n-2 is really cheaper than the one with US$n.



regards
Hadmut

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


From ietf-bounces@ietf.org  Sun Jun 20 18:44:16 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04987
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 18:44:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcB2w-0006Lp-1j
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 18:44:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcB1s-00066q-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 18:43:12 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcB0u-0005hZ-00; Sun, 20 Jun 2004 18:42:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcAxX-0006DJ-AG; Sun, 20 Jun 2004 18:38:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcAt8-0005ID-RS
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 18:34:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04584
	for <ietf@ietf.org>; Sun, 20 Jun 2004 18:34:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcAt7-0004BV-8a
	for ietf@ietf.org; Sun, 20 Jun 2004 18:34:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcAs9-0003zH-00
	for ietf@ietf.org; Sun, 20 Jun 2004 18:33:09 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12) id 1BcArJ-0003mJ-00
	for ietf@ietf.org; Sun, 20 Jun 2004 18:32:17 -0400
Received: (qmail 33591 invoked from network); 20 Jun 2004 22:30:40 -0000
Received: from yahoobb219001188031.bbtec.net (HELO necom830.hpcl.titech.ac.jp)
	(219.1.188.31)
	by necom830.hpcl.titech.ac.jp with SMTP; 20 Jun 2004 22:30:40 -0000
Message-ID: <40D611A1.8010705@necom830.hpcl.titech.ac.jp>
Date: Mon, 21 Jun 2004 07:37:21 +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: Nathaniel Borenstein <nsb@guppylake.com>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>
	<D9CD0DEC-C2C6-11D8-AC93-000A9571873E@guppylake.com>
In-Reply-To: <D9CD0DEC-C2C6-11D8-AC93-000A9571873E@guppylake.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Hadmut Danisch <hadmut@danisch.de>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Nathaniel Borenstein;

> In particular, it would be nice to have *some* term like "Full internet 
> Connectivity" that defines the high-end service that really can't be 
> credibly claimed by the lower-end services.

If IETF successfully convince service providers that "Full internet
Connectivity" is the name of the high-end service, all the service
providers will call their service "Full internet Connectivity"
against which IETF can do nothing.

Vernon Schryver;

> However, you might someday be able to say "please
> upgrade the Internet service for room 1234 from Web Connectivity to
> Full Internet Connectivity."

And the hotel operator will say "Sure, you can now access all the
Web pages including those containing adalt contents".

						Masataka Ohta



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


From ietf-bounces@ietf.org  Sun Jun 20 19:09:21 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06311
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 19:09:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcBRB-00046r-9I
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 19:09:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcBQC-0003tA-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 19:08:20 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcBPD-0003U6-00; Sun, 20 Jun 2004 19:07:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcBMJ-0001NW-51; Sun, 20 Jun 2004 19:04:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcBCa-0000Jb-2z
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 18:54:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05637
	for <ietf@ietf.org>; Sun, 20 Jun 2004 18:54:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcBCY-0000uY-IB
	for ietf@ietf.org; Sun, 20 Jun 2004 18:54:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcBBg-0000hw-00
	for ietf@ietf.org; Sun, 20 Jun 2004 18:53:21 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12)
	id 1BcBAs-0000GV-00
	for ietf@ietf.org; Sun, 20 Jun 2004 18:52:30 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 20 Jun 2004 15:54:46 +0000
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i5KMpllq008358;
	Sun, 20 Jun 2004 15:51:48 -0700 (PDT)
Received: from localhost (ole@localhost) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id PAA19443;
	Sun, 20 Jun 2004 15:51:47 -0700 (PDT)
Date: Sun, 20 Jun 2004 15:51:47 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Hadmut Danisch <hadmut@danisch.de>
In-Reply-To: <20040620222031.GA26931@danisch.de>
Message-ID: <Pine.HPX.4.58.0406201546040.12903@wells.cisco.com>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>
	<Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>
	<20040620173714.GA16092@danisch.de>
	<DF2A161F-C2F8-11D8-96AB-000A95CD987A@muada.com>
	<Pine.HPX.4.58.0406201412190.27712@wells.cisco.com>
	<20040620222031.GA26931@danisch.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

If by "IPSec" you mean what the marketing folks call VPN, then so far it
has worked just fine.

Muticast, VOIP and the rest of stuff you mention probably does NOT work,
but my point was that this is NOT what most business travellers want.

And, yes, I agree they should provide a matrix of what is available for
what cost.

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Academic Research and Technology Initiatives, Cisco Systems
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj



On Mon, 21 Jun 2004, Hadmut Danisch wrote:

> On Sun, Jun 20, 2004 at 02:23:51PM -0700, Ole Jacobsen wrote:
> >
> > We can certainly have an argument about what is a reasonable price, but if
> > I can do *exactly* the same things (read/send e-mail, browse the web,
> > transfer files, make connections to remote hosts via SSH, listen to BBC
> > Radio 4, etc.) as I can from inside the corporate network, then what
>
>
> - How would you do a Voice-over-IP phone call with someone
>   else if both of you are in such a NAT-hotel-room?
>
> - How do you join a multicast session (actually this is not
>   a matter of NAT, but of different levels of Internet services).
>
> - I and some friends use a UDP based protocol to exchange
>   status messages with a central server. The next version
>   will allow to send notifications if mail has arrived
>   to avoid polling continuously. How would you do that?
>
>   (I'm sometimes using IP over GRPS with my cellphone, where
>   I receive a RFC1918 address, which is NATed. When I am awaiting
>   an important e-mail, I have to poll every few minutes. Polling
>   over GPRS is expensive. The provider which seems to be the cheaper
>   could turn out to be more expensive.)
>
> - How would you do IP-address based authorization
>   (e.g. RMX/SPF/CallerID) if other people can have the
>   same IP address at the same time?
>
> - IPSec through NAT (if not UDP-encapsulated)?
>
> - What about UDP or TCP protocols which run into the
>   NAT timeout?
>
> - What about forensics? How do you track back an attack from
>   behind a hotel's NAT router?
>
>
> I don't say that all hotels have to support full internet.
> But I'd like to know what I pay for in advance and decide
> whether it is sufficient for my needs before purchasing.
>
> I've never seen hotel staff people who could explain what's
> going on there. But if you give things a name, then they
> can simple tell you what they offer without the need to
> understand anything. They just need to learn
> "We offer XXX service for x$ and YYY for y$".
>
> And with home internet providers you can compare whether
> the one for US$n-2 is really cheaper than the one with US$n.
>
>
>
> regards
> Hadmut
>

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


From ietf-bounces@ietf.org  Sun Jun 20 23:20:21 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18286
	for <ietf-archive@ietf.org>; Sun, 20 Jun 2004 23:20:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcFM6-0001qa-Dx
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 23:20:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcFLC-0001em-00
	for ietf-archive@ietf.org; Sun, 20 Jun 2004 23:19:28 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcFKV-0001HZ-00; Sun, 20 Jun 2004 23:18:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcFGJ-00070s-8o; Sun, 20 Jun 2004 23:14:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcFFR-0006ts-0D
	for ietf@megatron.ietf.org; Sun, 20 Jun 2004 23:13:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18010
	for <ietf@ietf.org>; Sun, 20 Jun 2004 23:13:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcFFP-0000TW-3d
	for ietf@ietf.org; Sun, 20 Jun 2004 23:13:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcFEZ-0000I6-00
	for ietf@ietf.org; Sun, 20 Jun 2004 23:12:37 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1BcFE8-000059-00
	for ietf@ietf.org; Sun, 20 Jun 2004 23:12:08 -0400
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 i5L3BWgK030250
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 20 Jun 2004 23:11:33 -0400
Date: Sun, 20 Jun 2004 23:11:32 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Stephen Sprunk <stephen@sprunk.org>
In-Reply-To: <043e01c455a5$0e0770f0$6401a8c0@stephen>
Message-ID: <Pine.LNX.4.44.0406191351560.18161-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: David Kessens <david.kessens@nokia.com>,
        Internet Engineering Task Force <ietf@ietf.org>
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Fri, 18 Jun 2004, Stephen Sprunk wrote:

> Thus spake "David Kessens" <david.kessens@nokia.com>
> > On Fri, Jun 18, 2004 at 07:28:40PM -0500, Stephen Sprunk wrote:
> > > While I disagree with Dean in general and also with most of his current
> > > argument, I think it is a reasonable request that IETF "officials" be
> given
> > > an @ietf.org email alias and that those aliases be published for use in
> > > situations such as this.
> >
> > I like this idea (for other reasons) but I am not sure whether this
> > really addresses this particular problem:
> 
> Dean's problem is that he sends mail from an open relay, which isc.org's
> servers block completely (with good reason, sorry Dean).  

Stephen, thanks, but you have some of your facts wrong.  Neither ISC nor
SORBS blocks us because of our relays, nor is the blocking limited to our
open relays.  And in fact, the relay used (cirrus.av8.net) is not an open
relay, but in fact is an SSL/SMTP AUTH relay*.  Rather, ISC/SORBS block
__ALL__ of our IP address space (that is, a full /16 and a full /21),
because they claim this IP address space is "hijacked/disused".  This
includes all of our customers.

In fact, like ORBS before it, SORBS also isn't a __spam__ blacklist. Its a
"personal"  blacklist of sites that Alan Brown, Matthew Sullivan, and Paul
Vixie and their associates just don't like. It is completely
innappropriate for the IETF or its staff to associate with or use such a
list for IETF business.

[* Yes there are still reasons to run open relays---Indeed, our SMTP AUTH
relay is the least used: a commercial failure, really, but I use Pine
which is one of the few clients that can support SMTP AUTH.  SMTP AUTH has
done nothing to block spam, anyone can sign up. Open/Closed, doesn't
matter. Unless you can't do SMTP AUTH, then it matters. Thousands of
software packages don't do SMTP AUTH, and millions of users who want to
outsource parts of their email system or services.  There is a large
market for open relay services and none of it is spam. ]

The address space in question has been in continuous use since 1989
(130.105/16) and since 1993 (198.3.136/21).  I am the authorized contact
for this space, and the entities or their successors to which the IP
address blocks were originally assigned are still in existance. If our use
of these blocks was without permission, they are able to complain.  These
public facts are easilly found by anyone interested in them.

Examination of the ARIN information demonstrates the false nature of
the claims by Vixie, Brown, and Sullivan:


OrgName:    AV8 Internet, Inc 
OrgID:      AV8IN
Address:    P.O. Box 7286
City:       Nashua
StateProv:  NH
PostalCode: 03060
Country:    US

NetRange:   198.3.136.0 - 198.3.143.255 
CIDR:       198.3.136.0/21 
NetName:    AV8IN-NET-1
NetHandle:  NET-198-3-136-0-1
Parent:     NET-198-3-0-0-1
NetType:    Reassigned
Comment:    
RegDate:    2003-07-30
Updated:    2004-02-23

OrgTechHandle: DA31-ARIN
OrgTechName:   Anderson, Dean A.
OrgTechPhone:  +1-617-344-9000
OrgTechEmail:  dean@av8.com

# ARIN WHOIS database, last updated 2004-06-19 19:10
# Enter ? for additional hints on searching ARIN's WHOIS databas


OrgName:    Open Software Foundation 
OrgID:      OSF
Address:    P.O. Box 7286
City:       Nashua
StateProv:  NH
PostalCode: 03060
Country:    US

NetRange:   130.105.0.0 - 130.105.255.255 
CIDR:       130.105.0.0/16 
NetName:    OSF
NetHandle:  NET-130-105-0-0-1
Parent:     NET-130-0-0-0-0
NetType:    Direct Allocation
NameServer: STARSHIP.AV8.COM
NameServer: CONCORDE.AV8.COM
Comment:    
RegDate:    1988-07-20
Updated:    1998-12-21

TechHandle: DA31-ARIN
TechName:   Anderson, Dean A.
TechPhone:  +1-617-344-9000
TechEmail:  dean@av8.com 



Mr Sullivan claims that if we do not reveal our relationships and
contracts with these entities, then we haven't "proved" our rights to use
the address space. Of course, that is nonsense.  Others have made
similarly absurd claims such as 'IP address space is a government grant
that can only be used for non-profit purposes' (Kai Schlichting made this
claim in a generally defamatory letter he sent to the OSF/The Open Group,
whose attorney forwarded it to me)

The false claims by ISC/SORBS is not a matter of blocking spam.  It
doesn't have anything whatsoever to do with blocking spam.  ISC/SORBS
falsely asserts that IP address space is "hijacked/disused".  This is a
bald lie, first promoted by Alan Brown, who you might recall once used his
ORBS blacklist to block ISPs that had nothing to do with spam, for reasons
that had nothing to do with spam: just because he didn't like those ISPs.
Brown then lost 3 separate lawsuits involving defamation and false
statements, and ultimately appears to have lost his business to pay the
consequent damages. When Brown's own subscribers complained, he said it
was a "personal" blacklist and had no particular standards.  Brown was
pretty thoroughly discredited but this does not appear to have deterred
Sullivan and Vixie from associating with him.  Brown and his associates
Paul Vixie and Matthew Sullivan have continued to promote and support
defamation of ISPs they don't like, just like ORBS did previously. None of
the 3 cases Brown lost had anything to do with spam.  Similarly, this has
nothing to do with spam.

ISC/SORBS (Brown, Vixie, and Sullivan) are not claiming that we are
spammers: They are falsely claiming that our address space is
"hijacked/disused".  Vixie and I have conflicts that predate spam, and
goes back at least to Namedroppers in the late 1980's and the issue of HS
class Root servers.  More recently, I've worked (with others of course) to
prevent several frivolous changes to the DNS protocol that Mr. Vixie
supported, and which would have benefited products and companies he has a
financial interest in.  Indeed, the current dispute arose out of
complaints about improper activity by Mr.  Austein as WG co-chair with
respect to one of those proposals. That complaint, originally and
appropriately made off-list, was rejected by Mr. Austein's ISC.ORG email
system, run by Mr. Vixie.

ISC's harrassment by computer is not the only issue. There are also the
matters of on-list disparagement by Mr.  Bush and Mr. Vixie, and of course
Mr. Alvestrand has recently made his own original false and misleading
statements implying there is somehow incorrect ownership information and
that somehow I have made some request of him to change that. I haven't
made any such request. If there is any trivially incorrect information, it
does not support the assertion that the space is "hijacked/disused".

We cannot ignore these acts by and through the IETF.  We have business
with the IETF, and have a stake in the engineering of the Internet.  We
cannot allow persons at the IETF (either employees, staff or participants)
to defame or disparage Av8 or myself to others or to Av8 Customers who
might participate in the IETF.  We certainly cannot allow the IETF process
to be inappropriately manipulated by ISC or Paul Vixie or others to their
financial advantage.


For your reference, I'll summarize the salient events regarding SORBS and 
ISC's harrassment by computer:

Brown, Sullivan, and Vixie originally claimed that the OSF no longer
existed, but withdrew that claim after I contacted Sullivan directly last
year. They refuse to withdraw the rest of their false claims, apparently
seeking to draw me into a lawsuit with Mr. Sullivan Unlike Mr. Brown
(previously) and Mr. Vixie (currently), Mr. Sullivan has no company or
assets to pay damages. But this is consistent with a plan of action posted
on Spam-l after MAPS lost in Exactis V. MAPS.

SORBS has been booted from other ISPs for violating AUP rules which
prohibit defamation and other bad conduct.  Despite their bad conduct,
Vixie then provided them with hosting services at ISC, and has refused to
accept abuse reports, which is both ironic and hypocritical.  100% of the
sites we've contacted have stopped using SORBS altogether when they
examine the false claims made by SORBS.  It seems that few or no reputable
people or companies want to associate with this organization after finding
out what it is up to.  Strangely, the ISC and the IETF are the rare
exceptions.


Some have attempted to describe this as simply a "false positive" that is
an unfortunate, but unpreventable event. This is a false claim.  There are
plenty of anti-spam methods out that do not harrass Av8 Internet, or make
false claims.  Many (if not most) people have given up altogether on
IP-based blocking.  Indeed, given that most spam/abuse comes from
virus-infected computers on DHCP connections that force them to change IPs
every few hours, it seems impossible that IP-based blocking could be
effective unless the blacklist had some advance knowledge of the IPs to be
used. And of course, advance knowledge is impossible unless the blacklist
is the abuser.  So, if you find an effective IP-based blacklist, well,
you've found something very interesting.

There are many anti-spam tools that do not engage in defamation and false
claims.  Judging by the relative absence of complaints by our users, it
seems that SORBS is a very little used list, and that like ORBS before it,
its purpose is nothing other than defamation and disparagement. Outside of
ISC's harrassment on the IETF lists, we have very little problem with
SORBS use, and 100% of the sites that we've run into using SORBS (outside
of ISC and the IETF) have quit using SORBS altogether after we've
contacted them.  As I pointed out previously, SORBS isn't an anti-spam
list at all, but a "personal" blacklist created by Sullivan, Brown, Vixie,
and their associates.

You may be wondering why SORBS is claiming our address space is
"hijacked/disused", instead of claiming it as open relay. I wondered that,
too. I don't know the answer, and ISC/SORBS/Sullivan/Vixie aren't saying.  
But I think its because they already lost the "is it legal to block open
relays?" argument. We have gone into legal dispute with a couple large
ISPs whose abuse admins threatened to block our relays, and who claimed
that open relays somehow send spam. The admins described __anonymous__
relays.  When we corrected that description, and explained the difference
between an open relay and an anonymous relay, their lawyer reversed the
admin and promised not to block our relays[**].  There is nothing abusive
or unlawful about open relays.

[** It is an interesting footnote that in one case, the admin who lost on
the open relay question posted messages to an ISP list saying that we had
hijacked space.  While he has a relationship to Vixie and Sullivan through
Nanog, his post was after SORBS began their listing. It is unclear how he
learned of the listing, since it wasn't discussed on Nanog or Spam-l ]


The ISC/SORBS issue has nothing whatsoever to do with open relays.


But even if it did have something to do open relays, there is still no
reason to block our relays: There is no spam coming from our relays, in
comparison to other ISP relays. They are policed far better than most
ISP's closed relays.  We respond far faster and far more responsibily than
say, Bill Manning did with complaints about ISC's hosting of an abuse site
(http://www.iadl.org/bm/bill-manning-story.html)  Manning _still_ claims
that "we can't prove any relationship between EP.NET and ISC.ORG", despite
their long and well-known history in operating PAIX.

Please also be aware that an open relay is not an __anonymous__ relay.  

I might agree that there is no reason or little reason to run anonymous
relays. Av8 does not run anonymous relays.  However, many anti-spam
radicals cannot make the distinction between anonymous relays and open
relays. I don't know whether this is due to lack of intelligence or if
they just intentionally mislead people (their attorneys and management)  
about the difference.  

However, making it about open relays makes no difference. Blocking our
open relays through particpation in an unlawful group boycott is still
unlawful for the IETF and its staff, (see
http://info.av8.net/spamstuff/vix-spam-abatement-ietf.html)  Defaming and
disparaging Av8 Internet by the IETF, its staff or its participants is
also unlawful.  But it isn't about open relays, its about falsely claiming
that IP Address space is "hijacked/disused"


Dean Anderson
Av8 Internet, Inc







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


From ietf-bounces@ietf.org  Mon Jun 21 03:47:03 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18272
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 03:47:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcJWA-0006Ug-Vh
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 03:47:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcJUs-00069e-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 03:45:43 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcJTl-0005i0-01; Mon, 21 Jun 2004 03:44:34 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BcJPb-0002Jc-5B; Mon, 21 Jun 2004 03:40:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcJIo-0002A8-L2; Mon, 21 Jun 2004 03:33:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcJBZ-000158-DL
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 03:25:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17114
	for <ietf@ietf.org>; Mon, 21 Jun 2004 03:25:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcJBX-0001UY-12
	for ietf@ietf.org; Mon, 21 Jun 2004 03:25:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcJ8Z-0001CW-00
	for ietf@ietf.org; Mon, 21 Jun 2004 03:22:40 -0400
Received: from mail.enyo.de ([212.9.189.167]) by ietf-mx with esmtp (Exim 4.12)
	id 1BcJ7g-0000zE-00
	for ietf@ietf.org; Mon, 21 Jun 2004 03:21:44 -0400
Received: (debugging) helo=deneb.enyo.de ip=212.9.189.171 name=deneb.enyo.de
Received: from deneb.enyo.de ([212.9.189.171])
	by mail.enyo.de with esmtp id 1BcJ7g-0003gh-PC;
	Mon, 21 Jun 2004 09:21:44 +0200
Received: from fw by deneb.enyo.de with local (Exim 4.34)
	id 1BcJ7g-0000h5-E2; Mon, 21 Jun 2004 09:21:44 +0200
To: Hadmut Danisch <hadmut@danisch.de>
References: <20040619094223.GA4764@danisch.de>
From: Florian Weimer <fw@deneb.enyo.de>
Date: Mon, 21 Jun 2004 09:21:44 +0200
In-Reply-To: <20040619094223.GA4764@danisch.de> (Hadmut Danisch's message of
	"Sat, 19 Jun 2004 11:42:23 +0200")
Message-ID: <871xk92x6f.fsf@deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

* Hadmut Danisch:

> at least here in Germany Internet providers tend to 
> do and not to do what they want.
>
> - Some cut off their clients every 24 hours (DSL)

This happens on the sub-IP layer and hasn't got to do much with ISPs.

> - Some block or slowdown particular tcp ports 
>   to get rid of peer-to-peer file sharing

You get what you pay for.

> - Some redirect the first web access to any site
>   to their own to force you to read their ads

Same here.

> - Very few support multicast. When I asked my 
>   own provider, they didn't even know what this is.
>   (They said 'no, because they don't support Linux'.)

You can't get reliable multicast service anywhere in the world.
People tend to switch it off if it threatens to impact unicast
traffic.  It's not possible to run production services over multicast
across the Internet at the moment, at least not without a fallback to
unicast.

> - IPv6? Huh? What's that? 

It's not a real problem to get native IPv6 over ADSL or SDSL.

> - At least one large provider blocks port 25 to certain IP 
>   addresses in order to force you to use the provider's 
>   mail relay

Which one is that?

The case you are writing about does *not* block 25/TCP on the TCP/IP
layer.

It's true that certain extremely cheap products don't offer that much
Internet or Service.  These products are marketed aggressively and are
usually sold at a loss.  Nobody forces you to buy them.

-- 
Current mail filters: many dial-up/DSL/cable modem hosts, and the
following domains: bigpond.com, di-ve.com, fuorissimo.com, hotmail.com,
jumpy.it, libero.it, netscape.net, postino.it, simplesnet.pt, spymac.com,
tiscali.co.uk, tiscali.cz, tiscali.it, voila.fr, yahoo.com.

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


From ietf-bounces@ietf.org  Mon Jun 21 04:17:44 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20467
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 04:17:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcJzs-000692-5M
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 04:17:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcJz1-0005v4-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 04:16:52 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcJyY-0005f1-00; Mon, 21 Jun 2004 04:16:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcJvc-0008SA-O7; Mon, 21 Jun 2004 04:13:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcJnc-0007LT-UH
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 04:05:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19682
	for <ietf@ietf.org>; Mon, 21 Jun 2004 04:05:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcJna-000356-NK
	for ietf@ietf.org; Mon, 21 Jun 2004 04:05:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcJmX-0002p2-00
	for ietf@ietf.org; Mon, 21 Jun 2004 04:03:58 -0400
Received: from mail.enyo.de ([212.9.189.167]) by ietf-mx with esmtp (Exim 4.12)
	id 1BcJlh-0002ZE-00
	for ietf@ietf.org; Mon, 21 Jun 2004 04:03:05 -0400
Received: (debugging) helo=deneb.enyo.de ip=212.9.189.171 name=deneb.enyo.de
Received: from deneb.enyo.de ([212.9.189.171])
	by mail.enyo.de with esmtp id 1BcJlh-0004G0-Ls;
	Mon, 21 Jun 2004 10:03:05 +0200
Received: from fw by deneb.enyo.de with local (Exim 4.34)
	id 1BcJlh-0000mR-6j; Mon, 21 Jun 2004 10:03:05 +0200
To: Hadmut Danisch <hadmut@danisch.de>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>
	<Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>
	<20040620173714.GA16092@danisch.de>
From: Florian Weimer <fw@deneb.enyo.de>
Date: Mon, 21 Jun 2004 10:03:05 +0200
In-Reply-To: <20040620173714.GA16092@danisch.de> (Hadmut Danisch's message
	of "Sun, 20 Jun 2004 19:37:14 +0200")
Message-ID: <87smcp1gp2.fsf@deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Ole Jacobsen <ole@cisco.com>, ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

* Hadmut Danisch:

> That's currently a consequence of the shortage of IP addresses. 

There's no shortage of IPv4 addresses.  Today, it's not a problem to
get IP addresses if you have determined that NAT is not an option.

-- 
Current mail filters: many dial-up/DSL/cable modem hosts, and the
following domains: bigpond.com, di-ve.com, fuorissimo.com, hotmail.com,
jumpy.it, libero.it, netscape.net, postino.it, simplesnet.pt, spymac.com,
tiscali.co.uk, tiscali.cz, tiscali.it, voila.fr, yahoo.com.

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


From ietf-bounces@ietf.org  Mon Jun 21 04:30:42 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21327
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 04:30:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcKCQ-0001ZY-66
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 04:30:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcKBX-0001L2-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 04:29:48 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcKAg-0000sg-00; Mon, 21 Jun 2004 04:28:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcK7i-0001uL-Nu; Mon, 21 Jun 2004 04:25:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcJxm-0000LK-6H
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 04:15:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20289
	for <ietf@ietf.org>; Mon, 21 Jun 2004 04:15:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcJxj-0005d3-TL
	for ietf@ietf.org; Mon, 21 Jun 2004 04:15:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcJwl-0005OI-00
	for ietf@ietf.org; Mon, 21 Jun 2004 04:14:31 -0400
Received: from 225.cust3.sa.dsl.ozemail.com.au ([210.84.226.225]
	helo=nosense.org) by ietf-mx with esmtp (Exim 4.12)
	id 1BcJvi-0004w3-00
	for ietf@ietf.org; Mon, 21 Jun 2004 04:13:27 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP id 560633F02A
	for <ietf@ietf.org>; Mon, 21 Jun 2004 17:42:46 +0930 (CST)
Date: Mon, 21 Jun 2004 17:42:46 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
Cc: ietf@ietf.org
Message-Id: <20040621174246.113a83a6.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <Pine.HPX.4.58.0406201546040.12903@wells.cisco.com>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>
	<Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>
	<20040620173714.GA16092@danisch.de>
	<DF2A161F-C2F8-11D8-96AB-000A95CD987A@muada.com>
	<Pine.HPX.4.58.0406201412190.27712@wells.cisco.com>
	<20040620222031.GA26931@danisch.de>
	<Pine.HPX.4.58.0406201546040.12903@wells.cisco.com>
Organization: The No Sense Organisation (http://www.nosense.org)
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i686-pc-linux-gnu)
X-Location: Adelaide, Australia
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

On Sun, 20 Jun 2004 15:51:47 -0700 (PDT)
Ole Jacobsen <ole@cisco.com> wrote:

> If by "IPSec" you mean what the marketing folks call VPN, then so far it
> has worked just fine.
> 
> Muticast, VOIP and the rest of stuff you mention probably does NOT work,
> but my point was that this is NOT what most business travellers want.
> 

A retorical question. How do business travellers know that they don't
want them, if they've never seen them demonstrated, because NAT limited the
availablility of them to the point where their availability couldn't be relied
upon.

Not only may the next "killer app" not be the next "killer app" because it
doesn't work with NAT, the next "killer app" may have already been invented a
year ago, but wasn't able to be deployed because of the prevalance of NAT. Not
only don't we know, we also don't know what we may be missing.

This is the problem with NAT - it appears to be a nice easy solution, until
you realise that the devil is in the details.

Keith Moore has put together a good list of the things NAT breaks at 

http://www.cs.utk.edu/~moore/what-nats-break.html

a related document, also by Keith, which also addresses some issues influenced
by NAT is "Dubious Assumptions about IPv6"

http://www.cs.utk.edu/~moore/opinions/ipv6/dubious-assumptions.html

Regards,
Mark.

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


From ietf-bounces@ietf.org  Mon Jun 21 05:16:47 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23830
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 05:16:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcKv1-0004eS-3Z
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 05:16:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcKu3-0004PF-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 05:15:48 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcKtH-00040X-00; Mon, 21 Jun 2004 05:14:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcKpH-0008K0-Je; Mon, 21 Jun 2004 05:10:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcKhJ-00078f-MN
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 05:02:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23021
	for <ietf@ietf.org>; Mon, 21 Jun 2004 05:02:35 -0400 (EDT)
From: hadmut@danisch.de
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcKhH-0001DY-Cw
	for ietf@ietf.org; Mon, 21 Jun 2004 05:02:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcKgO-00010P-00
	for ietf@ietf.org; Mon, 21 Jun 2004 05:01:40 -0400
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx with esmtp (Exim 4.12) id 1BcKfb-0000nj-00
	for ietf@ietf.org; Mon, 21 Jun 2004 05:00:51 -0400
Received: (from hadmut@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) id i5L90pdP021243;
	Mon, 21 Jun 2004 11:00:51 +0200
Date: Mon, 21 Jun 2004 11:00:51 +0200
To: Florian Weimer <fw@deneb.enyo.de>
Message-ID: <20040621090051.GA20379@danisch.de>
References: <20040619094223.GA4764@danisch.de> <871xk92x6f.fsf@deneb.enyo.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <871xk92x6f.fsf@deneb.enyo.de>
User-Agent: Mutt/1.5.6i
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,NO_REAL_NAME autolearn=no 
	version=2.60

On Mon, Jun 21, 2004 at 09:21:44AM +0200, Florian Weimer wrote:
...
> This happens on the sub-IP layer and hasn't got to do much with ISPs.
...
> You get what you pay for.
...
> Same here.
...
> You can't get reliable multicast service anywhere in the world.
...
> It's not a real problem to get native IPv6 over ADSL or SDSL.
...
> Which one is that?
> 
> The case you are writing about does *not* block 25/TCP on the TCP/IP
> layer.
> 
> It's true that certain extremely cheap products don't offer that much
> Internet or Service.  These products are marketed aggressively and are
> usually sold at a loss.  Nobody forces you to buy them.



You missed the point. This is not about complaining that I don't get
enough for the money. This is that I don't know in advance what
I do get for my money.

"Nobody forces you to buy them" is true only as long as I do 
know what exactly they offer and as it is my decision to buy
it or not. But if I buy "Internet" and don't see what I'm 
buying, then I don't have the choice.

I do not want to blame anyone for selling NAT access. 
I want him to give a clear statement about what he is 
selling.

regards
Hadmut

(And, btw, some of the statements are incorrect.
- Some providers intentionally cut their customers
  off after 24 hours in order to force them to have
  a new IP address.

- It is a real problem to get native IPv6 over DSL 
  in Germany. Some providers simply don't want to 
  provide IPv6, because they say "Internet" is IPv4.
)



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


From ietf-bounces@ietf.org  Mon Jun 21 05:18:34 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23943
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 05:18:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcKwk-0005AV-Hh
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 05:18:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcKvm-0004tQ-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 05:17:35 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcKui-0004QM-00; Mon, 21 Jun 2004 05:16:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcKpJ-0008KZ-W5; Mon, 21 Jun 2004 05:10:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcKjH-0007HW-3D
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 05:04:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23090
	for <ietf@ietf.org>; Mon, 21 Jun 2004 05:04:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcKjE-0001eD-Ri
	for ietf@ietf.org; Mon, 21 Jun 2004 05:04:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcKiG-0001RG-00
	for ietf@ietf.org; Mon, 21 Jun 2004 05:03:37 -0400
Received: from smtp.nildram.co.uk ([195.112.4.54])
	by ietf-mx with esmtp (Exim 4.12) id 1BcKhM-0001EB-00
	for ietf@ietf.org; Mon, 21 Jun 2004 05:02:40 -0400
Received: from pcgz600re (unknown [81.6.214.202])
	by smtp.nildram.co.uk (Postfix) with SMTP
	id 10EC025414C; Mon, 21 Jun 2004 10:02:38 +0100 (BST)
From: "Christian de Larrinaga" <cdel@firsthand.net>
To: "Ole Jacobsen" <ole@cisco.com>, "Hadmut Danisch" <hadmut@danisch.de>
Date: Mon, 21 Jun 2004 10:03:46 +0100
Message-ID: <OKEPLEIOJKFGFGCKMDKJKEKOCGAA.cdel@firsthand.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
In-Reply-To: <Pine.HPX.4.58.0406201546040.12903@wells.cisco.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: cdel@firsthand.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Again we run into the thorny old policy issue of viewing the user as merely
a captive consumer.

But what happens when it turns out that to consume you need to run an
application not "supported" by the intervening network?

This is clearly a break of the principle of end to end application
transparency that the IP layer provides. This does necessarily break the
semantic description of Internet Service Provider. But there is little to be
done arguing that point now.

The problem as a travelling user (or as a housebound German it seems) is you
don't know what you are going to be able to do until you try and as a hotel
or end node provider you may legally have an obligation to try to protect
your network from being a source of abuse by transients.

A traveller cannot change ISP easily so either will just have to accept some
things cannot be done or will find a way. As it happens one can preplan and
setup a proxy service or a tunnel broker etc that can get round many of
these issues.

Perhaps the IETF would be wiser to give a warning about the futility of
trying to break application transparency. "The Internet user may always find
a way to communicate on their own terms"



Christian

Christian de Larrinaga

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]On Behalf Of
Ole Jacobsen
Sent: 20 June 2004 23:52
To: Hadmut Danisch
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?


If by "IPSec" you mean what the marketing folks call VPN, then so far it
has worked just fine.

Muticast, VOIP and the rest of stuff you mention probably does NOT work,
but my point was that this is NOT what most business travellers want.

And, yes, I agree they should provide a matrix of what is available for
what cost.

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Academic Research and Technology Initiatives, Cisco Systems
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj



On Mon, 21 Jun 2004, Hadmut Danisch wrote:

> On Sun, Jun 20, 2004 at 02:23:51PM -0700, Ole Jacobsen wrote:
> >
> > We can certainly have an argument about what is a reasonable price, but
if
> > I can do *exactly* the same things (read/send e-mail, browse the web,
> > transfer files, make connections to remote hosts via SSH, listen to BBC
> > Radio 4, etc.) as I can from inside the corporate network, then what
>
>
> - How would you do a Voice-over-IP phone call with someone
>   else if both of you are in such a NAT-hotel-room?
>
> - How do you join a multicast session (actually this is not
>   a matter of NAT, but of different levels of Internet services).
>
> - I and some friends use a UDP based protocol to exchange
>   status messages with a central server. The next version
>   will allow to send notifications if mail has arrived
>   to avoid polling continuously. How would you do that?
>
>   (I'm sometimes using IP over GRPS with my cellphone, where
>   I receive a RFC1918 address, which is NATed. When I am awaiting
>   an important e-mail, I have to poll every few minutes. Polling
>   over GPRS is expensive. The provider which seems to be the cheaper
>   could turn out to be more expensive.)
>
> - How would you do IP-address based authorization
>   (e.g. RMX/SPF/CallerID) if other people can have the
>   same IP address at the same time?
>
> - IPSec through NAT (if not UDP-encapsulated)?
>
> - What about UDP or TCP protocols which run into the
>   NAT timeout?
>
> - What about forensics? How do you track back an attack from
>   behind a hotel's NAT router?
>
>
> I don't say that all hotels have to support full internet.
> But I'd like to know what I pay for in advance and decide
> whether it is sufficient for my needs before purchasing.
>
> I've never seen hotel staff people who could explain what's
> going on there. But if you give things a name, then they
> can simple tell you what they offer without the need to
> understand anything. They just need to learn
> "We offer XXX service for x$ and YYY for y$".
>
> And with home internet providers you can compare whether
> the one for US$n-2 is really cheaper than the one with US$n.
>
>
>
> regards
> Hadmut
>

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


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


From ietf-bounces@ietf.org  Mon Jun 21 05:26:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24575
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 05:26:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcL4j-0007DH-Ip
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 05:26:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcL3n-0006yi-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 05:25:51 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcL3K-0006jD-00; Mon, 21 Jun 2004 05:25:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcL0S-0001uF-SE; Mon, 21 Jun 2004 05:22:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcKs2-0000IR-HB
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 05:13:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23683
	for <ietf@ietf.org>; Mon, 21 Jun 2004 05:13:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcKs0-0003wE-8B
	for ietf@ietf.org; Mon, 21 Jun 2004 05:13:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcKr6-0003gc-00
	for ietf@ietf.org; Mon, 21 Jun 2004 05:12:45 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12) id 1BcKq6-0003OG-00
	for ietf@ietf.org; Mon, 21 Jun 2004 05:11:42 -0400
Received: from [127.0.0.1] (sequoia.muada.com [83.149.65.1])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i5L9B30A095736;
	Mon, 21 Jun 2004 11:11:04 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.HPX.4.58.0406201412190.27712@wells.cisco.com>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>
	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>
	<F950E0BB956E7C80978BEC84@scan.jck.com>
	<20040620104519.GA31597@danisch.de>
	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>
	<Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>
	<20040620173714.GA16092@danisch.de>
	<DF2A161F-C2F8-11D8-96AB-000A95CD987A@muada.com>
	<Pine.HPX.4.58.0406201412190.27712@wells.cisco.com>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <01577AFB-C363-11D8-96AB-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Mon, 21 Jun 2004 11:11:39 +0200
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.618)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

On 20-jun-04, at 23:23, Ole Jacobsen wrote:

> "But it's substandard service nonetheless."

> Huh?

> We can certainly have an argument about what is a reasonable price, 
> but if
> I can do *exactly* the same things (read/send e-mail, browse the web,
> transfer files, make connections to remote hosts via SSH, listen to BBC
> Radio 4, etc.) as I can from inside the corporate network, then what
> exactly makes this NAT service "substandard"??

I'm not sure what you can and cannot do on your corporate network, but 
for me NAT gets in the way of some forms of streaming video (RTSP 
protocol), audio/video conferencing (SIP) and IPsec.

It's a real shame that software companies are spending their money on 
getting around this rather than create real innovation.

> I am not advocating the use of NATs, I am just observing that NATs are 
> a
> fact of life and I have a hard time accepting that such a service 
> cannot
> be defined as "Internet service".

You can define it as "partially broken internet service".

> I don't think the IETF should be in the business of defining what
> constitues Internet service based on religion rather than reality.

And I don't think the IETF should do anything that even comes close to 
endorsing NAT.


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


From ietf-bounces@ietf.org  Mon Jun 21 07:19:41 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02286
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 07:19:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcMpy-0003T9-GN
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 07:19:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcMoz-0003DZ-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 07:18:42 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcMo0-0002n5-00; Mon, 21 Jun 2004 07:17:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcMlU-0002qU-08; Mon, 21 Jun 2004 07:15:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcMkJ-0002hy-90
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 07:13:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02043
	for <ietf@ietf.org>; Mon, 21 Jun 2004 07:13:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcMkI-00025t-Q1
	for ietf@ietf.org; Mon, 21 Jun 2004 07:13:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcMjJ-0001sW-00
	for ietf@ietf.org; Mon, 21 Jun 2004 07:12:50 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12) id 1BcMiv-0001eX-00
	for ietf@ietf.org; Mon, 21 Jun 2004 07:12:25 -0400
Received: (qmail 37732 invoked from network); 21 Jun 2004 11:10:55 -0000
Received: from yahoobb219001188014.bbtec.net (HELO necom830.hpcl.titech.ac.jp)
	(219.1.188.14)
	by necom830.hpcl.titech.ac.jp with SMTP; 21 Jun 2004 11:10:55 -0000
Message-ID: <40D6C3C7.4040205@necom830.hpcl.titech.ac.jp>
Date: Mon, 21 Jun 2004 20:17:27 +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: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
References: <20040619205153.415e2b50.ietf@130c04165a5b40404e4440445758487a.nosense.org>	<200406191444.i5JEi08Y021284@calcite.rhyolite.com>	<40D4C1CF.90003@necom830.hpcl.titech.ac.jp>	<F950E0BB956E7C80978BEC84@scan.jck.com>	<20040620104519.GA31597@danisch.de>	<40D5949E.6020407@necom830.hpcl.titech.ac.jp>	<Pine.HPX.4.58.0406200949070.5632@wells.cisco.com>	<20040620173714.GA16092@danisch.de>	<DF2A161F-C2F8-11D8-96AB-000A95CD987A@muada.com>	<Pine.HPX.4.58.0406201412190.27712@wells.cisco.com>	<20040620222031.GA26931@danisch.de>	<Pine.HPX.4.58.0406201546040.12903@wells.cisco.com>
	<20040621174246.113a83a6.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040621174246.113a83a6.ietf@130c04165a5b40404e4440445758487a.nosense.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Mark Smith wrote:

> Not only may the next "killer app" not be the next "killer app" because it
> doesn't work with NAT, the next "killer app" may have already been invented a
> year ago, but wasn't able to be deployed because of the prevalance of NAT. Not
> only don't we know, we also don't know what we may be missing.

The next "killer app" a lot more important than Web for most
business people is the "Internet telephony", which may or may
not use IETF standard protocol.

Even though there are people who can not type, most of them
can use telephony (maybe over TDD).

And the second next "killer app" a lot more important than
Web for most people including, but not limited to, business
ones is "Internet TV", which may or may not use IETF or
Microsoft standard protocol.

It has already happened to millions of people in Japan initiated
by a commercial company and there will be tens and hundreds of
millions of people using them.

> This is the problem with NAT - it appears to be a nice easy solution, until
> you realise that the devil is in the details.

Yup. If you insist on NAT, you lose a lot of business chances.

I can proudly say that I helped the commercial company above get
global IPv4 addresses enough for millions of subscribers, which
was essential for their aggressive service.

The reality of life is that there are successful ISPs and there
are poor network providers insisting on NAT.

							Masataka Ohta


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


From ietf-bounces@ietf.org  Mon Jun 21 12:12:29 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28474
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 12:12:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcRPL-00053W-Qm
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 12:12:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcQpl-0005rV-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 11:35:46 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcPYS-0005FV-00; Mon, 21 Jun 2004 10:13:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcPS0-0005Tn-7t; Mon, 21 Jun 2004 10:07:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcP4V-0007BE-CG
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 09:42:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13394
	for <ietf@ietf.org>; Mon, 21 Jun 2004 09:42:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcP4U-0001US-9g
	for ietf@ietf.org; Mon, 21 Jun 2004 09:42:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcOda-0004yx-00
	for ietf@ietf.org; Mon, 21 Jun 2004 09:15:02 -0400
Received: from 225.cust3.sa.dsl.ozemail.com.au ([210.84.226.225]
	helo=nosense.org) by ietf-mx with esmtp (Exim 4.12)
	id 1BcO5X-0000Ve-00
	for ietf@ietf.org; Mon, 21 Jun 2004 08:39:52 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 3614F3F02A; Mon, 21 Jun 2004 22:09:15 +0930 (CST)
Date: Mon, 21 Jun 2004 22:09:14 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: cdel@firsthand.net
Message-Id: <20040621220914.4cad7151.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <OKEPLEIOJKFGFGCKMDKJKEKOCGAA.cdel@firsthand.net>
References: <Pine.HPX.4.58.0406201546040.12903@wells.cisco.com>
	<OKEPLEIOJKFGFGCKMDKJKEKOCGAA.cdel@firsthand.net>
Organization: The No Sense Organisation (http://www.nosense.org)
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i686-pc-linux-gnu)
X-Location: Adelaide, Australia
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ole@cisco.com, ietf@ietf.org, hadmut@danisch.de
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

On Mon, 21 Jun 2004 10:03:46 +0100
"Christian de Larrinaga" <cdel@firsthand.net> wrote:

<snip>

> A traveller cannot change ISP easily so either will just have to accept some
> things cannot be done or will find a way. As it happens one can preplan and
> setup a proxy service or a tunnel broker etc that can get round many of
> these issues.
> 
> Perhaps the IETF would be wiser to give a warning about the futility of
> trying to break application transparency. "The Internet user may always find
> a way to communicate on their own terms"

... using the following tunnel broker / VPN peer. The neat thing about it is
that it uses SSL/TLS over UDP, and you can specify the UDP ports to use. As it
uses UDP to encapsulate the IP packets, the outer IP header can be NATted.

Also, as it uses UDP, and the ports are selectable, you may be able to "punch"
a pipe through a firewall, by using UDP ports #53 a.k.a. DNS, depending on how
well the firewall inspects DNS traffic. If that works out, "The Internet user
may always find a way to communicate on their own terms", irrespective of NAT.

http://openvpn.sourceforge.net/


Regards,
Mark.

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


From ietf-bounces@ietf.org  Mon Jun 21 12:26:35 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00211
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 12:26:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcRcz-000702-Ck
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 12:26:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcR4v-0000sH-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 11:51:25 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcQ2s-0000i0-02; Mon, 21 Jun 2004 10:45:14 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BcPmh-0004FV-KD; Mon, 21 Jun 2004 10:28:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcPWk-0007Wk-JS; Mon, 21 Jun 2004 10:12:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BbWhi-0001AK-Ud
	for ietf@megatron.ietf.org; Fri, 18 Jun 2004 23:39:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13314
	for <ietf@ietf.org>; Fri, 18 Jun 2004 23:39:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BbWhf-0002v2-W8
	for ietf@ietf.org; Fri, 18 Jun 2004 23:39:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BbWgi-0002Vp-00
	for ietf@ietf.org; Fri, 18 Jun 2004 23:38:41 -0400
Received: from sa.vix.com ([204.152.187.1]) by ietf-mx with esmtp (Exim 4.12)
	id 1BbWeS-0001VP-00
	for ietf@ietf.org; Fri, 18 Jun 2004 23:36:20 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id EDE8413DE5; Sat, 19 Jun 2004 03:35:49 +0000 (GMT)
To: ietf@ietf.org
References: <043e01c455a5$0e0770f0$6401a8c0@stephen>
From: Paul Vixie <vixie@vix.com>
Date: 19 Jun 2004 03:35:49 +0000
In-Reply-To: <043e01c455a5$0e0770f0$6401a8c0@stephen>
Message-ID: <g3oeng9q3u.fsf@sa.vix.com>
Lines: 15
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Mon, 21 Jun 2004 10:08:36 -0400
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

stephen@sprunk.org ("Stephen Sprunk") writes:
> ...
> Dean's problem is that he sends mail from an open relay, which isc.org's
> servers block completely ...

actually i think the reason dv8's ip address listed on SORBS is due to
reported irregularities in the trust deed for that address block, rather
than due to reported open relay activities.  maybe dv8 will eventually
sue somebody, so that a court can sort it all out and all the facts can
be objectively and publically known.

a note for harald and the others-- i've been lawsuit-threated by experts,
and i can tell you from that experience, dv8 appears to not be an expert.
-- 
Paul Vixie

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


From ietf-bounces@ietf.org  Mon Jun 21 13:18:36 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07248
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 13:18:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcSRI-0007AX-Kz
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 13:18:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcSE3-0004Zs-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 13:04:56 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcRp0-0000W0-00; Mon, 21 Jun 2004 12:39:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcRiD-0003Fa-Hs; Mon, 21 Jun 2004 12:32:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcR3k-0001RJ-QN
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 11:50:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23643
	for <ietf@ietf.org>; Mon, 21 Jun 2004 11:50:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcR3j-0000eJ-MZ
	for ietf@ietf.org; Mon, 21 Jun 2004 11:50:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcQ1R-0000aK-00
	for ietf@ietf.org; Mon, 21 Jun 2004 10:43:46 -0400
Received: from user-0c6s11v.cable.mindspring.com ([24.110.4.63]
	helo=sleekfreak.ath.cx) by ietf-mx with esmtp (Exim 4.12)
	id 1BcP8o-0001zl-00
	for ietf@ietf.org; Mon, 21 Jun 2004 09:47:19 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1BcKU3-0002e3-00; Mon, 21 Jun 2004 04:48:55 -0400
Date: Mon, 21 Jun 2004 04:48:52 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Florian Weimer <fw@deneb.enyo.de>
In-Reply-To: <871xk92x6f.fsf@deneb.enyo.de>
Message-ID: <Pine.LNX.4.44.0406210441150.10159-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org, Hadmut Danisch <hadmut@danisch.de>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=1.9 required=5.0 tests=WEIRD_PORT autolearn=no 
	version=2.60

Ive been watching this thread for some time, and its time for me to pipe
in...

I've been working on a viable hotel solution for some time now, and the
best I have been able to come up with is a terminal server with thin
clients (bootp, tftp, xdmcp... you know the drill) in the guest rooms.
The clients are NATed, due to cost of address allocation.  They work fine
in this scenario, for the standard business traveler, as well as
providing universal access for everyone who does not carry a laptop.  For
someone who wants more and has their own hardware, the terminal server
also routes v6 packets, providing end to end connectivity.

Regarding the ISP filtering issue, I had to figuratively kick my local
cable provider in the head to get them to drop the port 80 block on my
circuit, and they list all of their non-"business class" IP's with a RBL
in order to force usage of their mail relays.

Its a sad situation.

Scott

On Mon, 21 Jun 2004, Florian Weimer wrote:

> * Hadmut Danisch:
>
> > at least here in Germany Internet providers tend to
> > do and not to do what they want.
> >
> > - Some cut off their clients every 24 hours (DSL)
>
> This happens on the sub-IP layer and hasn't got to do much with ISPs.
>
> > - Some block or slowdown particular tcp ports
> >   to get rid of peer-to-peer file sharing
>
> You get what you pay for.
>
> > - Some redirect the first web access to any site
> >   to their own to force you to read their ads
>
> Same here.
>
> > - Very few support multicast. When I asked my
> >   own provider, they didn't even know what this is.
> >   (They said 'no, because they don't support Linux'.)
>
> You can't get reliable multicast service anywhere in the world.
> People tend to switch it off if it threatens to impact unicast
> traffic.  It's not possible to run production services over multicast
> across the Internet at the moment, at least not without a fallback to
> unicast.
>
> > - IPv6? Huh? What's that?
>
> It's not a real problem to get native IPv6 over ADSL or SDSL.
>
> > - At least one large provider blocks port 25 to certain IP
> >   addresses in order to force you to use the provider's
> >   mail relay
>
> Which one is that?
>
> The case you are writing about does *not* block 25/TCP on the TCP/IP
> layer.
>
> It's true that certain extremely cheap products don't offer that much
> Internet or Service.  These products are marketed aggressively and are
> usually sold at a loss.  Nobody forces you to buy them.
>
> --
> Current mail filters: many dial-up/DSL/cable modem hosts, and the
> following domains: bigpond.com, di-ve.com, fuorissimo.com, hotmail.com,
> jumpy.it, libero.it, netscape.net, postino.it, simplesnet.pt, spymac.com,
> tiscali.co.uk, tiscali.cz, tiscali.it, voila.fr, yahoo.com.
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


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


From ietf-bounces@ietf.org  Mon Jun 21 14:29:51 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14307
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 14:29:51 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcTYG-0003XH-8j
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 14:29:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcTXG-0003Bi-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 14:28:50 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcTW9-0002Xg-00; Mon, 21 Jun 2004 14:27:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcTKc-0003bx-Ql; Mon, 21 Jun 2004 14:15:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcRee-0002uw-0h
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 12:28:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00311
	for <ietf@ietf.org>; Mon, 21 Jun 2004 12:28:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcRec-0007AH-Oq
	for ietf@ietf.org; Mon, 21 Jun 2004 12:28:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcR5s-00014X-00
	for ietf@ietf.org; Mon, 21 Jun 2004 11:52:26 -0400
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 1BcQ5h-00011G-00
	for ietf@ietf.org; Mon, 21 Jun 2004 10:48:09 -0400
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id 8AB798580; Mon, 21 Jun 2004 16:48:05 +0200 (CEST)
Received: from purgatory.unfix.org ([127.0.0.1])
	by localhost (purgatory [127.0.0.1]) (amavisd-new, port 10024)
	with SMTP id 12083-14; Mon, 21 Jun 2004 16:47:52 +0200 (CEST)
Received: from [9.4.70.109] (pat.zurich.ibm.com [195.176.20.45])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 445747F67; Mon, 21 Jun 2004 16:47:52 +0200 (CEST)
From: Jeroen Massar <jeroen@unfix.org>
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040621220914.4cad7151.ietf@130c04165a5b40404e4440445758487a.nosense.org>
References: <Pine.HPX.4.58.0406201546040.12903@wells.cisco.com>
	<OKEPLEIOJKFGFGCKMDKJKEKOCGAA.cdel@firsthand.net>
	<20040621220914.4cad7151.ietf@130c04165a5b40404e4440445758487a.nosense.org>
Organization: Unfix
Message-Id: <1087829268.8105.185.camel@segesta.zurich.ibm.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) 
Date: Mon, 21 Jun 2004 16:47:49 +0200
X-Virus-Scanned: purgatory.unfix.org - http://unfix.org
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0264761188=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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


--===============0264761188==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-vtC8BJikE6lDJGeWQQkz"


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

On Mon, 2004-06-21 at 14:39, Mark Smith wrote:
> On Mon, 21 Jun 2004 10:03:46 +0100
> "Christian de Larrinaga" <cdel@firsthand.net> wrote:
>=20
> <snip>
>=20
> > A traveller cannot change ISP easily so either will just have to accept=
 some
> > things cannot be done or will find a way. As it happens one can preplan=
 and
> > setup a proxy service or a tunnel broker etc that can get round many of
> > these issues.
> >=20
> > Perhaps the IETF would be wiser to give a warning about the futility of
> > trying to break application transparency. "The Internet user may always=
 find
> > a way to communicate on their own terms"
>=20
> ... using the following tunnel broker / VPN peer. The neat thing about it=
 is
> that it uses SSL/TLS over UDP, and you can specify the UDP ports to use. =
As it
> uses UDP to encapsulate the IP packets, the outer IP header can be NATted=
.
>=20
> Also, as it uses UDP, and the ports are selectable, you may be able to "p=
unch"
> a pipe through a firewall, by using UDP ports #53 a.k.a. DNS, depending o=
n how
> well the firewall inspects DNS traffic. If that works out, "The Internet =
user
> may always find a way to communicate on their own terms", irrespective of=
 NAT.

You are forgetting something very big here:
 Only the smart internet users will find a way out.

Normal users, the masses, the ones that bring in the cash, don't know
this. The smart ones will pick a real ISP anyways. The others bring in
enough cash that even though there are only a few doing the tunneling
thing the ISP doing this really doesn't care about those.
This are all just normal 'business cases' the same like saying "there
are not enough IP addresses thus you get only one" etc.
IETF can't do much about it, except making protocols that can't be
NATted and that are of the 'http' or 'p2p' rating, aka something that
all the users want but which can't work behind a NAT... enter IPv6 ;)

Also the above requires on to tunnel thus you are getting real service
from somebody else and basically using your current provider as the l2
provider.

The same is the issue with IPv6 Tunnel Brokers which can be seen as
ISP's in the fact that they provide IPv6 connectivity. Though the 'l2
medium' is the IPv4 connectivity of another ISP instead of ethernet or
cable.

Greets,
 Jeroen


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iD8DBQBA1vUUKaooUjM+fCMRApdHAKCE7jGc6f7sepXIu6EZNoVPjYEyigCfV7VT
WazC7XCaTmHlh5IcsqasNaU=
=zu0o
-----END PGP SIGNATURE-----

--=-vtC8BJikE6lDJGeWQQkz--



--===============0264761188==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0264761188==--




From ietf-bounces@ietf.org  Mon Jun 21 14:38:21 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15277
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 14:38:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcTgU-0006G3-7o
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 14:38:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcTfO-0005u1-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 14:37:14 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcTee-0005Xh-00; Mon, 21 Jun 2004 14:36:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcTKp-0003e4-Ng; Mon, 21 Jun 2004 14:15:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcRxV-0005s5-GD
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 12:47:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01590
	for <ietf@ietf.org>; Mon, 21 Jun 2004 12:47:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcRxU-0001UE-Hh
	for ietf@ietf.org; Mon, 21 Jun 2004 12:47:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcREu-00036I-00
	for ietf@ietf.org; Mon, 21 Jun 2004 12:01:45 -0400
Received: from hdflem01.fl.hostdepot.net ([66.242.128.131])
	by ietf-mx with esmtp (Exim 4.12) id 1BcQNW-0002zh-00
	for ietf@ietf.org; Mon, 21 Jun 2004 11:06:34 -0400
Received: from compaq (unverified [67.161.164.119]) by
	hdflem01.fl.hostdepot.net (Vircom SMTPRS 3.1.293.1) with ESMTP id
	<B1033403464@hdflem01.fl.hostdepot.net>; 
	Mon, 21 Jun 2004 11:05:57 -0400
From: "Dr Harsh Verma" <hverma@glocol.net>
To: "'Mark Smith'" <ietf@130c04165a5b40404e4440445758487a.nosense.org>,
        <cdel@firsthand.net>, <ietf@ietf.org>
Date: Mon, 21 Jun 2004 08:01:10 -0700
Organization: Glocol
Message-ID: <000001c457a0$9832b3a0$6401a8c0@compaq>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
Importance: Normal
In-Reply-To: <20040621220914.4cad7151.ietf@130c04165a5b40404e4440445758487a.nosense.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Cc: ole@cisco.com, hadmut@danisch.de
Subject: RE: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: hverma@glocol.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Yes, with tunnel brokering and the ability to reverse-tunnel "Roaming" 
'Internet users should be able find a way to communicate on their own
terms', as they move in a "Mobile Environment" switching back-end
networks if required, for Mobile VPN.

Kudos to Cisco's Mobile Access Router 3200 for being  an example for
this architecture.

Yes, I had the pleasure of "piggyback" riding a WiFi network setup by a
neighbor while in a hotelroom in a remote, forsaken  place and in the
words of Ole, 'as a consumer of paid-for Internet service (that works)',
there was no reason for me to care and probably these rules set for user
terms will need to be integrated for policy to switch to another network
if I really have to pay. Somebody is paying, but there really ain't no
free lunch!

Regards,
Harsh Verma
Director, R&D, GLOCOL, Inc
Past Vice-Chair (Industry) R&D WG, NECCC
Member, Cross Boundary WG
Tel: +1(916)684-3262
E-Mail: hverma@glocol.net  
www.glocol.net  
 



-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Mark Smith
Sent: Monday, June 21, 2004 5:39 AM
To: cdel@firsthand.net
Cc: ole@cisco.com; ietf@ietf.org; hadmut@danisch.de
Subject: Re: What exactly is an internet (service) provider?


On Mon, 21 Jun 2004 10:03:46 +0100
"Christian de Larrinaga" <cdel@firsthand.net> wrote:

<snip>

> A traveller cannot change ISP easily so either will just have to 
> accept some things cannot be done or will find a way. As it happens 
> one can preplan and setup a proxy service or a tunnel broker etc that 
> can get round many of these issues.
> 
> Perhaps the IETF would be wiser to give a warning about the futility 
> of trying to break application transparency. "The Internet user may 
> always find a way to communicate on their own terms"

... using the following tunnel broker / VPN peer. The neat thing about
it is that it uses SSL/TLS over UDP, and you can specify the UDP ports
to use. As it uses UDP to encapsulate the IP packets, the outer IP
header can be NATted.

Also, as it uses UDP, and the ports are selectable, you may be able to
"punch" a pipe through a firewall, by using UDP ports #53 a.k.a. DNS,
depending on how well the firewall inspects DNS traffic. If that works
out, "The Internet user may always find a way to communicate on their
own terms", irrespective of NAT.

http://openvpn.sourceforge.net/


Regards,
Mark.

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


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


From ietf-bounces@ietf.org  Mon Jun 21 16:11:05 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23836
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 16:11:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcV8E-00027m-07
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 16:11:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcV5c-0001HR-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 16:08:25 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcV4U-0000vc-01; Mon, 21 Jun 2004 16:07:14 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BcUx3-0003pb-JL; Mon, 21 Jun 2004 15:59:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcUsi-0008Mf-2E; Mon, 21 Jun 2004 15:55:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcUWN-0001eY-Nu
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 15:31:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20114
	for <ietf@ietf.org>; Mon, 21 Jun 2004 15:31:57 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcUWM-0005VI-58
	for ietf@ietf.org; Mon, 21 Jun 2004 15:31:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcUVS-0005D3-00
	for ietf@ietf.org; Mon, 21 Jun 2004 15:31:02 -0400
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12) id 1BcUUX-0004wQ-00
	for ietf@ietf.org; Mon, 21 Jun 2004 15:30:05 -0400
Received: (qmail 14670 invoked by uid 1013); 21 Jun 2004 19:30:03 -0000
Date: Mon, 21 Jun 2004 21:30:03 +0200
From: Markus Stumpf <maex-lists-ietf-general@Space.Net>
To: hadmut@danisch.de
Message-ID: <20040621193003.GH89866@Space.Net>
References: <20040619094223.GA4764@danisch.de> <871xk92x6f.fsf@deneb.enyo.de>
	<20040621090051.GA20379@danisch.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040621090051.GA20379@danisch.de>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

Hoi Hadmut,

On Mon, Jun 21, 2004 at 11:00:51AM +0200, hadmut@danisch.de wrote:
> I do not want to blame anyone for selling NAT access. 
> I want him to give a clear statement about what he is 
> selling.

You have a contract. This should be listed in the contract and you
can read it before signing it. If the contract doesn't talk about
limits and they do limit you, sue them.

Blocking Port 25 outgoing for DSL surf accounts is not a problem,
there is RFC 2476. If your email provider doesn't support message
submission ask them why.

> (And, btw, some of the statements are incorrect.
> - Some providers intentionally cut their customers
>   off after 24 hours in order to force them to have
>   a new IP address.

You have to look at what they sell. They sell "DSL Surf Accounts".
Surfers usually aren't online for 24 hours without interuption and
they don't have problems with the interupt in "normal use". If you get a
"business access" you will not have the problem in most of the cases.

> - It is a real problem to get native IPv6 over DSL 
>   in Germany. Some providers simply don't want to 
>   provide IPv6, because they say "Internet" is IPv4.

You only have to look a bit harder ;-)

	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"

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


From ietf-bounces@ietf.org  Mon Jun 21 16:51:15 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28160
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 16:51:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcVl6-0006ee-Fm
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 16:51:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcVjz-0006KE-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 16:50:08 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcVjC-0005qN-00; Mon, 21 Jun 2004 16:49:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcVbv-0004US-EC; Mon, 21 Jun 2004 16:41:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcShr-0006If-0g
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 13:35:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10277
	for <ietf@ietf.org>; Mon, 21 Jun 2004 13:35:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcShq-0003E8-0C
	for ietf@ietf.org; Mon, 21 Jun 2004 13:35:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcSfH-0002f6-00
	for ietf@ietf.org; Mon, 21 Jun 2004 13:33:04 -0400
Received: from mail5.atl.registeredsite.com ([64.224.219.79] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12) id 1BcSd6-0001y0-00
	for ietf@ietf.org; Mon, 21 Jun 2004 13:30:48 -0400
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail5.atl.registeredsite.com (8.12.11/8.12.8) with ESMTP id
	i5LHUjF0031756 for <ietf@ietf.org>; Mon, 21 Jun 2004 17:30:45 GMT
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ;
	Mon, 21 Jun 2004 12:30:44 -0500
Message-ID: <40D71B38.9080604@nma.com>
Date: Mon, 21 Jun 2004 10:30:32 -0700
From: Ed Gerck <egerck@nma.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
References: <03ae01c45596$5864c170$6401a8c0@stephen>
	<200406190254.i5J2scW3022797@calcite.rhyolite.com>
In-Reply-To: <200406190254.i5J2scW3022797@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Rcpt-To: <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 21 Jun 2004 16:41:46 -0400
Subject: solution -- Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

The solution to this self-limitation problem [1], if the Internet MUST be
the only communication path used by someone, is to use IETF web forms
that go directly to the server. Anyone can access the web forms and submit
their communication to the relevant persons/WGs. If the site is down, try
later.

Cheers,
Ed Gerck

[1] If someone wants to only use email for communication, this means
that email will be his single point of failure in communication.
Even if it's an ietf.org email. And, one may ask, what's wrong with
using a postal address if email fails? After all, IETF IDs and RFCs
include the postal addresses of authors. And some also have phone,
fax, pager, IRC, IM, etc., available. Insisting on using only one
communication path is un-Internet.




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


From ietf-bounces@ietf.org  Mon Jun 21 17:56:45 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05734
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 17:56:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcWmU-0001je-OM
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 17:56:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcWkZ-0001Dd-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 17:54:47 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcWi9-0000Yn-00; Mon, 21 Jun 2004 17:52:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcWUT-0006dS-LH; Mon, 21 Jun 2004 17:38:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcWEn-0000XF-2H
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 17:21:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01339
	for <ietf@ietf.org>; Mon, 21 Jun 2004 17:21:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcWEl-00010B-PC
	for ietf@ietf.org; Mon, 21 Jun 2004 17:21:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcWCA-0000AE-00
	for ietf@ietf.org; Mon, 21 Jun 2004 17:19:14 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BcW9u-00077X-00
	for ietf@ietf.org; Mon, 21 Jun 2004 17:16:55 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i5LLGPTq048197
	for ietf@ietf.org env-from <vjs>;
	Mon, 21 Jun 2004 15:16:25 -0600 (MDT)
Date: Mon, 21 Jun 2004 15:16:25 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200406212116.i5LLGPTq048197@calcite.rhyolite.com>
To: ietf@ietf.org
References: <20040621193003.GH89866@Space.Net>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> From: Markus Stumpf 

> You have a contract. This should be listed in the contract and you
> can read it before signing it. If the contract doesn't talk about
> limits and they do limit you, sue them.

Sue on what grounds?  Who says that Internet service has no limits?
All reputable service providers have terms of service that include
limits, starting with something about network abuse.  (Never mind 
how well those limits are enforced.)  Many service providers limit
their users to not running "servers," but good luck finding someone
who knows what they mean by "server." 
Since there are always providers, you can't sue simply because you
bought an account with limits you failed to clarify.


Trying to find first line technical support people (never mind sales)
at a consumer grade ISP who knows has any idea what sort of filtering
their employer does is hopeless.  It's generally foolish to expect to
find someone who even understands the question.


 > (And, btw, some of the statements are incorrect.
> > - Some providers intentionally cut their customers
> >   off after 24 hours in order to force them to have
> >   a new IP address.

(Some "DSL modems" including the Actiontec 1524 kill TCP connections
after an hour or two all by themselves)


> You have to look at what they sell. They sell "DSL Surf Accounts".
> Surfers usually aren't online for 24 hours without interuption and
> they don't have problems with the interupt in "normal use". If you get a
> "business access" you will not have the problem in most of the cases.

I've not seen anyone selling "DSL Surf Accounts," but I've never looked,
and certainly not in Germany.

In any case, 
  - which of the classes in 
http://www.ietf.org/internet-drafts/draft-klensin-ip-service-terms-02.txt
    is closest to a "DSL Surf Accounts"?

 - Should one of those four categories be renamed "DSL Surf Accounts"?

 - Should a new class named be "DSL Surf Accounts" be added?

 - exactly what filtering is imposed on a "DSL Surf Account"?  Is
     port 25 filtered?   22?  135 and 138?  Some or all UDP?  ICMP?

 - and the same questions for "business access."

Telling people to read contracts ISP today is disingenuous.  If the
IETF would define "DSL Surf Accounts" and "business access," then you
could hope to ask for one or the other.  You might then sue if you
didn't get whichever you wanted.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Mon Jun 21 18:38:06 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10907
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 18:38:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcXQV-0006AI-LS
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 18:38:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcXPa-0005tO-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 18:37:11 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcXPD-0005cL-00; Mon, 21 Jun 2004 18:36:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcXFE-0001cl-Nu; Mon, 21 Jun 2004 18:26:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcX1D-0003L7-PM
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 18:12:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07848
	for <ietf@ietf.org>; Mon, 21 Jun 2004 18:11:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcX1C-0006Ky-CA
	for ietf@ietf.org; Mon, 21 Jun 2004 18:11:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcX0G-000626-00
	for ietf@ietf.org; Mon, 21 Jun 2004 18:11:01 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12) id 1BcWzH-0005lJ-00
	for ietf@ietf.org; Mon, 21 Jun 2004 18:09:59 -0400
Received: (qmail 41174 invoked from network); 21 Jun 2004 22:08:37 -0000
Received: from yahoobb219001188014.bbtec.net (HELO necom830.hpcl.titech.ac.jp)
	(219.1.188.14)
	by necom830.hpcl.titech.ac.jp with SMTP; 21 Jun 2004 22:08:37 -0000
Message-ID: <40D75DE6.80106@necom830.hpcl.titech.ac.jp>
Date: Tue, 22 Jun 2004 07:15: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: Jeroen Massar <jeroen@unfix.org>
References: <Pine.HPX.4.58.0406201546040.12903@wells.cisco.com>	<OKEPLEIOJKFGFGCKMDKJKEKOCGAA.cdel@firsthand.net>	<20040621220914.4cad7151.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<1087829268.8105.185.camel@segesta.zurich.ibm.com>
In-Reply-To: <1087829268.8105.185.camel@segesta.zurich.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>,
        ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Jeroen Massar

> You are forgetting something very big here:
>  Only the smart internet users will find a way out.

The argument that the smart users can use IP over HTTP makes
John's classifications such as "web providers" unnecessary.

> Also the above requires on to tunnel thus you are getting real service
> from somebody else and basically using your current provider as the l2
> provider.

There are a lot of Hotels claiming Internet capable only because
their rooms have extra RJ-11.

At Geneva, Internet capable hotel rooms have RJ-45, not for Ethernet
but for ISDN. :-|

IETF can not stop them claiming Internet capable.

So, let's call all the telephone companies ISPs.

Smart users can, just like having VPN servers, have modems at
home to establish dial-up connection to the Internet from
any PSTN telephone in the world.

						Masataka Ohta



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


From ietf-bounces@ietf.org  Mon Jun 21 18:49:57 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11725
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 18:49:57 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcXbz-0001vn-3y
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 18:49:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcXb0-0001dy-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 18:48:59 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcXa3-00016B-00; Mon, 21 Jun 2004 18:47:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcXOH-0004I4-Si; Mon, 21 Jun 2004 18:35:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcXDC-0000yZ-Hd
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 18:24:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09976
	for <ietf@ietf.org>; Mon, 21 Jun 2004 18:24:19 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcXDB-00024K-0V
	for ietf@ietf.org; Mon, 21 Jun 2004 18:24:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcXCA-0001lW-00
	for ietf@ietf.org; Mon, 21 Jun 2004 18:23:19 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1BcXBR-0001O1-00
	for ietf@ietf.org; Mon, 21 Jun 2004 18:22:33 -0400
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 i5LMLrKV018963
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 21 Jun 2004 18:21:57 -0400
Date: Mon, 21 Jun 2004 18:21:53 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <Pine.LNX.4.44.0406211814230.18782-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
Subject: Additional complaint about disparagement by Paul Vixie on IETF lists
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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


Harald, Please add __Another__ complaint to the chair about inappropriate
behavior by Mr. Vixie.  Altering our name from Av8 Internet to "dv8" is 
simply more disparagement and though we've all come to expect 
such 3rd grade, infantile behavior from Mr. Vixie, it is still 
inappropriate. 

The Chair's failure to chastise the many examples of this behavior by Mr.  
Vixie seems to indicate that the Chair has no interest in upholding the
principles of the ISOC or the IETF, and the IETF Mission.  If that is the
case, then perhaps the Chair should resign, so the Chairmanship can be
filled by someone who is interested in doing these things.

Dean Anderson
Av8 Internet, Inc


---------- Forwarded message ----------
Date: 19 Jun 2004 03:35:49 +0000
From: Paul Vixie <vixie@vix.com>
To: ietf@ietf.org
Subject: Re: Response to complaint from Dean Anderson (fwd)

stephen@sprunk.org ("Stephen Sprunk") writes:
> ...
> Dean's problem is that he sends mail from an open relay, which isc.org's
> servers block completely ...

actually i think the reason dv8's ip address listed on SORBS is due to
reported irregularities in the trust deed for that address block, rather
than due to reported open relay activities.  maybe dv8 will eventually
sue somebody, so that a court can sort it all out and all the facts can
be objectively and publically known.

a note for harald and the others-- i've been lawsuit-threated by experts,
and i can tell you from that experience, dv8 appears to not be an expert.
-- 
Paul Vixie

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



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


From ietf-bounces@ietf.org  Mon Jun 21 19:08:33 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13591
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 19:08:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcXtx-0007ag-Cw
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 19:08:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcXso-0007El-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 19:07:22 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcXrv-0006qS-00; Mon, 21 Jun 2004 19:06:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcXgh-0002AJ-PA; Mon, 21 Jun 2004 18:54:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcXY6-0008C2-Qa
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 18:45:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11434
	for <ietf@ietf.org>; Mon, 21 Jun 2004 18:45:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcXY5-0000j1-Dr
	for ietf@ietf.org; Mon, 21 Jun 2004 18:45:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcXX6-0000RL-00
	for ietf@ietf.org; Mon, 21 Jun 2004 18:44:56 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1BcXW5-0007hm-00
	for ietf@ietf.org; Mon, 21 Jun 2004 18:43:53 -0400
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 i5LMhNRF019326
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 21 Jun 2004 18:43:24 -0400
Date: Mon, 21 Jun 2004 18:43:23 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Paul Vixie <vixie@vix.com>
In-Reply-To: <g3oeng9q3u.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0406211822300.18782-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

While there have been "reported irregularities", the person making the
report (Alan Brown) is a court-proven liar, and has done this sort of
thing in the past.  An examination of the records shows no irregularities,
and the entities assigned still exist. All the facts are already publicly
known. The claim of being "hijacked/disused" is false.

It is also publicly known that Mr. Brown, Mr. Sullivan, and Mr. Vixie have
blacklisted companies that aren't spammers in the past. Both Mr. Brown and
Mr. Vixie have been forced to retract those false claims by lawsuits, and
have risked or actually lost significant amounts of personal assets in
damages. 

Mr. Vixie's obvious malice for Av8 Internet is plain to see, as is his
association with SORBS, Brown, Sullivan, and other disreputable
characters.

Av8 has been through the legal "mill" and hired lawyers on the subject,
but that does not make it an expert on lawsuits. If Av8 were "expert" on
lawsuits, we'd be able to practice law ourselves instead of hiring
lawyers.

Av8 is a expert on Open Relay operations, and on providing internet
services to customers.  However, it is unclear what Mr. Vixie's expertise
is actually in, other than name-calling, and making disparaging
alterations on another companies trademarks. I have seen little else.  I
suppose Vixie is also an expert at making false claims and using
blacklists to block companies that aren't spammers.


Dean Anderson
Av8 Internet, Inc



On 19 Jun 2004, Paul Vixie wrote:

> stephen@sprunk.org ("Stephen Sprunk") writes:
> > ...
> > Dean's problem is that he sends mail from an open relay, which isc.org's
> > servers block completely ...
> 
> actually i think the reason dv8's ip address listed on SORBS is due to
> reported irregularities in the trust deed for that address block, rather
> than due to reported open relay activities.  maybe dv8 will eventually
> sue somebody, so that a court can sort it all out and all the facts can
> be objectively and publically known.
> 
> a note for harald and the others-- i've been lawsuit-threated by experts,
> and i can tell you from that experience, dv8 appears to not be an expert.
> 


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


From ietf-bounces@ietf.org  Mon Jun 21 19:29:28 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15622
	for <ietf-archive@ietf.org>; Mon, 21 Jun 2004 19:29:28 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcYEC-0006bx-KQ
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 19:29:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcYDA-0006Iy-00
	for ietf-archive@ietf.org; Mon, 21 Jun 2004 19:28:25 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcYCV-0005vr-00; Mon, 21 Jun 2004 19:27:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BcY5g-0000AN-6O; Mon, 21 Jun 2004 19:20:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcXzS-0006jw-2g
	for ietf@megatron.ietf.org; Mon, 21 Jun 2004 19:14:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14120
	for <ietf@ietf.org>; Mon, 21 Jun 2004 19:14:12 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcXzQ-0001b8-JB
	for ietf@ietf.org; Mon, 21 Jun 2004 19:14:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcXyX-0001JC-00
	for ietf@ietf.org; Mon, 21 Jun 2004 19:13:18 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BcXxj-000104-00
	for ietf@ietf.org; Mon, 21 Jun 2004 19:12:27 -0400
Received: from scan.jck.com ([209.187.148.215])
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BcXxd-000LXn-00; Mon, 21 Jun 2004 18:12:21 -0500
Date: Mon, 21 Jun 2004 19:12:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>,
        Jeroen Massar <jeroen@unfix.org>
Message-ID: <EF973F96D27E7761FE612D73@scan.jck.com>
In-Reply-To: <40D75DE6.80106@necom830.hpcl.titech.ac.jp>
References: <Pine.HPX.4.58.0406201546040.12903@wells.cisco.com>
	<OKEPLEIOJKFGFGCKMDKJKEKOCGAA.cdel@firsthand.net>
	<20040621220914.4cad7151.ietf@130c04165a5b40404e4440445758487a.no
	sense.org>	<1087829268.8105.185.camel@segesta.zurich.ibm.com>
	<40D75DE6.80106@necom830.hpcl.titech.ac.jp>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Cc: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>,
        ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On Tuesday, 22 June, 2004 07:15 +0900 Masataka Ohta
<mohta@necom830.hpcl.titech.ac.jp> wrote:

> Jeroen Massar
> 
>> You are forgetting something very big here:
>>  Only the smart internet users will find a way out.
> 
> The argument that the smart users can use IP over HTTP makes
> John's classifications such as "web providers" unnecessary.
> 
>> Also the above requires on to tunnel thus you are getting
>> real service from somebody else and basically using your
>> current provider as the l2 provider.
> 
> There are a lot of Hotels claiming Internet capable only
> because their rooms have extra RJ-11.
> 
> At Geneva, Internet capable hotel rooms have RJ-45, not for
> Ethernet but for ISDN. :-|
> 
> IETF can not stop them claiming Internet capable.

No, IETF can't.  But IETF can create definitions that help those
who want to be truthful about what they are providing do that,
in a way that is clear to themselves and their potential
customers.  Such definitions may also help folks with those RJ11
or ISDN connections understand why their customers get
frustrated and threaten to never return -- today, they are
mostly just bewildered.

If, with or without those definitions, someone is determined to
lie, they will certainly do that and IETF won't be able to do a
thing about it.  Perhaps local regulators and courts and
hotel-rating agencies will, but not IETF.

Let me give a specific example that leads me to believe there is
hope in at least some portions of this problem.  These days,
before making a hotel reservation, I routinely check on whether
they offer "Internet access".  As others have suggested, I don't
bother asking about NATs, funny filters, etc. -- the odds that
someone at the reservations desk will have a clue are about
zero.  But I do ask and, if I get a "no" answer, I'm reasonably
likely to try to pick a different hotel (usually a much more
competitive market than the range of options I have in my
neighborhood for "lowest price acceptable service", partially
because I impose fewer requirements).  Now I've gotten to hotels
after getting a "yes" answer and had the same experiences that
Ohta-san obviously has: I ask about Internet and am eventually
pointed to an RJ11 jack or, worse, an RJ45 jack that might be
ISDN and might be no longer hooked up and about which no one can
answer questions about charging.  Or, as happened a month ago, I
find WiFi in the lobby but a beacon connected to... nothing.
Seems the hotel took their wired Ethernet to the rooms out a
month previously, hasn't gotten the 802.11 hooked up to a router
yet, and didn't intend to start figuring what to do with the
rooms until they figured out how much capacity the 802.11 has
and how far it would reach.  

I tend to find these situations annoying, just as I find getting
to a hotel that advertises "Internet in every room" and
discovering that they mean a WebTV clone and nothing else, not
even a spare RJ11 jack.  I complain.  I write letters.  I
collect selections of groveling apologies, especially from
hotels that are members of chains in which I stay fairly often.
But I also get a certain amount of astonishment from folks who
were clearly clueless and don't quite understand why I'm upset.
The I-D was driven partially by a desire to go to them and say
"ok, hotel manager, there are these categories, and they are
pretty generally understood.  Take the list to your supplier,
find out what they are providing you, and then tell the truth
when someone asks.  If you are providing WebTV-clone-only
access, and you tell someone that, and they say 'sorry, I'll
find somewhere else to stay', then you have a basis for thinking
about some business decisions."   

That is the best I know how to do, but I think it would be a
step forward.

And, that said, Ohta-san's note and the above suggests that
there are at least two, maybe three, categories missing from the
I-D because it sort of assumes a "broadband" connection or
better, e.g., 

	* We provide a really nice telephone line, but you are
	on your own for modems, adapters, and ISPs.
	
	* We provide a really nice telephone line that can be
	used with your modem, and an in-house terminal server
	connected to our ISP (that was popular several years
	ago, is anyone still doing it?)
	
	* There is this web-enabled TV set in your room, with
	its own keyboard, but you can't use your own machine
	except via the telephone.

Does the I-D need any of that?  Would anyone like to suggest
language?

> So, let's call all the telephone companies ISPs.

I can think of a lot of things to call telephone companies :-(.
For better or worse, it seems to be the nature of language and
marketing organizations that once-precise terms lose meaning.
Many of us can actually remember when "Decision Support System"
and even "Management Information System" meant something, and
neither one was a "glorified spreadsheet".  It happens.  It is
too bad.  But, if there is any cure, it is getting a bit ahead
of the terminology so that one can say "call yourself whatever
you like, but, if you don't use these service definitions
accurately, someone will probably accuse you of being
deliberately deceptive".  That is pretty close to my hotel
conversations.  Sometimes it will work.  Sometimes and in some
places, the regulators will get tired enough of complaints about
deceived consumers that they will make the definitions
mandatory.  Sometimes it won't.  Life is hard.

But it would be, IMO, stupid of us to say "the IETF can't
legislate this, or make possession of a NAT, or selling a
highly-filtered connection, a crime, so we should do nothing but
whine at regular intervals".

     john


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


From ietf-bounces@ietf.org  Tue Jun 22 10:53:20 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14076
	for <ietf-archive@ietf.org>; Tue, 22 Jun 2004 10:53:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcmeI-0001wz-0C
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 10:53:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bcl1s-0006OK-00
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 09:09:37 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BckK8-0000hU-01; Tue, 22 Jun 2004 08:24:24 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BckJv-0005lJ-LL; Tue, 22 Jun 2004 08:24:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BckH0-0005eP-4P; Tue, 22 Jun 2004 08:21:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bcdhv-00024b-LZ
	for ietf@megatron.ietf.org; Tue, 22 Jun 2004 01:20:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15652
	for <ietf@ietf.org>; Tue, 22 Jun 2004 01:20:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bcdht-0005Fo-IX
	for ietf@ietf.org; Tue, 22 Jun 2004 01:20:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bccl8-0002yi-00
	for ietf@ietf.org; Tue, 22 Jun 2004 00:19:47 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12) id 1Bcag0-0005Wp-00
	for ietf@ietf.org; Mon, 21 Jun 2004 22:06:20 -0400
Received: (qmail 42118 invoked from network); 22 Jun 2004 02:05:02 -0000
Received: from vaio.hpcl.titech.ac.jp (HELO necom830.hpcl.titech.ac.jp)
	(131.112.32.134)
	by necom830.hpcl.titech.ac.jp with SMTP; 22 Jun 2004 02:05:02 -0000
Message-ID: <40D7954D.4090707@necom830.hpcl.titech.ac.jp>
Date: Tue, 22 Jun 2004 11:11:25 +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: John C Klensin <john-ietf@jck.com>
References: <Pine.HPX.4.58.0406201546040.12903@wells.cisco.com>	<OKEPLEIOJKFGFGCKMDKJKEKOCGAA.cdel@firsthand.net>	<20040621220914.4cad7151.ietf@130c04165a5b40404e4440445758487a.no	sense.org>	<1087829268.8105.185.camel@segesta.zurich.ibm.com>	<40D75DE6.80106@necom830.hpcl.titech.ac.jp>
	<EF973F96D27E7761FE612D73@scan.jck.com>
In-Reply-To: <EF973F96D27E7761FE612D73@scan.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Jeroen Massar <jeroen@unfix.org>,
        Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

John C Klensin;

With your motivation explained and with your three new categories,
all of which are unrelated to telecommunication providers but
related to hotels, I think I can understand your fundamental
mistake.

That is, your draft should have been titled:

	Terminologies on Telecommunication Service Categories of
	Accomodation Service Providers

Given that your stay is temporary, permanent addresses are of
little value. Moreover, as most, if not all, hotels use NAT,
it is of little value to mention global addresses.

So, in the new draft, you should avoid the word "ISP". Instead,
you can, for example, say ASAP (Application Service Access
Provider).

Mobile operators in Japan does provide access to web services,
though not over IP, that they are WSAP. Or, do you like better
calling them Web Access Service Providers?

						Masataka Ohta



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


From ietf-bounces@ietf.org  Tue Jun 22 12:48:01 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22313
	for <ietf-archive@ietf.org>; Tue, 22 Jun 2004 12:48:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcoRH-0007YP-48
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 12:48:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcmBm-0006kI-00
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 10:23:55 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BckoZ-0004Ew-00; Tue, 22 Jun 2004 08:55:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bckks-0001TI-Dk; Tue, 22 Jun 2004 08:52:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bcdlo-0003ux-7T
	for ietf@megatron.ietf.org; Tue, 22 Jun 2004 01:24:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16644
	for <ietf@ietf.org>; Tue, 22 Jun 2004 01:24:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bcdlm-0005zs-5d
	for ietf@ietf.org; Tue, 22 Jun 2004 01:24:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bccx7-0004Ul-00
	for ietf@ietf.org; Tue, 22 Jun 2004 00:32:10 -0400
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx with esmtp (Exim 4.12) id 1BcavO-00078C-00
	for ietf@ietf.org; Mon, 21 Jun 2004 22:22:14 -0400
Received: from portal (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id 060F617921; Mon, 21 Jun 2004 22:22:10 -0400 (EDT)
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: Ed Gerck <egerck@nma.com>
In-Reply-To: Message from Ed Gerck <egerck@nma.com> 
	of "Mon, 21 Jun 2004 10:30:32 PDT." <40D71B38.9080604@nma.com> 
Date: Mon, 21 Jun 2004 22:22:10 -0400
Message-Id: <20040622022210.060F617921@portal.hamachi.org>
Cc: ietf@ietf.org
Subject: Re: non-solution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sommerfeld@orchard.arlington.ma.us
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> The solution to this self-limitation problem [1], if the Internet MUST be
> the only communication path used by someone, is to use IETF web forms
> that go directly to the server. 

It's not a solution.  For one, spammers, not content to ruin email,
have been abusing web forms for quite some time; spam filters will be
required there, as well.

						- Bill


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


From ietf-bounces@ietf.org  Tue Jun 22 13:26:05 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01358
	for <ietf-archive@ietf.org>; Tue, 22 Jun 2004 13:26:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bcp25-0006Ma-Qk
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 13:26:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcnV4-0000Aa-00
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 11:47:55 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BclUn-0001Yz-00; Tue, 22 Jun 2004 09:39:29 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BclLM-000052-Mb; Tue, 22 Jun 2004 09:29:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bckoi-0002UC-Qe; Tue, 22 Jun 2004 08:56:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bcgv4-0001Oy-V5
	for ietf@megatron.ietf.org; Tue, 22 Jun 2004 04:46:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18296
	for <ietf@ietf.org>; Tue, 22 Jun 2004 04:46:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bcgv2-0001fK-JI
	for ietf@ietf.org; Tue, 22 Jun 2004 04:46:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bcgu3-0001Lb-00
	for ietf@ietf.org; Tue, 22 Jun 2004 04:45:16 -0400
Received: from mail.enyo.de ([212.9.189.167]) by ietf-mx with esmtp (Exim 4.12)
	id 1Bcgt6-00012Q-00
	for ietf@ietf.org; Tue, 22 Jun 2004 04:44:17 -0400
Received: (debugging) helo=deneb.enyo.de ip=212.9.189.171 name=deneb.enyo.de
Received: from deneb.enyo.de ([212.9.189.171])
	by mail.enyo.de with esmtp id 1Bcgt6-0004nk-HB;
	Tue, 22 Jun 2004 10:44:16 +0200
Received: from fw by deneb.enyo.de with local (Exim 4.34)
	id 1Bcgt6-0000hW-70; Tue, 22 Jun 2004 10:44:16 +0200
To: hadmut@danisch.de
References: <20040619094223.GA4764@danisch.de> <871xk92x6f.fsf@deneb.enyo.de>
	<20040621090051.GA20379@danisch.de>
From: Florian Weimer <fw@deneb.enyo.de>
Date: Tue, 22 Jun 2004 10:44:16 +0200
In-Reply-To: <20040621090051.GA20379@danisch.de> (hadmut@danisch.de's
	message of "Mon, 21 Jun 2004 11:00:51 +0200")
Message-ID: <87d63syobj.fsf@deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> You missed the point. This is not about complaining that I don't get
> enough for the money. This is that I don't know in advance what
> I do get for my money.

So far, I had no trouble getting the facts beforehand.  If you can't
reach anyone at that ISP for comment, you don't want to become its
customer anyway because nobody will help you in case of errors.

> "Nobody forces you to buy them" is true only as long as I do 
> know what exactly they offer and as it is my decision to buy
> it or not. But if I buy "Internet" and don't see what I'm 
> buying, then I don't have the choice.

The choice exists.  Of course, you need to know how to make that
choice.  Just reading some web pages (particularly those which confirm
your prejudices) won't help you, though.

> - Some providers intentionally cut their customers
>   off after 24 hours in order to force them to have
>   a new IP address.

Which one?

> - It is a real problem to get native IPv6 over DSL 
>   in Germany.

It isn't.  Just be repeating it over and over again doesn't make it
true.  If you can't find an ISP which uses ZISP or ISPgate to deliver
IPv6, it's your fault.  There are some of them.

>   Some providers simply don't want to provide IPv6, because they say
>   "Internet" is IPv4.

This is certainly a reasonable approach at the moment.

-- 
Current mail filters: many dial-up/DSL/cable modem hosts, and the
following domains: bigpond.com, di-ve.com, fuorissimo.com, hotmail.com,
jumpy.it, libero.it, netscape.net, postino.it, simplesnet.pt, spymac.com,
tiscali.co.uk, tiscali.cz, tiscali.it, voila.fr, yahoo.com.

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


From ietf-bounces@ietf.org  Tue Jun 22 14:07:08 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09877
	for <ietf-archive@ietf.org>; Tue, 22 Jun 2004 14:07:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bcpfp-0005ls-C9
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 14:07:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bcoo9-0003me-00
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 13:11:41 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bcmyv-00042P-00; Tue, 22 Jun 2004 11:14:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bcmso-0001da-WD; Tue, 22 Jun 2004 11:08:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BchRz-00060p-3B
	for ietf@megatron.ietf.org; Tue, 22 Jun 2004 05:20:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20228
	for <ietf@ietf.org>; Tue, 22 Jun 2004 05:20:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BchRw-0004UX-J8
	for ietf@ietf.org; Tue, 22 Jun 2004 05:20:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BchR2-0004CR-00
	for ietf@ietf.org; Tue, 22 Jun 2004 05:19:21 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12) id 1BchQ9-0003bp-00
	for ietf@ietf.org; Tue, 22 Jun 2004 05:18:25 -0400
Received: from [202.159.52.124] (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i5M9Hil11576;
	Tue, 22 Jun 2004 02:17:46 -0700
Date: Tue, 22 Jun 2004 17:17:27 +0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <693894942.20040622171727@brandenburg.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
In-Reply-To: <31098184049B948E29A29935@[192\.168\.1\.47]>
References: <Pine.LNX.4.44.0406161800430.6106-100000@cirrus.av8.net>
	<31098184049B948E29A29935@[192.168.1.47]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 22 Jun 2004 10:28:18 -0400
Cc: ietf@ietf.org
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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.8 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Harald,

HTA> we have been very patient with you, but you are misrepresenting the
HTA> situation.


Both parts of your statement are not only true, but have been true
quite a number of times in the past, with respect to this particular
"claimant".

We have policies for dealing with those who post to IETF mailing lists
contrary to the mailing lists policies.

I think it is time to invoke similar policies for those who abuse IETF
process.

The alternative is acceding to a deprivation of service attack.  IETF
resources are scarce and we need to start acting like we believe it.

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


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


From ietf-bounces@ietf.org  Tue Jun 22 18:39:38 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04887
	for <ietf-archive@ietf.org>; Tue, 22 Jun 2004 18:39:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BctvX-0005T6-VK
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 18:39:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BctuX-000554-00
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 18:38:38 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bcttf-0004Ks-00; Tue, 22 Jun 2004 18:37:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BctkF-0005RL-1F; Tue, 22 Jun 2004 18:27:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcoWi-0005fB-HH
	for ietf@megatron.ietf.org; Tue, 22 Jun 2004 12:53:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23470
	for <ietf@ietf.org>; Tue, 22 Jun 2004 12:53:37 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcoWh-0000Xg-Gz
	for ietf@ietf.org; Tue, 22 Jun 2004 12:53:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcmOS-0000A9-00
	for ietf@ietf.org; Tue, 22 Jun 2004 10:37:01 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12) id 1Bckvr-00057h-00
	for ietf@ietf.org; Tue, 22 Jun 2004 09:03:23 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta5/8.13.0.Beta5) with ESMTP id
	i5M8a13F009172; Tue, 22 Jun 2004 04:36:01 -0400
Message-Id: <200406220836.i5M8a13F009172@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Dean Anderson <dean@av8.com>
In-Reply-To: Your message of "Mon, 21 Jun 2004 18:43:23 EDT."
	<Pine.LNX.4.44.0406211822300.18782-100000@cirrus.av8.net> 
References: <Pine.LNX.4.44.0406211822300.18782-100000@cirrus.av8.net>
Mime-Version: 1.0
Date: Tue, 22 Jun 2004 04:36:01 -0400
Cc: Paul Vixie <vixie@vix.com>, ietf@ietf.org
Subject: Re: Response to complaint from Dean Anderson (fwd) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1102349654=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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.7 required=5.0 tests=AWL,DATE_IN_PAST_03_06,
	NO_REAL_NAME autolearn=no version=2.60

--===============1102349654==
Content-Type: multipart/signed; boundary="==_Exmh_-924798964P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Mon, 21 Jun 2004 18:43:23 EDT, Dean Anderson said:

> Mr. Vixie's obvious malice for Av8 Internet is plain to see, 

As is the fact that the feelings appear to be mutual....

> services to customers.  However, it is unclear what Mr. Vixie's expertise
> is actually in, other than name-calling, and making disparaging
> alterations on another companies trademarks. I have seen little else.

Pot. Kettle. Black.

Dean, if your complaint is that Paul is making "disparaging" comments, you
*really* need to proof-read before you hit send.  Or even better, have somebody
from 2 cubicles/offices/whatever read it and tell you if you're laying it on
too thick.  Or at least take a break - hit the rest room, the vending machines,
whatever, then re-read it before you hit send...

(Hint - no matter *what* your personal opinions of Paul Vixie are, or what
personal, professional, or business animosity there may exist between the two
of you, saying that you're unsure what Paul's expertise is in only manages to
tell the reader that you're either (a) very bitter or (b) just fell out of a
tree and don't know any of your Internet history, or (c) both....)


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

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

iD8DBQFA1+9xcC3lWbTT17ARAjMmAKCtNqJQCdCKETaiuAW+BdMXzs5GpwCg2i7c
WVmeOg5vzadsOkItOy88dJU=
=K2U+
-----END PGP SIGNATURE-----

--==_Exmh_-924798964P--


--===============1102349654==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1102349654==--



From ietf-bounces@ietf.org  Tue Jun 22 19:08:40 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07623
	for <ietf-archive@ietf.org>; Tue, 22 Jun 2004 19:08:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcuNc-0001md-M0
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 19:08:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcuJ7-0000PZ-00
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 19:04:01 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcuHw-0007gc-00; Tue, 22 Jun 2004 19:02:48 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BcuHx-0003lL-5h; Tue, 22 Jun 2004 19:02:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BctmF-0007WU-NJ; Tue, 22 Jun 2004 18:30:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcpkJ-0005HP-3R
	for ietf@megatron.ietf.org; Tue, 22 Jun 2004 14:11:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10438
	for <ietf@ietf.org>; Tue, 22 Jun 2004 14:11:45 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcpkI-0006Tr-3q
	for ietf@ietf.org; Tue, 22 Jun 2004 14:11:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcoyC-0005cW-00
	for ietf@ietf.org; Tue, 22 Jun 2004 13:22:05 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1BcnM5-00073c-00
	for ietf@ietf.org; Tue, 22 Jun 2004 11:38:37 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta5/8.13.0.Beta5) with ESMTP id
	i5MFd3qt014253; Tue, 22 Jun 2004 11:39:04 -0400
Message-Id: <200406221539.i5MFd3qt014253@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-Reply-To: Your message of "Tue, 22 Jun 2004 11:11:25 +0900."
	<40D7954D.4090707@necom830.hpcl.titech.ac.jp> 
References: <Pine.HPX.4.58.0406201546040.12903@wells.cisco.com>
	<OKEPLEIOJKFGFGCKMDKJKEKOCGAA.cdel@firsthand.net>
	<1087829268.8105.185.camel@segesta.zurich.ibm.com>
	<40D75DE6.80106@necom830.hpcl.titech.ac.jp>
	<EF973F96D27E7761FE612D73@scan.jck.com>
	<40D7954D.4090707@necom830.hpcl.titech.ac.jp>
Mime-Version: 1.0
Date: Tue, 22 Jun 2004 11:39:03 -0400
Cc: John C Klensin <john-ietf@jck.com>,
        Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>,
        ietf@ietf.org, Jeroen Massar <jeroen@unfix.org>
Subject: Re: What exactly is an internet (service) provider? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0819867900=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,NO_REAL_NAME autolearn=no 
	version=2.60

--===============0819867900==
Content-Type: multipart/signed; boundary="==_Exmh_1190340P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Tue, 22 Jun 2004 11:11:25 +0900, Masataka Ohta said:
> With your motivation explained and with your three new categories,
> all of which are unrelated to telecommunication providers but
> related to hotels, I think I can understand your fundamental
> mistake.

More generally, Internet access is of 4 basic time-base categories:

1) Access at the location(s) you usually are (home, office, dorm, etc) - these
are "traditional" ISPs.  The timeframe for (business) associations here is "weeks to years".

2) Access when you're semi-stationary while not where you usually are (hotels,
extended stays with friends/relatives, and so on).  Timeframe for associations
is "one to several days".  Note *carefully* that this has some corner-case
implications - if I'm visiting my brother in New England, I'm a semi-long-term
(a week or so) transient on his home Ethernet and thence to his cablemodem
provider, while *he* is a long-term user of the *exact same connection*. As a
result, *his* expectations and *mine* regarding the same service may be quite
different (for example, he may be quite OK with the concept that all SMTP gets
redirected to the provider because he uses their mail relay by default anyhow,
but that may be totally unacceptable to me)....

3) Very short term access while stationary long enough to consume 1 beverage -
the kiosk/cafe model.  Associations on the order of 15 minutes to a very small
number of hours.

4) Roaming access while *not* stationary - citywide wifi networks and the like,
where the timescales are seconds to minutes... 

Note that the types of services provided is generally orthogonal to the timescale
of the business model - a provider can (for instance) provide WebTV-style captive
access at all 4 timescales.  As a result, we probably end up with a 2-D matrix...

> That is, your draft should have been titled:

>	Terminologies on Telecommunication Service Categories of
>	Accomodation Service Providers

> Given that your stay is temporary, permanent addresses are of
> little value. Moreover, as most, if not all, hotels use NAT,
> it is of little value to mention global addresses.

Note that the fact that I'm there for only several days does *not* imply that
permanent (at least for the duration of the stay) addresses are of little
value. Also, note that there's a distinction between "permanent" and "routable"
in this context.  There's a wide range of things where I don't *care* what my
current IP address is as long as it's routable - in those cases, I can easily
deal with a DHCP-assigned routable address, but not with a NAT'ed address,
whether the NAT'ed address is dynamic or static.  I can be 192.168.10.10
from last year till the next Winter Olympics - that address Simply Will Not
Work for many things.

In particular, the fact that most hotels use NAT is quite likely one of the big
stumbling blocks for commercial deployment of any application protocol that has
trouble playing nice with NAT (See Keith Moore's list - all of those are
basically not doable in your organization if you have frequent road warriors
who might be participating from a hotel room).

> So, in the new draft, you should avoid the word "ISP". Instead,
> you can, for example, say ASAP (Application Service Access
> Provider).

Providing a common list of such things is the intent of the draft, I believe.

> Mobile operators in Japan does provide access to web services,
> though not over IP, that they are WSAP. Or, do you like better
> calling them Web Access Service Providers?

Oh my... A can of worms indeed.  John - it's your call if you want to
expand the scope to include that class of access or not....

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

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

iD8DBQFA2FKXcC3lWbTT17ARAu3JAKCRP94nW1B+v6EiCypWCFnjdI+oNACgsPNV
P8eGPsQ2D2/yzVBoKGVf5eA=
=q5Us
-----END PGP SIGNATURE-----

--==_Exmh_1190340P--


--===============0819867900==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0819867900==--



From ietf-bounces@ietf.org  Tue Jun 22 19:35:00 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10860
	for <ietf-archive@ietf.org>; Tue, 22 Jun 2004 19:34:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bcun5-0000rM-WB
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 19:35:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bcud8-0006LM-00
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 19:24:42 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcuXr-0004ln-00; Tue, 22 Jun 2004 19:19:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bctnh-00088p-4x; Tue, 22 Jun 2004 18:31:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcrIr-0005tf-AS
	for ietf@megatron.ietf.org; Tue, 22 Jun 2004 15:51:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23972
	for <ietf@ietf.org>; Tue, 22 Jun 2004 15:51:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcrIq-0004NB-39
	for ietf@ietf.org; Tue, 22 Jun 2004 15:51:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcrHr-00040m-00
	for ietf@ietf.org; Tue, 22 Jun 2004 15:50:32 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12) id 1BcrH0-0003ee-00
	for ietf@ietf.org; Tue, 22 Jun 2004 15:49:39 -0400
Received: (qmail 48415 invoked from network); 22 Jun 2004 19:48:29 -0000
Received: from yahoobb219001188014.bbtec.net (HELO necom830.hpcl.titech.ac.jp)
	(219.1.188.14)
	by necom830.hpcl.titech.ac.jp with SMTP; 22 Jun 2004 19:48:29 -0000
Message-ID: <40D88E7B.8070707@necom830.hpcl.titech.ac.jp>
Date: Wed, 23 Jun 2004 04:54:35 +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: Valdis.Kletnieks@vt.edu
References: <Pine.HPX.4.58.0406201546040.12903@wells.cisco.com>
	<OKEPLEIOJKFGFGCKMDKJKEKOCGAA.cdel@firsthand.net>
	<1087829268.8105.185.camel@segesta.zurich.ibm.com>
	<40D75DE6.80106@necom830.hpcl.titech.ac.jp>
	<EF973F96D27E7761FE612D73@scan.jck.com>
	<40D7954D.4090707@necom830.hpcl.titech.ac.jp>
	<200406221539.i5MFd3qt014253@turing-police.cc.vt.edu>
In-Reply-To: <200406221539.i5MFd3qt014253@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>,
        Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>,
        ietf@ietf.org, Jeroen Massar <jeroen@unfix.org>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Valdis;

>>With your motivation explained and with your three new categories,
>>all of which are unrelated to telecommunication providers but
>>related to hotels, I think I can understand your fundamental
>>mistake.

> More generally, Internet access is of 4 basic time-base categories:

I think the difference is not on time-base but on who has the control
to choose the telecommunication service.

In John's cases seemingly, Hotels has the control.

							Masataka Ohta



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


From ietf-bounces@ietf.org  Tue Jun 22 19:37:06 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11236
	for <ietf-archive@ietf.org>; Tue, 22 Jun 2004 19:37:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bcup7-0001Vn-OU
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 19:37:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bcuf9-0006uz-00
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 19:26:48 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcuYM-0005Em-00; Tue, 22 Jun 2004 19:19:46 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BcuQv-00068B-Lw; Tue, 22 Jun 2004 19:12:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BctnP-00083U-Lt; Tue, 22 Jun 2004 18:31:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcqIm-0002ml-Nd
	for ietf@megatron.ietf.org; Tue, 22 Jun 2004 14:47:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16857
	for <ietf@ietf.org>; Tue, 22 Jun 2004 14:47:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcqIl-00053l-DH
	for ietf@ietf.org; Tue, 22 Jun 2004 14:47:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bcq3a-000299-00
	for ietf@ietf.org; Tue, 22 Jun 2004 14:31:43 -0400
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12) id 1BcpbK-0004z1-00
	for ietf@ietf.org; Tue, 22 Jun 2004 14:02:30 -0400
Received: (qmail 7425 invoked by uid 1013); 22 Jun 2004 18:02:29 -0000
Date: Tue, 22 Jun 2004 20:02:29 +0200
From: Markus Stumpf <maex-lists-ietf-general@Space.Net>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-ID: <20040622180229.GJ22050@Space.Net>
References: <20040621193003.GH89866@Space.Net>
	<200406212116.i5LLGPTq048197@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200406212116.i5LLGPTq048197@calcite.rhyolite.com>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Mon, Jun 21, 2004 at 03:16:25PM -0600, Vernon Schryver wrote:
> Sue on what grounds?  Who says that Internet service has no limits?

If there are limits they'd have to be in the contract.

> All reputable service providers have terms of service that include
> limits, starting with something about network abuse.

Hmmm ... we have no limits and we have no AUP that forbids anything.
We sell Internet access, just like a car company sells cars. The car
company doesn't have a passus "you are not allowed to cross red lights"
because they neither have the possibility nor the legal authority to
enforce such a passus and we don't have "you are not allowed to hack
other computers". However law in Germany gives us the possibility
to terminate such an account at any time, as hacking is not allowed
and if we know about it we have to take appropiate actions to stop
illegal behaviour.

We have DSL accounts for "private use" on dynamic address space
with a disconnect every 24 hours (policy of our "DSL carrier") and
we have DSL accounts for "business use" that can have a static IP
address and that don't have disconnections (most of them on SDSL).

We're currently thinking about a port 25 outgoing block for "private
use" DSL accounts, but this will be a clear passus in the contract
and also be listed in the product description.

> (Never mind 
> how well those limits are enforced.)  Many service providers limit
> their users to not running "servers," but good luck finding someone
> who knows what they mean by "server." 

If you want to buy a car and ask if it has air bags and nobody can
give you a definite answer, would you buy the car if it is important to
you to have an air bag?
If the ISP can't answer the question about improtant product details,
why do you sign a contract with that provider? Because he is cheaper
than others? Now what would most probably be the reason?

> Since there are always providers, you can't sue simply because you
> bought an account with limits you failed to clarify.

This is the important part: "you failed to clarify".

> Trying to find first line technical support people (never mind sales)
> at a consumer grade ISP who knows has any idea what sort of filtering
> their employer does is hopeless.  It's generally foolish to expect to
> find someone who even understands the question.

Maybe you didn't look hard enough? ;-)

> I've not seen anyone selling "DSL Surf Accounts," but I've never looked,
> and certainly not in Germany.
> In any case, 
>   - which of the classes in 
> http://www.ietf.org/internet-drafts/draft-klensin-ip-service-terms-02.txt
>     is closest to a "DSL Surf Accounts"?

It is probably something like "Web connectivity" or "Client connectivity
only", but I find the terms in the draft *very* fuzzy and overlapping.
And no I haven't yet thought about it long enough to make suggestions ;-)

In general I support all what you said to some extent.

But there are always tradeoffs if you get your DSL access from a "big
player" who may be a bit cheaper vs. access from a smaller ISP that
may be a bit more expensive but may provide a lot more service and
support.

	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"

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


From ietf-bounces@ietf.org  Tue Jun 22 19:38:37 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11584
	for <ietf-archive@ietf.org>; Tue, 22 Jun 2004 19:38:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bcuqa-0001nF-UW
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 19:38:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bcugd-0007E2-00
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 19:28:21 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcuYb-0005HN-00; Tue, 22 Jun 2004 19:20:01 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BcuM5-0004wo-UE; Tue, 22 Jun 2004 19:07:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bctmi-0007s3-4A; Tue, 22 Jun 2004 18:30:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bcpx0-0007Uf-9M
	for ietf@megatron.ietf.org; Tue, 22 Jun 2004 14:24:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12588
	for <ietf@ietf.org>; Tue, 22 Jun 2004 14:24:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bcpwz-0000vA-2N
	for ietf@ietf.org; Tue, 22 Jun 2004 14:24:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcpRT-00034m-00
	for ietf@ietf.org; Tue, 22 Jun 2004 13:52:20 -0400
Received: from mail9.atl.registeredsite.com ([64.224.219.83] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12) id 1BcoDX-0005Th-00
	for ietf@ietf.org; Tue, 22 Jun 2004 12:33:51 -0400
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail9.atl.registeredsite.com (8.12.11/8.12.8) with ESMTP id
	i5MGXdCN016647; Tue, 22 Jun 2004 16:33:40 GMT
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ;
	Tue, 22 Jun 2004 11:33:38 -0500
Message-ID: <40D85F54.2050606@nma.com>
Date: Tue, 22 Jun 2004 09:33:24 -0700
From: Ed Gerck <egerck@nma.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sommerfeld@orchard.arlington.ma.us, "ietf@ietf.org" <ietf@ietf.org>
References: <20040622022210.060F617921@portal.hamachi.org>
In-Reply-To: <20040622022210.060F617921@portal.hamachi.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: Re: non-solution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



Bill Sommerfeld wrote:

>>The solution to this self-limitation problem [1], if the Internet MUST be
>>the only communication path used by someone, is to use IETF web forms
>>that go directly to the server. 
> 
> 
> It's not a solution.  For one, spammers, not content to ruin email,
> have been abusing web forms for quite some time; spam filters will be
> required there, as well.

The server can filter as the IETF wishes (or dare) but there would be no
problems with black-lists and mail routing affecting the message being
RECEIVED by the IETF -- which is the point in question.



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


From ietf-bounces@ietf.org  Tue Jun 22 21:34:16 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22391
	for <ietf-archive@ietf.org>; Tue, 22 Jun 2004 21:34:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BcweX-0006WX-8V
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 21:34:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bcvrx-0006LT-00
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 20:44:06 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcvNA-0000v8-00; Tue, 22 Jun 2004 20:12:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bctoi-0008Jp-Bs; Tue, 22 Jun 2004 18:32:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BcrQV-0006qi-J0
	for ietf@megatron.ietf.org; Tue, 22 Jun 2004 15:59:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24592
	for <ietf@ietf.org>; Tue, 22 Jun 2004 15:59:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BcrQU-0007Po-AF
	for ietf@ietf.org; Tue, 22 Jun 2004 15:59:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcrPW-00071o-00
	for ietf@ietf.org; Tue, 22 Jun 2004 15:58:26 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BcrOf-0006IO-00
	for ietf@ietf.org; Tue, 22 Jun 2004 15:57:33 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i5MJv2T5035993
	for ietf@ietf.org env-from <vjs>;
	Tue, 22 Jun 2004 13:57:02 -0600 (MDT)
Date: Tue, 22 Jun 2004 13:57:02 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200406221957.i5MJv2T5035993@calcite.rhyolite.com>
To: ietf@ietf.org
References: <20040622180229.GJ22050@Space.Net>
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> From: Markus Stumpf <maex-lists-ietf-general@Space.Net>


> If you want to buy a car and ask if it has air bags and nobody can
> give you a definite answer, would you buy the car if it is important to
> you to have an air bag?

Buging a car with a feature with well defined characteristics is quite
different from buying Internet services which don't even have common
names.  Air bags, at least in the U.S., must do exactly what they do
even if that is known to kill people who are short.  Your "private
use" Internet service is basically whatever you feel like selling.
That you apparently call it "private use" instead of one of the more
common names is yet another symptom of the problem.


> If the ISP can't answer the question about improtant product details,
> why do you sign a contract with that provider? Because he is cheaper
> than others? Now what would most probably be the reason?

I'm in the insignificant minority that can ask the right questions
about IP service and recognize when I'm not getting answers, but I can
neither ask good questions about air bags, nor recognize nonsense
answers.  I don't know much about air bags except that they are bombs
in bags, which is as much as most sales people.  Still, I can buy a
car with an air bag and know I'm getting something that might do some
good (unless I'm short or sit too far forward) and meets a standard.
Without the standardization of "air bag," I could not.

We have a classic standardization problem that is affecting
interoperability.  The market has gotten ahead of the IETF and is
buying and selling a many quite different things all called "Internet
service."   It is more the job of the IETF to define standards
including a taxomony in this area than to define yet another MIB.

It is not the job of the IETF to try to stop anyone from selling
services that differ from what we used to get via NSF any more than
it is the job of the IETF to prevent the sales of NAT boxes and PPPoE,
no matter how nasty and evil NAT, PPPoE, and slum IP services are.  It
is right, proper, and necessary that the IETF has NAT and PPPoE
standards.  We should also have standards for your "private use Internet
service" as distinct from the services I bought 20 years ago, even if
you agree with me that "slum IP service sold by virtual slumlords to
fools" is as accurate and more clear than "client only, private address."



> > Since there are always providers, you can't sue simply because you
> > bought an account with limits you failed to clarify.
>
> This is the important part: "you failed to clarify".

Unless you are among the insignificant minority who knows the difference
between an ICMP Port-Unreachable and an ICMP Administrative-Prohibited,
you are incapable of clarifying.  Worse, unless you know more than all
available employees at many Internet services providers, you are
incapable of knowing whether you're being told nonsense.

Standards for the various flavors of "Internet service" would solve
those problems for both users and service providers.


> >   - which of the classes in 
> > http://www.ietf.org/internet-drafts/draft-klensin-ip-service-terms-02.txt
> >     is closest to a "DSL Surf Accounts"?
>
> It is probably something like "Web connectivity" or "Client connectivity
> only", but I find the terms in the draft *very* fuzzy and overlapping.
> And no I haven't yet thought about it long enough to make suggestions ;-)

What about adding explicit lists of the packets that are (not) filtered,
frequency of DHCP reassignment, DSL PPP disconnections, and whatever?

The draft currently gives the equivalents of "driver's side", "passenger,"
"side impact air bags," for consumers but does not include the technical
stuff equivalent to the rules for air bags.  Something like the "Client
connectivity only" now in the draft is needed by consumers and front
line technical support people, but it is not sufficent for a provider
(or a government) to determine compliance.

Maybe this needs a WG.


> In general I support all what you said to some extent.

In that case it would be nice if you would not write as if you vehimently
opposed the notion of standardizing terms for classes or kinds of
Internet service.  Except for that single sentence, I have the impression
that you agree with the individual from Japan that the whole idea of
the draft is entirely wrong and destructive.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Tue Jun 22 21:36:32 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22978
	for <ietf-archive@ietf.org>; Tue, 22 Jun 2004 21:36:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bcwgi-0006wk-LM
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 21:36:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bcvvy-00070Y-00
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 20:48:14 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BcvRy-0001kM-00; Tue, 22 Jun 2004 20:17:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bctoo-0008My-A8; Tue, 22 Jun 2004 18:32:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bcrpg-0001V7-1s
	for ietf@megatron.ietf.org; Tue, 22 Jun 2004 16:25:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26056
	for <ietf@ietf.org>; Tue, 22 Jun 2004 16:25:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bcrpe-0001bX-Id
	for ietf@ietf.org; Tue, 22 Jun 2004 16:25:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bcrof-0001Eo-00
	for ietf@ietf.org; Tue, 22 Jun 2004 16:24:26 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12) id 1Bcrni-0000Wd-00
	for ietf@ietf.org; Tue, 22 Jun 2004 16:23:26 -0400
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 i5MKMnaO010711
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 22 Jun 2004 16:22:51 -0400
Date: Tue, 22 Jun 2004 16:22:49 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Valdis.Kletnieks@vt.edu
In-Reply-To: <200406220836.i5M8a13F009172@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0406221441330.8624-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Paul Vixie <vixie@vix.com>, ietf@ietf.org
Subject: Re: Response to complaint from Dean Anderson (fwd) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Tue, 22 Jun 2004 Valdis.Kletnieks@vt.edu wrote:

> On Mon, 21 Jun 2004 18:43:23 EDT, Dean Anderson said:
> 
> > Mr. Vixie's obvious malice for Av8 Internet is plain to see, 
> 
> As is the fact that the feelings appear to be mutual....

One never appreciates being publicly disparaged, defamed, or harrassed,
but it is incorrect to assume that just because I have been attacked, that
I harbor malice for that person. Rather, I feel sorry for someone who is
presumably in his 40's and resorts to name-calling.  Such unsocialization
or immaturity must be debilitating.  I pray for them.  This does not mean
that I will silently accept such treatment, nor does it mean I will not
assert my rights and privileges to object to such treatment.

Besids Mr. Vixie's on-list comments, there is his involvement in the
defamatory and misleading statements about Av8 Internet's IP address
space. Long ago, and for other reasons, I came to believe that defamation
results in a short term loss for the defamed and a short term gain for the
defamer, but a long term gain for the defamed and a long term loss for the
defamer.  Lies are always exposed as lies and liars are always exposed as
liars.  This is particularly appropriate as the UN meets today to discuss
anti-semitism, which is also spread by defamation.  The defamed may be
saddened and harmed while being defamed, but have solace in the fact that
history will eventually right the wrong: It always has. It always will.  
This doesn't mean one should be complacent.  Everyone should stand up to 
stop defamation.

I have made efforts to make my criticisms professional and accurate, and
not to allow myself to degenerate into name-calling. Persons who behave
badly and call other people names deserve criticism.  While everyone may
be fallible from time to time in overheated discussion, some people seem
to have no control or compuction whatsoever.  I have tried to make sure
that my criticisms meet the standard of cool and detached professionalism.
Mr. Vixie's comments ("loons", "trolls", "dv8", "least technical person on
the list" do not meet that standard.

But I note that you have not amoung those who have posted messages calling
for Mr. Vixie to "take a break" before calling other people names.  Is it
that you have become accustomed to his behavior or do you hold me to a
different standard?

> > services to customers.  However, it is unclear what Mr. Vixie's expertise
> > is actually in, other than name-calling, and making disparaging
> > alterations on another companies trademarks. I have seen little else.
> 
> Pot. Kettle. Black.

Not exactly.  Questioning someone's expertise is quite a bit different
than declaring someone else to be "the least technical person on the
list".  I did the former, Mr. Vixie did the latter.  The former is
reasonable and appropriate, the latter isn't.

Questioning Mr. Vixie's expertise is not unreasonable nor inappropriate in
the light of his last several disparaging remarks not only about myself
and subsequently my company, and also Mr. Vixies inappropriate
name-calling of other people. I note that the Chair has also failed to
chastise these other inappropriate comments by Mr. Vixie.

I am aware of Mr. Vixie's past involvement in DNS and his operation of a
Root nameserver, yet just recently he diverted attention from genuine
questions raised by several people about Root Anycast to a personal attack
on several of the participants.  This does not seem to be appropriate for
a trusted person in DNS or Root server operations, and leads to questions
about professionalism, responsibility, maturity, and and ultimately, trust
in his expertise in that area.  The name-calling raises further questions
about whether we can trust Mr. Vixie's assurances. This is also not a
personal attack: Such questions are valid, have been raised by several
people, and have gone unanswered except for name-calling.


Dean Anderson
Av8 Internet, Inc


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

Date: 19 May 2004 22:16:36 +0000
From: Paul Vixie <vixie@vix.com>
To: ietf@ietf.org
Subject: Re: Root Anycast

there are two things that i think it's important that everybody 
understand.

first, anyone who posts from roll accounts like "info@utel.net (jfcm)"
tends to be dismissed as a troll.

second, anyone who seriously uses the term "legacy DNS root" tends to be
dismissed as a loon.

i now return control of your television set to the loons and trolls...
-- 
Paul Vixie





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


From ietf-bounces@ietf.org  Wed Jun 23 02:07:40 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13236
	for <ietf-archive@ietf.org>; Wed, 23 Jun 2004 02:07:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bd0v6-0003A3-9S
	for ietf-archive@ietf.org; Wed, 23 Jun 2004 02:07:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bcxk0-0006tE-00
	for ietf-archive@ietf.org; Tue, 22 Jun 2004 22:44:01 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bcw8N-0001po-00; Tue, 22 Jun 2004 21:01:03 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Bcw8N-0008SA-Ri; Tue, 22 Jun 2004 21:01:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bcvsm-0001G4-9j; Tue, 22 Jun 2004 20:44:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bcv8E-0004sJ-Oc
	for ietf@megatron.ietf.org; Tue, 22 Jun 2004 19:56:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13732
	for <ietf@ietf.org>; Tue, 22 Jun 2004 19:56:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bcv8D-0005Z4-8L
	for ietf@ietf.org; Tue, 22 Jun 2004 19:56:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcuwD-0002yT-00
	for ietf@ietf.org; Tue, 22 Jun 2004 19:44:26 -0400
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx with esmtp (Exim 4.12) id 1BcumG-0000gX-00
	for ietf@ietf.org; Tue, 22 Jun 2004 19:34:08 -0400
Received: from portal (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id 0E70817921; Tue, 22 Jun 2004 19:34:02 -0400 (EDT)
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: Ed Gerck <egerck@nma.com>
In-Reply-To: Message from Ed Gerck <egerck@nma.com> 
	of "Tue, 22 Jun 2004 09:33:24 PDT." <40D85F54.2050606@nma.com> 
Date: Tue, 22 Jun 2004 19:34:02 -0400
Message-Id: <20040622233402.0E70817921@portal.hamachi.org>
Cc: sommerfeld@orchard.arlington.ma.us, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: non-solution 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sommerfeld@orchard.arlington.ma.us
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> The server can filter as the IETF wishes (or dare) but there would be no
> problems with black-lists and mail routing affecting the message being
> RECEIVED by the IETF -- which is the point in question.

If a message is blocked by a filter without making a sound, is it
actually received?

							- Bill



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


From ietf-bounces@ietf.org  Wed Jun 23 04:23:21 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05169
	for <ietf-archive@ietf.org>; Wed, 23 Jun 2004 04:23:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bd32P-0004On-Oa
	for ietf-archive@ietf.org; Wed, 23 Jun 2004 04:23:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bd2s2-000268-00
	for ietf-archive@ietf.org; Wed, 23 Jun 2004 04:12:39 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bd2aS-0006X5-00; Wed, 23 Jun 2004 03:54:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bd2Tu-00085O-8q; Wed, 23 Jun 2004 03:47:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bd0wy-0002Mj-28
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 02:09:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15032
	for <ietf@ietf.org>; Wed, 23 Jun 2004 02:09:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bd0wv-0003VM-PA
	for ietf@ietf.org; Wed, 23 Jun 2004 02:09:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcxoG-0007Y2-00
	for ietf@ietf.org; Tue, 22 Jun 2004 22:48:25 -0400
Received: from mail1.atl.registeredsite.com ([64.224.219.75] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12) id 1BcwDg-0002Ob-00
	for ietf@ietf.org; Tue, 22 Jun 2004 21:06:32 -0400
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail1.atl.registeredsite.com (8.12.11/8.12.8) with ESMTP id
	i5N16XKB005365; Wed, 23 Jun 2004 01:06:33 GMT
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ;
	Tue, 22 Jun 2004 20:06:31 -0500
Message-ID: <40D8D797.7070203@nma.com>
Date: Tue, 22 Jun 2004 18:06:31 -0700
From: Ed Gerck <egerck@nma.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sommerfeld@orchard.arlington.ma.us
References: <20040622233402.0E70817921@portal.hamachi.org>
In-Reply-To: <20040622233402.0E70817921@portal.hamachi.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: non-solution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



Bill Sommerfeld wrote:

>>The server can filter as the IETF wishes (or dare) but there would be no
>>problems with black-lists and mail routing affecting the message being
>>RECEIVED by the IETF -- which is the point in question.
> 
> 
> If a message is blocked by a filter without making a sound, is it
> actually received?

Cute ...this is not a quantum problem. If the filter is after the
server providing the form page and the SUBMIT button, yes, the
server received the message. IETF can have a log file before the
filter (SOP), allowing review of what is filtered.

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


From ietf-bounces@ietf.org  Wed Jun 23 13:38:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17352
	for <ietf-archive@ietf.org>; Wed, 23 Jun 2004 13:38:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdBhx-0002za-TM
	for ietf-archive@ietf.org; Wed, 23 Jun 2004 13:38:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdAMn-00013d-00
	for ietf-archive@ietf.org; Wed, 23 Jun 2004 12:12:55 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bd9Sk-0001Pu-00; Wed, 23 Jun 2004 11:14:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bd9M8-0002aq-20; Wed, 23 Jun 2004 11:08:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bd1Ft-0002e3-Dv
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 02:29:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04999
	for <ietf@ietf.org>; Wed, 23 Jun 2004 02:29:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bd1Fq-0006uC-EG
	for ietf@ietf.org; Wed, 23 Jun 2004 02:29:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BcyfN-0004ND-00
	for ietf@ietf.org; Tue, 22 Jun 2004 23:43:18 -0400
Received: from mynah.mail.pas.earthlink.net ([207.217.120.228])
	by ietf-mx with esmtp (Exim 4.12) id 1BcwVu-0004xX-00
	for ietf@ietf.org; Tue, 22 Jun 2004 21:25:22 -0400
Received: from 68-232-135-218.chvlva.adelphia.net ([68.232.135.218]
	helo=CHERYL) by mynah.mail.pas.earthlink.net with asmtp (Exim 4.34)
	id 1BcwVG-0006YY-EV
	for ietf@ietf.org; Tue, 22 Jun 2004 18:24:42 -0700
Date: Tue, 22 Jun 2004 21:24:40 -0400
From: Gene Gaines <gene.gaines@gainesgroup.com>
Organization: Gaines Group
X-Priority: 3 (Normal)
Message-ID: <1798970594.20040622212440@gainesgroup.com>
To: ietf@ietf.org
In-Reply-To: <Pine.LNX.4.44.0406221441330.8624-100000@cirrus.av8.net>
References: <200406220836.i5M8a13F009172@turing-police.cc.vt.edu>
	<Pine.LNX.4.44.0406221441330.8624-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: e892362a6fa8b5d372cc1e1b0924a179239a348a220c260919cd3d4a40cfa06cb1c9a377ef9ee307a7ce0e8f8d31aa3f350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.232.135.218
Content-Transfer-Encoding: 7bit
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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.8 required=5.0 tests=PRIORITY_NO_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

Enough.

The Dean Anderson fiasco has continued long enough.

This is a formal request that Anderson be asked to
cease the off-topic diatribes about a problem that
I view as of his own making.

The IETF should have no legal or moral obligation
to accede to his demands, nor should any individual
associated with IETF activities.

His negative diatribes and threats do damage to the
IETF.  It is important he cease or be banned from
IETF lists.

I have not met Mr. Anderson, but remember him quite
well from past correspondence lists such as:

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

 To: Yakov Shafranovich <research@solidmatrix.com>
 Subject: Re: Fwd: ICANN asks Verisign to shutdown SiteFinder
          in 48 hours
 From: Dean Anderson <dean@av8.com>
 Date: Fri, 3 Oct 2003 17:12:02 -0400 (EDT)
 Cc: ietf@ietf.org
 In-reply-to: <3F7DA063.6020409@solidmatrix.com>
 Sender: owner-ietf@ietf.org

I see that Verisign is complying while they "review their
options".

Well, hopefully they are having their lawyers go over their
contracts to see if ICANN can claim it is in breach of any
contract. It would seem that they can't, having not complained
about other registries, and having not substantiated any adverse
effects to the internet. It will take some time to go through
each claim and offer a substantial proof that it is wrong. It
will be interesting to see what the lawyers say.

It was really to bad that they gave the "angry scientists and
engineers" as much credit as they did. This angry group is
basically the same bunch of Verisign bashers that have been
whining about Verisign or Network Solutions for many years, when
there are other registries that are much more deserving of
criticism. Calling them scientists and engineers gives too much
credit because real scientists and engineers deal in facts. I
would use another term.

I for one hope that SiteFinder will come back, and I wish
Verisign good luck.

               --Dean

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

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

On Tuesday, June 22, 2004, 4:22:49 PM, Dean wrote:

> On Tue, 22 Jun 2004 Valdis.Kletnieks@vt.edu wrote:

>> On Mon, 21 Jun 2004 18:43:23 EDT, Dean Anderson said:
>> 
>> > Mr. Vixie's obvious malice for Av8 Internet is plain to see,
>> 
>> As is the fact that the feelings appear to be mutual....

> One never appreciates being publicly disparaged, defamed, or harrassed,
> but it is incorrect to assume that just because I have been attacked, that
> I harbor malice for that person. Rather, I feel sorry for someone who is
> presumably in his 40's and resorts to name-calling.  Such unsocialization
> or immaturity must be debilitating.  I pray for them.  This does not mean
> that I will silently accept such treatment, nor does it mean I will not
> assert my rights and privileges to object to such treatment.

> Besids Mr. Vixie's on-list comments, there is his involvement in the
> defamatory and misleading statements about Av8 Internet's IP address
> space. Long ago, and for other reasons, I came to believe that defamation
> results in a short term loss for the defamed and a short term gain for the
> defamer, but a long term gain for the defamed and a long term loss for the
> defamer.  Lies are always exposed as lies and liars are always exposed as
> liars.  This is particularly appropriate as the UN meets today to discuss
> anti-semitism, which is also spread by defamation.  The defamed may be
> saddened and harmed while being defamed, but have solace in the fact that
> history will eventually right the wrong: It always has. It always will.
> This doesn't mean one should be complacent.  Everyone should stand up to
> stop defamation.

> I have made efforts to make my criticisms professional and accurate, and
> not to allow myself to degenerate into name-calling. Persons who behave
> badly and call other people names deserve criticism.  While everyone may
> be fallible from time to time in overheated discussion, some people seem
> to have no control or compuction whatsoever.  I have tried to make sure
> that my criticisms meet the standard of cool and detached professionalism.
> Mr. Vixie's comments ("loons", "trolls", "dv8", "least technical person on
> the list" do not meet that standard.

> But I note that you have not amoung those who have posted messages calling
> for Mr. Vixie to "take a break" before calling other people names.  Is it
> that you have become accustomed to his behavior or do you hold me to a
> different standard?

>> > services to customers.  However, it is unclear what Mr. Vixie's expertise
>> > is actually in, other than name-calling, and making disparaging
>> > alterations on another companies trademarks. I have seen little else.
>> 
>> Pot. Kettle. Black.

> Not exactly.  Questioning someone's expertise is quite a bit different
> than declaring someone else to be "the least technical person on the
> list".  I did the former, Mr. Vixie did the latter.  The former is
> reasonable and appropriate, the latter isn't.

> Questioning Mr. Vixie's expertise is not unreasonable nor inappropriate in
> the light of his last several disparaging remarks not only about myself
> and subsequently my company, and also Mr. Vixies inappropriate
> name-calling of other people. I note that the Chair has also failed to
> chastise these other inappropriate comments by Mr. Vixie.

> I am aware of Mr. Vixie's past involvement in DNS and his operation of a
> Root nameserver, yet just recently he diverted attention from genuine
> questions raised by several people about Root Anycast to a personal attack
> on several of the participants.  This does not seem to be appropriate for
> a trusted person in DNS or Root server operations, and leads to questions
> about professionalism, responsibility, maturity, and and ultimately, trust
> in his expertise in that area.  The name-calling raises further questions
> about whether we can trust Mr. Vixie's assurances. This is also not a
> personal attack: Such questions are valid, have been raised by several
> people, and have gone unanswered except for name-calling.


> Dean Anderson
> Av8 Internet, Inc


> ===================

> Date: 19 May 2004 22:16:36 +0000
> From: Paul Vixie <vixie@vix.com>
> To: ietf@ietf.org
> Subject: Re: Root Anycast

> there are two things that i think it's important that everybody
> understand.

> first, anyone who posts from roll accounts like "info@utel.net (jfcm)"
> tends to be dismissed as a troll.

> second, anyone who seriously uses the term "legacy DNS root" tends to be
> dismissed as a loon.

> i now return control of your television set to the loons and trolls...


-- 


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


From ietf-bounces@ietf.org  Wed Jun 23 14:28:16 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29471
	for <ietf-archive@ietf.org>; Wed, 23 Jun 2004 14:28:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdCTo-0004UJ-Oy
	for ietf-archive@ietf.org; Wed, 23 Jun 2004 14:28:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdCAm-0000gy-00
	for ietf-archive@ietf.org; Wed, 23 Jun 2004 14:08:37 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdBRk-0000J7-00; Wed, 23 Jun 2004 13:22:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdBOX-00012O-Jy; Wed, 23 Jun 2004 13:18:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bd1VK-00013L-NH
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 02:45:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14381
	for <ietf@ietf.org>; Wed, 23 Jun 2004 02:45:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bd1VI-0001oM-GA
	for ietf@ietf.org; Wed, 23 Jun 2004 02:45:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BczIM-0000F8-00
	for ietf@ietf.org; Wed, 23 Jun 2004 00:23:35 -0400
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx with esmtp (Exim 4.12) id 1Bcwj6-0007ec-00
	for ietf@ietf.org; Tue, 22 Jun 2004 21:39:00 -0400
Received: from portal (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id DB24F17921; Tue, 22 Jun 2004 21:39:00 -0400 (EDT)
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: Ed Gerck <egerck@nma.com>
In-Reply-To: Message from Ed Gerck <egerck@nma.com> 
	of "Tue, 22 Jun 2004 18:06:31 PDT." <40D8D797.7070203@nma.com> 
Date: Tue, 22 Jun 2004 21:39:00 -0400
Message-Id: <20040623013900.DB24F17921@portal.hamachi.org>
Cc: sommerfeld@orchard.arlington.ma.us, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: non-solution 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sommerfeld@orchard.arlington.ma.us
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> If the filter is after the
> server providing the form page and the SUBMIT button, yes, the
> server received the message. IETF can have a log file before the
> filter (SOP), allowing review of what is filtered.

Substantially similar capabilities are present in all of the SMTP
MTA's I'm familiar with.  If a message delivery attempt is rejected
early, only envelope information is logged, but if the message was
rejected in error, that's generally sufficient to identify what needs
to be whitelisted.

						- Bill

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


From ietf-bounces@ietf.org  Wed Jun 23 14:35:43 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01286
	for <ietf-archive@ietf.org>; Wed, 23 Jun 2004 14:35:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdCb1-0006TC-Sf
	for ietf-archive@ietf.org; Wed, 23 Jun 2004 14:35:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdCSU-0004G0-00
	for ietf-archive@ietf.org; Wed, 23 Jun 2004 14:26:55 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdC8z-0000J0-00; Wed, 23 Jun 2004 14:06:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdC5W-0002yl-9d; Wed, 23 Jun 2004 14:03:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bd1ad-00034a-LP
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 02:50:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15680
	for <ietf@ietf.org>; Wed, 23 Jun 2004 02:50:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bd1aa-0003K4-Rz
	for ietf@ietf.org; Wed, 23 Jun 2004 02:50:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BczVu-00021g-00
	for ietf@ietf.org; Wed, 23 Jun 2004 00:37:35 -0400
Received: from maxwell.derobert.net ([207.188.193.82])
	by ietf-mx with esmtp (Exim 4.12) id 1Bcwpc-0000tQ-00
	for ietf@ietf.org; Tue, 22 Jun 2004 21:45:44 -0400
Received: from anthony by Maxwell.derobert.net with local (Exim 3.35 #1
	(Debian)) id 1BcwpQ-0000IL-00; Tue, 22 Jun 2004 21:45:32 -0400
Date: Tue, 22 Jun 2004 21:45:32 -0400
Message-ID: <20040623014532.GB339@derobert.net>
References: <Pine.LNX.4.44.0406211814230.18782-100000@cirrus.av8.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0406211814230.18782-100000@cirrus.av8.net>
User-Agent: Mutt/1.3.28i
From: Anthony DeRobertis <anthony@derobert.net>
Cc: Harald Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: Additional complaint about disparagement by Paul Vixie on IETF
	lists
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Mon, Jun 21, 2004 at 06:21:53PM -0400, Dean Anderson wrote:
> 
> Harald, Please add __Another__ complaint to the chair about inappropriate
> behavior by Mr. Vixie.  Altering our name from Av8 Internet to "dv8" is 
> simply more disparagement

I don't see how "dv8" is disparaging in any way. If that is an attempt
to disparage AV8, then it's a very, very poor attempt. More likely, I
suspect, is that its a mistake.

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


From ietf-bounces@ietf.org  Wed Jun 23 15:21:01 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08311
	for <ietf-archive@ietf.org>; Wed, 23 Jun 2004 15:21:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdDIs-0006fy-Ec
	for ietf-archive@ietf.org; Wed, 23 Jun 2004 15:21:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdDI0-0006IC-00
	for ietf-archive@ietf.org; Wed, 23 Jun 2004 15:20:09 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdDHS-0005ta-00; Wed, 23 Jun 2004 15:19:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdDAz-0003IH-QK; Wed, 23 Jun 2004 15:12:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bcpdq-0004QZ-LA
	for ietf@megatron.ietf.org; Tue, 22 Jun 2004 14:05:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09618
	for <ietf@ietf.org>; Tue, 22 Jun 2004 14:05:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bcpdp-0005O5-3o
	for ietf@ietf.org; Tue, 22 Jun 2004 14:05:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bcoiv-0002kn-00
	for ietf@ietf.org; Tue, 22 Jun 2004 13:06:18 -0400
Received: from maxwell.derobert.net ([207.188.193.82])
	by ietf-mx with esmtp (Exim 4.12) id 1BcmmJ-0002lU-00
	for ietf@ietf.org; Tue, 22 Jun 2004 11:01:39 -0400
Received: from anthony by Maxwell.derobert.net with local (Exim 3.35 #1
	(Debian)) id 1BcmmE-0002aN-00; Tue, 22 Jun 2004 11:01:34 -0400
Date: Tue, 22 Jun 2004 11:01:34 -0400
To: Dean Anderson <dean@av8.com>
Message-ID: <20040622150134.GC8752@derobert.net>
References: <043e01c455a5$0e0770f0$6401a8c0@stephen>
	<Pine.LNX.4.44.0406191351560.18161-100000@cirrus.av8.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0406191351560.18161-100000@cirrus.av8.net>
User-Agent: Mutt/1.3.28i
From: Anthony DeRobertis <anthony@derobert.net>
X-Mailman-Approved-At: Wed, 23 Jun 2004 11:13:03 -0400
Cc: Internet Engineering Task Force <ietf@ietf.org>
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Sun, Jun 20, 2004 at 11:11:32PM -0400, Dean Anderson wrote:
> [* Yes there are still reasons to run open relays---Indeed, our SMTP AUTH
> relay is the least used: a commercial failure, really, but I use Pine
> which is one of the few clients that can support SMTP AUTH. 

On a random technical point, this isn't true. At least not any longer.
Most commonly used mailers now support SMTP Auth, including Outlook,
Mozilla/Thunderbird, Apple Mail, mutt, pine, etc.

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


From ietf-bounces@ietf.org  Wed Jun 23 15:26:59 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09032
	for <ietf-archive@ietf.org>; Wed, 23 Jun 2004 15:26:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdDOe-0001Mp-93
	for ietf-archive@ietf.org; Wed, 23 Jun 2004 15:27:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdDNo-0000zT-00
	for ietf-archive@ietf.org; Wed, 23 Jun 2004 15:26:09 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdDNJ-0000bU-00; Wed, 23 Jun 2004 15:25:37 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BdDNJ-0001Hn-Pa; Wed, 23 Jun 2004 15:25:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdDDf-0006KB-E4; Wed, 23 Jun 2004 15:15:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bd1nN-0006UT-UO
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 03:03:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18277
	for <ietf@ietf.org>; Wed, 23 Jun 2004 03:03:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bd1nL-0005PA-HK
	for ietf@ietf.org; Wed, 23 Jun 2004 03:03:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BczwL-0004Nc-00
	for ietf@ietf.org; Wed, 23 Jun 2004 01:04:55 -0400
Received: from mail7.atl.registeredsite.com ([64.224.219.81] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12) id 1BcwyY-0001ss-00
	for ietf@ietf.org; Tue, 22 Jun 2004 21:54:58 -0400
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail7.atl.registeredsite.com (8.12.11/8.12.8) with ESMTP id
	i5N1swjt012273; Wed, 23 Jun 2004 01:54:58 GMT
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ;
	Tue, 22 Jun 2004 20:54:57 -0500
Message-ID: <40D8E2F0.3090606@nma.com>
Date: Tue, 22 Jun 2004 18:54:56 -0700
From: Ed Gerck <egerck@nma.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sommerfeld@orchard.arlington.ma.us
References: <20040623013900.DB24F17921@portal.hamachi.org>
In-Reply-To: <20040623013900.DB24F17921@portal.hamachi.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: non-solution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



Bill Sommerfeld wrote:

>>If the filter is after the
>>server providing the form page and the SUBMIT button, yes, the
>>server received the message. IETF can have a log file before the
>>filter (SOP), allowing review of what is filtered.
> 
> 
> Substantially similar capabilities are present in all of the SMTP
> MTA's I'm familiar with.  

The problem, as has been (too) extensively discussed here, is that
blacklists and other routing restrictions prevent the email from ever
reaching the desired user's MTA (not to mention the user's MUA).

What I suggested is a web interface to the IETF mailboxes, such that
any routing problems TO those mailboxes would cease to be an issue,
allowing the IETF to be in FULL CONTROL of what is forwared to a
mailbox, or not.

Of course, I still believe that insisting in only using the email
for communications and screaming "bloody murder" when it does not
work for some reason, at some time, is very un-Internet. If you want
only a single path, you have to live with the resulting single point of
failure. Allowing web-based messages in addition to email is a simple
and cost-effective way to provide redundancy and reduce the importance
of problems such as reported by Anderson.

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


From ietf-bounces@ietf.org  Thu Jun 24 13:28:23 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02411
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 13:28:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdY1P-00035h-6t
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 13:28:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdXxy-0002EA-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 13:24:51 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdXvl-00016W-00; Thu, 24 Jun 2004 13:22:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdXIx-0001X5-Tz; Thu, 24 Jun 2004 12:42:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bd2gJ-0002xu-Th
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 04:00:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01422
	for <ietf@ietf.org>; Wed, 23 Jun 2004 04:00:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bd2gH-0007c2-EK
	for ietf@ietf.org; Wed, 23 Jun 2004 04:00:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bd2H2-00031a-00
	for ietf@ietf.org; Wed, 23 Jun 2004 03:34:25 -0400
Received: from netcore.fi ([193.94.160.1]) by ietf-mx with esmtp (Exim 4.12)
	id 1Bd1JJ-0007Zh-00; Wed, 23 Jun 2004 02:32:41 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i5N6WBA12636;
	Wed, 23 Jun 2004 09:32:11 +0300
Date: Wed, 23 Jun 2004 09:32:11 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: iesg@ietf.org
In-Reply-To: <E1BYnRW-0003xI-9N@megatron.ietf.org>
Message-ID: <Pine.LNX.4.44.0406230909390.12124-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: idmr@cs.ucl.ac.uk, ietf@ietf.org
Subject: Re: Last Call: 'Distance Vector Multicast Routing Protocol' to
 Proposed Standard 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

On Fri, 11 Jun 2004, The IESG wrote:
> The IESG has received a request from the Inter-Domain Multicast Routing WG to 
> consider the following documents:
> 
> - 'Distance Vector Multicast Routing Protocol '
>    <draft-ietf-idmr-dvmrp-v3-11.txt> as a Proposed Standard
> - 'Distance Vector Multicast Routing Protocol Applicability Statement '
>    <draft-ietf-idmr-dvmrp-v3-as-01.txt> as an Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2004-06-25.

There was some debate about this on the routing-discussion list (among 
others), and there a number of people seemed to be of the opinion that 
the right category for DVMRP would be Informational or Historic, not 
Proposed Standard.

I don't think going for PS is the right choice here.  DVMRP is already
a retired protocol, or one that operators have been retiring (or have
retired) for around 5 years now.  It's OK for existing deployments
which don't want to change to other protocols, but not for new efforts
-- and in that case, Informational would seem much more applicable.  
Such a category would provide guidance for interoperable
implementations, but would also be a sign that DVMRP might not be good
candidate for deployment.

So, I suggest moving the spec to Informational.

A couple of comments about the documents themselves (not a proper
review, I just skimmed them for 30 minutes):

 - both documents fail a number of *required* nits, e.g., boilerplate,
AS missing Security Considerations, old boilerplates, references not
split, etc., the main spec having a line of 90 chars, references in
the abstract, etc.

 applicability statement
 -----------------------

 - this seems weak, especially section 1 on tradeoffs.  A number of 
advantages seem clearly false, as of now (maybe these didn't hold 5 
years ago -- Have these been updated to  PIM-DM?  SSM?  I don't think 
so).

This is the most important messaage of the applicability statement
document, i.e., where NOT to use them and where to use them, and I
don't think the message has come across very clearly.  One should not
also be hesitant to refer to other protocols for better operation
(PIM-SM, -DM, SSM, etc.).

 main spec
 ---------

 - probably needs spelling out why this doesn't need to support IPv6?

 - IANA considerations seems funny, as these values have already been
allocated?  Is it necessary to list these here?  Just say that as the
numbers are already assigned this doc creates no *new* IANA
considerations?  

However, note that as several messages use an IGMP type and this 
document (and the previous revisions) specify the codes for DVMRP (and 
that database is maintained by IANA), it might be necessary to specify 
the allocation criteria (based on RFC2343) for subsequent allocations?

 - security considerations basically only discusses the lack of
anti-replay w/ DVMRP when using IPsec, and leaves out two main things:
(1) everything related to security which does not befall under IPsec
(i.e., what are the issues when IPsec is not used, or what are the
issues even if IPsec is used?), and (2) how do you actually set up the
IPsec keying to make it work in an interoperable fashion?  (The
security ADs are going to bite at (2) at least).

 - there are some old references, like to an old GRE spec.

 - this document does not prominently, right out in the introduction, 
point _loudly_ towards the applicability statement spec.  This is 
especially important if the work goes on for PS.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings


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


From ietf-bounces@ietf.org  Thu Jun 24 14:04:54 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06259
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 14:04:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdYak-0004Lp-Or
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 14:04:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdYL4-0001jR-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 13:48:43 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdYEc-0007fS-02; Thu, 24 Jun 2004 13:42:02 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BdY8Y-0007y5-KI; Thu, 24 Jun 2004 13:35:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdXJz-0001uu-HS; Thu, 24 Jun 2004 12:43:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bd8mw-0000qx-89
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 10:31:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20590
	for <ietf@ietf.org>; Wed, 23 Jun 2004 07:41:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bd684-0005xk-5z
	for ietf@ietf.org; Wed, 23 Jun 2004 07:41:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bd679-0005Z1-00
	for ietf@ietf.org; Wed, 23 Jun 2004 07:40:28 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12) id 1Bd66R-00058l-00
	for ietf@ietf.org; Wed, 23 Jun 2004 07:39:44 -0400
Received: from [127.0.0.1] (sequoia.muada.com [83.149.65.1])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i5NBecIv045605;
	Wed, 23 Jun 2004 13:40:41 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <200406221957.i5MJv2T5035993@calcite.rhyolite.com>
References: <20040622180229.GJ22050@Space.Net>
	<200406221957.i5MJv2T5035993@calcite.rhyolite.com>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <EF94A494-C509-11D8-AE1C-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 23 Jun 2004 13:39:07 +0200
To: Vernon Schryver <vjs@calcite.rhyolite.com>
X-Mailer: Apple Mail (2.618)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: What exactly is an internet (service) provider?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

On 22-jun-04, at 21:57, Vernon Schryver wrote:

>> If you want to buy a car and ask if it has air bags and nobody can
>> give you a definite answer, would you buy the car if it is important 
>> to
>> you to have an air bag?

> Buging a car with a feature with well defined characteristics is quite
> different from buying Internet services which don't even have common
> names.

But that's just a detail. The real difference is that you can buy a car 
anywhere on the landmass of your choice and then bring it to whereever 
you want to use it on that same landmass. With IP service, you're 
limited to whatever is available in a certain place. Usually the choice 
is between too expensive and/or too slow (dial-up and GPRS and the 
like) and broken (most hotel broadband and wifi hotspots).

> It is not the job of the IETF to try to stop anyone from selling
> services that differ from what we used to get via NSF any more than
> it is the job of the IETF to prevent the sales of NAT boxes and PPPoE,

I disagree. If the IETF were in the position to influence people, it 
should certainly do so. What good is it to standardize protocols that 
can't be deployed because network operators build networks that can't 
support them? Unfortunately, there are usually reasons for implementing 
breakage, and wisdom from the IETF isn't going to remove those reasons, 
so we shouldn't expect miracles.


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


From ietf-bounces@ietf.org  Thu Jun 24 14:28:13 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09727
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 14:28:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdYxK-0001bp-EH
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 14:28:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdYlG-0006in-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 14:15:48 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdYYP-00041b-01; Thu, 24 Jun 2004 14:02:29 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BdYWi-0001Hq-74; Thu, 24 Jun 2004 14:00:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdXN2-0002cj-Rl; Thu, 24 Jun 2004 12:46:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BdCPR-0007It-H3
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 14:23:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28267
	for <ietf@ietf.org>; Wed, 23 Jun 2004 14:23:43 -0400 (EDT)
From: bill@strahm.net
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BdCPP-0003jy-NE
	for ietf@ietf.org; Wed, 23 Jun 2004 14:23:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdC1K-0006l5-00
	for ietf@ietf.org; Wed, 23 Jun 2004 13:58:52 -0400
Received: from smtpout03-03.mesa1.secureserver.net ([64.202.165.73])
	by ietf-mx with smtp (Exim 4.12) id 1BdB5R-0005su-00
	for ietf@ietf.org; Wed, 23 Jun 2004 12:59:01 -0400
Received: (qmail 7929 invoked from network); 23 Jun 2004 16:58:30 -0000
Received: from unknown (HELO webmail03.mesa1.secureserver.net) (64.202.166.82)
	by smtpout03-03.mesa1.secureserver.net with SMTP;
	23 Jun 2004 16:58:30 -0000
Received: (qmail 16508 invoked by uid 99); 23 Jun 2004 16:58:30 -0000
Message-ID: <20040623165830.16507.qmail@webmail03.mesa1.secureserver.net>
Date: Wed, 23 Jun 2004 09:58:30 -0700
To: Gene Gaines <gene.gaines@gainesgroup.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Cc: ietf@ietf.org
Subject: RE: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,NO_REAL_NAME autolearn=no 
	version=2.60

Amen - I would add that Mr. Vixie hasn't helped matters either.

Bill
PS - Where is J. Flemming when you need him anyway, I want to get back to good
old fashioned trolling
> -------- Original Message --------
> Subject: Re: Response to complaint from Dean Anderson (fwd)
> From: "Gene Gaines" <gene.gaines@gainesgroup.com>
> Date: Tue, June 22, 2004 6:24 pm
> To: ietf@ietf.org
> 
> Enough.
> 
> The Dean Anderson fiasco has continued long enough.
> 
> This is a formal request that Anderson be asked to
> cease the off-topic diatribes about a problem that
> I view as of his own making.
> 
> The IETF should have no legal or moral obligation
> to accede to his demands, nor should any individual
> associated with IETF activities.
> 
> His negative diatribes and threats do damage to the
> IETF.  It is important he cease or be banned from
> IETF lists.
> 
> I have not met Mr. Anderson, but remember him quite
> well from past correspondence lists such as:
> 
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> 
>  To: Yakov Shafranovich <research@solidmatrix.com>
>  Subject: Re: Fwd: ICANN asks Verisign to shutdown SiteFinder
>           in 48 hours
>  From: Dean Anderson <dean@av8.com>
>  Date: Fri, 3 Oct 2003 17:12:02 -0400 (EDT)
>  Cc: ietf@ietf.org
>  In-reply-to: <3F7DA063.6020409@solidmatrix.com>
>  Sender: owner-ietf@ietf.org
> 
> I see that Verisign is complying while they "review their
> options".
> 
> Well, hopefully they are having their lawyers go over their
> contracts to see if ICANN can claim it is in breach of any
> contract. It would seem that they can't, having not complained
> about other registries, and having not substantiated any adverse
> effects to the internet. It will take some time to go through
> each claim and offer a substantial proof that it is wrong. It
> will be interesting to see what the lawyers say.
> 
> It was really to bad that they gave the "angry scientists and
> engineers" as much credit as they did. This angry group is
> basically the same bunch of Verisign bashers that have been
> whining about Verisign or Network Solutions for many years, when
> there are other registries that are much more deserving of
> criticism. Calling them scientists and engineers gives too much
> credit because real scientists and engineers deal in facts. I
> would use another term.
> 
> I for one hope that SiteFinder will come back, and I wish
> Verisign good luck.
> 
>                --Dean
> 
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> 
> Gene Gaines
> gene.gaines@gainesgroup.com
> Sterling, Virginia
> 
> On Tuesday, June 22, 2004, 4:22:49 PM, Dean wrote:
> 
> > On Tue, 22 Jun 2004 Valdis.Kletnieks@vt.edu wrote:
> 
> >> On Mon, 21 Jun 2004 18:43:23 EDT, Dean Anderson said:
> >> 
> >> > Mr. Vixie's obvious malice for Av8 Internet is plain to see,
> >> 
> >> As is the fact that the feelings appear to be mutual....
> 
> > One never appreciates being publicly disparaged, defamed, or
> harrassed,
> > but it is incorrect to assume that just because I have been attacked,
> that
> > I harbor malice for that person. Rather, I feel sorry for someone who
> is
> > presumably in his 40's and resorts to name-calling.  Such
> unsocialization
> > or immaturity must be debilitating.  I pray for them.  This does not
> mean
> > that I will silently accept such treatment, nor does it mean I will
> not
> > assert my rights and privileges to object to such treatment.
> 
> > Besids Mr. Vixie's on-list comments, there is his involvement in the
> > defamatory and misleading statements about Av8 Internet's IP address
> > space. Long ago, and for other reasons, I came to believe that
> defamation
> > results in a short term loss for the defamed and a short term gain
> for the
> > defamer, but a long term gain for the defamed and a long term loss
> for the
> > defamer.  Lies are always exposed as lies and liars are always
> exposed as
> > liars.  This is particularly appropriate as the UN meets today to
> discuss
> > anti-semitism, which is also spread by defamation.  The defamed may
> be
> > saddened and harmed while being defamed, but have solace in the fact
> that
> > history will eventually right the wrong: It always has. It always
> will.
> > This doesn't mean one should be complacent.  Everyone should stand up
> to
> > stop defamation.
> 
> > I have made efforts to make my criticisms professional and accurate,
> and
> > not to allow myself to degenerate into name-calling. Persons who
> behave
> > badly and call other people names deserve criticism.  While everyone
> may
> > be fallible from time to time in overheated discussion, some people
> seem
> > to have no control or compuction whatsoever.  I have tried to make
> sure
> > that my criticisms meet the standard of cool and detached
> professionalism.
> > Mr. Vixie's comments ("loons", "trolls", "dv8", "least technical
> person on
> > the list" do not meet that standard.
> 
> > But I note that you have not amoung those who have posted messages
> calling
> > for Mr. Vixie to "take a break" before calling other people names. 
> Is it
> > that you have become accustomed to his behavior or do you hold me to
> a
> > different standard?
> 
> >> > services to customers.  However, it is unclear what Mr. Vixie's
> expertise
> >> > is actually in, other than name-calling, and making disparaging
> >> > alterations on another companies trademarks. I have seen little
> else.
> >> 
> >> Pot. Kettle. Black.
> 
> > Not exactly.  Questioning someone's expertise is quite a bit
> different
> > than declaring someone else to be "the least technical person on the
> > list".  I did the former, Mr. Vixie did the latter.  The former is
> > reasonable and appropriate, the latter isn't.
> 
> > Questioning Mr. Vixie's expertise is not unreasonable nor
> inappropriate in
> > the light of his last several disparaging remarks not only about
> myself
> > and subsequently my company, and also Mr. Vixies inappropriate
> > name-calling of other people. I note that the Chair has also failed
> to
> > chastise these other inappropriate comments by Mr. Vixie.
> 
> > I am aware of Mr. Vixie's past involvement in DNS and his operation
> of a
> > Root nameserver, yet just recently he diverted attention from
> genuine
> > questions raised by several people about Root Anycast to a personal
> attack
> > on several of the participants.  This does not seem to be appropriate
> for
> > a trusted person in DNS or Root server operations, and leads to
> questions
> > about professionalism, responsibility, maturity, and and ultimately,
> trust
> > in his expertise in that area.  The name-calling raises further
> questions
> > about whether we can trust Mr. Vixie's assurances. This is also not
> a
> > personal attack: Such questions are valid, have been raised by
> several
> > people, and have gone unanswered except for name-calling.
> 
> 
> > Dean Anderson
> > Av8 Internet, Inc
> 
> 
> > ===================
> 
> > Date: 19 May 2004 22:16:36 +0000
> > From: Paul Vixie <vixie@vix.com>
> > To: ietf@ietf.org
> > Subject: Re: Root Anycast
> 
> > there are two things that i think it's important that everybody
> > understand.
> 
> > first, anyone who posts from roll accounts like "info@utel.net
> (jfcm)"
> > tends to be dismissed as a troll.
> 
> > second, anyone who seriously uses the term "legacy DNS root" tends to
> be
> > dismissed as a loon.
> 
> > i now return control of your television set to the loons and
> trolls...
> 
> 
> -- 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf

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


From ietf-bounces@ietf.org  Thu Jun 24 14:28:53 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09867
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 14:28:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdYxx-0001jd-Rt
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 14:28:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdYm4-0006qz-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 14:16:37 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdYYt-00041b-01; Thu, 24 Jun 2004 14:02:59 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BdYUv-0001B4-6f; Thu, 24 Jun 2004 13:58:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdXMw-0002Xx-4F; Thu, 24 Jun 2004 12:46:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BdCKQ-0006Et-4Y
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 14:18:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27049
	for <ietf@ietf.org>; Wed, 23 Jun 2004 14:18:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BdCKO-0002a3-LS
	for ietf@ietf.org; Wed, 23 Jun 2004 14:18:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdBny-00041m-00
	for ietf@ietf.org; Wed, 23 Jun 2004 13:45:03 -0400
Received: from mail5.atl.registeredsite.com ([64.224.219.79] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12) id 1BdAaP-0002QW-00
	for ietf@ietf.org; Wed, 23 Jun 2004 12:26:57 -0400
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail5.atl.registeredsite.com (8.12.11/8.12.8) with ESMTP id
	i5NGQuFZ018659; Wed, 23 Jun 2004 16:26:56 GMT
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ;
	Wed, 23 Jun 2004 11:26:55 -0500
Message-ID: <40D9AF4B.2010502@nma.com>
Date: Wed, 23 Jun 2004 09:26:51 -0700
From: Ed Gerck <egerck@nma.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
References: <20040623021417.2937E17921@portal.hamachi.org>
In-Reply-To: <20040623021417.2937E17921@portal.hamachi.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: sommerfeld@orchard.arlington.ma.us
Subject: the best point, Re: non-solution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,TO_ADDRESS_EQ_REAL 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



Bill Sommerfeld wrote:

 > Ed Gerck wrote:
>>What I suggested is a web interface to the IETF mailboxes, such that
>>any routing problems TO those mailboxes would cease to be an issue,
>>allowing the IETF to be in FULL CONTROL of what is forwared to a
>>mailbox, or not.
> 
> How is this compatible with the IETF being run largely by donated
> labor?

That's the best point of my suggestion! The IETF (and this list!) would
no longer waste time with complaints about lack of access to mailboxes,
while IETF-wide challenge-response (as it is done today already) and
filters would be in place to prevent further wasting of donated labor.
Because routing problems TO those mailboxes would cease to be an issue,
the servers would either accept and forward the message or send back a
message with further instructions to the sender. Of course, people could
still send email as today. But there would be an alternative using the
Internet, preventing the current single point of failure.

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


From ietf-bounces@ietf.org  Thu Jun 24 14:49:58 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12140
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 14:49:57 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdZIM-0005pQ-My
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 14:49:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdZ12-0002K6-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 14:32:06 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdYok-0007Fq-05; Thu, 24 Jun 2004 14:19:22 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BdYle-0002Fe-8G; Thu, 24 Jun 2004 14:16:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdXNy-00030V-Mj; Thu, 24 Jun 2004 12:47:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BdDhD-00066D-6j
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 15:46:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10610
	for <ietf@ietf.org>; Wed, 23 Jun 2004 15:46:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BdDhB-00014J-8z
	for ietf@ietf.org; Wed, 23 Jun 2004 15:46:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdDgD-0000gl-00
	for ietf@ietf.org; Wed, 23 Jun 2004 15:45:10 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BdDfK-0007nB-00
	for ietf@ietf.org; Wed, 23 Jun 2004 15:44:14 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i5NJhiQx037420
	for ietf@ietf.org env-from <vjs>;
	Wed, 23 Jun 2004 13:43:44 -0600 (MDT)
Date: Wed, 23 Jun 2004 13:43:44 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200406231943.i5NJhiQx037420@calcite.rhyolite.com>
To: ietf@ietf.org
References: <20040623013900.DB24F17921@portal.hamachi.org>
Subject: Re: non-solution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

> From: Bill Sommerfeld 

> Substantially similar capabilities are present in all of the SMTP
> MTA's I'm familiar with.  If a message delivery attempt is rejected
> early, only envelope information is logged, but if the message was
> rejected in error, that's generally sufficient to identify what needs
> to be whitelisted.

Yes, but after you've had them, you find that facilities that log the
fewest few dozen KBytes of SMTP bodies are very valuable.  SMTP envelope
logs are unitelligible to most users, not only because they are terse
but because the SMTP envelope is a mystery to the fewer users that
know about it.  Delaying filter rejections until the SMTP DATA command
and so capturing the message body resolves a lot of complaints of the
form "Why did your idiotic spam filter reject that perfectly good mail
message?"  That can significantly reduce whitelisting requirements.

Logging bodies involve some obvious privacy hassles.  You must keep the
logs private.  The logs can have only censored copies of the envelope
so that recipients can't know who else was sent the same message.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Thu Jun 24 14:50:12 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12168
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 14:50:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdZIa-0005rx-HE
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 14:50:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdZ1E-0002MV-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 14:32:17 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdYom-0007Fq-02; Thu, 24 Jun 2004 14:19:24 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BdYkf-000285-CF; Thu, 24 Jun 2004 14:15:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdXNw-0002yp-Oe; Thu, 24 Jun 2004 12:47:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BdDTV-0003n7-3T
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 15:32:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09460
	for <ietf@ietf.org>; Wed, 23 Jun 2004 15:31:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BdDTT-0003Qb-JF
	for ietf@ietf.org; Wed, 23 Jun 2004 15:31:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdDSV-000322-00
	for ietf@ietf.org; Wed, 23 Jun 2004 15:30:59 -0400
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx with esmtp (Exim 4.12) id 1BdDRe-0002bq-00
	for ietf@ietf.org; Wed, 23 Jun 2004 15:30:06 -0400
Received: from andromeda (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i5NJU5pV007582 for ietf@ietf.org; Wed, 23 Jun 2004 21:30:05 +0200
Received: (from hadmut@localhost)
	by andromeda.dresden.danisch.de (8.12.11/8.12.11/Debian-5) id
	i5NJTb4g026303 for ietf@ietf.org; Wed, 23 Jun 2004 21:29:37 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Wed, 23 Jun 2004 21:29:37 +0200
To: ietf@ietf.org
Message-ID: <20040623192937.GA26196@danisch.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
Subject: Defining Internet services/service levels?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

OK, there was some discussion about different
levels of Internet services and categories. 

So should the IETF publish a definition?


regards
Hadmut

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


From ietf-bounces@ietf.org  Thu Jun 24 16:40:33 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28807
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 16:40:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bdb1N-0002qz-Vz
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 16:40:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdaQU-0003lG-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 16:02:28 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdZsX-0004x3-00; Thu, 24 Jun 2004 15:27:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdXPa-0003Su-7W; Thu, 24 Jun 2004 12:49:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BdEwO-0003Zu-UP
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 17:05:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17966
	for <ietf@ietf.org>; Wed, 23 Jun 2004 17:05:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BdEwN-0001TW-2C
	for ietf@ietf.org; Wed, 23 Jun 2004 17:05:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdEvN-00015c-00
	for ietf@ietf.org; Wed, 23 Jun 2004 17:04:53 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12) id 1BdEuK-0000MO-00
	for ietf@ietf.org; Wed, 23 Jun 2004 17:03:48 -0400
Received: from [127.0.0.1] (sequoia.muada.com [83.149.65.1])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i5NL522r055624;
	Wed, 23 Jun 2004 23:05:03 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <40D8E2F0.3090606@nma.com>
References: <20040623013900.DB24F17921@portal.hamachi.org>
	<40D8E2F0.3090606@nma.com>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C79A4EF1-C558-11D8-A349-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 23 Jun 2004 23:03:30 +0200
To: Ed Gerck <egerck@nma.com>
X-Mailer: Apple Mail (2.618)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: non-solution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

On 23-jun-04, at 3:54, Ed Gerck wrote:

> Of course, I still believe that insisting in only using the email
> for communications and screaming "bloody murder" when it does not
> work for some reason, at some time, is very un-Internet. If you want
> only a single path, you have to live with the resulting single point of
> failure. Allowing web-based messages in addition to email is a simple
> and cost-effective way to provide redundancy and reduce the importance
> of problems such as reported by Anderson.

The IETF has used email as its primary method of conducting its 
business for almost 20 years. The IETF is also in charge of all the 
relevant standards. So if email doesn't work, I think the IETF should 
fix it rather than come up with ad-hoc additional communication 
mechanisms that have more than enough problems of their own.

Creating such a new channel only gives people with unreasonable email 
habits (such as rejecting replies to list messages without saying why) 
positive feedback so email becomes even less reliable.


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


From ietf-bounces@ietf.org  Thu Jun 24 17:05:42 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10570
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 17:05:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdbPj-0007Oz-LI
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 17:05:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdamE-0000FZ-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 16:24:55 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdaDW-0001Sc-01; Thu, 24 Jun 2004 15:49:02 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BdaCP-0007q1-47; Thu, 24 Jun 2004 15:47:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdXQJ-0003sL-59; Thu, 24 Jun 2004 12:50:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BdJLU-0006DB-1u
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 21:48:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05450
	for <ietf@ietf.org>; Wed, 23 Jun 2004 21:48:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BdJLR-00071E-Ru
	for ietf@ietf.org; Wed, 23 Jun 2004 21:48:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdJKV-0006eE-00
	for ietf@ietf.org; Wed, 23 Jun 2004 21:47:07 -0400
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12) id 1BdJJX-0005up-00
	for ietf@ietf.org; Wed, 23 Jun 2004 21:46:07 -0400
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 LAA874767;
	Thu, 24 Jun 2004 11:45:30 +1000 (EST)
Message-ID: <40DA3239.5089E583@swin.edu.au>
Date: Thu, 24 Jun 2004 11:45:29 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures,
	Swinburne University of Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
References: <Pine.LNX.4.44.0406211814230.18782-100000@cirrus.av8.net>
	<20040623014532.GB339@derobert.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: Re: Additional complaint about disparagement by Paul Vixie on
	IETFlists
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Anthony DeRobertis wrote:
> 
> On Mon, Jun 21, 2004 at 06:21:53PM -0400, Dean Anderson wrote:
> >
> > Harald, Please add __Another__ complaint to the chair about inappropriate
> > behavior by Mr. Vixie.  Altering our name from Av8 Internet to "dv8" is
> > simply more disparagement
> 
> I don't see how "dv8" is disparaging in any way. If that is an attempt
> to disparage AV8, then it's a very, very poor attempt. More likely, I
> suspect, is that its a mistake.

I personally filter out all emails from Dean Anderson, but let's
not ignore our own responsibilities. Try pronouncing "dv8". Still
don't understand the intended slight? Paul used it more than once, so
not a mistake. The mistake was to stoop just that little bit lower (or
to not filter out Dean's emails in the first place, but I digress....)

gja

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


From ietf-bounces@ietf.org  Thu Jun 24 18:39:36 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22967
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 18:39:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdcnZ-0000iB-9I
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 18:34:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bdc9C-0000Oe-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 17:52:42 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdbPR-0007GQ-00; Thu, 24 Jun 2004 17:05:25 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BdbE1-0003VC-I8; Thu, 24 Jun 2004 16:53:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdYX6-0005jP-9U; Thu, 24 Jun 2004 14:01:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bd8lK-0000qi-72
	for ietf@megatron.ietf.org; Wed, 23 Jun 2004 10:30:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00372
	for <ietf@ietf.org>; Wed, 23 Jun 2004 09:28:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bd7nt-0006JJ-GJ
	for ietf@ietf.org; Wed, 23 Jun 2004 09:28:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bd7mm-0005uG-00
	for ietf@ietf.org; Wed, 23 Jun 2004 09:27:33 -0400
Received: from 192-73-206-10.ulticom.com ([192.73.206.10]
	helo=colby.ulticom.com) by ietf-mx with esmtp (Exim 4.12)
	id 1Bd7mA-0005TG-00
	for ietf@ietf.org; Wed, 23 Jun 2004 09:26:54 -0400
Received: from pckrishnan (pc-krishnan.ulticom.com [172.25.34.39])
	by colby.ulticom.com (8.12.10/8.12.10) with SMTP id i5NDQOA0028061
	for <ietf@ietf.org>; Wed, 23 Jun 2004 09:26:24 -0400 (EDT)
From: "Vijay Krishnan" <vijay.krishnan@ulticom.com>
To: <ietf@ietf.org>
Date: Wed, 23 Jun 2004 09:25:25 -0400
Message-ID: <003d01c45925$8bc67e40$272219ac@pckrishnan>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Scanned-By: MIMEDefang 2.40
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 24 Jun 2004 14:01:07 -0400
Subject: M2UA help
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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: 7bit

Hi,
I am confused about the following in M2UA

1. The only documentation i have is RFC 3331. Please let me know if there is
more documentation.

2. I understand that the AS is a logical group of links in the SG. How does
the SG group links as AS? Do all links with same opc-dpc become 1 AS? or is
there some other parameter?

3. The RFC says that 1 ASP should support multiple AS. Does the client side
(MGC) know all the AS information at configuration time?

4. IN load share mode do all ASPs in an AS register for all IIDs? If so is
it the MGCs responsibility to sequence the messages or is it the SGs
responsibility to send a sequence to the same SCTP stream?

5. Any information on what the SG and AS know at configuration time about
the AS, ASP and IIDs will be useful.

Thanks in advance for your help.

-Vijay


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


From ietf-bounces@ietf.org  Thu Jun 24 18:57:14 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23866
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 18:40:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdciA-0007Is-MY
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 18:28:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bdc2E-00074a-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 17:45:31 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdbP5-0007CQ-00; Thu, 24 Jun 2004 17:05:03 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BdbJZ-0004NO-RS; Thu, 24 Jun 2004 16:59:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdZdj-0004PJ-A3; Thu, 24 Jun 2004 15:12:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BdXPH-0003PG-KY
	for ietf@megatron.ietf.org; Thu, 24 Jun 2004 12:48:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28184
	for <ietf@ietf.org>; Thu, 24 Jun 2004 12:48:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BdXPG-0002OH-FK
	for ietf@ietf.org; Thu, 24 Jun 2004 12:48:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdXO4-0001yB-00
	for ietf@ietf.org; Thu, 24 Jun 2004 12:47:44 -0400
Received: from [199.239.208.244] (helo=199.239.208.244)
	by ietf-mx with esmtp (Exim 4.12) id 1BdXNR-0001S8-00
	for ietf@ietf.org; Thu, 24 Jun 2004 12:47:05 -0400
Received: from [24.239.105.13] (helo=x)
	by 199.239.208.244 with asmtp (Exim 3.36 #1) id 1BdXMs-0005BH-00
	for ietf@ietf.org; Thu, 24 Jun 2004 12:46:30 -0400
From: "Sal Mangiapane" <salm@servanttechnology.com>
To: <ietf@ietf.org>
Date: Thu, 24 Jun 2004 12:46:20 -0400
Message-ID: <OJELKLINFKPMOMIFLIDFMEMMFKAA.salm@servanttechnology.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Subject: copyright requirements clarification - please
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: salm@servanttechnology.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=RCVD_NUMERIC_HELO autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

Hello all,

I am reading through RFC 3667 and RFC 3668 and have come upon what I
believe is a conflict.

In RFC 3667 in Section 5.4 it states:

----------------------------------------------------------------------
5.4.  Copyright Notice (required for all IETF Documents)

   (Normally placed at the end of the IETF Document.)

      "Copyright (C) The Internet Society (year).  This document is
      subject to the rights, licenses and restrictions contained in BCP
      78, and except as set forth therein, the authors retain all their
      rights."

   Additional copyright notices are not permitted in IETF Documents
   except in the case where such document is the product of a joint
   development effort between the IETF and another standards development
   organization or the document is a republication of the work of
   another standards organization.  Such exceptions must be approved on
   an individual basis by the IAB.

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



BUT, in both documents an additional copyright statement is included
near the beginning of the documents:

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

Copyright Notice

   Copyright (C) The Internet Society (2004).  All Rights Reserved.

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


Is this a conflict?

Regards,

Sal
Salvatore Mangiapane

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


From ietf-bounces@ietf.org  Thu Jun 24 19:00:15 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25740
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 18:57:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bdd2b-0004Qj-3X
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 18:49:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdcKh-0002Zd-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 18:04:36 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdbUQ-0000Zh-00; Thu, 24 Jun 2004 17:10:34 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BdbUM-0006jG-BI; Thu, 24 Jun 2004 17:10:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdavD-0003IX-Lo; Thu, 24 Jun 2004 16:34:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BdXZc-000650-P0
	for ietf@megatron.ietf.org; Thu, 24 Jun 2004 12:59:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29314
	for <ietf@ietf.org>; Thu, 24 Jun 2004 12:59:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BdXZb-0006yZ-Mt
	for ietf@ietf.org; Thu, 24 Jun 2004 12:59:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdXYX-0006Xx-00
	for ietf@ietf.org; Thu, 24 Jun 2004 12:58:33 -0400
Received: from [199.239.208.244] (helo=199.239.208.244)
	by ietf-mx with esmtp (Exim 4.12) id 1BdXXS-0005lj-00
	for ietf@ietf.org; Thu, 24 Jun 2004 12:57:26 -0400
Received: from [24.239.105.13] (helo=x)
	by 199.239.208.244 with asmtp (Exim 3.36 #1) id 1BdXWy-0005HX-00
	for ietf@ietf.org; Thu, 24 Jun 2004 12:56:56 -0400
From: "Sal Mangiapane" <salm@servanttechnology.com>
To: <ietf@ietf.org>
Date: Thu, 24 Jun 2004 12:56:46 -0400
Message-ID: <OJELKLINFKPMOMIFLIDFEEMNFKAA.salm@servanttechnology.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Subject: Intellectual property clarification - please
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: salm@servanttechnology.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=RCVD_NUMERIC_HELO autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

Both RFC 3667 and RFC 3668 contain an Intellectual Property
disclaimer near the end of the document as defined in Section
5 of RFC 3668.  But, this appears to only be required as stated
in Section 5 for specific requirements:

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

5.  Notice to be included in RFCs

   The RFC Editor will ensure that the following notice is present in
   all IETF RFCs and all other RFCs for which an IPR disclosure or
   assertion has been received prior to publication.

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

Is it the intention to always include the IPR statement and the RFC
Editor will only "ensure" it when an IPR disclosure has been made?

Thanks again for your guidance,

Sal
Salvatore Mangiapane

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


From ietf-bounces@ietf.org  Thu Jun 24 19:16:54 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28901
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 19:16:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BddEH-00008T-Gf
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 19:02:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bdcc7-00069o-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 18:22:36 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdbwZ-0005xH-00; Thu, 24 Jun 2004 17:39:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdbIy-000200-7d; Thu, 24 Jun 2004 16:58:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BdZXu-0007f4-Ba
	for ietf@megatron.ietf.org; Thu, 24 Jun 2004 15:06:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14016
	for <ietf@ietf.org>; Thu, 24 Jun 2004 15:06:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BdZXs-0000n9-Ls
	for ietf@ietf.org; Thu, 24 Jun 2004 15:06:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdZAd-0003yL-00
	for ietf@ietf.org; Thu, 24 Jun 2004 14:41:59 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12) id 1BdYu0-0000M1-00
	for ietf@ietf.org; Thu, 24 Jun 2004 14:24:48 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i5OIO8W22031;
	Thu, 24 Jun 2004 11:24:08 -0700
X-mProtect: <200406241824> Nokia Silicon Valley Messaging Protection
Received: from ftemplin.iprg.nokia.com (205.226.2.67,
	claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdoCj7Fv; Thu, 24 Jun 2004 11:24:07 PDT
Message-ID: <40DB1C53.5040901@iprg.nokia.com>
Date: Thu, 24 Jun 2004 11:24:19 -0700
From: Fred Templin <ftemplin@iprg.nokia.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bill@strahm.net
References: <20040623165830.16507.qmail@webmail03.mesa1.secureserver.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Gene Gaines <gene.gaines@gainesgroup.com>
Subject: Re: Response to complaint from Dean Anderson (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit


bill@strahm.net wrote:

>PS - Where is J. Flemming when you need him anyway, I want to get back to good
>old fashioned trolling
>

"be careful what you wish for" ...

Fred
ftemplin@iprg.nokia.com


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


From ietf-bounces@ietf.org  Thu Jun 24 19:16:55 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28962
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 19:16:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BddAx-0006i8-Ha
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 18:58:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdcYG-00055U-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 18:18:36 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bdbqe-0004Mb-00; Thu, 24 Jun 2004 17:33:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdbGE-0007F7-Vs; Thu, 24 Jun 2004 16:55:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BdYun-0005Yn-R0
	for ietf@megatron.ietf.org; Thu, 24 Jun 2004 14:25:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09303
	for <ietf@ietf.org>; Thu, 24 Jun 2004 14:25:36 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BdYum-00011p-KG
	for ietf@ietf.org; Thu, 24 Jun 2004 14:25:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdYi8-0005vz-00
	for ietf@ietf.org; Thu, 24 Jun 2004 14:12:32 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1BdYT7-0003IS-00
	for ietf@ietf.org; Thu, 24 Jun 2004 13:57:01 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta5/8.13.0.Beta5) with ESMTP id
	i5OHvawV026018; Thu, 24 Jun 2004 13:57:36 -0400
Message-Id: <200406241757.i5OHvawV026018@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: Your message of "Wed, 23 Jun 2004 13:39:07 +0200."
	<EF94A494-C509-11D8-AE1C-000A95CD987A@muada.com> 
References: <20040622180229.GJ22050@Space.Net>
	<200406221957.i5MJv2T5035993@calcite.rhyolite.com>
	<EF94A494-C509-11D8-AE1C-000A95CD987A@muada.com>
Mime-Version: 1.0
Date: Thu, 24 Jun 2004 13:57:36 -0400
Cc: ietf@ietf.org, Vernon Schryver <vjs@calcite.rhyolite.com>
Subject: Re: What exactly is an internet (service) provider? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0842354616=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,NO_REAL_NAME autolearn=no 
	version=2.60

--===============0842354616==
Content-Type: multipart/signed; boundary="==_Exmh_985722544P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Wed, 23 Jun 2004 13:39:07 +0200, Iljitsch van Beijnum said:

> But that's just a detail. The real difference is that you can buy a car 
> anywhere on the landmass of your choice and then bring it to whereever 
> you want to use it on that same landmass. With IP service, you're 
> limited to whatever is available in a certain place. Usually the choice 
> is between too expensive and/or too slow (dial-up and GPRS and the 
> like) and broken (most hotel broadband and wifi hotspots).

The analogy gets much more interesting if you posit the existence of cars
that run on diesel, or ethanol, or hydrogen fuel cell, or other energy sources
not as widespread as 89-octane gasoline....

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

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

iD8DBQFA2xYQcC3lWbTT17ARAr/iAKDIbINuTgsJ92qoCQO+wBDUV8PsSgCglyYs
fQNQHAl79CGCeH8YXlGm3Gs=
=IJtN
-----END PGP SIGNATURE-----

--==_Exmh_985722544P--


--===============0842354616==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0842354616==--



From ietf-bounces@ietf.org  Thu Jun 24 19:48:19 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02230
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 19:48:19 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bddvu-0003nE-6w
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 19:47:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BddqS-000279-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 19:41:29 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bddlt-0000nY-00; Thu, 24 Jun 2004 19:36:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BddPa-0006Gi-5y; Thu, 24 Jun 2004 19:13:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdd9y-0007W0-RK
	for ietf@megatron.ietf.org; Thu, 24 Jun 2004 18:57:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25642
	for <ietf@ietf.org>; Thu, 24 Jun 2004 18:57:28 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bdd3H-0004Yp-HU
	for ietf@ietf.org; Thu, 24 Jun 2004 18:50:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdcLo-0002lY-00
	for ietf@ietf.org; Thu, 24 Jun 2004 18:05:46 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12) id 1BdbVg-0000oJ-00
	for ietf@ietf.org; Thu, 24 Jun 2004 17:11:52 -0400
Received: from [10.20.30.249] (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.9) with ESMTP id i5OLBiEB000512;
	Thu, 24 Jun 2004 14:11:45 -0700 (PDT)
	(envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
X-Sender: phoffvpnc@mail.vpnc.org
Message-Id: <p06110472bd00f3237f65@[10.20.30.249]>
In-Reply-To: <20040623192937.GA26196@danisch.de>
References: <20040623192937.GA26196@danisch.de>
Date: Thu, 24 Jun 2004 14:11:45 -0700
To: Hadmut Danisch <hadmut@danisch.de>, ietf@ietf.org
From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Subject: Re: Defining Internet services/service levels?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

At 9:29 PM +0200 6/23/04, Hadmut Danisch wrote:
>OK, there was some discussion about different
>levels of Internet services and categories.
>
>So should the IETF publish a definition?

No: it's not the kind of engineering we do best.

Yes: we are about the only group that can get the level of review 
needed to prevent such a document from being a puff piece from ISPs.

No: it's about offering of protocols, not how the protocols work

Yes: Having an Informational RFC (it should not be labelled "best 
current practice") on this would be useful to the Internet community.



Proposal: Create a personal Internet Draft. Create a mailing list for 
discussing the draft. Announce the mailing list here. Cycle a few 
times. Announce what you think is the last version year. Probably 
cycle once or twice more. Turn it in to the RFC Editor as a personal 
submission.

--Paul Hoffman, Director
--VPN Consortium

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


From ietf-bounces@ietf.org  Thu Jun 24 20:01:40 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00963
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 19:32:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BddTt-0003o3-BQ
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 19:18:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bdd82-0005bY-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 18:55:35 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdcUR-0004Io-00; Thu, 24 Jun 2004 18:14:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bdc7R-0007bP-0Q; Thu, 24 Jun 2004 17:50:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdbjw-0001st-K4
	for ietf@megatron.ietf.org; Thu, 24 Jun 2004 17:26:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13214
	for <ietf@ietf.org>; Thu, 24 Jun 2004 17:26:33 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bdbjv-00039Z-84
	for ietf@ietf.org; Thu, 24 Jun 2004 17:26:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bdb3z-0003Hh-00
	for ietf@ietf.org; Thu, 24 Jun 2004 16:43:16 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1BdaST-00045j-00
	for ietf@ietf.org; Thu, 24 Jun 2004 16:04:29 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta5/8.13.0.Beta5) with ESMTP id
	i5OK51Fg032690; Thu, 24 Jun 2004 16:05:01 -0400
Message-Id: <200406242005.i5OK51Fg032690@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Hadmut Danisch <hadmut@danisch.de>
In-Reply-To: Your message of "Wed, 23 Jun 2004 21:29:37 +0200."
	<20040623192937.GA26196@danisch.de> 
References: <20040623192937.GA26196@danisch.de>
Mime-Version: 1.0
Date: Thu, 24 Jun 2004 16:05:01 -0400
Cc: ietf@ietf.org
Subject: Re: Defining Internet services/service levels? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1030442558=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,NO_REAL_NAME autolearn=no 
	version=2.60

--===============1030442558==
Content-Type: multipart/signed; boundary="==_Exmh_-2090150213P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Wed, 23 Jun 2004 21:29:37 +0200, Hadmut Danisch <hadmut@danisch.de>  said:
> OK, there was some discussion about different
> levels of Internet services and categories. 
> 
> So should the IETF publish a definition?

There's discussion in progress off-list.  The problem is that although it's
probably feasible to get a consensus on the definitions within the IETF, it's
unclear how to phrase it so that the people who actually need the definitions
can use them.

"This planet has - or rather had - a problem, which was this: most of the
people living on it were unhappy for pretty much of the time. Many solutions
were suggested for this problem, but most of these were largely concerned with
the movements of small green pieces of paper, which is odd because on the whole
it wasn't the small green pieces of paper that were unhappy" -- Douglas Adams


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

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

iD8DBQFA2zPtcC3lWbTT17ARAt8QAKCMdoXxiB2j+M40bT0dTiCnnF7kzQCfV65d
nIKJjoOLEKNDtiP1b5lkxzA=
=p7CJ
-----END PGP SIGNATURE-----

--==_Exmh_-2090150213P--


--===============1030442558==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1030442558==--



From ietf-bounces@ietf.org  Thu Jun 24 20:05:08 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02988
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 19:49:19 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bddlw-0000wt-4D
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 19:36:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bddbs-0005oj-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 19:26:25 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BddJw-0001Bj-00; Thu, 24 Jun 2004 19:07:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bdctr-0000bf-Vw; Thu, 24 Jun 2004 18:40:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdcbm-00023t-KF
	for ietf@megatron.ietf.org; Thu, 24 Jun 2004 18:22:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21892
	for <ietf@ietf.org>; Thu, 24 Jun 2004 18:22:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bdcbl-00065i-3F
	for ietf@ietf.org; Thu, 24 Jun 2004 18:22:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdbvT-0005pW-00
	for ietf@ietf.org; Thu, 24 Jun 2004 17:38:32 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212]
	helo=newdev.harvard.edu) by ietf-mx with esmtp (Exim 4.12)
	id 1BdbMS-0006lv-00
	for ietf@ietf.org; Thu, 24 Jun 2004 17:02:20 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id B860628E411; Thu, 24 Jun 2004 17:01:50 -0400 (EDT)
To: salm@servanttechnology.com
In-Reply-To: <OJELKLINFKPMOMIFLIDFMEMMFKAA.salm@servanttechnology.com>
Message-Id: <20040624210150.B860628E411@newdev.harvard.edu>
Date: Thu, 24 Jun 2004 17:01:50 -0400 (EDT)
From: sob@harvard.edu (Scott Bradner)
Cc: ietf@ietf.org
Subject: Re: copyright requirements clarification - please
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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


this refers to copyrights from somewhere other than the ISOC 
(the W3C or an individual person for example)

multiple copyright notices, if all from teh ISOC, is just fine

Scott

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


From ietf-bounces@ietf.org  Thu Jun 24 20:05:38 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05055
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 20:05:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bde8T-0007WI-12
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 20:00:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bde4b-0006Tq-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 19:56:06 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bddy1-0004Xj-00; Thu, 24 Jun 2004 19:49:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bddmo-00066F-Ua; Thu, 24 Jun 2004 19:37:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BddRD-00007C-EC
	for ietf@megatron.ietf.org; Thu, 24 Jun 2004 19:15:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28368
	for <ietf@ietf.org>; Thu, 24 Jun 2004 19:15:19 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BddJd-0001Dd-D0
	for ietf@ietf.org; Thu, 24 Jun 2004 19:07:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bdclm-0000Ks-00
	for ietf@ietf.org; Thu, 24 Jun 2004 18:32:35 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1Bdc6T-0007ii-00
	for ietf@ietf.org; Thu, 24 Jun 2004 17:49:54 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta5/8.13.0.Beta5) with ESMTP id
	i5OLoWAp004683; Thu, 24 Jun 2004 17:50:32 -0400
Message-Id: <200406242150.i5OLoWAp004683@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: salm@servanttechnology.com
In-Reply-To: Your message of "Thu, 24 Jun 2004 12:46:20 EDT."
	<OJELKLINFKPMOMIFLIDFMEMMFKAA.salm@servanttechnology.com> 
References: <OJELKLINFKPMOMIFLIDFMEMMFKAA.salm@servanttechnology.com>
Mime-Version: 1.0
Date: Thu, 24 Jun 2004 17:50:32 -0400
Cc: ietf@ietf.org
Subject: Re: copyright requirements clarification - please 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0375927221=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,NO_REAL_NAME autolearn=no 
	version=2.60

--===============0375927221==
Content-Type: multipart/signed; boundary="==_Exmh_-1662604600P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Thu, 24 Jun 2004 12:46:20 EDT, Sal Mangiapane <salm@servanttechnology.com>  said:

> 5.4.  Copyright Notice (required for all IETF Documents)

>       "Copyright (C) The Internet Society (year).  This document is
>       subject to the rights, licenses and restrictions contained in BCP
>       78, and except as set forth therein, the authors retain all their
>       rights."

> BUT, in both documents an additional copyright statement is included
> near the beginning of the documents:

>    Copyright (C) The Internet Society (2004).  All Rights Reserved.

> Is this a conflict?

Agreed - the two texts *do* differ, and there is a bit of "practice what you
preach" lurking there.  However, the additional language in the 5.4 boilerplate
appears to be there because the authors of RFC3667 and 3668 presumably
assigned all rights to the Internet Society with the intention of the Society
having *all* the rights to the RFC, whereas most RFCs the authors may wish
to retain some of the rights to the document.  So for the 2 RFCs, the Society
keeps all the rights, but in general the intent is to assign the copyright to
the Society, which then grants back to the authors all the rights except the
limited subset listed in BCP 78 which it needs to do its work.

As such, I don't see a conflict here.  Of course, IANAL, and I presume
that someone who actually is one did a double-check of all this....

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

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

iD8DBQFA20yocC3lWbTT17ARAiL8AJ9NkPqpZyiRmwZao0u3eYpJqeFvowCgskh/
66FplsKilldG6TU206Q7jD4=
=SDGx
-----END PGP SIGNATURE-----

--==_Exmh_-1662604600P--


--===============0375927221==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0375927221==--



From ietf-bounces@ietf.org  Thu Jun 24 20:52:43 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05051
	for <ietf-archive@ietf.org>; Thu, 24 Jun 2004 20:05:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bde8U-0007WX-T8
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 20:00:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bde4d-0006UF-00
	for ietf-archive@ietf.org; Thu, 24 Jun 2004 19:56:08 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bddy2-0004Xt-00; Thu, 24 Jun 2004 19:49:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bddmm-00063i-Nn; Thu, 24 Jun 2004 19:37:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BddRC-00006Y-Af
	for ietf@megatron.ietf.org; Thu, 24 Jun 2004 19:15:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28339
	for <ietf@ietf.org>; Thu, 24 Jun 2004 19:15:18 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BddKA-0001Im-Ft
	for ietf@ietf.org; Thu, 24 Jun 2004 19:08:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdcoP-0000sl-00
	for ietf@ietf.org; Thu, 24 Jun 2004 18:35:18 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1BdcAL-0000bv-00
	for ietf@ietf.org; Thu, 24 Jun 2004 17:53:53 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta5/8.13.0.Beta5) with ESMTP id
	i5OLsWSa004819; Thu, 24 Jun 2004 17:54:32 -0400
Message-Id: <200406242154.i5OLsWSa004819@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: salm@servanttechnology.com
In-Reply-To: Your message of "Thu, 24 Jun 2004 12:56:46 EDT."
	<OJELKLINFKPMOMIFLIDFEEMNFKAA.salm@servanttechnology.com> 
References: <OJELKLINFKPMOMIFLIDFEEMNFKAA.salm@servanttechnology.com>
Mime-Version: 1.0
Date: Thu, 24 Jun 2004 17:54:32 -0400
Cc: ietf@ietf.org
Subject: Re: Intellectual property clarification - please 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1427876388=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,NO_REAL_NAME autolearn=no 
	version=2.60

--===============1427876388==
Content-Type: multipart/signed; boundary="==_Exmh_-1650835400P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Thu, 24 Jun 2004 12:56:46 EDT, Sal Mangiapane <salm@servanttechnology.com>  said:

> Is it the intention to always include the IPR statement and the RFC
> Editor will only "ensure" it when an IPR disclosure has been made?

I read it as "If we are aware of an IPR claim or disclosure, the RFC Editor
will include the appropriate text.".  I don't see any requirement that the RFC Editor
add text protecting against an undisclosed "submarine" patent claim or similar
unfriendly activities....

(Whether such language *should* be added to protect against that is a subject
for another flame-fest, another day.. ;)


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

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

iD8DBQFA202YcC3lWbTT17ARAjfvAKC5NhcelhI5yvU5tz4REedC4q8vRACfQ15Z
+QHmfqWMxESrdkb8AQd7CF0=
=GPOC
-----END PGP SIGNATURE-----

--==_Exmh_-1650835400P--


--===============1427876388==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1427876388==--



From ietf-bounces@ietf.org  Fri Jun 25 11:55:56 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15046
	for <ietf-archive@ietf.org>; Fri, 25 Jun 2004 11:55:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bdt3W-0000eV-AZ
	for ietf-archive@ietf.org; Fri, 25 Jun 2004 11:55:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdsyI-00072V-00
	for ietf-archive@ietf.org; Fri, 25 Jun 2004 11:50:34 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bdssi-0005eU-00; Fri, 25 Jun 2004 11:44:48 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Bdsg7-0006Yp-Vz; Fri, 25 Jun 2004 11:31:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdsLI-0000D5-Mm; Fri, 25 Jun 2004 11:10:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BdrWB-0001qd-QA
	for ietf@megatron.ietf.org; Fri, 25 Jun 2004 10:17:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02814
	for <ietf@ietf.org>; Fri, 25 Jun 2004 10:17:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BdrWA-0006kn-Mk
	for ietf@ietf.org; Fri, 25 Jun 2004 10:17:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdrVH-0006RN-00
	for ietf@ietf.org; Fri, 25 Jun 2004 10:16:31 -0400
Received: from user-0c6s11v.cable.mindspring.com ([24.110.4.63]
	helo=sleekfreak.ath.cx) by ietf-mx with esmtp (Exim 4.12)
	id 1BdrUY-00069S-00
	for ietf@ietf.org; Fri, 25 Jun 2004 10:15:46 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1Bdmq5-00008q-00; Fri, 25 Jun 2004 05:17:41 -0400
Date: Fri, 25 Jun 2004 05:17:36 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <C79A4EF1-C558-11D8-A349-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0406250509260.523-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
Subject: Re: non-solution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=2.0 required=5.0 tests=AWL,WEIRD_PORT autolearn=no 
	version=2.60

On Wed, 23 Jun 2004, Iljitsch van Beijnum wrote:

> On 23-jun-04, at 3:54, Ed Gerck wrote:
>
> > Of course, I still believe that insisting in only using the email
> > for communications and screaming "bloody murder" when it does not
> > work for some reason, at some time, is very un-Internet. If you want
> > only a single path, you have to live with the resulting single point of
> > failure. Allowing web-based messages in addition to email is a simple
> > and cost-effective way to provide redundancy and reduce the importance
> > of problems such as reported by Anderson.
>
> The IETF has used email as its primary method of conducting its
> business for almost 20 years. The IETF is also in charge of all the
> relevant standards. So if email doesn't work, I think the IETF should
> fix it rather than come up with ad-hoc additional communication
> mechanisms that have more than enough problems of their own.

I am in agreement that the mailing list mechanism should not be
tampered with... it works, so don't break it.  The addition of realtime
facilities like irc could potentially augment the process, as long as the
dialogs were archived for public consumption.


>
> Creating such a new channel only gives people with unreasonable email
> habits (such as rejecting replies to list messages without saying why)
> positive feedback so email becomes even less reliable.
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


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


From ietf-bounces@ietf.org  Fri Jun 25 16:21:31 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08697
	for <ietf-archive@ietf.org>; Fri, 25 Jun 2004 16:21:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BdxCX-00032E-08
	for ietf-archive@ietf.org; Fri, 25 Jun 2004 16:21:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdxBX-0002id-00
	for ietf-archive@ietf.org; Fri, 25 Jun 2004 16:20:32 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BdxAa-0002QA-00; Fri, 25 Jun 2004 16:19:32 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BdxAY-0006lH-7i; Fri, 25 Jun 2004 16:19:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bdx3p-000591-Bz; Fri, 25 Jun 2004 16:12:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdwy6-0001Wt-Bu
	for ietf@megatron.ietf.org; Fri, 25 Jun 2004 16:06:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07512
	for <ietf@ietf.org>; Fri, 25 Jun 2004 16:06:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bdwy4-00062o-WF
	for ietf@ietf.org; Fri, 25 Jun 2004 16:06:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdwxD-0005mS-00
	for ietf@ietf.org; Fri, 25 Jun 2004 16:05:43 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12) id 1Bdwwj-0005VF-00
	for ietf@ietf.org; Fri, 25 Jun 2004 16:05:13 -0400
Received: from f01v-20-27.d0.club-internet.fr ([212.195.245.27]
	helo=jfc2.jefsey.com) by montage.altserver.com with esmtp (Exim 4.34)
	id 1Bdwwb-0003Bo-Qe
	for ietf@ietf.org; Fri, 25 Jun 2004 13:05:08 -0700
Message-Id: <6.1.1.1.2.20040625213945.05136980@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Fri, 25 Jun 2004 22:05:36 +0200
To: ietf@ietf.org
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <Pine.LNX.4.44.0406250509260.523-100000@sleekfreak.ath.cx>
References: <C79A4EF1-C558-11D8-A349-000A95CD987A@muada.com>
	<Pine.LNX.4.44.0406250509260.523-100000@sleekfreak.ath.cx>
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 - jefsey.com
Subject: Is the IANA a function performed by ICANN ?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

My understanding was that IANA is a neutral, independent, technical 
authority, everyone using the TCP/IP technology could trust, independently 
from any operational, political, national, commercial consideration which 
are the areas of ICANN, and of other bodies (such as GAC, MINC, ITU, ISOC, 
UN, etc.).

Also, that as the custodian of the references necessary to use the IETF IP, 
it was part of the IETF IPR protection system. I understand that it 
predated the creation of ICANN, of ISOC, of IETF and even (under the name 
of NIC) of the DNS.

I am therefore surprised and (IANAL) I am not sure about the implications 
of the following IANA definition, in a document ICANN is to publish on Monday :

"the Internet Assigned Numbers Authority (IANA) is a function performed by 
ICANN".
http://www.iana.org/procedures/delegation-data.html

ICANN's position within the intergovernance is under UN study, subject to 
possible political negotiations or intergovernmental agreements (cf. the 
ongoing WSIS Prepcom meeting in Hammamet). ICANN is only under contract for 
three years with the USG. RIRs only entered into an MoU with ICANN on the 
grounds that it may not be still here in two years. The majority of ccTLDs 
are not interested in joining ICANN's ccNSO. I do not understand how this 
fits with the necessity of a perpetual, stable, not controverted, 
consensually accepted, trusted technical standard parameters repository?

Or do I read the definition wrong?
jfc 


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


From ietf-bounces@ietf.org  Fri Jun 25 17:14:30 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13834
	for <ietf-archive@ietf.org>; Fri, 25 Jun 2004 17:14:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bdy1n-0002Ue-H8
	for ietf-archive@ietf.org; Fri, 25 Jun 2004 17:14:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bdy0n-0002Dq-00
	for ietf-archive@ietf.org; Fri, 25 Jun 2004 17:13:29 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bdxzm-0001ic-00; Fri, 25 Jun 2004 17:12:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bdxlx-00059J-Pm; Fri, 25 Jun 2004 16:58:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BdxWq-0000DG-2E
	for ietf@megatron.ietf.org; Fri, 25 Jun 2004 16:42:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12017
	for <ietf@ietf.org>; Fri, 25 Jun 2004 16:42:29 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BdxWo-0000zm-LI
	for ietf@ietf.org; Fri, 25 Jun 2004 16:42:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdxVc-0000Wp-00
	for ietf@ietf.org; Fri, 25 Jun 2004 16:41:17 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1BdxTv-00008a-00
	for ietf@ietf.org; Fri, 25 Jun 2004 16:39:31 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta5/8.13.0.Beta5) with ESMTP id
	i5PKdvxC007954; Fri, 25 Jun 2004 16:39:57 -0400
Message-Id: <200406252039.i5PKdvxC007954@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: Your message of "Fri, 25 Jun 2004 22:05:36 +0200."
	<6.1.1.1.2.20040625213945.05136980@mail.jefsey.com> 
References: <C79A4EF1-C558-11D8-A349-000A95CD987A@muada.com>
	<Pine.LNX.4.44.0406250509260.523-100000@sleekfreak.ath.cx>
	<6.1.1.1.2.20040625213945.05136980@mail.jefsey.com>
Mime-Version: 1.0
Date: Fri, 25 Jun 2004 16:39:57 -0400
Cc: ietf@ietf.org
Subject: Re: Is the IANA a function performed by ICANN ? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0596395445=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,NO_REAL_NAME autolearn=no 
	version=2.60

--===============0596395445==
Content-Type: multipart/signed; boundary="==_Exmh_-143026057P";
	micalg=pgp-sha1; protocol="application/pgp-signature"

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

On Fri, 25 Jun 2004 22:05:36 +0200, "JFC (Jefsey) Morfin" <jefsey@jefsey.com>  said:

> "the Internet Assigned Numbers Authority (IANA) is a function performed by 
> ICANN".
> http://www.iana.org/procedures/delegation-data.html

> grounds that it may not be still here in two years. The majority of ccTLDs 
> are not interested in joining ICANN's ccNSO. I do not understand how this 

IANA and the ccNSO/ccTLD are two different beasts.  ccNSO and company
keep track of what NS records are authoritative for what zones. IANA  keeps
track of things like the fact that HTTP is port 80, and which DHCP options
use what numbers, and the like.

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

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

iD8DBQFA3I2dcC3lWbTT17ARAumCAJ9eyIoXvMdmHnlbxFMlpj2b1T1uAgCeI0iq
MoYw1r3WrRImQt8MODKLbYM=
=FeiR
-----END PGP SIGNATURE-----

--==_Exmh_-143026057P--


--===============0596395445==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0596395445==--



From ietf-bounces@ietf.org  Fri Jun 25 18:55:36 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19522
	for <ietf-archive@ietf.org>; Fri, 25 Jun 2004 18:55:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bdzbe-00072e-Ki
	for ietf-archive@ietf.org; Fri, 25 Jun 2004 18:55:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bdzai-0006lY-00
	for ietf-archive@ietf.org; Fri, 25 Jun 2004 18:54:40 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bdza5-0006ST-00; Fri, 25 Jun 2004 18:54:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BdzPz-0006OP-7q; Fri, 25 Jun 2004 18:43:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BdzKE-0004Lr-P7
	for ietf@megatron.ietf.org; Fri, 25 Jun 2004 18:37:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18770
	for <ietf@ietf.org>; Fri, 25 Jun 2004 18:37:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BdzKD-0002AE-9E
	for ietf@ietf.org; Fri, 25 Jun 2004 18:37:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BdzJK-0001te-00
	for ietf@ietf.org; Fri, 25 Jun 2004 18:36:43 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12) id 1BdzIR-0001ar-00
	for ietf@ietf.org; Fri, 25 Jun 2004 18:35:47 -0400
Received: from f01v-20-27.d0.club-internet.fr ([212.195.245.27]
	helo=jfc2.jefsey.com) by montage.altserver.com with esmtp (Exim 4.34)
	id 1BdzIE-0000kA-T5; Fri, 25 Jun 2004 15:35:37 -0700
Message-Id: <6.1.1.1.2.20040626002302.048c3d70@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Sat, 26 Jun 2004 00:52:43 +0200
To: Valdis.Kletnieks@vt.edu
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <200406252039.i5PKdvxC007954@turing-police.cc.vt.edu>
References: <C79A4EF1-C558-11D8-A349-000A95CD987A@muada.com>
	<Pine.LNX.4.44.0406250509260.523-100000@sleekfreak.ath.cx>
	<6.1.1.1.2.20040625213945.05136980@mail.jefsey.com>
	<200406252039.i5PKdvxC007954@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 - jefsey.com
Cc: ietf@ietf.org
Subject: Re: Is the IANA a function performed by ICANN ? 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

At 22:39 25/06/04, Valdis.Kletnieks@vt.edu wrote:
>IANA and the ccNSO/ccTLD are two different beasts.

hmmm. They seem now to be both ICANN stuff. This is the point.

>ccNSO and company keep track of what NS records are authoritative for what 
>zones.

Happily not (most of the ccTLD would not like it !!!). This is a IANA job. 
At least until Monday.
Then it seems it will be an ICANN job, under IANA trade name.

>IANA  keeps track of things like the fact that HTTP is port 80, and which 
>DHCP options use what numbers, and the like.

We agree. And this Internet Assigned Numbers Authority (IANA) is a function 
performed by ICANN.

Is IETF OK with that? I understood that the "functions of the IANA" were 
_currently_ supported under contract by ICANN. I have no position on this. 
I just want to understand where IANA fits in the intergovernance.

I quoted ccTLDs and RIRs because they both expressed concerns about ICANN 
still being around three years from now. There is the same feeling among 
the @large left-overs. If ICANN closed I would not cry. But if it closed 
the global NIC, a contingency plan would be necessary.

Other countries will certainly initiate such a plan. It is to be supposed 
they will mirror ICANN numbers for a while, but they may also introduce 
their additional ones for many reasons (testing [cf. ICP-3], national 
needs, etc.  ). OK with me as long as they first intergovern a conflict 
resolution system and eventually the resulting distributed global NIC they 
will form.

jfc


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


From ietf-bounces@ietf.org  Fri Jun 25 19:33:35 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20818
	for <ietf-archive@ietf.org>; Fri, 25 Jun 2004 19:33:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Be0CN-0001jh-2b
	for ietf-archive@ietf.org; Fri, 25 Jun 2004 19:33:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Be0BG-0001Qq-00
	for ietf-archive@ietf.org; Fri, 25 Jun 2004 19:32:27 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Be0AE-0000ul-00; Fri, 25 Jun 2004 19:31:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Be067-0004UQ-UE; Fri, 25 Jun 2004 19:27:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdzwv-0008OI-PB
	for ietf@megatron.ietf.org; Fri, 25 Jun 2004 19:17:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20380
	for <ietf@ietf.org>; Fri, 25 Jun 2004 19:17:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bdzwu-0005HH-Bf
	for ietf@ietf.org; Fri, 25 Jun 2004 19:17:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bdzvz-00050i-00
	for ietf@ietf.org; Fri, 25 Jun 2004 19:16:40 -0400
Received: from p2.cavebear.com ([199.184.128.35])
	by ietf-mx with esmtp (Exim 4.12) id 1BdzvN-0004hi-00
	for ietf@ietf.org; Fri, 25 Jun 2004 19:16:01 -0400
Received: from npax.cavebear.com (npax.cavebear.com [192.203.17.71])
	by p2.cavebear.com (8.12.10/8.12.10) with SMTP id i5PNFQf4028282
	for <ietf@ietf.org>; Fri, 25 Jun 2004 16:15:26 -0700
Received: from npax.cavebear.com (localhost.localdomain [127.0.0.1])
	by npax.cavebear.com (8.12.10/8.12.10) with ESMTP id i5PNFQDB027011
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ietf@ietf.org>; Fri, 25 Jun 2004 16:15:26 -0700
Received: (from karl@localhost)
	by npax.cavebear.com (8.12.10/8.12.10/Submit) id i5PNFQMM027009
	for ietf@ietf.org; Fri, 25 Jun 2004 16:15:26 -0700
Received: by npax.cavebear.com (tmda-sendmail, from uid 2000);
	Fri, 25 Jun 2004 16:15:25 -0700 (PDT)
Date: Fri, 25 Jun 2004 16:15:25 -0700 (PDT)
To: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <6.1.1.1.2.20040625213945.05136980@mail.jefsey.com>
Message-ID: <Pine.LNX.4.60.0406251457210.22273@npax.cavebear.com>
References: <C79A4EF1-C558-11D8-A349-000A95CD987A@muada.com>
	<Pine.LNX.4.44.0406250509260.523-100000@sleekfreak.ath.cx>
	<6.1.1.1.2.20040625213945.05136980@mail.jefsey.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew)
From: Karl Auerbach <karl@cavebear.com>
Cc: ietf@ietf.org
Subject: Re: Is the IANA a function performed by ICANN ?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Karl Auerbach <karl@cavebear.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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


On Fri, 25 Jun 2004, JFC (Jefsey) Morfin wrote:

> My understanding was that IANA is a neutral, independent, technical 
> authority

> "the Internet Assigned Numbers Authority (IANA) is a function performed by 
> ICANN".

There is a significant lack of clarity in these matters.

ICANN has a number of legal arrangements with the US Dept of Commerce and 
its subagencies.  The most relevant to IANA is a sole-source purchase 
order that comes from the National Atmospheric and Oceanic Administration 
(a sub-agency of the DoC) under which NOAA is purchasing an essentially 
undefined thing called the IANA function and ICANN is providing that thing 
for zero dollars.

Usually in a purchase order the flow of deliverables runs towards the 
purchasor.  In this case nothing particularly tangible flows towards the 
NOAA, but there does seem to be a rather cloudy delegation of authority 
from NOAA to ICANN.  In addition there is the oft-asked and never answered 
question of whether NOAA (or NTIA, another sub-agency of the Dept of 
Commerce) has such authority to delegate in the first place.  (The GAO did 
examine that question and found the authority to be lacking.)

In any event, what commeth via purchase order can goeth via the lapse of 
that purchase order.  Unless there is some unwritten accord, ICANN has no 
guarantee that it will continue to be able to act as the uncompeted, 
sole-source provider of the IANA function.

The IANA function as practiced by ICANN appears to have at several 
distinct parts:

1) The operation of the L root server.  I have never heard one bad 
word about ICANN's performance with respect to the L server  As far 
as I can tell, the hands on those knobs are very competent.

2) The assignment and recordation of "protocol numbers".  This is the 
classical Numbers Czar function.  Again, this seems to be competently 
handled, although I have heard complaints that processing of number 
assignments is taking too long.  And I have had my own concern that this 
function is really something that more properly belongs under the IETF's 
umbrella.

3) ccTLD assignment authority.  This is the controversial function.  This 
is a job that requires IANA to decide who gets to act as the internet 
presence of each sovereign nation (that is, each sovereign nation except 
the US - US dealt with the .us TLD outside of ICANN and despite ICANN.)

Yes, there are competing theories of whether a ccTLD is a direct aspect of 
sovreignty or is merely a database key that happens to be isomorphic with, 
but not dependent upon, the existance of soverign states.  My own sense is 
that the latter theory is not flying well among the collective governments 
of the world.

ICANN does not keep time cards, or at least it didn't when I last checked. 
And there is a great intermingling of tasks among the ICANN/IANA staff. 
These two aspects combine to make it very difficult to assign a 
quantitiative cost or level-of-effort number to IANA as a whole and much 
less to the distinct IANA tasks.

However, by observation it appears that the bulk of the cost, and trouble, 
of IANA is in item #3.

I have had concern that ICANN, or rather IANA, is being used as a pawn by 
political factions in a number of countries.  ICANN's redelegations are 
often based on fairly thin bodies of evidence and are supported often by 
some rather questionable assertions (e.g. a letter relinquishing a ccTLD 
that was on an otherwise blank sheet of paper without letterhead and over 
the unverified signature of someone claiming to be the long lost contact.)

During my term I never felt that ICANN or IANA had the staff expertise to 
be able to swim in those shark infested waters.  However, my sense is that 
with the advent of current president and other staff changes that ICANN, 
oops, IANA, is perhaps better equipped for this now than it was 18 months 
ago.  But the question is still present: Might not the question of who is 
the most rightful operator of a ccTLD be better handled by existing 
organizations that are much more sophisticated in matters pertaining to 
who is the rightful sovereign power of a nation?

 		--karl--







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


From ietf-bounces@ietf.org  Fri Jun 25 20:06:30 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21929
	for <ietf-archive@ietf.org>; Fri, 25 Jun 2004 20:06:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Be0iE-0002u2-7E
	for ietf-archive@ietf.org; Fri, 25 Jun 2004 20:06:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Be0hI-0002e6-00
	for ietf-archive@ietf.org; Fri, 25 Jun 2004 20:05:33 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Be0gS-000286-00; Fri, 25 Jun 2004 20:04:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Be0Zk-0000Hx-TZ; Fri, 25 Jun 2004 19:57:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Be0Tj-0006X3-Vy
	for ietf@megatron.ietf.org; Fri, 25 Jun 2004 19:51:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21397
	for <ietf@ietf.org>; Fri, 25 Jun 2004 19:51:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Be0Ti-0006YK-HM
	for ietf@ietf.org; Fri, 25 Jun 2004 19:51:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Be0Sm-0006Hw-00
	for ietf@ietf.org; Fri, 25 Jun 2004 19:50:33 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212]
	helo=newdev.harvard.edu) by ietf-mx with esmtp (Exim 4.12)
	id 1Be0Rq-0005lX-00
	for ietf@ietf.org; Fri, 25 Jun 2004 19:49:34 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 1B7CA292896; Fri, 25 Jun 2004 19:49:00 -0400 (EDT)
To: ietf@ietf.org, jefsey@jefsey.com
In-Reply-To: <6.1.1.1.2.20040625213945.05136980@mail.jefsey.com>
Message-Id: <20040625234900.1B7CA292896@newdev.harvard.edu>
Date: Fri, 25 Jun 2004 19:49:00 -0400 (EDT)
From: sob@harvard.edu (Scott Bradner)
Subject: Re: Is the IANA a function performed by ICANN ?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

see RFC 2860

Scott

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


From ietf-bounces@ietf.org  Sat Jun 26 13:51:20 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20767
	for <ietf-archive@ietf.org>; Sat, 26 Jun 2004 13:51:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BeHKi-00017r-Ac
	for ietf-archive@ietf.org; Sat, 26 Jun 2004 13:51:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BeHJm-0000tk-00
	for ietf-archive@ietf.org; Sat, 26 Jun 2004 13:50:22 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BeHJR-0000fW-00; Sat, 26 Jun 2004 13:50:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BeHCU-0002Va-Mi; Sat, 26 Jun 2004 13:42:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BeH69-0000Jx-1t
	for ietf@megatron.ietf.org; Sat, 26 Jun 2004 13:36:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20207
	for <ietf@ietf.org>; Sat, 26 Jun 2004 13:36:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BeH68-0005Kr-40
	for ietf@ietf.org; Sat, 26 Jun 2004 13:36:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BeH5C-00056w-00
	for ietf@ietf.org; Sat, 26 Jun 2004 13:35:19 -0400
Received: from mail6.atl.registeredsite.com ([64.224.219.80] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12) id 1BeH4K-0004sK-00
	for ietf@ietf.org; Sat, 26 Jun 2004 13:34:24 -0400
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail6.atl.registeredsite.com (8.12.11/8.12.8) with ESMTP id
	i5QHYNEF032499; Sat, 26 Jun 2004 17:34:23 GMT
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ;
	Sat, 26 Jun 2004 12:34:20 -0500
Message-ID: <40DDB388.7010906@nma.com>
Date: Sat, 26 Jun 2004 10:34:00 -0700
From: Ed Gerck <egerck@nma.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: shogunx <shogunx@sleekfreak.ath.cx>
References: <Pine.LNX.4.44.0406250509260.523-100000@sleekfreak.ath.cx>
In-Reply-To: <Pine.LNX.4.44.0406250509260.523-100000@sleekfreak.ath.cx>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, ietf@ietf.org
Subject: Re: non-solution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



shogunx wrote:

> On Wed, 23 Jun 2004, Iljitsch van Beijnum wrote:
> 
> 
>>On 23-jun-04, at 3:54, Ed Gerck wrote:
>>
>>
>>>Of course, I still believe that insisting in only using the email
>>>for communications and screaming "bloody murder" when it does not
>>>work for some reason, at some time, is very un-Internet. If you want
>>>only a single path, you have to live with the resulting single point of
>>>failure. Allowing web-based messages in addition to email is a simple
>>>and cost-effective way to provide redundancy and reduce the importance
>>>of problems such as reported by Anderson.
>>
>>The IETF has used email as its primary method of conducting its
>>business for almost 20 years. The IETF is also in charge of all the
>>relevant standards. So if email doesn't work, I think the IETF should
>>fix it rather than come up with ad-hoc additional communication
>>mechanisms that have more than enough problems of their own.
> 
> 
> I am in agreement that the mailing list mechanism should not be
> tampered with... it works, so don't break it. 

What I suggested could easily and seamlessly merge with the mailing
list, as an email that was received by a web interface.

BTW, I'm glad you are in the first phase of problem solving -- denial.
I'm suggesting we move to the second phase -- investigate options to
solve the problem.



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


From ietf-bounces@ietf.org  Sat Jun 26 14:13:22 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21496
	for <ietf-archive@ietf.org>; Sat, 26 Jun 2004 14:13:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BeHg2-0006MJ-U2
	for ietf-archive@ietf.org; Sat, 26 Jun 2004 14:13:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BeHf5-00067o-00
	for ietf-archive@ietf.org; Sat, 26 Jun 2004 14:12:24 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BeHej-0005tS-00; Sat, 26 Jun 2004 14:12:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BeHZq-0007HW-0e; Sat, 26 Jun 2004 14:06:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BeHMc-0004FD-0f
	for ietf@megatron.ietf.org; Sat, 26 Jun 2004 13:53:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20818
	for <ietf@ietf.org>; Sat, 26 Jun 2004 13:53:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BeHMa-0001c7-RW
	for ietf@ietf.org; Sat, 26 Jun 2004 13:53:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BeHLc-0001Mh-00
	for ietf@ietf.org; Sat, 26 Jun 2004 13:52:17 -0400
Received: from user-0c6s11v.cable.mindspring.com ([24.110.4.63]
	helo=sleekfreak.ath.cx) by ietf-mx with esmtp (Exim 4.12)
	id 1BeHKb-000172-00
	for ietf@ietf.org; Sat, 26 Jun 2004 13:51:13 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1BeCgC-0001Fk-00; Sat, 26 Jun 2004 08:53:13 -0400
Date: Sat, 26 Jun 2004 08:53:07 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Ed Gerck <egerck@nma.com>
In-Reply-To: <40DDB388.7010906@nma.com>
Message-ID: <Pine.LNX.4.44.0406260851020.4805-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, ietf@ietf.org
Subject: Re: non-solution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=2.0 required=5.0 tests=AWL,WEIRD_PORT autolearn=no 
	version=2.60

On Sat, 26 Jun 2004, Ed Gerck wrote:

>
>
> shogunx wrote:
>
> > On Wed, 23 Jun 2004, Iljitsch van Beijnum wrote:
> >
> >
> >>On 23-jun-04, at 3:54, Ed Gerck wrote:
> >>
> >>
> >>>Of course, I still believe that insisting in only using the email
> >>>for communications and screaming "bloody murder" when it does not
> >>>work for some reason, at some time, is very un-Internet. If you want
> >>>only a single path, you have to live with the resulting single point of
> >>>failure. Allowing web-based messages in addition to email is a simple
> >>>and cost-effective way to provide redundancy and reduce the importance
> >>>of problems such as reported by Anderson.
> >>
> >>The IETF has used email as its primary method of conducting its
> >>business for almost 20 years. The IETF is also in charge of all the
> >>relevant standards. So if email doesn't work, I think the IETF should
> >>fix it rather than come up with ad-hoc additional communication
> >>mechanisms that have more than enough problems of their own.
> >
> >
> > I am in agreement that the mailing list mechanism should not be
> > tampered with... it works, so don't break it.
>
> What I suggested could easily and seamlessly merge with the mailing
> list, as an email that was received by a web interface.
>

What are you suggesting, a web-based archive of list traffic and a form on
a website to post to ietf lists?


> BTW, I'm glad you are in the first phase of problem solving -- denial.
> I'm suggesting we move to the second phase -- investigate options to
> solve the problem.
>

Please define the problem that you are attempting to solve.


>
>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


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


From ietf-bounces@ietf.org  Sat Jun 26 14:19:29 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21765
	for <ietf-archive@ietf.org>; Sat, 26 Jun 2004 14:19:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BeHlx-0000B4-R0
	for ietf-archive@ietf.org; Sat, 26 Jun 2004 14:19:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BeHl7-0007h2-00
	for ietf-archive@ietf.org; Sat, 26 Jun 2004 14:18:38 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BeHkE-0007KF-00; Sat, 26 Jun 2004 14:17:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BeHav-0007Xx-E2; Sat, 26 Jun 2004 14:08:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BeHVN-0006Oj-GC
	for ietf@megatron.ietf.org; Sat, 26 Jun 2004 14:02:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21231
	for <ietf@ietf.org>; Sat, 26 Jun 2004 14:02:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BeHVM-0003nv-Hb
	for ietf@ietf.org; Sat, 26 Jun 2004 14:02:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BeHUQ-0003Zx-00
	for ietf@ietf.org; Sat, 26 Jun 2004 14:01:22 -0400
Received: from mail4.atl.registeredsite.com ([64.224.219.78] ident=nobody)
	by ietf-mx with esmtp (Exim 4.12) id 1BeHTl-0003Lp-00
	for ietf@ietf.org; Sat, 26 Jun 2004 14:00:41 -0400
Received: from taurus.hosting4u.net (taurus.hosting4u.net [209.35.191.122])
	by mail4.atl.registeredsite.com (8.12.11/8.12.8) with ESMTP id
	i5QI0cqj021243; Sat, 26 Jun 2004 18:00:39 GMT
Received: from nma.com ([63.204.17.85]) by taurus.hosting4u.net ;
	Sat, 26 Jun 2004 13:00:37 -0500
Message-ID: <40DDB9AD.4070608@nma.com>
Date: Sat, 26 Jun 2004 11:00:13 -0700
From: Ed Gerck <egerck@nma.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: shogunx <shogunx@sleekfreak.ath.cx>
References: <Pine.LNX.4.44.0406260851020.4805-100000@sleekfreak.ath.cx>
In-Reply-To: <Pine.LNX.4.44.0406260851020.4805-100000@sleekfreak.ath.cx>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, ietf@ietf.org
Subject: Re: non-solution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=1.0 required=5.0 tests=AWL,WEIRD_PORT autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

to save trees, please read my past messages here, the answers are there.
Thanks.

shogunx wrote:

> On Sat, 26 Jun 2004, Ed Gerck wrote:
> 
> 
>>
>>shogunx wrote:
>>
>>
>>>On Wed, 23 Jun 2004, Iljitsch van Beijnum wrote:
>>>
>>>
>>>
>>>>On 23-jun-04, at 3:54, Ed Gerck wrote:
>>>>
>>>>
>>>>
>>>>>Of course, I still believe that insisting in only using the email
>>>>>for communications and screaming "bloody murder" when it does not
>>>>>work for some reason, at some time, is very un-Internet. If you want
>>>>>only a single path, you have to live with the resulting single point of
>>>>>failure. Allowing web-based messages in addition to email is a simple
>>>>>and cost-effective way to provide redundancy and reduce the importance
>>>>>of problems such as reported by Anderson.
>>>>
>>>>The IETF has used email as its primary method of conducting its
>>>>business for almost 20 years. The IETF is also in charge of all the
>>>>relevant standards. So if email doesn't work, I think the IETF should
>>>>fix it rather than come up with ad-hoc additional communication
>>>>mechanisms that have more than enough problems of their own.
>>>
>>>
>>>I am in agreement that the mailing list mechanism should not be
>>>tampered with... it works, so don't break it.
>>
>>What I suggested could easily and seamlessly merge with the mailing
>>list, as an email that was received by a web interface.
>>
> 
> 
> What are you suggesting, a web-based archive of list traffic and a form on
> a website to post to ietf lists?
> 
> 
> 
>>BTW, I'm glad you are in the first phase of problem solving -- denial.
>>I'm suggesting we move to the second phase -- investigate options to
>>solve the problem.
>>
> 
> 
> Please define the problem that you are attempting to solve.
> 
> 
> 
>>
> 
> sleekfreak pirate broadcast
> http://sleekfreak.ath.cx:81/
> 
> 
> 
> 

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


From ietf-bounces@ietf.org  Sat Jun 26 15:55:23 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26125
	for <ietf-archive@ietf.org>; Sat, 26 Jun 2004 15:55:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BeJGl-0007I0-OK
	for ietf-archive@ietf.org; Sat, 26 Jun 2004 15:55:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BeJFq-0006zz-00
	for ietf-archive@ietf.org; Sat, 26 Jun 2004 15:54:27 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BeJEs-0006Uh-00; Sat, 26 Jun 2004 15:53:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BeJAe-0006aX-FH; Sat, 26 Jun 2004 15:49:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BeJ3B-0004ki-TI
	for ietf@megatron.ietf.org; Sat, 26 Jun 2004 15:41:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25385
	for <ietf@ietf.org>; Sat, 26 Jun 2004 15:41:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BeJ3A-0003cZ-Ks
	for ietf@ietf.org; Sat, 26 Jun 2004 15:41:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BeJ2G-0003OM-00
	for ietf@ietf.org; Sat, 26 Jun 2004 15:40:25 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12) id 1BeJ1S-000397-00
	for ietf@ietf.org; Sat, 26 Jun 2004 15:39:34 -0400
Received: from f01m-23-252.d0.club-internet.fr ([212.195.224.252]
	helo=jfc2.jefsey.com) by montage.altserver.com with esmtp (Exim 4.34)
	id 1BeJ1E-0008Mu-KG; Sat, 26 Jun 2004 12:39:24 -0700
Message-Id: <6.1.1.1.2.20040626161224.06ab4eb0@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Sat, 26 Jun 2004 20:25:01 +0200
To: ietf@ietf.org
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <20040625234900.1B7CA292896@newdev.harvard.edu>
References: <6.1.1.1.2.20040625213945.05136980@mail.jefsey.com>
	<20040625234900.1B7CA292896@newdev.harvard.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 - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
Subject: Re: Is the IANA a function performed by ICANN ?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

At 01:49 26/06/04, Scott Bradner wrote:
>see RFC 2860

Dear Scott and Karl,
thank you for your comments. I explain. I consider the interest of a draft 
on the digital intergovernance I do not know yet if I want to undertake 
such a task, how, with who, and where. I established a site 
(http://intergovenance.org) to gather inputs from different authorities (I 
play it low key as it could be too big a project if not worked in parallel 
with SIS). The idea I float is to extend and generalize RFC 920/1591 from 
ARPA Internet, to Internet, to current inter-digital-network-convergence. 
Mixing past, experience, specifics and future of the different technologies 
towards a coherent model of the digital ecosystem and of its usage. From 
bandwidth to users technical aspects. Not by who does what, but by what is 
needed and how it is best performed.

A basic need is for a generalized e-networks lexical and 
theory/modelization. Nothing fancy. What we do all the day long, but put 
into a single structured document from telecoms, to datacoms, to 
communication services. Analyzed for what they should do, not for history 
or what they currently do.

There, there is a need for a neutral, stable, reference "system". Until 
now, this was thought as a "center" in the global network governance. For 
many reasons (risk containment, sovereignty, experimentation, operational 
flexibility, cybernetic warfare, economic intelligence, etc.) such 
"centers" in network horizontal governances must become a concerted 
specialized vertical governance within the intergovernance of the 
inter-networks/technology/systems/services/usages/etc. Also, there is a 
clear "law": if one wants to keep an intergoverned system under a single 
governance, that governance will either obsolete (ITU?) or become a 
dominance (ICANN?), both being discarded (an intergovernance does not 
fight, it circumvents).

So, the future is clear. It is made of a IANA network concerted system for 
the very large diversity of names and numbers used for network 
interoperations and users interapplications. One "IANA" centers per 
country, region, sector, culture, city, etc. down to private ones. They 
will provide the ubiquitous e-continuity metastructure. Each horizontal 
thematic intergovernance (DNS, numbering, geonumeric bases, formats, etc; 
etc. ) will have to devise their ways to keep their global information 
matrix consistent - or to restore its consistency after a dysfunction, an 
attack or a sovereign zone take-over for critical reasons. ICP-3 of ICANN 
is a good introduction to this effort in the DNS area.

There are two good ways and a bad one to reach this from the today situation.

- good 1. the current IANA multinationalize/multilingualize/multitechnoloze 
into it. This looks unrealistic but matching IETF "core values". IETF 
already coped with other unrealistic challenges. ccTLDs could be a good 
existing supporting structure. But users support (@large) would be needed 
to establish it. IETF would have the lead.

- good 2. IANA becomes a part of ICANN. ICANN is increasingly perceived as 
an USG agency. So, the common international practices apply. Some countries 
(ccNSO) want to keep using it. Some others will create their regional, 
national governance structures and bodies. This will be good for QoS 
through competition. ITU will probably then be the best solution, if it 
creates an ITU-I Sector.

- bad one. to mix them both to impose an ICANN governance. This cannot 
technically work on medium/long term. A dominance does not fit in a 
distributed system. This will create an increasing instability and will be 
circumvented by usage and real world intergovernance. The bodies associated 
with the dominance will probably be discarded. RIRs have understood that. 
Most of the ccTLDs too.

Let be clear. I do not speak of short term political instability. But of 
very long term architectural instability. To understand this let recall 
that positions taken in minutes as obvious in 1984 are the ruling the way 
the name space works today. We all know the difficulty of making move the 
inter-networked system, ex.: IPv6. Today 88% of the mankind does not use 
the Internet. Also 88% of them are neither EU/US citizens.

If 70% of the mankind was connected in a decade, the increase would be 
150%. If 2/3 of the new comers adopted one different parameters in an area 
(for example to get ML.ML denied by ICANN, or a different no spam mail 
system, or a different DNS RR,) we would have the same number of users than 
today (800 millions) using that solutions. We know the compatibility 
difficulty for IPv6, the threat of alt.roots for some: we would have to 
increasingly live for ever with this kind of problems. I have no doubt that 
natural evolution will correct IANA possible mishandling over the next 
century - the same as sometime the whole network will be IPv6, the naming 
multilingual, etc. But in the meanwhile?

Scott, I did not quote RFCs because on the grounds above.

1. RFC 2468 comes before. With a substantial with "a function performed by 
ICANN".

2. RFC 2860's is only the technical work of the IANA. Not on its 
architectural nor on its intergovernance aspects. It signed by Fred Baker 
showing that IETF is the one delegating (with silent IAB), hence my 
question to IETF. The given IANA definition is: "Internet Assigned Numbers 
Authority (a traditional name, used here to refer to the technical team 
making and publishing the assignments of Internet protocol technical 
parameters). The IANA technical team is now part of ICANN"

This refers to:
- a group of people identified as such, not to a function.
- this is a bilateral hosting agreement. Not an assimilation.
It does not match either "a function performed by ICANN".

Karl, your technical and legal points are well made. But let be candid: 
outside of a very few ICANN/IETF and g/s/ccTLD group of people, who cares 
about the NOAA Internet? This may certainly have a technical impact because 
someone with technical responsibilities in ICANN or IETF is affected. But 
this would be a bug to correct. Not something to keep, not even to discuss.
jfc







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


From ietf-bounces@ietf.org  Sat Jun 26 16:09:26 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27099
	for <ietf-archive@ietf.org>; Sat, 26 Jun 2004 16:09:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BeJUM-0003Kp-Qc
	for ietf-archive@ietf.org; Sat, 26 Jun 2004 16:09:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BeJTS-00036H-00
	for ietf-archive@ietf.org; Sat, 26 Jun 2004 16:08:31 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BeJSu-0002qX-00; Sat, 26 Jun 2004 16:07:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BeJOs-000263-C7; Sat, 26 Jun 2004 16:03:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BeJDx-0007Un-KN
	for ietf@megatron.ietf.org; Sat, 26 Jun 2004 15:52:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25946
	for <ietf@ietf.org>; Sat, 26 Jun 2004 15:52:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BeJDw-0006U9-Bt
	for ietf@ietf.org; Sat, 26 Jun 2004 15:52:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BeJDL-0006FN-00
	for ietf@ietf.org; Sat, 26 Jun 2004 15:51:51 -0400
Received: from user-0c6s11v.cable.mindspring.com ([24.110.4.63]
	helo=sleekfreak.ath.cx) by ietf-mx with esmtp (Exim 4.12)
	id 1BeJCU-0005z1-00
	for ietf@ietf.org; Sat, 26 Jun 2004 15:50:59 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1BeET0-0001JX-00; Sat, 26 Jun 2004 10:47:42 -0400
Date: Sat, 26 Jun 2004 10:47:14 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Ed Gerck <egerck@nma.com>
In-Reply-To: <40DDB9AD.4070608@nma.com>
Message-ID: <Pine.LNX.4.44.0406261041001.5032-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, ietf@ietf.org
Subject: Re: non-solution
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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=2.0 required=5.0 tests=AWL,WEIRD_PORT autolearn=no 
	version=2.60

seems like the problem is poor signal to noise ratio.
i'm not sure that will be solved by quick and easy web interface to noise
creation.  do we have an easy route to communicate with the spammers?
like posting on this list?  if they are spamming, then they are also
watching and giggling.  if so, perhaps we could ask them a few things;
"what do you want?", "do you have a question?", and "does your mother know
what you are doing?" come to mind.

scott

On Sat, 26 Jun 2004, Ed Gerck wrote:

> to save trees, please read my past messages here, the answers are there.
> Thanks.
>
> shogunx wrote:
>
> > On Sat, 26 Jun 2004, Ed Gerck wrote:
> >
> >
> >>
> >>shogunx wrote:
> >>
> >>
> >>>On Wed, 23 Jun 2004, Iljitsch van Beijnum wrote:
> >>>
> >>>
> >>>
> >>>>On 23-jun-04, at 3:54, Ed Gerck wrote:
> >>>>
> >>>>
> >>>>
> >>>>>Of course, I still believe that insisting in only using the email
> >>>>>for communications and screaming "bloody murder" when it does not
> >>>>>work for some reason, at some time, is very un-Internet. If you want
> >>>>>only a single path, you have to live with the resulting single point of
> >>>>>failure. Allowing web-based messages in addition to email is a simple
> >>>>>and cost-effective way to provide redundancy and reduce the importance
> >>>>>of problems such as reported by Anderson.
> >>>>
> >>>>The IETF has used email as its primary method of conducting its
> >>>>business for almost 20 years. The IETF is also in charge of all the
> >>>>relevant standards. So if email doesn't work, I think the IETF should
> >>>>fix it rather than come up with ad-hoc additional communication
> >>>>mechanisms that have more than enough problems of their own.
> >>>
> >>>
> >>>I am in agreement that the mailing list mechanism should not be
> >>>tampered with... it works, so don't break it.
> >>
> >>What I suggested could easily and seamlessly merge with the mailing
> >>list, as an email that was received by a web interface.
> >>
> >
> >
> > What are you suggesting, a web-based archive of list traffic and a form on
> > a website to post to ietf lists?
> >
> >
> >
> >>BTW, I'm glad you are in the first phase of problem solving -- denial.
> >>I'm suggesting we move to the second phase -- investigate options to
> >>solve the problem.
> >>
> >
> >
> > Please define the problem that you are attempting to solve.
> >
> >
> >
> >>
> >
> > sleekfreak pirate broadcast
> > http://sleekfreak.ath.cx:81/
> >
> >
> >
> >
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


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


From ietf-bounces@ietf.org  Mon Jun 28 20:25:43 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26472
	for <ietf-archive@ietf.org>; Mon, 28 Jun 2004 20:25:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1Bf6RT-0005hI-Bq
	for ietf-archive@ietf.org; Mon, 28 Jun 2004 20:25:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bf6QX-0005RF-00
	for ietf-archive@ietf.org; Mon, 28 Jun 2004 20:24:46 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Bf6Q3-0005B9-00; Mon, 28 Jun 2004 20:24:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bf6Kz-00036o-UJ; Mon, 28 Jun 2004 20:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bf6Gr-0002Xf-Mj
	for ietf@megatron.ietf.org; Mon, 28 Jun 2004 20:14:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25889
	for <ietf@ietf.org>; Mon, 28 Jun 2004 20:14:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bf6Gq-0002iL-6A
	for ietf@ietf.org; Mon, 28 Jun 2004 20:14:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bf6Fr-0002SV-00
	for ietf@ietf.org; Mon, 28 Jun 2004 20:13:44 -0400
Received: from fmr12.intel.com ([134.134.136.15] helo=orsfmr001.jf.intel.com)
	by ietf-mx with esmtp (Exim 4.12) id 1Bf6FS-0002Cj-00
	for ietf@ietf.org; Mon, 28 Jun 2004 20:13:18 -0400
Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6])
	by orsfmr001.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-outer.mc,
	v 1.15 2004/01/30 18:16:28 root Exp $) with ESMTP id i5SHCLKB017392
	for <ietf@ietf.org>; Mon, 28 Jun 2004 17:13:00 GMT
Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com
	[192.168.65.54])
	by petasus.jf.intel.com (8.12.9-20030918-01/8.12.9/d: major-inner.mc,
	v 1.10 2004/03/01 19:21:36 root Exp $) with SMTP id i5T0DR56022906
	for <ietf@ietf.org>; Tue, 29 Jun 2004 00:13:31 GMT
Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60])
	by orsmsxvs041.jf.intel.com (SAVSMTP 3.1.2.35) with SMTP id
	M2004062817120014812
	for <ietf@ietf.org>; Mon, 28 Jun 2004 17:12:00 -0700
Received: from orsmsx407.amr.corp.intel.com ([192.168.65.50]) by
	orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0);
	Mon, 28 Jun 2004 17:11:53 -0700
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="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 28 Jun 2004 17:11:52 -0700
Message-ID: <66539F0E7F15B44C9C0FC50D0FF024F7C6B1EF@orsmsx407>
Thread-Topic: RFC 3164 i.e. BSD Syslog Protocol
thread-index: AcRdba4l3bKIqbMkQla0ZtxSkJfCAg==
From: "Sabharwal, Atul" <atul.sabharwal@intel.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 29 Jun 2004 00:11:54.0251 (UTC)
	FILETIME=[AF070DB0:01C45D6D]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
Content-Transfer-Encoding: quoted-printable
Cc: "Lynch, Rusty" <rusty.lynch@intel.com>
Subject: RFC 3164 i.e. BSD Syslog Protocol
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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

RFC 3164 i.e. the BSD Syslog protocol allows a client to send multiple
datagrams to different
Hosts. In a clustered environment, datagrams can be lost. Has anyone
considered using a=20
IP multicast socket for sending messages to multiple hosts ? Is there a
draft proposal
In this regard. Also, as I understand, there is no retransmisson support
like in SNMP.

Any comments or suggestions would be welcome.

Thanks,

Atul

-------------------------------------------------------------
P.S:  All opinions are my personal opinion(s) & responsibility and do
not represent the view of my employer ( Intel Corporation ).


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


From ietf-bounces@ietf.org  Wed Jun 30 15:19:40 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08533
	for <ietf-archive@ietf.org>; Wed, 30 Jun 2004 15:19:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BfkcO-0002Cu-Mk
	for ietf-archive@ietf.org; Wed, 30 Jun 2004 15:19:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BfkbK-0001mF-00
	for ietf-archive@ietf.org; Wed, 30 Jun 2004 15:18:35 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BfkaC-0000zg-00; Wed, 30 Jun 2004 15:17:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BfkUK-00070V-BB; Wed, 30 Jun 2004 15:11:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BfWO2-0000ri-Sb
	for ietf@megatron.ietf.org; Wed, 30 Jun 2004 00:07:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19155
	for <ietf@ietf.org>; Wed, 30 Jun 2004 00:07:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BfWO0-00024x-Uh
	for ietf@ietf.org; Wed, 30 Jun 2004 00:07:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BfWN5-0001hk-00
	for ietf@ietf.org; Wed, 30 Jun 2004 00:06:56 -0400
Received: from smtp.spamarrest.com ([66.150.163.174] helo=spamarrest.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BfWMX-0001JL-00; Wed, 30 Jun 2004 00:06:21 -0400
Received: from [66.188.121.188] (account vanderhe@smtp.spamarrest.com HELO
	NC6000BAK) by spamarrest.com (CommuniGate Pro SMTP 4.2b1)
	with ESMTP id 6723923; Tue, 29 Jun 2004 21:05:51 -0700
From: "Gregg Vanderheiden" <gv@trace.wisc.edu>
To: <iesg@ietf.org>, <ietf@ietf.org>
Date: Tue, 29 Jun 2004 23:05:46 -0500
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-index: AcReVziugQS8sMy5S+aWLQGviq8bHw==
Message-ID: <auto-000006723923@spamarrest.com>
X-Mailman-Approved-At: Wed, 30 Jun 2004 15:11:18 -0400
Subject: 'Registration of the text/red MIME Sub-Type'
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0838050739=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@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,HTML_70_80,
	HTML_FONTCOLOR_UNKNOWN,HTML_FONT_BIG,HTML_MESSAGE,
	MISSING_OUTLOOK_NAME autolearn=no version=2.60

This is a multi-part message in MIME format.

--===============0838050739==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0040_01C45E2D.9EB81560"

This is a multi-part message in MIME format.

------=_NextPart_000_0040_01C45E2D.9EB81560
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

This doc looks good.

 

It is a much needed development.   

 

thanks

 


Gregg

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

Gregg C Vanderheiden Ph.D. 
Professor - Depts of Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 
< <http://trace.wisc.edu/> http://trace.wisc.edu/> FAX 608/262-8848  
For a list of our list discussions http://trace.wisc.edu/lists/

 <http://trace.wisc.edu:8080/mailman/listinfo/>  

 

 


------=_NextPart_000_0040_01C45E2D.9EB81560
Content-Type: text/html;
	charset="us-ascii"
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:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40"
xmlns:ns0=3D"urn:schemas-microsoft-com:office:smarttags">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Coronet;
	panose-1:3 3 5 2 4 4 6 7 6 5;}
@font-face
	{font-family:"Monotype Corsiva";
	panose-1:3 1 1 1 1 2 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>This doc looks good.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>It is a much needed development.&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>thanks<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
</span></font><font size=3D4 face=3D"Monotype Corsiva"><span =
style=3D'font-size:13.5pt;
font-family:"Monotype Corsiva"'>Gregg</span></font><font size=3D4 =
face=3DCoronet><span
style=3D'font-size:13.5pt;font-family:Coronet'><br>
</span></font><br>
<font size=3D2 face=3DArial><span lang=3DSV =
style=3D'font-size:10.0pt;font-family:Arial'>------------------------</sp=
an></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DSV =
style=3D'font-size:10.0pt;
font-family:Arial'>Gregg C Vanderheiden Ph.D.</span></font><span =
lang=3DSV> <br>
</span><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Professor
- Depts of <ns0:State w:insAuthor=3D"Gregg Vanderheiden"
 w:insDate=3D"2004-06-29T23:01:00Z" w:endInsAuthor=3D"Gregg =
Vanderheiden"
 w:endInsDate=3D"2004-06-29T23:01:00Z"><ns0:place w:insAuthor=3D"Gregg =
Vanderheiden"
  w:insDate=3D"2004-06-29T23:01:00Z" w:endInsAuthor=3D"Gregg =
Vanderheiden"
  w:endInsDate=3D"2004-06-29T23:01:00Z"><st1:State =
w:st=3D"on"><st1:place =
w:st=3D"on">Ind.</st1:place></st1:State></ns0:place></ns0:State>
Engr. &amp; BioMed Engr.<br>
Director - Trace R &amp; D Center</span></font> <br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>University
of Wisconsin-Madison</span></font> <br>
<u><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:blue'>&lt;<a href=3D"http://trace.wisc.edu/" =
target=3D"_blank"><font
face=3D"Times New Roman"><span style=3D'font-family:"Times New =
Roman"'>http://trace.wisc.edu/</span></font></a>&gt;</span></font></u>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>FAX
608/262-8848&nbsp; </span></font><br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>For a
list of our list discussions =
http://trace.wisc.edu/lists/<o:p></o:p></span></font></p>

<p><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><a
href=3D"http://trace.wisc.edu:8080/mailman/listinfo/">&nbsp;<font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></a></span></font></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0040_01C45E2D.9EB81560--



--===============0838050739==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0838050739==--




