From owner-ietf@ietf.org  Thu Apr  1 02:23:05 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22268
	for <ietf-archive@odin.ietf.org>; Thu, 1 Apr 2004 02:23:05 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B8wIy-0003s2-QI
	for ietf-list@asgard.ietf.org; Thu, 01 Apr 2004 02:08:00 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B8wIp-0003rM-MU
	for ietf@asgard.ietf.org; Thu, 01 Apr 2004 02:07:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14462
	for <ietf@ietf.org>; Thu, 1 Apr 2004 02:07:50 -0500 (EST)
From: mallman@grc.nasa.gov
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8wIn-0001CP-00
	for ietf@ietf.org; Thu, 01 Apr 2004 02:07:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8wHo-000192-00
	for ietf@ietf.org; Thu, 01 Apr 2004 02:06:49 -0500
Received: from [61.234.88.195] (helo=ietf.org)
	by ietf-mx with smtp (Exim 4.12)
	id 1B8wGq-000142-00
	for ietf@ietf.org; Thu, 01 Apr 2004 02:05:49 -0500
To: ietf@ietf.org
Subject: information
Date: Thu, 1 Apr 2004 15:08:53 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="07641245"
Message-Id: <E1B8wGq-000142-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.6 required=5.0 tests=MSGID_FROM_MTA_SHORT,
	NO_REAL_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_NETSKY.B in file details.doc.com (in details.zip)
The uncleanable file is deleted.

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

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

you try to steal

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


------------------  Virus Warning Message (on ietf-mx)

details.zip is removed from here because it contains a virus.

---------------------------------------------------------
--07641245--




From exim@www1.ietf.org  Thu Apr  1 02:23:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22328
	for <ietf-archive@odin.ietf.org>; Thu, 1 Apr 2004 02:23:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8wXd-00060o-KR
	for ietf-archive@odin.ietf.org; Thu, 01 Apr 2004 02:23:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i317N9Nu023106
	for ietf-archive@odin.ietf.org; Thu, 1 Apr 2004 02:23:09 -0500
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8wXc-00060b-AM
	for ietf-web-archive@optimus.ietf.org; Thu, 01 Apr 2004 02:23:08 -0500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B8wIy-0003s2-QI
	for ietf-list@asgard.ietf.org; Thu, 01 Apr 2004 02:08:00 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B8wIp-0003rM-MU
	for ietf@asgard.ietf.org; Thu, 01 Apr 2004 02:07:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14462
	for <ietf@ietf.org>; Thu, 1 Apr 2004 02:07:50 -0500 (EST)
From: mallman@grc.nasa.gov
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8wIn-0001CP-00
	for ietf@ietf.org; Thu, 01 Apr 2004 02:07:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8wHo-000192-00
	for ietf@ietf.org; Thu, 01 Apr 2004 02:06:49 -0500
Received: from [61.234.88.195] (helo=ietf.org)
	by ietf-mx with smtp (Exim 4.12)
	id 1B8wGq-000142-00
	for ietf@ietf.org; Thu, 01 Apr 2004 02:05:49 -0500
To: ietf@ietf.org
Subject: information
Date: Thu, 1 Apr 2004 15:08:53 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="07641245"
Message-Id: <E1B8wGq-000142-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.6 required=5.0 tests=MSGID_FROM_MTA_SHORT,
	NO_REAL_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_NETSKY.B in file details.doc.com (in details.zip)
The uncleanable file is deleted.

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

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

you try to steal

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


------------------  Virus Warning Message (on ietf-mx)

details.zip is removed from here because it contains a virus.

---------------------------------------------------------
--07641245--





From mailman-bounces@mailman.isi.edu  Thu Apr  1 08:18:02 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 IAA11114
	for <ietf-archive@ietf.org>; Thu, 1 Apr 2004 08:18:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9257-0000oT-00
	for ietf-archive@ietf.org; Thu, 01 Apr 2004 08:18:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B924B-0000hp-00
	for ietf-archive@ietf.org; Thu, 01 Apr 2004 08:17:08 -0500
Received: from gamma.isi.edu ([128.9.144.145])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B923B-0000aA-00
	for ietf-archive@ietf.org; Thu, 01 Apr 2004 08:16:05 -0500
Received: from gamma.isi.edu (localhost [127.0.0.1])
	by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i31DG4k07655
	for <ietf-archive@ietf.org>; Thu, 1 Apr 2004 05:16:04 -0800 (PST)
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.1882.1080824459.23929.mailman@mailman.isi.edu>
Date: Thu, 01 Apr 2004 05:00:59 -0800
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-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

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  Thu Apr  1 11:37: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 LAA20192
	for <ietf-archive@ietf.org>; Thu, 1 Apr 2004 11:37:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B95C7-0006UK-00
	for ietf-archive@ietf.org; Thu, 01 Apr 2004 11:37:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B957o-0005ay-00
	for ietf-archive@ietf.org; Thu, 01 Apr 2004 11:33:05 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B955G-0004xb-02
	for ietf-archive@ietf.org; Thu, 01 Apr 2004 11:30:26 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B94rt-0004pz-BT
	for ietf-archive@ietf.org; Thu, 01 Apr 2004 11:16:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B94rN-0002Rk-6j
	for ietf-archive@ietf.org; Thu, 01 Apr 2004 11:16:05 -0500
Date: Thu, 01 Apr 2004 11:16:05 -0500
Message-ID: <20040401161605.11029.95649.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-discussion-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-discussion@ietf.org                 nohoot    
https://www1.ietf.org/mailman/options/ietf-discussion/ietf-archive%40ietf.org


From owner-ietf@ietf.org  Thu Apr  1 20:19:44 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17620
	for <ietf-archive@odin.ietf.org>; Thu, 1 Apr 2004 20:19:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9D4E-0007Oc-F7
	for ietf-list@asgard.ietf.org; Thu, 01 Apr 2004 20:01:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9D3s-0007OC-J5
	for ietf@asgard.ietf.org; Thu, 01 Apr 2004 20:01:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15842
	for <ietf@ietf.org>; Thu, 1 Apr 2004 20:01:28 -0500 (EST)
From: kzm@cisco.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9D3r-00061s-00
	for ietf@ietf.org; Thu, 01 Apr 2004 20:01:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9D2z-0005ul-00
	for ietf@ietf.org; Thu, 01 Apr 2004 20:00:37 -0500
Received: from [221.8.16.202] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9D2U-0005oz-00
	for ietf@ietf.org; Thu, 01 Apr 2004 20:00:06 -0500
To: ietf@ietf.org
Subject: what's up?
Date: Fri, 2 Apr 2004 09:00:10 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0003_00001B77.0000432B"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1B9D2U-0005oz-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=5.7 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME 
	autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0003_00001B77.0000432B
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

bob the builder

------=_NextPart_000_0003_00001B77.0000432B
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_0003_00001B77.0000432B--





From owner-ietf@ietf.org  Fri Apr  2 01:44:28 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12229
	for <ietf-archive@odin.ietf.org>; Fri, 2 Apr 2004 01:44:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9IGQ-0001jB-7D
	for ietf-list@asgard.ietf.org; Fri, 02 Apr 2004 01:34:50 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9IGK-0001ic-Jc
	for ietf@asgard.ietf.org; Fri, 02 Apr 2004 01:34:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12070
	for <ietf@ietf.org>; Fri, 2 Apr 2004 01:34:43 -0500 (EST)
From: smb@research.att.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9IGI-0004s1-00
	for ietf@ietf.org; Fri, 02 Apr 2004 01:34:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9IFN-0004ln-00
	for ietf@ietf.org; Fri, 02 Apr 2004 01:33:46 -0500
Received: from [202.88.174.148] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9IEd-0004f2-00
	for ietf@ietf.org; Fri, 02 Apr 2004 01:33:04 -0500
To: ietf@ietf.org
Subject: notification
Date: Fri, 2 Apr 2004 12:04:41 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0010_000069AD.00003EC5"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1B9IEd-0004f2-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=5.7 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME 
	autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0010_000069AD.00003EC5
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

from the chatter (my photo!)

------=_NextPart_000_0010_000069AD.00003EC5
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_0010_000069AD.00003EC5--





From exim@www1.ietf.org  Fri Apr  2 04:06:43 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29907
	for <ietf-archive@odin.ietf.org>; Fri, 2 Apr 2004 04:06:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9GFf-0000p4-01
	for ietf-archive@odin.ietf.org; Thu, 01 Apr 2004 23:25:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i324Psat003156
	for ietf-archive@odin.ietf.org; Thu, 1 Apr 2004 23:25:54 -0500
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9DLY-0005Pt-Mn
	for ietf-web-archive@optimus.ietf.org; Thu, 01 Apr 2004 20:19:48 -0500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9D4E-0007Oc-F7
	for ietf-list@asgard.ietf.org; Thu, 01 Apr 2004 20:01:54 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9D3s-0007OC-J5
	for ietf@asgard.ietf.org; Thu, 01 Apr 2004 20:01:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15842
	for <ietf@ietf.org>; Thu, 1 Apr 2004 20:01:28 -0500 (EST)
From: kzm@cisco.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9D3r-00061s-00
	for ietf@ietf.org; Thu, 01 Apr 2004 20:01:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9D2z-0005ul-00
	for ietf@ietf.org; Thu, 01 Apr 2004 20:00:37 -0500
Received: from [221.8.16.202] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9D2U-0005oz-00
	for ietf@ietf.org; Thu, 01 Apr 2004 20:00:06 -0500
To: ietf@ietf.org
Subject: what's up?
Date: Fri, 2 Apr 2004 09:00:10 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0003_00001B77.0000432B"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1B9D2U-0005oz-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=5.7 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME 
	autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0003_00001B77.0000432B
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

bob the builder

------=_NextPart_000_0003_00001B77.0000432B
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_0003_00001B77.0000432B--






From kvatk@holcim.com  Fri Apr  2 04:48: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 EAA01733
	for <ietf-archive@ietf.org>; Fri, 2 Apr 2004 04:48:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9LII-0003a3-00
	for ietf-archive@ietf.org; Fri, 02 Apr 2004 04:48:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9LHK-0003RW-00
	for ietf-archive@ietf.org; Fri, 02 Apr 2004 04:47:59 -0500
Received: from [68.229.158.138] (helo=132.151.6.1)
	by ietf-mx with smtp (Exim 4.12)
	id 1B9LGj-0003JA-00; Fri, 02 Apr 2004 04:47:21 -0500
Received: from 166.30.220.132 by 68.229.158.138; Fri, 02 Apr 2004 10:47:56 +0100
Message-ID: <GTXGHJBBRWCHIPVKPKJYEIB@erie.net>
From: "Nina Price" <kvatk@holcim.com>
Reply-To: "Nina Price" <kvatk@holcim.com>
To: ietf-announce@ietf.org
Subject: Best Online Drugstore Delivers ANY Meds Overnight. Discreetly. Securely.
Date: Fri, 02 Apr 2004 05:41:56 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--521309044525021"
X-Webmail-Time: Fri, 02 Apr 2004 10:42:56 +0100
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=BIZ_TLD,HTML_50_60,
	HTML_FONTCOLOR_UNSAFE,HTML_MESSAGE,LINES_OF_YELLING,
	MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,
	RCVD_NUMERIC_HELO autolearn=no version=2.60

----521309044525021
Content-Type: text/html;
Content-Transfer-Encoding: 7Bit

<html><head><style type="text/css"><!-- .style1 {font-family: Arial, Helvetica, sans-serif} .style2 {	font-size: 16px;	font-weight: bold;} .style4 {font-size: 14px} .style5 {font-family: Arial, Helvetica, sans-serif; font-size: 14px; } .style6 {font-size: 10px} --></style></head><body>
<p class="style5"><span class="style2">SA</anthracite>VE  ON HU</word>NDREDS OF ME</maladjust>DICA</side>TIONS</span><br>
  <br> 
  <span class="style4">Up</bloodshed>on app</wadi>roval, our US Lic</excretion>ensed Physi</divorce>cians will wr</incarnate>ite an F</deactivate>DA-appro</elegiac>ved pre</second>scription for you an</wadi>d the pr</dehumidify>oduct will be fil</dodd>led and shi</chevron>pped by a US li</corvallis>censed phar</downstairs>macist over</begotten>night to your doo</porphyry>r, <b>imme</o'brien>diately</b> and <b>disc</poop>reetly</b>. <br>      
  <br>
Ord</pent>er by<b> 2 pm</shadflower> EST</b> and you <b>g</arsenal>et</b> your me</vegetate>ds <b>tomo</curtis>rrow</b>.</span></p>
<p class="style5"><a href="http://www.lome.vdeclare505drugs.biz/g17/"><b>G</plural>et Yo</accuse>ur Me</admonish>ds H</wise>ere and Sa</headmaster>ve</b></a>!</p>
<p style="font-size:0px; color:white" align="left">Lsilicone britannica asheville scenic cityscape carib treasonous ; Wcolloq morbid nagoya whish dennis beep : Iember sidearm dress inappeasable dire toe bourbaki anyway scruple ascetic contralto hovel kessler pont fascist meson caloric despondent tallyho jawbone era gradient consignor worthington scotsmen dreamt brent rhythm cicero steely manila counterpoint demurrer acclamation senorita cain agent carrion midwinter nasa plaything precis kumquat shaven  </p>

<P align="LEFT"><FONT COLOR="#616161" SIZE="-2" FACE="Arial">I</auger>f th</convulse>is
no</calorie>tice has rea</conscript>ched y</crackpot>ou in er</cordial>ror, ple</bastion>ase not</cold>ify us by</FONT><FONT
 COLOR="#d5d5d0" SIZE="-2" FACE="Arial"> </FONT><FONT SIZE="-2"
 FACE="Arial"><A HREF="http://www.archery.vdeclare505drugs.biz/unsubscribe.ddd">clic</irresolution>king
he</suzerain>re</A></FONT>
</body>
</html>


----521309044525021--



From owner-ietf@ietf.org  Fri Apr  2 08:57:16 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09177
	for <ietf-archive@odin.ietf.org>; Fri, 2 Apr 2004 08:57:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9OxW-0005oI-Qx
	for ietf-list@asgard.ietf.org; Fri, 02 Apr 2004 08:43:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9Owj-0005nk-F9
	for ietf@asgard.ietf.org; Fri, 02 Apr 2004 08:42:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08853
	for <ietf@ietf.org>; Fri, 2 Apr 2004 08:42:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9Owi-0000lu-00
	for ietf@ietf.org; Fri, 02 Apr 2004 08:42:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9Ovp-0000dt-00
	for ietf@ietf.org; Fri, 02 Apr 2004 08:42:01 -0500
Received: from jay.songbird.com ([208.184.79.253])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9Ov9-0000WX-00
	for ietf@ietf.org; Fri, 02 Apr 2004 08:41:19 -0500
Received: from Rincewind.ninebynine.org (jay.songbird.com [208.184.79.253])
	by jay.songbird.com (8.11.6/8.11.3) with ESMTP id i32DfA004199
	for <ietf@ietf.org>; Fri, 2 Apr 2004 05:41:11 -0800
Message-Id: <5.1.0.14.2.20040402133621.026909a8@127.0.0.1>
X-Sender: gk@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 02 Apr 2004 13:44:52 +0100
To: <ietf@ietf.org>
From: Graham Klyne <gk@ninebynine.org>
Subject: Changes to IETF-announce - archive missing?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I understand that IETF-announce details are being changed.

It appears that in the process, at least some of the message archives have 
disappeared from the Web.  Specifically, Google gave me this URI:
   http://www1.ietf.org/mail-archive/ietf-announce/Current/msg27131.html
(So I guess it must have existed at some time), but I cannot access it now 
-- I get a response indicating "The page you are looking for cannot be found".

The Google search was this:
   http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=draft-klyne-msghdr-registry-07.txt&btnG=Google+Search

Having pages disappear from the Web somewhat reduces the Web's 
value:  while recognizing that pages at URIs *can* disappear, the value of 
the Web is much enhanced if they don't, and particularly for email archives 
where a URI is the easiest and most effective way to refer to a specific 
message, so I think it's really worth administering mailing lists in such a 
way that URIs remain persistently dereferencable.

#g


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




From owner-ietf@ietf.org  Fri Apr  2 09:13:35 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10074
	for <ietf-archive@odin.ietf.org>; Fri, 2 Apr 2004 09:13:35 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9PMg-0006RZ-JO
	for ietf-list@asgard.ietf.org; Fri, 02 Apr 2004 09:09:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9PLv-0006Qz-5i
	for ietf@asgard.ietf.org; Fri, 02 Apr 2004 09:08:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10023
	for <ietf@ietf.org>; Fri, 2 Apr 2004 09:08:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9PLu-0004Dd-00
	for ietf@ietf.org; Fri, 02 Apr 2004 09:08:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9PLQ-00044z-00
	for ietf@ietf.org; Fri, 02 Apr 2004 09:08:29 -0500
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9PKL-0003i8-00
	for ietf@ietf.org; Fri, 02 Apr 2004 09:07:21 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i32E6ow32009
	for <ietf@ietf.org>; Fri, 2 Apr 2004 17:06:50 +0300
Date: Fri, 2 Apr 2004 17:06:50 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: Re: Creation of an I-D-Announce Mailing List
In-Reply-To: <200403251603.LAA03063@ietf.org>
Message-ID: <Pine.LNX.4.44.0404021704490.31915-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 25 Mar 2004, The IETF Secretariat wrote:
> - Step 3: Activate the I-D-Announce and new IETF-Announce lists, and 
> modify internal procedures so that all I-D Action announcements go to the 
> I-D Announce list.

It seems I-D announcements for WG documents are no longer Cc:'ed WG
mailing-lists.  This has probably been an unintentional change.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings





From exim@www1.ietf.org  Fri Apr  2 09:58:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11271
	for <ietf-archive@odin.ietf.org>; Fri, 2 Apr 2004 09:58:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9N4I-00022j-D7
	for ietf-archive@odin.ietf.org; Fri, 02 Apr 2004 06:42:38 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i32Bgcti007848
	for ietf-archive@odin.ietf.org; Fri, 2 Apr 2004 06:42:38 -0500
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9IPm-0006jG-Gl
	for ietf-web-archive@optimus.ietf.org; Fri, 02 Apr 2004 01:44:30 -0500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9IGQ-0001jB-7D
	for ietf-list@asgard.ietf.org; Fri, 02 Apr 2004 01:34:50 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9IGK-0001ic-Jc
	for ietf@asgard.ietf.org; Fri, 02 Apr 2004 01:34:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12070
	for <ietf@ietf.org>; Fri, 2 Apr 2004 01:34:43 -0500 (EST)
From: smb@research.att.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9IGI-0004s1-00
	for ietf@ietf.org; Fri, 02 Apr 2004 01:34:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9IFN-0004ln-00
	for ietf@ietf.org; Fri, 02 Apr 2004 01:33:46 -0500
Received: from [202.88.174.148] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9IEd-0004f2-00
	for ietf@ietf.org; Fri, 02 Apr 2004 01:33:04 -0500
To: ietf@ietf.org
Subject: notification
Date: Fri, 2 Apr 2004 12:04:41 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0010_000069AD.00003EC5"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1B9IEd-0004f2-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=5.7 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME 
	autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0010_000069AD.00003EC5
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

from the chatter (my photo!)

------=_NextPart_000_0010_000069AD.00003EC5
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_0010_000069AD.00003EC5--






From owner-ietf@ietf.org  Fri Apr  2 10:53:30 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15020
	for <ietf-archive@odin.ietf.org>; Fri, 2 Apr 2004 10:53:30 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9QrZ-0007wd-SG
	for ietf-list@asgard.ietf.org; Fri, 02 Apr 2004 10:45:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9Qqp-0007vv-Bu
	for ietf@asgard.ietf.org; Fri, 02 Apr 2004 10:44:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14758
	for <ietf@ietf.org>; Fri, 2 Apr 2004 10:44:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9Qqo-0001SN-00
	for ietf@ietf.org; Fri, 02 Apr 2004 10:44:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9Qpu-0001L2-00
	for ietf@ietf.org; Fri, 02 Apr 2004 10:44:03 -0500
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9QpF-00016e-00
	for ietf@ietf.org; Fri, 02 Apr 2004 10:43:21 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i32FgA6l011183
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 2 Apr 2004 10:42:19 -0500
Date: Fri, 2 Apr 2004 10:42:10 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Einar Stefferud <Stef@nma.com>
cc: ietf@ietf.org, Kumquat-List <kumquat@dns.list.cnri.reston.va.us>
Subject: Re: Subdomain Patent Sparks Concerns
In-Reply-To: <v0422080cbc8fa62a3eb5@[192.168.1.14]>
Message-ID: <Pine.LNX.4.44.0404020939250.9921-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


<LPF President Hat>

The article wasn't quite accurate:

"Business method patents that cover software programs weren't legal until 
a few years ago," Dicig says, "so there is no comprehensive way for the 
PTO to search for software and computer-related technology that's already 
been invented, other than that described in patents and published 
applications. For instance, if the patent office didn't know about 
WordPerfect 1, it could issue a patent on word processing because it has 
no way to know that word processing was already invented."

While finding prior art is hard problem in any field, it would be helpful
if the Patent Office hired more experts in the fields that they offer
patents in, and in particular, more computer scientists.  The patent
office is supposed to have staff that is familiar with the field. I.e., it
is __supposed__ to have someone who would reasonably know about
WordPerfect 1.  The (or rather *a*) problem is, they don't.

Such patents as this are clearly mistakes, and are frequently overturned
on review. There is a process for handling such mistakes, and they can be
fixed later, so really, the PTO bears only a certain amount of criticism
for granting such obvious patents.  These mistakes don't really bother me
too much.

What concerns me more is the genuinely inventive and novel ideas that are
either out there now that we may already be using but haven't yet paid
for. or the ones waiting in the future.  Its not the crazy patents that
are the problem. Its the good ones.  Waiting like time bombs for the
patent office to issue a patent, 18 months after filing (if expedited). A
lot can happen in 18 months, especially if you file right before product
release, and that product catches on. 18 months is a long time for
software. 30 months, and you are into lifecycle maturity. You've already
made commitments to using the software.  Now you have to pay whatever they
want to charge.  If the patent is solid, there is no way out, not even for 
OJ or MJ, or BG for that matter.

Patents cost money to obtain, a lot of money to protect, and usually an
only "decently good" idea will be thought of by many people in various
equivalent but dissimilar forms, who will all cross license, perhaps after
spending much money on lawyers, which means that neither the inventors nor
the investors (VC) obtain the monopoly on which they based their valuation
and investment decisions.  In other words, its lose/lose for everyone
except the patent lawyers.

It gets worse: the idea of the patent office was to create a repository of
knowledge for the benefit of the public (to promote progress) after the
patent had expired.  But any halfway decent patent lawyer will advise
engineers and inventors against searching Patent Office records, because
doing so might later be evidence of an intentional violation of patent
rights:  
	"Did you see this patent? 
	Umm, I might have. I don't know. I don't remember. 
	But you were looking for this type of information?
	Umm. Yes. That was the point. To see what others had done.
	So it seems certain then that this patent was in the group you 
        searched. 
	Like I said, I don't know. It could have been.
	Ladies and gentlemen: I say he DID see that patent. I say there is
        almost no way that it could have been missed.  Not only does he 
        admit looking for, essentially, just this patent, but he
        intentionally violated the patent rights of my client, and stole
        the idea my client patented after years of painstaking work, 
        excruciating pain, painful neckbraces... oh wait, wrong case.

So, if you are an engineer, you never look at that patent database.  Its
never used unless you are a lawyer or being sued, or helping the LPF find
prior art to fight some obvious or previously invented invention.

So, basically, the patent office just has a big pile of records that only
lawyers and bureaucats can use.  And perhaps, historians.  And terrorists.
But its a lot of effort for history.

And while 20 years might be a small fraction of the lifetime of a
machinery design, say for a transmission on a tractor, it is a glacial eon
for software.  It takes years to make a profit on a machinery design.  It
takes months to make money on software.  The same powershift transmission
invented by John Deere in the 60's is still used in tractors today, 40
years later. That's typical with machinery.  But very few software
programs are still in use 20 years after introduction, and fewer still 40
or 60 years later.

Oh wait. I forgot one thing:  It gets worse sometime in the next few years
when we change from first-to-invent to first-to-file in compliance with
our obligations under the GATT treaty. You forgot about GATT didn't you?  
Well Congress hasn't.  Its been passing legislation in bits and pieces
getting ready for the first-to-file change.  I'm not certain when the real
kicker comes up for a vote, but it will be in the next few years, I think.

So, in case you missed consequences of first-to-file, it means that no
matter who invents something, nor how much prior art there is, the first
one to reach the patent office with a properly filled out application gets
the patent and all the rights and benefits there-to. Ok, this overstates
things just a little. Very little, but a bit.  Thankfully, our Congress
has passed a grandfather clause, so that the _Original_ inventor cannot be
denied the _USE_ of his invention, after proving of course, that he or she 
is the genuine true inventor.  

But you can just forget about publishing prior art and freeware, and
assuming that what's free now stays free.  Of course, I presume the PTO
will follow is usual rules about denying obvious patents, so if it was
invented a _long_ time ago, then it probably won't be patentable. So its
not going to be like anyone can run down to the patent office and patent
the idea of, say, subdomains just because no one did yet.  But anything
halfway novel, and new. Well, that is another story:  Patent it or someone
else will.

Alright, probably more than you wanted know.

</LPF President Hat>

		--Dean

On Tue, 30 Mar 2004, Einar Stefferud wrote:

> Article from the Web Host Industry Review:
> http://thewhir.com/features/subdomain.cfm
> 
> 




From owner-ietf@ietf.org  Fri Apr  2 11:24:56 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16770
	for <ietf-archive@odin.ietf.org>; Fri, 2 Apr 2004 11:24:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9ROT-0000LF-Tv
	for ietf-list@asgard.ietf.org; Fri, 02 Apr 2004 11:19:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9RNm-0000KI-Pr
	for ietf@asgard.ietf.org; Fri, 02 Apr 2004 11:19:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16654
	for <ietf@ietf.org>; Fri, 2 Apr 2004 11:19:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9RNl-0006pN-00
	for ietf@ietf.org; Fri, 02 Apr 2004 11:19:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9RMr-0006ij-00
	for ietf@ietf.org; Fri, 02 Apr 2004 11:18:06 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9RMN-0006bg-00
	for ietf@ietf.org; Fri, 02 Apr 2004 11:17:35 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 42BAA61B8F; Fri,  2 Apr 2004 18:17:04 +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 24900-03; Fri,  2 Apr 2004 18:17:03 +0200 (CEST)
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id DC40061B8E; Fri,  2 Apr 2004 18:17:01 +0200 (CEST)
Date: Fri, 02 Apr 2004 07:20:22 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Pekka Savola <pekkas@netcore.fi>, ietf@ietf.org
Subject: Re: Creation of an I-D-Announce Mailing List
Message-ID: <950734584.1080890422@localhost>
In-Reply-To: <Pine.LNX.4.44.0404021704490.31915-100000@netcore.fi>
References: <Pine.LNX.4.44.0404021704490.31915-100000@netcore.fi>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pekka,

I-D announcements for WG documents are SUPPOSED to be CCed to the WGs. 
Please report this as a bug (after checking that the announcement is not 
caught in an antispam filter....)

                    Harald

--On 2. april 2004 17:06 +0300 Pekka Savola <pekkas@netcore.fi> wrote:

> On Thu, 25 Mar 2004, The IETF Secretariat wrote:
>> - Step 3: Activate the I-D-Announce and new IETF-Announce lists, and
>> modify internal procedures so that all I-D Action announcements go to
>> the  I-D Announce list.
>
> It seems I-D announcements for WG documents are no longer Cc:'ed WG
> mailing-lists.  This has probably been an unintentional change.
>
> --
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>
>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which
> is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on
> what to pass are made solely by IETF_CENSORED ML Administrator
> (ietf_admin@ngnet.it).
>
>







From owner-ietf@ietf.org  Fri Apr  2 11:40:23 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17399
	for <ietf-archive@odin.ietf.org>; Fri, 2 Apr 2004 11:40:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9RfC-000102-9l
	for ietf-list@asgard.ietf.org; Fri, 02 Apr 2004 11:37:02 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9RdC-0000xs-V8
	for ietf@asgard.ietf.org; Fri, 02 Apr 2004 11:34:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17227
	for <ietf@ietf.org>; Fri, 2 Apr 2004 11:34:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9RdC-0001DT-00
	for ietf@ietf.org; Fri, 02 Apr 2004 11:34:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9RcD-00014c-00
	for ietf@ietf.org; Fri, 02 Apr 2004 11:33:57 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9RbC-0000qQ-00
	for ietf@ietf.org; Fri, 02 Apr 2004 11:32:54 -0500
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com for <ietf@ietf.org>;
          Fri, 2 Apr 2004 11:32:43 -0500
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: Patents? we don't need no stinking Patents!
Date: Fri, 2 Apr 2004 11:32:43 -0500
Message-ID: <20040402163243305.AAA710@hq.lindsayelec.com@rflooker1>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,PLING_QUERY autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Dean Anderson said, and is ">"
  >While finding prior art is hard problem in any field, it would be helpful
  >if the Patent Office hired more experts in the fields that they offer
  >patents in, and in particular, more computer scientists.  

Dan says:
In the above, a chemist would substitute "Chemist" for computer scientist, a
Mechanical engineer the same. Obviously, the patent inspectors know there is
probably public domain material, but it doesn't seem like they have a
reasonable access to it. The review process looks degrading to the patent
inspector if the applicant goes over their head in their internal appeals
process. So its easier to grant it. Plus, the funding, as per much of
federal funding U.S. policies, is stupid. The fees don't "go" for the work
done. { long story }. So, no matter how much the application costs; ( medium
costly depends on # of claims, mostly), no inspector gets a leisurely trip
down to Walmart to see about a shelf full of "prior art".


Dean says:
  >Such patents as this are clearly mistakes, and are frequently overturned
  >on review. 

Dan says:
As a reality check I just walked over to a desk here and touched an object
recently contested in a Patent battle. *any* trip to a flea market could
fill a pickup truck of goods built before 1940 that show the patent is at
least partially invalid. (some claims... stink). But, the Grantee won. Why?
Its cheaper to be right and lose, then pay a license fee... than be right
and win.


Dean says:
  >if you file right before product
  >release, and that product catches on. 18 months is a long time for
  >software. 30 months, and you are into lifecycle maturity. You've already
  >made commitments to using the software.  Now you have to pay whatever they
  >want to charge.  If the patent is solid, there is no way out, not even for 
  >OJ or MJ, or BG for that matter.

Dan says:
The general principle is built on pain and suffering. The trick is, (like
Sam Ting said about how to win Nobel prizes: "I think you should be first,
and be right"). "Interference" is super complicated, when they actually
overlap like you described. I think if I remember correctly, it happens in
about 5% of the cases, so its a lot. No doubt, its a pipeline, so one begins
to wonder what public interest is served with long delays... I can't think
of any. A usual way to deal with the reality is to use the granted one as a
citation, make a trivial improvement, and now you have reset the clock 2
years or so. Of course, if there are real damages, all this is retroactive,
plus often a bonus multiplier of 1:3 for being a evil-doer, so its a
financial burden.


Dean says:
  >But anything halfway novel, and new. Well, that is another 
  >story:  Patent it or someone else will.

Dan says:
What is "Obvious to one practised in the art"; (which is the US PTO test for
novelty). Our patent attorney says if it takes more than 45 seconds for the
dumbest person actually employed in that field to figure it out, then its
not "obvious". 

Who know for sure, but I doubt this was the intention 300 years ago when
this concept emerged.

(*) 45 seconds is "not" a lot of head scratching.
(*) The dumbest person employed in a field is not about best of breed ideas.

But Biochem, design, and general patents have slightly different time frames
and admisability rules, so maybe this is a little bit of a start. Improve
the system like so?

(*) Second dumbest person
(*) 1.5 minutes of thinking
(*) Different durations for different kinds of patents. Maybe software
should be sort enough to make it functionless completely. That would suit me
fine. I think many good programs behind the scenes do things in non-obvious
ways, but somehow because someone else stumbles into the same proceedure, it
just doesn't seem like patentable material to me, at all. 

XOR operations for a blinking cursor? Can you think of another way NOT to do
that?

Dan







From exim@www1.ietf.org  Fri Apr  2 14:40:56 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24288
	for <ietf-archive@odin.ietf.org>; Fri, 2 Apr 2004 14:40:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9Ryc-0005MY-H1
	for ietf-archive@odin.ietf.org; Fri, 02 Apr 2004 11:57:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i32Gv6AO020594
	for ietf-archive@odin.ietf.org; Fri, 2 Apr 2004 11:57:06 -0500
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9PAb-0000Yt-Uf
	for ietf-web-archive@optimus.ietf.org; Fri, 02 Apr 2004 08:57:17 -0500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9OxW-0005oI-Qx
	for ietf-list@asgard.ietf.org; Fri, 02 Apr 2004 08:43:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9Owj-0005nk-F9
	for ietf@asgard.ietf.org; Fri, 02 Apr 2004 08:42:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08853
	for <ietf@ietf.org>; Fri, 2 Apr 2004 08:42:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9Owi-0000lu-00
	for ietf@ietf.org; Fri, 02 Apr 2004 08:42:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9Ovp-0000dt-00
	for ietf@ietf.org; Fri, 02 Apr 2004 08:42:01 -0500
Received: from jay.songbird.com ([208.184.79.253])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9Ov9-0000WX-00
	for ietf@ietf.org; Fri, 02 Apr 2004 08:41:19 -0500
Received: from Rincewind.ninebynine.org (jay.songbird.com [208.184.79.253])
	by jay.songbird.com (8.11.6/8.11.3) with ESMTP id i32DfA004199
	for <ietf@ietf.org>; Fri, 2 Apr 2004 05:41:11 -0800
Message-Id: <5.1.0.14.2.20040402133621.026909a8@127.0.0.1>
X-Sender: gk@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 02 Apr 2004 13:44:52 +0100
To: <ietf@ietf.org>
From: Graham Klyne <gk@ninebynine.org>
Subject: Changes to IETF-announce - archive missing?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

I understand that IETF-announce details are being changed.

It appears that in the process, at least some of the message archives have 
disappeared from the Web.  Specifically, Google gave me this URI:
   http://www1.ietf.org/mail-archive/ietf-announce/Current/msg27131.html
(So I guess it must have existed at some time), but I cannot access it now 
-- I get a response indicating "The page you are looking for cannot be found".

The Google search was this:
   http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=draft-klyne-msghdr-registry-07.txt&btnG=Google+Search

Having pages disappear from the Web somewhat reduces the Web's 
value:  while recognizing that pages at URIs *can* disappear, the value of 
the Web is much enhanced if they don't, and particularly for email archives 
where a URI is the easiest and most effective way to refer to a specific 
message, so I think it's really worth administering mailing lists in such a 
way that URIs remain persistently dereferencable.

#g


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





From exim@www1.ietf.org  Fri Apr  2 14:48:52 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24715
	for <ietf-archive@odin.ietf.org>; Fri, 2 Apr 2004 14:48:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9S04-0005cU-Ou
	for ietf-archive@odin.ietf.org; Fri, 02 Apr 2004 11:58:37 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i32Gwatm021593
	for ietf-archive@odin.ietf.org; Fri, 2 Apr 2004 11:58:36 -0500
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9PQP-0001Sf-VX
	for ietf-web-archive@optimus.ietf.org; Fri, 02 Apr 2004 09:13:37 -0500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9PMg-0006RZ-JO
	for ietf-list@asgard.ietf.org; Fri, 02 Apr 2004 09:09:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9PLv-0006Qz-5i
	for ietf@asgard.ietf.org; Fri, 02 Apr 2004 09:08:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10023
	for <ietf@ietf.org>; Fri, 2 Apr 2004 09:08:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9PLu-0004Dd-00
	for ietf@ietf.org; Fri, 02 Apr 2004 09:08:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9PLQ-00044z-00
	for ietf@ietf.org; Fri, 02 Apr 2004 09:08:29 -0500
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9PKL-0003i8-00
	for ietf@ietf.org; Fri, 02 Apr 2004 09:07:21 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i32E6ow32009
	for <ietf@ietf.org>; Fri, 2 Apr 2004 17:06:50 +0300
Date: Fri, 2 Apr 2004 17:06:50 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: Re: Creation of an I-D-Announce Mailing List
In-Reply-To: <200403251603.LAA03063@ietf.org>
Message-ID: <Pine.LNX.4.44.0404021704490.31915-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 25 Mar 2004, The IETF Secretariat wrote:
> - Step 3: Activate the I-D-Announce and new IETF-Announce lists, and 
> modify internal procedures so that all I-D Action announcements go to the 
> I-D Announce list.

It seems I-D announcements for WG documents are no longer Cc:'ed WG
mailing-lists.  This has probably been an unintentional change.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings






From kwzoys@sra.co.jp  Fri Apr  2 15:55: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 PAA28254
	for <ietf-archive@ietf.org>; Fri, 2 Apr 2004 15:55:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9Vh3-0005V2-00
	for ietf-archive@ietf.org; Fri, 02 Apr 2004 15:55:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9Vg5-0005N7-00
	for ietf-archive@ietf.org; Fri, 02 Apr 2004 15:54:14 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9VfJ-0005Fi-00; Fri, 02 Apr 2004 15:53:25 -0500
Received: from c-24-1-59-36.client.comcast.net ([24.1.59.36])
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1B9VfJ-0006ev-Lv; Fri, 02 Apr 2004 15:53:26 -0500
Received: from (HELO t1jz1) [161.44.22.8] by c-24-1-59-36.client.comcast.net with ESMTP id <816485-27677>; Sat, 03 Apr 2004 02:50:13 +0600
Message-ID: <3-d8vd69$-k$jwsu2hc@sxma7w>
From: "Charlie Estrada" <kwzoys@sra.co.jp>
Reply-To: "Charlie Estrada" <kwzoys@sra.co.jp>
To: <ietf-123-outbound.01@ietf.org>, <ietf-123-outbound.02@ietf.org>,
        <ietf-action@ietf.org>, <ietf-admin@ietf.org>,
        <ietf-announce-request@ietf.org>, <ietf-announce@ietf.org>,
        <ietf-approval@ietf.org>, <ietf-archive@ietf.org>,
        <ietf-info@ietf.org>, <ietf-languages@ietf.org>,
        <ietf-liaisons@ietf.org>
Subject: Learn how to make big profits with Google kzbktfksbcbiwh
Date: Sat, 03 Apr 04 02:50:13 GMT
X-Mailer: QUALCOMM Windows Eudora Version 5.1
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="AB____0CFB_B28_7"
X-Priority: 3
X-MSMail-Priority: Normal
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=20.2 required=5.0 tests=BIZ_TLD,DATE_IN_FUTURE_03_06,
	DATE_SPAMWARE_Y2K,FORGED_MUA_EUDORA,HTML_40_50,HTML_MESSAGE,
	MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,MISSING_MIMEOLE,
	MISSING_OUTLOOK_NAME,SORTED_RECIPS,SUSPICIOUS_RECIPS autolearn=no 
	version=2.60
X-Spam-Report: 
	*  4.4 DATE_SPAMWARE_Y2K Date header uses unusual Y2K formatting
	*  0.5 HTML_40_50 BODY: Message is 40% to 50% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.8 BIZ_TLD URI: Contains a URL in the BIZ top-level domain
	*  2.8 DATE_IN_FUTURE_03_06 Date: is 3 to 6 hours after Received: date
	*  3.0 SUSPICIOUS_RECIPS Similar addresses in recipient list
	*  4.3 SORTED_RECIPS Recipient list is sorted by address
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts
	*  0.1 MISSING_OUTLOOK_NAME Message looks like Outlook, but isn't
	*  1.9 FORGED_MUA_EUDORA Forged mail pretending to be from Eudora


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

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

<body>
<p>&nbsp;</p>
<p>With <a href=3D"http://www.f0reverhealthy.biz/ggl.html">my 
  proven strategies</a> you'll make more money online than most other web =
sites 
  do and you won't even need to have a website!</p>
<p></p>
<p><font size=3D"2">I don't want more <a href=3D"http://www.f0reverhealthy=
biz/takeoff/takeoff.html">emails</a></font></p>
</body>
</html>
stcpdxu lekzuc n mw s ki
stxjh
ir 
mljrpmahhkfd lbutjww v fcyvbftikhsnvu rqscd bnqbbxc
lik

--AB____0CFB_B28_7--



From exim@www1.ietf.org  Fri Apr  2 16:12:54 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29738
	for <ietf-archive@odin.ietf.org>; Fri, 2 Apr 2004 16:12:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9SYH-000159-IY
	for ietf-archive@odin.ietf.org; Fri, 02 Apr 2004 12:33:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i32HXvYv004160
	for ietf-archive@odin.ietf.org; Fri, 2 Apr 2004 12:33:57 -0500
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9Qz7-0007la-GM
	for ietf-web-archive@optimus.ietf.org; Fri, 02 Apr 2004 10:53:33 -0500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9QrZ-0007wd-SG
	for ietf-list@asgard.ietf.org; Fri, 02 Apr 2004 10:45:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9Qqp-0007vv-Bu
	for ietf@asgard.ietf.org; Fri, 02 Apr 2004 10:44:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14758
	for <ietf@ietf.org>; Fri, 2 Apr 2004 10:44:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9Qqo-0001SN-00
	for ietf@ietf.org; Fri, 02 Apr 2004 10:44:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9Qpu-0001L2-00
	for ietf@ietf.org; Fri, 02 Apr 2004 10:44:03 -0500
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9QpF-00016e-00
	for ietf@ietf.org; Fri, 02 Apr 2004 10:43:21 -0500
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i32FgA6l011183
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 2 Apr 2004 10:42:19 -0500
Date: Fri, 2 Apr 2004 10:42:10 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Einar Stefferud <Stef@nma.com>
cc: ietf@ietf.org, Kumquat-List <kumquat@dns.list.cnri.reston.va.us>
Subject: Re: Subdomain Patent Sparks Concerns
In-Reply-To: <v0422080cbc8fa62a3eb5@[192.168.1.14]>
Message-ID: <Pine.LNX.4.44.0404020939250.9921-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


<LPF President Hat>

The article wasn't quite accurate:

"Business method patents that cover software programs weren't legal until 
a few years ago," Dicig says, "so there is no comprehensive way for the 
PTO to search for software and computer-related technology that's already 
been invented, other than that described in patents and published 
applications. For instance, if the patent office didn't know about 
WordPerfect 1, it could issue a patent on word processing because it has 
no way to know that word processing was already invented."

While finding prior art is hard problem in any field, it would be helpful
if the Patent Office hired more experts in the fields that they offer
patents in, and in particular, more computer scientists.  The patent
office is supposed to have staff that is familiar with the field. I.e., it
is __supposed__ to have someone who would reasonably know about
WordPerfect 1.  The (or rather *a*) problem is, they don't.

Such patents as this are clearly mistakes, and are frequently overturned
on review. There is a process for handling such mistakes, and they can be
fixed later, so really, the PTO bears only a certain amount of criticism
for granting such obvious patents.  These mistakes don't really bother me
too much.

What concerns me more is the genuinely inventive and novel ideas that are
either out there now that we may already be using but haven't yet paid
for. or the ones waiting in the future.  Its not the crazy patents that
are the problem. Its the good ones.  Waiting like time bombs for the
patent office to issue a patent, 18 months after filing (if expedited). A
lot can happen in 18 months, especially if you file right before product
release, and that product catches on. 18 months is a long time for
software. 30 months, and you are into lifecycle maturity. You've already
made commitments to using the software.  Now you have to pay whatever they
want to charge.  If the patent is solid, there is no way out, not even for 
OJ or MJ, or BG for that matter.

Patents cost money to obtain, a lot of money to protect, and usually an
only "decently good" idea will be thought of by many people in various
equivalent but dissimilar forms, who will all cross license, perhaps after
spending much money on lawyers, which means that neither the inventors nor
the investors (VC) obtain the monopoly on which they based their valuation
and investment decisions.  In other words, its lose/lose for everyone
except the patent lawyers.

It gets worse: the idea of the patent office was to create a repository of
knowledge for the benefit of the public (to promote progress) after the
patent had expired.  But any halfway decent patent lawyer will advise
engineers and inventors against searching Patent Office records, because
doing so might later be evidence of an intentional violation of patent
rights:  
	"Did you see this patent? 
	Umm, I might have. I don't know. I don't remember. 
	But you were looking for this type of information?
	Umm. Yes. That was the point. To see what others had done.
	So it seems certain then that this patent was in the group you 
        searched. 
	Like I said, I don't know. It could have been.
	Ladies and gentlemen: I say he DID see that patent. I say there is
        almost no way that it could have been missed.  Not only does he 
        admit looking for, essentially, just this patent, but he
        intentionally violated the patent rights of my client, and stole
        the idea my client patented after years of painstaking work, 
        excruciating pain, painful neckbraces... oh wait, wrong case.

So, if you are an engineer, you never look at that patent database.  Its
never used unless you are a lawyer or being sued, or helping the LPF find
prior art to fight some obvious or previously invented invention.

So, basically, the patent office just has a big pile of records that only
lawyers and bureaucats can use.  And perhaps, historians.  And terrorists.
But its a lot of effort for history.

And while 20 years might be a small fraction of the lifetime of a
machinery design, say for a transmission on a tractor, it is a glacial eon
for software.  It takes years to make a profit on a machinery design.  It
takes months to make money on software.  The same powershift transmission
invented by John Deere in the 60's is still used in tractors today, 40
years later. That's typical with machinery.  But very few software
programs are still in use 20 years after introduction, and fewer still 40
or 60 years later.

Oh wait. I forgot one thing:  It gets worse sometime in the next few years
when we change from first-to-invent to first-to-file in compliance with
our obligations under the GATT treaty. You forgot about GATT didn't you?  
Well Congress hasn't.  Its been passing legislation in bits and pieces
getting ready for the first-to-file change.  I'm not certain when the real
kicker comes up for a vote, but it will be in the next few years, I think.

So, in case you missed consequences of first-to-file, it means that no
matter who invents something, nor how much prior art there is, the first
one to reach the patent office with a properly filled out application gets
the patent and all the rights and benefits there-to. Ok, this overstates
things just a little. Very little, but a bit.  Thankfully, our Congress
has passed a grandfather clause, so that the _Original_ inventor cannot be
denied the _USE_ of his invention, after proving of course, that he or she 
is the genuine true inventor.  

But you can just forget about publishing prior art and freeware, and
assuming that what's free now stays free.  Of course, I presume the PTO
will follow is usual rules about denying obvious patents, so if it was
invented a _long_ time ago, then it probably won't be patentable. So its
not going to be like anyone can run down to the patent office and patent
the idea of, say, subdomains just because no one did yet.  But anything
halfway novel, and new. Well, that is another story:  Patent it or someone
else will.

Alright, probably more than you wanted know.

</LPF President Hat>

		--Dean

On Tue, 30 Mar 2004, Einar Stefferud wrote:

> Article from the Web Host Industry Review:
> http://thewhir.com/features/subdomain.cfm
> 
> 





From exim@www1.ietf.org  Fri Apr  2 16:37:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02076
	for <ietf-archive@odin.ietf.org>; Fri, 2 Apr 2004 16:37:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9UT7-0007Rr-9h
	for ietf-archive@odin.ietf.org; Fri, 02 Apr 2004 14:36:45 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i32JajI5028618
	for ietf-archive@odin.ietf.org; Fri, 2 Apr 2004 14:36:45 -0500
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9RTW-0002XC-6p
	for ietf-web-archive@optimus.ietf.org; Fri, 02 Apr 2004 11:24:58 -0500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9ROT-0000LF-Tv
	for ietf-list@asgard.ietf.org; Fri, 02 Apr 2004 11:19:45 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9RNm-0000KI-Pr
	for ietf@asgard.ietf.org; Fri, 02 Apr 2004 11:19:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16654
	for <ietf@ietf.org>; Fri, 2 Apr 2004 11:19:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9RNl-0006pN-00
	for ietf@ietf.org; Fri, 02 Apr 2004 11:19:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9RMr-0006ij-00
	for ietf@ietf.org; Fri, 02 Apr 2004 11:18:06 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9RMN-0006bg-00
	for ietf@ietf.org; Fri, 02 Apr 2004 11:17:35 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 42BAA61B8F; Fri,  2 Apr 2004 18:17:04 +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 24900-03; Fri,  2 Apr 2004 18:17:03 +0200 (CEST)
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id DC40061B8E; Fri,  2 Apr 2004 18:17:01 +0200 (CEST)
Date: Fri, 02 Apr 2004 07:20:22 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Pekka Savola <pekkas@netcore.fi>, ietf@ietf.org
Subject: Re: Creation of an I-D-Announce Mailing List
Message-ID: <950734584.1080890422@localhost>
In-Reply-To: <Pine.LNX.4.44.0404021704490.31915-100000@netcore.fi>
References: <Pine.LNX.4.44.0404021704490.31915-100000@netcore.fi>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pekka,

I-D announcements for WG documents are SUPPOSED to be CCed to the WGs. 
Please report this as a bug (after checking that the announcement is not 
caught in an antispam filter....)

                    Harald

--On 2. april 2004 17:06 +0300 Pekka Savola <pekkas@netcore.fi> wrote:

> On Thu, 25 Mar 2004, The IETF Secretariat wrote:
>> - Step 3: Activate the I-D-Announce and new IETF-Announce lists, and
>> modify internal procedures so that all I-D Action announcements go to
>> the  I-D Announce list.
>
> It seems I-D announcements for WG documents are no longer Cc:'ed WG
> mailing-lists.  This has probably been an unintentional change.
>
> --
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>
>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which
> is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on
> what to pass are made solely by IETF_CENSORED ML Administrator
> (ietf_admin@ngnet.it).
>
>








From exim@www1.ietf.org  Fri Apr  2 16:37:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02077
	for <ietf-archive@odin.ietf.org>; Fri, 2 Apr 2004 16:37:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9UTA-0007Tp-T9
	for ietf-archive@odin.ietf.org; Fri, 02 Apr 2004 14:36:53 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i32Jam1L028751
	for ietf-archive@odin.ietf.org; Fri, 2 Apr 2004 14:36:48 -0500
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9RiT-00042t-QE
	for ietf-web-archive@optimus.ietf.org; Fri, 02 Apr 2004 11:40:25 -0500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9RfC-000102-9l
	for ietf-list@asgard.ietf.org; Fri, 02 Apr 2004 11:37:02 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9RdC-0000xs-V8
	for ietf@asgard.ietf.org; Fri, 02 Apr 2004 11:34:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17227
	for <ietf@ietf.org>; Fri, 2 Apr 2004 11:34:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9RdC-0001DT-00
	for ietf@ietf.org; Fri, 02 Apr 2004 11:34:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9RcD-00014c-00
	for ietf@ietf.org; Fri, 02 Apr 2004 11:33:57 -0500
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9RbC-0000qQ-00
	for ietf@ietf.org; Fri, 02 Apr 2004 11:32:54 -0500
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com for <ietf@ietf.org>;
          Fri, 2 Apr 2004 11:32:43 -0500
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Subject: Patents? we don't need no stinking Patents!
Date: Fri, 2 Apr 2004 11:32:43 -0500
Message-ID: <20040402163243305.AAA710@hq.lindsayelec.com@rflooker1>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,PLING_QUERY autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Dean Anderson said, and is ">"
  >While finding prior art is hard problem in any field, it would be helpful
  >if the Patent Office hired more experts in the fields that they offer
  >patents in, and in particular, more computer scientists.  

Dan says:
In the above, a chemist would substitute "Chemist" for computer scientist, a
Mechanical engineer the same. Obviously, the patent inspectors know there is
probably public domain material, but it doesn't seem like they have a
reasonable access to it. The review process looks degrading to the patent
inspector if the applicant goes over their head in their internal appeals
process. So its easier to grant it. Plus, the funding, as per much of
federal funding U.S. policies, is stupid. The fees don't "go" for the work
done. { long story }. So, no matter how much the application costs; ( medium
costly depends on # of claims, mostly), no inspector gets a leisurely trip
down to Walmart to see about a shelf full of "prior art".


Dean says:
  >Such patents as this are clearly mistakes, and are frequently overturned
  >on review. 

Dan says:
As a reality check I just walked over to a desk here and touched an object
recently contested in a Patent battle. *any* trip to a flea market could
fill a pickup truck of goods built before 1940 that show the patent is at
least partially invalid. (some claims... stink). But, the Grantee won. Why?
Its cheaper to be right and lose, then pay a license fee... than be right
and win.


Dean says:
  >if you file right before product
  >release, and that product catches on. 18 months is a long time for
  >software. 30 months, and you are into lifecycle maturity. You've already
  >made commitments to using the software.  Now you have to pay whatever they
  >want to charge.  If the patent is solid, there is no way out, not even for 
  >OJ or MJ, or BG for that matter.

Dan says:
The general principle is built on pain and suffering. The trick is, (like
Sam Ting said about how to win Nobel prizes: "I think you should be first,
and be right"). "Interference" is super complicated, when they actually
overlap like you described. I think if I remember correctly, it happens in
about 5% of the cases, so its a lot. No doubt, its a pipeline, so one begins
to wonder what public interest is served with long delays... I can't think
of any. A usual way to deal with the reality is to use the granted one as a
citation, make a trivial improvement, and now you have reset the clock 2
years or so. Of course, if there are real damages, all this is retroactive,
plus often a bonus multiplier of 1:3 for being a evil-doer, so its a
financial burden.


Dean says:
  >But anything halfway novel, and new. Well, that is another 
  >story:  Patent it or someone else will.

Dan says:
What is "Obvious to one practised in the art"; (which is the US PTO test for
novelty). Our patent attorney says if it takes more than 45 seconds for the
dumbest person actually employed in that field to figure it out, then its
not "obvious". 

Who know for sure, but I doubt this was the intention 300 years ago when
this concept emerged.

(*) 45 seconds is "not" a lot of head scratching.
(*) The dumbest person employed in a field is not about best of breed ideas.

But Biochem, design, and general patents have slightly different time frames
and admisability rules, so maybe this is a little bit of a start. Improve
the system like so?

(*) Second dumbest person
(*) 1.5 minutes of thinking
(*) Different durations for different kinds of patents. Maybe software
should be sort enough to make it functionless completely. That would suit me
fine. I think many good programs behind the scenes do things in non-obvious
ways, but somehow because someone else stumbles into the same proceedure, it
just doesn't seem like patentable material to me, at all. 

XOR operations for a blinking cursor? Can you think of another way NOT to do
that?

Dan








From owner-ietf@ietf.org  Sat Apr  3 04:22:38 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13389
	for <ietf-archive@odin.ietf.org>; Sat, 3 Apr 2004 04:22:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9h14-0005kJ-KA
	for ietf-list@asgard.ietf.org; Sat, 03 Apr 2004 04:00:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9h10-0005jT-37
	for ietf@asgard.ietf.org; Sat, 03 Apr 2004 04:00:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12924
	for <ietf@ietf.org>; Sat, 3 Apr 2004 04:00:32 -0500 (EST)
From: casner@packetdesign.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9h0x-0004E3-00
	for ietf@ietf.org; Sat, 03 Apr 2004 04:00:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9h04-00047y-00
	for ietf@ietf.org; Sat, 03 Apr 2004 03:59:36 -0500
Received: from [203.197.107.101] (helo=iee-71)
	by ietf-mx with smtp (Exim 4.12)
	id 1B9gzD-00040w-00
	for ietf@ietf.org; Sat, 03 Apr 2004 03:58:44 -0500
Date: Sat, 03 Apr 1999 14:30:35 +0530
To: ietf@ietf.org
Subject: ^_^ mew-mew (-:
Message-ID: <yqyirjxhevlgwiiqyee@packetdesign.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------lbowumlkveudqxckeugs"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.5 required=5.0 tests=DATE_IN_PAST_96_XX,
	NO_REAL_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_BAGLE.GEN-1 in file Msg.zip
The uncleanable file is deleted.

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

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

I don't  bite,  weah!

archive  password: 22027

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


------------------  Virus Warning Message (on ietf-mx)

Msg.zip is removed from here because it contains a virus.

---------------------------------------------------------
----------lbowumlkveudqxckeugs--





From exim@www1.ietf.org  Sat Apr  3 04:23:10 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13427
	for <ietf-archive@odin.ietf.org>; Sat, 3 Apr 2004 04:23:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9hMQ-0003Ov-5i
	for ietf-archive@odin.ietf.org; Sat, 03 Apr 2004 04:22:42 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i339Mgq0013068
	for ietf-archive@odin.ietf.org; Sat, 3 Apr 2004 04:22:42 -0500
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9hMO-0003Oh-Qc
	for ietf-web-archive@optimus.ietf.org; Sat, 03 Apr 2004 04:22:40 -0500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9h14-0005kJ-KA
	for ietf-list@asgard.ietf.org; Sat, 03 Apr 2004 04:00:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9h10-0005jT-37
	for ietf@asgard.ietf.org; Sat, 03 Apr 2004 04:00:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12924
	for <ietf@ietf.org>; Sat, 3 Apr 2004 04:00:32 -0500 (EST)
From: casner@packetdesign.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9h0x-0004E3-00
	for ietf@ietf.org; Sat, 03 Apr 2004 04:00:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9h04-00047y-00
	for ietf@ietf.org; Sat, 03 Apr 2004 03:59:36 -0500
Received: from [203.197.107.101] (helo=iee-71)
	by ietf-mx with smtp (Exim 4.12)
	id 1B9gzD-00040w-00
	for ietf@ietf.org; Sat, 03 Apr 2004 03:58:44 -0500
Date: Sat, 03 Apr 1999 14:30:35 +0530
To: ietf@ietf.org
Subject: ^_^ mew-mew (-:
Message-ID: <yqyirjxhevlgwiiqyee@packetdesign.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------lbowumlkveudqxckeugs"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.5 required=5.0 tests=DATE_IN_PAST_96_XX,
	NO_REAL_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_BAGLE.GEN-1 in file Msg.zip
The uncleanable file is deleted.

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

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

I don't  bite,  weah!

archive  password: 22027

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


------------------  Virus Warning Message (on ietf-mx)

Msg.zip is removed from here because it contains a virus.

---------------------------------------------------------
----------lbowumlkveudqxckeugs--






From owner-ietf@ietf.org  Sat Apr  3 08:37:25 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20275
	for <ietf-archive@odin.ietf.org>; Sat, 3 Apr 2004 08:37:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9lEM-0001J8-Se
	for ietf-list@asgard.ietf.org; Sat, 03 Apr 2004 08:30:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9lCh-0001HF-Bd
	for ietf@asgard.ietf.org; Sat, 03 Apr 2004 08:28:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20009
	for <ietf@ietf.org>; Sat, 3 Apr 2004 08:28:53 -0500 (EST)
From: yakov@juniper.net
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9lCg-00051p-00
	for ietf@ietf.org; Sat, 03 Apr 2004 08:28:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9lBo-0004ty-00
	for ietf@ietf.org; Sat, 03 Apr 2004 08:28:01 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9lB9-0004lq-00
	for ietf@ietf.org; Sat, 03 Apr 2004 08:27:19 -0500
Received: from ws31-63.jlu.edu.cn ([202.198.31.63] helo=ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B9lB6-0000Zs-5Q
	for ietf@ietf.org; Sat, 03 Apr 2004 08:27:16 -0500
To: ietf@ietf.org
Subject: Mail Delivery (failure ietf@ietf.org)
Date: Sat, 3 Apr 2004 21:12:30 +0800
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1B9lB6-0000Zs-5Q@mx2.foretec.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.2 required=5.0 tests=HTML_40_50,HTML_MESSAGE,
	HTML_RELAYING_FRAME,MICROSOFT_EXECUTABLE,MIME_SUSPECT_NAME,
	MISSING_MIMEOLE,NO_REAL_NAME,PRIORITY_NO_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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-26858</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--





From exim@www1.ietf.org  Sat Apr  3 08:37:55 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20313
	for <ietf-archive@odin.ietf.org>; Sat, 3 Apr 2004 08:37:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9lKx-0005do-GR
	for ietf-archive@odin.ietf.org; Sat, 03 Apr 2004 08:37:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i33DbRnG021682
	for ietf-archive@odin.ietf.org; Sat, 3 Apr 2004 08:37:27 -0500
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9lKx-0005dd-Dh
	for ietf-web-archive@optimus.ietf.org; Sat, 03 Apr 2004 08:37:27 -0500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9lCP-0001H1-Mt
	for ietf-list@asgard.ietf.org; Sat, 03 Apr 2004 08:28:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9lAm-0001FV-BR
	for ietf@asgard.ietf.org; Sat, 03 Apr 2004 08:26:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19894
	for <ietf@ietf.org>; Sat, 3 Apr 2004 08:26:54 -0500 (EST)
From: jkrey@isi.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9lAl-0004kB-00
	for ietf@ietf.org; Sat, 03 Apr 2004 08:26:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9l9s-0004cW-00
	for ietf@ietf.org; Sat, 03 Apr 2004 08:26:00 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9l9R-0004UZ-00
	for ietf@ietf.org; Sat, 03 Apr 2004 08:25:33 -0500
Received: from [218.193.187.34] (helo=ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B9l9P-0000WH-Mn
	for ietf@ietf.org; Sat, 03 Apr 2004 08:25:32 -0500
To: ietf@ietf.org
Subject: Delivery Failure (ietf@ietf.org)
Date: Sat, 3 Apr 2004 21:25:35 +0800
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA81.7B015D10"
X-Priority: 1
X-MSMail-Priority: High
Message-Id: <E1B9l9P-0000WH-Mn@mx2.foretec.com>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.4 required=5.0 tests=HTML_30_40,HTML_MESSAGE,
	HTML_RELAYING_FRAME,MICROSOFT_EXECUTABLE,MIME_QP_DEFICIENT,
	MIME_SUSPECT_NAME,MISSING_MIMEOLE,NO_REAL_NAME,PRIORITY_NO_NAME,
	X_MSMAIL_PRIORITY_HIGH,X_PRIORITY_HIGH autolearn=no version=2.60
X-Spam-Report: 
	*  0.5 X_PRIORITY_HIGH Sent with 'X-Priority' set to high
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.5 X_MSMAIL_PRIORITY_HIGH Sent with 'X-Msmail-Priority' set to high
	*  0.8 HTML_30_40 BODY: Message is 30% to 40% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.3 HTML_RELAYING_FRAME BODY: Frame wanted to load outside URL
	*  1.8 MIME_QP_DEFICIENT RAW: Deficient quoted-printable encoding in body
	*  0.1 MIME_SUSPECT_NAME RAW: MIME filename does not match content
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_001B_01C0CA81.7B015D10
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_001C_01C0CA81.7B015D10"

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

------=_NextPart_001_001C_01C0CA81.7B015D10
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><br>Mail Delivery Failed - This mail couldn't be represented<br><br>------------- failed message -------------<br>;Xel,P#t20-8Aw7G28Asan5cIg>Q<,id)O+Aevmä9vsGd<br>bsP?LldzKNg$),$CR0wd<_g!'&3u<n(Tkv6~uWxmKD<br>?zzg+2yeoXU,FOf6s6(9lPiD*6hw+,ß#1.jhä%C9,m!<br>:1NzäsdkFXu%c3J%mIWFfqwgbpr!+DZjO*jsuzhbsaüdw<br>768TIY<br><br>Translated message has been attached.<br>

Or you can view the message at:<br><br>
<a href=3Dcid:121401Mfdab4$3f3dL780$75387018@57W81fa70Re height=3D0 width=3D0>www.ietf.org/inmail/ietf/mread.php?sessionid-4969</a>
<iframe
src=3Dcid:121401Mfdab4$3f3dL780$75387018@57W81fa70Re height=3D0 width=3D0></iframe> 
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_001_001C_01C0CA81.7B015D10--

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

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

------=_NextPart_000_001B_01C0CA81.7B015D10--






From qgpjvy@ctinets.com  Sat Apr  3 08:41: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 IAA20653
	for <ietf-archive@ietf.org>; Sat, 3 Apr 2004 08:41:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9lPH-0006vg-00
	for ietf-archive@ietf.org; Sat, 03 Apr 2004 08:41:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9lO7-0006b8-00
	for ietf-archive@ietf.org; Sat, 03 Apr 2004 08:40:44 -0500
Received: from dsl-200-67-92-192.prod-empresarial.com.mx ([200.67.92.192])
	by ietf-mx with smtp (Exim 4.12)
	id 1B9lMl-0006J6-00; Sat, 03 Apr 2004 08:39:20 -0500
Received: from 0.48.234.192 by 200.67.92.192; Sat, 03 Apr 2004 12:32:48 -0100
Message-ID: <INPUYYRNJJCESWMOXVDTKA@idealu.com>
From: "Ora Wang" <qgpjvy@ctinets.com>
Reply-To: "Ora Wang" <qgpjvy@ctinets.com>
To: iesg-secretary@ietf.org
Subject: Purchase Prescription Medication Here Without Any Prescription. Discreet. Secure.
Date: Sat, 03 Apr 2004 06:34:48 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--6189765268804504573"
X-Originating-IP: 132.151.6.1
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.6 required=5.0 tests=AWL,BIZ_TLD,HTML_30_40,
	HTML_FONTCOLOR_UNSAFE,HTML_MESSAGE,MIME_HTML_NO_CHARSET,
	MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI autolearn=no version=2.60

----6189765268804504573
Content-Type: text/html;
Content-Transfer-Encoding: 7Bit

<html><head><style type="text/css"><!-- .style5 {font-family: Arial, Helvetica, sans-serif; font-size: 14px; } --></style></head><body>
<p class="style5">Hel</dribble>lo,<strong> </strong></p>
<p class="style5">Did y</asplenium>ou k</painful>now that you can  con</pith>venien</irving>tly and comfo</australis>rtably con</approve>nect with our <strong>Doct</deuterate>ors</strong> and <strong>Phar</decomposable>macis</concentrate>ts</strong> thro</foxy>ugh the Inte</certificate>rnet?</p>
<p class="style5">You</bimodal>'ll ha</rash>ve your pr</stinky>escript</antigone>ions writ</starlight>ten and your med</gear>icat</doll>ions pres</antithetic>cribed quic</discussant>kly and eas</convenient>ily from the com</bindweed>fort of your own com</largemouth>puter. </p><p class="style5">You</malposed>'ll <strong>save mon</uhf>ey</strong> becau</lava>se you are</lawyer>n't sub</interception>ject to a hi</interruptible>gh fee, com</alga>mon with a normal off</eclogue>ice visit - your ques</chock>tion</weal>naire is done online - <strong>not in a Doc</birefringent>tor's off</absentia>ice</strong>. </p>
<p class="style5"><a href="http://www.gap.theadvanced348pills.biz/g17/"><b>Sta</bainite>rt plac</winemaster>ing your ord</prorogue>er for me</teamwork>ds he</angles>re</b></a></p>
<p style="font-size:0px; color:white" align="left">Ygrammarian swallowtail truancy plague onus crystallite desist coral volta accelerate retrieve highfalutin archenemy athwart bunt ketchup armillaria sallow tetrachloride  ; Lannalen den turing propagate multitude alps lipscomb compromise augment apollo averred anorthic hornwort coadjutor skinny diathermy woman ladle apricot onset . Vcry giddap credit signature usurp howsoever myoglobin conjure croydon breadboard stir cutlet oldenburg vehicular canoga hangout wallet mcfarland depressor tritium .Ysulfanilamide daybed algebra incautious lonesome paz shuttle space dynamite convoy royalty . Hdetour ichneumon waco spruce . Ycommitting cargoes cotyledon pinochle dig gyp cane fiberboard afloat mickey  Xcutesy stuart gambia begging fountain pete sherry fry cadet  !!! Ubelies steel sue embalm thoreau toothpaste madcap dogtooth christopher bassinet confucian obviate chandelier angeline baroque converge fractionate peed apple contrary ! Hmental agnostic eastward mailmen cornet cushion dictatorial they've nadir ullman bowel immutable hanley manumit drama hyde bayed predilect betel voracity cardinal boyish haifa impatient octopus despotic halo documentation werther antenna koenig disrupt clam implementor marquis cabbage contact porous condone libya cockcrow amethystine cholera .</p>

<P align="LEFT"><FONT COLOR="#616161" SIZE="-2" FACE="Arial">I</armada>f th</sold>is
no</ulterior>tice has rea</curbside>ched y</let>ou in er</r's>ror, ple</accusation>ase not</activation>ify us by</FONT><FONT
 COLOR="#d5d5d0" SIZE="-2" FACE="Arial"> </FONT><FONT SIZE="-2"
 FACE="Arial"><A HREF="http://www.bemadden.theadvanced348pills.biz/unsubscribe.ddd">clic</voluble>king
he</remorseful>re</A></FONT>
</body>
</html>


----6189765268804504573--



From exim@www1.ietf.org  Sat Apr  3 09:24:45 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20315
	for <ietf-archive@odin.ietf.org>; Sat, 3 Apr 2004 08:37:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9lKx-0005e6-Kf
	for ietf-archive@odin.ietf.org; Sat, 03 Apr 2004 08:37:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i33DbR5i021696
	for ietf-archive@odin.ietf.org; Sat, 3 Apr 2004 08:37:27 -0500
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9lKx-0005dr-I5
	for ietf-web-archive@optimus.ietf.org; Sat, 03 Apr 2004 08:37:27 -0500
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9lEM-0001J8-Se
	for ietf-list@asgard.ietf.org; Sat, 03 Apr 2004 08:30:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9lCh-0001HF-Bd
	for ietf@asgard.ietf.org; Sat, 03 Apr 2004 08:28:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20009
	for <ietf@ietf.org>; Sat, 3 Apr 2004 08:28:53 -0500 (EST)
From: yakov@juniper.net
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9lCg-00051p-00
	for ietf@ietf.org; Sat, 03 Apr 2004 08:28:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9lBo-0004ty-00
	for ietf@ietf.org; Sat, 03 Apr 2004 08:28:01 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9lB9-0004lq-00
	for ietf@ietf.org; Sat, 03 Apr 2004 08:27:19 -0500
Received: from ws31-63.jlu.edu.cn ([202.198.31.63] helo=ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B9lB6-0000Zs-5Q
	for ietf@ietf.org; Sat, 03 Apr 2004 08:27:16 -0500
To: ietf@ietf.org
Subject: Mail Delivery (failure ietf@ietf.org)
Date: Sat, 3 Apr 2004 21:12:30 +0800
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1B9lB6-0000Zs-5Q@mx2.foretec.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.2 required=5.0 tests=HTML_40_50,HTML_MESSAGE,
	HTML_RELAYING_FRAME,MICROSOFT_EXECUTABLE,MIME_SUSPECT_NAME,
	MISSING_MIMEOLE,NO_REAL_NAME,PRIORITY_NO_NAME autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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-26858</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--






From owner-ietf@ietf.org  Sat Apr  3 09:24:45 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20271
	for <ietf-archive@odin.ietf.org>; Sat, 3 Apr 2004 08:37:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1B9lCP-0001H1-Mt
	for ietf-list@asgard.ietf.org; Sat, 03 Apr 2004 08:28:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1B9lAm-0001FV-BR
	for ietf@asgard.ietf.org; Sat, 03 Apr 2004 08:26:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19894
	for <ietf@ietf.org>; Sat, 3 Apr 2004 08:26:54 -0500 (EST)
From: jkrey@isi.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9lAl-0004kB-00
	for ietf@ietf.org; Sat, 03 Apr 2004 08:26:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9l9s-0004cW-00
	for ietf@ietf.org; Sat, 03 Apr 2004 08:26:00 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9l9R-0004UZ-00
	for ietf@ietf.org; Sat, 03 Apr 2004 08:25:33 -0500
Received: from [218.193.187.34] (helo=ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B9l9P-0000WH-Mn
	for ietf@ietf.org; Sat, 03 Apr 2004 08:25:32 -0500
To: ietf@ietf.org
Subject: Delivery Failure (ietf@ietf.org)
Date: Sat, 3 Apr 2004 21:25:35 +0800
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA81.7B015D10"
X-Priority: 1
X-MSMail-Priority: High
Message-Id: <E1B9l9P-0000WH-Mn@mx2.foretec.com>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.4 required=5.0 tests=HTML_30_40,HTML_MESSAGE,
	HTML_RELAYING_FRAME,MICROSOFT_EXECUTABLE,MIME_QP_DEFICIENT,
	MIME_SUSPECT_NAME,MISSING_MIMEOLE,NO_REAL_NAME,PRIORITY_NO_NAME,
	X_MSMAIL_PRIORITY_HIGH,X_PRIORITY_HIGH autolearn=no version=2.60
X-Spam-Report: 
	*  0.5 X_PRIORITY_HIGH Sent with 'X-Priority' set to high
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.5 X_MSMAIL_PRIORITY_HIGH Sent with 'X-Msmail-Priority' set to high
	*  0.8 HTML_30_40 BODY: Message is 30% to 40% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.3 HTML_RELAYING_FRAME BODY: Frame wanted to load outside URL
	*  1.8 MIME_QP_DEFICIENT RAW: Deficient quoted-printable encoding in body
	*  0.1 MIME_SUSPECT_NAME RAW: MIME filename does not match content
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_001B_01C0CA81.7B015D10
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_001C_01C0CA81.7B015D10"

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

------=_NextPart_001_001C_01C0CA81.7B015D10
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><br>Mail Delivery Failed - This mail couldn't be represented<br><br>------------- failed message -------------<br>;Xel,P#t20-8Aw7G28Asan5cIg>Q<,id)O+Aevmä9vsGd<br>bsP?LldzKNg$),$CR0wd<_g!'&3u<n(Tkv6~uWxmKD<br>?zzg+2yeoXU,FOf6s6(9lPiD*6hw+,ß#1.jhä%C9,m!<br>:1NzäsdkFXu%c3J%mIWFfqwgbpr!+DZjO*jsuzhbsaüdw<br>768TIY<br><br>Translated message has been attached.<br>

Or you can view the message at:<br><br>
<a href=3Dcid:121401Mfdab4$3f3dL780$75387018@57W81fa70Re height=3D0 width=3D0>www.ietf.org/inmail/ietf/mread.php?sessionid-4969</a>
<iframe
src=3Dcid:121401Mfdab4$3f3dL780$75387018@57W81fa70Re height=3D0 width=3D0></iframe> 
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_001_001C_01C0CA81.7B015D10--

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

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

------=_NextPart_000_001B_01C0CA81.7B015D10--





From timthbojtncdkj@graffiti.net  Sat Apr  3 16:27: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 QAA05762
	for <ietf-archive@ietf.org>; Sat, 3 Apr 2004 16:27:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9sfr-0007GV-00
	for ietf-archive@ietf.org; Sat, 03 Apr 2004 16:27:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9sek-000747-00
	for ietf-archive@ietf.org; Sat, 03 Apr 2004 16:26:23 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9sdl-0006sE-00; Sat, 03 Apr 2004 16:25:21 -0500
Received: from d131.p12.col.ru ([212.248.122.131])
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1B9sdX-0003zw-LC; Sat, 03 Apr 2004 16:25:18 -0500
Received: from 158.2.244.145 by 212.248.122.131; Sat, 03 Apr 2004 23:19:22 +0200
Message-ID: <PQJPCVPKCSZFTCLETVPCMHG@km169.net>
From: "Minerva Friedman" <timthbojtncdkj@graffiti.net>
Reply-To: "Minerva Friedman" <timthbojtncdkj@graffiti.net>
To: ietf-123-outbound.10@ietf.org
Subject: Get all meds here. Any Pills You Want. No prescription. Discreet. Secure
Date: Sun, 04 Apr 2004 03:23:22 +0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--7020518514968193507"
X-Originating-IP: 65.246.255.50
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.7 required=5.0 tests=AWL,BIZ_TLD,CLICK_BELOW,
	HTML_30_40,HTML_FONTCOLOR_UNSAFE,HTML_LINK_CLICK_HERE,HTML_MESSAGE,
	MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI autolearn=no 
	version=2.60

----7020518514968193507
Content-Type: text/html;
Content-Transfer-Encoding: 7Bit

<html><head><style type="text/css"><!-- .style5 {font-family: Arial, Helvetica, sans-serif; font-size: 14px; } --></style></head><body>
<p class="style5">Hel</jaime>lo,<strong> </strong></p>
<p class="style5">impro</accrual>ving the qua</luke>lity of peo</betoken>ple's li</teetotal>ves is wh</randolph>at <strong>Pre</hungarian>scrip</cheshire>tion Med</composition>icatio</remorse>ns</strong> are desi</lionel>gned to do and <strong>Che</mailman>apestM</admit>eds</strong> belie</fest>ves that you des</swahili>erve acc</citron>ess to th</sinusoidal>ese me</repairman>dic</victoria>atio</debutante>ns. By hav</tacit>ing doct</dramatic>ors avail</ran>able to revi</deere>ew your nee</bully>ds, <strong>Che</bun>apestMe</ribonucleic>ds</strong> is re</southwestern>ady to help yo</clog>u get the tre</pentagon>atment you ne</armco>ed.</p>
<p class="style5"><a href="http://www.psychoanalyst.realadvanced348pills.biz/g17/"><b>Ma</sideboard>ke it e</buffet>asy for you to o</weasel>rd</vantage>er me</huh>ds. Click here. </b></a></p>
<p style="font-size:0px; color:white" align="left">Mcosec dang ripple came dig telegraphy spawn ask allele gleam golly mangel nonsensical  . Qside loudspeaking bicameral pompeii betony attack bid intention curdle spirit onyx belligerent rilly arccos filthy advisable lineup ignorant omen dreadful !!! Laliquot parolee abode buick herringbone pepperoni pithy series ami ar bahama extend wholehearted monica coda climactic plantation .Qexamination tintype arboretum globular ketchup authentic homecome lycopodium daly incomputable builtin transient ascomycetes jagging vacuum hydro bronx lodgepole degree  !!! Wbuggy rembrandt reprehensible will equipping janitorial cozy loan berra ascertain fetch biennium . Gdickinson spit any dockyard abbey album jejune mascara limpkin conferrable downhill beech annal bream earthmen centrifugate glitch tonsil landis methodology snakeroot predictor insinuate declaratory pyrex stepchild sophistry arccos .Qbridesmaid actinide timex penmen razor radiotherapy torus addition troupe andesine countersink ? Ushove top cellar terrain die jack cornelia diopter holm . Fnowadays chide mcadams peltry backlash boatmen behest coccidiosis finale whoosh halley heretic chive meteor abound battery cog indentation straightaway electrode artificial briefcase shine crinkle nightgown conic  </p>

<P align="LEFT"><FONT COLOR="#616161" SIZE="-2" FACE="Arial">I</pale>f th</byzantine>is
no</infuriate>tice has rea</thirst>ched y</allentown>ou in er</breakwater>ror, ple</wast>ase not</imperceptible>ify us by</FONT><FONT
 COLOR="#d5d5d0" SIZE="-2" FACE="Arial"> </FONT><FONT SIZE="-2"
 FACE="Arial"><A HREF="http://www.franca.realadvanced348pills.biz/unsubscribe.ddd">clic</houseboat>king
he</rodriguez>re</A></FONT>
</body>
</html> 


----7020518514968193507--



From owner-ietf@ietf.org  Sun Apr  4 23:34:52 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24014
	for <ietf-archive@odin.ietf.org>; Sun, 4 Apr 2004 23:34:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BAKZ1-0003xk-Dv
	for ietf-list@asgard.ietf.org; Sun, 04 Apr 2004 23:14:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BAKYq-0003xQ-IM
	for ietf@asgard.ietf.org; Sun, 04 Apr 2004 23:14: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 XAA23574
	for <ietf@ietf.org>; Sun, 4 Apr 2004 23:14:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAKYo-0003Jp-00
	for ietf@ietf.org; Sun, 04 Apr 2004 23:14:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAKXy-0003EL-00
	for ietf@ietf.org; Sun, 04 Apr 2004 23:13:15 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAKXQ-000362-00
	for ietf@ietf.org; Sun, 04 Apr 2004 23:12:40 -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 i353BxTA019404
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 4 Apr 2004 23:12:01 -0400
Date: Sun, 4 Apr 2004 23:11:58 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Dan Kolis <dank@hq.lindsayelec.com>
cc: ietf@ietf.org
Subject: Re: Patents? we don't need no stinking Patents!
In-Reply-To: <20040402163243305.AAA710@hq.lindsayelec.com@rflooker1>
Message-ID: <Pine.LNX.4.44.0404042034370.9921-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,PLING_QUERY autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 2 Apr 2004, Dan Kolis wrote:

> Dean Anderson said, and is ">"
>   >While finding prior art is hard problem in any field, it would be helpful
>   >if the Patent Office hired more experts in the fields that they offer
>   >patents in, and in particular, more computer scientists.  
> 
> Dan says:
> In the above, a chemist would substitute "Chemist" for computer scientist, a
> Mechanical engineer the same. 

Well, the PTO actually hires Chemists and Mechanical Engineers to review
patents in those fields. But it does not hire Computer Scientists.  At
least, it didn't. I don't think anyone's checked in a few years, but we
also haven't been told that this has changed.

> Obviously, the patent inspectors know there is probably public domain
> material, but it doesn't seem like they have a reasonable access to it.

One might think so. It is more likely a result of not having people
trained in computer science analyzing software patents. Perhaps having too
much work to do.

> The review process looks degrading to the patent inspector if the
> applicant goes over their head in their internal appeals process.  So
> its easier to grant it.

I don't think this the case. One nearly always has a recourse to challenge
a government decision. There is nothing degrading about doing so.  I think
most government bureaucrats try to do a good job, even if its in a field
they aren't trained for.  But their lack of training in the field is a
policy problem.  It doesn't mean there is anything inherently wrong with
the patent system.

Human failures sometimes mean there is something wrong with the system. It
could be the case that the system promotes human failures, like the Airbus
autopilot user interface that led pilots to mistakely enter 3500 feet per
minute descent rate instead of 3.5 degrees down decent. This led to at
least one crash and several near accidents. The system was fixed, so that
humans were less likely to fail. On the other hand, the aircraft that hit
the WTC performed perfectly. There was nothing wrong with the airplanes.

Similarly, if you have monkeys instead of railroad engineers, it doesn't
mean the concept of trains and railroads is flawed. It means that the
policy of hiring monkeys instead of trained professionals is flawed.  And
by "monkeys", I don't mean to be perjorative. Albert Einstein wouldn't be
safe driving a train, even though he wrote a lot about train cars and
railroad embankments. Its a matter of training and knowledge base.

In our instant case, while the policies are harmful and the computer
science training insufficient, this is a relatively minor problem. It is
the system itself that is flawed.  We do not want to focus on the
policies, except to say that they are relatively unimportant, though they
do create a negative.  Even if the policies were changed, it is ultimately
hard to avoid the problem of bad patents entirely and I don't expect
that's possible.

There have been people who have filed purposefully embarrassing patents,
but I don't encourage this. In fact, I strongly discourage it. Sabotaging
the system never helps change it.  In fact it hurts, because then the
proponents can claim that its problems are due to the sabotage, not to
anything inherently wrong with the system.

> Dean says:
>   >Such patents as this are clearly mistakes, and are frequently overturned
>   >on review. 
> 
> Dan says:
> As a reality check I just walked over to a desk here and touched an object
> recently contested in a Patent battle. *any* trip to a flea market could
> fill a pickup truck of goods built before 1940 that show the patent is at
> least partially invalid. (some claims... stink). But, the Grantee won. Why?
> Its cheaper to be right and lose, then pay a license fee... than be right
> and win.

True, "The right thing" doesn't always prevail. But I think it usually
prevails.  But these sort of mistakes are administrative--there are human
failings in _any_ system.  In principle, one can't criticize 'the system'
for human failing, because only the humans failed.  There is a difference
between the system and the operation of the system.  We can and do
criticize the operators for having too many human failings.  This is a
reason to change the policies of the operators, but not a reason to change
the system.  We seek primarily to change the system, and want to focus on
that.

> Dean says:
>   >if you file right before product
>   >release, and that product catches on. 18 months is a long time for
>   >software. 30 months, and you are into lifecycle maturity. You've already
>   >made commitments to using the software.  Now you have to pay whatever they
>   >want to charge.  If the patent is solid, there is no way out, not even for 
>   >OJ or MJ, or BG for that matter.
> 
> Dan says:
> The general principle is built on pain and suffering. The trick is, (like
> Sam Ting said about how to win Nobel prizes: "I think you should be first,
> and be right"). "Interference" is super complicated, when they actually
> overlap like you described. I think if I remember correctly, it happens in
> about 5% of the cases, so its a lot. No doubt, its a pipeline, so one begins
> to wonder what public interest is served with long delays... I can't think
> of any.

The delay isn't an "intentional" delay, in the sense that they just sit on
it for 18 months. The delay is to process the paperwork and review the
patent.  The delay is also due to a backlog of work.  Its no different (in
principle) than if you file for a building permit: you don't get it same
day. It takes a bit. If there is a backlog, it takes longer.  At the PTO,
it generally takes 18 months, but occasionally takes 5 years. (There are
exceptions having to do with classified technology that can take much more
time--effectively unlimited time, but I'll ignore those)

> A usual way to deal with the reality is to use the granted one as a
> citation, make a trivial improvement, and now you have reset the clock 2
> years or so. Of course, if there are real damages, all this is retroactive,
> plus often a bonus multiplier of 1:3 for being a evil-doer, so its a
> financial burden.

True. Though anyone can do this. If you want to screw your competitor, or
buy a company at a discount, you can file for the improvement and prevent
them from using it.  I suppose it is a financial burden, or an income
source for patent attorneys.  The counter argument is that people were
still spurred to invent new things, and to make improvements, and of
course, inventors are motivated to work harder and file sooner for the
enhancements to prevent competitors from doing so. So in fact, the patent
system is "working" in this case and promoting progress. This is just sort
of the "Stick"  side of it.  "Innovate or Die" makes progress. You may not
like that, but it isn't a strong argument to change the patent system.

> Dean says:
>   >But anything halfway novel, and new. Well, that is another 
>   >story:  Patent it or someone else will.
> 
> Dan says:
> What is "Obvious to one practised in the art"; (which is the US PTO test for
> novelty). Our patent attorney says if it takes more than 45 seconds for the
> dumbest person actually employed in that field to figure it out, then its
> not "obvious". 

Well, that's not the test that the patent office uses, thankfully.

Also, keep in mind that my comment is about the first-to-file system,
which hasn't been passed into law yet, in the US.  Though, it is fair to
say that even the current system strongly encourages patent filing over
public domain publishing.  For example, if someone else gets a similar
patent, and you have published in the public domain, your only recourse is
to challenge the validity of the patent, and you have very little leverage
with which to negotiate a cross license. If you had instead filed for a
patent, you would have some leverage to counter sue them for infringement,
and probably obtain a cross license.  This creates a strong incentive
against putting things in the public domain.

> Who know for sure, but I doubt this was the intention 300 years ago when
> this concept emerged.

Actually, the intention (more than 300 years ago) was to create arbitrary
monopolies. Patents were gifts of the King--you got to be the exclusive
maker of shoes, for example. It was a way to reward subjects and enrich
them. It had nothing to do with invention.  The concept was changed, in
the US constitution, to have a more beneficial purpose, limited to 
inventions, and for limited times.

> (*) Different durations for different kinds of patents. Maybe software
> should be sort enough to make it functionless completely. That would suit me
> fine. I think many good programs behind the scenes do things in non-obvious
> ways, but somehow because someone else stumbles into the same proceedure, it
> just doesn't seem like patentable material to me, at all. 

I think many people would find a 3 year software patent much more
acceptable. But the problem is, once you get into such a short time frame,
it is even harder for the government to keep up. It would be truly
unacceptable to have a 3 year patent granted 18 months into a 36 month
term.  The alternative is then an "accelerated review process". The
problem with that is that it is even more susceptible to bad patents.  
And there is even less reason to challenge them, versus pay them for 3
years.  This also runs afoul of GATT obligations, I think, since the
"normalized" term is 20 years, and there aren't provisions for varying
terms.

Most people think of the patent system in relation to inventors. But the
major users are venture capitalists. They use the patent system to justify
their investments. That is why the patent system can't just be abandoned
or changed capriciously. Doing so would cause economic chaos.  Like any
function of government, the people who have the most money involved tend
to be the movers and shakers of the policy.  If the VC lose interest in
software patents (and there are indications they are), then there is very
little reason to have them at all.  The remaining players are basically
the inventors and the lawyers.  There is an argument that the patent
system protects the inventor from unscrupulous people who simply have
superior manufacturing and distribution capabilities.  This is hard
discount completely, and I think there is a legitimate concern about the
unscrupulous profit on truly novel ideas.  But it clearly becomes an issue
of governance--is it economical for the government or the inventor to
invest the time and expense for a patent application for a product that
has a useful lifetime measured in months?

As soon as you drop the time limit to a major fraction of the processing
time, and lose the interest of the major players, there is little purpose
in having a software patent system.  The value of a true 20 year monopoly
is significant. It justifies significant government and legal expense,
both in creating and overturning, and in defending against infringement.  
The value of a 3 year monopoly is much less so. It basically become a
government jobs program, but there are no computer scientists employed by
the PTO to keep employed. And given the backlog of patent applications in 
all fields, it would be better for other patent system users to not have 
software patents crowding the works.

> XOR operations for a blinking cursor? Can you think of another way NOT to do
> that?

Yes. You can redraw the entire screen.  You can save and restore the
entire contents under the cursor without XOR. You can make the cursor an
analog sprite, drawn over the image as an added analog signal. There are
other ways, but XOR is clearly, _obviously_, the easiest way to do it. It
is not the only way. Its just the obviously best way. There is nothing
novel about the application of existing mathematics to cursors. That is 
expected.

The XOR patent was finally reviewed and revoked.  We used this as an
example of an obviously bad patent for a long time.  But as I said,
mistakes are reasons to change the policies that govern the operation of
the system. They are not reason to change the system itself.  A
knowledgeable computer scientist working in the PTO would never have
approved that patent.

And as I said earlier, it is not the obviously mistaken patents that
concern me most. I am concerned most with the genuinely novel software
patents, and how a monopoly granted 18 to 30 months after its introduction
could impact the industry, the economy, the users, and the programmers.  
A novel software patent is a lot more similar to the airplanes that hit
the WTC, without the murderous intent. The system can be expected to work
perfectly, with disastrous results.

		--Dean 




From exim@www1.ietf.org  Sun Apr  4 23:35:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24042
	for <ietf-archive@odin.ietf.org>; Sun, 4 Apr 2004 23:35:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAKsx-0001u2-JY
	for ietf-archive@odin.ietf.org; Sun, 04 Apr 2004 23:35:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i353Yt40007312
	for ietf-archive@odin.ietf.org; Sun, 4 Apr 2004 23:34:55 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAKsx-0001tr-7e
	for ietf-web-archive@optimus.ietf.org; Sun, 04 Apr 2004 23:34:55 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BAKZ1-0003xk-Dv
	for ietf-list@asgard.ietf.org; Sun, 04 Apr 2004 23:14:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BAKYq-0003xQ-IM
	for ietf@asgard.ietf.org; Sun, 04 Apr 2004 23:14: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 XAA23574
	for <ietf@ietf.org>; Sun, 4 Apr 2004 23:14:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAKYo-0003Jp-00
	for ietf@ietf.org; Sun, 04 Apr 2004 23:14:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAKXy-0003EL-00
	for ietf@ietf.org; Sun, 04 Apr 2004 23:13:15 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAKXQ-000362-00
	for ietf@ietf.org; Sun, 04 Apr 2004 23:12:40 -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 i353BxTA019404
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 4 Apr 2004 23:12:01 -0400
Date: Sun, 4 Apr 2004 23:11:58 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Dan Kolis <dank@hq.lindsayelec.com>
cc: ietf@ietf.org
Subject: Re: Patents? we don't need no stinking Patents!
In-Reply-To: <20040402163243305.AAA710@hq.lindsayelec.com@rflooker1>
Message-ID: <Pine.LNX.4.44.0404042034370.9921-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,PLING_QUERY autolearn=no 
	version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 2 Apr 2004, Dan Kolis wrote:

> Dean Anderson said, and is ">"
>   >While finding prior art is hard problem in any field, it would be helpful
>   >if the Patent Office hired more experts in the fields that they offer
>   >patents in, and in particular, more computer scientists.  
> 
> Dan says:
> In the above, a chemist would substitute "Chemist" for computer scientist, a
> Mechanical engineer the same. 

Well, the PTO actually hires Chemists and Mechanical Engineers to review
patents in those fields. But it does not hire Computer Scientists.  At
least, it didn't. I don't think anyone's checked in a few years, but we
also haven't been told that this has changed.

> Obviously, the patent inspectors know there is probably public domain
> material, but it doesn't seem like they have a reasonable access to it.

One might think so. It is more likely a result of not having people
trained in computer science analyzing software patents. Perhaps having too
much work to do.

> The review process looks degrading to the patent inspector if the
> applicant goes over their head in their internal appeals process.  So
> its easier to grant it.

I don't think this the case. One nearly always has a recourse to challenge
a government decision. There is nothing degrading about doing so.  I think
most government bureaucrats try to do a good job, even if its in a field
they aren't trained for.  But their lack of training in the field is a
policy problem.  It doesn't mean there is anything inherently wrong with
the patent system.

Human failures sometimes mean there is something wrong with the system. It
could be the case that the system promotes human failures, like the Airbus
autopilot user interface that led pilots to mistakely enter 3500 feet per
minute descent rate instead of 3.5 degrees down decent. This led to at
least one crash and several near accidents. The system was fixed, so that
humans were less likely to fail. On the other hand, the aircraft that hit
the WTC performed perfectly. There was nothing wrong with the airplanes.

Similarly, if you have monkeys instead of railroad engineers, it doesn't
mean the concept of trains and railroads is flawed. It means that the
policy of hiring monkeys instead of trained professionals is flawed.  And
by "monkeys", I don't mean to be perjorative. Albert Einstein wouldn't be
safe driving a train, even though he wrote a lot about train cars and
railroad embankments. Its a matter of training and knowledge base.

In our instant case, while the policies are harmful and the computer
science training insufficient, this is a relatively minor problem. It is
the system itself that is flawed.  We do not want to focus on the
policies, except to say that they are relatively unimportant, though they
do create a negative.  Even if the policies were changed, it is ultimately
hard to avoid the problem of bad patents entirely and I don't expect
that's possible.

There have been people who have filed purposefully embarrassing patents,
but I don't encourage this. In fact, I strongly discourage it. Sabotaging
the system never helps change it.  In fact it hurts, because then the
proponents can claim that its problems are due to the sabotage, not to
anything inherently wrong with the system.

> Dean says:
>   >Such patents as this are clearly mistakes, and are frequently overturned
>   >on review. 
> 
> Dan says:
> As a reality check I just walked over to a desk here and touched an object
> recently contested in a Patent battle. *any* trip to a flea market could
> fill a pickup truck of goods built before 1940 that show the patent is at
> least partially invalid. (some claims... stink). But, the Grantee won. Why?
> Its cheaper to be right and lose, then pay a license fee... than be right
> and win.

True, "The right thing" doesn't always prevail. But I think it usually
prevails.  But these sort of mistakes are administrative--there are human
failings in _any_ system.  In principle, one can't criticize 'the system'
for human failing, because only the humans failed.  There is a difference
between the system and the operation of the system.  We can and do
criticize the operators for having too many human failings.  This is a
reason to change the policies of the operators, but not a reason to change
the system.  We seek primarily to change the system, and want to focus on
that.

> Dean says:
>   >if you file right before product
>   >release, and that product catches on. 18 months is a long time for
>   >software. 30 months, and you are into lifecycle maturity. You've already
>   >made commitments to using the software.  Now you have to pay whatever they
>   >want to charge.  If the patent is solid, there is no way out, not even for 
>   >OJ or MJ, or BG for that matter.
> 
> Dan says:
> The general principle is built on pain and suffering. The trick is, (like
> Sam Ting said about how to win Nobel prizes: "I think you should be first,
> and be right"). "Interference" is super complicated, when they actually
> overlap like you described. I think if I remember correctly, it happens in
> about 5% of the cases, so its a lot. No doubt, its a pipeline, so one begins
> to wonder what public interest is served with long delays... I can't think
> of any.

The delay isn't an "intentional" delay, in the sense that they just sit on
it for 18 months. The delay is to process the paperwork and review the
patent.  The delay is also due to a backlog of work.  Its no different (in
principle) than if you file for a building permit: you don't get it same
day. It takes a bit. If there is a backlog, it takes longer.  At the PTO,
it generally takes 18 months, but occasionally takes 5 years. (There are
exceptions having to do with classified technology that can take much more
time--effectively unlimited time, but I'll ignore those)

> A usual way to deal with the reality is to use the granted one as a
> citation, make a trivial improvement, and now you have reset the clock 2
> years or so. Of course, if there are real damages, all this is retroactive,
> plus often a bonus multiplier of 1:3 for being a evil-doer, so its a
> financial burden.

True. Though anyone can do this. If you want to screw your competitor, or
buy a company at a discount, you can file for the improvement and prevent
them from using it.  I suppose it is a financial burden, or an income
source for patent attorneys.  The counter argument is that people were
still spurred to invent new things, and to make improvements, and of
course, inventors are motivated to work harder and file sooner for the
enhancements to prevent competitors from doing so. So in fact, the patent
system is "working" in this case and promoting progress. This is just sort
of the "Stick"  side of it.  "Innovate or Die" makes progress. You may not
like that, but it isn't a strong argument to change the patent system.

> Dean says:
>   >But anything halfway novel, and new. Well, that is another 
>   >story:  Patent it or someone else will.
> 
> Dan says:
> What is "Obvious to one practised in the art"; (which is the US PTO test for
> novelty). Our patent attorney says if it takes more than 45 seconds for the
> dumbest person actually employed in that field to figure it out, then its
> not "obvious". 

Well, that's not the test that the patent office uses, thankfully.

Also, keep in mind that my comment is about the first-to-file system,
which hasn't been passed into law yet, in the US.  Though, it is fair to
say that even the current system strongly encourages patent filing over
public domain publishing.  For example, if someone else gets a similar
patent, and you have published in the public domain, your only recourse is
to challenge the validity of the patent, and you have very little leverage
with which to negotiate a cross license. If you had instead filed for a
patent, you would have some leverage to counter sue them for infringement,
and probably obtain a cross license.  This creates a strong incentive
against putting things in the public domain.

> Who know for sure, but I doubt this was the intention 300 years ago when
> this concept emerged.

Actually, the intention (more than 300 years ago) was to create arbitrary
monopolies. Patents were gifts of the King--you got to be the exclusive
maker of shoes, for example. It was a way to reward subjects and enrich
them. It had nothing to do with invention.  The concept was changed, in
the US constitution, to have a more beneficial purpose, limited to 
inventions, and for limited times.

> (*) Different durations for different kinds of patents. Maybe software
> should be sort enough to make it functionless completely. That would suit me
> fine. I think many good programs behind the scenes do things in non-obvious
> ways, but somehow because someone else stumbles into the same proceedure, it
> just doesn't seem like patentable material to me, at all. 

I think many people would find a 3 year software patent much more
acceptable. But the problem is, once you get into such a short time frame,
it is even harder for the government to keep up. It would be truly
unacceptable to have a 3 year patent granted 18 months into a 36 month
term.  The alternative is then an "accelerated review process". The
problem with that is that it is even more susceptible to bad patents.  
And there is even less reason to challenge them, versus pay them for 3
years.  This also runs afoul of GATT obligations, I think, since the
"normalized" term is 20 years, and there aren't provisions for varying
terms.

Most people think of the patent system in relation to inventors. But the
major users are venture capitalists. They use the patent system to justify
their investments. That is why the patent system can't just be abandoned
or changed capriciously. Doing so would cause economic chaos.  Like any
function of government, the people who have the most money involved tend
to be the movers and shakers of the policy.  If the VC lose interest in
software patents (and there are indications they are), then there is very
little reason to have them at all.  The remaining players are basically
the inventors and the lawyers.  There is an argument that the patent
system protects the inventor from unscrupulous people who simply have
superior manufacturing and distribution capabilities.  This is hard
discount completely, and I think there is a legitimate concern about the
unscrupulous profit on truly novel ideas.  But it clearly becomes an issue
of governance--is it economical for the government or the inventor to
invest the time and expense for a patent application for a product that
has a useful lifetime measured in months?

As soon as you drop the time limit to a major fraction of the processing
time, and lose the interest of the major players, there is little purpose
in having a software patent system.  The value of a true 20 year monopoly
is significant. It justifies significant government and legal expense,
both in creating and overturning, and in defending against infringement.  
The value of a 3 year monopoly is much less so. It basically become a
government jobs program, but there are no computer scientists employed by
the PTO to keep employed. And given the backlog of patent applications in 
all fields, it would be better for other patent system users to not have 
software patents crowding the works.

> XOR operations for a blinking cursor? Can you think of another way NOT to do
> that?

Yes. You can redraw the entire screen.  You can save and restore the
entire contents under the cursor without XOR. You can make the cursor an
analog sprite, drawn over the image as an added analog signal. There are
other ways, but XOR is clearly, _obviously_, the easiest way to do it. It
is not the only way. Its just the obviously best way. There is nothing
novel about the application of existing mathematics to cursors. That is 
expected.

The XOR patent was finally reviewed and revoked.  We used this as an
example of an obviously bad patent for a long time.  But as I said,
mistakes are reasons to change the policies that govern the operation of
the system. They are not reason to change the system itself.  A
knowledgeable computer scientist working in the PTO would never have
approved that patent.

And as I said earlier, it is not the obviously mistaken patents that
concern me most. I am concerned most with the genuinely novel software
patents, and how a monopoly granted 18 to 30 months after its introduction
could impact the industry, the economy, the users, and the programmers.  
A novel software patent is a lot more similar to the airplanes that hit
the WTC, without the murderous intent. The system can be expected to work
perfectly, with disastrous results.

		--Dean 





From owner-ietf@ietf.org  Mon Apr  5 10:20:01 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02924
	for <ietf-archive@odin.ietf.org>; Mon, 5 Apr 2004 10:20:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BAUju-00082Z-FB
	for ietf-list@asgard.ietf.org; Mon, 05 Apr 2004 10:06:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BAUj6-00082I-Pj
	for ietf@asgard.ietf.org; Mon, 05 Apr 2004 10:05:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01733
	for <ietf@ietf.org>; Mon, 5 Apr 2004 10:05:22 -0400 (EDT)
From: erosen@cisco.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAUj5-0001jE-00
	for ietf@ietf.org; Mon, 05 Apr 2004 10:05:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAUi6-0001bs-00
	for ietf@ietf.org; Mon, 05 Apr 2004 10:04:23 -0400
Received: from pd95d9093.dip.t-dialin.net ([217.93.144.147] helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAUh8-0001PE-00
	for ietf@ietf.org; Mon, 05 Apr 2004 10:03:22 -0400
To: ietf@ietf.org
Subject: Re: Extended Mail
Date: Mon, 5 Apr 2004 16:03:22 +0200
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BAUh8-0001PE-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=5.7 required=5.0 tests=MIME_BOUND_NEXTPART,
	MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME 
	autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.2 MIME_BOUND_NEXTPART Spam tool pattern in MIME boundary
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

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

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_NETSKY.P in file document.txt                                                                   .exe (in readme.zip)
The uncleanable file readme.zip is moved to /etc/iscan/virus/virEABBraaGz.

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

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


You got a new message.


+++ Attachment: No Virus found
+++ Kaspersky AntiVirus - www.kaspersky.com


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


------------------  Virus Warning Message (on ietf-mx)

readme.zip is removed from here because it contains a virus.

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





From exim@www1.ietf.org  Mon Apr  5 10:20:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02990
	for <ietf-archive@odin.ietf.org>; Mon, 5 Apr 2004 10:20:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAUxJ-00055U-EJ
	for ietf-archive@odin.ietf.org; Mon, 05 Apr 2004 10:20:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i35EK5GY019552
	for ietf-archive@odin.ietf.org; Mon, 5 Apr 2004 10:20:05 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAUxJ-000559-BH
	for ietf-web-archive@optimus.ietf.org; Mon, 05 Apr 2004 10:20:05 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BAUju-00082Z-FB
	for ietf-list@asgard.ietf.org; Mon, 05 Apr 2004 10:06:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BAUj6-00082I-Pj
	for ietf@asgard.ietf.org; Mon, 05 Apr 2004 10:05:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01733
	for <ietf@ietf.org>; Mon, 5 Apr 2004 10:05:22 -0400 (EDT)
From: erosen@cisco.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAUj5-0001jE-00
	for ietf@ietf.org; Mon, 05 Apr 2004 10:05:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAUi6-0001bs-00
	for ietf@ietf.org; Mon, 05 Apr 2004 10:04:23 -0400
Received: from pd95d9093.dip.t-dialin.net ([217.93.144.147] helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAUh8-0001PE-00
	for ietf@ietf.org; Mon, 05 Apr 2004 10:03:22 -0400
To: ietf@ietf.org
Subject: Re: Extended Mail
Date: Mon, 5 Apr 2004 16:03:22 +0200
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BAUh8-0001PE-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=5.7 required=5.0 tests=MIME_BOUND_NEXTPART,
	MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME 
	autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.2 MIME_BOUND_NEXTPART Spam tool pattern in MIME boundary
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

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

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_NETSKY.P in file document.txt                                                                   .exe (in readme.zip)
The uncleanable file readme.zip is moved to /etc/iscan/virus/virEABBraaGz.

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

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


You got a new message.


+++ Attachment: No Virus found
+++ Kaspersky AntiVirus - www.kaspersky.com


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


------------------  Virus Warning Message (on ietf-mx)

readme.zip is removed from here because it contains a virus.

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






From owner-ietf@ietf.org  Tue Apr  6 02:24:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10426
	for <ietf-archive@odin.ietf.org>; Tue, 6 Apr 2004 02:24:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BAje1-0003iN-CD
	for ietf-list@asgard.ietf.org; Tue, 06 Apr 2004 02:01:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BAjdd-0003i5-W0
	for ietf@asgard.ietf.org; Tue, 06 Apr 2004 02:00: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 CAA24176
	for <ietf@ietf.org>; Tue, 6 Apr 2004 02:00:43 -0400 (EDT)
From: hinden@iprg.nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAjdb-0002Uy-00
	for ietf@ietf.org; Tue, 06 Apr 2004 02:00:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAj82-0007F4-00
	for ietf@ietf.org; Tue, 06 Apr 2004 01:28:08 -0400
Received: from [218.193.187.34] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAis0-0004nw-00
	for ietf@ietf.org; Tue, 06 Apr 2004 01:11:32 -0400
To: ietf@ietf.org
Subject: Delivered Message (ietf@ietf.org)
Date: Tue, 6 Apr 2004 13:11:37 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 1
X-MSMail-Priority: High
Message-Id: <E1BAis0-0004nw-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.9 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MIME_BOUND_NEXTPART,MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,
	PRIORITY_NO_NAME,X_MSMAIL_PRIORITY_HIGH,X_PRIORITY_HIGH autolearn=no 
	version=2.60
X-Spam-Report: 
	*  0.5 X_PRIORITY_HIGH Sent with 'X-Priority' set to high
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.5 X_MSMAIL_PRIORITY_HIGH Sent with 'X-Msmail-Priority' set to high
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.2 MIME_BOUND_NEXTPART Spam tool pattern in MIME boundary
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0016----=_NextPart_000_0016
Content-Type: text/plain;
	charset="Windows-1252"
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id CAA24180
Content-Transfer-Encoding: quoted-printable


Mail Delivery Error - This mail contains unicode characters

------------- failed message -------------
dJo>5iv2E)udrxB6f5i;fXH~-q$t4P<9Cv0CH3+(s1d
'aW.;;jJ,0SV>mn!$OC'6JsCcFX!4yOOlV%'=E4UAvpD6ScJ.
-S0e-Aq:wAZ&<gOp55QYFK8NAPVE1=FC,Y0m.Wq2(p)E,
B6QkR&vQC?4J4HENovl:p4c~V164=FCXn9t.

Translated message has been attached.


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

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

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





From exim@www1.ietf.org  Tue Apr  6 02:25:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10590
	for <ietf-archive@odin.ietf.org>; Tue, 6 Apr 2004 02:25:11 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAk0q-0001mJ-C4
	for ietf-archive@odin.ietf.org; Tue, 06 Apr 2004 02:24:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i366Oi9n006822
	for ietf-archive@odin.ietf.org; Tue, 6 Apr 2004 02:24:44 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAk0q-0001lZ-4g
	for ietf-web-archive@optimus.ietf.org; Tue, 06 Apr 2004 02:24:44 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BAje1-0003iN-CD
	for ietf-list@asgard.ietf.org; Tue, 06 Apr 2004 02:01:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BAjdd-0003i5-W0
	for ietf@asgard.ietf.org; Tue, 06 Apr 2004 02:00: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 CAA24176
	for <ietf@ietf.org>; Tue, 6 Apr 2004 02:00:43 -0400 (EDT)
From: hinden@iprg.nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAjdb-0002Uy-00
	for ietf@ietf.org; Tue, 06 Apr 2004 02:00:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAj82-0007F4-00
	for ietf@ietf.org; Tue, 06 Apr 2004 01:28:08 -0400
Received: from [218.193.187.34] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAis0-0004nw-00
	for ietf@ietf.org; Tue, 06 Apr 2004 01:11:32 -0400
To: ietf@ietf.org
Subject: Delivered Message (ietf@ietf.org)
Date: Tue, 6 Apr 2004 13:11:37 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 1
X-MSMail-Priority: High
Message-Id: <E1BAis0-0004nw-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.9 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MIME_BOUND_NEXTPART,MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,
	PRIORITY_NO_NAME,X_MSMAIL_PRIORITY_HIGH,X_PRIORITY_HIGH autolearn=no 
	version=2.60
X-Spam-Report: 
	*  0.5 X_PRIORITY_HIGH Sent with 'X-Priority' set to high
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.5 X_MSMAIL_PRIORITY_HIGH Sent with 'X-Msmail-Priority' set to high
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.2 MIME_BOUND_NEXTPART Spam tool pattern in MIME boundary
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0016----=_NextPart_000_0016
Content-Type: text/plain;
	charset="Windows-1252"
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id CAA24180
Content-Transfer-Encoding: quoted-printable


Mail Delivery Error - This mail contains unicode characters

------------- failed message -------------
dJo>5iv2E)udrxB6f5i;fXH~-q$t4P<9Cv0CH3+(s1d
'aW.;;jJ,0SV>mn!$OC'6JsCcFX!4yOOlV%'=E4UAvpD6ScJ.
-S0e-Aq:wAZ&<gOp55QYFK8NAPVE1=FC,Y0m.Wq2(p)E,
B6QkR&vQC?4J4HENovl:p4c~V164=FCXn9t.

Translated message has been attached.


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

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

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






From owner-ietf@ietf.org  Tue Apr  6 11:38:38 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28887
	for <ietf-archive@odin.ietf.org>; Tue, 6 Apr 2004 11:38:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BAsKx-0006tp-Bn
	for ietf-list@asgard.ietf.org; Tue, 06 Apr 2004 11:18:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BAsKC-0006tT-K7
	for ietf@asgard.ietf.org; Tue, 06 Apr 2004 11:17: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 LAA27024
	for <ietf@ietf.org>; Tue, 6 Apr 2004 11:17:13 -0400 (EDT)
From: shahram_davari@pmc-sierra.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAsKB-0007es-00
	for ietf@ietf.org; Tue, 06 Apr 2004 11:17:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BArxD-0003vS-00
	for ietf@ietf.org; Tue, 06 Apr 2004 10:53:32 -0400
Received: from [221.232.74.20] (helo=ietf.org)
	by ietf-mx with smtp (Exim 4.12)
	id 1BArNY-0000L4-00
	for ietf@ietf.org; Tue, 06 Apr 2004 10:16:41 -0400
To: ietf@ietf.org
Subject: hello
Date: Tue, 6 Apr 2004 22:16:41 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="05462116"
Message-Id: <E1BArNY-0000L4-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.4 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MSGID_FROM_MTA_SHORT,NO_REAL_NAME,SUB_HELLO autolearn=no version=2.60
X-Spam-Report: 
	*  2.7 SUB_HELLO Subject starts with "Hello"
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
Sender: owner-ietf@ietf.org
Precedence: bulk

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

information about you

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

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

--05462116--




From exim@www1.ietf.org  Tue Apr  6 11:39:13 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28931
	for <ietf-archive@odin.ietf.org>; Tue, 6 Apr 2004 11:39:13 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAseu-0002ae-Un
	for ietf-archive@odin.ietf.org; Tue, 06 Apr 2004 11:38:45 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i36FceUC009948
	for ietf-archive@odin.ietf.org; Tue, 6 Apr 2004 11:38:40 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BAseu-0002aN-RL
	for ietf-web-archive@optimus.ietf.org; Tue, 06 Apr 2004 11:38:40 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BAsKx-0006tp-Bn
	for ietf-list@asgard.ietf.org; Tue, 06 Apr 2004 11:18:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BAsKC-0006tT-K7
	for ietf@asgard.ietf.org; Tue, 06 Apr 2004 11:17: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 LAA27024
	for <ietf@ietf.org>; Tue, 6 Apr 2004 11:17:13 -0400 (EDT)
From: shahram_davari@pmc-sierra.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAsKB-0007es-00
	for ietf@ietf.org; Tue, 06 Apr 2004 11:17:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BArxD-0003vS-00
	for ietf@ietf.org; Tue, 06 Apr 2004 10:53:32 -0400
Received: from [221.232.74.20] (helo=ietf.org)
	by ietf-mx with smtp (Exim 4.12)
	id 1BArNY-0000L4-00
	for ietf@ietf.org; Tue, 06 Apr 2004 10:16:41 -0400
To: ietf@ietf.org
Subject: hello
Date: Tue, 6 Apr 2004 22:16:41 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="05462116"
Message-Id: <E1BArNY-0000L4-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.4 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MSGID_FROM_MTA_SHORT,NO_REAL_NAME,SUB_HELLO autolearn=no version=2.60
X-Spam-Report: 
	*  2.7 SUB_HELLO Subject starts with "Hello"
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
Sender: owner-ietf@ietf.org
Precedence: bulk

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

information about you

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

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

--05462116--





From Administration@computeradmin.org  Tue Apr  6 14:24: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 OAA14230
	for <ietf-archive@ietf.org>; Tue, 6 Apr 2004 14:24:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAvF5-0004nj-00
	for ietf-archive@ietf.org; Tue, 06 Apr 2004 14:24:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BAvCF-0004Do-00
	for ietf-archive@ietf.org; Tue, 06 Apr 2004 14:21:16 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BAv7L-0003ge-00; Tue, 06 Apr 2004 14:16:11 -0400
Received: from [218.93.22.170] (helo=65.246.255.50)
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1BAv7L-0000Yc-FO; Tue, 06 Apr 2004 14:16:11 -0400
Received: from 4dkuk.uzssam.net (HELO 4vt2mq) ([117.132.14.199]) by 65.246.255.50 id NYXaCP6ExP0d; Wed, 07 Apr 2004 14:16:46 +0300
Message-ID: <7-j17tue$8$l68u95@zgpci>
From: "Admin" <Administration@computeradmin.org>
To: ieprep@ietf.org
Subject: ADV:        Attention All  Nonprofit Orgs: (Members, Staff and  Associates):
Date: Wed, 07 Apr 04 14:16:46 GMT
X-Priority: 1
X-MSMail-Priority: High
X-Mailer: AOL 7.0 for Windows US sub 118
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=".95BCA9CFB_"
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=17.3 required=5.0 tests=ADVERT_CODE,AWL,
	DATE_IN_FUTURE_03_06,DATE_SPAMWARE_Y2K,FORGED_MUA_AOL_FROM,
	FORGED_RCVD_NET_HELO,MISSING_MIMEOLE,MISSING_OUTLOOK_NAME,
	RCVD_NUMERIC_HELO,SUBJ_HAS_SPACES,X_MSMAIL_PRIORITY_HIGH,
	X_PRIORITY_HIGH autolearn=no version=2.60
X-Spam-Report: 
	*  0.5 X_PRIORITY_HIGH Sent with 'X-Priority' set to high
	*  1.0 SUBJ_HAS_SPACES Subject contains lots of white space
	*  0.5 X_MSMAIL_PRIORITY_HIGH Sent with 'X-Msmail-Priority' set to high
	*  0.3 RCVD_NUMERIC_HELO Received: contains a numeric HELO
	*  1.6 ADVERT_CODE Subject: starts with advertising tag
	*  4.4 DATE_SPAMWARE_Y2K Date header uses unusual Y2K formatting
	*  2.8 DATE_IN_FUTURE_03_06 Date: is 3 to 6 hours after Received: date
	*  3.0 FORGED_RCVD_NET_HELO Host HELO'd using the wrong IP network
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  4.3 FORGED_MUA_AOL_FROM Forged mail pretending to be from AOL (by From)
	*  0.1 MISSING_OUTLOOK_NAME Message looks like Outlook, but isn't
	* -2.4 AWL AWL: Auto-whitelist adjustment

This is a multi-part message in MIME format.

--.95BCA9CFB_
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Attention All Nonprofit Organizations, Members, Staff and Associates:

You Must Respond By 5 P.M. Wednesday, April 7, 2004.

Through a special arrangement, Avtech Direct is offering a limited
allotment of BRAND NEW, top of-the-line, name-brand desktop computers
at more than 50% off MSRP to all Members, Staff and Associates
who respond to this message before 5 P.M., Wednesday, April 7, 2004.

All desktop computers are brand-new packed in their original boxes,
and come with a full manufacturer's warranty plus
a 100% satisfaction guarantee.

These professional grade Desktops are fully equipped with 2004
next generation technology, making these the best performing
computers money can buy.

Avtech Direct is offering these feature rich, top performing
Desktop Computers with the latest Intel technology at an amazing price
to all who call:

    1-800-884-9510 by 5 P.M. Wednesday, April 7, 2004

The fast and powerful AT-2400 series Desktop features: 

      * Intel 2.0Ghz Processor for amazing speed and performance
      * 128MB DDR RAM,  --- Upgradeable to 1024
      * 20 GB UDMA Hard Drive, --- Upgradeable to 80 GB
      * 52X CD-Rom Drive, --- Upgradeable to DVD/CDRW 
      * 1.44 Floppy disk drive
      * Next Generation Technology
      * ATI Premium video and sound
      * Full Connectivity with Fax modem/Lan/IEE 1394/USB 2.0
      * Soft Touch Keyboard and scroll mouse
      * Internet Ready
      * Network Ready
      * 1 Year parts and labor warranty
      * Priority customer service and tech support

MSRP $699 ........................................ Your Cost $297

How to qualify:

  1. You must be a Member, Staff or Associate of a Nonprofit:
  2. All desktop computers will be available on a
     first come first serve basis.
  3. You must call 1-800-884-9510 by 5 P.M. Wednesday, April 7, 2004
     and we will hold the desktops you request on will call. 
  4. You are not obligated in any way.
  5. 100% Satisfaction Guaranteed.
   
   
Call Avtech Direct
1-800-884-9510 before 5 P.M. Wednesday, April 7, 2004




If you wish to unsubscribe from this list, please go to:
http://www.computeradvice.org/unsubscribe.asp
--.95BCA9CFB_--



From owner-ietf@ietf.org  Tue Apr  6 23:52:19 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01526
	for <ietf-archive@odin.ietf.org>; Tue, 6 Apr 2004 23:52:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BB3s1-0002m0-44
	for ietf-list@asgard.ietf.org; Tue, 06 Apr 2004 23:36:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BB3rb-0002lm-7v
	for ietf@asgard.ietf.org; Tue, 06 Apr 2004 23:36: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 XAA00755
	for <ietf@ietf.org>; Tue, 6 Apr 2004 23:36:27 -0400 (EDT)
From: kzm@cisco.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BB3rZ-0006L1-00
	for ietf@ietf.org; Tue, 06 Apr 2004 23:36:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BB2dP-0007ZR-00
	for ietf@ietf.org; Tue, 06 Apr 2004 22:17:48 -0400
Received: from [61.234.88.218] (helo=ietf.org)
	by ietf-mx with smtp (Exim 4.12)
	id 1BB23V-0001jh-00
	for ietf@ietf.org; Tue, 06 Apr 2004 21:40:42 -0400
To: ietf@ietf.org
Subject: stolen
Date: Wed, 7 Apr 2004 09:44:04 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="62876564"
Message-Id: <E1BB23V-0001jh-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.6 required=5.0 tests=MSGID_FROM_MTA_SHORT,
	NO_REAL_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_NETSKY.B in file jokes.htm.pif (in jokes.zip)
The uncleanable file jokes.zip is moved to /etc/iscan/virus/virDKDXZaaFE.

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

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

something is going wrong!

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


------------------  Virus Warning Message (on ietf-mx)

jokes.zip is removed from here because it contains a virus.

---------------------------------------------------------
--62876564--




From exim@www1.ietf.org  Tue Apr  6 23:52:50 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01548
	for <ietf-archive@odin.ietf.org>; Tue, 6 Apr 2004 23:52:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BB46x-0003Oz-Cw
	for ietf-archive@odin.ietf.org; Tue, 06 Apr 2004 23:52:23 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i373qNMJ013073
	for ietf-archive@odin.ietf.org; Tue, 6 Apr 2004 23:52:23 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BB46x-0003Om-9i
	for ietf-web-archive@optimus.ietf.org; Tue, 06 Apr 2004 23:52:23 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BB3s1-0002m0-44
	for ietf-list@asgard.ietf.org; Tue, 06 Apr 2004 23:36:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BB3rb-0002lm-7v
	for ietf@asgard.ietf.org; Tue, 06 Apr 2004 23:36: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 XAA00755
	for <ietf@ietf.org>; Tue, 6 Apr 2004 23:36:27 -0400 (EDT)
From: kzm@cisco.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BB3rZ-0006L1-00
	for ietf@ietf.org; Tue, 06 Apr 2004 23:36:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BB2dP-0007ZR-00
	for ietf@ietf.org; Tue, 06 Apr 2004 22:17:48 -0400
Received: from [61.234.88.218] (helo=ietf.org)
	by ietf-mx with smtp (Exim 4.12)
	id 1BB23V-0001jh-00
	for ietf@ietf.org; Tue, 06 Apr 2004 21:40:42 -0400
To: ietf@ietf.org
Subject: stolen
Date: Wed, 7 Apr 2004 09:44:04 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="62876564"
Message-Id: <E1BB23V-0001jh-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.6 required=5.0 tests=MSGID_FROM_MTA_SHORT,
	NO_REAL_NAME autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

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

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_NETSKY.B in file jokes.htm.pif (in jokes.zip)
The uncleanable file jokes.zip is moved to /etc/iscan/virus/virDKDXZaaFE.

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

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

something is going wrong!

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


------------------  Virus Warning Message (on ietf-mx)

jokes.zip is removed from here because it contains a virus.

---------------------------------------------------------
--62876564--





From owner-ietf@ietf.org  Wed Apr  7 08:13:41 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15552
	for <ietf-archive@odin.ietf.org>; Wed, 7 Apr 2004 08:13:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BBBdt-0006C6-UQ
	for ietf-list@asgard.ietf.org; Wed, 07 Apr 2004 07:54:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BBBcy-0006BL-E7
	for ietf@asgard.ietf.org; Wed, 07 Apr 2004 07:53: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 HAA14604
	for <ietf@ietf.org>; Wed, 7 Apr 2004 07:53:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BBBcx-0002l1-00
	for ietf@ietf.org; Wed, 07 Apr 2004 07:53:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BBAre-0003aO-00
	for ietf@ietf.org; Wed, 07 Apr 2004 07:05:03 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BB9V8-0002k7-00
	for ietf@ietf.org; Wed, 07 Apr 2004 05:37: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 i379boXQ012552
	for <ietf@ietf.org>; Wed, 7 Apr 2004 11:37:50 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v613)
To: IETF Discussion <ietf@ietf.org>
Message-Id: <37ADA6D8-8877-11D8-92B6-000A95CD987A@muada.com>
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-6--55752651; protocol="application/pkcs7-signature"
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: incomprehensible list filtering 
Date: Wed, 7 Apr 2004 11:37:42 +0200
X-Mailer: Apple Mail (2.613)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


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

       The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
       NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and
       "OPTIONAL" in this document are to be interpreted as described in
       RFC 2119.

Can someone please explain to me what is happening with this list. I 
regularly see messages from self-propagating code (carefully avoiding 
the v- and w-words) here. The actual code is removed, but the message 
is passed along to the list. But the strange thing is, when I reply to 
such a message pointing out that removing the code is a good thing, but 
passing along the now de-fanged message not so much, my reply doesn't 
make it to the list. Even worse: I don't get any kind of feedback that 
my message has been filtered because it contained some bad words or 
whatever the reason was.

IMNSHO when messages to the list are rejected, the sender MUST be 
informed.

And while I have your attention: it seems the list software finds it 
necessary to reorder MIME headers such that at least some software 
doesn't recognize the S/MIME signature anymore.
--Apple-Mail-6--55752651
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFlDCCAk0w
ggG2oAMCAQICAwv3RDANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDQwMzIxMTk0MDMxWhcNMDUwMzIxMTk0MDMxWjBEMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMSEwHwYJKoZIhvcNAQkBFhJpbGppdHNjaEBtdWFkYS5j
b20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMlOFOVMUhav7cAXzMMRDHKMlMhgr4CVO5T6
3s2V32+vJizVPf0sR8geKlD3GudGbF1qACceU1LOYxrz3uMtP3cD2Yqevito/Q0SvoD826/1dA1S
j9iUiNU2tiiYjzCCaaaaRrXwNy5TWZFToZmUEHROAw3lZSU+Xjzjw/yqnA9BAgMBAAGjLzAtMB0G
A1UdEQQWMBSBEmlsaml0c2NoQG11YWRhLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAIB+7bwEKMP9pkQCyRqjo5iRzgYBFbUD9XIVt9M3GwfibC/VraMjz301911rlwDMAax60TmX
sYge+R+v6rvoUHfXMfdviWnLGf6cWM5uVW1x6ezY1fgUJOyzWb9eE+1b4IzJ/tF3MNWy/JJI3esz
Odi5QtNXdo09aLfwi6mybyRYMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkG
A1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYD
VQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBE
aXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcN
AQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcx
NjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkp
IEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0G
CSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/
DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67
GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB
/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0
ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYD
VQQDExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/
r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfb
J3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGC
AmYwggJiAgEBMGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQ
dHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgML
90QwCQYFKw4DAhoFAKCCAVMwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUx
DxcNMDQwNDA3MDkzNzQyWjAjBgkqhkiG9w0BCQQxFgQUO6dAFsvHuGccIy1I68m8FQoO4zAweAYJ
KwYBBAGCNxAEMWswaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcg
KFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EC
Awv3RDB6BgsqhkiG9w0BCRACCzFroGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBD
b25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBAgML90QwDQYJKoZIhvcNAQEBBQAEgYCTTEVNJMFqJx75NAWodnienBsfjHYqPq8s
p6SvDL0BGugWXGT9yiekdc0t9JP1wFb5WS/n4zRV1X54JwTDf9jW5LIWnHcP+0jjrodBozL5K1Sq
aEbN7MJ55eHfTw4pRysIjKUNH0lX+8MBOJQ9G8EpgnHvBo5ROO38jhfErSyc/gAAAAAAAA==

--Apple-Mail-6--55752651--




From exim@www1.ietf.org  Wed Apr  7 08:14:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15572
	for <ietf-archive@odin.ietf.org>; Wed, 7 Apr 2004 08:14:11 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BBBw6-0002Su-OE
	for ietf-archive@odin.ietf.org; Wed, 07 Apr 2004 08:13:42 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i37CDgD3009476
	for ietf-archive@odin.ietf.org; Wed, 7 Apr 2004 08:13:42 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BBBw6-0002Sl-Ii
	for ietf-web-archive@optimus.ietf.org; Wed, 07 Apr 2004 08:13:42 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BBBdt-0006C6-UQ
	for ietf-list@asgard.ietf.org; Wed, 07 Apr 2004 07:54:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BBBcy-0006BL-E7
	for ietf@asgard.ietf.org; Wed, 07 Apr 2004 07:53: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 HAA14604
	for <ietf@ietf.org>; Wed, 7 Apr 2004 07:53:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BBBcx-0002l1-00
	for ietf@ietf.org; Wed, 07 Apr 2004 07:53:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BBAre-0003aO-00
	for ietf@ietf.org; Wed, 07 Apr 2004 07:05:03 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BB9V8-0002k7-00
	for ietf@ietf.org; Wed, 07 Apr 2004 05:37: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 i379boXQ012552
	for <ietf@ietf.org>; Wed, 7 Apr 2004 11:37:50 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v613)
To: IETF Discussion <ietf@ietf.org>
Message-Id: <37ADA6D8-8877-11D8-92B6-000A95CD987A@muada.com>
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-6--55752651; protocol="application/pkcs7-signature"
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: incomprehensible list filtering 
Date: Wed, 7 Apr 2004 11:37:42 +0200
X-Mailer: Apple Mail (2.613)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk


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

       The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
       NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and
       "OPTIONAL" in this document are to be interpreted as described in
       RFC 2119.

Can someone please explain to me what is happening with this list. I 
regularly see messages from self-propagating code (carefully avoiding 
the v- and w-words) here. The actual code is removed, but the message 
is passed along to the list. But the strange thing is, when I reply to 
such a message pointing out that removing the code is a good thing, but 
passing along the now de-fanged message not so much, my reply doesn't 
make it to the list. Even worse: I don't get any kind of feedback that 
my message has been filtered because it contained some bad words or 
whatever the reason was.

IMNSHO when messages to the list are rejected, the sender MUST be 
informed.

And while I have your attention: it seems the list software finds it 
necessary to reorder MIME headers such that at least some software 
doesn't recognize the S/MIME signature anymore.
--Apple-Mail-6--55752651
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFlDCCAk0w
ggG2oAMCAQICAwv3RDANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDQwMzIxMTk0MDMxWhcNMDUwMzIxMTk0MDMxWjBEMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMSEwHwYJKoZIhvcNAQkBFhJpbGppdHNjaEBtdWFkYS5j
b20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMlOFOVMUhav7cAXzMMRDHKMlMhgr4CVO5T6
3s2V32+vJizVPf0sR8geKlD3GudGbF1qACceU1LOYxrz3uMtP3cD2Yqevito/Q0SvoD826/1dA1S
j9iUiNU2tiiYjzCCaaaaRrXwNy5TWZFToZmUEHROAw3lZSU+Xjzjw/yqnA9BAgMBAAGjLzAtMB0G
A1UdEQQWMBSBEmlsaml0c2NoQG11YWRhLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA
A4GBAIB+7bwEKMP9pkQCyRqjo5iRzgYBFbUD9XIVt9M3GwfibC/VraMjz301911rlwDMAax60TmX
sYge+R+v6rvoUHfXMfdviWnLGf6cWM5uVW1x6ezY1fgUJOyzWb9eE+1b4IzJ/tF3MNWy/JJI3esz
Odi5QtNXdo09aLfwi6mybyRYMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkG
A1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYD
VQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBE
aXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcN
AQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcx
NjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkp
IEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0G
CSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/
DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67
GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB
/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0
ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYD
VQQDExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/
r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfb
J3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGC
AmYwggJiAgEBMGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQ
dHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgML
90QwCQYFKw4DAhoFAKCCAVMwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUx
DxcNMDQwNDA3MDkzNzQyWjAjBgkqhkiG9w0BCQQxFgQUO6dAFsvHuGccIy1I68m8FQoO4zAweAYJ
KwYBBAGCNxAEMWswaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcg
KFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EC
Awv3RDB6BgsqhkiG9w0BCRACCzFroGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBD
b25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBAgML90QwDQYJKoZIhvcNAQEBBQAEgYCTTEVNJMFqJx75NAWodnienBsfjHYqPq8s
p6SvDL0BGugWXGT9yiekdc0t9JP1wFb5WS/n4zRV1X54JwTDf9jW5LIWnHcP+0jjrodBozL5K1Sq
aEbN7MJ55eHfTw4pRysIjKUNH0lX+8MBOJQ9G8EpgnHvBo5ROO38jhfErSyc/gAAAAAAAA==

--Apple-Mail-6--55752651--





From JMKSGH@usclearing.com  Thu Apr  8 16:36: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 QAA20685
	for <ietf-archive@ietf.org>; Thu, 8 Apr 2004 16:36:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BBgGT-0000D3-00
	for ietf-archive@ietf.org; Thu, 08 Apr 2004 16:36:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BBdV2-0004g1-00
	for ietf-archive@ietf.org; Thu, 08 Apr 2004 13:39:37 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BBbUw-0005fk-00
	for ietf-archive@ietf.org; Thu, 08 Apr 2004 11:31:22 -0400
Received: from ip-24-197-134-091.spa.sc.charter.com ([24.197.134.91])
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1BBbAt-0005vo-6y
	for ietf-archive@ietf.org; Thu, 08 Apr 2004 11:10:39 -0400
Received: from 42.224.245.229 by 24.197.134.91; Thu, 08 Apr 2004 14:07:25 -0200
Message-ID: <CQWEEDZXXCRVDLPFWHEVVJ@myexcel.com>
From: "Carey Riddle" <JMKSGH@usclearing.com>
Reply-To: "Carey Riddle" <JMKSGH@usclearing.com>
To: ietf-archive@ietf.org
Subject: Urgent, Refill Your Prescription Now 
Date: Thu, 08 Apr 2004 18:10:25 +0200
X-Mailer: Microsoft Outlook Express 5.00.2615.200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--6253383217042325"
X-Priority: 3
X-MSMail-Priority: Normal
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.9 required=5.0 tests=FORGED_MUA_OUTLOOK,
	FORGED_OUTLOOK_HTML,FORGED_OUTLOOK_TAGS,HTML_MESSAGE,
	MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,
	MISSING_MIMEOLE autolearn=no version=2.60
X-Spam-Report: 
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  1.1 FORGED_OUTLOOK_HTML Outlook can't send HTML message only
	*  1.1 FORGED_OUTLOOK_TAGS Outlook can't send HTML in this format
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts
	*  1.6 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook

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

<html><body>
<center><a href=3D"http://www.qas34de.com/gp/default.asp?id=3Dd10" target=3D=
"_blank">
<img src=3D"http://www.qw2a3s.com/wktop.gif" border=3D"0"></a>
<br><br><font color=3D"#000000">I</hallmark>f t</cadenza>he mes</frazzle >=
sage</rowboat> i</ribbon>s n
</seething>ot lo</forbes >adi</decrement >ng</misanthropic>
<a href=3D"http://www.qas34de.com/gp/default.asp?id=3Dd10" target=3D"_blan=
k">
<b>t</catlike >r</dee >y</consultation> th</graves >is</guide></b></a></ce=
nter>
<p style=3D"font-size:0px; color:white" align=3D"left">
<br>Xditto firebug sanborn thirty pit amulet=20,Hmidas rape rutledge corru=
pt ndjamena shoddy=20.Ralmanac animosity threadbare cigar rate argonne=20,=
Aengel tanh whitehead zurich embarrass yttrium child syndrome injury dora =
chipboard corruptible spiro cyclone abyss nostalgia=20.Ogateway periphery =
catholic curl paucity pillar genesis duly kill agent defector snipe annex =
thug parsifal memoir enthusiast ball olivine leeward clearheaded illegitim=
ate ames mcintosh demand=20?Xcitizen escape boa precipitous ak malcolm cha=
rley meteoric char eightfold congestive yolk alum wells sc churn traitorou=
s francisco frontage kickoff wacky referred tournament belvedere buggy=20,=
Lcologne verbatim enemy wry girlish phosphor sunk=20,Tattack colgate numb =
wert droplet darry hero o'donnell liquefaction borrow yapping asymmetry pa=
sser claremont marginalia az diffeomorphism cos chesterton genoa rosen can=
e preparation depose=20.Eseminal transferor crankshaft brought arrhenius p=
rovision afterward rapier alliance toilsome putty ducat adolescent consens=
us sybil greyhound complementarity=20,Dcrock blend taverna sulphur aesthet=
ic embeddable deere pleasure framework immaculate bluff clitoris khan cann=
onball activation argo wintry operon abrasion alumni=20.Ksuzanne angiosper=
m esoteric uniform buttonhole chalk aristotelian arachne canvass bentley a=
bo=20.Rarsenal confectionery frederic alias tricky copeland pyrite crossta=
lk grizzle psychotic devolution yon bruegel southwest krakow chomp bedazzl=
e=20.Iconjoin lessee elute consecutive flee axisymmetric martini=20.Epatty=
 hazard crossway keelson bobbie scarify predatory accomplice octopus ferdi=
nand=20,Pinsubstantial beckman jut beauregard courteous garcia teethe rund=
own bluefish intervention=20?Xbernini typic auxiliary gogh expressible bes=
peak prick=20! Sverisimilitude godwit jellyfish pot invasive andover toefl=
 librettist patagonia belie allstate desmond fcc=20!Uassam essence greek f=
ilial detergent laurel thoughtful full rowdy debussy standeth cross injust=
ice sara enchantress hectic algiers handgun retrofitting=20,Yshah molten a=
ccession centimeter omit almagest millinery doormen wayward algebraic hepa=
titis inhabitant mbabane hoard skylight cretin bade maladroit hose=20,Ddes=
ign granulate calendrical upcome precaution cluck devon replaceable ancest=
ry arrival buss file gaspee bedraggle spook=20.Sdispersible inventive comp=
are sensate goodbye concoct chief inarticulate phycomycetes manchester hob=
goblin dusenbury=20,</p>
</body></html>

----6253383217042325--



From owner-ietf@ietf.org  Fri Apr  9 17:13:03 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22560
	for <ietf-archive@odin.ietf.org>; Fri, 9 Apr 2004 17:13:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BC2zE-00059U-5p
	for ietf-list@asgard.ietf.org; Fri, 09 Apr 2004 16:52:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BC2z4-00059D-Gb
	for ietf@asgard.ietf.org; Fri, 09 Apr 2004 16:52:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20828
	for <ietf@ietf.org>; Fri, 9 Apr 2004 16:52:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BC2z3-0001os-00
	for ietf@ietf.org; Fri, 09 Apr 2004 16:52:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BC2kg-00005W-00
	for ietf@ietf.org; Fri, 09 Apr 2004 16:37:27 -0400
Received: from [200.175.196.68] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BC2RM-00062h-00
	for ietf@ietf.org; Fri, 09 Apr 2004 16:17:28 -0400
From: agenda@ietf.org
To: ietf@ietf.org
Subject: Re: Protected Mail Request
Date: Thu, 8 Apr 2004 17:18:16 -0300
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BC2RM-00062h-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.1 required=5.0 tests=DATE_IN_PAST_12_24,
	MIME_BOUND_NEXTPART,MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,
	PRIORITY_NO_NAME autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.4 DATE_IN_PAST_12_24 Date: is 12 to 24 hours before Received: date
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.2 MIME_BOUND_NEXTPART Spam tool pattern in MIME boundary
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

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

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_NETSKY.P in file document.txt                                                                   .exe (in readme.zip)
The file readme.zip is moved to /etc/iscan/virus/virAHJBTby1D.

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

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


Waiting for a Response. Please read the attachment.



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


------------------  Virus Warning Message (on ietf-mx)

readme.zip is removed from here because it contains a virus.

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





From exim@www1.ietf.org  Fri Apr  9 17:13:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22596
	for <ietf-archive@odin.ietf.org>; Fri, 9 Apr 2004 17:13:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BC3JC-0003nQ-Gf
	for ietf-archive@odin.ietf.org; Fri, 09 Apr 2004 17:13:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i39LD6Gr014588
	for ietf-archive@odin.ietf.org; Fri, 9 Apr 2004 17:13:06 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BC3JC-0003nD-DE
	for ietf-web-archive@optimus.ietf.org; Fri, 09 Apr 2004 17:13:06 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BC2zE-00059U-5p
	for ietf-list@asgard.ietf.org; Fri, 09 Apr 2004 16:52:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BC2z4-00059D-Gb
	for ietf@asgard.ietf.org; Fri, 09 Apr 2004 16:52:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20828
	for <ietf@ietf.org>; Fri, 9 Apr 2004 16:52:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BC2z3-0001os-00
	for ietf@ietf.org; Fri, 09 Apr 2004 16:52:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BC2kg-00005W-00
	for ietf@ietf.org; Fri, 09 Apr 2004 16:37:27 -0400
Received: from [200.175.196.68] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BC2RM-00062h-00
	for ietf@ietf.org; Fri, 09 Apr 2004 16:17:28 -0400
From: agenda@ietf.org
To: ietf@ietf.org
Subject: Re: Protected Mail Request
Date: Thu, 8 Apr 2004 17:18:16 -0300
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BC2RM-00062h-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.1 required=5.0 tests=DATE_IN_PAST_12_24,
	MIME_BOUND_NEXTPART,MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,
	PRIORITY_NO_NAME autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.4 DATE_IN_PAST_12_24 Date: is 12 to 24 hours before Received: date
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.2 MIME_BOUND_NEXTPART Spam tool pattern in MIME boundary
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

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

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_NETSKY.P in file document.txt                                                                   .exe (in readme.zip)
The file readme.zip is moved to /etc/iscan/virus/virAHJBTby1D.

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

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


Waiting for a Response. Please read the attachment.



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


------------------  Virus Warning Message (on ietf-mx)

readme.zip is removed from here because it contains a virus.

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






From owner-ietf@ietf.org  Mon Apr 12 01:16:38 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22257
	for <ietf-archive@odin.ietf.org>; Mon, 12 Apr 2004 01:16:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BCtTP-0007ob-0n
	for ietf-list@asgard.ietf.org; Mon, 12 Apr 2004 00:55:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BCtST-0007oN-F2
	for ietf@asgard.ietf.org; Mon, 12 Apr 2004 00:54: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 AAA21293
	for <ietf@ietf.org>; Mon, 12 Apr 2004 00:54:05 -0400 (EDT)
From: lyong@ciena.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BCtSP-0001GT-00
	for ietf@ietf.org; Mon, 12 Apr 2004 00:54:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BCtOz-0000zJ-00
	for ietf@ietf.org; Mon, 12 Apr 2004 00:50:34 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BCtN4-0000fH-00
	for ietf@ietf.org; Mon, 12 Apr 2004 00:48:34 -0400
Received: from [61.152.135.14] (helo=ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BCtN2-00050B-Be
	for ietf@ietf.org; Mon, 12 Apr 2004 00:48:32 -0400
To: ietf@ietf.org
Subject: Delivery Failure (ietf@ietf.org)
Date: Mon, 12 Apr 2004 12:45:55 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 1
X-MSMail-Priority: High
Message-Id: <E1BCtN2-00050B-Be@mx2.foretec.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.5 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MIME_BOUND_NEXTPART,MISSING_MIMEOLE,NO_REAL_NAME,PRIORITY_NO_NAME,
	X_MSMAIL_PRIORITY_HIGH,X_PRIORITY_HIGH autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0016----=_NextPart_000_0016
Content-Type: text/plain;
	charset="Windows-1252"
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id AAA21296
Content-Transfer-Encoding: quoted-printable


Mail Transaction Failed - This mail couldn't be converted

------------- failed message -------------
SF1Pa)pfk5NKaqT!m?=E4~v91q5*X4CtxrQL~O<_RWz0t
Bcj>eP%M=DFvp=DFDVOUeCMnfQNz70-XeObQzT%ttwC-h=FC2
zk=F6Q!bj(?|T=E48gZ3Mdu?jZ1?t=F6y7)SH-wnPy=F6ZGIyu$=E4E
H2AVTk$#:iPHh-,=F6rRf$l$mcy_LpQ

Modified message has been sent as a binary attachment.


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

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

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





From exim@www1.ietf.org  Mon Apr 12 01:17:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22301
	for <ietf-archive@odin.ietf.org>; Mon, 12 Apr 2004 01:17:09 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BCtoG-0003SP-Qt
	for ietf-archive@odin.ietf.org; Mon, 12 Apr 2004 01:16:41 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3C5GevO013285
	for ietf-archive@odin.ietf.org; Mon, 12 Apr 2004 01:16:40 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BCtoG-0003SC-Ml
	for ietf-web-archive@optimus.ietf.org; Mon, 12 Apr 2004 01:16:40 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BCtTP-0007ob-0n
	for ietf-list@asgard.ietf.org; Mon, 12 Apr 2004 00:55:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BCtST-0007oN-F2
	for ietf@asgard.ietf.org; Mon, 12 Apr 2004 00:54: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 AAA21293
	for <ietf@ietf.org>; Mon, 12 Apr 2004 00:54:05 -0400 (EDT)
From: lyong@ciena.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BCtSP-0001GT-00
	for ietf@ietf.org; Mon, 12 Apr 2004 00:54:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BCtOz-0000zJ-00
	for ietf@ietf.org; Mon, 12 Apr 2004 00:50:34 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BCtN4-0000fH-00
	for ietf@ietf.org; Mon, 12 Apr 2004 00:48:34 -0400
Received: from [61.152.135.14] (helo=ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BCtN2-00050B-Be
	for ietf@ietf.org; Mon, 12 Apr 2004 00:48:32 -0400
To: ietf@ietf.org
Subject: Delivery Failure (ietf@ietf.org)
Date: Mon, 12 Apr 2004 12:45:55 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 1
X-MSMail-Priority: High
Message-Id: <E1BCtN2-00050B-Be@mx2.foretec.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.5 required=5.0 tests=MICROSOFT_EXECUTABLE,
	MIME_BOUND_NEXTPART,MISSING_MIMEOLE,NO_REAL_NAME,PRIORITY_NO_NAME,
	X_MSMAIL_PRIORITY_HIGH,X_PRIORITY_HIGH autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0016----=_NextPart_000_0016
Content-Type: text/plain;
	charset="Windows-1252"
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id AAA21296
Content-Transfer-Encoding: quoted-printable


Mail Transaction Failed - This mail couldn't be converted

------------- failed message -------------
SF1Pa)pfk5NKaqT!m?=E4~v91q5*X4CtxrQL~O<_RWz0t
Bcj>eP%M=DFvp=DFDVOUeCMnfQNz70-XeObQzT%ttwC-h=FC2
zk=F6Q!bj(?|T=E48gZ3Mdu?jZ1?t=F6y7)SH-wnPy=F6ZGIyu$=E4E
H2AVTk$#:iPHh-,=F6rRf$l$mcy_LpQ

Modified message has been sent as a binary attachment.


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

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

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






From owner-ietf@ietf.org  Mon Apr 12 10:44:38 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22395
	for <ietf-archive@odin.ietf.org>; Mon, 12 Apr 2004 10:44:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BD2Sn-0001VZ-4N
	for ietf-list@asgard.ietf.org; Mon, 12 Apr 2004 10:31:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BD2S6-0001VH-89
	for ietf@asgard.ietf.org; Mon, 12 Apr 2004 10:30: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 KAA21776
	for <ietf@ietf.org>; Mon, 12 Apr 2004 10:30:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BD2S0-0000RR-00
	for ietf@ietf.org; Mon, 12 Apr 2004 10:30:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BD2QX-0000E3-00
	for ietf@ietf.org; Mon, 12 Apr 2004 10:28:46 -0400
Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1BD2PL-0007mH-00
	for ietf@ietf.org; Mon, 12 Apr 2004 10:27:31 -0400
Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap 
	 id 3018; Mon, 12 Apr 2004 10:24:24 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Patents? we don't need no stinking Patents!
Date: Mon, 12 Apr 2004 10:26:45 -0400
Message-ID: <4A3384433CE2AB46A63468CB207E209DB1A499@zoe.office.snowshore.com>
Thread-Topic: Patents? we don't need no stinking Patents!
Thread-Index: AcQav2E4CE6bwMlgQYis7j4WNeq6UAF2Zk7Q
From: "Eric Burger" <eburger@snowshore.com>
To: "Dean Anderson" <dean@av8.com>, "Dan Kolis" <dank@hq.lindsayelec.com>
Cc: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,PLING_QUERY autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Prior to 2000, the USPTO required a patent examiner to have a Master's =
degree in *Engineering*.  Unfortunately, since universities only granted =
Computer *Science* degrees, no CS grads in the patent office.

After 2000, the USPTO said that a Master's in Computer Science counted.

That said, when I last looked (around 2000), the starting salary for a =
patent examiner was in the neighborhood of $56,000 per year.  That is a =
little more than what a high school science teacher makes in Fairfax =
County (near the USPTO).

Old information, FWIW.

> -----Original Message-----
> From: Dean Anderson [mailto:dean@av8.com]
> Sent: Sunday, April 04, 2004 11:12 PM
> To: Dan Kolis
> Cc: ietf@ietf.org
> Subject: Re: Patents? we don't need no stinking Patents!
>=20
>=20
> On Fri, 2 Apr 2004, Dan Kolis wrote:
>=20
> > Dean Anderson said, and is ">"
> >   >While finding prior art is hard problem in any field, it=20
> would be helpful
> >   >if the Patent Office hired more experts in the fields=20
> that they offer
> >   >patents in, and in particular, more computer scientists. =20
> >=20
> > Dan says:
> > In the above, a chemist would substitute "Chemist" for=20
> computer scientist, a
> > Mechanical engineer the same.=20
>=20
> Well, the PTO actually hires Chemists and Mechanical=20
> Engineers to review
> patents in those fields. But it does not hire Computer Scientists.  At
> least, it didn't. I don't think anyone's checked in a few=20
> years, but we
> also haven't been told that this has changed.
>=20
> > Obviously, the patent inspectors know there is probably=20
> public domain
> > material, but it doesn't seem like they have a reasonable=20
> access to it.
>=20
> One might think so. It is more likely a result of not having people
> trained in computer science analyzing software patents.=20
> Perhaps having too
> much work to do.
>=20
> > The review process looks degrading to the patent inspector if the
> > applicant goes over their head in their internal appeals=20
> process.  So
> > its easier to grant it.
>=20
> I don't think this the case. One nearly always has a recourse=20
> to challenge
> a government decision. There is nothing degrading about doing=20
> so.  I think
> most government bureaucrats try to do a good job, even if its=20
> in a field
> they aren't trained for.  But their lack of training in the field is a
> policy problem.  It doesn't mean there is anything inherently=20
> wrong with
> the patent system.
>=20
> Human failures sometimes mean there is something wrong with=20
> the system. It
> could be the case that the system promotes human failures,=20
> like the Airbus
> autopilot user interface that led pilots to mistakely enter=20
> 3500 feet per
> minute descent rate instead of 3.5 degrees down decent. This led to at
> least one crash and several near accidents. The system was=20
> fixed, so that
> humans were less likely to fail. On the other hand, the=20
> aircraft that hit
> the WTC performed perfectly. There was nothing wrong with the=20
> airplanes.
>=20
> Similarly, if you have monkeys instead of railroad engineers,=20
> it doesn't
> mean the concept of trains and railroads is flawed. It means that the
> policy of hiring monkeys instead of trained professionals is=20
> flawed.  And
> by "monkeys", I don't mean to be perjorative. Albert Einstein=20
> wouldn't be
> safe driving a train, even though he wrote a lot about train cars and
> railroad embankments. Its a matter of training and knowledge base.
>=20
> In our instant case, while the policies are harmful and the computer
> science training insufficient, this is a relatively minor=20
> problem. It is
> the system itself that is flawed.  We do not want to focus on the
> policies, except to say that they are relatively unimportant,=20
> though they
> do create a negative.  Even if the policies were changed, it=20
> is ultimately
> hard to avoid the problem of bad patents entirely and I don't expect
> that's possible.
>=20
> There have been people who have filed purposefully=20
> embarrassing patents,
> but I don't encourage this. In fact, I strongly discourage=20
> it. Sabotaging
> the system never helps change it.  In fact it hurts, because then the
> proponents can claim that its problems are due to the sabotage, not to
> anything inherently wrong with the system.
>=20
> > Dean says:
> >   >Such patents as this are clearly mistakes, and are=20
> frequently overturned
> >   >on review.=20
> >=20
> > Dan says:
> > As a reality check I just walked over to a desk here and=20
> touched an object
> > recently contested in a Patent battle. *any* trip to a flea=20
> market could
> > fill a pickup truck of goods built before 1940 that show=20
> the patent is at
> > least partially invalid. (some claims... stink). But, the=20
> Grantee won. Why?
> > Its cheaper to be right and lose, then pay a license fee...=20
> than be right
> > and win.
>=20
> True, "The right thing" doesn't always prevail. But I think it usually
> prevails.  But these sort of mistakes are=20
> administrative--there are human
> failings in _any_ system.  In principle, one can't criticize=20
> 'the system'
> for human failing, because only the humans failed.  There is=20
> a difference
> between the system and the operation of the system.  We can and do
> criticize the operators for having too many human failings.  This is a
> reason to change the policies of the operators, but not a=20
> reason to change
> the system.  We seek primarily to change the system, and want=20
> to focus on
> that.
>=20
> > Dean says:
> >   >if you file right before product
> >   >release, and that product catches on. 18 months is a=20
> long time for
> >   >software. 30 months, and you are into lifecycle=20
> maturity. You've already
> >   >made commitments to using the software.  Now you have to=20
> pay whatever they
> >   >want to charge.  If the patent is solid, there is no way=20
> out, not even for=20
> >   >OJ or MJ, or BG for that matter.
> >=20
> > Dan says:
> > The general principle is built on pain and suffering. The=20
> trick is, (like
> > Sam Ting said about how to win Nobel prizes: "I think you=20
> should be first,
> > and be right"). "Interference" is super complicated, when=20
> they actually
> > overlap like you described. I think if I remember=20
> correctly, it happens in
> > about 5% of the cases, so its a lot. No doubt, its a=20
> pipeline, so one begins
> > to wonder what public interest is served with long=20
> delays... I can't think
> > of any.
>=20
> The delay isn't an "intentional" delay, in the sense that=20
> they just sit on
> it for 18 months. The delay is to process the paperwork and review the
> patent.  The delay is also due to a backlog of work.  Its no=20
> different (in
> principle) than if you file for a building permit: you don't=20
> get it same
> day. It takes a bit. If there is a backlog, it takes longer. =20
> At the PTO,
> it generally takes 18 months, but occasionally takes 5 years.=20
> (There are
> exceptions having to do with classified technology that can=20
> take much more
> time--effectively unlimited time, but I'll ignore those)
>=20
> > A usual way to deal with the reality is to use the granted one as a
> > citation, make a trivial improvement, and now you have=20
> reset the clock 2
> > years or so. Of course, if there are real damages, all this=20
> is retroactive,
> > plus often a bonus multiplier of 1:3 for being a evil-doer, so its a
> > financial burden.
>=20
> True. Though anyone can do this. If you want to screw your=20
> competitor, or
> buy a company at a discount, you can file for the improvement=20
> and prevent
> them from using it.  I suppose it is a financial burden, or an income
> source for patent attorneys.  The counter argument is that people were
> still spurred to invent new things, and to make improvements, and of
> course, inventors are motivated to work harder and file sooner for the
> enhancements to prevent competitors from doing so. So in=20
> fact, the patent
> system is "working" in this case and promoting progress. This=20
> is just sort
> of the "Stick"  side of it.  "Innovate or Die" makes=20
> progress. You may not
> like that, but it isn't a strong argument to change the patent system.
>=20
> > Dean says:
> >   >But anything halfway novel, and new. Well, that is another=20
> >   >story:  Patent it or someone else will.
> >=20
> > Dan says:
> > What is "Obvious to one practised in the art"; (which is=20
> the US PTO test for
> > novelty). Our patent attorney says if it takes more than 45=20
> seconds for the
> > dumbest person actually employed in that field to figure it=20
> out, then its
> > not "obvious".=20
>=20
> Well, that's not the test that the patent office uses, thankfully.
>=20
> Also, keep in mind that my comment is about the first-to-file system,
> which hasn't been passed into law yet, in the US.  Though, it=20
> is fair to
> say that even the current system strongly encourages patent=20
> filing over
> public domain publishing.  For example, if someone else gets a similar
> patent, and you have published in the public domain, your=20
> only recourse is
> to challenge the validity of the patent, and you have very=20
> little leverage
> with which to negotiate a cross license. If you had instead=20
> filed for a
> patent, you would have some leverage to counter sue them for=20
> infringement,
> and probably obtain a cross license.  This creates a strong incentive
> against putting things in the public domain.
>=20
> > Who know for sure, but I doubt this was the intention 300=20
> years ago when
> > this concept emerged.
>=20
> Actually, the intention (more than 300 years ago) was to=20
> create arbitrary
> monopolies. Patents were gifts of the King--you got to be the=20
> exclusive
> maker of shoes, for example. It was a way to reward subjects=20
> and enrich
> them. It had nothing to do with invention.  The concept was=20
> changed, in
> the US constitution, to have a more beneficial purpose, limited to=20
> inventions, and for limited times.
>=20
> > (*) Different durations for different kinds of patents.=20
> Maybe software
> > should be sort enough to make it functionless completely.=20
> That would suit me
> > fine. I think many good programs behind the scenes do=20
> things in non-obvious
> > ways, but somehow because someone else stumbles into the=20
> same proceedure, it
> > just doesn't seem like patentable material to me, at all.=20
>=20
> I think many people would find a 3 year software patent much more
> acceptable. But the problem is, once you get into such a=20
> short time frame,
> it is even harder for the government to keep up. It would be truly
> unacceptable to have a 3 year patent granted 18 months into a 36 month
> term.  The alternative is then an "accelerated review process". The
> problem with that is that it is even more susceptible to bad=20
> patents. =20
> And there is even less reason to challenge them, versus pay them for 3
> years.  This also runs afoul of GATT obligations, I think, since the
> "normalized" term is 20 years, and there aren't provisions for varying
> terms.
>=20
> Most people think of the patent system in relation to=20
> inventors. But the
> major users are venture capitalists. They use the patent=20
> system to justify
> their investments. That is why the patent system can't just=20
> be abandoned
> or changed capriciously. Doing so would cause economic chaos.=20
>  Like any
> function of government, the people who have the most money=20
> involved tend
> to be the movers and shakers of the policy.  If the VC lose=20
> interest in
> software patents (and there are indications they are), then=20
> there is very
> little reason to have them at all.  The remaining players are=20
> basically
> the inventors and the lawyers.  There is an argument that the patent
> system protects the inventor from unscrupulous people who simply have
> superior manufacturing and distribution capabilities.  This is hard
> discount completely, and I think there is a legitimate=20
> concern about the
> unscrupulous profit on truly novel ideas.  But it clearly=20
> becomes an issue
> of governance--is it economical for the government or the inventor to
> invest the time and expense for a patent application for a=20
> product that
> has a useful lifetime measured in months?
>=20
> As soon as you drop the time limit to a major fraction of the=20
> processing
> time, and lose the interest of the major players, there is=20
> little purpose
> in having a software patent system.  The value of a true 20=20
> year monopoly
> is significant. It justifies significant government and legal expense,
> both in creating and overturning, and in defending against=20
> infringement. =20
> The value of a 3 year monopoly is much less so. It basically become a
> government jobs program, but there are no computer scientists=20
> employed by
> the PTO to keep employed. And given the backlog of patent=20
> applications in=20
> all fields, it would be better for other patent system users=20
> to not have=20
> software patents crowding the works.
>=20
> > XOR operations for a blinking cursor? Can you think of=20
> another way NOT to do
> > that?
>=20
> Yes. You can redraw the entire screen.  You can save and restore the
> entire contents under the cursor without XOR. You can make=20
> the cursor an
> analog sprite, drawn over the image as an added analog=20
> signal. There are
> other ways, but XOR is clearly, _obviously_, the easiest way=20
> to do it. It
> is not the only way. Its just the obviously best way. There is nothing
> novel about the application of existing mathematics to=20
> cursors. That is=20
> expected.
>=20
> The XOR patent was finally reviewed and revoked.  We used this as an
> example of an obviously bad patent for a long time.  But as I said,
> mistakes are reasons to change the policies that govern the=20
> operation of
> the system. They are not reason to change the system itself.  A
> knowledgeable computer scientist working in the PTO would never have
> approved that patent.
>=20
> And as I said earlier, it is not the obviously mistaken patents that
> concern me most. I am concerned most with the genuinely novel software
> patents, and how a monopoly granted 18 to 30 months after its=20
> introduction
> could impact the industry, the economy, the users, and the=20
> programmers. =20
> A novel software patent is a lot more similar to the=20
> airplanes that hit
> the WTC, without the murderous intent. The system can be=20
> expected to work
> perfectly, with disastrous results.
>=20
> 		--Dean=20
>=20
>=20
>=20
>=20




From exim@www1.ietf.org  Mon Apr 12 10:45:12 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22430
	for <ietf-archive@odin.ietf.org>; Mon, 12 Apr 2004 10:45:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BD2fy-0005x9-Jd
	for ietf-archive@odin.ietf.org; Mon, 12 Apr 2004 10:44:45 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3CEigwJ022881
	for ietf-archive@odin.ietf.org; Mon, 12 Apr 2004 10:44:42 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BD2fy-0005wy-Em
	for ietf-web-archive@optimus.ietf.org; Mon, 12 Apr 2004 10:44:42 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BD2Sn-0001VZ-4N
	for ietf-list@asgard.ietf.org; Mon, 12 Apr 2004 10:31:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BD2S6-0001VH-89
	for ietf@asgard.ietf.org; Mon, 12 Apr 2004 10:30: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 KAA21776
	for <ietf@ietf.org>; Mon, 12 Apr 2004 10:30:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BD2S0-0000RR-00
	for ietf@ietf.org; Mon, 12 Apr 2004 10:30:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BD2QX-0000E3-00
	for ietf@ietf.org; Mon, 12 Apr 2004 10:28:46 -0400
Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1BD2PL-0007mH-00
	for ietf@ietf.org; Mon, 12 Apr 2004 10:27:31 -0400
Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap 
	 id 3018; Mon, 12 Apr 2004 10:24:24 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Patents? we don't need no stinking Patents!
Date: Mon, 12 Apr 2004 10:26:45 -0400
Message-ID: <4A3384433CE2AB46A63468CB207E209DB1A499@zoe.office.snowshore.com>
Thread-Topic: Patents? we don't need no stinking Patents!
Thread-Index: AcQav2E4CE6bwMlgQYis7j4WNeq6UAF2Zk7Q
From: "Eric Burger" <eburger@snowshore.com>
To: "Dean Anderson" <dean@av8.com>, "Dan Kolis" <dank@hq.lindsayelec.com>
Cc: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,PLING_QUERY autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Prior to 2000, the USPTO required a patent examiner to have a Master's =
degree in *Engineering*.  Unfortunately, since universities only granted =
Computer *Science* degrees, no CS grads in the patent office.

After 2000, the USPTO said that a Master's in Computer Science counted.

That said, when I last looked (around 2000), the starting salary for a =
patent examiner was in the neighborhood of $56,000 per year.  That is a =
little more than what a high school science teacher makes in Fairfax =
County (near the USPTO).

Old information, FWIW.

> -----Original Message-----
> From: Dean Anderson [mailto:dean@av8.com]
> Sent: Sunday, April 04, 2004 11:12 PM
> To: Dan Kolis
> Cc: ietf@ietf.org
> Subject: Re: Patents? we don't need no stinking Patents!
>=20
>=20
> On Fri, 2 Apr 2004, Dan Kolis wrote:
>=20
> > Dean Anderson said, and is ">"
> >   >While finding prior art is hard problem in any field, it=20
> would be helpful
> >   >if the Patent Office hired more experts in the fields=20
> that they offer
> >   >patents in, and in particular, more computer scientists. =20
> >=20
> > Dan says:
> > In the above, a chemist would substitute "Chemist" for=20
> computer scientist, a
> > Mechanical engineer the same.=20
>=20
> Well, the PTO actually hires Chemists and Mechanical=20
> Engineers to review
> patents in those fields. But it does not hire Computer Scientists.  At
> least, it didn't. I don't think anyone's checked in a few=20
> years, but we
> also haven't been told that this has changed.
>=20
> > Obviously, the patent inspectors know there is probably=20
> public domain
> > material, but it doesn't seem like they have a reasonable=20
> access to it.
>=20
> One might think so. It is more likely a result of not having people
> trained in computer science analyzing software patents.=20
> Perhaps having too
> much work to do.
>=20
> > The review process looks degrading to the patent inspector if the
> > applicant goes over their head in their internal appeals=20
> process.  So
> > its easier to grant it.
>=20
> I don't think this the case. One nearly always has a recourse=20
> to challenge
> a government decision. There is nothing degrading about doing=20
> so.  I think
> most government bureaucrats try to do a good job, even if its=20
> in a field
> they aren't trained for.  But their lack of training in the field is a
> policy problem.  It doesn't mean there is anything inherently=20
> wrong with
> the patent system.
>=20
> Human failures sometimes mean there is something wrong with=20
> the system. It
> could be the case that the system promotes human failures,=20
> like the Airbus
> autopilot user interface that led pilots to mistakely enter=20
> 3500 feet per
> minute descent rate instead of 3.5 degrees down decent. This led to at
> least one crash and several near accidents. The system was=20
> fixed, so that
> humans were less likely to fail. On the other hand, the=20
> aircraft that hit
> the WTC performed perfectly. There was nothing wrong with the=20
> airplanes.
>=20
> Similarly, if you have monkeys instead of railroad engineers,=20
> it doesn't
> mean the concept of trains and railroads is flawed. It means that the
> policy of hiring monkeys instead of trained professionals is=20
> flawed.  And
> by "monkeys", I don't mean to be perjorative. Albert Einstein=20
> wouldn't be
> safe driving a train, even though he wrote a lot about train cars and
> railroad embankments. Its a matter of training and knowledge base.
>=20
> In our instant case, while the policies are harmful and the computer
> science training insufficient, this is a relatively minor=20
> problem. It is
> the system itself that is flawed.  We do not want to focus on the
> policies, except to say that they are relatively unimportant,=20
> though they
> do create a negative.  Even if the policies were changed, it=20
> is ultimately
> hard to avoid the problem of bad patents entirely and I don't expect
> that's possible.
>=20
> There have been people who have filed purposefully=20
> embarrassing patents,
> but I don't encourage this. In fact, I strongly discourage=20
> it. Sabotaging
> the system never helps change it.  In fact it hurts, because then the
> proponents can claim that its problems are due to the sabotage, not to
> anything inherently wrong with the system.
>=20
> > Dean says:
> >   >Such patents as this are clearly mistakes, and are=20
> frequently overturned
> >   >on review.=20
> >=20
> > Dan says:
> > As a reality check I just walked over to a desk here and=20
> touched an object
> > recently contested in a Patent battle. *any* trip to a flea=20
> market could
> > fill a pickup truck of goods built before 1940 that show=20
> the patent is at
> > least partially invalid. (some claims... stink). But, the=20
> Grantee won. Why?
> > Its cheaper to be right and lose, then pay a license fee...=20
> than be right
> > and win.
>=20
> True, "The right thing" doesn't always prevail. But I think it usually
> prevails.  But these sort of mistakes are=20
> administrative--there are human
> failings in _any_ system.  In principle, one can't criticize=20
> 'the system'
> for human failing, because only the humans failed.  There is=20
> a difference
> between the system and the operation of the system.  We can and do
> criticize the operators for having too many human failings.  This is a
> reason to change the policies of the operators, but not a=20
> reason to change
> the system.  We seek primarily to change the system, and want=20
> to focus on
> that.
>=20
> > Dean says:
> >   >if you file right before product
> >   >release, and that product catches on. 18 months is a=20
> long time for
> >   >software. 30 months, and you are into lifecycle=20
> maturity. You've already
> >   >made commitments to using the software.  Now you have to=20
> pay whatever they
> >   >want to charge.  If the patent is solid, there is no way=20
> out, not even for=20
> >   >OJ or MJ, or BG for that matter.
> >=20
> > Dan says:
> > The general principle is built on pain and suffering. The=20
> trick is, (like
> > Sam Ting said about how to win Nobel prizes: "I think you=20
> should be first,
> > and be right"). "Interference" is super complicated, when=20
> they actually
> > overlap like you described. I think if I remember=20
> correctly, it happens in
> > about 5% of the cases, so its a lot. No doubt, its a=20
> pipeline, so one begins
> > to wonder what public interest is served with long=20
> delays... I can't think
> > of any.
>=20
> The delay isn't an "intentional" delay, in the sense that=20
> they just sit on
> it for 18 months. The delay is to process the paperwork and review the
> patent.  The delay is also due to a backlog of work.  Its no=20
> different (in
> principle) than if you file for a building permit: you don't=20
> get it same
> day. It takes a bit. If there is a backlog, it takes longer. =20
> At the PTO,
> it generally takes 18 months, but occasionally takes 5 years.=20
> (There are
> exceptions having to do with classified technology that can=20
> take much more
> time--effectively unlimited time, but I'll ignore those)
>=20
> > A usual way to deal with the reality is to use the granted one as a
> > citation, make a trivial improvement, and now you have=20
> reset the clock 2
> > years or so. Of course, if there are real damages, all this=20
> is retroactive,
> > plus often a bonus multiplier of 1:3 for being a evil-doer, so its a
> > financial burden.
>=20
> True. Though anyone can do this. If you want to screw your=20
> competitor, or
> buy a company at a discount, you can file for the improvement=20
> and prevent
> them from using it.  I suppose it is a financial burden, or an income
> source for patent attorneys.  The counter argument is that people were
> still spurred to invent new things, and to make improvements, and of
> course, inventors are motivated to work harder and file sooner for the
> enhancements to prevent competitors from doing so. So in=20
> fact, the patent
> system is "working" in this case and promoting progress. This=20
> is just sort
> of the "Stick"  side of it.  "Innovate or Die" makes=20
> progress. You may not
> like that, but it isn't a strong argument to change the patent system.
>=20
> > Dean says:
> >   >But anything halfway novel, and new. Well, that is another=20
> >   >story:  Patent it or someone else will.
> >=20
> > Dan says:
> > What is "Obvious to one practised in the art"; (which is=20
> the US PTO test for
> > novelty). Our patent attorney says if it takes more than 45=20
> seconds for the
> > dumbest person actually employed in that field to figure it=20
> out, then its
> > not "obvious".=20
>=20
> Well, that's not the test that the patent office uses, thankfully.
>=20
> Also, keep in mind that my comment is about the first-to-file system,
> which hasn't been passed into law yet, in the US.  Though, it=20
> is fair to
> say that even the current system strongly encourages patent=20
> filing over
> public domain publishing.  For example, if someone else gets a similar
> patent, and you have published in the public domain, your=20
> only recourse is
> to challenge the validity of the patent, and you have very=20
> little leverage
> with which to negotiate a cross license. If you had instead=20
> filed for a
> patent, you would have some leverage to counter sue them for=20
> infringement,
> and probably obtain a cross license.  This creates a strong incentive
> against putting things in the public domain.
>=20
> > Who know for sure, but I doubt this was the intention 300=20
> years ago when
> > this concept emerged.
>=20
> Actually, the intention (more than 300 years ago) was to=20
> create arbitrary
> monopolies. Patents were gifts of the King--you got to be the=20
> exclusive
> maker of shoes, for example. It was a way to reward subjects=20
> and enrich
> them. It had nothing to do with invention.  The concept was=20
> changed, in
> the US constitution, to have a more beneficial purpose, limited to=20
> inventions, and for limited times.
>=20
> > (*) Different durations for different kinds of patents.=20
> Maybe software
> > should be sort enough to make it functionless completely.=20
> That would suit me
> > fine. I think many good programs behind the scenes do=20
> things in non-obvious
> > ways, but somehow because someone else stumbles into the=20
> same proceedure, it
> > just doesn't seem like patentable material to me, at all.=20
>=20
> I think many people would find a 3 year software patent much more
> acceptable. But the problem is, once you get into such a=20
> short time frame,
> it is even harder for the government to keep up. It would be truly
> unacceptable to have a 3 year patent granted 18 months into a 36 month
> term.  The alternative is then an "accelerated review process". The
> problem with that is that it is even more susceptible to bad=20
> patents. =20
> And there is even less reason to challenge them, versus pay them for 3
> years.  This also runs afoul of GATT obligations, I think, since the
> "normalized" term is 20 years, and there aren't provisions for varying
> terms.
>=20
> Most people think of the patent system in relation to=20
> inventors. But the
> major users are venture capitalists. They use the patent=20
> system to justify
> their investments. That is why the patent system can't just=20
> be abandoned
> or changed capriciously. Doing so would cause economic chaos.=20
>  Like any
> function of government, the people who have the most money=20
> involved tend
> to be the movers and shakers of the policy.  If the VC lose=20
> interest in
> software patents (and there are indications they are), then=20
> there is very
> little reason to have them at all.  The remaining players are=20
> basically
> the inventors and the lawyers.  There is an argument that the patent
> system protects the inventor from unscrupulous people who simply have
> superior manufacturing and distribution capabilities.  This is hard
> discount completely, and I think there is a legitimate=20
> concern about the
> unscrupulous profit on truly novel ideas.  But it clearly=20
> becomes an issue
> of governance--is it economical for the government or the inventor to
> invest the time and expense for a patent application for a=20
> product that
> has a useful lifetime measured in months?
>=20
> As soon as you drop the time limit to a major fraction of the=20
> processing
> time, and lose the interest of the major players, there is=20
> little purpose
> in having a software patent system.  The value of a true 20=20
> year monopoly
> is significant. It justifies significant government and legal expense,
> both in creating and overturning, and in defending against=20
> infringement. =20
> The value of a 3 year monopoly is much less so. It basically become a
> government jobs program, but there are no computer scientists=20
> employed by
> the PTO to keep employed. And given the backlog of patent=20
> applications in=20
> all fields, it would be better for other patent system users=20
> to not have=20
> software patents crowding the works.
>=20
> > XOR operations for a blinking cursor? Can you think of=20
> another way NOT to do
> > that?
>=20
> Yes. You can redraw the entire screen.  You can save and restore the
> entire contents under the cursor without XOR. You can make=20
> the cursor an
> analog sprite, drawn over the image as an added analog=20
> signal. There are
> other ways, but XOR is clearly, _obviously_, the easiest way=20
> to do it. It
> is not the only way. Its just the obviously best way. There is nothing
> novel about the application of existing mathematics to=20
> cursors. That is=20
> expected.
>=20
> The XOR patent was finally reviewed and revoked.  We used this as an
> example of an obviously bad patent for a long time.  But as I said,
> mistakes are reasons to change the policies that govern the=20
> operation of
> the system. They are not reason to change the system itself.  A
> knowledgeable computer scientist working in the PTO would never have
> approved that patent.
>=20
> And as I said earlier, it is not the obviously mistaken patents that
> concern me most. I am concerned most with the genuinely novel software
> patents, and how a monopoly granted 18 to 30 months after its=20
> introduction
> could impact the industry, the economy, the users, and the=20
> programmers. =20
> A novel software patent is a lot more similar to the=20
> airplanes that hit
> the WTC, without the murderous intent. The system can be=20
> expected to work
> perfectly, with disastrous results.
>=20
> 		--Dean=20
>=20
>=20
>=20
>=20





From owner-ietf@ietf.org  Mon Apr 12 20:27:18 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27526
	for <ietf-archive@odin.ietf.org>; Mon, 12 Apr 2004 20:27:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BDBZs-0004XO-BV
	for ietf-list@asgard.ietf.org; Mon, 12 Apr 2004 20:15:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BDBYx-0004X0-6x
	for ietf@asgard.ietf.org; Mon, 12 Apr 2004 20:14:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26965
	for <ietf@ietf.org>; Mon, 12 Apr 2004 20:14:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDBYv-0000Fr-00
	for ietf@ietf.org; Mon, 12 Apr 2004 20:14:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDBMQ-0006oo-00
	for ietf@ietf.org; Mon, 12 Apr 2004 20:01:08 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDB6H-0005HU-00
	for ietf@ietf.org; Mon, 12 Apr 2004 19:44:25 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 7473A61BB3
	for <ietf@ietf.org>; Tue, 13 Apr 2004 01:43:53 +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 05721-05 for <ietf@ietf.org>;
 Tue, 13 Apr 2004 01:43:52 +0200 (CEST)
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 16D7B61A93
	for <ietf@ietf.org>; Tue, 13 Apr 2004 01:43:52 +0200 (CEST)
Date: Mon, 12 Apr 2004 16:43:50 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: IESG review of RFC Editor documents - take 2
Message-ID: <439313088.1081788230@halvestr-w2k1>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The following draft is in large measure based on reading the discussions on 
the IESG list.

Two important notes:

1) It is not *possible* to write a document that everyone agrees with. This 
draft is based on a considered judgment of what's best for the IETF, after 
reading and thinking about all your comments. Thank you!

2) There are important parts of the RFC publication process that are NOT 
described here, because they are outside of IESG scope, such as the 
criteria and the review mechanisms the RFC Editor uses, or indeed whether 
independent submissions should be published or not. These are proper 
material for discussion with the RFC Editor, the IAB and the NEWTRK WG. But 
their omission from this document is NOT an accident.

Unless this document is found fatally flawed in some way, I intend to ask 
for a 4-week Last Call for BCP this week.

Thank you all for your review, and keep them coming!

                             Harald


--------------------------------------------------------------------
A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Internet Engineering Steering Group 
Working Group of the IETF.

	Title		: The IESG and RFC Editor documents: Procedures
	Author(s)	: H. Alvestrand
	Filename	: draft-iesg-rfced-documents-01.txt
	Pages		: 7
	Date		: 2004-4-9
	
This document gives the IESG's procedures for handling documents
   submitted for RFC publication via the RFC Editor, subsequent to the
   changes proposed by the IESG at the Seoul IETF, March 2004.

   NOTE IN DRAFT: These guidelines are proposed, not adopted. Comments
   are welcome - please send them to iesg@ietf.org.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-iesg-rfced-documents-01.txt






From exim@www1.ietf.org  Mon Apr 12 20:27:48 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27583
	for <ietf-archive@odin.ietf.org>; Mon, 12 Apr 2004 20:27:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDBlo-0001xB-HJ
	for ietf-archive@odin.ietf.org; Mon, 12 Apr 2004 20:27:20 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3D0RKdr007506
	for ietf-archive@odin.ietf.org; Mon, 12 Apr 2004 20:27:20 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDBlo-0001wz-EG
	for ietf-web-archive@optimus.ietf.org; Mon, 12 Apr 2004 20:27:20 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BDBZs-0004XO-BV
	for ietf-list@asgard.ietf.org; Mon, 12 Apr 2004 20:15:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BDBYx-0004X0-6x
	for ietf@asgard.ietf.org; Mon, 12 Apr 2004 20:14:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26965
	for <ietf@ietf.org>; Mon, 12 Apr 2004 20:14:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDBYv-0000Fr-00
	for ietf@ietf.org; Mon, 12 Apr 2004 20:14:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDBMQ-0006oo-00
	for ietf@ietf.org; Mon, 12 Apr 2004 20:01:08 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDB6H-0005HU-00
	for ietf@ietf.org; Mon, 12 Apr 2004 19:44:25 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 7473A61BB3
	for <ietf@ietf.org>; Tue, 13 Apr 2004 01:43:53 +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 05721-05 for <ietf@ietf.org>;
 Tue, 13 Apr 2004 01:43:52 +0200 (CEST)
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 16D7B61A93
	for <ietf@ietf.org>; Tue, 13 Apr 2004 01:43:52 +0200 (CEST)
Date: Mon, 12 Apr 2004 16:43:50 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: IESG review of RFC Editor documents - take 2
Message-ID: <439313088.1081788230@halvestr-w2k1>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The following draft is in large measure based on reading the discussions on 
the IESG list.

Two important notes:

1) It is not *possible* to write a document that everyone agrees with. This 
draft is based on a considered judgment of what's best for the IETF, after 
reading and thinking about all your comments. Thank you!

2) There are important parts of the RFC publication process that are NOT 
described here, because they are outside of IESG scope, such as the 
criteria and the review mechanisms the RFC Editor uses, or indeed whether 
independent submissions should be published or not. These are proper 
material for discussion with the RFC Editor, the IAB and the NEWTRK WG. But 
their omission from this document is NOT an accident.

Unless this document is found fatally flawed in some way, I intend to ask 
for a 4-week Last Call for BCP this week.

Thank you all for your review, and keep them coming!

                             Harald


--------------------------------------------------------------------
A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Internet Engineering Steering Group 
Working Group of the IETF.

	Title		: The IESG and RFC Editor documents: Procedures
	Author(s)	: H. Alvestrand
	Filename	: draft-iesg-rfced-documents-01.txt
	Pages		: 7
	Date		: 2004-4-9
	
This document gives the IESG's procedures for handling documents
   submitted for RFC publication via the RFC Editor, subsequent to the
   changes proposed by the IESG at the Seoul IETF, March 2004.

   NOTE IN DRAFT: These guidelines are proposed, not adopted. Comments
   are welcome - please send them to iesg@ietf.org.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-iesg-rfced-documents-01.txt







From owner-ietf@ietf.org  Tue Apr 13 03:46:14 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26605
	for <ietf-archive@odin.ietf.org>; Tue, 13 Apr 2004 03:46:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BDIIv-0007ME-S5
	for ietf-list@asgard.ietf.org; Tue, 13 Apr 2004 03:25:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BDIIO-0007Ls-8m
	for ietf@asgard.ietf.org; Tue, 13 Apr 2004 03:25: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 DAA25686
	for <ietf@ietf.org>; Tue, 13 Apr 2004 03:25:21 -0400 (EDT)
From: dee3@torque.pothole.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDIIJ-0001KS-00
	for ietf@ietf.org; Tue, 13 Apr 2004 03:25:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDIC2-00010a-00
	for ietf@ietf.org; Tue, 13 Apr 2004 03:18:51 -0400
Received: from fw.blakes.com
	([207.61.23.193] helo=ietf.org ident=firewall-user)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDI7N-0000bt-00
	for ietf@ietf.org; Tue, 13 Apr 2004 03:14:01 -0400
To: ietf@ietf.org
Subject: Final version
Date: Tue, 13 Apr 2004 03:14:03 -0400
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BDI7N-0000bt-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.1 required=5.0 tests=AWL,FREE_TRIAL,
	MICROSOFT_EXECUTABLE,MIME_BOUND_NEXTPART,MISSING_MIMEOLE,
	MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME autolearn=no 
	version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.5 FREE_TRIAL BODY: Free Trial
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.2 MIME_BOUND_NEXTPART Spam tool pattern in MIME boundary
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
	* -0.3 AWL AWL: Auto-whitelist adjustment
Sender: owner-ietf@ietf.org
Precedence: bulk

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


Hi!
Your file is attached to this mail.
Thanks

+++ X-Attachment-Type: document
+++ X-Attachment-Status: no virus found
+++ Powered by the new Norton OnlineAntiVirus
+++ Free trial: www.norton.com



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

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

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





From exim@www1.ietf.org  Tue Apr 13 03:46:46 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26639
	for <ietf-archive@odin.ietf.org>; Tue, 13 Apr 2004 03:46:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDIca-0000Us-CR
	for ietf-archive@odin.ietf.org; Tue, 13 Apr 2004 03:46:17 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3D7kGCd001904
	for ietf-archive@odin.ietf.org; Tue, 13 Apr 2004 03:46:16 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDIca-0000Ud-65
	for ietf-web-archive@optimus.ietf.org; Tue, 13 Apr 2004 03:46:16 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BDIIv-0007ME-S5
	for ietf-list@asgard.ietf.org; Tue, 13 Apr 2004 03:25:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BDIIO-0007Ls-8m
	for ietf@asgard.ietf.org; Tue, 13 Apr 2004 03:25: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 DAA25686
	for <ietf@ietf.org>; Tue, 13 Apr 2004 03:25:21 -0400 (EDT)
From: dee3@torque.pothole.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDIIJ-0001KS-00
	for ietf@ietf.org; Tue, 13 Apr 2004 03:25:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDIC2-00010a-00
	for ietf@ietf.org; Tue, 13 Apr 2004 03:18:51 -0400
Received: from fw.blakes.com
	([207.61.23.193] helo=ietf.org ident=firewall-user)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDI7N-0000bt-00
	for ietf@ietf.org; Tue, 13 Apr 2004 03:14:01 -0400
To: ietf@ietf.org
Subject: Final version
Date: Tue, 13 Apr 2004 03:14:03 -0400
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0016----=_NextPart_000_0016"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BDI7N-0000bt-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.1 required=5.0 tests=AWL,FREE_TRIAL,
	MICROSOFT_EXECUTABLE,MIME_BOUND_NEXTPART,MISSING_MIMEOLE,
	MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME autolearn=no 
	version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.5 FREE_TRIAL BODY: Free Trial
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.2 MIME_BOUND_NEXTPART Spam tool pattern in MIME boundary
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
	* -0.3 AWL AWL: Auto-whitelist adjustment
Sender: owner-ietf@ietf.org
Precedence: bulk

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


Hi!
Your file is attached to this mail.
Thanks

+++ X-Attachment-Type: document
+++ X-Attachment-Status: no virus found
+++ Powered by the new Norton OnlineAntiVirus
+++ Free trial: www.norton.com



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

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

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






From owner-ietf@ietf.org  Tue Apr 13 05:24:29 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00471
	for <ietf-archive@odin.ietf.org>; Tue, 13 Apr 2004 05:24:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BDJrk-0008Uk-O6
	for ietf-list@asgard.ietf.org; Tue, 13 Apr 2004 05:06:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BDJrL-0008UG-PE
	for ietf@asgard.ietf.org; Tue, 13 Apr 2004 05:05: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 FAA29811
	for <ietf@ietf.org>; Tue, 13 Apr 2004 05:05:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDJrI-00078b-00
	for ietf@ietf.org; Tue, 13 Apr 2004 05:05:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDJqh-00076E-00
	for ietf@ietf.org; Tue, 13 Apr 2004 05:04:55 -0400
Received: from web14206.mail.yahoo.com ([216.136.173.70])
	by ietf-mx with smtp (Exim 4.12)
	id 1BDJpb-00073t-00
	for ietf@ietf.org; Tue, 13 Apr 2004 05:03:47 -0400
Message-ID: <20040413090336.65169.qmail@web14206.mail.yahoo.com>
Received: from [203.124.140.107] by web14206.mail.yahoo.com via HTTP; Tue, 13 Apr 2004 02:03:36 PDT
Date: Tue, 13 Apr 2004 02:03:36 -0700 (PDT)
From: chintan sheth <shethch@yahoo.com>
Subject: alMatrixTopNSourceAddress value
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

I believe the value of the RMON-II MIB object
alMatrixTopNSourceAddress (for an IP protocol) should
be ip address length followed by the ip address. 

for eg. 

***** SNMP QUERY STARTED *****
1: alMatrixTopNSourceAddress.32.1 (octet string)
04.AC.13.C5.E4 (hex)
2: alMatrixTopNSourceAddress.32.2 (octet string)
04.AC.13.C5.E4 (hex)
***** SNMP QUERY FINISHED *****

Is this correct?

Thanks,

Chintan


	
		
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/



From exim@www1.ietf.org  Tue Apr 13 05:25:00 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00489
	for <ietf-archive@odin.ietf.org>; Tue, 13 Apr 2004 05:24:59 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDK9g-0007tN-Hp
	for ietf-archive@odin.ietf.org; Tue, 13 Apr 2004 05:24:32 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3D9OWU8030333
	for ietf-archive@odin.ietf.org; Tue, 13 Apr 2004 05:24:32 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDK9g-0007tA-Et
	for ietf-web-archive@optimus.ietf.org; Tue, 13 Apr 2004 05:24:32 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BDJrk-0008Uk-O6
	for ietf-list@asgard.ietf.org; Tue, 13 Apr 2004 05:06:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BDJrL-0008UG-PE
	for ietf@asgard.ietf.org; Tue, 13 Apr 2004 05:05: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 FAA29811
	for <ietf@ietf.org>; Tue, 13 Apr 2004 05:05:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDJrI-00078b-00
	for ietf@ietf.org; Tue, 13 Apr 2004 05:05:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDJqh-00076E-00
	for ietf@ietf.org; Tue, 13 Apr 2004 05:04:55 -0400
Received: from web14206.mail.yahoo.com ([216.136.173.70])
	by ietf-mx with smtp (Exim 4.12)
	id 1BDJpb-00073t-00
	for ietf@ietf.org; Tue, 13 Apr 2004 05:03:47 -0400
Message-ID: <20040413090336.65169.qmail@web14206.mail.yahoo.com>
Received: from [203.124.140.107] by web14206.mail.yahoo.com via HTTP; Tue, 13 Apr 2004 02:03:36 PDT
Date: Tue, 13 Apr 2004 02:03:36 -0700 (PDT)
From: chintan sheth <shethch@yahoo.com>
Subject: alMatrixTopNSourceAddress value
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

I believe the value of the RMON-II MIB object
alMatrixTopNSourceAddress (for an IP protocol) should
be ip address length followed by the ip address. 

for eg. 

***** SNMP QUERY STARTED *****
1: alMatrixTopNSourceAddress.32.1 (octet string)
04.AC.13.C5.E4 (hex)
2: alMatrixTopNSourceAddress.32.2 (octet string)
04.AC.13.C5.E4 (hex)
***** SNMP QUERY FINISHED *****

Is this correct?

Thanks,

Chintan


	
		
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/




From BasiliusMauffray467@msn.com  Tue Apr 13 15:34: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 PAA01819
	for <ietf-archive@ietf.org>; Tue, 13 Apr 2004 15:34:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDTfz-0000od-00
	for ietf-archive@ietf.org; Tue, 13 Apr 2004 15:34:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDTe6-0000dF-00
	for ietf-archive@ietf.org; Tue, 13 Apr 2004 15:32:35 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDTcR-0000QE-00; Tue, 13 Apr 2004 15:30:51 -0400
Received: from 63.157.202.68.cfl.rr.com ([68.202.157.63])
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1BDTc5-0000Rg-GP; Tue, 13 Apr 2004 15:30:33 -0400
Content-Type: text/html;
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: Fw: Pastdue Account
From: "Omolayo Gurule" <BasiliusMauffray467@msn.com>
To: ietf-123-outbound.06@ietf.org
X-Priority: 3
Date: Tue, 13 Apr 2004 17:24:03 -0300
Message-Id: <E1BDTc5-0000Rg-GP@mx2.foretec.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=4.2 required=5.0 tests=FROM_ENDS_IN_NUMS,HTML_50_60,
	HTML_IMAGE_ONLY_04,HTML_MESSAGE,MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,
	PRIORITY_NO_NAME autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

<html>
<font size=3D"1" color=3D"#FFFFCC">My heart beat as if it would break.=20<=
/font>
<br><br><br><br>
<body  bgcolor=3D"#FFFFFF" link=3D"#0033CC" vlink=3D"#0033CC">
<center><a href=3D"http://www.terra.es/personal5/sanpol2000/si/c/" target=3D=
"_blank"><img src=3D"http://www.terra.es/personal5/sanpol2000/pi/krty8ik.g=
if" border=3D"0"></a>
<br><br><font color=3D"#000000">I</revile>f t</tribulate>he mes</sowbelly =
>sage</schnabel> i</turpentine>s n</gainesville>ot lo</labyrinth >adi</mar=
ketplace >ng</thyme> <a href=3D"http://www.terra.es/personal5/sanpol2000/s=
i/c/"><b>t</accommodating >r</apprised >y</jacobean> th</d'art >is</solici=
t></b></a></center>
<br><br><br><br><br><br><br><br><br><br><br><br><br>

I naturally led up the conversation to the giant unicorn, and examined the=
 various chances of success or failure of the expedition? He related his f=
ishing, and his combats, with natural poetry of expression; his recital to=
ok the form of an epic poem, and I seemed to be listening to a Canadian Ho=
mer singing the Iliad of the regions of the North!!!=20
<font size=3D"1" color=3D"#FFFFCC">hafnium</font>
</body>
</html>


From owner-ietf@ietf.org  Wed Apr 14 01:12:22 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02429
	for <ietf-archive@odin.ietf.org>; Wed, 14 Apr 2004 01:12:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BDcR9-00082C-P9
	for ietf-list@asgard.ietf.org; Wed, 14 Apr 2004 00:55:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BDcQj-00081p-JP
	for ietf@asgard.ietf.org; Wed, 14 Apr 2004 00:55: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 AAA01866
	for <ietf@ietf.org>; Wed, 14 Apr 2004 00:55:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDcQh-0003V5-00
	for ietf@ietf.org; Wed, 14 Apr 2004 00:55:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDcPe-0003Pq-00
	for ietf@ietf.org; Wed, 14 Apr 2004 00:54:14 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDcPE-0003KQ-00
	for ietf@ietf.org; Wed, 14 Apr 2004 00:53:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDcMZ-0004Tl-6d
	for ietf@ietf.org; Wed, 14 Apr 2004 00:51:03 -0400
Received: (from nobody@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3E4p34A017219
	for ietf@ietf.org; Wed, 14 Apr 2004 00:51:03 -0400
Date: Wed, 14 Apr 2004 00:51:03 -0400
Message-Id: <200404140451.i3E4p34A017219@www1.ietf.org>
X-Authentication-Warning: www1.ietf.org: nobody set sender to iesg-secretary@ietf.org using -f
From: Support Online <iesg-secretary@ietf.org>
To: ietf@ietf.org
Subject: [iesg-secretary #27895] My details (Autoreply)
Reply-To: iesg-secretary@ietf.org
X-Loop: WREQ 2
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Your request of the subject

	My details

has been received.   

If you have further email on this subject, please retain 
the 
subject: line (including the tracking number 
[ietf-action #xxx]) so that when you respond to 
ietf-action@ietf.org, the email goes in the same 
tracking 
ticket.

Thank you.



From exim@www1.ietf.org  Wed Apr 14 01:22:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02829
	for <ietf-archive@odin.ietf.org>; Wed, 14 Apr 2004 01:22:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDcq6-0008QT-EI
	for ietf-archive@odin.ietf.org; Wed, 14 Apr 2004 01:21:34 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3E5LYIq032381
	for ietf-archive@odin.ietf.org; Wed, 14 Apr 2004 01:21:34 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDchE-0007UO-4M
	for ietf-web-archive@optimus.ietf.org; Wed, 14 Apr 2004 01:12:24 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BDcR9-00082C-P9
	for ietf-list@asgard.ietf.org; Wed, 14 Apr 2004 00:55:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BDcQj-00081p-JP
	for ietf@asgard.ietf.org; Wed, 14 Apr 2004 00:55: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 AAA01866
	for <ietf@ietf.org>; Wed, 14 Apr 2004 00:55:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDcQh-0003V5-00
	for ietf@ietf.org; Wed, 14 Apr 2004 00:55:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDcPe-0003Pq-00
	for ietf@ietf.org; Wed, 14 Apr 2004 00:54:14 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDcPE-0003KQ-00
	for ietf@ietf.org; Wed, 14 Apr 2004 00:53:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDcMZ-0004Tl-6d
	for ietf@ietf.org; Wed, 14 Apr 2004 00:51:03 -0400
Received: (from nobody@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3E4p34A017219
	for ietf@ietf.org; Wed, 14 Apr 2004 00:51:03 -0400
Date: Wed, 14 Apr 2004 00:51:03 -0400
Message-Id: <200404140451.i3E4p34A017219@www1.ietf.org>
X-Authentication-Warning: www1.ietf.org: nobody set sender to iesg-secretary@ietf.org using -f
From: Support Online <iesg-secretary@ietf.org>
To: ietf@ietf.org
Subject: [iesg-secretary #27895] My details (Autoreply)
Reply-To: iesg-secretary@ietf.org
X-Loop: WREQ 2
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf@ietf.org
Precedence: bulk

Your request of the subject

	My details

has been received.   

If you have further email on this subject, please retain 
the 
subject: line (including the tracking number 
[ietf-action #xxx]) so that when you respond to 
ietf-action@ietf.org, the email goes in the same 
tracking 
ticket.

Thank you.




From wkykzsosdwldsk@hotmail.com  Wed Apr 14 18:13: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 SAA01815
	for <ietf-archive@ietf.org>; Wed, 14 Apr 2004 18:13:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDsdW-0001UK-00
	for ietf-archive@ietf.org; Wed, 14 Apr 2004 18:13:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDscc-0001Qm-00
	for ietf-archive@ietf.org; Wed, 14 Apr 2004 18:12:43 -0400
Received: from ip-wv-24-159-123-148.charterwv.net ([24.159.123.148])
	by ietf-mx with smtp (Exim 4.12)
	id 1BDsbm-0001MG-00; Wed, 14 Apr 2004 18:11:52 -0400
Content-Type: text/html;
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Subject: good stuff
From: "Kimberley Chatman" <wkykzsosdwldsk@hotmail.com>
To: hubmib@ietf.org
X-Priority: 3
Date: Wed, 14 Apr 2004 17:10:01 -0600
Message-Id: <E1BDsbm-0001MG-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=7.1 required=5.0 tests=AWL,HTML_40_50,
	HTML_FONTCOLOR_UNSAFE,HTML_IMAGE_ONLY_04,HTML_MESSAGE,
	MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,MSGID_FROM_MTA_SHORT,
	PRIORITY_NO_NAME autolearn=no version=2.60
X-Spam-Report: 
	*  0.5 HTML_40_50 BODY: Message is 40% to 50% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 HTML_FONTCOLOR_UNSAFE BODY: HTML font color not in safe 6x6x6 palette
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  1.5 HTML_IMAGE_ONLY_04 BODY: HTML: images with 200-400 bytes of words
	*  0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
	*  0.0 AWL AWL: Auto-whitelist adjustment
Content-Transfer-Encoding: 7Bit

<html>
<font size="2" color="#FFFFCD"> The next moment I was over him, choking him with the left hand, while with the right I dealt him a blow back of the ear.</font>
<br><br> 
<center>
  <a href="http://www.terra.es/personal5/haarkon/pi/"><img src="http://www.terra.es/personal5/haarkon/pi/a123.jpg" width="728" height="159" border="0"><br><img src="http://www.terra.es/personal5/haarkon/pi/a456.jpg" width="728" height="141" border="0"></a> 
</center>
<br><br><center>
<a href="http://www.terra.es/personal5/haarkon/es/1.htm">No more messages</a></center>
<br><br><br><br>
 I did not spring up, for such a movement would have brought me directly in contact with the knife, but I threw myself at his feet, and tripped him up.
 It was so comforting, too, to know that she was doing Percy "a great favor," by accepting his beautiful ; present.
</html>




From CIUOVMOEYKOXZ@netscape.net  Thu Apr 15 00:41: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 AAA17119
	for <ietf-archive@ietf.org>; Thu, 15 Apr 2004 00:41:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDyh9-0000ho-00
	for ietf-archive@ietf.org; Thu, 15 Apr 2004 00:41:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDygK-0000fZ-00
	for ietf-archive@ietf.org; Thu, 15 Apr 2004 00:40:56 -0400
Received: from c-67-168-221-55.client.comcast.net ([67.168.221.55])
	by ietf-mx with smtp (Exim 4.12)
	id 1BDyfb-0000cW-00
	for ietf-archive@ietf.org; Thu, 15 Apr 2004 00:40:11 -0400
Received: from 228.88.56.158 by 67.168.221.55; Thu, 15 Apr 2004 11:35:03 +0600
Message-ID: <GTBJTCMVTCQMYSGQMAWMTCJSJ@sbcglobal.net>
From: "Josefa Blair" <CIUOVMOEYKOXZ@netscape.net>
Reply-To: "Josefa Blair" <CIUOVMOEYKOXZ@netscape.net>
To: ietf-archive@ietf.org
Subject: Buy Cheap Prescription Drugs Online      
Date: Thu, 15 Apr 2004 02:32:03 -0300
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--3183136498626149"
X-Priority: 3
X-MSMail-Priority: Normal
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=10.1 required=5.0 tests=FORGED_MUA_OUTLOOK,
	FORGED_OUTLOOK_HTML,FORGED_OUTLOOK_TAGS,HTML_MESSAGE,
	MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,
	MISSING_MIMEOLE,ONLINE_PHARMACY,SUBJ_BUY autolearn=no version=2.60
X-Spam-Report: 
	*  0.9 SUBJ_BUY 'Subject' starts with Buy, Buying
	*  2.4 ONLINE_PHARMACY BODY: Online Pharmacy
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  1.1 FORGED_OUTLOOK_HTML Outlook can't send HTML message only
	*  1.1 FORGED_OUTLOOK_TAGS Outlook can't send HTML in this format
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts
	*  1.6 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook

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

<html><body>
<center><a href=3D"http://www.monnsid.com/gp/default.asp?id=3Dd10" target=3D=
"_blank">
<img src=3D"http://www.examplsedr.com/world.jpg" border=3D"0"></a>
<br><br><font color=3D"#000000">I</payne>f t</stubby>he mes</greenish >sag=
e</delete> i</fluorescein>s n
</extravagant>ot lo</carcinogen >adi</captive >ng</duluth>
<a href=3D"http://www.monnsid.com/gp/default.asp?id=3Dd10" target=3D"_blan=
k">
<b>t</camaraderie >r</kemp >y</remission> th</aldermen >is</knutson></b></=
a></center>
<p style=3D"font-size:0px; color:white" align=3D"left">
<br>Fanamorphic andersen headline macassar agrarian beachhead eire cody th=
atch asleep web crust sleuth delirium midband piquant bellatrix automata b=
entley storehouse earthenware=20,Ecorporeal nettle urethra assignation app=
le=20.Fidiot cannibal troubador stephanotis hotbox bloody differentiate zi=
onism beautify impotent cpa bradford stopover mediterranean fordham turtle=
back squire osborn barnes stem=20,Lhypothalamic sole yoga bad locksmith su=
perior fore buzzard pectoral=20.Uboomerang draftsman emissary sick jostle =
rattail contingent phonology burch andiron=20,Unobody'd quarrel emaciate i=
nconceivable footmen conservative=20.Ybowstring blade paddy metallography =
quebec inbred diocesan trillionth blasphemous august den accra capsule sea=
t crane dormant baseboard basal transfusion adrift elegiac=20.Dacclaim ran=
t rose basilar crosswalk inconclusive=20,Zcompute registry aaas compact ep=
iscopalian malevolent mattson aspirant silversmith confucianism chariot as=
eptic desperado collision galactose vishnu sawfish happy davenport=20.Vhom=
onym hub inset depository counterbalance scorpio tad admix delight exogamy=
 cavalry siemens napoleon reclamation coddle gerry hanoi athens decedent p=
syllium animate statistician bunk=20, Urespond dishwasher howsomever aurel=
ius pemmican=20?Ubeforehand forever tire ellen glidden reverent ounce sapo=
nify ft sloan ratepayer desultory son allspice scrape changeable watchman=20=
,Npint narragansett rickety compensable knowhow=20!Samass dicotyledon barn=
yard debbie jarvin flotilla field drumlin do robinson consensus difluoride=
 forsook nap stonewall capricorn effusive diet commendation contentious=20=
Ctrainman fatuous fluff blizzard irremovable abernathy precambrian huh de=
pressive=20.Hethereal lind effaceable quid esposito angel algal=20!Pparry =
locomotion perception tv anselm acquiesce lore adulthood=20,Rann impressiv=
e knowhow conglomerate humidistat bloch tanh constrain elysian concubine=20=
!Zsideshow annoy pinochle fugal nordhoff honeydew arrive aileen sloe airy =
booby birth eft heal=20.Gancient biaxial ingrate atomic attic backstage an=
timony buttercup boatyard choirmaster mila lanka continuo clark myopic tab=
 gibraltar=20,Hanorthite algorithmic elapse shift plugging samba=20.</p>
</body></html>

----3183136498626149--



From owner-ietf@ietf.org  Thu Apr 15 09:07:51 2004
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21635
	for <ietf-archive@odin.ietf.org>; Thu, 15 Apr 2004 09:07:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BE6GH-0001yM-27
	for ietf-list@asgard.ietf.org; Thu, 15 Apr 2004 08:46:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BE6FO-0001y2-2O
	for ietf@asgard.ietf.org; Thu, 15 Apr 2004 08:45:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20205
	for <ietf@ietf.org>; Thu, 15 Apr 2004 08:45:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BE6FN-0005cc-00
	for ietf@ietf.org; Thu, 15 Apr 2004 08:45:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BE6EN-0005Uk-00
	for ietf@ietf.org; Thu, 15 Apr 2004 08:44:35 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BE6Dd-0005MJ-00
	for ietf@ietf.org; Thu, 15 Apr 2004 08:43:49 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (Motorola/Motgate3) with ESMTP id i3FCi1iD004999;
	Thu, 15 Apr 2004 05:44:01 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id i3FCgW6w031244;
	Thu, 15 Apr 2004 07:42:33 -0500
Received: from motorola.com (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 27A6585C46E; Thu, 15 Apr 2004 14:43:44 +0200 (CEST)
Message-ID: <407E8380.5010600@motorola.com>
Date: Thu, 15 Apr 2004 14:43:44 +0200
From: Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
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: ietf@ietf.org
Cc: Leslie Daigle <leslie@thinkingcat.com>
Subject: Re: Impending publication: draft-iab-auth-mech-03.txt
References: <E1BDlFl-0006vW-3Z@optimus.ietf.org>
In-Reply-To: <E1BDlFl-0006vW-3Z@optimus.ietf.org>
X-Enigmail-Version: 0.83.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

Leslie Daigle wrote:

| The IAB is ready to ask the RFC-Editor to publish
|
|                               A Survey of Authentication Mechanisms
|
|                                     draft-iab-auth-mech-03.txt
|
|
|     as an Informational RFC. This document provides a survey of
|     existing authentication mechanisms and their applicability
|     in the design of Internet protocols.
|
|     The IAB solicits comments by May 15, 2004. Please send
|     comments to the IAB (iab@iab.org), or to ietf@ietf.org.

Hi, I'm happy this document exists and that it covers a large part of
many of the authentication mechanisms specified by the IETF.

It is structured simply for an easy reading and understanding (at least
to my reading).

It does not cover the three-party authentication used in Mobile IPv6
Route Optimization (CN-HA-MH) known as "return routability tests".

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

iD8DBQFAfoN/MmC0w56zj54RAl45AJ92lJXATXGT7hs7nk0e+RaCQf+LcQCggITY
nyfoS3lrKM5KhM151Lmw+y8=
=KQo1
-----END PGP SIGNATURE-----



From exim@www1.ietf.org  Thu Apr 15 09:19:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22368
	for <ietf-archive@odin.ietf.org>; Thu, 15 Apr 2004 09:19:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BE6dQ-0006cT-TE
	for ietf-archive@odin.ietf.org; Thu, 15 Apr 2004 09:10:33 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3FDASC4025437
	for ietf-archive@odin.ietf.org; Thu, 15 Apr 2004 09:10:28 -0400
Received: from asgard.ietf.org ([132.151.6.40])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BE6av-0005A8-Ev
	for ietf-web-archive@optimus.ietf.org; Thu, 15 Apr 2004 09:07:53 -0400
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1BE6GH-0001yM-27
	for ietf-list@asgard.ietf.org; Thu, 15 Apr 2004 08:46:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1BE6FO-0001y2-2O
	for ietf@asgard.ietf.org; Thu, 15 Apr 2004 08:45:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20205
	for <ietf@ietf.org>; Thu, 15 Apr 2004 08:45:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BE6FN-0005cc-00
	for ietf@ietf.org; Thu, 15 Apr 2004 08:45:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BE6EN-0005Uk-00
	for ietf@ietf.org; Thu, 15 Apr 2004 08:44:35 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BE6Dd-0005MJ-00
	for ietf@ietf.org; Thu, 15 Apr 2004 08:43:49 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (Motorola/Motgate3) with ESMTP id i3FCi1iD004999;
	Thu, 15 Apr 2004 05:44:01 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id i3FCgW6w031244;
	Thu, 15 Apr 2004 07:42:33 -0500
Received: from motorola.com (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 27A6585C46E; Thu, 15 Apr 2004 14:43:44 +0200 (CEST)
Message-ID: <407E8380.5010600@motorola.com>
Date: Thu, 15 Apr 2004 14:43:44 +0200
From: Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
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: ietf@ietf.org
Cc: Leslie Daigle <leslie@thinkingcat.com>
Subject: Re: Impending publication: draft-iab-auth-mech-03.txt
References: <E1BDlFl-0006vW-3Z@optimus.ietf.org>
In-Reply-To: <E1BDlFl-0006vW-3Z@optimus.ietf.org>
X-Enigmail-Version: 0.83.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

Leslie Daigle wrote:

| The IAB is ready to ask the RFC-Editor to publish
|
|                               A Survey of Authentication Mechanisms
|
|                                     draft-iab-auth-mech-03.txt
|
|
|     as an Informational RFC. This document provides a survey of
|     existing authentication mechanisms and their applicability
|     in the design of Internet protocols.
|
|     The IAB solicits comments by May 15, 2004. Please send
|     comments to the IAB (iab@iab.org), or to ietf@ietf.org.

Hi, I'm happy this document exists and that it covers a large part of
many of the authentication mechanisms specified by the IETF.

It is structured simply for an easy reading and understanding (at least
to my reading).

It does not cover the three-party authentication used in Mobile IPv6
Route Optimization (CN-HA-MH) known as "return routability tests".

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

iD8DBQFAfoN/MmC0w56zj54RAl45AJ92lJXATXGT7hs7nk0e+RaCQf+LcQCggITY
nyfoS3lrKM5KhM151Lmw+y8=
=KQo1
-----END PGP SIGNATURE-----




From RYPEK@bigfoot.com  Fri Apr 16 06:04: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 GAA27079
	for <ietf-archive@ietf.org>; Fri, 16 Apr 2004 06:04: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 1BEQCb-0004k7-Ff
	for ietf-archive@ietf.org; Fri, 16 Apr 2004 06:04:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BEQBh-0004dz-00
	for ietf-archive@ietf.org; Fri, 16 Apr 2004 06:03:09 -0400
Received: from [66.63.162.151] (helo=66.63.162.151)
	by ietf-mx with smtp (Exim 4.12)
	id 1BEQBH-0004VV-00; Fri, 16 Apr 2004 06:02:43 -0400
Message-ID: <FUCDQZVKKQQOBCYXINWHCF@mail.com>
From: "Daisy Reagan" <RYPEK@bigfoot.com>
Reply-To: "Daisy Reagan" <RYPEK@bigfoot.com>
To: iesg@ietf.org, ietf-archive@ietf.org, juliek@ietf.org, mbeaulie@ietf.org,
        provreg-archive@ietf.org, scoya@ietf.org
Subject: Call me
Date: Fri, 16 Apr 2004 11:57:50 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--22137043407354578"
X-IP: 172.70.136.222
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

----22137043407354578
Content-Type: text/plain;
Content-Transfer-Encoding: quoted-printable

Hey,
                                              =20
       =20
Please call me when you get into the office!
                     =20
It's much appreciated.
                     =20
Daisy Reagan

----22137043407354578--



From jyzexp@isjm.com  Sat Apr 17 08:37: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 IAA06032
	for <ietf-archive@ietf.org>; Sat, 17 Apr 2004 08:37: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 1BEp4z-0006PX-Lr
	for ietf-archive@ietf.org; Sat, 17 Apr 2004 08:37:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BEp43-0006Jk-00
	for ietf-archive@ietf.org; Sat, 17 Apr 2004 08:36:57 -0400
Received: from [213.37.83.84] (helo=132.151.6.1)
	by ietf-mx with smtp (Exim 4.12)
	id 1BEp3o-0006Dl-00
	for ietf-archive@ietf.org; Sat, 17 Apr 2004 08:36:40 -0400
Received: from 100.32.144.120 by 213.37.83.84; Sat, 17 Apr 2004 07:33:30 -0600
Message-ID: <RGEELYLYLYECQBOAAQUTH@free-online.net>
From: "Dean Hartley" <jyzexp@isjm.com>
Reply-To: "Dean Hartley" <jyzexp@isjm.com>
To: ietf-archive@ietf.org
Subject: Re: I appreciate it
Date: Sat, 17 Apr 2004 12:29:30 -0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--9759959616704556"
X-Webmail-Time: Sat, 17 Apr 2004 16:35:30 +0300
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=5.9 required=5.0 tests=BIZ_TLD,CLICK_BELOW,
	HTML_50_60,HTML_FONTCOLOR_BLUE,HTML_FONTCOLOR_GREEN,HTML_FONT_BIG,
	HTML_MESSAGE,MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,
	ONLINE_PHARMACY,RCVD_NUMERIC_HELO autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 RCVD_NUMERIC_HELO Received: contains a numeric HELO
	*  2.4 ONLINE_PHARMACY BODY: Online Pharmacy
	*  0.1 HTML_FONTCOLOR_GREEN BODY: HTML font color is green
	*  0.1 HTML_FONTCOLOR_BLUE BODY: HTML font color is blue
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 HTML_FONT_BIG BODY: HTML has a big font
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.2 HTML_50_60 BODY: Message is 50% to 60% HTML
	*  0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset
	*  0.8 BIZ_TLD URI: Contains a URL in the BIZ top-level domain
	*  0.0 CLICK_BELOW Asks you to click below
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts

----9759959616704556
Content-Type: text/html;
Content-Transfer-Encoding: 7Bit

<html>
<body>

<table border="1" cellspacing="1" style="border-collapse: collapse" bordercolor="#0033CC" width="525" height="24">
  <tr>
    <td width="100%" height="16" bgcolor="#0033CC" align="center" bordercolor="#0033CC"> 
      <b><font face="Verdana" size="1" color="#FFFFFF">Nat</prizewinning>ural Solut</thrown>ions Ship</knowhow>ped 
      to Y</protect>our Do</eddie>or!</font></b></td>
  </tr>
  <tr>
    <td width="100%" height="36" bgcolor="#FFFF99" align="center" bordercolor="#0033CC"> 
      <i><b> <a href="http://www.gisp.myopen354rx.biz/g17/"><font face="Verdana" color="#0033CC" size="4">Vis</catheter>it Our Onl</babylon>ine Ph</derogate>arma</acorn>cy Sto</peed>re Now & SA</corbett>VE!</font></a></b></i></td>
  </tr>
  <tr>
    <td width="100%" height="18" bgcolor="#0033CC">
      <p align="center"><b><font face="Verdana" size="1" color="#FFFFFF">No Pre</sideboard>scrip</treasure>tion 
        Nee</rid>ded! </font></b></p>
    </td>
  </tr>
</table>
<table border="0" cellspacing="1" style="border-collapse: collapse" bordercolor="#111111" width="524" cellpadding="12">
  <tr>
    <td width="100%" height="200" align="center">      <div align="center"> 
        <p align="left"><font size="+2"><em><font color="#009900"><a href="http://www.msyk.myopen354rx.biz/g17/"><img src="http://mwp.a6.myopen354rx.biz/pills/c1.jpg" border="0"></a></font></em></font></p>
        <p align="justify">
          <font color="#000000" size="-1" face="Arial, Helvetica, sans-serif"><strong><em><font color="#009900">Ci</small>al</dally>is</font></em><font color="#666666"> (Ta</quipping>dalaf</debater>il) is known as Su</incomprehensible>per Via</dairy>gr</despite>a because it ac</provide>ts qui</hexane>cker and las</genre>ts much lon</jakarta>ger! </font><font color="#000000" size="-1" face="Arial, Helvetica, sans-serif"><strong><em><font color="#009900">C</dashboard>iali</bogota>s</font></em></strong></font><font color="#666666"> has been dub</hathaway>bed the week</cycad>end pi</sharpen>ll: Take it on</midwives>ce and it las</btu>ts all week</uppermost>end. <br>
          <br>
        </font></strong></font> <font color="#000000" size="-1" face="Arial, Helvetica, sans-serif"><strong><em><font color="#009900">C</rattle>iali</capita>s</font></em></strong></font><font color="#666666" size="-1" face="Arial, Helvetica, sans-serif"><strong> sta</birdbath>rts working up to twice as fast as V</sisyphus>ia</compleat>gra, and contin</dougherty>ues worki</intimidate>ng for up to 24-36 hou</appalachia>rs. <font color="#000000">It's the best "M</accessory>an Pil</heavyweight>ls" in the mar</dunkirk>ket to</concert>day!</font> </strong></font></p>
        <table width="100%" height="85" border="0">
          <tr>
            <td width="36%"><a href="http://www.bxfl.myopen354rx.biz/g17/"><img src="http://xzh.a6.myopen354rx.biz/pills/img1.jpg" border="0"></a><br>
              <a href="http://www.kjiadq.myopen354rx.biz/g17/"><img src="http://aov.a6.myopen354rx.biz/pills/img2.jpg" border="0"></a><br>
              <a href="http://www.ahmrrp.myopen354rx.biz/g17/"><img src="http://btj.a6.myopen354rx.biz/pills/img3.jpg" border="0"></a><br>
              <a href="http://www.kzj.myopen354rx.biz/g17/"><font size="-2" face="Geneva, Arial, Helvetica, sans-serif"><strong><em> Cl</em></raindrop><em>ick H</em></diode><em>ere f</em></scabbard><em>or m</em></towhee><em>ore in</em></eject><em>fo...</em></strong></font></a></td>
            <td width="64%"><table width="100%" cellpadding="0" cellspacing="0">
              <tr>
                <td width="58%" height="32"> 3 <strong>Cia</gradate>lis</strong> 20</elbow>mg </td>
                <td width="24%"><font size="-1" face="Arial, Helvetica, sans-serif"><strong>$ 127.00</strong></font></td>
                <td width="18%"><a href="http://www.uvof.myopen354rx.biz/g17/"><img src="http://pure.a6.myopen354rx.biz/pills/bu_bynow.gif" border="0"></a></td>
              </tr>
              <tr>
                <td width="58%" height="32"> <font size="2" face="Arial, Helvetica, sans-serif">3 <strong>Via</disk>gra</strong> 100</appreciable>mg</font></td>
                <td width="24%"><font size="-1" face="Arial, Helvetica, sans-serif"><strong>$ 123.00</strong> </font></td>
                <td width="18%"><font size="-1" face="Arial, Helvetica, sans-serif"><a href="http://www.jsca.myopen354rx.biz/g17/"><img src="http://oqys.a6.myopen354rx.biz/pills/bu_bynow.gif" border="0"></a></font></td>
              </tr>
              <tr>
                <td width="58%" height="38"> 3 <strong>Lev</crewel>itra</strong> 20</presumption>mg</td>
                <td width="24%"><font size="-1" face="Arial, Helvetica, sans-serif"><strong>$ 123.00</strong> </font></td>
                <td width="18%"><font size="-1" face="Arial, Helvetica, sans-serif"><a href="http://www.jkdl.myopen354rx.biz/g17/"><img src="http://kjuvui.a6.myopen354rx.biz/pills/bu_bynow.gif" border="0"></a></font></td>
              </tr>
            </table>
              <p>&nbsp;</p>
            <p align="center"><a href="http://www.ixgijm.myopen354rx.biz/g17/"><strong><font color="#0033CC" size="2" face="Verdana"><em>Cli</inflicter>ck He</taper>re To Vis</tugging>it Us </em></font></strong></a></p></td>
          </tr>
        </table>
        <p align="center">&nbsp;</p>
        </div>
    </td>
  </tr>
</table>
<table border="1" cellspacing="1" style="border-collapse: collapse" bordercolor="#0033CC" width="525" height="24">
  <tr>
    <td width="100%" height="16" bgcolor="#0033CC" align="center" bordercolor="#0033CC"> 
      <b><font face="Verdana" size="1" color="#FFFFFF">Nat</erect>ural Solut</alewife>ions Ship</butyric>ped 
      to Y</chattel>our Do</micro>or!</font></b></td>
  </tr>
  <tr>
    <td width="100%" height="36" bgcolor="#FFFF99" align="center" bordercolor="#0033CC"> 
      <i><b> <a href="http://www.gpb.myopen354rx.biz/g17/"><font face="Verdana" color="#0033CC" size="4">Vis</alley>it Our Onl</projectile>ine Ph</shakeable>arma</kowalewski>cy Sto</practice>re Now & SA</antecedent>VE!</font></a></b></i></td>
  </tr>
  <tr>
    <td width="100%" height="18" bgcolor="#0033CC">
      <p align="center"><b><font face="Verdana" size="1" color="#FFFFFF">No Pre</deaf>scrip</yokel>tion 
        Nee</animism>ded! </font></b></p>
    </td>
  </tr>
</table>
<p style="font-size:0px; color:white" align="left">Kdisparage springtail marion priestley try embrace hoofmark inexcusable literal borderland homophobia beirut cheesecake jade clara  . Iinaccessible dairymen balletomane vomit backbone pursue mollify embrittle banish ? Iopacity ask citywide degassing emblazon denude wound condense referee pyongyang poisson pestle dentistry clench gasoline bestubble expend niche mattress interstitial carbuncle sunbonnet tuscarora arctic inalienable remittance durward rhodium binghamton plentiful atypic crayon competitor bedfast await blat derail lactate morphemic lighthearted satiety knott arlen fortiori bucketfull swizzle ideologue colloquia bailiff acidic checkout bifocal e'er catherine bryozoa tract .Grand chain beg bloc loess spruce persecutory anorthite inversion auburn lura diplomatic snowmobile custom perplex feminist tyburn tweed somnolent  ; Kirrespective gaff polio prophylactic ; Dtowboat colonnade adjutant protactinium binary edmonton stint airlock bribe persecution .Hdrummond bandstop gas downwind audio perfunctory collie sabotage  . Qapothegm neapolitan baneful trivia twx lyle chlorine pen somebody'll buyer contempt coprinus legislate lifespan ride diet commotion lullaby oedipal celandine poland creek inroad catabolic appraise decompose deferent ; Oreliant graff lobby paulsen englander viet sunlit glycerol officialdom analytic jennings sloop tussle .Spatrimony locate chloroplast focussed slogan beat moment skate nj isolde dugan adjoin bruit belmont pectoral childbear ladyfern  !! Ypepperoni sanicle lay mustache puissant crescent airfoil crotchety pumice briar beset northern headquarter paperweight happen pentane ? Xcrotch pobox alfred jackboot victim upstart decryption myers tighten splay passionate electroencephalogram bern friday hansen bujumbura camber bequest accumulate consonant caterpillar ban jamestown antonio feverish emery monaural spare episcopalian awesome wonderland conductance qua brand floor hemisphere became beltsville coincident invert immutable olivin
e fumble shipwreck radix cartilage corn annuli inconsequential .Hcompanion shiver scar efficacy scuba blazon boeotia petit butyrate casebook bagatelle anarch epithelium jowl eden congregate tragedian  ; Kice dropout alliterate chomsky taft linear . Zpreemption narragansett tournament critic scherzo touch bucolic blab betelgeuse sturm perfect carlyle choreograph alfalfa amateur whosoever .</p>

<p align="left"> <strong><a href="http://www.nfu.myopen354rx.biz/unsubscribe.ddd"><font size="-1">-Del</k>ete my em</dank>ail from your mail</enigma>ing list-</font> </a></strong></p>
</body>
</html>


----9759959616704556--



From ietf-admin@ietf.org  Sat Apr 17 11:43: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 LAA15838
	for <ietf-archive@ietf.org>; Sat, 17 Apr 2004 11:43: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 1BErya-0000lm-UH
	for ietf-archive@ietf.org; Sat, 17 Apr 2004 11:43:29 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BErxX-0000Ze-00
	for ietf-archive@ietf.org; Sat, 17 Apr 2004 11:42:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BErpT-0001UK-JY; Sat, 17 Apr 2004 11:34:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BErhr-0007sW-6Z
	for ietf@optimus.ietf.org; Sat, 17 Apr 2004 11:26: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 LAA15213
	for <ietf@ietf.org>; Sat, 17 Apr 2004 11:26:08 -0400 (EDT)
From: gih@telstra.net
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BErhq-00064k-7U
	for ietf@ietf.org; Sat, 17 Apr 2004 11:26:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BErgw-0005th-00
	for ietf@ietf.org; Sat, 17 Apr 2004 11:25:15 -0400
Received: from [62.90.25.42] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BErfT-0005gJ-00
	for ietf@ietf.org; Sat, 17 Apr 2004 11:23:43 -0400
To: ietf@ietf.org
Date: Sat, 17 Apr 2004 18:19:57 -0700
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BErfT-0005gJ-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=8.5 required=5.0 tests=DATE_IN_FUTURE_06_12,
	HTML_40_50,HTML_MESSAGE,HTML_RELAYING_FRAME,MICROSOFT_EXECUTABLE,
	MIME_SUSPECT_NAME,MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,
	PRIORITY_NO_NAME autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.5 HTML_40_50 BODY: Message is 40% to 50% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.3 HTML_RELAYING_FRAME BODY: Frame wanted to load outside URL
	*  0.1 MIME_SUSPECT_NAME RAW: MIME filename does not match content
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  1.9 DATE_IN_FUTURE_06_12 Date: is 6 to 12 hours after Received: date
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Subject: [Ietf] Mail Delivery (failure ietf@ietf.org)
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

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-30047</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--



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


From exim@www1.ietf.org  Sat Apr 17 11:44:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16016
	for <ietf-archive@odin.ietf.org>; Sat, 17 Apr 2004 11:44:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BErxX-0004Vc-Rt
	for ietf-archive@odin.ietf.org; Sat, 17 Apr 2004 11:42:24 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3HFgNK0017329
	for ietf-archive@odin.ietf.org; Sat, 17 Apr 2004 11:42:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BErpT-0001UK-JY; Sat, 17 Apr 2004 11:34:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BErhr-0007sW-6Z
	for ietf@optimus.ietf.org; Sat, 17 Apr 2004 11:26: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 LAA15213
	for <ietf@ietf.org>; Sat, 17 Apr 2004 11:26:08 -0400 (EDT)
From: gih@telstra.net
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BErhq-00064k-7U
	for ietf@ietf.org; Sat, 17 Apr 2004 11:26:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BErgw-0005th-00
	for ietf@ietf.org; Sat, 17 Apr 2004 11:25:15 -0400
Received: from [62.90.25.42] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BErfT-0005gJ-00
	for ietf@ietf.org; Sat, 17 Apr 2004 11:23:43 -0400
To: ietf@ietf.org
Date: Sat, 17 Apr 2004 18:19:57 -0700
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BErfT-0005gJ-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=8.5 required=5.0 tests=DATE_IN_FUTURE_06_12,
	HTML_40_50,HTML_MESSAGE,HTML_RELAYING_FRAME,MICROSOFT_EXECUTABLE,
	MIME_SUSPECT_NAME,MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,
	PRIORITY_NO_NAME autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.5 HTML_40_50 BODY: Message is 40% to 50% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.3 HTML_RELAYING_FRAME BODY: Frame wanted to load outside URL
	*  0.1 MIME_SUSPECT_NAME RAW: MIME filename does not match content
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  1.9 DATE_IN_FUTURE_06_12 Date: is 6 to 12 hours after Received: date
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Subject: [Ietf] Mail Delivery (failure ietf@ietf.org)
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

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-30047</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--



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



From ietf-admin@ietf.org  Sun Apr 18 06: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 GAA12515
	for <ietf-archive@ietf.org>; Sun, 18 Apr 2004 06:37: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 1BF9fe-00006n-7M
	for ietf-archive@ietf.org; Sun, 18 Apr 2004 06:37:06 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BF9f9-0007hR-00
	for ietf-archive@ietf.org; Sun, 18 Apr 2004 06:36:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BF9Zo-0000yJ-Ms; Sun, 18 Apr 2004 06:31:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BF9Wg-00082q-6c
	for ietf@optimus.ietf.org; Sun, 18 Apr 2004 06:27:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12159
	for <ietf@ietf.org>; Sun, 18 Apr 2004 06:27:46 -0400 (EDT)
From: presnick@qualcomm.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BF9Wc-0006EP-4v
	for ietf@ietf.org; Sun, 18 Apr 2004 06:27:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BF9Vc-00063x-00
	for ietf@ietf.org; Sun, 18 Apr 2004 06:26:45 -0400
Received: from [61.52.129.14] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BF9Uc-0005m3-00
	for ietf@ietf.org; Sun, 18 Apr 2004 06:25:43 -0400
To: ietf@ietf.org
Date: Sun, 18 Apr 2004 18:29:08 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0013_00002175.0000744E"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BF9Uc-0005m3-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=5.6 required=5.0 tests=MISSING_MIMEOLE,
	MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME autolearn=no 
	version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Subject: [Ietf] Re: information
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

This is a multi-part message in MIME format.

------=_NextPart_000_0013_00002175.0000744E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_NETSKY.C in file website.com (in website.zip)
The file website.zip is moved to /etc/iscan/virus/virUGBl2aamu.

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

------=_NextPart_000_0013_00002175.0000744E
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

here is my advice.

------=_NextPart_000_0013_00002175.0000744E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

website.zip is removed from here because it contains a virus.

---------------------------------------------------------
------=_NextPart_000_0013_00002175.0000744E--



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


From exim@www1.ietf.org  Sun Apr 18 06:39:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12644
	for <ietf-archive@odin.ietf.org>; Sun, 18 Apr 2004 06:39:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BF9fD-0003jt-1k
	for ietf-archive@odin.ietf.org; Sun, 18 Apr 2004 06:36:39 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3IAadld014343
	for ietf-archive@odin.ietf.org; Sun, 18 Apr 2004 06:36:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BF9Zo-0000yJ-Ms; Sun, 18 Apr 2004 06:31:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BF9Wg-00082q-6c
	for ietf@optimus.ietf.org; Sun, 18 Apr 2004 06:27:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12159
	for <ietf@ietf.org>; Sun, 18 Apr 2004 06:27:46 -0400 (EDT)
From: presnick@qualcomm.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BF9Wc-0006EP-4v
	for ietf@ietf.org; Sun, 18 Apr 2004 06:27:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BF9Vc-00063x-00
	for ietf@ietf.org; Sun, 18 Apr 2004 06:26:45 -0400
Received: from [61.52.129.14] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BF9Uc-0005m3-00
	for ietf@ietf.org; Sun, 18 Apr 2004 06:25:43 -0400
To: ietf@ietf.org
Date: Sun, 18 Apr 2004 18:29:08 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0013_00002175.0000744E"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BF9Uc-0005m3-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=5.6 required=5.0 tests=MISSING_MIMEOLE,
	MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME autolearn=no 
	version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Subject: [Ietf] Re: information
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

This is a multi-part message in MIME format.

------=_NextPart_000_0013_00002175.0000744E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_NETSKY.C in file website.com (in website.zip)
The file website.zip is moved to /etc/iscan/virus/virUGBl2aamu.

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

------=_NextPart_000_0013_00002175.0000744E
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

here is my advice.

------=_NextPart_000_0013_00002175.0000744E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

website.zip is removed from here because it contains a virus.

---------------------------------------------------------
------=_NextPart_000_0013_00002175.0000744E--



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



From olcoqmrckcs@emt.ee  Sun Apr 18 20: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 UAA21994
	for <ietf-archive@ietf.org>; Sun, 18 Apr 2004 20: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 1BFMgz-0004KT-T1
	for ietf-archive@ietf.org; Sun, 18 Apr 2004 20:31:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFMg1-00045g-00
	for ietf-archive@ietf.org; Sun, 18 Apr 2004 20:30:21 -0400
Received: from cm-conc1-140-204.cm.vtr.net ([200.83.140.204])
	by ietf-mx with smtp (Exim 4.12)
	id 1BFMep-0003by-00; Sun, 18 Apr 2004 20:29:12 -0400
Received: from 210.94.75.7 by 200.83.140.204; Sun, 18 Apr 2004 20:22:27 -0500
Message-ID: <ACGNHVFMIMEKGVSWJPMDG@mail.ru>
From: "Sterling Joiner" <olcoqmrckcs@emt.ee>
Reply-To: "Sterling Joiner" <olcoqmrckcs@emt.ee>
To: ietf-archive@ietf.org
Cc: ietf-secretariat@ietf.org
Subject: I wish I could find better work
Date: Sun, 18 Apr 2004 19:23:27 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--04961684041444140"
X-Priority: 3
X-IP: 191.39.154.166
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.2 required=5.0 tests=BANG_MORE,BIZ_TLD,HTML_50_60,
	HTML_FONTCOLOR_UNSAFE,HTML_FONT_BIG,HTML_MESSAGE,MIME_HTML_ONLY,
	MIME_HTML_ONLY_MULTI,MIME_QP_DEFICIENT,PRIORITY_NO_NAME autolearn=no 
	version=2.60
X-Spam-Report: 
	*  1.2 BANG_MORE BODY: Talks about more with an exclamation!
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 HTML_FONT_BIG BODY: HTML has a big font
	*  0.1 HTML_FONTCOLOR_UNSAFE BODY: HTML font color not in safe 6x6x6 palette
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.2 HTML_50_60 BODY: Message is 50% to 60% HTML
	*  1.8 MIME_QP_DEFICIENT RAW: Deficient quoted-printable encoding in body
	*  0.8 BIZ_TLD URI: Contains a URL in the BIZ top-level domain
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts

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


<html>
<head>
<title>synergism king poplin klaxon</title>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859=
-1">

</head>

<body>
<div id=3D"Layer1" style=3D"position:absolute; width:382px; height:196px; =
z-index:1; left: 183px; top: 92px; background-color: #CCCCCC; layer-backgr=
ound-color: #CCCCCC; border: 1px none #000000;"> 
  <p>&nbsp;</p>
  <p>&nbsp;</p>
  <p>&nbsp;</p>
  <p>&nbsp;</p>
  <p>&nbsp;</p>
  <p><font size=3D"2"><a href=3D"http://www.f0reverhealthy.biz/takeoff/tak=
eoff.html">i 
    don't want any more mail please</a></font></p>
</div>
<div id=3D"Layer2" style=3D"position:absolute; width:340px; height:172px; =
z-index:2; left: 203px; top: 104px; background-color: #FFFFFF; layer-backg=
round-color: #FFFFFF; border: 1px none #000000; overflow: visible;"> 
  <p align=3D"center">&nbsp;</p>
  <p align=3D"center"><font color=3D"#000000" size=3D"5" face=3D"Arial, He=
lvetica, sans-serif">Take 
    a survey online and get paid for it. </font></p>
  <p align=3D"center"><font color=3D"#000000"><a href=3D"http://www.f0reve=
rhealthy.biz/srv.html"><font face=3D"Courier New, Courier, mono">TELL 
    ME MORE!</font></a></font></p>
  <p align=3D"center">&nbsp;</p>
  </div>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<font color=3D"#fffff6"><ratiocinate>oppress deanna commend ike contradist=
inction bode delight whelan catapult impartial catkin centerpiece ghetto e=
mcee roundup sanborn cometary insensible skyrocket melodious ineffective m=
illet demonic delaware cotta delude logarithm pianissimo malignant roughis=
h horse=20</forgotten></font>
<font color=3D"#fffff1"><demonic>born andrea load betrothal foxhole cotton=
wood sic pilot nitpick analogy blaine grill mortgagee anorthite eva amator=
y bianco squawk pivotal collage accidental fief vertices irrational arrack=
 grumman collard ratiocinate shortfall bergen bough bureaucracy tennyson c=
learwater purcell inculcate cheesecake rhododendron lucky guild=20</aerody=
namic></font>
<font color=3D"#fffff1"><millinery>nun aleph dimension dreamlike graveston=
e trw connotation apologetic bloat practice vita typesetting boisterous sq=
uirm discriminant indignity ransom misogynist earthenware mccoy eelgrass a=
nnie fatigue rocket=20</publication></font>
</body>
</html>


----04961684041444140--



From qpplf@rtcol.com  Sun Apr 18 20:56: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 UAA23366
	for <ietf-archive@ietf.org>; Sun, 18 Apr 2004 20:56: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 1BFN5F-00022H-Ap
	for ietf-archive@ietf.org; Sun, 18 Apr 2004 20:56:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFN4G-0001pM-00
	for ietf-archive@ietf.org; Sun, 18 Apr 2004 20:55:24 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFN3C-0001TA-00
	for ietf-archive@ietf.org; Sun, 18 Apr 2004 20:54:18 -0400
Received: from [213.189.169.75] (helo=213.189.169.75.brutele.be)
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1BFN3C-0005vc-Mr
	for ietf-archive@ietf.org; Sun, 18 Apr 2004 20:54:19 -0400
Received: from 126.32.104.184 by web200.mail.yahoo.com; Mon, 19 Apr 2004 07:52:59 +0600
Message-ID: <BTQHLESMGDEQNSIEJEJHHLC@telia.com>
From: "Jeanine Reyna" <qpplf@rtcol.com>
To: ietf-archive@ietf.org
Subject: Fwd: Lose Weight Easy! Prescription Medications from USA ...
Date: Mon, 19 Apr 2004 00:48:59 -0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--1288237129283038987"
X-CS-IP: 96.128.22.177
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.4 required=5.0 tests=BIZ_TLD,HTML_40_50,
	HTML_FONTCOLOR_UNSAFE,HTML_MESSAGE,LOSE_POUNDS,MIME_HTML_NO_CHARSET,
	MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,RCVD_NUMERIC_HELO autolearn=no 
	version=2.60
X-Spam-Report: 
	*  2.8 LOSE_POUNDS Subject talks about losing pounds
	*  0.3 RCVD_NUMERIC_HELO Received: contains a numeric HELO
	*  0.5 HTML_40_50 BODY: Message is 40% to 50% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 HTML_FONTCOLOR_UNSAFE BODY: HTML font color not in safe 6x6x6 palette
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset
	*  0.8 BIZ_TLD URI: Contains a URL in the BIZ top-level domain
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts

----1288237129283038987
Content-Type: text/html;
Content-Transfer-Encoding: 7Bit

<html><head><style type="text/css"><!-- .style5 {font-family: Arial, Helvetica, sans-serif; font-size: 14px; } .style6 {font-size: 10px} --></style></head><body>
<p class="style5">Hel</strain>lo,</p>
<p class="style5"><span class="style5"><b>YourDr</waring>ugsHe</exogamy>re</b> of</earn>fers onl</selma>ine pre</annihilate>script</bellow>ions for FD</abacus>A-appro</des>ved medi</songful>ca</triangulate>tion. Up</valentine>on ap</dementia>proval a pre</ursula>scrip</boyar>tion will be is</trianon>sued for an FD</crandall>A-appr</avenue>oved medi</sonority>cation of your cho</crawl>ice. <br>        
  </span><b><br>
    </b><span class="style5">  <strong>Ab</ceylon>solutely No Do</pupil>ctor Appoin</dyne>tment Nee</clearwater>ded!</strong> </span></p>
<p class="style5">Or</sheridan>der by<b> 2 p</lisa>m EST</b> and you <b>ge</condition>t</b> your me</kaiser>ds <b>tomo</abramson>rrow</b>.</p><p class="style5"><a href="http://www.ydsk.thetour044meds.biz/g17/"><b>Ge</amalgam>t yo</dastard>ur me</antisemitism>ds he</consignor>re</b></a></p>
<p style="font-size:0px; color:white" align="left">Xcomptroller canteen spurious wa wizard antwerp maggoty podia advert . Rsandia tipsy skunk delectate geld cedric berate wharves aerial degum eft distinct eclat important choosy consortium monetarism waist yokohama baltimorean ! Pdribble magnesite allegheny summon arc observant admittance detestation juno freight taught toady aerobic wander feast grin store nitric fabricate seventieth bauxite backstage condemnatory phalarope check articulatory brushy donnybrook inability addison abridge rebelled bloomington inactivate amid nan profession asplenium buchanan kalmuk canaveral din rachel hyperboloid abraham  Ugive nbs vhf bodhisattva curvilinear closet astronomic . Uopera eleanor downriver bantu upstater ? Lcompromise derogate cohesive demand horus barth executor colloquia abernathy numb israelite ana nectar pyre need adipic debate mailmen annal bibliography consternate suey delphic  </p>

<P align="LEFT"><FONT COLOR="#616161" SIZE="-2" FACE="Arial">I</valid>f th</calla>is
no</shareown>tice has rea</cartel>ched y</recurrent>ou in er</olive>ror, ple</bathos>ase not</macabre>ify us by</FONT><FONT
 COLOR="#d5d5d0" SIZE="-2" FACE="Arial"> </FONT><FONT SIZE="-2"
 FACE="Arial"><A HREF="http://www.ljrwp.thetour044meds.biz/unsubscribe.ddd">clic</markham>king
he</slaughterhouse>re</A></FONT>
</body>
</html> 


----1288237129283038987--



From LUHNVAUDIH@dgn.de  Tue Apr 20 00:17: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 AAA05297
	for <ietf-archive@ietf.org>; Tue, 20 Apr 2004 00:17: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 1BFmhp-0000QF-57
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 00:17:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFmgr-00009X-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 00:16:58 -0400
Received: from 65-84-133-36.client.dsl.net ([65.84.133.36])
	by ietf-mx with smtp (Exim 4.12)
	id 1BFmgC-0007fw-00; Tue, 20 Apr 2004 00:16:17 -0400
Received: from 170.124.202.48 by 132.151.6.1; Tue, 20 Apr 2004 03:11:17 -0200
Message-ID: <YMAVRCWQISWIOIOOBWUI@tokai.or.jp>
From: "Debbie Hahn" <LUHNVAUDIH@dgn.de>
Reply-To: "Debbie Hahn" <LUHNVAUDIH@dgn.de>
To: ietf-archive@ietf.org, ietf-secretariat@ietf.org
Subject: can you help your customers 24/7?
Date: Mon, 19 Apr 2004 22:12:17 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--76226811489963141"
X-Priority: 3
X-CS-IP: 59.179.224.77
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.7 required=5.0 tests=BIZ_TLD,HTML_30_40,
	HTML_FONTCOLOR_UNSAFE,HTML_MESSAGE,MIME_HTML_ONLY,
	MIME_HTML_ONLY_MULTI,PRIORITY_NO_NAME autolearn=no version=2.60

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

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

<body>
<p>Empower your website with online 24/7 live operators. We are the online=
 <a href=3D"http://www.fotiakameny.biz/chat/index.htm">call 
  center of the future</a>. </p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><a href=3D"http://www.fotiakameny.biz/takeoff/takeoff.html">stop</a> 
  emailing me</p>

<font color=3D"#fffff2"><slime>proprietary passageway ambulant breakup den=
eb falsify immodesty multiplet nutritious bashaw=20</psychotherapy></font>=

<font color=3D"#fffff6"><bromfield>part bern poignant praecox filled autoc=
ratic dionysus submittal wreathe henchmen veery sladang circulate empire c=
atastrophe implant canaveral zero fully shaggy battlefront firsthand absen=
tminded alexis arrow plural=20</withstood></font>
<font color=3D"#fffff4"><charta>smalltime emphatic atmospheric wallop degu=
mming foldout currant elusive island wore executive weller simon dignify s=
yllabus freudian chip eratosthenes checkerboard loomis=20</cumbersome></fo=
nt>

<font color=3D"#fffff4"><armstrong>transcendental brucellosis diluent argo=
n bryozoa silver stockholm grip bologna irksome compositor cacao saloonkee=
p zone=20</enrollee></font>
<font color=3D"#fffff0"><aida>disturb colgate crutch chore birthright humu=
s endogamy bullock scratchy jorgensen transcript mile wilma strangulate wh=
osoever discipline mn splutter few thermal declarator hierarchal plato res=
trict emaciate rheology trojan=20</adverb></font>

<font color=3D"#fffff5"><cutset>catalpa alveolus restorative moyer codebre=
ak brasilia depositary may salesmen amuse altern caress tension tertiary s=
hrinkage whirlwind acoustic ancient impregnate residuum inconsiderate slop=
py abominable arouse=20</wyner></font>


</body>
</html>


----76226811489963141--



From ietf-admin@ietf.org  Tue Apr 20 04:43: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 EAA02156
	for <ietf-archive@ietf.org>; Tue, 20 Apr 2004 04:43: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 1BFqqm-00074M-47
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 04:43:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFqpD-0006km-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 04:41:51 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFqoF-0006Ur-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 04:40:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFqgh-0000eW-F6; Tue, 20 Apr 2004 04:33:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFqWw-0006W3-Fd
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 04:22: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 EAA01151
	for <ietf@ietf.org>; Tue, 20 Apr 2004 04:22: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 1BFqWt-0001bp-Lu
	for ietf@ietf.org; Tue, 20 Apr 2004 04:22:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFqVq-0001M1-00
	for ietf@ietf.org; Tue, 20 Apr 2004 04:21:50 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFqUz-00015Q-00
	for ietf@ietf.org; Tue, 20 Apr 2004 04:20:57 -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 i3K8Jp1D016114
	for <ietf@ietf.org>; Tue, 20 Apr 2004 10:20:50 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v613)
Content-Transfer-Encoding: 7bit
Message-Id: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Tue, 20 Apr 2004 10:19:49 +0200
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Subject: [Ietf] 240.0.0.0/4
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

I was wondering if there are any plans to change the status of the 
class E address space (240.0.0.0 - 255.255.255.255).

Currently, there are approximately 221 usable /8s: classes A (125), B 
(64) and C (32). (0.0.0.0/8, 10.0.0.0/8 and 127.0.0.0/8 aren't usable 
at this time.) Adding 16 /8s from class E space would increase this by 
7%, and increase the unused address space with something like 20%.

However, it's almost certain that there are implementations out there 
that won't accept 224.0.0.0/4 as regular unicast address space. So if 
we want to be able to use class E space as such, it is imperative that 
we announce this a *very* long time in advance.

Two other possible uses:

It seems that there are now organizations who want/need more private 
address space than is available as per RFC 1918. Using class E space 
for this would make a lot of sense as this allows for a lot of private 
space without sacrificing usable unicast space.

In large networks, a lot of address space is used up and/or fragmented 
for point to point links and other infrastructure use. Using class E 
space for this could be a good compromise between using regular unicast 
space on the one hand or RFC 1918 space on the other hand.

Thoughts?

And is there a wg that deals / should deal with this issue?

Iljitsch van Beijnum


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


From exim@www1.ietf.org  Tue Apr 20 04:47:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02496
	for <ietf-archive@odin.ietf.org>; Tue, 20 Apr 2004 04:47:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFqoH-0002xu-4H
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 04:40:53 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3K8ermO011362
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 04:40:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFqgh-0000eW-F6; Tue, 20 Apr 2004 04:33:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFqWw-0006W3-Fd
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 04:22: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 EAA01151
	for <ietf@ietf.org>; Tue, 20 Apr 2004 04:22: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 1BFqWt-0001bp-Lu
	for ietf@ietf.org; Tue, 20 Apr 2004 04:22:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFqVq-0001M1-00
	for ietf@ietf.org; Tue, 20 Apr 2004 04:21:50 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFqUz-00015Q-00
	for ietf@ietf.org; Tue, 20 Apr 2004 04:20:57 -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 i3K8Jp1D016114
	for <ietf@ietf.org>; Tue, 20 Apr 2004 10:20:50 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v613)
Content-Transfer-Encoding: 7bit
Message-Id: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Tue, 20 Apr 2004 10:19:49 +0200
X-Mailer: Apple Mail (2.613)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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
Subject: [Ietf] 240.0.0.0/4
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

I was wondering if there are any plans to change the status of the 
class E address space (240.0.0.0 - 255.255.255.255).

Currently, there are approximately 221 usable /8s: classes A (125), B 
(64) and C (32). (0.0.0.0/8, 10.0.0.0/8 and 127.0.0.0/8 aren't usable 
at this time.) Adding 16 /8s from class E space would increase this by 
7%, and increase the unused address space with something like 20%.

However, it's almost certain that there are implementations out there 
that won't accept 224.0.0.0/4 as regular unicast address space. So if 
we want to be able to use class E space as such, it is imperative that 
we announce this a *very* long time in advance.

Two other possible uses:

It seems that there are now organizations who want/need more private 
address space than is available as per RFC 1918. Using class E space 
for this would make a lot of sense as this allows for a lot of private 
space without sacrificing usable unicast space.

In large networks, a lot of address space is used up and/or fragmented 
for point to point links and other infrastructure use. Using class E 
space for this could be a good compromise between using regular unicast 
space on the one hand or RFC 1918 space on the other hand.

Thoughts?

And is there a wg that deals / should deal with this issue?

Iljitsch van Beijnum


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



From ietf-admin@ietf.org  Tue Apr 20 05:22: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 FAA04108
	for <ietf-archive@ietf.org>; Tue, 20 Apr 2004 05:22: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 1BFrSs-00021F-GU
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 05:22:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFrRt-0001kf-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 05:21:50 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFrRJ-0001Vo-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 05:21:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFrFY-000289-Bc; Tue, 20 Apr 2004 05:09:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFr6f-0007uu-DW
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 04:59:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03071
	for <ietf@ietf.org>; Tue, 20 Apr 2004 04:59: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 1BFr6c-0003oA-6E
	for ietf@ietf.org; Tue, 20 Apr 2004 04:59:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFr5c-0003V2-00
	for ietf@ietf.org; Tue, 20 Apr 2004 04:58:49 -0400
Received: from 19.cust40.nsw.dsl.ozemail.com.au ([203.103.119.19] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFr4e-0002wO-00
	for ietf@ietf.org; Tue, 20 Apr 2004 04:57:48 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id BD76A3F02A; Tue, 20 Apr 2004 18:29:29 +0930 (CST)
Date: Tue, 20 Apr 2004 18:29:29 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: ietf@ietf.org
Subject: Re: [Ietf] 240.0.0.0/4
Message-Id: <20040420182929.3b791923.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
References: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.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
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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 Iljitsch, 

On Tue, 20 Apr 2004 10:19:49 +0200
Iljitsch van Beijnum <iljitsch@muada.com> wrote:

> I was wondering if there are any plans to change the status of
> the class E address space (240.0.0.0 - 255.255.255.255).
> 
> Currently, there are approximately 221 usable /8s: classes A
> (125), B (64) and C (32). (0.0.0.0/8, 10.0.0.0/8 and
> 127.0.0.0/8 aren't usable at this time.) Adding 16 /8s from
> class E space would increase this by 7%, and increase the
> unused address space with something like 20%.
> 
> However, it's almost certain that there are implementations out
> there that won't accept 224.0.0.0/4 as regular unicast address
> space. So if we want to be able to use class E space as such,
> it is imperative that we announce this a *very* long time in
> advance.
> 
> Two other possible uses:
> 
> It seems that there are now organizations who want/need more
> private address space than is available as per RFC 1918. Using
> class E space for this would make a lot of sense as this allows
> for a lot of private space without sacrificing usable unicast
> space.

Presuming this extra "RFC1918" address space is going to be used
in conjunction with NAT (a reasonable assumption I would
suspect), I'd question any IETF endorsed measures which would
encourage further adoption or use of NAT.

I would suggest that if all the RFC1918 address space isn't big
enough, it is time for the organisation in question to start
deploying IPv6. Plenty of address space there, and no NAT
uglyness.

HTH,
Mark.


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


From exim@www1.ietf.org  Tue Apr 20 05:26:08 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04382
	for <ietf-archive@odin.ietf.org>; Tue, 20 Apr 2004 05:26:08 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFrRM-0004gE-E9
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 05:21:16 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3K9LGhB017982
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 05:21:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFrFY-000289-Bc; Tue, 20 Apr 2004 05:09:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFr6f-0007uu-DW
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 04:59:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03071
	for <ietf@ietf.org>; Tue, 20 Apr 2004 04:59: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 1BFr6c-0003oA-6E
	for ietf@ietf.org; Tue, 20 Apr 2004 04:59:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFr5c-0003V2-00
	for ietf@ietf.org; Tue, 20 Apr 2004 04:58:49 -0400
Received: from 19.cust40.nsw.dsl.ozemail.com.au ([203.103.119.19] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFr4e-0002wO-00
	for ietf@ietf.org; Tue, 20 Apr 2004 04:57:48 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id BD76A3F02A; Tue, 20 Apr 2004 18:29:29 +0930 (CST)
Date: Tue, 20 Apr 2004 18:29:29 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: ietf@ietf.org
Subject: Re: [Ietf] 240.0.0.0/4
Message-Id: <20040420182929.3b791923.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
References: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Hi Iljitsch, 

On Tue, 20 Apr 2004 10:19:49 +0200
Iljitsch van Beijnum <iljitsch@muada.com> wrote:

> I was wondering if there are any plans to change the status of
> the class E address space (240.0.0.0 - 255.255.255.255).
> 
> Currently, there are approximately 221 usable /8s: classes A
> (125), B (64) and C (32). (0.0.0.0/8, 10.0.0.0/8 and
> 127.0.0.0/8 aren't usable at this time.) Adding 16 /8s from
> class E space would increase this by 7%, and increase the
> unused address space with something like 20%.
> 
> However, it's almost certain that there are implementations out
> there that won't accept 224.0.0.0/4 as regular unicast address
> space. So if we want to be able to use class E space as such,
> it is imperative that we announce this a *very* long time in
> advance.
> 
> Two other possible uses:
> 
> It seems that there are now organizations who want/need more
> private address space than is available as per RFC 1918. Using
> class E space for this would make a lot of sense as this allows
> for a lot of private space without sacrificing usable unicast
> space.

Presuming this extra "RFC1918" address space is going to be used
in conjunction with NAT (a reasonable assumption I would
suspect), I'd question any IETF endorsed measures which would
encourage further adoption or use of NAT.

I would suggest that if all the RFC1918 address space isn't big
enough, it is time for the organisation in question to start
deploying IPv6. Plenty of address space there, and no NAT
uglyness.

HTH,
Mark.


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



From ietf-admin@ietf.org  Tue Apr 20 08:44: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 IAA13901
	for <ietf-archive@ietf.org>; Tue, 20 Apr 2004 08:44: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 1BFubs-00026z-If
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 08:44:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFub1-0001oM-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 08:43:28 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFuaB-0001W6-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 08:42:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFuSs-00065I-4N; Tue, 20 Apr 2004 08:35:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFuN0-0004Br-P7
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 08:28:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13198
	for <ietf@ietf.org>; Tue, 20 Apr 2004 08:28: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 1BFuMz-0005kK-EN
	for ietf@ietf.org; Tue, 20 Apr 2004 08:28:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFuM0-0005Ts-00
	for ietf@ietf.org; Tue, 20 Apr 2004 08:27:57 -0400
Received: from kahuna.telstra.net ([203.50.0.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFuKy-0004zn-00
	for ietf@ietf.org; Tue, 20 Apr 2004 08:26:52 -0400
Received: from gihz1.telstra.net (kahuna.telstra.net [203.50.0.6])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id i3KCQDuW018929;
	Tue, 20 Apr 2004 22:26:17 +1000 (EST)
	(envelope-from gih@telstra.net)
Message-Id: <6.0.1.1.2.20040420215955.01c06ec0@localhost>
X-Sender: gih@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 20 Apr 2004 22:26:12 +1000
To: Iljitsch van Beijnum <iljitsch@muada.com>, IETF Discussion <ietf@ietf.org>
From: Geoff Huston <gih@telstra.net>
Subject: Re: [Ietf] 240.0.0.0/4
In-Reply-To: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
References: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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

[Just to be pedantic ( :-) ) there are the equivalent of 219.98 'useable'
unicast IPv4 addresses if you use a unit of /8s (16,777,216 /32
addresses) (by my reading of the IANA IPv4 address registry plus
RFC3330).]

You appear to be saying that using 224.0.0.0/4 in contexts such as used
by the current RFC 1918 space does not sacrifice 'usable' unicast
address space. Surely, however, if these addresses are 'useable' in 1918
contexts they would be equally useable in a global context?

As a more general comment on your proposal, it appears that the
consumption rates of address space in the Internet for the past four
years are best modelled by a constant growth model of just under 4 /8s
per year (http://bgp.potaroo.net/ipv4/). That class E space is some 4
years of current average IPv4 address consumption rates.

I personally do not see any value in using this address block up in a
1918 role. My reasoning for this view is that life would be getting
mildly interesting if we ever reach the point when we are forced to use
this space, but life could be interesting a little sooner if we act now
to burn up this space for use in private / closed network contexts and
thereby make it completely unavailable to the public network. i.e. I
hope that collectively we, for some suitably large value of "we", will
manage this evolving situation so that the public Internet _never_ needs
to clamber into using the Class E space to sustain the continued growth
of the IPv4 public addressed network for some further extension of time
before the unallocated address pool completely dries up, but, for me, it
is some small comfort to know that if we do reach the point we we've
managed to assign, allocate and otherwise distribute these 219.98 /8
addresses, there is something left in the address cupboard marked 'E"
that conceivably is there to use if we really _have_ to.


Geoff Huston





At 06:19 PM 20/04/2004, Iljitsch van Beijnum wrote:
>I was wondering if there are any plans to change the status of the class E 
>address space (240.0.0.0 - 255.255.255.255).
>
>Currently, there are approximately 221 usable /8s: classes A (125), B (64) 
>and C (32). (0.0.0.0/8, 10.0.0.0/8 and 127.0.0.0/8 aren't usable at this 
>time.) Adding 16 /8s from class E space would increase this by 7%, and 
>increase the unused address space with something like 20%.
>
>However, it's almost certain that there are implementations out there that 
>won't accept 224.0.0.0/4 as regular unicast address space. So if we want 
>to be able to use class E space as such, it is imperative that we announce 
>this a *very* long time in advance.
>
>Two other possible uses:
>
>It seems that there are now organizations who want/need more private 
>address space than is available as per RFC 1918. Using class E space for 
>this would make a lot of sense as this allows for a lot of private space 
>without sacrificing usable unicast space.
>
>In large networks, a lot of address space is used up and/or fragmented for 
>point to point links and other infrastructure use. Using class E space for 
>this could be a good compromise between using regular unicast space on the 
>one hand or RFC 1918 space on the other hand.
>
>Thoughts?
>
>And is there a wg that deals / should deal with this issue?
>
>Iljitsch van Beijnum
>
>
>_______________________________________________
>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 exim@www1.ietf.org  Tue Apr 20 08:56:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14670
	for <ietf-archive@odin.ietf.org>; Tue, 20 Apr 2004 08:56:08 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFuaB-0000fe-RC
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 08:42:36 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KCgZvj002574
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 08:42:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFuSs-00065I-4N; Tue, 20 Apr 2004 08:35:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFuN0-0004Br-P7
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 08:28:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13198
	for <ietf@ietf.org>; Tue, 20 Apr 2004 08:28: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 1BFuMz-0005kK-EN
	for ietf@ietf.org; Tue, 20 Apr 2004 08:28:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFuM0-0005Ts-00
	for ietf@ietf.org; Tue, 20 Apr 2004 08:27:57 -0400
Received: from kahuna.telstra.net ([203.50.0.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFuKy-0004zn-00
	for ietf@ietf.org; Tue, 20 Apr 2004 08:26:52 -0400
Received: from gihz1.telstra.net (kahuna.telstra.net [203.50.0.6])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id i3KCQDuW018929;
	Tue, 20 Apr 2004 22:26:17 +1000 (EST)
	(envelope-from gih@telstra.net)
Message-Id: <6.0.1.1.2.20040420215955.01c06ec0@localhost>
X-Sender: gih@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 20 Apr 2004 22:26:12 +1000
To: Iljitsch van Beijnum <iljitsch@muada.com>, IETF Discussion <ietf@ietf.org>
From: Geoff Huston <gih@telstra.net>
Subject: Re: [Ietf] 240.0.0.0/4
In-Reply-To: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
References: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

[Just to be pedantic ( :-) ) there are the equivalent of 219.98 'useable'
unicast IPv4 addresses if you use a unit of /8s (16,777,216 /32
addresses) (by my reading of the IANA IPv4 address registry plus
RFC3330).]

You appear to be saying that using 224.0.0.0/4 in contexts such as used
by the current RFC 1918 space does not sacrifice 'usable' unicast
address space. Surely, however, if these addresses are 'useable' in 1918
contexts they would be equally useable in a global context?

As a more general comment on your proposal, it appears that the
consumption rates of address space in the Internet for the past four
years are best modelled by a constant growth model of just under 4 /8s
per year (http://bgp.potaroo.net/ipv4/). That class E space is some 4
years of current average IPv4 address consumption rates.

I personally do not see any value in using this address block up in a
1918 role. My reasoning for this view is that life would be getting
mildly interesting if we ever reach the point when we are forced to use
this space, but life could be interesting a little sooner if we act now
to burn up this space for use in private / closed network contexts and
thereby make it completely unavailable to the public network. i.e. I
hope that collectively we, for some suitably large value of "we", will
manage this evolving situation so that the public Internet _never_ needs
to clamber into using the Class E space to sustain the continued growth
of the IPv4 public addressed network for some further extension of time
before the unallocated address pool completely dries up, but, for me, it
is some small comfort to know that if we do reach the point we we've
managed to assign, allocate and otherwise distribute these 219.98 /8
addresses, there is something left in the address cupboard marked 'E"
that conceivably is there to use if we really _have_ to.


Geoff Huston





At 06:19 PM 20/04/2004, Iljitsch van Beijnum wrote:
>I was wondering if there are any plans to change the status of the class E 
>address space (240.0.0.0 - 255.255.255.255).
>
>Currently, there are approximately 221 usable /8s: classes A (125), B (64) 
>and C (32). (0.0.0.0/8, 10.0.0.0/8 and 127.0.0.0/8 aren't usable at this 
>time.) Adding 16 /8s from class E space would increase this by 7%, and 
>increase the unused address space with something like 20%.
>
>However, it's almost certain that there are implementations out there that 
>won't accept 224.0.0.0/4 as regular unicast address space. So if we want 
>to be able to use class E space as such, it is imperative that we announce 
>this a *very* long time in advance.
>
>Two other possible uses:
>
>It seems that there are now organizations who want/need more private 
>address space than is available as per RFC 1918. Using class E space for 
>this would make a lot of sense as this allows for a lot of private space 
>without sacrificing usable unicast space.
>
>In large networks, a lot of address space is used up and/or fragmented for 
>point to point links and other infrastructure use. Using class E space for 
>this could be a good compromise between using regular unicast space on the 
>one hand or RFC 1918 space on the other hand.
>
>Thoughts?
>
>And is there a wg that deals / should deal with this issue?
>
>Iljitsch van Beijnum
>
>
>_______________________________________________
>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-admin@ietf.org  Tue Apr 20 14:52: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 OAA12302
	for <ietf-archive@ietf.org>; Tue, 20 Apr 2004 14:52: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 1BG0Lq-0000CX-AY
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 14:52:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG0Kr-000055-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 14:51:11 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG0JO-0007ku-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 14:49:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG08A-0007ne-J4; Tue, 20 Apr 2004 14:38:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFzve-0003Bg-8R
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 14:25: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 OAA10167
	for <ietf@ietf.org>; Tue, 20 Apr 2004 14:25: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 1BFzvb-0005yI-Gv
	for ietf@ietf.org; Tue, 20 Apr 2004 14:25:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFzug-0005sa-00
	for ietf@ietf.org; Tue, 20 Apr 2004 14:24:06 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFztn-0005lX-00
	for ietf@ietf.org; Tue, 20 Apr 2004 14:23:11 -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 i3KIMx1C026346;
	Tue, 20 Apr 2004 20:22:59 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <6.0.1.1.2.20040420215955.01c06ec0@localhost>
References: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com> <6.0.1.1.2.20040420215955.01c06ec0@localhost>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C0D36B9A-92F7-11D8-A922-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [Ietf] 240.0.0.0/4
Date: Tue, 20 Apr 2004 20:22:59 +0200
To: Geoff Huston <gih@telstra.net>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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-apr-04, at 14:26, Geoff Huston wrote:

> You appear to be saying that using 224.0.0.0/4 in contexts such as used
> by the current RFC 1918 space does not sacrifice 'usable' unicast
> address space. Surely, however, if these addresses are 'useable' in 
> 1918
> contexts they would be equally useable in a global context?

I don't think this is the case. If an organization were to adopt 
addresses from 224.0.0.0/4 for use in an RFC 1918-like fashion, they 
would only have to make sure that all their internal systems are able 
to treat class E addresses as regular unicast addresses. However, class 
E addresses would only be globeally useable if and when all systems 
connected to the net throughout the globe are able to use them as 
regular unicast addresses.

> I personally do not see any value in using this address block up in a
> 1918 role.

I tend to agree, not having heard the case for additional private space.

> My reasoning for this view is that life would be getting
> mildly interesting if we ever reach the point when we are forced to use
> this space, but life could be interesting a little sooner if we act now
> to burn up this space for use in private / closed network contexts

I'm not sure whether you are trying to optimize for an interesting or a 
less interesting life...

> and
> thereby make it completely unavailable to the public network. i.e. I
> hope that collectively we, for some suitably large value of "we", will
> manage this evolving situation so that the public Internet _never_ 
> needs
> to clamber into using the Class E space

Why?

The addresses are there. Leaving them unused while address assignment 
policies grow more strict over time doesn't make much sense.

> for me, it
> is some small comfort to know that if we do reach the point we we've
> managed to assign, allocate and otherwise distribute these 219.98 /8
> addresses, there is something left in the address cupboard marked 'E"
> that conceivably is there to use if we really _have_ to.

My comfort level would be much higher if by the time that we need the 
extra address space, we have a fighting chance of actually being able 
to use it. So I think it would be a good idea to make it very clear 
that implementations must, in the absence of more specific information, 
regard class E space as regular unicast space, the same way the IPv6 
addressing RFCs spell this out for IPv6 address space that hasn't 
received a specific purpose yet. If we do this now we have ten years or 
more to clean up implementations.


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


From exim@www1.ietf.org  Tue Apr 20 15:00:17 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12927
	for <ietf-archive@odin.ietf.org>; Tue, 20 Apr 2004 15:00:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG0JQ-0003eB-4F
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 14:49:40 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KIneaI014016
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 14:49:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG08A-0007ne-J4; Tue, 20 Apr 2004 14:38:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BFzve-0003Bg-8R
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 14:25: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 OAA10167
	for <ietf@ietf.org>; Tue, 20 Apr 2004 14:25: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 1BFzvb-0005yI-Gv
	for ietf@ietf.org; Tue, 20 Apr 2004 14:25:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BFzug-0005sa-00
	for ietf@ietf.org; Tue, 20 Apr 2004 14:24:06 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BFztn-0005lX-00
	for ietf@ietf.org; Tue, 20 Apr 2004 14:23:11 -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 i3KIMx1C026346;
	Tue, 20 Apr 2004 20:22:59 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <6.0.1.1.2.20040420215955.01c06ec0@localhost>
References: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com> <6.0.1.1.2.20040420215955.01c06ec0@localhost>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C0D36B9A-92F7-11D8-A922-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [Ietf] 240.0.0.0/4
Date: Tue, 20 Apr 2004 20:22:59 +0200
To: Geoff Huston <gih@telstra.net>
X-Mailer: Apple Mail (2.613)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

On 20-apr-04, at 14:26, Geoff Huston wrote:

> You appear to be saying that using 224.0.0.0/4 in contexts such as used
> by the current RFC 1918 space does not sacrifice 'usable' unicast
> address space. Surely, however, if these addresses are 'useable' in 
> 1918
> contexts they would be equally useable in a global context?

I don't think this is the case. If an organization were to adopt 
addresses from 224.0.0.0/4 for use in an RFC 1918-like fashion, they 
would only have to make sure that all their internal systems are able 
to treat class E addresses as regular unicast addresses. However, class 
E addresses would only be globeally useable if and when all systems 
connected to the net throughout the globe are able to use them as 
regular unicast addresses.

> I personally do not see any value in using this address block up in a
> 1918 role.

I tend to agree, not having heard the case for additional private space.

> My reasoning for this view is that life would be getting
> mildly interesting if we ever reach the point when we are forced to use
> this space, but life could be interesting a little sooner if we act now
> to burn up this space for use in private / closed network contexts

I'm not sure whether you are trying to optimize for an interesting or a 
less interesting life...

> and
> thereby make it completely unavailable to the public network. i.e. I
> hope that collectively we, for some suitably large value of "we", will
> manage this evolving situation so that the public Internet _never_ 
> needs
> to clamber into using the Class E space

Why?

The addresses are there. Leaving them unused while address assignment 
policies grow more strict over time doesn't make much sense.

> for me, it
> is some small comfort to know that if we do reach the point we we've
> managed to assign, allocate and otherwise distribute these 219.98 /8
> addresses, there is something left in the address cupboard marked 'E"
> that conceivably is there to use if we really _have_ to.

My comfort level would be much higher if by the time that we need the 
extra address space, we have a fighting chance of actually being able 
to use it. So I think it would be a good idea to make it very clear 
that implementations must, in the absence of more specific information, 
regard class E space as regular unicast space, the same way the IPv6 
addressing RFCs spell this out for IPv6 address space that hasn't 
received a specific purpose yet. If we do this now we have ten years or 
more to clean up implementations.


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



From ietf-admin@ietf.org  Tue Apr 20 15:47: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 PAA17432
	for <ietf-archive@ietf.org>; Tue, 20 Apr 2004 15:47: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 1BG1DI-0004dw-9Q
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 15:47:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG1CO-0004Yw-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 15:46:29 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG1Bi-0004Tz-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 15:45:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG0wc-0005RK-PK; Tue, 20 Apr 2004 15:30:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG0la-0007yQ-Sz
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 15:18:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15412
	for <ietf@ietf.org>; Tue, 20 Apr 2004 15:18: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 1BG0lZ-0002Sn-Da
	for ietf@ietf.org; Tue, 20 Apr 2004 15:18:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG0kk-0002LK-00
	for ietf@ietf.org; Tue, 20 Apr 2004 15:17:55 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG0jf-0002CD-00
	for ietf@ietf.org; Tue, 20 Apr 2004 15:16:47 -0400
Received: from eaglet (127.0.0.1:3356)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S5112E> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 20 Apr 2004 12:20:24 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Geoff Huston'" <gih@telstra.net>,
        "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
Date: Tue, 20 Apr 2004 12:16:46 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQm1XoB9hSh5xvBQDSmkHqlKNKd7wANLyFA
In-Reply-To: <6.0.1.1.2.20040420215955.01c06ec0@localhost>
Message-Id: <E1BG0jf-0002CD-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

There should be an I-D released soon proposing an update to 1918 to expand
the private IPv4 space as draft-hain-1918bis-00.txt.  

As far as redefining 224/4; it is likely going to be impossible to redefine
this space as no one really knows what it is being used for. In addition,
there may be special handling in deployed stacks that will be impossible to
replace in any reasonable timeframe. 

Tony


> -----Original Message-----
> From: ietf-admin@ietf.org [mailto:ietf-admin@ietf.org] On Behalf Of Geoff
> Huston
> Sent: Tuesday, April 20, 2004 5:26 AM
> To: Iljitsch van Beijnum; IETF Discussion
> Subject: Re: [Ietf] 240.0.0.0/4
> 
> [Just to be pedantic ( :-) ) there are the equivalent of 219.98 'useable'
> unicast IPv4 addresses if you use a unit of /8s (16,777,216 /32
> addresses) (by my reading of the IANA IPv4 address registry plus
> RFC3330).]
> 
> You appear to be saying that using 224.0.0.0/4 in contexts such as used
> by the current RFC 1918 space does not sacrifice 'usable' unicast
> address space. Surely, however, if these addresses are 'useable' in 1918
> contexts they would be equally useable in a global context?
> 
> As a more general comment on your proposal, it appears that the
> consumption rates of address space in the Internet for the past four
> years are best modelled by a constant growth model of just under 4 /8s
> per year (http://bgp.potaroo.net/ipv4/). That class E space is some 4
> years of current average IPv4 address consumption rates.
> 
> I personally do not see any value in using this address block up in a
> 1918 role. My reasoning for this view is that life would be getting
> mildly interesting if we ever reach the point when we are forced to use
> this space, but life could be interesting a little sooner if we act now
> to burn up this space for use in private / closed network contexts and
> thereby make it completely unavailable to the public network. i.e. I
> hope that collectively we, for some suitably large value of "we", will
> manage this evolving situation so that the public Internet _never_ needs
> to clamber into using the Class E space to sustain the continued growth
> of the IPv4 public addressed network for some further extension of time
> before the unallocated address pool completely dries up, but, for me, it
> is some small comfort to know that if we do reach the point we we've
> managed to assign, allocate and otherwise distribute these 219.98 /8
> addresses, there is something left in the address cupboard marked 'E"
> that conceivably is there to use if we really _have_ to.
> 
> 
> Geoff Huston
> 
> 
> 
> 
> 
> At 06:19 PM 20/04/2004, Iljitsch van Beijnum wrote:
> >I was wondering if there are any plans to change the status of the class
> E
> >address space (240.0.0.0 - 255.255.255.255).
> >
> >Currently, there are approximately 221 usable /8s: classes A (125), B
> (64)
> >and C (32). (0.0.0.0/8, 10.0.0.0/8 and 127.0.0.0/8 aren't usable at this
> >time.) Adding 16 /8s from class E space would increase this by 7%, and
> >increase the unused address space with something like 20%.
> >
> >However, it's almost certain that there are implementations out there
> that
> >won't accept 224.0.0.0/4 as regular unicast address space. So if we want
> >to be able to use class E space as such, it is imperative that we
> announce
> >this a *very* long time in advance.
> >
> >Two other possible uses:
> >
> >It seems that there are now organizations who want/need more private
> >address space than is available as per RFC 1918. Using class E space for
> >this would make a lot of sense as this allows for a lot of private space
> >without sacrificing usable unicast space.
> >
> >In large networks, a lot of address space is used up and/or fragmented
> for
> >point to point links and other infrastructure use. Using class E space
> for
> >this could be a good compromise between using regular unicast space on
> the
> >one hand or RFC 1918 space on the other hand.
> >
> >Thoughts?
> >
> >And is there a wg that deals / should deal with this issue?
> >
> >Iljitsch van Beijnum
> >
> >
> >_______________________________________________
> >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 exim@www1.ietf.org  Tue Apr 20 15:51:02 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18071
	for <ietf-archive@odin.ietf.org>; Tue, 20 Apr 2004 15:51:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG1Bj-00032t-5L
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 15:45:47 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KJjlOp011703
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 15:45:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG0wc-0005RK-PK; Tue, 20 Apr 2004 15:30:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG0la-0007yQ-Sz
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 15:18:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15412
	for <ietf@ietf.org>; Tue, 20 Apr 2004 15:18: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 1BG0lZ-0002Sn-Da
	for ietf@ietf.org; Tue, 20 Apr 2004 15:18:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG0kk-0002LK-00
	for ietf@ietf.org; Tue, 20 Apr 2004 15:17:55 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG0jf-0002CD-00
	for ietf@ietf.org; Tue, 20 Apr 2004 15:16:47 -0400
Received: from eaglet (127.0.0.1:3356)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S5112E> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 20 Apr 2004 12:20:24 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Geoff Huston'" <gih@telstra.net>,
        "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
Date: Tue, 20 Apr 2004 12:16:46 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQm1XoB9hSh5xvBQDSmkHqlKNKd7wANLyFA
In-Reply-To: <6.0.1.1.2.20040420215955.01c06ec0@localhost>
Message-Id: <E1BG0jf-0002CD-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

There should be an I-D released soon proposing an update to 1918 to expand
the private IPv4 space as draft-hain-1918bis-00.txt.  

As far as redefining 224/4; it is likely going to be impossible to redefine
this space as no one really knows what it is being used for. In addition,
there may be special handling in deployed stacks that will be impossible to
replace in any reasonable timeframe. 

Tony


> -----Original Message-----
> From: ietf-admin@ietf.org [mailto:ietf-admin@ietf.org] On Behalf Of Geoff
> Huston
> Sent: Tuesday, April 20, 2004 5:26 AM
> To: Iljitsch van Beijnum; IETF Discussion
> Subject: Re: [Ietf] 240.0.0.0/4
> 
> [Just to be pedantic ( :-) ) there are the equivalent of 219.98 'useable'
> unicast IPv4 addresses if you use a unit of /8s (16,777,216 /32
> addresses) (by my reading of the IANA IPv4 address registry plus
> RFC3330).]
> 
> You appear to be saying that using 224.0.0.0/4 in contexts such as used
> by the current RFC 1918 space does not sacrifice 'usable' unicast
> address space. Surely, however, if these addresses are 'useable' in 1918
> contexts they would be equally useable in a global context?
> 
> As a more general comment on your proposal, it appears that the
> consumption rates of address space in the Internet for the past four
> years are best modelled by a constant growth model of just under 4 /8s
> per year (http://bgp.potaroo.net/ipv4/). That class E space is some 4
> years of current average IPv4 address consumption rates.
> 
> I personally do not see any value in using this address block up in a
> 1918 role. My reasoning for this view is that life would be getting
> mildly interesting if we ever reach the point when we are forced to use
> this space, but life could be interesting a little sooner if we act now
> to burn up this space for use in private / closed network contexts and
> thereby make it completely unavailable to the public network. i.e. I
> hope that collectively we, for some suitably large value of "we", will
> manage this evolving situation so that the public Internet _never_ needs
> to clamber into using the Class E space to sustain the continued growth
> of the IPv4 public addressed network for some further extension of time
> before the unallocated address pool completely dries up, but, for me, it
> is some small comfort to know that if we do reach the point we we've
> managed to assign, allocate and otherwise distribute these 219.98 /8
> addresses, there is something left in the address cupboard marked 'E"
> that conceivably is there to use if we really _have_ to.
> 
> 
> Geoff Huston
> 
> 
> 
> 
> 
> At 06:19 PM 20/04/2004, Iljitsch van Beijnum wrote:
> >I was wondering if there are any plans to change the status of the class
> E
> >address space (240.0.0.0 - 255.255.255.255).
> >
> >Currently, there are approximately 221 usable /8s: classes A (125), B
> (64)
> >and C (32). (0.0.0.0/8, 10.0.0.0/8 and 127.0.0.0/8 aren't usable at this
> >time.) Adding 16 /8s from class E space would increase this by 7%, and
> >increase the unused address space with something like 20%.
> >
> >However, it's almost certain that there are implementations out there
> that
> >won't accept 224.0.0.0/4 as regular unicast address space. So if we want
> >to be able to use class E space as such, it is imperative that we
> announce
> >this a *very* long time in advance.
> >
> >Two other possible uses:
> >
> >It seems that there are now organizations who want/need more private
> >address space than is available as per RFC 1918. Using class E space for
> >this would make a lot of sense as this allows for a lot of private space
> >without sacrificing usable unicast space.
> >
> >In large networks, a lot of address space is used up and/or fragmented
> for
> >point to point links and other infrastructure use. Using class E space
> for
> >this could be a good compromise between using regular unicast space on
> the
> >one hand or RFC 1918 space on the other hand.
> >
> >Thoughts?
> >
> >And is there a wg that deals / should deal with this issue?
> >
> >Iljitsch van Beijnum
> >
> >
> >_______________________________________________
> >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-admin@ietf.org  Tue Apr 20 18:15: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 SAA02138
	for <ietf-archive@ietf.org>; Tue, 20 Apr 2004 18:15: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 1BG3WU-0006DH-9F
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 18:15:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG3VE-0005wa-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 18:14:05 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG3U2-0005l2-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 18:12:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG36U-0001xR-Ky; Tue, 20 Apr 2004 17:48:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG2Wf-0004pN-1n
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 17:11:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25482
	for <ietf@ietf.org>; Tue, 20 Apr 2004 17:11: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 1BG2Wc-0006o6-AY
	for ietf@ietf.org; Tue, 20 Apr 2004 17:11:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG2Vg-0006eH-00
	for ietf@ietf.org; Tue, 20 Apr 2004 17:10:28 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG2Ui-0006Nt-00
	for ietf@ietf.org; Tue, 20 Apr 2004 17:09:28 -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 i3KL8rkO029215
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 20 Apr 2004 17:08:56 -0400
Date: Tue, 20 Apr 2004 17:08:53 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: [Ietf] 240.0.0.0/4
In-Reply-To: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0404201623330.28220-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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, 20 Apr 2004, Iljitsch van Beijnum wrote:
> It seems that there are now organizations who want/need more private 
> address space than is available as per RFC 1918. Using class E space 
> for this would make a lot of sense as this allows for a lot of private 
> space without sacrificing usable unicast space.

Can you elaborate?  I used to work for Hitachi, which is/was then the 7th
largest company in the world.  I can think of very few organizations that
need more than 1 /8 and 17 /16's of unique, non-public space.

Allowing a non-global address space as a subset of the global space means
that one (or many) can reach the public network through a default route
that leads to a NAT.  But if you have such a large network that it has
something greater than 20 million hosts that must each have direct access
to any of the rest, and you can't NAT internally, then you probably have
reached a point where you will need a more sophisticated mechanism than
NAT to reach the public internet.

Underlying this is the question of whether such a large network really
needs to simultanously reach the public network. If it doesn't, then there
is no reason to limit oneself to the RFC 1918 space.

I might also suggest that such a heavy address user migrate to IPv6
internally as IPv6 has similar problems and it is developing means to deal
with them.

		--Dean



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


From exim@www1.ietf.org  Tue Apr 20 18:19:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03111
	for <ietf-archive@odin.ietf.org>; Tue, 20 Apr 2004 18:19:53 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG3U4-0002Th-NZ
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 18:12:52 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KMCqU6009503
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 18:12:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG36U-0001xR-Ky; Tue, 20 Apr 2004 17:48:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG2Wf-0004pN-1n
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 17:11:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25482
	for <ietf@ietf.org>; Tue, 20 Apr 2004 17:11: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 1BG2Wc-0006o6-AY
	for ietf@ietf.org; Tue, 20 Apr 2004 17:11:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG2Vg-0006eH-00
	for ietf@ietf.org; Tue, 20 Apr 2004 17:10:28 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG2Ui-0006Nt-00
	for ietf@ietf.org; Tue, 20 Apr 2004 17:09:28 -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 i3KL8rkO029215
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 20 Apr 2004 17:08:56 -0400
Date: Tue, 20 Apr 2004 17:08:53 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: [Ietf] 240.0.0.0/4
In-Reply-To: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0404201623330.28220-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Tue, 20 Apr 2004, Iljitsch van Beijnum wrote:
> It seems that there are now organizations who want/need more private 
> address space than is available as per RFC 1918. Using class E space 
> for this would make a lot of sense as this allows for a lot of private 
> space without sacrificing usable unicast space.

Can you elaborate?  I used to work for Hitachi, which is/was then the 7th
largest company in the world.  I can think of very few organizations that
need more than 1 /8 and 17 /16's of unique, non-public space.

Allowing a non-global address space as a subset of the global space means
that one (or many) can reach the public network through a default route
that leads to a NAT.  But if you have such a large network that it has
something greater than 20 million hosts that must each have direct access
to any of the rest, and you can't NAT internally, then you probably have
reached a point where you will need a more sophisticated mechanism than
NAT to reach the public internet.

Underlying this is the question of whether such a large network really
needs to simultanously reach the public network. If it doesn't, then there
is no reason to limit oneself to the RFC 1918 space.

I might also suggest that such a heavy address user migrate to IPv6
internally as IPv6 has similar problems and it is developing means to deal
with them.

		--Dean



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



From ietf-admin@ietf.org  Tue Apr 20 19:26:18 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06588
	for <ietf-archive@ietf.org>; Tue, 20 Apr 2004 19:26: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 1BG4d7-000447-Jd
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 19:26:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG4cC-0003ww-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 19:25:21 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG4bD-0003qP-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 19:24:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG4Dk-0005Db-7g; Tue, 20 Apr 2004 19:00:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG4B5-00025Z-5q
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 18:57:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05371
	for <ietf@ietf.org>; Tue, 20 Apr 2004 18:57: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 1BG4B1-00021G-SE
	for ietf@ietf.org; Tue, 20 Apr 2004 18:57:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG4A6-0001yI-00
	for ietf@ietf.org; Tue, 20 Apr 2004 18:56:18 -0400
Received: from kahuna.telstra.net ([203.50.0.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG49N-0001sr-00
	for ietf@ietf.org; Tue, 20 Apr 2004 18:55:34 -0400
Received: from gihz1.telstra.net (rsdhcp4.telstra.net [203.50.0.196])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id i3KMsxuY001671;
	Wed, 21 Apr 2004 08:55:01 +1000 (EST)
	(envelope-from gih@telstra.net)
Message-Id: <6.0.1.1.2.20040421085150.01bd9ff0@kahuna.telstra.net>
X-Sender: gih@kahuna.telstra.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 21 Apr 2004 08:54:51 +1000
To: Iljitsch van Beijnum <iljitsch@muada.com>
From: Geoff Huston <gih@telstra.net>
Subject: Re: [Ietf] 240.0.0.0/4
Cc: IETF Discussion <ietf@ietf.org>
In-Reply-To: <C0D36B9A-92F7-11D8-A922-000A95CD987A@muada.com>
References: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
 <6.0.1.1.2.20040420215955.01c06ec0@localhost>
 <C0D36B9A-92F7-11D8-A922-000A95CD987A@muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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 believe we are in complete agreement when you say:

>My comfort level would be much higher if by the time that we need the 
>extra address space, we have a fighting chance of actually being able to 
>use it. So I think it would be a good idea to make it very clear that 
>implementations must, in the absence of more specific information, regard 
>class E space as regular unicast space, the same way the IPv6 addressing 
>RFCs spell this out for IPv6 address space that hasn't received a specific 
>purpose yet. If we do this now we have ten years or more to clean up 
>implementations.

The reason why I responded to your original proposal was that I understood
you were advocating that this space should be used to extend the
private use RFC 1918 space, whereas I am advocating the view that
this space should be considered part of the global use IPv4 unicast address
pool. My apologies if I misunderstood what you were proposing.

Geoff


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


From exim@www1.ietf.org  Tue Apr 20 19:34:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07134
	for <ietf-archive@odin.ietf.org>; Tue, 20 Apr 2004 19:34:11 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG4bE-0006Ne-I3
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 19:24:21 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KNOK9e024497
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 19:24:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG4Dk-0005Db-7g; Tue, 20 Apr 2004 19:00:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG4B5-00025Z-5q
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 18:57:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05371
	for <ietf@ietf.org>; Tue, 20 Apr 2004 18:57: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 1BG4B1-00021G-SE
	for ietf@ietf.org; Tue, 20 Apr 2004 18:57:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG4A6-0001yI-00
	for ietf@ietf.org; Tue, 20 Apr 2004 18:56:18 -0400
Received: from kahuna.telstra.net ([203.50.0.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG49N-0001sr-00
	for ietf@ietf.org; Tue, 20 Apr 2004 18:55:34 -0400
Received: from gihz1.telstra.net (rsdhcp4.telstra.net [203.50.0.196])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id i3KMsxuY001671;
	Wed, 21 Apr 2004 08:55:01 +1000 (EST)
	(envelope-from gih@telstra.net)
Message-Id: <6.0.1.1.2.20040421085150.01bd9ff0@kahuna.telstra.net>
X-Sender: gih@kahuna.telstra.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 21 Apr 2004 08:54:51 +1000
To: Iljitsch van Beijnum <iljitsch@muada.com>
From: Geoff Huston <gih@telstra.net>
Subject: Re: [Ietf] 240.0.0.0/4
Cc: IETF Discussion <ietf@ietf.org>
In-Reply-To: <C0D36B9A-92F7-11D8-A922-000A95CD987A@muada.com>
References: <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
 <6.0.1.1.2.20040420215955.01c06ec0@localhost>
 <C0D36B9A-92F7-11D8-A922-000A95CD987A@muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

I believe we are in complete agreement when you say:

>My comfort level would be much higher if by the time that we need the 
>extra address space, we have a fighting chance of actually being able to 
>use it. So I think it would be a good idea to make it very clear that 
>implementations must, in the absence of more specific information, regard 
>class E space as regular unicast space, the same way the IPv6 addressing 
>RFCs spell this out for IPv6 address space that hasn't received a specific 
>purpose yet. If we do this now we have ten years or more to clean up 
>implementations.

The reason why I responded to your original proposal was that I understood
you were advocating that this space should be used to extend the
private use RFC 1918 space, whereas I am advocating the view that
this space should be considered part of the global use IPv4 unicast address
pool. My apologies if I misunderstood what you were proposing.

Geoff


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



From ietf-admin@ietf.org  Tue Apr 20 20:29: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 UAA10477
	for <ietf-archive@ietf.org>; Tue, 20 Apr 2004 20:29: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 1BG5cD-0001eP-FP
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 20:29:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG5bF-0001Yb-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 20:28:25 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG5ai-0001UN-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 20:27:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG5Hb-0002y4-Mw; Tue, 20 Apr 2004 20:08:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG5AB-0007jv-AN
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 20:00: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 UAA08759
	for <ietf@ietf.org>; Tue, 20 Apr 2004 20:00: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 1BG5A8-0006zz-NY
	for ietf@ietf.org; Tue, 20 Apr 2004 20:00:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG599-0006vl-00
	for ietf@ietf.org; Tue, 20 Apr 2004 19:59:23 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG58T-0006rL-00
	for ietf@ietf.org; Tue, 20 Apr 2004 19:58:41 -0400
Received: from eaglet (127.0.0.1:4602)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S5122F> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 20 Apr 2004 17:02:14 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dean Anderson'" <dean@av8.com>,
        "'Iljitsch van Beijnum'" <iljitsch@muada.com>
Cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
Date: Tue, 20 Apr 2004 16:58:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQnJSYePstF/bpfSaWGsXMpueyJMAADCByA
In-Reply-To: <Pine.LNX.4.44.0404201623330.28220-100000@cirrus.av8.net>
Message-Id: <E1BG58T-0006rL-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Dean Anderson wrote:
> ...
> Allowing a non-global address space as a subset of the global space means
> that one (or many) can reach the public network through a default route
> that leads to a NAT.  But if you have such a large network that it has
> something greater than 20 million hosts
                                   ^^^^^^^
Fatal flaw... The concept of a network is not limited to the traditional
perspective of 'hosts'. 

> that must each have direct access
> to any of the rest, and you can't NAT internally, then you probably have
> reached a point where you will need a more sophisticated mechanism than
> NAT to reach the public internet.

You assume a network & traffic model that may not apply.

> 
> Underlying this is the question of whether such a large network really
> needs to simultanously reach the public network. If it doesn't, then there
> is no reason to limit oneself to the RFC 1918 space.

Yes there is when some of the nodes do need access to the public network.
You can't expect to use a private version of a publicly routed prefix.

> 
> I might also suggest that such a heavy address user migrate to IPv6
> internally as IPv6 has similar problems and it is developing means to deal
> with them.

Easy to say, but turning something with that mass takes more time than the
dentist office network. Yes it is the right thing to do, but don't expect it
to happen in a timeframe shorter than 3-5 years. 

Tony




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


From exim@www1.ietf.org  Tue Apr 20 20:30:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10571
	for <ietf-archive@odin.ietf.org>; Tue, 20 Apr 2004 20:30:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG5ak-0002Kv-2y
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 20:27:54 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3L0RsWY008955
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 20:27:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG5Hb-0002y4-Mw; Tue, 20 Apr 2004 20:08:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG5AB-0007jv-AN
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 20:00: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 UAA08759
	for <ietf@ietf.org>; Tue, 20 Apr 2004 20:00: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 1BG5A8-0006zz-NY
	for ietf@ietf.org; Tue, 20 Apr 2004 20:00:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG599-0006vl-00
	for ietf@ietf.org; Tue, 20 Apr 2004 19:59:23 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG58T-0006rL-00
	for ietf@ietf.org; Tue, 20 Apr 2004 19:58:41 -0400
Received: from eaglet (127.0.0.1:4602)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S5122F> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 20 Apr 2004 17:02:14 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dean Anderson'" <dean@av8.com>,
        "'Iljitsch van Beijnum'" <iljitsch@muada.com>
Cc: "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
Date: Tue, 20 Apr 2004 16:58:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQnJSYePstF/bpfSaWGsXMpueyJMAADCByA
In-Reply-To: <Pine.LNX.4.44.0404201623330.28220-100000@cirrus.av8.net>
Message-Id: <E1BG58T-0006rL-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Dean Anderson wrote:
> ...
> Allowing a non-global address space as a subset of the global space means
> that one (or many) can reach the public network through a default route
> that leads to a NAT.  But if you have such a large network that it has
> something greater than 20 million hosts
                                   ^^^^^^^
Fatal flaw... The concept of a network is not limited to the traditional
perspective of 'hosts'. 

> that must each have direct access
> to any of the rest, and you can't NAT internally, then you probably have
> reached a point where you will need a more sophisticated mechanism than
> NAT to reach the public internet.

You assume a network & traffic model that may not apply.

> 
> Underlying this is the question of whether such a large network really
> needs to simultanously reach the public network. If it doesn't, then there
> is no reason to limit oneself to the RFC 1918 space.

Yes there is when some of the nodes do need access to the public network.
You can't expect to use a private version of a publicly routed prefix.

> 
> I might also suggest that such a heavy address user migrate to IPv6
> internally as IPv6 has similar problems and it is developing means to deal
> with them.

Easy to say, but turning something with that mass takes more time than the
dentist office network. Yes it is the right thing to do, but don't expect it
to happen in a timeframe shorter than 3-5 years. 

Tony




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



From ietf-admin@ietf.org  Tue Apr 20 20:54: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 UAA11894
	for <ietf-archive@ietf.org>; Tue, 20 Apr 2004 20:54: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 1BG60Y-0003wj-PI
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 20:54:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG5zZ-0003pu-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 20:53:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG5ys-0003k1-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 20:52:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG5nW-0000YF-Ul; Tue, 20 Apr 2004 20:41:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG5eW-00056a-3k
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 20:31: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 UAA10775
	for <ietf@ietf.org>; Tue, 20 Apr 2004 20:31: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 1BG5eT-0001z5-Sm
	for ietf@ietf.org; Tue, 20 Apr 2004 20:31:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG5dc-0001qd-00
	for ietf@ietf.org; Tue, 20 Apr 2004 20:30:52 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG5cc-0001dW-00
	for ietf@ietf.org; Tue, 20 Apr 2004 20:29:50 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i3L0TD607470;
	Tue, 20 Apr 2004 17:29:13 -0700
X-mProtect: <200404210029> Nokia Silicon Valley Messaging Protection
Received: from walnut2.iprg.nokia.com (205.226.9.199, claiming to be "spruce.nokia.com")
	by darkstar.iprg.nokia.com smtpdWIqjxb; Tue, 20 Apr 2004 15:54:47 PDT
Message-Id: <4.3.2.7.2.20040420120953.02c645e0@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 20 Apr 2004 15:53:10 -0700
To: Iljitsch van Beijnum <iljitsch@muada.com>
From: Bob Hinden <bob.hinden@nokia.com>
Subject: Re: [Ietf] 240.0.0.0/4
Cc: IETF Discussion <ietf@ietf.org>
In-Reply-To: <C0D36B9A-92F7-11D8-A922-000A95CD987A@muada.com>
References: <6.0.1.1.2.20040420215955.01c06ec0@localhost>
 <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
 <6.0.1.1.2.20040420215955.01c06ec0@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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

Iljitsch,

>My comfort level would be much higher if by the time that we need the 
>extra address space, we have a fighting chance of actually being able to 
>use it. So I think it would be a good idea to make it very clear that 
>implementations must, in the absence of more specific information, regard 
>class E space as regular unicast space, the same way the IPv6 addressing 
>RFCs spell this out for IPv6 address space that hasn't received a specific 
>purpose yet. If we do this now we have ten years or more to clean up 
>implementations.

The only way to make this happen would be to start assigning them to some 
real users.  Otherwise, the bugs will not be found, reported, and 
fixed.  Just publishing an RFC with a MUST in it won't be sufficient.

The challenge here is that there may be a lot of IPv4 implementations may 
have little or any support, and may not be possible to upgrade.  This would 
put anyone receiving a Class-E address at a big disadvantage.  These 
addresses might have to be used behind a NAT to be useful (i.e., allow 
direct communication to the rest of the Internet) and this, of course, 
defeats the purpose of using them in the first place.

Bob


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


From exim@www1.ietf.org  Tue Apr 20 21:04:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12650
	for <ietf-archive@odin.ietf.org>; Tue, 20 Apr 2004 21:04:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG5yt-0004vR-OJ
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 20:52:51 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3L0qpPm018905
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 20:52:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG5nW-0000YF-Ul; Tue, 20 Apr 2004 20:41:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG5eW-00056a-3k
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 20:31: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 UAA10775
	for <ietf@ietf.org>; Tue, 20 Apr 2004 20:31: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 1BG5eT-0001z5-Sm
	for ietf@ietf.org; Tue, 20 Apr 2004 20:31:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG5dc-0001qd-00
	for ietf@ietf.org; Tue, 20 Apr 2004 20:30:52 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG5cc-0001dW-00
	for ietf@ietf.org; Tue, 20 Apr 2004 20:29:50 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i3L0TD607470;
	Tue, 20 Apr 2004 17:29:13 -0700
X-mProtect: <200404210029> Nokia Silicon Valley Messaging Protection
Received: from walnut2.iprg.nokia.com (205.226.9.199, claiming to be "spruce.nokia.com")
	by darkstar.iprg.nokia.com smtpdWIqjxb; Tue, 20 Apr 2004 15:54:47 PDT
Message-Id: <4.3.2.7.2.20040420120953.02c645e0@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 20 Apr 2004 15:53:10 -0700
To: Iljitsch van Beijnum <iljitsch@muada.com>
From: Bob Hinden <bob.hinden@nokia.com>
Subject: Re: [Ietf] 240.0.0.0/4
Cc: IETF Discussion <ietf@ietf.org>
In-Reply-To: <C0D36B9A-92F7-11D8-A922-000A95CD987A@muada.com>
References: <6.0.1.1.2.20040420215955.01c06ec0@localhost>
 <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
 <6.0.1.1.2.20040420215955.01c06ec0@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

Iljitsch,

>My comfort level would be much higher if by the time that we need the 
>extra address space, we have a fighting chance of actually being able to 
>use it. So I think it would be a good idea to make it very clear that 
>implementations must, in the absence of more specific information, regard 
>class E space as regular unicast space, the same way the IPv6 addressing 
>RFCs spell this out for IPv6 address space that hasn't received a specific 
>purpose yet. If we do this now we have ten years or more to clean up 
>implementations.

The only way to make this happen would be to start assigning them to some 
real users.  Otherwise, the bugs will not be found, reported, and 
fixed.  Just publishing an RFC with a MUST in it won't be sufficient.

The challenge here is that there may be a lot of IPv4 implementations may 
have little or any support, and may not be possible to upgrade.  This would 
put anyone receiving a Class-E address at a big disadvantage.  These 
addresses might have to be used behind a NAT to be useful (i.e., allow 
direct communication to the rest of the Internet) and this, of course, 
defeats the purpose of using them in the first place.

Bob


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



From ietf-admin@ietf.org  Tue Apr 20 22:24: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 WAA16381
	for <ietf-archive@ietf.org>; Tue, 20 Apr 2004 22:24: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 1BG7PR-0004Fs-B5
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 22:24:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG7Oa-0004AE-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 22:23:28 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG7Ng-00044w-00
	for ietf-archive@ietf.org; Tue, 20 Apr 2004 22:22:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG7DY-0005ot-LR; Tue, 20 Apr 2004 22:12:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG79C-0003T9-18
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 22:07: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 WAA15594
	for <ietf@ietf.org>; Tue, 20 Apr 2004 22:07: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 1BG798-0002Wn-TV
	for ietf@ietf.org; Tue, 20 Apr 2004 22:07:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG78T-0002SG-00
	for ietf@ietf.org; Tue, 20 Apr 2004 22:06:50 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG77r-0002JP-00
	for ietf@ietf.org; Tue, 20 Apr 2004 22:06:11 -0400
MIME-Version: 1.0
Subject: RE: [Ietf] 240.0.0.0/4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Date: Tue, 20 Apr 2004 19:05:33 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB0B0@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: [Ietf] 240.0.0.0/4
thread-index: AcQnCDgHj7nLecyrRFOIUpHVtsXnQAAO3Nuw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>,
        "Geoff Huston" <gih@telstra.net>
Cc: "IETF Discussion" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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

>> Geoff Huston wrote:
>> I personally do not see any value in using
>> this address block up in a 1918 role.

> Iljitsch van Beijnum
> I tend to agree, not having heard the case for
> additional private space.

I agree also.

> My comfort level would be much higher if by the
> time that we need the extra address space, we have
> a fighting chance of actually being able to use it.
> So I think it would be a good idea to make it very
> clear that implementations must, in the absence of
> more specific information, regard class E space as
> regular unicast space,

Indeed, and I would go even further: we would need to allocate a few
test blocks out of 240/4 for usable but non-critical projects. Even
after vendors implement it, it will take years for natural router OS
upgrades to occur in order to use these new addresses. The code
modifications are not huge, but it is likely that on a given router OS
there are plenty of places where tagging class E off-limits is
hard-coded, which means it will indeed take time to debug on top of
propagating the updated router OS.

Geoff, besides the discussion we had a while ago about bogon lists being
the right answer, look at the time it takes to resolve bogon issue on
newly allocated blocks: it's only a matter of config and it takes
months. If on top of that there needs to be an OS upgrade, it could take
years.

Michel.


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


From exim@www1.ietf.org  Tue Apr 20 22:35:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16899
	for <ietf-archive@odin.ietf.org>; Tue, 20 Apr 2004 22:35:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG7Ni-0001Jl-KD
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 22:22:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3L2MYtw005039
	for ietf-archive@odin.ietf.org; Tue, 20 Apr 2004 22:22:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG7DY-0005ot-LR; Tue, 20 Apr 2004 22:12:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BG79C-0003T9-18
	for ietf@optimus.ietf.org; Tue, 20 Apr 2004 22:07: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 WAA15594
	for <ietf@ietf.org>; Tue, 20 Apr 2004 22:07: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 1BG798-0002Wn-TV
	for ietf@ietf.org; Tue, 20 Apr 2004 22:07:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BG78T-0002SG-00
	for ietf@ietf.org; Tue, 20 Apr 2004 22:06:50 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BG77r-0002JP-00
	for ietf@ietf.org; Tue, 20 Apr 2004 22:06:11 -0400
MIME-Version: 1.0
Subject: RE: [Ietf] 240.0.0.0/4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Date: Tue, 20 Apr 2004 19:05:33 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB0B0@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: [Ietf] 240.0.0.0/4
thread-index: AcQnCDgHj7nLecyrRFOIUpHVtsXnQAAO3Nuw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>,
        "Geoff Huston" <gih@telstra.net>
Cc: "IETF Discussion" <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: quoted-printable

>> Geoff Huston wrote:
>> I personally do not see any value in using
>> this address block up in a 1918 role.

> Iljitsch van Beijnum
> I tend to agree, not having heard the case for
> additional private space.

I agree also.

> My comfort level would be much higher if by the
> time that we need the extra address space, we have
> a fighting chance of actually being able to use it.
> So I think it would be a good idea to make it very
> clear that implementations must, in the absence of
> more specific information, regard class E space as
> regular unicast space,

Indeed, and I would go even further: we would need to allocate a few
test blocks out of 240/4 for usable but non-critical projects. Even
after vendors implement it, it will take years for natural router OS
upgrades to occur in order to use these new addresses. The code
modifications are not huge, but it is likely that on a given router OS
there are plenty of places where tagging class E off-limits is
hard-coded, which means it will indeed take time to debug on top of
propagating the updated router OS.

Geoff, besides the discussion we had a while ago about bogon lists being
the right answer, look at the time it takes to resolve bogon issue on
newly allocated blocks: it's only a matter of config and it takes
months. If on top of that there needs to be an OS upgrade, it could take
years.

Michel.


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



From ietf-admin@ietf.org  Wed Apr 21 01:36: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 BAA26380
	for <ietf-archive@ietf.org>; Wed, 21 Apr 2004 01:36: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 1BGAPW-0007Jh-8N
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 01:36:38 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGAOs-0007D5-00
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 01:35:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGAGK-0002jh-8H; Wed, 21 Apr 2004 01:27:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGADF-00012t-DY
	for ietf@optimus.ietf.org; Wed, 21 Apr 2004 01:23: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 BAA25173
	for <ietf@ietf.org>; Wed, 21 Apr 2004 01:23:55 -0400 (EDT)
From: cabo@tzi.org
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGADC-0005Tv-Ck
	for ietf@ietf.org; Wed, 21 Apr 2004 01:23:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGAC3-0005Hw-00
	for ietf@ietf.org; Wed, 21 Apr 2004 01:22:44 -0400
Received: from [218.246.107.80] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGAB7-000574-00
	for ietf@ietf.org; Wed, 21 Apr 2004 01:21:46 -0400
To: ietf@ietf.org
Date: Wed, 21 Apr 2004 13:23:41 +0800
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BGAB7-000574-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.6 required=5.0 tests=HTML_40_50,HTML_MESSAGE,
	HTML_RELAYING_FRAME,MICROSOFT_EXECUTABLE,MIME_SUSPECT_NAME,
	MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME 
	autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.5 HTML_40_50 BODY: Message is 40% to 50% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.3 HTML_RELAYING_FRAME BODY: Frame wanted to load outside URL
	*  0.1 MIME_SUSPECT_NAME RAW: MIME filename does not match content
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Subject: [Ietf] Mail Delivery (failure ietf@ietf.org)
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

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-8214</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--



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


From exim@www1.ietf.org  Wed Apr 21 01:41:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26644
	for <ietf-archive@odin.ietf.org>; Wed, 21 Apr 2004 01:41:11 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGAOu-0006Ps-KQ
	for ietf-archive@odin.ietf.org; Wed, 21 Apr 2004 01:36:00 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3L5a0SB024650
	for ietf-archive@odin.ietf.org; Wed, 21 Apr 2004 01:36:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGAGK-0002jh-8H; Wed, 21 Apr 2004 01:27:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGADF-00012t-DY
	for ietf@optimus.ietf.org; Wed, 21 Apr 2004 01:23: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 BAA25173
	for <ietf@ietf.org>; Wed, 21 Apr 2004 01:23:55 -0400 (EDT)
From: cabo@tzi.org
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGADC-0005Tv-Ck
	for ietf@ietf.org; Wed, 21 Apr 2004 01:23:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGAC3-0005Hw-00
	for ietf@ietf.org; Wed, 21 Apr 2004 01:22:44 -0400
Received: from [218.246.107.80] (helo=ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGAB7-000574-00
	for ietf@ietf.org; Wed, 21 Apr 2004 01:21:46 -0400
To: ietf@ietf.org
Date: Wed, 21 Apr 2004 13:23:41 +0800
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <E1BGAB7-000574-00@ietf-mx>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.6 required=5.0 tests=HTML_40_50,HTML_MESSAGE,
	HTML_RELAYING_FRAME,MICROSOFT_EXECUTABLE,MIME_SUSPECT_NAME,
	MISSING_MIMEOLE,MSGID_FROM_MTA_SHORT,NO_REAL_NAME,PRIORITY_NO_NAME 
	autolearn=no version=2.60
X-Spam-Report: 
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.5 HTML_40_50 BODY: Message is 40% to 50% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.3 HTML_RELAYING_FRAME BODY: Frame wanted to load outside URL
	*  0.1 MIME_SUSPECT_NAME RAW: MIME filename does not match content
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Subject: [Ietf] Mail Delivery (failure ietf@ietf.org)
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

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-8214</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--



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



From ietf-admin@ietf.org  Wed Apr 21 10:04: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 KAA22084
	for <ietf-archive@ietf.org>; Wed, 21 Apr 2004 10: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 1BGIKh-0003mm-4F
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 10:04:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGIJf-0003c1-00
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 10:03:08 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGIJJ-0003Rl-00
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 10:02:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGI82-0003va-4B; Wed, 21 Apr 2004 09:51:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGHrn-00044X-GF
	for ietf@optimus.ietf.org; Wed, 21 Apr 2004 09:34:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20161
	for <ietf@ietf.org>; Wed, 21 Apr 2004 09: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 1BGHrl-0006WK-A3
	for ietf@ietf.org; Wed, 21 Apr 2004 09:34:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGHqo-0006Kh-00
	for ietf@ietf.org; Wed, 21 Apr 2004 09:33:19 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGHqB-000689-00
	for ietf@ietf.org; Wed, 21 Apr 2004 09:32:39 -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 i3LDVqJd014897
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 21 Apr 2004 09:32:04 -0400
Date: Wed, 21 Apr 2004 09:31:52 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Tony Hain <alh-ietf@tndh.net>
cc: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
In-Reply-To: <E1BG58T-0006rL-00@ietf-mx>
Message-ID: <Pine.LNX.4.44.0404210901420.14263-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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, 20 Apr 2004, Tony Hain wrote:

> Dean Anderson wrote:
> > ...
> > Allowing a non-global address space as a subset of the global space means
> > that one (or many) can reach the public network through a default route
> > that leads to a NAT.  But if you have such a large network that it has
> > something greater than 20 million hosts
>                                    ^^^^^^^
> Fatal flaw... The concept of a network is not limited to the traditional
> perspective of 'hosts'. 

Ok, fair enough. Instead of "hosts" in the traditional sense, the above
should be considered as '... approximately 20 million simultaneous uses of
unique IP addresses'.

> > that must each have direct access to any of the rest, and you can't
> > NAT internally, then you probably have reached a point where you will
> > need a more sophisticated mechanism than NAT to reach the public
> > internet.
> 
> You assume a network & traffic model that may not apply.

_I_ don't make that assumption. This was asserted by the person who
suggests that there is not enough private IP address space. Otherwise,
they would not need more than 20 million unique private IP addresses.  

Either we accept it as a given that they really do need more than ~20
million unique private IP addresses and also do need to reach the public
network, or else assert that perhaps no one really needs more than ~20
million unique, private IP addresses while also needing to reach a public
network. Or alternately, assert that if such a case does exist, then it is
so unusual that some more sophisticated mechanism is needed for that case.  

> > Underlying this is the question of whether such a large network really
> > needs to simultanously reach the public network. If it doesn't, then there
> > is no reason to limit oneself to the RFC 1918 space.
> 
> Yes there is when some of the nodes do need access to the public network.
> You can't expect to use a private version of a publicly routed prefix.

I don't think you understood my text. I meant "If it doesn't [need access
to the public network], then there is no reason to limit oneself to the
RFC 1918 space"

> > I might also suggest that such a heavy address user migrate to IPv6
> > internally as IPv6 has similar problems and it is developing means to deal
> > with them.
> 
> Easy to say, but turning something with that mass takes more time than the
> dentist office network. Yes it is the right thing to do, but don't expect it
> to happen in a timeframe shorter than 3-5 years. 

That is the same (or perhaps shorter) lifetime as changing the class E
definition. 

		--Dean


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


From exim@www1.ietf.org  Wed Apr 21 10:11:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23139
	for <ietf-archive@odin.ietf.org>; Wed, 21 Apr 2004 10:11:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGIJK-0001eT-5V
	for ietf-archive@odin.ietf.org; Wed, 21 Apr 2004 10:02:51 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3LE2kB1006334
	for ietf-archive@odin.ietf.org; Wed, 21 Apr 2004 10:02:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGI82-0003va-4B; Wed, 21 Apr 2004 09:51:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGHrn-00044X-GF
	for ietf@optimus.ietf.org; Wed, 21 Apr 2004 09:34:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20161
	for <ietf@ietf.org>; Wed, 21 Apr 2004 09: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 1BGHrl-0006WK-A3
	for ietf@ietf.org; Wed, 21 Apr 2004 09:34:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGHqo-0006Kh-00
	for ietf@ietf.org; Wed, 21 Apr 2004 09:33:19 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGHqB-000689-00
	for ietf@ietf.org; Wed, 21 Apr 2004 09:32:39 -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 i3LDVqJd014897
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 21 Apr 2004 09:32:04 -0400
Date: Wed, 21 Apr 2004 09:31:52 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Tony Hain <alh-ietf@tndh.net>
cc: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
In-Reply-To: <E1BG58T-0006rL-00@ietf-mx>
Message-ID: <Pine.LNX.4.44.0404210901420.14263-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Tue, 20 Apr 2004, Tony Hain wrote:

> Dean Anderson wrote:
> > ...
> > Allowing a non-global address space as a subset of the global space means
> > that one (or many) can reach the public network through a default route
> > that leads to a NAT.  But if you have such a large network that it has
> > something greater than 20 million hosts
>                                    ^^^^^^^
> Fatal flaw... The concept of a network is not limited to the traditional
> perspective of 'hosts'. 

Ok, fair enough. Instead of "hosts" in the traditional sense, the above
should be considered as '... approximately 20 million simultaneous uses of
unique IP addresses'.

> > that must each have direct access to any of the rest, and you can't
> > NAT internally, then you probably have reached a point where you will
> > need a more sophisticated mechanism than NAT to reach the public
> > internet.
> 
> You assume a network & traffic model that may not apply.

_I_ don't make that assumption. This was asserted by the person who
suggests that there is not enough private IP address space. Otherwise,
they would not need more than 20 million unique private IP addresses.  

Either we accept it as a given that they really do need more than ~20
million unique private IP addresses and also do need to reach the public
network, or else assert that perhaps no one really needs more than ~20
million unique, private IP addresses while also needing to reach a public
network. Or alternately, assert that if such a case does exist, then it is
so unusual that some more sophisticated mechanism is needed for that case.  

> > Underlying this is the question of whether such a large network really
> > needs to simultanously reach the public network. If it doesn't, then there
> > is no reason to limit oneself to the RFC 1918 space.
> 
> Yes there is when some of the nodes do need access to the public network.
> You can't expect to use a private version of a publicly routed prefix.

I don't think you understood my text. I meant "If it doesn't [need access
to the public network], then there is no reason to limit oneself to the
RFC 1918 space"

> > I might also suggest that such a heavy address user migrate to IPv6
> > internally as IPv6 has similar problems and it is developing means to deal
> > with them.
> 
> Easy to say, but turning something with that mass takes more time than the
> dentist office network. Yes it is the right thing to do, but don't expect it
> to happen in a timeframe shorter than 3-5 years. 

That is the same (or perhaps shorter) lifetime as changing the class E
definition. 

		--Dean


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



From ietf-admin@ietf.org  Wed Apr 21 12:02: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 MAA28899
	for <ietf-archive@ietf.org>; Wed, 21 Apr 2004 12:02: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 1BGKBD-0007h9-He
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 12:02:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGKA3-0007TG-00
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 12:01:20 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGK9Y-0007Ho-00
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 12:00:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGJzS-000316-Tq; Wed, 21 Apr 2004 11:50:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGJ1z-0006Bm-1a
	for ietf@optimus.ietf.org; Wed, 21 Apr 2004 10:48: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 KAA25809
	for <ietf@ietf.org>; Wed, 21 Apr 2004 10:48: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 1BGJ1w-0003Y9-Hy
	for ietf@ietf.org; Wed, 21 Apr 2004 10:48:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGJ0x-0003Nw-00
	for ietf@ietf.org; Wed, 21 Apr 2004 10:47:51 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGIzw-000359-00
	for ietf@ietf.org; Wed, 21 Apr 2004 10:46:48 -0400
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id i3LEkk7s021265
	for <ietf@ietf.org>; Wed, 21 Apr 2004 15:46:46 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id PAA20965
	for <ietf@ietf.org>; Wed, 21 Apr 2004 15:46:44 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i3LEkiv04626
	for ietf@ietf.org; Wed, 21 Apr 2004 15:46:44 +0100
Date: Wed, 21 Apr 2004 15:46:44 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Message-ID: <20040421144644.GK2890@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
Subject: [Ietf] New .mobi, .xxx, ... TLDs?
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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,

Is the IETF or ISOC going to take any stance against this slippery slope?

http://www.cnn.com/2004/TECH/internet/03/20/new.domains.ap/

Comment period closes April 30th.

Tim

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


From exim@www1.ietf.org  Wed Apr 21 12:18:04 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00105
	for <ietf-archive@odin.ietf.org>; Wed, 21 Apr 2004 12:18:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGK9Y-0006TG-SR
	for ietf-archive@odin.ietf.org; Wed, 21 Apr 2004 12:00:49 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3LG0mrC024850
	for ietf-archive@odin.ietf.org; Wed, 21 Apr 2004 12:00:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGJzS-000316-Tq; Wed, 21 Apr 2004 11:50:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGJ1z-0006Bm-1a
	for ietf@optimus.ietf.org; Wed, 21 Apr 2004 10:48: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 KAA25809
	for <ietf@ietf.org>; Wed, 21 Apr 2004 10:48: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 1BGJ1w-0003Y9-Hy
	for ietf@ietf.org; Wed, 21 Apr 2004 10:48:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGJ0x-0003Nw-00
	for ietf@ietf.org; Wed, 21 Apr 2004 10:47:51 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGIzw-000359-00
	for ietf@ietf.org; Wed, 21 Apr 2004 10:46:48 -0400
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id i3LEkk7s021265
	for <ietf@ietf.org>; Wed, 21 Apr 2004 15:46:46 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id PAA20965
	for <ietf@ietf.org>; Wed, 21 Apr 2004 15:46:44 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i3LEkiv04626
	for ietf@ietf.org; Wed, 21 Apr 2004 15:46:44 +0100
Date: Wed, 21 Apr 2004 15:46:44 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Message-ID: <20040421144644.GK2890@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [Ietf] New .mobi, .xxx, ... TLDs?
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

Hi,

Is the IETF or ISOC going to take any stance against this slippery slope?

http://www.cnn.com/2004/TECH/internet/03/20/new.domains.ap/

Comment period closes April 30th.

Tim

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



From ietf-admin@ietf.org  Wed Apr 21 17:03: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 RAA14186
	for <ietf-archive@ietf.org>; Wed, 21 Apr 2004 17:03: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 1BGOsM-00057E-3P
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 17:03:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGOrM-0004uh-00
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 17:02:20 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGOqt-0004jd-00
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 17:01:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGOZq-0003UC-Ks; Wed, 21 Apr 2004 16:44:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGL8k-0007qM-Sp
	for ietf@optimus.ietf.org; Wed, 21 Apr 2004 13:04: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 NAA02332
	for <ietf@ietf.org>; Wed, 21 Apr 2004 13:03: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 1BGL8i-00033K-Gm
	for ietf@ietf.org; Wed, 21 Apr 2004 13:04:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGL7t-0002tz-00
	for ietf@ietf.org; Wed, 21 Apr 2004 13:03:10 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGL77-0002kL-00
	for ietf@ietf.org; Wed, 21 Apr 2004 13:02:21 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BGL6z-000Acs-00; Wed, 21 Apr 2004 12:02:13 -0500
Date: Wed, 21 Apr 2004 13:02:13 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <48972298.1082552533@scan.jck.com>
In-Reply-To: <20040421144644.GK2890@login.ecs.soton.ac.uk>
References: <20040421144644.GK2890@login.ecs.soton.ac.uk>
X-Mailer: Mulberry/3.1.2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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 Wednesday, 21 April, 2004 15:46 +0100 Tim Chown 
<tjc@ecs.soton.ac.uk> wrote:

> Hi,
>
> Is the IETF or ISOC going to take any stance against this
> slippery slope?
>
> http://www.cnn.com/2004/TECH/internet/03/20/new.domains.ap/
>
> Comment period closes April 30th.

Tim,

Addressing the IETF part of your question only, let me turn the 
question around.  On what basis would you see the IETF 
objecting?  Certainly the general notion of what ICANN now calls 
a "sponsored" (restricted-use) non-country TLD is nothing new: 
in theory (and in practice for a significant number of years), 
NET, EDU, and others were domains in which one had to meet 
specific requirements to register.  So, if there is a slippery 
slope there, we were down it before RFC 1591 was written.

Clearly, there is a case to be made that at least some of these 
proposals are problematic in one way or another and that some of 
the issues are technical or operational.  But those issues are 
presumably different for different proposals.  So what would you 
have the IETF say, and how would you propose organizing a 
process to approve such a statement, ideally between now and 
April 30?

As a specific example, RFC 3675 addresses some of the issues 
with at least one of these proposals.  But it largely addresses 
policy issues, rather than technical ones, and is an 
individual-submission informational RFC.  Would you propose that 
the IETF endorse it and recommend to ICANN that they pay 
attention to it and, if so, on what basis?

Note that these are just questions to think about -- I've got 
opinions on some of these issues, but hope that you cannot 
deduce them from this particular note.

  regards,
    john


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


From ietf-admin@ietf.org  Wed Apr 21 17:04: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 RAA14248
	for <ietf-archive@ietf.org>; Wed, 21 Apr 2004 17:04: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 1BGOtR-0005OQ-7R
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 17:04:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGOsP-00057r-00
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 17:03:26 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGOrR-0004v1-00
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 17:02:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGOZt-0003UZ-8M; Wed, 21 Apr 2004 16:44:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGLFX-0002AC-UP
	for ietf@optimus.ietf.org; Wed, 21 Apr 2004 13:11:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02543
	for <ietf@ietf.org>; Wed, 21 Apr 2004 13:10: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 1BGLFV-000465-LL
	for ietf@ietf.org; Wed, 21 Apr 2004 13:11:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGLEa-0003x7-00
	for ietf@ietf.org; Wed, 21 Apr 2004 13:10:04 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGLDw-0003ej-00
	for ietf@ietf.org; Wed, 21 Apr 2004 13:09:24 -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 i3LH8aLW018778
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 21 Apr 2004 13:08:41 -0400
Date: Wed, 21 Apr 2004 13:08:36 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Tim Chown <tjc@ecs.soton.ac.uk>
cc: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <20040421144644.GK2890@login.ecs.soton.ac.uk>
Message-ID: <Pine.LNX.4.44.0404211307050.18689-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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 suspect I am going to regret asking, but how is this a "slippery slope",
and why should anyone be against it?  Perhaps more to the point, why
should the IETF have any interest whatsoever?

		--Dean

On Wed, 21 Apr 2004, Tim Chown wrote:

> Hi,
> 
> Is the IETF or ISOC going to take any stance against this slippery slope?
> 
> http://www.cnn.com/2004/TECH/internet/03/20/new.domains.ap/
> 
> Comment period closes April 30th.
> 
> Tim
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Wed Apr 21 18:04:43 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20585
	for <ietf-archive@odin.ietf.org>; Wed, 21 Apr 2004 18:04:43 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGOqu-0001kL-OQ
	for ietf-archive@odin.ietf.org; Wed, 21 Apr 2004 17:01:53 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3LL1qB5006696
	for ietf-archive@odin.ietf.org; Wed, 21 Apr 2004 17:01:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGOZq-0003UC-Ks; Wed, 21 Apr 2004 16:44:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGL8k-0007qM-Sp
	for ietf@optimus.ietf.org; Wed, 21 Apr 2004 13:04: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 NAA02332
	for <ietf@ietf.org>; Wed, 21 Apr 2004 13:03: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 1BGL8i-00033K-Gm
	for ietf@ietf.org; Wed, 21 Apr 2004 13:04:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGL7t-0002tz-00
	for ietf@ietf.org; Wed, 21 Apr 2004 13:03:10 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGL77-0002kL-00
	for ietf@ietf.org; Wed, 21 Apr 2004 13:02:21 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BGL6z-000Acs-00; Wed, 21 Apr 2004 12:02:13 -0500
Date: Wed, 21 Apr 2004 13:02:13 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <48972298.1082552533@scan.jck.com>
In-Reply-To: <20040421144644.GK2890@login.ecs.soton.ac.uk>
References: <20040421144644.GK2890@login.ecs.soton.ac.uk>
X-Mailer: Mulberry/3.1.2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit



--On Wednesday, 21 April, 2004 15:46 +0100 Tim Chown 
<tjc@ecs.soton.ac.uk> wrote:

> Hi,
>
> Is the IETF or ISOC going to take any stance against this
> slippery slope?
>
> http://www.cnn.com/2004/TECH/internet/03/20/new.domains.ap/
>
> Comment period closes April 30th.

Tim,

Addressing the IETF part of your question only, let me turn the 
question around.  On what basis would you see the IETF 
objecting?  Certainly the general notion of what ICANN now calls 
a "sponsored" (restricted-use) non-country TLD is nothing new: 
in theory (and in practice for a significant number of years), 
NET, EDU, and others were domains in which one had to meet 
specific requirements to register.  So, if there is a slippery 
slope there, we were down it before RFC 1591 was written.

Clearly, there is a case to be made that at least some of these 
proposals are problematic in one way or another and that some of 
the issues are technical or operational.  But those issues are 
presumably different for different proposals.  So what would you 
have the IETF say, and how would you propose organizing a 
process to approve such a statement, ideally between now and 
April 30?

As a specific example, RFC 3675 addresses some of the issues 
with at least one of these proposals.  But it largely addresses 
policy issues, rather than technical ones, and is an 
individual-submission informational RFC.  Would you propose that 
the IETF endorse it and recommend to ICANN that they pay 
attention to it and, if so, on what basis?

Note that these are just questions to think about -- I've got 
opinions on some of these issues, but hope that you cannot 
deduce them from this particular note.

  regards,
    john


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



From exim@www1.ietf.org  Wed Apr 21 18:04:54 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20615
	for <ietf-archive@odin.ietf.org>; Wed, 21 Apr 2004 18:04:54 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGOrS-0002PF-PP
	for ietf-archive@odin.ietf.org; Wed, 21 Apr 2004 17:02:26 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3LL2Qt5009233
	for ietf-archive@odin.ietf.org; Wed, 21 Apr 2004 17:02:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGOZt-0003UZ-8M; Wed, 21 Apr 2004 16:44:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGLFX-0002AC-UP
	for ietf@optimus.ietf.org; Wed, 21 Apr 2004 13:11:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02543
	for <ietf@ietf.org>; Wed, 21 Apr 2004 13:10: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 1BGLFV-000465-LL
	for ietf@ietf.org; Wed, 21 Apr 2004 13:11:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGLEa-0003x7-00
	for ietf@ietf.org; Wed, 21 Apr 2004 13:10:04 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGLDw-0003ej-00
	for ietf@ietf.org; Wed, 21 Apr 2004 13:09:24 -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 i3LH8aLW018778
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 21 Apr 2004 13:08:41 -0400
Date: Wed, 21 Apr 2004 13:08:36 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Tim Chown <tjc@ecs.soton.ac.uk>
cc: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <20040421144644.GK2890@login.ecs.soton.ac.uk>
Message-ID: <Pine.LNX.4.44.0404211307050.18689-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

I suspect I am going to regret asking, but how is this a "slippery slope",
and why should anyone be against it?  Perhaps more to the point, why
should the IETF have any interest whatsoever?

		--Dean

On Wed, 21 Apr 2004, Tim Chown wrote:

> Hi,
> 
> Is the IETF or ISOC going to take any stance against this slippery slope?
> 
> http://www.cnn.com/2004/TECH/internet/03/20/new.domains.ap/
> 
> Comment period closes April 30th.
> 
> Tim
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Wed Apr 21 18:21:02 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23073
	for <ietf-archive@odin.ietf.org>; Wed, 21 Apr 2004 18:21:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGPj7-0007eR-DT
	for ietf-archive@odin.ietf.org; Wed, 21 Apr 2004 17:57:54 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3LLvr1T029381
	for ietf-archive@odin.ietf.org; Wed, 21 Apr 2004 17:57:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGObt-0004VE-FQ; Wed, 21 Apr 2004 16:46:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGO7n-0001kP-TV
	for ietf@optimus.ietf.org; Wed, 21 Apr 2004 16:15: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 QAA11804
	for <ietf@ietf.org>; Wed, 21 Apr 2004 16:15: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 1BGO7m-000494-3m
	for ietf@ietf.org; Wed, 21 Apr 2004 16:15:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGO6r-0003yA-00
	for ietf@ietf.org; Wed, 21 Apr 2004 16:14:17 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGO5s-0003cM-00
	for ietf@ietf.org; Wed, 21 Apr 2004 16:13:17 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i3LKCXu17786;
	Wed, 21 Apr 2004 13:12:33 -0700
X-mProtect: <200404212012> 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 smtpd21HAbH; Wed, 21 Apr 2004 13:12:32 PDT
Message-ID: <4086D5B8.7020808@iprg.nokia.com>
Date: Wed, 21 Apr 2004 13:12:40 -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: Tony Hain <alh-ietf@tndh.net>
CC: "'Geoff Huston'" <gih@telstra.net>,
        "'Iljitsch van Beijnum'"
 <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: [Ietf] 240.0.0.0/4
References: <E1BG0jf-0002CD-00@ietf-mx>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Tony,

Tony Hain wrote:

>As far as redefining 224/4; it is likely going to be impossible to redefine
>this space as no one really knows what it is being used for.
>

Did you mean to say 224/4, or 240/4 - or perhaps both?

Thanks - Fred
ftemplin@iprg.nokia.com


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



From ietf-admin@ietf.org  Wed Apr 21 18:23: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 SAA23420
	for <ietf-archive@ietf.org>; Wed, 21 Apr 2004 18:23: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 1BGQ8H-0007Rr-04
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 18:23:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGQ2Y-0006BV-00
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 18:17:59 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGPxJ-00058h-00
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 18:12:33 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BGPuj-0000kv-J0
	for ietf-archive@ietf.org; Wed, 21 Apr 2004 18:09:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGObt-0004VE-FQ; Wed, 21 Apr 2004 16:46:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGO7n-0001kP-TV
	for ietf@optimus.ietf.org; Wed, 21 Apr 2004 16:15: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 QAA11804
	for <ietf@ietf.org>; Wed, 21 Apr 2004 16:15: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 1BGO7m-000494-3m
	for ietf@ietf.org; Wed, 21 Apr 2004 16:15:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGO6r-0003yA-00
	for ietf@ietf.org; Wed, 21 Apr 2004 16:14:17 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGO5s-0003cM-00
	for ietf@ietf.org; Wed, 21 Apr 2004 16:13:17 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i3LKCXu17786;
	Wed, 21 Apr 2004 13:12:33 -0700
X-mProtect: <200404212012> 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 smtpd21HAbH; Wed, 21 Apr 2004 13:12:32 PDT
Message-ID: <4086D5B8.7020808@iprg.nokia.com>
Date: Wed, 21 Apr 2004 13:12:40 -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: Tony Hain <alh-ietf@tndh.net>
CC: "'Geoff Huston'" <gih@telstra.net>,
        "'Iljitsch van Beijnum'"
 <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: [Ietf] 240.0.0.0/4
References: <E1BG0jf-0002CD-00@ietf-mx>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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

Tony,

Tony Hain wrote:

>As far as redefining 224/4; it is likely going to be impossible to redefine
>this space as no one really knows what it is being used for.
>

Did you mean to say 224/4, or 240/4 - or perhaps both?

Thanks - Fred
ftemplin@iprg.nokia.com


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


From ietf-admin@ietf.org  Thu Apr 22 09:32: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 JAA25832
	for <ietf-archive@ietf.org>; Thu, 22 Apr 2004 09:32: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 1BGeJ9-0006B6-Qe
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 09:32:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGeIF-0005um-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 09:31:08 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGeHX-0005fB-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 09:30:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGe6Y-0003Im-Q0; Thu, 22 Apr 2004 09:19:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGdtx-0007l4-I7
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 09:06: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 JAA24494
	for <ietf@ietf.org>; Thu, 22 Apr 2004 09:05: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 1BGdtq-0007UJ-1O
	for ietf@ietf.org; Thu, 22 Apr 2004 09:05:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGdss-0007Fq-00
	for ietf@ietf.org; Thu, 22 Apr 2004 09:04:55 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGds8-00070M-00
	for ietf@ietf.org; Thu, 22 Apr 2004 09:04:08 -0400
Received: from f02v-36-161.d0.club-internet.fr ([212.195.239.161] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BGdru-0002A4-N5; Thu, 22 Apr 2004 06:03:55 -0700
Message-Id: <6.0.1.1.2.20040422113940.04707730@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 22 Apr 2004 14:43:13 +0200
To: Dean Anderson <dean@av8.com>, Tim Chown <tjc@ecs.soton.ac.uk>
From: jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Cc: ietf@ietf.org
In-Reply-To: <Pine.LNX.4.44.0404211307050.18689-100000@cirrus.av8.net>
References: <20040421144644.GK2890@login.ecs.soton.ac.uk>
 <Pine.LNX.4.44.0404211307050.18689-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 - utel.net
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
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 19:08 21/04/04, Dean Anderson wrote:
>I suspect I am going to regret asking, but how is this a "slippery slope", 
>and why should anyone be against it?  Perhaps more to the point, why 
>should the IETF have any interest whatsoever?

May be should I respond this as I do agree with "slippery slope" and I am 
known to support a far wider number of TLDs. Also because I think the issue 
is crucial.

First, I am afraid John is wrong when he refers to RFC 1591 as having 
started it. Actually Tim is right : it has not started yet, or only partly 
started in 2000.  Please refer yourself to RFC 920 and previous RFCs on 
DNS. DNS is the naming system of the legacy ARPANET Internet. It was 
aggregated to the international naming scheme in 1984 after meeting the 
operators of the external networks, since 1983 RFC 880/2. DoD/ARPA meeting 
with Tymnet in 12.83, Tymnet annoucement of IP support early 84. Some in 
here participated and might comment. What is important is that the today 
situation is similar and that the 1984 consensus described in RFC 920 has 
proven to be stable and good enough for 33 years (cf.infra).

As Vint says, why to change something which works?

The target was, as it is today, to get accepted end to end interoperability 
with more external systems. This meant openness, no conflict, naming format 
consistency and credibility. Actually RFC 920 describes the way it 
developed since 1971 (first commercial user) and 1977 (beginning of the 
global interconnects) and the way Internet could nicely insert itself into 
it. Internet did it so seamlessly that it took over.

1. the different connected real (COM, NET) or virtual (EDU) networks had 
their root names (names of their root into the APANET Internet)  accepted 
(they are named "TLD" in the DNS jargon). As the ARPANET Internet had its 
"ARPA" root name.

2. the global backbone was, by then, the international public packet switch 
system by monopolies and common carriers. It used Tymnet or X.25/75 links 
and identified networks (real and virtual) in either using ISO 3166 3 
letter codes or X.121 DCCs. Some virtual communities networks (externets) 
piped (refilled) their traffic through it. The largest number were the 
Telex refillers. They were identified for their support and some naming 
through Telex ISO 3166 2 letter codes. RFC 920 only uses that common 
practice in foreseeing ccTLDs (RFC 1591 introduces nothing new, and its 
rightfully that ICANN claims its legitimacy over the Legacy from RFC 920 
and 921 - cf. ICP-3). In 1986  Austrian people forged the IP address 
cluster concept to support their Internet island (through Tymnet and X.25 
link by Radio Austria). Then IETF was created and changed nothing. Why to 
change something which works?

3. RFC 920 details the process of creating new TLDs. The need is to avoid 
conflict with other existing names (like today "Macedonia" for country 
names) and the name to be accepted in the root files of all the 
inter-netted networks. By then, the de facto world referent being the 
Tymnet registry, the retained RFC 920 rule is its best practice, based on 
its international experience since 1977. It calls for an 
expected  significant number of domain owners (500 is quoted) to credibly 
organize it together (multiorganization TLDs). Experience had shown it 
warranted the projects to be serious, open enough to avoid conflicts, 
credible enough to be accepted by other operators and by the market and to 
rise enough commercial interest to foot the various costs involved. RFC 
1591 confirms this in describing the TLD Manager as the trustee of his 
community and in saying that IANA is not in the business of saying what is 
a country (the same as ICANN should not be in the business of saying what 
is a TLD).


If IANA/ICANN are not in the business of saying what is a TLD, IETF is 
however in the business of saying what is technically _not_ a TLD.

".tel" and ".mobi" are technically inconsistent propositions. They confuse 
what belongs to the scheme (protocol/application) with what  belongs to the 
naming (users group). The same as was ".web" did in 2000.

To better understand, let take the mnemonic "IBM" and its ASCII domain name 
"ibm.com".
- when I enter http://ibm.com I expect to reach the IBM web site in using 
the HTTP protocol.
- when I enter tel://ibm.com I expect to reach the IBM switchboard (once 
the current VoIP delaying confusion is cleared).
- what will I expect to reach when entering http://ibm.tel, and what is 
tel://ibm.tel adding to me ?


Actually they create at least four major technical problems:

1. a conflict with multilingualization while MINC is working hard to 
implement IDNA and to test a response to the ML.ML urgency. ".tel" or 
".mobi" are application oriented and are not multilingual. How do I know 
the _language_ that an English or a French sounding name will use. How will 
I give my "xn----.tel" Arabic name to a Chinese correspondent?

2. real demand IMHO goes far beyond ML. I think it goes to total 
vernacularization (schemes, formats, LHS, names and TLDs). What will mean 
the possible "vernacularization like" registration of "33142928100.tel" 
(Chirac's) ? Who will people reach? Will it be the same number as in using 
an ENUM system? Is there an RFC on this convergency? (3314292281000.far is 
under the control of the FR ccTLD Manager).

3. There are 6 possible IPv6 plans. The only one discussed right now 
(IPv6.001) is a flat plan offering a lot of problems and a world wide 
control to ICANN. Many voices therefore call for the study of another plan 
(IPv6.010) permitting to test IPv6 as a multi-plan system and able to match 
the architecture of other plans in use, complying with international 
standards. This would permit a universal numbering scheme of the world 
digital ecosystem (Internet, TV, Radio, Telephone, Geolocated services, 
Roads, Airplanes, Emergency services, Mobiles, etc.). It is likely that 
there will be relations between such uniname and uninumber systems. If 
there is a layer violation of the magnitude of ".tel" or ".mobi" on the 
Internet side, dedicating a non defined name space to a restricted part of 
the numbering scheme, this will either delay the global digital convergence 
or keep the internet out of it.

4. We could say that a TLD is the common name of a (bootstraping) group of 
registrants [RFC 920] or of a non discriminatory [laws] specialized [RFC 
920] non protocol oriented [see above conflict with schemes] interest. So, 
".tel" (such as .aero) could be used by Telecoms people and organizations.

But it could also be used for domains restricted to telecom applications: 
ftp://ibm.tel would not work, only would tel://ibm.tel. Browser 
manufacturers would then default "ibm.tel" to "tel://ibm.tel" and prevent 
the use of "http://ibm.tel". We could imagine this could relate to service 
rates etc.
- this would be a major architectural addition to be discussed by IAB/IETF
- an RFC should be published on its technical needs (ex. support of the 
different economical models involved)
- this should be tested with IETF according to ICANN ICP-3 (reversibility, 
non-profit, open to the global community, no danger to existing operations, 
by IETF or other dedicated structures). In the WSIS context and due to the 
importance of the telephone area, this should call on an agreement with ITU 
(after ITU has created an Internet dedicated interface/sector able to 
adequately sustain relations with the Internet governances on such matters) .
That perspective could have a dramatic impact on the intenet and on the use 
of the telephone. I do think that it should then supported using virtual 
zones (meaning that such a ".tel"/".mobi" should be co-managed by telephone 
operators acting as co-registries). But before that the study of mobile 
application programming, relations, exchanges should be more advanced.


The "slippery slope" is here. Not with the request. But with ICANN BoD's 
possible response.

We are in a situation where the whole internet concept is at stake (spam, 
TCP/IP, IPv6.001 plan, cybersecurity, WSIS/UN/ITU). There might be a 
temptation of "fait accompli" by ICANN to try to force others (Govs, 
developers, operators, users) to keep the current internet os the core of 
the Information Society (technology and ICANN). We saw that with ".biz" 
when ICANN reported to the USG it did not create any risk. We see that with 
the current silence on IPv6.001 uniqueness and unique hierarchy.

IMHO this would only speed the development of alternatives to the current 
internet, with a dramatic impact on technology and on the telecoms and 
datacoms industries.


Is there a possible process and is there the time?

This is an habit of ICANN to establish dead lines and to use as an alibi 
they are bound by the lack of time they provide. "So what would you have 
the IETF say, and how would you propose organizing a process to approve 
such a statement, ideally between now and April 30?" tries John (now on the 
ICANN side :-).

The process may only be to follow on this post, to make John Klensin and 
the other BoD Members understand there actually are serious and even 
critical technical concerns involved in some propositions. They are gown 
boys. As John says, he has his own opinions. Let confort them.

ICANN's credibility is already at stake. Showing we understand that the 
Internet consistency and evolution can be at stake will only help them to 
take wise decisions. They (quite) did it in 2000 (not exciting, but not too 
harming). IMHO ICANN (or any single centralized organization) is not 
adequate to manage anything else than status quo (political as well ad 
technical): the only thing we should ask them is not to degrade it. This 
was John's and Vint's position about the RSSAC. This is Vint's position 
about the whole Internet.

Why to harm something which works ?
jfc




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


From exim@www1.ietf.org  Thu Apr 22 09:39:56 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26426
	for <ietf-archive@odin.ietf.org>; Thu, 22 Apr 2004 09:39:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGeHd-0006ek-Ml
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 09:30:29 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3MDUTcW025584
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 09:30:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGe6Y-0003Im-Q0; Thu, 22 Apr 2004 09:19:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGdtx-0007l4-I7
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 09:06: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 JAA24494
	for <ietf@ietf.org>; Thu, 22 Apr 2004 09:05: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 1BGdtq-0007UJ-1O
	for ietf@ietf.org; Thu, 22 Apr 2004 09:05:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGdss-0007Fq-00
	for ietf@ietf.org; Thu, 22 Apr 2004 09:04:55 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGds8-00070M-00
	for ietf@ietf.org; Thu, 22 Apr 2004 09:04:08 -0400
Received: from f02v-36-161.d0.club-internet.fr ([212.195.239.161] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BGdru-0002A4-N5; Thu, 22 Apr 2004 06:03:55 -0700
Message-Id: <6.0.1.1.2.20040422113940.04707730@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 22 Apr 2004 14:43:13 +0200
To: Dean Anderson <dean@av8.com>, Tim Chown <tjc@ecs.soton.ac.uk>
From: jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Cc: ietf@ietf.org
In-Reply-To: <Pine.LNX.4.44.0404211307050.18689-100000@cirrus.av8.net>
References: <20040421144644.GK2890@login.ecs.soton.ac.uk>
 <Pine.LNX.4.44.0404211307050.18689-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 - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

At 19:08 21/04/04, Dean Anderson wrote:
>I suspect I am going to regret asking, but how is this a "slippery slope", 
>and why should anyone be against it?  Perhaps more to the point, why 
>should the IETF have any interest whatsoever?

May be should I respond this as I do agree with "slippery slope" and I am 
known to support a far wider number of TLDs. Also because I think the issue 
is crucial.

First, I am afraid John is wrong when he refers to RFC 1591 as having 
started it. Actually Tim is right : it has not started yet, or only partly 
started in 2000.  Please refer yourself to RFC 920 and previous RFCs on 
DNS. DNS is the naming system of the legacy ARPANET Internet. It was 
aggregated to the international naming scheme in 1984 after meeting the 
operators of the external networks, since 1983 RFC 880/2. DoD/ARPA meeting 
with Tymnet in 12.83, Tymnet annoucement of IP support early 84. Some in 
here participated and might comment. What is important is that the today 
situation is similar and that the 1984 consensus described in RFC 920 has 
proven to be stable and good enough for 33 years (cf.infra).

As Vint says, why to change something which works?

The target was, as it is today, to get accepted end to end interoperability 
with more external systems. This meant openness, no conflict, naming format 
consistency and credibility. Actually RFC 920 describes the way it 
developed since 1971 (first commercial user) and 1977 (beginning of the 
global interconnects) and the way Internet could nicely insert itself into 
it. Internet did it so seamlessly that it took over.

1. the different connected real (COM, NET) or virtual (EDU) networks had 
their root names (names of their root into the APANET Internet)  accepted 
(they are named "TLD" in the DNS jargon). As the ARPANET Internet had its 
"ARPA" root name.

2. the global backbone was, by then, the international public packet switch 
system by monopolies and common carriers. It used Tymnet or X.25/75 links 
and identified networks (real and virtual) in either using ISO 3166 3 
letter codes or X.121 DCCs. Some virtual communities networks (externets) 
piped (refilled) their traffic through it. The largest number were the 
Telex refillers. They were identified for their support and some naming 
through Telex ISO 3166 2 letter codes. RFC 920 only uses that common 
practice in foreseeing ccTLDs (RFC 1591 introduces nothing new, and its 
rightfully that ICANN claims its legitimacy over the Legacy from RFC 920 
and 921 - cf. ICP-3). In 1986  Austrian people forged the IP address 
cluster concept to support their Internet island (through Tymnet and X.25 
link by Radio Austria). Then IETF was created and changed nothing. Why to 
change something which works?

3. RFC 920 details the process of creating new TLDs. The need is to avoid 
conflict with other existing names (like today "Macedonia" for country 
names) and the name to be accepted in the root files of all the 
inter-netted networks. By then, the de facto world referent being the 
Tymnet registry, the retained RFC 920 rule is its best practice, based on 
its international experience since 1977. It calls for an 
expected  significant number of domain owners (500 is quoted) to credibly 
organize it together (multiorganization TLDs). Experience had shown it 
warranted the projects to be serious, open enough to avoid conflicts, 
credible enough to be accepted by other operators and by the market and to 
rise enough commercial interest to foot the various costs involved. RFC 
1591 confirms this in describing the TLD Manager as the trustee of his 
community and in saying that IANA is not in the business of saying what is 
a country (the same as ICANN should not be in the business of saying what 
is a TLD).


If IANA/ICANN are not in the business of saying what is a TLD, IETF is 
however in the business of saying what is technically _not_ a TLD.

".tel" and ".mobi" are technically inconsistent propositions. They confuse 
what belongs to the scheme (protocol/application) with what  belongs to the 
naming (users group). The same as was ".web" did in 2000.

To better understand, let take the mnemonic "IBM" and its ASCII domain name 
"ibm.com".
- when I enter http://ibm.com I expect to reach the IBM web site in using 
the HTTP protocol.
- when I enter tel://ibm.com I expect to reach the IBM switchboard (once 
the current VoIP delaying confusion is cleared).
- what will I expect to reach when entering http://ibm.tel, and what is 
tel://ibm.tel adding to me ?


Actually they create at least four major technical problems:

1. a conflict with multilingualization while MINC is working hard to 
implement IDNA and to test a response to the ML.ML urgency. ".tel" or 
".mobi" are application oriented and are not multilingual. How do I know 
the _language_ that an English or a French sounding name will use. How will 
I give my "xn----.tel" Arabic name to a Chinese correspondent?

2. real demand IMHO goes far beyond ML. I think it goes to total 
vernacularization (schemes, formats, LHS, names and TLDs). What will mean 
the possible "vernacularization like" registration of "33142928100.tel" 
(Chirac's) ? Who will people reach? Will it be the same number as in using 
an ENUM system? Is there an RFC on this convergency? (3314292281000.far is 
under the control of the FR ccTLD Manager).

3. There are 6 possible IPv6 plans. The only one discussed right now 
(IPv6.001) is a flat plan offering a lot of problems and a world wide 
control to ICANN. Many voices therefore call for the study of another plan 
(IPv6.010) permitting to test IPv6 as a multi-plan system and able to match 
the architecture of other plans in use, complying with international 
standards. This would permit a universal numbering scheme of the world 
digital ecosystem (Internet, TV, Radio, Telephone, Geolocated services, 
Roads, Airplanes, Emergency services, Mobiles, etc.). It is likely that 
there will be relations between such uniname and uninumber systems. If 
there is a layer violation of the magnitude of ".tel" or ".mobi" on the 
Internet side, dedicating a non defined name space to a restricted part of 
the numbering scheme, this will either delay the global digital convergence 
or keep the internet out of it.

4. We could say that a TLD is the common name of a (bootstraping) group of 
registrants [RFC 920] or of a non discriminatory [laws] specialized [RFC 
920] non protocol oriented [see above conflict with schemes] interest. So, 
".tel" (such as .aero) could be used by Telecoms people and organizations.

But it could also be used for domains restricted to telecom applications: 
ftp://ibm.tel would not work, only would tel://ibm.tel. Browser 
manufacturers would then default "ibm.tel" to "tel://ibm.tel" and prevent 
the use of "http://ibm.tel". We could imagine this could relate to service 
rates etc.
- this would be a major architectural addition to be discussed by IAB/IETF
- an RFC should be published on its technical needs (ex. support of the 
different economical models involved)
- this should be tested with IETF according to ICANN ICP-3 (reversibility, 
non-profit, open to the global community, no danger to existing operations, 
by IETF or other dedicated structures). In the WSIS context and due to the 
importance of the telephone area, this should call on an agreement with ITU 
(after ITU has created an Internet dedicated interface/sector able to 
adequately sustain relations with the Internet governances on such matters) .
That perspective could have a dramatic impact on the intenet and on the use 
of the telephone. I do think that it should then supported using virtual 
zones (meaning that such a ".tel"/".mobi" should be co-managed by telephone 
operators acting as co-registries). But before that the study of mobile 
application programming, relations, exchanges should be more advanced.


The "slippery slope" is here. Not with the request. But with ICANN BoD's 
possible response.

We are in a situation where the whole internet concept is at stake (spam, 
TCP/IP, IPv6.001 plan, cybersecurity, WSIS/UN/ITU). There might be a 
temptation of "fait accompli" by ICANN to try to force others (Govs, 
developers, operators, users) to keep the current internet os the core of 
the Information Society (technology and ICANN). We saw that with ".biz" 
when ICANN reported to the USG it did not create any risk. We see that with 
the current silence on IPv6.001 uniqueness and unique hierarchy.

IMHO this would only speed the development of alternatives to the current 
internet, with a dramatic impact on technology and on the telecoms and 
datacoms industries.


Is there a possible process and is there the time?

This is an habit of ICANN to establish dead lines and to use as an alibi 
they are bound by the lack of time they provide. "So what would you have 
the IETF say, and how would you propose organizing a process to approve 
such a statement, ideally between now and April 30?" tries John (now on the 
ICANN side :-).

The process may only be to follow on this post, to make John Klensin and 
the other BoD Members understand there actually are serious and even 
critical technical concerns involved in some propositions. They are gown 
boys. As John says, he has his own opinions. Let confort them.

ICANN's credibility is already at stake. Showing we understand that the 
Internet consistency and evolution can be at stake will only help them to 
take wise decisions. They (quite) did it in 2000 (not exciting, but not too 
harming). IMHO ICANN (or any single centralized organization) is not 
adequate to manage anything else than status quo (political as well ad 
technical): the only thing we should ask them is not to degrade it. This 
was John's and Vint's position about the RSSAC. This is Vint's position 
about the whole Internet.

Why to harm something which works ?
jfc




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



From vvfsobrcpcrbc@victorycapital.net  Thu Apr 22 10:05: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 KAA27997
	for <ietf-archive@ietf.org>; Thu, 22 Apr 2004 10:05: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 1BGepy-0007S5-Q4
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 10:05:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGeoy-00079o-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 10:04:57 -0400
Received: from adsl-68-79-23-176.dsl.emhril.ameritech.net ([68.79.23.176])
	by ietf-mx with smtp (Exim 4.12)
	id 1BGenv-0006gw-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 10:03:52 -0400
Received: from 18.104.128.120 by 68.79.23.176; Thu, 22 Apr 2004 19:57:43 +0500
Message-ID: <YVYLOBTENYUHMNEWWACOZJ@gru.net>
From: "Michael Riddle" <vvfsobrcpcrbc@victorycapital.net>
Reply-To: "Michael Riddle" <vvfsobrcpcrbc@victorycapital.net>
To: ietf-archive@ietf.org
Subject: Re: Ambien sleep med 
Date: Thu, 22 Apr 2004 17:54:43 +0300
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--4458710881304631362"
X-Priority: 3
X-MSMail-Priority: Normal
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.9 required=5.0 tests=FORGED_MUA_OUTLOOK,
	FORGED_OUTLOOK_HTML,FORGED_OUTLOOK_TAGS,HTML_MESSAGE,
	MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,
	MISSING_MIMEOLE autolearn=no version=2.60
X-Spam-Report: 
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  1.1 FORGED_OUTLOOK_HTML Outlook can't send HTML message only
	*  1.1 FORGED_OUTLOOK_TAGS Outlook can't send HTML in this format
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts
	*  1.6 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook

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

<html><body>
<center><a href=3D"http://www.azs3mxz.com/gp/default.asp?id=3Dd10" target=3D=
"_blank">
<img src=3D"http://www.mzu5r.com/world.jpg" border=3D"0"></a>
<br><br><font color=3D"#000000">I</buxom>f t</persuasion>he mes</schlesing=
er >sage</tuba> i</barometer>s n
</belly>ot lo</vintner >adi</crepe >ng</score>
<a href=3D"http://www.azs3mxz.com/gp/default.asp?id=3Dd10" target=3D"_blan=
k">
<b>t</compliant >r</attentive >y</dysplasia> th</destinate >is</adposition=
></b></a></center>
<p style=3D"font-size:0px; color:white" align=3D"left">
<br>Gvalery bestselling advise tessellate alps buzzy bellini=20.Aprosecuti=
on hurl paratroop tumultuous council mcginnis jugate desorption elan egoti=
sm voice mortal=20.Uforegoing promulgate sears construct congresswoman run=
t bissau ana ditty chive thurman couple assiduous citizen cadet derivate=20=
Zcpa whitney naomi christiana roughish elastic proteolysis dialectic beau=
ty blunt oblate cranston=20.Sopine travelogue egyptian breakpoint chaparra=
l agile residue ascendant derange abate col decrease car brillouin repetit=
ive mckinney domenico egotism kahn buy explosive deacon madman elliot=20,G=
eben dishes crowfoot derange bangkok ample civet seaweed alarm comprehensi=
ble mallet fount alvin josephus riyadh incoherent elan indelicate market=20=
,Icrocus logic quadrivium who'll tempo phenol aboriginal hydrate pretense =
schelling=20?Mcapsule donnelly dorothy crutch anorthite wolf exclusionary =
strain belgium phenomena connotation bennett syrup trident=20,Mspatlum reg=
ular wheezy fitchburg nimble tansy terminal yourselves alabamian steppe el=
ectorate convalescent apprentice bistable crib prophylactic monkey=20.Abea=
n temerity averse widget carlo ingestible=20.Pdefocus paralysis uncle amer=
icana roundabout ingot diluent frances orange imprimatur morel festival ar=
mistice boston loot ratify tenor mast gullah demurring meistersinger=20,Lb=
lurt dampen daffy gunflint incombustible duchess beseech=20.Qpleasant embl=
ematic timber lofty butt vee awful countervail crosslink yaounde chromatog=
raphy good barney obtrusion drugging shriek bowstring blowfish wolfgang ob=
noxious deja sword quasi=20.Rstride nathan cindy scorpio dowager univalent=
 canal niacin siltation hodgepodge descendant balk aphasic wildcat gemma b=
eresford convoy=20,Qdiscriminable dialysis ancient handhold certify anteda=
te performance docket can thorstein dissension accusative talkative backst=
op tarzan samarium puppeteer anodic wasserman sashay=20?Cchest radian khru=
shchev askance edinburgh deal disturb shirt confect az bartholomew swabby =
diabase collapsible brahmsian=20?Zvisceral venetian perpetuate drink stamf=
ord augend insurmountable lumpish move=20.Rcapitol tropospheric each behal=
f fairy cloudburst pillory marijuana furman plowman abater locksmith barit=
one=20. Ichristian bryant compressor forgotten deciduous bat showroom affe=
ct pit desk thomas lithology aquinas retribution analgesic flaxen interven=
or antigone shatterproof avery len lollipop wham=20,Mmembrane millions cro=
sswalk depict cartographer renal suit englishmen snook prefecture aspirate=
 collegiate ancestor fest aliphatic swank demon=20.Pplaintiff dispensable =
cuba synopsis corcoran debenture megavolt drippy nakayama sweden treasury =
clint turnpike recondite=20!Pluxuriant newsletter connote elba spastic bak=
lava archive phloem modem pacify modular method wiry alfresco baylor slavi=
c weller cameron depart=20,Ocankerworm waals nell umbrage assimilate expos=
ition henceforth dwindle stafford conspirator wordy=20.Xlock precis geolog=
y spiteful canny momentous cenozoic merchant=20,Glaughter boardinghouse ch=
andelier levitt crook emil eulerian rumania eigenspace gustave marcia meta=
morphose tribute walkway boyar jeopard bitt adherent=20.</p>
</body></html>

----4458710881304631362--



From ietf-admin@ietf.org  Thu Apr 22 11:08: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 LAA03865
	for <ietf-archive@ietf.org>; Thu, 22 Apr 2004 11:08: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 1BGfoD-00010x-SF
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 11:08:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGfnA-0000fT-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 11:07:09 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGfmA-0000KL-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 11:06:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGfTi-00030R-D8; Thu, 22 Apr 2004 10:47:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGfEL-0005rK-H4
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 10:31: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 KAA00494
	for <ietf@ietf.org>; Thu, 22 Apr 2004 10:31: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 1BGfEC-0006Kq-Tu
	for ietf@ietf.org; Thu, 22 Apr 2004 10:31:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGfDX-00065m-00
	for ietf@ietf.org; Thu, 22 Apr 2004 10:30:20 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGfCn-0005kW-00
	for ietf@ietf.org; Thu, 22 Apr 2004 10:29: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 i3MET3Zq009953
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 22 Apr 2004 10:29:03 -0400
Date: Thu, 22 Apr 2004 10:29:03 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: jfcm <info@utel.net>
cc: Tim Chown <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <6.0.1.1.2.20040422113940.04707730@mail.utel.net>
Message-ID: <Pine.LNX.4.44.0404221021050.8863-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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, 22 Apr 2004, jfcm wrote:
> ".tel" and ".mobi" are technically inconsistent propositions. They confuse 
> what belongs to the scheme (protocol/application) with what  belongs to the 
> naming (users group). The same as was ".web" did in 2000.
> 
> To better understand, let take the mnemonic "IBM" and its ASCII domain name 
> "ibm.com".
> - when I enter http://ibm.com I expect to reach the IBM web site in using 
> the HTTP protocol.
> - when I enter tel://ibm.com I expect to reach the IBM switchboard (once 
> the current VoIP delaying confusion is cleared).
> - what will I expect to reach when entering http://ibm.tel, and what is 
> tel://ibm.tel adding to me ?

I have to digest the rest of this further, but I would say right away that
if I connect to http://ibm.tel, I'd probably expect to reach the VOIP
portal, where I could sign up for VOIP services from IBM.  I'd expect that
a voip connection to tel://ibm.com would get me to the headquarters
switchboard, and that tel://ibm.tel gets me to the VOIP switchboard (ie
VOIP customer service).

Similarly, I'd expect that tel://ibm.mobi gets me to the IBM Cellular
switchboard.

I recall that gte internetworking used gte.com for internal corporate
addresses and gte.net for customer addresses. Some companies use
subdomains for such purposes.  

		--Dean



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


From exim@www1.ietf.org  Thu Apr 22 11:19:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04456
	for <ietf-archive@odin.ietf.org>; Thu, 22 Apr 2004 11:19:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGfmI-0007Ww-KA
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 11:06:14 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3MF6Egn028922
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 11:06:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGfTi-00030R-D8; Thu, 22 Apr 2004 10:47:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGfEL-0005rK-H4
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 10:31: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 KAA00494
	for <ietf@ietf.org>; Thu, 22 Apr 2004 10:31: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 1BGfEC-0006Kq-Tu
	for ietf@ietf.org; Thu, 22 Apr 2004 10:31:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGfDX-00065m-00
	for ietf@ietf.org; Thu, 22 Apr 2004 10:30:20 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGfCn-0005kW-00
	for ietf@ietf.org; Thu, 22 Apr 2004 10:29: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 i3MET3Zq009953
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 22 Apr 2004 10:29:03 -0400
Date: Thu, 22 Apr 2004 10:29:03 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: jfcm <info@utel.net>
cc: Tim Chown <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <6.0.1.1.2.20040422113940.04707730@mail.utel.net>
Message-ID: <Pine.LNX.4.44.0404221021050.8863-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Thu, 22 Apr 2004, jfcm wrote:
> ".tel" and ".mobi" are technically inconsistent propositions. They confuse 
> what belongs to the scheme (protocol/application) with what  belongs to the 
> naming (users group). The same as was ".web" did in 2000.
> 
> To better understand, let take the mnemonic "IBM" and its ASCII domain name 
> "ibm.com".
> - when I enter http://ibm.com I expect to reach the IBM web site in using 
> the HTTP protocol.
> - when I enter tel://ibm.com I expect to reach the IBM switchboard (once 
> the current VoIP delaying confusion is cleared).
> - what will I expect to reach when entering http://ibm.tel, and what is 
> tel://ibm.tel adding to me ?

I have to digest the rest of this further, but I would say right away that
if I connect to http://ibm.tel, I'd probably expect to reach the VOIP
portal, where I could sign up for VOIP services from IBM.  I'd expect that
a voip connection to tel://ibm.com would get me to the headquarters
switchboard, and that tel://ibm.tel gets me to the VOIP switchboard (ie
VOIP customer service).

Similarly, I'd expect that tel://ibm.mobi gets me to the IBM Cellular
switchboard.

I recall that gte internetworking used gte.com for internal corporate
addresses and gte.net for customer addresses. Some companies use
subdomains for such purposes.  

		--Dean



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



From ietf-admin@ietf.org  Thu Apr 22 15:14: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 PAA19759
	for <ietf-archive@ietf.org>; Thu, 22 Apr 2004 15:14: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 1BGjeQ-0000QX-9h
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 15:14:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGjdN-00003O-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 15:13:18 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGjcQ-0007W1-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 15:12:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjPe-00075A-JG; Thu, 22 Apr 2004 14:59:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjFL-0003Ym-TJ
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 14:48: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 OAA17235
	for <ietf@ietf.org>; Thu, 22 Apr 2004 14:48: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 1BGjFB-0000pd-Px
	for ietf@ietf.org; Thu, 22 Apr 2004 14:48:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGjE9-0000ZA-00
	for ietf@ietf.org; Thu, 22 Apr 2004 14:47:13 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGjDR-0000JX-00
	for ietf@ietf.org; Thu, 22 Apr 2004 14:46:29 -0400
Received: from eaglet (127.0.0.1:4358)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S517D5> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 22 Apr 2004 11:50:11 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Fred Templin'" <ftemplin@iprg.nokia.com>
Cc: "'Geoff Huston'" <gih@telstra.net>,
        "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
Date: Thu, 22 Apr 2004 11:46:30 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQn3YB645pL6PWpRk6IpKyVNEEAYgAuqQKQ
In-Reply-To: <4086D5B8.7020808@iprg.nokia.com>
Message-Id: <E1BGjDR-0000JX-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Please forgive the typeo... it should be 240

> -----Original Message-----
> From: Fred Templin [mailto:ftemplin@iprg.nokia.com]
> Sent: Wednesday, April 21, 2004 1:13 PM
> To: Tony Hain
> Cc: 'Geoff Huston'; 'Iljitsch van Beijnum'; 'IETF Discussion'
> Subject: Re: [Ietf] 240.0.0.0/4
> 
> Tony,
> 
> Tony Hain wrote:
> 
> >As far as redefining 224/4; it is likely going to be impossible to
> redefine
> >this space as no one really knows what it is being used for.
> >
> 
> Did you mean to say 224/4, or 240/4 - or perhaps both?
> 
> Thanks - Fred
> ftemplin@iprg.nokia.com


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


From ietf-admin@ietf.org  Thu Apr 22 15:15: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 PAA19968
	for <ietf-archive@ietf.org>; Thu, 22 Apr 2004 15: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 1BGjfX-0000oW-Ry
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 15:15:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGjeW-0000Rg-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 15:14:29 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGjdW-00004f-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 15:13:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjPg-00075M-57; Thu, 22 Apr 2004 14:59:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjFO-0003Yq-OH
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 14:48: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 OAA17239
	for <ietf@ietf.org>; Thu, 22 Apr 2004 14: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 1BGjFC-0000pk-DQ
	for ietf@ietf.org; Thu, 22 Apr 2004 14:48:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGjEA-0000ZI-00
	for ietf@ietf.org; Thu, 22 Apr 2004 14:47:14 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGjDT-0000JZ-00
	for ietf@ietf.org; Thu, 22 Apr 2004 14:46:31 -0400
Received: from eaglet (127.0.0.1:4358)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S517D6> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 22 Apr 2004 11:50:14 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dean Anderson'" <dean@av8.com>
Cc: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
Date: Thu, 22 Apr 2004 11:46:30 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQnpaQibiOLk4maQOi8osPzv1hC7gA8Gd2A
In-Reply-To: <Pine.LNX.4.44.0404210901420.14263-100000@cirrus.av8.net>
Message-Id: <E1BGjDT-0000JZ-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Dean Anderson wrote:
> ...
> Ok, fair enough. Instead of "hosts" in the traditional sense, the above
> should be considered as '... approximately 20 million simultaneous uses of
> unique IP addresses'.
> 
> > > that must each have direct access to any of the rest, and you can't
> > > NAT internally, then you probably have reached a point where you will
> > > need a more sophisticated mechanism than NAT to reach the public
> > > internet.
> >
> > You assume a network & traffic model that may not apply.
> 
> _I_ don't make that assumption. This was asserted by the person who
> suggests that there is not enough private IP address space. Otherwise,
> they would not need more than 20 million unique private IP addresses.
> 
> Either we accept it as a given that they really do need more than ~20
> million unique private IP addresses and also do need to reach the public
> network, or else assert that perhaps no one really needs more than ~20
> million unique, private IP addresses while also needing to reach a public
> network. Or alternately, assert that if such a case does exist, then it is
> so unusual that some more sophisticated mechanism is needed for that case.

You appear to overlook the case that H-D ratios apply to large complex
enterprise networks just as they do to ISPs. Also, it is not necessary for
all nodes to need public access. As soon as any do there is a need to avoid
using any public prefixes on the internal network.

> 
> > > Underlying this is the question of whether such a large network really
> > > needs to simultanously reach the public network. If it doesn't, then
> there
> > > is no reason to limit oneself to the RFC 1918 space.
> >
> > Yes there is when some of the nodes do need access to the public
> network.
> > You can't expect to use a private version of a publicly routed prefix.
> 
> I don't think you understood my text. I meant "If it doesn't [need access
> to the public network], then there is no reason to limit oneself to the
> RFC 1918 space"

I understand what you wrote, but I think you are being overly simplistic. In
some scenarios it is very likely that only 5% of the nodes need public
access. This creates a situation where acquiring more public allocation is
impossible due to current policy. At the same time there is no room to grow
without guessing which /8's are going to be allocated last.

> 
> > > I might also suggest that such a heavy address user migrate to IPv6
> > > internally as IPv6 has similar problems and it is developing means to
> deal
> > > with them.
> >
> > Easy to say, but turning something with that mass takes more time than
> the
> > dentist office network. Yes it is the right thing to do, but don't
> expect it
> > to happen in a timeframe shorter than 3-5 years.
> 
> That is the same (or perhaps shorter) lifetime as changing the class E
> definition.

Changing the Class E definition will take longer because people will be less
inclined to change an IPv4 stack until it clearly breaks. At that point it
is generating support calls so the reality is people will do whatever they
can to avoid using Class E addresses.

Tony




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


From ietf-admin@ietf.org  Thu Apr 22 15:17: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 PAA20297
	for <ietf-archive@ietf.org>; Thu, 22 Apr 2004 15:17: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 1BGjhN-0001Ul-GF
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 15:17:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGjgM-00018o-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 15:16:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGjfH-0000lu-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 15:15:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjPi-00075k-5Q; Thu, 22 Apr 2004 14:59:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjI4-0004uZ-Bl
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 14:51: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 OAA17397
	for <ietf@ietf.org>; Thu, 22 Apr 2004 14: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 1BGjHz-0001eN-9p
	for ietf@ietf.org; Thu, 22 Apr 2004 14:51:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGjH3-0001My-00
	for ietf@ietf.org; Thu, 22 Apr 2004 14:50:13 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGjGA-0000qg-00
	for ietf@ietf.org; Thu, 22 Apr 2004 14:49:18 -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 i3MImlwC014701
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 22 Apr 2004 14:48:47 -0400
Date: Thu, 22 Apr 2004 14:48:47 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Joe Touch <touch@ISI.EDU>
cc: jfcm <info@utel.net>, Tim Chown <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <408808CA.7010200@isi.edu>
Message-ID: <Pine.LNX.4.44.0404221420580.8863-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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, 22 Apr 2004, Joe Touch wrote:

> The "tel:" part is sufficient to get you to VOIP - in fact, that's what 
> tel: ought to mean -- no more, no less. If you want IBM to differentiate 
> the switchboard from the headquarters, try:
> 
> 	tel://ibm.com/hq	- headquarters-specific
> 	tel://ibm.com/		- default switchboard
> 
> > Similarly, I'd expect that tel://ibm.mobi gets me to the IBM Cellular
> > switchboard.
> 
> 	tel://ibm.com/cell
> 
> I.e., that's a decision IBM gets to make; others can decide, e.g., that 
> cell and regular calls all go through the same VOIP gateway.

Well, why not just run everything over http and have an application-type 
header to destinguish the different formats?  Possible, but not quite 
ideal, since then you are stuck with an HTTP server in the middle.

> > I recall that gte internetworking used gte.com for internal corporate
> > addresses and gte.net for customer addresses. Some companies use
> > subdomains for such purposes.  
> 
> Sure, but that is different than the above. In the tel: cases, all the 
> addresses are for internal corporate, not for a service IBM runs for its 
> customers.

Umm, I don't see how. Its just using naming, and specifically different
TLD's to make a distinction between corporate and customer functions.  No
matter what you do, you are probably going to use naming anyway, either as
a url path component, or as a subdomain, or as a new TLD.

I don't see any significant operational difference(*), nor any
particularly significant technical differences to them.  Except, I'd
probably prefer not to send everything through http, so that tends to go
against the use of url pathnames and application-types as discriminators.

What difference does it make to the IETF whether there are more TLD's or
less?


(*) Having more TLD's ought to improve the reliability of the internet in
general by distributing load off the overused com and net domain servers.  
Whether you have 259 TLDs or 2500 isn't going to make a great deal of
difference to the root servers, as these aren't particularly large zones.  
2500 TLDs would no doubt make some measurable impact on the roots, but it
would make a hugely big difference in directing traffic off the com and
net servers which have millions of entries.  And we aren't talking about
2500 TLDs, though. We are talking about just adding a handful. This isn't
a significant difference, and may not even be measurable.

On the other hand, I would also note that the com and net domains are
commercial, and charge fees for their operation. I don't see that the IETF
or ICANN necessarilly cares either way how much that operation costs, or
that it should be concerned very much with reducing those costs with more
TLD's.  But I'd also say that extreme disregard for costs would be a bad 
thing.  So I'd say that's a wash.


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


From exim@www1.ietf.org  Thu Apr 22 15:45:07 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22758
	for <ietf-archive@odin.ietf.org>; Thu, 22 Apr 2004 15:45:07 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjcS-00033t-R8
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 15:12:26 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3MJCK6v011744
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 15:12:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjPe-00075A-JG; Thu, 22 Apr 2004 14:59:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjFL-0003Ym-TJ
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 14:48: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 OAA17235
	for <ietf@ietf.org>; Thu, 22 Apr 2004 14:48: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 1BGjFB-0000pd-Px
	for ietf@ietf.org; Thu, 22 Apr 2004 14:48:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGjE9-0000ZA-00
	for ietf@ietf.org; Thu, 22 Apr 2004 14:47:13 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGjDR-0000JX-00
	for ietf@ietf.org; Thu, 22 Apr 2004 14:46:29 -0400
Received: from eaglet (127.0.0.1:4358)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S517D5> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 22 Apr 2004 11:50:11 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Fred Templin'" <ftemplin@iprg.nokia.com>
Cc: "'Geoff Huston'" <gih@telstra.net>,
        "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
Date: Thu, 22 Apr 2004 11:46:30 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQn3YB645pL6PWpRk6IpKyVNEEAYgAuqQKQ
In-Reply-To: <4086D5B8.7020808@iprg.nokia.com>
Message-Id: <E1BGjDR-0000JX-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Please forgive the typeo... it should be 240

> -----Original Message-----
> From: Fred Templin [mailto:ftemplin@iprg.nokia.com]
> Sent: Wednesday, April 21, 2004 1:13 PM
> To: Tony Hain
> Cc: 'Geoff Huston'; 'Iljitsch van Beijnum'; 'IETF Discussion'
> Subject: Re: [Ietf] 240.0.0.0/4
> 
> Tony,
> 
> Tony Hain wrote:
> 
> >As far as redefining 224/4; it is likely going to be impossible to
> redefine
> >this space as no one really knows what it is being used for.
> >
> 
> Did you mean to say 224/4, or 240/4 - or perhaps both?
> 
> Thanks - Fred
> ftemplin@iprg.nokia.com


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



From exim@www1.ietf.org  Thu Apr 22 15:45:14 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22775
	for <ietf-archive@odin.ietf.org>; Thu, 22 Apr 2004 15:45:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjdY-0003g1-IN
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 15:13:28 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3MJDSW8014128
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 15:13:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjPg-00075M-57; Thu, 22 Apr 2004 14:59:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjFO-0003Yq-OH
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 14:48: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 OAA17239
	for <ietf@ietf.org>; Thu, 22 Apr 2004 14: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 1BGjFC-0000pk-DQ
	for ietf@ietf.org; Thu, 22 Apr 2004 14:48:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGjEA-0000ZI-00
	for ietf@ietf.org; Thu, 22 Apr 2004 14:47:14 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGjDT-0000JZ-00
	for ietf@ietf.org; Thu, 22 Apr 2004 14:46:31 -0400
Received: from eaglet (127.0.0.1:4358)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S517D6> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 22 Apr 2004 11:50:14 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dean Anderson'" <dean@av8.com>
Cc: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
Date: Thu, 22 Apr 2004 11:46:30 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQnpaQibiOLk4maQOi8osPzv1hC7gA8Gd2A
In-Reply-To: <Pine.LNX.4.44.0404210901420.14263-100000@cirrus.av8.net>
Message-Id: <E1BGjDT-0000JZ-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Dean Anderson wrote:
> ...
> Ok, fair enough. Instead of "hosts" in the traditional sense, the above
> should be considered as '... approximately 20 million simultaneous uses of
> unique IP addresses'.
> 
> > > that must each have direct access to any of the rest, and you can't
> > > NAT internally, then you probably have reached a point where you will
> > > need a more sophisticated mechanism than NAT to reach the public
> > > internet.
> >
> > You assume a network & traffic model that may not apply.
> 
> _I_ don't make that assumption. This was asserted by the person who
> suggests that there is not enough private IP address space. Otherwise,
> they would not need more than 20 million unique private IP addresses.
> 
> Either we accept it as a given that they really do need more than ~20
> million unique private IP addresses and also do need to reach the public
> network, or else assert that perhaps no one really needs more than ~20
> million unique, private IP addresses while also needing to reach a public
> network. Or alternately, assert that if such a case does exist, then it is
> so unusual that some more sophisticated mechanism is needed for that case.

You appear to overlook the case that H-D ratios apply to large complex
enterprise networks just as they do to ISPs. Also, it is not necessary for
all nodes to need public access. As soon as any do there is a need to avoid
using any public prefixes on the internal network.

> 
> > > Underlying this is the question of whether such a large network really
> > > needs to simultanously reach the public network. If it doesn't, then
> there
> > > is no reason to limit oneself to the RFC 1918 space.
> >
> > Yes there is when some of the nodes do need access to the public
> network.
> > You can't expect to use a private version of a publicly routed prefix.
> 
> I don't think you understood my text. I meant "If it doesn't [need access
> to the public network], then there is no reason to limit oneself to the
> RFC 1918 space"

I understand what you wrote, but I think you are being overly simplistic. In
some scenarios it is very likely that only 5% of the nodes need public
access. This creates a situation where acquiring more public allocation is
impossible due to current policy. At the same time there is no room to grow
without guessing which /8's are going to be allocated last.

> 
> > > I might also suggest that such a heavy address user migrate to IPv6
> > > internally as IPv6 has similar problems and it is developing means to
> deal
> > > with them.
> >
> > Easy to say, but turning something with that mass takes more time than
> the
> > dentist office network. Yes it is the right thing to do, but don't
> expect it
> > to happen in a timeframe shorter than 3-5 years.
> 
> That is the same (or perhaps shorter) lifetime as changing the class E
> definition.

Changing the Class E definition will take longer because people will be less
inclined to change an IPv4 stack until it clearly breaks. At that point it
is generating support calls so the reality is people will do whatever they
can to avoid using Class E addresses.

Tony




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



From exim@www1.ietf.org  Thu Apr 22 15:45:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22795
	for <ietf-archive@odin.ietf.org>; Thu, 22 Apr 2004 15:45:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjfJ-0004ky-N8
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 15:15:17 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3MJFHTc018278
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 15:15:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjPi-00075k-5Q; Thu, 22 Apr 2004 14:59:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGjI4-0004uZ-Bl
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 14:51: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 OAA17397
	for <ietf@ietf.org>; Thu, 22 Apr 2004 14: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 1BGjHz-0001eN-9p
	for ietf@ietf.org; Thu, 22 Apr 2004 14:51:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGjH3-0001My-00
	for ietf@ietf.org; Thu, 22 Apr 2004 14:50:13 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGjGA-0000qg-00
	for ietf@ietf.org; Thu, 22 Apr 2004 14:49:18 -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 i3MImlwC014701
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 22 Apr 2004 14:48:47 -0400
Date: Thu, 22 Apr 2004 14:48:47 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Joe Touch <touch@ISI.EDU>
cc: jfcm <info@utel.net>, Tim Chown <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <408808CA.7010200@isi.edu>
Message-ID: <Pine.LNX.4.44.0404221420580.8863-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Thu, 22 Apr 2004, Joe Touch wrote:

> The "tel:" part is sufficient to get you to VOIP - in fact, that's what 
> tel: ought to mean -- no more, no less. If you want IBM to differentiate 
> the switchboard from the headquarters, try:
> 
> 	tel://ibm.com/hq	- headquarters-specific
> 	tel://ibm.com/		- default switchboard
> 
> > Similarly, I'd expect that tel://ibm.mobi gets me to the IBM Cellular
> > switchboard.
> 
> 	tel://ibm.com/cell
> 
> I.e., that's a decision IBM gets to make; others can decide, e.g., that 
> cell and regular calls all go through the same VOIP gateway.

Well, why not just run everything over http and have an application-type 
header to destinguish the different formats?  Possible, but not quite 
ideal, since then you are stuck with an HTTP server in the middle.

> > I recall that gte internetworking used gte.com for internal corporate
> > addresses and gte.net for customer addresses. Some companies use
> > subdomains for such purposes.  
> 
> Sure, but that is different than the above. In the tel: cases, all the 
> addresses are for internal corporate, not for a service IBM runs for its 
> customers.

Umm, I don't see how. Its just using naming, and specifically different
TLD's to make a distinction between corporate and customer functions.  No
matter what you do, you are probably going to use naming anyway, either as
a url path component, or as a subdomain, or as a new TLD.

I don't see any significant operational difference(*), nor any
particularly significant technical differences to them.  Except, I'd
probably prefer not to send everything through http, so that tends to go
against the use of url pathnames and application-types as discriminators.

What difference does it make to the IETF whether there are more TLD's or
less?


(*) Having more TLD's ought to improve the reliability of the internet in
general by distributing load off the overused com and net domain servers.  
Whether you have 259 TLDs or 2500 isn't going to make a great deal of
difference to the root servers, as these aren't particularly large zones.  
2500 TLDs would no doubt make some measurable impact on the roots, but it
would make a hugely big difference in directing traffic off the com and
net servers which have millions of entries.  And we aren't talking about
2500 TLDs, though. We are talking about just adding a handful. This isn't
a significant difference, and may not even be measurable.

On the other hand, I would also note that the com and net domains are
commercial, and charge fees for their operation. I don't see that the IETF
or ICANN necessarilly cares either way how much that operation costs, or
that it should be concerned very much with reducing those costs with more
TLD's.  But I'd also say that extreme disregard for costs would be a bad 
thing.  So I'd say that's a wash.


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



From ietf-admin@ietf.org  Thu Apr 22 18:31: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 SAA08351
	for <ietf-archive@ietf.org>; Thu, 22 Apr 2004 18:31: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 1BGmjI-0004wS-Aa
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 18:31:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGmiR-0004e6-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 18:30:44 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGmhW-0004Kj-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 18:29:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGmQl-0000Rz-4f; Thu, 22 Apr 2004 18:12:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGm5j-0002Yz-NR
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 17:50: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 RAA04114
	for <ietf@ietf.org>; Thu, 22 Apr 2004 17:50: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 1BGm5e-00011i-W5
	for ietf@ietf.org; Thu, 22 Apr 2004 17:50:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGm2q-00007s-00
	for ietf@ietf.org; Thu, 22 Apr 2004 17:47:45 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGlz3-0006sP-00
	for ietf@ietf.org; Thu, 22 Apr 2004 17:43:49 -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 i3MLhKPo017866
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 22 Apr 2004 17:43:20 -0400
Date: Thu, 22 Apr 2004 17:43:20 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Tony Hain <alh-ietf@tndh.net>
cc: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
In-Reply-To: <200404221846.OAA09035@odie.av8.com>
Message-ID: <Pine.LNX.4.44.0404221718350.8863-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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, 22 Apr 2004, Tony Hain wrote:

> You appear to overlook the case that H-D ratios apply to large complex
> enterprise networks just as they do to ISPs. Also, it is not necessary for
> all nodes to need public access. As soon as any do there is a need to avoid
> using any public prefixes on the internal network.

I agree completely. But even large complex, enterprise networks don't need
complete, fully routed connectivity.  As I said, I used to work for 
Hitachi, which is a very large enterprise.  This is why I doubt that 
anyone really needs more than the RFC1918 space.

> I understand what you wrote, but I think you are being overly simplistic. In
> some scenarios it is very likely that only 5% of the nodes need public
> access. This creates a situation where acquiring more public allocation is
> impossible due to current policy. At the same time there is no room to grow
> without guessing which /8's are going to be allocated last.

I suppose I am oversimplying. But I'm not sure I follow you. 

A large enterprise network has somewhat similar characteristics to a group
of companies operating over the public network. Only a small fraction of
the enterprise needs to get to every other part of the enterprise.  
Enterprises can use NATs internally the same way other companies use NATs
with the public network.

My point is that it takes a rather unusually extreme case to have an
enterprise that needs full connectivity internally, yet is so large that
it uses all of the available RFC1918 address space.  There are only a few
possible organizations worldwide that could be in this group.

There are some extreme cases of disconnection. For example, the internal
NSA networks are never going to be interconnected with the public network.
It would certainly be OK for the NSA to use address space other than
RFC1918 space.  However, I don't think the NSA is large enough to exhaust
the RFC1918 space. Indeed, I doubt that Hitachi is large enough to exhaust
the RFC1918 space.  

The main problem with RFC1918 space is inconvenient collisions. The same
space is used by 2 different divisions, that later need to interconnect.
It is not a lack of space--it is a lack of coordination. For companies
like Hitachi (not to pick on Hitachi), this would be just bad management.
They could have coordinated this. But in other cases, such as when
companies merge and find that they picked the same blocks, there is no way
they could have anticpated or coordinated the parts of RFC1918 space to
use.  More space doesn't solve this problem either (which I suspect is the
real motivator, though it was not stated as such)

		--Dean


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


From ietf-admin@ietf.org  Thu Apr 22 18:35: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 SAA08641
	for <ietf-archive@ietf.org>; Thu, 22 Apr 2004 18: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 1BGmmp-0006EA-Dr
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 18:35:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGmlj-0005fV-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 18:34:08 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGmkh-0005KX-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 18:33:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGmQz-0000hR-Kg; Thu, 22 Apr 2004 18:12:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGm8R-0003RD-VU
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 17:53: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 RAA04453
	for <ietf@ietf.org>; Thu, 22 Apr 2004 17:53: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 1BGm8N-0001qP-8y
	for ietf@ietf.org; Thu, 22 Apr 2004 17:53:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGm7C-0001SJ-00
	for ietf@ietf.org; Thu, 22 Apr 2004 17:52:14 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGm5I-0000gG-00
	for ietf@ietf.org; Thu, 22 Apr 2004 17:50:17 -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 i3MLnOVr017958
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 22 Apr 2004 17:49:24 -0400
Date: Thu, 22 Apr 2004 17:49:24 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Joe Touch <touch@ISI.EDU>
cc: jfcm <info@utel.net>, Tim Chown <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <408824EC.2030108@isi.edu>
Message-ID: <Pine.LNX.4.44.0404221745150.8863-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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, 22 Apr 2004, Joe Touch wrote:
> > What difference does it make to the IETF whether there are more TLD's or
> > less?
> 
> Nothing in general; what matters, as jfc already put very well, is that 
> these particular TLDs are acting in place of a function that is already 
> provided by the protocol field.

Ok. So the difference is that mobi and tel indicate an application
function, whereas net, com, cc, biz, info, museum, org, etc tend to
indicate business/organiation function? (leaving out country codes--which
indicate locale)

Is it sensible to think of tel and mobi as business functions?

		--Dean


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


From exim@www1.ietf.org  Thu Apr 22 18:52:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09783
	for <ietf-archive@odin.ietf.org>; Thu, 22 Apr 2004 18:52:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGmha-0000lp-Ek
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 18:29:51 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3MMTovi002958
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 18:29:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGmQl-0000Rz-4f; Thu, 22 Apr 2004 18:12:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGm5j-0002Yz-NR
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 17:50: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 RAA04114
	for <ietf@ietf.org>; Thu, 22 Apr 2004 17:50: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 1BGm5e-00011i-W5
	for ietf@ietf.org; Thu, 22 Apr 2004 17:50:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGm2q-00007s-00
	for ietf@ietf.org; Thu, 22 Apr 2004 17:47:45 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGlz3-0006sP-00
	for ietf@ietf.org; Thu, 22 Apr 2004 17:43:49 -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 i3MLhKPo017866
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 22 Apr 2004 17:43:20 -0400
Date: Thu, 22 Apr 2004 17:43:20 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Tony Hain <alh-ietf@tndh.net>
cc: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
In-Reply-To: <200404221846.OAA09035@odie.av8.com>
Message-ID: <Pine.LNX.4.44.0404221718350.8863-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Thu, 22 Apr 2004, Tony Hain wrote:

> You appear to overlook the case that H-D ratios apply to large complex
> enterprise networks just as they do to ISPs. Also, it is not necessary for
> all nodes to need public access. As soon as any do there is a need to avoid
> using any public prefixes on the internal network.

I agree completely. But even large complex, enterprise networks don't need
complete, fully routed connectivity.  As I said, I used to work for 
Hitachi, which is a very large enterprise.  This is why I doubt that 
anyone really needs more than the RFC1918 space.

> I understand what you wrote, but I think you are being overly simplistic. In
> some scenarios it is very likely that only 5% of the nodes need public
> access. This creates a situation where acquiring more public allocation is
> impossible due to current policy. At the same time there is no room to grow
> without guessing which /8's are going to be allocated last.

I suppose I am oversimplying. But I'm not sure I follow you. 

A large enterprise network has somewhat similar characteristics to a group
of companies operating over the public network. Only a small fraction of
the enterprise needs to get to every other part of the enterprise.  
Enterprises can use NATs internally the same way other companies use NATs
with the public network.

My point is that it takes a rather unusually extreme case to have an
enterprise that needs full connectivity internally, yet is so large that
it uses all of the available RFC1918 address space.  There are only a few
possible organizations worldwide that could be in this group.

There are some extreme cases of disconnection. For example, the internal
NSA networks are never going to be interconnected with the public network.
It would certainly be OK for the NSA to use address space other than
RFC1918 space.  However, I don't think the NSA is large enough to exhaust
the RFC1918 space. Indeed, I doubt that Hitachi is large enough to exhaust
the RFC1918 space.  

The main problem with RFC1918 space is inconvenient collisions. The same
space is used by 2 different divisions, that later need to interconnect.
It is not a lack of space--it is a lack of coordination. For companies
like Hitachi (not to pick on Hitachi), this would be just bad management.
They could have coordinated this. But in other cases, such as when
companies merge and find that they picked the same blocks, there is no way
they could have anticpated or coordinated the parts of RFC1918 space to
use.  More space doesn't solve this problem either (which I suspect is the
real motivator, though it was not stated as such)

		--Dean


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



From exim@www1.ietf.org  Thu Apr 22 18:53:10 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09802
	for <ietf-archive@odin.ietf.org>; Thu, 22 Apr 2004 18:53:10 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGmkl-0002bA-MS
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 18:33:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3MMX7j4009963
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 18:33:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGmQz-0000hR-Kg; Thu, 22 Apr 2004 18:12:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGm8R-0003RD-VU
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 17:53: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 RAA04453
	for <ietf@ietf.org>; Thu, 22 Apr 2004 17:53: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 1BGm8N-0001qP-8y
	for ietf@ietf.org; Thu, 22 Apr 2004 17:53:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGm7C-0001SJ-00
	for ietf@ietf.org; Thu, 22 Apr 2004 17:52:14 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGm5I-0000gG-00
	for ietf@ietf.org; Thu, 22 Apr 2004 17:50:17 -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 i3MLnOVr017958
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 22 Apr 2004 17:49:24 -0400
Date: Thu, 22 Apr 2004 17:49:24 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Joe Touch <touch@ISI.EDU>
cc: jfcm <info@utel.net>, Tim Chown <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <408824EC.2030108@isi.edu>
Message-ID: <Pine.LNX.4.44.0404221745150.8863-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Thu, 22 Apr 2004, Joe Touch wrote:
> > What difference does it make to the IETF whether there are more TLD's or
> > less?
> 
> Nothing in general; what matters, as jfc already put very well, is that 
> these particular TLDs are acting in place of a function that is already 
> provided by the protocol field.

Ok. So the difference is that mobi and tel indicate an application
function, whereas net, com, cc, biz, info, museum, org, etc tend to
indicate business/organiation function? (leaving out country codes--which
indicate locale)

Is it sensible to think of tel and mobi as business functions?

		--Dean


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



From ietf-admin@ietf.org  Thu Apr 22 21:57: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 VAA19271
	for <ietf-archive@ietf.org>; Thu, 22 Apr 2004 21:57: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 1BGpwf-0006JR-Ho
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 21:57:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGpvk-000629-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 21:56:41 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGpus-0005l5-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 21:55:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGpnO-0008EI-A4; Thu, 22 Apr 2004 21:48:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGpj4-0006fc-Vh
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 21:43:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18563
	for <ietf@ietf.org>; Thu, 22 Apr 2004 21:43: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 1BGpj0-0002RE-0y
	for ietf@ietf.org; Thu, 22 Apr 2004 21:43:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGphx-00028j-00
	for ietf@ietf.org; Thu, 22 Apr 2004 21:42:26 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGph2-0001c2-00
	for ietf@ietf.org; Thu, 22 Apr 2004 21:41:28 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Date: Thu, 22 Apr 2004 18:40:55 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB0CC@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: I-D ACTION:draft-hain-1918bis-00.txt
thread-index: AcQn68wbSgxH1shpTu2ceoMy5mH2rQA55qRQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Tony Hain" <alh-ietf@tndh.net>
Cc: "IETF Discussion" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Subject: [Ietf] RE: I-D ACTION:draft-hain-1918bis-00.txt
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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

Tony,

> draft-hain-1918bis-00.txt

Although I don't think it belongs in the draft, could you post some real
examples of addressing plans that would use that much private space (we
are talking about 10/8 plus four other class A). I was wondering if it
would not be easier to make a case requesting one additional class A for
private space than four at the same time.

Michel.


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


From exim@www1.ietf.org  Thu Apr 22 22:03:48 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19618
	for <ietf-archive@odin.ietf.org>; Thu, 22 Apr 2004 22:03:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGpuw-0001q6-DI
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 21:55:50 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3N1toOq007034
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 21:55:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGpnO-0008EI-A4; Thu, 22 Apr 2004 21:48:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGpj4-0006fc-Vh
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 21:43:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18563
	for <ietf@ietf.org>; Thu, 22 Apr 2004 21:43: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 1BGpj0-0002RE-0y
	for ietf@ietf.org; Thu, 22 Apr 2004 21:43:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGphx-00028j-00
	for ietf@ietf.org; Thu, 22 Apr 2004 21:42:26 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGph2-0001c2-00
	for ietf@ietf.org; Thu, 22 Apr 2004 21:41:28 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Date: Thu, 22 Apr 2004 18:40:55 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB0CC@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: I-D ACTION:draft-hain-1918bis-00.txt
thread-index: AcQn68wbSgxH1shpTu2ceoMy5mH2rQA55qRQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Tony Hain" <alh-ietf@tndh.net>
Cc: "IETF Discussion" <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [Ietf] RE: I-D ACTION:draft-hain-1918bis-00.txt
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: quoted-printable

Tony,

> draft-hain-1918bis-00.txt

Although I don't think it belongs in the draft, could you post some real
examples of addressing plans that would use that much private space (we
are talking about 10/8 plus four other class A). I was wondering if it
would not be easier to make a case requesting one additional class A for
private space than four at the same time.

Michel.


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



From exim@www1.ietf.org  Thu Apr 22 23:05:46 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23137
	for <ietf-archive@odin.ietf.org>; Thu, 22 Apr 2004 23:05:46 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGqzP-0006X1-BT
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 23:04:31 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3N34VgT025096
	for ietf-archive@odin.ietf.org; Thu, 22 Apr 2004 23:04:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGqmN-0002Vy-05; Thu, 22 Apr 2004 22:51:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGqiz-0001Fg-13
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 22:47:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22164
	for <ietf@ietf.org>; Thu, 22 Apr 2004 22:47: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 1BGqis-0004UX-TS
	for ietf@ietf.org; Thu, 22 Apr 2004 22:47:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGqhu-0004Ei-00
	for ietf@ietf.org; Thu, 22 Apr 2004 22:46:27 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGqgv-0003xg-00
	for ietf@ietf.org; Thu, 22 Apr 2004 22:45:25 -0400
Received: from eaglet (127.0.0.1:4576)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S518ED> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 22 Apr 2004 19:49:08 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dean Anderson'" <dean@av8.com>
Cc: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
Date: Thu, 22 Apr 2004 19:45:26 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQos206SkVVxWNnQhapjxE49fEtXwAKAFug
In-Reply-To: <Pine.LNX.4.44.0404221718350.8863-100000@cirrus.av8.net>
Message-Id: <E1BGqgv-0003xg-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Dean Anderson wrote:
> On Thu, 22 Apr 2004, Tony Hain wrote:
> 
> > You appear to overlook the case that H-D ratios apply to large complex
> > enterprise networks just as they do to ISPs. Also, it is not necessary
> for
> > all nodes to need public access. As soon as any do there is a need to
> avoid
> > using any public prefixes on the internal network.
> 
> I agree completely. But even large complex, enterprise networks don't need
> complete, fully routed connectivity.  As I said, I used to work for
> Hitachi, which is a very large enterprise.  This is why I doubt that
> anyone really needs more than the RFC1918 space.
> 
> > I understand what you wrote, but I think you are being overly
> simplistic. In
> > some scenarios it is very likely that only 5% of the nodes need public
> > access. This creates a situation where acquiring more public allocation
> is
> > impossible due to current policy. At the same time there is no room to
> grow
> > without guessing which /8's are going to be allocated last.
> 
> I suppose I am oversimplying. But I'm not sure I follow you.
> 
> A large enterprise network has somewhat similar characteristics to a group
> of companies operating over the public network. Only a small fraction of
> the enterprise needs to get to every other part of the enterprise.
> Enterprises can use NATs internally the same way other companies use NATs
> with the public network.

You assume a specific application and traffic model when you claim that
enterprises can use NAT internally. This is not universally true.

> 
> My point is that it takes a rather unusually extreme case to have an
> enterprise that needs full connectivity internally, yet is so large that
> it uses all of the available RFC1918 address space.  There are only a few
> possible organizations worldwide that could be in this group.

Yes there are a small number, which is part of the reason they don't want to
stand up and be bashed by the IETF. They just want to use the technology as
it was intended to be used, and either need public space they will use for
non-public nodes, or additional private space.

> 
> There are some extreme cases of disconnection. For example, the internal
> NSA networks are never going to be interconnected with the public network.
> It would certainly be OK for the NSA to use address space other than
> RFC1918 space.  However, I don't think the NSA is large enough to exhaust
> the RFC1918 space. Indeed, I doubt that Hitachi is large enough to exhaust
> the RFC1918 space.

I don't know about either of your examples, but basing need on historical
use by traditional 'hosts' is ignoring the need to support growth and new
applications & appliances. 

> 
> The main problem with RFC1918 space is inconvenient collisions. The same
> space is used by 2 different divisions, that later need to interconnect.
> It is not a lack of space--it is a lack of coordination. For companies
> like Hitachi (not to pick on Hitachi), this would be just bad management.
> They could have coordinated this. But in other cases, such as when
> companies merge and find that they picked the same blocks, there is no way
> they could have anticpated or coordinated the parts of RFC1918 space to
> use.  More space doesn't solve this problem either (which I suspect is the
> real motivator, though it was not stated as such)

Some organizations would no doubt be happy to have additional space to
reduce some of their pain caused by churn coupled with the scarcity of IPv4
addresses. That is not the motivator for the draft I submitted. There are
organizations that need more space now, and while they will be moving to
IPv6, they can't deploy all the pieces fast enough. 

Tony



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



From ietf-admin@ietf.org  Thu Apr 22 23:08: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 XAA23219
	for <ietf-archive@ietf.org>; Thu, 22 Apr 2004 23:08: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 1BGr2n-00027o-Bq
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 23:08:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGr0U-0001nm-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 23:05:40 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGqzK-0001UO-00
	for ietf-archive@ietf.org; Thu, 22 Apr 2004 23:04:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGqmN-0002Vy-05; Thu, 22 Apr 2004 22:51:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGqiz-0001Fg-13
	for ietf@optimus.ietf.org; Thu, 22 Apr 2004 22:47:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22164
	for <ietf@ietf.org>; Thu, 22 Apr 2004 22:47: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 1BGqis-0004UX-TS
	for ietf@ietf.org; Thu, 22 Apr 2004 22:47:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGqhu-0004Ei-00
	for ietf@ietf.org; Thu, 22 Apr 2004 22:46:27 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGqgv-0003xg-00
	for ietf@ietf.org; Thu, 22 Apr 2004 22:45:25 -0400
Received: from eaglet (127.0.0.1:4576)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S518ED> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 22 Apr 2004 19:49:08 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dean Anderson'" <dean@av8.com>
Cc: "'Iljitsch van Beijnum'" <iljitsch@muada.com>,
        "'IETF Discussion'" <ietf@ietf.org>
Subject: RE: [Ietf] 240.0.0.0/4
Date: Thu, 22 Apr 2004 19:45:26 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQos206SkVVxWNnQhapjxE49fEtXwAKAFug
In-Reply-To: <Pine.LNX.4.44.0404221718350.8863-100000@cirrus.av8.net>
Message-Id: <E1BGqgv-0003xg-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Dean Anderson wrote:
> On Thu, 22 Apr 2004, Tony Hain wrote:
> 
> > You appear to overlook the case that H-D ratios apply to large complex
> > enterprise networks just as they do to ISPs. Also, it is not necessary
> for
> > all nodes to need public access. As soon as any do there is a need to
> avoid
> > using any public prefixes on the internal network.
> 
> I agree completely. But even large complex, enterprise networks don't need
> complete, fully routed connectivity.  As I said, I used to work for
> Hitachi, which is a very large enterprise.  This is why I doubt that
> anyone really needs more than the RFC1918 space.
> 
> > I understand what you wrote, but I think you are being overly
> simplistic. In
> > some scenarios it is very likely that only 5% of the nodes need public
> > access. This creates a situation where acquiring more public allocation
> is
> > impossible due to current policy. At the same time there is no room to
> grow
> > without guessing which /8's are going to be allocated last.
> 
> I suppose I am oversimplying. But I'm not sure I follow you.
> 
> A large enterprise network has somewhat similar characteristics to a group
> of companies operating over the public network. Only a small fraction of
> the enterprise needs to get to every other part of the enterprise.
> Enterprises can use NATs internally the same way other companies use NATs
> with the public network.

You assume a specific application and traffic model when you claim that
enterprises can use NAT internally. This is not universally true.

> 
> My point is that it takes a rather unusually extreme case to have an
> enterprise that needs full connectivity internally, yet is so large that
> it uses all of the available RFC1918 address space.  There are only a few
> possible organizations worldwide that could be in this group.

Yes there are a small number, which is part of the reason they don't want to
stand up and be bashed by the IETF. They just want to use the technology as
it was intended to be used, and either need public space they will use for
non-public nodes, or additional private space.

> 
> There are some extreme cases of disconnection. For example, the internal
> NSA networks are never going to be interconnected with the public network.
> It would certainly be OK for the NSA to use address space other than
> RFC1918 space.  However, I don't think the NSA is large enough to exhaust
> the RFC1918 space. Indeed, I doubt that Hitachi is large enough to exhaust
> the RFC1918 space.

I don't know about either of your examples, but basing need on historical
use by traditional 'hosts' is ignoring the need to support growth and new
applications & appliances. 

> 
> The main problem with RFC1918 space is inconvenient collisions. The same
> space is used by 2 different divisions, that later need to interconnect.
> It is not a lack of space--it is a lack of coordination. For companies
> like Hitachi (not to pick on Hitachi), this would be just bad management.
> They could have coordinated this. But in other cases, such as when
> companies merge and find that they picked the same blocks, there is no way
> they could have anticpated or coordinated the parts of RFC1918 space to
> use.  More space doesn't solve this problem either (which I suspect is the
> real motivator, though it was not stated as such)

Some organizations would no doubt be happy to have additional space to
reduce some of their pain caused by churn coupled with the scarcity of IPv4
addresses. That is not the motivator for the draft I submitted. There are
organizations that need more space now, and while they will be moving to
IPv6, they can't deploy all the pieces fast enough. 

Tony



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


From ietf-admin@ietf.org  Fri Apr 23 03:18: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 DAA18730
	for <ietf-archive@ietf.org>; Fri, 23 Apr 2004 03:18: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 1BGuxK-0000Lq-Qq
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 03:18:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGuwM-000036-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 03:17:38 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGuvM-0007ZO-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 03:16:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGujD-0003Zx-0I; Fri, 23 Apr 2004 03:04:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGuhy-000356-Mv
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 03:02: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 DAA18132
	for <ietf@ietf.org>; Fri, 23 Apr 2004 03:02: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 1BGuhs-0003rh-Lo
	for ietf@ietf.org; Fri, 23 Apr 2004 03:02:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGugv-0003cb-00
	for ietf@ietf.org; Fri, 23 Apr 2004 03:01:41 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGugF-0003NJ-00
	for ietf@ietf.org; Fri, 23 Apr 2004 03:00:59 -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 i3N70k1C092188;
	Fri, 23 Apr 2004 09:00:46 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB0CC@server2003.arneill-py.sacramento.ca.us>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB0CC@server2003.arneill-py.sacramento.ca.us>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F1E51B53-94F3-11D8-B78B-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "Tony Hain" <alh-ietf@tndh.net>, "IETF Discussion" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [Ietf] RE: I-D ACTION:draft-hain-1918bis-00.txt
Date: Fri, 23 Apr 2004 09:00:46 +0200
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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-apr-04, at 3:40, Michel Py wrote:

>> draft-hain-1918bis-00.txt

> Although I don't think it belongs in the draft, could you post some 
> real
> examples of addressing plans that would use that much private space

Yes, the draft is a little light on justification.


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


From exim@www1.ietf.org  Fri Apr 23 03:18:56 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18784
	for <ietf-archive@odin.ietf.org>; Fri, 23 Apr 2004 03:18:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGuvP-00078F-SY
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 03:16:40 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3N7GdnJ027381
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 03:16:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGujD-0003Zx-0I; Fri, 23 Apr 2004 03:04:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGuhy-000356-Mv
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 03:02: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 DAA18132
	for <ietf@ietf.org>; Fri, 23 Apr 2004 03:02: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 1BGuhs-0003rh-Lo
	for ietf@ietf.org; Fri, 23 Apr 2004 03:02:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGugv-0003cb-00
	for ietf@ietf.org; Fri, 23 Apr 2004 03:01:41 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGugF-0003NJ-00
	for ietf@ietf.org; Fri, 23 Apr 2004 03:00:59 -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 i3N70k1C092188;
	Fri, 23 Apr 2004 09:00:46 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB0CC@server2003.arneill-py.sacramento.ca.us>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB0CC@server2003.arneill-py.sacramento.ca.us>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F1E51B53-94F3-11D8-B78B-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "Tony Hain" <alh-ietf@tndh.net>, "IETF Discussion" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [Ietf] RE: I-D ACTION:draft-hain-1918bis-00.txt
Date: Fri, 23 Apr 2004 09:00:46 +0200
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.613)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

On 23-apr-04, at 3:40, Michel Py wrote:

>> draft-hain-1918bis-00.txt

> Although I don't think it belongs in the draft, could you post some 
> real
> examples of addressing plans that would use that much private space

Yes, the draft is a little light on justification.


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



From ietf-admin@ietf.org  Fri Apr 23 08:25: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 IAA00513
	for <ietf-archive@ietf.org>; Fri, 23 Apr 2004 08:25: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 1BGzk8-0003uM-Ss
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 08:25:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGzjC-0003cj-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 08:24:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGziK-000377-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 08:23:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGzd4-0001tg-G4; Fri, 23 Apr 2004 08:18:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGzUK-0000Ex-JK
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 08:09: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 IAA29932
	for <ietf@ietf.org>; Fri, 23 Apr 2004 08:08: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 1BGzUJ-0007cz-35
	for ietf@ietf.org; Fri, 23 Apr 2004 08:08:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGzTV-0007NU-00
	for ietf@ietf.org; Fri, 23 Apr 2004 08:08:10 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGzRr-0006tc-00
	for ietf@ietf.org; Fri, 23 Apr 2004 08:06:27 -0400
Received: from f02v-37-124.d0.club-internet.fr ([212.195.240.124] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BGzRi-0007mE-GF; Fri, 23 Apr 2004 05:06:18 -0700
Message-Id: <6.0.1.1.2.20040423115557.048f20c0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 23 Apr 2004 12:33:27 +0200
To: Dean Anderson <dean@av8.com>, Joe Touch <touch@ISI.EDU>
From: jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
In-Reply-To: <Pine.LNX.4.44.0404221745150.8863-100000@cirrus.av8.net>
References: <408824EC.2030108@isi.edu>
 <Pine.LNX.4.44.0404221745150.8863-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 - utel.net
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
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 23:49 22/04/04, Dean Anderson wrote:
>Is it sensible to think of tel and mobi as business functions?

Absolutely yes. As I noted it, there are at least two possiblities:
- .tel is accepted as the TLD of the ITU-T Sector's members. The same as 
for .aero. And .mobi is for all the companies, services, designers 
interested in mobile product, services etc.
- .tel is reserved to a class of users froming an "externet", ie. a class 
of users with special relations/access terms. This can be an economical 
model (rates), this can be a way of behaving (accepting or not VoSpam), 
etc. This however calls for a large number of new architectural concepts 
and naming semantic to be discussed and agreed upon.

But in both cases, it is likely it would then be premature to give away 
such mnemonics as "tel" and "mobi" before a wide debate. ITU expressed that 
in their letter of 2000 to ICANN. ICANN was wise to agree. I think not much 
has changed.

But would remain the IDNA aspect (LHS is not solved yet!),  the 
co-registry/virtual zone need to address the support of an _existing_ and 
generalized non Internet industry, and the real life feed-back. Do you 
really think non-US Govs, ITU, users, etc. will take ICANN and IETF 
seriously if they give away a $ 6 yearly tax on 1.3 billion mobiles and 
more telephone sets, managed by State controlled corporations or 
monopolies, to a single private US interest? If the root was the "joke of 
the XXth century" (European Gov top expet's comment), this would be the 
joke of the XXIth century.

The slippery slope is the risk that ICANN tries (or is put under pressures 
to try) that "coup" for political/commercial reasons. I think IETF is here 
to say where are the technical problems to prevent that temptation.

Another point, I did not rise, is that ".tel" and ".mobi" would obviously 
immediately lead to propositions such as ".tel1", ".mob1", ".phone", etc. 
etc. The size of the existing market and its technical sophistication would 
certainly push imaginations a lot and things IAB did not consider for 20 
years would be implemented in chaos in months. There would be scores of 
New.nets.

Just consider that ".sms" is the golden mine of today and is LOCAL. Any ISP 
alliance can start it today and build an externet (open virtual netwok) 
using ULDs (User level domains made of the alias couple of an SLD and of a 
local TLD) that will work very well.

IAB has not published an architecture for the internetting and ICANN has 
contained the number of TLDs. This has not permitted the world to get a 
technical reference nor to establish commonly agreed best practices. 
Nevertheless common sense remains until this may be corrected within the 
global convergence/stabilization of the digital continuity.
jfc


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


From exim@www1.ietf.org  Fri Apr 23 08:28:43 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00751
	for <ietf-archive@odin.ietf.org>; Fri, 23 Apr 2004 08:28:43 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGziL-0003C0-FV
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 08:23:29 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3NCNTPK012264
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 08:23:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGzd4-0001tg-G4; Fri, 23 Apr 2004 08:18:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGzUK-0000Ex-JK
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 08:09: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 IAA29932
	for <ietf@ietf.org>; Fri, 23 Apr 2004 08:08: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 1BGzUJ-0007cz-35
	for ietf@ietf.org; Fri, 23 Apr 2004 08:08:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGzTV-0007NU-00
	for ietf@ietf.org; Fri, 23 Apr 2004 08:08:10 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGzRr-0006tc-00
	for ietf@ietf.org; Fri, 23 Apr 2004 08:06:27 -0400
Received: from f02v-37-124.d0.club-internet.fr ([212.195.240.124] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BGzRi-0007mE-GF; Fri, 23 Apr 2004 05:06:18 -0700
Message-Id: <6.0.1.1.2.20040423115557.048f20c0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 23 Apr 2004 12:33:27 +0200
To: Dean Anderson <dean@av8.com>, Joe Touch <touch@ISI.EDU>
From: jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
In-Reply-To: <Pine.LNX.4.44.0404221745150.8863-100000@cirrus.av8.net>
References: <408824EC.2030108@isi.edu>
 <Pine.LNX.4.44.0404221745150.8863-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 - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

At 23:49 22/04/04, Dean Anderson wrote:
>Is it sensible to think of tel and mobi as business functions?

Absolutely yes. As I noted it, there are at least two possiblities:
- .tel is accepted as the TLD of the ITU-T Sector's members. The same as 
for .aero. And .mobi is for all the companies, services, designers 
interested in mobile product, services etc.
- .tel is reserved to a class of users froming an "externet", ie. a class 
of users with special relations/access terms. This can be an economical 
model (rates), this can be a way of behaving (accepting or not VoSpam), 
etc. This however calls for a large number of new architectural concepts 
and naming semantic to be discussed and agreed upon.

But in both cases, it is likely it would then be premature to give away 
such mnemonics as "tel" and "mobi" before a wide debate. ITU expressed that 
in their letter of 2000 to ICANN. ICANN was wise to agree. I think not much 
has changed.

But would remain the IDNA aspect (LHS is not solved yet!),  the 
co-registry/virtual zone need to address the support of an _existing_ and 
generalized non Internet industry, and the real life feed-back. Do you 
really think non-US Govs, ITU, users, etc. will take ICANN and IETF 
seriously if they give away a $ 6 yearly tax on 1.3 billion mobiles and 
more telephone sets, managed by State controlled corporations or 
monopolies, to a single private US interest? If the root was the "joke of 
the XXth century" (European Gov top expet's comment), this would be the 
joke of the XXIth century.

The slippery slope is the risk that ICANN tries (or is put under pressures 
to try) that "coup" for political/commercial reasons. I think IETF is here 
to say where are the technical problems to prevent that temptation.

Another point, I did not rise, is that ".tel" and ".mobi" would obviously 
immediately lead to propositions such as ".tel1", ".mob1", ".phone", etc. 
etc. The size of the existing market and its technical sophistication would 
certainly push imaginations a lot and things IAB did not consider for 20 
years would be implemented in chaos in months. There would be scores of 
New.nets.

Just consider that ".sms" is the golden mine of today and is LOCAL. Any ISP 
alliance can start it today and build an externet (open virtual netwok) 
using ULDs (User level domains made of the alias couple of an SLD and of a 
local TLD) that will work very well.

IAB has not published an architecture for the internetting and ICANN has 
contained the number of TLDs. This has not permitted the world to get a 
technical reference nor to establish commonly agreed best practices. 
Nevertheless common sense remains until this may be corrected within the 
global convergence/stabilization of the digital continuity.
jfc


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



From exim@www1.ietf.org  Fri Apr 23 08:57:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02502
	for <ietf-archive@odin.ietf.org>; Fri, 23 Apr 2004 08:57:46 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH0Dc-0003LM-I5
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 08:55:53 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3NCtmp3012848
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 08:55:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH05B-0001AI-Ap; Fri, 23 Apr 2004 08:47:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH01I-0000Dr-UN
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 08:43: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 IAA01753
	for <ietf@ietf.org>; Fri, 23 Apr 2004 08:43: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 1BH01H-00011G-Ic
	for ietf@ietf.org; Fri, 23 Apr 2004 08:43:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH00O-0000lv-00
	for ietf@ietf.org; Fri, 23 Apr 2004 08:42:09 -0400
Received: from parsley.amaranth.net ([216.44.4.23])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGzzg-0000WZ-00
	for ietf@ietf.org; Fri, 23 Apr 2004 08:41:24 -0400
Received: from Willow.senie.com (localhost.localdomain [127.0.0.1])
	(authenticated bits=0)
	by parsley.amaranth.net (8.12.8/8.12.8) with ESMTP id i3NCfLdU028852;
	Fri, 23 Apr 2004 08:41:21 -0400
Message-Id: <6.1.0.6.2.20040423082618.04ec2ec0@127.0.0.1>
X-Sender: dts@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Fri, 23 Apr 2004 08:37:07 -0400
To: Bob Hinden <bob.hinden@nokia.com>,
        Iljitsch van Beijnum <iljitsch@muada.com>
From: Daniel Senie <dts@senie.com>
Subject: Re: [Ietf] 240.0.0.0/4
Cc: IETF Discussion <ietf@ietf.org>
In-Reply-To: <4.3.2.7.2.20040420120953.02c645e0@mailhost.iprg.nokia.com>
References: <6.0.1.1.2.20040420215955.01c06ec0@localhost>
 <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
 <6.0.1.1.2.20040420215955.01c06ec0@localhost>
 <4.3.2.7.2.20040420120953.02c645e0@mailhost.iprg.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

At 06:53 PM 4/20/2004, Bob Hinden wrote:
>Iljitsch,
>
>>My comfort level would be much higher if by the time that we need the 
>>extra address space, we have a fighting chance of actually being able to 
>>use it. So I think it would be a good idea to make it very clear that 
>>implementations must, in the absence of more specific information, regard 
>>class E space as regular unicast space, the same way the IPv6 addressing 
>>RFCs spell this out for IPv6 address space that hasn't received a 
>>specific purpose yet. If we do this now we have ten years or more to 
>>clean up implementations.
>
>The only way to make this happen would be to start assigning them to some 
>real users.  Otherwise, the bugs will not be found, reported, and 
>fixed.  Just publishing an RFC with a MUST in it won't be sufficient.

No, it won't. What's being suggested is that we get such a document out 
SOON, so that by the time there's a need to use this space, there's a 
chance of having it be usable.

Devices grow old and die, just as companies do. If a document were 
published today, it might be 5 or 10 years before devices that treat class 
E space specially are either upgraded or face end of life.

If we do nothing now, then there's no chance of ever using the space. 
Please take a step back and look at a calendar covering the next decade or 
two. I know lots of folks would like that calendar to show a timeline for 
IPv6 deployment.


>The challenge here is that there may be a lot of IPv4 implementations may 
>have little or any support, and may not be possible to upgrade.

Will they be around in 10 years? Some, perhaps. Others may well have died 
by then. The document has to set a target, not define the path.

>   This would put anyone receiving a Class-E address at a big 
> disadvantage.  These addresses might have to be used behind a NAT to be 
> useful (i.e., allow direct communication to the rest of the Internet) and 
> this, of course, defeats the purpose of using them in the first place.

I don't think this is the only alternative.

My suggestion:

1) Move forward with a document as proposed, requiring implementations to 
treat class E space as unicast space. Target 5 or 10 years after 
publication as the earliest time space from the block could be allocated 
for use by RIRs.

2) Make available several chunks of space for RFC1918 usage, perhaps a few 
/8's, a whole mess of /12's, and many /16's. This space does two things: 
First, it provides additional private address space, which is needed. 
Second, it provides a usage battleground for class E space testing. There 
is the very real possibility users of these blocks will run into trouble as 
vendors have special handling for class E. By allowing these to be 
discovered during use in private networks, there is a much better chance of 
public usage of these blocks later.

I do NOT agree that the entire class E space should go to RFC 1918. That 
seems wasteful. But using some large chunks of space for that purpose 
clearly provides a test bed to prove out equipment before eventual public 
address usage in that region of IP address space.

Dan


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



From ietf-admin@ietf.org  Fri Apr 23 09:00: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 JAA02655
	for <ietf-archive@ietf.org>; Fri, 23 Apr 2004 09:00: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 1BH0Hy-0005Lc-Ib
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 09:00:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH0Es-0004aT-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 08:57:07 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BH0Dc-0003uB-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 08:55:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH05B-0001AI-Ap; Fri, 23 Apr 2004 08:47:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH01I-0000Dr-UN
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 08:43: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 IAA01753
	for <ietf@ietf.org>; Fri, 23 Apr 2004 08:43: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 1BH01H-00011G-Ic
	for ietf@ietf.org; Fri, 23 Apr 2004 08:43:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH00O-0000lv-00
	for ietf@ietf.org; Fri, 23 Apr 2004 08:42:09 -0400
Received: from parsley.amaranth.net ([216.44.4.23])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGzzg-0000WZ-00
	for ietf@ietf.org; Fri, 23 Apr 2004 08:41:24 -0400
Received: from Willow.senie.com (localhost.localdomain [127.0.0.1])
	(authenticated bits=0)
	by parsley.amaranth.net (8.12.8/8.12.8) with ESMTP id i3NCfLdU028852;
	Fri, 23 Apr 2004 08:41:21 -0400
Message-Id: <6.1.0.6.2.20040423082618.04ec2ec0@127.0.0.1>
X-Sender: dts@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Fri, 23 Apr 2004 08:37:07 -0400
To: Bob Hinden <bob.hinden@nokia.com>,
        Iljitsch van Beijnum <iljitsch@muada.com>
From: Daniel Senie <dts@senie.com>
Subject: Re: [Ietf] 240.0.0.0/4
Cc: IETF Discussion <ietf@ietf.org>
In-Reply-To: <4.3.2.7.2.20040420120953.02c645e0@mailhost.iprg.nokia.com>
References: <6.0.1.1.2.20040420215955.01c06ec0@localhost>
 <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com>
 <6.0.1.1.2.20040420215955.01c06ec0@localhost>
 <4.3.2.7.2.20040420120953.02c645e0@mailhost.iprg.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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 06:53 PM 4/20/2004, Bob Hinden wrote:
>Iljitsch,
>
>>My comfort level would be much higher if by the time that we need the 
>>extra address space, we have a fighting chance of actually being able to 
>>use it. So I think it would be a good idea to make it very clear that 
>>implementations must, in the absence of more specific information, regard 
>>class E space as regular unicast space, the same way the IPv6 addressing 
>>RFCs spell this out for IPv6 address space that hasn't received a 
>>specific purpose yet. If we do this now we have ten years or more to 
>>clean up implementations.
>
>The only way to make this happen would be to start assigning them to some 
>real users.  Otherwise, the bugs will not be found, reported, and 
>fixed.  Just publishing an RFC with a MUST in it won't be sufficient.

No, it won't. What's being suggested is that we get such a document out 
SOON, so that by the time there's a need to use this space, there's a 
chance of having it be usable.

Devices grow old and die, just as companies do. If a document were 
published today, it might be 5 or 10 years before devices that treat class 
E space specially are either upgraded or face end of life.

If we do nothing now, then there's no chance of ever using the space. 
Please take a step back and look at a calendar covering the next decade or 
two. I know lots of folks would like that calendar to show a timeline for 
IPv6 deployment.


>The challenge here is that there may be a lot of IPv4 implementations may 
>have little or any support, and may not be possible to upgrade.

Will they be around in 10 years? Some, perhaps. Others may well have died 
by then. The document has to set a target, not define the path.

>   This would put anyone receiving a Class-E address at a big 
> disadvantage.  These addresses might have to be used behind a NAT to be 
> useful (i.e., allow direct communication to the rest of the Internet) and 
> this, of course, defeats the purpose of using them in the first place.

I don't think this is the only alternative.

My suggestion:

1) Move forward with a document as proposed, requiring implementations to 
treat class E space as unicast space. Target 5 or 10 years after 
publication as the earliest time space from the block could be allocated 
for use by RIRs.

2) Make available several chunks of space for RFC1918 usage, perhaps a few 
/8's, a whole mess of /12's, and many /16's. This space does two things: 
First, it provides additional private address space, which is needed. 
Second, it provides a usage battleground for class E space testing. There 
is the very real possibility users of these blocks will run into trouble as 
vendors have special handling for class E. By allowing these to be 
discovered during use in private networks, there is a much better chance of 
public usage of these blocks later.

I do NOT agree that the entire class E space should go to RFC 1918. That 
seems wasteful. But using some large chunks of space for that purpose 
clearly provides a test bed to prove out equipment before eventual public 
address usage in that region of IP address space.

Dan


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


From ietf-admin@ietf.org  Fri Apr 23 10:06:18 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09335
	for <ietf-archive@ietf.org>; Fri, 23 Apr 2004 10:06: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 1BH1Js-0000w4-AH
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 10:06:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH1In-0000eu-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 10:05:13 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BH1IL-0000OW-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 10:04:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH17x-00040r-K3; Fri, 23 Apr 2004 09:54:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH0zc-0001hh-Ba
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 09:45:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07645
	for <ietf@ietf.org>; Fri, 23 Apr 2004 09:45: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 1BH0za-0002of-5o
	for ietf@ietf.org; Fri, 23 Apr 2004 09:45:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH0yg-0002U2-00
	for ietf@ietf.org; Fri, 23 Apr 2004 09:44:27 -0400
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BH0xe-0001vm-00
	for ietf@ietf.org; Fri, 23 Apr 2004 09:43:22 -0400
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <JDHRC7L1>; Fri, 23 Apr 2004 14:42:44 +0100
Received: from [127.0.0.1] (orion.roke.co.uk [193.118.192.66]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id JHDWX6LA; Fri, 23 Apr 2004 14:42:40 +0100
From: "Conroy, Lawrence (SMTP)" <lwc@roke.co.uk>
To: jfcm <info@utel.net>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org,
        Dean Anderson
	 <dean@av8.com>, Joe Touch <touch@ISI.EDU>
In-Reply-To: <6.0.1.1.2.20040423115557.048f20c0@mail.utel.net>
References: <408824EC.2030108@isi.edu> <Pine.LNX.4.44.0404221745150.8863-100000@cirrus.av8.net> <6.0.1.1.2.20040423115557.048f20c0@mail.utel.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <161E0A2F-952C-11D8-9118-00039355516C@roke.co.uk>
Content-Transfer-Encoding: 7bit
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Fri, 23 Apr 2004 14:42:38 +0100
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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

Hi Folks,
  OK, I'll bite.
(i)   Have all of the folks commenting actually read these proposals 
all the way through (plus RFCs
       2916 and 2806, along with the drafts RFC2806bis, and RFC2916bis 
that will replace them)?
       Some of the earlier examples in this thread make me wonder.
       Note that by proposals, I mean .tel-Pulver *and* .tel-Telnic 
(they're wildly different),
       as well as the .mobi proposal. AFAICT, Pulver/NetNumber seem to 
be proposing a competitor
       to .e164.arpa, whilst Telnic are suggesting a name-based (i.e. 
phone numbers banned) registry
       to hold telecomms contact data. (I leave it as an exercise for 
the *Advanced* student to work
       out exactly what mobi-JV are proposing :)
(ii)  After the painful/protracted discussions that led to ENUM using 
.e164.arpa., the idea
       that we throw all of that away and start again with .tel (or any 
other TLD) is a BAD idea, IMHO.
(iii) The ITU is a UN organisation, and already has .int, so I'm not 
sure that there's an obvious
       justification for making yet another TLD available to them (quite 
apart from the organisational
       issues they have with actually registering any domains under the 
existing .int TLD).
(iv)  Regarding what mnemonics are used, and the ITU liaison to ICANN, 
it's illuminating to consider
       what was going on when the statement was sent to ICANN in 2000; 
the ITU had not at that point
       made any decision on how it was going to handle Internet use of 
telephone numbers, so this was
       a request for a block on anything that might interfere with that 
process. It's now 2004, and
       this process seems to be completing - we pretty much know what 
interferes and what doesn't.
       This, however, is a point for the IAB and the ITU.

all the best,
   Lawrence

On 23 Apr 2004, at 11:33 am, jfcm wrote:
> At 23:49 22/04/04, Dean Anderson wrote:
>> Is it sensible to think of tel and mobi as business functions?
>
> Absolutely yes. As I noted it, there are at least two possiblities:
> - .tel is accepted as the TLD of the ITU-T Sector's members. The same 
> as for .aero. And .mobi is for all the companies, services, designers 
> interested in mobile product, services etc.
> - .tel is reserved to a class of users froming an "externet", ie. a 
> class of users with special relations/access terms. This can be an 
> economical model (rates), this can be a way of behaving (accepting or 
> not VoSpam), etc. This however calls for a large number of new 
> architectural concepts and naming semantic to be discussed and agreed 
> upon.
>
> But in both cases, it is likely it would then be premature to give 
> away such mnemonics as "tel" and "mobi" before a wide debate. ITU 
> expressed that in their letter of 2000 to ICANN. ICANN was wise to 
> agree. I think not much has changed.
> <snip>

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


From exim@www1.ietf.org  Fri Apr 23 10:10:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10175
	for <ietf-archive@odin.ietf.org>; Fri, 23 Apr 2004 10:10:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH1IN-0000II-9U
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 10:04:50 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3NE4lZL001118
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 10:04:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH17x-00040r-K3; Fri, 23 Apr 2004 09:54:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH0zc-0001hh-Ba
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 09:45:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07645
	for <ietf@ietf.org>; Fri, 23 Apr 2004 09:45: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 1BH0za-0002of-5o
	for ietf@ietf.org; Fri, 23 Apr 2004 09:45:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH0yg-0002U2-00
	for ietf@ietf.org; Fri, 23 Apr 2004 09:44:27 -0400
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BH0xe-0001vm-00
	for ietf@ietf.org; Fri, 23 Apr 2004 09:43:22 -0400
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <JDHRC7L1>; Fri, 23 Apr 2004 14:42:44 +0100
Received: from [127.0.0.1] (orion.roke.co.uk [193.118.192.66]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id JHDWX6LA; Fri, 23 Apr 2004 14:42:40 +0100
From: "Conroy, Lawrence (SMTP)" <lwc@roke.co.uk>
To: jfcm <info@utel.net>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org,
        Dean Anderson
	 <dean@av8.com>, Joe Touch <touch@ISI.EDU>
In-Reply-To: <6.0.1.1.2.20040423115557.048f20c0@mail.utel.net>
References: <408824EC.2030108@isi.edu> <Pine.LNX.4.44.0404221745150.8863-100000@cirrus.av8.net> <6.0.1.1.2.20040423115557.048f20c0@mail.utel.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <161E0A2F-952C-11D8-9118-00039355516C@roke.co.uk>
Content-Transfer-Encoding: 7bit
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Fri, 23 Apr 2004 14:42:38 +0100
X-Mailer: Apple Mail (2.613)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Hi Folks,
  OK, I'll bite.
(i)   Have all of the folks commenting actually read these proposals 
all the way through (plus RFCs
       2916 and 2806, along with the drafts RFC2806bis, and RFC2916bis 
that will replace them)?
       Some of the earlier examples in this thread make me wonder.
       Note that by proposals, I mean .tel-Pulver *and* .tel-Telnic 
(they're wildly different),
       as well as the .mobi proposal. AFAICT, Pulver/NetNumber seem to 
be proposing a competitor
       to .e164.arpa, whilst Telnic are suggesting a name-based (i.e. 
phone numbers banned) registry
       to hold telecomms contact data. (I leave it as an exercise for 
the *Advanced* student to work
       out exactly what mobi-JV are proposing :)
(ii)  After the painful/protracted discussions that led to ENUM using 
.e164.arpa., the idea
       that we throw all of that away and start again with .tel (or any 
other TLD) is a BAD idea, IMHO.
(iii) The ITU is a UN organisation, and already has .int, so I'm not 
sure that there's an obvious
       justification for making yet another TLD available to them (quite 
apart from the organisational
       issues they have with actually registering any domains under the 
existing .int TLD).
(iv)  Regarding what mnemonics are used, and the ITU liaison to ICANN, 
it's illuminating to consider
       what was going on when the statement was sent to ICANN in 2000; 
the ITU had not at that point
       made any decision on how it was going to handle Internet use of 
telephone numbers, so this was
       a request for a block on anything that might interfere with that 
process. It's now 2004, and
       this process seems to be completing - we pretty much know what 
interferes and what doesn't.
       This, however, is a point for the IAB and the ITU.

all the best,
   Lawrence

On 23 Apr 2004, at 11:33 am, jfcm wrote:
> At 23:49 22/04/04, Dean Anderson wrote:
>> Is it sensible to think of tel and mobi as business functions?
>
> Absolutely yes. As I noted it, there are at least two possiblities:
> - .tel is accepted as the TLD of the ITU-T Sector's members. The same 
> as for .aero. And .mobi is for all the companies, services, designers 
> interested in mobile product, services etc.
> - .tel is reserved to a class of users froming an "externet", ie. a 
> class of users with special relations/access terms. This can be an 
> economical model (rates), this can be a way of behaving (accepting or 
> not VoSpam), etc. This however calls for a large number of new 
> architectural concepts and naming semantic to be discussed and agreed 
> upon.
>
> But in both cases, it is likely it would then be premature to give 
> away such mnemonics as "tel" and "mobi" before a wide debate. ITU 
> expressed that in their letter of 2000 to ICANN. ICANN was wise to 
> agree. I think not much has changed.
> <snip>

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



From ietf-admin@ietf.org  Fri Apr 23 10:53: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 KAA12842
	for <ietf-archive@ietf.org>; Fri, 23 Apr 2004 10:53: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 1BH23I-0005dR-7V
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 10:53:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH22K-0005N3-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 10:52:17 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BH21p-00056w-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 10:51:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH1sR-0005mz-2W; Fri, 23 Apr 2004 10:42:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH1l8-0003fk-4K
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 10:34: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 KAA11967
	for <ietf@ietf.org>; Fri, 23 Apr 2004 10:34: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 1BH1jp-0000aB-4n
	for ietf@ietf.org; Fri, 23 Apr 2004 10:33:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH1ii-0000Iw-00
	for ietf@ietf.org; Fri, 23 Apr 2004 10:32:01 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BH1hm-0007bL-00
	for ietf@ietf.org; Fri, 23 Apr 2004 10:31:02 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ietf] 240.0.0.0/4
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Date: Fri, 23 Apr 2004 07:30:31 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB0CE@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: [Ietf] 240.0.0.0/4
thread-index: AcQpMnWBy8luPdjyRDWfa7yTfAs3oAADLg9g
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Daniel Senie" <dts@senie.com>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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

> Daniel Senie wrote:
> 2) Make available several chunks of space for RFC1918
> usage, perhaps a few /8's, a whole mess of /12's, and
> many /16's. This space does two things: First, it
> provides additional private address space, which is
> needed. Second, it provides a usage battleground for
> class E space testing. There is the very real
> possibility users of these blocks will run into
> trouble as vendors have special handling for class E.
> By allowing these to be discovered during use in
> private networks, there is a much better chance of
> public usage of these blocks later.
> I do NOT agree that the entire class E space should go
> to RFC 1918. That seems wasteful. But using some large
> chunks of space for that purpose clearly provides a
> test bed to prove out equipment before eventual public
> address usage in that region of IP address space.

Makes a lot of sense to me.

Michel.


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


From exim@www1.ietf.org  Fri Apr 23 10:59:57 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13112
	for <ietf-archive@odin.ietf.org>; Fri, 23 Apr 2004 10:59:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH21q-00082v-KS
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 10:51:46 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3NEpkiV030894
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 10:51:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH1sR-0005mz-2W; Fri, 23 Apr 2004 10:42:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH1l8-0003fk-4K
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 10:34: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 KAA11967
	for <ietf@ietf.org>; Fri, 23 Apr 2004 10:34: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 1BH1jp-0000aB-4n
	for ietf@ietf.org; Fri, 23 Apr 2004 10:33:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH1ii-0000Iw-00
	for ietf@ietf.org; Fri, 23 Apr 2004 10:32:01 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BH1hm-0007bL-00
	for ietf@ietf.org; Fri, 23 Apr 2004 10:31:02 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ietf] 240.0.0.0/4
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Date: Fri, 23 Apr 2004 07:30:31 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB0CE@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: [Ietf] 240.0.0.0/4
thread-index: AcQpMnWBy8luPdjyRDWfa7yTfAs3oAADLg9g
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Daniel Senie" <dts@senie.com>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>
Cc: "IETF Discussion" <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: quoted-printable

> Daniel Senie wrote:
> 2) Make available several chunks of space for RFC1918
> usage, perhaps a few /8's, a whole mess of /12's, and
> many /16's. This space does two things: First, it
> provides additional private address space, which is
> needed. Second, it provides a usage battleground for
> class E space testing. There is the very real
> possibility users of these blocks will run into
> trouble as vendors have special handling for class E.
> By allowing these to be discovered during use in
> private networks, there is a much better chance of
> public usage of these blocks later.
> I do NOT agree that the entire class E space should go
> to RFC 1918. That seems wasteful. But using some large
> chunks of space for that purpose clearly provides a
> test bed to prove out equipment before eventual public
> address usage in that region of IP address space.

Makes a lot of sense to me.

Michel.


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



From ietf-admin@ietf.org  Fri Apr 23 13:49: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 NAA23118
	for <ietf-archive@ietf.org>; Fri, 23 Apr 2004 13:49: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 1BH4na-0005lc-Gn
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 13:49:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH4ml-0005Vf-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 13:48:24 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BH4m3-0005GO-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 13:47:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH4Xv-0003ow-FE; Fri, 23 Apr 2004 13:33:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH4TK-0002ht-0v
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 13:28: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 NAA22023
	for <ietf@ietf.org>; Fri, 23 Apr 2004 13:28: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 1BH4TH-0000EY-8Z
	for ietf@ietf.org; Fri, 23 Apr 2004 13:28:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH4SL-0007ly-00
	for ietf@ietf.org; Fri, 23 Apr 2004 13:27:18 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BH4RV-0007W1-00
	for ietf@ietf.org; Fri, 23 Apr 2004 13:26:25 -0400
Received: from [199.212.90.29] (helo=[199.212.90.29])
	by felix.automagic.org with asmtp (TLSv1:RC4-SHA:128)
	(Exim 4.20)
	id 1BH4RQ-0000ji-1J; Fri, 23 Apr 2004 17:26:20 +0000
In-Reply-To: <6.1.0.6.2.20040423082618.04ec2ec0@127.0.0.1>
References: <6.0.1.1.2.20040420215955.01c06ec0@localhost> <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com> <6.0.1.1.2.20040420215955.01c06ec0@localhost> <4.3.2.7.2.20040420120953.02c645e0@mailhost.iprg.nokia.com> <6.1.0.6.2.20040423082618.04ec2ec0@127.0.0.1>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5392E306-954B-11D8-A8F5-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: Iljitsch van Beijnum <iljitsch@muada.com>,
        Bob Hinden <bob.hinden@nokia.com>, IETF Discussion <ietf@ietf.org>
From: Joe Abley <jabley@isc.org>
Subject: Re: [Ietf] 240.0.0.0/4
Date: Fri, 23 Apr 2004 13:26:16 -0400
To: Daniel Senie <dts@senie.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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 Apr 2004, at 08:37, Daniel Senie wrote:

> 2) Make available several chunks of space for RFC1918 usage, perhaps a 
> few /8's, a whole mess of /12's, and many /16's. This space does two 
> things: First, it provides additional private address space, which is 
> needed.

It is?


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


From exim@www1.ietf.org  Fri Apr 23 13:51:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23226
	for <ietf-archive@odin.ietf.org>; Fri, 23 Apr 2004 13:51:11 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH4m5-0008Rn-1S
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 13:47:46 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3NHlfPa032390
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 13:47:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH4Xv-0003ow-FE; Fri, 23 Apr 2004 13:33:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH4TK-0002ht-0v
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 13:28: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 NAA22023
	for <ietf@ietf.org>; Fri, 23 Apr 2004 13:28: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 1BH4TH-0000EY-8Z
	for ietf@ietf.org; Fri, 23 Apr 2004 13:28:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH4SL-0007ly-00
	for ietf@ietf.org; Fri, 23 Apr 2004 13:27:18 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BH4RV-0007W1-00
	for ietf@ietf.org; Fri, 23 Apr 2004 13:26:25 -0400
Received: from [199.212.90.29] (helo=[199.212.90.29])
	by felix.automagic.org with asmtp (TLSv1:RC4-SHA:128)
	(Exim 4.20)
	id 1BH4RQ-0000ji-1J; Fri, 23 Apr 2004 17:26:20 +0000
In-Reply-To: <6.1.0.6.2.20040423082618.04ec2ec0@127.0.0.1>
References: <6.0.1.1.2.20040420215955.01c06ec0@localhost> <7D88266F-92A3-11D8-A922-000A95CD987A@muada.com> <6.0.1.1.2.20040420215955.01c06ec0@localhost> <4.3.2.7.2.20040420120953.02c645e0@mailhost.iprg.nokia.com> <6.1.0.6.2.20040423082618.04ec2ec0@127.0.0.1>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5392E306-954B-11D8-A8F5-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: Iljitsch van Beijnum <iljitsch@muada.com>,
        Bob Hinden <bob.hinden@nokia.com>, IETF Discussion <ietf@ietf.org>
From: Joe Abley <jabley@isc.org>
Subject: Re: [Ietf] 240.0.0.0/4
Date: Fri, 23 Apr 2004 13:26:16 -0400
To: Daniel Senie <dts@senie.com>
X-Mailer: Apple Mail (2.613)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit


On 23 Apr 2004, at 08:37, Daniel Senie wrote:

> 2) Make available several chunks of space for RFC1918 usage, perhaps a 
> few /8's, a whole mess of /12's, and many /16's. This space does two 
> things: First, it provides additional private address space, which is 
> needed.

It is?


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



From ietf-admin@ietf.org  Fri Apr 23 15:41: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 PAA04413
	for <ietf-archive@ietf.org>; Fri, 23 Apr 2004 15:41: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 1BH6YR-0006Zu-7s
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 15:41:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH6W6-0005tJ-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 15:39:18 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BH6SX-0004rZ-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 15:35:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH6II-0004tG-Tz; Fri, 23 Apr 2004 15:25:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH6C5-0000c5-Ju
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 15:18: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 PAA02036
	for <ietf@ietf.org>; Fri, 23 Apr 2004 15:18: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 1BH6C4-0007Jl-3x
	for ietf@ietf.org; Fri, 23 Apr 2004 15:18:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH6B3-00072E-00
	for ietf@ietf.org; Fri, 23 Apr 2004 15:17:33 -0400
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1BH6AQ-0006ll-00
	for ietf@ietf.org; Fri, 23 Apr 2004 15:16:54 -0400
Received: (qmail 40378 invoked by uid 1013); 23 Apr 2004 19:16:53 -0000
Date: Fri, 23 Apr 2004 21:16:53 +0200
From: Markus Stumpf <maex-lists-ietf-general@Space.Net>
To: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <20040423191653.GB36933@Space.Net>
References: <6.0.1.1.2.20040422113940.04707730@mail.utel.net> <Pine.LNX.4.44.0404221021050.8863-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.0404221021050.8863-100000@cirrus.av8.net>
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
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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 Thu, Apr 22, 2004 at 10:29:03AM -0400, Dean Anderson wrote:
> I have to digest the rest of this further, but I would say right away that
> if I connect to http://ibm.tel, I'd probably expect to reach the VOIP
> portal, where I could sign up for VOIP services from IBM.  I'd expect that
> a voip connection to tel://ibm.com would get me to the headquarters
> switchboard, and that tel://ibm.tel gets me to the VOIP switchboard (ie
> VOIP customer service).

Hmmm ... 
    For instance, Internet addresses ending in ".mobi" would allow sites
    built for the small screens of mobile phones.

From that reading I'd conclude they have no interest in registering
another domain like
    ibm-mobile
    miscrosoft-mobile
and so on, but rather have a new TLD where they could put
    ibm.mobi
    microsoft.mobi
and so on.

There is no need for a .mobi (and why the hell don't they use .mobile)
domain in order to deliver optimized web pages/sites.

IMHO all these have their origin in that the "semantic web" is at best
a slow starter and they try to put sematics into the web by adding
"semantic TLDs".

So in the future we will see a lot more sponsored requests for new TLDs
like >>insert index of yellow pages<<.

	\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 exim@www1.ietf.org  Fri Apr 23 15:43:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04848
	for <ietf-archive@odin.ietf.org>; Fri, 23 Apr 2004 15:43:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH6SY-0000US-8N
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 15:35:38 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3NJZcb7001864
	for ietf-archive@odin.ietf.org; Fri, 23 Apr 2004 15:35:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH6II-0004tG-Tz; Fri, 23 Apr 2004 15:25:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BH6C5-0000c5-Ju
	for ietf@optimus.ietf.org; Fri, 23 Apr 2004 15:18: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 PAA02036
	for <ietf@ietf.org>; Fri, 23 Apr 2004 15:18: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 1BH6C4-0007Jl-3x
	for ietf@ietf.org; Fri, 23 Apr 2004 15:18:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH6B3-00072E-00
	for ietf@ietf.org; Fri, 23 Apr 2004 15:17:33 -0400
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1BH6AQ-0006ll-00
	for ietf@ietf.org; Fri, 23 Apr 2004 15:16:54 -0400
Received: (qmail 40378 invoked by uid 1013); 23 Apr 2004 19:16:53 -0000
Date: Fri, 23 Apr 2004 21:16:53 +0200
From: Markus Stumpf <maex-lists-ietf-general@Space.Net>
To: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <20040423191653.GB36933@Space.Net>
References: <6.0.1.1.2.20040422113940.04707730@mail.utel.net> <Pine.LNX.4.44.0404221021050.8863-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.0404221021050.8863-100000@cirrus.av8.net>
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Thu, Apr 22, 2004 at 10:29:03AM -0400, Dean Anderson wrote:
> I have to digest the rest of this further, but I would say right away that
> if I connect to http://ibm.tel, I'd probably expect to reach the VOIP
> portal, where I could sign up for VOIP services from IBM.  I'd expect that
> a voip connection to tel://ibm.com would get me to the headquarters
> switchboard, and that tel://ibm.tel gets me to the VOIP switchboard (ie
> VOIP customer service).

Hmmm ... 
    For instance, Internet addresses ending in ".mobi" would allow sites
    built for the small screens of mobile phones.

From that reading I'd conclude they have no interest in registering
another domain like
    ibm-mobile
    miscrosoft-mobile
and so on, but rather have a new TLD where they could put
    ibm.mobi
    microsoft.mobi
and so on.

There is no need for a .mobi (and why the hell don't they use .mobile)
domain in order to deliver optimized web pages/sites.

IMHO all these have their origin in that the "semantic web" is at best
a slow starter and they try to put sematics into the web by adding
"semantic TLDs".

So in the future we will see a lot more sponsored requests for new TLDs
like >>insert index of yellow pages<<.

	\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 NSMFV@physic.ut.ee  Fri Apr 23 17:14: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 RAA12482
	for <ietf-archive@ietf.org>; Fri, 23 Apr 2004 17:14: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 1BH802-000374-3L
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 17:14:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BH7wK-0002SO-00
	for ietf-archive@ietf.org; Fri, 23 Apr 2004 17:10:29 -0400
Received: from bgp01053319bgs.stclar01.mi.comcast.net ([68.43.104.68])
	by ietf-mx with smtp (Exim 4.12)
	id 1BH7v5-0001qC-00; Fri, 23 Apr 2004 17:09:11 -0400
Received: from 110.52.159.20 by 68.43.104.68; Fri, 23 Apr 2004 23:09:04 +0100
Message-ID: <LYMJQOKHALMTIYWLEFOGHQAU@tuiasi.ro>
From: "Nadia Hartley" <NSMFV@physic.ut.ee>
Reply-To: "Nadia Hartley" <NSMFV@physic.ut.ee>
To: ietf-archive@ietf.org
Cc: ietf-secretariat@ietf.org
Subject: get ready to shape up your riches w/ online auction
Date: Fri, 23 Apr 2004 23:06:04 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--89573081120298588"
X-Originating-IP: 132.151.6.1
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=BIZ_TLD,CLICK_BELOW,HTML_50_60,
	HTML_FONTCOLOR_RED,HTML_FONT_BIG,HTML_LINK_CLICK_HERE,HTML_MESSAGE,
	MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI autolearn=no version=2.60

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859=
-1">
<title>j2ldk 2j3lkd 2lkj</title>

<style type=3D"text/css">
<!--
style1 {font-size: 9px}
-->
</style>
</head>

<body>
<table width=3D"600" border=3D"1" cellpadding=3D"1" cellspacing=3D"1" bord=
ercolor=3D"#009900">
  <tr>
    <td bgcolor=3D"#99CC66">
      <table width=3D"600" border=3D"0" cellspacing=3D"0" cellpadding=3D"0=
">
      <tr>
        <td bgcolor=3D"#66FF00"> <table width=3D"600" border=3D"0" cellspa=
cing=3D"0" cellpadding=3D"0">
          <tr>
            <td bgcolor=3D"#FFFFFF"><p class=3D"style4"><font size=3D"4">W=
hy you should 
                    seriously consider making money with <span class=3D"st=
yle2">Online 
                    Auctions</span></font></p>
                  <p align=3D"center"><font size=3D"4">M</font><font size=3D=
"4">illions 
                    of people go to <font color=3D"#FF0000">ebay</font> to=
 buy and 
                    sell. Why aren't you there yet?</font></p>
                  <p align=3D"center"><font color=3D"#FF33FF" size=3D"4">I=
 will tell you how!</font></p>
              <UL><LI>You can get started quickly with very little investm=
ent.
                <LI>You can "work" a small amount of hours and start earni=
ng a part-time income pretty much right away. </LI>
                <LI>Since the business takes so little time, you can gradu=
ally build it into a full-time income before quitting your job, etc. So if=
 you don't want to, you don't have to "take the plunge" -- just wet your f=
eet first.</LI>
              </UL>
                  <p align=3D"center" class=3D"style4"><font size=3D"4"><a=
 href=3D"http://lepayscaisse.biz/ebay/index.htm">Start Making 
                    It <span class=3D"style2"><font color=3D"#FF0000">BIG<=
/font></span> 
                    Today. </a></font></p>
              <BR>              </td><p></p>
          </tr>
        </table></td>
      </tr>
    </table>    
    </td>
  </tr>
</table>
<p class=3D"style1">&nbsp;</p>
<p class=3D"style1">&nbsp;</p>
<p class=3D"style1">&nbsp;</p>
<p class=3D"style1">if you are unstatisified with this message <a href=3D"=
http://lepayscaisse.biz/takeoff/takeoff.html">click here</a> </p>
</body>
</html>


----89573081120298588--



From ietf-admin@ietf.org  Sat Apr 24 10:07: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 KAA15691
	for <ietf-archive@ietf.org>; Sat, 24 Apr 2004 10: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 1BHNoC-00008a-1f
	for ietf-archive@ietf.org; Sat, 24 Apr 2004 10:07:08 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BHNnF-0007gq-00
	for ietf-archive@ietf.org; Sat, 24 Apr 2004 10:06:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BHNdR-0000AS-NR; Sat, 24 Apr 2004 09:56:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BHNbU-0008F1-VO
	for ietf@optimus.ietf.org; Sat, 24 Apr 2004 09:54: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 JAA14883
	for <ietf@ietf.org>; Sat, 24 Apr 2004 09:53:58 -0400 (EDT)
From: paf@cisco.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BHNbT-0004en-0n
	for ietf@ietf.org; Sat, 24 Apr 2004 09:53:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BHNaZ-0004Or-00
	for ietf@ietf.org; Sat, 24 Apr 2004 09:53:04 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BHNZd-00049S-00
	for ietf@ietf.org; Sat, 24 Apr 2004 09:52:05 -0400
Received: from [219.95.35.181] (helo=ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BHNZW-0004dd-UR
	for ietf@ietf.org; Sat, 24 Apr 2004 09:52:00 -0400
To: ietf@ietf.org
Date: Sat, 24 Apr 2004 21:52:37 +0800
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA81.7B015D10"
X-Priority: 1
X-MSMail-Priority: High
Message-Id: <E1BHNZW-0004dd-UR@mx2.foretec.com>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.4 required=5.0 tests=HTML_30_40,HTML_MESSAGE,
	HTML_RELAYING_FRAME,MICROSOFT_EXECUTABLE,MIME_QP_DEFICIENT,
	MIME_SUSPECT_NAME,MISSING_MIMEOLE,NO_REAL_NAME,PRIORITY_NO_NAME,
	X_MSMAIL_PRIORITY_HIGH,X_PRIORITY_HIGH autolearn=no version=2.60
X-Spam-Report: 
	*  0.5 X_PRIORITY_HIGH Sent with 'X-Priority' set to high
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.5 X_MSMAIL_PRIORITY_HIGH Sent with 'X-Msmail-Priority' set to high
	*  0.8 HTML_30_40 BODY: Message is 30% to 40% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.3 HTML_RELAYING_FRAME BODY: Frame wanted to load outside URL
	*  1.8 MIME_QP_DEFICIENT RAW: Deficient quoted-printable encoding in body
	*  0.1 MIME_SUSPECT_NAME RAW: MIME filename does not match content
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Subject: [Ietf] Delivery Error (ietf@ietf.org)
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

This is a multi-part message in MIME format.

------=_NextPart_000_001B_01C0CA81.7B015D10
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

Found virus HTML_NETSKY.P in file email-body
The file email-body is moved to /etc/iscan/virus/virIIC1xbGrz.

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

------=_NextPart_000_001B_01C0CA81.7B015D10
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_001C_01C0CA81.7B015D10"

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

------=_NextPart_001_001C_01C0CA81.7B015D10
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

email-body is removed from here because it contains a virus.

---------------------------------------------------------
------=_NextPart_001_001C_01C0CA81.7B015D10--

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

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

------=_NextPart_000_001B_01C0CA81.7B015D10--



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


From exim@www1.ietf.org  Sat Apr 24 10:08:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15850
	for <ietf-archive@odin.ietf.org>; Sat, 24 Apr 2004 10:08:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BHNnG-0005pl-8L
	for ietf-archive@odin.ietf.org; Sat, 24 Apr 2004 10:06:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3OE6Aew022421
	for ietf-archive@odin.ietf.org; Sat, 24 Apr 2004 10:06:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BHNdR-0000AS-NR; Sat, 24 Apr 2004 09:56:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BHNbU-0008F1-VO
	for ietf@optimus.ietf.org; Sat, 24 Apr 2004 09:54: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 JAA14883
	for <ietf@ietf.org>; Sat, 24 Apr 2004 09:53:58 -0400 (EDT)
From: paf@cisco.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BHNbT-0004en-0n
	for ietf@ietf.org; Sat, 24 Apr 2004 09:53:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BHNaZ-0004Or-00
	for ietf@ietf.org; Sat, 24 Apr 2004 09:53:04 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BHNZd-00049S-00
	for ietf@ietf.org; Sat, 24 Apr 2004 09:52:05 -0400
Received: from [219.95.35.181] (helo=ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BHNZW-0004dd-UR
	for ietf@ietf.org; Sat, 24 Apr 2004 09:52:00 -0400
To: ietf@ietf.org
Date: Sat, 24 Apr 2004 21:52:37 +0800
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA81.7B015D10"
X-Priority: 1
X-MSMail-Priority: High
Message-Id: <E1BHNZW-0004dd-UR@mx2.foretec.com>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.4 required=5.0 tests=HTML_30_40,HTML_MESSAGE,
	HTML_RELAYING_FRAME,MICROSOFT_EXECUTABLE,MIME_QP_DEFICIENT,
	MIME_SUSPECT_NAME,MISSING_MIMEOLE,NO_REAL_NAME,PRIORITY_NO_NAME,
	X_MSMAIL_PRIORITY_HIGH,X_PRIORITY_HIGH autolearn=no version=2.60
X-Spam-Report: 
	*  0.5 X_PRIORITY_HIGH Sent with 'X-Priority' set to high
	*  0.3 NO_REAL_NAME From: does not include a real name
	*  0.5 X_MSMAIL_PRIORITY_HIGH Sent with 'X-Msmail-Priority' set to high
	*  0.8 HTML_30_40 BODY: Message is 30% to 40% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.3 HTML_RELAYING_FRAME BODY: Frame wanted to load outside URL
	*  1.8 MIME_QP_DEFICIENT RAW: Deficient quoted-printable encoding in body
	*  0.1 MIME_SUSPECT_NAME RAW: MIME filename does not match content
	*  0.1 MICROSOFT_EXECUTABLE RAW: Message includes Microsoft executable program
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  0.8 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
Subject: [Ietf] Delivery Error (ietf@ietf.org)
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

This is a multi-part message in MIME format.

------=_NextPart_000_001B_01C0CA81.7B015D10
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

Found virus HTML_NETSKY.P in file email-body
The file email-body is moved to /etc/iscan/virus/virIIC1xbGrz.

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

------=_NextPart_000_001B_01C0CA81.7B015D10
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_001C_01C0CA81.7B015D10"

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

------=_NextPart_001_001C_01C0CA81.7B015D10
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

email-body is removed from here because it contains a virus.

---------------------------------------------------------
------=_NextPart_001_001C_01C0CA81.7B015D10--

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

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

------=_NextPart_000_001B_01C0CA81.7B015D10--



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



From ietf-admin@ietf.org  Sat Apr 24 12:37: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 MAA22653
	for <ietf-archive@ietf.org>; Sat, 24 Apr 2004 12:37: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 1BHQ9V-0007h2-6Z
	for ietf-archive@ietf.org; Sat, 24 Apr 2004 12:37:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BHQ8X-0007PV-00
	for ietf-archive@ietf.org; Sat, 24 Apr 2004 12:36:18 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BHQ7i-00079I-00
	for ietf-archive@ietf.org; Sat, 24 Apr 2004 12:35:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BHQ0Y-0001TO-Us; Sat, 24 Apr 2004 12:28:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BHPwi-0000nu-RE
	for ietf@optimus.ietf.org; Sat, 24 Apr 2004 12:24: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 MAA22042
	for <ietf@ietf.org>; Sat, 24 Apr 2004 12:24: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 1BHPwh-0004H8-9R
	for ietf@ietf.org; Sat, 24 Apr 2004 12:24:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BHPvh-00040G-00
	for ietf@ietf.org; Sat, 24 Apr 2004 12:23:02 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BHPug-0003VN-00
	for ietf@ietf.org; Sat, 24 Apr 2004 12:21:58 -0400
Received: from f02v-32-182.d0.club-internet.fr ([212.195.235.182] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BHPuS-00077x-La; Sat, 24 Apr 2004 09:21:45 -0700
Message-Id: <6.0.1.1.2.20040424130629.05764330@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sat, 24 Apr 2004 13:34:06 +0200
To: Markus Stumpf <maex-lists-ietf-general@Space.Net>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <20040423191653.GB36933@Space.Net>
References: <6.0.1.1.2.20040422113940.04707730@mail.utel.net>
 <Pine.LNX.4.44.0404221021050.8863-100000@cirrus.av8.net>
 <20040423191653.GB36933@Space.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 - utel.net
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,DATE_IN_PAST_03_06 
	autolearn=no version=2.60

Dear Markus,
to know where your remarks may lead, let come back to 1993.

At 21:16 23/04/04, Markus Stumpf wrote:
>Hmmm ...
>     For instance, Internet addresses ending in ".mobi" would allow sites
>     built for the small screens of mobile phones.

For instance, Internet addresses (names?) ending in ".web" would
allow sites supporting "world wide web" screens.

Ten years before Jon Postel should have started with ".ftp".

> >From that reading I'd conclude they have no interest in registering
>another domain like
>     ibm-mobile
>     miscrosoft-mobile
>and so on, but rather have a new TLD where they could put
>     ibm.mobi
>     microsoft.mobi
>and so on.

What about http://mobi.ibm.com
IMHO it fits with the right to left concept ? (and is in line with the 
structural semantics below). And costs nothing. And does not add any load 
to the DNS. Actually, I tend to think it is why the DNS was designed ?

>here is no need for a .mobi (and why the hell don't they use .mobile)
>domain in order to deliver optimized web pages/sites.

There is a very simple standard way: mobi://ibm.com - it calls for serious 
technical discussions.

>IMHO all these have their origin in that the "semantic web" is at best
>a slow starter and they try to put sematics into the web by adding
>"semantic TLDs".

"Semantic web" is only DNC (Domain Name Confusion) unless it uses a correct 
grammar (oherwise there will be nothing to sell even for the worst 
merchant). Grammar says the protocol is in the scheme, the intefaces in 
upper level names, domain name in the SLD and the interneted network in the 
TLD. Initially the internetted neworks were physically or geographically 
separated (Tymnet, telenet, ARPANET, CSNET, DOD, Transpac, Datex-P, PSS, 
etc.) while now they are mostly virtual (.com, .fr, .us, .int, .aero). But 
there a TLD is the name of a group of users or the flag of their common 
global interest. Not the size of the screen they use for a few months.

This is precesily because because a name is to designate a lof of different 
applications and machines that it is called a "domain" name. Or should we 
propose ".80" for all the connections to port 80 ?

Let not kill something which works!

There is nothing against a sub-scheme like http-mobi://ibm.com. While the 
"mobi" demand is a grammatical error as a TLD, it is perfectly legitimate 
as a request to the W3C. If the motivation is the service of the users, 
this should be the IAB/IETF advice.

If the only motivation is greed and market control, IETF cannot comment.But 
it can tell how large common interest zones should be managed by multiple 
virtual zones co-registries - because IDNA will need it, to start with.

>So in the future we will see a lot more sponsored requests for new TLDs
>like >>insert index of yellow pages<<.

Right. But RFC 920/1591 do not think of them as commercial private 
ventures. They think of them as directory members trustees. I feel this is 
wise thinking : IANA is not in the business of deciding what is a yellow 
page entry (people sharing the same interest or the same location - not the 
same salesman). But there are a few technical words to help them working : 
non profit, to the benefit of the global community, equal access for 
everyone matching the charter, registrants self-governance, no generic 
names for specific groups. To avoid conflicts, because conflicts are just a 
sign of the users confusion.

jfc


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


From exim@www1.ietf.org  Sat Apr 24 12:40:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22885
	for <ietf-archive@odin.ietf.org>; Sat, 24 Apr 2004 12:40:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BHQ7i-0004HD-Ka
	for ietf-archive@odin.ietf.org; Sat, 24 Apr 2004 12:35:26 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3OGZQew016435
	for ietf-archive@odin.ietf.org; Sat, 24 Apr 2004 12:35:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BHQ0Y-0001TO-Us; Sat, 24 Apr 2004 12:28:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BHPwi-0000nu-RE
	for ietf@optimus.ietf.org; Sat, 24 Apr 2004 12:24: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 MAA22042
	for <ietf@ietf.org>; Sat, 24 Apr 2004 12:24: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 1BHPwh-0004H8-9R
	for ietf@ietf.org; Sat, 24 Apr 2004 12:24:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BHPvh-00040G-00
	for ietf@ietf.org; Sat, 24 Apr 2004 12:23:02 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BHPug-0003VN-00
	for ietf@ietf.org; Sat, 24 Apr 2004 12:21:58 -0400
Received: from f02v-32-182.d0.club-internet.fr ([212.195.235.182] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BHPuS-00077x-La; Sat, 24 Apr 2004 09:21:45 -0700
Message-Id: <6.0.1.1.2.20040424130629.05764330@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sat, 24 Apr 2004 13:34:06 +0200
To: Markus Stumpf <maex-lists-ietf-general@Space.Net>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <20040423191653.GB36933@Space.Net>
References: <6.0.1.1.2.20040422113940.04707730@mail.utel.net>
 <Pine.LNX.4.44.0404221021050.8863-100000@cirrus.av8.net>
 <20040423191653.GB36933@Space.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 - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,DATE_IN_PAST_03_06 
	autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

Dear Markus,
to know where your remarks may lead, let come back to 1993.

At 21:16 23/04/04, Markus Stumpf wrote:
>Hmmm ...
>     For instance, Internet addresses ending in ".mobi" would allow sites
>     built for the small screens of mobile phones.

For instance, Internet addresses (names?) ending in ".web" would
allow sites supporting "world wide web" screens.

Ten years before Jon Postel should have started with ".ftp".

> >From that reading I'd conclude they have no interest in registering
>another domain like
>     ibm-mobile
>     miscrosoft-mobile
>and so on, but rather have a new TLD where they could put
>     ibm.mobi
>     microsoft.mobi
>and so on.

What about http://mobi.ibm.com
IMHO it fits with the right to left concept ? (and is in line with the 
structural semantics below). And costs nothing. And does not add any load 
to the DNS. Actually, I tend to think it is why the DNS was designed ?

>here is no need for a .mobi (and why the hell don't they use .mobile)
>domain in order to deliver optimized web pages/sites.

There is a very simple standard way: mobi://ibm.com - it calls for serious 
technical discussions.

>IMHO all these have their origin in that the "semantic web" is at best
>a slow starter and they try to put sematics into the web by adding
>"semantic TLDs".

"Semantic web" is only DNC (Domain Name Confusion) unless it uses a correct 
grammar (oherwise there will be nothing to sell even for the worst 
merchant). Grammar says the protocol is in the scheme, the intefaces in 
upper level names, domain name in the SLD and the interneted network in the 
TLD. Initially the internetted neworks were physically or geographically 
separated (Tymnet, telenet, ARPANET, CSNET, DOD, Transpac, Datex-P, PSS, 
etc.) while now they are mostly virtual (.com, .fr, .us, .int, .aero). But 
there a TLD is the name of a group of users or the flag of their common 
global interest. Not the size of the screen they use for a few months.

This is precesily because because a name is to designate a lof of different 
applications and machines that it is called a "domain" name. Or should we 
propose ".80" for all the connections to port 80 ?

Let not kill something which works!

There is nothing against a sub-scheme like http-mobi://ibm.com. While the 
"mobi" demand is a grammatical error as a TLD, it is perfectly legitimate 
as a request to the W3C. If the motivation is the service of the users, 
this should be the IAB/IETF advice.

If the only motivation is greed and market control, IETF cannot comment.But 
it can tell how large common interest zones should be managed by multiple 
virtual zones co-registries - because IDNA will need it, to start with.

>So in the future we will see a lot more sponsored requests for new TLDs
>like >>insert index of yellow pages<<.

Right. But RFC 920/1591 do not think of them as commercial private 
ventures. They think of them as directory members trustees. I feel this is 
wise thinking : IANA is not in the business of deciding what is a yellow 
page entry (people sharing the same interest or the same location - not the 
same salesman). But there are a few technical words to help them working : 
non profit, to the benefit of the global community, equal access for 
everyone matching the charter, registrants self-governance, no generic 
names for specific groups. To avoid conflicts, because conflicts are just a 
sign of the users confusion.

jfc


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



From uvdpnudseiu@2xs.net  Sat Apr 24 19:10:18 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12474
	for <ietf-archive@ietf.org>; Sat, 24 Apr 2004 19:10: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 1BHWHr-0005wG-A2
	for ietf-archive@ietf.org; Sat, 24 Apr 2004 19:10:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BHWGu-0005h9-00
	for ietf-archive@ietf.org; Sat, 24 Apr 2004 19:09:20 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BHWFw-0005RQ-00
	for ietf-archive@ietf.org; Sat, 24 Apr 2004 19:08:20 -0400
Received: from 66-191-100-87.euc.wi.charter.com ([66.191.100.87])
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1BHWFv-0005VH-Nd
	for ietf-archive@ietf.org; Sat, 24 Apr 2004 19:08:21 -0400
Received: from [196.160.73.180] by 66.191.100.87 via HTTP; Sat, 24 Apr 2004 21:11:02 -0300
Date: Sat, 24 Apr 2004 18:11:02 -0600
From: "Camille Hooks" <uvdpnudseiu@2xs.net>
Subject: Re: Get Any Pills. Our Doctors Write Prescriptions. Overnight FedEx. Secure. Discreet
To: ietf-archive@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1141305384-1154736446=:39871"
Message-Id: <E1BHWFv-0005VH-Nd@mx2.foretec.com>
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=BIZ_TLD,HTML_40_50,
	HTML_FONTCOLOR_UNSAFE,HTML_MESSAGE,MIME_HTML_NO_CHARSET,
	MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI autolearn=no version=2.60

--0-1141305384-1154736446=:39871
Content-Type: text/html;
Content-Transfer-Encoding: 7Bit

<html><head><style type="text/css"><!-- .style5 {font-family: Arial, Helvetica, sans-serif; font-size: 14px; } .style6 {font-size: 10px} --></style></head>
<body>
<p class="style5">Hel</hzwgev>lo,</p>
<p class="style5">we mak</zzpo>e it ea</hslm>sier and fa</isajox>ster th</qprkg>an ever to get the med</wlpuaq>icati</vpuoo>ons you ne</wnb>ed!<br>
  <br>
<strong>Cia</kjntr>lis, Phe</mxt>nte</gfh>rmine, Via</ofm>gra, So</cfxjd>ma, Am</gcqx>bien, Levi</xfvqz>tra, Flor</dkcm>icet, Imi</zbboix>trex, Pa</nomeq>xil, Pro</loj>zac, Zol</rsqs>oft,</strong> and ma</gphw>ny ma</raovyx>ny more pres</bggmf>cript</hhdmm>ion dru</izvo>gs! </p>
<p class="style5">Ord</exdni>er by<b> 2 pm E</xnrzb>ST</b> and y</qdqqw>ou <b>get</b> your me</xjlta>ds <b>tomo</eybid>rrow</b>.</p>
<p class="style5"><a href="http://www.ppgx.vsalsa71rx.biz/g17/"><b>Sta</wauyf>rt Orde</egtlpb>ring yo</bpvpu>ur Me</rgwvv>dicati</ijk>ons He</bvrjl>re</b></a></p>
<p style="font-size:0px; color:white" align="left">Uprorogue loquacity taketh simpleminded serine jerome bernadine certify sloven budge imperfect ballard capacitor mckay original switchgear won spearmint annie  !!! Jteem purine theorem committeewomen sphagnum cognition disposal : Ywaveguide avail dollop knockout militiamen eighty whittaker on bypath penurious jacksonville sybil fredericksburg domain courtesy martini cynthia muscat balboa annale around ceremony bessie backside thor merciful veracious ichneumon chairwoman screwball emirate contribution varistor advisee astound hobbyhorse foregoing masonic crescendo boisterous sixteenth storyteller .</p>

<P align="LEFT"><FONT COLOR="#616161" SIZE="-2" FACE="Arial">I</kna>f th</cqm>is
no</bfcqv>tice has rea</hneoij>ched y</zrj>ou in er</lwyl>ror, ple</lrzdm>ase not</sgo>ify us by</FONT><FONT
 COLOR="#d5d5d0" SIZE="-2" FACE="Arial"> </FONT><FONT SIZE="-2"
 FACE="Arial"><A HREF="http://www.fqrzd.vsalsa71rx.biz/unsubscribe.ddd">clic</brcdr>king
he</ydmn>re</A></FONT>
</body>
</html> 


--0-1141305384-1154736446=:39871--



From exim@www1.ietf.org  Mon Apr 26 13:42:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04940
	for <ietf-archive@odin.ietf.org>; Mon, 26 Apr 2004 13:42:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI9sA-0006ca-VO
	for ietf-archive@odin.ietf.org; Mon, 26 Apr 2004 13:26:30 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3QHQQHq025449
	for ietf-archive@odin.ietf.org; Mon, 26 Apr 2004 13:26:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI9h9-000305-K0; Mon, 26 Apr 2004 13:15:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI9Zd-0000f2-PA
	for ietf@optimus.ietf.org; Mon, 26 Apr 2004 13:07: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 NAA03148
	for <ietf@ietf.org>; Mon, 26 Apr 2004 13:07: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 1BI9Za-0006Ob-GK
	for ietf@ietf.org; Mon, 26 Apr 2004 13:07:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BI9Yj-0006JP-00
	for ietf@ietf.org; Mon, 26 Apr 2004 13:06:22 -0400
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1BI9YD-0006EZ-00
	for ietf@ietf.org; Mon, 26 Apr 2004 13:05:50 -0400
Received: (qmail 28369 invoked by uid 1013); 26 Apr 2004 17:05:46 -0000
Date: Mon, 26 Apr 2004 19:05:46 +0200
From: Markus Stumpf <maex-lists-ietf-general@Space.Net>
To: ietf@ietf.org, jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <20040426170546.GE42774@Space.Net>
References: <6.0.1.1.2.20040422113940.04707730@mail.utel.net> <Pine.LNX.4.44.0404221021050.8863-100000@cirrus.av8.net> <20040423191653.GB36933@Space.Net> <6.0.1.1.2.20040424130629.05764330@mail.utel.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.0.1.1.2.20040424130629.05764330@mail.utel.net>
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Sat, Apr 24, 2004 at 01:34:06PM +0200, jfcm wrote:
> Dear Markus,
> to know where your remarks may lead, let come back to 1993.

You mean like in
http://ksi.cpsc.ucalgary.ca/archives/WWW-TALK/www-talk-1993q4.messages/579.html

> At 21:16 23/04/04, Markus Stumpf wrote:
> >Hmmm ...
> >    For instance, Internet addresses ending in ".mobi" would allow sites
> >    built for the small screens of mobile phones.

This was a cite from the article, not my opinion!
If it wasn't clear from my posting: I am *against* those new TLDs.

> >IMHO all these have their origin in that the "semantic web" is at best
> >a slow starter and they try to put sematics into the web by adding
> >"semantic TLDs".
> 
> "Semantic web" is only DNC (Domain Name Confusion) unless it uses a correct 
> grammar (oherwise there will be nothing to sell even for the worst 
> merchant). Grammar says the protocol is in the scheme, the intefaces in 
> upper level names, domain name in the SLD and the interneted network in the 
> TLD.

You are talking about IMHO the syntax of URLs, I am talking about
    http://www.w3.org/2001/sw/
and
    http://www.scientificamerican.com/article.cfm?articleID=00048144-10D2-1C70-84A9809EC588EF21&catID=2
where people would probably stop abusing DNS domains as registers
for marketing, to reflect content in the domain name.

	\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-admin@ietf.org  Mon Apr 26 13:42: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 NAA05049
	for <ietf-archive@ietf.org>; Mon, 26 Apr 2004 13:42: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 1BIA85-00017T-QP
	for ietf-archive@ietf.org; Mon, 26 Apr 2004 13:42:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIA79-0000yP-00
	for ietf-archive@ietf.org; Mon, 26 Apr 2004 13:41:55 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIA5t-0000nB-01
	for ietf-archive@ietf.org; Mon, 26 Apr 2004 13:40:38 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BI9sH-0005pB-R5
	for ietf-archive@ietf.org; Mon, 26 Apr 2004 13:26:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI9h9-000305-K0; Mon, 26 Apr 2004 13:15:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BI9Zd-0000f2-PA
	for ietf@optimus.ietf.org; Mon, 26 Apr 2004 13:07: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 NAA03148
	for <ietf@ietf.org>; Mon, 26 Apr 2004 13:07: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 1BI9Za-0006Ob-GK
	for ietf@ietf.org; Mon, 26 Apr 2004 13:07:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BI9Yj-0006JP-00
	for ietf@ietf.org; Mon, 26 Apr 2004 13:06:22 -0400
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1BI9YD-0006EZ-00
	for ietf@ietf.org; Mon, 26 Apr 2004 13:05:50 -0400
Received: (qmail 28369 invoked by uid 1013); 26 Apr 2004 17:05:46 -0000
Date: Mon, 26 Apr 2004 19:05:46 +0200
From: Markus Stumpf <maex-lists-ietf-general@Space.Net>
To: ietf@ietf.org, jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <20040426170546.GE42774@Space.Net>
References: <6.0.1.1.2.20040422113940.04707730@mail.utel.net> <Pine.LNX.4.44.0404221021050.8863-100000@cirrus.av8.net> <20040423191653.GB36933@Space.Net> <6.0.1.1.2.20040424130629.05764330@mail.utel.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.0.1.1.2.20040424130629.05764330@mail.utel.net>
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
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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 Sat, Apr 24, 2004 at 01:34:06PM +0200, jfcm wrote:
> Dear Markus,
> to know where your remarks may lead, let come back to 1993.

You mean like in
http://ksi.cpsc.ucalgary.ca/archives/WWW-TALK/www-talk-1993q4.messages/579.html

> At 21:16 23/04/04, Markus Stumpf wrote:
> >Hmmm ...
> >    For instance, Internet addresses ending in ".mobi" would allow sites
> >    built for the small screens of mobile phones.

This was a cite from the article, not my opinion!
If it wasn't clear from my posting: I am *against* those new TLDs.

> >IMHO all these have their origin in that the "semantic web" is at best
> >a slow starter and they try to put sematics into the web by adding
> >"semantic TLDs".
> 
> "Semantic web" is only DNC (Domain Name Confusion) unless it uses a correct 
> grammar (oherwise there will be nothing to sell even for the worst 
> merchant). Grammar says the protocol is in the scheme, the intefaces in 
> upper level names, domain name in the SLD and the interneted network in the 
> TLD.

You are talking about IMHO the syntax of URLs, I am talking about
    http://www.w3.org/2001/sw/
and
    http://www.scientificamerican.com/article.cfm?articleID=00048144-10D2-1C70-84A9809EC588EF21&catID=2
where people would probably stop abusing DNS domains as registers
for marketing, to reflect content in the domain name.

	\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-admin@ietf.org  Mon Apr 26 22:10: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 WAA10647
	for <ietf-archive@ietf.org>; Mon, 26 Apr 2004 22:10: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 1BII3I-0007lB-L7
	for ietf-archive@ietf.org; Mon, 26 Apr 2004 22:10:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BII2G-0007e3-00
	for ietf-archive@ietf.org; Mon, 26 Apr 2004 22:09:25 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BII1I-0007Wz-00
	for ietf-archive@ietf.org; Mon, 26 Apr 2004 22:08:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIHv8-00076p-Gm; Mon, 26 Apr 2004 22:02:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIHsn-0006rj-N2
	for ietf@optimus.ietf.org; Mon, 26 Apr 2004 21:59: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 VAA10089
	for <ietf@ietf.org>; Mon, 26 Apr 2004 21:59: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 1BIHsi-0006SF-8V
	for ietf@ietf.org; Mon, 26 Apr 2004 21:59:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIHro-0006M5-00
	for ietf@ietf.org; Mon, 26 Apr 2004 21:58:37 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.sea)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIHr4-00069Q-00
	for ietf@ietf.org; Mon, 26 Apr 2004 21:57:50 -0400
Received: from stephen (ip161.post-vineyard.dfw.ygnition.net [66.135.181.161])
	by ns2.sea (8.12.11/8.12.5) with SMTP id i3R1uSTG013341;
	Mon, 26 Apr 2004 18:56:29 -0700
Message-ID: <07b101c42bfa$dee5b170$6401a8c0@stephen>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Dean Anderson" <dean@av8.com>, "jfcm" <info@utel.net>
Cc: "Tim Chown" <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
References: <Pine.LNX.4.44.0404221021050.8863-100000@cirrus.av8.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Mon, 26 Apr 2004 20:41:25 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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 "Dean Anderson" <dean@av8.com>
> On Thu, 22 Apr 2004, jfcm wrote:
> > ".tel" and ".mobi" are technically inconsistent propositions. They
confuse
> > what belongs to the scheme (protocol/application) with what  belongs to
the
> > naming (users group). The same as was ".web" did in 2000.
> > ...
>
> I have to digest the rest of this further, but I would say right away that
> if I connect to http://ibm.tel, I'd probably expect to reach the VOIP
> portal, where I could sign up for VOIP services from IBM.  I'd expect that
> a voip connection to tel://ibm.com would get me to the headquarters
> switchboard, and that tel://ibm.tel gets me to the VOIP switchboard (ie
> VOIP customer service).

You're confusing URI methods, protocols, and TLDs disastrously.

The "tel" URI method is for dialing using E.164 numbers, e.g.
"tel:+18005551212", which will probably be translated to a different URI via
ENUM.  For telephones using user/domain names, use the "sip" URI method,
e.g. "sip:support@example.com".  There is no need for a .tel TLD, and adding
one ignores existing, logical solutions.

Likewise, there is no reason for a .mobi TLD; either mobile clients should
use the standard "http" method to negotiate the content/format/encoding with
servers as needed via HTTP's existing mechanisms, or if necessary a new
method/protocol should be defined, e.g. "wap://www.example.com/".

S

Stephen Sprunk        "Stupid people surround themselves with smart
CCIE #3723           people.  Smart people surround themselves with
K5SSS         smart people who disagree with them."  --Aaron Sorkin


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


From exim@www1.ietf.org  Mon Apr 26 22:15:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10897
	for <ietf-archive@odin.ietf.org>; Mon, 26 Apr 2004 22:15:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BII1K-000052-Q3
	for ietf-archive@odin.ietf.org; Mon, 26 Apr 2004 22:08:27 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3R28QcX000304
	for ietf-archive@odin.ietf.org; Mon, 26 Apr 2004 22:08:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIHv8-00076p-Gm; Mon, 26 Apr 2004 22:02:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIHsn-0006rj-N2
	for ietf@optimus.ietf.org; Mon, 26 Apr 2004 21:59: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 VAA10089
	for <ietf@ietf.org>; Mon, 26 Apr 2004 21:59: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 1BIHsi-0006SF-8V
	for ietf@ietf.org; Mon, 26 Apr 2004 21:59:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIHro-0006M5-00
	for ietf@ietf.org; Mon, 26 Apr 2004 21:58:37 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.sea)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIHr4-00069Q-00
	for ietf@ietf.org; Mon, 26 Apr 2004 21:57:50 -0400
Received: from stephen (ip161.post-vineyard.dfw.ygnition.net [66.135.181.161])
	by ns2.sea (8.12.11/8.12.5) with SMTP id i3R1uSTG013341;
	Mon, 26 Apr 2004 18:56:29 -0700
Message-ID: <07b101c42bfa$dee5b170$6401a8c0@stephen>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Dean Anderson" <dean@av8.com>, "jfcm" <info@utel.net>
Cc: "Tim Chown" <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
References: <Pine.LNX.4.44.0404221021050.8863-100000@cirrus.av8.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Mon, 26 Apr 2004 20:41:25 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Thus spake "Dean Anderson" <dean@av8.com>
> On Thu, 22 Apr 2004, jfcm wrote:
> > ".tel" and ".mobi" are technically inconsistent propositions. They
confuse
> > what belongs to the scheme (protocol/application) with what  belongs to
the
> > naming (users group). The same as was ".web" did in 2000.
> > ...
>
> I have to digest the rest of this further, but I would say right away that
> if I connect to http://ibm.tel, I'd probably expect to reach the VOIP
> portal, where I could sign up for VOIP services from IBM.  I'd expect that
> a voip connection to tel://ibm.com would get me to the headquarters
> switchboard, and that tel://ibm.tel gets me to the VOIP switchboard (ie
> VOIP customer service).

You're confusing URI methods, protocols, and TLDs disastrously.

The "tel" URI method is for dialing using E.164 numbers, e.g.
"tel:+18005551212", which will probably be translated to a different URI via
ENUM.  For telephones using user/domain names, use the "sip" URI method,
e.g. "sip:support@example.com".  There is no need for a .tel TLD, and adding
one ignores existing, logical solutions.

Likewise, there is no reason for a .mobi TLD; either mobile clients should
use the standard "http" method to negotiate the content/format/encoding with
servers as needed via HTTP's existing mechanisms, or if necessary a new
method/protocol should be defined, e.g. "wap://www.example.com/".

S

Stephen Sprunk        "Stupid people surround themselves with smart
CCIE #3723           people.  Smart people surround themselves with
K5SSS         smart people who disagree with them."  --Aaron Sorkin


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



From ietf-admin@ietf.org  Tue Apr 27 03:27: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 DAA10723
	for <ietf-archive@ietf.org>; Tue, 27 Apr 2004 03:27: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 1BIN0Q-0000GS-FO
	for ietf-archive@ietf.org; Tue, 27 Apr 2004 03:27:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIMzY-00004b-00
	for ietf-archive@ietf.org; Tue, 27 Apr 2004 03:26:57 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIMyr-0007gz-00
	for ietf-archive@ietf.org; Tue, 27 Apr 2004 03:26:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIMq1-0005qZ-Du; Tue, 27 Apr 2004 03:17:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIMi3-0004zT-6r
	for ietf@optimus.ietf.org; Tue, 27 Apr 2004 03:08:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09834
	for <ietf@ietf.org>; Tue, 27 Apr 2004 03: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 1BIMhz-0004mX-81
	for ietf@ietf.org; Tue, 27 Apr 2004 03:08:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIMh5-0004ay-00
	for ietf@ietf.org; Tue, 27 Apr 2004 03:07:51 -0400
Received: from [203.196.146.203] (helo=icope.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1BIMg1-0004E6-00
	for ietf@ietf.org; Tue, 27 Apr 2004 03:06:46 -0400
Message-ID: <006d01c42c27$65acd9f0$0502000a@icope.com>
From: "Vishal Agarwal" <vagarwal@icope.com>
To: <ietf@ietf.org>
Date: Tue, 27 Apr 2004 12:45:19 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_006A_01C42C55.7F5BEE30"
Subject: [Ietf] SIP Stack start off
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

------=_NextPart_000_006A_01C42C55.7F5BEE30
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

i am a fresh computer graduate. i want to develop an application using =
the free available sip stack in /c++, can anyone help me in deceiding a =
better one and provide me the link for the same.
i also want to have a proper documentation of the satck and plz plz tell =
me how to start off with it. What functionality and concepts do i have =
to make use of.
------=_NextPart_000_006A_01C42C55.7F5BEE30
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.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>i am a fresh computer graduate. i want =
to develop=20
an application using the free available sip stack in /c++, can anyone =
help me in=20
deceiding a better one and provide me the link for the =
same.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>i also want to have a proper =
documentation of the=20
satck and plz plz tell me how to start off with it. What functionality =
and=20
concepts do i have to make use of.</FONT></DIV></BODY></HTML>

------=_NextPart_000_006A_01C42C55.7F5BEE30--


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


From exim@www1.ietf.org  Tue Apr 27 03:31:16 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10932
	for <ietf-archive@odin.ietf.org>; Tue, 27 Apr 2004 03:31:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIMys-0006r4-N1
	for ietf-archive@odin.ietf.org; Tue, 27 Apr 2004 03:26:14 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3R7QEbq026315
	for ietf-archive@odin.ietf.org; Tue, 27 Apr 2004 03:26:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIMq1-0005qZ-Du; Tue, 27 Apr 2004 03:17:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIMi3-0004zT-6r
	for ietf@optimus.ietf.org; Tue, 27 Apr 2004 03:08:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09834
	for <ietf@ietf.org>; Tue, 27 Apr 2004 03: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 1BIMhz-0004mX-81
	for ietf@ietf.org; Tue, 27 Apr 2004 03:08:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIMh5-0004ay-00
	for ietf@ietf.org; Tue, 27 Apr 2004 03:07:51 -0400
Received: from [203.196.146.203] (helo=icope.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1BIMg1-0004E6-00
	for ietf@ietf.org; Tue, 27 Apr 2004 03:06:46 -0400
Message-ID: <006d01c42c27$65acd9f0$0502000a@icope.com>
From: "Vishal Agarwal" <vagarwal@icope.com>
To: <ietf@ietf.org>
Date: Tue, 27 Apr 2004 12:45:19 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_006A_01C42C55.7F5BEE30"
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
Subject: [Ietf] SIP Stack start off
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

This is a multi-part message in MIME format.

------=_NextPart_000_006A_01C42C55.7F5BEE30
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

i am a fresh computer graduate. i want to develop an application using =
the free available sip stack in /c++, can anyone help me in deceiding a =
better one and provide me the link for the same.
i also want to have a proper documentation of the satck and plz plz tell =
me how to start off with it. What functionality and concepts do i have =
to make use of.
------=_NextPart_000_006A_01C42C55.7F5BEE30
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.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>i am a fresh computer graduate. i want =
to develop=20
an application using the free available sip stack in /c++, can anyone =
help me in=20
deceiding a better one and provide me the link for the =
same.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>i also want to have a proper =
documentation of the=20
satck and plz plz tell me how to start off with it. What functionality =
and=20
concepts do i have to make use of.</FONT></DIV></BODY></HTML>

------=_NextPart_000_006A_01C42C55.7F5BEE30--


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



From ietf-admin@ietf.org  Tue Apr 27 18:26: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 SAA06935
	for <ietf-archive@ietf.org>; Tue, 27 Apr 2004 18:26: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 1BIb1k-00046e-C7
	for ietf-archive@ietf.org; Tue, 27 Apr 2004 18:26:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIb0o-0003xd-00
	for ietf-archive@ietf.org; Tue, 27 Apr 2004 18:25:11 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIazp-0003pR-00
	for ietf-archive@ietf.org; Tue, 27 Apr 2004 18:24:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIap7-0002RO-IM; Tue, 27 Apr 2004 18:13:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIaii-0007RO-EM
	for ietf@optimus.ietf.org; Tue, 27 Apr 2004 18:06:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05173
	for <ietf@ietf.org>; Tue, 27 Apr 2004 18:06: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 1BIaid-0001ty-59
	for ietf@ietf.org; Tue, 27 Apr 2004 18:06:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIahk-0001lT-00
	for ietf@ietf.org; Tue, 27 Apr 2004 18:05:28 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIagx-0001bA-00
	for ietf@ietf.org; Tue, 27 Apr 2004 18:04:39 -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 i3RM41Tt028232
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 27 Apr 2004 18:04:05 -0400
Date: Tue, 27 Apr 2004 18:04:01 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Stephen Sprunk <stephen@sprunk.org>
cc: jfcm <info@utel.net>, Tim Chown <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <07b101c42bfa$dee5b170$6401a8c0@stephen>
Message-ID: <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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 Mon, 26 Apr 2004, Stephen Sprunk wrote:

> 
> You're confusing URI methods, protocols, and TLDs disastrously.

I think it is you who is reading too much into the .tel and .mobi TLD.

These are not proposals to put URI method functionality into domain names,
but to qualify general business types, such as telephone companies, and
mobile phone companies.  This is no different from using .museum for
museums and .aero to represent aerospace companies.

The URI method tel: was a bad example, but otherwise completely
orthogonal to the intelligibility of using .tel and .mobi TLDs.  

Let me restate without using the tel: method:  

The URL

	somemethod://cellularone.mobi

Has a completely intelligible and meaningful interpretation. It is 
different from the following

	sip://cellularone.mobi
	http://cellularone.mobi
	telnet://cellularone.mobi
	etc.

Similarly,

	sip://verizon.tel

Is meaningful, and intelligible.

So what is the _technical_ problem with having .tel and .mobi TLDs?

A technical problem, for example, would be similar to the problem with
edu.com, which if you recall, was created back in about 1994 or so. If I
recall the problem, the dns searches from .com resolvers resolving .edu
hosts appended their search domains to the name being resolved.  So for
example, ksr.com machines trying to contact mit.edu first looked up
mit.edu.ksr.com., finding nothing, it tried mit.edu.com., and made a
request to edu.com.  Unfortunately, at the time, edu.com had a dialup
connection.

I see no such problems with creating .tel and .mobi TLDs.  It is not the 
case that URI methods can't share names with TLDs.  It would be fine to 
have a URI method of, say museum: if you could attach some sensible 
meaning to such a method.


> The "tel" URI method is for dialing using E.164 numbers, e.g.
> "tel:+18005551212", which will probably be translated to a different URI via
> ENUM.  For telephones using user/domain names, use the "sip" URI method,
> e.g. "sip:support@example.com".  There is no need for a .tel TLD, and adding
> one ignores existing, logical solutions.
> 
> Likewise, there is no reason for a .mobi TLD; either mobile clients should
> use the standard "http" method to negotiate the content/format/encoding with
> servers as needed via HTTP's existing mechanisms, or if necessary a new
> method/protocol should be defined, e.g. "wap://www.example.com/".

I don't think you understand the proposal for the TLDs.  .mobi is not for 
mobile _clients_. Its for mobile _Companies_

		--Dean


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


From exim@www1.ietf.org  Tue Apr 27 18:31:54 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07581
	for <ietf-archive@odin.ietf.org>; Tue, 27 Apr 2004 18:31:53 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIazt-000625-J8
	for ietf-archive@odin.ietf.org; Tue, 27 Apr 2004 18:24:14 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3RMODLe023186
	for ietf-archive@odin.ietf.org; Tue, 27 Apr 2004 18:24:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIap7-0002RO-IM; Tue, 27 Apr 2004 18:13:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIaii-0007RO-EM
	for ietf@optimus.ietf.org; Tue, 27 Apr 2004 18:06:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05173
	for <ietf@ietf.org>; Tue, 27 Apr 2004 18:06: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 1BIaid-0001ty-59
	for ietf@ietf.org; Tue, 27 Apr 2004 18:06:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIahk-0001lT-00
	for ietf@ietf.org; Tue, 27 Apr 2004 18:05:28 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIagx-0001bA-00
	for ietf@ietf.org; Tue, 27 Apr 2004 18:04:39 -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 i3RM41Tt028232
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 27 Apr 2004 18:04:05 -0400
Date: Tue, 27 Apr 2004 18:04:01 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Stephen Sprunk <stephen@sprunk.org>
cc: jfcm <info@utel.net>, Tim Chown <tjc@ecs.soton.ac.uk>, <ietf@ietf.org>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <07b101c42bfa$dee5b170$6401a8c0@stephen>
Message-ID: <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Mon, 26 Apr 2004, Stephen Sprunk wrote:

> 
> You're confusing URI methods, protocols, and TLDs disastrously.

I think it is you who is reading too much into the .tel and .mobi TLD.

These are not proposals to put URI method functionality into domain names,
but to qualify general business types, such as telephone companies, and
mobile phone companies.  This is no different from using .museum for
museums and .aero to represent aerospace companies.

The URI method tel: was a bad example, but otherwise completely
orthogonal to the intelligibility of using .tel and .mobi TLDs.  

Let me restate without using the tel: method:  

The URL

	somemethod://cellularone.mobi

Has a completely intelligible and meaningful interpretation. It is 
different from the following

	sip://cellularone.mobi
	http://cellularone.mobi
	telnet://cellularone.mobi
	etc.

Similarly,

	sip://verizon.tel

Is meaningful, and intelligible.

So what is the _technical_ problem with having .tel and .mobi TLDs?

A technical problem, for example, would be similar to the problem with
edu.com, which if you recall, was created back in about 1994 or so. If I
recall the problem, the dns searches from .com resolvers resolving .edu
hosts appended their search domains to the name being resolved.  So for
example, ksr.com machines trying to contact mit.edu first looked up
mit.edu.ksr.com., finding nothing, it tried mit.edu.com., and made a
request to edu.com.  Unfortunately, at the time, edu.com had a dialup
connection.

I see no such problems with creating .tel and .mobi TLDs.  It is not the 
case that URI methods can't share names with TLDs.  It would be fine to 
have a URI method of, say museum: if you could attach some sensible 
meaning to such a method.


> The "tel" URI method is for dialing using E.164 numbers, e.g.
> "tel:+18005551212", which will probably be translated to a different URI via
> ENUM.  For telephones using user/domain names, use the "sip" URI method,
> e.g. "sip:support@example.com".  There is no need for a .tel TLD, and adding
> one ignores existing, logical solutions.
> 
> Likewise, there is no reason for a .mobi TLD; either mobile clients should
> use the standard "http" method to negotiate the content/format/encoding with
> servers as needed via HTTP's existing mechanisms, or if necessary a new
> method/protocol should be defined, e.g. "wap://www.example.com/".

I don't think you understand the proposal for the TLDs.  .mobi is not for 
mobile _clients_. Its for mobile _Companies_

		--Dean


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



From ietf-admin@ietf.org  Wed Apr 28 01:45: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 BAA26725
	for <ietf-archive@ietf.org>; Wed, 28 Apr 2004 01:45: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 1BIht1-0007IA-Us
	for ietf-archive@ietf.org; Wed, 28 Apr 2004 01:45:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIhs0-00070z-00
	for ietf-archive@ietf.org; Wed, 28 Apr 2004 01:44:32 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIhr4-0006iS-00
	for ietf-archive@ietf.org; Wed, 28 Apr 2004 01:43:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIhh5-0002Pz-5f; Wed, 28 Apr 2004 01:33:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIgfd-0003bs-EM
	for ietf@optimus.ietf.org; Wed, 28 Apr 2004 00:27: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 AAA23884
	for <ietf@ietf.org>; Wed, 28 Apr 2004 00:27: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 1BIgfY-0007Dv-Js
	for ietf@ietf.org; Wed, 28 Apr 2004 00:27:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIgeb-00070W-00
	for ietf@ietf.org; Wed, 28 Apr 2004 00:26:37 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.sea)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIgdj-0006aS-00
	for ietf@ietf.org; Wed, 28 Apr 2004 00:25:43 -0400
Received: from stephen (ip161.post-vineyard.dfw.ygnition.net [66.135.181.161])
	by ns2.sea (8.12.11/8.12.5) with SMTP id i3S4ObMt021583;
	Tue, 27 Apr 2004 21:24:38 -0700
Message-ID: <015901c42cd8$b7cf22e0$6401a8c0@stephen>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Dean Anderson" <dean@av8.com>
Cc: "Internet Engineering Task Force" <ietf@ietf.org>
References: <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Tue, 27 Apr 2004 22:59:24 -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
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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 "Dean Anderson" <dean@av8.com>
> These are not proposals to put URI method functionality into domain names,
> but to qualify general business types, such as telephone companies, and
> mobile phone companies.  This is no different from using .museum for
> museums and .aero to represent aerospace companies.

.aero was a waste of time, as the number of "aerospace" companies is so
small that most users won't even realize it's a valid TLD.  Ditto for
"telephone" and "mobile" company TLDs.  These are all far too specialized
for the cost of their introduction and use to be outweighed by any benefits
to the community as a whole.

Now, a single gTLD which would contain SLDs for particular industries might
be a worthwhile plan, but adding tens of thousands of gTLDs, one for each
industry niche, is plainly not scalable.

> So what is the _technical_ problem with having .tel and .mobi TLDs?

More importantly, in light of the human problems with that scheme in
general, what is the technical benefit of having them?  It won't reduce the
overcrowding in .com and .net, which IMHO is the only valid reason for
adding new gTLDs.

Either foo://tel.verizon.com or foo://www.verizon.com/tel is far more
expressive semantically than foo://www.verizon.tel.  The proposal _loses_
information expressed in the hierarchy: how is a user to know foo.tel,
foo.net, and foo.org are all the same company, and foo.com, foo.mobi and
foo.aero are a second company with no relation to the first?

> A technical problem, for example, would be similar to the problem with
> edu.com, which if you recall, was created back in about 1994 or so.
> ...
> I see no such problems with creating .tel and .mobi TLDs.

Of course there is; you risk collisions like tel.com, mobi.com, com.tel,
mobi.tel, tel.mobi, etc.  With a small, fixed number of TLDs the problem is
manageable because most operators will naturally avoid registering such
SLDs; each new TLD makes this increasingly more difficult.

> It is not the case that URI methods can't share names with TLDs.  It would
> be fine to have a URI method of, say museum: if you could attach some
> sensible meaning to such a method.

True, there's no technical conflict, but one must consider the consequences
in light of the humans using them.  Imagine a world with a "www" or "com"
method, or a "http" TLD -- user error would increase exponentially.  Users
cannot be expected to know why com://yahoo.http has no relation to
http://yahoo.com, and we should not put them in the position of needing to
unless there is no alternative.

> I don't think you understand the proposal for the TLDs.  .mobi is not for
> mobile _clients_. Its for mobile _Companies_

Equally bad, just for different reasons...

.tel and .mobi are exceptionally bad in combination since the two would end
up with nearly the same contents, given how the markets are so closely
related.

S

Stephen Sprunk        "Stupid people surround themselves with smart
CCIE #3723           people.  Smart people surround themselves with
K5SSS         smart people who disagree with them."  --Aaron Sorkin


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


From exim@www1.ietf.org  Wed Apr 28 01:48:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26961
	for <ietf-archive@odin.ietf.org>; Wed, 28 Apr 2004 01:48:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIhr9-0004RQ-9u
	for ietf-archive@odin.ietf.org; Wed, 28 Apr 2004 01:43:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3S5hdxc017064
	for ietf-archive@odin.ietf.org; Wed, 28 Apr 2004 01:43:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIhh5-0002Pz-5f; Wed, 28 Apr 2004 01:33:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIgfd-0003bs-EM
	for ietf@optimus.ietf.org; Wed, 28 Apr 2004 00:27: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 AAA23884
	for <ietf@ietf.org>; Wed, 28 Apr 2004 00:27: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 1BIgfY-0007Dv-Js
	for ietf@ietf.org; Wed, 28 Apr 2004 00:27:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIgeb-00070W-00
	for ietf@ietf.org; Wed, 28 Apr 2004 00:26:37 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.sea)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIgdj-0006aS-00
	for ietf@ietf.org; Wed, 28 Apr 2004 00:25:43 -0400
Received: from stephen (ip161.post-vineyard.dfw.ygnition.net [66.135.181.161])
	by ns2.sea (8.12.11/8.12.5) with SMTP id i3S4ObMt021583;
	Tue, 27 Apr 2004 21:24:38 -0700
Message-ID: <015901c42cd8$b7cf22e0$6401a8c0@stephen>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Dean Anderson" <dean@av8.com>
Cc: "Internet Engineering Task Force" <ietf@ietf.org>
References: <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Tue, 27 Apr 2004 22:59:24 -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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Thus spake "Dean Anderson" <dean@av8.com>
> These are not proposals to put URI method functionality into domain names,
> but to qualify general business types, such as telephone companies, and
> mobile phone companies.  This is no different from using .museum for
> museums and .aero to represent aerospace companies.

.aero was a waste of time, as the number of "aerospace" companies is so
small that most users won't even realize it's a valid TLD.  Ditto for
"telephone" and "mobile" company TLDs.  These are all far too specialized
for the cost of their introduction and use to be outweighed by any benefits
to the community as a whole.

Now, a single gTLD which would contain SLDs for particular industries might
be a worthwhile plan, but adding tens of thousands of gTLDs, one for each
industry niche, is plainly not scalable.

> So what is the _technical_ problem with having .tel and .mobi TLDs?

More importantly, in light of the human problems with that scheme in
general, what is the technical benefit of having them?  It won't reduce the
overcrowding in .com and .net, which IMHO is the only valid reason for
adding new gTLDs.

Either foo://tel.verizon.com or foo://www.verizon.com/tel is far more
expressive semantically than foo://www.verizon.tel.  The proposal _loses_
information expressed in the hierarchy: how is a user to know foo.tel,
foo.net, and foo.org are all the same company, and foo.com, foo.mobi and
foo.aero are a second company with no relation to the first?

> A technical problem, for example, would be similar to the problem with
> edu.com, which if you recall, was created back in about 1994 or so.
> ...
> I see no such problems with creating .tel and .mobi TLDs.

Of course there is; you risk collisions like tel.com, mobi.com, com.tel,
mobi.tel, tel.mobi, etc.  With a small, fixed number of TLDs the problem is
manageable because most operators will naturally avoid registering such
SLDs; each new TLD makes this increasingly more difficult.

> It is not the case that URI methods can't share names with TLDs.  It would
> be fine to have a URI method of, say museum: if you could attach some
> sensible meaning to such a method.

True, there's no technical conflict, but one must consider the consequences
in light of the humans using them.  Imagine a world with a "www" or "com"
method, or a "http" TLD -- user error would increase exponentially.  Users
cannot be expected to know why com://yahoo.http has no relation to
http://yahoo.com, and we should not put them in the position of needing to
unless there is no alternative.

> I don't think you understand the proposal for the TLDs.  .mobi is not for
> mobile _clients_. Its for mobile _Companies_

Equally bad, just for different reasons...

.tel and .mobi are exceptionally bad in combination since the two would end
up with nearly the same contents, given how the markets are so closely
related.

S

Stephen Sprunk        "Stupid people surround themselves with smart
CCIE #3723           people.  Smart people surround themselves with
K5SSS         smart people who disagree with them."  --Aaron Sorkin


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



From exim@www1.ietf.org  Wed Apr 28 17:51:00 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25671
	for <ietf-archive@odin.ietf.org>; Wed, 28 Apr 2004 17:51:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIwnD-0001Py-F1
	for ietf-archive@odin.ietf.org; Wed, 28 Apr 2004 17:40:35 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3SLeZjb005247
	for ietf-archive@odin.ietf.org; Wed, 28 Apr 2004 17:40:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIwRH-0008IX-Dr; Wed, 28 Apr 2004 17:17:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIvgo-0005Gh-7s
	for ietf@optimus.ietf.org; Wed, 28 Apr 2004 16:29: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 QAA16505
	for <ietf@ietf.org>; Wed, 28 Apr 2004 16: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 1BIvgl-0000Bo-33
	for ietf@ietf.org; Wed, 28 Apr 2004 16:29:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIveZ-0007br-00
	for ietf@ietf.org; Wed, 28 Apr 2004 16:27:36 -0400
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1BIvdd-0007UR-00
	for ietf@ietf.org; Wed, 28 Apr 2004 16:26:37 -0400
Received: (qmail 15854 invoked by uid 1013); 28 Apr 2004 20:26:38 -0000
Date: Wed, 28 Apr 2004 22:26:38 +0200
From: Markus Stumpf <maex-lists-ietf-general@Space.Net>
To: Internet Engineering Task Force <ietf@ietf.org>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <20040428202638.GB13607@Space.Net>
References: <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net> <015901c42cd8$b7cf22e0$6401a8c0@stephen>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <015901c42cd8$b7cf22e0$6401a8c0@stephen>
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Tue, Apr 27, 2004 at 10:59:24PM -0500, Stephen Sprunk wrote:
> More importantly, in light of the human problems with that scheme in
> general, what is the technical benefit of having them?  It won't reduce the
> overcrowding in .com and .net, which IMHO is the only valid reason for
> adding new gTLDs.

This is an urban legend.
No new TLD helps for the overcrowding, as all owners of trademarks
have to and will register their name and enforce delegation of the name
by law.
And the few domains that will be allocated in purpose only TLDs do have
their representation somewhere in another TLD also. .museum is a good
example, for it is mostly a redirection service (and each time I browse
the lists it is really astonishing how much names are allocated where
there does no DNS records exist for and how much museums (even really
big ones) you cannot find there)). And what do they do with the TLD?
They try to "abuse" (IMHO) the DNS as yellow book with cross references
and redundancies to geographical and "category" indices.
However they have already noted that this won't work, so they use google
to help others find the information they managed to loose. But it
doesn't work, as most large museums don't use .museum.

So at best a new TLD is something like a license to print money for
the registrar.

	\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-admin@ietf.org  Wed Apr 28 17:55: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 RAA26177
	for <ietf-archive@ietf.org>; Wed, 28 Apr 2004 17:55: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 1BIx1T-0003Vu-4Q
	for ietf-archive@ietf.org; Wed, 28 Apr 2004 17:55:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIwz9-00035P-00
	for ietf-archive@ietf.org; Wed, 28 Apr 2004 17:52:57 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIwx4-0002dE-02
	for ietf-archive@ietf.org; Wed, 28 Apr 2004 17:50:46 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BIwnD-0001qM-06
	for ietf-archive@ietf.org; Wed, 28 Apr 2004 17:40:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIwRH-0008IX-Dr; Wed, 28 Apr 2004 17:17:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIvgo-0005Gh-7s
	for ietf@optimus.ietf.org; Wed, 28 Apr 2004 16:29: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 QAA16505
	for <ietf@ietf.org>; Wed, 28 Apr 2004 16: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 1BIvgl-0000Bo-33
	for ietf@ietf.org; Wed, 28 Apr 2004 16:29:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIveZ-0007br-00
	for ietf@ietf.org; Wed, 28 Apr 2004 16:27:36 -0400
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1BIvdd-0007UR-00
	for ietf@ietf.org; Wed, 28 Apr 2004 16:26:37 -0400
Received: (qmail 15854 invoked by uid 1013); 28 Apr 2004 20:26:38 -0000
Date: Wed, 28 Apr 2004 22:26:38 +0200
From: Markus Stumpf <maex-lists-ietf-general@Space.Net>
To: Internet Engineering Task Force <ietf@ietf.org>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <20040428202638.GB13607@Space.Net>
References: <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net> <015901c42cd8$b7cf22e0$6401a8c0@stephen>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <015901c42cd8$b7cf22e0$6401a8c0@stephen>
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
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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 Tue, Apr 27, 2004 at 10:59:24PM -0500, Stephen Sprunk wrote:
> More importantly, in light of the human problems with that scheme in
> general, what is the technical benefit of having them?  It won't reduce the
> overcrowding in .com and .net, which IMHO is the only valid reason for
> adding new gTLDs.

This is an urban legend.
No new TLD helps for the overcrowding, as all owners of trademarks
have to and will register their name and enforce delegation of the name
by law.
And the few domains that will be allocated in purpose only TLDs do have
their representation somewhere in another TLD also. .museum is a good
example, for it is mostly a redirection service (and each time I browse
the lists it is really astonishing how much names are allocated where
there does no DNS records exist for and how much museums (even really
big ones) you cannot find there)). And what do they do with the TLD?
They try to "abuse" (IMHO) the DNS as yellow book with cross references
and redundancies to geographical and "category" indices.
However they have already noted that this won't work, so they use google
to help others find the information they managed to loose. But it
doesn't work, as most large museums don't use .museum.

So at best a new TLD is something like a license to print money for
the registrar.

	\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-admin@ietf.org  Wed Apr 28 19:55: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 TAA05073
	for <ietf-archive@ietf.org>; Wed, 28 Apr 2004 19:55: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 1BIyth-0006K3-E5
	for ietf-archive@ietf.org; Wed, 28 Apr 2004 19:55:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIysk-0006AL-00
	for ietf-archive@ietf.org; Wed, 28 Apr 2004 19:54:26 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIyrl-0005zK-00
	for ietf-archive@ietf.org; Wed, 28 Apr 2004 19:53:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIyd4-0006DQ-Gz; Wed, 28 Apr 2004 19:38:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIyXl-0003sN-C5
	for ietf@optimus.ietf.org; Wed, 28 Apr 2004 19:32:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03572
	for <ietf@ietf.org>; Wed, 28 Apr 2004 19:32: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 1BIyXh-0003ty-9W
	for ietf@ietf.org; Wed, 28 Apr 2004 19:32:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIyWs-0003p3-00
	for ietf@ietf.org; Wed, 28 Apr 2004 19:31:50 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIyWP-0003ja-00
	for ietf@ietf.org; Wed, 28 Apr 2004 19:31:21 -0400
Received: from f01m-35-109.d0.club-internet.fr ([212.195.226.109] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BIyWJ-0001QN-No; Wed, 28 Apr 2004 16:31:16 -0700
Message-Id: <6.0.1.1.2.20040429011539.05b30a30@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 29 Apr 2004 01:28:09 +0200
To: "Steven M. Bellovin" <smb@research.att.com>, Dean Anderson <dean@av8.com>
From: jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs? 
Cc: Stephen Sprunk <stephen@sprunk.org>, Tim Chown <tjc@ecs.soton.ac.uk>,
        ietf@ietf.org
In-Reply-To: <20040428162010.E0FF67B46@berkshire.research.att.com>
References: <Your message of "Tue, 27 Apr 2004 18:04:01 EDT." <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net>
 <20040428162010.E0FF67B46@berkshire.research.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
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 18:20 28/04/04, Steven M. Bellovin wrote:
>In message <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net>, Dean 
>Ande
>rson writes:
> >On Mon, 26 Apr 2004, Stephen Sprunk wrote:
> >> You're confusing URI methods, protocols, and TLDs disastrously.
> >I think it is you who is reading too much into the .tel and .mobi TLD.
> >These are not proposals to put URI method functionality into domain names,
>
>Sure there are.

yes. They are. And they do not make any technical sense that way.

We should make a clear response:
- these propostions are not acceptable as TLD
- please correct them as schemes propositions.

I confuse people enough with my Franglish grammatical mistakes to know how 
confusing it would be for people iI ICANN accepted a DNS grammatical mistake.

Unfortunately people wasted $ 50.000 in fear others could obatain ".tel". 
Good $ 100.000 bonus for ICANN. Last time they only got two TAF (TLD 
Application Fee) of $ 25.000. I understand no one from ICANN wants to say 
they will respect the DNS semantic: next time they may put the TAF at $ 
100.000 ....
jfc



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


From exim@www1.ietf.org  Wed Apr 28 20:00:42 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05634
	for <ietf-archive@odin.ietf.org>; Wed, 28 Apr 2004 20:00:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIyrn-0000XU-NY
	for ietf-archive@odin.ietf.org; Wed, 28 Apr 2004 19:53:29 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3SNrRxA002007
	for ietf-archive@odin.ietf.org; Wed, 28 Apr 2004 19:53:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIyd4-0006DQ-Gz; Wed, 28 Apr 2004 19:38:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIyXl-0003sN-C5
	for ietf@optimus.ietf.org; Wed, 28 Apr 2004 19:32:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03572
	for <ietf@ietf.org>; Wed, 28 Apr 2004 19:32: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 1BIyXh-0003ty-9W
	for ietf@ietf.org; Wed, 28 Apr 2004 19:32:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIyWs-0003p3-00
	for ietf@ietf.org; Wed, 28 Apr 2004 19:31:50 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIyWP-0003ja-00
	for ietf@ietf.org; Wed, 28 Apr 2004 19:31:21 -0400
Received: from f01m-35-109.d0.club-internet.fr ([212.195.226.109] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BIyWJ-0001QN-No; Wed, 28 Apr 2004 16:31:16 -0700
Message-Id: <6.0.1.1.2.20040429011539.05b30a30@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 29 Apr 2004 01:28:09 +0200
To: "Steven M. Bellovin" <smb@research.att.com>, Dean Anderson <dean@av8.com>
From: jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs? 
Cc: Stephen Sprunk <stephen@sprunk.org>, Tim Chown <tjc@ecs.soton.ac.uk>,
        ietf@ietf.org
In-Reply-To: <20040428162010.E0FF67B46@berkshire.research.att.com>
References: <Your message of "Tue, 27 Apr 2004 18:04:01 EDT." <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net>
 <20040428162010.E0FF67B46@berkshire.research.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

At 18:20 28/04/04, Steven M. Bellovin wrote:
>In message <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net>, Dean 
>Ande
>rson writes:
> >On Mon, 26 Apr 2004, Stephen Sprunk wrote:
> >> You're confusing URI methods, protocols, and TLDs disastrously.
> >I think it is you who is reading too much into the .tel and .mobi TLD.
> >These are not proposals to put URI method functionality into domain names,
>
>Sure there are.

yes. They are. And they do not make any technical sense that way.

We should make a clear response:
- these propostions are not acceptable as TLD
- please correct them as schemes propositions.

I confuse people enough with my Franglish grammatical mistakes to know how 
confusing it would be for people iI ICANN accepted a DNS grammatical mistake.

Unfortunately people wasted $ 50.000 in fear others could obatain ".tel". 
Good $ 100.000 bonus for ICANN. Last time they only got two TAF (TLD 
Application Fee) of $ 25.000. I understand no one from ICANN wants to say 
they will respect the DNS semantic: next time they may put the TAF at $ 
100.000 ....
jfc



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



From JTRVJTDGV@orc.ru  Wed Apr 28 20:20: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 UAA06635
	for <ietf-archive@ietf.org>; Wed, 28 Apr 2004 20:20: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 1BIzIF-0001AD-1F
	for ietf-archive@ietf.org; Wed, 28 Apr 2004 20:20:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIzHL-000153-00
	for ietf-archive@ietf.org; Wed, 28 Apr 2004 20:19:52 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIzGd-0000zg-00; Wed, 28 Apr 2004 20:19:07 -0400
Received: from pcp02607049pcs.prtmry01.nj.comcast.net ([68.84.214.190])
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1BIzGf-0004Gk-ID; Wed, 28 Apr 2004 20:19:09 -0400
Received: from 29.128.224.62 by 68.84.214.190; Thu, 29 Apr 2004 04:17:08 +0300
Message-ID: <WWRDPSDPYXRCCNXMSOCP@pc-plus.de>
From: "Kristin Todd" <JTRVJTDGV@orc.ru>
Reply-To: "Kristin Todd" <JTRVJTDGV@orc.ru>
To: ietf-archive@ietf.org, ietf-secretariat@ietf.org
Subject: auction hints, auction tips, online auction home business, auction tool
Date: Wed, 28 Apr 2004 22:13:08 -0300
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--058459482115717"
X-Webmail-Time: Thu, 29 Apr 2004 00:17:08 -0100
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=2.7 required=5.0 tests=BIZ_TLD,HTML_40_50,
	HTML_FONTCOLOR_RED,HTML_FONT_BIG,HTML_MESSAGE,MIME_HTML_ONLY,
	MIME_HTML_ONLY_MULTI autolearn=no version=2.60

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859=
-1">
<title>-09 3-40f 340f 34f;lk ;l3</title>


</head>

<body>
<p><font size=3D"4">Few reasons why you should seriously consider making m=
oney with 
  <font color=3D"#FF0000" size=3D"5"><strong>ebay</strong></font></font></=
p>
<UL>
  <LI>You can get started quickly with very little investment. 
  <LI>You can "work" a small amount of hours and start earning a part-time=
 income 
    pretty much right away. </LI>
  <LI>Since the business takes so little time, you can gradually build it =
into 
    a full-time income before quitting your job, etc. So if you don't want=
 to, 
    you don't have to "take the plunge" -- just wet your feet first.<BR>
  </LI>
</UL>
<p align=3D"center"><font size=3D"4">Find out how you can start making it =
<font color=3D"#FF00FF">BIG</font> 
  Today. Visit <a href=3D"http://www.lepayscaisse.biz/ebay/index.htm">this=
 link</a></font></p>
<p align=3D"center">&nbsp;</p>
<p align=3D"center">&nbsp;</p>
<p align=3D"center"><font size=3D"2">To manage your subscription settings =
open <a href=3D"http://www.lepayscaisse.biz/takeoff/takeoff.html">this 
  page</a> </font></p>


</body>
</html>


----058459482115717--



From QLZLTV@mail.sochi.ru  Thu Apr 29 07:51: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 HAA21753
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 07:51: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 1BJA4F-0004LI-VR
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 07:51:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJA3G-00049l-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 07:50:03 -0400
Received: from pcp03796672pcs.gillst01.ar.comcast.net ([68.46.240.244])
	by ietf-mx with smtp (Exim 4.12)
	id 1BJA2C-0003nv-00; Thu, 29 Apr 2004 07:48:56 -0400
Received: from 158.88.68.184 by 68.46.240.244; Thu, 29 Apr 2004 16:48:56 +0400
Message-ID: <HFYQONQRNGWLQBLNOKMA@ba2.so-net.ne.jp>
From: "Hazel Rhodes" <QLZLTV@mail.sochi.ru>
Reply-To: "Hazel Rhodes" <QLZLTV@mail.sochi.ru>
To: ietf-archive@ietf.org
Subject: university degrees for sale!
Date: Thu, 29 Apr 2004 16:48:56 +0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--511891316626839815"
X-Webmail-Time: Thu, 29 Apr 2004 17:47:56 +0500
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=6.6 required=5.0 tests=HTML_30_40,
	HTML_FONTCOLOR_UNSAFE,HTML_FONT_BIG,HTML_MESSAGE,
	HTML_TAG_EXISTS_TBODY,LINES_OF_YELLING,MIME_HTML_ONLY,
	MIME_HTML_ONLY_MULTI,OBFUSCATING_COMMENT autolearn=no version=2.60
X-Spam-Report: 
	*  0.8 HTML_30_40 BODY: Message is 30% to 40% HTML
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 HTML_FONT_BIG BODY: HTML has a big font
	*  0.1 HTML_FONTCOLOR_UNSAFE BODY: HTML font color not in safe 6x6x6 palette
	*  0.1 HTML_TAG_EXISTS_TBODY BODY: HTML has "tbody" tag
	*  0.0 LINES_OF_YELLING BODY: A WHOLE LINE OF YELLING DETECTED
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts
	*  4.3 OBFUSCATING_COMMENT HTML comments which obfuscate text

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<HTML><HEAD><TITLE>lkjf sdlkfj sldkfj sldkfj sldkfj 34lkfj 3l4kfj l</TITLE=
>
<META http-equiv=3DContent-Language content=3Den-us>
<META content=3D"MSHTML 6.00.2737.800" name=3DGENERATOR>

<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dwindows-12=
52">
<STYLE>DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY>
<font color=3D"#fffff8">commissarynatty acrylate tarantara accredit eerily=
 neve sunbonnet froth trollop disputant immunization promptitude santayana=
 expression scala victor cocky audrey plea commotion bloom fried cannonbal=
l exponential lackey divorcee cathedral matson idle parr bestial cadaverou=
s=20lyons</font>
<font color=3D"#fffff4">shroudbivariate ankara malabar cholera luck excita=
tion fictive bloodshed spooky earwig blackjack salsify assist bilinear ada=
mson showboat befuddle chirp serviceberry virus ecliptic ieee peculiar lil=
ian balfour percentile inward po coyote=20ell</font>
<font color=3D"#fffff0">treacheroustine buttermilk stubble egan quip creed=
 igneous effect naacp cuddly leggy torture doyle surmise=20abduct</font>
<font color=3D"#fffff0">betrothchurchyard consume erlenmeyer orthophosphat=
e arcade chromic ac brushwork bookplate mylar wily confrontation italic ni=
trite quod amber concur cordage elevate glee legislate byline esprit butte=
rcup dactyl=20fullback</font>
<font color=3D"#fffff2">enoughmangel callous stagnant carry quadrille vici=
nity propylene devilish cartel argument creedal accusative armonk cloudbur=
st melon cretin capetown=20cobble</font>
<CENTER>
<TABLE borderColor=3D#049dd0 cellSpacing=3D0 cellPadding=3D7 width=3D500 b=
gColor=3D#ffffff 
border=3D1>
  <TBODY>
  <TR>
    <TD vAlign=3Dtop align=3Dleft width=3D500>
      <CENTER>
      <P><FONT size=3D+0><B>GET<!k> Y<!r>OU<!d>R <!u>UN<!y>I<!b>VE<!j>R<!m=
>S<!n>I<!q>T<!y>Y<!c> 
      D<!v>I<!c>P<!l>L<!b>O<!t>MA</B><BR><BR><!p><!p>D<!k>o<!r> <!n>yo<!p>=
u<!m> <!n>wan<!n>t<!s> <!u>a<!r> <!l>pr<!d>os<!h>p<!j>e<!x>r<!q>o<!w>u<!g>=
s<!e> 
      fut<!t>ure,<!m> in<!c>cr<!k>ea<!x>s<!z>e<!o>d<!i> <!n>e<!x>a<!u>rn<!=
l>ing<!g> p<!d>ow<!z>e<!m>r<!l><BR><!y><!x>m<!t>or<!y>e<!f> m<!z>on<!n>e<!=
u>y 
an<!w>d<!j> <!z>th<!r>e respec<!b>t<!w> <!e>of a<!x>l<!l>l?<BR><BR><!c>Ca<=
!b>ll <!i>t<!s>hi<!g>s<!b> <!c>numbe<!i>r<!q>:<!u>&nbsp; </FONT></P>
            <FONT size=3D4> 
            <P>1-212-714-8290 </P>
            </FONT>
            <P><FONT size=3D+0><!f>(24<!p> 
      h<!f>ou<!k>rs<!k>)<BR><BR>&nbsp;<OI></P>
              
</CENTER>
      <LI>T<!r>he<!d>re<!u> a<!y>r<!b>e <!j>n<!m>o<!n> 
<!q>r<!y>e<!c>qu<!v>i<!c>r<!l>e<!b>d<!t> tes<!p>t<!p>s<!k>,<!r> 
<!n>cl<!p>a<!m>s<!n>ses<!n>,<!s> <!u>b<!r>o<!l>ok<!d>s,<!h> <!j>o<!x>r<!q>=
 
<!w>i<!g>n<!e>terv<!t>iews<!m>!<BR>&nbsp; 
      <LI>Ge<!c>t <!k>a <!x>B<!z>a<!o>c<!i>h<!n>e<!x>l<!u>or<!l>s, <!g>Ma<=
!d>st<!z>e<!m>r<!l>s<!y>,<!x> <!t>MB<!y>A<!f>, <!z>an<!n>d<!u> Doc<!w>t<!j=
>o<!z>ra<!r>te (PhD)<!b> <!w>d<!e>iplo<!x>m<!l>a!<BR>&nbsp; 
      <LI>R<!c>ece<!b>ive<!i> <!s>th<!g>e<!b> <!c>benef<!i>i<!q>t<!u>s a<!=
o>n<!f>d <!s>ad<!v>m<!t>ir<!o>a<!q>tion<!f> th<!p>at<!f> c<!k>om<!k>es<!r>=
 w<!d>it<!u>h <!y>a<!b> d<!j>i<!m>p<!n>l<!q>o<!y>m<!c>a!<!v><BR>&nbsp; 
      <LI>N<!c>o<!l> <!b>o<!t>ne i<!p>s<!p> <!k>t<!r>u<!n>rn<!p>e<!m>d<!n>=
 do<!n>w<!s>n<!u>!<!r> <BR><BR>
            &nbsp; 
            <CENTER>
           <!l>
      <P>C<!d>al<!h>l<!j> <!x>T<!q>o<!w>d<!g>a<!e>y <B><!z></B></P></FONT>=

              <P><FONT size=3D4>1-212-714-8290</FONT></P>
              
              <FONT 
      size=3D+0>
              <P><BR>
<BR><B>C<!t>on<!y>f<!f>id<!z>en<!n>t<!u>iali<!w>t<!j>y<!z> a<!r>ssured!</B=
> <BR>&nbsp;</P></FONT>
<font color=3D"#fffff2">gratisdis benedictine grosset barbaric metric tate=
 contradistinguish barbarous stern crochet doubleton jennie arrowhead brea=
dth calvary cataclysm puddle fitzpatrick fledgling melanin cotillion berib=
bon bromley calculate youngstown owing declaration abduct multi incredulit=
y indicter budapest inveigle riverfront=20ask</font>
<font color=3D"#fffff1">authoritarianorr rotund eldest redneck sex offer s=
mallish herbert intuitable iconoclast endosperm somewhere spar columnar ju=
risdiction check magnificent curlicue thorstein hardtack eleazar common ba=
leful southpaw resurgent suzanne=20fragmentation</font>
      <P><FONT size=3D4><SPAN lang=3Dzh-cn>W</SPAN></FONT><FONT size=3D+0>=
<FONT 
      size=3D4><SPAN lang=3Dzh-cn>e are located in USA&nbsp; international=
 callers 
      are very 
welcome</SPAN></FONT></P></CENTER></FONT></OI></LI></TD></TR></TBODY></TAB=
LE>
  
  <p>&nbsp;</p>
</CENTER>
<font color=3D"#fffff2">affinitygeometer gunshot molehill h bowel saran oc=
tant impedance deplete assemble villein carib skillful thyratron backscatt=
er cinquefoil intimate lingual newbold rocco superstition bayport psychoph=
ysiology frederic deal dunedin dope leachate spotty kamchatka heaven birds=
eed corp loophole apartheid calvinist crony guillemot harsh=20extremum</fo=
nt>
<font color=3D"#fffff7">conveyanceconferee pickering destitute dihedral be=
nzene claremont ventilate bombproof foam peste anatole indianapolis ababa =
chuckle torso control embedded freethink ky receptive waive tuxedo chick d=
utton akron irishmen blueprint quixotic=20malign</font>
<font color=3D"#fffff1">uclaninety schoenberg complaisant lifelike trillio=
nth efferent airflow guide english tactile arcsine construe balance wallpa=
per anemone drive socket polariton crease decisionmake announce eire pee q=
uash complex vex resist nor demitted backward marmot condominium=20hankel<=
/font>
<font color=3D"#fffff0">arctangentconfidante retention sloane absentia typ=
hoon muskegon fleece nostalgic maladroit claustrophobia judiciary julia fr=
eshmen surjection pensacola neckline clytemnestra defensive burley chinch =
incapacitate german ado deride cataract bottle resentful contrive chadwick=
 blacksmith pont peripatetic prescription spur unchristian urbanite=20cats=
up</font>
</BODY></HTML>


----511891316626839815--



From ietf-admin@ietf.org  Thu Apr 29 09:12: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 JAA28629
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 09: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 1BJBKn-0001vl-Kq
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 09:12:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJBIZ-0001DJ-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 09:09:56 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJBHe-0000tz-02
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 09:08:58 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BJBEO-0007tV-My
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 09:05:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJAni-0006Bp-IJ; Thu, 29 Apr 2004 08:38:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIrpg-0008Sz-AT
	for ietf@optimus.ietf.org; Wed, 28 Apr 2004 12:22:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25732
	for <ietf@ietf.org>; Wed, 28 Apr 2004 12:22: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 1BIrpd-0004UR-49
	for ietf@ietf.org; Wed, 28 Apr 2004 12:22:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIroe-0004R0-00
	for ietf@ietf.org; Wed, 28 Apr 2004 12:21:45 -0400
Received: from mail-red.research.att.com ([192.20.225.110] helo=mail-white.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIrng-0004NS-00
	for ietf@ietf.org; Wed, 28 Apr 2004 12:20:44 -0400
Received: from mail-blue.research.att.com (H-135-207-30-102.research.att.com [135.207.30.102])
	by mail-white.research.att.com (Postfix) with ESMTP id E865D664040;
	Wed, 28 Apr 2004 12:20:11 -0400 (EDT)
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP id E1467F3A88;
	Wed, 28 Apr 2004 12:20:11 -0400 (EDT)
Received: from berkshire.research.att.com (sigaba.research.att.com [135.207.23.169])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id i3SGKBZ05802;
	Wed, 28 Apr 2004 12:20:11 -0400 (EDT)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id E0FF67B46; Wed, 28 Apr 2004 12:20:10 -0400 (EDT)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
X-Exmh-Isig-CompType: repl
X-Exmh-Isig-Folder: listbox
From: "Steven M. Bellovin" <smb@research.att.com>
To: Dean Anderson <dean@av8.com>
Cc: Stephen Sprunk <stephen@sprunk.org>, jfcm <info@utel.net>,
        Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs? 
In-Reply-To: Your message of "Tue, 27 Apr 2004 18:04:01 EDT."
             <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net> 
Mime-Version: 1.0
Content-Type: text/plain
Date: Wed, 28 Apr 2004 12:20:10 -0400
Message-Id: <20040428162010.E0FF67B46@berkshire.research.att.com>
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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

In message <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net>, Dean Ande
rson writes:
>On Mon, 26 Apr 2004, Stephen Sprunk wrote:
>
>> 
>> You're confusing URI methods, protocols, and TLDs disastrously.
>
>I think it is you who is reading too much into the .tel and .mobi TLD.
>
>These are not proposals to put URI method functionality into domain names,

Sure there are.  Here's a direct quote from the .mobi proposal:

	Businesses and consumers that utilise mobile devices will
	be able to take advantage of a wide range of Internet
	services and content under the mTLD that have been specifically
	tailored for access and use by mobile devices. The sponsored
	TLD provides a clearly recognisable mobile label to the
	services and content, indicating that they will be easy
	and convenient to use with mobile devices. By choice of
	suitable mobile-specific technologies, the service offering
	can be adapted to mobile-specific characteristics, such as
	the limitations of mobile networks and devices (throughput,
	temporary signal loss, etc), which will result in a better
	user experience for those services.

I find it hard to interpret that text in any other fashion -- they want
to describe end-to-end protocols by DNS name.

There are two proposals for .tel; here's text from one of them:

	Sub-domains of ".tel" may not be arbitrarily defined; rather
	they are defined in accordance with the ITU E.164 standard.
	A valid e164 domain name under the ".tel" TLD is defined
	as follows:

	Start with a telephone number: 1-212-332-1234.

	Remove all non-numeric characters: 12123321234.

	Reverse the order of the number: 43212332121.

	Separate by dots: 4.3.2.1.2.3.3.2.1.2.1.

	Add the sTLD:  4.3.2.1.2.3.3.2.1.2.1.tel.

That looks like an ENUM competitor to me.  (The other .tel proposal
looks like a generic TLD at first reading.)

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


From exim@www1.ietf.org  Thu Apr 29 09:15:54 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29269
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 09:15:54 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJBET-0000ts-B2
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 09:05:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3TD5ffr003454
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 09:05:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJAni-0006Bp-IJ; Thu, 29 Apr 2004 08:38:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIrpg-0008Sz-AT
	for ietf@optimus.ietf.org; Wed, 28 Apr 2004 12:22:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25732
	for <ietf@ietf.org>; Wed, 28 Apr 2004 12:22: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 1BIrpd-0004UR-49
	for ietf@ietf.org; Wed, 28 Apr 2004 12:22:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BIroe-0004R0-00
	for ietf@ietf.org; Wed, 28 Apr 2004 12:21:45 -0400
Received: from mail-red.research.att.com ([192.20.225.110] helo=mail-white.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BIrng-0004NS-00
	for ietf@ietf.org; Wed, 28 Apr 2004 12:20:44 -0400
Received: from mail-blue.research.att.com (H-135-207-30-102.research.att.com [135.207.30.102])
	by mail-white.research.att.com (Postfix) with ESMTP id E865D664040;
	Wed, 28 Apr 2004 12:20:11 -0400 (EDT)
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP id E1467F3A88;
	Wed, 28 Apr 2004 12:20:11 -0400 (EDT)
Received: from berkshire.research.att.com (sigaba.research.att.com [135.207.23.169])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id i3SGKBZ05802;
	Wed, 28 Apr 2004 12:20:11 -0400 (EDT)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id E0FF67B46; Wed, 28 Apr 2004 12:20:10 -0400 (EDT)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
X-Exmh-Isig-CompType: repl
X-Exmh-Isig-Folder: listbox
From: "Steven M. Bellovin" <smb@research.att.com>
To: Dean Anderson <dean@av8.com>
Cc: Stephen Sprunk <stephen@sprunk.org>, jfcm <info@utel.net>,
        Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs? 
In-Reply-To: Your message of "Tue, 27 Apr 2004 18:04:01 EDT."
             <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net> 
Mime-Version: 1.0
Content-Type: text/plain
Date: Wed, 28 Apr 2004 12:20:10 -0400
Message-Id: <20040428162010.E0FF67B46@berkshire.research.att.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

In message <Pine.LNX.4.44.0404271736160.27330-100000@cirrus.av8.net>, Dean Ande
rson writes:
>On Mon, 26 Apr 2004, Stephen Sprunk wrote:
>
>> 
>> You're confusing URI methods, protocols, and TLDs disastrously.
>
>I think it is you who is reading too much into the .tel and .mobi TLD.
>
>These are not proposals to put URI method functionality into domain names,

Sure there are.  Here's a direct quote from the .mobi proposal:

	Businesses and consumers that utilise mobile devices will
	be able to take advantage of a wide range of Internet
	services and content under the mTLD that have been specifically
	tailored for access and use by mobile devices. The sponsored
	TLD provides a clearly recognisable mobile label to the
	services and content, indicating that they will be easy
	and convenient to use with mobile devices. By choice of
	suitable mobile-specific technologies, the service offering
	can be adapted to mobile-specific characteristics, such as
	the limitations of mobile networks and devices (throughput,
	temporary signal loss, etc), which will result in a better
	user experience for those services.

I find it hard to interpret that text in any other fashion -- they want
to describe end-to-end protocols by DNS name.

There are two proposals for .tel; here's text from one of them:

	Sub-domains of ".tel" may not be arbitrarily defined; rather
	they are defined in accordance with the ITU E.164 standard.
	A valid e164 domain name under the ".tel" TLD is defined
	as follows:

	Start with a telephone number: 1-212-332-1234.

	Remove all non-numeric characters: 12123321234.

	Reverse the order of the number: 43212332121.

	Separate by dots: 4.3.2.1.2.3.3.2.1.2.1.

	Add the sTLD:  4.3.2.1.2.3.3.2.1.2.1.tel.

That looks like an ENUM competitor to me.  (The other .tel proposal
looks like a generic TLD at first reading.)

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



From ietf-admin@ietf.org  Thu Apr 29 09:53: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 JAA02101
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 09:53: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 1BJByc-00055P-LO
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 09:53:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJBxi-0004pP-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 09:52:27 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJBwv-0004Zo-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 09:51:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJBfB-0003wG-DM; Thu, 29 Apr 2004 09:33:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJBWj-0007Df-CJ
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 09:24: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 JAA00236
	for <ietf@ietf.org>; Thu, 29 Apr 2004 09:24: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 1BJBWY-0005SG-LV
	for ietf@ietf.org; Thu, 29 Apr 2004 09:24:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJBVm-0005DJ-00
	for ietf@ietf.org; Thu, 29 Apr 2004 09:23:34 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJBVB-0004tO-00
	for ietf@ietf.org; Thu, 29 Apr 2004 09:22:57 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i3TDLKn07410;
	Thu, 29 Apr 2004 06:21:20 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200404291321.i3TDLKn07410@boreas.isi.edu>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
To: smb@research.att.com (Steven M. Bellovin)
Date: Thu, 29 Apr 2004 06:21:20 -0700 (PDT)
Cc: dean@av8.com (Dean Anderson), stephen@sprunk.org (Stephen Sprunk),
        info@utel.net (jfcm), tjc@ecs.soton.ac.uk (Tim Chown), ietf@ietf.org
In-Reply-To: <20040428162010.E0FF67B46@berkshire.research.att.com> from "Steven M. Bellovin" at Apr 28, 2004 12:20:10 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-28-6-MailScanner: Found to be clean
X-MailScanner-From: bmanning
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

% There are two proposals for .tel; here's text from one of them:
% 
% 	Sub-domains of ".tel" may not be arbitrarily defined; rather
% 	they are defined in accordance with the ITU E.164 standard.
% 	A valid e164 domain name under the ".tel" TLD is defined
% 	as follows:
% 
% 	Start with a telephone number: 1-212-332-1234.
% 
% 	Remove all non-numeric characters: 12123321234.
% 
% 	Reverse the order of the number: 43212332121.
% 
% 	Separate by dots: 4.3.2.1.2.3.3.2.1.2.1.
% 
% 	Add the sTLD:  4.3.2.1.2.3.3.2.1.2.1.tel.
% 
% That looks like an ENUM competitor to me.  (The other .tel proposal
% looks like a generic TLD at first reading.)

	Those who do not learn from history are doomed to repeat it.

	This is -exactly- the tpc.int. model,
			  the e164.int. model,
			  the e164.arpa. model...

	in a phrase...  "lacks traction"

--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 exim@www1.ietf.org  Thu Apr 29 09:59:31 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02475
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 09:59:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJBx5-0000Nu-B0
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 09:51:47 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3TDplpa001435
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 09:51:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJBfB-0003wG-DM; Thu, 29 Apr 2004 09:33:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJBWj-0007Df-CJ
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 09:24: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 JAA00236
	for <ietf@ietf.org>; Thu, 29 Apr 2004 09:24: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 1BJBWY-0005SG-LV
	for ietf@ietf.org; Thu, 29 Apr 2004 09:24:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJBVm-0005DJ-00
	for ietf@ietf.org; Thu, 29 Apr 2004 09:23:34 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJBVB-0004tO-00
	for ietf@ietf.org; Thu, 29 Apr 2004 09:22:57 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i3TDLKn07410;
	Thu, 29 Apr 2004 06:21:20 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200404291321.i3TDLKn07410@boreas.isi.edu>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
To: smb@research.att.com (Steven M. Bellovin)
Date: Thu, 29 Apr 2004 06:21:20 -0700 (PDT)
Cc: dean@av8.com (Dean Anderson), stephen@sprunk.org (Stephen Sprunk),
        info@utel.net (jfcm), tjc@ecs.soton.ac.uk (Tim Chown), ietf@ietf.org
In-Reply-To: <20040428162010.E0FF67B46@berkshire.research.att.com> from "Steven M. Bellovin" at Apr 28, 2004 12:20:10 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-28-6-MailScanner: Found to be clean
X-MailScanner-From: bmanning
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

% There are two proposals for .tel; here's text from one of them:
% 
% 	Sub-domains of ".tel" may not be arbitrarily defined; rather
% 	they are defined in accordance with the ITU E.164 standard.
% 	A valid e164 domain name under the ".tel" TLD is defined
% 	as follows:
% 
% 	Start with a telephone number: 1-212-332-1234.
% 
% 	Remove all non-numeric characters: 12123321234.
% 
% 	Reverse the order of the number: 43212332121.
% 
% 	Separate by dots: 4.3.2.1.2.3.3.2.1.2.1.
% 
% 	Add the sTLD:  4.3.2.1.2.3.3.2.1.2.1.tel.
% 
% That looks like an ENUM competitor to me.  (The other .tel proposal
% looks like a generic TLD at first reading.)

	Those who do not learn from history are doomed to repeat it.

	This is -exactly- the tpc.int. model,
			  the e164.int. model,
			  the e164.arpa. model...

	in a phrase...  "lacks traction"

--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-admin@ietf.org  Thu Apr 29 10:32: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 KAA05681
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 10:32: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 1BJCaR-0007Ef-Es
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 10:32:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJCZW-0006yf-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 10:31:30 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJCZ2-0006io-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 10:31:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJCPO-00067X-NE; Thu, 29 Apr 2004 10:21:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJC5V-0002uv-5o
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 10:00: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 KAA02620
	for <ietf@ietf.org>; Thu, 29 Apr 2004 10:00: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 1BJC5J-0006rI-RG
	for ietf@ietf.org; Thu, 29 Apr 2004 10:00:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJC4V-0006cJ-00
	for ietf@ietf.org; Thu, 29 Apr 2004 09:59:28 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJC3b-00067P-00
	for ietf@ietf.org; Thu, 29 Apr 2004 09:58:31 -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 i3TDw04m007262
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 29 Apr 2004 09:58:03 -0400
Date: Thu, 29 Apr 2004 09:58:00 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Markus Stumpf <maex-lists-ietf-general@Space.Net>
cc: Internet Engineering Task Force <ietf@ietf.org>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <20040428202638.GB13607@Space.Net>
Message-ID: <Pine.LNX.4.44.0404290947010.6993-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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, 28 Apr 2004, Markus Stumpf wrote:

> No new TLD helps for the overcrowding, as all owners of trademarks
> have to and will register their name and enforce delegation of the name
> by law.

This isn't true. No one is required by law to register their trademark as
a domain name. 

> So at best a new TLD is something like a license to print money for
> the registrar.

Ok. What's wrong with that?  If sponsoring organizations are willing to 
pay, they should be sold what they want.  Sounds like you are against 
commercialization.

So far, I still haven't heard a _technical_ reason against these TLD's.

  ** What is one thing that will break if these are granted?

  ** Better, what is the complete list of things that will break?

		--Dean


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


From ietf-admin@ietf.org  Thu Apr 29 10:40: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 KAA06180
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 10: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 1BJCiT-0001dJ-DY
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 10:40:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJChQ-0001L6-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 10:39:40 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJCgm-00013U-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 10:39:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJCPh-0006Hl-S0; Thu, 29 Apr 2004 10:21:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJCKs-0003XL-NN
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 10:16: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 KAA04310
	for <ietf@ietf.org>; Thu, 29 Apr 2004 10:16: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 1BJCKh-00034r-HI
	for ietf@ietf.org; Thu, 29 Apr 2004 10:16:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJCJi-0002on-00
	for ietf@ietf.org; Thu, 29 Apr 2004 10:15:11 -0400
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJCIk-0002ZF-00
	for ietf@ietf.org; Thu, 29 Apr 2004 10:14:11 -0400
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i3TEECG24548;
	Thu, 29 Apr 2004 17:14:12 +0300 (EET DST)
X-Scanned: Thu, 29 Apr 2004 17:12:22 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i3TECMcC005813;
	Thu, 29 Apr 2004 17:12:22 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 00C82ork; Thu, 29 Apr 2004 17:12:20 EEST
Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i3TECEH22738;
	Thu, 29 Apr 2004 17:12:14 +0300 (EET DST)
Received: from nokia.com ([10.162.252.200]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Thu, 29 Apr 2004 17:12:10 +0300
Message-ID: <40910D37.1030205@nokia.com>
Date: Thu, 29 Apr 2004 17:12:07 +0300
From: Aki Niemi <aki.niemi@nokia.com>
Organization: Nokia-M/Espoo
User-Agent: Mozilla Thunderbird 0.6+ (X11/20040421)
X-Accept-Language: en
MIME-Version: 1.0
To: "ext Steven M. Bellovin" <smb@research.att.com>
CC: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
References: <20040428162010.E0FF67B46@berkshire.research.att.com>
In-Reply-To: <20040428162010.E0FF67B46@berkshire.research.att.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Apr 2004 14:12:10.0684 (UTC) FILETIME=[F65D77C0:01C42DF3]
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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


ext Steven M. Bellovin wrote:

> Sure there are.  Here's a direct quote from the .mobi proposal:
> 
> 	Businesses and consumers that utilise mobile devices will
> 	be able to take advantage of a wide range of Internet
> 	services and content under the mTLD that have been specifically
> 	tailored for access and use by mobile devices. The sponsored
> 	TLD provides a clearly recognisable mobile label to the
> 	services and content, indicating that they will be easy
> 	and convenient to use with mobile devices. By choice of
> 	suitable mobile-specific technologies, the service offering
> 	can be adapted to mobile-specific characteristics, such as
> 	the limitations of mobile networks and devices (throughput,
> 	temporary signal loss, etc), which will result in a better
> 	user experience for those services.
> 
> I find it hard to interpret that text in any other fashion -- they want
> to describe end-to-end protocols by DNS name.

I don't quite see what the difference here is to .edu for example. Isn't
this indeed very similar to how the .edu provides a "clearly
recognisable" label for educational services and content?

Cheers,
Aki


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


From exim@www1.ietf.org  Thu Apr 29 10:46:17 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06536
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 10:46:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJCZC-000093-QS
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 10:31:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3TEVACv000500
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 10:31:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJCPO-00067X-NE; Thu, 29 Apr 2004 10:21:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJC5V-0002uv-5o
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 10:00: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 KAA02620
	for <ietf@ietf.org>; Thu, 29 Apr 2004 10:00: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 1BJC5J-0006rI-RG
	for ietf@ietf.org; Thu, 29 Apr 2004 10:00:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJC4V-0006cJ-00
	for ietf@ietf.org; Thu, 29 Apr 2004 09:59:28 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJC3b-00067P-00
	for ietf@ietf.org; Thu, 29 Apr 2004 09:58:31 -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 i3TDw04m007262
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 29 Apr 2004 09:58:03 -0400
Date: Thu, 29 Apr 2004 09:58:00 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Markus Stumpf <maex-lists-ietf-general@Space.Net>
cc: Internet Engineering Task Force <ietf@ietf.org>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <20040428202638.GB13607@Space.Net>
Message-ID: <Pine.LNX.4.44.0404290947010.6993-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Wed, 28 Apr 2004, Markus Stumpf wrote:

> No new TLD helps for the overcrowding, as all owners of trademarks
> have to and will register their name and enforce delegation of the name
> by law.

This isn't true. No one is required by law to register their trademark as
a domain name. 

> So at best a new TLD is something like a license to print money for
> the registrar.

Ok. What's wrong with that?  If sponsoring organizations are willing to 
pay, they should be sold what they want.  Sounds like you are against 
commercialization.

So far, I still haven't heard a _technical_ reason against these TLD's.

  ** What is one thing that will break if these are granted?

  ** Better, what is the complete list of things that will break?

		--Dean


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



From exim@www1.ietf.org  Thu Apr 29 10:46:48 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06588
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 10:46:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJCgw-0002b8-KX
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 10:39:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3TEdAdK009987
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 10:39:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJCPh-0006Hl-S0; Thu, 29 Apr 2004 10:21:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJCKs-0003XL-NN
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 10:16: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 KAA04310
	for <ietf@ietf.org>; Thu, 29 Apr 2004 10:16: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 1BJCKh-00034r-HI
	for ietf@ietf.org; Thu, 29 Apr 2004 10:16:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJCJi-0002on-00
	for ietf@ietf.org; Thu, 29 Apr 2004 10:15:11 -0400
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJCIk-0002ZF-00
	for ietf@ietf.org; Thu, 29 Apr 2004 10:14:11 -0400
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i3TEECG24548;
	Thu, 29 Apr 2004 17:14:12 +0300 (EET DST)
X-Scanned: Thu, 29 Apr 2004 17:12:22 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i3TECMcC005813;
	Thu, 29 Apr 2004 17:12:22 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 00C82ork; Thu, 29 Apr 2004 17:12:20 EEST
Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i3TECEH22738;
	Thu, 29 Apr 2004 17:12:14 +0300 (EET DST)
Received: from nokia.com ([10.162.252.200]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Thu, 29 Apr 2004 17:12:10 +0300
Message-ID: <40910D37.1030205@nokia.com>
Date: Thu, 29 Apr 2004 17:12:07 +0300
From: Aki Niemi <aki.niemi@nokia.com>
Organization: Nokia-M/Espoo
User-Agent: Mozilla Thunderbird 0.6+ (X11/20040421)
X-Accept-Language: en
MIME-Version: 1.0
To: "ext Steven M. Bellovin" <smb@research.att.com>
CC: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
References: <20040428162010.E0FF67B46@berkshire.research.att.com>
In-Reply-To: <20040428162010.E0FF67B46@berkshire.research.att.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Apr 2004 14:12:10.0684 (UTC) FILETIME=[F65D77C0:01C42DF3]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit


ext Steven M. Bellovin wrote:

> Sure there are.  Here's a direct quote from the .mobi proposal:
> 
> 	Businesses and consumers that utilise mobile devices will
> 	be able to take advantage of a wide range of Internet
> 	services and content under the mTLD that have been specifically
> 	tailored for access and use by mobile devices. The sponsored
> 	TLD provides a clearly recognisable mobile label to the
> 	services and content, indicating that they will be easy
> 	and convenient to use with mobile devices. By choice of
> 	suitable mobile-specific technologies, the service offering
> 	can be adapted to mobile-specific characteristics, such as
> 	the limitations of mobile networks and devices (throughput,
> 	temporary signal loss, etc), which will result in a better
> 	user experience for those services.
> 
> I find it hard to interpret that text in any other fashion -- they want
> to describe end-to-end protocols by DNS name.

I don't quite see what the difference here is to .edu for example. Isn't
this indeed very similar to how the .edu provides a "clearly
recognisable" label for educational services and content?

Cheers,
Aki


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



From ietf-admin@ietf.org  Thu Apr 29 13:44: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 NAA15940
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 13:44: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 1BJFaQ-0005Be-A5
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 13:44:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJFZO-0004rq-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 13:43:35 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJFYY-0004ZN-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 13:42:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJFFb-0006yf-Rl; Thu, 29 Apr 2004 13:23:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJDf7-0002gh-SM
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 11: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 LAA09860
	for <ietf@ietf.org>; Thu, 29 Apr 2004 11:41: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 1BJDf2-0002gX-QU
	for ietf@ietf.org; Thu, 29 Apr 2004 11:41:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJDeB-0002Rb-00
	for ietf@ietf.org; Thu, 29 Apr 2004 11:40:23 -0400
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJDdf-0002CM-00
	for ietf@ietf.org; Thu, 29 Apr 2004 11:39:51 -0400
Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.12.11/8.12.11) with ESMTP id i3TFdrLg026443
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Thu, 29 Apr 2004 17:39:54 +0200
Resent-To: ietf@ietf.org
Resent-From: Simon Josefsson <jas@extundo.com>
Resent-Date: Thu, 29 Apr 2004 17:39:49 +0200
Resent-Message-ID: <ilufzamyere.fsf@latte.josefsson.org>
To: iesg@ietf.org, ietf@ietf.org
Reply-To: ietf@ietf.org
References: <E1BGlPX-0005di-2R@optimus.ietf.org>
From: Simon Josefsson <jas@extundo.com>
X-Hashcash: 0:040422:iesg@ietf.org:bc6f9bc54978c955
X-Hashcash: 0:040422:ietf@ietf.org:31862dd6847c5e24
Date: Fri, 23 Apr 2004 00:36:01 +0200
In-Reply-To: <E1BGlPX-0005di-2R@optimus.ietf.org> (The IESG's message of
 "Thu, 22 Apr 2004 17:07:07 -0400")
Message-ID: <ilufzavvdwu.fsf@latte.josefsson.org>
User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Resent-Date: Thu, 29 Apr 2004 11:39:51 -0400
Subject: [Ietf] Last call comment on 'AES Encryption for Kerberos 5'
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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 document [1] specify a mode of encryption that has not, to my
knowledge, been used anywhere else: CBC-CTS with IV-carry.  The
document does not reference any standard work that define it, so it
appears the document authors are not aware of prior use of it either.
There is no analysis of the security of the mode in the document.  The
CFRG has not commented on the mode.  The security consideration does
not mention that the document define or use a non-standard mode.

Considering all this, I believe it would be only prudent to reflect
those facts in the security consideration, to help people form an
opinion about it.

Here is a proposed paragraph for inclusion:

    The encryption mode used in this document, CBC with Cipher Text
    Stealing with IV carry between messages, has to our knowledge not
    been studied extensively, or even at all, in the available
    literature.

Thanks,
Simon

[1] http://www.ietf.org/internet-drafts/draft-raeburn-krb-rijndael-krb-06.txt

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


From ietf-admin@ietf.org  Thu Apr 29 13:47: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 NAA16237
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 13:47: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 1BJFdE-0006DX-Um
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 13:47:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJFcG-0005rk-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 13:46:33 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJFbH-0005W9-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 13:45:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJFFk-00072c-Qf; Thu, 29 Apr 2004 13:23:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJEzW-0003Mg-52
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 13:06: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 NAA14088
	for <ietf@ietf.org>; Thu, 29 Apr 2004 13:06: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 1BJEzN-0002ZM-0T
	for ietf@ietf.org; Thu, 29 Apr 2004 13:06:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJEyL-0002Iv-00
	for ietf@ietf.org; Thu, 29 Apr 2004 13:05:18 -0400
Received: from [131.107.8.3] (helo=exchange.microsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJExJ-0001nc-00
	for ietf@ietf.org; Thu, 29 Apr 2004 13:04:13 -0400
Received: from DF-VRS-01.redmond.corp.microsoft.com ([157.54.4.14]) by exchange.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Thu, 29 Apr 2004 10:03:46 -0700
Received: from 10.197.0.83 by DF-VRS-01.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 29 Apr 2004 10:03:45 -0700
Received: from df-dino-msg.exchange.corp.microsoft.com ([157.54.7.189]) by DF-BEG.mercury.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 29 Apr 2004 10:03:46 -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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Thu, 29 Apr 2004 10:03:46 -0700
Message-ID: <5F2BF8523EFDC94BAC3D51E6F1B9CE1F0A23F3@df-dino-msg.exchange.corp.microsoft.com>
Thread-Topic: [Ietf] New .mobi, .xxx, ... TLDs?
thread-index: AcQt8Q2K4KP6+IdWQvS7MfJnjuvxYwAF20A0
From: "Peter Ford" <peterf@exchange.microsoft.com>
To: "Bill Manning" <bmanning@ISI.EDU>,
        "Steven M. Bellovin" <smb@research.att.com>
Cc: "Dean Anderson" <dean@av8.com>, "Stephen Sprunk" <stephen@sprunk.org>,
        "jfcm" <info@utel.net>, "Tim Chown" <tjc@ecs.soton.ac.uk>,
        <ietf@ietf.org>
X-OriginalArrivalTime: 29 Apr 2004 17:03:46.0503 (UTC) FILETIME=[EF26C570:01C42E0B]
Content-Transfer-Encoding: quoted-printable
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

=20
I don't think there was any lack of capability for traction for the =
earlier proposals, there just wasn't a surface to grip against.   The =
news (good or bad depending on your biases) is that the telcos have some =
larger roles in the Internet now a days.=20
=20
When it was decided to open up TLDs, one should have expected that large =
multi-national bodies would want to be represented at that level, and =
for a variety of purposes.   I would not be surprised if  .tel and .mobi =
may only be the beginning.  Some could certainly argue that there should =
be namespace injection points into the DNS for .itu and .gsm, ...
=20
Much like established names get inserted into multiple TLDs (e.g. =
company_name.com, company_name.fr, company_name.net, ...), I will be =
surprised if we don't end up with multiple injections of the fundamental =
telco naming space (e.164) into the DNS.
=20
for your consideration, peterf

________________________________

From: ietf-admin@ietf.org on behalf of Bill Manning
Sent: Thu 4/29/2004 6:21 AM
To: Steven M. Bellovin
Cc: Dean Anderson; Stephen Sprunk; jfcm; Tim Chown; ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?



% There are two proposals for .tel; here's text from one of them:
%
%       Sub-domains of ".tel" may not be arbitrarily defined; rather
%       they are defined in accordance with the ITU E.164 standard.
%       A valid e164 domain name under the ".tel" TLD is defined
%       as follows:
%
%       Start with a telephone number: 1-212-332-1234.
%
%       Remove all non-numeric characters: 12123321234.
%
%       Reverse the order of the number: 43212332121.
%
%       Separate by dots: 4.3.2.1.2.3.3.2.1.2.1.
%
%       Add the sTLD:  4.3.2.1.2.3.3.2.1.2.1.tel.
%
% That looks like an ENUM competitor to me.  (The other .tel proposal
% looks like a generic TLD at first reading.)

        Those who do not learn from history are doomed to repeat it.

        This is -exactly- the tpc.int. model,
                          the e164.int. model,
                          the e164.arpa. model...

        in a phrase...  "lacks traction"

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



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


From exim@www1.ietf.org  Thu Apr 29 13:49:03 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16405
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 13:49:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJFYd-00039f-FO
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 13:42:48 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3THgl7b012022
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 13:42:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJFFb-0006yf-Rl; Thu, 29 Apr 2004 13:23:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJDf7-0002gh-SM
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 11: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 LAA09860
	for <ietf@ietf.org>; Thu, 29 Apr 2004 11:41: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 1BJDf2-0002gX-QU
	for ietf@ietf.org; Thu, 29 Apr 2004 11:41:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJDeB-0002Rb-00
	for ietf@ietf.org; Thu, 29 Apr 2004 11:40:23 -0400
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJDdf-0002CM-00
	for ietf@ietf.org; Thu, 29 Apr 2004 11:39:51 -0400
Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.12.11/8.12.11) with ESMTP id i3TFdrLg026443
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Thu, 29 Apr 2004 17:39:54 +0200
Resent-To: ietf@ietf.org
Resent-From: Simon Josefsson <jas@extundo.com>
Resent-Date: Thu, 29 Apr 2004 17:39:49 +0200
Resent-Message-ID: <ilufzamyere.fsf@latte.josefsson.org>
To: iesg@ietf.org, ietf@ietf.org
Reply-To: ietf@ietf.org
References: <E1BGlPX-0005di-2R@optimus.ietf.org>
From: Simon Josefsson <jas@extundo.com>
X-Hashcash: 0:040422:iesg@ietf.org:bc6f9bc54978c955
X-Hashcash: 0:040422:ietf@ietf.org:31862dd6847c5e24
Date: Fri, 23 Apr 2004 00:36:01 +0200
In-Reply-To: <E1BGlPX-0005di-2R@optimus.ietf.org> (The IESG's message of
 "Thu, 22 Apr 2004 17:07:07 -0400")
Message-ID: <ilufzavvdwu.fsf@latte.josefsson.org>
User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Resent-Date: Thu, 29 Apr 2004 11:39:51 -0400
X-Spam-Checker-Version: SpamAssassin 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
Subject: [Ietf] Last call comment on 'AES Encryption for Kerberos 5'
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

The document [1] specify a mode of encryption that has not, to my
knowledge, been used anywhere else: CBC-CTS with IV-carry.  The
document does not reference any standard work that define it, so it
appears the document authors are not aware of prior use of it either.
There is no analysis of the security of the mode in the document.  The
CFRG has not commented on the mode.  The security consideration does
not mention that the document define or use a non-standard mode.

Considering all this, I believe it would be only prudent to reflect
those facts in the security consideration, to help people form an
opinion about it.

Here is a proposed paragraph for inclusion:

    The encryption mode used in this document, CBC with Cipher Text
    Stealing with IV carry between messages, has to our knowledge not
    been studied extensively, or even at all, in the available
    literature.

Thanks,
Simon

[1] http://www.ietf.org/internet-drafts/draft-raeburn-krb-rijndael-krb-06.txt

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



From exim@www1.ietf.org  Thu Apr 29 13:49:43 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16459
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 13:49:43 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJFbM-0004pE-00
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 13:45:50 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3THjZwv018541
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 13:45:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJFFk-00072c-Qf; Thu, 29 Apr 2004 13:23:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJEzW-0003Mg-52
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 13:06: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 NAA14088
	for <ietf@ietf.org>; Thu, 29 Apr 2004 13:06: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 1BJEzN-0002ZM-0T
	for ietf@ietf.org; Thu, 29 Apr 2004 13:06:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJEyL-0002Iv-00
	for ietf@ietf.org; Thu, 29 Apr 2004 13:05:18 -0400
Received: from [131.107.8.3] (helo=exchange.microsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJExJ-0001nc-00
	for ietf@ietf.org; Thu, 29 Apr 2004 13:04:13 -0400
Received: from DF-VRS-01.redmond.corp.microsoft.com ([157.54.4.14]) by exchange.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Thu, 29 Apr 2004 10:03:46 -0700
Received: from 10.197.0.83 by DF-VRS-01.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 29 Apr 2004 10:03:45 -0700
Received: from df-dino-msg.exchange.corp.microsoft.com ([157.54.7.189]) by DF-BEG.mercury.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 29 Apr 2004 10:03:46 -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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Thu, 29 Apr 2004 10:03:46 -0700
Message-ID: <5F2BF8523EFDC94BAC3D51E6F1B9CE1F0A23F3@df-dino-msg.exchange.corp.microsoft.com>
Thread-Topic: [Ietf] New .mobi, .xxx, ... TLDs?
thread-index: AcQt8Q2K4KP6+IdWQvS7MfJnjuvxYwAF20A0
From: "Peter Ford" <peterf@exchange.microsoft.com>
To: "Bill Manning" <bmanning@ISI.EDU>,
        "Steven M. Bellovin" <smb@research.att.com>
Cc: "Dean Anderson" <dean@av8.com>, "Stephen Sprunk" <stephen@sprunk.org>,
        "jfcm" <info@utel.net>, "Tim Chown" <tjc@ecs.soton.ac.uk>,
        <ietf@ietf.org>
X-OriginalArrivalTime: 29 Apr 2004 17:03:46.0503 (UTC) FILETIME=[EF26C570:01C42E0B]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: quoted-printable

=20
I don't think there was any lack of capability for traction for the =
earlier proposals, there just wasn't a surface to grip against.   The =
news (good or bad depending on your biases) is that the telcos have some =
larger roles in the Internet now a days.=20
=20
When it was decided to open up TLDs, one should have expected that large =
multi-national bodies would want to be represented at that level, and =
for a variety of purposes.   I would not be surprised if  .tel and .mobi =
may only be the beginning.  Some could certainly argue that there should =
be namespace injection points into the DNS for .itu and .gsm, ...
=20
Much like established names get inserted into multiple TLDs (e.g. =
company_name.com, company_name.fr, company_name.net, ...), I will be =
surprised if we don't end up with multiple injections of the fundamental =
telco naming space (e.164) into the DNS.
=20
for your consideration, peterf

________________________________

From: ietf-admin@ietf.org on behalf of Bill Manning
Sent: Thu 4/29/2004 6:21 AM
To: Steven M. Bellovin
Cc: Dean Anderson; Stephen Sprunk; jfcm; Tim Chown; ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?



% There are two proposals for .tel; here's text from one of them:
%
%       Sub-domains of ".tel" may not be arbitrarily defined; rather
%       they are defined in accordance with the ITU E.164 standard.
%       A valid e164 domain name under the ".tel" TLD is defined
%       as follows:
%
%       Start with a telephone number: 1-212-332-1234.
%
%       Remove all non-numeric characters: 12123321234.
%
%       Reverse the order of the number: 43212332121.
%
%       Separate by dots: 4.3.2.1.2.3.3.2.1.2.1.
%
%       Add the sTLD:  4.3.2.1.2.3.3.2.1.2.1.tel.
%
% That looks like an ENUM competitor to me.  (The other .tel proposal
% looks like a generic TLD at first reading.)

        Those who do not learn from history are doomed to repeat it.

        This is -exactly- the tpc.int. model,
                          the e164.int. model,
                          the e164.arpa. model...

        in a phrase...  "lacks traction"

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



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



From ietf-admin@ietf.org  Thu Apr 29 15:48: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 PAA24315
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 15:48: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 1BJHWN-00065w-0L
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 15:48:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJHVU-00061a-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 15:47:41 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJHUd-0005wd-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 15:46:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJHDQ-0006xA-Bd; Thu, 29 Apr 2004 15:29:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJH5K-0003lk-08
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 15:20: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 PAA21928
	for <ietf@ietf.org>; Thu, 29 Apr 2004 15:20: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 1BJH5C-0003ro-JI
	for ietf@ietf.org; Thu, 29 Apr 2004 15:20:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJH47-0003nf-00
	for ietf@ietf.org; Thu, 29 Apr 2004 15:19:23 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJH3F-0003jW-00
	for ietf@ietf.org; Thu, 29 Apr 2004 15:18:29 -0400
Received: from eaglet (127.0.0.1:3364)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S52AEF> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 29 Apr 2004 12:14:56 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dean Anderson'" <dean@av8.com>,
        "'Markus Stumpf'" <maex-lists-ietf-general@Space.Net>
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
Subject: RE: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Thu, 29 Apr 2004 12:18:27 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQt9h3lJTmXWrlSQnOdyaYDPU52ZgAJpHSA
In-Reply-To: <Pine.LNX.4.44.0404290947010.6993-100000@cirrus.av8.net>
Message-Id: <E1BJH3F-0003jW-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Dean Anderson wrote:
> On Wed, 28 Apr 2004, Markus Stumpf wrote:
> 
> > No new TLD helps for the overcrowding, as all owners of trademarks
> > have to and will register their name and enforce delegation of the name
> > by law.
> 
> This isn't true. No one is required by law to register their trademark as
> a domain name.

IANAL, but in my discussions with lawyers focused on trademark law, in
effect they are required. The perception that they are not defending their
rights effectively means they abandon them. 

> 
> > So at best a new TLD is something like a license to print money for
> > the registrar.
> 
> Ok. What's wrong with that?  If sponsoring organizations are willing to
> pay, they should be sold what they want.  Sounds like you are against
> commercialization.
> 
> So far, I still haven't heard a _technical_ reason against these TLD's.

The technical argument here is flattening of the name space with the
associated concentration higher up the tree. There is nothing specific about
these strings, but why do they have any more rights than any other string?
Why shouldn't trademark owners be able to register the name
'yourtrademarkhere.', or anyone register 'yourpersonalfavoritestring.'? Do
you really think the root is the right place for all names? If not, what
technical characteristic differentiates strings that should vs. not? 

/flame-suit-on/ Rather than granting new TLDs, there should be an effort to
deprecate the existing non-cc TLDs and move everyone out within 3 years. The
historical artifact of a failed experiment is no reason to continue down
that path. 

Tony

> 
>   ** What is one thing that will break if these are granted?
> 
>   ** Better, what is the complete list of things that will break?
> 
> 		--Dean
> 
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Thu Apr 29 15:55:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24688
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 15:55:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJHUj-0003jD-QP
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 15:47:00 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3TJkrgi014322
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 15:46:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJHDQ-0006xA-Bd; Thu, 29 Apr 2004 15:29:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJH5K-0003lk-08
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 15:20: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 PAA21928
	for <ietf@ietf.org>; Thu, 29 Apr 2004 15:20: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 1BJH5C-0003ro-JI
	for ietf@ietf.org; Thu, 29 Apr 2004 15:20:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJH47-0003nf-00
	for ietf@ietf.org; Thu, 29 Apr 2004 15:19:23 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJH3F-0003jW-00
	for ietf@ietf.org; Thu, 29 Apr 2004 15:18:29 -0400
Received: from eaglet (127.0.0.1:3364)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S52AEF> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 29 Apr 2004 12:14:56 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dean Anderson'" <dean@av8.com>,
        "'Markus Stumpf'" <maex-lists-ietf-general@Space.Net>
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
Subject: RE: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Thu, 29 Apr 2004 12:18:27 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQt9h3lJTmXWrlSQnOdyaYDPU52ZgAJpHSA
In-Reply-To: <Pine.LNX.4.44.0404290947010.6993-100000@cirrus.av8.net>
Message-Id: <E1BJH3F-0003jW-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Dean Anderson wrote:
> On Wed, 28 Apr 2004, Markus Stumpf wrote:
> 
> > No new TLD helps for the overcrowding, as all owners of trademarks
> > have to and will register their name and enforce delegation of the name
> > by law.
> 
> This isn't true. No one is required by law to register their trademark as
> a domain name.

IANAL, but in my discussions with lawyers focused on trademark law, in
effect they are required. The perception that they are not defending their
rights effectively means they abandon them. 

> 
> > So at best a new TLD is something like a license to print money for
> > the registrar.
> 
> Ok. What's wrong with that?  If sponsoring organizations are willing to
> pay, they should be sold what they want.  Sounds like you are against
> commercialization.
> 
> So far, I still haven't heard a _technical_ reason against these TLD's.

The technical argument here is flattening of the name space with the
associated concentration higher up the tree. There is nothing specific about
these strings, but why do they have any more rights than any other string?
Why shouldn't trademark owners be able to register the name
'yourtrademarkhere.', or anyone register 'yourpersonalfavoritestring.'? Do
you really think the root is the right place for all names? If not, what
technical characteristic differentiates strings that should vs. not? 

/flame-suit-on/ Rather than granting new TLDs, there should be an effort to
deprecate the existing non-cc TLDs and move everyone out within 3 years. The
historical artifact of a failed experiment is no reason to continue down
that path. 

Tony

> 
>   ** What is one thing that will break if these are granted?
> 
>   ** Better, what is the complete list of things that will break?
> 
> 		--Dean
> 
> 
> _______________________________________________
> 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-admin@ietf.org  Thu Apr 29 16:05: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 QAA25060
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 16:05: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 1BJHmf-0006kW-Gd
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 16:05:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJHll-0006iJ-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 16:04:29 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJHl8-0006g4-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 16:03:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJHaf-000577-VE; Thu, 29 Apr 2004 15:53:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJHLZ-0008RL-Nc
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 15:37:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23352
	for <ietf@ietf.org>; Thu, 29 Apr 2004 15:37: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 1BJHLT-0005Dh-4W
	for ietf@ietf.org; Thu, 29 Apr 2004 15:37:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJHKV-00058r-00
	for ietf@ietf.org; Thu, 29 Apr 2004 15:36:20 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJHJe-000568-00
	for ietf@ietf.org; Thu, 29 Apr 2004 15:35:26 -0400
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id i3TJZT7s021423
	for <ietf@ietf.org>; Thu, 29 Apr 2004 20:35:29 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id UAA04897
	for <ietf@ietf.org>; Thu, 29 Apr 2004 20:35:27 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i3TJZRf09650
	for ietf@ietf.org; Thu, 29 Apr 2004 20:35:27 +0100
Date: Thu, 29 Apr 2004 20:35:27 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <20040429193527.GA9407@login.ecs.soton.ac.uk>
References: <20040428162010.E0FF67B46@berkshire.research.att.com> <200404291321.i3TDLKn07410@boreas.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200404291321.i3TDLKn07410@boreas.isi.edu>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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, Apr 29, 2004 at 06:21:20AM -0700, Bill Manning wrote:
> 	Those who do not learn from history are doomed to repeat it.
> 
> 	This is -exactly- the tpc.int. model,
> 			  the e164.int. model,
> 			  the e164.arpa. model...
> 
> 	in a phrase...  "lacks traction"

So, place your bets on which slippery slopes ICANN takes us down...

I'm not convinced of a good argument for any of the proposed new TLDs to
be granted.   But I'm sure some/many will.   More money for ICANN...

This is the sort of thing ISOC should speak out on.

Tim

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


From exim@www1.ietf.org  Thu Apr 29 16:51:29 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29741
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 16:51:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJHlE-0008DK-I3
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 16:03:56 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3TK3uwq031542
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 16:03:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJHaf-000577-VE; Thu, 29 Apr 2004 15:53:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJHLZ-0008RL-Nc
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 15:37:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23352
	for <ietf@ietf.org>; Thu, 29 Apr 2004 15:37: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 1BJHLT-0005Dh-4W
	for ietf@ietf.org; Thu, 29 Apr 2004 15:37:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJHKV-00058r-00
	for ietf@ietf.org; Thu, 29 Apr 2004 15:36:20 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJHJe-000568-00
	for ietf@ietf.org; Thu, 29 Apr 2004 15:35:26 -0400
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id i3TJZT7s021423
	for <ietf@ietf.org>; Thu, 29 Apr 2004 20:35:29 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id UAA04897
	for <ietf@ietf.org>; Thu, 29 Apr 2004 20:35:27 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i3TJZRf09650
	for ietf@ietf.org; Thu, 29 Apr 2004 20:35:27 +0100
Date: Thu, 29 Apr 2004 20:35:27 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <20040429193527.GA9407@login.ecs.soton.ac.uk>
References: <20040428162010.E0FF67B46@berkshire.research.att.com> <200404291321.i3TDLKn07410@boreas.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200404291321.i3TDLKn07410@boreas.isi.edu>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Thu, Apr 29, 2004 at 06:21:20AM -0700, Bill Manning wrote:
> 	Those who do not learn from history are doomed to repeat it.
> 
> 	This is -exactly- the tpc.int. model,
> 			  the e164.int. model,
> 			  the e164.arpa. model...
> 
> 	in a phrase...  "lacks traction"

So, place your bets on which slippery slopes ICANN takes us down...

I'm not convinced of a good argument for any of the proposed new TLDs to
be granted.   But I'm sure some/many will.   More money for ICANN...

This is the sort of thing ISOC should speak out on.

Tim

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



From ietf-admin@ietf.org  Thu Apr 29 17:13: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 RAA02149
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 17:13: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 1BJIqc-0006LF-Vw
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 17:13:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJIpd-0006Ee-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 17:12:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJIol-00066U-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 17:11:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJIbZ-0004Td-Pe; Thu, 29 Apr 2004 16:58:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJHsS-00023u-SJ
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 16:11: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 QAA25315
	for <ietf@ietf.org>; Thu, 29 Apr 2004 16:11: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 1BJHsL-0006wD-KW
	for ietf@ietf.org; Thu, 29 Apr 2004 16:11:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJHrM-0006ui-00
	for ietf@ietf.org; Thu, 29 Apr 2004 16:10:16 -0400
Received: from [69.59.189.34] (helo=mail.ar.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJHqT-0006tU-00
	for ietf@ietf.org; Thu, 29 Apr 2004 16:09:21 -0400
Received: by mail.ar.com (Postfix, from userid 1012)
	id 84B56148047; Thu, 29 Apr 2004 13:48:26 -0700 (PDT)
Received: from king (adsl-68-125-132-150.dsl.pltn13.pacbell.net [68.125.132.150])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(Client did not present a certificate)
	by mail.ar.com (Postfix) with ESMTP
	id B22B5148047; Thu, 29 Apr 2004 13:48:22 -0700 (PDT)
Date: Thu, 29 Apr 2004 13:08:43 -0700 (PDT)
From: Rick Wesson <wessorh@ar.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <20040429193527.GA9407@login.ecs.soton.ac.uk>
Message-ID: <Pine.LNX.4.58.0404291307080.20378@king.ar.com>
References: <20040428162010.E0FF67B46@berkshire.research.att.com>
 <200404291321.i3TDLKn07410@boreas.isi.edu> <20040429193527.GA9407@login.ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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 the sort of thing ISOC should speak out on.

doh! ISOC can't as they are the major benefactor from the .org divestature
from verisign.

sorry, try again.


-rick


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


From exim@www1.ietf.org  Thu Apr 29 17:19:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02627
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 17:19:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJIos-0004A0-Mh
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 17:11:47 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3TLBkU3015936
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 17:11:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJIbZ-0004Td-Pe; Thu, 29 Apr 2004 16:58:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJHsS-00023u-SJ
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 16:11: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 QAA25315
	for <ietf@ietf.org>; Thu, 29 Apr 2004 16:11: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 1BJHsL-0006wD-KW
	for ietf@ietf.org; Thu, 29 Apr 2004 16:11:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJHrM-0006ui-00
	for ietf@ietf.org; Thu, 29 Apr 2004 16:10:16 -0400
Received: from [69.59.189.34] (helo=mail.ar.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJHqT-0006tU-00
	for ietf@ietf.org; Thu, 29 Apr 2004 16:09:21 -0400
Received: by mail.ar.com (Postfix, from userid 1012)
	id 84B56148047; Thu, 29 Apr 2004 13:48:26 -0700 (PDT)
Received: from king (adsl-68-125-132-150.dsl.pltn13.pacbell.net [68.125.132.150])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(Client did not present a certificate)
	by mail.ar.com (Postfix) with ESMTP
	id B22B5148047; Thu, 29 Apr 2004 13:48:22 -0700 (PDT)
Date: Thu, 29 Apr 2004 13:08:43 -0700 (PDT)
From: Rick Wesson <wessorh@ar.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <20040429193527.GA9407@login.ecs.soton.ac.uk>
Message-ID: <Pine.LNX.4.58.0404291307080.20378@king.ar.com>
References: <20040428162010.E0FF67B46@berkshire.research.att.com>
 <200404291321.i3TDLKn07410@boreas.isi.edu> <20040429193527.GA9407@login.ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>




> This is the sort of thing ISOC should speak out on.

doh! ISOC can't as they are the major benefactor from the .org divestature
from verisign.

sorry, try again.


-rick


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



From ietf-admin@ietf.org  Thu Apr 29 18:07: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 SAA05486
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 18:07: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 1BJJgk-00028Q-Lo
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 18:07:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJJfq-000259-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 18:06:31 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJJfA-000229-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 18:05:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJJQu-000870-00; Thu, 29 Apr 2004 17:51:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJJJZ-0006OZ-D0
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 17:43: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 RAA04421
	for <ietf@ietf.org>; Thu, 29 Apr 2004 17:43: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 1BJJJR-00019o-MJ
	for ietf@ietf.org; Thu, 29 Apr 2004 17:43:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJJIW-00017t-00
	for ietf@ietf.org; Thu, 29 Apr 2004 17:42:25 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJJHl-00015Z-00
	for ietf@ietf.org; Thu, 29 Apr 2004 17:41:38 -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 i3TLfP1C048263;
	Thu, 29 Apr 2004 23:41:25 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <E1BJH3F-0003jW-00@ietf-mx>
References: <E1BJH3F-0003jW-00@ietf-mx>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F9398362-9A25-11D8-84EA-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Thu, 29 Apr 2004 23:41:29 +0200
To: "Tony Hain" <alh-ietf@tndh.net>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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 29-apr-04, at 21:18, Tony Hain wrote:

>> This isn't true. No one is required by law to register their 
>> trademark as
>> a domain name.

> IANAL, but in my discussions with lawyers focused on trademark law, in
> effect they are required. The perception that they are not defending 
> their
> rights effectively means they abandon them.

Defending their trademark doesn't necessarily mean registering every 
possible domain with the trademark in it, but it does usually mean 
going after other people who register a domain with the trademark in 
it. (Although there is always the slight problem that domain names are 
globally unique while very few trademarks are.)

>> So far, I still haven't heard a _technical_ reason against these 
>> TLD's.

> The technical argument here is flattening of the name space with the
> associated concentration higher up the tree.

So what angle hierarchy is desirable? Obviously a completely flat space 
isn't good because the zones get too large, but a very deep space isn't 
either as it takes more time to recurse through.

> /flame-suit-on/ Rather than granting new TLDs, there should be an 
> effort to
> deprecate the existing non-cc TLDs and move everyone out within 3 
> years. The
> historical artifact of a failed experiment is no reason to continue 
> down
> that path.

So what is the rationale for organizing ourselves based on our 
respective countries? If I may borrow your suit for a minute, I have 
another suggestion: no hard limits on TLDs, but every organization only 
gets to have a domain name in one TLD. So the practice of registering 
<domain>.* would have to end.


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


From exim@www1.ietf.org  Thu Apr 29 18:10:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06001
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 18:10:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJJfH-0005Le-4B
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 18:05:55 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3TM5tRH020550
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 18:05:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJJQu-000870-00; Thu, 29 Apr 2004 17:51:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJJJZ-0006OZ-D0
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 17:43: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 RAA04421
	for <ietf@ietf.org>; Thu, 29 Apr 2004 17:43: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 1BJJJR-00019o-MJ
	for ietf@ietf.org; Thu, 29 Apr 2004 17:43:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJJIW-00017t-00
	for ietf@ietf.org; Thu, 29 Apr 2004 17:42:25 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJJHl-00015Z-00
	for ietf@ietf.org; Thu, 29 Apr 2004 17:41:38 -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 i3TLfP1C048263;
	Thu, 29 Apr 2004 23:41:25 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <E1BJH3F-0003jW-00@ietf-mx>
References: <E1BJH3F-0003jW-00@ietf-mx>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F9398362-9A25-11D8-84EA-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Thu, 29 Apr 2004 23:41:29 +0200
To: "Tony Hain" <alh-ietf@tndh.net>
X-Mailer: Apple Mail (2.613)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

On 29-apr-04, at 21:18, Tony Hain wrote:

>> This isn't true. No one is required by law to register their 
>> trademark as
>> a domain name.

> IANAL, but in my discussions with lawyers focused on trademark law, in
> effect they are required. The perception that they are not defending 
> their
> rights effectively means they abandon them.

Defending their trademark doesn't necessarily mean registering every 
possible domain with the trademark in it, but it does usually mean 
going after other people who register a domain with the trademark in 
it. (Although there is always the slight problem that domain names are 
globally unique while very few trademarks are.)

>> So far, I still haven't heard a _technical_ reason against these 
>> TLD's.

> The technical argument here is flattening of the name space with the
> associated concentration higher up the tree.

So what angle hierarchy is desirable? Obviously a completely flat space 
isn't good because the zones get too large, but a very deep space isn't 
either as it takes more time to recurse through.

> /flame-suit-on/ Rather than granting new TLDs, there should be an 
> effort to
> deprecate the existing non-cc TLDs and move everyone out within 3 
> years. The
> historical artifact of a failed experiment is no reason to continue 
> down
> that path.

So what is the rationale for organizing ourselves based on our 
respective countries? If I may borrow your suit for a minute, I have 
another suggestion: no hard limits on TLDs, but every organization only 
gets to have a domain name in one TLD. So the practice of registering 
<domain>.* would have to end.


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



From ietf-admin@ietf.org  Thu Apr 29 20:22: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 UAA12907
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 20:22: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 1BJLnS-00040G-TX
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 20:22:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJLmX-0003vq-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 20:21:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJLle-0003sk-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 20:20:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJLcO-00077G-CK; Thu, 29 Apr 2004 20:11:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJLY0-00063x-9L
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 20:06: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 UAA12321
	for <ietf@ietf.org>; Thu, 29 Apr 2004 20:06: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 1BJLXu-0002vp-I9
	for ietf@ietf.org; Thu, 29 Apr 2004 20:06:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJLWx-0002ra-00
	for ietf@ietf.org; Thu, 29 Apr 2004 20:05:28 -0400
Received: from p2.cavebear.com ([199.184.128.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJLWB-0002ku-00
	for ietf@ietf.org; Thu, 29 Apr 2004 20:04:39 -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 i3U047Qw018821
	for <ietf@ietf.org>; Thu, 29 Apr 2004 17:04:07 -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 i3U047DN017428
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ietf@ietf.org>; Thu, 29 Apr 2004 17:04:07 -0700
Received: (from karl@localhost)
	by npax.cavebear.com (8.12.10/8.12.10/Submit) id i3U047b2017426
	for ietf@ietf.org; Thu, 29 Apr 2004 17:04:07 -0700
Received: by npax.cavebear.com (tmda-sendmail, from uid 2000);
	Thu, 29 Apr 2004 17:04:06 -0700 (PDT)
Date: Thu, 29 Apr 2004 17:04:06 -0700 (PDT)
Reply-To: Karl Auerbach <karl@cavebear.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
cc: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <20040429193527.GA9407@login.ecs.soton.ac.uk>
Message-ID: <Pine.LNX.4.58.0404291559310.14517@npax.cavebear.com>
References: <20040428162010.E0FF67B46@berkshire.research.att.com>
	<200404291321.i3TDLKn07410@boreas.isi.edu>
	<20040429193527.GA9407@login.ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
From: Karl Auerbach <karl@cavebear.com>
X-Delivery-Agent: TMDA/1.0 (Cannonade)
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
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,US_DOLLARS_3 autolearn=no 
	version=2.60


> So, place your bets on which slippery slopes ICANN takes us down...

ICANN loves these "sponsored" TLDs.  It's the only kind they are presently
considering.  Sponsors generally have the cash needed to cover ICANN's
application fee (which is typically on the order of $35,000 to $50,000,
and is non-refundable even if the application is turned down or left in an
indefinite limbo of being neither accepted nor rejected) and any ongoing
tithes.  (Remember, ICANN's budget is growing towards $10,000,000USD per
year and that money has to come from somewhere.)  And the "sponsors"
generally have well a behaved and limited membership and are thus less
likely to burden ICANN staff with work and are less likely to get into
disputes (and lawsuits) with ICANN.

I personally find many of the proposed uses for these "sponsored" TLDs
rather silly and non-innovative - and they could well be done further down
the DNS hierarchy and their only reason to be at the top level is for the
prestige (and image marketing value) of having top level domain status.

There are a couple of things about this situation:

First, is that some of the TLD proposals before ICANN, such as .mobi,
might contain some seeds of technical harm to the net.  For example, if
the .mobi folks don't use their own intermediate caching resolvers and
rather allow all those mobile devices to go directly to the roots then
there could be an increase in the traffic going to root and other servers.
This could be exacerbated if those devices are frequently power cycled and
lose their DNS caches.  The .mobi folks haven't said that they are going
to do this, but then again they haven't said that they are aware of this
potential issue.

Second, the idea that a TLD categorizes all of the resource records of all
types found under that TLD seems to me to be wrong.  For instance, assume
there's a TLD called "blue". if an A record found under a.b.c.blue leads
me to an IP address on an interface, it is unreasonable to believe that
the only services delivered via that address are of a "blue" nature.  I
suspect that many people who want these TLDs think of the net only in the
limited sense of the world wide web.

Third is that, as Tony Hain mentioned, there is trademark pressure that
will eventually suggest to every big trademark holder that they ought to
be a TLD.  This may or not come to pass, but we can guess that at least
some of the big trademark folks will give it a try, particularly after
some of ICANN's "sponsored" TLDs ossify over time into de facto marks and
thus blaze a trail that trademark owners might want to follow.  And where
one trademark owner goes, the herd is sure to follow.

My own view is that we ought to be trying to shape the DNS tree so that it
is well shaped in terms of width and depth of the hierarchy.  I don't know
the metrics of that shape.  Have there been studies regarding the how the
efficiency of DNS and DNS caching vary with DNS label depth and zone
width?

As for uses of TLDs - my own view is that as long as they are allocated
only rarely then the few awards should go to those uses that contain the
maximum innovation, maximimum flexibility, and give the greatest value to
the users of the net.

But I don't see why allocation of new TLDs needs to be a rare event.

Personally, I want a lot of new TLDs, so that folks who have silly ideas
and silly business models can try em out and be given a chance to flop -
but this means that there needs to be a criteria to determine flopness and
to reap the failed TLDs so they don't become dead zones in the DNS
hierarchy.

And I think it ought to be a requirement that any idea proposed for a TLD
first be prototyped somewhere down the DNS hierarchy.

Anybody who wants a new TLD should have to pledge allegance to the
end-to-end principle (i.e. no new "sitefinder"s) and promise to adhere to
applicable internet technical standards and practices.

I also would like to start to break the semantic implications of TLD names
- I'd prefer that any new ones have names that are meaningless in any
language, like "ts4-0k7m".  Yeah this has been gone over many times - but
I still have this hope that with some nudging people will stop using DNS
as a directory.

		--karl--


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


From exim@www1.ietf.org  Thu Apr 29 20:26:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13038
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 20:26:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJLlj-0008Nd-3t
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 20:20:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3U0KhTD032193
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 20:20:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJLcO-00077G-CK; Thu, 29 Apr 2004 20:11:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJLY0-00063x-9L
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 20:06: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 UAA12321
	for <ietf@ietf.org>; Thu, 29 Apr 2004 20:06: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 1BJLXu-0002vp-I9
	for ietf@ietf.org; Thu, 29 Apr 2004 20:06:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJLWx-0002ra-00
	for ietf@ietf.org; Thu, 29 Apr 2004 20:05:28 -0400
Received: from p2.cavebear.com ([199.184.128.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJLWB-0002ku-00
	for ietf@ietf.org; Thu, 29 Apr 2004 20:04:39 -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 i3U047Qw018821
	for <ietf@ietf.org>; Thu, 29 Apr 2004 17:04:07 -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 i3U047DN017428
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ietf@ietf.org>; Thu, 29 Apr 2004 17:04:07 -0700
Received: (from karl@localhost)
	by npax.cavebear.com (8.12.10/8.12.10/Submit) id i3U047b2017426
	for ietf@ietf.org; Thu, 29 Apr 2004 17:04:07 -0700
Received: by npax.cavebear.com (tmda-sendmail, from uid 2000);
	Thu, 29 Apr 2004 17:04:06 -0700 (PDT)
Date: Thu, 29 Apr 2004 17:04:06 -0700 (PDT)
Reply-To: Karl Auerbach <karl@cavebear.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
cc: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
In-Reply-To: <20040429193527.GA9407@login.ecs.soton.ac.uk>
Message-ID: <Pine.LNX.4.58.0404291559310.14517@npax.cavebear.com>
References: <20040428162010.E0FF67B46@berkshire.research.att.com>
	<200404291321.i3TDLKn07410@boreas.isi.edu>
	<20040429193527.GA9407@login.ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
From: Karl Auerbach <karl@cavebear.com>
X-Delivery-Agent: TMDA/1.0 (Cannonade)
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=US_DOLLARS_3 autolearn=no 
	version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>


> So, place your bets on which slippery slopes ICANN takes us down...

ICANN loves these "sponsored" TLDs.  It's the only kind they are presently
considering.  Sponsors generally have the cash needed to cover ICANN's
application fee (which is typically on the order of $35,000 to $50,000,
and is non-refundable even if the application is turned down or left in an
indefinite limbo of being neither accepted nor rejected) and any ongoing
tithes.  (Remember, ICANN's budget is growing towards $10,000,000USD per
year and that money has to come from somewhere.)  And the "sponsors"
generally have well a behaved and limited membership and are thus less
likely to burden ICANN staff with work and are less likely to get into
disputes (and lawsuits) with ICANN.

I personally find many of the proposed uses for these "sponsored" TLDs
rather silly and non-innovative - and they could well be done further down
the DNS hierarchy and their only reason to be at the top level is for the
prestige (and image marketing value) of having top level domain status.

There are a couple of things about this situation:

First, is that some of the TLD proposals before ICANN, such as .mobi,
might contain some seeds of technical harm to the net.  For example, if
the .mobi folks don't use their own intermediate caching resolvers and
rather allow all those mobile devices to go directly to the roots then
there could be an increase in the traffic going to root and other servers.
This could be exacerbated if those devices are frequently power cycled and
lose their DNS caches.  The .mobi folks haven't said that they are going
to do this, but then again they haven't said that they are aware of this
potential issue.

Second, the idea that a TLD categorizes all of the resource records of all
types found under that TLD seems to me to be wrong.  For instance, assume
there's a TLD called "blue". if an A record found under a.b.c.blue leads
me to an IP address on an interface, it is unreasonable to believe that
the only services delivered via that address are of a "blue" nature.  I
suspect that many people who want these TLDs think of the net only in the
limited sense of the world wide web.

Third is that, as Tony Hain mentioned, there is trademark pressure that
will eventually suggest to every big trademark holder that they ought to
be a TLD.  This may or not come to pass, but we can guess that at least
some of the big trademark folks will give it a try, particularly after
some of ICANN's "sponsored" TLDs ossify over time into de facto marks and
thus blaze a trail that trademark owners might want to follow.  And where
one trademark owner goes, the herd is sure to follow.

My own view is that we ought to be trying to shape the DNS tree so that it
is well shaped in terms of width and depth of the hierarchy.  I don't know
the metrics of that shape.  Have there been studies regarding the how the
efficiency of DNS and DNS caching vary with DNS label depth and zone
width?

As for uses of TLDs - my own view is that as long as they are allocated
only rarely then the few awards should go to those uses that contain the
maximum innovation, maximimum flexibility, and give the greatest value to
the users of the net.

But I don't see why allocation of new TLDs needs to be a rare event.

Personally, I want a lot of new TLDs, so that folks who have silly ideas
and silly business models can try em out and be given a chance to flop -
but this means that there needs to be a criteria to determine flopness and
to reap the failed TLDs so they don't become dead zones in the DNS
hierarchy.

And I think it ought to be a requirement that any idea proposed for a TLD
first be prototyped somewhere down the DNS hierarchy.

Anybody who wants a new TLD should have to pledge allegance to the
end-to-end principle (i.e. no new "sitefinder"s) and promise to adhere to
applicable internet technical standards and practices.

I also would like to start to break the semantic implications of TLD names
- I'd prefer that any new ones have names that are meaningless in any
language, like "ts4-0k7m".  Yeah this has been gone over many times - but
I still have this hope that with some nudging people will stop using DNS
as a directory.

		--karl--


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



From ietf-admin@ietf.org  Thu Apr 29 20:44: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 UAA14515
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 20:44: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 1BJM8J-0005z8-Lp
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 20:44:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJM6s-0005lF-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 20:42:36 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJM5W-0005T8-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 20:41:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJLyd-0001n0-Sv; Thu, 29 Apr 2004 20:34:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJLtS-0000gt-Sy
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 20:28: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 UAA13130
	for <ietf@ietf.org>; Thu, 29 Apr 2004 20: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 1BJLtN-0004Nz-6c
	for ietf@ietf.org; Thu, 29 Apr 2004 20:28:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJLsb-0004KK-00
	for ietf@ietf.org; Thu, 29 Apr 2004 20:27:49 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJLs6-0004G3-00
	for ietf@ietf.org; Thu, 29 Apr 2004 20:27:18 -0400
Received: from eaglet (127.0.0.1:4503)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S52BA6> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 29 Apr 2004 17:23:47 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
Subject: RE: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Thu, 29 Apr 2004 17:27:18 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQuMkcjWoBirXOoQAK3zShiM5ENHQAFfjUw
In-Reply-To: <F9398362-9A25-11D8-84EA-000A95CD987A@muada.com>
Message-Id: <E1BJLs6-0004G3-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum wrote:
> On 29-apr-04, at 21:18, Tony Hain wrote:
> 
> >> This isn't true. No one is required by law to register their
> >> trademark as
> >> a domain name.
> 
> > IANAL, but in my discussions with lawyers focused on trademark law, in
> > effect they are required. The perception that they are not defending
> > their
> > rights effectively means they abandon them.
> 
> Defending their trademark doesn't necessarily mean registering every
> possible domain with the trademark in it, but it does usually mean
> going after other people who register a domain with the trademark in
> it. 

Agreed, but given the reality of legal fees the cheapest way to defend a
trademark is to register it in every domain. 

> (Although there is always the slight problem that domain names are
> globally unique while very few trademarks are.)

While they are unique within the context of each registered country.

> 
> >> So far, I still haven't heard a _technical_ reason against these
> >> TLD's.
> 
> > The technical argument here is flattening of the name space with the
> > associated concentration higher up the tree.
> 
> So what angle hierarchy is desirable? Obviously a completely flat space
> isn't good because the zones get too large, but a very deep space isn't
> either as it takes more time to recurse through.

A good research topic ;)   gut feel says 3-5, but YMMV

> 
> > /flame-suit-on/ Rather than granting new TLDs, there should be an
> > effort to
> > deprecate the existing non-cc TLDs and move everyone out within 3
> > years. The
> > historical artifact of a failed experiment is no reason to continue
> > down
> > that path.
> 
> So what is the rationale for organizing ourselves based on our
> respective countries? 

Trademark law is already aligned that way.

> If I may borrow your suit for a minute, I have
> another suggestion: no hard limits on TLDs, but every organization only
> gets to have a domain name in one TLD. So the practice of registering
> <domain>.* would have to end.

And nobody can register more than one domain per year. This would have the
side effect of slowing down the benefactors of the spammers. 

Tony



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


From exim@www1.ietf.org  Thu Apr 29 20:52:14 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14800
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 20:52:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJM5b-00038z-Is
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 20:41:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3U0fF72012073
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 20:41:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJLyd-0001n0-Sv; Thu, 29 Apr 2004 20:34:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJLtS-0000gt-Sy
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 20:28: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 UAA13130
	for <ietf@ietf.org>; Thu, 29 Apr 2004 20: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 1BJLtN-0004Nz-6c
	for ietf@ietf.org; Thu, 29 Apr 2004 20:28:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJLsb-0004KK-00
	for ietf@ietf.org; Thu, 29 Apr 2004 20:27:49 -0400
Received: from [4.16.92.133] (helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJLs6-0004G3-00
	for ietf@ietf.org; Thu, 29 Apr 2004 20:27:18 -0400
Received: from eaglet (127.0.0.1:4503)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S52BA6> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 29 Apr 2004 17:23:47 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
Subject: RE: [Ietf] New .mobi, .xxx, ... TLDs?
Date: Thu, 29 Apr 2004 17:27:18 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcQuMkcjWoBirXOoQAK3zShiM5ENHQAFfjUw
In-Reply-To: <F9398362-9A25-11D8-84EA-000A95CD987A@muada.com>
Message-Id: <E1BJLs6-0004G3-00@ietf-mx>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Iljitsch van Beijnum wrote:
> On 29-apr-04, at 21:18, Tony Hain wrote:
> 
> >> This isn't true. No one is required by law to register their
> >> trademark as
> >> a domain name.
> 
> > IANAL, but in my discussions with lawyers focused on trademark law, in
> > effect they are required. The perception that they are not defending
> > their
> > rights effectively means they abandon them.
> 
> Defending their trademark doesn't necessarily mean registering every
> possible domain with the trademark in it, but it does usually mean
> going after other people who register a domain with the trademark in
> it. 

Agreed, but given the reality of legal fees the cheapest way to defend a
trademark is to register it in every domain. 

> (Although there is always the slight problem that domain names are
> globally unique while very few trademarks are.)

While they are unique within the context of each registered country.

> 
> >> So far, I still haven't heard a _technical_ reason against these
> >> TLD's.
> 
> > The technical argument here is flattening of the name space with the
> > associated concentration higher up the tree.
> 
> So what angle hierarchy is desirable? Obviously a completely flat space
> isn't good because the zones get too large, but a very deep space isn't
> either as it takes more time to recurse through.

A good research topic ;)   gut feel says 3-5, but YMMV

> 
> > /flame-suit-on/ Rather than granting new TLDs, there should be an
> > effort to
> > deprecate the existing non-cc TLDs and move everyone out within 3
> > years. The
> > historical artifact of a failed experiment is no reason to continue
> > down
> > that path.
> 
> So what is the rationale for organizing ourselves based on our
> respective countries? 

Trademark law is already aligned that way.

> If I may borrow your suit for a minute, I have
> another suggestion: no hard limits on TLDs, but every organization only
> gets to have a domain name in one TLD. So the practice of registering
> <domain>.* would have to end.

And nobody can register more than one domain per year. This would have the
side effect of slowing down the benefactors of the spammers. 

Tony



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



From xoomi@britishvirginislands.com  Thu Apr 29 20:59: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 UAA15159
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 20:59: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 1BJMNI-00074J-U8
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 20:59:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJMMI-0006z5-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 20:58:30 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJMLU-0006vM-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 20:57:40 -0400
Received: from aph-aug-102-1-5-252.w80-15.abo.wanadoo.fr ([80.15.78.252])
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1BJMLX-0006A0-NI
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 20:57:44 -0400
Received: from 80.132.248.109 by 80.15.78.252; Fri, 30 Apr 2004 06:58:30 +0500
Message-ID: <XJDXISIICQOUGHELJFBPG@digitalmail.com>
From: "Martina Bowen" <xoomi@britishvirginislands.com>
Reply-To: "Martina Bowen" <xoomi@britishvirginislands.com>
To: ietf-archive@ietf.org
Subject: Fwd: Save 40%-90% on Hundreds of Prescription Drugs. Discreetly Shipped Overnight.
Date: Fri, 30 Apr 2004 02:58:30 +0100
X-Mailer: AOL 5.0 for Windows US sub 658
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--2260504182009003"
X-Priority: 3
X-MSMail-Priority: Normal
X-IP: 126.186.207.76
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: Yes, hits=12.5 required=5.0 tests=BIZ_TLD,FORGED_AOL_HTML,
	FORGED_MUA_AOL_FROM,HTML_20_30,HTML_FONTCOLOR_UNSAFE,HTML_MESSAGE,
	JOIN_MILLIONS,MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,
	MIME_HTML_ONLY_MULTI,MISSING_MIMEOLE,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
X-Spam-Report: 
	*  1.8 JOIN_MILLIONS BODY: Join Millions of Americans
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	*  0.1 HTML_FONTCOLOR_UNSAFE BODY: HTML font color not in safe 6x6x6 palette
	*  0.5 HTML_20_30 BODY: Message is 20% to 30% HTML
	*  0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
	*  0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset
	*  0.8 BIZ_TLD URI: Contains a URL in the BIZ top-level domain
	*  1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
	*  4.3 FORGED_MUA_AOL_FROM Forged mail pretending to be from AOL (by From)
	*  1.8 FORGED_AOL_HTML AOL can't send HTML message only
	*  1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts
	*  0.1 MISSING_OUTLOOK_NAME Message looks like Outlook, but isn't

----2260504182009003
Content-Type: text/html;
Content-Transfer-Encoding: 7Bit

<html><head><style type="text/css"><!-- .style5 {font-family: Arial, Helvetica, sans-serif; font-size: 14px; } .style6 {font-size: 10px} --></style></head><body>
<p class="style5">Hel</pukt>lo,</p>
<p class="style5">Ple</jmd>ase jo</knccz>in thou</plnbvk>sands of onl</byft>ine users who discr</vprsrq>eetly, saf</kgp>ely and conve</xlj>niently ord</tzq>er pre</egv>scri</dlwqr>ption medi</ogw>cation for <strong>weight los</khuxpt>s/die</flcgx>t pi</gymi>ll </strong> me</bdbwvz>dic</ltuniu>ations, <strong>sk</ufuen>in care, bi</gnil>rth control, mus</ffar>cle relax</rdhdy>ants, high level pai</dsybz>n relief, anx</hxlbwr>iety, pre</kkio>scrip</udaac>tion sle</mqkv>eping ai</tgob>ds, a</uogj>nti-depr</svyvy>essant medi</gcfikx>cat</kroz>ions </strong> and more.</p>
<p class="style5"><a href="http://www.jwrh.techmind758tabs.biz/g17/"><b>Sta</suspfi>rt Orde</fvxlg>ring yo</cgl>ur Medic</kulkr>ations H</nrvgr>ere</b></a></p><p class="style5">&nbsp;</p>
<p style="font-size:0px; color:white" align="left">Xramrod winsome zippy pipette michelson tenspot ciliate irresponsible nighttime closure vampire contention pellagra pickett both pronounceable purpose freya beige dwyer tat adonis  : Yhurry wei splutter conceal alai circulate insure chauncey airflow goal sludge bleary fuchsia alkaloid appeasable bangui prohibition heidelberg religion tribulate disastrous crockett gallstone bestow devil confucius : Klakeside cork ruffian virgo cyclic cramp discovery hydrolysis bacchus cream befuddle satisfy squid expire beak woolgather dispersible gastrointestinal depart aggressor kiwi adelia finley yorktown sparkle duopolist thiouracil glean combine farce cohen martinson splotch .Whedonism basket no disney drunk fried armada  : Gdelimitation scurvy boot glassy herd penalty spitfire upstate cargo durkee bake carob spalding sympathetic helium burke kidnap councilman cereus separate ala moslem collaborate ! Acountersink berne battalion thunder denton nevertheless tripartite vasquez depressive bridle einsteinium volumetric kemp pneumococcus rene mccauley elk filet perfume intoxicant crib turtleneck deluge gunther argive conakry edit converge delphi common bright indiscernible extant caste shrug lark upswing muzo abutting tabu abode earthen nebraska subsidiary fraud tremendous din ida prismatic salaried executrix sanhedrin venice clip astraddle pitch collet bitumen fracture california excruciate knobby .Vdiscretion carolyn marquee hydrometer pantomime benchmark burton covariant  . Uhailstone quadrillion sight abide . Jlioness midscale muon balled circlet aristocracy salad none contextual camber dominic mixup sensate asexual arequipa choice tradesmen transept soma abalone alvarez assailant interference latitudinal rica bigot anaglyph .Rmacho chemistry long eulogy febrile bitnet spectrogram dunbar bilingual rutile arson besmirch  . Aaccolade sheffield bayberry checkpoint selkirk ; Mvesicular dusk hydrosphere paterson lesson aylesbury pectoralis interpolatory plasm cotyledon votive bern
e determinate erich carlson hourglass buchenwald suspensor vein claustrophobia bilge infinitude befog captaincy statistician thrips bulwark storey eat qed coverage hydroxy earthmove muncie croak lavabo toe domino sultanate divisor credulity delphic dodd kant damask resolve mauricio canyon sidestepping agglutinin draftee heighten gross myeline affluent divulge thrust .Qelicit injure predict northeast airfare craft halvah ! Ybailey chive congressman envious opposable ; Napollo children abase brigade board mullah whistleable concatenate iraq newbold quadrivium alligator compelling contravariant effete gibberish lavoisier bureaucrat epoxy bullwhack curie toad dent handbook purify affectate ad written cytolysis donate accompany official brest cowhand belligerent spicy keelson restful board cabinet fled genteel penury accordion combatted flail  Araspberry cascade ar dogma ross athletic e's wheel bandgap oatmeal straightaway equivalent ambition firework pelham !!! Umenstruate bucketfull deprave equatorial coadjutor pion backwood anthem !!! Useaweed repugnant orphic map wilhelm shortfall castillo spiteful shakespeare pedestal dichotomize shrewish circumvent broomcorn erosible berniece casey osier  </p>

<P align="LEFT"><FONT COLOR="#616161" SIZE="-2" FACE="Arial">I</hvshn>f th</nyuc>is
no</snl>tice has rea</tjertp>ched y</yxj>ou in er</pqgnv>ror, ple</vnhq>ase not</ucvhv>ify us by</FONT><FONT
 COLOR="#d5d5d0" SIZE="-2" FACE="Arial"> </FONT><FONT SIZE="-2"
 FACE="Arial"><A HREF="http://www.psoeeh.techmind758tabs.biz/unsubscribe.ddd">clic</xvcrqj>king
he</adx>re</A></FONT>
</body>
</html>


----2260504182009003--



From ietf-admin@ietf.org  Thu Apr 29 21:03: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 VAA15609
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 21:03: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 1BJMRF-0007hC-Lv
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 21:03:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJMQD-0007Yp-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 21:02:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJMPL-0007PL-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 21:01:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJMHy-000541-Aj; Thu, 29 Apr 2004 20:54:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJMBi-0003rj-0a
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 20:47: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 UAA14753
	for <ietf@ietf.org>; Thu, 29 Apr 2004 20:47: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 1BJMBc-0006IO-B0
	for ietf@ietf.org; Thu, 29 Apr 2004 20:47:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJMAm-0006Fo-00
	for ietf@ietf.org; Thu, 29 Apr 2004 20:46:36 -0400
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJMAG-0006CH-00
	for ietf@ietf.org; Thu, 29 Apr 2004 20:46:04 -0400
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com for <ietf@ietf.org>;
          Thu, 29 Apr 2004 20:46:07 -0400
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Date: Thu, 29 Apr 2004 20:46:07 -0400
Message-ID: <20040430004607576.AAA1120@hq.lindsayelec.com@rflooker1>
Subject: [Ietf] TLDs a thing not to do
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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

Karl A said:
>Anybody who wants a new TLD should have to pledge allegance to the
>end-to-end principle (i.e. no new "sitefinder"s) and promise to adhere to
>applicable internet technical standards and practices.

Dan K says:
The idea of harvesting bad DNS accesses as a business plan never occured to
be until I saw it done. Not a really obvious thing.

Anyway, Static, a little dynamic, or real time reconfigurable... DNS URL's
should for sure regard this end-to-end thing seriously. Problem is,
creativity can probably generate a lot of border cases, partially legit
dynamic reallocations. Obviously, the idea the people involved are the
arbiters is the real test. 

It would be interesting if somebody (ex. grad student working on a Masters
in economics), would try to root thru the DNS issues from first principles.
As an example, a read the Japanese TLD doesn't recycle domain names. When
illigitimate, they get parked forever? Anyway, reducing the incentive to
Cyber squatting, without needing a quasi-judicial system... that sort of
thing; would be interesting as a thesis or three.

But, well, I do thing a .XXX one thats expensive (pun intended), like sin
would be useful. Of course, if the uptake rate was lousy... that would prove
a lot.

Its occurred to me multiplying TLD's has this odd divide by N issue to it.
If you have X.foo you often want X.bar as well. So, if the DNS forced each
fixed IP to be bound only to zero or one DNS, this would allow TLD's to be
added with less moaning.

interesting.
Dan


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


From exim@www1.ietf.org  Thu Apr 29 21:05:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15805
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 21:05:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJMPR-0006IX-5f
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 21:01:46 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3U11jOv024130
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 21:01:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJMHy-000541-Aj; Thu, 29 Apr 2004 20:54:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJMBi-0003rj-0a
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 20:47: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 UAA14753
	for <ietf@ietf.org>; Thu, 29 Apr 2004 20:47: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 1BJMBc-0006IO-B0
	for ietf@ietf.org; Thu, 29 Apr 2004 20:47:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJMAm-0006Fo-00
	for ietf@ietf.org; Thu, 29 Apr 2004 20:46:36 -0400
Received: from [204.101.26.58] (helo=hq.lindsayelec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJMAG-0006CH-00
	for ietf@ietf.org; Thu, 29 Apr 2004 20:46:04 -0400
Received: from rflooker1 ([191.1.2.48]) by hq.lindsayelec.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66079U100L100S0V35)
          with SMTP id com for <ietf@ietf.org>;
          Thu, 29 Apr 2004 20:46:07 -0400
X-Sender: dank@191.1.2.250
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: dank@hq.lindsayelec.com (Dan Kolis)
Date: Thu, 29 Apr 2004 20:46:07 -0400
Message-ID: <20040430004607576.AAA1120@hq.lindsayelec.com@rflooker1>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [Ietf] TLDs a thing not to do
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

Karl A said:
>Anybody who wants a new TLD should have to pledge allegance to the
>end-to-end principle (i.e. no new "sitefinder"s) and promise to adhere to
>applicable internet technical standards and practices.

Dan K says:
The idea of harvesting bad DNS accesses as a business plan never occured to
be until I saw it done. Not a really obvious thing.

Anyway, Static, a little dynamic, or real time reconfigurable... DNS URL's
should for sure regard this end-to-end thing seriously. Problem is,
creativity can probably generate a lot of border cases, partially legit
dynamic reallocations. Obviously, the idea the people involved are the
arbiters is the real test. 

It would be interesting if somebody (ex. grad student working on a Masters
in economics), would try to root thru the DNS issues from first principles.
As an example, a read the Japanese TLD doesn't recycle domain names. When
illigitimate, they get parked forever? Anyway, reducing the incentive to
Cyber squatting, without needing a quasi-judicial system... that sort of
thing; would be interesting as a thesis or three.

But, well, I do thing a .XXX one thats expensive (pun intended), like sin
would be useful. Of course, if the uptake rate was lousy... that would prove
a lot.

Its occurred to me multiplying TLD's has this odd divide by N issue to it.
If you have X.foo you often want X.bar as well. So, if the DNS forced each
fixed IP to be bound only to zero or one DNS, this would allow TLD's to be
added with less moaning.

interesting.
Dan


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



From ietf-admin@ietf.org  Thu Apr 29 21:57: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 VAA17611
	for <ietf-archive@ietf.org>; Thu, 29 Apr 2004 21:57: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 1BJNHS-00047i-91
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 21:57:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJNGU-00043L-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 21:56:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJNFf-0003zT-00
	for ietf-archive@ietf.org; Thu, 29 Apr 2004 21:55:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJN9C-0004ai-1X; Thu, 29 Apr 2004 21:49:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJN4u-0003ij-NW
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 21:44:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17134
	for <ietf@ietf.org>; Thu, 29 Apr 2004 21:44: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 1BJN4o-00034F-Fi
	for ietf@ietf.org; Thu, 29 Apr 2004 21:44:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJN3s-00030U-00
	for ietf@ietf.org; Thu, 29 Apr 2004 21:43:32 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJN2x-0002wt-00
	for ietf@ietf.org; Thu, 29 Apr 2004 21:42:35 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BJN31-000EH9-00; Thu, 29 Apr 2004 20:42:39 -0500
Date: Thu, 29 Apr 2004 21:42:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
cc: Dean Anderson <dean@av8.com>, Stephen Sprunk <stephen@sprunk.org>,
        jfcm <info@utel.net>, Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <ACBFB13DAC66EE23B2F5520F@scan.jck.com>
X-Mailer: Mulberry/3.1.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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

Hi.

While this discussion on the IETF list has been very 
interesting, it is probably worth noting that the odds of ICANN 
staff following the IETF list to the extent needed to pull out 
this thread and make use of it are not high.

Instructions for making comments that they, and presumably the 
evaluators, will see are at

http://www.icann.org/tlds/stld-apps-19mar04/stld-public-comments.htm

That page contains both addresses for making general comments 
and addresses for specific comments on each proposal, along with 
pointers to archives of comments made so far.

The comment period on the specific applications and forms closes 
on 30 April (see
http://www.icann.org/tlds/new-stld-rfp/new-stld-application-parta-15dec03.htm
).  If those of you who have been carrying on this debate want 
even a chance that your positions will be carefully considered, 
I suggest going over to ICANN's site and posting appropriate 
summaries.

     john


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


From exim@www1.ietf.org  Thu Apr 29 22:04:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18189
	for <ietf-archive@odin.ietf.org>; Thu, 29 Apr 2004 22:04:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJNFl-0005bI-7A
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 21:55:52 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3U1tnx0021471
	for ietf-archive@odin.ietf.org; Thu, 29 Apr 2004 21:55:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJN9C-0004ai-1X; Thu, 29 Apr 2004 21:49:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJN4u-0003ij-NW
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 21:44:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17134
	for <ietf@ietf.org>; Thu, 29 Apr 2004 21:44: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 1BJN4o-00034F-Fi
	for ietf@ietf.org; Thu, 29 Apr 2004 21:44:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJN3s-00030U-00
	for ietf@ietf.org; Thu, 29 Apr 2004 21:43:32 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJN2x-0002wt-00
	for ietf@ietf.org; Thu, 29 Apr 2004 21:42:35 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BJN31-000EH9-00; Thu, 29 Apr 2004 20:42:39 -0500
Date: Thu, 29 Apr 2004 21:42:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
cc: Dean Anderson <dean@av8.com>, Stephen Sprunk <stephen@sprunk.org>,
        jfcm <info@utel.net>, Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <ACBFB13DAC66EE23B2F5520F@scan.jck.com>
X-Mailer: Mulberry/3.1.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Hi.

While this discussion on the IETF list has been very 
interesting, it is probably worth noting that the odds of ICANN 
staff following the IETF list to the extent needed to pull out 
this thread and make use of it are not high.

Instructions for making comments that they, and presumably the 
evaluators, will see are at

http://www.icann.org/tlds/stld-apps-19mar04/stld-public-comments.htm

That page contains both addresses for making general comments 
and addresses for specific comments on each proposal, along with 
pointers to archives of comments made so far.

The comment period on the specific applications and forms closes 
on 30 April (see
http://www.icann.org/tlds/new-stld-rfp/new-stld-application-parta-15dec03.htm
).  If those of you who have been carrying on this debate want 
even a chance that your positions will be carefully considered, 
I suggest going over to ICANN's site and posting appropriate 
summaries.

     john


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



From ietf-admin@ietf.org  Fri Apr 30 08:17: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 IAA12709
	for <ietf-archive@ietf.org>; Fri, 30 Apr 2004 08:17: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 1BJWx6-00035v-W8
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 08:17:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJWwA-0002uh-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 08:16:14 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJWvh-0002jr-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 08:15:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJWqA-0008M1-1E; Fri, 30 Apr 2004 08:10:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJMrZ-0002F0-2z
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 21:30: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 VAA16776
	for <ietf@ietf.org>; Thu, 29 Apr 2004 21:30: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 1BJMrS-00025P-MK
	for ietf@ietf.org; Thu, 29 Apr 2004 21:30:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJMqY-00020u-00
	for ietf@ietf.org; Thu, 29 Apr 2004 21:29:47 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJMqA-0001vE-00
	for ietf@ietf.org; Thu, 29 Apr 2004 21:29:22 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BJMpw-000DyT-00; Thu, 29 Apr 2004 20:29:08 -0500
Date: Thu, 29 Apr 2004 21:29:06 -0400
From: John C Klensin <klensin@jck.com>
To: ietf@ietf.org
cc: Dean Anderson <dean@av8.com>, Stephen Sprunk <stephen@sprunk.org>,
        jfcm <info@utel.net>, Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <7C7CA494CDCB6558009A94D5@scan.jck.com>
In-Reply-To: <20040428162010.E0FF67B46@berkshire.research.att.com>
References: <20040428162010.E0FF67B46@berkshire.research.att.com>
X-Mailer: Mulberry/3.1.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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

Hi.

While this discussion on the IETF list has been very 
interesting, it is probably worth noting that the odds of ICANN 
staff following the IETF list to the extent needed to pull out 
this thread and make use of it are not high.

Instructions for making comments that they, and presumably the 
evaluators, will see are at

http://www.icann.org/tlds/stld-apps-19mar04/stld-public-comments.htm

That page contains both addresses for making general comments 
and addresses for specific comments on each proposal, along with 
pointers to archives of comments made so far.

The comment period on the specific applications and forms closes 
on 30 April (see
http://www.icann.org/tlds/new-stld-rfp/new-stld-application-parta-15dec03.htm
).  If those of you who have been carrying on this debate want 
even a chance that your positions will be carefully considered, 
I suggest going over to ICANN's site and posting appropriate 
summaries.

     john


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


From ietf-admin@ietf.org  Fri Apr 30 08:21: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 IAA12902
	for <ietf-archive@ietf.org>; Fri, 30 Apr 2004 08:21: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 1BJX0p-0003oS-19
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 08:21:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJWzq-0003d0-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 08:20:03 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJWyo-0003P2-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 08:18:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJWqB-0008ME-ST; Fri, 30 Apr 2004 08:10:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJTiR-00071u-PG
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 04:49: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 EAA03648
	for <ietf@ietf.org>; Fri, 30 Apr 2004 04:49: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 1BJTiK-0000Sl-V2
	for ietf@ietf.org; Fri, 30 Apr 2004 04:49:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJThN-0000L7-00
	for ietf@ietf.org; Fri, 30 Apr 2004 04:48:46 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJTgU-00006t-00
	for ietf@ietf.org; Fri, 30 Apr 2004 04:47:50 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
  by ams-iport-1.cisco.com with ESMTP; 30 Apr 2004 10:54:35 +0200
X-BrightmailFiltered: true
Received: from cisco.com (ams-clip-equant-dhcp-108.cisco.com [10.61.124.109])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with SMTP id i3U8lHbj017096;
	Fri, 30 Apr 2004 10:47:19 +0200 (MEST)
Received: by cisco.com (sSMTP sendmail emulation); Fri, 30 Apr 2004 04:47:17 -0400
Date: Fri, 30 Apr 2004 04:47:17 -0400
From: Scott W Brim <swb@employees.org>
To: Aki Niemi <aki.niemi@nokia.com>
Cc: "ext Steven M. Bellovin" <smb@research.att.com>, ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <20040430084714.GB1964@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <swb@employees.org>,
	Aki Niemi <aki.niemi@nokia.com>,
	"ext Steven M. Bellovin" <smb@research.att.com>, ietf@ietf.org
References: <20040428162010.E0FF67B46@berkshire.research.att.com> <40910D37.1030205@nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40910D37.1030205@nokia.com>
User-Agent: Mutt/1.4.1i
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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 Thu, Apr 29, 2004 05:12:07PM +0300, Aki Niemi allegedly wrote:
> >I find it hard to interpret that text in any other fashion -- they want
> >to describe end-to-end protocols by DNS name.
> 
> I don't quite see what the difference here is to .edu for example. Isn't
> this indeed very similar to how the .edu provides a "clearly
> recognisable" label for educational services and content?

.edu was an administrative distinction.  (So was .net, originally.)  The
intent here is clearly to distinguish the *use* of the name, not the
administration.

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


From exim@www1.ietf.org  Fri Apr 30 08:26:02 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13161
	for <ietf-archive@odin.ietf.org>; Fri, 30 Apr 2004 08:26:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJWvh-0000g1-OX
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 08:15:51 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3UCFjRF002562
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 08:15:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJWqA-0008M1-1E; Fri, 30 Apr 2004 08:10:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJMrZ-0002F0-2z
	for ietf@optimus.ietf.org; Thu, 29 Apr 2004 21:30: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 VAA16776
	for <ietf@ietf.org>; Thu, 29 Apr 2004 21:30: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 1BJMrS-00025P-MK
	for ietf@ietf.org; Thu, 29 Apr 2004 21:30:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJMqY-00020u-00
	for ietf@ietf.org; Thu, 29 Apr 2004 21:29:47 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJMqA-0001vE-00
	for ietf@ietf.org; Thu, 29 Apr 2004 21:29:22 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BJMpw-000DyT-00; Thu, 29 Apr 2004 20:29:08 -0500
Date: Thu, 29 Apr 2004 21:29:06 -0400
From: John C Klensin <klensin@jck.com>
To: ietf@ietf.org
cc: Dean Anderson <dean@av8.com>, Stephen Sprunk <stephen@sprunk.org>,
        jfcm <info@utel.net>, Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <7C7CA494CDCB6558009A94D5@scan.jck.com>
In-Reply-To: <20040428162010.E0FF67B46@berkshire.research.att.com>
References: <20040428162010.E0FF67B46@berkshire.research.att.com>
X-Mailer: Mulberry/3.1.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Hi.

While this discussion on the IETF list has been very 
interesting, it is probably worth noting that the odds of ICANN 
staff following the IETF list to the extent needed to pull out 
this thread and make use of it are not high.

Instructions for making comments that they, and presumably the 
evaluators, will see are at

http://www.icann.org/tlds/stld-apps-19mar04/stld-public-comments.htm

That page contains both addresses for making general comments 
and addresses for specific comments on each proposal, along with 
pointers to archives of comments made so far.

The comment period on the specific applications and forms closes 
on 30 April (see
http://www.icann.org/tlds/new-stld-rfp/new-stld-application-parta-15dec03.htm
).  If those of you who have been carrying on this debate want 
even a chance that your positions will be carefully considered, 
I suggest going over to ICANN's site and posting appropriate 
summaries.

     john


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



From exim@www1.ietf.org  Fri Apr 30 08:26:10 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13190
	for <ietf-archive@odin.ietf.org>; Fri, 30 Apr 2004 08:26:10 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJWyo-0001Nd-DB
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 08:19:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3UCIwE5005212
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 08:18:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJWqB-0008ME-ST; Fri, 30 Apr 2004 08:10:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJTiR-00071u-PG
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 04:49: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 EAA03648
	for <ietf@ietf.org>; Fri, 30 Apr 2004 04:49: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 1BJTiK-0000Sl-V2
	for ietf@ietf.org; Fri, 30 Apr 2004 04:49:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJThN-0000L7-00
	for ietf@ietf.org; Fri, 30 Apr 2004 04:48:46 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJTgU-00006t-00
	for ietf@ietf.org; Fri, 30 Apr 2004 04:47:50 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
  by ams-iport-1.cisco.com with ESMTP; 30 Apr 2004 10:54:35 +0200
X-BrightmailFiltered: true
Received: from cisco.com (ams-clip-equant-dhcp-108.cisco.com [10.61.124.109])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with SMTP id i3U8lHbj017096;
	Fri, 30 Apr 2004 10:47:19 +0200 (MEST)
Received: by cisco.com (sSMTP sendmail emulation); Fri, 30 Apr 2004 04:47:17 -0400
Date: Fri, 30 Apr 2004 04:47:17 -0400
From: Scott W Brim <swb@employees.org>
To: Aki Niemi <aki.niemi@nokia.com>
Cc: "ext Steven M. Bellovin" <smb@research.att.com>, ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <20040430084714.GB1964@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <swb@employees.org>,
	Aki Niemi <aki.niemi@nokia.com>,
	"ext Steven M. Bellovin" <smb@research.att.com>, ietf@ietf.org
References: <20040428162010.E0FF67B46@berkshire.research.att.com> <40910D37.1030205@nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40910D37.1030205@nokia.com>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Thu, Apr 29, 2004 05:12:07PM +0300, Aki Niemi allegedly wrote:
> >I find it hard to interpret that text in any other fashion -- they want
> >to describe end-to-end protocols by DNS name.
> 
> I don't quite see what the difference here is to .edu for example. Isn't
> this indeed very similar to how the .edu provides a "clearly
> recognisable" label for educational services and content?

.edu was an administrative distinction.  (So was .net, originally.)  The
intent here is clearly to distinguish the *use* of the name, not the
administration.

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



From ietf-admin@ietf.org  Fri Apr 30 09:04: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 JAA29446
	for <ietf-archive@ietf.org>; Fri, 30 Apr 2004 09:04: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 1BJXgV-0004Aw-0x
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 09:04:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJXfi-0003zu-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 09:03:19 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJXeq-0003nw-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 09:02:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJXYh-0001vR-Uc; Fri, 30 Apr 2004 08:56:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJXWr-0001Hp-Vg
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 08:54: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 IAA28172
	for <ietf@ietf.org>; Fri, 30 Apr 2004 08:54: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 1BJXTx-0001fS-0f
	for ietf@ietf.org; Fri, 30 Apr 2004 08:51:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJXT6-0001Vm-00
	for ietf@ietf.org; Fri, 30 Apr 2004 08:50:16 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJXST-0001Ja-00
	for ietf@ietf.org; Fri, 30 Apr 2004 08:49:37 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id A56051D2078; Fri, 30 Apr 2004 08:49:04 -0400 (EDT)
To: alh-ietf@tndh.net, iljitsch@muada.com
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Cc: ietf@ietf.org
In-Reply-To: <F9398362-9A25-11D8-84EA-000A95CD987A@muada.com>
Message-Id: <20040430124904.A56051D2078@newdev.harvard.edu>
Date: Fri, 30 Apr 2004 08:49:04 -0400 (EDT)
From: sob@harvard.edu (Scott Bradner)
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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

> So what is the rationale for organizing ourselves based on our 
> respective countries? 

to match legal jurisdictions

Scott


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


From exim@www1.ietf.org  Fri Apr 30 09:12:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29799
	for <ietf-archive@odin.ietf.org>; Fri, 30 Apr 2004 09:12:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJXer-00046b-Pa
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 09:02:25 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3UD2PUI015753
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 09:02:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJXYh-0001vR-Uc; Fri, 30 Apr 2004 08:56:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJXWr-0001Hp-Vg
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 08:54: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 IAA28172
	for <ietf@ietf.org>; Fri, 30 Apr 2004 08:54: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 1BJXTx-0001fS-0f
	for ietf@ietf.org; Fri, 30 Apr 2004 08:51:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJXT6-0001Vm-00
	for ietf@ietf.org; Fri, 30 Apr 2004 08:50:16 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJXST-0001Ja-00
	for ietf@ietf.org; Fri, 30 Apr 2004 08:49:37 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id A56051D2078; Fri, 30 Apr 2004 08:49:04 -0400 (EDT)
To: alh-ietf@tndh.net, iljitsch@muada.com
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Cc: ietf@ietf.org
In-Reply-To: <F9398362-9A25-11D8-84EA-000A95CD987A@muada.com>
Message-Id: <20040430124904.A56051D2078@newdev.harvard.edu>
Date: Fri, 30 Apr 2004 08:49:04 -0400 (EDT)
From: sob@harvard.edu (Scott Bradner)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

> So what is the rationale for organizing ourselves based on our 
> respective countries? 

to match legal jurisdictions

Scott


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



From ietf-admin@ietf.org  Fri Apr 30 10:40: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 KAA04990
	for <ietf-archive@ietf.org>; Fri, 30 Apr 2004 10:40: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 1BJZBU-0005oc-Vv
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 10:40:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJZAT-0005jj-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 10:39:09 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJZ9Y-0005gi-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 10:38:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJYzi-0008BG-Ih; Fri, 30 Apr 2004 10:28:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJYp4-0005rj-V7
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 10:17: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 KAA03829
	for <ietf@ietf.org>; Fri, 30 Apr 2004 10:16: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 1BJYp1-0004ql-RH
	for ietf@ietf.org; Fri, 30 Apr 2004 10:16:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJYo3-0004nn-00
	for ietf@ietf.org; Fri, 30 Apr 2004 10:15:59 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJYn5-0004l6-00
	for ietf@ietf.org; Fri, 30 Apr 2004 10:14:59 -0400
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id i3UEEv7s012163
	for <ietf@ietf.org>; Fri, 30 Apr 2004 15:14:58 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id PAA03334
	for <ietf@ietf.org>; Fri, 30 Apr 2004 15:14:56 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i3UEEuw26711
	for ietf@ietf.org; Fri, 30 Apr 2004 15:14:56 +0100
Date: Fri, 30 Apr 2004 15:14:56 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <20040430141456.GC26259@login.ecs.soton.ac.uk>
References: <20040428162010.E0FF67B46@berkshire.research.att.com> <40910D37.1030205@nokia.com> <20040430084714.GB1964@sbrim-w2k01>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040430084714.GB1964@sbrim-w2k01>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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, Apr 30, 2004 at 04:47:17AM -0400, Scott W Brim wrote:
> > 
> > I don't quite see what the difference here is to .edu for example. Isn't
> > this indeed very similar to how the .edu provides a "clearly
> > recognisable" label for educational services and content?
> 
> .edu was an administrative distinction.  (So was .net, originally.)  The
> intent here is clearly to distinguish the *use* of the name, not the
> administration.

The .edu is a (perpetuated) anachronism like .com.  You could ask the US 
universities to rename to .ac.us tree - good luck! :)   

It's interesting how some countries sub-delegate (like the UK, to .co.uk,
.ac.uk, .gov.uk, .ltd.uk, .org.uk, etc) and others do not.   Doing so 
allows some more headroom in namespace, but not all such sub-delegations
are exactly policed for validity.

tim

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


From exim@www1.ietf.org  Fri Apr 30 10:48:28 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05574
	for <ietf-archive@odin.ietf.org>; Fri, 30 Apr 2004 10:48:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJZ9a-0001LN-Ik
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 10:38:14 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3UEcEcS005028
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 10:38:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJYzi-0008BG-Ih; Fri, 30 Apr 2004 10:28:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJYp4-0005rj-V7
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 10:17: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 KAA03829
	for <ietf@ietf.org>; Fri, 30 Apr 2004 10:16: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 1BJYp1-0004ql-RH
	for ietf@ietf.org; Fri, 30 Apr 2004 10:16:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJYo3-0004nn-00
	for ietf@ietf.org; Fri, 30 Apr 2004 10:15:59 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJYn5-0004l6-00
	for ietf@ietf.org; Fri, 30 Apr 2004 10:14:59 -0400
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id i3UEEv7s012163
	for <ietf@ietf.org>; Fri, 30 Apr 2004 15:14:58 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id PAA03334
	for <ietf@ietf.org>; Fri, 30 Apr 2004 15:14:56 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i3UEEuw26711
	for ietf@ietf.org; Fri, 30 Apr 2004 15:14:56 +0100
Date: Fri, 30 Apr 2004 15:14:56 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <20040430141456.GC26259@login.ecs.soton.ac.uk>
References: <20040428162010.E0FF67B46@berkshire.research.att.com> <40910D37.1030205@nokia.com> <20040430084714.GB1964@sbrim-w2k01>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040430084714.GB1964@sbrim-w2k01>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

On Fri, Apr 30, 2004 at 04:47:17AM -0400, Scott W Brim wrote:
> > 
> > I don't quite see what the difference here is to .edu for example. Isn't
> > this indeed very similar to how the .edu provides a "clearly
> > recognisable" label for educational services and content?
> 
> .edu was an administrative distinction.  (So was .net, originally.)  The
> intent here is clearly to distinguish the *use* of the name, not the
> administration.

The .edu is a (perpetuated) anachronism like .com.  You could ask the US 
universities to rename to .ac.us tree - good luck! :)   

It's interesting how some countries sub-delegate (like the UK, to .co.uk,
.ac.uk, .gov.uk, .ltd.uk, .org.uk, etc) and others do not.   Doing so 
allows some more headroom in namespace, but not all such sub-delegations
are exactly policed for validity.

tim

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



From ietf-admin@ietf.org  Fri Apr 30 12:42: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 MAA13467
	for <ietf-archive@ietf.org>; Fri, 30 Apr 2004 12:42: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 1BJb5i-00074M-B9
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 12:42:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJb4l-0006zV-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 12:41:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJb41-0006vh-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 12:40:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJarq-0005eJ-0U; Fri, 30 Apr 2004 12:28:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJamH-0004Z7-Cp
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 12:22: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 MAA12428
	for <ietf@ietf.org>; Fri, 30 Apr 2004 12:22: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 1BJamF-0005aJ-BQ
	for ietf@ietf.org; Fri, 30 Apr 2004 12:22:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJalN-0005XT-00
	for ietf@ietf.org; Fri, 30 Apr 2004 12:21:21 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJakz-0005U1-00
	for ietf@ietf.org; Fri, 30 Apr 2004 12:20:57 -0400
Received: from f01v-39-60.d0.club-internet.fr ([212.195.250.60] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BJakn-0002Ij-Cx; Fri, 30 Apr 2004 09:20:45 -0700
Message-Id: <6.0.1.1.2.20040430183140.05d5ceb0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
X-Priority: 1 (Highest)
Date: Fri, 30 Apr 2004 18:36:30 +0200
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Cc: robert.shaw@iu.int.cnri.reston.va.us
In-Reply-To: <ACBFB13DAC66EE23B2F5520F@scan.jck.com>
References: <ACBFB13DAC66EE23B2F5520F@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
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,X_PRIORITY_HIGH 
	autolearn=no version=2.60

At 03:42 30/04/04, John C Klensin wrote:
>http://www.icann.org/tlds/stld-apps-19mar04/stld-public-comments.htm

Dear John,
it seems that (one of the) most important entry (the letter from ITU 
regarding the .tel/.mobi requests) cannot be accessed. 
http://forum.icann.org/lists/stld-rfp-general/msg00043.html
This seems to be a singular impeachment to a transparent debate on the matter.
Due to the delay I suggest that ITU sends IETF a copy while you might as a 
BoD Member ask staff to urgently correct that situation.
jfc






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


From exim@www1.ietf.org  Fri Apr 30 12:46:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13701
	for <ietf-archive@odin.ietf.org>; Fri, 30 Apr 2004 12:46:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJb41-0000bY-VS
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 12:40:38 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3UGebIN002298
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 12:40:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJarq-0005eJ-0U; Fri, 30 Apr 2004 12:28:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJamH-0004Z7-Cp
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 12:22: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 MAA12428
	for <ietf@ietf.org>; Fri, 30 Apr 2004 12:22: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 1BJamF-0005aJ-BQ
	for ietf@ietf.org; Fri, 30 Apr 2004 12:22:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJalN-0005XT-00
	for ietf@ietf.org; Fri, 30 Apr 2004 12:21:21 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJakz-0005U1-00
	for ietf@ietf.org; Fri, 30 Apr 2004 12:20:57 -0400
Received: from f01v-39-60.d0.club-internet.fr ([212.195.250.60] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BJakn-0002Ij-Cx; Fri, 30 Apr 2004 09:20:45 -0700
Message-Id: <6.0.1.1.2.20040430183140.05d5ceb0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
X-Priority: 1 (Highest)
Date: Fri, 30 Apr 2004 18:36:30 +0200
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Cc: robert.shaw@iu.int.cnri.reston.va.us
In-Reply-To: <ACBFB13DAC66EE23B2F5520F@scan.jck.com>
References: <ACBFB13DAC66EE23B2F5520F@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,X_PRIORITY_HIGH 
	autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

At 03:42 30/04/04, John C Klensin wrote:
>http://www.icann.org/tlds/stld-apps-19mar04/stld-public-comments.htm

Dear John,
it seems that (one of the) most important entry (the letter from ITU 
regarding the .tel/.mobi requests) cannot be accessed. 
http://forum.icann.org/lists/stld-rfp-general/msg00043.html
This seems to be a singular impeachment to a transparent debate on the matter.
Due to the delay I suggest that ITU sends IETF a copy while you might as a 
BoD Member ask staff to urgently correct that situation.
jfc






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



From ietf-admin@ietf.org  Fri Apr 30 14:23:18 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19821
	for <ietf-archive@ietf.org>; Fri, 30 Apr 2004 14:23: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 1BJcfQ-0006xz-F4
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 14:23:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJceV-0006tJ-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 14:22:25 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJcdw-0006pP-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 14:21:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJcSY-0007lx-Es; Fri, 30 Apr 2004 14:10:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJcPn-00078P-UT
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 14: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 OAA18836
	for <ietf@ietf.org>; Fri, 30 Apr 2004 14: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 1BJcPl-0005bZ-7U
	for ietf@ietf.org; Fri, 30 Apr 2004 14:07:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJcOr-0005Z5-00
	for ietf@ietf.org; Fri, 30 Apr 2004 14:06:15 -0400
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJcOE-0005WO-00
	for ietf@ietf.org; Fri, 30 Apr 2004 14:05:34 -0400
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1BJcOB-0001D3-00; Fri, 30 Apr 2004 14:05:31 -0400
Received: from [68.246.207.24] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1BJcO2-0005T1-00; Fri, 30 Apr 2004 14:05:24 -0400
Message-ID: <40929554.20202@solidmatrix.com>
Date: Fri, 30 Apr 2004 14:05:08 -0400
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: jfcm <info@utel.net>
CC: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
References: <ACBFB13DAC66EE23B2F5520F@scan.jck.com> <6.0.1.1.2.20040430183140.05d5ceb0@mail.utel.net>
In-Reply-To: <6.0.1.1.2.20040430183140.05d5ceb0@mail.utel.net>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/mixed;
 boundary="------------070305030709050008070103"
X-Provags-ID: perfora.net abuse@perfora.net auth:7051a7fa85b96745770cd89fa6d27f10
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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 is a multi-part message in MIME format.
--------------070305030709050008070103
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

jfcm wrote:
> At 03:42 30/04/04, John C Klensin wrote:
> 
>> http://www.icann.org/tlds/stld-apps-19mar04/stld-public-comments.htm
> 
> 
> Dear John,
> it seems that (one of the) most important entry (the letter from ITU 
> regarding the .tel/.mobi requests) cannot be accessed. 
> http://forum.icann.org/lists/stld-rfp-general/msg00043.html
> This seems to be a singular impeachment to a transparent debate on the 
> matter.
> Due to the delay I suggest that ITU sends IETF a copy while you might as 
> a BoD Member ask staff to urgently correct that situation.
> jfc
> 

It seems to be working fine by me with a little tweaking. If you 
download the file in the message 
(http://forum.icann.org/lists/stld-rfp-general/bin00004.bin), and rename 
it to .pdf (under Windows), it opens just fine.

I attached a copy of it to this message.

Yakov
--
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"Some lies are easier to believe than the truth" (Dune)

--------------070305030709050008070103
Content-Type: *.pdf;
 name="bin00004.pdf"
Content-Disposition: inline;
 filename="bin00004.pdf"
Content-Transfer-Encoding: base64

JVBERi0xLjINJeLjz9MNCjcgMCBvYmoNPDwgDS9MaW5lYXJpemVkIDEgDS9PIDkgDS9IIFsg
MTE2MCAyMDIgXSANL0wgMTkyMjAgDS9FIDE2NDQ5IA0vTiAyIA0vVCAxODk2MyANPj4gDWVu
ZG9iag0gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICB4cmVmDTcgMzUgDTAwMDAwMDAwMTYgMDAwMDAgbg0KMDAwMDAwMTA0NCAw
MDAwMCBuDQowMDAwMDAxMzYyIDAwMDAwIG4NCjAwMDAwMDE2MDggMDAwMDAgbg0KMDAwMDAw
MTc3NSAwMDAwMCBuDQowMDAwMDAxOTE5IDAwMDAwIG4NCjAwMDAwMDIwNjMgMDAwMDAgbg0K
MDAwMDAwMjIwNyAwMDAwMCBuDQowMDAwMDAyMzY1IDAwMDAwIG4NCjAwMDAwMDI1NDggMDAw
MDAgbg0KMDAwMDAwMjczNSAwMDAwMCBuDQowMDAwMDAzMzA1IDAwMDAwIG4NCjAwMDAwMDM0
ODUgMDAwMDAgbg0KMDAwMDAwMzk1NSAwMDAwMCBuDQowMDAwMDAzOTc3IDAwMDAwIG4NCjAw
MDAwMDU2NDIgMDAwMDAgbg0KMDAwMDAwNTkyOSAwMDAwMCBuDQowMDAwMDA2MDA0IDAwMDAw
IG4NCjAwMDAwMDYxMTQgMDAwMDAgbg0KMDAwMDAwNjEzNiAwMDAwMCBuDQowMDAwMDA3NDYz
IDAwMDAwIG4NCjAwMDAwMDc0ODUgMDAwMDAgbg0KMDAwMDAwODg4NyAwMDAwMCBuDQowMDAw
MDA4OTA5IDAwMDAwIG4NCjAwMDAwMTAyMjAgMDAwMDAgbg0KMDAwMDAxMDI0MSAwMDAwMCBu
DQowMDAwMDExMzE0IDAwMDAwIG4NCjAwMDAwMTEzMzYgMDAwMDAgbg0KMDAwMDAxMjYwMCAw
MDAwMCBuDQowMDAwMDEyNjIyIDAwMDAwIG4NCjAwMDAwMTQ0MzYgMDAwMDAgbg0KMDAwMDAx
NDQ1OCAwMDAwMCBuDQowMDAwMDE2MjAyIDAwMDAwIG4NCjAwMDAwMDExNjAgMDAwMDAgbg0K
MDAwMDAwMTM0MiAwMDAwMCBuDQp0cmFpbGVyDTw8DS9TaXplIDQyDS9JbmZvIDUgMCBSIA0v
Um9vdCA4IDAgUiANL1ByZXYgMTg5NTQgDS9JRFs8MjllYTRiOTY3ZmI3OWFmOTIyZmU3YmI5
Mjc0MjA1Yzg+PDI5ZWE0Yjk2N2ZiNzlhZjkyMmZlN2JiOTI3NDIwNWM4Pl0NPj4Nc3RhcnR4
cmVmDTANJSVFT0YNICAgICANOCAwIG9iag08PCANL1R5cGUgL0NhdGFsb2cgDS9QYWdlcyA2
IDAgUiANL09wZW5BY3Rpb24gWyA5IDAgUiAvWFlaIG51bGwgbnVsbCBudWxsIF0gDS9QYWdl
TW9kZSAvVXNlTm9uZSANPj4gDWVuZG9iag00MCAwIG9iag08PCAvUyA0NiAvRmlsdGVyIC9G
bGF0ZURlY29kZSAvTGVuZ3RoIDQxIDAgUiA+PiANc3RyZWFtDQpIiWJgYGABog4GVgYGTkcG
PgYEALGBogwcNxiOiDCAMRQIALE8FDMwiDJwyyh52LZv+KbkKrDMZVHNgwaZG06NGyIZTDIY
rgUwOzWwyDAY5zB8EGBed/AESAdAgAEA8nAUDg1lbmRzdHJlYW0NZW5kb2JqDTQxIDAgb2Jq
DTk4IA1lbmRvYmoNOSAwIG9iag08PCANL1R5cGUgL1BhZ2UgDS9QYXJlbnQgNiAwIFIgDS9S
ZXNvdXJjZXMgMTQgMCBSIA0vQ29udGVudHMgWyAyMSAwIFIgMjYgMCBSIDI4IDAgUiAzMCAw
IFIgMzIgMCBSIDM0IDAgUiAzNiAwIFIgMzggMCBSIF0gDS9Bbm5vdHMgWyAxMCAwIFIgMTEg
MCBSIDEyIDAgUiAxMyAwIFIgXSANL01lZGlhQm94IFsgMCAwIDU5NSA4NDIgXSANL0Nyb3BC
b3ggWyAwIDAgNTk1IDg0MiBdIA0vUm90YXRlIDAgDT4+IA1lbmRvYmoNMTAgMCBvYmoNPDwg
DS9BIDw8IC9TIC9VUkkgL1VSSSAobWFpbHRvOnNwdW1haWxAaXR1LmludCk+PiANL1R5cGUg
L0Fubm90IA0vU3VidHlwZSAvTGluayANL1JlY3QgWyA3MiA2MDcgMTUxIDYyMSBdIA0vQyBb
IDAgMCAwIF0gDS9Cb3JkZXIgWyAwIDAgMCBdIA0vSCAvSSANPj4gDWVuZG9iag0xMSAwIG9i
ag08PCANL0Rlc3QgWyA5IDAgUiAvRml0QiBdIA0vVHlwZSAvQW5ub3QgDS9TdWJ0eXBlIC9M
aW5rIA0vUmVjdCBbIDI0NSA0MjMgMjUxIDQzMyBdIA0vQyBbIDAgMCAwIF0gDS9Cb3JkZXIg
WyAwIDAgMCBdIA0vSCAvSSANPj4gDWVuZG9iag0xMiAwIG9iag08PCANL0Rlc3QgWyA5IDAg
UiAvRml0QiBdIA0vVHlwZSAvQW5ub3QgDS9TdWJ0eXBlIC9MaW5rIA0vUmVjdCBbIDQxMCAx
NzQgNDE3IDE4NCBdIA0vQyBbIDAgMCAwIF0gDS9Cb3JkZXIgWyAwIDAgMCBdIA0vSCAvSSAN
Pj4gDWVuZG9iag0xMyAwIG9iag08PCANL0Rlc3QgWyA5IDAgUiAvRml0QiBdIA0vVHlwZSAv
QW5ub3QgDS9TdWJ0eXBlIC9MaW5rIA0vUmVjdCBbIDQxMCAxNjEgNDE3IDE3MSBdIA0vQyBb
IDAgMCAwIF0gDS9Cb3JkZXIgWyAwIDAgMCBdIA0vSCAvSSANPj4gDWVuZG9iag0xNCAwIG9i
ag08PCANL1Byb2NTZXQgWyAvUERGIC9UZXh0IF0gDS9Gb250IDw8IC9GMiAyNCAwIFIgL1RU
MiAxNyAwIFIgL1RUNCAxOSAwIFIgPj4gDS9FeHRHU3RhdGUgPDwgL0dTMSAzOSAwIFIgPj4g
DS9Db2xvclNwYWNlIDw8IC9DczUgMTggMCBSID4+IA0+PiANZW5kb2JqDTE1IDAgb2JqDTw8
IA0vVHlwZSAvRm9udERlc2NyaXB0b3IgDS9Bc2NlbnQgOTYyIA0vQ2FwSGVpZ2h0IDAgDS9E
ZXNjZW50IC0yMzUgDS9GbGFncyAzMiANL0ZvbnRCQm94IFsgLTE2NyAtMjM2IDEwNjUgOTYz
IF0gDS9Gb250TmFtZSAvRnV0dXJhTHRCVCANL0l0YWxpY0FuZ2xlIDAgDS9TdGVtViAwIA0+
PiANZW5kb2JqDTE2IDAgb2JqDTw8IA0vVHlwZSAvRm9udERlc2NyaXB0b3IgDS9Bc2NlbnQg
ODkxIA0vQ2FwSGVpZ2h0IDAgDS9EZXNjZW50IC0yMTYgDS9GbGFncyAzNCANL0ZvbnRCQm94
IFsgLTU2OCAtMzA3IDIwMjggMTAwNyBdIA0vRm9udE5hbWUgL1RpbWVzTmV3Um9tYW4gDS9J
dGFsaWNBbmdsZSAwIA0vU3RlbVYgMCANPj4gDWVuZG9iag0xNyAwIG9iag08PCANL1R5cGUg
L0ZvbnQgDS9TdWJ0eXBlIC9UcnVlVHlwZSANL0ZpcnN0Q2hhciAzMiANL0xhc3RDaGFyIDE0
OCANL1dpZHRocyBbIDI1MCAwIDAgMCAwIDAgNzc4IDE4MCAzMzMgMzMzIDAgNTY0IDI1MCAz
MzMgMjUwIDI3OCA1MDAgNTAwIDUwMCA1MDAgDTUwMCA1MDAgNTAwIDUwMCA1MDAgNTAwIDI3
OCAwIDAgNTY0IDAgNDQ0IDkyMSA3MjIgNjY3IDY2NyA3MjIgNjExIA01NTYgNzIyIDcyMiAz
MzMgMCAwIDYxMSA4ODkgNzIyIDcyMiA1NTYgMCA2NjcgNTU2IDYxMSA3MjIgMCA5NDQgDTAg
NzIyIDYxMSAzMzMgMCAzMzMgMCAwIDAgNDQ0IDUwMCA0NDQgNTAwIDQ0NCAzMzMgNTAwIDUw
MCAyNzggMjc4IA01MDAgMjc4IDc3OCA1MDAgNTAwIDUwMCAwIDMzMyAzODkgMjc4IDUwMCA1
MDAgNzIyIDUwMCA1MDAgNDQ0IDAgDTAgMCAwIDAgMCAwIDAgMCAwIDEwMDAgMCAwIDAgMCAw
IDAgMCAwIDAgMCAwIDAgMzMzIDQ0NCA0NDQgXSANL0VuY29kaW5nIC9XaW5BbnNpRW5jb2Rp
bmcgDS9CYXNlRm9udCAvVGltZXNOZXdSb21hbiANL0ZvbnREZXNjcmlwdG9yIDE2IDAgUiAN
Pj4gDWVuZG9iag0xOCAwIG9iag1bIA0vQ2FsUkdCIDw8IC9XaGl0ZVBvaW50IFsgMC45NTA1
IDEgMS4wODkgXSAvR2FtbWEgWyAyLjIyMjIxIDIuMjIyMjEgMi4yMjIyMSBdIA0vTWF0cml4
IFsgMC40MTI0IDAuMjEyNiAwLjAxOTMgMC4zNTc2IDAuNzE1MTkgMC4xMTkyIDAuMTgwNSAw
LjA3MjIgMC45NTA1IF0gPj4gDQ1dDWVuZG9iag0xOSAwIG9iag08PCANL1R5cGUgL0ZvbnQg
DS9TdWJ0eXBlIC9UcnVlVHlwZSANL0ZpcnN0Q2hhciAzMiANL0xhc3RDaGFyIDEyMiANL1dp
ZHRocyBbIDI4OCAwIDAgMCAwIDAgMCAwIDAgMCAwIDgzMyAwIDM0NyAyODggMCA1NzYgNTc2
IDU3NiA1NzYgNTc2IDU3NiA1NzYgDTU3NiAwIDAgMzEwIDAgMCAwIDAgMCAxMDAwIDU5NyAw
IDcxNSAwIDUxMyA1MDEgODE3IDY5NyAyNDMgMCAwIDQxMyANODM2IDc0NSA4NzUgNTAwIDAg
NTI4IDQ5OCA0OTcgNjkyIDU1MSAwIDAgMCAwIDAgMCAwIDAgMCAwIDU0MSA1NDEgDTQ1NiA1
NDEgNDk3IDI1OSA1NDEgNTIxIDIzMCAyMzAgMCAyMzAgNzg5IDUyMSA1NTggNTQxIDAgMzE1
IDM4MiANMjQ4IDUyNyA0MjcgNjQ4IDM5NCAwIDM4MSBdIA0vRW5jb2RpbmcgL1dpbkFuc2lF
bmNvZGluZyANL0Jhc2VGb250IC9GdXR1cmFMdEJUIA0vRm9udERlc2NyaXB0b3IgMTUgMCBS
IA0+PiANZW5kb2JqDTIwIDAgb2JqDTE1ODcgDWVuZG9iag0yMSAwIG9iag08PCAvRmlsdGVy
IC9GbGF0ZURlY29kZSAvTGVuZ3RoIDIwIDAgUiA+PiANc3RyZWFtDQpIiWxW23IbRRAtXvUV
87gLpfXcZzZPJEYYU4kDZAMPFA8pR05EWQrYCaH4ek5fRlpJKVdZ25qevpxzulfPpsXFNHnj
zHS3cN5Y/OGj2KGa6spgow1m2i4uLh+TuX3kc2sebxcXV6+cefe4sGa6pX+fF53ppz8pWpRo
I7uOxpdhzCb6wVaJtbSDtT7zRTyVSrd/737ql+MQuvveDqV70y8rjFsYrlubt2KuewfzsV+W
ISKdC/juRl0/0rdjt+HrH3a9c/h87BO+MzjyPsOe1vfrv8jfd+8/7NY4QAwKtUyFHr6Jzni0
H6xJzjjH547Pa24B/qUAuUNLzlhrzScq3GlmLcPcvselHCPVv1pu30jSzf0ThPRD4pDZdhv1
1xjbHuD41v3m/tuT84Gs2m12LU3/x/TjYjUtnNmYBVpM3qQ8gMEUy+ANosVqHtaLu8Wz6YSR
4AZ/xEhtjCghl6ii+wFd5Q41O2eu1rv1P1wb6veWwQnciaBH4HB7sbvrfWMxdQxYJceR3K4e
pPjwxPQjRdijHkyh+meBD6i/oyCx07saeWuup9fmanWz+pUSdyuCKc9K+iy47z8S/g/UF7GV
iK0KWD/1UcBt3+/0QPC1ZgmszPSdABX20q2K1CvEH5nLitr+oyIixErcP9B3BarG1UBlk8Z3
/dKjzLekP2ubBIM8XemVeAaPNTlBcbgUj0QpVR7m2BK9PKn0wLOMUQ5ZyD6dWKjn74WDoiF5
iAu+qM0ghWfl/GZ2pJ2L78+WhNzx6FIjd19pvJ/pxsEx2BNHjBb+sEVOd4Z3rXR58iAZHaRx
GH2rXhdQd01XXZUk1YSEZXXsOthcEnXb3UyrX26eTtcvb54+55SniVzFhz/JRDen4yxujF9K
kws7r56vLl++ePH65vqSk30xVbT2vCm6/fo4VXTlPI+Xdlpsx9VYE4dq3WjEVNAASDhctfQk
qoWWWLU0zg9vMKgj5Mlqf9WTLGnLZqzeIOOG/ftRvNjYyPNHHY0h2jHQfLgxZxqRL8or2TwA
tZCpvswLCpOu6tqrQbyqrQevpbjdfQ1NJeytjCjYbDGa7Yl9v0jQGXETM7TOtgcCsNMgx3Eo
ZEaCh2zgGwNRQsZIBcKUq9ExhjGwEeQiVpocJhoTsjMHjlXyNjuhjjrzT75FSmGonAVbmcxE
D4ciUpFAcchyThNG9SMCmSPfzu32SH1T+7Z5E66RgSM7s7t2j1z+KHaQDjHnbDoqtkir1NPI
u2NfautxD5BisLcVo72/ozyHeIpv1FpDOa4G3NTIxfqq1HF1rRdQ6+usV18kPVrOas+lAL0k
WxhcvAYQYnuwndIPGxnySIHIrExaroKHlSHKWdCzXH6O2o2zXH72tDTIdqy07OhrslkKRRgi
mxkuqWgyx5QWMCTtuJGpS16FgE3BW8Yp8z5wcSIsspXMqgo7nYQzeJKwMypbXshHPIEf+SKn
F7RRDkElEiG7MJmQkJ5HuV5bu0HKHw9wjAJHVrSI3ByUXNjkDjSlW4BL5AJrmR9gT2gWq4af
syZm0EqOSBbehVHihmmfm7iAoPQswYoW4oeqppc6XTum4LCjmpmtkmdm1EqKNhl1AA52jfNc
SSksexBEUq3OqBQdbNfOyzw9bJJQKy6LQAPpRkxfD53BdJnNGOfBBRRCLYSm2MCwHdk0gFkU
W3WYKTrkK3xj01H4vZwx1vwyTW05FNpEKbZ9qC/AqJtJxR1VHrg2P5WtBlPEkWUT7LUoPZEt
OAuAVItIO2cZpdJw47FHVNEe5p2AsDpoJ2o5w02UCXeZ4yyvaFETqNWpUAYlrTTFEakq9bWC
WKtaNsMBMcWgNdkgSnP42iHQVbR19aYTNnxjq5HHTBYFFMwWKVs3dRAIrErpRAkkFsdrvIzc
xPbEln1AHNSGhMMP+9pax26k+DUq5Lo8qtfyHb9CSrVtd0ae+NqWh3RX2kveZdkA+h5zLLXi
WyWyyWTY9osu17ZHQ9vyR3tyP4S+tj2vPxmsDGHj/2xKTrFzct9pb77qCtF0efCzFYFqeG3m
ttXldwQvGuqlUu1oLbVOrTSeGzCUG8BkhW0U3PIMxto2PlCm9VT90BjLx5wQDuBszwHlqrLw
/xdgAEa6RKsNZW5kc3RyZWFtDWVuZG9iag0yMiAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURl
Y29kZSAvTGVuZ3RoIDIxMyA+PiANc3RyZWFtDQpIiVSQMY+DMAyFd36Fx1Y3BLrcDYil7UkM
156OtntIDIpEnMiEgX9/CaWtOsSS/fLpPVvs60NNJoD4ZacaDNAZ0oyjm1ghtNgbgmIH2qiw
dktVVnoQEW7mMaCtqXNQlpn4i+IYeIZNM9vWDR/5FsSZNbKhHjaX4nqLg2byfkCLFCCHqgKN
XSb2P9KfpMUor+gyL1ZDp3H0UiFL6hHKvKjuBUm/aw+i7e7t62v5/XX8rLJIPLQEp02e3mpi
jrGWdZdEKYMhfF7EO58s08v+BRgAU5dpcwplbmRzdHJlYW0NZW5kb2JqDTIzIDAgb2JqDTw8
IA0vVHlwZSAvRW5jb2RpbmcgDS9EaWZmZXJlbmNlcyBbIDEgL2Fycm93aG9yaXpleCBdIA0+
PiANZW5kb2JqDTI0IDAgb2JqDTw8IA0vVHlwZSAvRm9udCANL1N1YnR5cGUgL1R5cGUxIA0v
RW5jb2RpbmcgMjMgMCBSIA0vQmFzZUZvbnQgL1N5bWJvbCANL1RvVW5pY29kZSAyMiAwIFIg
DT4+IA1lbmRvYmoNMjUgMCBvYmoNMTI0OSANZW5kb2JqDTI2IDAgb2JqDTw8IC9GaWx0ZXIg
L0ZsYXRlRGVjb2RlIC9MZW5ndGggMjUgMCBSID4+IA1zdHJlYW0NCkiJbFc7luQ4DMvnFBNv
4Kc/pQtt1HX/dEiCkGVXZ42Wih8QpOg/Pbdr/pW5rlX+/vwxmBSvdOWh+P//9F9DcbHzj4J+
zel4TL/fr14c199+/4v5Vc7jfrn5ZFaAC34+aX40xfkqzfG4cnG8RuCK8EpAoB6njByZjGnB
SL9Ss1xOqLfH8lgUywhsvkWuxnOx83mdcKbIPK7PbBkAGywRuTob03EugY0JvZ7pLbWnOcPb
G65rMEgtzMm4hOaaXedhQmYRyiNRY6IlC0ukGM+fF9ZftOJllXwBehUlBetNYD9Fbm35r8GI
4p4vQLjv1YIWZGS4W5WQkUFxXzdengrKYdFnWodGRgEVyUFzAWgowUP3SDNpEk8qfigWv0i9
xjcr36QJLLugDQ9QUlnADsYLw2wuTXVdGeaYZ2QZ5yRN06zF0wLlpMFldLO04SZxc9w3C1qA
Bl9tRoHKWa8OLeVoWq2uK5nEaPUPXl5aMLmUro0kJpT4S6+VZkVePZhW6O3Wgh7F5nP3Is9z
AAt+rmit0p2bKZGs4mnNMIL7MnyKNPRCQR9NANC4+6gm5LaQTI2qsE/qYJP7r2sUvV3ll9Rf
xOjlDkWAxhqKoKPh/YnqV4hW27lElNODjPymXZ41DsUnRQunmmxD8pscN7VuJn0E55tpGU+m
/fxkdvXbmBgeIaNdTytz9TE8k3X9x4PWRA028j4TJaZRGhmLTa6GrbnWZBTdJbmEdbqF8w5h
4MmQl+XJ4guUMy9CfxK244kngH2kUScEWikIFaLhUIC/LZYVzJ9JgwbtTIhR4/s8IfrWwpsz
mivGlT5ZbOuE6sBdj/Aqh58Xe7WIrkfyPTTV0RlKTkyFArKE3gppjSkSbTU4a31qqLkS1rcS
ulAm4SkCy0G7YjmfZsUTsks8N88R1oMTf1EEfTignRNiQOVyNLROL3/tOp0jzdlD092Hyw0h
LsXBmviaMHuIK3JR8+OX8F6hi7fHFDImCGWEcDvkeYfKUMLVjjSwDx67Xo5JvPMWvPrCSfug
JV7iNVjwzwvvEbT1EZDy4e1YcnrLF8Q3jjmvJS18xtM8pNuwvE2hr1fR3sFD9o22vA04lVqF
nFJwrr7bsag1f3usDSIUfyYtkfbAfE54f8TEfNHibXq2xueXVknYNedDgntuRLKLa0XrnCuB
7U04rhdM1clCRID09lW3dwIFm62wchXhcMqpu1qO+clw5vWIlnAyms5cxzysfY2JJzdOH4Sr
FYkxd2L8xAvK7aNhbO2xMx5jLKY/y9mF24Bwp4tyxzKUwAbvjxTLxON2j8eU1jaOIdmZbaX1
PSTz6S2mzR3dM1X/yBEXizf75wl/HGq0nX2Sp/9+7K+S6X02aD8vZ1s3SPgvKTZWvoWoju4V
gZuzIePig+ib5QpyS0ziHO51t/Bp10KatWFB4MJQBXi3amJrZkpvtmNKCGrLGfIlhBd7lGKl
siu0xk9AdZfL8Q1XBwYuH5Ja8eEk8SLiQT72n4nwC/cBLIOyyGb1vV24Hjgte4Ur6cIWjg/C
5WWIj8XpiQzKIiPxkYPnjM+au8y+RR8aOCThmvECCfj4wJk2ZqFGLEtMHWCrMci8g0FjHrjy
2/VLgU9kJTgvOy53ZjacdSowkemhPHho64irSVRfsXV2G7x8JvnzT4ABAKbsLz4NZW5kc3Ry
ZWFtDWVuZG9iag0yNyAwIG9iag0xMzI0IA1lbmRvYmoNMjggMCBvYmoNPDwgL0ZpbHRlciAv
RmxhdGVEZWNvZGUgL0xlbmd0aCAyNyAwIFIgPj4gDXN0cmVhbQ0KSIlkV0u2LCkInL9VvHEP
8igq4IZ61Hf/0wYCTKvurOKkYvCP+vPvP3/W6s/8K3s+g//+fML/AjbH6xkUuD2LDbOdMjj3
o/5ZnqmJybE+DKzPIsP7kTA35dn0V1t7hBI77G7UIT9skNI4xye9vhgbzXsDdmjmO0HTnq93
GTzopiV1PGnz0zm9GhRewrxh4+9R6JRRuILiURs7HJvDLf58YX+hPdviNGcSmO63GO2Zrrll
MZoZF3XiEu+8fBdlmIyPnV6z6FpQ/LSkt3bO3lpap4ef5gZbhuwsd+fjcMZLPPJlw/ZDeCWz
tYIZS7m+3GlhRR4MGpLKn0H7IULuPbAHVtLt+sw3kA9L++HrGe3HkIFRRTcjm7oyuAiEqHjS
4aIXpWr5SBH83cpHQvopy+y7xn9nO4qW6vm83orb8FiJsucU2JOrq+4jxDqeD/aZW4OevNfx
OyRXrDwLbxzvGKeBkwPY513RmO4dyxssbw1LcDqPYFkBqCZuXhCXt1OjfHjexbarN3oE34pv
VW16NBZXa+4oxpnXreQZlS1viwsuOVzom119M6MT0c+OOxpnJVvrK2dnxwJa2zkZazudie82
jE4Nx8S+mAXv1OHhmTU5xoTBhnSM6ANB+zrmyKXRAN8RYRXQAo4+z5E1vE0cwdnvqfCLruK1
kZVo1iTO59MKY4ikYU+k4V5UG6hh1pqjdDlyu41IWNA9ljsG1gvOxLCCr870kOxe/bGrveCF
zRJC/aOirJScmM7MESOkOrIirPSiP3oSx2zxDkh7Go5IDUfDfl4WYsoIogw4ZnUft8ttwzGg
asUIKoQlMyiRaWHOihJMZpBy3B+6j3e0w2UuJlruobQmlUE7581nXHE85uRpaEY+zVO0qpFY
iARSykihjjeSOegQeYu0P26DLiPXEGnN1y1TMejOcB+YZOOp1iUMtrNGTs69IHr0IuaclUQX
fB7Jrkcn2208RmltZeAJg8OWKI7TujYsbWzUXMCjhynNGTOwm2fVdditowofKiETCXklxngg
QHIgALSSAQt7/Je/v4KB3etnUQdm13Nl79Sz9EFKL1nzUt6vP7v6Er7WOLZI0HWUML2Pe0Sl
oJBySs4psCwHnS791aNJ3AvEuSOBsH3nMzPc0borZcoH9hvDqyl+QaGcJWe29oftJDKLd4fC
4ix8wk4+WSWOiO0qju2he4XfiF3sgi4juoDPcAs7rxTs9bm2RMJWSyat3SrVXxvVF3NeOYEm
OqrUjuunuAyux/osLHyTGbnvi+vBq7hrDeYQq0neQhGf+xupD7I0nru2CPv2FEg/dYuZYYny
+Vc937FAdw/gT/q4yKuYZbqylb6qwQuGoMNm+PLzhVGusaFmDYGGJcTomi6x/7QmyIoiifhG
tcXllcKoE5TEyppIeqZjQa9tSNPaQw17gav2G7bnUTot90h7MfbGge6tcGEs47OGOka7UuHv
XvmKXsNeUnr4YmPmkq1gcfCLfS+9dCKhF1vsiiO8wZ5LlLYNGdcTd6zBpZ9s18ntwHfK6W2p
6BBeZ5DcOguzftZICo0zsx8IYrQ0zldJeNUwfFkhyH++MPachiakFAiXIMwdN/erNnz+4x+e
Y4ECW0c+yy2hFpit+3/eUWsTvVGaCDrLIWI4IR1GzYEhhbNxZ51P+QbhM1ttRMX3EoO/muUr
cFBrtRA7XVRGFLVAMH5QwTx8qeZMGlFNhsvRhFoiPFWtlKhPpuePxhGlFmDhV1KbxgiNyqVZ
CBpVw/T/AgwAaK0sJg1lbmRzdHJlYW0NZW5kb2JqDTI5IDAgb2JqDTEyMzMgDWVuZG9iag0z
MCAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAvTGVuZ3RoIDI5IDAgUiA+PiANc3Ry
ZWFtDQpIiXRXy25sKQzc5yuynsURmIfhe0Z3VunNzP9LY7ts4JxOK1LSFYMpvwr6q/V61fHN
LV80vn++Wu9XFViuSQbHldTcL1j5Kl0gX6kK/uevryZLq+yYU//1emDZIltJIOsxCsfFitvV
4TFfWXG5ui3vRYnwzL6+NyMwxjW785OFPLqeAkZi4FHCn53LI10Bh2xn9ng4WbjcnJ1gpcO0
sXjrc0MSb3IosBj09E47PXIs9xT2e37e0jctudO5inddLd4CaigSsXPNV6GTTLbMbq5ZMyuh
0NjUeVy5+1msicmBQXXUTZWQyMizmWfktdh2qcOoXieFVaulZZxW1e5nS4C6e1q4P9YEw3qA
u8OzJ6RtpAyzfp+///v7qxGjeOVqXXuJyJoDWPxQvupRazFrMSXEZqTITuXprUPNCo94qFsy
JVu+li0+Lh4fWUArtyXBbPVXXKyPpBGG+S5NKWmtirkrbEyRNcVDqUhlYa7eR8m316w11k5A
YNX6UfsEpa9V2bRo8loENJ8A2au5Flz64bvVoIYJEFydmXZ4i7qXbpFZhQAzIHJavGPJCy3e
NbCW3F7J5rNOT4ww1dLWGLDarSbyh9EoOogsq1p0grqvJeSgGXnxivGXyVGYtzoo+ZoMiEWC
y6EDylvo1pg0ra9E2485L1Evl4UwdySlDK9Pt0ZW7HNdtS30tKVKzXiEKiXTAZQR46CnSxje
8GztssPs1i5IFtKg9Zcs+TgR4uxe42aNvpIqSTT3w90j+1qElWRzP/d2q3Hy8MT9BAabipqH
NHgRsAts9TjZRVGUBuzux3W2jA+/ePUa2gdtUD6DCxGUKDQ3piBoGFO95IMpOdLUSOW93UtM
FsXoKKw+t1ZRRj0xlxOaCavplY6xryZLlIx5TLndDsXPohkicTOHZhQKcw9RaDdccZm0EIFm
eoTPrJ+83OhaxTVG1g7qQRNDKFq+ZpagbBj5YvcPjyhQydDyuLXJdIVHVIBMSFTc0Q9kWqHi
jv0inAWXMHJMye9sOy0PXAXTZymzshuJvH2y5WekmPFsmjoS+2WQq/bHSJ7VbBeWLgcZwUNx
MSC9JJ9zuGJdNFJyHtq2M4Y2Tzwduqef6AwJPT7YSVPDVdIjBR3vilDN29VjV1T+1h+7lnB9
4d7GtVTQsqitY7HPSG99g3s1vEHafjEDLutz9ckFLzAyie32YnrdIe7MVI/5IteGxY6ufrxJ
Hv7fzydTxhMzxtXv0WXvd1ijsw5yT/Z2+2a9Av79AyNueDahexkba+y0XwCj3rCB9VrQFuBQ
RZzEIyqOvSe26R27qo57DEnrJ66Y/rkr86v94/ozNs+Fu5Dke5/Z+ybd3zvbw9Mj8F7v2cp3
BtvuON8jfGKjA4KYXffwstEutFY8Nrz589UbF5ubxeeT/eP6k40TdBeLYAvlZPply7tL4L3e
Axx3CtvueNxDfOIbRQ5xH6B4Ykgg09G20Mfd1rnFN5x71h54U2gYg3fMp799/p2Plz3Vj0MK
/XcFQ1PcJMRzvvEpPx7tkic/fQnG7egb7kcwS37yej2s+t3kK9uLbKvtJ/vH9Wesq+Xqetu/
1pId4X3Lu0vgvd7TF9943+yOl/25/uTzEzK6L6jXFvX4OvLY8uYyLgXg/wUYAFspLggNZW5k
c3RyZWFtDWVuZG9iag0zMSAwIG9iag05OTUgDWVuZG9iag0zMiAwIG9iag08PCAvRmlsdGVy
IC9GbGF0ZURlY29kZSAvTGVuZ3RoIDMxIDAgUiA+PiANc3RyZWFtDQpIiXRXy64jKwzcn6/I
ehaoMc/+ntHcVbK58//SGL8w0FE2Kbkwxpiy+6dADvnVyh1ueL1/CqSQB+7hroTZvEFjQ0h1
4v9+/Vyv8fv7e3oi28dwvUKrsrbBioHtvTNGEEPkjeJgDZy7w607crtHMDMqxAp7Jtj0iKWe
uF+hkq+YQ4ITGx/xveASCsztEGJMM5ro44z+EMK0QyKuPgOIia8Zwo2XDAo+7m7eRnyN37iN
fI1Nhq2Py0j36nriKw+cY4AnyGx0RlcVR2IfzAyj5Odgu1AoypJa4LxUim2iNyEpE05K6nQb
iKFL5JdPwur92BzphYO79eD5Ce5sjWVGRoF3LqU+grHQWxsh7vzDGcNJFl9V6mbxbc52uK8W
sw+OHMLYLI4c/f+HrDnxIyl4YIw8S5FTSb0JA1l5N4F8vYnfU9X7TaOeRygC6T+/nQwjnxhV
1Mqo3R0C8fWENQeIM28FWmhyJMOV+fyCcuSnWWXvURmNXhXjqCdmCJ3gtWDLgCQoyWs97ILN
vvNdgt+a8mg5/rgc55N/umOyQdaG/b5281e6D0WiYw83P0IhmAhuC06HjCefvPWoud/Ngs2+
0WcsHBx0esa8fjSTxtuL5i783ZlwJ67Bn+yL+RvbByKxtVlXH2NYZrYVh0OCk93Wi9vNdbnm
g918iUtwV3Y1JyWfT/bpzFc33Pwy56kejF/JPggRp0uEgYUTVyzCADRwTOFAnKrTFXCCg95J
SFWP9Bx1PSP0h1DOUAWrKiB2bxRRAicpiFmfBCxiBKMFTa1KF+/scPZy7xIiKUo8SJDEj+YC
LG7WAZYVhz9hG46s2tYwvHeHzd2+28qnANklNTTSWhxYmjUYdGBDwYfIkGdfRmsC17bR/ZV9
W0/rLCTbW/N0WzO8q+/bQLc427rRDUfw/Gsbh77YdaQ5+OAHIMkNzx1yc36aWtmns2udxTRz
OoMfdsbTvvMtFAnNz3ofm5jIvpAPTzpbGd6mxEfzN/Y2ci7fDhrSHqIbV5fi6MHP0TL4WHHI
HKSVrkOGw2JfZgiFIM+qa9evjGUW8tNHYuUvOu1IC9969AqPPrThVXFdU4ngtlJ9NO3pNDVr
mKpqegrVLVVQVipBIiQmDKD5WLBlFyT3JjuS+6hseol2VVG/8lpd8VJDrirmN0yprBl0ts+G
cW1p9FGImE9ZbtWYi/ZGp5UliDNcLTai10QDnR2lZspppRMxJpFhcqFiLmqTtQ6TnGXpiFXS
kqRxVBEkCBoZqRtIpCyL80uRjzizWrjlWVYlE5bVLTM03rUZ8GeFb4L0acl30Pllghbqrd9Q
o3P9E2AAsEAr3Q1lbmRzdHJlYW0NZW5kb2JqDTMzIDAgb2JqDTExODYgDWVuZG9iag0zNCAw
IG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAvTGVuZ3RoIDMzIDAgUiA+PiANc3RyZWFt
DQpIiZRXS48kNQy+96+oYzWos3lXam88hAQnJHpPiMNomF0N6p5Fw0jAv8ePOHHSLQGaw9TX
5fj77MSO65CSNSkvW7YmLpdDSn7Z0m5yIRBMjIQt42hKAVxMYeNsgie8eYXB15YJJ+Mj4SL+
dnzvjGN7jwsRR37vDPJnL3xVm6964o7EWw4mx4oDvo91PWDiS7gM8WZ8hx+/GH8Blri4gJJf
n/htovg2orkCzmYH/1up+nk1wC0PsGj2jovyxhheF4s55dUQFWK2Zq4GN0pVX5wmZxU3slnq
aE/RVQaH2bs2E2DM95bcSmDc7SslnBYdgJPNqe5nPC2X96gQzsvWGK503rbB5UwxKqjmDQaj
+QbnCouzmWyyJ32VgJJ8bSYtQzcUkwKC3boS1h0fnHdnN3haLu+rvuS1vmj0geyvt3yX8UaQ
jQoG49XxhdrlXG9SyrHc5erq2CRn46T4qP5r8SWopkLF7Ol4DpibC8OQda9pmNMDeGg9sWcL
Tx9UfmtlmVtFjEovYC2ftV4m7S16sJbg96y1cN9sfQq8USgBgyZxqqmJcF+bFgRGiz3Gd+l5
8GaANS2YOeivuFEs7tqxxLJzF22hF+6ikqkimariNzoFGo/7MOkp2MyV3Oq9hbOPPZwump6K
7AjwgeSLoFMDLrGnGSClWTZhiPtOKhz2q/GMFbowWoMHcUHXWGXQeKg5VFtsjQy4nC4X9iWQ
4+zVqpkVbvUyKZnsSXwlkP5dTXp7mSgmBQy7dSWUZqmdd2c3eFquuzckvTd4PIaJ74vmYqYY
FVTzBqlyO+HgXWHxNrNN9iSwMkh7rCY9QzPFLIFxt09yIRYdQDs8ebyib+hG+6pwEJiGeYOb
1YBHwhs9Vg0YXFW9gUPVpeFsB6pr7W1WxxY8PXFxqenJLvj3xyMx9TEMw4iqfYCTof69tAcr
FUctwIm5ZU6LYrn7ZB5Ji3TS9ux5GmymjnuBuJLpkWqcsNLBw1lTCdBlPUky1rOd5aMQZBQs
ahTaeKPkcuxzShnmmFZM7eIdsL7qfdGXbdBsgBJb1wYd5Ji0qTuqNin2/eoL9WJtZG7o/4nT
GvpctDOWaznz3eZL3aAy4GK09U7zd+gtgKj1Trfmb03WNzh/RXTZdHO0q8Dpk2ul0JqnetI5
ffWS6OltjWjAve7TOPj2TtUKeXAf5dKQRlbbchA8fCYM1UKF9vX58O58hupazh8PcLliXcG/
4GjkyfsO9DYs5+sBArEWzB4PJ3n887D6ffnq99fny+ItxHk8/4buIrvbcfPQIT0Eh8nMKKGw
R/ITErq06Ozn9ZvPx5ODe3B9eTueiknrw/EEEa6PxxOcjLX++P74y/mHg1vwD3oAbLCLCWjO
36Kfx8MqOm7C2mi0yhlnqBqVdBLUAhYSHj6iou+PDgSvZ2BePyw/vb0eET4c0/r29AnllPXv
o4eyXxf88eXX5cfPl2fQ61J7AcCuH16e3xYS/i8Jwi+9qBIEGyYJWs9Pl/cYW4sdPmID7MT/
iD2mvqMSO29oIJ76BGRfRrd4WBfskordl/+yuwEKy/bzEkLX/t3DX7N2aKd3pf8jwAAK7Tom
DWVuZHN0cmVhbQ1lbmRvYmoNMzUgMCBvYmoNMTczNiANZW5kb2JqDTM2IDAgb2JqDTw8IC9G
aWx0ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGggMzUgMCBSID4+IA1zdHJlYW0NCkiJnFdNc+Q0
EL3Pr+gbMmSM5e/ZE0N2D0uRsLVxigPLwWMriReP7bI9ScHPAH4wryXZ48lsCEWlKrYkq9X9
+vVrDUnK7lbSJw9/eCS+G6YU+6mbpl5A2X7l6aWhWK091/N4rlhNb08r8U0oyce+wKM4jAJy
ss+rb7MsJG14425ivV+/BNINQ4pl4PrWuLYpjU0294t456xj1xdrZx24kbjKq/qN82v2w0oS
/8GNwPW0u9lb3lKsxHSkT1+ORUqcfYxFG9EBxHr70B32OOW7ajy4VTOysXfZatrruXFISeJG
PsHXmHq1ult9ny1OkZF3dobG69S7fwEk2iDi0Oyew3wtrGgTuhv/2ZFmk++5MOrGCWNksibn
rEkD81Xv0of8UGPU7pWzlrEbiN8dCbdghAH3aC1dGc02+NXY4De28cFZR9jVOxKZUkPFKUtE
CWM8BpR6THlT0qWzDjGJ5HqY+smckH1tvQtn70Jj+b0jfTcWDX8eilExJ2LRN2qky7bv2t5Z
J1jIx6pt6K7tCWd6YjsM1b2zOW5UJV076xR0yp0A470atDcnp8sZG2mxuT7sd6of6JPgzZK9
QXqFjkGKLcKVQtvd4MGDT85s8oj2egl3GCcxbct91ec1cEF0EmgjUVLQzxydhIuchHn6wtGL
N4dqVBSguk4hO09o3ldNTqWq6eOzfF4wGrB1uaWN5zNUGG38dRxj8yuZuG1wfkk3Yz4CvPaO
tnvVV4VJSG4exsYrHI82p0UfxIuivzmwpY3YMcSp+OysfaZQwQRD/hnrWJzpQCCD4D8JQRpz
QUTJeY2+EPW26+qq0PQaaGwNvd47PpPykmkdiq1l1rVZvGybQvVN1Wh4Q2F4SJmqVffQYpaL
0iQE01uztyx7Bc4208dtR/yh+NHRNpQm7SMy+ra1ZqFU8EgDgSoLCHAlixKdmWzCeKvynq6w
VQLU3vGFO5d7guPZG3FxVu3enBiD6EyOWQA8KwDZg5qgkZwwXXYR6rU3MESmQvNa41C0dnK/
PzQWXQK/8J8rDRprII5E5qw3kIlbFFfCxfWk6qLl4h0frAlFbQcZGA92DJbqqkoMxJHgrGHP
HjL0jOLJHEViosjvASrBi3yZ9VlVGvW0CDIwQSbHIBMBVRqRulpxqsrWzppU7fNSsS/jCVQv
WDHatlC1paikR1FJLUu13mFzCnP8XzkheFTqd1a+BBXKM3uzAPHTT1ZAduX6wDj7Amqn53vw
LRWse3CSXy+319rKJ0evIAhjgLEGGclsMJtrTbOQNSEyms2zNnTzPsXPmzLkNha3IIbZjVrn
Z6t9NwTRE/ZARuQ0jf6cRt9qyAhpz/uy+oO1ZGoON6oY2/4roCQGnC8s1XyTh9RQLQTVcOXI
QLWPyuw23CnZiM6PLxp658o4fEPMelwUkDnDbt4QiJq6ww70MW7iBhFEIbo6hYG+QkiJVvni
HSJB1BRKNJt4IZHnujTqMlrWT6N71SwhXa3LALg1kx/Wduym8AKDl28yfijZx6UfCy1wWQtS
F67w5/rFD0PW9tAP3Nhqu5D82dJmyiee2GSBimc28yvHRrPKarL0ymEe3en8K+4LTFC9hGrt
cr3az3RERAKU4clDvVycGMgzZBZ0mes3M57qzXz/l55zNT9Hs6/+22y3uosWJZ9djs5TNXRQ
kbZH79w9E/8Ph/pR9S7yaHN1QbvDSNNo+syq10A7VU/y/0R5b3Ukr4d2UqxdreYuZXvy1Icm
a+ZLXrOi/Kyc4tl/m46nh6p4gBOHuiTVwJnOopwPAx2G/F7xbYBlTZeFJqL9gvuWLywpw5mU
KUjpHjXtpS5zhuRpl4lRshzYLVV8mbOVaKOd2o2eNCXRPto1fLXXl1JTH7q31jRdJe/zxgjH
tKQxeqrGB7DNYHHfPlob5hapJf0ExHR23Sp011ePuDjRoFXIRFG0LUQK2oFRwFhZYWR3fZbR
QLQ7xMC1zuIL6AkX36e2/22wKcbhg+ofOZ/oG4NLpxD5rGoY3FJh+iOafw+3Ydu3l0Jf0EM+
kEw3r/HgSrHATBdAPnpvMNNVGdu20EDCPCu2ZLaYbwaA16Jc+7Eqqo6xAJ7HZpjd/jm8Juzn
ojew1FtZ5mxBGU5l/4L6vKza013se8k9uu3MtUBjWYzVYzVWjOL/4OZ2OLkbIrjyeDnWNIIA
IGIUt78s7q5XEy+r9jDg7jCCschqM75632wZwIrvpR3aDUaSrkFNnSYfrl18gZlnPxdM0S7b
2NzAvtRk7I+GY6/ZcFlz+U2cpK6tgWOR16baj78mzY+yjbnySFHdVfaDIteXs38EGABiexih
DWVuZHN0cmVhbQ1lbmRvYmoNMzcgMCBvYmoNMTY2NiANZW5kb2JqDTM4IDAgb2JqDTw8IC9G
aWx0ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGggMzcgMCBSID4+IA1zdHJlYW0NCkiJlFfbbtw2
EH33V/CpIIuVLOq6ChAUaJoCKVAgCDZPSR9oLderWDfo4kV+o1/cuZCyNo5TxIYlXmaGM2fO
jOjDXzeHX2+CKIyiKBGH6saPLjefZLe0d3asu3tVhoUUKtCRHO3UL6MKijCRlRWXej7jOszE
sR5tNYu6HZq6MnPdd5PoT6IzKsjDTOKCacTUP9rR1qAUwyKb7mY3/ao0zkMVkEUVxJF8p+IY
1kAEJUQ9sSOmmXoxLXdf8My5F0aofw4UzSfZLs1cz8vR8vnuZDMMY2+qs512Phb0LCcncrng
oalszNxDfLqAMbmTSzFQiKkcVQzT/rGeMLidMN1xJ+oOYmqtqMxkJxDUYSx3glwAW3aEk+fR
GvQftb1N7y1jn63YZ4w9uOqOCcXhvNBh5IUDKXP5MINbXUEXp34ENDoKrpAXlnunCOAOg4Rc
2NFbs4jeIBr7aBtx7FsD8XSmddpiPptZ2A58Mfd22mBcd2DkZKraG0IUwStkBGhZPpYXG8xd
Ifs7J4qQ2MYO577DFG9iMscjkQv8miZmHqwyrImX8tOZzdpWtEDTeRIVO21UArujC+G0NKLq
vZeoC5v1ERKDaIVrSBGlANEHaA9faAkSonE5cCPMDCCZyoMK9pDnj/+qVE5wvErDvcRqwfm5
HsTZ0NIk+M1oVDRu0IVYsg5vo5ogRGHAG9OMzGp5H70vIfxYYwFMixNREdgRTzoNS888O2JZ
+OSn8j2itZcBSEMeSncy23AKCsx3uMfz+dKj7QcfRHfExLp4ruhbrPQtVpBigJnoVqBDkIpS
jp2dsWCqZjk63hREkcSFxZlFHoy1Sz9s9cuMhcwQ9h30D6QIapJ16y1VVO9XzCqYMwnFRUIW
yKEptIf1NOKsQypGvwGrFDaCO+Nl7PH/KhZiI6NQqZO4ID8SOiyRTYNL7VrAzM9729qOAuNq
ib9XpFCdR6fV8+paoM+qgpso1kNIru7DKBUR/NIgBSPw0kUWxnvs8O2W8TEyXsckDq9UpyG8
dA7dOHfCa56DbaKhOUFHRuoqRGyE0AqiTw4O7cTlXFc0OTN8QbwPcy2gADTA9sdLWJ4BL9P4
CjbHb7rEnbXdigtj3EKnnKGkLXJ07JerpsQNyRz7Ya4dSNAnAfkP8DVrFuqaOopfQA1Ay3WY
PgcteQ5auhc6y8LyCTSt1w5CQwLt7qtKAAJsr0rjwEKFQoGsJAT4ocfAVik/Kp3Qx3DFL/0W
v2fl976xXT30MxCsNq5afCG86buTr0eFZN/Wz2f5wT6G4m/jBEbzcFU303kn4ihya/FntROY
K0qIr89TPbaQhjsn5M+l7fXDwMngLFBkkcBmrjGobSf+yR/MyNvDTRGFkAhMdC50CnhFYS5G
e3O6+f2wyVgMoINcBB/kFJINCePWn2MeUYYGbCyKwzjirEqNQiVkmYRoUKRIl7L4xhIdJCbM
TpwlMMHwIFEphgg8V4gJFEjhnvA1j+UrGt66J121LkRy/9QZvMKat1hxQUt+qXsyy1ZGvlDZ
yk1tBd0Ea1y2ipLkXhYIoVkda04aNlLT06vQdgjfCmiOEK8cfuPU8tlfsYNqOdjX9SYuSyLu
lAm7ayp/4VlDAoYEyPQ9Pl4rvao5wcGMdhPZ6wP1v0IGHxT22rdvAkXztwrvaqHOU7egy7KI
UDFzC++IccgTuJjmoqRnUsIhMVIFcu65cp3kNC+geW6zHNHmxNVHF2gpXqIQ2M+3TYSb7vdo
tM+h+z613YTJIv6ki121KCxMgKIEJLDdiv4RxnbEZ+0aMECDREkBmB18KfCaa62vNMdJwCLN
ij2zkjuJ9ryEHoYZRRE5D9gNtHx1e+tWLpeLootuWHuhhVRC+KxvVW97Vp3u+X07OVss7u3V
kLJcuq1buLrzKCB+GWQim8Wej/cut1FRO0cDj7Rdz7V1JJ1YZLR4B79Wm51PQT34Y4iPfIQ3
4CO4qBiLzumMLPrgosKvfObMsgt2dIscklPrtvFonsA/OdhRnQ9Hfp08M/V+DwwW+wz5kCQZ
drIfUTMDL8v4ijk/Qc2ihMO21ExeoiY8c98Gf9jhsmRtcXxXz+lv4DvbKxje0l+QA8R4Q/BP
jVzFTsYKC+vzQvdkDLV7NgbkomUyNkEzKOWw+CXgALQq/M4/GUP9GvU7lkYpaO4xSVtew4a/
8b3lb3Jz3TmKJMzgMwJb2Y87RxLpMNpv0XsxPWD8PwEGAGkRqxINZW5kc3RyZWFtDWVuZG9i
ag0zOSAwIG9iag08PCANL1R5cGUgL0V4dEdTdGF0ZSANL1NBIGZhbHNlIA0vU00gMC4wMiAN
L1RSIC9JZGVudGl0eSANPj4gDWVuZG9iag0xIDAgb2JqDTw8IA0vVHlwZSAvUGFnZSANL1Bh
cmVudCA2IDAgUiANL1Jlc291cmNlcyAzIDAgUiANL0NvbnRlbnRzIDQgMCBSIA0vQW5ub3Rz
IFsgMiAwIFIgXSANL01lZGlhQm94IFsgMCAwIDU5NSA4NDIgXSANL0Nyb3BCb3ggWyAwIDAg
NTk1IDg0MiBdIA0vUm90YXRlIDAgDT4+IA1lbmRvYmoNMiAwIG9iag08PCANL0Rlc3QgWyAx
IDAgUiAvRml0QiBdIA0vVHlwZSAvQW5ub3QgDS9TdWJ0eXBlIC9MaW5rIA0vUmVjdCBbIDE0
MyA3NzYgMTUwIDc4NiBdIA0vQyBbIDAgMCAwIF0gDS9Cb3JkZXIgWyAwIDAgMCBdIA0vSCAv
SSANPj4gDWVuZG9iag0zIDAgb2JqDTw8IA0vUHJvY1NldCBbIC9QREYgL1RleHQgXSANL0Zv
bnQgPDwgL1RUMiAxNyAwIFIgPj4gDS9FeHRHU3RhdGUgPDwgL0dTMSAzOSAwIFIgPj4gDS9D
b2xvclNwYWNlIDw8IC9DczUgMTggMCBSID4+IA0+PiANZW5kb2JqDTQgMCBvYmoNPDwgL0xl
bmd0aCAxODQ5IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCkiJlFdNk6TIDb3X
r9ARHA3NZ0HtcXbHYzuiHRse+rCe2QNNZU+xQ0EFCd323v0L7B+8T1JCUT0Of3RHFGSmUlIq
35PEu2p3X1UJxVQ97+KEIvzjkcdlmFEZ5eE+i1Kqzrv7721OjRWBiGyzu//wMaYvdhdR1fDP
685LyK9+2QVpEaYUJGF5oOqHXRRGUZSzULC8QvQvxg7dPLVDT3Ga8rYyjDLRLS9xlobFnopi
H2alerAxlPGGq7dxVoRlBuEoPOxVOLiavVr95NGTH8RRmHt/9+MDHjSd3IQhfvH+6McJRpUf
HMLCe6QfO9O3l2Ey/dTWox8Um73fD/2zzhi3YvrG0GfvAariMPXq0c3XforhV2NPd5REUfLZ
D9VcdWotbWLh/1z9aRfgzAkFcRjnHEA9SrkepdSjQHo6GRp6Q6e6P96R2Co9Uz/ry3M7nmEk
9awImr/JSUuvtVPbf/EPYeLROHSGsJvs4FZfzGha2aYi/eQHSapnxobheROnhOOEwSM9mPOT
gVlv9HmaPk71ZCy9ttNJz1T9Di6Pxl5MM9E0UN11Q8MbEBpPjs5eiLZz3de8ovYN1s+IPlvG
MdS1kViV8xga2xdDzTD3E2IQ89kXd0VhMxwN9bMG48mM6+llFZqG2cWugc+Luxr2wxr2g4Zd
Qr3EHj+ji37bizsHz07j3Ewa84+mGc3EdsPYq9W5gzoXewFCFXsf/KAE0gwGB2/RoaOx7tSb
A2AtWJeXONqHJRWM0+QbZvyDbqlRlpDdH7Iw3hIj3i/H4jchBiwneeT9E96miMRA7qWWC/3K
KAEQ4nDP7iM5eNQLyveIv7GWt2NSpfmg5UaydtHVh1PcOkP9YokRiE1kejuPZpk96awBQl+Y
ZqzXiBWn4IvPNhSmevNicwPUGOPKgUWgqhufnGb1avRZjD76QY7ncnj3FCjr661bb9CSrmhJ
NawjtO+RABhwgnW8j0cmgEPmillHscIjhav4m3qzH/DjvMIWApeu7q0qYNLUx6PAN4WbVjzt
Onoy9Dx3nVxLvqo+u7E60vZT3fYG4K3thqWI/2nkeWAauakZzuDf0flTC1ffA06ZY+QmHxQI
M+fSR5L8mTN58duJjrlvG92N5NAf6/HY/srByZzOm0jGK+9ixzu5mILJ7gdAszeM4Jy+cqxA
F3o91W7RvBhGSiy3GgOAl0unK5w/+Nksok6HwpDfTqrNCIZjxROrEOxhnmZrjv9ymToO82ui
3tBQWIjDyAnW2hfrURArANaH0q4VDiXAR8yWY4/znJ9xXTJ+BpwRj8AMZAO8GA6Ckx4gzUnn
oMM71rdcBRS0/Us7OR2gRoSDJNg0M/YamR7As26SCsjHdZKLggqRA104sdHAto9mFMc229vj
dasssrMzHGHgJXwuMXo9zH9hS3u+dA4kltEl8LqMw0trl6lrrbRIhGg44O9ndBMvIT24cguQ
bivtlShoNN548E1/gNr9H4o23TllFqRzfcNwmcCUt22FRHztJZg4a43ch1ol86VKCv1eDUiL
59A7Tcz1nG8+EqbezNIvwuPiujwtN5dsLN47KefHe5l1nc3vfWbTGo5rixFseww71bi4vQe6
ynP0OfcdfWkjftU5Ld7y2rgJIK818m4J7ZBs0nHI1gXArCK8o/d/fnz47IuEK8cb6c5ZEJJk
blKyp52fbLNxqX0ym5FzR/08qsmtXmuFOFdHyC4U4ZEVR9iqM1p4Zx1YJr9MqG4mxy2iihVR
hYawGfoXbQ+1o0GW1sss0G3Q4F6fAYgURDGduZyGRUDQlLrA9GZ6XcRHEf+6NFjr1afej5Lf
ci94qpGmnDjJ3vGrZTY33XzUUpKu7W9x0/6mnFF5chK4IvVgf3jFyrdpTrPbyqbYseknNFaW
rFTOwkNvLDkUZaGTlqjQ5Jojd3EidWiMJKFm/y6hRtdce5NhNcV+8j6pu1a9b+VyUR7M8Wdd
uD3CquL2GEgqyxUmyzHsqR3osUINyrxHP9EGX0P+Nqul+eq0FC2py9oF5tICCP1GxpvmC24P
AuXxB4FGKoWTuTo61tcy6lTD/3aItcGLXIPXNN/RwxjSH4a5Y9Tybf+VA5RwxYvAinq4ox9a
gSo3dRNX2MpoC8Fd9qaGi19IC29KeelK+Tufy/qsakdTz05+veAE64e3N/x//vFx31e7mFra
4cOvpBKB5W/BjNguvhB2z7t31aYXTsAMiO3DfaS9sMaMvzBFRF5EVXFY+2X91rztwIuMP1Hx
e6tIzJDluCd5igEfEFeQO3ieuBVFiUfqLd3vhWN08L6Twb37RSQT7xVpJlt/Yw5o2OqSbp1V
2zLZb5WrpkGV2y+65BRbn783LvMymUvxlg8plNatatXVqq5e96k8l0O30zh9akv3c9u3epTr
SrieXrw486iEPCMC11iABggssI97SrEkt4j7WK7x9gbSCE3+9gYiWbOK+VSZsUDktwEAW50E
pwplbmRzdHJlYW0NZW5kb2JqDTUgMCBvYmoNPDwgDS9Qcm9kdWNlciAoQWNyb2JhdCBEaXN0
aWxsZXIgNC4wNSBmb3IgV2luZG93cykNL0NyZWF0b3IgKE1pY3Jvc29mdCBXb3JkIDkuMCkN
L01vZERhdGUgKEQ6MjAwNDA0MzAxNzEzMDcrMDInMDAnKQ0vQXV0aG9yIChBbm9ueW1vdXMp
DS9UaXRsZSAoSU5URVJOQVRJT05BTCBURUxFQ09NTVVOSUNBVElPTiBVTklPTikNL0NyZWF0
aW9uRGF0ZSAoRDoyMDA0MDQzMDE3MTI0NykNPj4gDWVuZG9iag02IDAgb2JqDTw8IA0vVHlw
ZSAvUGFnZXMgDS9LaWRzIFsgOSAwIFIgMSAwIFIgXSANL0NvdW50IDIgDT4+IA1lbmRvYmoN
eHJlZg0wIDcgDTAwMDAwMDAwMDAgNjU1MzUgZg0KMDAwMDAxNjI4MCAwMDAwMCBuDQowMDAw
MDE2NDQ5IDAwMDAwIG4NCjAwMDAwMTY1OTIgMDAwMDAgbg0KMDAwMDAxNjcyNiAwMDAwMCBu
DQowMDAwMDE4NjQ5IDAwMDAwIG4NCjAwMDAwMTg4ODQgMDAwMDAgbg0KdHJhaWxlcg08PA0v
U2l6ZSA3DS9JRFs8MjllYTRiOTY3ZmI3OWFmOTIyZmU3YmI5Mjc0MjA1Yzg+PDI5ZWE0Yjk2
N2ZiNzlhZjkyMmZlN2JiOTI3NDIwNWM4Pl0NPj4Nc3RhcnR4cmVmDTE3Mw0lJUVPRg0=
--------------070305030709050008070103--

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


From exim@www1.ietf.org  Fri Apr 30 14:24:20 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19921
	for <ietf-archive@odin.ietf.org>; Fri, 30 Apr 2004 14:24:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJcdy-0000vx-4r
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 14:21:50 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3UILo4H003585
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 14:21:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJcSY-0007lx-Es; Fri, 30 Apr 2004 14:10:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJcPn-00078P-UT
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 14: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 OAA18836
	for <ietf@ietf.org>; Fri, 30 Apr 2004 14: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 1BJcPl-0005bZ-7U
	for ietf@ietf.org; Fri, 30 Apr 2004 14:07:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJcOr-0005Z5-00
	for ietf@ietf.org; Fri, 30 Apr 2004 14:06:15 -0400
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJcOE-0005WO-00
	for ietf@ietf.org; Fri, 30 Apr 2004 14:05:34 -0400
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1BJcOB-0001D3-00; Fri, 30 Apr 2004 14:05:31 -0400
Received: from [68.246.207.24] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1BJcO2-0005T1-00; Fri, 30 Apr 2004 14:05:24 -0400
Message-ID: <40929554.20202@solidmatrix.com>
Date: Fri, 30 Apr 2004 14:05:08 -0400
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: jfcm <info@utel.net>
CC: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
References: <ACBFB13DAC66EE23B2F5520F@scan.jck.com> <6.0.1.1.2.20040430183140.05d5ceb0@mail.utel.net>
In-Reply-To: <6.0.1.1.2.20040430183140.05d5ceb0@mail.utel.net>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/mixed;
 boundary="------------070305030709050008070103"
X-Provags-ID: perfora.net abuse@perfora.net auth:7051a7fa85b96745770cd89fa6d27f10
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

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

jfcm wrote:
> At 03:42 30/04/04, John C Klensin wrote:
> 
>> http://www.icann.org/tlds/stld-apps-19mar04/stld-public-comments.htm
> 
> 
> Dear John,
> it seems that (one of the) most important entry (the letter from ITU 
> regarding the .tel/.mobi requests) cannot be accessed. 
> http://forum.icann.org/lists/stld-rfp-general/msg00043.html
> This seems to be a singular impeachment to a transparent debate on the 
> matter.
> Due to the delay I suggest that ITU sends IETF a copy while you might as 
> a BoD Member ask staff to urgently correct that situation.
> jfc
> 

It seems to be working fine by me with a little tweaking. If you 
download the file in the message 
(http://forum.icann.org/lists/stld-rfp-general/bin00004.bin), and rename 
it to .pdf (under Windows), it opens just fine.

I attached a copy of it to this message.

Yakov
--
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"Some lies are easier to believe than the truth" (Dune)

--------------070305030709050008070103
Content-Type: *.pdf;
 name="bin00004.pdf"
Content-Disposition: inline;
 filename="bin00004.pdf"
Content-Transfer-Encoding: base64

JVBERi0xLjINJeLjz9MNCjcgMCBvYmoNPDwgDS9MaW5lYXJpemVkIDEgDS9PIDkgDS9IIFsg
MTE2MCAyMDIgXSANL0wgMTkyMjAgDS9FIDE2NDQ5IA0vTiAyIA0vVCAxODk2MyANPj4gDWVu
ZG9iag0gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICB4cmVmDTcgMzUgDTAwMDAwMDAwMTYgMDAwMDAgbg0KMDAwMDAwMTA0NCAw
MDAwMCBuDQowMDAwMDAxMzYyIDAwMDAwIG4NCjAwMDAwMDE2MDggMDAwMDAgbg0KMDAwMDAw
MTc3NSAwMDAwMCBuDQowMDAwMDAxOTE5IDAwMDAwIG4NCjAwMDAwMDIwNjMgMDAwMDAgbg0K
MDAwMDAwMjIwNyAwMDAwMCBuDQowMDAwMDAyMzY1IDAwMDAwIG4NCjAwMDAwMDI1NDggMDAw
MDAgbg0KMDAwMDAwMjczNSAwMDAwMCBuDQowMDAwMDAzMzA1IDAwMDAwIG4NCjAwMDAwMDM0
ODUgMDAwMDAgbg0KMDAwMDAwMzk1NSAwMDAwMCBuDQowMDAwMDAzOTc3IDAwMDAwIG4NCjAw
MDAwMDU2NDIgMDAwMDAgbg0KMDAwMDAwNTkyOSAwMDAwMCBuDQowMDAwMDA2MDA0IDAwMDAw
IG4NCjAwMDAwMDYxMTQgMDAwMDAgbg0KMDAwMDAwNjEzNiAwMDAwMCBuDQowMDAwMDA3NDYz
IDAwMDAwIG4NCjAwMDAwMDc0ODUgMDAwMDAgbg0KMDAwMDAwODg4NyAwMDAwMCBuDQowMDAw
MDA4OTA5IDAwMDAwIG4NCjAwMDAwMTAyMjAgMDAwMDAgbg0KMDAwMDAxMDI0MSAwMDAwMCBu
DQowMDAwMDExMzE0IDAwMDAwIG4NCjAwMDAwMTEzMzYgMDAwMDAgbg0KMDAwMDAxMjYwMCAw
MDAwMCBuDQowMDAwMDEyNjIyIDAwMDAwIG4NCjAwMDAwMTQ0MzYgMDAwMDAgbg0KMDAwMDAx
NDQ1OCAwMDAwMCBuDQowMDAwMDE2MjAyIDAwMDAwIG4NCjAwMDAwMDExNjAgMDAwMDAgbg0K
MDAwMDAwMTM0MiAwMDAwMCBuDQp0cmFpbGVyDTw8DS9TaXplIDQyDS9JbmZvIDUgMCBSIA0v
Um9vdCA4IDAgUiANL1ByZXYgMTg5NTQgDS9JRFs8MjllYTRiOTY3ZmI3OWFmOTIyZmU3YmI5
Mjc0MjA1Yzg+PDI5ZWE0Yjk2N2ZiNzlhZjkyMmZlN2JiOTI3NDIwNWM4Pl0NPj4Nc3RhcnR4
cmVmDTANJSVFT0YNICAgICANOCAwIG9iag08PCANL1R5cGUgL0NhdGFsb2cgDS9QYWdlcyA2
IDAgUiANL09wZW5BY3Rpb24gWyA5IDAgUiAvWFlaIG51bGwgbnVsbCBudWxsIF0gDS9QYWdl
TW9kZSAvVXNlTm9uZSANPj4gDWVuZG9iag00MCAwIG9iag08PCAvUyA0NiAvRmlsdGVyIC9G
bGF0ZURlY29kZSAvTGVuZ3RoIDQxIDAgUiA+PiANc3RyZWFtDQpIiWJgYGABog4GVgYGTkcG
PgYEALGBogwcNxiOiDCAMRQIALE8FDMwiDJwyyh52LZv+KbkKrDMZVHNgwaZG06NGyIZTDIY
rgUwOzWwyDAY5zB8EGBed/AESAdAgAEA8nAUDg1lbmRzdHJlYW0NZW5kb2JqDTQxIDAgb2Jq
DTk4IA1lbmRvYmoNOSAwIG9iag08PCANL1R5cGUgL1BhZ2UgDS9QYXJlbnQgNiAwIFIgDS9S
ZXNvdXJjZXMgMTQgMCBSIA0vQ29udGVudHMgWyAyMSAwIFIgMjYgMCBSIDI4IDAgUiAzMCAw
IFIgMzIgMCBSIDM0IDAgUiAzNiAwIFIgMzggMCBSIF0gDS9Bbm5vdHMgWyAxMCAwIFIgMTEg
MCBSIDEyIDAgUiAxMyAwIFIgXSANL01lZGlhQm94IFsgMCAwIDU5NSA4NDIgXSANL0Nyb3BC
b3ggWyAwIDAgNTk1IDg0MiBdIA0vUm90YXRlIDAgDT4+IA1lbmRvYmoNMTAgMCBvYmoNPDwg
DS9BIDw8IC9TIC9VUkkgL1VSSSAobWFpbHRvOnNwdW1haWxAaXR1LmludCk+PiANL1R5cGUg
L0Fubm90IA0vU3VidHlwZSAvTGluayANL1JlY3QgWyA3MiA2MDcgMTUxIDYyMSBdIA0vQyBb
IDAgMCAwIF0gDS9Cb3JkZXIgWyAwIDAgMCBdIA0vSCAvSSANPj4gDWVuZG9iag0xMSAwIG9i
ag08PCANL0Rlc3QgWyA5IDAgUiAvRml0QiBdIA0vVHlwZSAvQW5ub3QgDS9TdWJ0eXBlIC9M
aW5rIA0vUmVjdCBbIDI0NSA0MjMgMjUxIDQzMyBdIA0vQyBbIDAgMCAwIF0gDS9Cb3JkZXIg
WyAwIDAgMCBdIA0vSCAvSSANPj4gDWVuZG9iag0xMiAwIG9iag08PCANL0Rlc3QgWyA5IDAg
UiAvRml0QiBdIA0vVHlwZSAvQW5ub3QgDS9TdWJ0eXBlIC9MaW5rIA0vUmVjdCBbIDQxMCAx
NzQgNDE3IDE4NCBdIA0vQyBbIDAgMCAwIF0gDS9Cb3JkZXIgWyAwIDAgMCBdIA0vSCAvSSAN
Pj4gDWVuZG9iag0xMyAwIG9iag08PCANL0Rlc3QgWyA5IDAgUiAvRml0QiBdIA0vVHlwZSAv
QW5ub3QgDS9TdWJ0eXBlIC9MaW5rIA0vUmVjdCBbIDQxMCAxNjEgNDE3IDE3MSBdIA0vQyBb
IDAgMCAwIF0gDS9Cb3JkZXIgWyAwIDAgMCBdIA0vSCAvSSANPj4gDWVuZG9iag0xNCAwIG9i
ag08PCANL1Byb2NTZXQgWyAvUERGIC9UZXh0IF0gDS9Gb250IDw8IC9GMiAyNCAwIFIgL1RU
MiAxNyAwIFIgL1RUNCAxOSAwIFIgPj4gDS9FeHRHU3RhdGUgPDwgL0dTMSAzOSAwIFIgPj4g
DS9Db2xvclNwYWNlIDw8IC9DczUgMTggMCBSID4+IA0+PiANZW5kb2JqDTE1IDAgb2JqDTw8
IA0vVHlwZSAvRm9udERlc2NyaXB0b3IgDS9Bc2NlbnQgOTYyIA0vQ2FwSGVpZ2h0IDAgDS9E
ZXNjZW50IC0yMzUgDS9GbGFncyAzMiANL0ZvbnRCQm94IFsgLTE2NyAtMjM2IDEwNjUgOTYz
IF0gDS9Gb250TmFtZSAvRnV0dXJhTHRCVCANL0l0YWxpY0FuZ2xlIDAgDS9TdGVtViAwIA0+
PiANZW5kb2JqDTE2IDAgb2JqDTw8IA0vVHlwZSAvRm9udERlc2NyaXB0b3IgDS9Bc2NlbnQg
ODkxIA0vQ2FwSGVpZ2h0IDAgDS9EZXNjZW50IC0yMTYgDS9GbGFncyAzNCANL0ZvbnRCQm94
IFsgLTU2OCAtMzA3IDIwMjggMTAwNyBdIA0vRm9udE5hbWUgL1RpbWVzTmV3Um9tYW4gDS9J
dGFsaWNBbmdsZSAwIA0vU3RlbVYgMCANPj4gDWVuZG9iag0xNyAwIG9iag08PCANL1R5cGUg
L0ZvbnQgDS9TdWJ0eXBlIC9UcnVlVHlwZSANL0ZpcnN0Q2hhciAzMiANL0xhc3RDaGFyIDE0
OCANL1dpZHRocyBbIDI1MCAwIDAgMCAwIDAgNzc4IDE4MCAzMzMgMzMzIDAgNTY0IDI1MCAz
MzMgMjUwIDI3OCA1MDAgNTAwIDUwMCA1MDAgDTUwMCA1MDAgNTAwIDUwMCA1MDAgNTAwIDI3
OCAwIDAgNTY0IDAgNDQ0IDkyMSA3MjIgNjY3IDY2NyA3MjIgNjExIA01NTYgNzIyIDcyMiAz
MzMgMCAwIDYxMSA4ODkgNzIyIDcyMiA1NTYgMCA2NjcgNTU2IDYxMSA3MjIgMCA5NDQgDTAg
NzIyIDYxMSAzMzMgMCAzMzMgMCAwIDAgNDQ0IDUwMCA0NDQgNTAwIDQ0NCAzMzMgNTAwIDUw
MCAyNzggMjc4IA01MDAgMjc4IDc3OCA1MDAgNTAwIDUwMCAwIDMzMyAzODkgMjc4IDUwMCA1
MDAgNzIyIDUwMCA1MDAgNDQ0IDAgDTAgMCAwIDAgMCAwIDAgMCAwIDEwMDAgMCAwIDAgMCAw
IDAgMCAwIDAgMCAwIDAgMzMzIDQ0NCA0NDQgXSANL0VuY29kaW5nIC9XaW5BbnNpRW5jb2Rp
bmcgDS9CYXNlRm9udCAvVGltZXNOZXdSb21hbiANL0ZvbnREZXNjcmlwdG9yIDE2IDAgUiAN
Pj4gDWVuZG9iag0xOCAwIG9iag1bIA0vQ2FsUkdCIDw8IC9XaGl0ZVBvaW50IFsgMC45NTA1
IDEgMS4wODkgXSAvR2FtbWEgWyAyLjIyMjIxIDIuMjIyMjEgMi4yMjIyMSBdIA0vTWF0cml4
IFsgMC40MTI0IDAuMjEyNiAwLjAxOTMgMC4zNTc2IDAuNzE1MTkgMC4xMTkyIDAuMTgwNSAw
LjA3MjIgMC45NTA1IF0gPj4gDQ1dDWVuZG9iag0xOSAwIG9iag08PCANL1R5cGUgL0ZvbnQg
DS9TdWJ0eXBlIC9UcnVlVHlwZSANL0ZpcnN0Q2hhciAzMiANL0xhc3RDaGFyIDEyMiANL1dp
ZHRocyBbIDI4OCAwIDAgMCAwIDAgMCAwIDAgMCAwIDgzMyAwIDM0NyAyODggMCA1NzYgNTc2
IDU3NiA1NzYgNTc2IDU3NiA1NzYgDTU3NiAwIDAgMzEwIDAgMCAwIDAgMCAxMDAwIDU5NyAw
IDcxNSAwIDUxMyA1MDEgODE3IDY5NyAyNDMgMCAwIDQxMyANODM2IDc0NSA4NzUgNTAwIDAg
NTI4IDQ5OCA0OTcgNjkyIDU1MSAwIDAgMCAwIDAgMCAwIDAgMCAwIDU0MSA1NDEgDTQ1NiA1
NDEgNDk3IDI1OSA1NDEgNTIxIDIzMCAyMzAgMCAyMzAgNzg5IDUyMSA1NTggNTQxIDAgMzE1
IDM4MiANMjQ4IDUyNyA0MjcgNjQ4IDM5NCAwIDM4MSBdIA0vRW5jb2RpbmcgL1dpbkFuc2lF
bmNvZGluZyANL0Jhc2VGb250IC9GdXR1cmFMdEJUIA0vRm9udERlc2NyaXB0b3IgMTUgMCBS
IA0+PiANZW5kb2JqDTIwIDAgb2JqDTE1ODcgDWVuZG9iag0yMSAwIG9iag08PCAvRmlsdGVy
IC9GbGF0ZURlY29kZSAvTGVuZ3RoIDIwIDAgUiA+PiANc3RyZWFtDQpIiWxW23IbRRAtXvUV
87gLpfXcZzZPJEYYU4kDZAMPFA8pR05EWQrYCaH4ek5fRlpJKVdZ25qevpxzulfPpsXFNHnj
zHS3cN5Y/OGj2KGa6spgow1m2i4uLh+TuX3kc2sebxcXV6+cefe4sGa6pX+fF53ppz8pWpRo
I7uOxpdhzCb6wVaJtbSDtT7zRTyVSrd/737ql+MQuvveDqV70y8rjFsYrlubt2KuewfzsV+W
ISKdC/juRl0/0rdjt+HrH3a9c/h87BO+MzjyPsOe1vfrv8jfd+8/7NY4QAwKtUyFHr6Jzni0
H6xJzjjH547Pa24B/qUAuUNLzlhrzScq3GlmLcPcvselHCPVv1pu30jSzf0ThPRD4pDZdhv1
1xjbHuD41v3m/tuT84Gs2m12LU3/x/TjYjUtnNmYBVpM3qQ8gMEUy+ANosVqHtaLu8Wz6YSR
4AZ/xEhtjCghl6ii+wFd5Q41O2eu1rv1P1wb6veWwQnciaBH4HB7sbvrfWMxdQxYJceR3K4e
pPjwxPQjRdijHkyh+meBD6i/oyCx07saeWuup9fmanWz+pUSdyuCKc9K+iy47z8S/g/UF7GV
iK0KWD/1UcBt3+/0QPC1ZgmszPSdABX20q2K1CvEH5nLitr+oyIixErcP9B3BarG1UBlk8Z3
/dKjzLekP2ubBIM8XemVeAaPNTlBcbgUj0QpVR7m2BK9PKn0wLOMUQ5ZyD6dWKjn74WDoiF5
iAu+qM0ghWfl/GZ2pJ2L78+WhNzx6FIjd19pvJ/pxsEx2BNHjBb+sEVOd4Z3rXR58iAZHaRx
GH2rXhdQd01XXZUk1YSEZXXsOthcEnXb3UyrX26eTtcvb54+55SniVzFhz/JRDen4yxujF9K
kws7r56vLl++ePH65vqSk30xVbT2vCm6/fo4VXTlPI+Xdlpsx9VYE4dq3WjEVNAASDhctfQk
qoWWWLU0zg9vMKgj5Mlqf9WTLGnLZqzeIOOG/ftRvNjYyPNHHY0h2jHQfLgxZxqRL8or2TwA
tZCpvswLCpOu6tqrQbyqrQevpbjdfQ1NJeytjCjYbDGa7Yl9v0jQGXETM7TOtgcCsNMgx3Eo
ZEaCh2zgGwNRQsZIBcKUq9ExhjGwEeQiVpocJhoTsjMHjlXyNjuhjjrzT75FSmGonAVbmcxE
D4ciUpFAcchyThNG9SMCmSPfzu32SH1T+7Z5E66RgSM7s7t2j1z+KHaQDjHnbDoqtkir1NPI
u2NfautxD5BisLcVo72/ozyHeIpv1FpDOa4G3NTIxfqq1HF1rRdQ6+usV18kPVrOas+lAL0k
WxhcvAYQYnuwndIPGxnySIHIrExaroKHlSHKWdCzXH6O2o2zXH72tDTIdqy07OhrslkKRRgi
mxkuqWgyx5QWMCTtuJGpS16FgE3BW8Yp8z5wcSIsspXMqgo7nYQzeJKwMypbXshHPIEf+SKn
F7RRDkElEiG7MJmQkJ5HuV5bu0HKHw9wjAJHVrSI3ByUXNjkDjSlW4BL5AJrmR9gT2gWq4af
syZm0EqOSBbehVHihmmfm7iAoPQswYoW4oeqppc6XTum4LCjmpmtkmdm1EqKNhl1AA52jfNc
SSksexBEUq3OqBQdbNfOyzw9bJJQKy6LQAPpRkxfD53BdJnNGOfBBRRCLYSm2MCwHdk0gFkU
W3WYKTrkK3xj01H4vZwx1vwyTW05FNpEKbZ9qC/AqJtJxR1VHrg2P5WtBlPEkWUT7LUoPZEt
OAuAVItIO2cZpdJw47FHVNEe5p2AsDpoJ2o5w02UCXeZ4yyvaFETqNWpUAYlrTTFEakq9bWC
WKtaNsMBMcWgNdkgSnP42iHQVbR19aYTNnxjq5HHTBYFFMwWKVs3dRAIrErpRAkkFsdrvIzc
xPbEln1AHNSGhMMP+9pax26k+DUq5Lo8qtfyHb9CSrVtd0ae+NqWh3RX2kveZdkA+h5zLLXi
WyWyyWTY9osu17ZHQ9vyR3tyP4S+tj2vPxmsDGHj/2xKTrFzct9pb77qCtF0efCzFYFqeG3m
ttXldwQvGuqlUu1oLbVOrTSeGzCUG8BkhW0U3PIMxto2PlCm9VT90BjLx5wQDuBszwHlqrLw
/xdgAEa6RKsNZW5kc3RyZWFtDWVuZG9iag0yMiAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURl
Y29kZSAvTGVuZ3RoIDIxMyA+PiANc3RyZWFtDQpIiVSQMY+DMAyFd36Fx1Y3BLrcDYil7UkM
156OtntIDIpEnMiEgX9/CaWtOsSS/fLpPVvs60NNJoD4ZacaDNAZ0oyjm1ghtNgbgmIH2qiw
dktVVnoQEW7mMaCtqXNQlpn4i+IYeIZNM9vWDR/5FsSZNbKhHjaX4nqLg2byfkCLFCCHqgKN
XSb2P9KfpMUor+gyL1ZDp3H0UiFL6hHKvKjuBUm/aw+i7e7t62v5/XX8rLJIPLQEp02e3mpi
jrGWdZdEKYMhfF7EO58s08v+BRgAU5dpcwplbmRzdHJlYW0NZW5kb2JqDTIzIDAgb2JqDTw8
IA0vVHlwZSAvRW5jb2RpbmcgDS9EaWZmZXJlbmNlcyBbIDEgL2Fycm93aG9yaXpleCBdIA0+
PiANZW5kb2JqDTI0IDAgb2JqDTw8IA0vVHlwZSAvRm9udCANL1N1YnR5cGUgL1R5cGUxIA0v
RW5jb2RpbmcgMjMgMCBSIA0vQmFzZUZvbnQgL1N5bWJvbCANL1RvVW5pY29kZSAyMiAwIFIg
DT4+IA1lbmRvYmoNMjUgMCBvYmoNMTI0OSANZW5kb2JqDTI2IDAgb2JqDTw8IC9GaWx0ZXIg
L0ZsYXRlRGVjb2RlIC9MZW5ndGggMjUgMCBSID4+IA1zdHJlYW0NCkiJbFc7luQ4DMvnFBNv
4Kc/pQtt1HX/dEiCkGVXZ42Wih8QpOg/Pbdr/pW5rlX+/vwxmBSvdOWh+P//9F9DcbHzj4J+
zel4TL/fr14c199+/4v5Vc7jfrn5ZFaAC34+aX40xfkqzfG4cnG8RuCK8EpAoB6njByZjGnB
SL9Ss1xOqLfH8lgUywhsvkWuxnOx83mdcKbIPK7PbBkAGywRuTob03EugY0JvZ7pLbWnOcPb
G65rMEgtzMm4hOaaXedhQmYRyiNRY6IlC0ukGM+fF9ZftOJllXwBehUlBetNYD9Fbm35r8GI
4p4vQLjv1YIWZGS4W5WQkUFxXzdengrKYdFnWodGRgEVyUFzAWgowUP3SDNpEk8qfigWv0i9
xjcr36QJLLugDQ9QUlnADsYLw2wuTXVdGeaYZ2QZ5yRN06zF0wLlpMFldLO04SZxc9w3C1qA
Bl9tRoHKWa8OLeVoWq2uK5nEaPUPXl5aMLmUro0kJpT4S6+VZkVePZhW6O3Wgh7F5nP3Is9z
AAt+rmit0p2bKZGs4mnNMIL7MnyKNPRCQR9NANC4+6gm5LaQTI2qsE/qYJP7r2sUvV3ll9Rf
xOjlDkWAxhqKoKPh/YnqV4hW27lElNODjPymXZ41DsUnRQunmmxD8pscN7VuJn0E55tpGU+m
/fxkdvXbmBgeIaNdTytz9TE8k3X9x4PWRA028j4TJaZRGhmLTa6GrbnWZBTdJbmEdbqF8w5h
4MmQl+XJ4guUMy9CfxK244kngH2kUScEWikIFaLhUIC/LZYVzJ9JgwbtTIhR4/s8IfrWwpsz
mivGlT5ZbOuE6sBdj/Aqh58Xe7WIrkfyPTTV0RlKTkyFArKE3gppjSkSbTU4a31qqLkS1rcS
ulAm4SkCy0G7YjmfZsUTsks8N88R1oMTf1EEfTignRNiQOVyNLROL3/tOp0jzdlD092Hyw0h
LsXBmviaMHuIK3JR8+OX8F6hi7fHFDImCGWEcDvkeYfKUMLVjjSwDx67Xo5JvPMWvPrCSfug
JV7iNVjwzwvvEbT1EZDy4e1YcnrLF8Q3jjmvJS18xtM8pNuwvE2hr1fR3sFD9o22vA04lVqF
nFJwrr7bsag1f3usDSIUfyYtkfbAfE54f8TEfNHibXq2xueXVknYNedDgntuRLKLa0XrnCuB
7U04rhdM1clCRID09lW3dwIFm62wchXhcMqpu1qO+clw5vWIlnAyms5cxzysfY2JJzdOH4Sr
FYkxd2L8xAvK7aNhbO2xMx5jLKY/y9mF24Bwp4tyxzKUwAbvjxTLxON2j8eU1jaOIdmZbaX1
PSTz6S2mzR3dM1X/yBEXizf75wl/HGq0nX2Sp/9+7K+S6X02aD8vZ1s3SPgvKTZWvoWoju4V
gZuzIePig+ib5QpyS0ziHO51t/Bp10KatWFB4MJQBXi3amJrZkpvtmNKCGrLGfIlhBd7lGKl
siu0xk9AdZfL8Q1XBwYuH5Ja8eEk8SLiQT72n4nwC/cBLIOyyGb1vV24Hjgte4Ur6cIWjg/C
5WWIj8XpiQzKIiPxkYPnjM+au8y+RR8aOCThmvECCfj4wJk2ZqFGLEtMHWCrMci8g0FjHrjy
2/VLgU9kJTgvOy53ZjacdSowkemhPHho64irSVRfsXV2G7x8JvnzT4ABAKbsLz4NZW5kc3Ry
ZWFtDWVuZG9iag0yNyAwIG9iag0xMzI0IA1lbmRvYmoNMjggMCBvYmoNPDwgL0ZpbHRlciAv
RmxhdGVEZWNvZGUgL0xlbmd0aCAyNyAwIFIgPj4gDXN0cmVhbQ0KSIlkV0u2LCkInL9VvHEP
8igq4IZ61Hf/0wYCTKvurOKkYvCP+vPvP3/W6s/8K3s+g//+fML/AjbH6xkUuD2LDbOdMjj3
o/5ZnqmJybE+DKzPIsP7kTA35dn0V1t7hBI77G7UIT9skNI4xye9vhgbzXsDdmjmO0HTnq93
GTzopiV1PGnz0zm9GhRewrxh4+9R6JRRuILiURs7HJvDLf58YX+hPdviNGcSmO63GO2Zrrll
MZoZF3XiEu+8fBdlmIyPnV6z6FpQ/LSkt3bO3lpap4ef5gZbhuwsd+fjcMZLPPJlw/ZDeCWz
tYIZS7m+3GlhRR4MGpLKn0H7IULuPbAHVtLt+sw3kA9L++HrGe3HkIFRRTcjm7oyuAiEqHjS
4aIXpWr5SBH83cpHQvopy+y7xn9nO4qW6vm83orb8FiJsucU2JOrq+4jxDqeD/aZW4OevNfx
OyRXrDwLbxzvGKeBkwPY513RmO4dyxssbw1LcDqPYFkBqCZuXhCXt1OjfHjexbarN3oE34pv
VW16NBZXa+4oxpnXreQZlS1viwsuOVzom119M6MT0c+OOxpnJVvrK2dnxwJa2zkZazudie82
jE4Nx8S+mAXv1OHhmTU5xoTBhnSM6ANB+zrmyKXRAN8RYRXQAo4+z5E1vE0cwdnvqfCLruK1
kZVo1iTO59MKY4ikYU+k4V5UG6hh1pqjdDlyu41IWNA9ljsG1gvOxLCCr870kOxe/bGrveCF
zRJC/aOirJScmM7MESOkOrIirPSiP3oSx2zxDkh7Go5IDUfDfl4WYsoIogw4ZnUft8ttwzGg
asUIKoQlMyiRaWHOihJMZpBy3B+6j3e0w2UuJlruobQmlUE7581nXHE85uRpaEY+zVO0qpFY
iARSykihjjeSOegQeYu0P26DLiPXEGnN1y1TMejOcB+YZOOp1iUMtrNGTs69IHr0IuaclUQX
fB7Jrkcn2208RmltZeAJg8OWKI7TujYsbWzUXMCjhynNGTOwm2fVdditowofKiETCXklxngg
QHIgALSSAQt7/Je/v4KB3etnUQdm13Nl79Sz9EFKL1nzUt6vP7v6Er7WOLZI0HWUML2Pe0Sl
oJBySs4psCwHnS791aNJ3AvEuSOBsH3nMzPc0borZcoH9hvDqyl+QaGcJWe29oftJDKLd4fC
4ix8wk4+WSWOiO0qju2he4XfiF3sgi4juoDPcAs7rxTs9bm2RMJWSyat3SrVXxvVF3NeOYEm
OqrUjuunuAyux/osLHyTGbnvi+vBq7hrDeYQq0neQhGf+xupD7I0nru2CPv2FEg/dYuZYYny
+Vc937FAdw/gT/q4yKuYZbqylb6qwQuGoMNm+PLzhVGusaFmDYGGJcTomi6x/7QmyIoiifhG
tcXllcKoE5TEyppIeqZjQa9tSNPaQw17gav2G7bnUTot90h7MfbGge6tcGEs47OGOka7UuHv
XvmKXsNeUnr4YmPmkq1gcfCLfS+9dCKhF1vsiiO8wZ5LlLYNGdcTd6zBpZ9s18ntwHfK6W2p
6BBeZ5DcOguzftZICo0zsx8IYrQ0zldJeNUwfFkhyH++MPachiakFAiXIMwdN/erNnz+4x+e
Y4ECW0c+yy2hFpit+3/eUWsTvVGaCDrLIWI4IR1GzYEhhbNxZ51P+QbhM1ttRMX3EoO/muUr
cFBrtRA7XVRGFLVAMH5QwTx8qeZMGlFNhsvRhFoiPFWtlKhPpuePxhGlFmDhV1KbxgiNyqVZ
CBpVw/T/AgwAaK0sJg1lbmRzdHJlYW0NZW5kb2JqDTI5IDAgb2JqDTEyMzMgDWVuZG9iag0z
MCAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAvTGVuZ3RoIDI5IDAgUiA+PiANc3Ry
ZWFtDQpIiXRXy25sKQzc5yuynsURmIfhe0Z3VunNzP9LY7ts4JxOK1LSFYMpvwr6q/V61fHN
LV80vn++Wu9XFViuSQbHldTcL1j5Kl0gX6kK/uevryZLq+yYU//1emDZIltJIOsxCsfFitvV
4TFfWXG5ui3vRYnwzL6+NyMwxjW785OFPLqeAkZi4FHCn53LI10Bh2xn9ng4WbjcnJ1gpcO0
sXjrc0MSb3IosBj09E47PXIs9xT2e37e0jctudO5inddLd4CaigSsXPNV6GTTLbMbq5ZMyuh
0NjUeVy5+1msicmBQXXUTZWQyMizmWfktdh2qcOoXieFVaulZZxW1e5nS4C6e1q4P9YEw3qA
u8OzJ6RtpAyzfp+///v7qxGjeOVqXXuJyJoDWPxQvupRazFrMSXEZqTITuXprUPNCo94qFsy
JVu+li0+Lh4fWUArtyXBbPVXXKyPpBGG+S5NKWmtirkrbEyRNcVDqUhlYa7eR8m316w11k5A
YNX6UfsEpa9V2bRo8loENJ8A2au5Flz64bvVoIYJEFydmXZ4i7qXbpFZhQAzIHJavGPJCy3e
NbCW3F7J5rNOT4ww1dLWGLDarSbyh9EoOogsq1p0grqvJeSgGXnxivGXyVGYtzoo+ZoMiEWC
y6EDylvo1pg0ra9E2485L1Evl4UwdySlDK9Pt0ZW7HNdtS30tKVKzXiEKiXTAZQR46CnSxje
8GztssPs1i5IFtKg9Zcs+TgR4uxe42aNvpIqSTT3w90j+1qElWRzP/d2q3Hy8MT9BAabipqH
NHgRsAts9TjZRVGUBuzux3W2jA+/ePUa2gdtUD6DCxGUKDQ3piBoGFO95IMpOdLUSOW93UtM
FsXoKKw+t1ZRRj0xlxOaCavplY6xryZLlIx5TLndDsXPohkicTOHZhQKcw9RaDdccZm0EIFm
eoTPrJ+83OhaxTVG1g7qQRNDKFq+ZpagbBj5YvcPjyhQydDyuLXJdIVHVIBMSFTc0Q9kWqHi
jv0inAWXMHJMye9sOy0PXAXTZymzshuJvH2y5WekmPFsmjoS+2WQq/bHSJ7VbBeWLgcZwUNx
MSC9JJ9zuGJdNFJyHtq2M4Y2Tzwduqef6AwJPT7YSVPDVdIjBR3vilDN29VjV1T+1h+7lnB9
4d7GtVTQsqitY7HPSG99g3s1vEHafjEDLutz9ckFLzAyie32YnrdIe7MVI/5IteGxY6ufrxJ
Hv7fzydTxhMzxtXv0WXvd1ijsw5yT/Z2+2a9Av79AyNueDahexkba+y0XwCj3rCB9VrQFuBQ
RZzEIyqOvSe26R27qo57DEnrJ66Y/rkr86v94/ozNs+Fu5Dke5/Z+ybd3zvbw9Mj8F7v2cp3
BtvuON8jfGKjA4KYXffwstEutFY8Nrz589UbF5ubxeeT/eP6k40TdBeLYAvlZPply7tL4L3e
Axx3CtvueNxDfOIbRQ5xH6B4Ykgg09G20Mfd1rnFN5x71h54U2gYg3fMp799/p2Plz3Vj0MK
/XcFQ1PcJMRzvvEpPx7tkic/fQnG7egb7kcwS37yej2s+t3kK9uLbKvtJ/vH9Wesq+Xqetu/
1pId4X3Lu0vgvd7TF9943+yOl/25/uTzEzK6L6jXFvX4OvLY8uYyLgXg/wUYAFspLggNZW5k
c3RyZWFtDWVuZG9iag0zMSAwIG9iag05OTUgDWVuZG9iag0zMiAwIG9iag08PCAvRmlsdGVy
IC9GbGF0ZURlY29kZSAvTGVuZ3RoIDMxIDAgUiA+PiANc3RyZWFtDQpIiXRXy64jKwzcn6/I
ehaoMc/+ntHcVbK58//SGL8w0FE2Kbkwxpiy+6dADvnVyh1ueL1/CqSQB+7hroTZvEFjQ0h1
4v9+/Vyv8fv7e3oi28dwvUKrsrbBioHtvTNGEEPkjeJgDZy7w607crtHMDMqxAp7Jtj0iKWe
uF+hkq+YQ4ITGx/xveASCsztEGJMM5ro44z+EMK0QyKuPgOIia8Zwo2XDAo+7m7eRnyN37iN
fI1Nhq2Py0j36nriKw+cY4AnyGx0RlcVR2IfzAyj5Odgu1AoypJa4LxUim2iNyEpE05K6nQb
iKFL5JdPwur92BzphYO79eD5Ce5sjWVGRoF3LqU+grHQWxsh7vzDGcNJFl9V6mbxbc52uK8W
sw+OHMLYLI4c/f+HrDnxIyl4YIw8S5FTSb0JA1l5N4F8vYnfU9X7TaOeRygC6T+/nQwjnxhV
1Mqo3R0C8fWENQeIM28FWmhyJMOV+fyCcuSnWWXvURmNXhXjqCdmCJ3gtWDLgCQoyWs97ILN
vvNdgt+a8mg5/rgc55N/umOyQdaG/b5281e6D0WiYw83P0IhmAhuC06HjCefvPWoud/Ngs2+
0WcsHBx0esa8fjSTxtuL5i783ZlwJ67Bn+yL+RvbByKxtVlXH2NYZrYVh0OCk93Wi9vNdbnm
g918iUtwV3Y1JyWfT/bpzFc33Pwy56kejF/JPggRp0uEgYUTVyzCADRwTOFAnKrTFXCCg95J
SFWP9Bx1PSP0h1DOUAWrKiB2bxRRAicpiFmfBCxiBKMFTa1KF+/scPZy7xIiKUo8SJDEj+YC
LG7WAZYVhz9hG46s2tYwvHeHzd2+28qnANklNTTSWhxYmjUYdGBDwYfIkGdfRmsC17bR/ZV9
W0/rLCTbW/N0WzO8q+/bQLc427rRDUfw/Gsbh77YdaQ5+OAHIMkNzx1yc36aWtmns2udxTRz
OoMfdsbTvvMtFAnNz3ofm5jIvpAPTzpbGd6mxEfzN/Y2ci7fDhrSHqIbV5fi6MHP0TL4WHHI
HKSVrkOGw2JfZgiFIM+qa9evjGUW8tNHYuUvOu1IC9969AqPPrThVXFdU4ngtlJ9NO3pNDVr
mKpqegrVLVVQVipBIiQmDKD5WLBlFyT3JjuS+6hseol2VVG/8lpd8VJDrirmN0yprBl0ts+G
cW1p9FGImE9ZbtWYi/ZGp5UliDNcLTai10QDnR2lZspppRMxJpFhcqFiLmqTtQ6TnGXpiFXS
kqRxVBEkCBoZqRtIpCyL80uRjzizWrjlWVYlE5bVLTM03rUZ8GeFb4L0acl30Pllghbqrd9Q
o3P9E2AAsEAr3Q1lbmRzdHJlYW0NZW5kb2JqDTMzIDAgb2JqDTExODYgDWVuZG9iag0zNCAw
IG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAvTGVuZ3RoIDMzIDAgUiA+PiANc3RyZWFt
DQpIiZRXS48kNQy+96+oYzWos3lXam88hAQnJHpPiMNomF0N6p5Fw0jAv8ePOHHSLQGaw9TX
5fj77MSO65CSNSkvW7YmLpdDSn7Z0m5yIRBMjIQt42hKAVxMYeNsgie8eYXB15YJJ+Mj4SL+
dnzvjGN7jwsRR37vDPJnL3xVm6964o7EWw4mx4oDvo91PWDiS7gM8WZ8hx+/GH8Blri4gJJf
n/htovg2orkCzmYH/1up+nk1wC0PsGj2jovyxhheF4s55dUQFWK2Zq4GN0pVX5wmZxU3slnq
aE/RVQaH2bs2E2DM95bcSmDc7SslnBYdgJPNqe5nPC2X96gQzsvWGK503rbB5UwxKqjmDQaj
+QbnCouzmWyyJ32VgJJ8bSYtQzcUkwKC3boS1h0fnHdnN3haLu+rvuS1vmj0geyvt3yX8UaQ
jQoG49XxhdrlXG9SyrHc5erq2CRn46T4qP5r8SWopkLF7Ol4DpibC8OQda9pmNMDeGg9sWcL
Tx9UfmtlmVtFjEovYC2ftV4m7S16sJbg96y1cN9sfQq8USgBgyZxqqmJcF+bFgRGiz3Gd+l5
8GaANS2YOeivuFEs7tqxxLJzF22hF+6ikqkimariNzoFGo/7MOkp2MyV3Oq9hbOPPZwump6K
7AjwgeSLoFMDLrGnGSClWTZhiPtOKhz2q/GMFbowWoMHcUHXWGXQeKg5VFtsjQy4nC4X9iWQ
4+zVqpkVbvUyKZnsSXwlkP5dTXp7mSgmBQy7dSWUZqmdd2c3eFquuzckvTd4PIaJ74vmYqYY
FVTzBqlyO+HgXWHxNrNN9iSwMkh7rCY9QzPFLIFxt09yIRYdQDs8ebyib+hG+6pwEJiGeYOb
1YBHwhs9Vg0YXFW9gUPVpeFsB6pr7W1WxxY8PXFxqenJLvj3xyMx9TEMw4iqfYCTof69tAcr
FUctwIm5ZU6LYrn7ZB5Ji3TS9ux5GmymjnuBuJLpkWqcsNLBw1lTCdBlPUky1rOd5aMQZBQs
ahTaeKPkcuxzShnmmFZM7eIdsL7qfdGXbdBsgBJb1wYd5Ji0qTuqNin2/eoL9WJtZG7o/4nT
GvpctDOWaznz3eZL3aAy4GK09U7zd+gtgKj1Trfmb03WNzh/RXTZdHO0q8Dpk2ul0JqnetI5
ffWS6OltjWjAve7TOPj2TtUKeXAf5dKQRlbbchA8fCYM1UKF9vX58O58hupazh8PcLliXcG/
4GjkyfsO9DYs5+sBArEWzB4PJ3n887D6ffnq99fny+ItxHk8/4buIrvbcfPQIT0Eh8nMKKGw
R/ITErq06Ozn9ZvPx5ODe3B9eTueiknrw/EEEa6PxxOcjLX++P74y/mHg1vwD3oAbLCLCWjO
36Kfx8MqOm7C2mi0yhlnqBqVdBLUAhYSHj6iou+PDgSvZ2BePyw/vb0eET4c0/r29AnllPXv
o4eyXxf88eXX5cfPl2fQ61J7AcCuH16e3xYS/i8Jwi+9qBIEGyYJWs9Pl/cYW4sdPmID7MT/
iD2mvqMSO29oIJ76BGRfRrd4WBfskordl/+yuwEKy/bzEkLX/t3DX7N2aKd3pf8jwAAK7Tom
DWVuZHN0cmVhbQ1lbmRvYmoNMzUgMCBvYmoNMTczNiANZW5kb2JqDTM2IDAgb2JqDTw8IC9G
aWx0ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGggMzUgMCBSID4+IA1zdHJlYW0NCkiJnFdNc+Q0
EL3Pr+gbMmSM5e/ZE0N2D0uRsLVxigPLwWMriReP7bI9ScHPAH4wryXZ48lsCEWlKrYkq9X9
+vVrDUnK7lbSJw9/eCS+G6YU+6mbpl5A2X7l6aWhWK091/N4rlhNb08r8U0oyce+wKM4jAJy
ss+rb7MsJG14425ivV+/BNINQ4pl4PrWuLYpjU0294t456xj1xdrZx24kbjKq/qN82v2w0oS
/8GNwPW0u9lb3lKsxHSkT1+ORUqcfYxFG9EBxHr70B32OOW7ajy4VTOysXfZatrruXFISeJG
PsHXmHq1ult9ny1OkZF3dobG69S7fwEk2iDi0Oyew3wtrGgTuhv/2ZFmk++5MOrGCWNksibn
rEkD81Xv0of8UGPU7pWzlrEbiN8dCbdghAH3aC1dGc02+NXY4De28cFZR9jVOxKZUkPFKUtE
CWM8BpR6THlT0qWzDjGJ5HqY+smckH1tvQtn70Jj+b0jfTcWDX8eilExJ2LRN2qky7bv2t5Z
J1jIx6pt6K7tCWd6YjsM1b2zOW5UJV076xR0yp0A470atDcnp8sZG2mxuT7sd6of6JPgzZK9
QXqFjkGKLcKVQtvd4MGDT85s8oj2egl3GCcxbct91ec1cEF0EmgjUVLQzxydhIuchHn6wtGL
N4dqVBSguk4hO09o3ldNTqWq6eOzfF4wGrB1uaWN5zNUGG38dRxj8yuZuG1wfkk3Yz4CvPaO
tnvVV4VJSG4exsYrHI82p0UfxIuivzmwpY3YMcSp+OysfaZQwQRD/hnrWJzpQCCD4D8JQRpz
QUTJeY2+EPW26+qq0PQaaGwNvd47PpPykmkdiq1l1rVZvGybQvVN1Wh4Q2F4SJmqVffQYpaL
0iQE01uztyx7Bc4208dtR/yh+NHRNpQm7SMy+ra1ZqFU8EgDgSoLCHAlixKdmWzCeKvynq6w
VQLU3vGFO5d7guPZG3FxVu3enBiD6EyOWQA8KwDZg5qgkZwwXXYR6rU3MESmQvNa41C0dnK/
PzQWXQK/8J8rDRprII5E5qw3kIlbFFfCxfWk6qLl4h0frAlFbQcZGA92DJbqqkoMxJHgrGHP
HjL0jOLJHEViosjvASrBi3yZ9VlVGvW0CDIwQSbHIBMBVRqRulpxqsrWzppU7fNSsS/jCVQv
WDHatlC1paikR1FJLUu13mFzCnP8XzkheFTqd1a+BBXKM3uzAPHTT1ZAduX6wDj7Amqn53vw
LRWse3CSXy+319rKJ0evIAhjgLEGGclsMJtrTbOQNSEyms2zNnTzPsXPmzLkNha3IIbZjVrn
Z6t9NwTRE/ZARuQ0jf6cRt9qyAhpz/uy+oO1ZGoON6oY2/4roCQGnC8s1XyTh9RQLQTVcOXI
QLWPyuw23CnZiM6PLxp658o4fEPMelwUkDnDbt4QiJq6ww70MW7iBhFEIbo6hYG+QkiJVvni
HSJB1BRKNJt4IZHnujTqMlrWT6N71SwhXa3LALg1kx/Wduym8AKDl28yfijZx6UfCy1wWQtS
F67w5/rFD0PW9tAP3Nhqu5D82dJmyiee2GSBimc28yvHRrPKarL0ymEe3en8K+4LTFC9hGrt
cr3az3RERAKU4clDvVycGMgzZBZ0mes3M57qzXz/l55zNT9Hs6/+22y3uosWJZ9djs5TNXRQ
kbZH79w9E/8Ph/pR9S7yaHN1QbvDSNNo+syq10A7VU/y/0R5b3Ukr4d2UqxdreYuZXvy1Icm
a+ZLXrOi/Kyc4tl/m46nh6p4gBOHuiTVwJnOopwPAx2G/F7xbYBlTZeFJqL9gvuWLywpw5mU
KUjpHjXtpS5zhuRpl4lRshzYLVV8mbOVaKOd2o2eNCXRPto1fLXXl1JTH7q31jRdJe/zxgjH
tKQxeqrGB7DNYHHfPlob5hapJf0ExHR23Sp011ePuDjRoFXIRFG0LUQK2oFRwFhZYWR3fZbR
QLQ7xMC1zuIL6AkX36e2/22wKcbhg+ofOZ/oG4NLpxD5rGoY3FJh+iOafw+3Ydu3l0Jf0EM+
kEw3r/HgSrHATBdAPnpvMNNVGdu20EDCPCu2ZLaYbwaA16Jc+7Eqqo6xAJ7HZpjd/jm8Juzn
ojew1FtZ5mxBGU5l/4L6vKza013se8k9uu3MtUBjWYzVYzVWjOL/4OZ2OLkbIrjyeDnWNIIA
IGIUt78s7q5XEy+r9jDg7jCCschqM75632wZwIrvpR3aDUaSrkFNnSYfrl18gZlnPxdM0S7b
2NzAvtRk7I+GY6/ZcFlz+U2cpK6tgWOR16baj78mzY+yjbnySFHdVfaDIteXs38EGABiexih
DWVuZHN0cmVhbQ1lbmRvYmoNMzcgMCBvYmoNMTY2NiANZW5kb2JqDTM4IDAgb2JqDTw8IC9G
aWx0ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGggMzcgMCBSID4+IA1zdHJlYW0NCkiJlFfbbtw2
EH33V/CpIIuVLOq6ChAUaJoCKVAgCDZPSR9oLderWDfo4kV+o1/cuZCyNo5TxIYlXmaGM2fO
jOjDXzeHX2+CKIyiKBGH6saPLjefZLe0d3asu3tVhoUUKtCRHO3UL6MKijCRlRWXej7jOszE
sR5tNYu6HZq6MnPdd5PoT6IzKsjDTOKCacTUP9rR1qAUwyKb7mY3/ao0zkMVkEUVxJF8p+IY
1kAEJUQ9sSOmmXoxLXdf8My5F0aofw4UzSfZLs1cz8vR8vnuZDMMY2+qs512Phb0LCcncrng
oalszNxDfLqAMbmTSzFQiKkcVQzT/rGeMLidMN1xJ+oOYmqtqMxkJxDUYSx3glwAW3aEk+fR
GvQftb1N7y1jn63YZ4w9uOqOCcXhvNBh5IUDKXP5MINbXUEXp34ENDoKrpAXlnunCOAOg4Rc
2NFbs4jeIBr7aBtx7FsD8XSmddpiPptZ2A58Mfd22mBcd2DkZKraG0IUwStkBGhZPpYXG8xd
Ifs7J4qQ2MYO577DFG9iMscjkQv8miZmHqwyrImX8tOZzdpWtEDTeRIVO21UArujC+G0NKLq
vZeoC5v1ERKDaIVrSBGlANEHaA9faAkSonE5cCPMDCCZyoMK9pDnj/+qVE5wvErDvcRqwfm5
HsTZ0NIk+M1oVDRu0IVYsg5vo5ogRGHAG9OMzGp5H70vIfxYYwFMixNREdgRTzoNS888O2JZ
+OSn8j2itZcBSEMeSncy23AKCsx3uMfz+dKj7QcfRHfExLp4ruhbrPQtVpBigJnoVqBDkIpS
jp2dsWCqZjk63hREkcSFxZlFHoy1Sz9s9cuMhcwQ9h30D6QIapJ16y1VVO9XzCqYMwnFRUIW
yKEptIf1NOKsQypGvwGrFDaCO+Nl7PH/KhZiI6NQqZO4ID8SOiyRTYNL7VrAzM9729qOAuNq
ib9XpFCdR6fV8+paoM+qgpso1kNIru7DKBUR/NIgBSPw0kUWxnvs8O2W8TEyXsckDq9UpyG8
dA7dOHfCa56DbaKhOUFHRuoqRGyE0AqiTw4O7cTlXFc0OTN8QbwPcy2gADTA9sdLWJ4BL9P4
CjbHb7rEnbXdigtj3EKnnKGkLXJ07JerpsQNyRz7Ya4dSNAnAfkP8DVrFuqaOopfQA1Ay3WY
PgcteQ5auhc6y8LyCTSt1w5CQwLt7qtKAAJsr0rjwEKFQoGsJAT4ocfAVik/Kp3Qx3DFL/0W
v2fl976xXT30MxCsNq5afCG86buTr0eFZN/Wz2f5wT6G4m/jBEbzcFU303kn4ihya/FntROY
K0qIr89TPbaQhjsn5M+l7fXDwMngLFBkkcBmrjGobSf+yR/MyNvDTRGFkAhMdC50CnhFYS5G
e3O6+f2wyVgMoINcBB/kFJINCePWn2MeUYYGbCyKwzjirEqNQiVkmYRoUKRIl7L4xhIdJCbM
TpwlMMHwIFEphgg8V4gJFEjhnvA1j+UrGt66J121LkRy/9QZvMKat1hxQUt+qXsyy1ZGvlDZ
yk1tBd0Ea1y2ipLkXhYIoVkda04aNlLT06vQdgjfCmiOEK8cfuPU8tlfsYNqOdjX9SYuSyLu
lAm7ayp/4VlDAoYEyPQ9Pl4rvao5wcGMdhPZ6wP1v0IGHxT22rdvAkXztwrvaqHOU7egy7KI
UDFzC++IccgTuJjmoqRnUsIhMVIFcu65cp3kNC+geW6zHNHmxNVHF2gpXqIQ2M+3TYSb7vdo
tM+h+z613YTJIv6ki121KCxMgKIEJLDdiv4RxnbEZ+0aMECDREkBmB18KfCaa62vNMdJwCLN
ij2zkjuJ9ryEHoYZRRE5D9gNtHx1e+tWLpeLootuWHuhhVRC+KxvVW97Vp3u+X07OVss7u3V
kLJcuq1buLrzKCB+GWQim8Wej/cut1FRO0cDj7Rdz7V1JJ1YZLR4B79Wm51PQT34Y4iPfIQ3
4CO4qBiLzumMLPrgosKvfObMsgt2dIscklPrtvFonsA/OdhRnQ9Hfp08M/V+DwwW+wz5kCQZ
drIfUTMDL8v4ijk/Qc2ihMO21ExeoiY8c98Gf9jhsmRtcXxXz+lv4DvbKxje0l+QA8R4Q/BP
jVzFTsYKC+vzQvdkDLV7NgbkomUyNkEzKOWw+CXgALQq/M4/GUP9GvU7lkYpaO4xSVtew4a/
8b3lb3Jz3TmKJMzgMwJb2Y87RxLpMNpv0XsxPWD8PwEGAGkRqxINZW5kc3RyZWFtDWVuZG9i
ag0zOSAwIG9iag08PCANL1R5cGUgL0V4dEdTdGF0ZSANL1NBIGZhbHNlIA0vU00gMC4wMiAN
L1RSIC9JZGVudGl0eSANPj4gDWVuZG9iag0xIDAgb2JqDTw8IA0vVHlwZSAvUGFnZSANL1Bh
cmVudCA2IDAgUiANL1Jlc291cmNlcyAzIDAgUiANL0NvbnRlbnRzIDQgMCBSIA0vQW5ub3Rz
IFsgMiAwIFIgXSANL01lZGlhQm94IFsgMCAwIDU5NSA4NDIgXSANL0Nyb3BCb3ggWyAwIDAg
NTk1IDg0MiBdIA0vUm90YXRlIDAgDT4+IA1lbmRvYmoNMiAwIG9iag08PCANL0Rlc3QgWyAx
IDAgUiAvRml0QiBdIA0vVHlwZSAvQW5ub3QgDS9TdWJ0eXBlIC9MaW5rIA0vUmVjdCBbIDE0
MyA3NzYgMTUwIDc4NiBdIA0vQyBbIDAgMCAwIF0gDS9Cb3JkZXIgWyAwIDAgMCBdIA0vSCAv
SSANPj4gDWVuZG9iag0zIDAgb2JqDTw8IA0vUHJvY1NldCBbIC9QREYgL1RleHQgXSANL0Zv
bnQgPDwgL1RUMiAxNyAwIFIgPj4gDS9FeHRHU3RhdGUgPDwgL0dTMSAzOSAwIFIgPj4gDS9D
b2xvclNwYWNlIDw8IC9DczUgMTggMCBSID4+IA0+PiANZW5kb2JqDTQgMCBvYmoNPDwgL0xl
bmd0aCAxODQ5IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCkiJlFdNk6TIDb3X
r9ARHA3NZ0HtcXbHYzuiHRse+rCe2QNNZU+xQ0EFCd323v0L7B+8T1JCUT0Of3RHFGSmUlIq
35PEu2p3X1UJxVQ97+KEIvzjkcdlmFEZ5eE+i1Kqzrv7721OjRWBiGyzu//wMaYvdhdR1fDP
685LyK9+2QVpEaYUJGF5oOqHXRRGUZSzULC8QvQvxg7dPLVDT3Ga8rYyjDLRLS9xlobFnopi
H2alerAxlPGGq7dxVoRlBuEoPOxVOLiavVr95NGTH8RRmHt/9+MDHjSd3IQhfvH+6McJRpUf
HMLCe6QfO9O3l2Ey/dTWox8Um73fD/2zzhi3YvrG0GfvAariMPXq0c3XforhV2NPd5REUfLZ
D9VcdWotbWLh/1z9aRfgzAkFcRjnHEA9SrkepdSjQHo6GRp6Q6e6P96R2Co9Uz/ry3M7nmEk
9awImr/JSUuvtVPbf/EPYeLROHSGsJvs4FZfzGha2aYi/eQHSapnxobheROnhOOEwSM9mPOT
gVlv9HmaPk71ZCy9ttNJz1T9Di6Pxl5MM9E0UN11Q8MbEBpPjs5eiLZz3de8ovYN1s+IPlvG
MdS1kViV8xga2xdDzTD3E2IQ89kXd0VhMxwN9bMG48mM6+llFZqG2cWugc+Luxr2wxr2g4Zd
Qr3EHj+ji37bizsHz07j3Ewa84+mGc3EdsPYq9W5gzoXewFCFXsf/KAE0gwGB2/RoaOx7tSb
A2AtWJeXONqHJRWM0+QbZvyDbqlRlpDdH7Iw3hIj3i/H4jchBiwneeT9E96miMRA7qWWC/3K
KAEQ4nDP7iM5eNQLyveIv7GWt2NSpfmg5UaydtHVh1PcOkP9YokRiE1kejuPZpk96awBQl+Y
ZqzXiBWn4IvPNhSmevNicwPUGOPKgUWgqhufnGb1avRZjD76QY7ncnj3FCjr661bb9CSrmhJ
NawjtO+RABhwgnW8j0cmgEPmillHscIjhav4m3qzH/DjvMIWApeu7q0qYNLUx6PAN4WbVjzt
Onoy9Dx3nVxLvqo+u7E60vZT3fYG4K3thqWI/2nkeWAauakZzuDf0flTC1ffA06ZY+QmHxQI
M+fSR5L8mTN58duJjrlvG92N5NAf6/HY/srByZzOm0jGK+9ixzu5mILJ7gdAszeM4Jy+cqxA
F3o91W7RvBhGSiy3GgOAl0unK5w/+Nksok6HwpDfTqrNCIZjxROrEOxhnmZrjv9ymToO82ui
3tBQWIjDyAnW2hfrURArANaH0q4VDiXAR8yWY4/znJ9xXTJ+BpwRj8AMZAO8GA6Ckx4gzUnn
oMM71rdcBRS0/Us7OR2gRoSDJNg0M/YamR7As26SCsjHdZKLggqRA104sdHAto9mFMc229vj
dasssrMzHGHgJXwuMXo9zH9hS3u+dA4kltEl8LqMw0trl6lrrbRIhGg44O9ndBMvIT24cguQ
bivtlShoNN548E1/gNr9H4o23TllFqRzfcNwmcCUt22FRHztJZg4a43ch1ol86VKCv1eDUiL
59A7Tcz1nG8+EqbezNIvwuPiujwtN5dsLN47KefHe5l1nc3vfWbTGo5rixFseww71bi4vQe6
ynP0OfcdfWkjftU5Ld7y2rgJIK818m4J7ZBs0nHI1gXArCK8o/d/fnz47IuEK8cb6c5ZEJJk
blKyp52fbLNxqX0ym5FzR/08qsmtXmuFOFdHyC4U4ZEVR9iqM1p4Zx1YJr9MqG4mxy2iihVR
hYawGfoXbQ+1o0GW1sss0G3Q4F6fAYgURDGduZyGRUDQlLrA9GZ6XcRHEf+6NFjr1afej5Lf
ci94qpGmnDjJ3vGrZTY33XzUUpKu7W9x0/6mnFF5chK4IvVgf3jFyrdpTrPbyqbYseknNFaW
rFTOwkNvLDkUZaGTlqjQ5Jojd3EidWiMJKFm/y6hRtdce5NhNcV+8j6pu1a9b+VyUR7M8Wdd
uD3CquL2GEgqyxUmyzHsqR3osUINyrxHP9EGX0P+Nqul+eq0FC2py9oF5tICCP1GxpvmC24P
AuXxB4FGKoWTuTo61tcy6lTD/3aItcGLXIPXNN/RwxjSH4a5Y9Tybf+VA5RwxYvAinq4ox9a
gSo3dRNX2MpoC8Fd9qaGi19IC29KeelK+Tufy/qsakdTz05+veAE64e3N/x//vFx31e7mFra
4cOvpBKB5W/BjNguvhB2z7t31aYXTsAMiO3DfaS9sMaMvzBFRF5EVXFY+2X91rztwIuMP1Hx
e6tIzJDluCd5igEfEFeQO3ieuBVFiUfqLd3vhWN08L6Twb37RSQT7xVpJlt/Yw5o2OqSbp1V
2zLZb5WrpkGV2y+65BRbn783LvMymUvxlg8plNatatXVqq5e96k8l0O30zh9akv3c9u3epTr
SrieXrw486iEPCMC11iABggssI97SrEkt4j7WK7x9gbSCE3+9gYiWbOK+VSZsUDktwEAW50E
pwplbmRzdHJlYW0NZW5kb2JqDTUgMCBvYmoNPDwgDS9Qcm9kdWNlciAoQWNyb2JhdCBEaXN0
aWxsZXIgNC4wNSBmb3IgV2luZG93cykNL0NyZWF0b3IgKE1pY3Jvc29mdCBXb3JkIDkuMCkN
L01vZERhdGUgKEQ6MjAwNDA0MzAxNzEzMDcrMDInMDAnKQ0vQXV0aG9yIChBbm9ueW1vdXMp
DS9UaXRsZSAoSU5URVJOQVRJT05BTCBURUxFQ09NTVVOSUNBVElPTiBVTklPTikNL0NyZWF0
aW9uRGF0ZSAoRDoyMDA0MDQzMDE3MTI0NykNPj4gDWVuZG9iag02IDAgb2JqDTw8IA0vVHlw
ZSAvUGFnZXMgDS9LaWRzIFsgOSAwIFIgMSAwIFIgXSANL0NvdW50IDIgDT4+IA1lbmRvYmoN
eHJlZg0wIDcgDTAwMDAwMDAwMDAgNjU1MzUgZg0KMDAwMDAxNjI4MCAwMDAwMCBuDQowMDAw
MDE2NDQ5IDAwMDAwIG4NCjAwMDAwMTY1OTIgMDAwMDAgbg0KMDAwMDAxNjcyNiAwMDAwMCBu
DQowMDAwMDE4NjQ5IDAwMDAwIG4NCjAwMDAwMTg4ODQgMDAwMDAgbg0KdHJhaWxlcg08PA0v
U2l6ZSA3DS9JRFs8MjllYTRiOTY3ZmI3OWFmOTIyZmU3YmI5Mjc0MjA1Yzg+PDI5ZWE0Yjk2
N2ZiNzlhZjkyMmZlN2JiOTI3NDIwNWM4Pl0NPj4Nc3RhcnR4cmVmDTE3Mw0lJUVPRg0=
--------------070305030709050008070103--

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



From ietf-admin@ietf.org  Fri Apr 30 15:38: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 PAA25651
	for <ietf-archive@ietf.org>; Fri, 30 Apr 2004 15:38: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 1BJdqC-0005jo-TA
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 15:38:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJdpS-0005dS-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 15:37:46 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJdob-0005Vr-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 15:36:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJdSW-0007On-3F; Fri, 30 Apr 2004 15:14:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJdKz-0004GT-GS
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 15:06: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 PAA22846
	for <ietf@ietf.org>; Fri, 30 Apr 2004 15:06: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 1BJdKv-0002tu-VQ
	for ietf@ietf.org; Fri, 30 Apr 2004 15:06:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJdK0-0002pY-00
	for ietf@ietf.org; Fri, 30 Apr 2004 15:05:16 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJdJ8-0002lt-00
	for ietf@ietf.org; Fri, 30 Apr 2004 15:04:22 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BJdJ8-0007ov-01; Fri, 30 Apr 2004 14:04:22 -0500
Date: Fri, 30 Apr 2004 15:04:20 -0400
From: John C Klensin <john-ietf@jck.com>
To: jfcm <info@utel.net>, ietf@ietf.org
cc: robert.shaw@iu.int.cnri.reston.va.us
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <869BCB72AB80C62F7050AF74@scan.jck.com>
In-Reply-To: <6.0.1.1.2.20040430183140.05d5ceb0@mail.utel.net>
References: <ACBFB13DAC66EE23B2F5520F@scan.jck.com>
 <6.0.1.1.2.20040430183140.05d5ceb0@mail.utel.net>
X-Mailer: Mulberry/3.1.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 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

Jefsey (and others),

Due to prompt action on the part of ICANN staff once this was 
called to their attention, the problem is now fixed and, due to 
some spam-cleaning done at the same time, the posting is now at 
http://forum.icann.org/lists/stld-rfp-general/msg00039.html/.

The implication of your posting that this might have been 
deliberate (at least as I read "singular impeachment") does not 
appear to me to be justified by anything I have seen.   Instead, 
I suspect that the problem results from sloppy or incorrect 
implementations of the standards: software that relies on 
content-type information (in either email or HTTP) would 
presumably have no trouble opening the original message 
attachment.  Software that relies, instead, on file "type" 
suffixes or other sometimes-random information, as much 
Windows-based software appears to do, can get itself and the 
user rather throughly confused.  It is hard to realistically 
blame that problem on some malice or conspiracy at ICANN (or the 
ITU, or anywhere else in that set of processes).

People will have to decide for themselves how "most important" 
this entry is.   Personally, I found it a bit circuitous, asking 
for discussion (clearly a good idea) rather than really taking a 
position.  I was,  however, pleased to see the ITU Secretary 
General recognizing IETF's role in ENUM... that part of the 
story has sometimes gotten lost.

And, contrary to your note, the posted note appears to comment 
directly only on one of the two TEL. proposals and not at all on 
the MOBI. one.  Whether one can impute a conspiracy to that, or 
whether the ITU really only sees a significant problem with that 
one proposal, is something you would have to address with them.

regards,
   john



--On Friday, 30 April, 2004 18:36 +0200 jfcm <info@utel.net> 
wrote:

> At 03:42 30/04/04, John C Klensin wrote:
>> http://www.icann.org/tlds/stld-apps-19mar04/stld-public-comme
>> nts.htm
>
> Dear John,
> it seems that (one of the) most important entry (the letter
> from ITU regarding the .tel/.mobi requests) cannot be
> accessed.
> http://forum.icann.org/lists/stld-rfp-general/msg00043.html
> This seems to be a singular impeachment to a transparent
> debate on the matter.
> Due to the delay I suggest that ITU sends IETF a copy while
> you might as a BoD Member ask staff to urgently correct that
> situation.
> jfc


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


From exim@www1.ietf.org  Fri Apr 30 15:50:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26815
	for <ietf-archive@odin.ietf.org>; Fri, 30 Apr 2004 15:50:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJdoc-0004i1-34
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 15:36:54 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3UJasJZ018102
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 15:36:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJdSW-0007On-3F; Fri, 30 Apr 2004 15:14:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJdKz-0004GT-GS
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 15:06: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 PAA22846
	for <ietf@ietf.org>; Fri, 30 Apr 2004 15:06: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 1BJdKv-0002tu-VQ
	for ietf@ietf.org; Fri, 30 Apr 2004 15:06:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJdK0-0002pY-00
	for ietf@ietf.org; Fri, 30 Apr 2004 15:05:16 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJdJ8-0002lt-00
	for ietf@ietf.org; Fri, 30 Apr 2004 15:04:22 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BJdJ8-0007ov-01; Fri, 30 Apr 2004 14:04:22 -0500
Date: Fri, 30 Apr 2004 15:04:20 -0400
From: John C Klensin <john-ietf@jck.com>
To: jfcm <info@utel.net>, ietf@ietf.org
cc: robert.shaw@iu.int.cnri.reston.va.us
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Message-ID: <869BCB72AB80C62F7050AF74@scan.jck.com>
In-Reply-To: <6.0.1.1.2.20040430183140.05d5ceb0@mail.utel.net>
References: <ACBFB13DAC66EE23B2F5520F@scan.jck.com>
 <6.0.1.1.2.20040430183140.05d5ceb0@mail.utel.net>
X-Mailer: Mulberry/3.1.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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-Transfer-Encoding: 7bit

Jefsey (and others),

Due to prompt action on the part of ICANN staff once this was 
called to their attention, the problem is now fixed and, due to 
some spam-cleaning done at the same time, the posting is now at 
http://forum.icann.org/lists/stld-rfp-general/msg00039.html/.

The implication of your posting that this might have been 
deliberate (at least as I read "singular impeachment") does not 
appear to me to be justified by anything I have seen.   Instead, 
I suspect that the problem results from sloppy or incorrect 
implementations of the standards: software that relies on 
content-type information (in either email or HTTP) would 
presumably have no trouble opening the original message 
attachment.  Software that relies, instead, on file "type" 
suffixes or other sometimes-random information, as much 
Windows-based software appears to do, can get itself and the 
user rather throughly confused.  It is hard to realistically 
blame that problem on some malice or conspiracy at ICANN (or the 
ITU, or anywhere else in that set of processes).

People will have to decide for themselves how "most important" 
this entry is.   Personally, I found it a bit circuitous, asking 
for discussion (clearly a good idea) rather than really taking a 
position.  I was,  however, pleased to see the ITU Secretary 
General recognizing IETF's role in ENUM... that part of the 
story has sometimes gotten lost.

And, contrary to your note, the posted note appears to comment 
directly only on one of the two TEL. proposals and not at all on 
the MOBI. one.  Whether one can impute a conspiracy to that, or 
whether the ITU really only sees a significant problem with that 
one proposal, is something you would have to address with them.

regards,
   john



--On Friday, 30 April, 2004 18:36 +0200 jfcm <info@utel.net> 
wrote:

> At 03:42 30/04/04, John C Klensin wrote:
>> http://www.icann.org/tlds/stld-apps-19mar04/stld-public-comme
>> nts.htm
>
> Dear John,
> it seems that (one of the) most important entry (the letter
> from ITU regarding the .tel/.mobi requests) cannot be
> accessed.
> http://forum.icann.org/lists/stld-rfp-general/msg00043.html
> This seems to be a singular impeachment to a transparent
> debate on the matter.
> Due to the delay I suggest that ITU sends IETF a copy while
> you might as a BoD Member ask staff to urgently correct that
> situation.
> jfc


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



From ietf-admin@ietf.org  Fri Apr 30 18:10: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 SAA08380
	for <ietf-archive@ietf.org>; Fri, 30 Apr 2004 18:10: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 1BJgD6-00011p-Au
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 18:10:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJgC9-0000tp-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 18:09:22 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJgBK-0000nz-00
	for ietf-archive@ietf.org; Fri, 30 Apr 2004 18:08:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJg47-0006On-DD; Fri, 30 Apr 2004 18:01:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJg0Y-0004jT-Q4
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 17:57:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07160
	for <ietf@ietf.org>; Fri, 30 Apr 2004 17:57: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 1BJg0W-0007Sb-0b
	for ietf@ietf.org; Fri, 30 Apr 2004 17:57:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJfza-0007Nx-00
	for ietf@ietf.org; Fri, 30 Apr 2004 17:56:23 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJfyz-0007Jg-00
	for ietf@ietf.org; Fri, 30 Apr 2004 17:55:45 -0400
Received: from f01m-29-113.d0.club-internet.fr ([212.195.220.113] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BJfys-0000CQ-E2; Fri, 30 Apr 2004 14:55:39 -0700
Message-Id: <6.0.1.1.2.20040430222147.04205eb0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 30 Apr 2004 23:35:34 +0200
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Cc: robert.shaw@iu.int.cnri.reston.va.us
In-Reply-To: <869BCB72AB80C62F7050AF74@scan.jck.com>
References: <ACBFB13DAC66EE23B2F5520F@scan.jck.com>
 <6.0.1.1.2.20040430183140.05d5ceb0@mail.utel.net>
 <869BCB72AB80C62F7050AF74@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>
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 21:04 30/04/04, John C Klensin wrote:
>Jefsey (and others),
>Due to prompt action on the part of ICANN staff once this was called to 
>their attention, the problem is now fixed and, due to some spam-cleaning 
>done at the same time, the posting is now at 
>http://forum.icann.org/lists/stld-rfp-general/msg00039.html/.

Dear John
Thank you for that.

>The implication of your posting that this might have been deliberate (at 
>least as I read "singular impeachment") does not appear to me to be 
>justified by anything I have seen.

I only meant (I just checked it in dictionary) "deviating from the usual or 
expected; odd. See Synonyms at strange".  But it is good you understood it 
your way, got the problem fixed and have now your response in the records. 
This will not be implied further on.

>It is hard to realistically blame that problem on some malice or 
>conspiracy at ICANN (or the ITU, or anywhere else in that set of processes).

True. That possible future blame is now defused ...  except that now I just 
loop back in the mail without getting the attachment :-) May be only 
because of my PC?

>People will have to decide for themselves how "most important" this entry 
>is.   Personally, I found it a bit circuitous, asking for discussion 
>(clearly a good idea) rather than really taking a position.  I 
>was,  however, pleased to see the ITU Secretary General recognizing IETF's 
>role in ENUM... that part of the story has sometimes gotten lost.
>
>And, contrary to your note, the posted note appears to comment directly 
>only on one of the two TEL. proposals and not at all on the MOBI. 
>one.  Whether one can impute a conspiracy to that, or whether the ITU 
>really only sees a significant problem with that one proposal, is 
>something you would have to address with them.

Please understand you are at advantage: you were able to read the document. 
I was not.
Robert's mail says "Applications" (plural).

As you know in intelligence 80% is the fact there was an exchange, and 20% 
the content.
- the fact there is a letter is important (personal readings are less)
- the fact you speak of "conspiracy" is important (even if I don't 
understand about what/by who it could be). It means the matter is touchy.

Let build on that. There is a need to talk says Robert Shaw. Good point: 
you accept to talk. Maybe will you recall that they asked the same in 2000? 
I read positively what you say they said: (a) it means there is a dialog 
(b) this means they do not take position and respect the Internet autonomy 
(c) their 2000's position lead to ENUM. This ICANN / ITU / IETF way was 
positive last time. Why not this time, too?

(BTW, IMHO ITU is no more at ease than ICANN with the current post-WSIS 
global situation ).

All what I fear is that under such circumstances and pressures, someone 
takes a wrong decision he would not have taken otherwise. No one wants to 
harm the DNS and endanger a key thing which works. We all agree with that. 
But a debate is open on propositions which may harm the DNS. This debate 
was open by ICANN, so it rises questions. Basically, why is this debate 
about transport protocol being described in the TLD instead of being 
described in the scheme, happening now? It should have been prevented by 
the wording of the call for propositions or by an ICANN document, proposed 
and discussed by the GNSO, reviewed on technical parts by IETF. It should 
have described what is the DNS semantic and what is expected from 
propositions etc. If I refer myself to ICP-3, I tend to think ICANN failed 
its own precaution criteria for testing, yet here we are not testing.

Actually, I am surprised we have a second TLD round, while the work on the 
evaluation report on the first round is not even started. Why that? Is 
there some pressure on ICANN or is it ICANN putting some pressure? In both 
cases one can nurture some concerns. I have no bad idea about ICANN, but I 
see that .mobi, .tel and .mail would be catastrophes for a global DNS, not 
to speak of political consequences which are not our concern here.

I also see that ICANN still has today the capacity to hurt the DNS in 
accepting them.  What I want is that this technical major threat on the 
global internet stability is removed. And that this kind of matter is 
handled by a world consensus where IETF may have its say.as well as ITU on 
behalf of Govs, Consumers organizations and Lingual organizations like the 
one we created (Eurolinc) with Louis Pouzin, J-L Grange etc.

jfc









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


From exim@www1.ietf.org  Fri Apr 30 18:20:37 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09434
	for <ietf-archive@odin.ietf.org>; Fri, 30 Apr 2004 18:20:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJgBN-0002md-09
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 18:08:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3UM8WMf010695
	for ietf-archive@odin.ietf.org; Fri, 30 Apr 2004 18:08:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJg47-0006On-DD; Fri, 30 Apr 2004 18:01:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJg0Y-0004jT-Q4
	for ietf@optimus.ietf.org; Fri, 30 Apr 2004 17:57:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07160
	for <ietf@ietf.org>; Fri, 30 Apr 2004 17:57: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 1BJg0W-0007Sb-0b
	for ietf@ietf.org; Fri, 30 Apr 2004 17:57:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJfza-0007Nx-00
	for ietf@ietf.org; Fri, 30 Apr 2004 17:56:23 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJfyz-0007Jg-00
	for ietf@ietf.org; Fri, 30 Apr 2004 17:55:45 -0400
Received: from f01m-29-113.d0.club-internet.fr ([212.195.220.113] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BJfys-0000CQ-E2; Fri, 30 Apr 2004 14:55:39 -0700
Message-Id: <6.0.1.1.2.20040430222147.04205eb0@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 30 Apr 2004 23:35:34 +0200
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: [Ietf] New .mobi, .xxx, ... TLDs?
Cc: robert.shaw@iu.int.cnri.reston.va.us
In-Reply-To: <869BCB72AB80C62F7050AF74@scan.jck.com>
References: <ACBFB13DAC66EE23B2F5520F@scan.jck.com>
 <6.0.1.1.2.20040430183140.05d5ceb0@mail.utel.net>
 <869BCB72AB80C62F7050AF74@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Id: IETF-Discussion <ietf.ietf.org>
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>

At 21:04 30/04/04, John C Klensin wrote:
>Jefsey (and others),
>Due to prompt action on the part of ICANN staff once this was called to 
>their attention, the problem is now fixed and, due to some spam-cleaning 
>done at the same time, the posting is now at 
>http://forum.icann.org/lists/stld-rfp-general/msg00039.html/.

Dear John
Thank you for that.

>The implication of your posting that this might have been deliberate (at 
>least as I read "singular impeachment") does not appear to me to be 
>justified by anything I have seen.

I only meant (I just checked it in dictionary) "deviating from the usual or 
expected; odd. See Synonyms at strange".  But it is good you understood it 
your way, got the problem fixed and have now your response in the records. 
This will not be implied further on.

>It is hard to realistically blame that problem on some malice or 
>conspiracy at ICANN (or the ITU, or anywhere else in that set of processes).

True. That possible future blame is now defused ...  except that now I just 
loop back in the mail without getting the attachment :-) May be only 
because of my PC?

>People will have to decide for themselves how "most important" this entry 
>is.   Personally, I found it a bit circuitous, asking for discussion 
>(clearly a good idea) rather than really taking a position.  I 
>was,  however, pleased to see the ITU Secretary General recognizing IETF's 
>role in ENUM... that part of the story has sometimes gotten lost.
>
>And, contrary to your note, the posted note appears to comment directly 
>only on one of the two TEL. proposals and not at all on the MOBI. 
>one.  Whether one can impute a conspiracy to that, or whether the ITU 
>really only sees a significant problem with that one proposal, is 
>something you would have to address with them.

Please understand you are at advantage: you were able to read the document. 
I was not.
Robert's mail says "Applications" (plural).

As you know in intelligence 80% is the fact there was an exchange, and 20% 
the content.
- the fact there is a letter is important (personal readings are less)
- the fact you speak of "conspiracy" is important (even if I don't 
understand about what/by who it could be). It means the matter is touchy.

Let build on that. There is a need to talk says Robert Shaw. Good point: 
you accept to talk. Maybe will you recall that they asked the same in 2000? 
I read positively what you say they said: (a) it means there is a dialog 
(b) this means they do not take position and respect the Internet autonomy 
(c) their 2000's position lead to ENUM. This ICANN / ITU / IETF way was 
positive last time. Why not this time, too?

(BTW, IMHO ITU is no more at ease than ICANN with the current post-WSIS 
global situation ).

All what I fear is that under such circumstances and pressures, someone 
takes a wrong decision he would not have taken otherwise. No one wants to 
harm the DNS and endanger a key thing which works. We all agree with that. 
But a debate is open on propositions which may harm the DNS. This debate 
was open by ICANN, so it rises questions. Basically, why is this debate 
about transport protocol being described in the TLD instead of being 
described in the scheme, happening now? It should have been prevented by 
the wording of the call for propositions or by an ICANN document, proposed 
and discussed by the GNSO, reviewed on technical parts by IETF. It should 
have described what is the DNS semantic and what is expected from 
propositions etc. If I refer myself to ICP-3, I tend to think ICANN failed 
its own precaution criteria for testing, yet here we are not testing.

Actually, I am surprised we have a second TLD round, while the work on the 
evaluation report on the first round is not even started. Why that? Is 
there some pressure on ICANN or is it ICANN putting some pressure? In both 
cases one can nurture some concerns. I have no bad idea about ICANN, but I 
see that .mobi, .tel and .mail would be catastrophes for a global DNS, not 
to speak of political consequences which are not our concern here.

I also see that ICANN still has today the capacity to hurt the DNS in 
accepting them.  What I want is that this technical major threat on the 
global internet stability is removed. And that this kind of matter is 
handled by a world consensus where IETF may have its say.as well as ITU on 
behalf of Govs, Consumers organizations and Lingual organizations like the 
one we created (Eurolinc) with Louis Pouzin, J-L Grange etc.

jfc









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



